Rfi Template Final

Document Sample
Rfi Template Final Powered By Docstoc
					Request for Information
Digikoppeling (ebMS and WUS)
Messaging Software for endpoints,
intermediaries and brokers (growing
model), scalable for high-volumes and
high-performance
Author(s):
       Ernst Jan van Nigtevegt, Pim van de Eijk,(Sonnenglanz Consulting) Michel de Zwart and Bob
       van Os, Frank Terpstra, Julien Rentrop (ICTU programma Renoir)
Abstract:
       This Request for Information (RFI) is issued on behalf of XXXXX in the government sector in
                                                                              1
       the Netherlands that have standardized on the use of the Digikoppeling
       (http://www.logius.nl/producten/gegevensuitwisseling/digikoppeling/) Messaging specification
       to facilitate large scale automated electronic exchange of business documents.
Procedure:
      We wish to complete this first vendor selection phase within 6 weeks. Therefore we ask you,
      as a candidate vendor of Digikoppeling Messaging software, to react to this questionnaire
      promptly and to supply us your response within XXX working days.
         On the basis of the response of vendors we will eliminate or promote solutions from the long
         list of candidate solutions to a short list of candidate solutions, develop a short list
         recommendation and present this to the customer for approval.
         Subject to customer approval, we will request intent to bid responses from the short list of
         vendors to determine who will be bidding for the project and to establish who has authority to
         quote prices for products and/or services in the bid on behalf of the vendor. Subject to
         customer approval, subsequent activities may include any or all of the following activities:
             Develop a Request for Proposal (RFP) from the technical and functional requirements
              defined earlier as well as relevant commercial requirements.
             Contact the short listed vendors to conduct a vendor demonstration to either qualify or
              eliminate vendors and to clarify issues from the RFI or RFP.
          Contact vendor references and/or attend a site visit for an existing vendor customer
         Depending on the expected total costs of the purchase of the solution, the following activities
         may involve a public bidding/tender process.
         In order for your response to be accepted in this phase, please abide to the follow rules:

             Supply all your answers in Word format as well in printed form.
              Send the Word file to this email address:  XXXXXX

             Send the printed version to:
              XXXXX



         1
          Digikoppeling used to be called Overheidsservicebus(OSB) before 1-1-2010. The name
         OSB may still occur in some referenced documents




Request for Information Digikoppeling Messaging Software                                              Page 121
             Your answers must be received by Email (include 3 copies by post) on XXXXX

             For each question your answer may not exceed half an A4 page of written text. Answers
              may be illustrated with diagrams or pictures. In this case the Illustrations and text together
              may not exceed one page of A4 for each answer.

             Answers must use the same numbering corresponding with the questions.




Request for Information Digikoppeling Messaging Software                                              Page 221
Table of Contents
1      Purpose and Scope ........................................................................................................................ 4
2      Vendor and Product........................................................................................................................ 5
    2.1      Contact information ................................................................................................................ 5
    2.2      General information ............................................................................................................... 5
    2.3      Differentiation ......................................................................................................................... 6
3      Pricing, licensing, terms and conditions ......................................................................................... 7
4      Support ........................................................................................................................................... 9
    4.1      Support availability ................................................................................................................. 9
    4.2      Support offerings ................................................................................................................... 9
    4.3      Implementation ...................................................................................................................... 9
5      System Architecture ..................................................................................................................... 10
    5.1      Platforms .............................................................................................................................. 10
    5.2      Interface ............................................................................................................................... 11
    5.3      Performance / scalability...................................................................................................... 12
    5.4      High Availability Solutions.................................................................................................... 13
    5.5      System Management ........................................................................................................... 13
    5.6      Security and related management ....................................................................................... 14
6      Requirements at the level of the Digikoppeling Messaging Service ............................................ 15
    6.1      Required Digikoppeling ebMS 1.1 Messaging Profile ......................................................... 15
    6.2      Digikoppeling ebMS 2.0 Messaging Profile ......................................................................... 15
    6.3      Interopability ........................................................................................................................ 16
    6.4      Extensibility .......................................................................................................................... 16
    6.5      Configuration ....................................................................................................................... 17
    6.6      Other Digikoppeling Support Issues .................................................................................... 17
7      Requirements at the level of the Digikoppeling WUS (Web Services) Profile ............................. 18
    7.1      Required Digikoppeling WUS 1.1 Profile ............................................................................. 18
    7.2      Optional Digikoppeling WUS 2.0 Profile .............................................................................. 18
    7.3      Features ............................................................................................................................... 19
    7.4      Interopability ........................................................................................................................ 19
    7.5      Configuration ....................................................................................................................... 19
8      Revision History............................................................................................................................ 20
9      References ................................................................................................................................... 21




Request for Information Digikoppeling Messaging Software                                                                                            Page 321
1 Purpose and Scope
This questionnaire will be used for Digikoppeling Messaging Software Vendor evaluation for an
interoperable, open, secure, reliable Internet-based messaging solution to facilitate large scale
automated electronic exchange of business documents between organizations in the government
sector in the Netherlands.



Digikoppeling is an essential part of the Dutch e-government as documented in the NORA(Dutch
Government Reference Architecture). Within the dutch e-government Service Oriented architecture
plays an important part. The Digikoppeling standards, based on the international webservices(W3C)
and ebXML/ebMS standards allow SOA interfaces to be developed. The Digikoppeling standards take
care of the logistics of electronic messaging between all types of government organizations, ranging
from ministries to municipalities. It is important that the wide array of different internal software
landscapes which these government organizations contain can interoperate with each other. That is
why each organization has to implement an adapter to convert their internal messaging standards to
Digikoppeling standards for communication with other government organizations. This RFI concerns
such an adapter.

We are looking for solutions in one or more of the following areas:

        Digikoppeling Messaging Endpoint functionality.

        Digikoppeling Messaging Intermediary functionality.

        Digikoppeling Messaging Intermediary with limited additional functionality, such as protocol
         conversion, content-based routing.

        Enterprise Application Integration.

        'Broker' functionality.

Vendors should be able to provide solutions to all of these requirements. Fields marked with * are
knock out criteria.

The current needs and future direction for the messaging solution are specified in [Requirements
W1].




Request for Information Digikoppeling Messaging Software                                          Page 421
2 Vendor and Product
Evaluation will rank vision, completeness, and partnering/competitive advantage.

2.1 Contact information
Question                                                   Response

2.1.1 Company name:
       In which country(ies) is your company (head
       office) based?
       Is your company registered, or do you have
       a subsidiary listed with, the Dutch chamber
       of commerce (Y/N)?
2.1.2 Contact name:
       Position of contact:
       Phone number of contact:
       Email of contact:


2.2 General information
Question                                                   Response

2.2.1 product name:

2.2.2 Installed base of the product:
      • Number of customers in the Netherlands?
       • Number of customers in Europe?
       • Number of customers world wide?
       • Number of customers in the public sector?
       • Number of customers in the public sector in
       Europe?
       • Average contract value?
2.2.3 References in the public sector in Europe:
      • Description (company, problem, solution)?
      • Can they be contacted (please provide
      name and phone number of person to be
      contacted)?
       Note: this RFI is about solutions supporting
       the Digikoppeling Messaging standard, not
       arbitrary integration solutions. Therefore,
       focus on customer or project references that
       actually use the ebXML and
       WEBSERVICES(W3C) Messaging
       functionality of your product as core features
       of the solution provided and clearly indicate
       how they are used.
2.2.4 Are you willing and able to participate in the
      next phase of the selection (supplying
      information, proposal, demo’s, etc.) without
      costs for demanding party?




Request for Information Digikoppeling Messaging Software                           Page 521
Question                                                   Response

2.2.5 Are you capable of delivering the product on
      a turn key basis (product selling,
      consultancy, development, customizing,
      implementing, support services, etc.) or are
      any third parties or partners used?




       Do you have any strategic alliances with
       systems integrators? If so, with whom?



       Do you have any alliances with other
       software vendors to jointly develop
       software? If so, with whom?



2.3 Differentiation
Question                                                   Response

2.3.1 Please list your four top competitors:


2.3.2 Briefly describe what differentiates your
      product from your competitors.




2.4 Maturity
Question                                                   Response

2.4.1 Please describe the major releases of your
      product(s) over the last two years
      (added/changed features).
2.4.2 Please describe the 2010/2011 roadmap for
      your product(s) (Scheduled releases,
      new/changed functionality, etc).




Request for Information Digikoppeling Messaging Software              Page 621
3 Pricing, licensing, terms and conditions
Evaluation will rank reasonability and flexibility.


Question                                                            Response

1      What is your licensing policy f.i.:
       • What are license conditions?

       • What different kind of licenses are there (such as hot
       or cold standby, high availability, clustered, high
       performance, etc.)?


       What type of licence structure do you apply:
               per CPU
               per URI
               per IP-address
               per message number
               per transferred amount of data
               per CPA
               per trading partner
               other?
       • Are there separate licenses for run time and
       development environments

       • What determines the number of licenses needed?.

       • Are there discounts for large volumes? Please specify.

       • What are license fees for the package, specified per
       needed module?

       • Are there fees for updates?

       • Are there annual fees?

       • What are consultancy costs (per hour /day/ week)



       • Other costs?
       (full licence conditions are allowed as an attachment, the
       answer to this question should be short summary
       addressing issues mentioned above)




Request for Information Digikoppeling Messaging Software                       Page 721
Question                                                          Response

3.2    What is the average cost of the software license (base)
       for an Endpoint Digikoppeling messaging node?
       What is the average cost of the software license (base)
       for a central intermediary Digikoppeling ebMS
       messaging node?
       What is the average cost when the above two options
       are combined?
       See figure below




3.3    What is included (bundled) in a typical sale?

3.4    In relation to the European tenders, what flexibility is
       there with regard to the pricing structure? Please
       specify.
3.5    Is a trial license possible? For what period?




Request for Information Digikoppeling Messaging Software                     Page 821
4 Support
Evaluation will rank quality and completeness.

4.1 Support availability
Question                                                   Response

4.1.1 National support available? (Y/N)
                                rd
       Is this support via a 3 party?
4.1.2 International support available (Y/N)
                                rd
       Is this support via a 3 party?



4.2 Support offerings
Question                                                   Response

4.2.1 How are customizations supported? How
      does the support staff keep up with
      customizations support? Describe
4.2.2 What kind of support is offered for
      installation of new versions? (technical and
      functional? training offered?)



4.3 Implementation
Question                                                   Response

4.3.1 How long does it normally take to implement
      the standard (vanilla) package?
4.3.2 On average, how many resources are
      required to implement the software? What
      skills do they have?




Request for Information Digikoppeling Messaging Software              Page 921
5 System Architecture
Evaluation will rank quality and completeness.

5.1 Platforms
Question                                                   Response

5.1.1 Which if any of the following Operating
      Systems does your product support?
               HP UX
               Linux
               Microsoft Windows
               True 64
               Other? Red Hat
               Virtual Environment
       Please note any required versions and
       dependencies.
5.1.2 Does your system require a Relational
      Database Management System?
      Which if any of the following products can be
      used to provide this functionality?
               Oracle Database
               Sybase
               MySQL
               Other (please specify)
       Please note any required versions and
       dependencies.
5.1.3 If your solution is J2EE-based, is your
      solution known (or has it been validated to)
      work with any of the following J2EE
      application servers?
               JBOSS
               Oracle Application Server
               Apache Tomcat
               Other (please specify)
       Please elaborate and note any required
       versions and dependencies.
5.1.4 Does you solution depend on specific Open
      Source software (other than open source
      software provided by the vendor solution, as
      part of its product)? Please elaborate.
5.1.5 Are there any other software dependencies?
      Please elaborate.




Request for Information Digikoppeling Messaging Software              Page 1021
5.2 Interface
The questions in this paragraph investigate how easily each organization can be “connected” to the
ebXML messaging infrastructure to set up collaborations with other “connected” organizations.

Question                                                   Response

5.2.1 Does your product offer an Application
      Programming Interface (API) for an
      application to compose, send, receive and
      decompose messages?
       If yes, which programming languages does it
       support?
               C/C++
               Java
               PL/SQL
               COM
               C#
               Other (please specify)
       Please note any required versions and
       dependencies.
5.2.2 Does your product support bridge
      functionality to EAI messaging protocols? If
      yes, which of the following protocols can
      your product bridge Digikoppeling messages
      to?
               IBM MQSeries
               Oracle Advanced Queues
               Sonic MQ
               Other/proprietary (please specify)
       Please note any required versions and
       dependencies.
5.2.3 If your product offers a Java interface, which
      interface does it support specifically?
               JMS
               JCA
               JAXM (please elaborate)
               Other/proprietary (please specify)
       Please note any required versions and
       dependencies.
5.2.4 If your solution is Java-based, can it be used
      in environments requiring light-weight,
      standalone configurations (not requiring a
      J2EE application server)?
       Please elaborate.




Request for Information Digikoppeling Messaging Software                                      Page 1121
Question                                                   Response

5.2.5 Does your system consist of a separate
      messaging client and server, or is it a single
      combined functionality? If yes:
               Can this be used to deploy the
                server in the DMZ and the client
                behind the firewall?


               SSL Offloading capability?
       What interface or protocol is used to
       communicate between server and client?


5.3 Performance / scalability
Question                                                   Response

5.3.1 Is the product able to handle 2000
      messages per hour with an average size of
      100 Kbyte?
       Which measures (hardware and/or
       application level) have to be taken to support
       an increase of the above figure by a factor of
       10?


       Is the product able to handle large
       messages like 100 Mbyte or more?


       What are the dependencies?
       Please describe OS, hardware and other
       configuration options assumed in your
       response.
5.3.2 What are the limits for the size of
      messages?
       Does your product have a mechanism to
       split, transfer and reassemble large
       messages automatically as a series multiple
       smaller messages?
5.3.5 Can your system be used in conjunction with .
      SSL/TLS accelerator hardware (offloading)?
      Which products?

5.3.6 Please present real-life examples and
      figures where this has been applied for the
      ebXML and WEBSERVICES(W3C)
      messaging solution.




Request for Information Digikoppeling Messaging Software              Page 1221
5.4 High Availability Solutions
Question                                                   Response

5.4.1 Which hardware level measures can be
      taken to create a high availability (at least
      99%) DIGIKOPPELING messaging solution?
      What are the dependencies?
5.4.2 Which application level measures have to be
      taken to avoid a single-point of failure using
      the Digikoppeling messaging solution?
5.4.3 Which measures can be taken to recover
      gracefully from a system crash?

5.4.4 Can the product run in a cluster environment
      to realize fail-save functionality?

5.4.5 What is the impact of clustering of message
      handling nodes on message ordering?

5.4.6 Please present real-life examples and
      figures where this has been applied for the
      Digikoppeling messaging solution.




5.5 System Management
Question                                                   Response

5.5.1 How can your system be monitored to make
      sure it is working well?
5.5.2 Does your system archive processed       .
      messages? Does your product have screens
      and search options to monitor processed
      messages?


       If yes, can archived messages be deleted /
       purged in a controlled way? Please explain.
5.5.3 What functionality does your system offer to
      manually analyze, correlate, select and re-
      process (sets of) messages?
5.5.4 Does your system have a backup / restore
      procedure?
5.5.5 Does your system have an automatic start
      and stop procedure?
5.5.6 Does your system have a webinterface that
      can be used for remote system management
      and configuration?




Request for Information Digikoppeling Messaging Software              Page 1321
5.6 Security and related management
Question                                                   Response

5.6.1 What is the security model of your product?


           -    How does authentication work?
           -    How does authorization work?
           -    Which types of authorization do you
                support?


           -    What are the standards on which
                you base the security model?

5.6.2 Does your product support the use of
*     certificate revocation lists (CRL’s) for
      certificate verification?

5.6.3 Does it support an autorisation table based
      on the subjectserialnumber field from the
      certificate?


5.6.4 Which certificate maintenance options does
*     your product provide?
       -   Is it possible to import certicates
           (including the certicate chain)?

5.6.5 Does your product provide detailed SSL log
      information to facilitate debugging
      problems?




Request for Information Digikoppeling Messaging Software              Page 1421
6 Requirements at the level of the Digikoppeling
  Messaging Service
Evaluation will rank availability, quality and completeness.



6.1 Required Digikoppeling ebMS 1.1 Messaging Profile
Question                                                   Response

6.1.1 At the minimum, your solution should be
*     able to support the Digikoppeling feature set
      described in [Requirements W1].
       Does your product support this feature set?
       If not (completely), please indicate which
       specific features it does not support.

6.1.2 The Digikoppeling profile described in
      [Requirements W1] describes limited
      support for the optional ebMS Message
      Ordering module. Does your product support
      this feature? If yes, does it impose any
      additional configuration requirements?
      Please elaborate.

6.1.3 The message handler should be
      configurable to process something like
            <eb:PartyId
            eb:type=”Type”>PartyId</Part
            yId>

       using an external function that takes Type
       and PartyId as parameters and returns a
       specific next MSH URI.
       Can your solution accommodate this?
       Please explain.

6.1.4 Does the product support the use of ebMS
*     servicetype and roles?


6.2 Digikoppeling ebMS 2.0 Messaging Profile
Question                                                   Response

6.2.1 The Digikoppeling ebMS 2.0 profile
*     described in [Requirements W1] specifies a
      very limited use of the optional Multihop
      module (transparent, non-reliable
      intermediaries). Does your product support
      (this restricted use of) the multihop module?

6.2.2 The Digikoppeling ebMS 2.0 profile
*     described in [Requirements E2] specifies
      End-to-End Security using XML Signing and
      XML Encryption. Does your product support
      XML Signing and Encryption?


Request for Information Digikoppeling Messaging Software              Page 1521
Question                                                   Response

6.2.3 Does your product support multiple payload
*     containers for attachments (one container
      per attachment) as described in
      [Requirements E2]?



6.3 Interopability
Question                                                   Response

6.3.1 Has the current version of your solution
      been submitted to any ebXML messaging
      interoperability and/or conformance tests?If
      yes, please elaborate.

6.3.2 Are there any known interoperability issues
      with other ebXML messaging solutions?

6.3.3 Specifically, does your product interoperate
      with the Hermes open source ebXML
      solution? If there are any interoperability
      issues, please elaborate.



6.4 Extensibility
Question                                                   Response

6.4.1 Is it possible to instruct the Digikoppeling
      message handler (NOT an underlying EAI or
      other middleware product) to perform
      custom types of message processing
      involving the ebMS/W3C SOAP header
      and/or payload containers?
       Potential use case for this functionality are:
               Rejecting messages containing
                specific payloads based on MIME
                types.
               Rejecting messages larger than a
                (configurable) maximum message
                size.
               Rejecting messages that have
                payloads with unallowed MIME
                types.
               Applying an XSLT transform on an
                XML payload.
               Invoking a content scanner (e.g. to
                reject messages containing viruses).
       Please elaborate.

6.4.2 If the answer to the previous question is
      “YES”, can this behavior be controlled using
      specific parameters, such as Service/Action
      combinations or CPAIds?



Request for Information Digikoppeling Messaging Software              Page 1621
6.5 Configuration
Question                                                   Response

6.5.1 Does your system support message service
*     configuration using the ebXML CPP/CPA
      [ISO 15000-1] mechanism?

6.5.2 Is it possible to import ebXML CPP/CPA files
      (instead of manual entry)?

6.5.3 Does your solution support other
      configuration mechanisms? Please
      elaborate.



6.6 Other Digikoppeling Support Issues
Question                                                   Response

6.6.2 Digikoppeling is based on international
      ebXML/ebMS and Webservices(W3C)
      standards.
       Is your company currently involved in or
       otherwise supportive of these international
       standards? Please explain.

6.6.3 Does your company actively develop and/or
      extend the ebMS and Webservices
      functionality of your product, or is this
      functionality in maintenance mode with no
      resources allocated to other activities than
      servicing existing customers and fixing
      critical bugs?

6.6.4 Please list your company’s relevant
      references for Digikoppeling specifically and
      for the implementation of comparable
      ebXML/ebMS and webservices(W3C)
      standards in general.
       If these references can be contacted please
       list contact information.




Request for Information Digikoppeling Messaging Software              Page 1721
7 Requirements at the level of the Digikoppeling
  WUS (Web Services) Profile
7.1 Required Digikoppeling WUS 1.1 Profile
Please elaborate these specific points from [requirements W1]

Question                                                   Response

7.1.1 Does your product support the WS-I Basic
*     Profile 1.1 standards?

7.1.2 Does your product support the WS-I Simple
*     SOAP Binding Profile 1.0?

7.1.3 Does your product support the WS
*     Addressing 2005/08 standard?
       (http://www.w3.org/TR/2005/CR-ws-addr-
       core-20050817/)

7.1.4 Does your product support the WS
*     Addressing 2006/05 standard?
       (http://www.w3.org/TR/ws-addr-core/)
       -   Specifically does it support the
           http://www.w3.org/TR/2007/REC-ws-
           addr-metadata-20070904/ metadata
           standard WS-Addressing


7.2 Optional Digikoppeling WUS 2.0 Profile
Please elaborate these points from [requirements W2]

Question                                                   Response

7.2.1 Does your product support MTOM using the
      SOAP 1.1 Binding for MTOM 1.0 standard?

7.2.2 Does your product support WS-I Basic
      Security Profile 1.0 standards?




Request for Information Digikoppeling Messaging Software              Page 1821
7.3 Features
Question                                                   Response

7.3.1 Can WUS endpoints on your message
*     handler be configured to relay messages to
      backoffice applications using the available
      interfaces(e.g. JMS simple webservices) in a
      synchronous manner? That is enable a
      synchronous session between backoffice
      application and an external WUS service
      where your message handling solution acts
      as intermediary?
       If so what is the delay (if any) in
       synchronous response times added by your
       message handler?



7.4 Interopability
Question                                                   Response

7.4.1 Are there any known interopability issues
      with other parties WS-I basic profile 1.1
      solutions? Please elaborate.

7.4.2 Are there any known interopability issues
      with other parties WS-I basic profile 1.2
      solutions? Specifically for MTOM and WS-
      Addressing. Please elaborate.



7.5 Configuration
Question                                                   Response

7.5.1 Does your product support (semi) automatic
      configuration by importing WSDL’s?

7.5.2 Does your product support SOAP / WSA
      headers request validation? Please
      elaborate.

7.5.3 Does your product support content based
      filtering? Please elaborate. (see also 6.4.1)




Request for Information Digikoppeling Messaging Software              Page 1921
8 Revision History

   Revision              Date                  Editor      Changes Made

1.1                 5-2-2010           Frank Terpstra      Changed from Overheidsservicebus to
                                                           digikoppeling. Minor adjustedments based on
                                                           comments from Kristel Nieuwenhuis.




Request for Information Digikoppeling Messaging Software                                        Page 2021
9 References
[Requirements W1]
                            http://www.logius.nl/fileadmin/logius/product/digikoppeling/koppelvlakstandaa
                            rden/Koppelvlakstandaard%20WUS%201.1.pdf

[Requirements W2]
                            http://www.logius.nl/fileadmin/logius/product/digikoppeling/koppelvlakstandaa
                            rden/Koppelvlakstandaard%20WUS%202.0.pdf
[Requirements E1]
                            http://www.logius.nl/fileadmin/logius/product/digikoppeling/koppelvlakstandaa
                            rden/Koppelvlakstandaard%20ebMS%201.1.pdf

[Requirements E2]
                            http://www.logius.nl/fileadmin/logius/product/digikoppeling/koppelvlakstandaa
                            rden/Koppelvlakstandaard%20ebMS%202.0.pdf

    [ISO 15000-1]           ISO 15000-1 ebXML Collaboration Protocol Profile and Agreement
                            Specification. OASIS ebXML Collaboration Protocol Profile and Agreement
                            Specification (2.0).
                            URL http://www.oasis-open.org/committees/ebxml-cppa/documents/ebcpp-
                            2.0.pdf
    [ISO 15000-2]           ISO 15000-2 ebXML Message Service Specification.
                            URL http://www.oasis-open.org/specs/index.php#ebxmlmsgv2 .




Request for Information Digikoppeling Messaging Software                                           Page 2121

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:16
posted:7/26/2011
language:English
pages:21
Description: Rfi Template Final document sample