SOURCES SOUGHT
D -- NHTSA System/Process Consulting Services
- Notice Date
- 7/22/2010
- Notice Type
- Sources Sought
- NAICS
- 541519
— Other Computer Related Services
- Contracting Office
- Department of Transportation, National Highway Traffic Safety Administration (NHTSA), National Highway Traffic Safety Administration HQ, 1200 New Jersey Avenue, SE, Washington, District of Columbia, 20590
- ZIP Code
- 20590
- Solicitation Number
- 2011-001
- Archive Date
- 8/21/2010
- Point of Contact
- Lloyd S. Blackwell, Phone: 202-366-9564
- E-Mail Address
-
lloyd.blackwell@nhtsa.dot.gov
(lloyd.blackwell@nhtsa.dot.gov)
- Small Business Set-Aside
- N/A
- Description
- This Sources Sought Notice is for planning purposes only and shall not be construed as a solicitation or as an obligation on the part of the National Highway Traffic Safety Administration (NHTSA). The purpose of this Notice is to identify potential sources that may be interested in and capable of performing the work described herein. The NHTSA welcomes Corporate Capability Statements from all individuals and organizations. The NHTSA does not intend to award a contract on the basis of responses nor otherwise pay for the preparation of any information submitted or NHTSA's use of such information. Acknowledgement of receipt of responses will not be made, nor will respondents be notified of NHTSA's evaluation of the information received. As a result of this Notice, the NHTSA may issue a Request for Proposals (RFP). However, should such a requirement fail to materialize, no basis for claims against the NHTSA shall arise as a result of a response to this Notice. Scope: The pilot instance and final product are both expected to be a fully operational system meeting the applicable business requirements deemed to be within scope and necessary to collect and present incoming data received from a multiple sources using a web-based tool as the primary user interface. It is recognized that Phase 1 pilot components may be scaled down to meet a short timeframe requirement, but these components will become part of the Phase 2 activities where applicable, and appropriate. Overall, the system is required to have a standardized interface using the NHTSA style guide for the public facing environment, and an agreed upon standard for the internal users. Internal users are to have the ability to access standard prepared views / reports of data within the data warehouse, in addition to performing ad-hoc queries on both the internal data warehouse and source operational data stores. The internal interface is required to be available only to authenticated users and allow for supporting data elements to be added to the records to show where/when action was taken on specific records (where appropriate). The public facing environment is to be fully functional to allow for full access using stock "view" and guided research on approved datasets using a user friendly and aesthetically appealing interface. Specific Requirements: This contract initiative is specific to the delivery of a high-quality platform for the management of multiple datasets to provide information in a more effective and meaningful fashion to internal audiences and the general public. The project is expected to initiate the first iteration of an agency data warehousing and data distribution platform that will be used as a shared services resource across multiple agency programs. As the system development for this project is expected to be managed using an iterative design it is understood there will be a continuous controlled process of improvement and data integration through the life of the CIF. As such, work is expected to be managed in a phased approach to ensure goals are clearly understood for each phase of development and iteration. In addition, the model and technology, if successfully implemented, is expected to serve as a base for potential cross-mode data sharing within the DOT. The approach for development and deployment of the technology is partially based on existing software and hardware, but the government is open to the use of no-cost or low cost options which may not be within the current options of technical resources to meet the requirements. The use of open source is available as an option to the Contractor to achieve success, while saving licensing and maintenance costs for the government. Although open source technologies are available as an option, due to security and technology maintenance concerns all software introduced into the environment which is not currently being used must first be approved by both the NHTSA Chief Information Officer (CIO) and Contracting Officer Technical Representative (COTR). The Contractor is required, wherever possible, to apply the principles of implementation of a high-level-architecture (HLA) to the design of the system, especially for repeatable components. As such, documentation for reusable components is expected to be clear and concise and updated as iterations are moved to production. All customizations, scripting and graphic components are expected to be stored within a system asset repository. The design of the repository is required to be searchable, contain clear references to use, and referenced whenever applicable within system and software documentation. The project is expected to follow principles of "best practices" of data warehousing and as such it is suggested that the Contractor review certain written material prior to execution of the data model / design to ensure "best practices" is truly applied. A recent publication, Data Warehouse Design: Modern Principles and Methodologies, by Matteo Golfarelli (2009), is one suggested text to use as a guide. Where appropriate within documentation it is expected the contractor apply APA references to ensure proper sources can be further reviewed by the reader. As this initiative is expected to be broken into multiple phases due to both the complexity of the data and the technologies, the Contractor is required to establish a methodology for incorporating features and datasets. This process is required to include a review and approval process, which should lead to an overall NHTSA data blueprint that will evolve as datasets are better understood through the process. The Contractor is required to maintain a process for management of datasets and features, which may include interfacing with a Change Control Board (CCB) consisting of subject matter experts (SMEs) and members of the NHTSA OCIO. Management of the data related to features, documentation and metadata for datasets is required to be maintained within the NHTSA Project Management Office (PMO) SharePoint site, which the Contractor will have access to for posting and management of the most current version of the content. The Contractor is also required to maintain risks related to specific project elements related to security compliance within the NHTSA iREX system, which access will be granted upon award of the contract. The internal environment is expected to serve as a stable platform for data cleansing and preparation for the public, in addition to providing a more robust platform for cross-program analysis. The Contractor is expected to create a phased implementation plan that distinguishes the development of "pilot" versus full production system stages. In addition, requirements analysis, documentation, security authorization updates, and training are to be included within the work included by the Contractor. As the government is committed to the success of this project, the contractor is open to suggesting additional deliverables which may not be included in their response proposal. The following specific deliverables are minimum requirements for this effort: •1. NHTSA Corporate Information Factory (CIF) - Proof of Concept (POC) (a.k.a., "Data Warehouse Pilot") - Initial development for the "pilot" will focus on a minimum of at least two key datasets and supporting data that are centered on, consumer feedback, vehicle recalls and/or vehicle safety data. The integration, standardization and presentation of these datasets is to occur within the "proof of concept" phase of this project. This phase of the project will include at a minimum a public facing web browser-based interface, as well as an internal data analysis center. The Contractor will be required to use existing architecture and software resources for the implementation of this requirement to maximize the investment currently owned by NHTSA. The Contractor may utilize a low-cost or no-cost software option if it is deemed to enhance the current software resources for successful implementation of the "pilot". All work within this phase is intended to be fully functional upon completion and serve as a high-quality example of a program resource for accessing, presenting and analyzing programmatic data. Documentation for this phase is to include the following: •a. Proof of Concept Specification - Includes both an overview and specification data for the POC, or "pilot" system. This document is expected to be robust enough to support clear understanding of what the configuration, system requirements and operational requirements are within the POC. Material within this specification is to include, but not limited to: • i. System configuration data; • ii. Data dictionary and Entity Relationship Diagram (ERD); and • iii. Business Requirements Matrix. •b. Executive Briefing Packet - Intended to facilitate cross-program marketing of the data warehousing project within NHTSA and to be used for executive and senior management authorities in discussions with stakeholders. This package should include some standard forms for capturing feedback during discussions. •c. Training / Use Packet - Intended to serve as a training aid to facilitate users in using the interface as well as allowing system administrators the ability to manage the application. The package is not expected to be "all inclusive" but robust enough to give the users the high-level aspects of the system use to get them started. •2. NHTSA Corporate Information Factory (CIF) - The Contractor is required to develop and implement on behalf of the NHTSA CIF program using a multi-stage data processing and data warehousing platform for the purpose of data management, research, investigative activities, and public dissemination of non-PII / non-sensitive data deemed as distributable. •a. Data Migration and Preparation - Datasets Included: The contractor is required to work together with the government to identify datasets which can be readily integrated within the NHTSA CIF Version 1.0. This work of course cannot be unlimited due to project schedule and cost expectations. As such, work for this project will be performed based on a negotiated dataset schedule that is a result on an analysis period following the successful implementation of the "pilot". The Contractor is expected to develop a Data Selection Matrix, which will aid the government in making decisions on suggested datasets for inclusion in the NHTSA CIF Version 1.0. The Contractor is required to perform the initial analysis to determine if the migration of suggested datasets is achievable within the Level of Effort (LOE) contained within the data migration and preparation line item of this contract. •b. System Development / Implementation - The Contractor is required to develop the first iteration of the NHTSA CIF using the requirements discovered as a result of the system and software requirements specification work contained within this contract. Within the initial documentation effort, system and software requirements will be prioritized and identified for inclusion within specific iterations of the system. It is expected that all high-priority / high-risk requirements will be agreed upon for each iteration of the NHTSA CIF prior to initiation of development, which will aid in defining of scope. As such, the final product and what the expected outcome of features, datasets, and output options are of the NHTSA CIF Version 1.0 is expected to be agreed upon following completion of the first phase of the requirements phase to be identified within the project plan by the Contractor. The Government will approve the elements to be contained within NHTSA CIF Version 1.0 prior to initiation of Phase 2 to ensure work can be achieved within the expected level of effort (LOE) planned for the phase. •c. Ongoing Iterative Design - The Contractor is expected to manage the system development activities in a manner that allows for iterations of the system to be fully completed and operational prior to initiation of "new" iterative design requirements. This will also require that the Contractor maintain the documentation set to ensure up-to-date information is contained within the content, and stored within a Government approved repository. •3. NHTSA Corporate Information Factory Documentation Requirements - The Contractor is required to develop a full set of documentation to support the project, which includes at a minimum the following : •a. Data Decision Matrix / Integration Decision Form - A documentation set which describes the high-level information about a proposed dataset to be included in the NHTSA CIF. The matrix is expected to describe several attributes about the data to include at a minimum: stakeholders, audience, use, size, number of rows, attributes (data only, data + images, etc.), relationship to other datasets, and difficulty of integration. The form associated with the matrix is to be digitally signed using Adobe digital signature by the program sponsor, the NHTSA CIF project manager and COTR. In addition, the process is required to include digital signature of the NHTSA OCCI associate administrator; NHTSA CIO and NHTSA Chief Council representative, or their designees, prior to allowing public data to be made available to users external to NHTSA. NOTE: Preparation of the data within a staging area behind the DMZ firewall prior to movement to the external data warehouse is thus required for all publically targeted data as a general requirement in the migration process described in system documentation. •b. Proof of Concept (POC) Packet - A high level architecture and system design description. The document is to serve as an initial technical and non-technical description that can be distributed within NHTSA to market the principles of the NHTSA CIF. This specification will include at a minimum: • i. Background information; • ii. System design concept; • iii. Base system configuration and user system requirements; • iv. Data flow diagrams and approval process; • v. Entity relationship diagram for base datasets and data descriptions for both in-house and public facing sides; and • vi. Executive brief / slides to showcase platform for off-line audiences. •c. System Requirements Specification (SyRS) - The Contractor shall deliver the SyRS within the first phase of system implementation to support the program documentation process. The SyRS is intended to serve as a high level architecture and system design document to define what the NHTSA CIF is and how data is prepared and communicated through the systems technologies and interfaces. This document is required to follow IEEE standards, unless approved by the government. •d. Software Requirements Specification(s) (SRS) - The Contractor shall deliver a set of SRS documents within the first phase of system implementation that will be used to support the completion of the system development and implementation. The documentation is expected to be broken up into multiple SRS documents for each software piece of the NHTSA CIF. For the purposes of the public side of the NHTSA CIF, it is required that SRS documentation be written to support the use of the system within the public, and as such a separate pack of SRS documentation is required to be developed for this environment, which will be posted to a technical support area of the Public Information Center (PIC). In general, the SRS is intended to serve as a complete overview and design document to define what the NHTSA CIF is from the software level to the end users. In addition, the use of the interfaces, the data within the system and the relationship to the business requirements is described. This document is required to follow IEEE standards, unless approved by the government. •e. Software Test Plan (STP) / Test Logs - The Contractor is required to develop and maintain a full software test plan and associated test logs, which is to be reviewed and accepted by the government. The STP will include procedures for testing, documentation and acceptance to include (where applicable): • i. Alpha • ii. Beta • iii. Section 508 • iv. Usability; and • v. User Acceptance Testing All test logs are to be maintained by the Contractor and available to the government upon request for each of the test phases. Testing is expected to conform to the agreed upon STP, Section 508 guidance and IEEE standards where applicable. •f. Business Requirements Matrix - The Contractor shall provide a deliverable which shows the key business requirements and which system component is used to support the need. Since not all business requirements will be completed within the first phase of development for the pilot this document should be considered a tool for scope management and a working document. The CCB will be an input into this deliverable in the future following establishment of the CCB after initial completion of the NHTSA CIF "pilot". The Contractor will be required to maintain the repository of requirements as a function of the CCB review / approval process throughout the life of this project. •g. Change Management Plan / Process - The Contractor is required to document the process for which changes are to be managed and support the change management process that will be used to track and log changes which are proposed for review by the CCB. The Contractor will participate as a non-voting member / consultant and support the documentation and presentation of material to the CARS Data Warehouse CCB. CCB review is required for changes which are deemed to be significant to scope, usability, functionality or have a significant impact on the timeline or costs of the system. •h. Internal Controls - The Contractor shall assist in determining the best manner for conducting internal audits, applying process controls, and related functions. Controls will be in place for addition of new data as well as the process for reviewing and establishment of new ETL processes. Data controls are expected to be fully documented as well as the process for how information is distributed to the public facing environment. It is important that this aspect of the data processing within the CIF is tightly controlled to ensure there is no release of PII and/or sensitive data which has not been masked for release to the public. •i. Data Dictionary / Entity Relationship Diagram - The Contractor is required to support maintaining an up-to-date Data Dictionary for the database that serves to support the overall functionality of the internal and public facing sides of the CIF. In addition, an Entity Relationship Diagram (ERD) is required to be delivered prior to initial implementation and continually maintained during development/implementation of CIF iterations and/or modifications. To support the ERD, a business focused data dictionary clearly correlated to the ERD is required to be developed for the internal data warehouse as well as the externally public facing data warehouse. The public content/documentation will be posted within the PIC technical guide area as a resource for the public to allow clearer understanding of the data being presented to the users. As such, there will essentially be two sets of data documentation required to be maintained by the Contractor. The approach to maintaining the data dictionary may be better supported through technology rather than a single typed file. As such, the Government is open to options on management of the metadata for the CIF as long as the solution is easy to use and clearly understandable by the end user(s). •j. Customizations / Scripting / Graphics - The Contractor is required to create and manage a repository of all customizations, scripts and graphics used within the NHTSA CIF. The repository should be created and managed using technology currently in existence at NHTSA, or through the use of a low-cost/no-cost open source solution. The repository is required to be searchable and contain proper indexing to allow appropriate users the ability to find material easily. The repository is to be referenced within system documentation whenever applicable. •k. Security Authorization (SA) Support Material - The Contractor shall assist the government in the creation of Security Authorization (SA) material for use within NHTSA to ensure their IT portfolio is up-to-date and in compliance with NIST standards in order to meet the demands of the Office of Management and Budget (OMB) and NHTSA Security. A base level of SA documentation will be made available to the Contractor to update and build upon for the environment, which is based on work performed by a prior contractor. •4. System / End-User Training - The Contractor will be required to support "train the trainer" training on the use of the system for internal users at both the technical and program level. Training material is to be created and/or supplied on the use of the tools. Training on the use of the NHTSA CIF will be required within 15 days of deployment of the "pilot", and continued training support throughout the course of the performance period will be required at a reduced rate as new features and data is included. As such, the Contractor should expect that following initial training a minimum of one monthly training session is required for internal users, which could be performed on one reoccurring workday. •5. Public User Training / Help Material - The Contractor is required to use professional graphic and documentation development talent to develop material for distribution in a help area of the Public Information Center (PIC) portion of the NHTSA CIF. The PIC's help area is expected to have at a minimum a set of user guidance for the general user. In addition NHTSA CIF software requirement specifications, and data description and ERD documents for only the publically available portions of the environment are to be created to allow the public user which is interested in research using the data the ability to do so easily. The concept is to present the public audience with not only preformatted "slices" of the data, but also the "raw" data with a set of help content that can act as a "data catalog" for the public users. The documentation does not have to be presented in PDF format, but the Contractor may create HTML formatted content to supplement the PIC using a NHTSA approved web template. The Contractor is responsible for maintaining the content and/or documentation in this area in a manner that allows it to be reflective of the most current release of data within the public facing components of the CIF. •6. OPTIONAL Phase 3: Maintenance / Continued Operational Support - Following completion of the main development phase within this contract the Contractor will supply ongoing support to ensure the system is adequately supported through the end of the performance period. This requirement is on an "as needed" basis for minor system modifications, maintenance, enhancements, and user/ administrator assistance. Work performed within this phase may require addition of other datasets not included within the "proof of concept" and/or NHTSA CIF Version 1.0 phases. Work may include expansion of documentation to include system and/or software requirement information. It is understood and reasonable to assume that due to the iterative approach of this contract the initial phased work will not include all NHTSA datasets, and as such there will be an ongoing requirement for incorporation of new datasets and system features through a process of continuous improvement. The primary development phases are expected to establish principle dataset for the NHTSA CIF. Contained within this work will be a new feature and dataset development review / approval processes, which will be used in future work by the Contractor and Government to manage scope for ongoing maintenance requirements. The maintenance phase may be broken up into multiple optional tasks to be issued based on funding, program priorities and the needs of agency. Each task period will include proper guidance and a clearly identified scope that will be established by the Government. Funding level and period of performance of the optional period(s) will be determined at the time of award and managed by the CO/COTR team. Format of Corporate Capabilities Statement: Any interested organizations should submit the Corporate Capability Statement which demonstrates the firm's ability and interest in no more than 10 pages to perform the key requirements described above. All proprietary information should be marked as such. All respondents are asked to indicate the type and size of their business organization, e.g., Large business, Small Business, Small Disadvantaged Business, Women-Owned-Business, 8(A), Historically Black College or University/Minority Institution (HBCU/MI), educational institution, profit/non-profit organization, in their response. Interested offerors shall respond to this Sources Sought Notice no later than 15 calendar days from date of posting. E-mail is the preferred method when receiving responses to this Notice.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/DOT/NHTSA/NHTSAHQ/2011-001/listing.html)
- Record
- SN02214378-W 20100724/100722234836-dcc8822a8fe923599c5a6d66654abd8e (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 |