FA8525-12-R-31541-0004.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE

2. AMENDMENT/MODIFICATION NO.

FA8525-12-R-31541-0004

3. EFFECTIVE DATE

23 JAN 2013

4. REQUISITION/PURCHASE REQ. NO.

FD2060-11-31541

5. PROJECT NO (If applicable)

6. ISSUED BY CODE

GALAXY (C-5), AFLCMC/WLKB

235 BYRON ST STE 19A

BLDG 300 CML PHN 478 926 6501

ROBINS AFB GA 31098-1670

BUYER: David A. Eldridge/WLKB David.Eldridge@robins.af.mil Phone: (478) 926- 0170 No Collect Calls

7. ADMINISTERED BY (If other than item 6) CODE

FA8525

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code)

CODE

X

9A. AMENDMENT OF SOLICITATION NO.

FA8525-12-R-31541

9B. DATED (SEE ITEM 11)

18-MAY-2012

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers is extended, is not extended. Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods. ( a ) By completing Items 8 and 15, and returning copies of the amendment; ( b ) By acknowledging receipt of this amendment on each copy of the offer submitted; or ( c ) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return 1 copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

ROUTINE

15A. NAME AND TITLE OF SIGNER (Type or print)

15B. CONTRACTOR/OFFEROR

BY ________________________________________________________

(Signature of person authorized to sign)

15C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16B. UNITED STATES OF AMERICA

BY ____________________________________________________

(Signature of Contracting Officer)

16C. DATE SIGNED

FACILITY CODE

NSN 7540-01-152-8070

PREVIOUS EDITION UNUSABLE 30-105 STANDARD FORM 30 (REV. 10-83)

PRESCRIBED BY GSA

FAR (48 CFR) 53.243

X

X X

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

Amendment/Modification FA8525-12-R-31541-0004

Continuation of block 14. DESCRIPTION OF AMENDMENT/MODIFICATION

The purpose of this amendment is to revise the Performance Work Statement (PWS) for implementation of "Contractor Full-Time Equivalent Reporting" in accordance with FY11 National Defense Authorization Act (NDAA), Section 8108, Public Law 112-10. The implementation requires the revision of the PWS to include the requirement for Contractor Full-Time Equivalent Reporting.

a. PWS 13-730GFEA-01, dated 26 July 2012, is hereby revised to include PWS sections 4.13, 4.13.1, 4.13.2, and 4.13.3 and update the PWS date to 23 January 2013.

b. PWS 13-730GFEA-01, dated 23 January 2013, is hereby attached and incorporated into the solicitation as evidenced in Part III, Section J, "List of Attachments," below.

c. All other terms and conditions remain unchanged.

Request for Proposal FA8525-12-R-31541-0004

PART III - LIST OF DOCUMENTS, EXHIBITS, AND OTHER ATTACHMENTS

SECTION J

LIST OF ATTACHMENTS

Form Number Description/File Name Date Number of Pages

13-730GFEA-01 PWS

23JAN2013 102

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

26 July 2012

Revision Record

Revision Number

Revision Date

Page Number(s)

Paragraph Description

Table of Contents

1.0 DESCRIPTION OF SERVICES

1.1 Applicable Documents

1.2 Background

1.3 Scope

2.0 SERVICES Summary

3.0 GOVERNMENT PROPERTY, SERVICES, AND INFORMATION

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

3.2 Contractor Responsibility

3.3 DFARS 252.245-7002, Reporting Loss of Government Property

3.4 Return/Retention of Government Property

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

3.6 Government-Furnished Information (GFI)

3.6.1 Government Automated Information System (AIS)

3.6.2 Wide Area Workflow (WAWF)

4.0 General Information

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.5 C-5 Configuration Control Board (CCB)

4.2.6 Independent Verification & Validation (IV&V)

4.2.7 Integration and Regression Testing with other Agencies

4.2.8 Data Accession List (DAL)

4.3 Engineering Studies and Analyses

4.3.1 Special Studies and Analyses

4.3.2 Prototype Engineering

4.3.3 Regression Testing of Software changes not directly accomplished under a BCC Contract/Task Order .. 24

FILE NUMBER: FD2060-11-31541/REV 0

4.4 System/Software Engineering Environment (S/SEE)

4.4.1 S/SEE Definition

4.4.2 Tools and Materials

4.4.3 Support Facility

4.4.4 S/SEE Availability

4.5 BCC Task Orders

4.5.1 Requirements

4.5.2 Contract/Task Order Kick-Off

4.5.3 Analysis and Specification

4.5.3.1 Weapon System Specification (WSS) and Air Vehicle Specification (AVS)

4.5.4 Design, Code, Integrate, Test

4.5.4.1 CSCI Level

4.5.4.2 System Integration

4.5.4.3 Regression Tests

4.5.4.4 System Verification

4.5.4.5 Aircraft Test Support

4.5.5 Technical Manual Source Data

4.5.6 Flight Data Recorder

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

4.5.8 System Verification Review

4.5.9 Analyze and Identify Impacts and/or Changes to C-5 Certifications

4.5.10 Related Activities and Management

4.5.11 Government Support

4.5.12 Preparation for Use

4.5.13 Configuration Management (CM)

4.5.14 System Safety

4.5.14.1 System Safety Analysis

4.5.15 Quality Assurance

4.5.16 Training

4.5.17 Process Improvement

4.5.18 Technical Baseline Management

4.6 Emergency Block Cycle Change (EBCC) Task Orders

4.7 Technical Manuals

4.8 Technical Data and Computer Software

4.8.1 Data Management

4.8.2 Financial Management

4.8.3 Integrated Product Team (IPT)

4.8.4 Contractor-Furnished Equipment (CFE) Statement

4.8.5 Subcontractor Management

4.9 Procedures and Controls

4.9.1 Task or Order Authorization

4.9.2 Safety and Health

4.9.2.1 Government Safety and Health Regulations

4.9.2.2 Safety and Health Plan/Program

FILE NUMBER: FD2060-11-31541/REV 0

4.9.2.3 Mishap Notification/Investigation

4.9.3 Technical Data Package (TDP) Preparation

4.9.4 Government Access and Inspection of Services

In accordance with FAR 52.246-4, Inspection of Services - Fixed-Price, and/or FAR 52.246-6, Inspection - Time-and-Material and Labor-Hour, the Contractor shall maintain a quality inspection process acceptable to the Government In accordance with FAR 52.246-4 and/or FAR 52.246-6, the Government reserves the right to inspect Contractor performance The Government reserves the right for Government personnel and their Contractor representatives to frequently enter the Contractor’s plant. The Contractor shall provide access badges and parking passes. 47

4.9.5 Travel

4.9.6 Continuation of Mission-Essential Services During a Crisis

4.9.6.1 DFARS 252.237-7023(a), Continuation of Essential Contractor Services / Definitions

4.9.6.2 Designation of Services as Mission-Essential

4.9.7 Points of Contact

4.9.8 Government Security Requirements

4.9.8.1 Government Security Regulations

4.9.8.2 Physical Security for GFP

4.9.8.3 Security Clearance

4.9.8.4 COMSEC

4.9.8.5 Access to Government System

4.9.8.6 External Certification Authority for Network Access

4.9.8.7 Access to Government Facility

4.9.8.8 Identification Credential Requirements

4.9.8.9 Operations Security (OPSEC)

4.9.8.10 Security Incident or Violation

4.9.9 Environmental Management System (EMS)

4.9.10 Green Procurement Program (GPP)

4.9.11 Contractor / Subcontractor Intellectual Property

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

4.10 Other Contractual Requirements

4.10.1 Period of Performance (POP)

4.10.2 Duty and Location

4.11 Technical Support

4.12 Related Activities and Associations with Other Agencies

4.13 Contractor Manpower Reporting Requirements

4.13.1 Reporting Period

4.13.2 Uses and Safeguarding of Information

4.13.3 User Manuals

5.0 APPENDICES

Appendix A: Acronyms

Appendix B: C-5 Template for Maintenance and Flight Crew Technical Order Change

FILE NUMBER: FD2060-11-31541/REV 0

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

Appendix H: CDRL Requirements

Appendix I: Review Entrance/Exit Criteria

FILE NUMBER: FD2060-11-31541/REV 0

1.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 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), collecting 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.

1.1 Applicable Documents

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

FILE NUMBER: FD2060-11-31541/REV 0

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 Personal 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.

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.

FILE NUMBER: FD2060-11-31541/REV 0

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.2g

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 to DR investigations as an interim report within JDRS within the following time periods after Contractor is assigned DR and is notified (e.g. JDRS, email, telephone):

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

Provide final resolution response or resolution plan, including new Estimated Completion Date (ECD), as an interim report within JDRS with a notification to the COR within the following time periods:

CAT I: 45 calendar days CAT II: 100 calendar days COR requested corrective action to the interim report within JDRS shall be completed within 48 hours.

DRs in open status which have been referred to the Contractor shall be updated with an interim report within JDRS every

FILE NUMBER: FD2060-11-31541/REV 0

Performance Objective PWS Paragraph Performance Threshold

80 days with a notification to the COR, with the exception of DRs in open awaiting funds status COR requested corrective action to interim report shall be completed within 48 hours. DRs in open awaiting funds status shall be updated every 350 days. Responses for all categories shall meet the requirement 100% of the time.

Formal Qualification Test Report

(FQT)

4.5.4.2,4.5.4.3,4.5.4.4,4.5.7

For each task order, DO-178B Criticality Levels A through E Computer Software Configuration Items (CSCIs) shall complete all RBT testing of the FQT at a pass rate of 98% or higher. Any Legacy test script failures that the Contractor has not been tasked to update prior to this Contract are not part of this metric.

System Regression Testing shall pass at a rate of 100% with the exception of any regression tests with existing IPRs prior to this Contract. System Integration Testing shall pass at a rate of 100%. System Verification Testing shall pass at a rate of 100%.

Processor Throughput 4.5.3

Processor throughput for the C-5 software configurations shall be measured for each configured software build including engineering builds for all hardware affected by a software build. Processor throughput usage for the final build shall

FILE NUMBER: FD2060-11-31541/REV 0

Performance Objective PWS Paragraph Performance Threshold not increase by 5%. Processor throughput for the final build shall not exceed 90% with an objective of 85% at the processing frame level.

Computer Processor Unit (CPU) Memory

4.5.3

CPU memory for the C-5 software configurations shall be measured for each configured 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.5.3

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

SIL 4.4.3

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 risks shall be reviewed for

updates at least once per month.

Integrated Master Schedule 4.1.2

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

FILE NUMBER: FD2060-11-31541/REV 0

Performance Objective PWS Paragraph Performance Threshold program.

Safety and Health Plan/Program 4.9.2.2 100% compliance.

Mishap Notification 4.9.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 “ ‘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) ….”

“ ‘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

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.

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.

FILE NUMBER: FD2060-11-31541/REV 0

3.3 DFARS 252.245-7002, Reporting Loss of Government Property

(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;

FILE NUMBER: FD2060-11-31541/REV 0

(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 less fair wear and tear from normal usage unless approved in advance by the Procuring Contracting Officer (PCO). Property acquired by the Contractor using Government funds 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 ground integration 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.

FILE NUMBER: FD2060-11-31541/REV 0

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 submittal of CDRL A002, Status Report. The Specification Change Notice (SCN) shall include the part number of the item and quantity, as well as, the basis/reason for the change. Contractor shall track and account for all GFP and GFE in accordance with CDRL A00E, Physical Inventories Report. (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.

The Government will provide Contractor personnel access to the Joint Deficiency Reporting System (JDRS) and the Air Force (AF) Portal. JDRS 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 https://wawf.eb.mil and designate an Electronic Business Point of Contact (EB POC) in the

FILE NUMBER: FD2060-11-31541/REV 0

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 90 calendar 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, CDRL A003 Contract Funds Status Report. 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 register, opportunity and mitigation plan shall include impacts to concurrent running programs and be updated once per month. The risk management status shall either be integrated or be an attachment to the MSR, CDRL A002 Status Report.

The Contractor shall plan and conduct a Program Management Review (PMR). The Contractor shall hold a PMR 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, CDRL A008 Conference 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, CDRL A001 Conference Minutes. 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

FILE NUMBER: FD2060-11-31541/REV 0

accomplished by the Contractor and shall make every effort to ensure there are no resource 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 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 90 calendar days after contract/task order award, CDRL A005 Integrated Master Schedule. 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 three 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 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, and deliver CDRL A008 Conference Agenda and CDRL A001 Conference Minutes for the Kick-Off meeting. 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.

FILE NUMBER: FD2060-11-31541/REV 0

Earned Value Management System (EVMS) requirements for each cost type CLIN if the individual task order cost is equal to or greater than $20M. The Contractor shall use an EVMS 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), CDRL A003.

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), CDRL A006 Contract Performance Report and IMS, CDRL A005 Integrated Master Schedule, 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)

FILE NUMBER: FD2060-11-31541/REV 0

4.2.2 Contract Work Breakdown Structure (CWBS)

The Contractor shall develop and maintain the CWBS, CDRL A007 Contract Work Breakdown Structure, and CWBS dictionary in accordance with DI-MGMT-81334D. 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 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 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-81334D, 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. The Contractor shall complete the initial baseline and host an IBR NLT 90 calendar 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. An agenda, CDRL A008 Conference Agenda and meeting minutes, CDRL A001 Conference Minutes shall be created and delivered by the Contractor.

(CDRL A001, DI-MGMT-81505/T, Conference Minutes; CDRL A008, DI-ADMN-81249A, Conference Agenda)

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 or via video teleconference.or. For each joint review the Contractor shall deliver an agenda, CDRL A008 Conference Agenda and meeting minutes, CDRL A001 Conference Minutes.

FILE NUMBER: FD2060-11-31541/REV 0

The joint reviews shall be as follows:

SRR

FSWG

CERTWG

SRAR/PDR

CDR/TOGC

VRC

TRR

FCA/PCA

For the applicable reviews the Contractor shall deliver a design review information package, CDRL C00B Design Review Information Package. Reviews listed in Appendix I shall use the established Entrance/Exit criteria listed in Appendix I.

The Contractor shall perform a detailed joint System Requirements Review (SRR) with the Government. 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 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 FSWGs shall be conducted in accordance with the Government approved IMS. 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 Critical Design Review (CDR). The VRC will be held thirty (30) days after CDR. 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. The Contractor shall provide, as part of the PDR, a PowerPoint presentation (i/e, first draft) describing each problem report (e.g., DR, FMS PLIs, etc.) and the solution to correct the problem. In addition, the SRAR/PDR shall include a review of baseline processor throughput, bus utilization, and memory usage for the proposed changes.

The Contractor shall perform a CDR, which shall contain the Government approved entrance and

FILE NUMBER: FD2060-11-31541/REV 0

exit criteria accomplished in a CDR, with the goal of accomplishing the detailed design review in no more than three business days. 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 perform a VRC, which shall contain the Government approved entrance and exit criteria accomplished in a VRC, The Contractor shall organize the software update tasks so all VRC efforts are completed with no more than two meetings. Testing venues and methods of testing shall be captured in a PowerPoint presentation as part of the VRC.

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 A008, DI-ADMN-81249A, Conference Agenda; CDRL C00B, DI-SESS-81757A/T, Design Review Information Package;, CDRL C00D, DI-MISC-80711A/T, Scientific and Technical Reports )

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.

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 Data Output (FIDO) Interface Control Document (ICD), CDRL C00E Interface Control Document - FIDO (CDRL C00E, DI-CMAN-81248A/T, Interface Control Document—

FIDO)

FILE NUMBER: FD2060-11-31541/REV 0

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, CDRL E004 Integration Test Information Sheets - Regression and CDRL D007 Computer Software Product - General Test Scripts. The Contractor shall document and deliver the efforts noted in this paragraph in a separate technical report, CDRL C00D Scientific and Technical Report. (CDRL C00D, DI-MISC-80711A/T, Scientific and Technical Reports; E004, DI-QCIC-81536A, Integration Test Information Sheets - Regression; CDRL D007, DI-IPSC-81482/T, Computer Software Product - General Test Scripts)

4.2.8 Data Accession List (DAL)

The Contractor shall maintain a Data Accession List (DAL). The DAL is an index of data or work products generated or modified under the contract but are not covered by existing CDRLs.

Work products and data listed in the DAL shall be delivered to the Government upon request.

(CDRL A004, MGMT-81453A, Data Accession List)

4.3 Engineering Studies and Analyses

The Contractor shall provide engineering studies and analysis in support of C-5 software activities as required by task orders issued bilaterally under this Contract. The Contractor shall flow all requirements stated in this paragraph to the subcontractor as applicable.

4.3.1 Special Studies and Analyses

The Contractor shall perform special studies and analyses that are not defined in depth in the current PWS but fall within the general scope of the C-5 software modernization program. The Contractor shall conduct these special studies and analyses, if requested and authorized by the PCO. The special studies and analysis include but are not limited to:

a. Analysis of potential changes to the program budget, schedule, and/or content, and the impacts thereof

b. Budgetary costs estimates in support of Government contract/task order planning

c. Cost reduction initiatives

d. DR and/or requirements analysis in support of future task orders

FILE NUMBER: FD2060-11-31541/REV 0

When instructed in an 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 assessment, impacted changes and associated testing shall be documented in CDRLs identified within each task order. 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. When instructed in an 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 report of all open software deficiencies against the AMP and RERP configurations.

Specific report format and CDRL requirement will be indentified in the task order. 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.

The Contractor shall also, at the PCO’s request, provide recommendations for potential special studies and analyses to the PCO and/or Government PM.

4.3.2 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 as authorized by task orders. 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, CDRL C00D Scientific and Technical Report.

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

e. Preparing ECP and applicable engineering drawing changes

FILE NUMBER: FD2060-11-31541/REV 0

(CDRL C00D, DI-MISC-80711A/T, Scientific and Technical Report; CDRL A00G, DI- CMAN-80639C,…