MODIFICATION
D -- Request for Information - Standard Database Solution
- Notice Date
- 6/1/2004
- Notice Type
- Modification
- NAICS
- 518210
— Data Processing, Hosting, and Related Services
- Contracting Office
- DHS - Border and Transportation Security, Transportation Security Administration, Headquarters TSA, 601 S. 12th Street TSA-25, 4th Floor, Arlington, VA, 22202
- ZIP Code
- 22202
- Solicitation Number
- Reference-Number-OIT-RFI
- Response Due
- 6/11/2004
- Archive Date
- 6/26/2004
- Point of Contact
- Michael Derrios, Contracting Officer, Phone 571.227.1573, Fax 571.227.2913,
- E-Mail Address
-
mike.derrios@tsa.dot.gov
- Description
- ***********THE CLOSING DATE FOR THIS RFI HAS BEEN EXTENDED. RESPONSES ARE DUE NO LATER THAN CLOSE OF BUSINESS (5:00 P.M. EST) ON 6/11/04.********* Request for Information for a Standardized Database Solution for Converting Microsoft Access Databases 1.0 SUBJECT Request for Information (RFI) for a two phased solution to convert, store, manipulate and report data located in multiple databases/spreadsheets (Microsoft Access, Excel, etc.) into a standardized database, and report data to multiple internal and external TSA stakeholders to be integrated with the Transportation Security Administration (TSA) Operating Platform located at the data hosting center in St. Louis, Missouri. The database will support users from multiple departments within TSA. Responses are due to this RFI by 4:00 PM on June 4, 2004. See section 8.0 for further information. 2.0 DESCRIPTION The Transportation Security Administration, at the request of the Office of Information Technology (OIT), and in support the OIT goals to design, deploy, maintain and enhance the information technology essential for TSA to protect the Nation?s transportation systems to ensure freedom of movement for people; is seeking information from industry that will assist in the development and deployment of a standardized, enterprise database solution. Specifically, this RFI seeks the following information: Conceptual technical architecture alternatives for a solution that will: Interface with multiple systems (internal and external to TSA) to download required data into a standardized database. Interface with authorized TSA users via a limited number of approved applications to sort and manipulate data located in the standardized database.  Report data in a variety of formats (including MS Excel, HTML, etc.) to TSA Stakeholders. 3.0 REQUIREMENTS This section enumerates the high-level functional requirements for the Standardized Database Solution. TSA requires the conversion of existing operational Access databases to a stable, readily managed, multi-user environment to best support their day-to-day operations. The end state environment required is the target Oracle platform shared by TSA and DHS. TSA has immediate needs to access and manage critical data during conversion with no operational downtime, and reach the end state Oracle environment in the quickest and most cost-effective manner. An intermediate database environment would be acceptable while transitioning to Oracle, provided TSA?s data accessibility is not interrupted and this approach meets the business needs of TSA in a cost-effective manner. TSA?s Office of Information Technology requires the ability to store, manipulate, and report unclassified yet sensitive data. These capabilities are required short term to quickly support users from multiple departments within TSA using a standard data dictionary. The Standardized Database Solution will eliminate redundant efforts (i.e., less employee time spent developing across the enterprise). The Standardized Database Solution will be hosted in a central location, such as TSA?s hosting center that allows for 24 x 7 support and fault tolerance, depending upon the build, with a dedicated Database Administrator (DBA) to ease management and trouble-shooting of all applications. TSA?s long term requirements involve the ability to download, store, manipulate, and report mission critical data to multiple internal and external TSA stakeholders. This solution will:  Interface with multiple systems (internal and external to TSA) to download required data into the standardized DB created in Phase I.  Interface with authorized TSA users via a limited number of approved applications to sort and manipulate data located in the standardized DB created in Phase I.  Report data in a variety of formats (Including Excel, HTML, etc.) to TSA Stakeholders. Other requirements not directly related to database architecture will be addressed at a later date. Examples of such requirements include security policies and security management requirements, service level agreements, and other important considerations. The purpose of this RFI is to gather information about those requirements enumerated above. To the extent simplifying assumptions are needed, respondents are encouraged to make and document such assumptions in their responses. 4.0 POSSIBLE NETWORK SOLUTION The Standardized Database Solution will meet the functional requirements specified above. The Government is open to alternative concepts for solutions that meet these requirements. The Government encourages creativity and outside the box thinking in responses to this RFI. The following parameters should be considered when developing a solution to TSA?s database conversion and management requirements:  Grouping TSA conversions in order to fully utilize economy of scale.  Eliminating database redundancies in TSA offices to minimize the number of conversions and subsequent data maintenance activities.  A transitional approach, initially converting TSA databases quickly to a less complex but stable multiple user?s environment to satisfy immediate customer needs.  Single server for all TSA conversions to consolidate and organize these databases for more orderly follow-on conversions or add-ons.  A two-phase solution:  Phase 1- converting unclassified yet sensitive data located in multiple databases/spreadsheets (Microsoft Access, Excel, etc.) into a standardized database at a TSA specified data hosting facility.  Phase 2 - creating a long-term solution to download, store, manipulate, and report mission critical data to multiple internal and external TSA stakeholders. Accordingly, respondents are encouraged to provide information about any alternatives that can be demonstrated to be immune from the kinds of disruptions described in section 3.0, above. 5.0 SAMPLE RESPONSE OUTLINE Following is a suggested outline and suggested page counts for a response to this RFI. This outline is intended to minimize the effort of the respondent and structure the responses for ease of analysis by the government. Nevertheless, respondents are free to develop their response as they see fit. Section 1 ? Conceptual Alternatives Briefly describe two or more alternative architecture concepts for the Standardized Database Solution, including the reliability and availability characteristics of the alternatives. Discuss the capability for the solution to be hosted by a third party. (3-5 pages per alternative with one diagram of the hosting site identifying the brand/type of equipment that would typically be deployed). Section 2 ? Feasibility Assessment Briefly describe the feasibility of each alternative and the design tradeoffs involved as matched against the functional requirements and risks of penetration. (1 page per alternative) Section 3 ? Cost and Schedule Estimates Provide cost estimates for each alternative for 5 and 10-year contract terms for non-recurring and annual recurring costs. The costs will include required hardware and software purchases, design and development costs, as well as maintenance and operational support needs. Also, discuss cost drivers, cost tradeoffs, and schedule considerations (2-3 pages) Section 4 ? Corporate Expertise Briefly describe your company, your products and services, history, ownership, financial information, and other information you deem relevant. (There is no suggested page count) In particular, please describe any projects you have been involved in that are similar in concept to what is described in this RFI, including management and operations approach, security requirements, security assurance processes, and any relevant lessons learned (1-2 pages per project). Include any comments on the structure of the requirements for a formal RFP response. Section 5 ? Additional Materials Please provide any other materials, suggestions, and discussion you deem appropriate. 6.0 INFORMATION EXCHANGE MEETINGS TSA and the Office of Information Technology will hold an information exchange meeting on May 27, 2004 at 2:00PM to discuss this RFI with interested potential respondents. Details about this meeting will be made available at a later date. If you wish to attend this meeting, please respond in writing (via email) to the contact provided in section 8.0, below. 7.0 DISCLAIMER This RFI is issued solely for information and planning purposes only and does not constitute a solicitation. All information received in response to this RFI that is marked Proprietary will be handled accordingly. Responses to the RFI will not be returned. Responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. Responders are solely responsible for all expenses associated with responding to this RFI. 8.0 CONTACT INFORMATION Following is the Point of Contact (POC) for this RFI, including the public information exchange meeting: Mr. Michael Derrios (571) 227-1573 mike.derrios@dhs.gov Please submit responses via e-mail in Microsoft Office format by 4:00 PM (Eastern Time) on June 4, 2004, to the POC at: mike.derrios@dhs.gov.
- Place of Performance
- Address: Transportation Security Administration, 701 South 12th Street, Arlington, VA
- Zip Code: 22202
- Country: USA
- Zip Code: 22202
- Record
- SN00595043-W 20040603/040601211530 (fbodaily.com)
- Source
-
FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |