ATTACHMENT_4_ADS-B_SOO_Revision_01.pdf
PDF 616 KB Posted
- Attached to
- T-38C Avionics Component Integration and Contractor Logistics Support Federal contract opportunity
- Solicitation number
- FA8211-15-R-0001
About this file
ADS-B SOO
View the file
Other files for this federal contract opportunity
Show all 50
T-38C Avionics Component Integration and Contractor Logistics Support has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Attachment 4
FA821115R0001
Revision 1 (02 February 2015)
T-38C Avionics Component Integration (AvCI)
STATEMENT OF OBJECTIVES (SOO)
Automatic Dependent Surveillance – Broadcast
(ADS-B) Development and Integration
T-38 Systems Program Office (SPO)
AFLCMC/WLDMA
Hill AFB UT 84056
Date 15 January 2015
Revision 1 (02 February 2015)
Revision 1 (02 February 2015)
Table of Contents 1 Overview
1.1 Purpose
1.2 Background
2 Objectives
2.1 Development Concept
2.2 Notional Development Schedule
2.3 Key Performance Parameters
3 Scope of Work (CLIN X003 AE)
3.1 Administration
3.2 Program Management
3.3 Data Rights
3.4 Quality Assurance
3.5 Corrosion Prevention and Management
3.6 Configuration Management
3.7 Risk Management
3.8 Software Management
3.9 COMMERCIAL SMALL BUSINESS INVOLVEMENT
4 Automatic Dependent Surveillance – Broadcast (ADS-B) Proposal (CLIN X003 AA)
4.1 ECP Content
4.2 System Requirements
5 Test and Test Support Activities (CLIN X003 AA)
5.1 System Test and Integration
5.2 Developmental Test (DT and Force Development Evaluation (FDE)
6 Certifications and Approvals (CLIN X003 AA)
6.1 Authority to Test and Authority to Operate
6.2 Platform Information Assurance
6.3 Airworthiness
6.4 CNS-ATM
7 Formalize Change after Successful Test (CLIN X003 AA)
Page ii of iv
Revision 1 (02 February 2015)
7.1 Finalize configuration and Release Documents
8 Hardware and Production and Delivery
8.1 A-Kits - Aircraft Modification Kit (CLIN X003 AB)
8.2 B-Kits – System LRUs (CLIN X003 AC)
8.3 Production Schedule
8.4 Packaging
8.5 Contract Field Team (CLIN X003 AD)
9 Diminishing Manufacturing and Material Shortages (DMSMS) (CLIN X003 AE)
9.1 DMSMS Management
9.2 DMSMS Reporting
9.3 DMSMS Mitigation
10 Government Furnished Equipment (CLIN X003 AE)
10.1 Systems Integration Lab (SIL)
11 Associate Contractor Agreement
12 Conditions and Assumptions
13 Reference Documents
13.1 T-38C Performance Requirements
13.2 Department of Defense Instructions
13.3 Air Force Instructions
13.4 Air Force Manuals & Pamphlets
13.5 Military Standards and Specifications
13.6 Military Handbooks
13.7 Civilian Aviation Directives
14 Deliverables:
15 Technical Data Package (TDP)
16 Record of Revisions
Page iii of iv
Revision 1 (02 February 2015)
Table of Tables Table 2-1 T-38C Avionics System Components Table 2-2 Notional Development schedule Table 6-1 Minimum Documents Required for ATT/ATO Table 8-1 T-38C Aircraft locations
Page iv of iv
Revision 1 (02 February 2015)
1 Overview
1.1 Purpose
This SOO provides the basis for a priced proposal to develop and integrate a solution for the Federal Aviation Administration (FAA) Automatic Dependent Surveillance - Broadcast (ADS-B) system requirement into the T-38C aircraft and avionics system. The requirement is to provide a developed and fully integrated solution to include all drawings, technical data and Time Compliance Technical Order (TCTO) information outlining installation requirements.
1.2 Background
All T-38C that will continue to fly after 1 January 2020 shall have ADS-B Out capability installed with equipment that:
1. Meets the requirements in TSO-C166, Extended Squitter Automatic Dependent Surveillance – Broadcast (ADS–B) and Traffic Information Service – Broadcast (TIS–B) Equipment Operating on the Radio Frequency of 1090 Megahertz (MHz)
2. Meets the requirements of Title 14 Code of Federal Regulations (14 CFR) § 91.227
As mandated by the FAA, Full Operational Capability (FOC) must be no later than 1 January 2020.
2 Objectives
2.1 Development Concept
The concept of development shall minimize, to the extent possible impact to the T-38C mission. The Government desires that the Time Compliance Technical Order (TCTO) be accomplished at the field level to reduce aircraft downtime and programmed maintenance impact. Field Level TCTOs are limited to approximately 25 man-hours.
Proposals shall provide an estimate of the time required for equipment retrofit. If the estimate exceeds 25 man-hours, the contractor shall provide a recommended retrofit solution. The related T-38C avionics system components are listed below in table 2-1.
Table 2-1 T-38C Avionics System Components
Part Number Description Supplier CAGE Unit(s) Per Assembly
34200602-3SRB NAVIGATION UNIT (EGI/INS) Honeywell International Inc. 94580 1
066-01143-0601 TRANSPONDER, MODE S Honeywell International Inc. 22373 1
066-01146-0101 PROCESSOR, TCAS II Honeywell International Inc. 22373 1
Revision 1 (02 February 2015)
2.2 Notional Development Schedule
The period of performance (PoP) shall not exceed 54 months from receipt of order. Table 2-2 depicts a notional schedule. The contractor shall use the PoP for development of the Integrated Master Schedule (IMS) and Material Fielding and Basing Plan for this effort. It is understood by the Government that there will be deviations from what is depicted in table 2-2 based on the Offeror’s proposed solution.
Table 2-2 Notional Development schedule
2.3 Key Performance Parameters
2.3.1 The ADS-B system shall meet or exceed the current system specifications. Refer to the following documents.
1. Meets the requirements in TSO-C166, Extended Squitter Automatic Dependent Surveillance – Broadcast (ADS–B) and Traffic Information Service – Broadcast (TIS–B) Equipment Operating on the Radio Frequency of 1090 Megahertz (MHz)
2. Meets the requirements of Title 14 Code of Federal Regulations (14 CFR) § 91.227
2.3.2 The solution shall integrate with the avionics system components and not compromise current system performance. All equipment shall continue to meet or exceed the current T-38C System Performance Specification. Additionally, the solution shall operate with the replacement components being developed as part of this contract.
3 Scope of Work (CLIN X003 AE)
3.1 Administration
3.1.1 The Contractor shall perform administrative functions, to include scheduling meetings, arranging facilities, providing status reports, documenting official decisions and actions assigned, and maintaining charter documents, records, and databases referenced within this document.
3.1.2 The Contractor shall appoint a primary Point of Contact (POC) for this contract. This individual shall be the primary representative and have the Contractor’s full authority to act on matters pertaining to the performance of the services under this contract.
Revision 1 (02 February 2015)
3.1.3 To meet the requirements of this contract the contractor shall be required to develop and deliver information to the Government in accordance with the Contract Data Requirements List (CDRL). Where possible the contractor shall submit one CDRL to encompass the program requirements. (e.g. Configuration Management Plan should include the HUD, MDP, ADS-B, VHF Nav/Comm development and integration and overall T-38C avionics system management)
The Government will use an alpha prefix of “A” for CDRLs if the delivery order is contracted in the base year of the contract. The alpha prefix “B” will be used for the CDRLs if the delivery order is contracted in year two of the contract.
3.1.4 All documents sited in this SOO may be available on ASSIST or other Government document repository sites. (https://assist.dla.mil/online/start/index.cfm) (http://www.e-publishing.af.mil/) (http://www.e-publishing.af.mil/otherpublishingsites.asp)
3.1.5 The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Department of the Air Force via a secure data collection site. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil.
Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the CMRA help desk.
• Reporting Period: Contractors are required to input data by 31 October of each year.
• User Manuals: User manuals for government personnel and contractors are available at the Army CMRA link at http://www.ecmra.mil.
Uses and Safeguarding of Information: Information from the secure web site is considered to be proprietary in nature when the contract number and contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data.
3.2 Program Management
3.2.1 The Contractor shall develop and deliver an Engineering Change Proposal (ECP). (CDRL
A014)
3.2.2 The Contractor shall develop and maintain an Integrated Master Schedule (IMS). (CDRL A001)
3.2.3 Kickoff Meeting: The Contractor shall host a kickoff meeting within 30 working days after receipt of order (ARO) and provide meeting minutes within five working days of meeting (CDRL A017) https://assist.dla.mil/online/start/index.cfm http://www.e-publishing.af.mil/ http://www.e-publishing.af.mil/otherpublishingsites.asp http://www.e-publishing.af.mil/otherpublishingsites.asp http://www.ecmra.mil/ http://www.ecmra.mil/
Revision 1 (02 February 2015)
3.2.4 Technical Interchange Meetings (TIM): The Contractor shall host TIMs as required, at an expected frequency of two per year. Levels of participation will be based on the subject matter. Meeting minutes shall be provided within five working days of the conclusion of the meeting. (CDRL A017)
3.2.5 Program Management Reviews (PMR): The Contractor shall host PMRs to brief program status to Government program office personnel. The Government will coordinate/notify the Contractor of the meeting schedule. There will be a maximum of two meetings per year. The PMR location will alternate between the Contractor’s facility and a government facility. Meeting minutes shall be provided by the Contractor within 5 working days of the conclusion of the meeting. (CDRL A003)
3.3 Data Rights
3.3.1 The Government requires Unlimited or Government Purpose Rights for all developed items, components, processes, computer software, and technical data used in the execution of this contract.
3.3.2 Software procured by the Contractor shall have the licensing agreement(s) assigned or transferred to the Government, giving the Government the same direct rights against suppliers that the Contractor would have.
3.3.3 The Contractor shall obtain prior written approval from the Procuring Contracting Officer (PCO) prior to committing to the use of any private and mixed funds developed items, components, processes, computer software, and technical data which it:
A. Intends to deliver with Limited Rights B. Intends to deliver with Government Purpose License Rights C. Intends to deliver with Restricted Rights D. May have less than Unlimited Rights E. Will use in the performance of this Contract F. Cannot meet the requirements outlined in paragraph 3.3.1 through 3.3.2
3.4 Quality Assurance
3.4.1 The Contractor shall implement and maintain a Quality Assurance (QA) program in accordance with AS9100 and AS9110 standards as applicable. As part of this QA program the Contractor shall maintain a responsive surveillance system that continually monitors, documents, and corrects deficiencies in processes and procedures. When requested, the Contractor shall allow the Government access to their QA program documents and processes.
3.4.2 The Contractor shall submit a Quality Control Plan. (CDRL A025)
3.4.3 The Contractor Quality Organization shall provide support of requirement peer reviews, monitoring of activities to ensure processes are being followed, review of products generated (e.g., System Change Description) and support of meetings (staff, program status, Technical Interchange, etc.) to ensure compliance with established Contractor quality standards.
Revision 1 (02 February 2015)
3.4.4 Contracting Officer Representative (COR): The Program Office COR(s) will review and approve Contractor submitted metrics and deliverables for purposes of billing and acceptance. Program Office CORs must receive and concur with Contractor-submitted metrics prior to DCMA acceptance of invoices in Wide Area Work Flow (WAWF).
3.4.5 The Contractor will be notified by letter upon contract award of the Primary and Alternate CORs assigned to this contract.
3.5 Corrosion Prevention and Management
3.5.1 Using MIL-STD-1568C (Dated 12 August 2014) as a guide, develop a Corrosion
Prevention and Control Management Plan. (CDRL A034)
3.5.2 Identify production manufacturer and repair facility corrosion prevention and control procedures. (AC 43.206 - Inspection, Prevention, Control, and Repair of Corrosion on Avionics Equipment or equivalent)
3.6 Configuration Management
3.6.1 Using MIL-HDBK-61A(SE)(Dated 7 February 2001) and MIL-STD-3046 for guidance, the
Contractor shall develop, implement and maintain a Configuration Management Plan (CMP) that describes how the T-38C configuration documentation is to be maintained during the Contract Period of Performance (PoP) (CDRL A006). The plan shall describe the processes to:
A. Maintain the existing configuration identification B. Establish configuration control to evaluate proposed engineering changes and determine affected items and means of approval
1. The Contractor shall perform a Physical Configuration Audit (PCA) to ensure the design matches the specifications of the equipment being delivered to the Government.
2. The Contractor shall perform a Functional Configuration Audit (FCA) to ensure that the equipment being delivered to the Government meets the documented performance specifications and meets or exceeds the performance specifications specified in the T-38C System Performance Specification.
C. Provide updates to Technical Orders/Technical Manuals in accordance with TM-86- 01N, Attachment 9 of this proposal (CDRL A029)
D. Provide updates to engineering drawings (CDRL A033) E. Provide change documentation and update the Technical Data Package (TDP) as required for this effort. The TDP is defined in Section 15 of this document. (CDRL A029)
F. Provide for and deliver to the Government the necessary Configuration Status accounting documents (CDRL A037)
3.6.2 The Contractor shall ensure suppliers maintain configuration control in accordance with the Contractor developed Configuration Management Plan and as outlined in the Engineering Change Proposal.
Revision 1 (02 February 2015)
3.7 Risk Management
3.7.1 The Contractor shall develop the criteria, methods, and procedures used for identifying critical risks associated with the implementation of this Contract. Using the latest Department of Defense (DoD) Risk Management Guide as reference, the Contractor shall implement a risk management process and provide a Risk Management Plan (RMP) that efficiently identifies, analyzes, mitigates, and tracks potential impacts to mission success.
3.7.2 The Contractor shall develop, implement, and maintain a RMP using AFI 63-101/20-101 (Dated 7 March 2013 Incorporating Change 1, 21 March 2014), AFMCI 63-1201 (Dated 14 October 2009 Incorporating Through Change 3, 26 July 2012) and AFPAM 63-128 (Dated 10 July 2014) as guidance. The RMP will be delivered to and approved by the Government. (CDRL A002)
3.7.3 The Contractor’s RMP shall identify risk, assess or analyze risk and implement procedures to reduce or eliminate risk to achieve program goals.
3.7.4 The Contractor’s RMP shall be implemented by Integrated Product Teams and managed as part of systems engineering/program management processes.
3.7.5 The Contractor shall provide on-going identification, analysis, abatement, and risk tracking.
3.7.6 The Contractor shall maintain a system risk summary and provide regular status reporting of key risk areas to the Government Program Manager.
3.8 Software Management
3.8.1 The Contractor shall design, fabricate, integrate, test, and evaluate the hardware, software, facilities, personnel subsystems, training, and the principle items necessary to satisfy program requirements, and to support and operate the system. This includes the requirements analysis, design, coding and unit testing, component integration and testing, and Computer Software Configuration Item (CSCI) level testing for software. This also includes system development and operational test and evaluation, software quality, configuration management, and support for software.
3.8.2 The Contractor shall develop and maintain a Software Management Plan. (CDRL A021)
Revision 1 (02 February 2015)
3.9 COMMERCIAL SMALL BUSINESS INVOLVEMENT
3.9.1 The contractor shall be required to make a best effort to meet small business subcontracting goals to include Small Businesses (SB), Veteran-Owned Small Business (VOSB), Service Disabled Veteran-Owned Small Business (SDVOSB), HUBZone Small Business (HUBZone), Small Disadvantaged Business (SDB), and with Women Owned Small Business (WOSB). The Small Business Subcontracting Requirements clause will require the contractor to make a best effort to meet an overall minimum small business subcontracting goal. The contractor will also be encouraged to meet and/or exceed goals for each socioeconomic category stated in the clause. A Small Business Subcontracting Plan will be required in accordance with Federal Acquisition Regulation (FAR) 52-219-9, Small Business Subcontracting Plan.
3.9.2 DoD Implementation of Electronic Subcontracting Reporting System (eSRS) requires that Clause 52.219-9 (Jul 2013 and DoD Deviation Aug 2013) is inserted in all solicitations and contracts that require subcontracting plans. The Air Force requires contractors to use eSRS to input subcontracting reports. The SF 294/295 will no longer be used to report subcontracting activities to the ACO or contract administrator. Training publication and webinars on eSRS use well as eSRS registration is located at the following link:
http://www.esrs.gov/
4 Automatic Dependent Surveillance – Broadcast (ADS-B) Proposal (CLIN X003 AA)
4.1 ECP Content
4.1.1 The ECP shall be Firm Fixed Price (FFP).
4.1.2 The Contractor shall conduct necessary system and design reviews and provide meeting minutes within five working days (CDRL A017). The minimum requirements are:
A. Systems Requirements Review (SRR) B. Preliminary Design Review (PDR) C. Critical Design Review (CDR) D. Test Readiness Review (TRR) E. Production Readiness Review (PRR)
4.1.3 The ECP shall contain an Integrated Master Schedule (IMS) to encompass all Government/Contractor interrelationships. (CDRL A001)
A. The IMS shall integrate the tasks of all Government stakeholders and the Contractor’s teams.
B. The IMS shall use critical path methodology to define and emphasize the program’s critical elements.
C. The IMS shall contain all control points (milestones) and all requirements for reviews, audits, and meetings required by this SOO.
http://www.esrs.gov/
Revision 1 (02 February 2015)
4.1.4 The ECP shall provide a detail system design and include integration into the current T- 38C avionics system.
4.1.5 The ECP shall identify all hardware components by manufacturer, manufacturer source/cage code, manufacturer part number, quantity and nomenclature.
4.1.6 Software items required to integrate and test the solution shall be identified by developer, developer source/cage code, title, and version identification number. All software executable code, source code (including developer notes) shall be delivered with Unlimited Rights to the Government. (CDRL A005)
4.1.7 The ECP shall Identify and define any environmental qualification testing that may be required to include additional testing that may be required for Commercial Off-The- Shelf (COTS) or Non-Developmental Items (NDI) that do not meet the T-38C specifications.
4.1.8 The contractor shall develop the overall ESOH risk management approach for the ADS-B system as part of the Systems Engineering (SE) Process per MIL-STD-882E (Dated 11 May 2012) and National Environmental Policy Act (NEPA).
4.1.9 The Contractor shall perform weight and balance computations of proposed configurations and provide the results to the Government program office and Government engineering for determination and approval.
4.1.10 The Contractor shall provide drawing and Technical Order (TO) changes for all TOs affected by the aircraft system changes. The contactor shall comply with TM-86-01N, Air Force Technical Manual Contract Requirements (TMCR). The Contractor shall:
A. Provide mark-ups in accordance with TM-86-01N for all TOs and aircrew flight manuals affected by the aircraft system changes. (CDRL A029)
B. Provide all required changes to the Technical Manuals and installation drawings.
(CDRL A033)
C. Prepare and deliver a Time Compliant Technical Order (TCTO) for the installation of the ADS-B system into the T-38C (CDRL A029)
4.1.11 The Contractor shall provide information and technical support during development of the Technical Engineering Review Board (TERB) and Configuration Control Board (CCB) documentation and provide telephone support during these meetings.
4.2 System Requirements
4.2.1 The Contractor shall design and develop a hardware and/or software solution to provide
ADS-B Out capability in accordance with the requirements of 14 CFR § 91.227 and TSO- C166.
4.2.2 The Contractor shall complete all integration and test activities required to modify aircraft and associated support equipment.
Revision 1 (02 February 2015)
4.2.3 The Contractor shall ensure that equipment installed on aircraft as a result of this modification meets the antenna and power output requirements of Class A1, A1S, A2, A3, B1S, or B1 equipment as defined in TSO–C166.
4.2.4 The Contractor shall ensure that modified aircraft meet the following performance requirements for Navigation Accuracy Category for Position (NACP), Navigation Accuracy Category for Velocity (NACV), Navigation Integrity Category (NIC), System Design Assurance (SDA), and Source Integrity Level (SIL) as defined in TSO-C166:
1. The aircraft's NACP must be less than 0.05 nautical miles.
2. The aircraft's NACV must be less than 10 meters per second.
3. The aircraft's NIC must be less than 0.2 nautical miles.
4. The aircraft's SDA must be 2.
5. The aircraft's SIL must be 3.
6. Changes in NACP, NACV, SDA, and SIL must be broadcast within 10 seconds.
7. Changes in NIC must be broadcast within 12 seconds.
4.2.5 Modified aircraft must be capable of broadcasting the following information, as defined in TSO–C166. The message elements defined in paragraphs 4.2.5 items 7 through 10 and shall be enterable inputs during the appropriate phase of flight.
1. Length and width of the aircraft
2. An indication of the aircraft's latitude and longitude
3. An indication of the aircraft's barometric pressure altitude
4. An indication of the aircraft's velocity
5. An indication that TCAS II is installed and operating in a mode that can generate resolution advisory alerts
6. An indication if a resolution advisory is in effect
7. An indication of the Mode 3/A transponder code specified by Air Traffic Control
(ATC)
8. An indication of the aircraft's call sign that is submitted on the flight plan, or the aircraft's registration number
9. An indication if the flight crew has identified an emergency, radio communication failure, or unlawful interference
10. An indication of the aircraft's “IDENT” to ATC
11. An indication of the aircraft assigned International Civil Aviation Organization (ICAO)
24-bit address
12. An indication of the aircraft's emitter category
13. An indication of whether an ADS–B In capability is installed
14. An indication of the aircraft's geometric altitude
15. An indication of the NACP;
16. An indication of the NACV;
17. An indication of the NIC;
18. An indication of the SDA
19. An indication of the SIL
Revision 1 (02 February 2015)
4.2.6 Modified aircraft shall meet the following latency requirements:
1. The aircraft must transmit its geometric position no later than 2.0 seconds from the time of measurement of the position to the time of transmission.
2. Within the 2.0 total latency allocation, a maximum of 0.6 seconds can be uncompensated latency. The aircraft must compensate for any latency above 0.6 seconds up to the maximum 2.0 seconds total by extrapolating the geometric position to the time of message transmission.
3. The aircraft must transmit its position and velocity at least once per second while airborne or while moving on the airport surface.
4. The aircraft must transmit its position at least once every 5 seconds while stationary on the airport surface.
4.2.7 The Contractor shall ensure that the ADS-B Out modification has minimal impact to current configuration and no interference with current aircraft capabilities.
4.2.8 The offeror shall provide schedule timelines for design, development, and integration testing activities and the optional task of aircraft modification to ensure full operational capability (FOC) by 1 January 2020. The proposed dates cannot be earlier than 1 October 2015 due to Government funding procedures. Proposed development/integration timeline must allow sufficient time for fleet retrofit, whether Government or Contractor install, in order to meet the January 2020 operational need date.
5 Test and Test Support Activities (CLIN X003 AA)
5.1 System Test and Integration
5.1.1 All performance/environmental test results shall meet or exceed current T-38C
Performance Specifications. Test reports shall be delivered to the Government Program Office. (CDRL A036)
5.1.2 The developed system and all proposed replacement equipment shall meet or exceed the Mean Time Between Failure (MTBF) rate(s) identified in the Form-Fit-Function & Interface Specification. (e.g. Mode S Transponder vs. ADS-B capable Mode S Transponder)
5.1.3 The Contractor shall identify requirements for any additional test or support equipment and deliver requirements to the Government. (CDRL A038)
5.1.4 The Contractor shall install and evaluate the ADS-B system for proper fit in the aircraft.
5.1.5 The ADS-B system installation procedures and hardware configurations shall comply with USAF aircraft hardware and maintenance practices. Reference: 1-1A-XX series Technical Manuals.
5.1.6 The Contractor shall develop new or adapt existing Acceptance Test Procedures (ATP) for the ADS-B system components/LRUs. (CDRL A036) The Government will provide current system test procedures.
Revision 1 (02 February 2015)
5.1.7 Using the Systems Integration Lab (SIL), the Contractor shall perform the T-38C Avionics ATP for the ADS-B system equipment and deliver the resulting test report to the Government. (CDRL A036)
5.2 Developmental Test (DT and Force Development Evaluation (FDE)
5.2.1 The Contractor shall prepare and deliver a pre-DT release letter and configuration memo. (CDRL A015)
5.2.2 The Contractor shall provide inputs to the test team at Edwards AFB to aid in development of the DT test plan.
5.2.3 The Contractor shall install and evaluate the ADS-B system for proper fit in the aircraft.
5.2.4 The Contractor shall perform on-aircraft ground operational checkout in accordance with the current T.O. 1T-38C-2-12 procedures or newly developed procedures as required.
5.2.5 The Contractor shall perform on-aircraft Electromagnetic Compatibility/Interference (EMC/EMI) Safety of Flight (SOF) testing and deliver the test report to the Government.
(CDRL A036)
5.2.6 The Contractor shall provide engineering support during DT flight tests at Edwards AFB.
5.2.7 The Contractor shall prepare and deliver a pre- Force Development Evaluation (FDE) release letter and configuration memo.
5.2.8 The Contractor shall assist the test team at Randolph AFB in the development of the FDE test plan.
5.2.9 The Contractor shall provide engineering support during FDE at Randolph AFB.
5.2.10 The Contractor shall support all Government system test review boards, as required.
6 Certifications and Approvals (CLIN X003 AA)
6.1 Authority to Test and Authority to Operate
The Contractor shall develop and coordinate the documents below with the T-38 Systems Program Office (SPO) and other government agencies to ensure systems(s) receive Authority to Test (ATT) and Authority to Operate (ATO). (CDRL A029) Table 6-1 Minimum Documents Required for ATT/ATO
Document Purpose Time Compliance Technical Order Installation instruction and required support Program Introduction Document Test organization requirements and objectives e.g.
instrumentation requirements, data analysis plan Deficiency Reports Make the test organization aware of potential issues to assign risk Suggested Flight Test Plans for all phases of testing (DT, FDE)
Test techniques, test points, limitations, and management information
Revision 1 (02 February 2015)
6.2 Platform Information Assurance
The Contractor shall provide information and technical support during the development of the update to USAF Platform Information Technology (PIT), Architecture Analysis Report (AAR), Security Requirements Tailored Matrix (SRTM) and Risk Analysis for the T- 38C Talon. (CDRL A039)
6.3 Airworthiness
6.3.1 The Contractor shall provide support for airworthiness risk assessment activities.
6.3.2 The Contractor shall comply with all relevant Airworthiness requirements cited in MIL- HDBK-516C (Dated 12 December 2014) and provide documentation of compliance to the Government and assist with the following processes or approvals: (CDRL A040)
A. Impact Assessment B. Modified Airworthiness Certification Criteria (CDRL A041) C. Risk Assessment D. System Program Office Engineering and T-38 Chief Engineer approval E. Air Force Material Command, Director of Engineering Approval
6.4 CNS-ATM
6.4.1 The contractor shall provide technical assistance and act as the T-38C Subject Matter
Expert (SME) for all CNS/ATM compliance requirements. The contractor is responsible for all processes and administration to support the Government in obtaining a CNS/ATM Type 2 Data Chain Letter of Acceptance (LOA), RNAV, VNAV & RNP Letter of Compliance (LoC) and all applicable certifications required for any JMPS and OFP software development, sustainment efforts, fielding and operation (Reference AFI63-137, RTCA/DO-200A, 201A & FAA AC 20-153).
6.4.2 The contractor shall maintain and update as required for certification currency all T-38C CNS/ATM documentation throughout the period of performance in accordance with AFI63-137. At a minimum, CNS/ATM documentation consists of the following: (CDRL A015)
A. T-38C Data Quality Requirements (DQR) B. T-38C Navigation Data Chain Architecture C. T-38C Navigation Data Chain Compliance Plan D. T-38C Tailored RNAV Matrix E. T-38C Tailored VNAV Matrix F. T-38C Tailored RNP Matrix G. T-38C Generic ADS-B Matrix
Revision 1 (02 February 2015)
7 Formalize Change after Successful Test (CLIN X003 AA)
7.1 Finalize configuration and Release Documents
7.1.1 The Contractor shall prepare release documents for Government approval.
7.1.2 The Contractor shall deliver final drawings and final TCTO(s) requirements.
7.1.3 The Contractor shall acquire final release approval from the Government.
7.1.4 The Contractor shall provide all final system documentation and deliverables to the government.
8 Hardware and Production and Delivery The contractor shall provide the necessary Kits/materials to modify 456 aircraft. Delivery location(s) shall be determined based on the developed ADS-B solution and shall coincide with the Material Fielding and Basing Plan. The Contractor shall deliver a list of all procurable hardware to include: (CDRL A042)
8.1 A-Kits - Aircraft Modification Kit (CLIN X003 AB)
8.1.1 Package and deliver 456 A-Kits. A-Kits will include all components and hardware required to modify the T-38C aircraft to accept the new ADS-B system.
8.2 B-Kits – System LRUs (CLIN X003 AC)
8.2.1 Package and deliver 456 B-Kits. B-Kits will include ADS-B system LRU components
(Packaged Separately).
8.3 Production Schedule
8.3.1 The Contractor shall provide a projected schedule for kit production and delivery assuming quantities sufficient to modify 456 T-38C aircraft. The schedule should highlight ramp up periods and maximum monthly deliveries once full rate production is achieved.
8.3.2 The Contractor shall provide a Material Fielding and Basing Plan. (CDRL A010)
8.4 Packaging
8.4.1 The contractor shall be responsible for the preservation, packaging, marking and shipping of all items to be delivered under the terms of this SOO to include kits, LRUs, components and hardware. The contractor shall follow packaging requirements listed in Section D of the contract and listed on AFMC Form 158 (Section J, Attachment 14 of the contract) to ensure all items arrive at the destination in an undamaged condition. The contractor shall also comply with ASTM D3951-10 (2010) and MIL-STD-129R (Dated 18 February 2014) for packaging and marking of commercial packaging. The contractor shall provide packaging data for new equipment or for modified equipment when the packaging data has changed. The contractor shall ensure packaging data identifies ESD sensitive items and assemblies as defined in MIL-STD-1686C (Dated 25 October 1995)
Revision 1 (02 February 2015) and hazardous materials per Code of Federal Regulations (CFR) 49. Shipments of classified/sensitive material or equipment shall be handled, transported, transmitted and protected IAW the National Industrial Security Program Operating Manual, DoD 5220.22M (Dated 28 February 2006 incorporating change 1 dated 28 March 2013).
The contractor shall ensure kits, LRUs, components and hardware can be shipped by the appropriate modes of transportation. All items shall be shipped according to the transportation provisions and clauses in Section F of the contract and given on DD Form 1653 (Section J, Attachment 15 of the contract).The contractor shall provide transportation data for new items or for modified items IAW FAR 52.247-53. The contractor shall identify and manage any items requiring special handling and/or movement procedures which may include hazardous, classified/ sensitive, oversize/outsize, or electrostatic sensitive device items, items requiring demilitarization, or precious metals. The contractor shall ensure shipped items are protected from the hazards of handling equipment and shall be transportable IAW MIL-STD-1366E (Dated 31 October 2006).
8.5 Contract Field Team (CLIN X003 AD)
8.5.1 8.5.1 This is an optional requirement to be exercised at Government discretion and the installation timeframe is not depicted in nor included in the requirements of paragraph 2.2.
8.5.2 The Contract shall provide a proposal for system installation by a contractor provided contract field team.
8.5.3 The proposal shall be a Firm-Fixed-Price for a single team to retrofit the aircraft by operating location and should coincide with the Material Fielding Plan. Once an operating location is completed the team will move to the next location. For estimating purposes use table 8-1 for the operating locations and installations shall be completed within 72 months of executing the development CLIN.
Table 8-1 T-38C Aircraft locations
Operating Locations
(July 2014)
Command
*Assigned Aircraft
COMBS
Columbus AFB, MS AETC 87 YES Laughlin AFB, TX AETC 65 YES Randolph AFB, TX AETC 90 YES Sheppard AFB, TX AETC 123 YES Vance AFB, OK AETC 66 YES Holloman AFB, NM AFMC 4 NO Edwards AFB, CA AFMC 11 NO Patuxent River, MD USN 10 NO
∗ Number of aircraft may change due to unforeseen circumstances
Revision 1 (02 February 2015)
9 Diminishing Manufacturing and Material Shortages
(DMSMS) (CLIN X003 AE)
9.1 DMSMS Management
9.1.1 The Contractor shall acquire and deliver the ADS-B system Bill of Materials (BOM).
(CDRL A035)
9.1.2 The Contractor shall ensure all BOM information is entered into the Government and Industry Data Exchange Program (GIDEP).
9.1.3 The Contractor shall develop and submit a DMSMS Management Plan for managing the potential loss of manufacturers or supplier(s) of parts and/or material required for performance of this SOO. At a minimum, the plan shall address the following: (CDRL A008)
A. Means and approach for providing the Government with information regarding obsolescence and DMSMS issues
B. Planned resolution of discovered DMSMS issues C. Parts list screening D. Parts list monitoring E. Communication with and availability of information to the Government F. Means and approach for establishing obsolescence and DMSMS solutions G. Process for data entry and extraction from predictive tools used. GIDEP shall be used and is the minimum requirement.
9.2 DMSMS Reporting
9.2.1 The Contractor shall prepare and submit to the Government a report upon discovery or notification of any obsolescence issues affecting components utilized in the replacement ADS-B system. (CDRL A007)
9.2.2 The Contractor shall continue to update the report provided in paragraph 9.2.1 until the issue is successfully mitigated. (Successfully mitigated is defined as “no impact to the Government or future supportability of the ADS-B system”.)
9.3 DMSMS Mitigation
9.3.1 The Contractor shall be responsible for the costs of investigating part availability, inter-changeability and substitutability, locating part replacement, vendor interface, engineering efforts, testing requirements, drawing changes, and all other actions associated with this SOO/ECP.
9.3.2 During the period of performance the Contractor shall prevent any additional costs from being incurred by the Government due to obsolescence.
Revision 1 (02 February 2015)
10 Government Furnished Equipment (CLIN X003 AE)
10.1 Systems Integration Lab (SIL)
10.1.1 The Contractor shall have use of the T-38C Systems Integration Lab (SIL), located at the
Boeing St. Louis facility. The use shall be on a non-interference basis and shall be scheduled in advance to preclude schedule and performance conflicts.
10.1.2 Location of SIL:
The Boeing Company 5890 N. Lindbergh Blvd.
Hazelwood, MO 63402
If necessary, the SIL will begin transfer to the non-incumbent facility approximately January 2017.
10.1.3 Current T-38C avionics system Acceptance Test Procedures will be provided by the Government to the awardee.
11 Associate Contractor Agreement Offeror shall enter into Associate Contractor Agreement (ACA) in the accomplishment of this requirement. The agreement shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the accomplishment of the AvCI Program Task Orders which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract. (In accordance with Clause H040 of the basic AvCI contract)
12 Conditions and Assumptions Preliminary Test (PT), and Developmental Test (DT) will be conducted at Edwards AFB, CA.
The Government will provide aircraft, pilots, fuel, and facilities during the test period.
FDE will be conducted at Randolph AFB, TX. The Government will provide aircraft, pilots, fuel, and facilities during the test period.
Revision 1 (02 February 2015)
13 Reference Documents The Contractor’s shall be familiar with and use the following documents for reference when executing the requirements within this document.
13.1 T-38C Performance Requirements
• T-38C System Performance Specification, Revision H, dated 14 Feb 2011.
13.2 Department of Defense Instructions
• DoDI 8510.01, Risk Management Framework (RMF) for DoD Information
Technology (IT) (DIACAP)
• DoD Directive 4715.1E – Environment, Safety, and Occupational Health
13.3 Air Force Instructions
• AFI 33-200, IA Management
• AFI 33-210, Air Force Certification and Accreditation (C&A) Program (AFCAP)
• AFI 62-601, MIL-HDBK-516B, and AW Bulletins: USAF Airworthiness
• AFPD 62-6, USAF Airworthiness
• AFI 63-101, Acquisition and Sustainment Life Cycle Management
• AFI 63-131, Modification Management
• AFI 63-137, Assurance of Communications, Navigation, Surveillance/Air Traffic
Management (CNS/ATM) Navigation Safety, and Next Generation Air Transportation System (NEXGEN) Performance.
• AFMCI 63-1201, Implementing Operational Safety, Suitability, and Effectiveness (OSS&E) and Life Cycle Systems Engineering
13.4 Air Force Manuals & Pamphlets
• AFM 36-2234, Instructional Systems Development, Courseware Development
Standards HQ AETC/A3F
• AFMAN 63-119, Certification of System Readiness for Dedicated Operational
Testing
13.5 Military Standards and Specifications
• MIL-STD-129R, Military Marking for Shipment and Storage
• MIL-STD-882, Department Of Defense Standard Practice for System Safety
• MIL-STD-411, Aircrew Station Alerting Systems
• MIL-STD-461, Requirements for the Control of Electromagnetic Interference
Characteristics of Subsystems and Equipment
• MIL-STD-464, Electromagnetic Environmental Effects Requirements for Systems
• MIL-STD-704, Aircraft Electric Power Characteristics
• MIL-STD-1366E, Interface Standard for Transportability Criteria
• MIL-STD-1472, Human Engineering
Revision 1 (02 February 2015)
• MIL-STD-1686C, Electrostatic Discharge Control Program For Protection Of Electrical And Electronic Parts, Assemblies And Equipment (Excluding Electrically Initiated Explosive Devices).
• MIL-STD-1787, Aircraft Display Symbology
• MIL-STD-2073-1E, Standard Practice for Military Packaging
• MIL-DTL-5096, Manuals, Technical: Inspection and Maintenance Requirements;
Acceptance and Functional Check Flight Procedures and Checklists; Inspection Work Cards; and Checklists; Preparation of
• MIL-DTL-38804, Time Compliance Technical Order Specification
• MIL-DTL-38807, Technical Manuals - Illustrated Parts Breakdown
• MIL-STD-38784, Standard Practice for Manuals, Technical: General Style and Format
Requirements
• AFGS-87219B, Electrical Power Systems, Aircraft
• AFGS-87256, Integrated Diagnostics
13.6 Military Handbooks
• MIL-HDBK-516, Airworthiness Certification Criteria
• MIL-HDBK-419A, Grounding, Bonding, and Shielding for Electronic Equipment and
Facilities, Volume 1 & 2 (Attachment 15)
• MIL-HDBK-454B, General Guidelines for Electronic Equipment (Attachment 16)
• The Contractor should contact the government if they have difficulty in locating any of the above listed documents.
• MIL-DTL-5920G, Manuals, Technical: Sample Basic Weight Checklists And Loading
Data (Attachment 6)
• MIL-DTL-5096G, Manuals, Technical: Inspection and Maintenance Requirements;
Acceptance and Functional Check Flight Procedures and Checklists, Inspection Work Cards, and Checklists, Preparation of
13.7 Civilian Aviation Directives
• AS 9100C, Quality Management Systems - Requirements for Aviation, Space and
Defense Organizations
• AS 9110, Quality Maintenance Systems – Aerospace – Requirements for
Maintenance Organizations
• Federal Aviation Administration Advisory Circular, AC 20-153A, Acceptance of Aero Data Processes and Associated Databases
• Radio Technical Commission for Aeronautics, RTCA/DO-200A, Standard for Processing Aeronautical Data and AC 20-153A, Acceptance of Aeronautical Data Processes and Associated Databases
• Federal Aviation Administration Technical Standard Order, TSO-C166, Extended Squitter Automatic Dependent Surveillance – Broadcast (ADS–B) and Traffic Information Service – Broadcast (TIS–B) Equipment Operating on the Radio Frequency of 1090 Megahertz (MHz)
Revision 1 (02 February 2015)
14 Deliverables:
CDRL
Short Name
Full Name Paragraph DID
A001 IMS Integrated Program Management Report (IPMR)
3.2.2, 4.1.3 DI-MGMT-81861
A002 RMP Contractor’s Risk Management Plan 3.7.2 DI-MGMT-81808
A003 Status Report Contractor’s Progress, Status and Management Report
3.2.5 DI-MGMT-80227
A004 Report Manhour Estimate, Technical Cost Proposals
DI-FNCL-81116
A005 Software Applications Computer Software Product End Items
4.1.6 DI-MCCR-80700
A006 CMP Contractor’s Configuration Management Plan
3.6.1 DI-CMAN-80858B
A007 Obsolescence Report Progress Report (Studies) 9.2.1 DI-ADMN-81313A A008 DMSMS Management
Plan Diminishing Material Shortages and Material Management Plan
9.1.3 DI-MGMT-81949
A009 Engineering Analysis Human Engineering System Analysis Report
DI-HFAC-80745B
A010 Field Material and Basing Plan
Management Plan 8.3.2 DI-MGMT-80004A
A011 CAP Corrective Action Plan DI-RELI-80254
A012 Database Database Design Description (DBDD) DI-IPSC-81437A
A013 Analysis Producibility Analysis Report DI-MGMT-80797
A014 ECP Engineering Change Proposal (ECP) 3.2.1 DI-CMAN-80639C
A015 Evaluation Primary Flight Reference Endorsement Package
Technical Report-Study/Services 5.2.1, 6.4.2 DI-MISC-80508B
A016 Block Upgrade Process Management Plan DI-MGMT-80004A
A017 Meeting Minutes and Action Items
Report, Record of Meeting/Minutes 3.2.3, 3.2.4, 4.1.2 DI-ADMN-81505
A018 System Change Description
Revisions to Existing Government Documents
DI-ADMN-80925
A019
Specification Change Notices SCN, Requirements Change Notice
Specification Change Notices (SCN) DI-CMAN-80643C
A020 AvCI Avionics Roadmap
Management Plan DI-MGMT-80004A
A021 Software Management Plan
Management Plan 3.8.2 DI-MGMT-80004A
A022 Courseware Delivery Web-Based Courseware DI-SESS-81699
A023 ATD Software Changes Computer Software Product End Items
DI-MCCR-80700
CDRL
Short Name
Full Name Paragraph DID
A024 Safety and Health Mgmt Report
Contractor's Progress, Status and Management Report
DI-MGMT-80227
A025 Quality Control Plan Management Plan 3.4.2 DI-MGMT-80004A
A026 Safety Plan Environmental Health and Safety Plan
(HSP)
DI-ENVR-81375
A027 Phase-in/out Transition Plan
Management Plan DI-MGMT-80004A
A028 Government Owned Equipment
Inventory Checklist/Record (ICL/R) DI-MISC-81191A
A029 Document Changes Document Changes
3.6.1 C, 3.6.1 E,
4.1.10 A, 4.1.10 C, 6.1
DI-MISC-80358
A030 DAL Data Accession List (DAL) DI-MGMT-81453A
A031 Property Management Plan
Management Plan DI-MGMT-80004A
A032 Safety Accident/Incident Report DI-SAFT-81563
A033 Drawings Product Drawings/Models and Associated Lists
3.6.1 D, 4.1.10 B DI-SESS-81000E
A034 Corrosion Prevention Corrosion Prevention and Control Plan
3.5.1 DI-MFFP-81403
A035 Data for Forecasting Source Data for Forecasting DMSMS 9.1.1 DI-SESS-81656
A036 ATR Acceptance Test Report (ATR) 5.1.1, 5.1.6, 5.1.7, 5.2.5
DI-QCIC-81891
A037 CSA Configuration Status Accounting Information
3.6.1 F DI-CMAN-81253A
A038 Equipment Requirements List
Maintenance Test and Support Equipment Requirements List
5.1.3 DI-SESS-80294B
A039 Sys. Architectural Analysis
DoD Architecture Framework Documentation
6.2 DI-MGMT-81644B
A040 Specifications Airworthiness Specification 6.3.2 DI-SESS-81766
A041 Airworthiness Report Airworthiness Certification Criteria Report
6.3.2 B DI-SESS-81768
A042 Procurable Hardware Provisioning Parts List Section 8 DI-SESS-81715
A043 Corrective Action Plan Contractor’s Corrective Action Plan DI-MGMT-80501
A044 50/50 Reporting 10 USC 2466 (50/50) Requirements Report
DI-MGMT-81749A
A045 Cost-Per-Flight-Hour Report
Technical Report-Study/Services DI-MISC-80508B
Revision 1 (02 February 2015)
15 Technical Data Package (TDP)
1. T-38C Avionics System Performance Specifications
2. T-38C ATD Performance Specifications
3. T-38C Avionics System Architecture Diagram
4. T-38C ATD Architecture Diagram
5. T-38C Air Vehicle Drawings
6. T-38C ATD Drawings
7. T-38C Form Fit Function & Interface (F3I) Specifications
8. T-38C Interface Control Documents (ICDs) T-38C Avionics Architecture Diagram
9. ATD System Interface Control Documents (ICD)
10. T-38C Avionics Upgrade Program, Electrical Loads Analysis Report
11. List of Government Furnished Equipment (GFE) at Suppliers/Vendors
12. GFE List Supplement, Equipment at L-3 DS
13. GFE List - T-38 System Integration Lab – Avionics
14. GFE List - T-38 System Integration Lab – Test Equipment
15. GFE List - T-38 System Integration Lab – Computing Equipment
16. GFE List - Equipment Planned for T-4 Engine Test Cell
17. GFE List - Training Support Equipment (Items used for Courseware support)
18. GFE TCNO Computers
19. List of Aircraft Panels in Storage at COMBS facilities
20. Group A Parts Inventory and Consumption
21. Group B Inventory and Consumption
22. GFI T-38C Air Vehicle Technical Manuals
23. List of Software Components
24. T-38C Contractor Furnished Test Equipment List
25. DMSMS Data from predictive Tools/Database
26. ACMI Parameters
27. List of MFL/PFL
28. ATD Equipment at Contractor
29. GFI T-38C ATD Technical Manuals
30. IMIS Historical Data
Revision 1 (02 February 2015)
16 Record of Revisions
DATE REVISION NUMBER PURPOSE
02 February 2015 Revision 1 Paragraph 8.5.1 and 8.5.3 have been modified to clarify optional CFT requirements.
| 1 Overview |
| 1.1 Purpose |
| 1.2 Background |
| 2 Objectives |
| 2.1 Development Concept |
| 2.2 Notional Development Schedule |
| 2.3 Key Performance Parameters |
| 2.3.1 The ADS-B system shall meet or exceed the current system specifications. Refer to the following documents. |
| 2.3.2 The solution shall integrate with the avionics system components and not compromise current system performance. All equipment shall continue to meet or exceed the current T-38C System Performance Specification. Additionally, the solution shall... |
| 3 Scope of Work (CLIN X003 AE) |
| 3.1 Administration |
| 3.1.1 The Contractor shall perform administrative functions, to include scheduling meetings, arranging facilities, providing status reports, documenting official decisions and actions assigned, and maintaining charter documents, records, and databases... |
| 3.1.2 The Contractor shall appoint a primary Point of Contact (POC) for this contract. This individual shall be the primary representative and have the Contractor’s full authority to act on matters pertaining to the performance of the services under t... |
| 3.1.3 To meet the requirements of this contract the contractor shall be required to develop and deliver information to the Government in accordance with the Contract Data Requirements List (CDRL). Where possible the contractor shall submit one CDRL t... |
| 3.1.4 All documents sited in this SOO may be available on ASSIST or other Government document repository sites. (https://assist.dla.mil/online/start/index.cfm) (http://www.e-publishing.af.mil/) (http://www.e-publishing.af.mil/otherpublishingsites.asp) |
| 3.1.5 The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Department of the Air Force via a secure data collection site. The contractor ... |
| 3.2 Program Management |
| 3.2.1 The Contractor shall develop and deliver an Engineering Change Proposal (ECP). (CDRL A014) |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .