AFSC PWS 07Nov2023 Revision 1.pdf

PERFORMANCE WORK STATEMENT

(PWS)

For

AIR LAUNCHED CRUISE MISSILE ENGINEERING

SERVICES

PREPARATION DATE: 07 Nov 23

PURCHASE REQUEST NUMBER: FD2030-23-32205

PREPARING ORGANIZATION: AFNWC/NDMES and AFNWC/NDMLL

TINKER AFB OK 73145-8901

Signature Page

Lam Nguyen, NH-03 Project Engineer Missile Sustainment Division

Zealetta Barton, GS-12 Contracting Officer Representative

Brett A. Kearney, NH-04 Chief, Engineering Branch

Michael W. Hall, NH-04 Chief, Program Management Branch

Allona S Stanley, NH-04 Chief, Logistic Branch

REVISION SHEET

When a revision is received, it should be inserted into this PWS. The superseded pages should be retained as a record.

NOTE: The portion of the text of this specification affected by the current revision is indicated by a black underscore for figures, words, or phrases within a given paragraph, and by a black vertical line in the outer margin where the change constitutes a whole.

After the revised pages have been inserted into the PWS, the revised title page should be inserted in front of the existing title page. This revision page is placed under the existing title page.

Dates of Issue for the Original and Changed pages are:

Revision Number

Change Summary Page Date i

TABLE of CONTENTS

SECTION PARAGRAPH / TITLE

TABLE of CONTENTS ..................................................................................................... i

1 SECTION I – GENERAL INFORMATION

1.1 Scope

1.2 Mission Essential Designation

1.3 Surge Requirements

1.4 Program Requirements

1.5 Emergency Procedures

1.6 Travel Requirements

1.7 Operations Security (OPSEC) Requirements

1.8 Release of Public Information

1.9 System Safety Requirements

1.10 Contractor Work Schedule

1.11 Access/use of Original Equipment Manufacturer (OEM) Data

1.12 Monthly Status Report (MSR)

1.13 Engineering Integrated Product Team (IPT) Meetings

1.14 Pre/Post-Award Meetings

1.15 Deliverables

1.16 Contractor Personnel

1.17 Contact Funds Status Report (CFSR)

1.18 Security Requirements

1.19 Cybersecurity Requirements

1.20 Counterfeit Parts

1.21 Environmental Requirements

1.22 Quality System and Quality Program Requirements

1.23 Sixty Day Transition Period

1.24 Over and Above

1.25 Contractor Manpower Reporting

1.26 Privately Owned Motor Vehicles (POV)

2 SECTION Il – DESCRIPTION OF RECURRING ENGINEERING SERVICES

2.1 Configuration and Data Management

2.2 Sustainment Engineering Requirement Plan (SERP)

2.3 Laboratory Support – ALCM

2.4 Design Tool Support

2.5 GIDEP Technical Surveillance

2.6 Technical Inquiries (TIs)

2.7 Force Development Evaluation (FDE) Flight Test Support

2.8 Functional Ground Test (FGT) Support

2.9 Pre-Air Launched Munition Analysis Group (Pre-ALMAG) Support

2.10 Flight Test Performance Analysis Tool (FTPAT) Software

2.11 Users’ Day/Product Improvement Working Group (PIWG) Support ii

2.12 Contract Program Management Review (PMR)

2.13 Data Reporting Requirements

2.14 Contract Data Requirements List Markings and Submissions

2.15 Joint Requirements Review

3 SECTION Ill – DESCRIPTION OF NON-RECURRING ENGINEERING SERVICES

3.1 Engineering Assignment (Eas)

3.2 Engineering Assignment Common Tasks

3.3 Engineering Assignment Material

4 SECTION IV – SERVICE SUMMARY

4.1 Service Summary (SS) Requirements

4.2 Contractor Performance Evaluation

5 SECTION V – GOVERNMENT FURNISHED

PROPERTY/EQUIPMENT/MATERIAL (GFP/GFE/GFM)

5.1 Nuclear Certified Equipment Annual Inventory/Verification

5.2 Comprehensive Engine Management System (CEMS)

5.3 Plant Clearance

5.4 Government Furnished Plant Equipment

5.5 Physical Inventory

5.6 Replacement of GFP

5.7 Government Furnished Material at Contract Closeout

APPENDIX A ACRONYMS

APPENDIX B DEFINITIONS

APPENDIX C CONTRACT DATA REQUIREMENT LIST

APPENDIX D APPLICABLE DOCUMENTS

1 SECTION I – GENERAL INFORMATION

1.1 Scope

The purpose of this Performance Work Statement (PWS) is to define the requirements for the Air Launched Cruise Missile (ALCM) Engineering Services effort. This requirement includes support of the legacy strategic cruise missile integration with B-52, carriage equipment and peculiar support equipment. The ALCM weapon systems are managed by the Air Force Nuclear Weapons Center Missile Sustainment Division (AFNWC/NDM), hereafter referred to as the Program Office.

1.1.1 Contract Tasks

The Contractor shall provide requisite systems engineering and logistics analysis skills for the ALCM weapon systems. Tasks include, but are not limited to: investigative engineering, feasibility and data analysis studies; prototype/engineering model fabrication and testing; logistics studies and analyses; software and hardware problem investigations and development of recommended corrective actions; laboratory testing and analyses; technical data package (TDP) development; development of engineering inputs preceding and supporting formal modifications; and air vehicle and component testing and analyses. This includes support of the legacy strategic cruise missile integration with B-52, carriage equipment and peculiar support equipment.

1.1.2 Area of Expertise

The Contractor shall provide engineering and logistics supportability expertise, including but not limited to system design, aerodynamics, manufacturing/repair materials and processes, mass properties, corrosion, guidance, mission planning, reliability/maintainability, survivability/vulnerability, low observable technology and testing, system software, electrical, electronics, structures, test equipment, and Diminishing Manufacturing Sources and Material Shortages.

1.1.3 Weapon System Description

The ALCM systems are comprised of the ALCM missile and all components installed therein, support systems and equipment including B-52 Bomber Weapon Integration Equipment (BWIE), engineering data, technical orders (TOs), software, ALCM-peculiar carrier aircraft equipment and ALCM system test facilities and equipment.

1.2 Mission Essential Designation

The Contractor shall provide mission essential services in accordance with (IAW) Federal Acquisition Regulation (FAR) Title 48, Subpart 237.76 and Defense FAR Supplement (DFARS) clause 252.237-7023, Continuation of Essential Contractor Services, and 252.237-7024, Notice of Continuation of Essential Contract Services. The Contractor shall provide continuing services in the time of crisis for tasks deemed as “Mission Essential” addressed in this Engineering Services PWS. The Contractor shall provide 24 hours a day, 7 days a week and 365 days a year (24/7/365) Point of Contact (POC) for assistance via telephone to crews, technical or engineering personnel assuring responsive actions. The Contractor shall provide the name and telephone number for a 24-hour POC to the Contracting Officer (CO). The Contractor shall establish and provide a written plan to ensure continued support during a crisis IAW DFARS 252.237-7023 within sixty (60) days after contract award. The plan shall be submitted with the Contractor's proposal (CDRL A008).

1.3 Surge Requirements

In the event that the Department of Defense (DoD) experiences an unplanned spike or sudden increase in demand, due to a major theater warfare or a national emergency (also known as surge) and invokes surge: The Contractor shall be willing to work to meet and sustain the demand for services called for under this contract above and beyond normal peacetime requirements. After being notified of the surge demand in writing, the Contractor may see additional Task Orders and/or will see the priority status elevated on current Task Orders.

1.3.1 DoD shall be notified in advance of, and be given the opportunity to negotiate, any expedite charges and increase in schedule that might apply at the time of surge.

1.4 Program Requirements

1.4.1 Risk Management

The Contractor shall establish and maintain a Risk Management Program for early identification of program risks and mitigation of risks. The Contractor shall submit a Bomber level Risk Management Plan and provide Risk Reporting. The Contractor shall brief risk management status for all risks during Contract Program Management Review (PMR) meeting per para 2.12 (CDRL A023, CDRL A024).

1.4.2 Program Management Plan

The Contractor shall develop, maintain, deliver, and execute a Program Management Plan within 30 days of contract award. The Program Management Plan shall indicate how systems engineering (SE) principles, processes and methodology are integrated throughout the technical management efforts. The Program Management Plan shall address affordability and cost effectiveness (CDRL A033).

1.5 Emergency Procedures

Contractor employees shall follow the direction of Government employees in regard to emergency procedures, i.e., fire, tornado, active shooter, bomb threats. It is the responsibility of the Contractor to provide guidance and establish procedures when responding to an emergency for their employees. It is the Contractors’ responsibility to account for their employees following an emergency evacuation. Contractor Personnel shall participate with Government Personnel in all fire and tornado drills at no additional cost to the Government.

1.6 Travel Requirements

1.6.1 Travel and transportation costs related to recurring and non-recurring efforts shall be individually authorized by the CO IAW the DoD Joint Travel Regulation (JTR).

1.6.2 All travel requests shall be provided to the CO prior to travel and shall include estimated costs, IAW with the JTR.

1.6.3 Travel must be approved by the CO prior to travel occurrence.

1.7 Operations Security (OPSEC) Requirements

The ALCM Program Protection Plan (PPP) and the Counterintelligence Support Plan (CISP) will be provided as Government Furnished Information (GFI). The Contractor shall provide OPSEC protection for all Sensitive/Critical Information (CI) in accordance with Air Force Instruction (AFI) 10-701, Chapter 8, PPP and CISP for protection of Critical Program Information (CPI) and CI identified. The Contractor shall, as requested by the Government, provide input to updates of the PPP and CISP. Any modifications or deviations shall be made in writing to the CO. Requests for clarification of the PPP and/or CISP shall be made by the Contractor to the CO no later than thirty (30) business days from receipt of the PPP and CISP or updates thereof.

1.8 Release of Public Information

Release of information pertaining to this contract shall be reviewed and approved for release in accordance with DoD 522.22-M, National Industrial Security Operating Manual (NISPOM), Section 5, Para, 5-511, Disclosure to the Public, and the DoD Contract Security Classification Specification, DD Form 254, section 12.

1.8.1 Information Requests

The Contractor shall ensure responses to requests for information and data are only provided to customers with a need-to-know in performance of official duties.

1.9 System Safety Requirements

The Contractor shall consider system safety, including Nuclear Safety/Surety, in all endeavors undertaken IAW this PWS. The Contractor shall maintain currency with developments in all matters pertaining to safety in the design and operation of the ALCM weapon systems. The Contractor shall accomplish and document nuclear surety and system safety throughout recurring and non-recurring work involving new development or modification of software and hardware. The Contractor shall immediately provide written notification to the CO of any potential safety problems and update the ALCM System Safety Programs Plans (D232-11533-1 and D541-10149-1)

(CDRL A010).

1.10 Contractor Work Schedule

CO’s must ensure contract holidays to be observed under the contract are established in the PWS and/or Statement of Objectives (SOO) when Contractor performance occurs on a Government installation. Normally, the eleven federal Government holidays are observed in the United States. Some Contractor personnel policies and labor agreements provide for observing different holidays than observed by the Government.

Services performed outside the United States usually observe the holidays of the country where the services are performed.

1.11 Access/use of Original Equipment Manufacturer (OEM) Data The Contractor shall establish agreements as needed with OEMs that allow the Contractor to obtain the data and technical support necessary to maintain the systems identified in this PWS. The Contractor shall ensure the agreements are in effect at the beginning of the contract Period of Performance (PoP) for all engineering efforts referenced in Section 2 and Section 3 of this PWS.

1.12 Monthly Status Report (MSR)

The Contractor shall develop and maintain processes to evaluate and monitor progress made by the Contractor in accomplishing the requirement of this PWS, which includes recurring and nonrecurring efforts. The Contractor shall submit monthly status/progress reports which summarize all accomplishments and efforts (technical, financial, projections, problems, etc.) during the reporting month (CDRL A008).

1.13 Engineering Integrated Product Team (IPT) Meetings

The Contractor shall participate in monthly Engineering IPT meetings at Tinker Air Force Base (AFB), by telecom, Microsoft (MS) Teams, or other medium as specified by the CO/Contracting Officer’s Representative (COR) to discuss status/progress of all accomplishments and efforts. The Contractor shall have support from varying area of expertise on all efforts to brief and answer questions during IPT meeting. The meeting date shall be coordinated with the Program Office. Briefing materials shall be provided within five (5) business days of the meeting and meeting minutes to document the discussion/action items is due within five (5) business days after the meeting (CDRL A002, CDLR A032). The Contractor shall provide initial response to all assigned action items within ten (10) business days.

1.14 Pre/Post-Award Meetings

The Contractor shall participate in pre/post-award meetings at Tinker AFB, by telecom, MS Teams, or other medium to discuss contractual/technical requirements of the projected/anticipated and awarded Task Orders as directed by the CO.

1.15 Deliverables

The Contractor shall ensure that all deliverables are submitted IAW the Delivery Schedule specified by this PWS, individual Task Orders, and Technical Inquiries. The format, content, and distribution of such deliverables must comply with that of Contract Data Requirements List (CDRL), Form 1423’s.

1.15.1 If the Government does not provide a response after sixty (60) days upon CDRL submittal by the Contractor that requires approval, then the CDRL shall be considered approved.

1.16 Contractor Personnel

The selection, hiring, assignment of duties, reassignment of duties, transfer, supervision, management, control, and termination of Contractor employees in performance of this PWS shall be the responsibility and prerogative of the Contractor.

The Contractor shall ensure all Contractor employees wear appropriate attire, depending on the particular job assignment, and can be easily recognized as Contractor employees. Contractor employees shall identify themselves as Contractor personnel by introducing themselves, or being introduced, as Contractor personnel and displaying distinguishing badges or other visible identification for meetings with Government personnel. In addition, Contractor personnel shall appropriately identify themselves as Contractor employees in telephone conversations, in person and on MS Teams meetings, and in formal and informal written correspondence, at all times.

1.16.1 Contractor Employee General Requirements

The Contractor shall ensure Contractor employees who are required to communicate with Government personnel have the ability to clearly read, write, and speak English.

1.16.2 Hours of Operation

The Contractor shall ensure management and personnel provide support as follows:

1.16.2.1 Normal Hours

The Contractor shall have management and personnel on-site to provide uninterrupted support between the normal hours of 0900 to 1500, Monday through Friday, excluding federal holidays, Contractor’s compressed work schedule, and base closure dates, unless otherwise instructed. If the Contractor has a compressed work schedule, provide the details to the Government upon contract award via contract letter.

NOTE: Federal holidays are as follows: New Year’s Day, Martin Luther King’s Birthday, President’s Day, Juneteenth, Memorial Day, Independence Day, Labor Day, Columbus Day, Veterans’ Day, Thanksgiving, and Christmas Day. If the holiday falls on Sunday, it is observed on Monday. If the holiday falls on Saturday, it is observed on Friday.

1.17 Contact Funds Status Report (CFSR)

The Contractor shall provide a monthly Contract Funds Status report (CFSR) that contains authorized funding, labor hours expended, amounts billed, Estimated at Completion (EAC) and a percent of monthly expended by Engineering Assignment and Accounting Classification Reference Number (ACRN). The CFSR shall include all Cost type Contract Line-Item Number (CLIN) Reporting. This report shall be provided monthly and include all Engineering Assignments. A separate CFSR for each Engineering Assignment is not required. (CDRL A037).

1.18 Security Requirements

The Contractor shall provide information and documentation to comply with the requirements identified in DD Form 254, DoD Contract Security Classification Specification, attached to this contract. The Contractor shall obtain and maintain a minimum of SECRET security clearances for all required personnel working on or having access to data related to this contract. The Contractor shall ensure all Contractor personnel receive required security briefings. The Contractor shall comply with the following paragraphs:

1.18.1 Safeguarding Classified Information

The Contractor shall conform to the provisions of DoD 5220.22-M for safeguarding classified information and material contained in controlled areas. The Contractor shall ensure only those persons who have the proper security clearance and a need-to-know according to the performance of work under this contract shall be given access to classified information or material. The Contractor shall handle classified and sensitive data IAW AFI 21-401 and AFI 31-401.

1.18.2 Inventory of Classified Documents and Material

The Contractor shall ensure inventory of classified documents and materials are conducted as follows:

1.18.2.1 Initial Inventory

The Contractor shall conduct and complete inventory of all classified documents and material no later than thirty (30) workdays after issuance of this contract. During inventory, the Contractor shall determine the current status of all classified documents and material. The Contractor shall document the condition of all classified documents and material. The Contractor shall notify the CO in writing and deliver through the appropriate channels within ten (10) workdays of completion of the inventory of classified documents and material.

1.18.2.2 Final Inventory

The Contractor and a Government representative, as designated by the CO, shall conduct and complete a joint inventory of all classified documents and material no later than thirty (30) workdays before the contract end date. During the joint inventory, the Contractor and a Government representative shall jointly determine the current status of all classified documents and material. The Contractor shall document the condition of all classified documents and material. The Contractor shall notify the CO in writing and deliver through the appropriate channels within ten (10) workdays of completion of the joint inventory of classified documents and material.

1.19 Cybersecurity Requirements

Cybersecurity requirements apply to all Platform Information Technology (PIT) systems, subsystems, and Automated Test Equipment (ATE) supporting the ALCM within Contractor facilities at the unclassified level. Information provided from the Contractor based on the cybersecurity requirements identified in this section will support the Program Office’s Risk Management Framework (RMF) efforts and maintenance of the ALCM Authority to Operate (ATO).

1.19.1 Risk Management Framework (RMF) Assessment Support

The Contractor shall provide documentation supporting annual RMF assessments for ATE, verifying implementation of required security controls through a Security Control Traceability Matrix (SCTM) (CDRL A041).

1.19.2 Physical Security Measures

The Contractor shall ensure physical security measures are in place in the development and maintenance facility to prevent unauthorized access to the system. The contractor shall vet personnel prior to access to Contractor facilities to ensure only authorized personnel are granted access to the system and development environment (CDRL A041).

1.19.3 Supported Operating Systems

The Contractor shall support system users in maintaining the required configuration of the current Operating System (OS) and software in compliance with Security Technical Implementation Guides (STIGs) and Secure Content Automation Protocol (SCAP) scans (CDRL A041).

1.19.4 OS Patching

The Contractor shall support patching of the ATE based on Windows 10 Long-Term Servicing Branch (LTSB) patching requirements.

1.19.5 Security Impact Analysis (SIA)

The Contractor shall provide a Security Impact Analysis (SIA) for any changes to the system configuration requiring a Configuration Control Board (CCB) that may affect cybersecurity for the systems. The SIA shall include documentation providing evidence of cybersecurity controls in place, associated with applicable RMF security controls.

1.19.6 Cyber Incident Reporting

The Contractor shall report any cyber-related incidents associated with the ATE systems under Contractor controls to the Program Office, IAW DFARS Clause 252.204- 7012, Safeguarding Covered Defense Information and Cyber Incident Reporting.

1.20 Counterfeit Parts

The Contractor shall provide and maintain a Counterfeit Prevention Plan within sixty

(60) days after contract award (CDRL A030) to detect counterfeit parts and ensure that parts comply with DoDI 5200.44, Protection of Mission Critical Functions to Achieve Trusted Systems and Networks, and DOD 4140 DoD, Supply Chain Materiel Management Regulations. Upon discovery of suspected or confirmed counterfeit items associated with this contract, the Contractor shall enter the information into the Government-Industry Data Exchange Program (GIDEP) system. The Contractor shall notify the CO/Administrative Contracting Officer (ACO) IAW contract clause DFARS 252.246-7003, Notification of Potential Safety Issues. The Contractor shall inform the CO in writing of any situations which could affect the ALCM weapon systems. The Contractor shall inform the CO in writing of any situations which the weapon systems have an effect on other systems or equipment. The Contractor shall notify the CO immediately in writing of any known or potential system and operational safety problems

(CDRL A008).

1.21 Environmental Requirements

1.21.1 Compliance with Laws and Regulations

The Contractor shall be knowledgeable of and comply with all applicable Federal, State, and Local laws, regulations, and requirements regarding environmental protection. In the event environmental laws and regulations change during the term of this contract, the Contractor shall be required to comply with such laws when they come into effect. If there is an increase or decrease in cost as a result of the change, the Contractor shall inform the CO of the change within thirty (30) days and the CO will determine if an equitable adjustment is required. The Contractor shall develop, maintain, and deliver a Hazardous Material Management Program (HMMP) Report within sixty (60) days after contract award (CDRL A038).

1.21.2 Notification of Environmental Spills

In the event of an environmental spill or release of substance occurs on Federal property, the Contractor shall call the Command Post at 911 who in turn will contact Environmental Management Spill Response Team.

1.22 Quality System and Quality Program Requirements

The Contractor shall ensure the quality system and quality program meets the following requirements:

1.22.1 Quality System

The Contractor shall provide and maintain a quality system that adheres to the requirements of SAE-AS9100, Quality Management Systems – Requirements. The Contractor shall ensure the quality system procedures, planning, and other documentation and data comprise of the quality system shall be made available to the Government for review. The Contractor shall utilize existing quality documents that meet the requirements of the contract. The Contractor shall support the Government’s requested quality audit for inspections, verifications, and evaluations to ascertain conformance to requirements and the adequacy of implementing procedures. The Contractor shall allow, on a non-interference basis, Government audits to be performed on Contractor maintained files. The Government shall notify the Contractor twenty (20) calendar days in advance of the audit date and the type of audits to be performed. Upon completion of the Government’s quality audit, the Contractor shall incorporate into the repair process the corrective action(s) to eliminate the cause of the defects. The Contractor shall ensure all materials purchased or subcontracted from other contractors meets all technical requirements of this contract. The Contractor shall develop, maintain, and deliver a Quality System Plan within sixty (60) calendar days of contract award (CDRL A009).

1.22.2 Quality Program

The Contractor shall ensure the quality program is designed to detect and correct conditions adverse to quality. The Contractor shall investigate all Deficiency Reports (DRs) submitted against defective items manufactured, repaired, or overhauled by the Contractor. The Contractor shall ensure each DR is processed IAW TO 00-35D-54-WA-

1, USAF Deficiency Reporting and Investigating System. When the Contractor receives a DR or Quality Deficiency Report (QDR) the Contractor shall ensure deficiency reports include: analysis of data to determine extent and cause of deficiencies; analysis of trends in processes or performance of work to prevent recurrence; and introduction of required improvement, corrections, and monitoring of the effectiveness of corrective actions taken (CDRL A039, CDRL A040).

1.22.3 Government Quality Assurance Surveillance Support

The Contractor shall support Government quality assurance surveillance to periodically evaluate the Contractor’s performance IAW the Government’s Quality Surveillance Plan.

NOTE: For those requirements listed in Section 4, Service Summary, the COR will follow the methods of surveillance specified in the Quality Assurance Surveillance Plan.

The COR is the Governments authorized representative for the CO and will participate in the administration of this contract.

1.23 Sixty Day Transition Period

The Contractor shall ensure a smooth transition is accomplished during both the phase-in and phase-out periods as follows:

1.23.1 Phase-In Period Requirements

The Contractor shall provide, with the proposal, a Program Management Plan IAW PWS paragraph 1.4.2. The Contractor shall ensure the Program Management Plan incorporates the phase-in requirements and schedules to address how all the following requirements are to be accomplished. During the phase-in transition period the Contractor shall:

a. Complete workforce requirements including the hiring of personnel to assure satisfactory performance beginning on the contract start date IAW PWS paragraph 1.16.

b. Submit applications for required personal to obtain security clearances no later than ten (10) workdays after contract award IAW PWS paragraph 1.18.

c. Familiarize all Contractor personnel with the ALCM program to include equipment operation, workflow to include work in progress, reporting, priorities, forms, documents, scheduling, storage, safety, security, and quality control procedures. The Contractor shall make arrangements to access the Government facilities through the COR. The Contractor shall not interfere with the production efforts of current Contractor personnel.

e. Complete the physical inventory of Government property during phase-in joint inventory IAW PWS paragraph 5.5.1.

1.23.2 Phase-Out Period Requirements

The Contractor shall be fully responsible for all work performed under this PWS during the phase-out period. The Contractor shall ensure the following phase-out requirements are accomplished within sixty (60) calendar days prior to contract end date.

a. Cooperate fully to permit an orderly changeover of workload.

c. Allow all follow-on Contractor and Government personnel access on a non-interference basis to observe equipment operation and workflow to include work in progress, reporting, priorities, forms, documents, scheduling, storage, safety, security, and quality control procedures.

d. Complete the phase-out joint inventory IAW PWS paragraph 5.5.2.

e. Complete the final inventory of classified documents and materials identified IAW PWS paragraph 1.18.2.2.

1.24 Over and Above

Over and above shall only be considered for work discovered during the course of performing engineering services that is within the general scope of the PWS and not covered by the line items for the basic work under the contract and necessary in order to satisfactorily complete the contract. Over and above work discovered must be necessary to satisfactorily complete the scope of the PWS. Examples are, but not all inclusive, include additional flight and ground tests, engineering assignment (EA) material not previously contemplated or known at the onset of the EA Approval from the Contracting Officer shall be obtained prior to performing any over and above work. The Government shall be the sole authority to determine whether over and above is appropriate.

1.25 Contractor Manpower Reporting

1.25.1 The Contractor shall report all Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. The Contractor is required to completely fill in all required data fields in the Service Contract Report (SCR) at www.SAM.gov.

1.25.2 Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs from 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October* of each calendar year. Contractors may direct questions to the Sam.gov service desk (https://www.fsd.gov/fsd-gov/home.do).

1.25.3 *Reporting Period: Contractors are required to input data by 31 October of each year.

1.25.4 Uses and Safeguarding of Information: Information from the secure web site is considered to be proprietary in nature when the contract number and Contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any http://www.sam.gov/ https://www.fsd.gov/fsd-gov/home.do) data be released to the public with the Contractor name and contract number associated with the data.

1.25.5 User Guide: Data for Air Force service requirements must be input at www.SAM.gov. A quick start user guide is available on the SAM.gov website at https://sam.gov/SAM/transcript/SCR_QSG.pdf. In addition, full user guides for Contractors and Government personnel are available at https://www.sam.gov/SAM/pages/public/help/samUserGuides.jsf.

1.26 Privately Owned Motor Vehicles (POV)

Contractor personnel shall comply with state, local, and directives pertaining to operation of POVs on Tinker AFB per AFMAN 31-116 and TAFB Supplement, in its entirety, “Motor Vehicle Traffic Supervision”.

2 SECTION Il – DESCRIPTION OF RECURRING ENGINEERING SERVICES Tasks in section 2 will be performed on a continuous and recurring basis through the applicable PoP.

2.1 Configuration and Data Management

The Contractor shall provide hardware and software configuration management for the ALCM programs as required by the latest Configuration Management Plan (D541- 10192-1) for all items under Contractor control. This effort shall include establishing, maintaining, and complying with all the processes, methods, and procedures to be used to assure effective configuration identification, changes control, status accounting and audits of the total configuration (CDRL A005).

2.2 Sustainment Engineering Requirement Plan (SERP)

The Contractor shall provide the Government with a Sustaining Engineering Requirement Plan (SERP) that defines future engineering requirements. This effort shall include the development of a joint SERP submittal schedule, Technical Interchange Meeting (TIM) to discuss and refine requirements; brainstorm hardware and software engineering deficiencies and logistics support needs; compile and prioritize draft lists of engineering requirement tasks; and conduct activities to maintain a recurring SERP process (CDRL A028) due within ten (10) calendar days before the annual SERP meeting. The Contractor shall host an annual SERP meeting the first quarter of each calendar year. The meeting date shall be coordinated with the Program Office. The Contractor shall support the meeting with engineers of varying areas of expertise for discussion of the SERP proposed tasks. The Contractor shall deliver meeting minutes from the SERP TIM, due within five (5) calendar days after the meeting (CDRL A002).

2.2.1 Post SERP Meeting

The Contractor shall host a post-SERP meeting 6 months from the annual SERP meeting to discuss all assigned action items and status of the action items. The Contractor shall deliver meeting minutes from the SERP TIM, due within 5 calendar days after the meeting (CDRL A002).

http://www.sam.gov/ https://sam.gov/SAM/transcript/SCR_QSG.pdf https://www.sam.gov/SAM/pages/public/help/samUserGuides.jsf

2.3 Laboratory Support – ALCM

The Contractor shall provide and maintain hardware and support software in all ALCM related laboratories. The Contractor shall ensure these facilities are maintained in the latest ALCM functional configuration and have the capability to support directed investigations or other activities. Examples include Electronic System Test Set (ESTS) and other ATE, Subsystem Simulator, Power Hawk until it is replaced with iHawk, the Wyle System supporting ALCM Test Instrumentation Kit (CATIK) telemetry, and the ALCM-unique electrical, electronic and mechanical test aids. This effort shall include laboratory support (developmental and engineering labor), security provisions, data vault and necessary materials, and periodic maintenance of equipment, (except for the Heim/Zodiak Telemetry Recorder/Playback for legacy missile telemetry). The Contractor shall limit troubleshooting to 24 hours per month, anything greater shall be authorized by the CO.

2.4 Design Tool Support

The Contractor shall maintain and support Guidance and Control design and analysis tools including the Six-Degree-of-Freedom (6DOF) simulation and stability analysis simulation, Java Covariance Analysis Program (JCAP) and associated support tools.

The maintenance and support tasks shall consist of tool review/updates following computer maintenance, yearly analysis, and migration of tools into the current Contractor Enterprise standard development environments, error troubleshooting and analysis of tools. The Contractor shall provide a summary of the support tasks identified in this section in the first quarter of each calendar year (CDRL A008). Configuration changes shall be approved by the CO.

2.5 GIDEP Technical Surveillance

The Contractor shall provide technical surveillance of the Government-Industry Data Exchange Program (GIDEP) and inform AFNCW/NDM of possible impacts by written notification. Contractor shall review the “Alerts” identified and provide a summary of the items having potential Weapon Systems impacts (CDRL A026). The Contractor shall provide a summary of GIDEP surveillance activity in the MSR (CDRL A008).

2.6 Technical Inquiries (TIs)

Technical Inquiries are tasks executed to provide technical/logistical assessments, information, analysis and/or systems engineering assistance in support of ALCM weapon system’s Operational Safety, Suitability and Effectiveness (OSS&E). TIs may support sustaining engineering studies, modification assessments and studies, research, development, test, and evaluation (RDT&E) activities, and/or real time field support needs. TIs shall be issued by the CO within the limitations specified below:

2.6.1 The Contractor shall track TIs and report status in MSR (CDL A008).

2.6.2 The Contractor shall complete all TIs by the assigned due date specified in the individual TI and shall not exceed their respective hours, not to exceed 1000 hours. If additional hours are required, they will be negotiated separately. The Contractor shall comply with reporting and closeout as specified in the individual TI.

2.6.3 TI Material

2.6.3.1 Material as defined in Appendix B, may be utilized on a TI as approved by the CO for the purpose of completion.

2.6.3.2 Material approved for use on a TI must be able to be acquired within the established PoP of the accepted TI. If material is required for completion of TI and known prior to issuance, the TI SOO will state the need for material requirements. If the need for material arises during the course of the TI, then the Contractor shall notify the CO immediately.

2.6.3.3 The Contractor shall provide the POC a quote which includes the original supplier quote for material costs and include the negotiated handling rate.

2.6.3.4 The handling rate is a negotiated rate for the handling and processing of material, which is only applicable to ALCM System Integration Laboratory (ASIL) and TI material.

2.6.4 Subcontractors may only be utilized on TIs if the subcontracted effort is less than 10% of the TI’s total effort. If a subcontractor is needed for more than 10% of the effort on a TI, subject TI should be placed on an engineering assignment.

2.6.5 Each TI will depict one of the following priorities: Emergency, Urgent, or Routine.

The Contractor shall apply effort to the TI in accordance with the designated priority as assigned by the Government. The Government reserves the right to revise priority as work progresses. If a conflict exists concerning assigned priorities, the Contractor shall notify the CO for resolution/clarification.

2.6.5.1 Emergency: An emergency TI shall require immediate action and shall have priority over urgent or routine TIs for all resource allocation. Each individual TI will have a specific PoP. The Contractor shall acknowledge receipt of the TI to the CO within 24 hours.

2.6.5.2 Urgent: an urgent TI shall have priority over routine TIs for resource allocation.

Each individual TI will have a specific PoP. The Contractor shall acknowledge receipt of the TI to the CO within two (2) business days.

2.6.5.3 Routine: Each individual TI will have a specific PoP. The Contractor shall acknowledge receipt of the TI to the CO within two (2) business days.

2.6.6 Hours estimated and authorized under a TI for an effort wherein the full number of hours are not expended for the deliverable, shall revert back to the Government allocations for use on future TI requirements within that period of performance.

Reporting on the reallocated hours must be done at the next transpiring monthly reporting requirement.

2.6.7 The CO may authorize Contractor travel under a TI, as required. See paragraph 1.6.

2.6.8 TIs authorized under 10 hours with no CDRL, or travel requirement shall be submitted by the Government to the Contractor via email. Examples of this type of request would be for retrieval of drawings, rapid response to noncomplex technical questions, etc.

2.6.9 Safeguarding Covered Defense Information and Cyber incident Reporting for any additional cybersecurity engineering requirements will be called out specifically on each

TI.

2.6.10 For all TIs, the CDRLs from the Table in Appendix C are applicable to the deliverables requested by each effort. The Government will not create CDRLs for each TI but will instead refer to the CDRLs in Appendix C of this contract.

2.6.11 For all applicable TIs, the cybersecurity requirements in paragraph 1.19 apply.

The Government will not specify cyber security requirements for each individual TI. The Contractor shall reference this PWS for cyber security requirements.

2.6.12 TI Common Tasks

2.6.12.1 TI’s will have their own Statement of Objectives (SOO); however, common tasks are as follows:

2.6.12.1.1 The Contractor shall respond to all documentation change requests and engineering drawings updates IAW re-procurement data packages and MILSTRIP Defense Logistics Manual (DLM) 4000.25-1 activities (CDRL A003).

2.6.12.1.2 The Contractor shall provide a new technical manual, change package, or source data for an existing manual, as directed (CDRL A006).

2.6.12.1.3 The Contractor shall prepare Class I and Class II Engineering Change Proposals (ECP) IAW the latest approved Configuration and Data Management Plan (D541-10192-1) (CDRL A007).

2.6.12.1.4 The Contractor shall assist in documenting the impact to Nuclear Certification for all changes proposed (CDRL A031).

2.6.12.1.5 The Contractor shall submit a System Safety Hazard Analysis Report

(CDRL A011).

2.6.12.1.6 The Contractor shall support test planning and reporting and submit Test Requirements Documents, Test Plans, Test Procedures, and Test/Inspection Reports (CDRL A012, CDRL A013, CDRL A014, CDRL A015).

2.6.12.1.7 The Contractor shall submit Computer Software Products, Software Requirements Specifications, Software Version Descriptions, and Automated Computer Program Identification Number Data and Control Records, Software Requirements Specifications (CDRL A016, CDRL A018, CDRL A020, CDRL A021, CDRL A022).

2.6.12.1.8 The Contractor shall submit Failure Modes, Effects and Criticality Analysis (FMECA) Reports (CDRL A017).

2.6.12.1.9 The Contractor shall submit Deficiency Reports (DR) (CDRL A025).

2.6.12.1.10 The Contractor shall submit Performance Specification Documents (CDRL A019).

2.6.12.1.11 The Contractor shall submit Integrated Program Management Reports using the Government identified DID format on each TI (CDRL A004).

2.6.12.1.12 The Contractor shall submit a Design Review Information Package (CDRL A034).

2.6.12.1.13 The Contractor shall submit a Test Readiness Review Information Package

(CDRL A035).

2.7 Force Development Evaluation (FDE) Flight Test Support

Contractor shall provide FDE Flight Test Support for 6 Flight Tests per year. If more than 6 Flight Tests are required, the additional support will be negotiated and executed on the Over and Above CLIN.

2.7.1 The Contractor shall provide flight test support, to include:

2.7.1.1 Perform mission screening and provide a summary report (CDRL A008).

2.7.1.2 Support preparation, and support of ALCM live launches, related flight test activities and provide a quick look report (CDRL A008).

2.7.1.3 Process the flight test data, assess ALCM flight performance data, analyze data for any anomalous performance, to include telemetry data, and provide an engineering report with the results and recommendations (CDRL A008).

2.7.1.3.1 If the Program Office identifies discrepancies or issues in a report, the Contactor shall correct the report within fourteen (14) business days of CO notification.

2.7.1.3.2 The Contractor shall conduct a Technical Interchange Meeting (TIM) forty-five

(45) days after Contractor receipt of all flight test data required for analysis to discuss the initial findings and any anomalies observed during the actions completed per paragraph 2.7.1.3 (CDRL A001, CDRL A002). However, if anomalies are discovered before the TIM, the Contractor shall notify the Government immediately upon discovery, as such, via email for situational awareness.

2.8 Functional Ground Test (FGT) Support

Contractor shall provide FGT support for two functional ground tests per year. If more than two function ground tests are required, the additional support will be negotiated and executed on the Over and Above CLIN.

2.8.1 Support preparation and participate with the FGT activities and assist the Government in resolving test-related problems.

2.8.2 Process the FGT test data, assess performance data, analyze data for any anomalous performance, to include telemetry data, and provide a report with the results and recommendations (CDRL A008).

2.8.2.1 If the Program Office identifies discrepancies or issues in a report, the Contactor shall correct the report within fourteen (14) business days of CO notification.

2.8.2.2 The Contractor shall conduct a Technical Interchange Meeting (TIM) forty-five

(45) days after Contractor receipt of all flight test data required for analysis to discuss the initial findings and any anomalies observed during the actions completed per paragraph 2.8.2 (CDRL A001, CDRL A002). However, if anomalies are discovered before the TIM, the Contractor shall notify the Government immediately upon discovery via email for situational awareness.

2.9 Pre-Air Launched Munition Analysis Group (Pre-ALMAG) Support The CO will direct the initiation of pre-ALMAG Support. The Contractor shall visually inspect in person and assist with collecting the missile debris from the impact site, receipt of missile debris into the ASIL, inventory of the debris with the ALMAG members and other Government and Contractor participants as needed, thorough visual inspection of the debris, document anomalies during onsite FDE support to include telemetry data, environmental issues, etc., utilize the fault tree for investigation, and support three teleconferences with the ALMAG Chair. The Contractor shall document pre-ALMAG activities in the MSR (CDRL A008).

2.9.1 The Government will ensure two Pre-ALMAG’s are funded yearly. If there are additional Pre-ALMAG efforts needed beyond the two, they will be executed via the Over and Above Contract Line Item Number (CLIN).

2.10 Flight Test Performance Analysis Tool (FTPAT) Software

The Contractor shall add annual flight test data into the current FTPAT data file(s) for trending analysis. The Contractor shall deliver to the Program Office once a year the comprehensive FTPAT data file(s), and the updated user’s instructions to use FTPAT to project future ALCM performance trend (CDRL A018).

2.11 Users’ Day/Product Improvement Working Group (PIWG) Support The Contractor shall provide support for annual Users’ Day/PIWG meetings at location to be determined as directed by the Program Office. PIWG support includes the following:

2.11.1 Participation by contractor systems engineer, mechanical engineer, electronics engineer, and software engineer.

2.11.2 Verbal feedback on action items that are brought up during the meetings.

2.11.3 Summary in the MSR (CDRL A008).

2.11.4 Travel as authorized by CO. See paragraph 1.6.

2.12 Contract Program Management Review (PMR)

The Contractor shall host and participate in two Contract PMR meetings per year as directed by the Program Office. The Contractor shall coordinate the agenda, length of meeting and meeting location with the Program Office/COR (CDRL A001, CDRL A002, CDRL A032). The Contractor shall support the meeting with functions of varying areas of expertise for discussion of topics presented during the PMR.

2.13 Data Reporting Requirements

The Contractor shall submit data deliverables per the Contract Data Requirements Lists (CDRLs). The Contractor shall ensure all CDRLs are submitted correctly per the PWS and CDRL instructions to include timeliness, currency, adequacy, and proper format and markings. The Contractor shall ensure all agreed upon comments from draft deliverables are addressed in the final deliverables.

2.14 Contract Data Requirements List Markings and Submissions The Contractor shall ensure proper markings and data rights legends are applied to all submissions. Data delivered with improper markings shall be returned to the Contractor for correction at no additional cost to the Government. No additional time for scheduled reporting will be allowed for improper markings. For information submitted by e-mail, ensure data containing Controlled Unclassified Information (CUI) or other protected information is properly marked and encrypted. Do not send classified information except through authorized secure systems.

2.15 Joint Requirements Review

The Contractor shall review draft Engineering Assignment (EA) PWS and/or TI SOO for scope/clarity/feasibility/schedule and provide feedback as directed by the CO/COR.

3 SECTION Ill – DESCRIPTION OF NON-RECURRING ENGINEERING SERVICES

3.1 Engineering Assignment (EAs)

3.1.1 The Contractor shall perform engineering assignments as directed by the CO.

The Contractor shall provide field support as directed by individual EAs. The Contractor shall track status of all EAs in the Engineering Services MSR (CDRL A008).

3.1.2 The Contractor shall complete all EA tasks by assigned due dates. If the Contractor is unable to complete any EA on time or within the cost authorized (except for Firm-Fixed-Priced (FFP) tasks), the Contractor shall notify the CO in writing as soon as possible.

3.1.3 The Contractor shall provide a written notification to the CO prior to 75 percent of the authorized funding being expended. If additional funds or schedule are required, the Contractor shall provide the estimated dollar amounts and updated schedule to include a list of completed and remaining tasks with their notification. If additional funds or schedule become known AFTER the 75 percent notification is provided, the Contractor shall notify the Government immediately and provide the proper cost estimate and schedule with an updated notification letter.

3.1.4 If a potential problem is discovered, the Contractor shall immediately provide written notification to the CO of the implications and potential solutions.

3.1.4.1 In the process of performing any non-recurring activity, the Contractor shall notify the Government of any technical data that requires correction in the EA reporting.

3.1.5 Each EA will depict one of the following priorities: Emergency, Urgent, or Routine. The Contractor shall apply effort to the EA in accordance with the designated priority as assigned by the Government.