R -- BASELINE COMPARISON SYSTEM (BCS) UPGRADE AND UPDATE

Notice Date

July 5, 2001

Contracting Office

NASA/George C. Marshall Space Flight Center, Procurement Office, Marshall Space Flight Center, AL 35812

ZIP Code

35812

Solicitation Number

8-1-1-T3-D2144

Response Due

July 18, 2001

Point of Contact

Paula J Battles, Contract Specialist, Phone (256) 544-5940, Fax (256) 544-2812, Email penny.battles@msfc.nasa.gov -- George E. Pendley, Contracting Officer, Phone (256) 544-2949, Fax (256) 544-2812, Email george.pendley@msfc.nasa.gov

E-Mail Address

Paula J Battles (penny.battles@msfc.nasa.gov)

Description

NASA/MSFC plans to issue a Request for Quotation (RFQ) for contractor services to provide MSFC/NASA with Reliability, Availability, Maintainability, Operability, and Cost (RAMOC) analysis capability to support the development of low cost advanced space transportation systems. OVERVIEW: If the United States is to remain competitive in the launch services market, substantial improvement in vehicle and ground systems reliability, availability, maintainability and operability (RAMO) and reduced support infrastructure and associated recurring operations cost are essential. The factors that now drive current and will drive future launch operations costs can be understood through acquisition of quantifiable data and analyses of appropriate metrics. NASA engineers and management must have the ability to accurately and rapidly assess pertinent characteristics of space transportation vehicle and ground systems, for all phases of design, development, test, production and operation. The data needed to support the necessary analyses are available to a limited extent in government and industry databases but are difficult to access in an effective manner. The Baseline Comparison System (BCS) will aggregate these disparate databases into a single source of launch vehicle and aircraft information pertaining directly to system characteristics that allows detailed analysis of existing systems and projections for conceptual systems. The goal toward which use of the database is directed is to 1) reduce costs through increased systems RAMO by analyzing potential technology incorporations with tools and techniques based on existing rocket and aircraft data, and 2) integrate and apply proven analysis and simulation tools to facilitate understanding the total system. The work in this contract is intended to establish a BCS with enhanced capability (automated data collection/data mining) on a MSFC server, update and upgrade the hardware and software as appropriate in support of this enhanced BCS. In addition, this effort should include verification of the data and internet functionality. When completed, the BCS should contain a comprehensive set of data from all the STS flights to date as well as equivalent comparison data from the aircraft and ELV data sources. The BCS shall have the capability to compare and assess theoretical transportation systems versus existing or other theoretical transportation systems with a simple, easily navigated GUI interface capable of producing a variety of output formats -electronic display, hardcopy, output to file, etc. DESCRIPTION OF WORK: The Baseline Comparison System (BCS) database was developed in 1998 and demonstrated within NASA MSFC's Virtual Research Center(VRC). The purpose of the VRC Internet-based Database/Tool Set was to 1) increase productivity, functionality, reliability and operability gains at a reduced cost, by leveraging corporate knowledge, expertise and systems analysis techniques with comparisons traceable to actual rocket and aircraft data, and 2) incorporate and apply proven analysis and simulation tools to better communicate and understand inherent benefits of proposed 2nd/3rd Generation technologies, as applied to the system and overall integrated system. Experience has shown that current manual data collection techniques are time consuming and labor intensive. To populate the database more efficiently and at a lower cost, an artificial intelligent agent systems will be developed and installed for the VRC-based RAMO database, using the current USAF Integrated Weapons System Database as a model. This system development has been at the forefront of deploying Intelligent Integration of Information (I3) technology and provides integrated data source wrappers, intelligent querying, I3 common languages, and data source mediators to assist designers in accessing information from their desktop computer. This work will continue the development of the database capabilities by adding automated data mining (automated data collection, etc.,) and updating the database to current shuttle, aircraft, and ELV data. In addition, this effort will add the capability to compare and assess theoretical transportation systems versus existing or other theoretical transportation systems with a simple easily navigated GUI interface capable of producing a variety of output formats -- electronic display, output to hardcopy, output to file (spreadsheet, etc.). TASKS: 4.1 Develop and Implement Automated Data Mining Capabilities (automated data collection, etc.,) for the BCS resident on the MSFC VRC. This task is to provide an interface within the VRC BCS capable of connecting to and retrieving data from the appropriate data sources and should include but not be limited to the following systems/databases: 1. USA/NASA-KSC Fast Retrieval of Enterprise Data (FRED) system; 2. KSC PRACA; 3. Shop Floor Data Collection System; 4. Integrated operations System; 5. Rockwell PEARL Database (NSLD -- NASA Shuttle Logistics Depot); 6. IWCS (Integrated Work Control System); 7. TACCS (Time, Age, Cycle Control System); 8. Redstar Database; 9. MSFC PRACA (for data not included in the KSC PRACA system (test data, etc.,); 10. JSC PRACA (for data not included in either the KSC or MSFC PRACA. The source of the data should be identified, however the data source should be transparent to the user of the VRC BCS display. The data content and structure must be compatible with the Langley Research Center Reliability and Maintainability Assessment Tool (RMAT) and the Marshall Space Flight Center Launch Systems Operations Cost Model (LSOCM). This task will include all documentation (update to existing user's manual as a minimum), user training and support as required. 4.2 Update BCS Database to validate the data mining capability (automated data collection, etc.), the BCS database will be updated using the latest available information from the appropriate databases. The BCS shall provide the capability to verify through automated means that all updated and existing data in the BCS Database is traceable back to the original source data. A printable log file shall be generated as an output of the BCS Database as evidence of this verification/validation procedure. This update shall include a comprehensive set of data from all the STS flights to date as well as equivalent comparison data from the aircraft and ELV data sources. Note: Standard R&M practices and terminology shall be used in the enhanced BCS database system. 5.0 DELIVERABLES: 5.1 Fully operational, verified, validated, and VRC integrated BCS. 5.1.1 The delivered BCS shall have verified/validated Automated Data Mining capability (automated data collection, etc.), including all necessary hardware and software. Validation of data mining capability shall be accomplished and demonstrated by the automated update of the BCS to include all STS flights to date. 5.1.2 The final delivered BCS database shall be populated with all STS flights to date. Equivalent comparison data shall be provided in the ELV and aircraft sections such that useful comparisons can be made. 5.1.3 BCS installation, integration, and setup. The updated BCS shall be delivered to MSFC and integrated into the VRC system and all BCS functions tested and verified. All appropriate administrative and security functions should be fully operational and the appropriate MSFC personnel given full access and control. 5.1.3.1 An additional electronic delivery (CD's, etc) of the BCS complete with all files including final updates to database (all STS flights to date and equivalent comparison data from ELV and aircraft. This delivery will include all code, both compiled and non-compiled (Javascripts, etc). 5.1.4 The BCS will support up to 10 concurrent users. 5.1.5 The BCS will support a minimum of 10 GB of data storage. 5.1.6 The BCS data collection interface is to be within the VRC BCS, meaning that the VRC has a network interface to the databases from which the BCS is gathering data from. 5.1.7 The BCS user data access will be through a web browser and will have an efficient, easily navigated GUI interface. 5.1.8 The BCS shall have the capability to produce a variety of types of output, reports, etc. The BCS shall be capable of easily changing from one output format to another to accommodate a variety of demands. 5.1.9 The BCS shall have the capability to compare and assess theoretical transportation system versus existing or other theoretical transportation systems using similar and extrapolated data from existing systems. The BCS shall accommodate user input data to characterize new systems and technologies in place of similar or extrapolated data based on existing systems. The option for this shall be at the user's discretion. There shall be a wide variety of comparison metrics available to the BCS user for analysis. The comparison metrics shall include but should not be limited to the following metrics: Cost, Reliability, Maintainability, Supportability, Availability, etc. 5.1.10 The BCS shall provide a backup and recovery capability for all data to protect against data loss. 5.2 Documentation of the processes: All source data should be explicitly identified and the traceability path from raw data (including if possible an assessment of the probability of error due to human in the loop problems when data is entered into the system by the engineer/technician) to BCS database to final output data from the BCS database defined. Method and detailed description of data input to spreadsheets or first level database system should be included as part of traceability path definition. A brief description of each of the source databases should be included as well as the method of data extraction and transfer. Points of contact for source data should be provided with email address, mailing address, phone numbers, etc. Sufficient information should be provided such that any data from the BCS Database can be independently verified. Other process descriptions should be included if they are required for independent verification of any BCS database output. Note: Standard R&M practices and terminology shall be used in the enhanced BCS database system. 5.3 Training and Support. 5.4 BCS User's Manual and other documentation. Database User's Manual should be provided in hardcopy, electronic, and online as part of the BCS Database System interface. The manual should address in detail all capabilities of the BCS Database System such that a new user can successfully navigate/operate the system in a reasonable time frame. 6.0 SCHEDULE: Work shall be completed as necessary as well and submission of all required deliverables as scheduled on or before November 30, 2001. This procurement is being conducted under the Simplified Acquisition Procedures (SAP). NASA/MSFC intends to purchase this service from Lockheed Martin Corporation pursuant to FAR 6.302-1. Interested organizations may submit their capabilities and qualifications to perform the effort in writing to the identified point of contact not later than 4:30 p.m. local time on July 18, 2001. Such capabilities/qualifications will be evaluated solely for the purpose of determining whether or not to conduct this procurement on a competitive basis. A determination by the Government not to compete this proposed effort on a full and open competition basis, based upon responses to this notice is solely within the discretion of the government. Oral communications are not acceptable in response to this notice. All responsible sources may submit an offer which shall be considered by the agency. An Ombudsman has been appointed. See NASA Specific Note "B". Any referenced notes can be viewed at the following URL: http://genesis.gsfc.nasa.gov/nasanote.html

Web Link

Click here for the latest information about this notice (http://nais.msfc.nasa.gov/cgi-bin/EPS/bizops.cgi?gr=D&pin=62#8-1-1-T3-D2144)

Record

Loren Data Corp. 20010709/RSOL021.HTM (D-186 SN50Q9D7)