70 -- Request for Information - Test Information Management System

THIS IS A REQUEST FOR INFORMATION ONLY. The Government does not intend to award a contract or any other type of agreement on the basis of this synopsis or to otherwise pay for the information solicited under this synopsis. This is NOT a request for a proposal or an invitation for bid, merely a request for information only. The Government is interested in obtaining information from industry to identify existing commercial off the shelf (COTS) systems, or ongoing or planned development efforts for test data modernization studies. Please see the Statement of Objectives (SOO) below.The information provided through the responses will be used to aid in requirements definition for future acquisitions. POINT OF CONTACT: Technical: contact@example.gov Dwight Fuqua, 412/LG/LGLO Edwards AFB, CA +1 (555) 000-0000 x 2823 or Contracting: Patrick Terry, AFFTC/PKDB Edwards AFB, CA +1 (555) 000-0000 contact@example.gov . STATEMENT OF OBJECTIVES C-17 Test Information Management System C.1. Purpose. This document provides the objectives for development and integration of a C-17 Test Data Archive System. The test team envisions an integrated architecture maximizing the Government's investment to date in information management, data processing, and instrumentation resources. C.2. Scope. This effort encompasses all classes of information associated with the C-17 Follow-on Flight Test Program (FOFTP), and much of the information from the earlier Full Scale Engineering Development (FSED) program phase. Information elements are categorized as either programmatic information or test data, where: q Test Programmatic Information includes Test Plans, Test/Work Requests, and Test Reports; and the supporting documentation such as Class T-2 Aircraft Modification Documentation, Test Parameter Requirements (TPR) documents, and instrumentation configuration load files. q Test data is raw and processed flight test data available in engineering unit format. Information from the C-17 aircraft instrumentation suite, Edwards AFB range and other test range resources, and Boeing Long Beach operations. It includes digital, analog, video, and audio source data items. C.3. Goal. Government-managed C-17 Test Information Management structure compliant with DOD Directive 5015.2, Design Criteria Standard for Electronic Records Management-Software Applications, and the C-17 Security Classification Guide. C.4. End-Users. Two categories of users are provided based on anticipated access demand. q High Demand Users: Three primary geographically separated locations: System Program Office at Wright Patterson AFB, OH; Global Reach CTF at Edwards AFB, CA; and Boeing Engineering Operations at Long Beach, CA. q Lower Demand Users: Government and Boeing sites on the AFFTC Complex; Sites within the Boeing Long Beach Complex; HQ Air Mobility Command at Scott AFB; Test Team Units deployed at remote locations; and NASA Dryden and Ames Research Centers. C.5. C-17 FOFTP Objectives. The C-17 Test Information Management architecture shall satisfy the seven objectives defined by the C-17 Test Integrated Product Team herein. The technical approach will integrate, to the extent feasible and affordable, each objective. Solutions proposed may include hardware and software-based upgrades, modification of procedures, and/or any combination of these that clearly integrates each objective area into the C-17 Test Information Management architecture. q Objective 1: Information Exchange, Users will have the ability to exchange, transmit, and receive, programmatic and test data information elements necessary for mission execution. The capacity and bandwidth of the C-17 Test Information Management System must simultaneously support all end-users using existing Government internet access. The System will facilitate the C-17 test business process in a manner that has been approved by the Government to meet information assurance, and security requirements. q Objective 2: Information Access. Within the C-17 Test Information Management System, users will have the ability to access and retrieve programmatic and test data information for planning and reporting purposes. All information will be in digital format (where practical), accessible from engineering workstations with Government Internet access. Search capability will employ DTIC keyword standards and formats; current and archived information will be accessible using standard Government PC software products (i.e.; MS Office Suite, Adobe, Matlab...etc). Specialized and tailored products will be available from long-term archives within 24-48 hours; server side processing will be maximized to support data requests within minutes subject to bandwidth restrictions. Server side processing must fully comply with Government Information Technology (IT) security and assurance guidelines as approved by local implementing agencies. Role-based privileges will provide the necessary security and integrity for the system. Operational Availability and Reliability must exceed 95%;, local and national backup protocols must be in-place to support downtime periods. Emerging information management concepts, namely "Data Merging" and "Data Mining" are highly desirable attributes if economically achievable within the projected schedule guidelines. q Objective 3: Data Storage. Within the C-17 Test Information Management System, both test programmatic information and test data must be accessible within stated timelines therefore the architecture must have the capability to retain information in both an "immediately accessible" state, and an archived state for long term access. Based on C-17 end-state data management policy; the storage capacity must be readily expandable as further data is collected and legacy information is converted to digital format. Data storage devices and interfaces must fully comply with Government Information Technology (IT) security and assurance guidelines as approved by local implementing agencies. Concerning long term access to archived data, IRIG Standard Chapter 10 is the solid state recorder standard that defines the use of a common set of playback/data reduction software to take advantage of emerging random access recording media. Stated therein, digital data acquisition shall be compatible with the multiplexing of both synchronous and asynchronous digital inputs such as Pulse Code Modulation (PCM) and MIL-STD-1553 data bus, time, analog, video, ARINC 429, discrete and RS-232/422 communication data. The C-17 Test Information Management System seeks to comply, within an acceptable schedule and if proved economically practical and feasible, with this common format standard. q Objective 4: Magnetic and Audio/Video Tape Storage Mediums. Within the C-17 Test Information Management System, an on-demand capability to retrieve archived legacy and near term test data from magnetic tape media will be available to support data requests. Support turn-around time must not exceed 72 hours from date/time of request. Conversion and storage of all media must fully comply with Government Information Technology (IT) security assurance guidelines as approved by local implementing agencies. q Objective 5: Paper and Still Photo Documentation. Within the C-17 Test Information Management System, on-demand conversion of C-17 FOFTP and FSED legacy programmatic information and test data to digital format is required. That data must be accessible as described in Objectives 1-3 above. Keyword search files will be created in MS Word and/or Adobe PDF formats with links to the referenced documents using DTIC guidelines. Conversion and storage of all paper products must fully comply with Government Information Technology (IT) security and assurance guidelines as approved by local implementing agencies. q Objective 6: Standardization of Data Products. Within the C-17 Test Information Management System, a standard data package will be defined and coordinated with managers and engineers for completeness and quality. q Objective 7: Instrumentation and Data Processing Support at the Global Reach CTF. The C-17 Test Information Management System will require integration of many diverse tools, some in use, some being developed. AFFTC-wide, Commercial and/or Non-developmental item (CaNDI) software products are being purchased and deployed. Two examples of CaNDI products are Telelogics DOORSTM and SYNERGYTM software packages respectively employed to track requirements and configuration management plans and issues. Employment of this class of tools will require integration into C-17 IPT business practices. The Test Information, Generation, Analysis, and Reporting System (TIGARS) is the C-17 legacy tool used by managers and engineers. The user interface for TIGARS is bulky; improvement of this interface is possible using CaNDI software and is a primary sub-objective. The Flight Test Support Software (FTSS) is being developed by the CTF to improve management and access to the measurands index, historical and current calibration data items, and the Test Parameter Report (TPR) library. It must interface with the OMEGA database providing seamless update of over 40,000 defined and definable parameters. Integration of the FTSS-OMEGA packages is a primary sub-objective of this effort. C.6. Schedule. The services provider will provide a detailed schedule. C-17 FOFTP Schedule Objectives are: o FY 2004. Requirements Definition with parallel Proof-of-Concept Studies; Acquisition, Integration, and Deployment of Tools and Resources; o FY 2005. Integration into the C-17 Business Process.