USAF_C-130_AIRCAT_PWS_Aug_2018.pdf

FD2060-18-30409

Performance-Based Work Statement (PWS)

C-130 Automated Inspection, Repair, Corrosion, and Aircraft Tracking (AIRCAT)

Support

Air Force Life Cycle Management Center (AFLCMC) Robins AFB, GA

Date: 4 SEP 2018

Prepared by:

AFLCMC/WLNE

235 Byron Street, Suite 19A Robins AFB, GA 31098

DISTRIBUTION STATEMENT: Distribution authorized to U.S. Government Agencies and their Contractors (Critical Technical) (14Jul08). 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.

Rev C (30 May 2018) - DRAFT

1.0 DESCRIPTION OF SERVICES:

1.1 Background:

The C-130 Automated Inspection, Repair, Corrosion, and Aircraft Tracking (AIRCAT) system collects and processes Individual Aircraft Tracking Program (IATP) data to support the Aircraft Structural Integrity Program (ASIP). AIRCAT allows uploads of flight data from the field, stores, and then processes this data to track C-130 service life.

The C-130 Original Equipment Manufacturer (OEM), Lockheed Martin, has developed and delivered the methodology to track C-130 fracture growth. The USAF C-130 ASIP Managers use this methodology in AIRCAT to calculate service life as required by AFI 63-140 and MIL-STD-1530D. The OEM is under contract to periodically deliver updated crack growth data which is used to update AIRCAT.

In addition to the IATP functions, C-130 AIRCAT processes Technical Assistance Requests in accordance with Technical Order (TO) 00-25-107, collects inspection finding data via the Inspection, Crack/Corrosion, And Repair Reporting (ICARR-3D) tool;

provides individual aircraft inspection tracking capability, performs structural analyses via the Stress Tool module, contains a repository for engineering reports, and generates engineering reports based on AFLCMC/WLNE defined queries.

1.2 Objective(s):

The Contractor shall maintain and update C-130 AIRCAT in support of C-130 ASIP requirements. Additionally, the Contractor shall support the development, evaluation, and implementation (as directed) of the new “FTP-7000” mission grid for C-130H processing. Examples of updates include changes to fracture growth tracking based on OEM updates, ICARR-3D changes based on TO updates and user requested improvements, maintain the aircraft database and modules IAW USAF and DoD software requirements, correct identified deficiencies and enhancements identified in System Change Requests (SCRs), and correct defects in the data.

1.3 Benefit to the United States Air Force (USAF):

The C-130 AIRCAT system is utilized to track the service life and inspections required to ensure the safety of flight of the USAF C-130 fleet. Without the capability provided by AIRCAT, the required service life and safety of flight inspections on C-130 aircraft cannot be determined, and the data necessary to maintain the safety of the C-130 fleet will be deficient and impaired. Accomplishment of these updates is necessary to ensure aircraft and aircrew safety.

2.0 SERVICES SUMMARY (SS):

Performance Objectives

PWS

Paragraph Performance Threshold

Accurate and timely reporting of updates to the AIRCAT system in monthly status reports

5.1

No more than two (2) monthly status reports shall contain errors per contract year. The Contractor shall have three (3) business days to correct these errors after they are identified by the Government. No more than one (1) late monthly status report per quarter.

Timely scheduling of PMRs/TIMs and delivery of accurate minutes

5.1

Contractor shall conduct quarterly PMR/TIM. Minutes and submissions shall be provided as prescribed per the Contract Data Requirements List (CDRL). Minutes shall be comprehensive and accurately describe the events of the meeting.

Minutes shall never be more than five (5) business days late and no more than one (1) submission shall be returned for correction per contract year. Any mandated rewrites shall be due within five (5) business days after Government’s identification of error(s). No more than one (1) late submission of minutes per contract year.

3.0 GOVERNMENT FUNISHED PROPERTY, EQUIPMENT, MATERIAL, AND

SERVICES (GFP/GFE/GFM/GFS):

3.1 Government Property:

The Government will supply access to C-130 AIRCAT, all necessary Government peculiar software programs [e.g. Global Combat Support System (GCSS) – AF Data Services, Reliability and Maintainability Information System (REMIS), Integrated Maintenance Data System (IMDS), ICARR-3D, etc.], TOs, and releasable engineering drawings required to complete the tasks identified herein. Data supplied by the Government remains the property of the US Government.

3.2 Government Property to be Provided:

The Government will supply on-site contractor personnel with Individual Aircraft Tracking Program and Aircraft Structural Integrity Program (IATP/ASIP) data to be manipulated.

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) in accordance with the FAR and applicable supplements.

3.4 Reporting of Government Property:

The Contractor shall create and maintain records of all Government property accountable to the contract, including Government-Furnished Property (GFP) in accordance with the FAR and applicable supplements, and shall be in compliance with all applicable guidance and clauses in the contract.

3.4.1 Definitions:

3.4.1.1 As used in this clause, “Government property” is defined in the clause of FAR 52.245-1(a), Government Property. “Loss of Government property” means unintended, unforeseen, or accidental loss, damage, or destruction of Government property that reduces the Government’s expected economic benefits of the property. Loss of Government property does not include purposeful destructive testing, obsolescence, normal wear and tear, or manufacturing defects. Loss of Government property includes, but is not limited to,

3.4.1.1.1 Items that cannot be found after a reasonable search;

3.4.1.1.2 Theft;

3.4.1.1.3 Damage resulting in unexpected harm to property requiring repair to restore the item to a usable condition; or

3.4.1.1.4 Destruction resulting from incidents that render the item useless for its intended purpose or beyond economical repair.

3.4.1.2 As used in this clause, “unit acquisition cost” means,

3.4.1.2.1 For Government-furnished property, the dollar value assigned by the Government and identified in the contract; and

3.4.1.2.2 For Contractor-acquired property, the cost derived from the Contractor’s records that reflect consistently applied, generally acceptable accounting principles.

3.4.2 Reporting loss of Government property:

3.4.2.1 The Contractor shall use the Defense Contract Management Agency

(DCMA) eTools software application for reporting loss of Government property. Reporting value shall be at unit acquisition cost. The eTools “LTDD of Government Property” toolset can be accessed from the DCMA home page External Web Access Management application at http://www.dcma.mil/aboutetools.cfm.

3.4.2.2 Unless otherwise provided for in this contract, the requirements of paragraph 3.4.2.1 of this clause do not apply to normal and reasonable inventory adjustments, i.e., losses of low-risk consumable material such as common hardware, as agreed to by the Contractor and the Government Property Administrator. Such losses are typically a product of normal process variation. The Contractor shall ensure that its property management system provides adequate management control measures, e.g., statistical process controls, as a means of managing such variation.

3.4.2.3 The Contractor shall report losses of Government property outside normal process variation, e.g., losses due to theft; inadequate storage;

lack of physical security; or “acts of God.”

3.4.2.4 This reporting requirement does not change any liability provisions or other reporting requirements that may exist under this contract.

3.5 Return/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 Contractor is directed by the PCO 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 Contractor is directed by the PCO to retain the material for continued use under a successor contract.

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

4.0 TECHNICAL REQUIREMENTS:

4.1 Place and Period of Performance:

4.1.1 Place of Performance: These services shall be performed at the Contractor’s facility and Robins AFB, GA.

4.1.2 Holidays and Facility Closings: On-site Contractor personnel shall observe the ten federal holidays and facility closings (e.g. energy down days) authorized by the Government. On-site Contractor personnel will only be permitted access to Government facilities when Government personnel are present.

4.1.3 Period of Performance: The period of performance for the contract/order will include a one (1) year basic period for a total period of performance of one (1) year.

4.2 The Contractor shall update the AIRCAT system to incorporate changes identified by the USG, the C-130 OEM, or the Contractor’s analysis of C-130 recorded data.

AIRCAT changes may include, but are not limited to: changes in growth coefficients, changes in mission profile descriptions, addition or deletion of mission profiles, additions or deletions of tracking zones, changes in static tables, and changes to system algorithms. These changes shall be approved by the USAF C- 130 ASIP Managers prior to implementation.

4.2.1 The Contractor shall work with the USAF C-130 ASIP Managers and the C-

130 OEM to develop, incorporate, process, analyze, evaluate, and correct discrepancies with the proposed new mission grid (FTP-7000 series) for C- 130H Equivalent Flight Hour (EFH) tracking. If approved by the USAF C- 130 ASIP Managers, the Contractor shall implement the new mission grid on the production AIRCAT server.

4.3 The Contractor shall support Government efforts for Loads/Environment Spectra

Survey (L/ESS) data recording, retrieval, archiving, and analysis. The Contractor shall provide independent review of the L/ESS program. Contractor shall support planning, design, installation, validation, and maintenance of data retrieval, storage, and assessment requirements as tasked. Contractor shall provide usage monitoring on select aircraft as an interim bridge to the long-term permanent L/ESS installation.

(CDRL A007, DI-MISC-80711A/T, Scientific and Technical Report) (CDRL A008, DI-SESS-80776A, Technical Data Package)

4.4 The Contractor shall process C-130J Structural Health Monitoring (SHM) data in AIRCAT for the purpose of facture growth tracking IAW requirements defined by the OEM. Examples of these tasks include, but are not limited to: processing of C-

130J SHM data by a dedicated server, development of a separate database schema to store and record C-130J data (actual and makeup), update and maintain AIRCAT reports to include C-130J results in the outputs, and sustainment of the C-130J Usage Admin module to allow C-130J flight data to be reviewed and corrections made on erroneous flight data.

4.5 The Contractor shall maintain and update the Inspection Tracker tool to match changes to C-130 technical manuals (e.g. -6, -36 series), to apply updates to fracture growth tracking, and to incorporate user defined improvements to the Graphical User Interface (GUI). These changes shall be approved by the USAF C-130 ASIP Managers prior to implementation

4.6 The Contractor shall perform updates to the ICARR-3D tool to reflect changes in published technical manual requirements, incorporate improvements to the GUI, and incorporate fixes to user defined problem tickets. Examples of these requirements include, but are not limited to: updates of administrative functionality, interface with maintenance requirements database, updates to training modules, updates to parts tree, updates to GUI, browser compatibility, and addition of parts to the 3D model. These changes shall be approved by the USAF C-130 ASIP Managers prior to implementation.

4.7 The Contractor shall provide technical support with AIRCAT integration and enhancements to the C-130 Stress Tool to meet HTML 5 standards similar to ICARR-3D. Enhancements include the addition of aircraft parts, new/updated load cases, and GUI improvements. Model enhancements shall include updates to and reverification/revalidation of the C-130 global Finite Element Model (FEM). New results files shall be generated for all load cases.

4.8 The Contractor shall maintain and update the Engineering Reports Repository (ERR) as the centralized database for all USG C-130 and C-130 modification related reports. The ERR shall permit uploads of searchable PDF and Microsoft Office (e.g. Word, Excel, PowerPoint) file types.

4.9 The Contractor shall update Web and Tableau reports to address deficiencies, redundancies, inaccuracies, and user defined improvements. Additionally, the Contractor shall add new Web and Tableau reports as directed by the USAF C-130 ASIP Managers to assist with engineering studies.

4.10 The Contractor shall maintain a list System Change Requests (SCRs) to document changes made to C-130 AIRCAT. These SCRs represent identified deficiencies, corrections, or enhancements to the AIRCAT system. The Contractor shall change/update AIRCAT to implement the SCRs as directed and approved by the USAF C-130 ASIP Managers.

(CDRL A001, DI-MGMT-80227/T, Contractor’s Progress, Status, and Management Report)

4.11 The Contractor shall update the AIRCAT system to implement software patches and compatibility with the latest software versions. The Contractor shall identify and correct data entry errors associated with the input of flight, inspection, and repair data.

4.11.1 The Contractor shall provide an on-site individual who possesses certification equivalent to an Oracle Database Administrator (DBA) in order to identify data/system errors and to maintain the latest software changes.

4.11.2 The Contractor shall use the sources below to determine database update requirements:

4.11.2.1 The Contractor shall monitor the AIRCAT Oracle database performance and make changes to improve performance and correct deficiencies.

4.11.2.2 The Contractor shall coordinate with 581st SMXS on

integration and testing of software changes.

4.11.2.3 The Contractor shall implement deficiency corrections and

SCRs identified by the USAF C-130 ASIP Managers.

4.11.2.4 The Contractor shall implement software changes when approved for USAF use.

4.12 The Contractor shall identify and correct AIRCAT data discrepancies IAW the following:

4.12.1 The Contractor shall interface with AFLCMC/WLNE, Depot users, MAJCOM users, field units, Mobility Aircraft Data Systems G081, Integrated Maintenance Data Systems (IMDS), Reliability & Maintainability Information System (REMIS), and/or Global Combat Sustainment System (GCSS) to resolve discrepancies between flight, inspection, and repair data;

TO 00-25-107 requests in the AIRCAT database, and data obtained from these systems.

4.12.2 The Contractor shall interface with G081, IMDS, REMIS, and/or GCSS to determine a plan to share data and reduce duplicate data entries required by AIRCAT and those systems.

4.12.3 The Contractor shall, at the request of the AFLCMC/WLNE, build queries to extract sustainment data from the AIRCAT database.

4.13 The Contractor shall update the Live Document module, or equivalent, and facilitate updates to the ASIP Master Plan and Force Structural Maintenance Plan.

4.14 The Contractor shall maintain existing documentation and create any newly required documentation to keep current the C-130 AIRCAT system Authorization To Operate (ATO). The Contractor shall conduct the activities required by the C-130 AIRCAT Continuous Monitoring Plan, including, but not limited to, scanning source code for vulnerabilities, scanning operating systems and databases for vulnerabilities, and maintaining compliance with DoD Security Technical Implementation Guides (STIGs) and the NIST 800-137 Special Publication – Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations.

4.15 The Data Center Optimization Initiative (DCOI) established in OMB Memorandum M-16-19 supersedes the Federal Data Center Consolidation Initiative (FDCCI) and fulfills the data center requirements of the Federal Information Technology Acquisition Reform Act (FITARA). The Contractor shall conduct activities to allow for the migration of the C-130 AIRCAT system to an approved cloud service to achieve compliance with the DCOI.

4.16 The Contractor shall document changes made to the C-130 AIRCAT system and deliver final source data at the completion of the contract. Source data remains the property of the USG. The Contractor shall utilize Microsoft Visual Studio for modules. Source code shall be tested and delivered in a format that is compatible with the above-mentioned development environments (i.e. compile and run with no errors).

(CDRL A003, DI-MISC-80508B, Technical Support – Study/Services) (CDRL A004, DI-IPSC-81488, Computer Software Product) (CDRL A005, DI-IPSC-81437A/T, Database Design Description)

4.17 The Contractor may be required to purchase material, licenses, or equipment necessary to support the efforts defined in this PWS. The Contractor’s purchases of material, licenses, or equipment shall not exceed $25,000 in a 12 month period without prior Government approval.

4.18 Any requested changes outside the scope of this effort shall be coordinated with the USG PCO, PM, and USAF ASIP Managers prior to implementation.

5.0 GENERAL INFORMATION:

5.1 Program Management: The Contractor shall provide monthly status reports in accordance with the Contract Data Requirements List (CDRL). The Contractor shall document task status, data deliverables, contract issues and actions as well as anticipated future task requirements during the next reporting period. In addition, all problem areas shall be covered as necessary, with recommended solutions and the outcome after solutions are implemented. The Contractor shall hold a quarterly Program Management Review (PMR)/ Technical Interchange Meeting (TIM) to review progress and status, including any outstanding action items. The quarterly PMR/TIM shall be held at the Contractor’s facility. The Contractor shall provide external support briefings as requested, and generate minutes and track action items for PMRs/TIMs. The Contractor shall assign and track action items for each unresolved program problem or issue. The Contractor shall assign action item numbers based on the program and action item source.

The Contractor shall provide minutes of any other program meeting if determined necessary by the Program Manager (PM) and Procurement Contracting Officer (PCO).

Meeting minutes shall include attendees and record the significant decisions and commitments that are made during the meeting. Meeting minutes shall be in accordance with the CDRL. Minutes shall never be more than five (5) business days late and no more than one (1) submission shall be returned for correction per contract year. Any mandated rewrites shall be due within five (5) business days after the Government’s identification of error(s). There shall be no more than one (1) late submission of minutes per contract year. Monthly status reports shall be IAW CDRL. No more than two (2) monthly status reports shall contain errors per contract year. The Contractor shall have three (3) business days to correct these errors after they are identified by the Government.

There shall be no more than one (1) late monthly status report per quarter.

(CDRL A001, DI-MGMT-80227/T, Contractor’s Progress, Status, and Management Report) (CDRL A002, DI-ADMN-81250B/T, Conference Minutes)

5.2 Travel: The Contractor may be required to travel to Government installations or to other Contractor facilities. Routine travel requests shall be submitted for approval to the COR a minimum of two (2) weeks in advance of the departure date. Urgent travel requests may be submitted for approval in a shorter timeline and will be considered on a case by case basis. The Contractor shall provide a list of any projected travel requirements in the monthly status report. Trips, as well as number and types of personnel, shall be limited to the minimum required to accomplish work requirements. The Contractor shall be responsible for arranging all travel of Contractor personnel during the program effort. All travel shall be in accordance with FAR 31.205-46 Travel costs. All trip reports shall be documented in the monthly status report. The Government anticipates that no more than four (4) trips to Continental United States (CONUS) will be necessary.

5.3 Continuation of Mission-Essential Services During a Crisis:

5.3.1 In accordance with DFARS 252.237-7023(a) and AFI 10-403, Deployment

Planning and Execution, paragraph 1.9.1.33.2, the Functional Commander (FC) or civilian equivalent has determined these services are not mission-essential and will not continue in the event of a crisis.

5.4 Security Requirements.

5.4.1 Classification of Information: This project is unclassified; however, no data, technical or otherwise, concerning this project, shall be released through publication or in any manner, except with specific written authorization by the PCO. As a minimum, a National Agency Check (NAC) is required. Access to classified information will not be required in the performance of this effort;

however, access to restricted or unclassified export control information may be required. Actual knowledge of, generation, or production of classified information is not required for performance of the contract. Cleared personnel are required to perform this service because security measures which are in force do not preclude access to classified information.

5.4.2 Government Security Regulations: The Contractor shall ensure personnel, information, system, property, and facility security requirements are met.

The Contractor shall comply with Government security regulations including, but not limited to, Department of Defense (DoD) 5200.2-R, Personnel Security Program; DoD Directive (DoDD) 5205.02E, DoD Operations Security (OPSEC) Program; DoD Manual 5205.02-M, DoD Operations Security (OPSEC) Program Manual; and Robins Air Force Base Integrated Defense Plan (RAFB IDP) 31-101.

5.4.3 Operations Security (OPSEC): The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. The Contractor shall ensure compliance with DoDD 5205.02E, DoD Directive for Operations Security (OPSEC) and DoD Manual 5205.02-M, DoD Operations Security (OPSEC) Program Manual to protect United States (U.S.) Government interests. The Contractor shall ensure Contractor personnel who perform work on a Government facility comply with the OPSEC procedures of the facility.

5.4.4 Security Clearance: Contractor employees that require access to Government-owned Automated Information Systems (AIS) will require the minimum of a Favorable NAC. Submit a Standard Form 85P, Questionnaire for Public Trust Positions, (fingerprint cards, if available) to the AFLCMC/WLN Security Office for processing. If security clearances become necessary after contract/order award, the Contractor shall ensure applicable Contractor personnel obtain valid security clearances appropriate to the access required for proper accomplishment of contract/order requirements.

5.4.5 Security Incidents and Violations: The Contractor shall immediately notify the AFLCMC/WLN Security Office of any potential or actual security incident or violation including potential or actual unauthorized disclosure or compromise of classified and/or controlled unclassified information.

5.4.6 Security Education: All full-time contractor employees occupying physical space on Robins Air Force Base will comply with the AFLCMC/WLN Security Education and Awareness Program. The program consists of the following components: Initial Training, Annual Refresher Training, and periodic tailored training.

5.5 Withholding of Unclassified Technical Data from Public Disclosure.

5.5.1 Pursuant to Department of Defense Directive (DoDD) 5230.24 Distribution

Statements on Technical Documents(18 Mar 1987), DoDD 5230.25 Withholding of Unclassified Technical Data From Public Disclosure(6 Nov 1984), 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 PWS and CDRL requirements, with the following:

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government Agencies and their contractors (Critical Technical) (14Jul08). 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.

5.6 Common Access Card (CAC).

5.6.1 Obtaining a CAC: The Contractor shall ensure a CAC is obtained by all contractor/subcontractor personnel who require access to DoD computer networks/systems, DoD facility entry control, and/or 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 Contractor Verification System (CVS) 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 System (RAPIDS) issuing facility [usually the Military Personnel Flight (MPF)].

5.6.2 Loss of Card: In accordance with RAFB IDP 31-101, if Contractor personnel lose their DBIDS ID card or CAC, they shall notify the badging agent immediately.

5.6.3 Retrieval of Card: In accordance with RAFB IDP 31-101, the Contractor shall notify the badging agent immediately upon Contractor personnel being transferred/terminated. The Contractor shall be responsible for retrieving contractor/subcontractor CAC(s) and/or DBIDS ID card(s) (including restricted/controlled area badges) upon transfer/termination of Contractor personnel or completion/termination of the contract/order. The Contractor shall return all retrieved CAC(s) and/or DBIDS ID card(s) to 78 SFS/S5P.

5.7 Environmental Management System (EMS):

5.7.1 The requirements for EMS are established under Executive Order (E.O.)

13693, Planning for Federal Sustainability in the Next Decade.

5.7.2 All Contractors who physically perform work on Robins AFB shall receive EMS awareness training. All prime Contractors shall complete the training prior to the start of work on RAFB and shall ensure that all subcontractors comply with this requirement.

5.7.3 The EMS training requirements shall be satisfied by any of the following means:

5.7.3.1 If the Contractor is ISO 14000 certified, Contractor personnel do not have to complete EMS training; however, the Contractor shall provide documentation of ISO 14000 certification to the PCO.

5.7.3.2 With a CAC, Environmental Management System – General

Awareness Training can be completed via the Advanced Distributed Learning Service (ADLS) site, https://golearn.adls.af.mil/kc/main/kc_frame.asp. The Contractor shall provide their certificates to the PCO.

5.7.3.3 Without a CAC, the Contractor shall request a copy of Robins EMS

Awareness Training via the Environment Management Workflow, 78ceg.cev.FrontOfc@robins.af.mil. The Contractor shall notify the PCO that EMS training has been completed and provide any certificates.

5.8 Green Procurement Program (GPP).

5.8.1 GPP is a mandatory federal acquisition program that focuses on the purchase and use of environmentally preferable products and services. GPP https://golearn.adls.af.mil/kc/main/kc_frame.asp mailto:78ceg.cev.FrontOfc@robins.af.mil requirements apply to all acquisitions using U. S. Government appropriated funds, including services and new requirements. FAR 23.404(b), Agency Affirmative Procurement Program, applies and states the GPP requires 100% of EPA designated product purchases that are included in the Comprehensive Procurement Guidelines (CPG) list that contains recovered materials, unless the item cannot be acquired: (a) competitively within a reasonable timeframe;

(b) meet appropriate performance standards, or (c) at a reasonable price. The prime contractor shall be responsible for ensuring that all subcontractors comply with this requirement.

5.9 Quality Management System (QMS).

5.9.1 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 A009, DI-QCIC-81795, Software Quality Assurance Report)

5.10 Inspection of Services

5.10.1 In accordance with FAR 52.246-4 Inspection of Services – Fixed-Price and

FAR 52.246-5 Inspection of Services – Cost-Reimbursement, the Government reserves the right to inspect Contractor performance.

5.11 Safety Requirements.

5.11.1 Contractor Compliance: Contractors shall comply with Occupational Safety and Health Act (OSHA) Public Law 91-596, OSHA Standard 29 CFR 1910, and DoDD 4715.1E, Environmental, Safety, and Occupational Health (ESOH) for the protection of their employees. To ensure the protection of Air Force personnel, assets, and interests, the Contractor shall be solely responsible for compliance with all federal, state, and local laws, codes, ordinances, regulations, the Occupational, Safety and Health Act (Public Law 91-596), and the resulting OSHA Standards 29 CFR 1910, (ESOH), all Air Force Occupational Safety and Health (AFOSH) Standards, and any applicable local guidance. The Contractor shall establish and maintain a safety and health program detailed in a written Contractor’s Safety and Health Plan.

5.11.1.1 The Air Force is part of the OSHA Voluntary Protection

Program (VPP). All Contractor personnel who perform work on a

USAF installation shall participate in the local VPP. Information on the VPP can be accessed at http://www.osha.gov/dcsp/vpp/index.html. Additionally, the Contractor is responsible for the safety and health of all subcontractor employees.

(CDRL A006, DI-ENVR-81375, Environmental Health and Safety Plan)

5.11.2 Mishap Notification: In accordance with AFI 91-204, Safety Investigations and Reports, paragraph 2.4.6.1.1, the Contractor shall report mishaps involving damage or injury to USAF interests. Damage or injury includes:

damage to DoD property; occupational illness to DoD military or civilian personnel; injury to on- or off-duty DoD military personnel; injury to on-duty DoD civilian personnel; and damage to public or private property or injury or illness to non-DoD personnel caused by USAF operations. The Contractor shall ensure the USAF [Safety Office] and the applicable contract management authority are notified of mishaps. The Contractor shall contact the MFT [Contracting Officer’s Representative (COR), if available, or another MFT member] by telephone within four business hours. The MFT will notify the AFLCMC Safety Office, DSN 785-3395 or 3239, Commercial

(937) 255-3395 or 3239, and the PCO.

5.11.3 Mishap Investigation: If requested by the Government Procuring Contracting Officer (PCO) or Administrative Contracting Officer (ACO), the Contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenances and training records until released by the investigating safety office.

If the Government investigates the mishap, the Contractor and the subcontractors shall cooperate fully and assist the Government personnel until the investigation is completed.

5.12 Contractor Manpower Reporting Requirements.

5.12.1 Per reference SAF/AQ Memo, 13 Nov 12, “The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the USAF via a secure data collection site. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil. Reporting inputs shall be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 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 CMRA help desk.

5.12.1.1 Reporting Period: Contractors are required to input data by 31

October of each year.

http://www.osha.gov/dcsp/vpp/index.html http://www.ecmra.mil/

5.12.1.2 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 data be released to the public with the contractor name and contract number associated with the data.

5.12.1.3 User Manuals: Data for Air Force service requirements must be input at the Air Force CMRA link. However, user manuals for Government personnel and contractors are available at the CMRA link at http://www.ecmra.mil.

5.12.2 Trafficking in Persons.

5.12.2.1 The Contractor shall comply with FAR 52.222-50, Combating Trafficking in Persons. Additional information about Trafficking in Persons is available at the Department of State’s Office to Monitor and Combat Trafficking in Persons site at: http://www.state.gov/j/tip.

5.12.2.2 In accordance with the Department of Defense COR Handbook section on Combating Trafficking in Persons, the COR(s) must inform the PCO if the Contractor/subcontractor and/or Contractor/subcontractor personnel fail to comply with the requirements of FAR 52.222.50. The PCO must convey the information to DoD Combat Trafficking in Persons (CTIP) Law Enforcement and Support / Office of Under Secretary of Defense (OUSD) Personnel and Readiness (P&R) Defense Human Resources Activity (DHRA).

5.13 Procedure for Invoicing/Payment/Acceptance.

5.13.1 The Contractor shall submit/process payment requests and receipt/acceptance documents via iRAPT (formerly WAWF).

6.0 APPENDIX A:

http://www.ecmra.mil/ http://www.state.gov/j/tip

Name of Publication Sections That Apply

Date of Publication Title of Publication

MIL-STD-1530D Entire Document 13 Oct 2016 AIRCRAFT STRUCTURAL INTEGRITY

PROGRAM (ASIP)

AFI 63-140 Entire Document 7 Apr 2014 AIRCRAFT STRUCTURAL INTEGRITY

PROGRAM

AFI 61-201 Entire Document 29 Jan 2016 DISSEMINATING SCIENTIFIC AND

TECHNICAL INFORMATION

DoDD 5230.24 Entire Document Change 2 – 1 Nov 2017

Distribution Statements on Technical Documents

DoDD 5230.25 Entire Document Change 1 – 18 Aug 1995

Withholding of Unclassified Technical Data from Public Disclosure

T.O. 00-25-107 Entire Document 1 Oct 2015 MAINTENANCE ASSISTANCE

T.O. 1C-130A-3 Entire Document Change 58 – 1 Dec 2017

STRUCTURAL REPAIR

INSTRUCTIONS

T.O. 1C-130A-6 Entire Document Change 11 – 1 Feb 2018

SCHEDULED INSPECTION AND

MAINTENANCE REQUIREMENTS

T.O. 1C-130A-23 Entire Document Change 10 – 15 Feb 2018

SYSTEM PECULIAR CORROSION

CONTROL

T.O. 1C-130A-36 Entire Document Change 3 – 15 Aug 2017

NONDESTRUCTIVE INSPECTION

PROCEDURES

T.O. 1C-130J-3 Entire Document Change 25 – 1 Jan 2018

STRUCTURAL REPAIR MANUAL

T.O. 1C-130J-6 Entire Document 1 Jan 2018

AIRCRAFT SCHEDULED INSPECTION

AND MAINTENANCE

REQUIREMENTS

T.O. 1C-130J-23 Entire Document Change 23 – 1 Jan 2018

CORROSION PREVENTION AND

CONTROL MANUAL

T.O. 1C-130J-36 Entire Document Change 26 – 1 Jan 2018

NONDESTRUCTIVE INSPECTION

MANUAL

SAF Policy Letter (For contractors working on

RAFB)

Entire Document 11 Dec 06

Conformance with AF Environmental Management System (EMS) Requirements for Contract Performed on AF Installations

AFI 10-403 Paragraph 1.9.1.33.2 23 Feb 2018 DEPLOYMENT PLANNING AND

EXECUTION

DFARS 252.237-

7023(a) Entire Document 26 Jun 2015 Continuation of Essential Contractor

Services FAR 23.404 Paragraph “b” 18 May 12 Agency Affirmative Procurement Program FAR 52.245 -1 Jan 2017 GOVERNMENT PROPERTY

FAR 52.246 -4

-5

Aug 1996 Apr 1984 INSPECTION OF SERVICES

OSHA Public Law 91- 596 Entire Document 1 Jan 2004 Occupational Safety and Health Act

(OSHA) of 1970 Occupational Safety

And Health Standards Part 1910 1 Jan 2004 Occupational Safety and Health Act (OSHA) of 1970

SAF/AQ Memo Entire Document 13 Nov

Contractor Manpower Reporting Requirements

M-16-19 Entire Document 1 Aug 2016 Data Center Optimization Initiative

(DCOI)