C-5_Software_Modernization_PWS_13-730GFEA-01.pdf

PWS: 13-730GFEA-01

FILE NUMBER: FD2060-11-31541/REV 0

Performance-based Work Statement (PWS)

For

C-5 Software Modernization Contract

WR-ALC/GRS (Galaxy Division) Warner Robins Air Logistics Center

Robins AFB GA

12 April 2012

Revision Record

Revision Number

Revision Date

Page Number(s)

Paragraph Description

FILE NUMBER: FD2060-11-31541/REV 0

Table of Contents

Table of Contents

1.1 Applicable Documents

1.2 Background

1.3 Scope

2.0 SERVICES Summary

3.0 GOVERNMENT PROPERTY, SERVICES, AND INFORMATION

3.5 Government-Furnished Equipment (GFE)/Material (GFM)

3.6 Government-Furnished Information (GFI)

4.1 General

4.1.1 Integrated Program Management (IPM)

4.1.2 Integrated Master Schedule (IMS)

4.1.3 Contract/Task Order Kick-Off

4.2 Software Update Task Orders

4.2.1 Contractor Integrated Performance Management

4.2.2 Contract Work Breakdown Structure (CWBS)

4.2.3 Integrated Baseline Reviews (IBRs)

4.2.4 Joint Reviews

4.2.6 Independent Verification & Validation (IV&V)

4.4.1 System Subsystem Specification (SSS)

4.5 System/Software Engineering Environment (S/SEE)

4.5.1 S/SEE Definition

4.5.2 Tools and Materials

4.5.3 Support Facility

4.5.4 Support Equipment (SE)

4.5.5 S/SEE Availability

4.5.6 Special Studies and Analyses

4.6 BCC Task Orders

4.6.1 Requirements

4.6.2 Contract/Task Order Kick-Off

4.6.3 Analysis and Specification

4.6.4 Design, Code, Integrate, Test

4.6.5 Formal Qualification Testing (FQT)

4.6.6 Functional Configuration Audit/Physical Configuration Audit (FCA/PCA)

4.6.7 System Verification

4.6.8 System Verification Review

4.6.12 Government Support

FILE NUMBER: FD2060-11-31541/REV 0

4.6.13 Preparation for Use

4.6.14 Configuration Management (CM)

4.6.15 System Safety

4.6.16 Quality Assurance

4.6.17 Software Acceptance Testing

4.6.18 Training

4.6.19 Process Improvement

4.6.20 Technical Baseline Management

4.7 Emergency Block Cycle Change (EBCC) Task Orders

4.8 Technical Manuals

4.9 Technical Data and Computer Software

4.9.1 Data Management

4.9.2 Financial Management

4.9.3 Integrated Product Team (IPT)

4.9.4 Contractor-Furnished Equipment (CFE) Statement

4.9.5 Subcontractor Management

4.10 Procedures and Controls

4.10.1 Task or Order Authorization

4.10.3 Government Access and Inspection of Services

4.10.4 Travel

4.10.6 Points of Contact

4.10.7.8 Identification Credential Requirements

4.10.10 Contractor / Subcontractor Intellectual Property

4.10.11 Contract Change Proposal (CCP), ECP, Deviations, and Waivers

4.11 Deliverables

4.12 Other Contractual Requirements

4.12.1 Period of Performance (POP)

4.12.2 Duty and Location

4.0 APPENDICES

APPENDIX A: Acronyms

APPENDIX C: References

Appendix D: Definitions

Appendix E: Crypto Keys and Data Transfer Device

Appendix F: AHMU 1/SATCOM/MADARS GFE Components

APPENDIX G: Deficiency Reports

FILE NUMBER: FD2060-11-31541/REV 0

DESCRIPTION OF SERVICES

This Performance-based Work Statement (PWS) outlines the tasks and duties required of Lockheed Martin Aeronautics Company (LM Aero) in the sustainment of software for the C-5M model. This acquisition will benefit the United States Air Force (USAF) by providing a means to maintain the C-5M software configurations.

The Contractor shall accomplish a partnership arrangement with the 402nd Software Maintenance Group through a work share agreement in the areas of development and independent testing. Specific activities of the partnership shall be identified and mutually agreed upon by the Contractor and the Government and documented in an implementation agreement.

The Contractor shall provide a fully-tested C-5M compatible aircraft Operational Flight Program (OFP) and/or related software support applications. The Contractor activities shall include but are not limited to, specification/analysis, engineering development, software design, associated testing, Technical Data Package (TDP) updates, support of airworthiness and Communication, Navigation, Surveillance/Air Traffic Control (CNS/ATM) certifications, support of Government Software Integration Laboratory (SIL), collection of data to support the Joint Interoperability Test Certification (JITC), and Technical Order (TO) updates associated with software maintenance and sustainment.

The Contractor shall accomplish special engineering studies and analysis of the software deficiencies and enhancements as directed by the Government. In the special engineering and analysis reports, the Contractor shall provide recommendations that fully resolve the software Deficiency Reports (DRs) in the most cost effective means. The Government reserves the right to determine how these efforts shall be accomplished for C-5M.

The Contractor shall maintain the ability to accomplish, on an as needed basis, software emergency builds. The Contractor may be required to quickly execute the correction of fleet critical software deficiencies. The Contractor shall maintain the capability to quickly respond to a Government requirement to accomplish an Emergency Block Cycle Change (EBCC). The Contractor shall develop a comprehensive plan identifying all resources needed to accomplish EBCC corrections providing a safe reliable resolution to a deficiency. The Contractor shall plan to support the C-5 aircraft, to provide emergency software corrections, and to investigate and resolve on-aircraft software issues as they arise. These services are necessary to reduce the risk of Safety Of Flight (SOF) incidents.

The Contractor shall maintain the AMP and RERP configurations of the Systems Integration Laboratory (SIL) including updates to support efforts contained in this PWS.

The Contractor shall support the C-5 software partnership agreement. The support shall include access to engineering data, technical support for software development activities, specification/analysis, engineering development, software design, associated testing, TDP updates, support of certifications, airworthiness, collection of data to support the JITC, and TO updates associated with software sustainment. Contractor furnished data and equipment shall be

FILE NUMBER: FD2060-11-31541/REV 0

identified as applicable within the specific implementation agreement under the established partnership.

1.1 Applicable Documents

Applicable documents are listed in Appendix C, References, of the PWS.

1.2 Background

The C-5 Weapon System is currently undergoing the RERP modification. The AMP modification is complete. Although the AMP program was the common technological baseline for both configurations, these activities have evolved into two different aircraft configurations.

C-5 software requires periodic updates, corrective measures, and/or modifications to continue its performance as designed.

The C-5 fleet has two distinct software configurations which are the C-5A/B/C aircraft with the AMP modification and the C-5M aircraft that have received the RERP modification. There are numerous software deficiencies as well as other software maintenance tasks with the AMP system have been identified that apply to either one or both configurations.

There have been four AMP software sustainment activities prior to this effort to resolve software deficiencies for the C-5 aircraft that have received the AMP modification. The AMP Block Cycle Change (BCC)04 corrected deficiencies focused on Flight Management System (FMS), Automatic Flight Control System (AFCS), SATCOM data-link messaging and displays.

The C5 RERP 3.5.2 software modification consists of updates to the Versatile Integrated Avionics / Avionics Interface Unit (VIA/AIU) Computer Software Configuration Item (CSCI)

• Includes updated Automatic Flight Control System (AFCS) CSCI

• Includes updated Flight Management System (FMS) CSCI

• Includes updated Timeline

• Includes updates to the Display Services (DS) CSCI

The 3.5.2 software modification also consists of updates to the Multi-function Display Unit (MFDU) Application Client (MAC) software CSCI, the Portable Computer Interface Unit (PCIU) CSCI and Auxiliary Maintenance Computer (AMC) CSCI.

The basic RERP 3.5.2 effort incorporates all of the BCC03 DR content – some of which was matured in 3.5.1. The effort was accomplished in 3 phases. Phase 3 of the effort entails the QT/flight release testing/development flight test efforts, software rework, FQT/flight release testing/verification flight tests effort and FCA/PCA.

FILE NUMBER: FD2060-11-31541/REV 0

1.3 Scope

The Contractor shall provide a fully-tested C-5M compatible aircraft OFP and related software support applications. The Contractor shall plan to accomplish one RERP BCC. The Contractor activities shall include specification/analysis, engineering development, software design, associated testing, TDP updates, support of CNS/ATM and airworthiness certifications, support of government SIL at WR-ALC, collection of data to support the JITC, and TO updates associated with software sustainment.

The general requirements to achieve the contract/task order objectives are described throughout this PWS. The Contractor shall maintain the capability to support all efforts outline in the PWS.

The Contractor shall ensure software updates, fixes, and corrections are provided to the USAF within a reasonable time period as directed by the Government. The Contractor shall flow all requirements stated in this PWS to its subcontractor(s).

2.0 SERVICES SUMMARY

Performance Objective

PWS

Paragraph Performance Threshold

DR Investigations 4.3.1.g

For investigations conducted under paragraphs 4.3 and

4.3.1 during the period of performance of fixed level-of-effort tasks (paragraph 4.2.2), identify root cause in accordance with TO 00-35D-54.

Provide initial response within the following time periods:

CAT I: 20 clock hours CAT II: 7 calendar days

Provide final resolution response within the following time periods:

CAT I: 45 calendar days CAT II: 100 calendar days

DRs in open status shall be updated every 90 calendar days and as significant events occur. Responses for all categories shall meet the requirement 100% of the time.

Formal Qualification Test Report (FQT)

4.6.5, 4.6.17

For each task order, DO-178B Criticality Levels A through E Computer Software Configuration Items (CSCIs) shall complete all phases of the FQT at a pass

FILE NUMBER: FD2060-11-31541/REV 0

Performance Objective

PWS

Paragraph Performance Threshold

Section 3 and 4 Specification Requirements of the Air Vehicle Specification, Consolidated Specification for Software rate of 100%.

Processor Throughput 4.6.3

Processor throughput for the C-5 software configurations shall be measured for each software build including engineering builds for all hardware affected by a software build. Processor throughput shall not increase by 5%. Processor throughput shall not exceed 90% with an objective of 85%.

Computer Processor Unit (CPU) Memory

4.6.3

CPU memory for the C-5 software configurations shall be measured for each software build including engineering builds for all hardware affected by a software build. CPU memory shall not increase by 5%.

CPU memory shall not exceed 90%.

1553 Bus Utilization 4.6.3

1553 Bus Utilization for the C-5 software configurations shall be measured for each build including engineering builds. 1553 Bus Utilization shall not increase by 5%. 1553 Bus Utilization shall not exceed 90%.

SIL 4.9.4

Ensure Avionics Hot Mockup (AHMU 1), Avionics Hot Mockup (AHMU 2), Engineering Simulator (ESIM), Operational Flight Program Mock-Up (OFPMU), and Satellite Communication (SATCOM) Lab, associated SIL equipment and software is maintained and configured to support all fielded C-5 AMP and/or RERP modified aircraft. Ensure the AHMU 1, AHMU 2, ESIM, OFPMU, and SATCOM Lab is available 95% of the time for a one-shift operation during the normal five-day workweek.

Risk Management Plan 4.1.1 The program Risk Management Plan shall be updated at least once per month.

FILE NUMBER: FD2060-11-31541/REV 0

Performance Objective

PWS

Paragraph Performance Threshold

Integrated Master Schedule 4.1.2

Schedule elements shall show interdependencies with the critical path(s) being updated monthly. A maximum of two (2) formal schedule re-baselines shall be permitted over the course of the program.

Safety and Health Plan/Program 4.10.2 100% compliance.

Mishap Notification 4.10.2.3 No more than one late mishap notification per contract/task order year.

Table 2.1 Services Summary

3.0 GOVERNMENT PROPERTY, SERVICES, AND INFORMATION

3.1_ Federal Acquisition Regulation (FAR) 45.101, [Government Property] Definitions

3.1.1 “ ‘Government property’ means all property owned or leased to the Government or acquired by the Government under the terms of the contract. It includes both Government- Furnished Property (GFP) and Contractor-Acquired Property (CAP) ….”

3.1.2 “ ‘Contractor-acquired property’ … means property acquired or otherwise provided by the contractor for performing a contract and to which the Government has title.”

3.2_ Contractor Responsibility

3.2.1 The Contractor shall be responsible for Government property in their possession in accordance with the FAR and Defense Federal Acquisition Regulation Supplement (DFARS) including, but not limited to, FAR Part 45, Government Property, FAR 52.245, and DFARS, Part 245, Government Property.

3.2.2 At the end of each work period, Contractor personnel shall ensure all equipment and materials provided for their use are secure. A report identifying location, use, and status of all Government property assigned to the Contractor for the tasks associated with this PWS shall be provided quarterly.

3.3 DFARS 252.245-7002, Reporting Loss of Government Property

FILE NUMBER: FD2060-11-31541/REV 0

(a) Definitions.

“Loss of Government property” means unintended, unforeseen, or accidental loss, damage, or destruction of Government property that reduces the Government’s expected economic benefits of the property. Loss of Government property does not include purposeful destructive testing, obsolescence, normal wear and tear, or manufacturing defects. Loss of Government property includes, but is not limited to –

(1) Items that cannot be found after a reasonable search

(2) Theft

(3) Damage resulting in unexpected harm to property requiring repair to restore the item to usable condition, or

(4) Destruction resulting from incidents that render the item useless for its intended purpose or beyond economical repair.

“Unit acquisition cost” means –

(1) For Government-furnished property, the dollar value assigned by the Government and identified in the contract; and

(2) For Contractor-acquired property, the cost derived from the Contractor’s records that reflect consistently applied, generally acceptable accounting principles.

(b) Reporting loss of Government property.

(1) The Contractor shall use the Defense Contract Management Agency (DCMA) eTools software application for reporting loss of Government property. Reporting value shall be at unit acquisition cost. The eTools “LTDD of Government Property” toolset can be accessed from the DCMA home page External Web Access Management application at http://www.dcma.mil/aboutetools.cfm.

(2) Unless otherwise provided for in this contract, the requirements of paragraph (b)(1) of this clause do not apply to normal and reasonable inventory adjustments, i.e., losses of low-risk consumable material such as common hardware, as agreed to by the Contractor and the Government Property Administrator. Such losses are typically a product of normal process variation. The Contractor shall ensure that its property management system provides adequate management control measures, e.g., statistical process controls, as a means of managing such variation.

(3) The Contractor shall report losses of Government property outside normal process variation, e.g., losses due to -

(i) Theft;

(ii) Inadequate storage;

(iii) Lack of physical security; or

(iv) “Acts of God.”

(4) This reporting requirement does not change any liability provisions or other reporting requirements that may exist under this contract.

3.4 Return/Retention of Government Property: All GFP remains the property of the Government and shall be returned to the Government upon completion of the contract/task order or as directed by WR-ALC/GRSA. All GFP shall be returned to the Government in the condition provided unless approved in advance by the Procuring Contracting Officer (PCO). All property acquired by the Contractor for accomplishment of contract/order requirements becomes the property of the Government and shall be returned to the Government upon completion of the contract/task order or as directed by WR-ALC/GRSA. All material generated under the contract/task order becomes the property of the Government and shall be returned to the Government upon completion of the contract/order or as directed by WR-ALC/GRSA.

Department of Defense (DD) Form 1423-1, Contract Data Requirements List (CDRL), deliverables become the property of the Government upon receipt.

3.5 Government-Furnished Equipment (GFE)/Material (GFM)

The Government will provide access to C-5 aircraft, as required and if available, in order for the Contractor to accomplish software sustainment activities. The Contractor shall plan to accomplish all aircraft testing in no more than two events for each task order. The Contractor shall plan to accomplish the majority of software testing using the SIL and other venues and shall only accomplish aircraft testing as directed by the Government.

The Government will provide access to components/systems, as required, in order for the Contractor to perform engineering analysis tasks. Components/systems will be made available based on fleet requirements and with the approval of the responsible organization at WR-ALC, Ogden Air Logistics Center (OO-ALC), Oklahoma City Air Logistics Center (OC-ALC), and any other Government agency.

The Government will provide access to components/systems, as required, in order for Contractor to maintain the SIL. Components/systems will be made available based on fleet requirements and with the approval of responsible organization at WR-ALC, OO-ALC, OC-ALC, and any other Government agency.

The Contractor shall report NLT 5 business days after discovery any defective GFE to the Government via a contract notification letter. The Contractor shall requisition replacements

FILE NUMBER: FD2060-11-31541/REV 0

parts using the approved Government systems NLT 5 business days after discovery it is defective. The Contractor is responsible for the repair costs of any asset that is deemed to be Serviceable or Could Not Duplicate (CND) by the repair facility.

Note: AHMU-1, AHMU-2, ESIM, SATCOM, Malfunction Detection, Analysis, and Recording System (MADARS) Component GFE Listing is in Appendix F of the PWS.

The Contractor shall notify the Government of any required changes to the System /Software Engineering Environment (S/SEE) in the Monthly Status Report (MSR). The Specification Change Notice (SCN) shall include the part number of the item and quantity, as well as, the basis/reason for the change. (CDRL A002, DI-MGMT-80368A/T, Status Report; CDRL A00E, DI-MGMT-80259/T, Physical Inventories Report)

3.6 Government-Furnished Information (GFI)

The Government will provide the Contractor with the baseline TOs required to complete the efforts outlined in this PWS. Updates of the TOs will be provided as required.

3.6.1 Government Automated Information System (AIS)

The Government will provide Contractor personnel access to systems required to perform tasks under the contract/task order. The Contractor shall ensure Contractor personnel who require access to a Government AIS have a Department of Defense (DoD) National Agency Check Plus Written Inquiries (DNACI) conducted in accordance with DoD 5200.2-R, Personnel Security Program. The Government will provide system access subject to approval of the DD Form 2875, System Authorization Access Request (SAAR). Upon completion/termination of the contract/task order or transfer/termination of Contractor personnel, the system account will be closed.

3.6.1.1 The Government will provide Contractor personnel access to the Joint Deficiency Reporting System (JDRS) and the Air Force (AF) Portal. System access will be provided subject to completion of a security check, approval of the required forms, and issuance of a Common Access Card (CAC). Upon completion/termination of the contract/task order or transfer/termination of Contractor personnel, the CAC, shall be returned to the PCO or as directed by WR-ALC/GRSA.

3.6.2 Wide Area Workflow (WAWF):

In accordance with DFARS 252.232-7003, Electronic Submission of Payment Requests, the Contractor shall submit/process payment requests (invoices, Receiving Reports or combos), Receipt/Acceptance documents, and CDRL deliverables via WAWF. Contractor personnel shall register to access Wide Area Workflow-Receipt and Acceptance (WAWF-RA) at

FILE NUMBER: FD2060-11-31541/REV 0

https://wawf.eb.mil and designate an Electronic Business Point of Contact (EB POC) in the Central Contractor Registration (CCR) site at http://www.ccr.gov within ten calendar days after award of the contract/task order.

4.0 General Information

Section 4 is divided into five major sections: General (Section 4.1) software update task orders (Section 4.2), special engineering studies analysis (Section 4.3), software emergency builds (Section 4.4) and SIL maintenance (Section 4.5).

4.1 General

This section outlines tasks that are applicable to all task orders.

4.1.1 Integrated Program Management (IPM)

The Contractor shall provide a financial overview NLT 30 business days after the award of each task order showing the projected spend plan for labor and material on one chart and projected travel on another chart. The charts shall plot, by month, the actual expenditures against the baseline plan. The charts shall plot from initial award amounts showing any possible changes as a result of contract/task order modifications. The Contractor shall track the project including notification of any schedule changes. The Contractor shall notify the Government of any possible financial or technical changes that may impact the planned completion per the schedule and cost information.

The Contractor shall establish and maintain standard program plans and controls. The Contractor shall develop and maintain a risk management plan to identify and provide resolution to any risks in a timely manner. The risk management plan shall include impacts to concurrent running programs and be updated at least once per month. The risk management status shall either be integrated or be an attachment to the MSR.

The Contractor shall plan and conduct a Program Management Review (PMR). The Contractor shall hold a PMR at least once every six months via video teleconference or at a location to be determined by the Government. PMRs will be approximately one-half day in length. Upon receipt of an approved agenda, PMR slides shall be provided in draft form two weeks in advance of the meeting. Meeting minutes shall be generated and delivered by the Contractor. The Contractor may request to revise the PMR schedule or to not conduct a particular PMR. The Government will only consider requests if a particular task order is more than 10% under the baseline planned budget and schedule.

The Contractor shall coordinate tasks associated with each task order with other projects accomplished by the Contractor and shall make every effort to ensure there are no resource

FILE NUMBER: FD2060-11-31541/REV 0

conflicts impacting the contract/task order(s). (CDRL A001, DI-ADMN-81505/T, Conference Minutes; CDRL A002, DI-MGMT-80368A/T, Status Report; CDRL A003, DI-MGMT- 81468/T, Contract Funds Status Report; CDRL A004, DI-MGMT-81453A, Data Accession List; CDRL A008, DI-ADMN-81249A,Conference Agenda)

4.1.2 Integrated Master Schedule (IMS)

The Contractor shall develop and maintain a logical, networking–detailed program activities IMS for each task order and shall establish a Government-approved schedule baseline within 30 calendar days after contract/task order award. The IMS shall show deviations from the baseline plan as well as the critical path(s). The Contractor shall submit a request to the Government to combine task orders into a common IMS for two or more tasks. The IMS shall show deviations from the baseline plan. If the IMS requires a new baseline, due to significant variance over the course of the program, the Contractor shall notify the Government Program Manager (PM) prior to re-baselining the IMS. The IMS shall be re-baselined only with Government approval via the PCO. As a performance measure, the IMS may only be formally baselined a maximum of two times over the course of the program. The schedule shall contain the specific activities and milestones, accomplishments, exit criteria, and activities associated with contract/task order events from contract/task order award to the completion of the contract/task order. All key supplier activities and milestones shall also be included in the IMS including USAF provided schedules for associated teams (i.e., test communities, partnership activities). The IMS shall show interrelationships and dependencies of schedule elements along with the critical path of the program. At a minimum, the critical path of the IMS shall be updated for each monthly reporting period. (CDRL A002, DI-MGMT-80368A/T, Status Report; CDRL A005, DI-MGMT- 81650/T, Integrated Master Schedule)

4.1.3 Contract/Task Order Kick-Off

The Contractor shall conduct detailed activity planning for each task order under this contract.

The Contractor shall conduct a contract/task order kick-off meeting NLT 20 business days after contract/task order award or other mutually agreed upon date. The Contractor shall address cost planning, project schedule, planned development activities, planned test activities, test venues, and risk management for each BCC at the contract/task order kick-off meeting. (CDRL A001, DI-ADMN-81505/T, Conference Minutes; CDRL A008, DI-ADMN-81249A, Conference Agenda)

4.2 Software Update Task Orders

The software maintenance task order under this PWS shall be treated as a stand-alone contract.

Earned Value Management System (EVMS) requirements for each task order shall apply if the individual task order cost is equal to or greater than $20M. The Contractor shall use an EVMS

FILE NUMBER: FD2060-11-31541/REV 0

in compliance with guidelines in American National Standards Institute/Electronic Industries Alliance (ANSI/EIA)-748, A Standard for Earned Value Management System.

4.2.1 Contractor Integrated Performance Management

The Contractor shall utilize its existing internal performance management system to plan, schedule, budget, monitor, manage, and report cost, schedule, and technical status applicable to each task order under this contract. The Contractor’s internal performance management system shall serve as the single, formal, integrated system meeting both the Contractor’s internal management requirements and the requirements of the Government for timely, reliable, and auditable performance information. The application of these concepts shall provide an early indication of contract/task order cost, schedule, and technical challenges. Earned value assessments shall correlate with technical achievement. The outputs of this system shall be used as the basis to report detailed performance status during PMRs and other status meetings. The Contractor’s system shall satisfy the industry guidelines delineated in the ANSI/EIA-748, EVMS identified in Appendix C of the PWS, the general provisions of the contract/task order, and this PWS. The schedule and cost information used in the EVMS shall be consistent with the information contained in the IMS and the Contract Funds Status Report (CFSR).

The Contractor’s system shall meet the guidelines and be maintained in accordance with the requirements of the EVMS guidelines as described in this contract/task order, under DFARS 252.242-7002 and the Contractor’s own documented system description. The Contract Performance Report (CPR) and IMS shall be developed, maintained, updated, and reported on a monthly basis per CDRL requirements. The application of these concepts shall provide for early indications of contract/task order cost and schedule problems. Earned value assessments shall correlate with technical achievement. For task orders under this contract the above requirements shall apply; however, in regards to DFARS 252.242-7001, Notice of Earned Value Management System, and 252.242-7002, Earned Value Management System, the Contractor shall be required to have an EVMS that complies with ANSI/EIA-748. If the Contractor EVMS does not comply, the Government will not formally accept the Contractor’s system (i.e., no compliance review).

However, in the event the Contractor requests to change their EVMS, the change must be approved by the Government Contracting Officer before it can be implemented. (CDRL A003, DI-MGMT-81468/T, Contract Funds Status Report; CDRL A005, DI-MGMT-81650/T, Integrated Master Schedule; CDRL A006, DI-MGMT-81466A/T, Contract Performance Report)

4.2.2 Contract Work Breakdown Structure (CWBS)

The Contractor shall develop and maintain the CWBS and CWBS dictionary in accordance with DI-MGMT-81334C. The Contractor shall extend the CWBS down to the appropriate level required to provide adequate internal management, surveillance, and performance measurement, for Government visibility. The Contractor shall use the CWBS as the primary framework for

FILE NUMBER: FD2060-11-31541/REV 0

contract/task order planning, budgeting, and reporting of the cost, schedule, and technical performance status to the Government. The Contractor shall analyze the system requirements specified in the task order PWS and system specification and translate them into a structure representing the products and services comprising the entire work effort. The Contractor shall prepare the technical elements of the extended CWBS. The Contractor, if necessary, shall update the CWBS during the execution of the contract/task order. (CDRL A007, DI-MGMT- 81334C, Contract Work Breakdown Structure)

4.2.3 Integrated Baseline Reviews (IBRs)

The IBR shall focus on the realism of the Contractor’s integrated Performance Measurement Baseline (PMB) and the appropriateness of the earned value methodology to be employed. If stated in the task order PWS, the Contractor shall complete the initial baseline and host an IBR NLT 45 working days after award of each task order. Incremental IBRs shall be conducted, as needed, throughout the life of the contract/task order, if required, following major changes (i.e, 10%) to the baseline. The Government will verify during the IBR, and follow-on IBRs if required, that the Contractor has established and maintains a reliable PMB. The Contractor shall ensure the baseline includes the entire contract technical scope of work consistent with contract/task order schedule requirements and has adequate resources assigned. The Contractor shall ensure the Government-effective earned value methods are used to provide accurate status of contract/task order cost, schedule, and technical performance. The IBR will 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 program. Participation in the IBR will be a joint responsibility of both the Government PM and the Contractor. The Contractor shall flow-down the IBR requirement to those subcontractors meeting the applicable thresholds for Earned Value Management (EVM) reporting. Meeting minutes shall be created and delivered by the Contractor. (CDRL A001, DI-MGMT-81505/T, Conference Minutes; CDRL A008, DI-ADMN-81249A, Conference Agenda; CDRL A006, DI-MGMT-81466A/T, Contract Performance Report; CDRL A007, DI-MGMT-81334C, Contract Work Breakdown Structure)

4.2.4 Joint Reviews

The Contractor shall plan to accomplish all joint reviews (including joint reviews with subcontractors) on Robins AFB, GA or the LMA facility at Warner Robins, GA except where noted below. The Contractor shall perform a detailed joint System Requirements Review (SRR) with the Government. The Government-approved entrance and exit criteria typically accomplished in an SRR shall apply. Testing venues and methods of testing shall also be a part of this event.

The Contractor shall conduct Flight Station Working Group (FSWG) meetings early in the software update task order schedule to validate user interface requirements. The FSWG invitee

FILE NUMBER: FD2060-11-31541/REV 0

list should include representatives from the Contractor, WR-ALC/GRSA, WR-ALC/GRSE, Air Mobility Command (AMC)/A3V, and at least two pilots and one flight engineer from each base receiving the software update. The first FSWG shall be conducted NLT 30 calendar days prior to the combined Software Requirements Analysis Review (SRAR)/Preliminary Design Review (PDR). The Contractor shall hold at least one of the FSWG meetings at an AMC or AFRC C- 5M location. The Contractor shall ensure all FSWG collected requirements are fully known and included in the final design presented to the Government as part of the combined Critical Design Review (CDR)/Verification Review Council (VRC). The Contractor shall ensure, with Government support, the user interface is reviewed by no less than ten Government pilots and no less than five Government flight engineers either as part of a FSWG meeting or another means.

As necessary, the Contractor shall update the Human Engineering Design Approach Document- Operator Document and the Human Engineering Design Approach Document-Maintenance. The Contractor shall accomplish a TRR to ensure joint understanding of Government requirements, reduce design rework, and reduce the number of code-test-code steps

The Contractor shall hold a combined SRAR/PDR including assessment of changes to the requirements. The Government approved entrance and exit criteria for the SRAR and PDR shall be included as part of this event. In addition, the SRAR/PDR shall include a review of processor throughput, bus utilization, and memory usage for the proposed changes.

The Contractor shall perform a combined CDR/VRC, which shall contain the Government approved entrance and exit criteria accomplished in a CDR, with the goal of accomplishing the detailed design review in no more than three business days. The Contractor shall organize the software update tasks so all VRC efforts are completed with no more than two meetings. A Technical Order Guidance Conference shall also be held as part of this event to ensure personnel developing the TO changes gain the benefit of hearing the design requirements and can assess impacts of design changes from the proposal phase of the contract/task order. The Contractor shall consider Government inputs from working groups (e.g., Flight Station, TO, etc.) leading up to the CDR. This recommendation shall be documented as a report and included as part of the minutes for the CDR. The Contractor shall provide, as part of the CDR, a PowerPoint presentation (i/e, first draft) describing each problem report (e.g., DR, FMS PLIs, etc.) and the solution to correct the problem. The PowerPoint presentation shall include a list of TO changes and other related information. The Government reserves the right to postpone any review if the draft and final documentation packages are not received within the time limitations noted on the CDRLs or in this paragraph.

The Contractor shall accomplish a TRR to ensure joint understanding of Government requirements, reduce design rework, and reduce the number of code-test-code steps.

(CDRL A001, DI-ADMIN-81505/T, Conference Minutes; CDRL A002, DI-MGMT- 80368A/T, Status Report; CDRL A003, DI-MGMT-81468/T, Contract Funds Status Report; CDRL A004, DI-MGMT-81453A, Data Accession List; CDRL A005, DI-MGMT- 81650/T, Integrated Master Schedule; CDRL A008, DI-ADMN-81249A, Conference Agenda; CDRL B001, TM-86-01N, Technical Manual Contracts Requirement; CDRL

FILE NUMBER: FD2060-11-31541/REV 0

C001, DI-IPSC-81441A/T, Software Product Specification; CDRL C002, DI-IPSC- 81433A/T, Software Requirements Specification; CDRL C003, DI-IPSC-81434A/T, Interface Requirements Specification; CDRL C004, DI-CMAN-81248A/T, Interface Control Document; CDRL C006, DI-IPSC-81431A/T, System/Subsystem Specification;

C009, DI-HFAC-80746B/T, Human Engineering Design Approach Document-Operator;

CDRL C00B, DI-SESS-81757A/T, Design Review Information Package; CDRL C00C, DI- IPSC-81442A/T, Software Version Description; CDRL D001, DI-MCCR-80700, Computer Software Product End Items; CDRL E001, DI-QCIC-81536/T, Test Information Sheet;

CDRL E002, DI-NDTI-80809B/T, Test/Inspection Report; CDRL; CDRL C00A, DI- HFAC-80747B/T, Human Engineering Design Approach Document-Maintainer)

4.2.5 C-5 Configuration Control Board (CCB)

The Contractor shall support the Government CCB reviews required for the implementation and testing of the elements of this PWS. Support shall include attending the CCB in person or by phone, providing task order documentation, and testing instrumentation documentation as required. (CDRL A001, DI-ADMIN-81505/T, Conference Minutes; CDRL A002, DI- MGMT-80368A/T, Status Report; CDRL A003, DI-MGMT-81468/T, Contract Funds Status Report; CDRL A004, DI-MGMT-81453A, Data Accession List; CDRL A005, DI- MGMT-81650/T, Integrated Master Schedule; CDRL A008, DI-ADMN-81249A, Conference Agenda; CDRL B001, TM-86-01N, Technical Manual Contracts Requirement;

CDRL C001, DI-IPSC-81441A/T, Software Product Specification; CDRL C002, DI-IPSC- 81433A/T, Software Requirements Specification; CDRL C003, DI-IPSC-81434A/T, Interface Requirements Specification; CDRL C004, DI-CMAN-81248A/T, Interface Control Document; CDRL C006, DI-IPSC-81431A/T, System/Subsystem Specification;

CDRL C00B, DI-SESS-81757A/T, Design Review Information Package; CDRL C00C, DI- IPSC-81442A/T, Software Version Description; CDRL D001, DI-MCCR-80700, Computer Software Product End Items; CDRL E001, DI-QCIC-81536A, Test Information Sheets;

CDRL C00F, DI-NDTI-80809B/T, Test/Inspection Report; CDRL E003, DI-NDTI- 80566A/T, Test Plan; CDRL D002, DI-IPSC-81488, Computer Software Product End Item- Source Code; CDRL E005, DI-QCIC-81536A, Verification Test Information Sheets; CDRL E006, DI-QCIC-81536A, Integration Test Information Sheets; CDRL D003,DI-IPSC- 81488, Computer Software End Item-Source Code-Test Scripts)

4.2.6 Independent Verification & Validation (IV&V)

The Contractor shall support, in the Contractor’s or Government facilities the IV&V of any software products they update or test as a result of a BCC, software development, or EBCC task order including software products that interface with or impact the software products sustained under this effort. The Contractor shall maintain, update, and deliver the Flight Information and

FILE NUMBER: FD2060-11-31541/REV 0

Data Output (FIDO) Interface Control Document (ICD). (CDRL A002, DI-MGMT-80368A/T, Status Report; CDRL A003, DI-MGMT-81468/T, Contract Funds Status Report; CDRL C004, DI-CMAN-81248A/T, Interface Control Document)

4.2.7 Integration and Regression Testing with other Agencies

The Contractor shall support integration tests with the applicable agency in accordance with the task order to ensure the software changes made as part of the task order do not have a negative impact on the current capability. A full dry-run integration test of the task order software changes shall be performed in the SIL. This may create the need to update regression test procedures and scripts. All updated test procedures and scripts shall be delivered to the Government. The Contractor shall document the efforts noted in this paragraph in a separate technical report. (CDRL A002, DI-MGMT-80368A/T, Status Report; CDRL A003, DI- MGMT-81468/T, Contract Funds Status Report; CDRL A004, DI-MGMT-81453A, Data Accession List; CDRL A005, DI-MGMT-81650/T, Integrated Master Schedule; CDRL C006, DI-IPSC-81431A/T, System/Subsystem Specification; CDRL C00D, DI-MISC- 80711A/T, Scientific and Technical Reports; CDRL E003, DI-NDTI-80566A/T, Test Plan;

CDRL E005, DI-QCIC-81536A, Verification Test Information Sheets; E006, DI-QCIC- 81536A, Integration Test Information Sheets; CDRL E007, DI-IPSC-81440A/T, Software Test Report)

4.3 Engineering and Technical Support The Contractor shall provide engineering studies and analysis in support of C-5 software activities. The Contractor shall flow all requirements stated in this paragraph to the subcontractor as applicable. Where instructed in the engineering studies and analysis task order, the Contractor shall determine the corrective action of a software deficiency to the pseudo code level. The Contractor shall provide a safety/air-worthiness risk assessment that details at the Computer Software Unit (CSU) level the impacted software changes and the testing required to maintain the C-5 in accordance with DO-178B specifications.

The engineering study shall identify any shortfalls in testing capability with proposed solutions to resolving the shortfall. The Contractor shall provide block flow analysis to the CSCI level for the incorporation of new software capability. Where instructed in the engineering studies and analysis task order, the Contractor shall provide Not Later Than (NLT) the 15th business day of March of each calendar year a technical report of all open software deficiencies against the AMP and RERP configurations. The report shall be developed from a list of AMP and RERP software deficiencies that is documented and regularly updated in the monthly status report. The Contractor shall document as a software DR any Contractor findings, i.e. Integration Problem Report (IPR), the Government has reviewed and agrees to track as an unresolved deficiency against the software. If the software deficiency impacts both AMP and RERP, the Contractor shall ensure that separate software DRs are entered into JDRS for each configuration. (CDRL

FILE NUMBER: FD2060-11-31541/REV 0

A002, DI-MGMT-80368A/T, Status Report; CDRL C00D, DI-MISC-80711A/T, Scientific and Technical Reports)

4.3.1 Technical Support

The Contractor shall provide technical support for AMP and RERP computer resources and interfaces to members of the C-5 software sustainment MFT including, but not limited to, trainers, Government test organizations, field users, and maintainers of systems interfacing with AMP and RERP components. Unless otherwise directed by the Government Contracting Officer the Contractor shall directly interface with the Government test organizations, field users, and maintainers of system interfacing with AMP and RERP components. The Contractor shall use the Government Integrated Product Team (IPT) noted in this PWS as a means to these organizations. The Contractor shall not construe requests from Government test organization, field users or maintainers as direction to accomplish work under this contract. The technical support shall also include testing of commercial software changes (i.e. EGPWS, TCAS, SDU etc)

For software related activities the Contractor shall:

a. Provide subject matter expert information and technical support to operational, maintenance, program office and depot maintenance personnel.

b. Respond to requests from depot maintenance or field operations for engineering support (i.e., Request of Assistance “107”, TO 00-25-107 Maintenance Assistance and Nonconforming Technical Assistance Request and Reply “202” process [Air Force Material Command (AFMC) Manual 21-1, Air Force Materiel Command Technical Order System Procedures], that does not include Contractor’s intellectual property.

c. If requirements for engineering and/or maintenance actions are identified, prepare project plans identifying man-hour and associated cost estimates for planning, execution, and reporting of projects as applicable.

d. Prepare and present briefings to the Government on operation and/or maintenance of the systems and on engineering services supported by the applicable tasks.

e. Perform evaluations of guidance from regulatory organizations ( i.e. e.g., Airworthiness Directives, Service Bulletins, Federal Aviation Administration Revisions, Commercial Consortiums, CNS/ATM) including apprising the Government of the potential impacts to the C-5.

f. Support various reviews, working groups, and boards (e.g., quarterly Computer Resource Working Group, semi-annual/annual Aircraft Information Working Group, bi-weekly CCB telecon, annual Product Improvement Working Group (PIWG), annual CNS/ATM Conference and other meetings) related to tasks under this contract/task order.

g. DR Investigations: Identify root cause in accordance with TO 00-35D-54.

FILE NUMBER: FD2060-11-31541/REV 0

Provide initial response within the following time periods:

CAT I: 20 clock hours CAT II: 7 calendar days

Provide final resolution response within the following time periods:

CAT I: 45 calendar days CAT II: 100 calendar days

DRs in open status shall be updated every 90 days and as significant events occur. Responses for all categories shall meet the requirement 100% of the time. (CDRL A002, DI-MGMT- 80368A/T, Status Report; CDRL C00D, DI-MISC-80711A/T, Scientific and Technical Reports; CDRL C00F, DI-NDTI-80809B/T, Test/Inspection Report)

4.3.2 Technical Data Package (TDP) Preparation

The Contractor shall:

a. Evaluate and/or prepare data needed for TO changes.

b. Prepare Engineering Change Orders/Engineering Change Proposals (ECOs/ECPs).

c. Revise technical documents and drawings, as needed, to support work requirements of the routine engineering task.

(CDRL C00D, DI-MISC-80711A/T, Scientific and Technical Report)

4.3.3 Prototype Engineering A request for prototype engineering will normally follow an analytical engineering effort that has pinpointed the cause of deficiencies or problems and determined the course of engineering action necessary to design and develop corrective changes or improvements. The Contractor shall perform prototype engineering services to design, modify source code, and test proposed solutions to address operational capability requirements and/or deficiencies. The Contractor shall submit, in a technical report, a plan for accomplishing the prototype effort and document design, cost, software code activities, and technical data applicable to the prototype.

Work requirements shall include, but may not be limited to:

a. Reviewing data generated during investigation and confirming initial design proposal

b. Identifying prototype software code requirements

c. Identifying and documenting detailed design

d. Conducting system and aircraft testing

FILE NUMBER: FD2060-11-31541/REV 0

e. Preparing ECP and applicable engineering drawing changes

(CDRL C00D, DI-MISC-80711A/T, Scientific and Technical Report; CDRL A002, DI- MGMT-80368A/T, Status Report; CDRL A00D, DI-ADMN-81401B, Contract Change Proposal; CDRL A00G, DI-CMAN-80639C, Engineering Change Proposal; CDRL D002, DI-IPSC-81488, Computer Software Product End Item-Source Code; CDRL E005, DI- QCIC-81536A, Verification Test Information Sheets; CDRL E006, DI-QCIC-81536A, Integration Test Information Sheets; CDRL D003, DI-IPSC-81488, Computer Software Product End Item-Source Code-Test Scripts;;)

4.3.4 Design, Code, Integrate, Test

The Contractor shall implement, integrate, and test all changes to the C-5M software design for all tasks awarded under this PWS. Implementation includes, firmware development, operating system update, timeline optimization, OFP coding, integration and test products to include updates to test scripts used in the Requirements-based Testing (RBT) or integration testing.

Software includes aircraft CSCI and S/SEE software. The Contractor shall maintain software development folders/files in electronic format. The Contractor shall make the development folders/files available for Government review at the Contractor facility on an as requested basis.

The Contractor shall perform CSCI and system-level testing and regression testing to ensure all changes are successfully implemented and to verify no existing capability was degraded or lost.

Testing shall address full component functional and interoperability capabilities. Test environments shall utilize Contractor SIL assets, the engineering support environment, weapon system trainer, and on-aircraft testing as applicable. The Contractor shall deliver a test report of the results identifying what tests were performed. The Contractor shall specifically identify any tests that failed along with the date/time that re-tests were successfully performed. A root cause of why the test failed along with its resolution shall be provided.

The Contractor shall perform bench testing along with software unit and component RBT to verify code changes, as well as, verify that the changes meet the requirement specifications and shall provide a test report of the results via a scientific and technical report. The Contractor shall update integration test scripts for all software impacted and provide a name listing of which scripts were updated, the reason for the update and the change request number or deficiency report number associated with the change via a scientific and technical report. The Contractor shall conduct verification to ensure software is ready for Government witnessed Verification Testing. The Contractor shall also establish a regression test baseline, to include all safety critical failure mode effects testing, for the program to demonstrate that the modified software does not adversely impact the existing functionality of the C-5M. The regression test

FILE NUMBER: FD2060-11-31541/REV 0

procedures shall be documented in Test Information Sheet (TIS), Integration Test Information Sheet (ITIS) or Verification Test Information Sheet (VTIS) format as appropriate for the level of testing. The contractor shall develop, execute, and deliver regression test procedures to ensure that software changes have not introduced unintended impacts upon the existing code base. The Contractor shall deliver a test report of the results for all testing activities. Final submittals of all documentation shall reflect any and all changes.

(CDRL A004, DI-MGMT-81453A,Data Accession List; CDRL C001, DI-IPSC-81441A/T, -Software Product…