ALSF -2 SLEP SOW 5-28-25.pdf

PART I – SECTION C

STATEMENT OF WORK

OVERVIEW

This Statement of Work (SOW) defines the requirements for the High Intensity Approach Lighting System with Sequenced Flashing Lights Service Life Extension Program (ALSF-2 SLEP) described in FAA-E-2999, Performance Specification for ALSF-2 SLEP. As stated earlier in Section B, any reference to ALSF-2 SLEP, unless explicitly stated otherwise, means the ALSF-2 SLEP system specified in FAA-E-2999, Performance Specification for ALSF-2 SLEP.

General Information

The following specifications, handbooks, standards, and drawings form a part of this SOW and are applicable to the extent specified herein. The Contractor must refer to the latest version of these documents, as of the contract award date. In the event of a conflict between this SOW and any of the applicable documents cited below, the provisions of this SOW must apply.

Amendments and Changes to the FAA-E-2999

Add to FAA-E-2999 the following requirements:

1. RCP to RMMC Interface The RCP shall interface with the Remote Maintenance Monitoring Capability (RMMC) using the serial interface described as follows:

The RICI 6000 system supports a Data Circuit Terminating Equipment (DCE) or Data Terminal Equipment (DTE) implementation of the RS232/422/530 specification. The RICI units are DCE natively but can be connected with null-modem cabling to support DTE applications. The table below details the RS-530 pinout.

RS-422/530 Pinouts Pin Signal Mnemonic Pin Signal Mnemonic 1 Frame Ground FG 2 Transmit Data TDA 14 Transmit Data TDB 3 Receive Data RDA 16 Receive Data RDB 4 Request To Send RTSA 19 Request To Send RTSB 5 Clear To Send CTSA/B 13 Clear To Send CTSB 6 Data Set Ready DSRA 22 Data Set Ready DSRB 7 Signal Ground GND 8 Carrier Detect CDA 10 Carrier Detect CDB

15 Transmit Clock TCA 12 Transmit Clock TCB 17 Receive Clock RCA 9 Receive Clock RCB

18 Local Loopback (not supported)

RS-422/530 Pinouts Pin Signal Mnemonic Pin Signal Mnemonic

20 Data Terminal Ready

DTRA 23 Data Terminal Ready

DTRB

21 Remote Loopback RL 24 External Clock EXT_CLKA 11 External Clock EXT_CLKB 25 Test Mode TM

The RCP shall provide the RMMC with the following status information when polled:

(a) System On/Off

(b) ALSF/SSALR Mode

(c) ALSF/SSALR Mode Error

(d) ATCT/MAINT Mode

(e) Approach Lights On/Off

(f) Selected Brightness

(g) Flashers On/Off

(h) Flasher Intensity

(i) Communication Fault Alarm

(j) Caution Alarm

(k) Failure Alarm

This status information shall be in accordance with the NAS-MD-790A and R-1605-1.

The following data points shall be sent from the RCP as specified below:

(LU) DATA

POINT#

(hex)

DATA POINT

DESCRIPTION MFC csc

(hex)

STATUS

DESCRIPTION

Scaling Factor

Value Range

Units of Measure

RMS Master

LU

(20) 49 ALSF/SSALR Mode *C

1 = ALSF-2

2 = SSALR

5 = ALSF-2 with Mode Error 6 = SSALR with Mode Error Not Monitored

1 1 to 6 N/A

(20) 4A MAINT/ATCT

Mode

1 = MAINT Mode 2 =ATCT Mode

3 = MDT/FTT A

4 = MDT/FTT B

5 = MPS Control A

6 = MPS

Control B Not Monitored

1 1 to 6 N/A

(20) 4B Flasher Status

0=OFF

1 =ON

Not Monitored

1 0, 1 N/A

(LU) DATA

POINT#

(hex)

DATA POINT

DESCRIPTION MFC csc

(hex)

STATUS

DESCRIPTION

Scaling Factor

Value Range

Units of Measure

(20) 4C Flasher Intensity

1 = Low 2 = Medium 3 = High Not Monitored

1 1 to 3 N/A

(20) 4D ALS Status

0=OFF

1 =ON

Not Monitored

1 0, 1 N/A

(20) 4E ALS Intensity

1 = Brightness 1 2 = Brightness 2 3 = Brightness 3 4 = Brightness 4 5 = Brightness 5 Not Monitored

1 1 to 5 N/A

(30) 2F Caution/Failure *A *a *B

41,42

Upper Hard Alarm (Failure) Upper Soft Alarm (Caution) Normal, Not Monitored

1 0 N/A

(44) 31 Communications

RCP

*A *B

41,42

Upper Hard Alarm Normal, Not Monitored

1 0 N/A

The message protocol to the RCP shall be in accordance with the following:

Message Number = 2 Length = 3 Parameters: 3 byte field Byte 1 Byte 2 Byte 3 76543210 76543210 76543210 ........ ........ .......x B5 Blinker 1 = blink ........ ........ ......x. B1 1 = light on ........ ........ .....x.. B2 1 = light on ........ ........ ....x... B3 1 = light on ........ ........ ...x.... B4 1 = light on ........ ........ ..x..... B5 1 = light on ........ ........ .x...... Maint/ATCT 1 = Maint ........ ........ x....... FAILURE 1 = Light on * ........ .......x ........ ALSF Blinker Not Used ........ ......x. ........ ALSF status 1 = on ........ .....x.. ........ Light status 1 = on ........ ....x... ........ Flasher status 1 = on ........ ...x.... ........ Audio Disable 1 = disable ........ ..x..... ........ CAUTION 1 = Light on * ........ .x...... ........ B4 Blinker 1 = on ........ x....... ........ Mode Error 1 = error .......x ........ ........ Buzzer 1 1 = .1 sec beep ......x. ........ ........ Buzzer 2 1 = .2 sec beep .....x.. ........ ........ Buzzer 3 1 = .33 on .67 off ....x... ........ ........ Buzzer 4 1 = cont double beep ...x.... ........ ........ Maint Blinker 1 = blinking ..x..... ........ ........ B3 Blinker 1 = on

.x...... ........ ........ B2 Blinker 1 = on x....... ........ ........ B1 Blinker 1 = on

2049 Byte 2:1(ALSF = 1, SSALR = 0)and Byte 2:7 (Mode Error = 1) 204A Byte 1:6 (ATCT = 1, MAINT = 0) 204B Byte 2:3 (ON = 1, OFF = 0) 204C Byte 3:0-5 and 2:6 (LOW = Byte 3:1 or 3:2, MED = Byte 3:3, HIGH = Byte 3:4 or 2:6 or 3:0 or 3:5) 204D Byte 2:2 (ON = 1, OFF = 0) 204E Byte 3:0-5 and 2:6 (B1 = Byte 3:1, B2 = Byte 3:2, B3 = Byte 3:3, B4 = Byte 3:4 or 2:6, B5 – Byte 3:0 or 3:5) 302F Byte 2:5 (CAUTION = 1) or 3:7 (FAILURE = 1) 4431 No data transmitted from CM after 10 seconds (COMM FAULT)

2. RCP to RMMC Interface Block Diagram

3. RCP Response Procedures

• The RCP shall respond to the RMMC with status information when polled.

• Communication between the RCP and the Control and Monitoring (CM) Cabinet shall take precedence over the required status response to RMMC polling.

• The RCP shall accept polling from the RMMC up to a maximum of one (1) poll per one second.

• If the polling signals exceed three (3) per one second, the RCP shall only respond to the first polling request from the RMMC.

4. Recovery Time In the event of a loss of power, the RCP and CM Cabinet shall recover within less than six seconds once the power has been restored.

5. RMMC Failures The failure of the RMMC shall not affect the operation of the RCP.

6. RCP/RMMC Testing Requirements

• All added requirements shall be implemented and tested in accordance with the SOW and Section C.3.6, Test and Evaluation (T&E).

• The FAA will test the RCP to RMMC interface during Operational Test (OT).

• The RCP to RMMC interface shall be tested during the 24-hour Test conducted as part of Production Acceptance Test (PAT).

• The RCP to RMMC interface shall be tested during Site Acceptance Test (SAT).

Applicable Documents Federal Aviation Administration (FAA) Documents

FAA-STD-002 Standard Engineering Drawing Preparation and Support FAA-STD-026 Software Development for the National Airspace System, (NAS) FAAD-STD-1293 Servicing Standards and Test Requirements for Ground Electronic

Equipment

FAA-D-2494

FAA-E-2689a

Technical Instruction Book Manuscript: Electronic, Electrical, and Mechanical Equipment, Requirements for Preparation of Manuscript and Production of Books Dual Mode High Intensity Approach Lighting System (ALSF- 2/SSALR), Notice 6

FAA-E-2999 High Intensity Approach Lighting System With Sequenced Flashing Lights (ALSF-2) Service Life Extension Program (SLEP) Requirements

TI 6850.56

TI 6850.69

TI 6850.94

TI 6850.101

TI 6850.111

NAS-IC-33130001

NAS-MD-790A

R-1605 D-6131 D-6138

Type FA-9993, Dual Mode High Intensity Approach Light System Type FA-10048, Dual Mode High Intensity Approach Light System 2400 Volt 50 KW Constant Current Regulator (CCR) Replacement Lamp Monitoring System (RLMS) Low Voltage Individual Control Cabinet (400VDC Flasher Light Assembly) Low Voltage Individual Control Cabinet (LVICC) Interface Control Document (ICD) Remote Maintenance Monitoring System Interface Control Document ALSF RMS/MPS Interface Control Document ALSF-2 Installation Drawings for Godfrey ALSF-2 Installation Drawings for Airflo

VSPT-E5-GDE-017 FAA William J. Hughes Technical Center, T&E Content and Format Guidance Document, v3.0

Military Standards/Handbooks

MIL-HDBK-61 Configuration Management Guidance MIL-HDBK-217 Reliability Prediction of Electronic Equipment MIL-HDBK-470 Designing and Developing Maintainable Products and Systems MIL-HDBK-472 Maintainability Prediction MIL-HDBK-781 Handbook for Reliability Test Methods, Plans, and Environments for

Engineering, Development Qualification, and Production MIL-HDBK-881 Work Breakdown Structure MIL-STD-129 Military Marking for Shipment and Storage MIL-STD-2073-1 Standard Practice for Military Packaging MIL-STD-31000 Technical Data Packages

Other Documents

SAE ANSI/EIA-649 National Consensus Standard for Configuration Management AS9100D Quality Management Systems - Requirements for Aviation, Space, and Defense Organizations ASTM-D-3951 Standards and Practices for Commercial Packaging

OSHA 29 CFR 1910

SUN2014, Rev 2.4 SUN2850, Rev 1.3 SUN2569, Rev 2.0

Occupational Safety and Health Administration Standards RICI 6000 Hardware Users Guide Ventnor Concentrator/RICI 6000 Gateway User’s Guide LITE Software Suite User Manual

Copies of Documents

Copies of FAA specifications, standards, publications, drawings and interface documents may be obtained from the Federal Aviation Administration Regulations and Policies website at http://www.faa.gov/regulations_policies/ or the U.S. Department of Transportation (DOT) Publications Library at http://isddc.dot.gov/.

Military standards and specifications may be ordered from the Department of Defense Single Stock Point (DoDSSP) through the website http://quicksearch.dla.mil.

Copies of federal publications may be obtained from the U. S. Government Printing Office through the website http://bookstore.gpo.gov/.

American National Standards Institute (ANSI) and International Organization for Standardization (ISO) documents may be obtained through the website http://www.ansi.org.

The Acquisition Management System Test and Evaluation Process Guidelines is available for download from the FAA Acquisition System Toolset (FAST) website at https://fast.faa.gov/docs/teguidelines.docx http://www.faa.gov/regulations_policies/ http://isddc.dot.gov/ http://quicksearch.dla.mil/ http://bookstore.gpo.gov/ http://www.ansi.org/

Electronic copies of Occupational Safety and Health Administration (OSHA) and other Code of Federal Regulations (CFR) documents may be found at https://www.osha.gov/html/a-z-index.html.

Requests for copies of FAA documents not covered in the preceding paragraphs should be addressed to the ALSF-2 SLEP Contracting Officer (CO). Requests should fully identify material desired and cite the solicitation or contract number.

Acronyms

Acronym Definition

ALSF-2 SLEP

AMS

Acquisition Management System

ANSI American National Standards Institute ARP Aerospace Recommended Practice ASIC Application Specific Integrated Circuit ASQ American Society for Quality ASTM American Society for Testing and Materials ATE Automated Test Equipment ATO Air Traffic Organization BIT Built-In Test CAGE Commercial and Government Entity CASE Computer-Aided Software Engineering CCA Circuit Card Assembly CDR Critical Design Review CDRL Contract Data Requirements List CFR Code of Federal Regulations CI Configuration Item CLIN Contract Line Item Number CM Configuration Management CMP Configuration Management Plan CMTP Contractor’s Master Test Plan CO Contracting Officer COR Contracting Officer’s Representative COTS Commercial Off-The-Shelf CSAR Configuration Status Accounting Report CSCI Computer Software Configuration Item DAC Days After Contract (award) DID Data Item Description DMTP Depot Maintenance Transition Plan DoDSSP Department of Defense Single Stock Point DOT Department of Transportation DT Development Test E&R Exchange and Repair EAN European Article Numbering ECP Engineering Change Proposal https://www.osha.gov/html/a-z-index.html https://www.osha.gov/html/a-z-index.html

Acronym Definition ECR Engineering Change Request EIA Electronics & Information Technology Association EOSH Environmental, Occupational Safety, and Health EPLD Electrically Programmable Logic Device ESD Electrostatic Discharge EULA End User License Agreement FAA Federal Aviation Administration FAALC FAA Logistics Center FAST FAA Acquisition System Toolset FCA Functional Configuration Audit FFMEA Functional Failure Modes and Effects Analysis FOB Freight On Board FPGA Field Programmable Gate Array FSM Firmware Support Manual FTE Functional Test Equipment GFE Government Furnished Equipment GFP Government Furnished Property HDBK Handbook HWCI Hardware Configuration Item IAW In Accordance With ICD Interface Control Document ICDLS Interim Contractor Depot Logistics Support ILS Integrated Logistics Support ILSMT ILS Management Team IM Item Manager IRS Interface Requirements Specification ISO International Organization for Standardization LGC Logistics Guidance Conference LMI Logistics Management Information LRU Line Replaceable Unit NAS National Airspace System NASE National Airway Systems Engineering NDI Non-Developmental Item NFPA National Fire Protection Association NLS Network Logic Schedule NSN National Stock Number NSP Not Separately Priced NTIA National Telecommunications and Information Administration O&M Operations and Maintenance OEM Original Equipment Manufacturer OJT On-The-Job Training OSHA Occupational Safety and Health Administration OT Operational Test PAC Post Award Conference PAL Programmable Array Logic

PAT Production Acceptance Test PC Provisioning Conference PCA Physical Configuration Audit PCB Printed Circuit Board PDR Preliminary Design Review PE Performance Examination PLD Programmable Logic Device PM Program Manager PMP Program Management Plan POC Point-of-Contact POM Program Overview Meeting PROM Programmable Read-Only Memory PSR Program Status Report PTR Problem Trouble Report QA Quality Assurance QRO Quality Reliability Officer QSP Quality System Plan QUP Quantity per Unit Pack RMA Reliability and Maintainability Analysis SAE Society of Automotive Engineers SAT Site Acceptance Test SCMP Software Configuration Management Plan SDD Software Design Description SDP Software Development Plan SEM Systems Engineering Manual SEMP Systems Engineering Management Plan SME Subject Matter Expert SMT Software Maintenance Training SOW Statement of Work SPS Software Product Specification SQAP Software Quality Assurance Plan SRS Software Requirements Specification SSDD System/Subsystem Design Description SSE Software Support Environment SSS System/Subsystem Specification STD Standard STLM Service Team Logistics Manager STP Software Test Plan STPr Software Test Procedures STR Software Test Report STrP Software Transition Plan STTETF Special Tools and Test Equipment, Test Fixtures SVD Software Version Description T&E Test and Evaluation T&TE Tools and Test Equipment

TASA Task and Skills Analysis TBD To Be Determined TDP Technical Data Package TIB Technical Instruction Book TIM Technical Interchange Meeting TPS Test Program Set TRR Test Readiness Review UCC Uniform Code Council, Inc.

UI Unit of Issue VRTM Verification Requirements Traceability Matrix WBS Work Breakdown Structure WJHTC William J. Hughes Technical Center

Requirements

The Contractor must perform the work described in this SOW. Work described herein must be fully integrated to ensure efficient and timely execution. The data items to be delivered by the Contractor prescribed by this SOW are specified in the Contract Data Requirements Lists (CDRLs) included in Section J, Attachment J-03 of this SIR.

ALSF-2 SLEP Equipment and Documentation

The ALSF-2 SLEP equipment (including site spares) and all supporting equipment, documentation, and other requirements described in this SOW must be procured, designed, developed, produced, and delivered in accordance with (IAW) the requirements of Specification FAA-E-2999 and this SOW.

ALSF-2 SLEP equipment must consist of the following units:

(a) One (1) Remote Control Panel and one site spare kit;

(b) One (1) Control and Monitor (CM) Cabinet, one site spare kit;

(c) One (1) High Voltage Input Cabinet, one site spare kit;

(d) One (1) High Voltage Output Cabinet, one site spare kit;

(e) Sixteen (16) FAA-approved Low Voltage Elevated Flasher Assemblies (FA-32000/2) , five (5) site spare kit; two (2) site spare kit;

(f) Sixteen (16) FAA-approved Low Voltage Individual Control Cabinets (LVICCs), (FA-

32000/1), five (5) site spare kits; two (2) site spare kits;

(g) Sixteen (16) CM/LVICC Power Line Communication Interface Kit Assemblies; one (1) site spare

(h) One (1) CM Maintenance Terminal;

And two (2) Technical Instruction Books (TIBs); and

(i) The Contractor must procure the LVICCs and LV Flasher Light Assemblies (as specified in C.3.1(e) and (f) above) to complete the ALSF-2 SLEP equipment. They must be tested as part of the ALSF-2 SLEP system configuration throughout Development Test (DT), Production Acceptance Test (PAT), and Type Test in accordance with the FAA-E-2999, ALSF-2 SLEP specification.

Government Furnished Property

The FAA will provide the following Government Furnished Property (GFP) to the Contractor in order to design, develop, manufacture, and test the ALSF-2 SLEP system per the SOW and FAA- E-2999 specification. The contractor must provide facility and power to operate the GFP throughout the life cycle of this contract:

(a) Three (3) 2400 VAC 50 KW Constant Current Regulators (CCR)

(b) One (1) RLMS Control Cabinet

(c) One (1) RLMS High Voltage Filter Cabinet

(d) Sunhillo RICI 6000

(e) Sunhillo LITE Software Suite

(f) Simulator laptop to host LITE Software Suite

In addition, the FAA will be providing the following equipment or fraction of in the event it is needed to test the ALSF-2 SLEP equipment in the ALSF-2 Test Bed:

(a) Isolation transformers

(1) Sixty six (66) watt, 20 ampere (A) primary, 20 A secondary

(2) Sixty three (63) 500 watt, 20 A primary, 20 A secondary

(3) Twenty four (24) 1500 watt, 20 A primary, 20 A secondary

(b) PAR-56 lamps

(1) One hundred forty four (144) 300 watt lamps

(2) One hundred and three (103) 500 watt lamps

(c) Two hundred forty seven (247) PAR 56 Lampholders

(d) Two hundred forty seven (247) Transceiver/Shorting Devices

(e) Fifteen (15) Low Voltage Individual Control Cabinets (LVICCs)

(f) Fifteen (15) Low Voltage Flasher Light Assemblies

Program Management

Program Management Organization

The Contractor must establish and maintain a formal organization to manage the ALSF-2 SLEP contract and any subcontracts. The Contractor must develop and implement a management program to efficiently and effectively execute the requirements of this contract to include:

program control, systems engineering, logistics management, quality assurance (QA), configuration management (CM), Government-furnished resources management, risk management, system safety, and system security for the life of the contract, including option years. The Contractor must prepare a Program Management Plan (PMP) to serve as the baseline for the Contractor’s work plan that describes the process, activities, and personnel required to meet all the requirements of the contract. The PMP must be prepared in accordance with CDRL A001.

CDRL A001 Program Management Plan (PMP)

Program Control

The Contractor must assign a Program Manager (PM)/Project Engineer to organize, plan, schedule, implement, control, analyze, and report on all elements of the contract. The PM must have the experience, authority, and resources to ensure program execution and must be the Contractor’s focal point for all required program tasks. The Contractor must provide a monthly Program Status Report (PSR) during the base period of the contract, and a quarterly PSR during the option periods. The PSR must describe the current activities and progress; identify deliveries made in the previous month; identify deliveries scheduled or planned for the following month;

identify problems encountered along with their solutions, risks, and risk mitigation plans; and define a three-month projection of work activities. The PSR must include updated versions of the Network Logic Schedule as defined in Section C.3.2.2.2. Such action must be in accordance with CDRL A002.

CDRL A002 Program Status Report (PSR)

Risk Management

The Contractor must identify cost, schedule, and technical risks as well as the specialty risks of safety and security and describe how these risks will be managed throughout the performance of the contract. The Contractor must identify and quantify these risks and the risk management techniques in the Risk Analysis section of the PMP. Guidance on risk classifications are outlined in the FAA Systems Engineering Manual (SEM). A copy of the SEM will be provided by the CO, if needed. Risks that will impact schedule milestones must be reflected in the deliverables of C.3.2.2.2.

Work Breakdown Structure (WBS) and Network Logic Schedule (NLS)

The Contractor must use a WBS and NLS to aid in project tracking and reporting. The Contractor must ensure the WBS includes the structure from Section 3.0 of the WBS specialty function detailed in FAST at http://fast.faa.gov/docs/WBS.doc. The Contractor’s WBS must be tailored to show the Contract WBS elements and be developed to the third level of detail as described in MIL-HDBK-881.

The Contractor must develop a NLS that describes the sequence of events needed to accomplish the requirements of this contract by WBS elements. The Contractor must ensure that the NLS portrays an integrated schedule plan to meet the milestones and delivery requirements of this contract, taking into account the risks and possible schedule impacts of the risks identified per C.3.2.2.1. The NLS must identify the program’s critical path. The NLS must be constructed using Microsoft Project as the software tool. Data delivered must be in accordance with CDRL A003.

CDRL A003 Work Breakdown Schedule (WBS) and Network Logic Schedule (NLS) http://fast.faa.gov/docs/WBS.doc

Quality Assurance

During the entire product lifecycle, the Contractor must use a quality assurance process based on AS9100D, Quality Management Systems - Requirements for Aviation, Space, and Defense Organizations. The Contractor’s quality assurance procedures must be documented in the Quality System Plan (CDRL F001) and may be used to verify item compliance and delivery requirements. The Contractor’s quality assurance processes must be subject to audit by the FAA and the applicable certifying authority.

The QSP must, at a minimum, assure that the following items and guidelines are included in the program:

(a) Independent responsibility and authority granted to assigned personnel to identify, evaluate, and report quality problems, and to recommend solutions , all without fear of reprisal, intervention, or adverse action;

(b) CDRLs are peer-reviewed and technical edited before submittal;

(c) All CM processes are performed throughout the period of performance of the contract;

(d) All tests and inspections are performed in compliance with contract requirements and all test data are complete, correct, traceable, repeatable, and acceptable; and

(e) All manufacturing processes are monitored to ensure that a quality product is delivered.

The Contractor must require quality control of the services and supplies provided from suppliers and Subcontractors. The Contractor must report its quality control data upon request and in the

PSR.

The Contractor must identify all software development QA activities in accordance with FAA- STD-026/DID-FAA-026-23. The Contractor must include the Software Quality Assurance Plan as a section or appendix in the QSP.

CDRL F001 Quality System Plan (QSP)

Meetings, Reviews, and Audits

Post Award Conference (PAC), Logistics Guidance Conference (LGC), Training Guidance Conference (TGC)

A PAC must be conducted at the Contractor’s facility in conjunction with the LGC and TGC, as stated in C.3.7.1.1 and C.3.8.1, no later than 30 calendar days after contract award to review contract and product specification requirements. During the PAC, the Contractor must brief the required plans and deliver, for FAA approval, a baseline schedule for satisfying each SOW requirement based on the WBS identified in C.3.2.2.2. During the PAC, the Contractor and FAA technical personnel will review FAA-E-2999 in detail to ensure a mutual understanding of the specification requirements.

The PAC, LGC, and TGC must be targeted for five (5) working days in length. The first three (3) days is PAC and the two (2) days are for the LGC and TGC. The Contractor’s technical key personnel in attendance at this meeting must be limited to those as specified in Section H of this contract, and their contract personnel. For the PAC, the FAA attendance will be limited to approximately 20 personnel. For the LGC and TGC, the FAA attendance will be limited to approximately 15 personnel. The Contractor must prepare and submit agendas and meeting minutes with all such items being subject to FAA approval as outlined in the appropriate CDRL.

CDRL A004 Meeting Agendas CDRL A005 Meeting Minutes

Program Overview Meeting (POM)

The Contractor must host a POM when requested by the FAA. The POM will include a summary of the requirements of the monthly PSR. When formal POMs are held, the meeting location must be at the Contractor’s facility. The Contractor’s technical key personnel in attendance at this meeting must be limited to those as specified in Section H of this contract, and their contract personnel. The POMs must not exceed three (3) working days in length. FAA attendance will be limited to approximately 25 personnel. The Contractor must prepare and submit agendas and meeting minutes with all such items being subject to FAA approval as outlined in the appropriate

CDRL.

CDRL A004 Meeting Agendas CDRL A005 Meeting Minutes

Technical Interchange Meeting (TIM)

The FAA may conduct TIMs as requested to discuss specific technical activities, including, design and technical issues, questions related to the FAA-E-2999 requirement, CDRLs related documents, test procedures, test plans, test results, quality issues, training issues, logistics issues, safety and security issues, and implementation concerns at the Contractor’s facility. The purpose of the TIM is to ensure continuing FAA awareness and participation in the review and concurrence with the technical progress of the contract. The Contractor’s technical key personnel in attendance at this meeting must be limited to those as specified in Section H of this contract, and their contract personnel. The TIMs must not exceed three (3) days in length. FAA attendance will generally be limited to approximately 25 personnel. The Contractor must prepare and submit agendas and meeting minutes with all such items being subject to FAA approval as outlined in the appropriate CDRL.

CDRL A004 Meeting Agendas CDRL A005 Meeting Minutes

Formal Reviews and Audits

The Contractor must plan, host, provide administrative support, and participate in the required formal reviews and audits listed below in accordance with contract requirements. The Contractor must prepare and submit agendas and meeting minutes with all such items being subject to FAA approval as outlined in the appropriate CDRL.

Formal reviews and audits include but not limited to:

(a) Logistics Guidance Conference (C.3.7.1.1);

(b) Preliminary Design Review (PDR) (C.3.3.1);

(c) Critical Design Review (CDR) (C.3.3.2);

(d) Test Readiness Review (TRR) (C.3.6.4.2);

(e) Functional Configuration Audit (FCA) (C.3.5.5.1);

(f) Physical Configuration Audit (PCA) (C.3.5.5.2);

(g) Provisioning Conference (C.3.7.2.2);

(h) Technical Instruction Book (TIB) Review (C.3.7.6.2).

Design Reviews

The Contractor must conduct design review meetings as described below. The Contractor must provide a 15-business day notification to the CO before each proposed design review meeting.

Preliminary Design Review (PDR)

The Contractor must host a PDR no later than 30 calendar days after receipt of System/Subsystem Design Description (SSDD) FAA comments by the Contractor (C.3.4.1.2).

The requirement for a PDR is outlined in the FAA Acquisition Management System (AMS). This information is found at http://fast.faa.gov. This review will also trace the design approach to the technical requirements in FAA-E-2999, outline and assess test strategies, and review the impact of design on supportability and cost. For Non-Developmental Items (NDIs), the Contractor must provide the results of the analysis that verify that the item will meet the associated technical requirements and the methods used to ensure that each requirement has been met. The Contractor’s technical key personnel in attendance at this meeting must be limited to those as specified in Section H of this contract, and their contract personnel. The Contractor must prepare and submit agendas and meeting minutes with all such items being subject to FAA approval as outlined in the appropriate CDRL.

The following documentation and information must be available for review at PDR:

(a) System and Allocated Requirements Database as defined in the System Subsystem Specification (SSS) in accordance with CDRL C002;

(b) Updated preliminary System/Subsystem Design Description (SSDD) (detailed hardware design concepts, detailed block diagrams, schematic diagrams, and preliminary parts lists that capture all requirements of FAA-E-2999) in accordance with CDRL C003;

(c) Preliminary Software Description Document (SDD) (software/firmware design concepts, proposed software platform and proposed software development tools) and preliminary Interface Control Document (ICD) in accordance with CDRL C006;

(d) Preliminary Contractor Master Test Plan (CMTP) in accordance with CDRL D001a;

(e) Commercial Off-the-Shelf (COTS)/NDI/Developmental Item specification sheet and technical data;

http://fast.faa.gov/

(f) Power consumption, distribution, surge protection, and grounding design;

(g) Lifecycle cost information;

(h) System Safety considerations;

(i) Risk assessments; and

(j) Updated schedule.

The following is required for PDR milestone approval:

(a) Provided updated versions of the CDRL documentation listed above (a-e);

(b) Closed all PDR action items; and

(c) Submitted, and received FAA approval of, the Contractor-developed PDR Report in accordance with CDRL A006.

CDRL A004 Meeting Agendas CDRL A005 Meeting Minutes CDRL A006 PDR Report

Critical Design Review (CDR)

The requirement for a CDR is outlined in the FAA AMS. This information is found at http://fast.faa.gov/docs/sowgen_docs/dids/FAA-SE-014.docx. The Contractor must host a CDR to establish the final ALSF-2 SLEP configuration no later than 240 calendar days after PDR. The Contractor’s technical key personnel in attendance at this meeting must be limited to those as specified in Section H of this contract, and their contract personnel. The Contractor must prepare and submit agendas and meeting minutes with all such items being subject to FAA approval as outlined in the appropriate CDRL.

The following, and not limited to, documentation and information must be available for review at CDR:

(a) Updated SSS in accordance with CDRL C002;

(b) Updated SSDD in accordance with CDRL C003;

(c) Updated SDD and ICD in accordance with CDRL C006;

(d) Updated CMTP in accordance with CDRL D001a;

(e) Preliminary Reliability and Maintainability Analysis (RMA) in accordance with CDRL

C011

(f) Preliminary DT Plan in accordance with CDRL D001b ;

(g) Preliminary Standard Installation Drawings (30%) in accordance with CDRL D010;

(h) Preliminary Technical Instruction Book (60%) in accordance with CDRL L009;

(i) For NDIs, the Contractor must also provide the following:

(1) Detailed functional/physical description,

(2) Any other relevant results or analyses,

(3) Detailed description of the interfaces, and

(4) List of any identified long lead items.

(j) Updated System Safety considerations;

(k) Design concerns (e.g., environmental control, transient/lightning protection electromagnetic compatibility and interoperability, technical risks);

http://fast.faa.gov/docs/sowgen_docs/dids/FAA-SE-014.docx

(l) ALSF-2 SLEP prototype units;

(m) Identification of design- and cost-driven requirements;

(n) Production and manufacturing flow processes of the First Articles and Production systems;

(o) Logistics support (e.g., test tools/test equipment, sparing, training, etc.); and

(p) Updated schedule.

The following is required for CDR milestone approval:

(a) Received FAA approval of the CDRL documentation listed above (a-f);

(b) Closed all CDR action items; and

(c) Submitted, and received FAA approval of, the Contractor-developed CDR Report in accordance with CDRL A007.

CDRL A004 Meeting Agendas CDRL A005 Meeting Minutes CDRL A007 CDR Report

System Engineering Management

The Contractor must develop and implement a System Engineering Management Plan (SEMP) for the definition, development, integration, and verification of ALSF-2 SLEP requirements allocated to the Hardware Configuration Items (HWCIs) and Computer Software Configuration Items (CSCIs). System engineering efforts must include all aspects of performance, quality, and cost for the projected duration of the contract, maintainability, reliability, schedule, data processing reserves, and future growth requirements.

The Contractor must maintain effective control over the system engineering and design development process, including subcontract items and services, to ensure cost, performance, and schedule requirements are met, to provide early detection and resolution of problems, and to reduce risk.

CDRL C001 System Engineering Management Plan (SEMP)

Hardware Design and Development

System/Subsystem Specification (SSS)

The Contractor must conduct a system engineering analysis to translate and allocate requirements specified in FAA-E-2999 to the hardware and software requirements in the SSS.

The SSS must be included in the CVRTM, which will serve as the Contractor’s system-level functional baseline. The baseline must be in accordance with CDRL C002.

CDRL C002 System/Subsystem Specification (SSS)

System/Subsystem Design Description (SSDD)

The Contractor must allocate requirements from the SSS to the System/Subsystem Design Description (SSDD). The SSDD must provide a detailed documentation of the hardware and software design of the ALSF-2 SLEP equipment. The SSDD must be included in the CVRTM.

The SSDD must be in accordance with CDRL C003.

CDRL C003 System/Subsystem Design Description (SSDD)

Software and Firmware Design and Development

All ALSF-2 SLEP system software or firmware developed by the Contractor must be developed in accordance with FAA-STD-026. The Contractor must allow full access, and deliver to the FAA, all source and compiled code, including libraries, for all developed and modified commercial code in accordance with C.3.5.3.1. The Contractor must provide all hardware and software development tools, including all source and header files, required to complete testing.

The following software documentation applies to both software and firmware and must be provided using FAA-STD-026 as guidance for content.

(a) Software Transition Plan (STrP);

(b) Software Design Description (SDD);

(c) Software Product Specification (SPS);

(d) Software Version Description (SVD);

(e) Firmware Support Manual (FSM).

CDRL C005 Software Transition Plan (STrP) CDRL C006 Software Design Description (SDD) CDRL C007 Software Product Specification (SPS) CDRL C008 Software Version Description (SVD) CDRL C009 Firmware Support Manual (FSM)

The ALSF-2 SLEP Contractor must incorporate the following software or firmware information into other documents already described in this contract using FAA-STD-026 as guidance for content. The Contractor’s format must be preapproved by the FAA, as stated in Section F of this contract.

(a) Software Development Plan (SDP) – Incorporate into the SEMP (CDRL C001);

(b) Software Requirements Specification (SRS) – Incorporate into the SSS (CDRL C002);

(c) Interface Requirements Specification (IRS) - Incorporate into CDRL C002, SSS;

(d) Software Test Plan (STP) - Incorporate into CDRL D001a, Contractor’s Master Test Plan

(CMTP) and CDRL D001b, Development Test (DT) Plan;

(e) Software Test Procedures (STPr) - Incorporate into CDRL D002, DT Procedures;

(f) Software Test Report (STR) - Incorporate into CDRL D007, DT Report;

(g) Software Quality Assurance Plan (SQAP) - Incorporate into CDRL F001, QSP;

(h) Software Configuration Management Plan (SCMP) - Incorporate into CDRL E001, Configuration Management Plan (CMP).

The Contractor must obtain End-User License Agreements (EULA) with software owners for all COTS software and software upgrades that are part of the ALSF-2 SLEP system. The EULA must show the Government as the end user. The Contractor will provide a copy of each EULA to the Government. Each EULA must allow for the long-term requirements of the project to be met, including configuration control and reproduction.

Software Support Environment (SSE)

The Contractor must deliver a Software Support Environment (SSE) to the FAA National Airway Systems Engineering (NASE), Navigation and Landing Team (AJW-143) facility in Oklahoma City, OK. The SSE must consist of the items identified in the STrP, including all hardware/software items necessary to transfer the compiled software to the ALSF-2 SLEP:

(a) Computer (with monitor, keyboard, mouse, and Network Interface Controller connection);

(b) Source code;

(c) Software (with compiled executables);

(d) Software development and verification tools (versions of the development tools must be the same as the ones used for development);

(e) Any hardware and software applications used to load firmware into memory devices; and

(f) Documentation (as stated in C.3.4.2) needed to perform software development and verification activities.

If the ALSF-2 SLEP system includes complex electronic devices such as Application-Specific Integrated Circuits (ASICs), Field-Programmable Gate Arrays (FPGA), and Programmable Logic Devices (PLDs), then the Contractor must provide a master for each programmed device, the tools and documentation necessary to perform complex electronic device development and verification activities as part of the SSE.

The Contractor must submit the SSE as part of the SDD in accordance with CDRL C006. The SSE and SDD must be updated to include any changes as a result of all test activities. The updated documentation must be delivered 30 calendar days after the Government’s acceptance of the PCA Report.

CDRL C006 Software Design Document (SDD)

Software Maintenance Training

The Contractor must develop and conduct Software Maintenance Training (SMT) to provide students with the knowledge and skills necessary to understand the SSE employed and perform ALSF-2 SLEP software maintenance including design modifications, site specific adaptations, source code changes, debugging, integration, tests, documentation of changes, and configuration control.

The SMT course content must describe the following:

(a) Computer-Aided Software Engineering (CASE) tools used for requirement analysis, design, coding, CM, testing, documentation, and reverse engineering;

(b) Models, simulators, and emulators including interfaces, requirements analysis, and performance measuring/testing tools;

(c) ALSF-2 SLEP software architecture down to the source code;

(d) Programming site-adaptation data;

(e) Description of the documentation tools used for automatic documentation, production of documentation, and publishing;

(f) Overview of CM, requirements management, and traceability tools. This includes compilers, debuggers, and software-build procedures;

(g) Transfer of compiled software and verification of transfer to the ALSF-2 SLEP; and

(h) Loading new firmware onto programmable devices.

The SMT course content must also include the use of complex electronic hardware development data, methods, and tools including any hardware descriptive language that may be used for all ASICs, FPGAs, and PLDs used in the design. The Contractor must deliver the training course materials no later than 60 calendar days following the completion of FCA/PCA, per CDRL C010. The Contractor must conduct the SMT course within a reasonable time following the completion of FCA/PCA and prior to the commissioning of the first site, per CDRL C010..

CDRL C010 Software Maintenance Training (SMT)

Reliability and Maintainability Analysis (RMA)

The Contractor must establish and implement an FAA-approved RMA program that accounts for both hardware and software components. Serial reliability analysis must be conducted in accordance with MIL-HDBK-217F to determine the predicted MTBF for the ALSF-2 SLEP system. Maintainability analysis must be developed using guidance found in MIL-HDBK-472.

CDRL C011 Reliability and Maintainability Analysis (RMA)

Program Trouble Reports

The contractor must develop and maintain a database for submitting, tracking, reporting, and maintaining records on PTRs. The database supports the FAA in maintaining awareness of problems from initiation to final corrective action and archiving. The database must enable status reporting of all test problems. The contractor must use the database for tracking problems associated with any system, equipment, software, or firmware that has been placed under formal configuration control. The FAA will review and approve the overall design of the database to ensure operational use and functionality. The contractor must provide government personnel with access to the database and provides reports at the request of the FAA.

At a minimum, each PTR must contain the following information:

1. A unique ID and title;

2. Date, time, and location of the issue;

3. Priority;

4. Test activity and test step affected;

5. A brief description of the issue;

6. Affected configuration items and requirements;

7. Failure analysis;

8. Planned corrective actions;

9. Closure description; and

10. Closure date.

After the First Article has been baselined, each PTR must contain the following additional information:

1. Line replaceable unit (LRU) or component description

2. LRU/component identification using bar-code or serial number

3. National stock number (NSN) (if assigned)

4. Next higher level component

5. Site location where failure occurred including point of contact (POC) (if available)

6. Component disposition

The priority of each PTR must be determined according to the following definitions:

Priority 1: is assigned to a problem that prevents the accomplishment of an operational, mission-critical, or mission-essential capability, jeopardizes safety, security, or other critical requirements.

Priority 2: is assigned to a problem that adversely affects the accomplishment of an operational, mission-critical, or mission-essential capability, and no work-around solution is known.

Priority 3: is assigned to a problem that adversely affects accomplishing an operational, mission critical, or mission-essential capability, but a work-around solution is known.

Priority 4: is assigned to a problem that results in a user/operator inconvenience or annoyance but does not affect a required operational, mission-critical, or mission-essential capability.

Priority 5: is assigned to any other problem/defect not described above (e.g., system documentation errors).

The PTR process is required throughout the life of the contract to include base contract and all exercised options. This includes all failures discovered during production phase and Type Tests.

The PTR must also feedback into the products of C.3.2.2.1 and C.3.2.2.2.

CDRL C012 Program Trouble Reports

Configuration Management Program

Configuration Management Planning

The Contractor must establish, implement, and maintain a CM program using MIL-HDBK-61 and ANSI/Electronics & Information Technology Association (EIA)-649 for guidance, and must document the CM program using MIL-HDBK-61, Appendix A, focusing on Phase II and III, as described in Table A-3. The CM program must cover the Contractor’s CM organizational structure and methods of configuration identification, change control, configuration status accounting, and configuration auditing for documentation, physical media, and physical parts representing or comprising the ALSF-2 SLEP. The Contractor must maintain configuration control of hardware, software, firmware, developmental documentation, and commercial documentation until delivery of the last ordered production unit (including all option years), subject to configuration change control requirements specified below. The Contractor must identify the single focal point who will serve as the primary point-of-contact (POC) for all communication on CM-related issues. The CMP must be in accordance with CDRL E001.

CDRL E001 Configuration Management Plan (CMP)

Configuration Item Identification

The Contractor must identify, establish, and maintain the configuration of the ALSF-2 SLEP and its subordinate CIs. This configuration must include the following:

(a) Selecting developmental and commercial CIs at appropriate levels of the product structure to facilitate control and support of the items;

(b) Determining the types of configuration documentation required for each CI to define its performance, functional, and physical attributes, including internal and external interfaces;

(c) Determining the appropriate configuration control authority for each configuration document consistent with logistics support planning for the associated CI;

(d) Issuing identifiers for the CIs and the configuration documentation;

(e) Maintaining the configuration identification of CIs to facilitate effective logistics support of items in service;

(f) Releasing configuration documentation;

(g) Establishing configuration baselines for the configuration control of CIs.

Software CI

The Contractor must assign a discrete part/identification number to each software/firmware version, containing release or build type software executables.

Configuration Control

The Contractor must maintain and demonstrate a systematic lifecycle configuration change management process for the ALSF-2 SLEP as described in the CMP. The Contractor must manage the preparation, justification, evaluation, coordination, disposition, and implementation of proposed engineering changes and deviations to the ALSF-2 SLEP hardware, software and firmware, and baseline configuration documentation. The Contractor must integrate the ALSF-2 SLEP into its ongoing configuration management activities upon successful completion of FCAs and PCAs.

Engineering Change

Engineering Change Proposals (ECPs) required to be submitted to the Government are classified as either Class I or Class II. A Class I ECP is approved by the Government and authorized with a contract modification. A Class II change is reviewed for concurrence in classification by the FAA Quality Reliability Officer (QRO).

If the Contractor determines that a requirement, design, and equipment change is necessary, the Contractor must submit an ECP.

C.3.5.3.1.1 Class I Change Definition A proposed engineering change to a CI, or any combination or discrete portion thereof, must be Class I if the functional or allocated baselines, once established, are affected to the extent that a proposed change affects the CI’s form, fit, and function; corrects a deficiency; or impacts logistic documentation or support. The terms “Form”, “Fit”, “Function” and “Deficiency” are defined as follows:

(a) Form – The physical configuration (shape) of an item to ensure interchangeability and compatibility with intended applications;

(b) Fit – The description of input/output characteristics to ensure interoperability with related interfacing items;

(c) Function – The performance characteristics to ensure that the item is capable of doing its intended job; and

(d) Deficiency – Any combination or characteristic of the CI which is not in compliance with the established baseline.

The Contractor must prepare a Class I ECP if the proposed change to a CI or part thereof results in any of the following requirements being outside specified limits or specified tolerances:

(a) Performance;

(b) Reliability, maintainability, safety;

(c) Weight, balance, moment of inertia, physical dimensions;

(d) Interface characteristics;

(e) Electromagnetic characteristics; and

(f) Other technical requirements in FAA-E-2999.

C.3.5.3.1.2 Class I Changes The Contractor must submit all Class I ECPs along with all supporting documentations and all test documented results to the CO or his/her designated Contracting Officer’s Representative (COR), with a copy to the FAA QRO. The Government will have 30 calendar days to review the subsequent ECP. If approved, the Contractor must proceed with the engineering change. The Contractor must submit to the CO and COR all changes to documentation resulting from the approved ECP. The documentation includes, at a minimum, all affected assembly drawings, LMI, and TIB change pages within 30 calendar days of FAA approval. All changed documentation must have all changes within it highlighted by change bars and was/now annotations. ECPs will be applicable and required for all equipment procured throughout the life of the contract, including option years.

If the change is not approved, the Contractor must withdraw it or resubmit with further clarification of the proposed change(s). If Class I ECP changes are approved by the FAA, they are at no additional cost to the Government.

C.3.5.3.1.3 Class II Change Definition An engineering change which impacts none of the Class I form, fit and function factors of C.3.5.3.1.1 must be classified as a Class II engineering change.

C.3.5.3.1.4 Class II Changes The Contractor must submit Class II ECPs to the FAA QRO and FAA COR. The FAA QRO is responsible to determine ECPs classification concurrence and approval. The FAA has 7 calendar days to review and approve Class II ECPs. If approved, the Contractor must submit to the CO and COR all changes to documentation resulting from the approved Class II ECPs within 30 calendar days of FAA approval. The documentation includes, at a minimum, all affected assembly drawings, and TIB change pages. All changed documentation must have all changes within it highlighted by change bars and was/now annotations.

If the QRO does not concur in the classification of a…