SRCSGT | 70 | The purpose of this RFI is to conduct market research that will be used to formulate an acquisition strategy that may be used to procure the Department of Defenses (DoD) future Data Integration System.

FBO DAILY ISSUE OF APRIL 26, 2009 FBO #2708
SOURCES SOUGHT

70 -- The purpose of this RFI is to conduct market research that will be used to formulate an acquisition strategy that may be used to procure the Department of Defenses (DoD) future Data Integration System.

Notice Date: 4/24/2009
Notice Type: Sources Sought
NAICS: 443120 — Computer and Software Stores
Contracting Office: ACA, ITEC4, Directorate of Contracting , 2461 Eisenhower Avenue, Alexandria, VA 22331-0700
ZIP Code: 22331-0700
Solicitation Number: W91QUZ-DATAINTEGRAT
Response Due: 5/19/2009
Archive Date: 7/18/2009
Point of Contact: Freda McDonald, 703-325-6011<br />
Small Business Set-Aside: N/A
Description: SOURCES SOUGHT OR REQUEST FOR INFORMATION (RFI), DATA INTEGRATION SYSTEM (For Informational or Planning Purposes Only) Purpose: The purpose of this RFI is to conduct market research that will be used to formulate an acquisition strategy that may be used to procure the Department of Defenses (DoD) future Data Integration System. Background: DoD currently employs multiple solutions for data integration based on current and legacy technology. In order to simplify the data integration process and provide enhanced workflow and data visibility, DoD is investigating new technologies. Areas of particular interest include: "Data integration solutions that employ metadata-driven transformations and/or adaptations that ensure metadata are visible, accessible and understandable. "Integration patterns that decouple transformations and adaptations from business logic and business rules. "Message broker capabilities including data routing (content-based addressing), publish & subscribe and other message brokering functions. "Mediation capabilities for protocol adaptation. "Other capabilities in a technology stack for the purpose of mediating data between two or more IT components. "Adherence to Open Standards where possible and effective. Requested Information: Interested vendors shall submit their knowledge and capabilities to perform each of the requirements outlined below. If the respondent focuses on a particular piece of technology that addresses a single area, the respondent should make it clear how this technology contributes to the overall program/process. 1. Routing and Transformation - The capability to respond to a clients request for data in a particular format, retrieve that data from a data service, and transform and reformat it to the client-requested format including, but not limited to: -XML -MILS -EDI ANXI X12 -UDF (User defined File/Field) -EDINT (AS2/AS3) -SOAP (Simple Object Access Protocol in 1.1) -(SOAP in 1.2) -REST (Representational state transfer) -CSV (comma-separated values) -WS* (Web Services Standards) -IDOC -Other identified standard or protocol 2.Semantic-based Mediation - The capability to mediate between systems based on semantics. A semantic-based mediation is a data model that represents a set of concepts within a domain and the relationship between those concepts including, but not limited to: -RDF - Resource Description Framework (RDF) is a model for representing metadata in XML. -OWL Web Ontology Language (OWL) facilitates greater machine interpretability of Web content than that supported by XML, RDF, and RDF Schema (RDF-S) by providing additional vocabulary along with a formal semantics. -SWRL - Semantic Web Rule Language (SWRL) based on a combination of the OWL DL and OWL Lite sublanguages of the OWL Web Ontology Language with the Unary/Binary Datalog RuleML sub-languages of the Rule Markup Language. -Other identified standard or protocol 3.Mapping based Mediation - The capability to mediate between systems based on mappings between the data models of those systems including, but not limited to: -Cross-walks -Reference tables -Provide output as: oXSL oXQuery oOWL oCode oOther -Import: oXSL oXQuery oOther 4.Metadata based Mediation - The capability to mediate based on structural and/or semantic metadata including, but not limited to: - Mediation engine based on a Metadata repository - Structural metadata: oXpath Expression - Semantic metadata using Mapping Relations: oSame as oEquivalent Class oCorrespondence Mapping - Support for Metadata Repository (MDR) federation (exchanges between MDRs): oebXML RIM specifications support oRS query specifications 5.Protocol Adaptation - The capability to provide adapters to bridge the gap created when a client cannot communicate directly with a service, Transfer Protocol Mediation, including, but not limited to: - HTTP/HTTPS - FTP (File Transfer Protocol) - FTP over SSL (SFTP) - FTP Secure (FTPS) - SCP (Secure Copy) - SMTP (Simple Mail Transport Protocol) - Message-oriented middleware - JMS (Java Message Service) - SNMP (Simple Network Management Protocol) - Other - UDP - TCP 6.Security, Encryption and Digital Signature - The capability to provide an Information Assurance shell of data so as to address consumption of data by the unanticipated consumer. This includes all IA aspects as well as data encryption and digital signature for exchanges including, but not limited to: - WS-Security (Web Services Standards) - Security Encryption and Digital Signature - Process to ensure the fidelity of information - Other 7.Rules Engine Support - Capability to provide support for a rules engine which allows the separation of processing logic of business rules from data storage specific to the management of business rules data including, but not limited to: - Standards/protocols to be identified - Other 8.Audit-ability and Accountability - Capability to provide auditing data that details the integrity and quality of the conversion process to indicate any data loss, resolution loss, and semantic alteration including but not limited not limited to: - Standards/protocols to be identified - Other 9.Performance, Scalability and Reliability - The extent to which an echnology used by a program in data integration can be scaled to support all anticipated and unanticipated consumers. Includes non-material solutions put in place by the program to address reliability issues including, but not limited to: - Hardware-based Load Balancing - Software-based Load Balancing - Clustering - COOP Strategy (continuity of operations planning) Other. Submission Instructions and Format Submission shall be no more than 15 pages, excluding cover sheet, single-spaced, 8.5 x 11 paper, 1 inch margin, and no smaller than 12 point type and compatible with MS Office Word or Adobe PDF format. The 15 page limit shall include all attachments. The cover page shall include, at a minimum, general information, company name, and address, points of contact, telephone and fax numbers, and email addresses. Disclaimer and Important Notes Federal Acquisition Regulation (FAR) 5.215-3, Request for Information or Solicitation for Planning Purposes (Oct 1997) (a) The Government does not intend to award a contract on the basis of this solicitation or to otherwise pay for the information solicited except as an allowable cost under other contracts as provided in subsection 31.205-18, Bid and proposal costs, of the Federal Acquisition Regulation. (b) Although proposal and offeror are used in this Request for Information, your response will be treated as information only. It shall not be used as a proposal. (c) This solicitation is issued for the purpose of: obtaining information on DATA INTEGRATION SYSTEM (End of Provision) Proprietary Information and trade secrets, if any, must be clearly marked on all materials. All information received that is marked Proprietary will be handled accordingly. Please be advised that all submissions become Government property and will not be returned. The Government shall not be held liable for any damages incurred if proprietary information is not properly identified. Questions. The Government suggestions you address each question below in addition to providing additional information related to the requested information. These questions are provided to assist the respondents. 1. Explain your companies capabilities related to Routing and Transformation especially address your capability to respond to a clients request for data in a particular format, retrieve that data from a data service, and transform and reformat it to the client-requested format including, but not limited to: -XML -MILS -EDI ANXI X12 -UDF (User defined File/Field) -EDINT (AS2/AS3) -SOAP (Simple Object Access Protocol in 1.1) -(SOAP in 1.2) -REST (Representational state transfer) -CSV (comma-separated values) -WS* (Web Services Standards) -IDOC -Other identified standard or protocol Address each item individually. 2. Explain your companies capabilities related to Semantic-based Mediation, and the capability to mediate between systems based on semantics. A semantic-based mediation is a data model that represents a set of concepts within a domain and the relationship between those concepts including, but not limited to, each of the following. Address each one as it relates to your company. -RDF - Resource Description Framework (RDF) is a model for representing metadata in XML. -OWL Web Ontology Language (OWL) facilitates greater machine interpretability of Web content than that supported by XML, RDF, and RDF Schema (RDF-S) by providing additional vocabulary along with a formal semantics. -SWRL - Semantic Web Rule Language (SWRL) based on a combination of the OWL DL and OWL Lite sublanguages of the OWL Web Ontology Language with the Unary/Binary Datalog RuleML sub-languages of the Rule Markup Language -Other identified standard or protocol 3. Explain your capabilities related to mapping based mediation between systems and based on mappings between the data models of those systems. Provide specific information on the following: -Cross-walks -Reference tables -Provide output as: oXSL oXQuery oOWL oCode oOther -Import: oXSL oXQuery oOther 4. Explain your capabilities related to metadata based mediation in your discussion include the following at a minimum: - Mediation engine based on a Metadata repository - Structural metadata: oXpath Expression - Semantic metadata using Mapping Relations: oSame as oEquivalentClass oCorrespondence Mapping - Support for Metadata Repository (MDR) federation (exchanges between MDRs): oebXML RIM specifications support oRS query specifications 5. Explain your capabilities to relate to Protocol Adaptation. The capability to provide adapters to bridge the gap created when a client cannot communicate directly with a service, Transfer Protocol Mediation. In your explanation, please address each of the following at a minimum: - HTTP/HTTPS - FTP (File Transfer Protocol) - FTP over SSL (SFTP) - FTP Secure (FTPS) - SCP (Secure Copy) - SMTP (Simple Mail Transport Protocol) - Message-oriented middleware - JMS (Java Message Service) - SNMP (Simple Network Management Protocol) - Other - UDP - TCP 6. Explain your capabilities related to Security, Encryption and Digital Signature. The capability to provide an Information Assurance shell of data so as to address consumption of data by the unanticipated consumer. This discussion should include all IA aspects as well as data encryption and digital signature for exchanges and the following list at a minimum: - WS-Security (Web Services Standards) - Security Encryption and Digital Signature - Process to ensure the fidelity of information - Other 7. Explain your rules engine support or your capability to provide support for a rules engine which allows the separation of processing logic of business rules from data storage specific to the management of business rules data. Please specifically address the following at a minimum: - Standards/protocols to be identified - Other 8. Explain your audit-ability and accountability. Specially address, your capability to provide auditing data that details the integrity and quality of the conversion process to indicate any data loss, resolution loss, and semantic alteration. Please address each of the following at a minimum: - Standards/protocols to be identified - Other 9. Explain your performance, scalability,and reliability. The extent to which an echnology used by a program in data integration can be scaled to support all anticipated and unanticipated consumers. Please include non-material solutions put in place by the program to address reliability issues including the following at a minimum: - Hardware-based Load Balancing - Software-based Load Balancing - Clustering - COOP Strategy (continuity of operations planning) 10. What type of business are you? Small? Large? Disadvantage Business? Etc.? 11. Do you an existing contract for these type services which we might access? If so, with what organization? Contract number? Contact information? 12. Do you have a website? Site Information? 13. Are you a member of any trade or professional organizations? Contact information? Submission: This RFI should be submitted by email to freda.mcdonald@us.army.mil by 3 PM (local time Alexandria, VA) on May 19, 2009. Freda McDonald, CPCM Contracting Officer 703-325-6011 ITEC4 Division D, Branch A Alexandria, VA
Web Link: FedBizOpps Complete View
(https://www.fbo.gov/?s=opportunity&mode=form&id=9f55c3f13d702bbb8cadc5711e17b6d9&tab=core&_cview=1)
Place of Performance: Address: ACA, ITEC4 Directorate of Contracting , 2461 Eisenhower Avenue Alexandria VA<br />; Zip Code: 22331-0700<br />
Record: SN01801106-W 20090426/090424220820-9f55c3f13d702bbb8cadc5711e17b6d9 (fbodaily.com)
Source: FedBizOpps Link to This Notice
(may not be valid after Archive Date)

| FSG Index | This Issue's Index | Today's FBO Daily Index Page |

Loren Data's SAM Daily™

70 -- The purpose of this RFI is to conduct market research that will be used to formulate an acquisition strategy that may be used to procure the Department of Defenses (DoD) future Data Integration System.