Attachment 1 PWS.pdf
PDF 298 KB Posted
- Attached to
- Engineering Investigation Systems
- Solicitation number
- FA850425RB002
About this file
This is a Performance Work Statement (PWS) for C-130 Aircraft Engineering Support at Air Force Life Cycle Management Center (AFLCMC) Robins AFB, GA, with a period of performance of 12 months plus four one-year options. The contractor will provide engineering, technical and logistics support for overall Operational, Suitability, Sustainment, and Effectiveness (OSS&E) responsibility for all C-130 systems, including avionics systems (navigation, GPS, communications, radar), mechanical systems (landing gear, hydraulics, propulsion, flight controls), and structural systems.
Key requirements include supporting field and operational maintenance problem resolution, evaluating airworthiness certification documents, participating in safety review boards, providing depot/field sustainment engineering support, developing technical procedures, and supporting test activities. The contractor must maintain a local office near Robins AFB, submit quarterly status reports, conduct program management reviews, and comply with security requirements including Secret clearance levels. Performance metrics include requirements for timely and accurate technical reports, CDRL deliverables, and responses to maintenance issues. The work supports C-130 fleet configuration control, modification programs, and resolution of field concerns that could impact future aircraft missions. The contractor will also provide support for Navy, USG, NASA and Foreign Military Sales aircraft configurations.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Solicitation - FA850425RB002.pdf | ||
| Exhibit A CDRL A004.pdf | ||
| Exhibit A CDRL A003.pdf | ||
| Exhibit A CDRL A002.pdf | ||
| Exhibit A CDRL A001.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
FD2060-24-30073 1
Performance-Based Work Statement (PWS)
C-130 Aircraft Engineering Support
Air Force Life Cycle Management Center (AFLCMC) Robins AFB, GA
Date: 17 September 2024
DISTRIBUTION STATEMENT B: Distribution authorized to U.S. Government Agencies and their Contractors (Critical Technology) (Sep2018). Other requests for this document shall be referred to AFLCMC/WLNE Robins AFB, GA 31098-5365. Questions concerning the technical content should be directed to AFLCMC/WLNE.
WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec. 2751 et seq.) or the Export Administration Act of 1979, as amended (Title 50, U.S.C., App. 2401 et seq.). Violators of these export laws are subject to severe criminal penalties.
HANDLING AND DESTRUCTION NOTICE: Comply with distribution statement and destroy by any method that will prevent disclosure of the contents or reconstruction of the document.
1.0 DESCRIPTION OF SERVICES
1.1 Objective(s):
FD2060-25-30215 2
The objective of the C-130 Engineering Support program is to provide engineering, technical and logistics support of overall Operational, Suitability, Sustainment, and Effectiveness (OSS&E) responsibility and authority for all C-130 systems. Support includes, but is not limited to, avionics systems such Self-Contained Navigation System, Global Positioning System, communication/radio systems, aircraft radar, air defense systems, mechanical systems such as landing gear, hydraulics, propulsion, and flight controls, primary and secondary structural systems. Responsibility includes configuration control for all C-130 modifications and monitoring of field concerns, which often represent potentially significant impacts to future aircraft missions.
1.2 Benefit to the United States Air Force (USAF):
The effective execution of the C-130 Engineering Support program will ensure proper support channels are in place for the C-130 fleet. Technical and logistics support to be provided will assist in identification and resolution of potentially significant impacts to future aircraft missions, safety and aircraft availability.
1.3 Background:
AFLCMC/WLN has overall Operational, Suitability, Sustainment, and Effectiveness (OSS&E) responsibility and authority for all C-130 systems to include, but not limited to; avionics systems such Self-Contained Navigation System, Global Positioning System, communication/radio systems, aircraft radar, air defense systems, mechanical systems such as landing gear, hydraulics, propulsion and flight controls; primary and secondary structural systems. This effort provides engineering, technical and logistics support for referenced systems, including requirements definition, systems engineering, installation support, and technical documentation and evaluation, on an as required basis. AFLCMC/WLN is also responsible for configuration control for all C-130 modifications. Field reported concerns often represent potentially significant impacts to future aircraft missions.
2.0. SERVICES SUMMARY:
Performance Objective
PWS
Paragraph
Performance Threshold
Accurate and timely submission of technical reports and the annual program reports. Technical reports must comply with PWS objectives and Contract Data Requirements Lists (CDRLs).
4.2 Technical reports shall be timely, accurate and comprehensive.
No more than one (1) report shall be received late during the contract period of performance, and it shall be received no later than five (5) business days after its scheduled submission date. Any mandated rewrites shall be due within five (5) business days after the Government’s identification of the error(s).
FD2060-25-30215 3
Quality of CDRL deliverable 4.2.1 There shall be no more than one rejection of any single deliverable. There shall be no more than three total rejection(s) of deliverables per quarter. The Government will reject a deliverable if two (2) technical errors or three or more minor errors are found within the deliverable. The rejected deliverable shall be corrected and resubmitted within ten business days of notification of Government rejection.
Receipt of CDRL deliverable 4.2.2 There shall be no more than three (3) late submission(s) of deliverables per quarter. The Contractor shall notify the Government 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.
Accurate and timely response to AFMC Form 202s, T.O. 107s, DLA 339s, AFTO Form 22s, and AFMC Form 252s
4.7.1 No more than two (2) submissions shall be received after the Government’s suspense date during the contract period, and those two (2) delinquent submissions shall be no more than two (2) business days late. Documents shall not have more than two (2) minor errors and zero (0) major errors per document. All corrections must be accomplished within two
(2) business days of Government notification.
The Contractor shall evaluate field and operational maintenance problems submitted at the depot level via AFMC Form 202 & field level IAW T.O. 00-25-107, for resolution within three business days. The Contractor shall provide engineering and technical support for Defense Logistics Agency (DLA) 339s, First Articles and DLA local purchase requests within five business days. The Contractor shall provide timely Contract Field Team (CFT) support at the depot repair facility or operational field units to troubleshoot and resolve aircraft problems.
Timely scheduling of quarterly Program
Management Review /Technical Interchange Meetings (PMR/TIM), and delivery of the Conference Minutes in accordance with the appropriate CDRLs.
4.13 The Contractor shall conduct quarterly PMRs/TIMs. The
minute’s submissions shall be provided as prescribed in the CDRLs. The minutes shall be comprehensive and accurately describe the events of the meeting and shall never be more than five (5) business days late. There shall be no more than one (1) rewrite per submission. Any mandated rewrites shall be due within five (5) business days after the Government’s identification of the error(s).
FD2060-25-30215 4
Accurate and timely reporting in the Quarterly Status Report in accordance with PWS programmatic objectives and
CDRL.
4.14 The Contractor shall clearly outline and report their schedule and status. Program objectives shall be addressed as outlined by the Government. The Contractor shall provide notification of all possible impacts to schedule or cost within two (2) business days of determining an impact could exist. No more than two (2) data submissions shall be received late during the contract period of performance, and no late submissions in consecutive months. No submission shall be received later than five (5) business days after its scheduled submission date.
Any mandated rewrites shall be due within five (5) business days after the Government’s identification of the error(s). A Performance Assessment Report (PAR) will be created by USG each quarter for performance validation. PAR will be routed to Contractor for concur/non-concur, signed and returned within five (5) business days. A negative PAR or a Corrective Action Report (CAR) will be signed and returned by the suspense date.
Service Contract Reporting 5.7 Within 30 calendar days of contract award, the Contractor shall establish a record for the contract/order in the System for Award Management (SAM) 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. All data shall be reported no later than October 31 of the following fiscal year.
Adherence to Contractor QMS 5.9 100% compliance with the QMS is required.
3.0 GOVERNMENT PROPERTY
3.1 Contractor Responsibility: The Contractor shall be responsible for Government property in accordance with the Federal Acquisition Regulation (FAR) and as specified in the contract.
3.2 Government Property to be Provided: Government property to be provided includes Computer Systems.
3.2.1 GOVERNMENT FURNISHED INFORMATION (GFI): During the period of performance of this task, the Government will provide to the Contractor the data necessary, on an as-available basis, for the accomplishment of this task. The Government will provide access to:
Legacy systems include but are not limited to G081/IMDS, REMIS, AFSAS, GCSS, LMDS, DRILS, LIMS, G050, RAMPOD, JEDMICS, IETMS, JDRS, and CEMS C-130 Engineering and Technical Documents, including but not limited to, all C-130 related Technical Orders including Flight Manuals and Operating Instructions.
All data provided will be returned to the AFLCMC/WLNE at the completion of the program and all data generated as a result of this tasking will become the property of the U.S. Government
FD2060-25-30215 5
All products developed under this contract shall be considered Government work and shall have no license encumbrances. All Government Furnished Equipment (GFE), Government Furnished Software (GFS), and Government Furnished Material (GFM) shall be returned to the Government upon completion of this contract and will be required to be returned to its original configuration prior to delivery to the Government unless specified by the Government.
3.3 BASE SUPPORT: The Government will furnish property incidental to the place of performance including office space and equipment, i.e., computer equipment, software, output device(s), phone/phone line, facsimile equipment, reproduction equipment and office supplies.
3.4 REPORTING OF GOVERNMENT PROPERTY: The Contractor shall have a system of internal controls to manage (control, use, preserve, protect, repair, and maintain) Government property in its possession in accordance with FAR 52.245-1, and its property management system shall be adequate to satisfy the requirements of this clause. The contractor shall record receipt and return of all Government Furnished Property (GFP), as well as the reporting of shipment, consumption, disposal, or transfer to another contract, in the GFP Module in Procurement Integrated Enterprise Environment (PIEE), https://piee.eb.mil, as stipulated by DFARS 252.245-7002. This reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract. GFP training and guidance is located at the DoD Procurement Toolbox at https://dodprocurementtoolbox.com/.
3.5 LOSS OF GOVERNMENT PROPERTY:
3.5.1 Definition of Loss of Government Property: “Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.
3.5.2 Reporting Loss of Government Property: The Contractor shall report loss of Government property in the GFP Module located in PIEE, https://piee.eb.mil/piee-landing/.
3.5.3 Return or Retention of Government Property: 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. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes 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 PCO directs the Contractor to retain the material for continued use under a successor contract.
4.0 TECHNICAL REQUIREMENTS
The Contractor shall provide engineering/technical services for the efforts described within Section 4.1 below.
4.0.1 CONTRACTOR REQUIREMENTS
https://piee.eb.mil/ https://dodprocurementtoolbox.com/ https://piee.eb.mil/piee-landing/
FD2060-25-30215 6
The Contractor shall be provided government equipment described within Section 3.2 and will provide services described in sections 4.0 thru 4.14. The Contractor shall furnish all supplies and equipment (with the exception of Government Furnished Equipment/Information (GFE)/(GFI) identified in Paragraph 3.2.1 of this document) necessary for the completion of this effort in accordance with the requirements of the contract. The Contractor shall provide engineering and equipment specialist sustainment support and engineering modification support for the C-130 aircraft. The Contractor shall also have an office space within the vicinity of Robins Air Force Base, Georgia. The Government will provide all technical data required to perform this effort. Requirements for reference documentation are based on need to accomplish a particular task. Related documents and electronic files will be made available to the Contractor as necessary. This may include documents marked “For Official Use Only (FOUO)” or other restrictive marking, reference: DoD 5400.7-R. Some documents may be proprietary, and the Contractor shall establish a Non-Disclosure Agreement (NDA) with the owning company. The Contractor shall notify the Government of any Government design data or documents required for the successful performance of the requirements of this PWS. The Contractor shall comply with all computer and network access requirements.
4.0.2 AIRCRAFT SUSTAINMENT SUPPORT
The Contractor shall provide engineering and technical support for ongoing and future C-130 aircraft sustainment efforts. Such aircraft efforts include, but are not limited to, the following systems:
• Aircraft avionics systems
• Aircraft electrical systems
• Aircraft structures systems
• Aircraft mechanical systems
The Contractor shall provide engineering and technical installation services to support trial install/kit proof activities for each Mission Design Series (MDS). Support shall include but not be limited to reviewing installation diagrams and instructions, reviewing support equipment requirements and, participating in technical and engineering problem resolution, determining, and resolving airworthiness impacts, determining, and resolving cyber security impacts. If requested, the Contractor shall design, test and support installation of prototypes at locations directed by the Government in a task order to support C- 130 sustainment and modifications. The Contractor shall provide ancillary support for various sub-configurations for the Navy, USG, NASA, and Foreign Military Sales (FMS) aircraft. The trial installation shall be accomplished for the purpose of proving the validity of the Contractor’s design, verification of the adequacy of kit component design, completeness of kit contents, checking electromagnetic effects and performance through specified testing and verification of the preliminary Time Compliance Technical Order (TCTO). (CDRL A004, DI-MISC-80711A)
4.1 PLACE AND PERIOD OF PERFORMANCE:
PLACE OF PERFORMANCE: Services shall be performed at a Government facility; Robins AFB GA, and other United States Air Force (USAF) bases, as required.
PERIOD OF PERFORMANCE: The basic contract period is 12-months with four (4) one-year option periods.
FD2060-25-30215 7
4.2 CONTRACT DATA REQUIREMENTS LIST(s) (CDRL):
Technical reports shall be timely, accurate and comprehensive.
No more than one (1) report shall be received late during the contract period of performance, and it shall be received no later than five (5) business days after its scheduled submission date.
Any mandated rewrites shall be due within five (5) business days after the Government’s identification of the error(s).
The Contractor shall notify the Government 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.
Document Identifier Base Year
Option Year
Option Year
Option Year
DID Title PWS Reference(s)
A001 B001 C001 D001 DI-ADMIN-
81249C
Conference Agenda 4.2, 4.13, 4.13.1, 4.13.2, 4.13.3
A002 B002 C002 D002 DI-ADMIN-
81250C
Conference Minutes 4.2, 4.13. 4.13.1, 4.13.2, 4.13.3, 4.13.4, 4.13.5
A003 B003 C003 D003 DI-MGMT-
80368A
Quarterly Status Report
4.2, 4.10, 4.14, 5.9
A004 B004 C004 D004 DI-MISC-
80711A
Technical Report 4.0.2, 4.2, 4.2.1, 4.3, 4.4, 4.6, 4.7.1, 4.7.2, 4.8.2, 4.8.3, 4.9.1, 4.9.2, 4.9.3, 4.10, 4.11.1, 4.11.2, 4.11.3, 4.11.4, 4.12, 4.12.1, 4.12.2, 4.13.4, 4.13.5, 4.14, 4.16
4.2.1 Quality of CDRL Deliverable: There shall be no more than one rejection of any single deliverable.
There shall be no more than three (3) total rejection(s) of deliverables per contract. The Government will reject a deliverable if two (2) technical errors or three or more minor errors are found within 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, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within four (4) business days of notification of Government rejection. (CDRL A004, DI-
MISC 80711A)
4.2.2 Receipt of CDRL Deliverable: CDRL deliverables may be submitted via Procurement Integrated Enterprise Environment (PIEE)/Wide Area Workflow (WAWF) and/or be submitted directly to the MFT member identified on the CDRL. The CDRL will determine submittal requirements. There shall be no more than three (3) late submission(s) of deliverables per quarter. The Contractor shall notify the Government 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.
4.3 The Contractor shall actively participate in system and subsystem Functional Configuration Audits (FCA), Physical Configuration Audits (PCA) and verify that all requirements are documented. (CDRL A004, DI-MISC- 80711A)
FD2060-25-30215 8
4.4 The Contractor shall analyze training, operational testing, tactics development, specialized support equipment (including effects on deployment), and manpower requirements which will result from modification programs. The Contractor shall identify and report impacts resulting from modifications as they affect total cost of ownership. (CDRL A004, DI-MISC-80711A)
4.5 The Contractor shall support the Government Engineer/Equipment Specialist in technical data validation and verification, as required. When required, the Contractor shall participate in trial installations and kit proofing of modifications for validation and verification of TCTOs, relative to modification activity.
4.6 The Contractor shall provide support to the Government during Safety Review Boards (SRBs) and Safety Investigation Boards (SIBs) with in-depth knowledge of system functionality on the aircraft to determine the root cause(s) of accidents. (CDRL A004, DI-MISC-80711A)
4.7 DEPOT/FIELD SUSTAINMENT ENGINEERING SUPPORT
4.7.1 The Contractor shall provide engineering and technical expertise in support of avionics and defensive systems, aircraft structures, mechanical systems, and support equipment. The Contractor shall provide initial development and evaluation for modifications. The Contractor shall evaluate field and operational maintenance problems submitted at the depot level via AFMC Form 202 & field level IAW T.O. 00-25-107, for resolution within three business days. The Contractor shall provide engineering and technical support for Defense Logistics Agency (DLA) 339s and DLA local purchase requests within the suspense date. The Contractor shall provide timely Contract Field Team (CFT) support at the depot repair facility or operational field units to troubleshoot and resolve aircraft problems. No more than two (2) submissions shall be received after the Government’s suspense date during the contract period, and those two (2) delinquent submissions shall be no more than two (2) business days late. Documents shall not have more than two (2) minor errors and zero (0) major errors per document. All corrections must be accomplished within two (2) business days of Government notification. (CDRL A004, DI-MISC-
4.7.2 The Contractor shall develop technical procedures and technical data updates for test and support equipment requirements and identify the availability of components necessary to provide solutions to depot or field level support equipment sustainment issues. (CDRL A004, DI-MISC-80711A)
4.8 RELIABILITY AND LOGISTICS ENGINEERING
4.8.1 The Contractor shall: provide C-130 supportability analysis, to include root cause analysis for deficiency report (DRs); identify sources of supply for obsolete parts and support equipment; identify system deficiencies that impact logistics supportability such as, long lead items and non-standard parts approval; and recommend corrective actions and alternatives.
4.8.2 The Contractor shall perform research and analysis for C-130 reparable items to correct asset shortfalls and maintain designated asset supply levels. The Contractor shall evaluate system effectiveness in terms of reliability and maintainability. The Contractor shall support the Government with diminishing manufacturing sources & material shortages (DMSMS) efforts for the C-130 fleet to include, but are not limited to, analysis of part availability, analysis of impact of DMSMS parts and verification of aircraft
FD2060-25-30215 9
technical data used with DMSMS evaluation tools. The Contractor shall lead or assist with the full implementation of a robust C-130 DMSMS Program, which includes executing technical & administrative requirements needed for the program. The Contractor shall also provide information and/or assist with other C-130 fleet support project/program sustainment initiatives where DMSMS may be a factor. (CDRL
A004, DI-MISC-80711A)
4.8.3 The Contractor shall support the Government with cost benefit analyses, Level of Repair Analyses, and economic analyses to determine the most economic source of repair. The Contractor shall provide research and analysis of select items, track item reliability data, and generate status and action reports in support of program manager tasks. (CDRL A004, DI-MISC-80711A)
4.9 TEST PLANNING AND SUPPORT
4.9.1 The Contractor shall support the development of test documents to include but not limited to: test plans, criteria, and procedures. The Contractor shall support Government test activities to verify and document technical performance and/or procedure accuracy. (CDRL A004, DI-MISC-80711A)
4.9.2 The Contractor shall identify the instrumentation required to obtain test data, making maximum use of existing Government test equipment. (CDRL A004, DI-MISC-80711A)
4.9.3 The Contractor shall provide test engineering support for sustainment/modification programs, systems integration efforts and field reported issues, as directed. In support of this task, the Contractor shall support Test Readiness Reviews (TRR), Safety Review Board (SRB), and ground and flight test observation/events. This task shall include support for Developmental Test and Evaluation (DT&E)/Operational Test and Evaluation (OT&E), ground and flight testing, to include regression testing, and system troubleshooting. (CDRL A004, DI-MISC-80711A)
4.10 VERIFICATION AND VALIDATION
The Contractor shall perform an Independent Validation and Verification of new and/or existing systems, when required. Results shall be reported under CDRL A004. GFM/GFP required for Verification and Validation will be reported quarterly under CDRL A003. Reporting/disposition instructions for GFM/GFP will be provided by the Government. (CDRL A003, DI-MGMT-80368A), (CDRL A004, DI-MISC-
4.11 ENGINEERING DATA/TECHNICAL MANUALS
4.11.1 TCTOs/TOs: The Contractor shall perform analyses and give recommendations for changes to Time Compliance Technical Orders (TCTOs), supporting technical manuals and artwork to support recommended update of engineering drawings and ECOs as required. The Government will participate in the process for publication reviews, certification and verification process, pre-publication review and submitting data of the Interactive Electronic Technical Manual (IETM) tool. (CDRL A004, DI-MISC- 80711A)
4.11.2 TO updates/changes: The Contractor shall review technical data deficiencies submitted on AFTO Form 22, AFMC Form 252/AFMC Form 847 and provide the corrective action/response for incorporation into printed technical manuals. The Contractor will be provided electronic or paper copies of AFTO Form 22/AFMC Form 252/AFMC Form 847. The Contractor shall evaluate vendor and manufacturer technical
FD2060-25-30215 10
data provided by the Government to develop procedures necessary to perform organic repair of C-130 components. (CDRL A004, DI-MISC-80711A).
4.11.3 IETMs: The Contractor shall review technical manual source data and provide recommendations/corrective actions for discrepancies during Interactive Electronic Technical Manuals (IETMs) development and deliver for incorporation into the IETM’s tool. (CDRL A004, DI-MISC- 80711A)
4.11.4 Engineering Data: The Contractor shall assist in providing information to be used for development/production/maintaining a Technical Data Package (TDP) that accurately depicts the final product. The TDP shall represent the approved, tested, and accepted configuration of the defined delivered item(s). TDP data includes, but is not limited to, Computer-Aided Design (CAD) data, CAD models, model-based definition data sets, Gerber data and Master Bill of Materials (BOM). The TDP shall provide the necessary design, engineering, manufacturing, testing and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product without additional design engineering effort or recourse to the original design activity or any third party. The Contractor may also be asked to provide drafting support for engineering drawings. All engineering product definition data created as a result of input on this contract shall be considered a part of the TDP. The TDP shall be in accordance with Air Force Product Data Specification drawing 9579776 (CAGE 98752), reference attached DD Form 1423-1 Block 16.
(CDRL A004, DI-MISC-80711A), (CDRL A080, DI-SESS-81000F), if applicable.
4.11.4.1 Relationship of Contractor with Subcontractors/Vendors: The Contractor shall levy on sub-contractors and sub-vendors the same requirements for TDPs as levied on them by this contract. This requirement shall apply at all tiers of sub-contractor/vendor levels associated with the program.
4.11.4.2 Engineering Data Updates and Revisions: The Contractor shall (and shall cause subcontractors and vendors to) provide documentation for updating and maintaining engineering data for the item(s) designed/developed/modified/produced by this contract for the life of this contract and shall provide changes to support the following Government actions:
a. All engineering changes shall be incorporated into the applicable engineering data within
90 calendar days after engineering release/Air Force concurrence, or at intervals of five changes, whichever occurs first, except a change involving safety, which shall be incorporated immediately.
b. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of data for review.
c. All engineering changes shall be incorporated into the applicable engineering data prior to delivery of final media (this includes all Engineering Orders (EOs) generated as a result of the preliminary data review).
4.11.4.3 WITHHOLDING OF UNCLASSIFIED TECHNICAL DATA FROM PUBLIC
DISCLOSURE: Pursuant to Department of Defense Instruction (DoD) 5230.24 Distribution Statements on DoD Technical Information (10 Jan 2023), DoDD 5230.25 Withholding of Unclassified Technical Data From Public Disclosure(6 Nov 1984- Reissued 18 Aug 1995), and Air Force Instruction 61-204 for Marking and Dissemination of Operations and Support Technical Data, the Contractor shall mark technical data/reports generated under Technical
FD2060-25-30215 11
Requirements (PWS) and CDRL requirements, with the following:
DISTRIBUTION STATEMENT B: Distribution authorized to U.S. Government Agencies and their Contractors (Critical Technology) (Sep2018). Other requests for this document shall be referred to AFLCMC/WLNE Robins AFB, GA 31098- 5365. Questions concerning the technical content should be directed to
AFLCMC/WLNE.
WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec. 2751 et seq.) or the Export Administration Act of 1979, as amended (Title 50, U.S.C., App. 2401 et seq.).
Violators of these export laws are subject to severe criminal penalties.
4.12 TECHNICAL REPORTS
4.12.1 The Contractor shall document field-reported anomalies in technical reports identifying options and recommendations for resolving technical discrepancies. The Contractor shall develop technical reports relative to independent evaluations of modification proposals, Budgetary Costs estimates, complex logistics, engineering, and maintenance procedure recommendations, including trade studies. (CDRL A004, DI-MISC-80711A)
4.12.2 The Contractor shall evaluate airworthiness certification documents, test reports, cyber security documents and engineering change proposals provided by the Government for accuracy to confirm successful compliance with program requirements. (CDRL A004, DI-MISC-80711A)
4.13 TECHNICAL MEETINGS AND REVIEWS
The Contractor shall host/attend pertinent meetings and reviews such as Technical Interchange Meetings (TIM), Preliminary Design Reviews/Critical Design Reviews (PDR/CDR), Test Readiness Reviews (TRR), Program Planning Meeting (PPM), Program Management Reviews (PMR), acceptance and qualification testing, trial installations and kit proof. If possible, the meetings, reviews and audits shall be held at Robins AFB, GA. or in the local vicinity at a site and on a date agreed upon by the Government contracting officer and the contractor. The Contractor shall prepare agendas, meeting minutes, technical reports, briefings, analyses, and recommendations in support of these meetings, reviews, and audits, as required. There shall be no more than one (1) rewrite per submission. Any mandated rewrites shall be due within five (5) business days after the Government’s identification of the error(s). (CDRL A002, DI-ADMN-81250C), (CDRL A001, DI-ADMN-81249C)
4.13.1 Program Planning Meeting (PPM) A PPM shall be held no later than 30 calendar days after contract award. The purpose of the PPM is to review all projected program activities/tasks. The Contractor shall identify any concerns or potential risks, programmatic issues. The Contractor shall deliver an agenda and minutes for the PPM. The PPM shall be held at Robins AFB, GA. or in local vicinity. (CDRL A002, DI-ADMN-81250C), (CDRL A001, DI-ADMN-81249C)
4.13.2 Technical Interchange Meeting (TIM)
The Contractor shall attend TIMs to review progress. The TIM will address any action items or issues originating from the previous meetings and/or reviews. The TIM will be held in conjunction with quarterly PMRs. The Contractor shall deliver an agenda prior to the TIM and minutes following the meeting. The TIM shall be held at Robins AFB, GA. or in the local vicinity. (CDRL A002, DI-ADMN-81250C), (CDRL
A001, DI-ADMN-81249C)
FD2060-25-30215 12
4.13.3 Program Management Review (PMR) The Contractor shall hold a quarterly PMR to review task progress and status and discuss programmatic requirements. The Contractor shall deliver an agenda and minutes for the PMR. The minutes shall be comprehensive and accurately describe the events of the meeting and shall never be more than five (5) business days late. The PMR shall be held at Robins AFB GA or in the local vicinity. (CDRL A002, DI-ADMN-81250C) (CDRL A001, DI-ADMN-81249C)
4.13.4 Preliminary Design Review (PDR) The Contractor shall support the Government at PDR, to include, reviewing documents and documenting minutes of the actions, activities and decisions discussed at the PDR. (CDRL A002, DI-ADMN-81250C) (CDRL A004 DI-MISC-80711A)
4.13.5 Critical Design Review (CDR) If required, the Contractor shall support the Government at CDR, to include, reviewing documents and documenting minutes of the actions, activities and decisions discussed at the CDR. (CDRL A002, DI-ADMN-81250C) (CDRL A004, DI-MISC-80711A)
4.14 CONTRACTOR PROGRAM MANAGEMENT: The Contractor shall prepare quarterly status reports describing technical and financial status to include, GFM/GFP required for Verification and Validation. The Contractor’s Quarterly Status Report (QSR) shall clearly outline and report their schedule and status. Program objectives shall be addressed as outlined by the Government. The Contractor shall provide notification of all possible impacts to schedule or cost within two (2) business days of determining an impact could exist. Data submissions shall be timely, accurate and comprehensive.
No more than two (2) data submissions shall be received late during the contract period of performance, and no late submissions in consecutive months. No submission shall be received later than five (5) business days after its scheduled submission date. Any mandated rewrites shall be due within five (5) business days after the Government’s identification of the error(s).
A Performance Assessment Report (PAR) will be created by USG each quarter for performance validation. A final report shall be submitted at end of basic and option period of performance. PAR will be routed to Contractor for concur/non-concur, signed, and returned within five (5) business days. A negative PAR or a Corrective Action Report (CAR) will be signed and returned by the suspense date. At the end of each contract year, a Contractor Performance Assessment Report (CPAR) is required. A CPAR draft will be routed to Contractor with justifications only to examine for seven (7) calendar days. Contractor’s response to the CPAR will be coordinated through Division level management and once approved the CPAR will be sent to the Contractor via CPARS for the official sixty (60) calendar day review. The Contractor shall have the option to concur or non-concur, with comments, via Contractor Performance Assessment Reporting System (CPARS).
(CDRL A003, DI-MGMT-80368A) (CDRL A004, DI-MISC-80711A)
4.15 Holidays and Facility Closings: Contractor/subcontractor personnel shall observe holidays and facility closings as authorized for government personnel. Contractor/subcontractor personnel shall only be permitted access to Government facilities when Government personnel are present.
4.16 TRAVEL
The Contractor may be required from time to time to travel to other Government or non-Government installations or facilities. Trips and numbers and types of personnel shall be limited to the minimum required to accomplish the work requirements. The Contractor shall be responsible for arranging all Contractor personnel travel. All requests for travel conducted in support of this PWS must be approved by the Government PCO. The Contractor shall submit a Request for Travel to the PCO ten (10) business days prior to the scheduled departure date.
Travel requests submitted to the PCO must be pre-approved by the PM. The names of travelers, anticipated costs, as
FD2060-25-30215 13
well as dates and purpose of travel, shall be included in the travel requests and reported in the QSR. Travel by Contractor personnel shall be conducted in accordance with FAR 31.205-46, Travel Costs. Trip report shall be submitted under technical report (CDRL A004, DI-MISC-80711A).
5.0 GENERAL INFORMATION
5.1 Continuation of Mission-Essential Services During a Crisis: The Functional Service Manager (FSM) has determined these services are not mission-essential and will not continue in the event of a crisis.
5.2 Security Requirements
5.2.1 Security Regulations: The Contractor shall ensure personnel, information, system, property, facility and, if applicable, international security requirements are met. The Contractor shall ensure contractor/subcontractor personnel who perform work on a Government facility comply with the security requirements of the facility. The Contractor shall comply with the following security regulations: Property/Facility - RAFBI Chapters 5, Key and Lock Control, and 7, Physical Security of the Facility. Personnel - DoDM 5200.02_AFMAN 16-1405, Air Force Personnel Security Program. Information - DoDI 5200.48_DAFI16-1403, Controlled Unclassified Information and DoDM 5200.01V3_AFMAN 16-1404V1-3, Information Security Program.
5.2.2 Operations Security (OPSEC): The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. DoDD 5205.02E and DoD Manual 5205.02-M require contractors supporting DoD activities use OPSEC to protect critical information for specified contracts, subcontracts, and information used in the performance of duties in support of Air Force requirements/missions. The Contractor shall ensure Contractor personnel who perform work on (or in) a Government facility comply with the OPSEC procedures and training requirements of the facility as specified in
AFI 10-701.
5.2.3 Communications Security (COMSEC): The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer classified information and/or Controlled Unclassified Information (CUI) in accordance with 32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM), § 117.7(a).
5.2.4 Security Clearance: The Contractor shall ensure applicable contractor/subcontractor personnel have security clearance(s) at the Secret level for proper accomplishment of contract/order requirements. The security clearance(s) shall be obtained in accordance with the Department of Defense (DD) Form 254, Department of Defense Contract Security Classification Specification.
5.2.5 Security Incident or Violation: The Contractor shall immediately notify the Government Security Office of any potential or actual security incident or violation.
5.2.6 Access to Government System(s): The Government will provide contractor/subcontractor personnel access to system(s) necessary to perform tasks under the contract/order. The Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified or classified Government Automated Information System (AIS) have the respective background check or security investigation conducted. At a minimum, the Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified AIS have a National Agency Check with Inquiries (NACI) conducted. Upon completion/termination of the contract/order or transfer/termination of contractor/subcontractor personnel, the Contractor shall ensure the system account(s) are closed.
FD2060-25-30215 14
5.2.7 Access to Government Facility or Military Installation: The Contractor shall ensure contractor/subcontractor personnel who require access to a Government facility or military installation comply with the security requirements of the facility or installation.
5.2.8 Access to Robins Air Force Base (AFB): The Contractor shall ensure contractor/subcontractor personnel who require access to Robins AFB comply with the security requirements of the installation. The Contractor shall provide the PCO a list of all contractor/subcontractor personnel requiring access to Robins AFB, the contract/order number and the period of performance. The Contractor shall also provide, if possible, the location of the work site and the days/hours during which the contractor/subcontractor personnel will require access to Robins AFB.
5.2.9 Common Access Card (CAC)
5.2.9.1 The Contractor shall ensure a CAC is obtained by all contractor/subcontractor personnel who require access to DoD computer networks/systems, for DoD facility entry control and/or for physical access to facilities and buildings to perform tasks under the contract/order. The Contractor shall provide a list of contractor/subcontractor personnel who require a CAC to the PCO. The Government will provide the Contractor instruction on how to complete a Trusted Associate Sponsorship System (TASS) application and notify the Contractor of approval/disapproval of contractor/subcontractor personnel application. Contractor/subcontractor personnel shall obtain the CAC from the local Real Time Automated Personnel Identification Documentation System (RAPIDS) issuing facility [usually the Military Personnel Flight (MPF)].
5.2.9.2 The Contractor shall immediately report a lost or stolen CAC as directed by local Government policy.
The Contractor shall notify the PCO of any change to the list of contractor/subcontractor personnel who require a CAC and provide an updated list within five business days. The Contractor shall return a CAC within five business days once contractor/subcontractor personnel no longer require computer network/system access and/or facility access. The Contractor shall return an expired CAC within five business days after the expiration date.
The Contractor shall return any and all CACs within five business days after completion/termination of the contract as directed by local Government policy.
5.3 Environmental Management System (EMS): Contractor/subcontractor personnel who perform work on any Government facility shall comply with the EMS requirements established by the facility.
Contractor/subcontractor personnel may be required to complete EMS training prior to beginning work.
5.4 Agency Affirmative Procurement Programs: This acquisition does not require the purchase of Environmental Protection Agency (EPA)-designated products or United States Department of Agriculture (USDA)-designated products; therefore, the requirement does not apply.
5.5 Safety Requirements
5.5.1. Contractor Environmental, Safety, and Occupational Health Compliance: The Contractor shall comply with Government Safety and Health regulations including, but not limited to, Public Law 91-596, Occupational Safety and Health Act (OSHA), and DoD Directive 4715.01E, Environmental, Safety, and Occupational Health (ESOH). The Contractor shall establish and maintain a safety and health program detailed in a written Contractor’s Safety and Health Plan (SHP). The Contractor shall require all subcontractors to comply with required safety, health and fire standards
5.5.2. Contractor Safety & Health Program/Plan. The Contractor shall establish and maintain a safety and health program detailed in a written Contractor’s Safety and Health Plan (SHP) in accordance with OSHA
FD2060-25-30215 15
and ESOH and tailored to the contract. The SHP shall address the requirements established in the Safety Appendix (Environmental, Safety and Occupational Health Requirements) to the contract. The Contractor shall submit the SHP to the MFT member identified on the CDRL [CDRL Reference in paragraph 4.2, DI- MGMT-80368A, Environmental, Safety, and Occupational Health (ESOH) Plan]. The cognizant Government safety office will review the SHP to determine if safety requirements are correctly addressed.
The Contractor shall notify the cognizant Government safety office of any revisions made to its SHP after contract award. All changes to the SHP must also be submitted in writing and approved by the cognizant Government safety office [CDRL Reference in paragraph 4.2, DI- MGMT-80368A, Contractor’s Standard Operating Procedures – Company Safety Plan].
5.5.3 Mishap Notification/Investigation: In accordance with DAFI 91-204, Safety Investigations and Reports, the Contractor shall report mishaps involving damage or injury to USAF assets/interests. The Contractor shall ensure the USAF is notified of mishaps. The Contractor shall contact the Contracting Officer (CO) or the Contracting Officer’s Representative (COR), if available, or another MFT member by telephone within eight (8) hours of any damage to government property where the dollar value exceeds $600,000.00, and within two workdays for any damage to government property less than $600,000.00 during the execution of the contract. Mishap notifications shall contain, as a minimum, the following information:
a. Contract, contract number, name, and title of person(s) reporting
b. Date, time, and exact location of accident/incident
c. Brief narrative of accident/incident (events leading to accident/incident)
d. Cause of accident/incident, if known
e. Estimated cost of accident/incident (material and labor to repair/replace)
f. Nomenclature of equipment and personnel involved in accident/incident
g. Corrective actions (taken or proposed)
h. Other pertinent information
If requested by the designated CO or COR, the Contractor shall immediately secure the mishap scene (and damaged property) and impound pertinent maintenance and training records until released by the Government’s safety office. Such release shall be accomplished through the Contracting Officer. The Contractor shall cooperate and assist Government personnel in the investigation of the mishap and submit an Accident/Incident Report within 48 hours of the mishap [CDRL Reference in paragraph 4.2, Accident/Incident Report, DI-MGMT-80368A]
5.6 Inspection of Services: In accordance with the Inspection of Supply/Services clause(s) identified in the contract/order, the Government reserves the right to inspect Contractor performance.
5.7 Service Contract Reporting: In accordance with 10 United States Code 2330(a), and DFARS 252.204- 7023 (Reporting Requirements for Contracted Services), the Contractor shall provide a Service Contract Report for each contract/order that meets the DoD Contract Reporting criteria and has obligations in excess of
FD2060-25-30215 16
$3,000,000. The Contractor shall report the total amount invoiced and contractor labor hours expended on the services performed during the previous fiscal year. Prime contractor labor hours, including any required Tier 1 subcontractor information, shall be reported in the System for Award Management (SAM). The Contractor shall report annually, by October 31, on the services performed during the preceding government fiscal year. SAM will only enable reporting for entities with contracts that meet the SCR criteria and thresholds. Additional information and user manuals for government personnel and Contractors is available at https://www.sam.gov.
SCR eligibility, reporting rules and criteria is located on the DoD Procurement Toolbox at https://dodprocurementtoolbox.com/site-pages/service-contract-reporting-scr.
5.8 Invoicing/Payment and Receipt/Acceptance: The Contractor shall submit/process payment requests and receipt/acceptance documents via WAWF.
5.9 Quality Control Plan/Quality Management System (QMS): The Contractor shall ensure the quality of services through a quality and/or inspection system. The Contractor shall submit a Quality Control Plan (QCP) addressing detection of quality program problems and defects, identification of root causes for quality related problems/defects, correction of root causes related to detected problems/defects, and follow-up to ensure quality related problems/defects do not recur. The plan shall include the schedule of quality assurance/control inspections planned by the Contractor. 100% compliance with the QMS is required. (CDRL A003 DI-MGMT-80368A, Quarterly Status Report, paragraph 4.2)
5.10 Trafficking in Persons: The Contractor shall comply in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract as it relates to Trafficking in Persons. Additional information about Trafficking in Persons is available at the site for the Department of State’s Office to Monitor and Combat Trafficking in Persons. http://www.state.gov/j/tip
6.0 Appendices
6.1 Appendix A, Reference(s)
Publication Information Access Publication Date DFARS https://www.acquisition.gov/dfars FAR https://www.acquisition.gov/ GFP Training https://dodprocurementtoolbox.com/ Air Force Instruction (AFI) 10-701
OPSEC 24 Jul 2019
Procurement Integrated Enterprise Environment
(PIEE)
https://piee.eb.mil
Technical Oder 00-25-107 Maintenance Assistance 1 Oct 2015 https://www.sam.gov/ https://dodprocurementtoolbox.com/site-pages/service-contract-reporting-scr http://www.state.gov/j/tip https://www.acquisition.gov/dfars https://www.acquisition.gov/ https://dodprocurementtoolbox.com/ https://piee.eb.mil/
File details come from the government source that posted it. Updated .