SOLICITATION NOTICE
99 -- COTS transaction messages - Package #1
- Notice Date
- 8/27/2010
- Notice Type
- Presolicitation
- NAICS
- 511210
— Software Publishers
- Contracting Office
- Department of Justice, Federal Bureau of Investigation, Information Technology Contracts Unit/PPMS, 1000 Custer Hollow Road, Module B-3, Clarksburg, West Virginia, 26306
- ZIP Code
- 26306
- Solicitation Number
- 021340
- Point of Contact
- Michael Konchesky, Phone: 304-625-4031
- E-Mail Address
-
mkonches@leo.gov
(mkonches@leo.gov)
- Small Business Set-Aside
- N/A
- Description
- Tables REQUEST FOR INFORMATION Federal Bureau of Investigation 1.0 Description 1.1 The Criminal Justice Information Systems (CJIS) Division in support of the Federal Bureau of Investigation (FBI) is seeking information on how an interested contractor could provide a Commercial-Off-The-Shelf (COTS) application for the processing of transaction messages with other transaction-based systems including the National Crime Information Center (NCIC), International Justice and Public Safety Network (Nlets), and Interstate Identification Index (III). 1.2 THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is issued solely for information and planning purposes - it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This request for information does not commit the Government to contract for any supply or service whatsoever. Further, the FBI is not at this time seeking proposals and will not accept unsolicited proposals. Respondees are advised that the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested party's expense. Not responding to this RFI does not preclude participation in any future RFP, if any is issued. 2.0 Background 2.1 The FBI is considering an upgrade to its internal network with the latest technologies for accessing NCIC, Nlets, and III. This network provides access control, message switching, and database messaging to internal FBI, Federal, and State users. 2.2 The current messaging system utilizes a software application that processes both inbound and outbound transaction messages. Software application enhancements have been required as a result of Advisory Policy Board (APB) approvals or Congressional mandated direction. 2.3 The CJIS Division is researching COTS products that satisfy functional, system, interface, policy, and business requirements as well as provide for future growth and application enhancement. Training, migration support, and on-going maintenance of the COTS product will be required. 2.4 The current workstation client software receives and sends message transactions between the user and the server; provides preformatted message transaction forms; prints message transactions; provides help functions; and logs user transactions. The client software permits the creation of NCIC image records with a flatbed image scanner or file import; allows the user to configure keyboard shortcuts to access commonly used message transactions; and provides a drop down menu to retrieve a preformatted message form that is displayed on the screen. Preformatted message transaction forms reside on the server and contain all fields of the selected message transaction. The forms highlight the mandatory fields required for the message transaction and perform error checking to ensure all mandatory fields are complete and syntactically correct before sending the message transaction. The user also has the ability to override error checking in case of a field input error or form error. 2.5 The workstation client software is typically installed on Microsoft Windows desktop computers. The FBI would prefer to also enable client capabilities on mobile devices such as Blackberries. Vendor responses to 6.18 should discuss the capabilities of the COTS product and assist the FBI in determining favorable procurement strategies. 2.6 The FBI intends to integrate this application with their Enterprise Identity Management System (EIMS) that provides Identification and Authentication (I&A) and access management services. Access to COTS product features is accomplished by granting user access to specific items from a set of customizable attributes. The EIMS team will implement a vendor supplied list of fine grained authorizations understood by the COTS product for access to specific features. EIMS permits the exchange of user security attributes via Security Assertion Markup Language (SAML) assertions or HTTP header attributes. The integrated COTS product must request and accept user security attributes from EIMS and provide access control based upon those attributes. 2.7 The FBI will conduct an Advisory Multistep Process using the Federal Business Opportunities (FEDBIZOpps) with Contractor Teaming Arrangements allowed. The FBI will invite interested parties to demonstrate their product's out-of-the-box capability to meet the asterisked requirements shown in the attached Tables 1 through 11 at the FBI facility in Clarksburg, WV. This demonstration will involve actual performance of the configured product and documentation review. Each demonstration will be limited to a three week period. Week One will allow the vendor to install and configure their product, to include training FBI test personnel; Week Two will involve FBI and vendor demonstrations and assessments; and Week Three will involve any re-demonstration resulting from vendor adjustments to the product. At the conclusion of the demonstration period, the FBI will determine its next course of action. 2.8 Based on experience with related products, the FBI is concerned with the security capabilities of the supplied products. As a result, during the product demonstration period, the product must demonstrate to the satisfaction of the FBI full compliance with the FIPS 140-2 and the ability to achieve the integration described in paragraph 2.6. To be considered technically acceptable, the product must demonstrate one of the following: a. Full compliance with both the FIPS 140-2 requirements and the integration described in paragraph 2.6 b. Full compliance with the integration described in paragraph 2.6 c. Full compliance with the FIPS 140-2 requirements and a demonstrated product evolution plan (and vendor certification) that incorporates the integration described in paragraph 2.6 as part of the commercial product not later than 1/1/2012 The interested vendors are advised that demonstration of FIPS 140-2 compliance will involve FBI review of the source code implementation of NIST certified products. 3.0 Responses 3.1 Interested parties are requested to respond to this RFI with a white paper. 3.2 White papers in Microsoft Word compatible format are due no later than September 14, 2010, 1200 EST. Responses shall be limited to 40 letter sized pages with 12 point font for Section 2 and submitted via e-mail to Michael.Konchesky@leo.gov. The response shall also be delivered in hardcopy and on CD to the following address: Federal Bureau of Information Attention: Michael Konchesky Module E-3 1000 Cluster Hollow Road Clarksburg, WV 26306 3.3 Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information. Please be advised that all submissions become Government property and will not be returned. Proprietary information shall fall under the provisions of Title 18, Part 1, Chapter 93, Section 1905 of the US Code. 3.4 Section 1 of the white paper shall be limited to 2 pages. Section 1 shall provide administrative information, and shall include the following as a minimum: 3.4.1 Name, mailing address, overnight delivery address (if different from mailing address), phone number, fax number, and e-mail of designated point of contact. 3.4.2 Either 1) a statement that the respondee will allow the Government to release its proprietary data to the Government support contractors for technical evaluation, or 2) a statement that the respondee will not allow the Government to release its proprietary data to the Government support contractors. In the absence of either of the foregoing, the Government will assume that the respondee does NOT agree to the release of its submission to Government support contractors. 3.4.3 Provide company information to include the size of the company and the Dun & Bradstreet D-U-N-S Number. 3.5 The number of pages in Section 1 of the white paper shall not be included in the 40-page limitation, i.e., the 40-page limitation applies only to Section 2 of the white paper. Section 2 of the white paper shall answer the issues addressed in Section 6 of this RFI including the completed requirements matrix. 4.0 Industry Discussions FBI representatives may or may not choose to meet with potential vendors in addition to the product demonstrations discussed in paragraph 2.7. Such discussions would only be intended further clarify the potential capability to meet the requirements and certification risks. 5.0 Questions Questions regarding this announcement shall be submitted in writing by e-mail to the Contracting Officer, at Michael.Konchesky@leo.gov. Verbal questions will NOT be accepted. Questions will be answered by posting answers to FEDBIZOpps; accordingly, questions shall NOT contain proprietary or classified information. The Government does not guarantee that questions received after September 3, 2010 will be answered. 6.0 Requested Information 6.1 Describe the evolution of the offered COTS product. Include details regarding certifications achieved, the product's customer base, options offered, and the platforms/devices supported. 6.2 Describe available software development kits for customized interfaces. 6.3 Describe the product's licensing strategy. 6.4 Describe the product maintenance options and what the options include. 6.5 Describe the provided COTS product documentation (e.g. user guides, database dictionaries, configuration file format specifications, log file format specifications, administrations manuals). 6.6 Describe the product release cycle for updates. 6.7 Describe the training courses offered and recommended training time. 6.8 Describe the offeror's ability to support installation, security accreditation, site acceptance testing and transition. 6.9 Describe the product's disaster recovery capabilities. 6.10 Describe the product's message routing performance capabilities to include: the allowable number of logical connections, and messages routed per second. 6.11 List the number of concurrent users the system supports. 6.12 Describe the user interface with regard to customizing message transaction forms. 6.13 Describe the product's ability to trace message transactions. 6.14 Describe the product's report generation ability. 6.15 Describe the product's role-based access controls. 6.16 Describe the internal and external I&A methods supported by the product. 6.17 Describe the product's ability to interface with other web services. 6.18 Describe the product's mobile device capability (device types and operating systems supported, browser-based or application-based, encryption method used, information cached or otherwise stored, inactivity logout, I&A, ORI assignments, migration to newer devices, synchronous/asynchronous/notifications messages, server side device recognition). 6.19 Describe the product's notification message implementation. 6.20 Please include in the white paper a completed copy of the requirements matrix contained in the attachment and indicate whether or not the COTS product in its current state complies with the stated requirements. The respondee may include comments to clarify their responses. 7.0 Summary THIS IS A RFI ONLY to identify sources that can provide a COTS application for the processing of transaction messages with other transaction-based systems including the NCIC, Nlets, and III. The information provided in the RFI is subject to change and is not binding on the Government. The FBI has not made a commitment to procure any of the items discussed, and release of this RFI should not be construed as such a commitment or as authorization to incur cost for which reimbursement would be required or sought. All submissions become Government property and will not be returned.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/DOJ/FBI/PPMS4/021340/listing.html)
- Place of Performance
- Address: 1000 Custer Hollow Road, Clarksburg, West Virginia, 26306, United States
- Zip Code: 26306
- Zip Code: 26306
- Record
- SN02258485-W 20100829/100827235825-43868cfb1b97c04de48d9fa71f2f079a (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 |