HSES_PWS_Revision_4.pdf

Performance-based Work Statement (PWS) for

C-5 Honeywell Software and Engineering Support (HSES)

PWS for C-5 HSES Date: 2017-05-08

PR: FD2060-16-92847 PWS REVISION: 4 Page 2 of 95

Record of Changes

Description of Change Date Revision

Honeywell Draft Review 2017-03-02 0

QAPC Draft Review 2017-03-29 1

Minor Edits; QAPC Draft Review 2017-04-10 2

Released 2017-04-27 3

Updates from PK Review 2017-05-08 4

PR: FD2060-16-92847 PWS REVISION: 4 Page 3 of 95

Table of Contents

1.0 Description of Services

1.1 Objective(s)

1.2 Benefit to United States Air Force

1.3 Background

2.0 Services Summary

3.0 Government Property and Services

3.1 Contractor Responsibility

3.1.1 Federal Acquisition Regulation (FAR) 45.101, [Government Property] Definitions . 12

3.2 Government Property to be Provided

3.3 Loss of Government Property

3.3.1 Definition of Loss of Government Property

3.3.2 Reporting Loss of Government Property

3.4 Return of Government Property

3.5 Government System(s)

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

3.7 Government-Furnished Information (GFI)

4.0 Technical Requirements

4.1 Period and Place of Performance

4.1.1 Contract/Order Period of Performance

4.1.2 Place of Performance

4.2 Program Management

4.2.1 Integrated Program Management (IPM)

4.2.2 Integrated Master Schedule (IMS)

4.2.3 Contractor/Task Order Kick-Off

4.3 Software Update Task Orders

4.3.1 Contractor Integrated Performance Management

4.3.2 Contractor Work Breakdown Structure (CWBS)

4.3.3 Integrated Baseline Review (IBRs)

4.3.4 Joint Reviews

4.3.5 C-5 Configuration Control Board (CCB)

PR: FD2060-16-92847 PWS REVISION: 4 Page 4 of 95

4.3.6 Independent Verification & Validation (IV&V)

4.3.7 Testing with other Agencies

4.3.8 Data Accession List (DAL)

4.4 Engineering Studies and Analyses

4.4.1 Special Studies and Analyses

4.4.2 Prototype Engineering

4.4.3 Regression Testing of Software changes not directly accomplished under a SU

Contract/Task Order

4.5 System/Software Engineering Environment (S/SEE)

4.5.1 S/SEE Definition

4.5.2 Tools, Materials and Specialized Support Equipment

4.5.3 Support Facilities

4.5.4 S/SEE Availability

4.5.5 Diminishing Manufacturing Sources (DMS)

4.5.6 Test Environment Software and Test Script Updates

4.6 SU Task Orders

4.6.1 Requirements

4.6.2 Design, Code, Integrate, Test

4.6.3 Flight Manual Source Data

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

4.6.5 System Verification Review (SVR)

4.6.6 Analyze and Identify Impact and/or Changes to C-5M Certifications

4.6.7 Cybersecurity

4.6.8 Airworthiness Certification

4.6.9 Related Activities and Management

4.6.10 Government Support

4.6.11 Preparation for Use

4.6.12 Configuration Management (CM)

4.6.13 System Safety

4.6.14 Quality Assurance

4.6.15 Training

PR: FD2060-16-92847 PWS REVISION: 4 Page 5 of 95

4.6.16 Process Improvement

4.6.17 Technical Baseline Management

4.7 Emergency Software Update (ESU) Task Order

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.2 Technical Data Package (TDP) Preparation

4.10.3 Travel

4.10.4 Points of Contact

4.10.5 Contractor / Subcontractor Intellectual Property

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

4.11 Technical Support

4.12 Related Activities

4.12.1 Software Development Environment

4.12.2 Integrated Bench Tool (IBT) Development

4.12.3 Operational Flight Program (OFP) Development and Updates

4.12.4 Deficiency Report (DR) Investigations and Analysis

4.12.5 Reverse Engineering

4.12.6 Line Replaceable Unit (LRU) DMS Analysis

4.13 Item Unique Identification (IUID)

4.14 Packaging

4.15 Counterfeit Electronics Parts

4.16 Government-Industry Data Exchange Program (GIDEP)

5.0 General Information

5.1 Continuation of Mission-Essential Services during a Crisis

PR: FD2060-16-92847 PWS REVISION: 4 Page 6 of 95

5.2 Security Requirements

5.2.1 Security Level

5.2.2 Government Security Regulations

5.2.3 Physical Security of GFP

5.2.4 Operations Security (OPSEC)

5.2.5 Communications Security (COMSEC)

5.2.6 Security Clearance

5.2.7 Security Incident or Violation

5.2.8 Security of Contractor System(s)

5.2.9 Access to Government System(s)

5.2.10 External Certification Authority for Network Access

5.2.11 Access to Government Facility

5.2.12 Access to Robins Air Force Base (AFB)

5.2.13 Identification Card

5.2.14 Common Access Card (CAC)

5.3 Environmental Management System (EMS)

5.4 Agency Affirmative Procurement Programs

5.5 Safety Requirements

5.5.1 Contractor Compliance

5.5.2 Voluntary Protection Program (VPP)

5.5.3 Mishap Notification/Investigation

5.5.4 Safety and Health Plan

5.6 Inspection of Services

5.7 Trafficking in Persons

5.8 Contract Manpower Reporting

5.8.1

5.8.2

5.8.3

5.8.4

5.9 Invoicing/Payment and Receipt/Acceptance

6.0 Appendices

PR: FD2060-16-92847 PWS REVISION: 4 Page 7 of 95

Appendix A: Acronyms

Appendix B: Government Furnished Property

Appendix C: References

Appendix D: Review Entry/Exit Criteria

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

Appendix F: Contractor Furnished Equipment (CFE)

Appendix G: Honeywell Hardware

Appendix H: Contract Data Requirements Lists (CDRLs)

PR: FD2060-16-92847 PWS REVISION: 4 Page 8 of 95

1.0 Description of Services

This Performance-based Work Statement (PWS) outlines the tasks and duties required of

Honeywell in the sustainment of software for the C-5M model. The Contractor shall develop multiple fully-tested C-5M compatible aircraft Operational Flight Programs (OFPs) and/or related software support applications in partnership with the Government. The Contractor activities shall include but are not limited to, specification/analysis, engineering development, engineering studies/analyses, software design, associated testing, Technical Data Package (TDP) updates, support of airworthiness and Communication, Navigation, Surveillance/Air Traffic

Management (CNS/ATM) certifications, 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 plan to provide emergency software corrections, and to investigate and resolve on-aircraft software issues as they arise. The Contractor shall maintain the capability to quickly respond to a Government requirement to accomplish an Emergency Software Update

(ESU). The Contractor shall develop a comprehensive plan identifying all resources needed to accomplish ESU corrections providing a safe reliable resolution to a deficiency.

The Contractor shall perform sustaining engineering tasks and accomplish special engineering studies and analysis of service-revealed deficiencies, software deficiencies, obsolescence issues, and enhancements as directed by the Government. In the special engineering and analysis reports, the Contractor shall provide recommendations that fully resolve any 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 provide support tothe Government System Integration Laboratory (SIL) located at Robins Air Logistics Center (ALC) along with any updates or maintenance of contractor SILs to include addressing obsolescence. The Contractor shall maintain all C-5M configurations of the contractor's SIL including updates to support efforts contained in this PWS.

(CDRL A00J, DI-MGMT-81749B, 10 USC 2466 (50/50) Requirements Report)

1.1 Objective(s)

This PWS describes the services required to provide multiple fully-tested C-5M compatible aircraft OFPs, related software support applications, sustaining engineering activities, and SIL maintenance. These services include engineering investigations, specification/analysis, engineering development, software design, associated testing, TDP updates, support of aircraft certifications, support of the Government SIL, support/maintenance of contractor SILs, collection of data to support certification/compliance criteria, and TO updates.

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 outlined in the

PWS. The Contractor shall ensure software updates, fixes, and corrections are provided to the

United States Air Force (USAF) within a reasonable time period as directed by the Government.

It is the Government’s intent to manage OFP updates so as to achieve eighteen to twenty-four month product cycles. The Contractor shall flow down all requirements stated in this PWS to any subcontractor(s) as required.

PR: FD2060-16-92847 PWS REVISION: 4 Page 9 of 95

1.2 Benefit to United States Air Force

This acquisition will benefit the USAF by providing a means to investigate/resolve aircraft deficiencies, service-revealed deficiencies, obsolescence, and maintain the C-5M software configurations, thereby allowing the C-5M fleet to maintain its readiness and availability in support of the AF Mission (…fly, fight, and win…in air, space, and cyberspace).

1.3 Background

It is the intent of the Government to allocate a portion of the system integration activities previous performed by the OEM to the Government. Therefore the Government is seeking to establish a direct contractual relationship with Honeywell in place of what has historically been a sub-contractual relationship through the OEM. Establishing a direct relationship with Honeywell to address the tasks listed in this PWS will bring the required expertise and capability for the

Honeywell developed/sustained portions of the C-5M to the Government SIL.

PR: FD2060-16-92847 PWS REVISION: 4 Page 10 of 95

2.0 Services Summary

Performance

Objective

PWS

Reference Performance Threshold

DR Investigations 4.4.1, 4.11, 4.12.4

For performing investigations successfully identify root cause in accordance with TO 00-35D-54. Performance metrics will only apply to first ten (10) DRs processed in each calendar month.

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 80 calendar 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 calendar days. Responses for all categories shall meet the requirement 100% of the time.

FQT Report 4.6.2.1, 4.6.2.2

4.6.2.3, 4.6.2.4, 4.6.5

For each task order, DO-178B Criticality Levels A through E

Computer Software Configuration Items (CSCIs) shall complete all Requirements-based Testing (RBT) of the Formal

Qualification Test (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. Regression Testing shall pass at a rate of 100% with the exception of any regression tests with existing IPRs prior to this Contract.

Processor Throughput 4.6.1.2 Processor throughput for the C-5M 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 not increase by more than 5%. Processor throughput for any final build shall not exceed 85% with an objective of 80% at the processing frame level.

PR: FD2060-16-92847 PWS REVISION: 4 Page 11 of 95

Performance

Objective

PWS

Reference Performance Threshold

CPU Memory 4.6.1.2 CPU memory for the C-5M 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 more than 5%. CPU memory shall not exceed 85%.

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

SIL 4.5.4 Ensure test venues and software are maintained and configured to support all fielded C-5M aircraft. Ensure the test venues are available 50% of the time for a one-shift operation during the normal five-day workweek. The measure of success is 80 hours of availability in a thirty (30) day calendar period.

Risk Management Plan 4.2.1, 4.6.9

The program risks shall be reviewed for updates at least once per month.

Integrated Master

Schedule

4.2.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 program.

Safety and Health

Plan/Program

5.5 100% compliance.

Mishap Notification

5.5.3

No (0) late mishap notifications per contract/task order year.

Establish requirements-based FQT and structural coverage capability for

FMS, AFCS, CMF, and

TCS OFPs at the Robins

SIL

4.12.3, 4.6.2.1, 4.6.15

DO-178B Criticality Levels A through E shall complete all requirements based FQT at a pass rate of 98% or higher.

Structural coverage capability shall be 100% coverage.

Establish common software development environments (including integrated bench tools) at the Government SIL and

Contractor’s test venues

4.12.1, 4.12.2, 4.12.3, 4.12.4, 4.12.5, 4.5

The differences between the all Contractor’s SILs at all locations shall be no more than 10% for each of the following categories:

Scripts used to compile, link, and build environments

Hardware components

Software tools

FQT software

Contractor Manpower

Reporting

5.8

Within 30 calendar days of contract/order award, the

Contractor shall establish a record for the contract/order in eCMRA including Order Data, Contact Data and Location

Data.

The Contractor shall provide an annual count of contractor/subcontractor personnel performing services and report all contractor/subcontractor labor hours required for performance of services for each fiscal year. All data shall be reported no later than October 31 of the following fiscal year.

PR: FD2060-16-92847 PWS REVISION: 4 Page 12 of 95

3.0 Government Property and Services

3.1 Contractor Responsibility

The Contractor shall be responsible for Government property in their possession in accordance with the Federal Acquisition Regulation (FAR) and applicable supplements including, but not limited to, FAR Part 45, Government Property; FAR 52.245-1, Government Property; and

Defense Federal Acquisition Regulation Supplement (DFARS) Part 245, Government Property.

The FAR and applicable supplements can be accessed at the site below.

http://farsite.hill.af.mil

3.1.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 Government Property to be Provided

Government property to be provided includes items included in Appendix B, Government-

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

(CDRL A00K, DI-MGMT-80441B, Government Property Inventory Report)

3.3 Loss of Government Property

3.3.1 Definition of Loss of Government Property

In accordance with DFARS 252.245-7002, Reporting Loss of Government Property, “loss of

Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, theft, loss due to lack of security, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair

(BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

http://farsite.hill.af.mil/

PR: FD2060-16-92847 PWS REVISION: 4 Page 13 of 95

3.3.2 Reporting Loss of Government Property

The Contractor shall use the Defense Contract Management Agency (DCMA) eTools software application to report loss of Government property at the site below. The reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract/order.

http://www.dcma.mil/aboutetools.cfm

3.4 Return of Government Property

All property provided by the Government remains the property of the Government and shall be returned to the Government upon completion of the contract/order or as directed by the

Government. All Government property shall be returned to the Government in the condition provided 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 AFLCMC/WLS. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government upon completion of the contract/order or as directed by

AFLCMC/WLS. All Department of Defense (DD) Form 1423, Contract Data Requirements List

(CDRL), deliverables become the property of the Government upon receipt.

3.5 Government System(s)

The Government will provide Contractor personnel access to system(s) necessary to perform tasks under the contract/order. Upon completion/termination of the contract/order or transfer/termination of Contractor personnel, the Contractor shall ensure the system account(s) are closed.

Government systems to be accessed are:

Joint Deficiency Reporting System (JDRS)

AF Portal

C-5 Form 107 System

C-5 Form 202 System

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

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

The Government will provide access to C-5M aircraft, as required and if available, in order for the Contractor to accomplish sustaining engineering or software sustainment activities. The

Contractor shall plan to accomplish any required aircraft ground integration testing for software in no more than two events for each task order unless specifically approved by the Government.

The Contractor shall plan to accomplish the majority of engineering or 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 Contractor to maintain the SILs.

http://www.dcma.mil/aboutetools.cfm

PR: FD2060-16-92847 PWS REVISION: 4 Page 14 of 95

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

PR: FD2060-16-92847 PWS REVISION: 4 Page 15 of 95

4.0 Technical Requirements

4.1 Period and Place of Performance

4.1.1 Contract/Order Period of Performance

The PoP is defined in the contract/task order.

4.1.2 Place of Performance

These services shall be performed at the Government SIL and/or the Contractor’s C-5M software development/test facilities. Engineering investigations and testing will take place as required at

Government and Contractor facilities. Travel to C-5M operating locations will be coordinated with the Government program manager as required.

4.2 Program Management

4.2.1 Integrated Program Management (IPM)

The Contractor shall provide 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

(CFSR). 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 Monthly Status Report (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 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 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;

PR: FD2060-16-92847 PWS REVISION: 4 Page 16 of 95

CDRL A008, DI-ADMN-81249B/T Conference Agenda)

4.2.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 Program Management

Report – 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-81861A/T, Integrated Program Management Report –

Integrated Master Schedule)

4.2.3 Contractor/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 contracted activity at the contract/task order kick-off meeting.

(CDRL A001, DI-ADMN-81505/T, Conference Minutes;

CDRL A008, DI-ADMN-81249B/T, Conference Agenda)

PR: FD2060-16-92847 PWS REVISION: 4 Page 17 of 95

4.3 Software Update Task Orders

Software maintenance task orders under this PWS shall be treated as stand-alone contracts.

Earned Value Management System (EVMS) requirements apply 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. Contract

Performance Report (CPR) reporting will only apply to Cost type CLINs.

4.3.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, 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.234-7002 and the Contractor’s own documented system description. The CPR, CDRL

A006 Integrated Program Management Report – Contract Performance Report and IMS, CDRL A005 Integrated Program Management Report – 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.234-7001, Notice of Earned Value Management System, and 252.234-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-81861A/T, Integrated Program Management Report – Integrated

Master Schedule;

CDRL A006, DI-MGMT-81861A/T, Integrated Program Management Report – Contract

Performance Report)

PR: FD2060-16-92847 PWS REVISION: 4 Page 18 of 95

4.3.2 Contractor 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.3.3 Integrated Baseline Review (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-81249B/T, Conference Agenda)

4.3.4 Joint Reviews

The Contractor shall plan to accomplish all joint reviews (including joint reviews with subcontractors) on Robins AFB, GA or the Honeywell facility in Albuquerque, NM or via video teleconference. For each joint review, the Contractor shall deliver an agenda, CDRL A008

Conference Agenda and meeting minutes, CDRL A001 Conference Minutes.

PR: FD2060-16-92847 PWS REVISION: 4 Page 19 of 95

The joint reviews shall be as follows:

System Requirements Review (SRR)

Flight Station Working Group (FSWG)

Certification Working Group (CERTWG)

Software Requirements Analysis Review (SRAR)/Preliminary Design Review (PDR)

Critical Design Review (CDR)/ Technical Order Guidance Conference (TOGC)

Verification Review Council (VRC)

Test Readiness Review (TRR)

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

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

The Contractor shall perform a detailed joint SRR with the Government. Testing venues and methods of testing shall also be a part of this event.

The Contractor shall conduct FSWG meetings early in any software update task order schedule to validate user interface requirements. The FSWG invitee list should include representatives from the Contractor, AFLCMC/WLS, 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 CDR. The VRC will be held 30 calendar 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. For changes involving the Primary Flight Display

(PFD), the contractor shall provide any necessary documentation and support to aid the

Government in obtaining approval and certification from the Air Force Safety Office for the PFD change. 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./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. Opportunities for source code optimization shall also be identified.

The Contractor shall perform a CDR, which shall contain the Government approved entrance and exit criteria accomplished in a CDR, with the goal of accomplishing the detailed design review in

PR: FD2060-16-92847 PWS REVISION: 4 Page 20 of 95 no more than three business days. A TOGC shall also be held within 60 calendar days after contract award 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 (CDRL C00D Scientific and Technical Reports) and included as part of the minutes for the CDR. The Contractor shall provide, as part of the CDR, a PowerPoint presentation (i.e./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-81249B/T, Conference Agenda;

CDRL C00B, DI-SESS-81757A/T, Design Review Information Package (DRIP);

CDRL C00D, DI-MISC-80711A, Scientific and Technical Reports)

4.3.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.3.6 Independent Verification & Validation (IV&V)

The Contractor shall support, in the Contractor’s or Government facilities, the IV&V of any conceptual engineering solutions or software products they may develop or test. This shall also include supporting software products (e.g. simulations, models, development environments, etc.)

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 C004 Interface Control Document – FIDO.

(CDRL C004, DI-SESS-81248B/T, Interface Control Document (ICD))

4.3.7 Testing with other Agencies

The Contractor shall support formal qualification, integration, regression, ground and flight 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

PR: FD2060-16-92847 PWS REVISION: 4 Page 21 of 95 dry-run integration/regression tests of the task order software changes shall be performed in the

Government SIL to support independent verification/validation activities. This may create the need to update regression test procedures and scripts. All test procedures and scripts shall be delivered to the Government with appropriate rights and licensing, CDRL E003 Integration

Test Information Sheets – Regression, CDRL E004 Verification Test Information Sheets, 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 Reports.

(CDRL C00D, DI-MISC-80711A, Scientific and Technical Reports;

CDRL D007, DI-IPSC-81488/T, Computer Software Product – General Test Scripts;

CDRL E003, DI-QCIC-81536/T, Integration Test Information Sheets – Regression;

CDRL E004, DI-QCIC-81536, Verification Test Information Sheets)

4.3.8 Data Accession List (DAL)

The Contractor shall maintain a 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, DI-MGMT-81453A, Data Accession List)

4.4 Engineering Studies and Analyses

The Contractor shall provide engineering studies and analysis in support of service-revealed deficiencies and C-5M software activities as required by task orders issued under this contract.

The Contractor shall flow all requirements stated in this section to subcontractors as applicable.

4.4.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-5M engineering and software sustainment activities. 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. Budgetary costs estimates in support of Government contract/task order planning

b. Analysis of impacts to changes to program requirements that affect program budget, schedule, and/or content

c. Cost reduction initiatives

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

e. Investigation and resolution of service-revealed deficiencies

f. Investigation of and potential solutions to update or replace items affected by obsolescence (e.g. aircraft components, support equipment, SIL items)

g. Analysis of alternatives in support of future task orders

When instructed in an engineering studies and analysis task order for a software-related deficiency, the Contractor shall determine the corrective action of a software deficiency to the

PR: FD2060-16-92847 PWS REVISION: 4 Page 22 of 95 level necessary to clearly show that the corrective action is viable (e.g. pseudo-code level, source code level, developmental build). The Contractor shall provide a safety/air-worthiness risk assessment that details at the Computer Software Upgrade (CSU) level the impacted software changes and the testing required to maintain the C-5M 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 for C-5M configurations. Specific report format and CDRL requirement will be identified in the task order. The report shall be developed from a list of 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), that the Government has reviewed and agrees to track as an unresolved deficiency against the software.

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.4.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 subsystems/software, 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, hardware, software code activities, and technical data applicable to the prototype, CDRL C00D Scientific and Technical

Reports.

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

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

b. Identifying prototype hardware and software code requirements

c. Identifying and documenting detailed design

d. Conducting system and aircraft testing

e. Preparing Engineering Change Proposal (ECP) and applicable engineering drawing changes

PR: FD2060-16-92847 PWS REVISION: 4 Page 23 of 95

Deliverables will be identified for the specific task order and will include all or a subset of the following:

(CDRL A00G, DI-SESS-80639D/T, Engineering Change Proposal;

CDRL B001, TM-86-01P, Technical Manual Contract Requirement;

CDRL B002, DI-SESS-81000E/T, Product Drawings/Models and Associated Lists;

CDRL C001, DI-IPSC-81441A/T, Software Product Specification;

CDRL C002, DI-IPSC-81433A/T, Software Requirements Specification (SRS);

CDRL C003, DI-IPSC-81434A/T, Interface Requirements Specification (IRS);

CDRL C004, DI-SESS-81248B/T, Interface Control Document (ICD);

CDRL C005, DI-SAFT-80101C, System Safety Hazard Analysis Report;

CDRL C006 DI-IPSC-81427A, Software Development Plan;

CDRL C007, DI-SESS-81768, Airworthiness Certification Criteria Report;

CDRL C008, DI-SESS-81766, Airworthiness Specification;

CDRL C009, DI-HFAC-80746C/T, Human Engineering Design Approach Document –

Operator;

CDRL C00A, DI-HFAC-80747C/T, Human Engineering Design Approach Document –

Maintainer;

CDRL C00B, DI-SESS-81757A/T, Design Review Information Package (DRIP);

CDRL C00C, DI-IPSC-81442A, Software Version Description;

CDRL C00D, DI-MISC-80711A, Scientific and Technical Reports;

CDRL C00G, DI-MGMT-81844/T, Information Assurance (IA) Test Plan;

CDRL C00H, DI-MGMT-81843/T, Information Assurance (IA) Test Report;

CDRL C00J, DI-SDMP-81465A/T, Performance Specification – Air Vehicle Specification;

CDRL C00K, DI-IPSC-81431A/T, System/Subsystem Specification;

CDRL C00L, DI-IPSC-81432A/T, System/Subsystem Design Description;

CDRL C00M, DI-IPSC-81435A, Software Design Document;

CDRL C00N, DI-SDMP-81465A/T, Performance Specification – Weapon System

Specification;

CDRL C00P, DI-EDRS-81729, VHSIC Hardware Description Language (VHDL)

Documentation;

CDRL C00Q, DI-SDMP-81465A/T, Performance Specification Documents;

CDRL C00S, DI-MISC-80508B/T, Technical Report – Study/Service;

CDRL C00T, DI-SESS-80198B, Internal Loads and Static Strength Analysis Report;

PR: FD2060-16-92847 PWS REVISION: 4 Page 24 of 95

CDRL C00U, DI-EMCS-81540B, Electromagnetic, Environmental Effects (E3) Integration and Analysis Report (E3IAR);

CDRL D001, DI-AVCS-80700/T, Computer Software Product End Item – Compiled

Loadable Image;

CDRL D002, DI-IPSC-81488/T, Computer Software Product – Source Code;

CDRL D003, DI-IPSC-81488/T, Computer Software Product – Source Code – Test Scripts;

CDRL D004, DI-AVCS-80700/T, Computer Software Product End Items – Software

License;

CDRL D005, DI-AVCS-80700/T, Computer Software Product End Items – Software

Toolsets and Associated Documentation;

CDRL D006, DI-IPSC-81429A/T, Software Transition Plan;

CDRL D007, DI-IPSC-81488/T, Computer Software Product – General Test Scripts;

CDRL E001, DI-NDTI-80809B/T, Test/Inspection Report;

CDRL E002, DI-NDTI-80566A/T, Test Plan;

CDRL E003, DI-QCIC-81536/T, Integration Test Information Sheets – Regression;

CDRL E004, DI-QCIC-81536, Verification Test Information Sheets;

CDRL E005, DI-QCIC-81536, Integration Test Information Sheets – Development;

CDRL E006, DI-IPSC-81440A, Software Test Report;

CDRL E007, DI-IPSC-81438A, Software Test Plan;

CDRL E008, DI-IPSC-81439A, Software Test Description;

CDRL E009, DI-QCIC-80553A, Acceptance Test Plan;

CDRL E00A, DI-QCIC-81890, Qualification Test Report;

CDRL E00B, DI-NDTI-81307A, First Article Qualification Test Plan and Procedures;

CDRL E00C, DI-EMCS-80201C, Electromagnetic Interference Test Procedure (EMITP);

CDRL E00D, DI-EMCS-80200C, Electromagnetic Interference Test Report (EMITR))

4.4.3 Regression Testing of Software changes not directly accomplished under a SU

Contract/Task Order

The Contractor shall perform subsystem regression testing of software changes with the latest version of software that functions with C-5M to ensure full functionality of the architecture is preserved. For software updates (e.g. AFCS, FMS, CMF, etc.) in or associated with a SU or changed during a SU cycle, the Contractor shall ensure all changes are fully functional with either fielded software versions or SUs currently in work. The Contractor shall develop, update, modify and deliver all regression test procedures, CDRL E003 Integration Test Information

Sheets – Regression, to the Government as appropriate to support the activity. The Contractor shall document the regression testing results in separate technical reports, CDRL E001

Test/Inspection Report.

PR: FD2060-16-92847 PWS REVISION: 4 Page 25 of 95

System level regression testing shall be performed by the Government in the Government SIL and shall be supported by the Contractor.

(CDRL E001, DI-NDTI-80809B/T, Test/Inspection Report

CDRL E003, DI-QCIC-81536/T, Integration Test Information Sheets – Regression;)

4.5 System/Software Engineering Environment (S/SEE)

4.5.1 S/SEE Definition

The collection of all hardware and software tools a system developer uses to build and test software or systems.

4.5.2 Tools, Materials and Specialized Support Equipment

The Contractor shall obtain and integrate software and hardware tools and material, as applicable, to the test station/benches designated as the S/SEE. For changes to the SIL environment, the Contractor shall utilize Commercial-Off-The-Shelf (COTS) tools and materials to the greatest extent possible, or provide unlimited or Government purpose rights and source code for Government use of any tools or materials developed at government expense under this contract/task order.