99--Aviation Safety/Accident Prevention (ASAP)

This requirement is limited to only those previously qualified and li= sted on the Southwest Regional Qualified Vendors List (QVL) for the Results= Basic Ordering Agreement (BOA). The FAA has an evolving requirement for a Aviation Safety/Accident Preventi= on (ASAP) reporting system, a key element in providing the FAA with empiric= al data and easy access to information regarding aircraft system difficulty= trends and other accident precursor information. =20 The FAA Administrator=E2=80=99s Safer Skies initiative requires that the FA= A become a data driven agency that uses a proactive, empirical approach to = initiate corrective measures before accidents occur. ASAP provides that em= pirical data. =20 Background and Objectives The Rotorcraft Directorate (ASW-100) created the ASAP information system th= at collects aircraft data from a number of national databases. ASAP is a r= elational database, created in FoxPro 2.6, that adds trends and warnings to= safety data not available in the national databases. Accountable technica= l personnel investigate, analyze, and input safety information from operato= rs and manufacturers to provide an in-depth analytical capability. The abi= lity to discover trends and initiate warnings gives FAA senior decision mak= ers information for proactive safety measures in support of Safer Skies ini= tiatives. The current ASAP system needs re-hosting to a new software platfo= rm and an upgrade of its capabilities to meet the Continued Operational Saf= ety Management (COSM) business plan items. =20 Contractor support is needed to produce documentation of the current ASAP s= ystem. Design documentation is required to prepare for the re-hosting of t= he information system to a new web enabled platform.=20 Technical Services Requirement=20 The Technical Services Requirement defines the =E2=80=9CHigh Level=E2=80=9D= tasks to be completed by the contractor.=20 1.=09Project Management Deliverables =C2=B7=09Project Plan =C2=B7=09Project Gantt Chart =C2=B7=09Risk Assessment Sheet (note: this can be a part of the Project Pla= n) =C2=B7=09Monthly status reporting 2.=09Design Deliverables =C2=B7=09Users Requirements Document =C2=B7=09Users Manual =C2=B7=09Design Document =C2=B7=09Format for use in the Windows OS/Microsoft Office 2000 environment Task 1: Produce Project Management Documentation The Contractor shall: Produce Project Management documentation listed in 3.0 above in accordance = with FAA AIR-520 Configuration Management and Standards and other standards= in paragraph 9 below. Task 2: Analyze Current ASAP Information System to produce Users Requiremen= ts, documentation. The Contractor shall: Gleen the user requirements from the current ASAP system and document them = in accordance with FAA AIR-520 Configuration Management and Standards. The= Users requirements document will contain user=E2=80=99s requirements as se= en presented in the software or gathered from existing documentation. The = document will also contain the national scope of captured data, analysis ca= pabilities, and output products currently available to FAA Directorates, AC= O=E2=80=99s, and field offices. Task 3: Analyze Current ASAP Information System to Produce Design Documenta= tion=20 The Contractor shall: Document the design of the current ASAP information system and produce a do= cument in accordance with FAA AIR-520 Configuration Management and Standard= s. The design document shall describe the system and subsystem architectur= e, operating environment, files and database design, input formats, output = layouts, human-machine interface, processing logic and external interfaces.= =20 Task 4: Analyze Current ASAP Information System to Produce Users Manual=20 The Contractor shall:=20 Produce a User Manual for the ASAP information system documented in accorda= nce with FAA AIR-520 Configuration Management and Standards. The user manu= al shall contain all essential information required for the user to make fu= ll use of the ASAP information system. The manual shall include a descript= ion of the system functions and capabilities, contingencies and alternate m= odes of operation, and step-by step procedures for system access and use.= =20 Government Furnished Resources 1 Information Sources The government will provide copies of all information sources necessary for= the contractor to perform the duties defined in Section 3. The information= sources will be identified with the contractor upon task order award. =20 2 Documentation The government will provide copies of all documentation necessary for the c= ontractor to perform the duties defined in Section 3. The documentation sou= rces will be identified with the contractor upon task order award. Document= ation will also be furnished on CD-ROM. 3 Facilities, Supplies and Services The government shall furnish all facilities, supplies and services necessar= y to support contractor personnel performing the duties defined in Section = 3. Place of Performance/Work Location Technical services shall be primarily performed at the FAA Southwest Region= al Office, 2601 Meacham Blvd., Fort Worth, TX 76137 Vendors interested in participating in a competitive procurement for this r= equirement are required to attend a pre-proposal conference at the date/loc= ation listed below. Due to the complexity of this requirement, the Governm= ent will not accept proposals from non-attendees. =20 DATE/TIME: =0915 July 2003 from 9:00 until 11:00 A.M LOCATION: =09Southwest Region Headquarters =09=09=09=092601 Meacham Blvd. =09=09=09=09Fort Worth, TX 76137-4298 =09=09=09=09Don Watson Room =09=09=09=094th Floor Primary point of Contact: =09Eric L. Barnett, telephone 817- 222- 5363 Secondary point of contract: =09Clark Davenport +1 (555) 000-0000 E-mail: =20 Eric - contact@example.gov Clark - contact@example.gov=20 Reservations must be made for all attendees not later than July 10, 2003, 2= :00 p.m. (CST). Following the pre-proposal conference, vendors interested in participating = in a competitive procurement for this requirement are requested to submit a= capabilities statement not to exceed 10 pages in length. It is requested t= hat this statement address the following:=20 =C2=B7=09Provide a synopsis of experience focusing on each task identified = above =C2=B7=09Provide a list of previous efforts of the same or similar scope. = Include company name, point of contact, phone number, and value of the cont= ract. =C2=B7=09Provide a project scope assessment that includes estimated labor c= ategories/number of personnel, estimate of time to complete project and ove= rall cost estimate. (This data will be used for informational purposes on= ly.)=20 The capabilities statements are due in the Contracting Office at any time, = but no later than Thursday, July 31, 2003, at 4:00 p.m. Central Daylight Ti= me, and/or shall be delivered to the following address: =09Results Contracting Officer, FAA =09Headquarters Building/Room 216 =096500 South MacArthur Blvd =09Oklahoma City OK 73169 The FAA will not use the capabilities statements to screen or down select. = Rather, they will be used to determine the range of vendor interest, experi= ence and capability.=20 This is not a request for offers. However, the Government may invite selec= ted vendors for follow up discussions. Interested vendors must make their = reservations for the conference by providing information regarding conferen= ce attendees to the personnel listed above. Any additional conference info= rmation will be made available at that time.