Attch9_PWS_v1.4.pdf

Performance Based Work Statement for

Contractor Logistics Support & Services (CLS&S) VI for RQ-4B Global Hawk Enhanced Integrated Sensor Suite (EISS)

Contract #: FA8577-21-C-0002

PR#: F3QCAC0352A101

14 December 2020

Prepared by AFLCMC/WIG

235 Byron St, Ste 19A

Robins AFB, GA 31098-1670

DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD Contractors only (Critical Technology and Direct Military Support) (26 November 2013). Other requests shall be referred to AFLCMC/WIG, 235 Byron St, Suite 19A, and Robins

AFB, GA 31098- 1670.

CHANGES AND REVISIONS

TYPE DESCRIPTION PAGE/PARA DATE

Contract #: FA8577-21-C-0002; PR#: F3QCAC0352A101

Table of Contents

Table of Contents ______________________________________________________________ i

1.0 DESCRIPTION OF SERVICES __________________________________________________ 1

1.1. Objectives: ____________________________________________________________________ 1

1.2. Benefit to the United States Air Force (USAF): ________________________________________ 1

1.3. Background: ___________________________________________________________________ 2

2.0. SERVICES SUMMARY _____________________________________________________ 2

3.0. GOVERNMENT PROPERTY & SERVICES _________________________________________ 4

3.1. Government Property: __________________________________________________________ 4

3.2. Contractor Responsibility: ________________________________________________________ 5

3.3. Reporting Government Property: __________________________________________________ 5

3.3.1. Loss of Government Property: ___________________________________________________________ 5

3.4. Return and Retention of Government Property: _____________________________________ 5

3.4.1. Return/Retention: ____________________________________________________________________ 5

3.4.2. Generated Materials: __________________________________________________________________ 6

3.4.3. Contractor Acquired Property (CAP): _____________________________________________________ 6

3.5. Financial Improvement and Audit Readiness (FIAR) Compliance: _________________________ 6

3.6. Base Support: __________________________________________________________________ 6

3.7. Government and Contractor Systems: ______________________________________________ 6

4.0. TECHNICAL INFORMATION __________________________________________________ 6

4.1. Period and Place of Performance: _______________________________________________ 6

4.2. Place of Performance: ___________________________________________________________________ 6

4.3. Contract Data Requirements List (CDRL) ____________________________________________________ 7

4.3.1. Quality of CDRL Deliverable: ____________________________________________________________ 8

4.3.2. Receipt of CDRL Deliverable: ____________________________________________________________ 8

4.2. Program Management: __________________________________________________________ 8

4.2.1. Performance and Financial Reporting: ____________________________________________________ 9

4.2.2. Program and Sustainment Meetings: ____________________________________________________ 10

4.2.3. Risk/Issue Management: __________________________________________________________ 11

4.3. Support Services Personnel: ___________________________________________________ 11

4.3.1. Field Service Representatives (FSRs): ____________________________________________________ 11

4.3.2. Mission Essential Functions: _______________________________________________________ 12

4.4. Software: __________________________________________________________________ 12

4.4.1. Software License Inventory:____________________________________________________________ 12

4.4.2. Assessment & Authorization (A&A): _____________________________________________________ 12

4.4.3. Cyber Security (CS) of Fielded and Sustained Systems: ______________________________________ 12

4.5. Engineering: __________________________________________________________________ 13

4.5.1. Engineering Activity Report: ___________________________________________________________ 13

4.5.2. Engineering Requirements and Scheduled Maintenance Support: _____________________________ 14

4.5.3. Technical Publications & Engineering Data Package: ________________________________________ 14

4.5.4. Weapon System Integrity (WSIP) Program ________________________________________________ 15

4.5.5. Diminishing Manufacturing Sources and Material Shortages (DMSMS): _________________________ 17

4.5.6. Technology Refresh: __________________________________________________________________ 18

4.5.7. Image Quality Investigation and Support: _________________________________________________ 18

4.5.8. Product Improvement Technical Solutions ____________________________________________ 19

4.6. Data Accession List (DAL): ____________________________________________________ 19

5.0. GENERAL INFORMATION: __________________________________________________ 19

5.1. Continuation of Mission-Essential (M-E) Services During a Crisis: _____________________ 19

5.2. Security Requirements: ______________________________________________________ 19

5.2.1. Program Protection: ______________________________________________________________ 20

5.2.2. Operations Security (OPSEC): _______________________________________________________ 20

5.2.3. Communications Security (COMSEC): ________________________________________________ 20

5.2.4. Security Clearance: _______________________________________________________________ 20

5.2.5. Security Incident or Violation: ______________________________________________________ 21

5.2.6. Security of Contractor’s System(s): __________________________________________________ 21

5.2.7. Common Access Card: ____________________________________________________________ 21

5.3. Environmental Management System (EMS): ______________________________________ 21

5.4. Agency Affirmative Procurement Programs: ____________________________________ 21

5.5. Safety Requirements: ________________________________________________________ 21

5.5.1. Contractor Compliance: ___________________________________________________________ 22

5.5.2. Voluntary Protection Program (VPP): ________________________________________________ 22

5.5.3. Mishap Notification and Investigation: ___________________________________________________ 22

5.5.4. Safety and Health Plan: ___________________________________________________________ 22

5.6. Inspection of Supply and Services: ______________________________________________ 22

5.7. Trafficking in Persons: _______________________________________________________ 23

5.8. Contractor Management Reporting: ____________________________________________ 23

5.9. Anthrax Information: ________________________________________________________ 23

5.10. Combat Related Tasks: _____________________________________________________ 23

5.11. Performance Flexibility: ____________________________________________________ 23

5.12. Shut-Down of Operations: __________________________________________________ 24

5.13. Travel: __________________________________________________________________ 24

5.14. 50/50 Title 10 Reporting: ___________________________________________________ 24

5.15. Uses and Safeguarding of Information: ________________________________________ 24

5.16. Precious Metals Program: __________________________________________________ 25

5.17. Associated Contract Agreements: ____________________________________________ 25

5.18. Requirements Flow-Down: __________________________________________________ 25

6.0. REFERENCES: __________________________________________________________ 25

1.0 DESCRIPTION OF SERVICES

1.1. Objectives:

This Performance-based Work Statement (PWS) describes the services required by the Global Hawk Program Office (GHPO), AFLCMC/WIG, to sustain the Enhanced Integrated Sensor Suite (EISS) in an operational (serviceable) state to meet assigned missions. The services include:

• Program Management

• Financial Management

• Support Services Personnel

– Field Service Representative (FSR)

– Maintenance Data

• Software

– Software License Inventory

– Assessment and Authorization (A&A)

– Cyber Security (CS) of Fielded and Sustained Systems

• Engineering

– Engineering Activity Report (EAR)

– Reliability, Availability & Maintainability

– Technical Publications/Updates (Source Data)

– Configuration Management

– Weapon System Integrity Programs (WSIP)

– Deployment Planning and Execution

– Image Quality Investigation and Support

– Safety

– Technical Refresh

– Diminishing Manufacturing Sources and Material Shortages (DMSMS)

– Data Accession List

1.2. Benefit to the United States Air Force (USAF):

The support and services requirements will benefit the USAF by ensuring the EISS sub-system installed on the RQ-4 (GH) is mission capable in support of national defense strategic initiatives and the Department of Defense (DoD) Intelligence, Surveillance and Reconnaissance (ISR) requirements. The EISS is part of an integrated ISR constellation providing accurate, timely, decision-quality and critical information to decision-makers, shooters and other warfighters.

1.3. Background:

The EISS, one of numerous payloads installed on the RQ-4 GH Block 30I and 30M weapon systems provides imagery and actionable Imagery Intelligence (IMINT) products to operational users. The RQ-4 GH weapon system is comprised of Air, Ground, and Support segments.

Holistically, the major components of the various segments include the Air Vehicle (AV), vehicle/mission management systems, data links (airborne component), and the EISS.

The EISS provides an operational capability to collect, transmit, and process IMINT information.

During daytime, clear weather conditions, the EISS Electrical Optical (EO) sensor produces high-resolution spot mode imagery that provides valuable intelligence information. During night, clear weather operations, or in environments with high thermal gradients, the Infra-Red (IR) sensor produces high-resolution spot mode imagery at short, near-nadir (overhead) ranges. The Synthetic Aperture Radar (SAR) sensor provides around-the-clock, all-weather IMINT collection capabilities, producing high-resolution spot mode imagery. The EISS installed on the GH weapon system supports missions in AFRICOM, EUCOM, NORTHCOM, INDIOPACOM, SOUTHCOM and CENTCOM as required.

2.0. SERVICES SUMMARY

This contracting effort includes the provisions of services and supplies that Raytheon Space and Airborne Systems (SAS), a major business sector of Raytheon Company, and its Subcontractors shall provide to sustain the EISS. The operational locations and flying hours of Block 30 aircraft capable of employing the EISS are defined in Appendix A, FY21-26 Flying Hours and Sorties

(EISS).

The Services Summary (SS) below identifies the Performance Objectives (POs) and Thresholds that are significant to ensure the EISS are mission capable. The POs provide the criteria by which the Contractor’s performance will be evaluated during the five periods of performance. The first period of measurement is the first one-year basic with the remaining four periods correlating to the four one-year options.

Table 1: Services Summary

Performance Requirement PWS Reference Performance Threshold

Conduct a Contractor Safety Program with minimal or no mishaps caused by the Contractor.

5.5.3 Mishaps per period of performance

• Zero Class A or B mishaps

• No more than two Class C mishaps

Deliver all documentation in a timely manner per the CDRL or the mutually negotiated and revised delivery date.

4.3.2 There shall be no more than zero (0)

late submission(s) of deliverables per contract period unless the Contractor has requested/negotiated a revised delivery date with the United States Government (USG) Primary Contracting Officer (PCO). The Contractor shall notify the USG if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

Deliver quality documentation with minimal errors. The error shall be corrected and resubmitted per the applicable Contract Data Requirements List, DD Form

4.3.1 There shall be no more than 10 total

rejection(s) of deliverables per period of performance (contract period). The Government will reject a deliverable if one or more technical errors per deliverable or two or more minor errors are found per twenty pages of the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is exemplified by a typographical error or a grammatical error. The rejected deliverable shall be corrected and resubmitted within 10 business days of notification of Government rejection.

Notify and report all mishaps on time.

5.5.3 Zero allowance for late mishap

notification per period of performance.

Mishap notification shall be no more than four hours.

Adhere to security requirements per Program Protection Plan and Security Guide.

5.2 Zero allowance for security violations

per period of performance (PoP). No more than one security incident per PoP.

Manage and fill FSRs planned personnel positions and unplanned personnel vacancies within allotted time.

4.5.1 Planned. 95 percent of all planned

positions defined at contract award shall be filled within 10 business days of contract award. Remaining 5 percent of all planned positions defined at contract award shall be filled within 35 business days of contract award.

Unplanned. Unplanned staffing changes during the contract period due to position vacancy shall not exceed 60 calendar days, with a goal to fill vacancy within 45 calendar days of the unplanned vacancy.

Adhere to maintenance and operational steps expressed in technical data, flight/ operational manuals, or engineering direction.

4.5.1.2 Meet or exceed:

Warnings & Cautions: 100% (T/O)

Maintenance & Operational: 85% / 90% (T/O)

Contractor Manpower Reporting (if over $3M)

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 a count of contractor/ subcontractor personnel performing services for each fiscal year and report all contractor/subcontractor labor hours required for performance of services for each fiscal year. An average of a typical repair years’ worth of repair activities is acceptable. Data from Oct through Sep of the FY shall be reported no later than the succeeding 31 Oct of the following fiscal year.

Table 2 identifies RQ-4 GH Weapon System Performance Objectives (PO). These POs, as reported in Logistics, Installations and Mission Support-Enterprise View (LIMS-EV), are provided to bound levels of EISS support and services to meet overarching customer requirements in conjunction with Appendix A, FY21-26 Flying Hours and Sorties (EISS).

Table 2: RQ-4 EISS Performance Objectives

3.0. GOVERNMENT PROPERTY & SERVICES

3.1. Government Property:

The Government property includes Government Furnished Property (GFP), Government Furnished Equipment (GFE), and Government Furnished Material (GFM) that will be made

Performance Objective Target Unit of Measure

Aircraft Availability (AA) – Overall Aircraft Performance 72 Percent

Not Mission Capable (NMC) for EISS 10 Percent

Not Mission Capable for Supply (NMCS) for EISS 2 Percent

Not Mission Capable for Maintenance- Unscheduled (NMCMU) for EISS

3 Percent available for activities under the CLS VI contract. GFP include assets furnished for repair, maintenance, overhaul or modification. USG Property/Services are authorized per Appendix B, Government Property.

3.2. Contractor Responsibility:

The Contractor shall be responsible for USG property in their possession per the Federal Acquisition Regulation (FAR) and as specified in the contract. The Contractor shall define all GFP, GFE, GFM, Government Furnished Services and Contract Furnished Materials (CFM) required for the execution of this PWS. The Contractor shall return or retain USG property as required. See para. 3.4., Return and Retention of Government Property.

3.3. Reporting Government Property:

The Contractor shall report “GFM by National Stock Number.” Additionally, the Contractor shall report all Government Property in their possession. The latter will result in a GFP baseline to enable proper accounting and accountability. (A001, Government Furnished Materials By National Stock Number, DI-ILSS 80727; A002, Government Furnished Property Inventory Baseline Report, DI-MGMT-80441C).

3.3.1. Loss of Government Property:

The Contractor shall use the Defense Contract Management Agency (DCMA) eTools to report loss of USG property. The application is located at http://www.dcma.mil/aboutetools. The Contractor shall comply with FAR 52.245.1. The Contractor shall ensure that its property management system provides adequate management control measures. The Contractor shall report losses of USG property outside normal process variation, e.g., items that cannot be located after a reasonable search; theft; damage resulting in unexpected harm to property requiring repair to restore the item to usable condition; or destruction resulting from incidents that render the item useless for its intended purpose or beyond economical repair. This reporting requirement does not change liability provisions or other reporting requirements that may exist under the contract.

3.4. Return and Retention of Government Property:

3.4.1. Return/Retention:

All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. The Contractor shall provide the necessary documentation required to retain, return or dispose of the USG property within 60 business days after contract award.

(CDRL A003, Status of Government Furnished Equipment (GFE) Report, DI-MGMT-80269/T).

The Contractor shall:

• Submit documents for retention of USG property per FAR Part 45, Subpart 45.106, “Transferring Accountability”

• Return all USG property in the condition it was originally provided unless approved in advance by the PCO

• Dispose of property per MIL STD 3019, Parts Management, SD-19, Parts Management Guide, and as authorized by the PCO http://www.dcma.mil/aboutetools

3.4.2. Generated Materials:

The Contractor shall return all materials generated under the contract to the USG upon completion of the task order. All CDRL deliverables become the property of the USG upon receipt.

3.4.3. Contractor Acquired Property (CAP):

The USG obtains title to CAP acquired, fabricated, or otherwise provided by the Contractor to perform tasks under the contract per FAR 45.402, Title to Contractor-Acquired Property, and clauses listed in this PWS and the contract. The Contractor shall return all CAP to the USG upon completion of the contract unless retained by the Contractor for continued use under a successor contract. If retained by the Contractor for a successor contract, CAP becomes USG Property and the Contractor shall adhere to the guidance for retention identified in PWS paragraph 3.4.1, “Return and Retention.”

3.5. Financial Improvement and Audit Readiness (FIAR) Compliance:

The Contractor shall adhere to FIAR guidance and policy per DoDI 5000.64, “Accountability and Management of DoD Equipment and Other Accountable Property”; DODI 4161.02, “Accountability and Management of Government Contract Property”; and, DODI 4140.01, “DoD Supply Chain Material Management Policy.”

3.6. Base Support:

The USG will furnish property incidental to the place of performance as prescribed in the Base Support Agreements. Nominally, the property includes office space and equipment, i.e., computer equipment, software, output device(s), phone/phone line, facsimile equipment, reproduction equipment and office supplies in accordance with applicable FAR and the contract.

3.7. Government and Contractor Systems:

The Contractor shall use a combination of contractor and USG systems to support the functionalities and the inherent tasks required by this PWS. The Contractor shall provide GHPO personnel access to the data (database) systems required by the USG team to support this sustainment effort.

4.0. TECHNICAL INFORMATION

4.1. Period and Place of Performance:

The contract period of performance (PoP) is defined within the contract.

4.2. Place of Performance:

The place of performance will be at the Contractor and Subcontractor’s facilities, to include other Raytheon facilities, and designated USG operating locations. The USG operation locations include a Main Operating Base (MOB) and the Forward Operation Locations (FOLs). The MOB is located at Beale AFB, CA. The FOLs are located at Andersen AFB, Guam (including re-location); Naval Air Station Sigonella, Italy. Additional locations of performance may include operations/sustainment re-location, operational exercises, designated sustainment facilities, and airshows as approved by the PCO. Support of these locations may require a contracting action.

4.3. Contract Data Requirements List (CDRL)

Document Identifier

Data Item Description

Title PWS Reference

A001 DI-ILSS 80727 Government Furnished Materials By National Stock Number

3.3

A002 DI-MGMT-80441C Government Furnished Property Inventory Baseline Report

3.3

A003 DI-MGMT-80269/T Status of Government Furnished Equipment (GFE) Report

3.4.1

A004 DI-MGMT-81468/T Contract Funds Status Report, 4.4.1 A005 DI-MISC-80508B/T Contractors Progress, Status, and Management

Report 4.4.1.2

A006 DI-FNCL-82162 Cost and Hour (FlexFile) 4.4.1.3 A007 DI-MGMT-82164 Quantity Data Report 4.4.1.3 A008 DI-MGMT-81765 Contractor Business Data Report DD Form 1921-3 4.4.1.3 A009 DI-MGMT- 80259/T Physical Inventories Report 4.4.1.4 A010 DI-ADMN-81373/T Presentation Material 4.4.2.1 A011 DI-ADMN-81249A Conference Agenda 4.4.2.1,

4.4.2.3 A012 DI-ADMN-81250B Conference Minutes 4.4.2.1,

4.4.2.3 A013 DI-MISC-80508/T EISS Software License Inventory 4.6.1 A014:

Optional

DI-MGMT-

80368A/T

Engineering Activity Report 4.7.1

A015:

Optional

DI-SESS-81000E/T Product Drawings/Models and Associated Lists 4.7.3.2

A016:

Optional

DI-SESS-81495 Failure Mode Effects and Criticality Analysis

(FMECA)

4.7.4.2

A017:

Optional

DI-SAFT-80101 Sub/system Safety Hazard Analysis (SSHA) 4.7.4.2

A018:

Optional

DI-MGMT-81988 Critical Item Characteristics List 4.7.4.3

A019:

Optional

DI-MGMT-

80508B/T

Minimum Acceptable Performance (MAP) Analysis 4.7.4.3

A020:

Optional

DI-MISC-80508A/T FRACAS Report 4.7.4.4

A02:

Optional

DI-MISC-80508B/T RAM Report 4.7.4.5

A022:

Optional

DI- MGMT-81899 DMSMS Implementation Plan 4.7.5

A023:

Optional

DI- MISC-80508B/T DMSMS Management Program Reports 4.7.5

A024:

Optional

DI-MISC-80508B/T Sustainment Technology Refresh Updates 4.7.6

A025:

Optional

DI-MISC-80508B/T Image Quality Investigation Report 4.7.7

A026:

Optional

DI-SESS-80639D Engineering Change Proposal 4.7.8

4.3.1. Quality of CDRL Deliverable:

There shall be no more than 10 total rejection(s) of deliverables per period of performance (contract period). The Government will reject a deliverable if one, more technical errors are identified per deliverable, or two or more minor errors are found per twenty pages of the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is exemplified by a typographical error or a grammatical error.

4.3.2. Receipt of CDRL Deliverable:

CDRL deliverables shall be submitted via Wide Area Workflow (WAWF) and submitted per the DD Form 1423, Contract Data Requirements List. There shall be no late submissions of deliverables per contract period unless the Contractor has requested/negotiated a revised delivery date with the USGPCO . The data/document shall be delivered by the revised delivery date agreed upon by the Government.

4.4. Program Management:

The Contractor shall establish and maintain a Program Management Office (PMO) to support the EISS requirements identified in this PWS and as options are exercised. The Contractor shall:

• Provide program management

• Define the program governance (controls)

• Plan the overall program and monitor the progress

• Manage the program’s budget

• Coordinate the projects and their interdependencies

• Manage and utilize resources

• Manage stakeholders’ communication

• Provide deliverables in a timely manner

• Manage program documentations

• Integrate subcontractors and other Raytheon inter-agency work organizations (IWOs)

• Execute, sustain, support and maintain the sustainment life cycle

• Identify opportunities for improving processes and reducing total life cycle cost

A027 DI-MGMT-

81453A/T

Data Accession List 4.8

A028 DI-MISC-80508B/T Mission Essential Contractor Services Plan

(MECSP)

5.1

A029 DI-SAFT-81563 Accident/Incident Report 5.5.3 A030 DI-SAFT-81626 System Safety Program Plan 5.5.4 A031 DI-MGMT-81749A Distribution of Department of Defense (DoD) Depot

Maintenance Workload (50/50) Report 5.14

• Facilitate continued operations and sustainment

• Perform risk management The Contractor shall maintain and deliver an organizational chart delineating the points of contact for the areas identified below and for options exercised. The chart shall include area of responsibility, name, organization, and commercial phone number. The Contractor shall deliver the information to the GHPO.

― Change Requests

― Contracts/Subcontractor Management

― Cybersecurity

― Deficiency Report (DR)

― Diminishing Manufacturer Sources and Material Shortages (DMSMS)

― Engineering Requirements Review Support

― Field Service Representative (FSR)

― Finance

― FSR Deployment Management

― Hardware

― Peculiar Support Equipment

― Program Manager – (Primary/Alternate)

― Reach-back Capability

― Reliability, Availability, & Maintainability

― Safety

― Security

― Software

― Technical Order Sustainment (Source Data)

― Technology Refresh

― Weapon System Integrity Programs & Aircraft Information Program

4.4.1. Performance and Financial Reporting:

4.4.1.1 Contract Funds Status Report (CFSR):

The Contractor shall report the contract funds status by the Contract Line Item Number (CLIN) for all efforts. The report shall provide the GHPO with monthly contract funds status, projected costs, estimate at completion, actual costs, and estimated termination cost. The Contractor shall state the dollar value of any differences from month to month and the reason for the differences in the reports. In the event that programmatic changes warrant changes to either funding or contract type, changes to the above reporting requirements can be requested. (A004, Contract Funds Status Report, DI-MGMT-81468/T)

4.4.1.2. Contractor’s Progress, Status, and Management Report (CPSMR):

The Contractor shall report the progress, status and management (CPSMR) at the contract summary level and within an agreed upon GHPO and Contractor report format structure. This report shall include period milestones, field support highlights, field support look ahead, Support Services/Field Service Engineering, upcoming program events, and correspondence. (A005, Contractors Progress, Status, and Management Report, DI-MISC-80508B/T)

4.4.1.3. Office of Secretary Defense (OSD) Cost Reporting:

The Contractor shall systematically collect and report actual contract costs to provide DoD cost analysts with needed data to estimate future costs. Contractor reports shall be prepared per “The Cost and Hour Report (FLEXFILE) and Quantity Data Report Implementation Guidance,” Mar 2019, and the applicable CDRLs. (A006, DI-FNCL-82162, Cost and Hour (FlexFile); A007, DI- MGMT-82164, Quantity Data Report; and, A008, DI-MGMT-81765, Contractor Business Data Report DD Form 1921-3)

4.4.1.4. Chief Financial Officer (CFO) Reporting:

The Contractor shall document inventories of Government-furnished/contractor-acquired material and expendable special tooling (including vendor tools), special test equipment; and all accessories per CFO directives. The report shall identify quantities and monetarily segregated categories of property. (A009, Physical Inventories Report, DI-MGMT- 80259/T)

4.4.2. Program and Sustainment Meetings:

4.4.2.1. Program Management Reviews/Technical Interchange Meetings:

The Contractor shall participate in Joint Program Management Reviews (JPMRs) for Northrop Grumman Company (NGC) contractor at either a Government facility or the Contractor’s facility as required by the Government.

The Contractor shall advise the GHPO of Contractor-conducted PMRs/TIMs with Subcontractors and/or Interagency Working Organizations (IWOs) 30 calendar days in advance of the PMR/TIM to afford the GHPO the ability to plan for attendance as necessary. The Contractor shall provide Agendas, Minutes, and Action Items for the EISS PMRs. The Contractor shall track the action items to closure and publish a final closed action item list with resolutions. (A010, Presentation Material, DI-ADMN-81373/T; A011, Conference Agenda, DI-ADMN-81249A; A012, Conference Minutes, DI-ADMN-81250B)

4.4.2.2. Product Improvement Working Group (PIWG)

The Contractor shall support one (1) annual PIWG meeting held at an either one of the RQ-4 Main Operating Bases or GHPO locations as selected by the Government. In addition to the annual PIWG, the Contractor shall also participate telephonically in quarterly PIWG reviews to convey status and updates of responsible items as required.

4.4.2.3. Engineering Activity Report Meeting (EAR) - Option:

(OPTION) The Contractor shall participate in the GHPO-chaired EAR meetings comprised of stakeholders from the Sustaining Engineering (SE) organizations in support of this PWS as required. The purposes of the meetings are to provide oversight of the SE activities, and coordinate GHPO and Contractor activities. The Contractor shall support EAR teleconference meetings to be held monthly as determined by the GHPO. (A011, Conference Agenda, DI-ADMN-81249A;

A012, Conference Minutes, DI-ADMN-81250B)

4.4.2.4. Other Support Meetings:

The Contractor shall provide support and attend meetings, as requested by the GHPO and mutually agreed between the Contractor and GHPO. The Contractor shall minimize travel by attending the meeting via telephone when possible

4.4.3. Risk/Issue Management - Option:

The Contractor shall manage risk IAW AFI 90-802. At a minimum, the Contractor shall:

• Provide Risk/Issue summary to the Global Hawk Program Office and at a minimum at the

JPMR.

4.5. Support Services Personnel:

The Contractor shall provide technically qualified personnel to support this PWS as required.

4.5.1. Field Service Representatives (FSRs):

The Contractor shall provide FSRs in support of this PWS and Appendix A. The Contractor shall adhere to Appendix C, “Field Service Representatives” and Appendix D, “Travel and Premiums.”

Appendix C defines FSR general and specific roles and responsibilities. Appendix D defines “Travel and Premiums.”

4.5.1.1. Planned and Unplanned Vacancies:

The Contractor shall manage and fill FSRs planned personnel positions and unplanned personnel vacancies within allotted time.

• Planned. 95 percent of all planned positions defined at contract award shall be filled within 10 business days of contract award. Remaining 5 percent of all planned positions defined at contract award shall be filled within 35 business days of contract award.

• Unplanned. Unplanned staffing changes during the contract period due to position vacancy shall not exceed 60 calendar days, with a goal to fill vacancy within 45 calendar days of the unplanned vacancy.

4.5.1.2. Maintenance and Operational Steps:

The Contractor shall adhere to all maintenance and operational steps expressed in technical data, flight/ operational manuals, or engineering direction.

• Warnings and Cautions. Assigned Contractor FSRs shall adhere to all maintenance warnings and cautions 100% of the time as expressed in technical data, flight/ operational manuals, or engineering direction. The Threshold and Objective are 100% and are based on possible injury, loss of life and/or damage to the equipment.

• Maintenance & Operational. Assigned Contractor FSRs shall adhere to all maintenance and operational directions as expressed in technical data, flight/ operational manuals, or engineering direction. The Contractor FSR shall comply with the directions with a minimum of threshold is 85% and an objective to achieve 90%.

4.5.2. Mission Essential Functions:

The Contractor shall provide services that are Mission Essential (ME); generate the Mission Essential Contractor Services Plan (MECSP); and, notify the PCO if Contractor anticipates not being able to perform. These functions are delineated in this PWS, paragraph 5.1., “Continuation of Mission-Essential (M-E) Services During a Crisis.”

4.6. Software:

4.6.1. Software License Inventory - Option:

The Contractor shall provide a list of software required for EISS operation, installation and maintenance. The list shall include expiration dates, part number or hardware identification number for software installation, EISS component or subsystem by 5-digit Work Unit Code (WUC), and identification of government rights to the software. The Contractor shall provide for the update and maintenance of unique analysis tools, simulation tools, and automated test tools.

This include updates and maintenance of tools supporting documentation and process improvements. The Contractor shall ensure the list is maintained and provided to the Government as required (A013, EISS Software License Inventory, DI-MISC-80508/T).

4.6.2. Cybersecurity:

The Contractor shall implement a Cybersecurity Risk Management Framework (RMF) using Committee on National Security Systems (CNSS) Instructions No. 1253 and the National Institute of Standards and Technology (NIST) 800 series for guidance. The Contractor shall prepare and provide a Cybersecurity Assessment and Authorization Plan and Test Report and other Artifacts.

The plan/report shall include all of the requirements in this paragraph and subparagraphs. The Contractor shall maintain the Cybersecurity posture of the RQ-4 Global Hawk Enhanced Integrated Sensor Suite (EISS) System/Subsystems, including the RMF Package, for the RQ-4 weapon systems and subsystems per DoDD 8500.1, DoDI 8500.1, DoD 8510.01 and AFSSI 5020 guidance. The Contractor shall collaborate with the USG designated system security information System Security Managers (ISSMs), Information Systems Security Officers (ISSOs), Information System Security Engineers (ISSEs), and other USG subject matter experts, for the engineering solutions in achieving acceptable compliance. Additionally, the Contractor shall ensure the above are incorporated into the RMF Package for approval by the GHPO throughout the PoP. The Contractor shall conduct a Static Code Analysis (SCA) and Dynamic Code Analysis (if feasible) scan for each fielded release and issue a SCA Triage Report with Non-Mitigation Worksheets providing a detailed level of fidelity technical rationale for any Cybersecurity controls/standards that cannot and/or should not be implemented.

4.6.3. Cyber Security (CS) of Fielded and Sustained Systems:

Hardware/Software/Firmware Spreadsheet. The spreadsheet shall include a Yes/No Column addressing whether or not any SW is foreign developed. Foreign SW is not authorized on GH.

Assured Compliance Assessment Scans (ACAS) results Security Content Automation Protocol (SCAP) results The Contractor shall ensure Cybersecurity is integrated into their internal Configuration Management processes and address changes across the baseline program of weapon systems, which are in sustainment, and ensure Cybersecurity is implemented as needed for A&A and documentation updates. The Contractor shall support baseline fielded EISS components and items supporting EISS, addressing key issues and providing system insight. The Contractor shall provide responses to Requests for Information, conduct updates to system and/or documentation as necessary, and provide “on-call” support to address concerns of the Global Hawk Program Office Cybersecurity team. The Contractor shall generate sanitization procedures to support the scope of work under this contract.

The system shall ensure interfaces are hardened while remaining accessible for safety/mission functionality. The Contractor shall sustain and provide RMF compliant systems, software, and documentation for EISS capabilities to the Government in accordance with Para 4.6.2 guidance documents. The Contractor shall sustain Cybersecurity Controls and their associated Security Technical Implementation Guides (STIGs). The Contractor shall run and provide Assured Compliance Assessment Solutions (ACAS), Security Content Automation Protocol (SCAP), and provide their reports and associated Non-Mitigation Worksheets providing a detailed level of fidelity technical rationale for any Cybersecurity controls/standards that cannot and/or should not be implemented. The Contractor shall execute Associate Contractor Agreements and ensure the interoperability between their systems and the platform OEM. The Contractor shall update legacy software and/or Operating Systems as approved and directed by the GH Program Office PM and

PCO.

4.6.4 Internet Protocol:

The Contractor shall verify, as a function of Cybersecurity Risk Management Frame Assessment and Authorization that all EISS systems sustained after award of this contract are not utilizing foreign Internet Protocol (IP) addresses in the internal network. The Contractor shall utilize DISA, the Internet Assigned Numbers Authority (IANA), or Maxwell-Gunter AFB.

4.7. Engineering:

The Contractor shall provide sustaining engineering including in-plant engineering, field service engineering, and technical services supporting the EISS.

4.7.1. Engineering Activity Report - Option:

The Contractor shall provide an Engineering Activity Report (EAR) reporting Sustaining Engineering activities performed under the contract for the reporting month and planned for the next three months. The sustaining engineering activities include the main functional area and the areas delineated in the subparagraphs below. The main functional areas include:

• Technical Publications & Engineering Source Data

• Weapon System Integrity Program

― RAM Performance Metrics

― FMECA

― SSHA

― FRACAS

― RAM Improvement Initiatives

― DMSMS Improvement Initiatives and Metrics

• Technology Refresh

• Image Quality Investigation and Support The Contractor shall provide status of the functional areas and cumulative metrics. The report shall identify the reporting period, the date the report was prepared, and technical POCs for each section.

The Contractor shall generate the EAR and report each functional area to include the progress for the period by tasks and subtasks performed. The report shall include dollars (actuals and cumulative actuals) expended supporting the functional areas and tasks. The report shall: identify issues and concerns; expound on the resolution or status of the issues and concerns; detail the progress and status of each functional area and associated tasks, and identify travel accomplished and planned, i.e., number of persons, purpose, dates, and location. (A014, Engineering Activity Report, DI-MGMT-80368A/T)

4.7.2. Engineering Requirements and Scheduled Maintenance Support - Option:

The Contractor shall provide source data on an ad hoc basis identified by the USG in support of the Engineering Requirements Review Process (ERRP) detailed in Chapter 3 of AFMAN 63-143.

Types of data includes, but is not limited to FMECA/Testability, RCM, Durability and Damage Tolerance (DaDT), OEM Maintenance Recommendations, Maintenance Data History, Service Life Predictions, etc. The source data may be used to determine and/or justify scheduled maintenance requirements, create logistics forecasts and detailed List of Materials (LOM), and develop procedures to facilitate field and depot level aircraft maintenance.

4.7.3. Technical Publications & Engineering Data Package:

4.7.3.1. Technical Publications - Option

The Contractor shall provide source data for technical publications and updates specific to EISS operations and maintenance to the GHPO. This includes source data for emergency, urgent, and routine updates, and TCTOs as applicable. The Contractor shall coordinate the selection and priority of emergency, urgent and routine updates with the GHPO. The Contractor shall abide by the requirements defined in TO 00-5-1, “Air Force Technical System,” TO 00-5-3, “Technical Order Life Cycle Management,” and TO 00-5-15, “Air Force Time Compliance Technical Order Process,” as it applies to the defined source data. The Contractor shall coordinate the delivery dates of the source data with the GHPO. The Contractor shall provide the GHPO an informational copy of all Service Bulletins (to include Subcontractors) by submitting them to the GHPO, as applicable.

4.7.3.2 Engineering Data Package - Option

The Contractor shall provide engineering support and coordination in response to technical publication change requests; Source, Maintenance, and Recoverability (SMR) code change requests; drawing packages; service bulletins; technical data packages in accordance with MIL-

STD-31000; and other forms of technical order and technical data change requests. This comprises design control and interface control drawings indicative of all additions, changes or updates.

(A015, DI-SESS-81000E/T, Product Drawings/Models and Associated Lists) The Contractor shall make available to the USG, data for the EISS system to include:

engineering data created via ECP’s, drawing updates created via the WSIP integrity program;

and other data such as system architecture, system performance, and other documents as defined per Mil-STD-31000.

4.7.4. Weapon System Integrity (WSIP) Program

The Contractor shall provide engineering and technical support to assist and execute the GHPO WSIP efforts for the EISS subsystem and interface. The Contractor shall capitalize on synergies of the various groups supporting WSIP to leverage information and eliminate duplication of efforts. The goal of WSIP is to identify existing and potential issues that may affect fleet performance, identify root case, and provide solutions to improve fleet performance metrics.

While the majority of EISS sub-components fall within the avionics category of WSIP, the contractor shall provide WSIP support as a total EISS system effort, and include non-avionics components that are part of the EISS system architecture and design. The following paragraphs apply to all EISS system components and interfaces, regardless of references to the avionics category.

The Contractor shall maintain an Integrated Master Schedule (IMS) for major sustainment effort under WSIP for each option that is exercised. Each effort shall include the specific tasks and subtasks from start to completion. The Contractor shall use the remarks section to identify programmatic information affecting resources and schedules.

4.7.4.1. Avionics Integrity Program (AVIP) - Option:

The Contractor shall execute a tailored AVIP per MIL-STD-1796A as directed below. The Contractor shall perform the AVIP activities per the Global Hawk AVIP Master Plan and provide recommended changes to the Master Plan as it applies to EISS. Additional guidance will be rendered during the Engineering Activity Report review meeting as needed. The primary measures of AVIP effectiveness are safety, aircraft availability, mission performance, and reduced operational costs. Specific objectives of EISS AVIP in the sustainment phase are:

Improve operational readiness and mission success of the EISS Reduce demand for maintenance manpower and logistic support Identify the resources, schedule, management structure, and controls necessary to execute the

AVIP

For Master Plan requirements set-forth in MIL-STD-1796A that have not been accomplished to date or Contractor identified tasks/subtasks (to include tasks not specifically addressed in this PWS) that require analyses, tests, reviews, or have gaps; a strategy to resolution and an estimated delivery date shall be provided along with an Integrated Master Plan to meet the AVIP requirements.

4.7.4.2. Failure Mode Effects and Criticality Analysis (FMECA) and Sub/System Safety Hazard Analysis (SSHA) - Option:

The Contractor shall provide and update FMECA reports/Testability Analysis and Sub/system Safety Hazard Analysis (SSHA) Reports affecting EISS items and to support criticality determinations per MIL-STD-1796A, Paragraphs 4.3, 5.1.6, 5.2.6, 5.3.6, and 5.4.6. (A016, Failure Mode Effects and Criticality Analysis (FMECA), DI-SESS-81495; A017, Sub/system Safety Hazard Analysis (SSHA), DI-SAFT-80101).

4.7.4.3. AVIP Hardware/Function Criticality - Option:

The Contractor shall classify the criticality of all EISS AVIP Hardware/Functions into categories with supporting analysis (Mission Reliability Analysis, FMECA/Testability Analysis, Functional Hazard Analysis, Sub/system Safety Hazard Analysis, etc.) for: safety critical; flight critical; non-flight and non-safety critical; mission critical; durability critical. The Contractor shall propose appropriate details to the GHPO to track, manage, mitigate and/or prevent failure based on those classifications per MIL-STD-1796A, Paragraphs 4.3, 5.1.5. 5.2.4, 5.2.5, 5.3.5, 5.4.5, and 5.5.5.

For all safety-, mission-critical parts (including life-limited parts), the Contractor shall serially track and establish and define Minimum Acceptable Performance (MAP) levels and identify, predict, track, investigate and alert the USG of AVIP components that do not meet the 80 percent (80%) of the MAP per MIL-STD-1796A. (A018, Critical Item Characteristics List, DI-MGMT- 81988; A019, Minimum Acceptable Performance (MAP) Analysis, DI-MGMT-80508B/T)

4.7.4.4. Failure Reporting and Corrective Action System (FRACAS) Analysis - Option:

The Contractor shall update and maintain the FRACAS data and field anomalies in a USG or USG approved database; this is all-inclusive from the EISS system to the Line Replaceable Unit down to the Shop Replaceable Unit (SRU) level. FRACAS includes the circumstances surrounding the anomaly, the vendor-level corrective action, and associated deficiency reports. The FRACAS data analysis, including the BIT/Fault Code analysis, shall include all aspects of the EISS system (field, depot, repair, organic or contractor) maintenance. The FRACAS data and analysis shall be utilized for any WSIP related task. The Contractor shall submit recommended improved maintenance and preventative maintenance procedures that support system performance and affordability improvements to sustainment based on the FRACAS data as part of the RAM report. (A020, FRACAS Report, DI-MISC-80508A/T)

4.7.4.5. Reliability, Availability and Maintainability (RAM) - Option:

The Contractor shall manage EISS RAM sustainment activities. The Contractor shall identify on-going RAM efforts to the GHPO so it can capitalize on the synergies going forward, conserve resources, and ensure no duplication of efforts occur.

The Contractor shall provide an EISS RAM Report that provides suitability, metric, and performance analysis using unaltered field maintenance data collected from field operations and associated drivers. The Contractor shall base all metrics, presented analyses, and recommendations on unaltered maintenance data, unless directed otherwise, maintained in the Integrated Maintenance Data System (IMDS). The metrics analyzed shall be reviewed at the 5-digit Work Unit Code (WUC) level for EISS systems and shall include but are not limited to Not Mission Capable (NMC), Not Mission Capable Supply (NMCS), Not Mission Capable Maintenance (NMCM), Not Mission Capable Both (NMCB), Mission Aborts, FRACAS data, etc.

The Contractor shall analyze the current data and predict the reliability performance of the EISS segments, to include Special Test Equipment (STE) and Peculiar Support Equipment (PSE). The Contractor shall provide trend analysis to predict future performance based on proposed and in-work growth initiatives. The report shall be provided in conjunction with the EAR. (A021, RAM Report, DI-MISC-80508B/T) The Contractor shall recommend RAM improvement initiatives in the RAM report. The Contractor shall review and prioritize program recommendations for reliability and maintainability improvements based on impact to EISS sustainment and life cycle cost. The Contractor shall submit sustainment recommendations for Reliability, Availability, and Maintainability (RAM), Reliability Centered Maintenance (RCM), and affordability improvements to subsystems or Line Replaceable Units (LRUs) to the GHPO in the monthly RAM reports. The Contractor shall develop corrective actions including drawing updates, and provide source data detailing technical data updates, TCTO development, and any other solution under $100,000 USD and delivered in accordance with the Technical Publications & Engineering Data Package Source Data and Configuration Management paragraphs.

4.7.4.6. Lead-Free Electronics - Option:

The Contractor shall establish and implement mitigations for lead-free electronics per MIL-STD- 1796A, Paragraphs 3.1.17, 5.1.4, 5.2.4, 5.3.4, 5.4.4, and 5.5.4. The Contractor and/or parts procuring agency shall define, document, and implement a plan to require replacement parts meet the same level of Parts Integrity as the original parts.

4.7.5. Diminishing Manufacturing Sources and Material Shortages (DMSMS) - Option:

NOTE

DMSMS will only be performed on this contract if an Engineering Change Proposal Class I is generated. For Class II changes, the cognizant management authority is responsible.

The Contractor shall use SD-22, “DMSMS: A Guidebook of Best Practices and Tools for Implementing a DMSMS Management Program” to develop and maintain the EISS DMSMS Implementation Plan.