AH-1W Critical Cockpit Upgrade _CCU_

							DRAFT
11 April 2008

STATEMENT OF WORK FOR

AH-1W CRITICAL COCKPIT UPGRADE (CCU) PROJECT

Prepared by NAVAL AIR SYSTEMS COMMAND, PMA-276

Page 1

10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
Table of Contents

1
1.1 1.2

INTRODUCTION........................................................................... 5
BACKGROUND .................................................................................................... 5 SCOPE AND DELIVERABLES ................................................................................. 6

1.2.1 SCOPE .............................................................................................................. 6 1.2.2 HARDWARE AND SOFTWARE DELIVERABLES ......................................................... 6

2
2.1 2.2

APPLICABLE DOCUMENTS ....................................................... 6
GOVERNMENT DOCUMENTS .................................................................................. 6 ADDITIONAL DOCUMENTS .................................................................................... 8

3
3.1 3.2

TECHNICAL REQUIREMENTS .................................................... 8
REQUIREMENTS OVERVIEW .................................................................................. 8 THRESHOLD UPGRADED COCKPIT CONTROL SYSTEM (CCS) REQUIREMENTS .......... 8

3.2.1 UPGRADED COCKPIT CONTROL SYSTEM (CCS) ................................................... 9 3.2.2 BLUE FORCE SITUATIONAL AWARENESS (BFSA) ................................................ 11 3.2.3 MOVING MAP FUNCTIONALITY ........................................................................... 12 3.2.4 VARIABLE MESSAGE FORMAT (VMF) FUNCTIONALITY ......................................... 13 3.2.5 HARDWARE ..................................................................................................... 14 3.3 PRE-PRODUCTION UNITS ................................................................................... 15 3.3.1 PRE-PRODUCTION UNIT SUPPORT..................................................................... 16 3.3.2 LABORATORY MODIFICATION INSTALLATION ........................................................ 16 3.3.3 AIRCRAFT INSTALLATION ................................................................................... 16 3.3.3.1 Electric Power Compatibility........................................................................ 16 3.3.3.2 Electromagnetic Compatibility ..................................................................... 17 3.3.3.3 Audit and Certification of Private and Public Laboratories.......................... 17 3.3.3.4 Assessment Plan and Report ......................................................................... 17 3.3.4 GROUND AND FLIGHT ASSESSMENT SUPPORT .................................................... 17 3.3.5 PRE-PRODUCTION UNIT METRICS ..................................................................... 17 3.3.6 INTEGRATED LOGISTICS SUPPORT (ILS) ............................................................ 18 3.3.6.1 Logistics Management Information (LMI) Database ................................... 19 3.3.6.2 Technical Manual Source Data with Illustrations ......................................... 21 3.3.6.3 Support Equipment (SE) ............................................................................... 22 3.3.6.4 Training ......................................................................................................... 22 3.3.6.5 Maintenance Plan .......................................................................................... 23 3.3.6.6 Engineering Data for Provisioning (EDFP) .................................................. 23 3.3.6.7 Interim Support Items List (ISIL) ................................................................. 23 3.3.6.8 Provisioning Parts List (PPL) ....................................................................... 23 3.3.6.9 Packaging, Handling, Storage, and Transportation (PHS&T) ...................... 24 3.3.6.10 ILSMT/IPT Meetings.................................................................................... 24 3.3.6.11 Maintenance Plan Review............................................................................. 24 3.3.6.12 Reliability and Maintainability (R&M) Program ......................................... 24 Page 2 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
Reliability and Maintainability (R&M) Predictions ..................................... 24 Maintainability .............................................................................................. 25 Failure Reporting, Analysis, and Corrective Action System (FRACAS) ..... 25 Failure Modes Effects and Criticality Analysis (FMECA)........................... 25 Reliability-Centered Maintenance (RCM) Analysis ..................................... 25 Level of Repair Analysis (LORA) ................................................................ 26 Field Maintainability Article (FMA) Demonstration ................................... 26 Obsolescence Management / Diminishing Manufacturing Sources & Material Shortages (DMSMS) ..................................................................... 27 3.3.6.21 Notification ................................................................................................... 27 3.3.6.22 Unique Identification (UID) ......................................................................... 28 3.3.6.23 Bill of Materials (BOM) ............................................................................... 28 3.4 DESIGN RIGHTS ISSUES ..................................................................................... 28 3.5 COPYRIGHTS ON DOCUMENTS AND MANUALS ..................................................... 28 3.3.6.13 3.3.6.14 3.3.6.15 3.3.6.16 3.3.6.17 3.3.6.18 3.3.6.19 3.3.6.20

4
4.1 4.2 4.3 4.4

PROGRAM MANAGEMENT REQUIREMENTS ......................... 29
INTEGRATED MASTER SCHEDULE (IMS) ............................................................. 29 CONTRACT WORK BREAKDOWN STRUCTURE (CWBS) ........................................ 29 PROGRAM MANAGEMENT PLAN (PMP) ............................................................... 30 SYSTEM ENGINEERING PLAN (SEP) ................................................................... 30

4.4.1 CONFIGURATION MANAGEMENT (CM) ................................................................ 30 4.4.1.1 Engineering Change Proposal (ECP) ............................................................ 31 4.4.1.2 Request For Deviation (RFD) ....................................................................... 31 4.4.2 DATA MANAGEMENT (DM) ................................................................................ 31 4.4.3 QUALITY ASSURANCE (QA)............................................................................... 32 4.4.4 SUBCONTRACTOR MANAGEMENT....................................................................... 32 4.5 PROGRESS REPORTING ..................................................................................... 32 4.6 4.7 REQUIREMENTS TRACEABILITY MATRIX (RTM) ................................................... 32 SECURITY ......................................................................................................... 33

4.7.1 DATA ACCESS ................................................................................................. 33 4.7.2 GOVERNMENT FACILITY ACCESS ....................................................................... 33 4.8 GOVERNMENT-FURNISHED EQUIPMENT, MATERIALS, SOFTWARE, AND INFORMATION .................................................................................................... 33 4.9 SAFETY ............................................................................................................ 33

5
5.1 5.2 5.3 5.4

PROGRAM REVIEW REQUIREMENTS ..................................... 34
PROGRAM MANAGEMENT REVIEW (PMR) AND TECHNICAL INTERCHANGE MEETINGS (TIM) ............................................................................................... 34 POST AWARD CONFERENCE (PAC)/SYSTEM REQUIREMENTS REVIEW (SRR) ....... 34 INTEGRATED BASELINE REVIEW (IBR)/PRELIMINARY DESIGN REVIEW (PDR) ....... 35 CRITICAL DESIGN REVIEW (CDR) ...................................................................... 36 Page 3 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
6 7 8 9 10 TRAVEL REQUIREMENTS ........................................................ 37 PERFORMANCE PERIOD ......................................................... 37 CONTRACT DATA REQUIREMENTS LIST (CDRL) .................. 37 STANDARDS.............................................................................. 41 ACRONYMS AND ABBREVIATIONS ........................................ 41

Page 4

10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
1 INTRODUCTION
This Statement of Work (SOW) identifies the work required of the Contractor for the Critical Cockpit Upgrade (CCU) project. The overarching CCU project goal is to meet the Blue Force Situational Awareness (BFSA) requirements. Requisite and complementary requirements include optimization of current AH-1W cockpit control and pilot interface attributes with the aircraft‟s communication and navigation systems. This document defines the systems capabilities, functionality, and performance standards for the CCU project.

1.1 BACKGROUND
PMA-276 is seeking a cost-wise system replacement for the existing, obsolete Cockpit Control System (CCS) in the AH-1W. Currently the CCS functions are allocated to the pilot and co-pilot Control, Display, Navigation Units (CDNU) and Interface Control Units (ICUs) in the AH-1W. The intent of the CCU project is to replace these configuration items (CDNUs and ICUs) with modern, commodity hardware and software solutions. A common chassis with "plug-in" Sub-system Replaceable Assembly (SRA) functionality and expandability is envisioned. The optimum solution will provide at a minimum, existing CDNU and ICU functionality, BFSA functionality, Moving Map capabilities, and Variable Message Format (VMF) protocol formatted datalink capabilities. Integration of Weapons Replaceable Assemblies (WRA) and their associated software configuration item components, which shall provide the optimum solution for the obsolete CCS, is inherent to this tasking. The upgraded CCS shall control all current CDNU and ICU functionality, in addition to the threshold capabilities. The upgraded CCS must satisfy existing AH-1W requirements for power, size, weight, interfaces, and environmental factors. A limitation of the current CCS is the inability of the Government to efficiently update and support legacy and/or proprietary software. To meet modern software supportability objectives, it is the Government‟s intention to seek the least restrictive rights to all hardware and software configuration items associated with the CCU project, allowing Government support activities to upgrade hardware and software components throughout the upgraded CCS‟ life without reliance on future Contractor resources. A primary goal of the upgraded CCS is to decrease fratricide events (i.e. “blue-on-blue” engagements) and increase force protection/safety. BFSA is a digital command and control system capability that decreases fratricide by providing on-the-move, near realtime, increased Situational Awareness (SA). BFSA capable systems share Position Location Information (PLI), text messages and other information; which provide the knowledge of friendly location, identification, intent, and status. This upgrade will allow the AH-1W aircrew to achieve a degree of SA in the operational arena that was previously unattainable. A successful, cost-effective integration of the upgraded CCS will increase the effectiveness, lethality, and survivability of the AH-1W and provide the basis for a formal AH-1W inventory procurement request by USMC/Navy resource sponsors. Page 5 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
1.2 SCOPE AND DELIVERABLES 1.2.1 Scope
The scope of this effort shall be to fully integrate the pilot and co-pilot upgraded CCS in the AH-1W. The goal of this integration is to facilitate more efficient allocation of pilot task time to critical functions including weapons systems employment, navigation, communication, and aircraft vehicle status tasks. The requirement for BFSA hardware and software architecture is the critical performance parameter of this effort. The core control and display functions of the BFSA solution and current CCS functions must reside in the current physical locations of the CDNUs and the ICUs. The only expected exception to these constraints is that the Government recognizes the BFSA requirement shall include accommodating an additional transceiver and its associated antenna system. Using current technologies, the Contractor solution shall optimize these BFSA requirements and increase the existing CCS performance capabilities of the AH-1W cockpit. The Contractor shall furnish all services, hardware, materials, and equipment required to integrate and assure airworthiness for the upgraded CCS in the AH-1W. The Contractor shall also provide all technical, planning, management and manufacturing efforts to complete this contract.

1.2.2 Hardware and Software Deliverables
The Contractor shall deliver Hardware Configuration Items (HCI), Software Configuration Items (SCI), and aircraft kit integration items that will meet the performance requirements identified in this SOW and Contract Data Requirements List (CDRL).

2 APPLICABLE DOCUMENTS
In the event of conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

2.1 GOVERNMENT DOCUMENTS
The most recent revision of the referenced document at the time of contract shall be used unless otherwise specified. In the event of conflict between the applicable documents and this SOW, the SOW shall take precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained. Most Government Documents may be obtained online at The Department of Defense Single Stock Point for Military Specifications, Standards and Related Publications: http://dodssp.daps.dla.mil/assist.htm. Alternatively, copies of applicable documents listed in the Department of Defense Index of Specifications and Standards (DODISS) and required by the Contractor in connection with specific procurement functions may be obtained upon application to the Commanding Officer, Naval Publications and Forms Center, Code 105, 5801 Tabor Avenue, Philadelphia, PA Page 6 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
19120. Refer to both title and number when requesting specifications, standards, handbooks, drawings, and other publications. MIL-STD-704 MIL-STD-1553 MIL-STD-2525 MIL-STD 2073 MIL-STD-188-220 MIL-STD-2045-47001 MIL-STD-6017 MIL-STD-810 MIL-STD-461 MIL-STD-464 MIL-STD-1472 MIL-STD-129 MIL-STD-130 MIL-STD-2217 MIL-L-85762 MIL-PRF-49506 MIL-HDBK-263 MIL-HDBK-704 Aircraft Electric Power Characteristics Digital Time Division Command/Response Multiplex Data Bus Common Warfighting Symbology DoD Standard Practice For Military Packaging Digital Message Transfer Device Subsystems Connectionless Data Transfer Application Layer Standard Variable Message Format (VMF) Environmental Engineering Considerations and Laboratory Tests Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment Electromagnetic Environmental Effects Requirements for Systems Human Engineering Military Marking for Shipment and Storage Identification Marking of U.S. Military Property Requirements for Memory Loader/Verifier Multiplex Bus Interface with Avionic Systems Lighting, Aircraft, Interior, Night Vision Imaging System (NVIS) Compatible Logistics Management Information Electrostatic Discharge Control Handbook Guidance for Test Procedures for Demonstration of Utilization Equipment Compliance to Aircraft Electrical Power Characteristics Work Breakdown Structures for Defense Materiel Items Configuration Management Guidance Acquisition Logistics

MIL-HDBK-881 MIL-HDBK-61A MIL-HDBK-502

AH-1W Associated Systems Interface Control Document (ICD) NAVAL SYSTEMS ENGINEERING GUIDE: (http://www.navair.navy.mil/kms/41g/SE%20Guide.pdf) NAVAIRINST 3080.1 NAVAIRINST 2450.2 Page 7 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
NAVAIRINST 4130.1 OPNAVINST 4790.2J Electrical Load Analysis

2.2 ADDITIONAL DOCUMENTS
Requirements for reference documentation are dynamic. Related documents and electronic files shall be made available to the Contractor as necessary. The Detailed Specification for Model AH-1W Marine Attack Helicopter is SD-549-16R1 with H1-AFC301.

3 TECHNICAL REQUIREMENTS
The Contractor solution delivered in response to this SOW shall meet the requirements (Sections 3.1 - 3.5) for the upgraded CCS integration. The Contractor‟s proposal shall address any requirement that cannot be met. Upon procurement, all ownership for the upgraded CCS (and its associated software elements) shall be transferred to the Government for maintenance and revision responsibility.

3.1 REQUIREMENTS OVERVIEW
The purpose of this effort is the optimum integration of modern computer architectures and processors as commodity technologies to be applied to the current and emerging tactical operational requirements in the AH-1W. The Contractor shall, at a minimum, be required to integrate a solution that maintains current CDNU and ICU functionality and embeds BFSA, Moving Map, and VMF capabilities. PMA-276 requires a hardware solution constrained to the current physical dimensions of the CDNUs and ICUs, with the exception of the additional transceiver and antenna system for BFSA functionality, using a Real-Time Operating System (RTOS) open architecture software solution, written in modern, High-Order Language (HOL). The CCU project shall allow for collection of both qualitative and quantitative data. The data collected during Government ground and flight assessments shall be used to evaluate performance of the Contractor solution. Threshold Goals:
   

Current CDNU and ICU functionality. Embedded BFSA functionality. Moving Map functionality. VMF functionality.

3.2 THRESHOLD UPGRADED COCKPIT CONTROL SYSTEM (CCS) REQUIREMENTS
The integration of the proposed, upgraded CCS into the AH-1W shall require the Contractor to provide documentation for meetings, reviews, conferences, and to support PMA-276 in obtaining approval to install the system in the aircraft and obtain flight clearances for use in flight assessments. The Contractor shall: Page 8 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
    

Where feasible, utilize existing interfaces. Utilize an open hardware and software architecture framework. Minimize additional aircrew workload with new functionalities/capabilities. Minimize impact of obsolescence in vendor selection of system components. Ensure that the upgraded CCS is compatible with the OPNAVINST 4790 series maintenance philosophy and processes. Documentation shall be delivered IAW the Government approved System Engineering Plan (SEP), and shall include, but not be limited to: CDRLs A001A005, A007-A008, A030-A032, C001-C005, C007-C008, and C029-C031. This documentation shall support obtaining flight clearances. Deliver a final upgraded CCS Performance Specification and upgraded CCS Software Specification IAW CDRLs A006, B001, C006, and D001. Provide a written description of upgraded CCS expansion capabilities IAW CDRLs A029 and C028.







[CDRL A001, C001; Technical Report Study/Services: Theory of System Operation]; [CDRL A002, C002; Technical Report Study/Services: Operators Guide]; [CDRL A003, C003; Technical Report Study/Services: System Component Qualification Data and Reports]; [CDRL A004, C004; Technical Report Study/Services: Structural Analysis Report (SAR)]; [CDRL A005, C005; Installation Specification: Installation Data Package (IDP)]; [CDRL A006, C006; Technical Report Study/Services: System Performance Specification]; [CDRL A007, C007; Weight and Balance Report for Aircraft]; [CDRL A008, C008; Engineering Change Proposal (ECP)]; [CDRL B001, D001; Technical Report Study/Services: System Software Specification]; [CDRL A029, C028; Technical Report Study/Services: Expansion Capabilities];
[CDRL A030, C029; Developmental Design Drawings/Models and Associated Lists];

[CDRL A031, C030; Electrical Loads Analysis (ELA)]; [CDRL A032, C031; Interface Control Document (ICD)];

3.2.1 Upgraded Cockpit Control System (CCS)
The upgraded CCS shall act as the primary AH-1W controller for all embedded, realtime avionics. The Contractor shall deliver a functioning Operational Flight Program (OFP), written in a modern HOL, using a RTOS (e.g., vxWorks) that can be supported, modified, or otherwise maintained by Government software support activity engineers Page 9 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
and operational specialists. The source code files; RTOS; compiler and linker; tools to format, recreate and reload the OFP; and all files required to reproduce the software solution for the AH-1W (i.e., System Product Specification (SPS) IAW CDRLs B002 and D002) shall be delivered to the Government. The Government shall provide the awardee with the Cobra 3 OFP for the upgraded CCS. Cobra 3 constitutes the software baseline for the upgraded CCS development. Cobra 3 utilizes VxWorks as the RTOS and ANSI C as the programming language. The Contractor shall:


Ensure retention of all communication, navigation, display, and Built-In-Test (BIT) functionality associated with Cobra 3 System Configuration Set (SCS), with the addition of control over the new functionalities/capabilities or potential proprietary software modules. Ensure compatibility with Military Standard (MIL-STD) 1553 Multiplex Bus (MUXBUS) format. Ensure compatibility with existing ICDs, ARC-210 radio systems, Mission Data Loader (MDL), and Joint Mission Planning System (JMPS). Ensure compatibility with existing aircraft serial buses (e.g. RS-232/422/485; ARINC-429). Ensure greater than 50% throughput and memory available for future upgrades. Ensure OFP capable of being loaded via serial bus, Universal Serial Bus (USB), 1553 Data Transfer Module (DTM), and Memory Loader Verifier System (MLVS). Ensure that the BFSA, VMF, and Moving Map are capable of being reprogrammed into the FLASH memory through Ethernet, 1553 bus, and USB connectivity protocols. Ensure that the OFP shall be capable of being downloaded and run in Random Access Memory (RAM) simultaneously after system is powered up. Ensure that the OFP shall be capable of reporting internal status through one of the serial buses for debugging. Ensure that the OFP shall be able to be independently updated and reloaded without negative impact to the individual WRAs. Provide a system that captures all in-flight messages (i.e., variable messages). Provide a hardware and software architecture design that supports modular growth, with respect to additional devices and features. Provide plain text messaging format, BIT functionality on a “maintenance page” capable of avionic assembly monitoring, for use in diagnostics, as well as, a BIT description and fault isolation table. Description of the assessment procedures and environment used to verify the upgraded CCS functionality IAW CDRLs B003 and D003. Demonstrate ability to meet all applicable Information Assurance (IA) requirements and ensure the ability to declassify the AH-1W upon Operator departure. Page 10 10/30/2009







 









 







Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT


Prepare and provide a Software Development Plan (SDP) IAW CDRLs B004 and D004. Prepare and provide Software Resources Data Report (SRDR) IAW CDRLs B005-B006 and D005-D006 using the Contract Work Breakdown Structure (CWBS). Customized DD Forms 2630-2 and 2630-3 shall be submitted with a SRDR Data Dictionary.



[CDRL B002, D002; Software Product Specification (SPS)]; [CDRL B003, D003; Technical Report Study/Services: Upgraded CCS Functionality Assessment Procedures]; [CDRL B004, D004; Software Development Plan (SDP)]; [CDRL B005, D005; Software Resources Data Reporting: Initial Developer Report and Data Dictionary]; [CDRL B006, D006; Software Resources Data Reporting: Final Developer Report and Data Dictionary]

3.2.2 Blue Force Situational Awareness (BFSA)
Specific system and functional requirements the Contractor shall address in BFSA are:


The BFSA system shall be interoperable with the Force XXI Battle Command Brigade and Below – Blue Force Tracking (FBCB2-BFT) technology. The BFSA system shall be able to support FBCB2 hardware/software growth and change as the FBCB2-BFT technology matures.



NOTE: This note is for informational purposes only and shall not be construed as Government direction. The Government is aware that the FBCB2-BFT Satellite Upgrade Program Overview is being aggressively pursued to provide an upgraded satellite servicing network, waveform, data throughput, and message completion rates in order to upgrade the current FBCB2 L-band network. FY10 – FY13 is the targeted operational timeframe.


The BFSA system shall be capable of accepting position data from the Global Positioning System (GPS). The BFSA system shall be compatible with and capable of supporting current and future cryptologic devices for transmitting classified data and text.



NOTE: This note is for informational purposes only and shall not be construed as Government direction. The Government is aware that KGV-72, “aviation box, “ is being designed to meet Type 1 Encryption Device (TIED) requirement of the FBCB2 Operational Requirements Document (ORD), dated 26 March 2002. FY10 is the targeted fielding timeframe.


The BFSA system shall be able to send/receive friendly position location reports. At a minimum, the BFSA system shall provide 75% of the position location and survivability information within the aircraft‟s immediate battlespace (immediate battlespace is defined as a circular area surrounding the aircraft with a radius of 20 km) and 65% of the position location and survivability information within the Page 11 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
aircraft‟s extended battlespace (extended battlespace is defined as a circular area surrounding the aircraft with a radius of 20 km beyond the immediate battlespace).


The BFSA system shall support information exchange (i.e. transmit, receive, and display of preformatted messages and text) over the FBCB2 network, such as, but not limited to: Size, Activity, Location, and Time (SALT); SPOT Report; Engagement; Threat Warning; Nuclear, Biological, and Chemical (NBC1); Obstacle; Bridge; Position; Supply Point Status; Strike Warning; Contact; Call For Fire; Check Fire; Medical Evacuation (MEDEVAC); Mission Oriented Protection Posture (MOPP) Alert; Reconnaissance (RECON); Land Route; Free Text; Warning Order (WARNO); Fragmentation Order (FRAGO); Operations Order (OPORD); Overlays; Mayday/911. Data exchange using Joint Variable Message Format (JVMF) and tagged according to DOD Joint Technical Architecture (JTA) standard for tagged data items (e.g., Extensible Markup Language [XML]) is an objective. The BFSA system shall automatically update when new data is received and shall automatically track with the aircraft‟s movement to the upgraded CCS map display. The BFSA system shall allow operator input regarding time/distance criteria for automated position location/status (own) reporting. The BFSA system shall be capable of providing amplifying data about individually selected icons. The BFSA system shall automatically discriminate when identical reports with redundant information of the same entity are received and shall then display a single entity. The BFSA system shall allow the operator to be able to aggregate and display individual force entities into a group. Additionally, the operator shall be able to decompose these previously aggregated groups into individual entities. The BFSA system shall allow the operator to be able to select the type of data displayed by classes, de-clutter, and remove selected icons or classes of icons from the screen display. The BFSA system shall not report aircraft position location greater than 500 meters than actual aircraft position location. The BFSA system shall not cause failure or interference with of any other aircraft system or subsystem. Near real-time display of direct fire and lasing to facilitate target identification and orientation of direct fires in order to assist in preventing fratricide is a BFSA system objective.





















3.2.3 Moving Map Functionality
Specific system and functional requirements the Contractor shall address in their Moving Map are: Page 12 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT


System shall be an upgradeable digital moving map representative of existing digital map capabilities currently available on the market. System shall be able to display National Geospatial-Intelligence Agency (NGA) map products of various scales, including Compressed ARC Digitized Raster Graphics (CADRG) and Controlled Image Base (CIB). Map and imagery data shall be scalable based on user selected zoom factors. System shall be able to display mission data generated on the mission planning system (Portable Flight Planning System (PFPS) and JMPS) to include routes, waypoints, threats, targets, etc. System shall be able to display Digital Aeronautical Flight Information File (DAFIF) information to include airports, special use airspace, navigational aids and other ground references. System shall be capable of generating map symbols IAW MIL-STD-2525. System shall be able to support displaying and recording of pilot initiated weapon system target location designation marks on map display. Map symbols shall be declutterable based on symbol type and distance from own aircraft as selected by the user. Map symbols shall be scalable in size based on map zoom scale. System shall be able to provide terrain avoidance through graphical representation of terrain elevation based on Level 1 and Level 2 Digital Terrain Elevation Data (DTED). Map orientation shall be user selectable. Options shall include True North, Magnetic North and aircraft heading. Own ship symbol position on the display shall be user selectable. System shall be capable of providing top and side-view terrain presentation. System shall support post-mission analysis and reconstruction. System shall be able to save a snapshot of the map display, including all symbology, for postflight analysis. System shall be compatible with current and future AH-1W mission planning systems (PFPS, JMPS).













 



3.2.4 Variable Message Format (VMF) Functionality
Specific system and functional requirements the Contractor shall address in VMF are:


Capability to transmit, receive, display and manipulate data in support of Close Air Support (CAS) missions via the upgraded CCS in plain and secure modes of operation to and from multiple supporting arms elements using the aircraft‟s existing ARC-210 radio. Synchronized bit level implementation to be interoperable with the fielded Marine Target Location Designation and Handoff System (TLDHS). The VMF system shall support information exchange (i.e. transmit, receive, and display of and text) over the VMF network, such as, but not limited to: Aircraft On Station Report, CAS Aircrew Briefing (9-Line), Aircraft Departing Initial Point, Aircraft Final Attack Control, CAS Battle Damage Report, Free Text, Aircraft Page 13 10/30/2009





Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
Position / Target Designation, Request Aircraft Position / Target Designation, Air Close Air Support Request, Mission Request Rejection, CAS Request Acceptance, Free Text, and Tactical Imagery.


Providing multiple and operator selectable VMF waveforms via the upgraded CCS. Providing software re-programmable VMF waveforms at the O-level using existing loading devices and support equipment to ensure continuous interoperability with the TLDHS as VMF MIL-STD‟s 188-220, 2045-47001 and 6017 change. The VMF software shall reside separate from the OFP on a PC module to enable software re-programming outside of the SCS build cycle. Extending the communication via data link to not less than 15 nautical miles (nmi) for Very High Frequency (VHF) and 35 nmi for Ultra High Frequency (UHF).







NOTE: This note is for informational purposes only and shall not be construed as Government direction. The Government is aware that StrikelinkTM/A by Stauder Technologies is currently being assessed on the AV-8B with plans of being implemented on the AV-8B and FA-18/A-D. As implemented by Stauder Technologies, the StrikelinkTM/A solution is able to meet the upgraded CCS VMF functionality requirements and is currently the TLDHS fielded system software.

3.2.5 Hardware
Specific hardware requirements the Contractor shall address are:


The upgraded CCS physical dimensions shall not exceed the space currently occupied by the pilot and co-pilot‟s CDNU in the console and ICU#1 and ICU#2 in their current location. The upgraded CCS design shall not negatively affect aircraft weight and balance. A minimum of 30% expandability for future CCS capability upgrades, including new SRA insertion within the upgraded CCS. Utilize existing helicopter 28 volts DC power not to exceed 7.5 amps. Capable of sustained operations within temperature ranges between -20°C and 75°C, with cooling as required. IAW with MIL-STD-810 for engineering environment considerations. NOTE: Due to the AH-1W canopy design, the current CDNU experiences exposure to rain and dripping water. As such, the upgraded CCS shall be engineered to be capable of meeting the performance requirements during and after exposure to water and shall not experience any deterioration due to water exposure.

 

 



 

IAW with MIL-STD-461 and MIL-STD-464 for electromagnetic considerations. IAW with MIL-STD-1472 for human engineering considerations.

Page 14

10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT


IAW with MIL-L-85762 for Night Vision Imaging System (NVIS) compatibility considerations, including all displays, switches, selection keys, and additional lighting. Must be compatible with current MLVS loading standards set forth in "Requirements for Memory Loader/Verifier Multiplex Bus Interface with Avionic Systems" (MIL-STD-2217). Compatibility with the Next Generation MLVS is an objective. It is expected that the Next Generation MLVS will be required to support the following data bus protocols; MIL-STD-1553B Data Bus including Enhanced Bit Rate 1553 (EBR1553), Ethernet, Fibre Channel, USB 2.0, MIL-STD-2217, RS-232,RS-422 and any other emerging interfaces that allow the unit to load large OFPs. Installation utilizing wiring connections compatible with existing aircraft wiring or a harness for the upgraded CCS. Dimensionally maximized upgraded CCS display not greater than the existing CDNU faceplate, using color, sunlight readable, scratch resistant, flat-screen technology and capable of displaying National Television Standard Committee/Super Video Graphics Array (NTSC/SVGA) graphics or better. NOTE: The current CDNU experiences a blunt force associated with pilot/co-pilot entrance into the cockpit due to occasional „kicking”. As such, the display shall be sufficiently rugged to withstand such human factor and environmental considerations within the AH-1W environment.











Software-programmable, bezel selection keys for feature access; capable of being operated by a user wearing both summer-weight flight gloves and MOPP gloves. The upgraded CCS shall minimize the number of screens and manipulations while optimizing the number of button pushes required with most commonly used functions. Minimum of four selectable video input sources, independently operable by the pilot and co-pilot. The selectable video input sources shall be able to accept input from both internal and external video/sensor sources; such as the Night Targeting System Upgrade (NTSU), Digital Video Recorder (DVR), Tactical Video Data Links (TVDL); and display this imagery on the upgraded CCS display. Capable of accepting external keyboard device, operable by a user wearing both summer-weight flight gloves and MOPP gloves, via the front panel. The structural integrity of the AH-1W shall not be compromised by installation of the upgraded CCS and associated components.







3.3 PRE-PRODUCTION UNITS
The Contractor shall deliver and support installation of six complete upgraded CCSs on the AH-1W. One complete upgraded CCS shall consist of the pilot and co-pilot‟s upgraded CCS and associated components.

Page 15

10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
3.3.1 Pre-Production Unit Support

Successful and timely completion of ground and flight assessments shall require the Contractor to provide adequate pre-production unit assets/components of the proposed, upgraded CCS. The Contractor shall determine the number of pre-production unit assets/components that are needed to ensure that ground and flight assessments occur with minimal delays.

3.3.2

Laboratory Modification Installation

The Contractor, as the expert on the upgraded CCS, shall be available for consultation while modifying the H-1 China Lake, CA laboratory environment to utilize the upgraded CCS. The Government anticipates approximately eighty hours of Contractor effort for this task.

3.3.3

Aircraft Installation

The Contractor, as the expert on the upgraded CCS, shall deliver a proposed aircraft installation package. The Government, with technical assistance provided by the Contractor, shall route the proposed system package through the flight worthiness authority. The Contractor may be requested to provide additional drawings, schematics or other information necessary for PMA-276 to obtain the upgraded CCS flight certification and proposed system approval. The Contractor shall provide on-site technical assistance at China Lake, CA or Patuxent River, MD, during the installation of the upgraded CCS in designated AH-1W aircraft. Results of this task shall be used to create or revise the installation instructions.

3.3.3.1 Electric Power Compatibility
Electrical power requirements for the upgraded CCS equipment shall be compatible with the power characteristics of MIL-STD-704C. The upgraded CCS equipment qualification to a Government approved plan shall confirm compatibility with MIL-STD704C input power characteristics for all power system operations (Normal, Transfer, Protected/Abnormal, Emergency, and Engine Start). The upgraded CCS equipment shall not cause AH-1W electrical power characteristics to degrade beyond the limits of MIL-STD-704C and the aircraft demonstration shall confirm the upgraded CCS equipment compatibility with the AH-1W power system and other aircraft equipment during all operating conditions. Degraded performance is permitted during engine starts and abnormal power (protected) operation. The upgraded CCS equipment shall automatically resume full performance when normal power is restored. Unless otherwise specified in the upgraded CCS Specification, the upgraded CCS equipment shall provide full performance during emergency power operation (input voltage of 16 VDC to 30 VDC) and input power initialization circuits (warm-up time delay, BIT, etc.) shall not be activated/recycled by Engine Start low voltage transients (10 VDC to 16 VDC). Data loaded in non-volatile memory shall be retained during engine starts, momentary power interrupts (transfer operation), and abnormal power conditions. Page 16 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
3.3.3.2 Electromagnetic Compatibility
28 VDC power line spikes (less than 50 microseconds duration) generated/emitted by the upgraded CCS equipment shall not exceed +14 volts (positive spike) or -42 volts (negative spike). The upgraded CCS filtering of electrical input power shall be compatible with MIL-STD-461 requirements. Aircraft electrical grounding and bonding of the upgraded CCS equipment shall be IAW MIL-STD-464.

3.3.3.3 Audit and Certification of Private and Public Laboratories
The Contractor shall ensure that the Government has sufficient access to audit and certify all public and private laboratories conducting electric power interface assessments on the upgraded CCS equipment IAW NAVAIR Instruction 3080.1. Laboratories conducting MIL-STD-461 electromagnetic compatibility assessments on the upgraded CCS equipment shall be NVLAP certified IAW NAVAIR Instruction 2450.2.

3.3.3.4 Assessment Plan and Report
Each upgraded CCS equipment (WRA) must be individually assessed using a Government approved plan to confirm compliance with MIL-STD-704C. MIL-HDBK-704 Part 8 provides guidance on methods and procedures to confirm 28 VDC equipment compliance with MIL-STD-704 input power. The report shall include the results for each operating condition (Normal, Transfer, Protected/Abnormal, Emergency, and Engine Start). [CDRL A033, C032; Technical Report Study/Services: Electric Compatibility Assessment Plan and Report]

3.3.4

Ground and Flight Assessment Support

The Contractor shall provide on-site technical assistance and trouble-shooting for the proposed system during ground and flight assessment operations in a designated AH1W aircraft. Aircraft post-modification assessment shall consist of, but is not limited to, installation checkout and ground and flight functional-assessment of the AH-1W aircraft with the upgraded CCS installed, as well as other affected mission avionics subsystems. Post-modification assessment shall confirm the proper function, performance and maintainability of the upgraded CCS in the AH-1W aircraft. Collected data shall confirm that the upgraded CCS integration has not degraded performance of the AH-1W aircraft. Contractor support during the ground and flight assessment shall be documented in a Technical Report. [CDRL A00H, C00H; Technical Report Study/Services: Ground and Flight Assessment Support]

3.3.5

Pre-Production Unit Metrics

The Contractor shall gather data on this system to aid in successful support of the system upon transition to Government control and Fleet support. At a minimum, the Contractor shall gather and provide the projected and actual value for the items below Page 17 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
at each review. The data shall be presented for each WRA and summarized for the upgraded CCS.


Anomaly Identification: Characterization of the issue, system or software source, and potential impact to Government assessment and/or operational use. The metrics are to include items uncovered and not resolved prior to Government assessment, and those discovered during Government assessment. Failures: Characterization of the failure, Mean Time Between Failures (MTBF), Mean Time To Repair (MTTR).



[CDRL A00J; Technical Report Study/Services: Pre-Production Unit Metric Data]

3.3.6

Integrated Logistics Support (ILS)

The Contractor shall plan and conduct an ILS program, which shall govern the management of the ILS effort. The ILS program shall be conducted as an integral part of the process to define the range and depth of all the required support for the life of the contract, and address all applicable and related elements of logistics. [CDRL A00K, C00J; Management Plan] a. ILS Management: The Contractor shall manage the ILS efforts for the upgraded CCS and report to the PMA-276, Assistant Program Manager for Logistics (APML); Deputy APML; and Logistics Element Managers (LEMs). The Contractor ILS management team shall participate as members of the AH-1W CCU project ILS IPT. As a part of this function, the Contractor shall:


Provide timely responses to communications received from the Government related to ILS specific issues and communications addressed to logistics functional departments. Be an integral part of the AH-1W upgraded CCS (Government and Contractor) change process to ensure that logistics engineers review the drawings, and that Fleet supportability and maintenance practices, along with all Logistics elements are taken into consideration. Sustain communications with other qualified Contractors, sub-Contractors, and vendors, to ensure effective management of the program.





The Contractor ILS Management Team shall attend the AH-1W CCU project Maintenance Working Group, DMSMS Management Team (DMT), and ILS Working Group meetings. b. ILS Management Team/Integrated Product Team: A Joint Government/Contractor ILS Management Team/Integrated Product Team (ILSMT/IPT) shall be formed to continually assess the status of the CCU project ILS implementation. The ILSMT/IPT shall provide a means for coordinating logistics matters, schedules and SOW performance, ensuring adequacy and timeliness of Government inputs and action, and assisting the Government ILS manager in discharging their responsibilities. The Government will appoint a chairperson of the Page 18 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
ILSMT/IPT. Sub-teams or committees may be formed as necessary to continually assess such program elements. c. Integrated Logistics Support Process: The Contractor shall have a documented ILS process that identifies how the ILS elements will be used to meet the logistics support requirements for the upgraded CCS. The ILS process shall also assign responsibilities; generate milestones for executing the ILS program. The Contractor shall describe the process, involving both the Government and the Contractor, which shall be employed in planning, structuring, and acquiring the logistics resources for assessment support and operational support at all specified maintenance levels. The ILS process shall ensure the upgraded CCS, when fielded, will satisfy all the supportability criteria. The Contractor shall review and revise the Integrated Support Plan to reflect changes emanating from program changes, reviews and other actions affecting the logistics aspects of the program. The Contactor‟s program/process shall be available for Government review, upon request. The Contractor shall perform supportability analyses concurrent with the upgraded CCS performance requirements assessment and verification and ensure that operational requirements are achieved and ensure formation of optimum support resources. The Contractor shall perform these analyses IAW MIL-PRF-49506. The Government shall conduct a Logistics Management Information (LMI) Guidance Conference at the Post Award Conference (PAC)/System Requirements Review (SRR).

3.3.6.1 Logistics Management Information (LMI) Database
The Contractor shall prepare a LMI Data Summary that provides the source data for generating the upgraded CCS support system that considers all logistics elements required for Government flight assessment, interim support and in-service support; and all Supportability Analyses for the upgraded CCS as noted in the following subparagraphs and CDRLs. The Contractor shall perform and document analyses to support maintenance planning interface, repair analysis, supply support, support and test equipment, technical data, packaging/handling/storage and transportation, manpower, personnel, and training and computer resources support. The Contractor shall use the Technical Data Package, MIL-HDBK-502 and MIL-PRF-49506, as tailored in Attachments A through H, for guidance. [CDRL A00L, C00K; Logistics Management Information (LMI) Data Product]

3.3.6.1.1

Maintenance Planning Supportability Assessment Summary (SAS)

The Contractor shall prepare a Maintenance Planning SAS that identifies maintenance actions and related support structure that are aligned with the upgraded CCS requirements delineated in the performance documents and this SOW. This summary shall include all preventive and corrective maintenance actions, calibration requirements, required spare parts and support and calibration equipment, and those data elements specifically identified in Attachment B (Upgraded CCS Maintenance Planning Summary). The Upgraded CCS Maintenance Planning SAS shall be traceable to the Failure Modes Effects and Criticality Analysis (FMECA), Reliability Centered Maintenance (RCM) Page 19 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
Analysis, Level of Repair Analysis (LORA), the latest engineering drawings and existing maintenance practices. The Maintenance Planning Summary shall be generated IAW MIL-HDBK-502 paragraph 7.3.2. [CDRL A00M, C00L; Logistics Management Information (LMI) Summaries: Maintenance Planning]

3.3.6.1.2

Repair Analysis Supportability Assessment Summary (SAS)

The Contractor shall prepare a Repair Analysis SAS that stipulates the upgraded CCS components requiring repair or discard, the level of maintenance at which any repair action should be performed, and recommendations for influencing system construct. This summary shall also include those data elements specifically identified in Attachment C (Upgraded CCS Repair Analysis Summary) The contents of the Repair Analysis SAS shall be traceable to the FMECA, RCM Analysis, LORA, the latest engineering drawings and existing maintenance practices. The Repair Analysis shall be generated IAW MIL-HDBK-502 paragraph 7.3.3. [CDRL A00N, C00M; Logistics Management Information (LMI) Summaries: Repair Analysis]

3.3.6.1.3

Support and Test Equipment Supportability Assessment Summary (SAS)

The Contractor shall prepare a Support and Test Equipment SAS that provides data necessary to register, or verify the registry of any required upgraded CCS support or test equipment in the Government‟s inventory; calibration procedures; technical parameters; and any piece of support equipment required to support the upgraded CCS support equipment. This SAS shall also include those data elements specifically identified in Attachment D (Upgraded CCS Support Equipment Summary) The Support and Test Equipment SAS shall be generated IAW MIL-HDBK-502 paragraph 7.3.4. [CDRL A00P, C00N; Logistics Management Information (LMI) Summaries: Support and Test Equipment]

3.3.6.1.4

Supply Support Supportability Assessment Summary (SAS)

The Contractor shall prepare a Supply Support SAS that provides data to be used to determine initial supply requirements and the cataloging of these items to be procured through the provisioning process. This SAS shall include an upgraded CCS top down breakdown; source, maintenance and recoverability coding; maintenance replacement factors, overhaul rates; and those data elements specifically identified in Attachment E (Upgraded CCS Supply Support Summary) The Supply Support Summary shall be generated IAW MIL-HDBK-502 paragraph 7.3.5. [CDRL A00Q, C00P; Logistics Management Information (LMI) Summaries: Supply Support]

Page 20

10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
3.3.6.1.5 Manpower, Personnel and Training Supportability Assessment Summary (SAS)

The Contractor shall prepare a Manpower, Personnel and Training SAS that identifies the maintenance task details/steps, manpower estimates, personnel skill levels, maintenance levels and any recommended training required to perform the upgraded CCS preventive and corrective tasks identified in the Maintenance Planning SAS and Repair Analysis SAS. This SAS shall also include those data elements specifically identified in Attachment F (Upgraded CCS Manpower, Personnel and Training Summary) The Manpower, Personnel and Training Summary shall be generated IAW MIL-HDBK-502 paragraph 7.3.6. [CDRL A00R, C00Q; Logistics Management Information (LMI) Summaries: Manpower, Personnel and Training]

3.3.6.1.6

Packaging, Handling, Storage, and Transportation Supportability Assessment Summary (SAS)

The Contractor shall prepare a Packaging, Handling, Storage, and Transportation SAS that identifies packaging, handling and transportation information. This summary shall include information such as dimensions and weight of an item, the degree of packaging, and any special packaging, handling and storage instructions. This SAS shall also include those data elements identified in Attachment G (Upgraded CCS PHS&T Summary) The PHS&T Summary shall be generated IAW MIL-HDBK-502 paragraph 7.3.8. [CDRL A00S, C00R; Logistics Management Information (LMI) Summaries: Packaging, Handling, Storage, and Transportation]

3.3.6.1.7

Post Production Support Supportability Assessment Summary (SAS)

The Contractor shall prepare a Post-Production Support SAS that identifies Contractor unique and vendor unique components and/or parts of the upgraded CCS that could go out of production during the planned service life of the upgraded CCS. This SAS shall also include proposed alternative methods to ensure continued availability of any components and/or parts identified. This SAS shall also include those data elements specifically identified in Attachment G (Upgraded CCS Post Production Support Summary). The Post Production Support Summary shall be generated IAW MIL-HDBK502 paragraph 7.3.9. [CDRL A00T, C00S; Logistics Management Information (LMI) Summaries: Post Production]

3.3.6.2 Technical Manual Source Data with Illustrations
The Contractor shall provide source data for the upgraded CCS for the generation of technical manuals. Source data shall include illustrations of the system and its components suitable for use in Government technical manuals. All plain text source Page 21 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
data documentation shall be in Microsoft Word format. All illustrations and graphics shall be in Joint Photographic Experts Group (JPEG) format. [CDRL A014, C013; Technical Manual Research and Analysis Source Data]

3.3.6.3 Support Equipment (SE)
The Contractor shall identify, if necessary and after a thorough Engineering and LMI process, SE requirements via a Support Equipment Requirements Data (SERD). The SERD will be the principal recommendation and approval medium used for the SE required to support the upgraded CCS and shall be generated by the Contractor IAW the Joint Services SERD Handbook and mutually agreed to SERD ground rules. The Contractor shall submit SERDs within 120 days of the LMI process identifying the requirement for new or revised SE. [CDRL A019, C018; Special Equipment Tools and Test Equipment List]

3.3.6.4 Training
The Contractor shall generate the upgraded CCS training materials and conduct operator and maintainer training prior to commencement of Government flight assessment for the maximum of twelve operator and twelve maintainer students. Training course materials shall cover the upgraded CCS changes on AH-1W operation and maintenance procedures. The Contractor shall deliver the training course materials in the standard Center for Naval Aviation Technical Training (CNATT) format (AIM II). The training course packages shall include (but not be limited to) the following topics in detail:
 

Theory of operation. Illustrations and explanations of the uses and functions of all controls and indicators (including settings and readings, if possible). Step-by-step pre-flight performance procedures, system start-up/initialization procedures, normal operation procedures, and proper shutdown procedures. Step-by-step procedures and operation under emergency, adverse or abnormal conditions (if different than under normal conditions) and emergency shutdown procedures (if applicable). Step-by-step trouble shooting procedures. Step-by-step procedures for mission planning loading, including mission planning data and ground station interfacing.





 

Additionally, the Contractor shall provide cost estimates for an additional “initial training” class for a maximum of twenty students. Each student shall be provided all training materials. [CDRL A020, C019; Training Materials]

Page 22

10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
3.3.6.5 Maintenance Plan
The Contractor shall provide a three part Maintenance Plan. Part I shall be a summary of the system and shall include the items that make up the systems in a top-down indenture; Part II shall include item name, removal factors, Source, Maintenance, and Recoverability (SM&R) codes, Work Unit Codes (WUC), part numbers and stock numbers (if available) for all repairable items and maintenance significant consumables; Part III shall include fault isolation, repair, and test tasks with appropriate support equipment to perform the task at each maintenance level. The Maintenance Plan shall be traceable to the Maintenance Planning, Repair Analysis and Support Equipment SASs. The Government will approve the content and format of the Maintenance Plan after a formal Maintenance Plan Review is completed. [CDRL A021, C020; Maintenance Support Plan]

3.3.6.6 Engineering Data for Provisioning (EDFP)
The Contractor shall provide the EDFP in Portable Document Format (PDF). Repairable assemblies obtained from vendors/subcontractors shall be provided in the same manner. EDFP shall be submitted in Top-Down breakdown sequence and shall include all Government approved repairable items and maintenance significant consumables. The EDFP shall be traceable to the Supply Support SAS and be IAW the Provisioning SOW. [CDRL A022, C021; Supplemental Data for Provisioning (SDFP)]

3.3.6.7 Interim Support Items List (ISIL)
The Contractor shall provide the ISIL of recommended spares and quantities in support of the upgraded CCS. The ISIL items shall be developed based on the specified “O”, “I” and “D” level maintenance practices and shall be in Contractor format. The ISIL shall include part number, item name, SM&R codes, Commercial and Government Entity (CAGE) codes, MTBF, and quantity per end item, unit price, production lead time, shelf life, quantity per aircraft, next higher assembly, and recommended quantity. The ISIL shall be traceable to the Supply Support SAS. [CDRL A023, C022; Logistics Management Information (LMI) Data Product: Interim Support Items List (ISIL)]

3.3.6.8 Provisioning Parts List (PPL)
The Contractor shall provide a PPL including all applicable items (prime, vendor, U.S. Government Standards and Industry Standards) contained in the upgraded CCS. The PPL shall be provided IAW the Provisioning SOW. [CDRL A024, C023; Logistics Management Information (LMI) Data Product: Provisioning Parts List (PPL)]

Page 23

10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
3.3.6.9 Packaging, Handling, Storage, and Transportation (PHS&T)
The Contractor shall provide the PHS&T recommendations for the upgraded CCS to identify new packaging, handling, storage and transportation requirements. The PHS&T requirements shall be traceable to the PHS&T SAS. [CDRL A025, C024; Packaging Plan]

3.3.6.10 ILSMT/IPT Meetings
In conjunction with each System Review, Program Review and IPR, the joint ILSMT/IPT shall meet to review ILS program progress as a minimum, the agenda shall provide for status reporting, analysis of problem areas, analysis of schedules and proposed changes to the ILS program. Each open agenda item shall have a completion date and the action officer responsibility shall provide status at subsequent meetings. [CDRL A00V, C00U; Conference Minutes]

3.3.6.11 Maintenance Plan Review
The Contractor shall host one Maintenance Plan Review. Review will be held at the Contractor‟s facility. [CDRL A00V, C00U; Conference Minutes] The Maintenance Plan

3.3.6.12 Reliability and Maintainability (R&M) Program
The Contractor shall provide and continually assess a comprehensive R&M program to ensure the upgraded CCS meets the R&M standards set forth in the performance specification. The proposed system shall be reviewed throughout the entire period of performance to identify and assess any changes, which would impact reliability or maintainability. The Contractor shall generate R&M analyses and predictions as required to ensure compliance with the performance specification. The program shall encompass all aspects of R&M with respect to selection of components, predictions, and sensitivity analysis. The Contactor shall keep up and make available to the Government all R&M data on any vendor or subcontractor supplied item and shall inform the Government of any part or component, which will degrade system R&M requirements. [CDRL A00W, C00V; Reliability & Maintainability (R&M) Program Plan]

3.3.6.13 Reliability and Maintainability (R&M) Predictions
The Contractor shall provide detailed system R&M predictions based on a defined configuration and associated models. The predictions shall be allocated down to the lowest indenture level and revised each time significant system or mission profile changes significantly impact the upgraded CCS or any subsystems. The reliability modeling method shall mathematically relate to the reliability block diagram of the upgraded CCS. [CDRL A00X, C00W; Maintainability Predictions Report]; Page 24 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
[CDRL A00Y, C00X; Reliability Prediction and Documentation of Supporting Data]

3.3.6.14 Maintainability
The upgraded CCS shall be removable and repairable at the “O” Level of Maintenance by replacing WRAs. The upgraded CCS shall not impact the existing scheduled maintenance requirements of the aircraft. No special tools or fixtures shall be required for installation, removal or repair of the upgraded CCS. [CDRL A00Z, C00Y; Maintainability Program Plan]

3.3.6.15 Failure Reporting, Analysis, and Corrective Action System (FRACAS)
The Contractor shall provide for a failure/fault reporting, analysis and corrective action program. The Contractor‟s reliability program shall use the formal failure reporting, analysis, and corrective action system. Failure reports and failure analyses shall be initiated for all Environmental Stress Screening (ESS), flight assessment, reliability analysis, module/WRA manufacturing and acceptance failures. The Contractor‟s failure report, failure analysis forms, operational data measurement and metric reporting shall be addressed as part of the reliability program. The Contractor shall deliver a report of all faults, failures and the corrective actions quarterly. [CDRL A010, C00Z; Failure Analysis and Corrective Action Report]

3.3.6.16 Failure Modes Effects and Criticality Analysis (FMECA)
The Contractor shall conduct a FMECA to identify potential system weaknesses and failure modes in system components. The Contractor shall identify all potential failure modes for the proposed upgraded CCS design, the effect and severity of each failure mode, and the criticality of each failure based on severity and probability of occurrence. The Contractor shall propose compensating provisions to minimize the likelihood or eliminate the effects or severity for the identified failure modes. The FMECA shall be in sufficient detail to allow a LORA to be performed. [CDRL A011, C010; Failure Mode Effects, and Criticality Analysis Report]

3.3.6.17 Reliability-Centered Maintenance (RCM) Analysis
The Contractor shall conduct a RCM Analysis using a decision tree process based on the information generated by the FMECA. A complete analysis of each Functional Significant Item and its assigned failure modes shall be conducted. The results of the analysis will be used by the Government to decide which preventative maintenance tasks should be pursued to support the system. [CDRL A012, C011; Technical Report Study/Services: Reliability-Centered Maintenance (RCM)]

Page 25

10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
3.3.6.18 Level of Repair Analysis (LORA)
The upgraded CCS maintenance model identifies the desired levels of maintenance and the depth of maintenance activities to be implemented. In order to confirm this model, a LORA shall be performed. The LORA shall be conducted to generate an optimized maintenance philosophy for the upgraded CCS and it‟s components based on economic and non-economic rational to aid the Government in determining the maintenance level optimally suited to perform repair actions and the extent and depth of those repair actions. The economic objective of the upgraded CCS LORA is to determine the optimum cost of repair of the upgraded CCS by taking into consideration all associated support cost drivers that would be required at each level of maintenance. The Government will provide specific USN/USMC cost data to the Contractor. The LORA economic analysis shall focus on the following major cost drivers that provide life-cycle cost and system data:


Inventory costs to include administration, attrition, transportation, storage and handling. SE costs to include the cost of providing the unique or new SE for completing a particular upgraded CCS task at a given level of maintenance. Space - required for inventory. Labor cost - the associated cost for personnel to complete each repair task. Training cost - the cost for upgrading and providing the necessary training to personnel performing a maintenance task at a given maintenance site and/or shop. Documentation - the cost for generating the required documentation for each of the maintenance options.



  



The LORA non-economic algorithms shall include: expected operational life, operational profile, site data, reliability and maintainability objectives and thresholds, predicted repair times, procurement lead times, and any other requirements or constraints that will affect the repair/discard decision process. The Government shall provide necessary data for Government procurement lead times and site data. Sensitivity analysis shall also be performed as part of the LORA process by varying different elements to determine their impact on recommended maintenance models and provide critical input to a system‟s overall design process. [CDRL A013, C012; Technical Report Study/Services: Level of Repair Analysis (LORA)]

3.3.6.19 Field Maintainability Article (FMA) Demonstration
The Contractor shall support the Government conducted FMA Demonstration to confirm the ability of maintenance personnel to perform all identified and documented inspections, scheduled and unscheduled maintenance, calibration and repair tasks consistent with the upgraded CCS Maintainability objectives and Supportability Page 26 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
requirements specified in this document and identified in the LMI Data and SASs. Contractor support of the FMA demonstrations shall include one complete upgraded CCS in post-qualification/pre-PCA configuration to support the demonstration; any required detailed maintenance task descriptions for inspection; any required removal, replacement, calibration and repair tasks; and identification and provision of any required replacement parts and support and calibration equipment other than hand tools. The demonstration will take place at either MCAS Pendleton or New River. The Contractor shall provide training prior to the FMA demonstration to the Government personnel who shall conduct the demonstration. Training shall be conducted at the designated FMA demonstration site. The Contractor shall generate training requirements that utilize existing USMC skill specialties, training equipment and materials, and training programs as appropriate. The training event is anticipated to require four to eight hours.

3.3.6.20 Obsolescence Management / Diminishing Manufacturing Sources & Material Shortages (DMSMS)
The Contractor shall review sources of information such as the Government Industry Data Exchange Program (GIDEP) Diminishing Manufacturing Source (DMS) notices and supplier notifications for applicability of the hardware being delivered. DMSMS Guidebook, SD-22 should be used as a reference. The Contractor shall provide microelectronic management and obsolescence avoidance by conducting engineering technology assessments of the upgraded CCS hardware. The result of the assessments will provide an understanding of the current microelectronic status of the systems, the scope of any immediate non-availability, obsolescence problem, and magnitude of future problems and possibilities for alleviating the impact to the program. Examples: alternative manufacturing, redesign, substitution, emulation, and life-of-type buy. [CDRL A015, C014; Source Data for Forecasting Diminishing Manufacturing Sources and Material Shortages (DMSMS)]

3.3.6.21 Notification
The Contractor shall identify alternate sources, replacement parts, or optional part numbers for parts and materials that become or will become obsolete and will revise the assembly drawings to incorporate the new information. If a direct replacement is not available or possible, the Contractor shall notify the Government in writing through the contracting officer. The Contractor shall proactively identify and document the availability and the obsolescence or DMS of all parts and materials used to produce and support the AH-1W aircraft in a System Problem Report. The report shall include all obsolescence issues identified by Contractor and its subcontractors. Any nonrecurring effort associated with generating and/or qualifying replacement components and subsystems shall be separately contracted. Recurring costs shall be addressed once the replacement component/subsystem has been introduced for the production line. [CDRL A016, C015; System Problem Report (SPR)] Page 27 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
3.3.6.22 Unique Identification (UID)
The AH-1W UID implementation plan dated 30 May 2005 has been generated to provide a roadmap to meet OUSD (AT&L) direction for full implementation of UID within DoD by FY10. This plan identifies the strategies, organizational structures, timeframes, and resources required to meet UID requirements in a cost effective manner consistent with OSD policy. The upgraded CCS will be marked and registered IAW Phase III of the AH-1W UID implementation schedule. This phase will follow successful completion of OT. The Contractor shall place a DoD UID compliant symbol, per DFARS 252.211-7003 Clause “Item Identification and Valuation (June 2005)” as prescribed at DFARS 211-274-4 IAW MIL-STD-130. [CDRL A017, C016; Technical Report Study/Services: Unique Item Identification Report]

3.3.6.23 Bill of Materials (BOM)
The Contractor shall submit an indentured BOM for production lot configurations to the piece/part level for all upgraded CCS electrical/electronic piece/parts installed in all Contractors furnished electrical, electronic and avionics assemblies and subassemblies and components, including subcontractor and vendor items, as well as related Peculiar Support Equipment (PSE). All repairable items and any Maintenance Significant Consumables (MSCs) shall be included on the list and identified as such. [CDRL A018, C017; Source Data for Forecasting Diminishing Manufacturing Sources and Material Shortages (DMSMS): Bill of Materials (BOM)]

3.4 DESIGN RIGHTS ISSUES
The Contractor shall identify any hardware, software, and technical data rights proposed for use in the design for which the Government may not have unrestricted rights. For those items that have significant impact on cost, readiness or supportability, the Contractor shall identify the specific item(s). It is the intention of the Government to have Government Purpose Rights for the core upgraded CCS software. Unrestrictive rights to the core upgraded CCS software application make this a high priority key performance parameter selection criteria. For clarification, the core upgraded CCS software application and its parameter for unrestrictive rights does not mean an Offeror cannot propose proprietary software for other software functional modules, nor does this mean the Government expects to procure unrestrictive rights to the proposed operating system software. Functional modules which may be expected to bring proprietary restrictions include the BFSA, Moving Map, VMF functionality, and potentially others, which are dependent upon optimum Contractor software integration.

3.5 COPYRIGHTS ON DOCUMENTS AND MANUALS
PMA-276 shall have authority on all software, manuals and documentation, thus allowing the Government to have the capability to revise all manuals and documentation for insertion and use in AH-1W manuals, documentation and training manuals. Page 28 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
The Contractor shall provide to the Government with fully dimensional product level drawings for the upgraded CCS. The Government shall have full data rights to review and print the drawings in support of activities to include but not limited to engineering investigations, Technical Publication Deficiency Reports (TPDR), ECPs, and maintenance.

4 PROGRAM MANAGEMENT REQUIREMENTS
The Contractor shall establish and continually provide an effective program management capacity as outlined in the paragraphs below.

4.1 INTEGRATED MASTER SCHEDULE (IMS)
The Contractor shall generate and keep up an Integrated Master Schedule (IMS) as part of the CCU project. The Contractor taskings shall be able to be cross-referenced between the IMS and CWBS. The IMS shall be used as the primary document for tracking program activity and schedule. The IMS shall be updated monthly to include the program inputs made by the Contractor and the Government. Program deliverables shall be scheduled in the IMS with initial target dates allowing adequate time for program activities to meet the CCU project period of performance. Project maturity shall dictate actual delivery dates for program deliverables and shall be fully coordinated between the parties and approved by the Government. The Contractor shall prepare a contract performance report (CPR) and a Contract Funds Status Report (CFSR). The Contractor shall update the proposed IMS. [CDRL A009, C009; Contract Performance Report (CPR)]; [CDRL A00A, C00A; Contract Funds Status Report (CFSR)]; [CDRL A00B, C00B; Integrated Master Schedule (IMS)]

4.2 CONTRACT WORK BREAKDOWN STRUCTURE (CWBS)
The Contractor shall generate and keep up the CWBS/Contractor Cost Data Reporting Plan and WBS dictionary using MIL-HDBK-881 for guidance. The CWBS shall provide the basis for further extension by the Contractor to lower levels during the performance of the contract. The Contractor shall extend the CWBS to the appropriate level required to provide adequate internal management, surveillance, and performance measurement, regardless of the reporting level stipulated in the contract for Government visibility. The Contractor shall use the CWBS as the primary framework for contract planning, budgeting, and reporting of the cost, schedule and technical performance status to the Government. The Contractor shall analyze the system requirements generated and translate them into a structure representing the products and services that comprise the entire work effort commensurate with the acquisition phase and contract requirements. The Contractor's team or organizational entity responsible for the systems engineering of the system shall prepare the technical elements of the extended CWBS. The Contractor shall update the CWBS during the execution of the contract. Changes to the CWBS or associated definitions at any reporting level shall require approval of the Government. The Contractor shall also provide a matrix identifying the contract line item and SOW paragraphs applicable to each CWBS element. The CWBS shall be the basis Page 29 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
for planning, monitoring, reporting, and controlling cost, schedule, and technical performance. [CDRL A00C, C00C; Contract Work Breakdown Structure (CWBS)]

4.3 PROGRAM MANAGEMENT PLAN (PMP)
The Contractor shall generate a PMP that shall provide insight into its experience and business practices in relation to the applied strategy in successfully designing and producing the upgraded CCSs, and the major Program Events (PE) and milestones associated with the CCU project. The PMP shall outline the significant accomplishments that must be completed in order to make each PE successful, and the criteria by which the successful completion of each accomplishment shall be measured. The plan shall provide the blueprint for planning, direction, control and execution to produce the upgraded CCS within cost, schedule, and the proposed hardware and software specifications. The PMP shall cross reference the SOW and the IMS within the document. [CDRL A00D, C00D; Management Plan: Program Management Plan (PMP)]

4.4 SYSTEM ENGINEERING PLAN (SEP)
The Contractor shall generate, implement, keep up, and revise a SEP (formerly, System Engineering Management Plan (SEMP)), using the Naval Systems Engineering Guide as guidance, documenting the CCU project‟s current and evolving systems engineering strategy and its relationship with the overall program management effort. The SEP shall serve as guidance in all technical aspects of the program and shall correlate to the generated IMS. Planning activities shall include, at a minimum, requirements management, subcontractor coordination, metrics plan, engineering planning cycle to be used in the upgraded CCS engineering, risk management practices and mechanisms for controlling resources and schedule. [CDRL A00E, C00E; System Engineering Plan (SEP)]

4.4.1 Configuration Management (CM)
The Contractor shall be responsible for the generation and implementation of a Configuration Management (CM) approach, using MIL-HDBK-61A and NAVAIRINST 4130.1 as guidance, that provides Configuration Identification (CI), Configuration Control, Status Accounting, and auditing of CIs. The Contractor‟s CM approach shall be documented (or referenced) in the SEP. The Contractor CM approach shall include:


Identification of processes for drawings, schematics, documents, software, firmware, and media. Interface change control. A process for reporting anomaly status to closure. Ascertain and reporting of baselines, and changes to the baselines. Generation of a Version Description Document (VDD) to be provided with each baseline delivery. Page 30 10/30/2009

   

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT


Storage, handling and delivery of media.

[CDRL A028, C027; Contractor's Configuration Management Plan (CCMP)]

4.4.1.1 Engineering Change Proposal (ECP)
The Contractor shall generate and submit an ECP for the creation and integration of the upgraded CCS. MIL-HDBK-61A provides guidance concerning the Classification of ECPs.

[CDRL A008, C008; Engineering Change Proposal (ECP)]

4.4.1.2 Request For Deviation (RFD)
The Contractor shall process Requests for Deviation (RFD) from current approved configuration documentation. Authorized deviations are a temporary departure from the requirements and do not constitute a change in an approved baseline. Submission of recurring deviations is discouraged and shall be minimized. Where it is determined that a change should be permanent, the Contractor shall process an Engineering Change Proposal. RFDs shall be prepared using ANSI/EIA 649/ISO10007, contractually identified DIDs and MIL-HDBK-61A as guides. Additionally, the MIL-HDBK-61A provides guidance concerning the classification of RFDs. As a minimum, the RFD shall contain the following information: (a) Date prepared; (b) Originator; (c) RFD Classification (critical, major or minor); (d) Designation for deviation (model/type, CAGE code, system designation, and deviation number); (e) Class of deviation; (f) Part Number affected; (g) Cost/Price data; (h) Effectively; (i) Description of deviation; (j) Need for deviation; (k) Effect on delivery schedule; (l) Recommended corrective action; and (m) Alternatives evaluated. [CDRL A026, C025; Request For Deviation (RFD)]

4.4.2 Data Management (DM)
The Contractor shall be responsible for the generation and implementation of a Data Management (DM) approach that provides a systematic approach for controlling the data products called for in this SOW, to include the DAL. Contractor data, not specifically required by another CDRL, generated in performance of the contract shall be available and provided as part of the DAL. The Contractor‟s DM approach shall be documented (or referenced) in the SEP. The Contractor DM approach shall include:
     

A single point of contact for all incoming and outgoing data items. A process for delivering software media. Generation and keeping up of a distribution list. Access control mechanisms. Account keeping for all deliveries. Data security and classification management.

[CDRL A027, C026; Data Accession List (DAL)]

Page 31

10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
4.4.3 Quality Assurance (QA)
The Contractor shall be responsible for the generation and implementation of a Quality Assurance (QA) approach that promotes confidence in the products and processes used to generate the data products called for in this SOW. The Contractor‟s QA approach shall be documented (or referenced) in the SEP. The Contractor QA approach shall include:
  

Objective evaluation of products and processes. A process for recording, statusing and elevating items requiring corrective action. Reporting data on QA findings.

4.4.4 Subcontractor Management
The Contractor shall be solely responsible for the performance and quality of all subcontractor work performed in response to the requirements of this contract. The Contractor shall identify and continually assess significant technical, quality, schedule, and milestone achievement on a continuing basis, according to the Contractor's own established subcontract management techniques. The Contractor shall be responsible for ensuring all Program Management activities stated in Section 4. The Contractor shall make provision for Government representatives to participate in subcontractor visits, technical working groups and reviews, and to observe work in progress when requested by the Government. Ten days advance notice shall be given to the Government‟s designated representative, prior to the planned subcontractor program. The Contractor‟s subcontractor management approach shall be documented (or referenced) in the SEP.

4.5 PROGRESS REPORTING
The Contractor shall host bi-weekly (i.e., once every other week) telephone or video conferences with the Government at mutually agreed upon dates and locations with video and/or teleconference availability. The Government and the Contractor shall mutually establish the agenda for each meeting to ensure it covers all the critical issues and the conference will be limited to not more than two hours. During these reviews, the Contractor shall present integrated cost, schedule, technical performance and risk status. Progress shall be reported in the Contractor‟s Progress, Status and Management Report [Monthly Status Report (MSR)]. [CDRL A00F, C00F; Status Report: Monthly Status Reports (MSR)]

4.6 REQUIREMENTS TRACEABILITY MATRIX (RTM)
The Contractor shall substantiate the proposed system with a Requirements Traceability Matrix (RTM) that organizes, presents, and provides a comprehensive rationale for the relationship between requirements and capabilities. The RTM uniquely identifies program requirements to ensure that the requirements can be traced and confirmed through the engineering phases. [CDRL A00G, C00G; Technical Report Study/Services: Requirements Traceability Matrix (RTM)]

Page 32

10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
4.7 SECURITY
The efforts required for this SOW are expected to be UNCLASSIFIED and should not require the Contractor personnel to obtain a security clearance. However, if the tasking performance requires access to classified data, a security clearance of SECRET shall be required for all personnel having access to the classified data and a DD Form 254 shall be submitted. Contractor personnel shall not release or remove system documentation, data, or reports generated by or through the use of Government systems. All requests for information shall be forwarded to PMA-276. PMA-276 shall assist the Contractor personnel in processing the necessary DoD forms to obtain base or area badges for access to Government facilities.

4.7.1 Data Access
The Contractor shall not divulge any information regarding files, data, processing activities/functions, user ID's, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. Contractor personnel shall abide by all Government rules, procedures, and standard of conduct. Contractors requiring access to Government Automated Information Systems (AIS) shall have background investigations and security awareness training completed prior to the start of contract performance. When the period of performance is complete or Contractor personnel leave work on this project, they shall have five working days to terminate all their network user account and to return all access cards and base identification badges.

4.7.2 Government Facility Access
Access to Government facilities is limited. The Contractor shall coordinate required access/usage times and dates through PMA-276 approximately thirty working days prior to the need date. Failure to notify required Government Facility access within thirty working days prior to the need date may result in delayed Government Facility access. Control of the facilities shall remain with the Government.

4.8 GOVERNMENT-FURNISHED EQUIPMENT, MATERIALS, SOFTWARE, AND INFORMATION
All Government-Furnished Equipment (GFE), Government-Furnished Software (GFS), Government-Furnished Material (GFM), and Government-Furnished Information (GFI) shall be returned to the Government upon completion of this contract. At the end of this project, the Contractor shall return the GFE to the Government in its original condition.

4.9 SAFETY
The Contractor shall comply with all safety provisions, e.g., technical specifications, technical publications, Federal Occupational Safety and Health Standards (Title 29 CFR. Part 1910). If there is no applicable Occupational Safety and Health Administration (OSHA) standard, use other applicable nationally recognized sources of safety, health, and fire prevention standards referenced in the work requirements of this contract. Page 33 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
The Contractor shall protect Government property to prevent damage during the period of time the property is in the possession of the Contractor. The Contractor shall report promptly to the Administrative Contracting Officer (ACO) all available facts relating to each instance of damage to Government property. When a major mishap ($10,000 or more) involving Government property occurs, the Contractor shall immediately secure the accident scene and the damaged item until released by the accident investigative authority as designated by the contracting (PMA276) Safety Office. Such release shall be accomplished by the ACO. If the Government elects to conduct an investigation of the accident, the Contractor shall cooperate fully and assist Government personnel until the investigation is completed. The Contractor shall include a clause in each of its subcontracts requiring subcontractor cooperation and assistance in accident reporting and investigation.

5 PROGRAM REVIEW REQUIREMENTS
The Contractor shall conduct the program reviews outlined below. For each review the Contractor shall document attendees, action items, decisions made, and provide them to the Government.

5.1 PROGRAM MANAGEMENT REVIEW (PMR) AND TECHNICAL INTERCHANGE MEETINGS (TIM)
The Contractor shall conduct either a PMR or TIM when requested by the Government or as required. At each PMR, the Contractor shall report progress and work status to the Government and shall address: risk management issues and activities including the current Project Watchlist; any changes in the approaches presented in plans or foreseeable delays and associated schedule recovery actions; and any changes in the Contractor‟s and subcontractors‟ organizations. The Government anticipates a need for four reviews to coordinate technical interfaces for the CCU project. [CDRL A00U, C00T; Conference Agenda]; [CDRL A00V, C00U; Conference Minutes]

5.2 POST AWARD CONFERENCE (PAC)/SYSTEM REQUIREMENTS REVIEW (SRR)
The Contractor shall conduct a PAC/SRR within thirty calendar days after award of contract. The objective is to ensure understanding of the scope of effort and an understanding of system requirements, and the formation of milestones and communication guidelines. The Contractor shall generate and present a system level functional baseline that traces to functional requirements in this SOW. The Contractor shall summarize their proposed project structure, key personnel, IMS, and risks in a presentation. Additionally, the preliminary hardware and software system specifications shall be provided at this time. [CDRL A00U, C00T; Conference Agenda]; Page 34 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
[CDRL A00V, C00U; Conference Minutes]

5.3 INTEGRATED BASELINE REVIEW (IBR)/PRELIMINARY DESIGN REVIEW (PDR)
The Contractor shall hold an IBR/PDR at the Contractor facility when appropriate based on project maturity (approximately ninety calendar days following contract award). The IBR/PDR shall be determined based on the program maturity as defined in the IMS. The IBR/PDR shall include each equipment, hardware, and software configuration items and related peculiar support equipment. The Contractor shall review its performance measurement baseline plan with the Government, show that the selection of materials, lead times, tooling, fabrication techniques, assembly methods, test equipment, skills, processes, and inspection techniques have been accomplished for each equipment, hardware, and software configuration items and related support equipment, and the producibility objectives have been achieved. At this review, the Government will assess the progress, technical adequacy, and risk resolution (on a technical, cost, and schedule basis) of the proposed system and will assess the technical risk associated with the selected manufacturing (assembly) methods (processes). The Contractor will ensure that the baseline includes the entire contract technical scope of work consistent with the contract schedule requirements and has adequate resources assigned. Technical performance metrics shall also be reviewed. The IBR/PDR shall be used to achieve a mutual understanding of the baseline plan, cost and schedule risk, and the underlying management processes used for planning and controlling the project. The IBR/PDR also shall identify all single source, sole source, and diminishing source(s). Follow-on IBRs shall be required following major changes to the baseline. [CDRL A00U, C00T; Conference Agenda]; [CDRL A00V, C00U; Conference Minutes] Entry Criteria a. A PAC/SRR has been successfully completed, and all Request For Actions have been responded to. b. A preliminary agenda has been coordinated (nominally) thirty days prior to the IBR/PDR. c. IBR/PDR technical products for each system hardware and software configuration item have been made available to the cognizant IBR/PDR participants prior to the review. d. Revised system specifications. e. Preliminary subsystem specifications for each configuration item (hardware and software), with supporting tradeoff analyses and data, as required. The preliminary software specification must include a completed definition of the software architecture, and a preliminary database description is applicable. f. Revised risk assessment. g. SEP changes (if any). h. Revised logistics documentation. i. Revised Human Systems Engineering related documentation (if required). Exit Questions Page 35 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
a. Does technical effort and proposed system indicate successful full system integration and aircraft demonstration assessment criteria can be met? b. Does preliminary system satisfy full system integration, validation, and verification requirements? c. Does the status of the technical effort and proposed system indicate Operational Evaluation (OPEVAL) success (operationally suitable and effective)? d. Are the risks known and mitigated for DT / OT? e. Is the approved CWBS and functional system allocation to subsystem level set up and documented to enable proceeding with proper CM? f. Are the program and technical risks known and documented? g. Are adequate processes and metrics in place for the program to succeed? h. Have Human System Engineering factors been reviewed and included, where needed, in the overall system? i. Is the program executable within existing budget, resources, and timeline? j. Is the software functionality, in the approved allocated baseline, consistent with the updated software metrics and resource-loaded schedule? k. Has all logistical documentation been provided? l. The IBR/PDR is considered complete when all draft Request For Actions (RFAs) are signed off, and an acceptable level of program risk is ascertained.

5.4 CRITICAL DESIGN REVIEW (CDR)
The Contractor shall conduct a CDR at the Contractor facility when appropriate based on project maturity (approximately nine months following contract award). The CDR shall be determined based on the maturity of the system‟s technical baseline as described in the System Specifications and program maturity defined in the IMS. The CDR shall present a final system that incorporates all deficiencies identified from the IBR/PDR. The CDR shall be a detailed review of the system for the upgraded CCS and all data items required by the contract. The Contractor shall provide a trace capable of demonstrating the system furnished at CDR implements the performance requirements of the CCU project, and present the processes used in validation and verification of the system. An assessment of the results of producibility analyses conducted on system hardware shall be made to ensure detailed producibility design solutions satisfy the established requirements. [CDRL A00U, C00T; Conference Agenda]; [CDRL A00V, C00U; Conference Minutes] Entry Criteria a. An IBR/PDR has been successfully completed, and all IBR/PDR Request For Actions have been responded to. b. All IBR/PDR exit criteria key issues have been satisfied, if applicable. c. A preliminary agenda has been coordinated (nominally) thirty days prior to the CDR. d. CDR technical products (hardware and software elements of the product baseline to be reviewed and approved at the CDR) have been made available to the cognizant CDR participants prior to the review. e. Final specifications for each hardware and software configuration item. f. Current risk assessment. Page 36 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
g. h. i. j. k. SEP changes (if any). CPR and CFSR changes (if any). Revised logistics documentation. Are the Software Documents complete and ready to be placed under CM? Are the preliminary assessment procedures for Software Integration and Systems assessment available for review?

Exit Questions a. Does technical effort and proposed system indicate successful full system integration (accomplished by flight assessment and installation validation and verification) can be met? b. Does the status of the technical effort and proposed system indicate OPEVAL success (operationally suitable and effective)? c. Does design satisfy demonstration of full system integration requirements? d. Has the system product baseline been established and documented to enable hardware fabrication and software coding to proceed with proper CM? e. Approved CWBS? f. Engineering drawings and documentation approved. g. Has the proposed system satisfy Human Systems Engineering requirements? h. Are the program and technical risks known, documented, and mitigated? i. Is the program executable within existing budget, resources, and timeline? j. Have all logistic document requirements been met? k. Are adequate processes and metrics in place for the program to succeed?

6 TRAVEL REQUIREMENTS
The Contractor shall be required to travel to support the objectives of this SOW. Travel destinations shall include: China Lake, California; Cherry Point, North Carolina; and Patuxent River, Maryland. However, at this time, travel frequencies and durations are not known. For purpose of the proposal, use an estimate of $30,000. The Contractor shall obtain approval from the Government Integrated Product Team Lead (IPTL) five working days in advance before traveling. Airfare for travel and per diem shall be billed IAW Joint Travel Regulations (JTR). The Contractor shall be responsible for making all necessary travel arrangements.

7 PERFORMANCE PERIOD
The base period of performance for the CCU project shall be from date of contract award through eighteen months.

8 CONTRACT DATA REQUIREMENTS LIST (CDRL)
The Contractor shall provide an uncompressed electronic copy of the text of each document created on this project on separate diskettes. Electronic submission shall be on CD using Microsoft Word version 7.0 or later. All CDs shall be write-protected and no file shall be password protected. CDs shall be labeled to indicate the Contractor‟s name, Page 37 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
CDRL number, and date of submission. The Contractor shall screen all disks for computer viruses prior to submittal to PMA-276. Graphics, tables, photographs, etc., beyond the capability of Microsoft Word and Excel, or not compatible with versions used to prepare the Contractor‟s CDRL, may be submitted in hard copy only. Existing documentation of off the shelf products are acceptable and supplementary materials may be submitted where minor changes to existing documents are necessary.
SOW PARA CDRL# A001 A002 A003 A004 A005 3.2 A006 A007 A008 B001 A029 A030 A031 A032 B002 B003 3.2.1 B004 B005 B006 C001 C002 C003 C004 C005 C006 C007 C008 D001 C028 C029 C030 C031 D002 D003 D004 D005 D006 DID DI-MISC-80508B DI-MISC-80508B DI-MISC-80508B DI-MISC-80508B DI-QCIC-80510 DI-MISC-80508B DI-MGMT-81501 DI-CMAN-80639C DI-MISC-80508B DI-MISC-80508B DI-SESS-81002D MIL-STD-704 & MIL-HDBK-704 DI-CMAN-81248A DI-IPSC-81441A DI-MISC-80508B DI-IPSC-81427A DI-MGMT-81739 DI-MGMT-81740 DI-MISC-80508B & MIL-HDBK-704, Part 8 DI-MISC-80508B Title Technical Report Study/Services: Theory of System Operation Technical Report Study/Services: Operators Guide Technical Report Study/Services: System Component Qualification Data and Reports Technical Report Study/Services: Structural Analysis Report (SAR) Installation Specification: Installation Data Package (IDP) Technical Report Study/Services: System Performance Specification Weight and Balance Report for Aircraft Engineering Change Proposal (ECP) Technical Report Study/Services: System Software Specification Technical Report Study/Services: Expansion Capabilities Developmental Design Drawings/Models and Associated Lists Electrical Loads Analysis (ELA) Interface Control Document (ICD) Software Product Specification (SPS) Technical Report Study/Services: Upgraded CCS Functionality Assessment Procedures Software Development Plan (SDP) Software Resources Data Reporting: Initial Developer Report and Data Dictionary Software Resources Data Reporting: Final Developer Report and Data Dictionary Technical Report Study/Services: Electric Compatibility Assessment Plan and Report Technical Report Study/Services: Ground and Flight Assessment Support Technical Report Study/Services: PreProduction Unit Metric Data

3.3.3.4

A033

C032

3.3.4

A00H

C00H

3.3.5

A00J

DI-MISC-80508B

Page 38

10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT

3.3.6 3.3.6.1

A00K A00L

C00J C00K

DI-MGMT-80004A DI-ALSS-81529

Management Plan Logistics Management Information (LMI) Data Product Logistics Management Information (LMI) Summaries: Maintenance Planning Logistics Management Information (LMI) Summaries: Repair Analysis Logistics Management Information (LMI) Summaries: Support and Test Equipment Logistics Management Information (LMI) Summaries: Supply Support Logistics Management Information (LMI) Summaries: Manpower, Personnel and Training Logistics Management Information (LMI) Summaries: Packaging, Handling, Storage, and Transportation Logistics Management Information (LMI) Summaries: Post Production Technical Manual Research and Analysis Source Data Special Equipment Tools and Test Equipment List Training Materials Maintenance Support Plan Supplemental Data for Provisioning (SDFP) Logistics Management Information (LMI) Data Product: Interim Support Items List (ISIL) Logistics Management Information (LMI) Data Product: Provisioning Parts List (PPL) Packaging Plan

3.3.6.1.1

A00M

C00L

DI-ALSS-81530

3.3.6.1.2

A00N

C00M

DI-ALSS-81530

3.3.6.1.3

A00P

C00N

DI-ALSS-81530

3.3.6.1.4

A00Q

C00P

DI-ALSS-81530

3.3.6.1.5

A00R

C00Q

DI-ALSS-81530

3.3.6.1.6

A00S

C00R

DI-ALSS-81530

3.3.6.1.7

A00T

C00S

DI-ALSS-81530

3.3.6.2

A014

C013

DI-TMSS-81354

3.3.6.3 3.3.6.4 3.3.6.5 3.3.6.6 3.3.6.7

A019 A020 A021 A022 A023

C018 C019 C020 C021 C022

DI-ILSS-80868 DI-ILSS-80872 DI-ILSS-81225 DI-ALSS-81557 DI-ALSS-81529

3.3.6.8 3.3.6.9

A024 A025

C023 C024

DI-ALSS-81529 DI-PACK-80455

Page 39

10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
3.3.6.12 A00W A00X 3.3.6.13 A00Y A00Z A010 A011 C00V C00W C00X C00Y C00Z C010 DI-MNTY-81600 DI-MNTY-81602 DI-RELI-81497 DI-MNTY-81600 DI-SESS-81315A DI-ILSS-81495 Reliability & Maintainability (R&M) Program Plan Maintainability Predictions Report Reliability Prediction and Documentation of Supporting Data Maintainability Program Plan Failure Analysis and Corrective Action Report Failure Mode Effects, and Criticality Analysis Report Technical Report Study/Services: ReliabilityCentered Maintenance (RCM) Technical Report Study/Services: Level of Repair Analysis (LORA) Source Data for Forecasting Diminishing Manufacturing Sources and Material Shortages (DMSMS) System Problem Report (SPR) Technical Report Study/Services: Unique Item Identification Report Source Data for Forecasting Diminishing Manufacturing Sources and Material Shortages (DMSMS): Bill of Materials (BOM) Contract Performance Report (CPR) Contract Funds Status Report (CFSR) Integrated Master Schedule (IMS) Contract Work Breakdown Structure (CWBS) Management Plan: Program Management Plan (PMP)

3.3.6.14 3.3.6.15 3.3.6.16

3.3.6.17

A012

C011

DI-MISC-80508B

3.3.6.18

A013

C012

DI-MISC-80508B

3.3.6.20

A015

C014

DI-SESS-81656

3.3.6.21 3.3.6.22

A016 A017

C015 C016

DI-MGMT-81232 DI-MISC-80508B

3.3.6.23

A018

C017

DI-SESS-81656

4.1

A009 A00A A00B A00C

C009 C00A C00B C00C

DI-MGMT-81466A DI-MGMT-81468 DI-MGMT-81650 DI-MGMT-81334C & MIL-HDBK-881 DI-MGMT-80004A DI-MGMT-81024 & Naval System Engineering Guide DI-CMAN-80858B

4.2

4.3

A00D

C00D

4.4

A00E

C00E

System Engineering Plan (SEP)

4.4.1

A028

C027

Contractor's Configuration Management Plan (CCMP)

Page 40

10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT

4.4.1.1 4.4.1.2 4.4.2 4.5 4.6 5.1; 5.2; 5.3; 5.4 3.3.6.10; 3.3.6.11; 5.1; 5.2; 5.3; 5.4

A008 A026 A027 A00F A00G

C008 C025 C026 C00F C00G

DI-CMAN-80639C DI-CMAN-80640C DI-MGMT-81453 DI-MGMT-80368A DI-MISC-80508B

Engineering Change Proposal (ECP) Request For Deviation (RFD) Data Accession List (DAL) Status Report: Monthly Status Reports (MSR) Technical Report Study/Services: Requirements Traceability Matrix (RTM) Conference Agenda Conference Minutes

A00U A00V

C00T C00U

DI-ADMN-81249A DI-ADMN-81505

9 STANDARDS

ANSI/ASQC Q9001-1994 ANSI/EIA-649-1998 ISO 10007:1995 ISO 9001:1994 ISO 9001:2000

Quality Systems - Model for Quality Assurance in Design, Development, Installation, and Servicing National Consensus Standard for Configuration Management Quality Management – Guidelines for Configuration Management International Standard: Quality Systems - Model for quality assurance in design, development, production, installation and servicing (1994) International Standard: Quality Management Systems Requirements (2000) [supersedes ISO 9001: 1994]

10 ACRONYMS AND ABBREVIATIONS
ACO AIS APML BFSA BIT BOM CADRG CAS CCMP CCS CCU Administrative Contracting Officer Automated Information Systems Assistant Program Manager for Logistics Blue Force Situational Awareness Built-In-Test Bill of Materials Compressed ARC Digitized Raster Graphics Close Air Support Contractor's Configuration Management Plan Cockpit Control System Critical Cockpit Upgrade Page 41 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
CDNU CDRL CFSR CI CIB CM CNATT CPR CWBS DAFIF DM DMS DMT DTED DTM DVR ECP EDFP ESS FBCB2-BFT FMA FMECA FRACAS FRAGO GFE GFI GFM GFS GIDEP GPS HCI HOL IA IBR ICD ICU ILS ILSMT/IPT IMS IPTL ISIL JMPS JPEG JTA JTR JVMF Control, Display, Navigation Unit Contract Data Requirements List Contract Funds Status Report Configuration Identification Controlled Image Base Configuration Management Center for Naval Aviation Technical Training Contract Performance Report Contract Work Breakdown Structure Digital Aeronautical Flight Information File Data Management Diminishing Manufacturing Source DMSMS Management Team Digital Terrain Elevation Data Data Transfer Module Digital Video Recorder Engineering Change Proposal Engineering Data for Provisioning Environmental Stress Screening Force XXI Battle Command Brigade and Below – Blue Force Tracking Field Maintainability Article Failure Modes Effects and Criticality Analysis Failure Reporting, Analysis, and Corrective Action System Fragmentation Order Government-Furnished Equipment Government-Furnished Information Government-Furnished Material Government-Furnished Software Government Industry Data Exchange Program Global Positioning System Hardware Configuration Items High-Order Language Information Assurance Integrated Baseline Review Interface Control Document Interface Control Unit Integrated Logistics Support ILS Management Team/Integrated Product Team Integrated Master Schedule Integrated Product Team Lead Interim Support Items List Joint Mission Planning System Joint Photographic Experts Group Joint Technical Architecture Joint Travel Regulations Joint Variable Message Format Page 42 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
LEM LMI LORA MDL MEDEVAC MIL MLVS MOPP MSC MSR MTTR MUXBUS NBC NGA NMI NTS NTSC OFP OPORD OSHA PDF PE PFPS PHS&T PLI PMR PPL PSE QA RAM RCM RECON RFD RTM RTOS SA SALT SAS SCI SCS SDP SE SEP SERD SOW SRA Logistics Element Manager Logistics Management Information Level of Repair Analysis Mission Data Loader Medical Evacuation Military Memory Loader Verifier System Mission Oriented Protection Posture Maintenance Signficant Consumable Monthly Status Report Mean Time to Repair Multiplex Bus Nuclear, Biological, and Chemical National Geospatial-Intelligence Agency Nautical Miles Night Targeting System Upgrade National Television Standard Committee Operational Flight Program Operations Order Occupational Safety and Health Administration Portable Document Format Program Events Portable Flight Planning System Packaging, Handling, Storage, and Transportation Position Location Information Program Management Review Provisioning Parts List Peculiar Support Equipment Quality Assurance Random Access Memory Reliability Centered Maintenance Reconnaissance Request For Deviation Requirements Traceability Matrix Real-Time Operating System Situational Awareness Size, Activity, Location, and Time Supportability Assessment Summary Software Configuration Items System Configuration Set Software Development Plan Support Equipment System Engineering Plan Support Equipment Requirements Data Statement of Work Sub-system Replaceable Assembly Page 43 10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.

DRAFT
SRDR STD SVGA TIED TLDHS TPDR TVDL UHF UID USB VDD VHF VMF WARNO WRA XML Software Resources Data Report Standard Super Video Graphics Array Type 1 Encryption Device Target Location Designation and Handoff System Technical Publication Deficiency Report Tactical Video Data Link Ultra High Frequency Unique Identification Universal Serial Bus Version Description Document Very High Frequency Variable Message Format Warning Order Weapons Replaceable Assemblies Extensible Markup Language

Page 44

10/30/2009

Contains competition sensitive data which shall not be disclosed or used for the benefit of others without prior written permission of PMA-276.