PWS_BASIC_T_38_and_F_5_NGC_Eng_Services_Contract_Final_24_Sep_18.pdf

PERFORMANCE WORK STATEMENT (PWS)

Engineering Services Contract

Northrop Grumman Corporation for the

Mature and Proven Aircraft Directorate

24 September 2018

Prepared by:

Michael P. Blinn

AFLCMC/WLDE

(801) 777-0535 michael.blinn@usaf.af.mil

AFLCMC/WLD

MATURE AND PROVEN AIRCRAFT DIRECTORATE

HILL AIR FORCE BASE, UTAH 84056

i MAPA/NGC Engineering Services

Last Rev. Date: 24 Sep 18

Table of Contents Page

RECORD OF REVISIONS ......................................................................................................... iv

ACRONYMS AND ABBREVIATIONS ......................................................................................v

1 DESCRIPTION OF SERVICES

1.1 Performance Based Service Acquisition (PBSA)

1.2 Scope

2 SERVICE SUMMARY

3 GOVERNMENT FURNISHED PROPERTY AND SERVICES

3.1 Modification Drawings, Contractor Reports, and Tech Orders Provided

3.1.1 T-38C Structural Modification Drawings

3.1.2 Contractor Reports and Tech Orders

3.2 Security and Access to Government Facilities and Equipment

3.2.1 Security Clearance

3.2.2 Access to Government Facilities

3.2.3 Obtaining and Retrieving Base Identification

3.2.4 Entry Procedures to Controlled or Restricted Areas

3.2.5 Procedures and Controls

3.2.6 Cybersecurity

3.2.7 Network Security

3.2.8 Operational Security (OPSEC)

4 GENERAL INFORMATION

4.1 General Requirements

4.2 Technical Objectives and Goals

4.3 Specific Requirements

4.3.1 Aircraft Structural Integrity Program (ASIP)

4.3.2 Structures

4.3.3 Avionics Integrity Program (AVIP)

4.3.4 Mechanical Systems Integrity Program (MECSIP) and Landing Gear

4.3.5 Nondestructive Inspection (NDI)

4.3.6 Systems and Sustainment Engineering

4.3.7 Failure and Metallurgical Analysis

4.3.8 Material Properties Testing

4.3.9 Component Testing

ii MAPA/NGC Engineering Services

4.4 Technical Documentation

4.4.1 Data Compatibility

4.4.2 Data Analysis

4.4.3 Data Documentation

4.5 Formal Evaluations

4.5.1 Preliminary Program Reviews

4.5.2 Mid-course Evaluations and Status Updates

4.5.3 Final Program Reviews

4.6 Contractor Travel

4.6.1 Preliminary Program Review Trip

4.6.2 Final Program Review Trip

4.6.3 Miscellaneous Program Support Trips

4.6.4 Government Site Visits

4.7 Integrated Management Support

4.7.1 Contractor Program Manager

4.7.2 Contractor Interim Reporting

4.7.3 Management Systems Requirements

4.7.4 Validation Program

4.7.5 Maintainability Program

4.8 Configuration Management

4.9 Quality Control

4.10 Contracting Officer Representative (COR)

4.11 Management Objectives

4.11.1 Government Inspection and Acceptance of Deliverables

4.11.2 Assessment

5 APPENDICES AND ATTACHMENTS

5.1 Applicable Documents

5.1.1 Document Availability and Delivery

5.2 Applicable CDRLs

5.2.1 CDRL List

5.2.2 Contractor Reporting

Attachment One: List of Applicable Documents ................................................................. A1-1

Attachment Two: Applicable CDRLs ................................................................................... A2-1 iii MAPA/NGC Engineering Services

List of Tables

Page

Table 1: Service Summary for the MAPA/NGC Engineering Services

Table 2: CDRL List for the MAPA/NGC Engineering Services Contract ............................... A2-1 iv MAPA/NGC Engineering Services

RECORD OF REVISIONS

REV DATE

PAGE(S)

AFFECTED

SECTION

AFFECTED

REASON FOR REVISION

- 24 Sep 18 n/a n/a Original PWS date of release v MAPA/NGC Engineering Services

ACRONYMS AND ABBREVIATIONS

AETC - Air Education and Training Command

AF - Air Force

AFI - Air Force Instruction

AFB - Air Force Base

AIS - Automated Information System

ASIP - Aircraft Structural Integrity Program

AUP - Avionics Upgrade Program

AVIP - Avionics Integrity Program

CDRL - Contract Data Requirements List

COR - Contracting Officer Representative

CPARS - Contractor Performance Assessment Reporting System

CS - Cybersecurity

CUI - Controlled Unclassified Information

DCMA - Defense Contract Management Agency

DFARS - Defense Federal Acquisition Regulation Supplement

DID - Data Item Description

DoD - Department of the Defense

DTA - Damage Tolerance Analysis

ECO - Engineering Change Order

FAR - Federal Acquisition Regulations

FEM - Finite Element Model

FLDR - Flight Loads Data Recorder

FOUO - For Official Use Only

FSIP - Functional System Integrity Program

FSMP - Force Structure Maintenance and Planning

IATP - Individual Aircraft Tracking Program

IAW - In Accordance With

IT - Information Technology

MAPA - Mature and Proven Aircraft Directorate

MFT - Multi-functional Team

MECSIP - Mechanical Systems Integrity Program

MSFT - Microsoft

NDI - Nondestructive Inspection

NGC - Northrop Grumman Corporation

NLign - NLign software as from Etegent Technologies

NOR - Northrop

OEM - Original Equipment Manufacturer

OPSEC - Operational Security

Para. - Paragraph

PBSA - Performance Based Service Acquisition

PC - Pacer Classic

PWS - Performance Work Statement

PM - Program Manager vi MAPA/NGC Engineering Services

ACRONYMS AND ABBREVIATIONS (Cont)

PMP - Propulsion Modernization Program

Ref. - Reference

SEM - Scanning Electron Microscopy

SPO - System Program Office

SS - Service Summary

TCTO - Time Compliance Technical Order

TMCR - Technical Manual Contract Requirements

TO - Technical Order

USAF - United States Air Force

1 MAPA/NGC Engineering Services

1 DESCRIPTION OF SERVICES

The following Performance Work Statement (PWS) provides a general description of the required contractor services in support of the T-38 and F-5 weapon systems. Both weapons systems are managed by the Mature and Proven Aircraft Directorate (MAPA), T-38 System Program Office

(SPO), Air Education and Training Command (AETC), and/or other commands and services.

1.1 Performance Based Service Acquisition (PBSA)

This PWS is prepared in accordance with Air Force Instruction 63-124. The philosophy of PBSA is to design mission support strategies that obtain higher levels of contractor performance, foster synergistic partnerships, accommodate changing or unforeseen mission needs, and leverage commercial best practices.

1.2 Scope

This PWS covers the broad, over-arching engineering and technical activities that are required by the government.

2 SERVICE SUMMARY

Table 1 describes the Service Summary (SS) for the tasks as outlined in this PWS. Most of the efforts as described in this PWS will be engineering services and program management related.

3 GOVERNMENT FURNISHED PROPERTY AND SERVICES

3.1 Modification Drawings, Contractor Reports, and Tech Orders Provided

3.1.1 T-38C Structural Modification Drawings

The government will provide the contractor with the available structural modification drawings and engineering data that relate to the latest configuration T-38C aircraft. Key modifications that the T-38 weapon system has undergone include: Pacer Classic (PC) I, II, and III, the T-38C Avionics Upgrade Program (AUP), and the Propulsion Modernization

Program (PMP). The intention here is for the contractor to have all the required configuration baseline data readily available, assisting in the development of the T-38

Finite Element Model (FEM) and stress reports.

3.1.2 Contractor Reports and Tech Orders

The government will provide the contractor with all the necessary government technical orders (TOs), time compliance technical orders (TCTOs), and contractor reports, required to accomplish the tasks as detailed in this PWS.

2 MAPA/NGC Engineering Services

Table 1 – Service Summary for the MAPA/NGC Engineering Services

Performance Objectives

PWS

Reference

Performance Threshold

(Minimum Acceptable)

Engineering Activities:

Provide engineering analyses, assessments, studies, component or system-level designs, or testing to substantiate a new or improved system

(or sub-system or component) capability or troubleshoot / isolate faults in a current design configuration.

4.3.1 through

4.3.9

For engineering analysis (or assessments or studies): the analysis must have standard English grammar, punctuation and spelling; the problem statement and assumptions must be clearly stated;

the reference must be cited for the mathematic analytical model (be it deterministic or a stochastic model); the flow of analysis must be logical, the analysis steps must be shown in sufficient detail such that an entry-level engineer can follow and a journeymen engineer can recreate; the input values/units to the model must be cited; the mathematics must be free from significant errors;

the results/conclusions must be clearly identified;

and the implications of the result/conclusion must be clearly stated.

For component or system-level designs: the design must be validated by one or more of the following methods: analysis, inspection, demonstration, or test

For testing: the test must follow the approved test plan.

Technical Documentation:

Submit revisions to Technical Orders

(TO) and Time Compliance Technical

Orders (TCTO) to include source data for USAF aircraft specific TOs and

TCTOs.

4.4.1 through

4.4.3

100% of revisions are free of content errors (i.e.

they reflect the configuration defined in the approved product or functional baseline.

Configuration Management:

Establish and implement control procedures for managing established

USAF aircraft specific baselines.

4.8 A clear and unambiguous definition of the product

and functional configuration baseline.

Quality Control:

Engineering services shall develop and maintain a quality program to ensure services are delivered in accordance with established procedures and guidelines.

4.9 Provide for a quality assurance program 15 days

after contract award, program shall include procedures and policies for demonstrating 100% inspection of studies/reports are accomplished prior to delivery.

3 MAPA/NGC Engineering Services

3.2 Security and Access to Government Facilities and Equipment

3.2.1 Security Clearance

The efforts required for this task are UNCLASSIFIED and will not require contractor personnel to obtain a security clearance. Contractor personnel shall abide by all Air Force rules, procedures, and standard of conduct. Contractors requiring access to Air Force

Automated Information Systems (AIS) shall have background investigations and security awareness training completed prior to the start of contract performance. When the period of performance is complete and/or the contractor personnel leave work on this project, they will return all access cards and base identification badges within five days.

3.2.2 Access to Government Facilities

Access to government facilities is limited. Therefore, the contractor shall coordinate the need, time, and personnel requiring access to government facilities with the PM, at least one week prior to need. The government PM or designated representative will coordinate between the contractor and base personnel as required.

3.2.3 Obtaining and Retrieving Base Identification

Contractors requiring access to government installations shall obtain the appropriate base identification for all contractor personnel who make frequent visits to or perform work at government sites. Contractor personnel are required to wear or prominently display installation identification badges or contractor-furnished identification badges while visiting or performing work on the installation(s). During performance of the contract, the contractor shall be responsible for obtaining required identification for newly assigned personnel and for prompt return of credentials for any employee who no longer requires access to the work site(s). Upon completion or termination of the contract or expiration of base identification, the contractor shall ensure that all base identification passes issued to contractor employees are returned to the appropriate issuing office.

3.2.4 Entry Procedures to Controlled or Restricted Areas

Contractor employees shall comply with local base procedures for entry into government controlled and restricted areas. If contractor employees require unescorted entry to controlled or restricted areas, the contractor shall comply with the Federal Installations

Command Physical Security Plan and Department of Defense (DoD) Personnel Security

Program, DoD 5200.2-R.

3.2.5 Procedures and Controls

The contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of controlled unclassified information and to control distribution of controlled unclassified information IAW DoD 5220.22-M, National Industrial Security

Program Operating Manual. All contractor facilities shall provide appropriate means of storage for controlled unclassified information and materials. All controlled unclassified information shall be appropriately identified and marked as For Official Use Only

(FOUO) In Accordance With (IAW) DoD 5200.01, DoD Information Security Program:

Controlled Unclassified Information Volume 4 (enclosure 3) and DoD 5400.7-R Freedom

4 MAPA/NGC Engineering Services of Information Act Regulation Chapter 3. The contractor shall not store or transmit controlled unclassified information on personal information technology systems or via personal e-mail.

3.2.6 Cybersecurity

Cybersecurity (CS) is the discipline that protects and defends information and information systems by ensuring their availability, integrity, authentication, confidentiality, and non-repudiation. These measures include providing for restoration of information systems by incorporating protection, detection, and reaction capabilities.

DoD Instruction 8500.01 establishes a DoD cybersecurity program to protect and defend

DoD information and information technology. The contractor shall implement DoDI

8500.01 guidance for development of a cybersecurity strategy as defined below.

3.2.7 Network Security

The contractor shall take means (defense-in-depth measures) necessary to protect the availability, integrity, and confidentiality of government Controlled Unclassified

Information (CUI) in the same manner as the contractor would protect its own unclassified company proprietary information IAW DoD Instruction 8582.01. The contractor shall safeguard CUI stored on non-DoD information systems to prevent the loss, misuse, and unauthorized access to or modification of this information. The contractor shall ensure that contractor-owned and operated unclassified information technology (IT) network assets (including assets used for contractor teleworkers) used to process sensitive government CUI are managed and maintained IAW commercial best practices, vendor-specific, or other nationally or internationally-recognized IT configuration and management standards.

3.2.8 Operational Security (OPSEC)

OPSEC requirements are required in an effort to reduce program vulnerability from successful adversary collection and exploitation of critical information. OPSEC will be applied throughout the contract. A critical information list will be provided by the government.

4 GENERAL INFORMATION

4.1 General Requirements

General requirements for sustainment engineering are given in MIL-HDBK-514, “Operational

Safety, Suitability, and Effectiveness for the Aeronautical Enterprise,” (Ref. 4, Attachment One).

In addition, other key guiding documents that cover the integrity programs are JSSG-2006, MIL-

STD-1530D, MIL-STD-1798B, MIL-HDBK-515, and MIL-HDBK-87244 (Ref. 1-3, 5 and 6, Attachment One).

5 MAPA/NGC Engineering Services

4.2 Technical Objectives and Goals

The T-38 and F-5 weapon systems are required to remain viable for at least the next decade. As mature weapon systems in their later stages of sustainment, it is imperative that the T-38 and F-5 communities have a strong and experienced engineering support system to address the anticipated aging aircraft related challenges yet to be faced. Under the over-arching guidance of this PWS, it is intended that the government shall have a direct link to the T-38 and F-5 Original Equipment

Manufacturer (OEM), Northrop Grumman Corporation (NGC), in order to obtain engineering services to meet the sustainment goals of both weapon systems.

4.3 Specific Requirements

The contractor shall provide the appropriate engineering, program management, and technical services as required for this PWS. It is an objective of this program that the contract defines, as a minimum, the contractor’s support of the following United States Air Force (USAF) aircraft engineering activities:

4.3.1 Aircraft Structural Integrity Program (ASIP)

General guidance for the ASIP are given in JSSG-2006; more specific requirements are found in MIL-STD-1530D (Ref. 1 and 2, Attachment One). Engineering services for

ASIP can include, but are not limited to: damage tolerance analyses (DTA), finite element modeling (FEM) and analyses, stress analyses, failure analyses, life predictions, risk assessment, environmental impact assessments (e.g., corrosion study), weight and balance assessments, flight loads data recorder (FLDR) programs, individual aircraft tracking programs (IATP), force structure maintenance and planning (FSMP) documentation, loads analyses, and general consultations.

For establishing a baseline for ASIP and structures technical activities, some of the more recent (and core) documents are included at the end of this PWS (Ref. 7-12).

4.3.2 Structures

General requirements for structures are given in JSSG-2006 (Ref. 1, Attachment One).

Engineering services can include, but are not limited to: structural design, repair evaluations, classic stress analyses, FEM and analyses, failure analyses, special reviews/studies (e.g., bonded honeycomb evaluation, weight reduction study), part improvements (e.g., wing, horizontal tail), and general consultations.

4.3.3 Avionics Integrity Program (AVIP)

General requirements for the AVIP are given in MIL-HDBK-87244 (Ref. 6, Attachment

One). Engineering services can include, but are not limited to: electrical loads analyses, wiring studies, electrical component evaluations, focused avionics and electrical engineering studies, and general consultations.

4.3.4 Mechanical Systems Integrity Program (MECSIP) and Landing Gear

General requirements for MECSIP are given in MIL-STD-1798B (Ref. 3, Attachment

One). Engineering services can include, but are not limited to: component (part) stress

6 MAPA/NGC Engineering Services analyses, FEM and analyses, component failure analyses, risk assessment, mechanical parts and/or system improvements, focused studies, and general consultations.

In addition to MECSIP and other mechanical systems technical activities, engineering services for landing gear sustainment are required. Engineering services can include, but are not limited to: component (part) stress analyses, FEM and analyses, component failure analyses, risk assessment, mechanical parts and/or system improvements, focused studies, and general consultations.

4.3.5 Nondestructive Inspection (NDI)

Engineering services can include, but are not limited to: NDI improvement studies, methods developments, teardown analysis support, and general consultations.

4.3.6 Systems and Sustainment Engineering

General requirements for systems and sustainment engineering are given in MIL-HDBK-

514 and MIL-HDBK-515 (Ref. 4 and 5, Attachment One). Engineering services can include, but are not limited to: systems analyses, fault tree analyses, single-point failure analyses, Functional System Integrity Program (FSIP) studies (i.e., maintenance related), and general consultations.

4.3.7 Failure and Metallurgical Analysis

Engineering services can include, but are not limited to: structural teardowns (e.g., wing, empennage, and horizontal stabilizer), scanning electron microscopy (SEM) evaluation, low-power microscope assessments, failure analysis support, and general consultations.

4.3.8 Material Properties Testing

Engineering services can include, but are not limited to: static testing, fatigue testing, crack growth testing, fracture toughness testing, and general consultations.

4.3.9 Component Testing

Engineering services can include, but are not limited to: wing testing, empennage testing, fuselage testing, built-up coupon testing, and general consultations.

4.4 Technical Documentation

Engineering services can include, but are not limit to revisions to USAF aircraft-specific TOs and TCTOs. Engineering services can also include providing source data for these technical documents. In some instances a TO may require delivery of technical data. In those instances the use of Technical Manual Contract Requirements (TMCR) 8601 (See attachment 3) shall be utilized.

4.4.1 Data Compatibility

All contractor work shall be fully compatible and usable when loaded onto MAPA assets.

It should be noted that software is continually being upgraded, so any specific listing herein are given as examples. At the present time, the T-38 ASIP and Analysis Group

(AFLCMC/WLDEJ) has PATRAN 2010, NASTRAN 2010, StressCheck Ver. 10.2, 7 MAPA/NGC Engineering Services

AFGROW Ver. 5.2.4.19, Siemens NX Ver. 8.5, NLign Ver. 6.9, and a Microsoft (MSFT)

Windows based operating system.

4.4.2 Data Analysis

Data modeling and analysis techniques for Para. 4.3.1 through 4.3.9 cover a broad range of engineering disciplines; thus, these analyses require their own specific and unique engineering approaches. As good examples of recent modeling and analysis work, a number of engineering reports are provided at the end of this PWS (Ref. 7-12, Attachment One). All reporting of the data analysis shall be according to the guidelines of the Service Summary (see Table 1) and Para. 5.2.2 of this PWS.

4.4.3 Data Documentation

Various levels of reporting and documentation may be required under each delivery order per the CDRL (DD Form 1423). Additional data requirements, such as TOs, engineering change orders (ECOs), and drawings may be specified in the individual delivery orders.

4.5 Formal Evaluations

The following formal evaluations are to be supported by the contractor:

4.5.1 Preliminary Program Reviews

A preliminary program review for the contractor to present their refined “way ahead” for each task order, and further discuss the anticipated challenges with the tasks, is required.

The contractor shall provide a MSFT PowerPoint document as well as present minutes of the meeting in the most appropriate quarterly report.

4.5.2 Mid-course Evaluations and Status Updates

Depending on the needs of a specific task order, monthly or quarterly status updates and information exchanges between the government and the contractor will be conducted.

These interchanges can be accomplished via teleconferencing or by a face-to-face meeting. Unless otherwise arranged, minutes will be maintained by the contractor. For each task order, performance and cost reporting must be submitted monthly. The performance and cost reports shall provide current status and projected requirements of funds, man-hours, and work completion.

4.5.3 Final Program Reviews

A final review to present the final results and discuss the outcomes of the particular task orders shall be held at the conclusion of the program.

4.6 Contractor Travel

The following are general contractor travel requirements to be considered:

8 MAPA/NGC Engineering Services

4.6.1 Preliminary Program Review Trip

To ensure the appropriate level of up-front detail for each specific task order, the contractor shall plan for one preliminary program review trip (see also Para. 4.5.1).

4.6.2 Final Program Review Trip

To ensure a final close-out for each specific task order, the contractor shall plan for one final program review trip (see also Para. 4.5.3).

4.6.3 Miscellaneous Program Support Trips

The contractor should plan for miscellaneous trips, tailored to each task order.

4.6.4 Government Site Visits

During the course of task order execution and in addition to the program reviews, the contractor shall plan for various site visits to government facilities (e.g., Hill AFB, UT, Randolph AFB, TX, etc.). These site visits are intended to promote better communication during the course of any program.

4.7 Integrated Management Support

4.7.1 Contractor Program Manager

For all tasks required by this PWS, the contractor shall identify and maintain a program manager (PM). The program manager shall have a defined and direct line of authority and responsibility over all aspects of the work effort. The contractor’s work progress, status and any corrective action shall be documented.

4.7.2 Contractor Interim Reporting

The contractor shall submit status reports on the program’s progress. Reports shall be relatively error free and technically correct, as per the guidelines of Table 1.

4.7.3 Management Systems Requirements

Management systems requirements are to be provided by the contractor.

4.7.4 Validation Program

Validation requirements are to be provided by the contractor.

4.7.5 Maintainability Program

Maintainability requirements are to be provided by the contractor.

4.7.5.1 Continuation of Essential DoD Contractor Services During Crisis

The Functional Commander/Director has determined that this requirement is not

Mission Essential in accordance with Defense Federal Acquisition Regulation

Supplement (DFARS) clause 252.237-7023, Continuation of Essential Contractor

Services and AFI 10-403, Deployment Planning and Execution, paragraph 1.9.1.33.

4.8 Configuration Management

9 MAPA/NGC Engineering Services

Engineering services can include, but are not limited to updating of the USAF aircraft-specific baseline (e.g., engineering drawings or engineering change orders and associated process specifications). These configuration baselines could be either the product, allocated or functional configuration baselines.

4.9 Quality Control

Engineering services shall include development and maintenance of a quality program to ensure services are delivered in accordance with requirements. Assume some oversight from Defense

Contract Management Agency (DCMA).

4.10 Contracting Officer Representative (COR)

4.10.1 The Contracting Officer Representative (COR) is the authorized government representative who will perform assessments of the contractor’s performance. Subsequent to contract award, the identity of the COR, with a letter defining their duties and authority, will be promptly furnished to the successful bidder/offeror.

4.10.2 The COR or alternate(s) will inform the contract manager when discrepancies occur and will request corrective action. The COR or alternate(s) will make a notation of the discrepancy on their assessment checklist with the date and time the discrepancy was noted and will request the contract manager (or authorized representative) to initial the entry on the checklist.

4.10.3 Any matter concerning a change to the scope, prices, terms or conditions of this contract shall be referred to the Contracting Officer and not to the COR.

4.10.4 The services to be performed by the contractor during the period of this contract shall, at all times and places, be subject to review by the Contracting Officer or authorized representative(s).

4.11 Management Objectives

The management objective is to allow Northrop the maximum flexibility to innovatively manage the program schedule, performance, risks, warranties, subcontracts, and data to produce engineering services that satisfy the USAF performance requirements. Another objective is to maintain clear government visibility into the program schedule, performance, and risk.

4.11.1 Government Inspection and Acceptance of Deliverables

The government program manager shall have the right to reject or require corrections of any deficiencies found in deliverables. In the event of rejection of any deliverable, the contractor will be notified in writing by the government PM of the specific reason/s why the deliverable was rejected. The contractor shall have 30 workdays to correct the rejected deliverable and resubmit to the government PM for re-inspection. If no comments are

10 MAPA/NGC Engineering Services provided within 30 calendar days of deliverable receipt, the deliverable will be deemed to have been accepted by the government.

4.11.2 Assessment

The contractor, not the government, is responsible for managing and ensuring the contractor’s performance meets the terms of the contract. It is the government’s responsibility to monitor the performance and hold the contractor accountable for meeting the performance requirements in the contract. The contractor’s performance will be evaluated by the responsible multi-functional team (MFT) member assigned to the engineering activity addressed in 2.1-2.1.9 of this document, according to three categories:

1) Superior, 2) Acceptable, and 3) Unacceptable.

All efforts performed by the contractor will be expected to meet the level of “Acceptable” at a minimum. For each delivery order, that contractor performs at an “Unacceptable” level; the government will first negotiate re-performance measures to eliminate deliverable defects. If re-performance measures fail to produce “Acceptable” levels the government

Program Manager will compile a list of “Unacceptable” performances and notify the contractor’s upper management in writing of the government’s dissatisfaction with the level of performance demonstrated.

Additionally, the notifications may result in negative entries into the contractor

Performance Assessment Report System (CPARS) in accordance with Federal Acquisition

Regulations (FAR) Part 15.304.

5 APPENDICES AND ATTACHMENTS

5.1 Applicable Documents

5.1.1 Document Availability and Delivery

If the government deems appropriate, the contractor may use other applicable documents.

Also, the contractor shall request necessary documents from the government, as required.

In turn, the government shall supply all required TOs and TCTOs for the contractor to perform the tasks of this PWS.

5.2 Applicable CDRLs

5.2.1 CDRL List

The deliverable products (CDRL list) for this PWS are presented in Table 2 (see

Attachment Two). Specific CDRL use will be listed in the applicable task order or, in special cases, will be listed in the applicable approval documentation.

Note: See DD Form 1423 for further details.

11 MAPA/NGC Engineering Services

5.2.2 Contractor Reporting

The contractor shall submit reports in accordance with the Data Item Descriptions (DIDs) specified in DD form 1423 (see Attachment Two) with the following stipulations. Tables, figures, drawings, etc. shall be placed immediately following their reference in the main body of the text (i.e. same page if possible or on the next page). Reports shall be submitted in electronic format compatible with current Government software (ie, Microsoft, Adobe, etc) unless otherwise specified. Unless otherwise noted, any necessary corrections shall be made within 30 days of government notification.

A1-1 MAPA/NGC Engineering Services

Attachment One: List of Applicable Documents

Department of Defense (DoD) Specifications

1) JSSG-2006, “Aircraft Structures,” 30 October 1998.

Department of Defense (DoD) Standards

2) MIL-STD-1530D with Chg 1, “Aircraft Structural Integrity Program,” 13 October 2016.

3) MIL-STD-1798C, “Mechanical Equipment and Subsystems Integrity Program,” 8 August

2013.

Department of Defense (DoD) Handbooks

4) MIL-HDBK-514, “Operational Safety, Suitability, and Effectiveness for the Aeronautical

Enterprise,” 2 May 2011.

5) MIL-HDBK-515, “Weapon System Integrity Guide (WSIG),” 31 May 2012.

6) MIL-HDBK-87244, “Avionics/Electronics Integrity,” 14 April 2008.

Northrop Grumman Reports

7) NOR 07-101, Rev. C, “Finite Element Model User's Manual,” September 2010.

8) NOR 08-100, Rev. C, “T-38C Fuselage Update Analysis,” September 2010.

9) NOR 09-100, Rev. A, “Finite Element Model Description and Internal Loads,” September

2010.

10) NOR 09-101, Rev. A, “Finite Element Model Section Properties,” September 2010.

11) NOR 09-102, “T-38C Pacer Classic III (Phase I) Engineering Study,” August 2009.

12) NOR 10-104, “T-38C Pacer Classic III (Phase II) Engineering Study,” September 2010.

Note: If the government deems appropriate, the contractor may use other applicable documents.

A2-1 MAPA/NGC Engineering Services

Attachment Two: Applicable CDRLs

Table 2 - CDRL List for the MAPA/NGC Engineering Services Contract

CDRL DID Reference Title

A001 DI-MISC-80508B Technical Report - Study/Services.

T-38 IATP and L/ESS Development

Report

A002 DI-AVCS-80700A Computer Software Product End Items

A003 DI-IPSC-81443A Software User Manual (SUM)

T-38 Aircraft IATP and L/ESS

A004 DI-MISC-80508B Technical Report - Study/Services.

T-38 IATP and L/ESS Final Report

A005 DI-MGMT-80368A Status Report

A006 DI-MGMT-80227 Progress, Status and Management Report

A007 DI-MISC-80508B Technical Report

Individual Task Order Report

A008 DI-MISC-80508B Technical Report - Study/Services.

T-38 Aircraft FEM

A009 DI-IPSC-81443A Software User Manual (SUM)

T-38 Aircraft FEM