PWS 11-730GFEA-43 C5 ERR Program Final.pdf

GRSEA POC: Amy Eddy PWS 11-730GFEA-43 GRSA POC: Jessica Holliday Revision: Basic GRSKA POC: LaToya Brown Date: 22 March 2012

FILE NUMBER: FD2060-12-31240/REV 0 Page 1 of 22

Performance-based Work Statement (PWS)

For C-5

Engineering Requirements Review (ERR) Program

1.0 Description of Services

The Warner Robins Air Logistics Center (WR-ALC) is the primary Air Force (AF) depot responsible for multiple aircraft and subsystems. The ERR program is comprised of disciplined processes and procedures, organizational, and systematic operating elements designed to improve aircraft repair productivity, with the overall goal of increasing aircraft mission capability, reliability and maintainability. The program includes processes that streamline the industrial and maintenance support practices for aircraft repair, provide improved visibility of recurring repair issues for tail numbers in the C-5 fleet, identify solutions to correct aircraft deficiencies, provide accurate forecasting of maintenance, provide support for the annual 20% Maintenance Requirements Supportability Process (MRSP) review and establish accurate performance metrics for quality, schedule and cost. This effort will provide engineering services and integrated solutions for C-5 ERR goals.

1.1 Scope

The overall objective of this PWS is the sustainment of a maintenance program in support of the overall C-5 scheduled maintenance goals consistent with MSG-3 philosophy. The foundational elements of the program include: ERR engineering support, associated database sustainment, maintenance data analysis and Standard Visual Work Card (SVWC) sustainment. These sustaining engineering services shall provide the C-5 organization with engineering and analysis solutions that improve the sustainment of the aircraft. Together these services shall support fleet-wide reliability and availability requirements.

The ERR support shall draw from the Federal Aviation Administration (FAA) Continuing Analysis and Surveillance System (CASS) and Continuing Analysis Maintenance Program (CAMP) regulations to provide a continuous, structured analysis and surveillance process that monitors fleet health, evaluates the effectiveness of the scheduled maintenance program, and identifies necessary changes using a 20% annual review. The ERR support shall include input for the implementation and sustainment of processes, procedures, data analysis, and software tools for C-5 aircraft sustainment and reliability improvement. This support involves continuously analyzing data requirements, providing support of existing applications, updating all supporting documentation, conducting application testing to ensure optimal performance, and maintaining Certification and Accreditation (C&A) and compliance with the Enterprise Information Technology Data Repository (EITDR). These activities shall be integrated into a web-enabled IDE to streamline the complex logistics challenges of supporting fleet readiness.

The sustainment of SVWCs shall facilitate documenting scheduled maintenance and other tasks using modern commercial best practice format and content to maximize maintainer on-aircraft

GRSKA POC: LaToya Brown Date: 22 March 2012

FILE NUMBER: FD2060-12-31240/REV 0 Page 2 of 22 time. These cards shall delineate task purpose, safety-related cautions and warnings, required parts, technical data and tools. To clarify and speed task accomplishment, the SVWCs shall extensively incorporate photographs and graphic illustrations while minimizing external Technical Order (TO) library references. Each scheduled maintenance task associated with each work card shall be maintained and updated throughout the ERR process.

2.0 Services Summary

Performance Objective PWS Paragraph(s)

Performance Threshold

Task review 4.8.1 Contractor shall ensure at least 95% of analyses are completed on time to support the annual 20% MRSP review in accordance with Contracting Officer’s Representative (COR) approved schedule. Remaining 5% shall be completed within a task specific timeline agreed upon by the COR.

Source of Supply Analysis

4.8.1.11.2 The results of Sources of Supply (SOS)

meetings shall be reviewed with the COR(s) within 20 business days of the end of each quarter. The results shall be 95% acceptable as presented. The remaining 5% of unacceptable results shall be corrected within five business days of notification.

System availability 4.8.2 Contractor shall ensure downtime attributed to software failures for any IDE application does not exceed one business day per any 30 calendar day period.

EITDR update 4.8.2.5 Contractor shall register and maintain all developed software in EITDR. Contractor shall update EITDR to reflect any upgrades or changes in application functionality within three business days of completion of each project. Contractor shall provide documentation to COR(s) on registered systems in EITDR.

Software application compliance with C&A

4.8.2.5 Contractor shall ensure all software applications

remain compliant with C&A guidelines 100% of the time.

Maintenance of Authority to Connect (ATC) and Authority to Operate

(ATO)

4.8.2.5 Contractor shall ensure ATC/ATO is

maintained with no lapse in authority.

Mishap Notification and Reporting

4.13.2 No more than one instance of late mishap

notification per year.

GRSKA POC: LaToya Brown Date: 22 March 2012

FILE NUMBER: FD2060-12-31240/REV 0 Page 3 of 22

Conduct acceptable Contractor Safety Program

4.13.3 No more than two Class C mishaps per contract

year. Zero Class A or B mishaps.

3.0 Government Property and Services

3.1 Federal Acquisition Regulation (FAR) 45.101, Government Property Definitions

3.1.1 “Government property” means all property owned or leased to the Government or acquired by the Government under the terms of the contract. It includes both Government-furnished property and contractor-acquired property.

3.1.2 “Contractor-acquired property” … means property acquired or otherwise provided by the contractor for performing a contract and to which the Government has title.

3.2 Contractor Responsibility

The Contractor shall be responsible and liable for any Government property in their possession in accordance with FAR Part 45, Government Property, FAR 52.245, and Defense Federal Acquisition Regulation Supplement (DFARS), Part 245, Government Property.

3.3 Subject to availability, the Government will provide access to work-card software (i.e.

Techsight/X and Serna), legacy data systems, facilities, key personnel, computers and monitors, printers, copy machines, shredders, fax machines, required office space, supplies/equipment, manuals, and regulations, comparable to that provided Government employees for the accomplishment of the objectives/tasks of this PWS if the Contractor is required to be collocated on Robins Air Force Base (RAFB) to complete day-to-day tasks. Additionally, the Government will provide Class A phone lines.

3.4 The Government will provide access to aircraft, as required, in order for the Contractor to perform analysis. Aircraft will be made available based on fleet requirements and with the approval of Air Mobility Command (AMC), Air Force Reserve Command (AFRC), Air National Guard Command (ANG), and 402nd Maintenance Wing (402 MXW).

3.5 The Government will provide access to components/systems, as required, in order for the Contractor to perform analysis. Components/systems will be made available based on fleet requirements and with the approval of the responsible organization at WR-ALC, Ogden Air Logistic Center (OO-ALC), Oklahoma Air Logistic Center (OC-ALC) and any other Government agency.

3.6 DFARS 252.245-7002, Reporting Loss of Government Property

3.6.1 Definitions

GRSKA POC: LaToya Brown Date: 22 March 2012

FILE NUMBER: FD2060-12-31240/REV 0 Page 4 of 22

3.6.1.1 “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-

(1) Items that cannot be found after a reasonable search;

(2) Theft;

(3) Damage resulting in unexpected harm to property requiring repair to restore the item to usable condition; or

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

3.6.1.2 “Unit acquisition cost” means-

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

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

3.6.2 Reporting loss of Government property

(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.

(2) Unless otherwise provided for in this contract, the requirements of paragraph (b)(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) The Contractor shall report losses of Government property outside normal process variation, e.g., losses due to -

(i) Theft;

(ii) Inadequate storage;

(iii) Lack of physical security; or

(iv) “Acts of God”.

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

3.7 Return of Government Property

All Government Furnished Property (GFP) remains the property of the Government and shall be returned to the Government upon completion of the contract or as directed by the COR(s). All Contractor Acquired Property (CAP) becomes the property of the Government and shall be

GRSKA POC: LaToya Brown Date: 22 March 2012

FILE NUMBER: FD2060-12-31240/REV 0 Page 5 of 22 returned to the Government upon completion of the contract or as directed by the COR(s). Any material generated under the contract becomes the property of Government and shall be returned to the Government upon completion of the contract or as directed by the COR(s).

3.8 Government Information Systems Access and Data

3.8.1 The Government will provide Contractor personnel access to systems required to perform tasks under the contract. The Contractor shall ensure Contractor personnel who require access to a Government Automated Information System (AIS) have a Department of Defense (DoD) National Agency Check Plus Written Inquiries (DNACI) conducted in accordance with DoD 5200.2-R, Personnel Security Program. The Government will provide system access subject to approval of the Department of Defense (DD) Form 2875, System Authorization Access Request (SAAR). Upon completion/termination of the contract or transfer/termination of Contractor personnel, applicable system accounts will be closed.

3.8.2 The Government will provide access to Government data systems and data archived by the C-5 organization. The Contractor can obtain Point of Contact (POC) information, for any system listed below, from the COR(s). The Contractor shall collect and collate data from the following systems and other systems as necessary:

• G081 (Core Automated Maintenance System for Transport Aircraft)

• REMIS (Reliability & Maintainability Information System)

• GCSS (Global Combat Support System)

• PDMSS (Program Depot Maintenance Schedule System)

• EDW (Enterprise Data Warehouse) / (AFDS) Air Force Data Services as available

• G021 (Quality Deficiency Reports Repository)

• ROCIT (Role Oriented Consolidation Information Tool)

• PDMSS (Programmed Depot Maintenance Scheduling System)

• Techsight/X and Serna technical data software

• EIDTR (Enterprise Information Technology Data Repository)

• AFDS (Air Force Data Services)

• MIMS (Mission Impaired Capability Awaiting Parts (MICAP) Information Management

System)

• C-5 Programmed Depot Maintenance (PDM) Non-Destructive Inspection (NDI)

Database

• 202 Database (PDM Initiated Engineering Assistance Request)

• 107 Database (Field Initiated Engineering Assistance Request)

• 339 Database (Defense Logistics Agency (DLA) Initiated Engineering Assistance

Request)

• PDM CANN (Cannibalization) Database

• Wholesale and Retail Supply Systems

• MADARS (Malfunction Detection, Analysis and Recording System)

• Aircraft Health Management System (AHMS)

GRSKA POC: LaToya Brown Date: 22 March 2012

FILE NUMBER: FD2060-12-31240/REV 0 Page 6 of 22

3.8.3 Wide Area Workflow (WAWF)

In accordance with DFARS 252.232-7003, Electronic Submission of Payment Requests, the Contractor shall submit/process payment requests (invoices, Receiving Reports or combos), Receipt/Acceptance documents, and Contract Data Requirements List (CDRL) deliverables via WAWF. Contractor personnel shall register to access WAWF-Receipt and Acceptance (WAWF-RA) at https://wawf.eb.mil and designate an Electronic Business Point of Contact (EB POC) in the Central Contractor Registration (CCR) site at http://www.ccr.gov no later than ten calendar days after award of the contract.

4.0 General Information

4.1 Program Management

4.1.1 The Contractor shall assign a Program Manager (PM) to plan and execute the overall contract; however, each individual objective area shall have a project lead assigned for the day-to-day execution of tasks as required.

4.1.2 The Contractor PM assigned shall:

• Understand in detail the contractual requirements, terms and conditions of the task.

• Assign, track progress and review performance of tasks on a periodic basis.

• Be the single POC for the Government.

• Review all deliverables for accuracy and completeness.

• Hold a Kick-Off Meeting (KOM) once contract is awarded.

• Hold Program Management Reviews (PMRs) as required.

4.2 Quality Assurance (QA) and Control

The Contractor shall have a Quality Assurance (QA) and Control Program that is in accordance with or meets the intent of International Organization for Standardization (ISO) 9001:2000, Quality Management Systems – Requirements.

4.3 Procedures and Control

4.3.1 If Unsatisfactory Report (UR) exhibits or other AF items associated with failed or malfunctioning equipment are needed for analysis, they will be forwarded to the Contractor, if available, and if determined to be in the best interest of the Government.

4.3.2 In the accomplishment of the objectives/tasks of this PWS, attention shall be given to all aspects of safety, particularly system safety. The Contractor shall identify all Category One (CAT I) and Category Two (CAT II) hazard levels (as defined in paragraph A.4.4.3.2.1 of Military Standard (MIL-STD)-882D, Standard Practice for System Safety) and submit recommendations for corrections of the safety deficiencies.

GRSKA POC: LaToya Brown Date: 22 March 2012

FILE NUMBER: FD2060-12-31240/REV 0 Page 7 of 22

4.3.3 The Contractor may be required to purchase equipment and/or material for the accomplishment of the objectives/tasks of this PWS. The requirement for purchases and availability of funds must be identified and approved by the PCO, with COR coordination, prior to purchase.

4.4 Continuation of Mission Essential Services During Crises

4.4.1 DFARS 252.237-7023(a), Continuation of Essential Contractor Services / Definitions

4.4.1.1 In accordance with DFARS 237-7023(a)(1), “ ‘Essential contractor service’ means a service provided by a firm or individual under contract to DoD to support mission-essential functions, such as support of vital systems, … associated support activities, … and similar services provided to foreign military sales customers under the Security Assistance Program.

Services are essential if the effectiveness of defense systems or operations has the potential to be seriously impaired by the interruption of these services, as determined by the appropriate functional commander or civilian equivalent.”

4.4.1.2 In accordance with DFARS 237-7023(a)(2), “ ‘Mission-essential functions’ means those organizational activities that must be performed under all circumstances to achieve DoD component missions or responsibilities, as determined by the appropriate functional commander or civilian equivalent. Failure to perform or sustain these functions would significantly affect DoD’s ability to provide vital services or exercise authority, direction, and control.”

4.4.2 Designation of Services as Mission-Essential

In accordance with Air Force Instruction (AFI) 10-403, Deployment Planning and Execution, 1.6.1.25, DFARS 237-7023(a)(1), and DFARS 237-7023(a)(2), the Functional Commander (FC) or civilian equivalent has determined that these services are not mission-essential and will not continue in the event of a crisis.

4.5 Inspection of Services

4.5.1 In accordance with FAR 52.246-4, Inspection of Services - Fixed-Price and FAR 52.246-5, Inspection of Services – Cost Reimbursement, the Contractor shall maintain a quality inspection process acceptable to the Government.

4.5.2 In accordance with FAR 52.246-4, the Government reserves the right to inspect Contractor performance as long as it does not cause undue delay to delivery of services.

4.6 Experience

Successful accomplishment of the objectives/tasks of this PWS shall require knowledge and understanding of systems, programs and architectures related to the following areas:

• Project Management

GRSKA POC: LaToya Brown Date: 22 March 2012

FILE NUMBER: FD2060-12-31240/REV 0 Page 8 of 22

• Information Technology (IT) and Networking compliant with D0D 8570

• Web Design, Testing, and Sustainment

• Database Design

• Configuration Management

• Centralized Work Control and Standard Daily Work

• Technical Data Quality Assurance

• Knowledge of C-5 Weapon System and Processes

• Engineering Analysis using AF Form 202, 107, G081, REMIS, ROCIT and PDMSS

• Root Cause / Reliability Analysis

• Maintenance Data Collection and Correction

• Data Cleansing Techniques

• Standard Visual Work Cards for Scheduled Maintenance

• Systems Safety Analysis per MIL-STD-882D

• Conditioned-Based Maintenance (CBM and CBM+)

• MSG-3 Maintenance Program Capabilities on aged military and commercial aircraft

• Commercial-based aircraft maintenance work cards and Serna authoring software

• Technical Order development complying with Air Force regulations

• Developing technical data using ATA standard conventions

• Authoring S1000D compliant technical data

• Techsight technical data software suite

• Maintenance and logistics expertise with military strategic airlift or similar commercial aircraft

• Enterprise Information Technology Data Repository (EITDR)

• C&A packages and processes using AF applications

4.7 Travel

Contractor personnel shall be required to travel to accomplish tasks as directed by the COR(s).

In conjunction with the required engineering services, Contractor personnel may be required to travel to an Air Force Base (AFB) where aircraft are located or other locations. All travel will be within the Continental United States (CONUS). Travel may be required to discuss problems, conduct evaluations, obtain background information, observe or conduct tests, ensure compatibility of configuration changes and other integration services. The number of trips and Contractor personnel traveling shall be kept to the minimum required to accomplish tasks.

Travel requests for Contractor personnel shall be submitted to the COR(s) for coordination and to the Procuring Contacting Officer (PCO) for approval a minimum of five business days prior to travel being accomplished. Travel shall be conducted and expenses shall be limited in accordance with FAR 31.205-46, Travel costs.

4.8 Requirements

4.8.1 ERR

For maintenance analysis, the Contractor shall ensure there is no more than a 5% deviation from the scheduled maintenance task review, performed by the Contractor each month to support the

GRSKA POC: LaToya Brown Date: 22 March 2012

FILE NUMBER: FD2060-12-31240/REV 0 Page 9 of 22 annual 20% MRSP review of the approximately 2765 tasks in the C-5 maintenance program.

The Contractor shall ensure at least 95% of analyses are completed on time in accordance with COR approved schedule. Remaining 5% shall be completed within a task specific timeline agreed upon by the COR. (CDRL A002, DI-MISC-80711A/T, Scientific and Technical Reports)

4.8.1.1 ERR Support

The implementation and sustainment of an ERR Program requires extensive communication channels to be in place, as well as, flexible processes and infrastructures to support the various stages of current maintenance data analysis and reviews (of Structural Significant Items (SSI’s), Other Structural Items (OSI’s), Maintenance Significant Items (MSI’s) and Zonal tasks as they relate to both structures and systems analysis consistent with MSG-3 philosophy).The Contractor shall support the C-5 ERR by investigating reliability deficiencies that are identified throughout the fleet. The contractor shall maintain Operational Safety, Suitability and Effectiveness (OSS&E) in accordance with WR-ALC/GRS requirements while performing analysis. Program support includes implementing a robust reliability program for the C-5 aircraft by utilizing appropriate tools and processes to improve overall fleet reliability, implementing best practices from the commercial aviation industry, and using current DoD guidelines and industry philosophies to implement and sustain scheduled maintenance process solutions for the fleet. Program support requires the Contractor maintain membership with Airlines for America (A4A), formerly known as Air Transport Association of America (ATA) in order to ensure timely updates to the MSG-3 logic flow.

The ERR shall: (1) Ensure maintenance tasks are accomplishing their primary intent and the assigned interval is appropriate through analysis of maintenance data and associated task tracking numbers; (2) Revise work cards to comply with TO revisions; (3) Assemble business cases for proposed maintenance program changes; (4) Manage the approval process for proposed maintenance program changes using the Technical Review Board concepts; (5) Provide oversight to ensure expeditious processing of TO changes; and (6) Accomplish other tasks within the scope of this requirement as determined. (CDRL A002, DI-MISC-80711A/T, Scientific and Technical Reports)

4.8.1.2 Functional Systems Analysis

The Contractor shall identify problems and/or deficiencies that require configuration or procedural changes and evaluate performance improvements to ensure the functional systems meet operational requirements. The Contractor shall perform activities including, but not limited to, analysis of aircraft systems to establish weapon system baselines, functional and physical configuration audits, analysis and support of AFI 63-101, Life Cycle Systems Engineering. The contractor shall maintain OSS&E requirements while performing analysis. All engineering analysis affecting OSS&E shall be accomplished by appropriately accredited personnel in possession of Accreditation Board for Engineering and Technology (ABET) accredited degrees, state issued Engineering-in-Training certifications and/or state issued Professional Engineer license. (CDRL A002, DI-MISC-80711A/T, Scientific and Technical Reports)

4.8.1.3 Product Improvement Analysis

GRSKA POC: LaToya Brown Date: 22 March 2012

FILE NUMBER: FD2060-12-31240/REV 0 Page 10 of 22

The Contractor shall perform preliminary and in-depth analysis for all Work Unit Codes (WUCs) that are identified as poor performer in order to determine the need for product improvements and recommend further engineering analysis and resolutions that can be implemented for fleet-wide sustainment and/or be implemented during the PDM process. (CDRL A002, DI-MISC- 80711A/T, Scientific and Technical Reports)

4.8.1.4 Maintenance Data Analysis

The Contractor shall identify, collect, and analyze C-5 diagnostic, reliability and maintainability data, engineering disposition data, and deficiency reporting data from various sources with the goal of improving mission capability of the fleet. The Contractor shall perform these activities in accordance with FMECA requirements per Service Acquisition Executive Aerospace Information Report 4845 (SAE AIR4845) and system safety and hazard analysis per MIL-STD- 882D. (CDRL A002, DI-MISC-80711A/T, Scientific and Technical Reports)

4.8.1.5 Work Card Sustainment

The Contractor shall deploy and sustain 1C-5A-6 inspection and PDM work cards using commercial concepts and best practices including the use of graphics and specific job instructions. The work cards shall leverage the sample prototype work cards (based on MIL- STD-38784 requirements) previously developed for 1C-5A-6WC-5 isochronal inspections using Government-provided software (Framemaker version 7.2 or higher) in an 8.5” X 11” page format. The PDM work cards shall interface with Air Force Materiel Command (AFMC) 173 Cards. All TO references contained within work cards shall be recorded so that future TO updates and revisions can be incorporated into the work cards. (CDRL A001, DI-MGMT- 80368A/T, Status Report)

4.8.1.6 PDM Bill of Materials (BOM) Update

As required, the Contractor shall update the Bill of Materials (BOM) to support the maintenance program implementation. (CDRL A001, DI-MGMT-80368A/T, Status Report)

4.8.1.7 Integration with Maintenance Requirements Review Board (MRRB)

The Contractor shall integrate and update the maintenance-derived tasks and interval recommendations to be incorporated into the MRRB Brochure. The Contractor shall provide all technical data necessary to facilitate transition and incorporate the maintenance program into the MRRB Brochure. (CDRL A001, DI-MGMT-80368A/T, Status Report)

4.8.1.8 Field and PDM Maintenance Training Program

The Contractor shall integrate, update, and sustain a comprehensive training program to ensure successful implementation and acceptance of the program. The ERR program is a “task-oriented” method of maintenance, resulting in a different maintenance philosophy and new

GRSKA POC: LaToya Brown Date: 22 March 2012

FILE NUMBER: FD2060-12-31240/REV 0 Page 11 of 22 inspection techniques (i.e., Detailed Visual Inspection (DVI), General Visual Inspection (GVI), and zonal inspections).

4.8.1.9 Collaborative Engineering Capability

The Contractor shall establish a collaborative capability that supports visual and voice communication among the C-5 Regional Isochronical (RISO) community. The Contractor shall analyze a concept of operations, identify and procure the necessary equipment, and implement a “proof-of-concept” prototype. The Contractor shall ensure the capability facilitates daily collaborative meetings between the RISO and C-5 Engineering, and facilitates improvements in C-5 Form 107 engineering dispositions. (CDRL A002, DI-MISC-80711A/T, Scientific and Technical Reports)

4.8.1.10 CBM Process

The Contractor shall establish a process to facilitate CBM actions in conjunction with RISO activities. The Contractor shall ensure the processes and tools provide the ability to accurately plan and document tail number-specific maintenance tasks before the aircraft arrives at the RISO for maintenance.

4.8.1.11 Aircraft Availability and Supplier Support

4.8.1.11.1 The Contractor shall possess skills to analyze C-5 parts support provided by various suppliers. Suppliers include all Air Force Global Logistics Support Center (GLSC) Sources of Supply (SoS) locations, the applicable DLA Support Centers, as well as, major modification program prime contractors. The Contractor shall lead or support supplier support meetings, as well as, provide status briefings to the C-5 Galaxy Enterprise leadership. The Contractor shall select items to be briefed by monitoring selected metric criteria and impact to the C-5 fleet Aircraft Availability thresholds. (CDRL A001, DI-MGMT-80368A/T, Status Report)

4.8.1.11.2 The Contractor shall identify items from SoS parts meetings affecting Aircraft Availability, major modification programs, and the MRSP. The results shall be maintained by the Contractor and reviewed with the COR(s), and corrections made as required. (CDRL A001, DI-MGMT-80368A/T, Status Report)

4.8.1.11.3 The Contractor shall analyze new parts requirements for the MRSP team. The Contractor shall determine whether new requirements part lists are supportable or when they are predicted to be supportable. The Contractor shall analyze major modification program contractor supply support and management data trends and watch items. The Contractor shall provide analysis/status briefings to C-5 Enterprise leadership. (CDRL A001, DI-MGMT- 80368A/T, Status Report)

4.8.1.12 Configuration Management

The Contractor shall assist the Chief Engineer in maintaining configuration management per DoD 5000.2-R, Mandatory Procedures for Major Defense Acquisition Programs (MDAPS) and

GRSKA POC: LaToya Brown Date: 22 March 2012

FILE NUMBER: FD2060-12-31240/REV 0 Page 12 of 22

Major Automated Information System (MAIS) Acquisition Programs, and AFI 63-1201, Life Cycle Systems Engineering. The Contractor shall perform activities including, but not limited to, analysis of aircraft systems to establish weapon system baselines, functional and physical configuration audits, analysis and support of the Configuration Control Board (CCB).

4.8.2 IDE Sustainment

For customer disruptions due to software failures, system downtime attributed to software failures or any IDE application shall not exceed one business day per any 30 calendar day period.

For customer support, the Contractor shall respond to submitted customer requests within three business days of requirement notification. For EITDR registration, the Contractor shall provide documentation to the COR(s) on registered systems in the EITDR within three business days of completion of each project. For C&A compliance, the Contractor shall comply with AF and WR-ALC mandate regarding connectivity of systems and applications to network 100% of the time. Certification for 8570-M Information Assurance Management -3 (IAM - 3)/Information Assurance Technical -3 (IAT -3) Certified Information Systems Security Professional (CISSP) is required.

4.8.2.1 Data Requirements Analysis

The Contractor shall enhance, update, and sustain the C-5 maintenance database that contains all Inspection and Maintenance (I&M) requirements for structures, systems and zonal applicability across all C-5 inspection zones, consistent with MSG-3 philosophy. The C-5 Maintenance Database shall be used throughout the life of the contract to update maintenance tasks and provide decision support data for each requirement including Force Structural Maintenance Program (FSMP) references, maintenance failure statistics, reliability data, maintainability factors and economic factors. Database fields shall include standard work card data, as well as, current approved interval, Failure Effect Category (FEC), recommended threshold intervals for each applicable FEC and decision support data references. Project details in terms of technical risk, cost, and schedule shall be provided and reviewed during PMRs to determine whether any priority changes/modifications/additions may be required to meet war fighter needs. (CDRL A002, DI-MISC-80711A/T, Scientific and Technical Reports)

4.8.2.2 Support of Existing Applications

Maximum care shall be taken to avoid duplication of effort in support and deployment of applications to the IDE through the use of state-of-the-art Information Technology (IT) techniques and tool sets. The Contractor shall ensure all systems modified or upgraded under the contract, are entered into the EITDR. The Contractor shall provide documentation, on registered systems in the EITDR, to the COR(s) within three business days of completion of each project.

The Contractor shall provide timely support of and maintenance of all applications listed in Table 1 below. These applications may be modified to provide additional capability based upon customer feedback or receipt of additional requirements.

Table 1- Existing C-5 Applications

GRSKA POC: LaToya Brown Date: 22 March 2012

FILE NUMBER: FD2060-12-31240/REV 0 Page 13 of 22

Program Name Purpose Aircraft Integrated Data Environment (AIDE) Framework

Application framework to support C-5 applications

Form 107 C-5 Form 107 System

C-5 MICAP

Information Management System

(MIMS)

C-5 Mission Impaired Capability Awaiting Parts (MICAP) Information Management System

Techsight/X C-5 Maintenance Workcard Authoring System

4.8.2.2.1 Application Requirements and Analysis

The Contractor shall perform requirements analysis to gather the system-level requirements for each system integration project assigned by the customer. The analysis should be accomplished through customer feedback or other methods of communication. The system-level requirements shall be captured in the System Requirements Specification (SRS). (CDRL A002, DI-MISC- 80711A/T, Scientific and Technical Reports)

4.8.2.2.2 System Design

Based upon analysis, the Contractor shall identify changes required and provide initial system design methodology to the customer to ensure the design complies with and fulfills the requirement.

4.8.2.3 Supporting Documentation

All required upgrades shall be appropriately documented and maintained within the program.

Documentation shall be supplied to the customer upon request. A baseline version of the application shall be maintained for configuration management purposes.

4.8.2.4 Application Testing

The Contractor shall test the functionality of each system integration application based on criteria established in the SRS. Necessary modifications and corrections identified during verification testing shall be documented and incorporated into the system prior to proceeding to system deployment. The Contractor shall deploy applications to the web production server and database server, as applicable.

4.8.2.5 Application C&A and the EITDR

The Contractor shall register and maintain all developed software in the EITDR. The Contractor shall update the EITDR to reflect any upgrades or changes in application functionality within three business days of completion of each project. The Contractor shall provide documentation

GRSKA POC: LaToya Brown Date: 22 March 2012

FILE NUMBER: FD2060-12-31240/REV 0 Page 14 of 22 to the COR(s) on registered systems in the EITDR. (CDRL A001, DI-MGMT-80368A/T, Status Report)

The Contractor shall ensure all software applications remain compliant with C&A guidelines 100% of the time. The Contractor shall establish supporting documentation and provide application configuration details in the support of the DoD Information Assurance (IA) C&A process and maintenance of the Authority to Connect/Authority to Operate (ATC/ATO). The Contractor shall ensure ATC/ATO is maintained with no lapse in authority. The Contractor shall comply with the AF and WR-ALC mandate regarding connectivity of systems and applications to the network 100% of the time.

4.9 Data Deliverables

4.9.1 The Contractor shall submit a monthly status report. The report shall detail status/progress, expenditures, travel costs, performance, and schedule of all analysis performed in the previous month. (CDRL A001, DI-MGMT-80368A/T, Status Report)

4.9.2 The Contractor shall submit monthly engineering reports to document prior month services, schedule and financials. (CDRL A002, DI-MISC-80711A/T, Scientific and Technical Reports)

4.9.3 The Contractor shall submit a Safety and Health Plan for review and acceptance by the Government Safety Office. (CDRL A003, DI-ENV-81375, Environmental Health and Safety Plan (HSP))

4.9.4 The Contractor shall submit a Quality Program Plan (QPP). The plan shall submit 15 days after contract award and as changes occur. (CDRL A004, DI-QCIC-81722, Quality Program Plan (QPP) - Contractor’s Quality Control Plan)

4.9.5 The Contractor shall submit Accident/Incident Reports on ALL mishaps, damage to DoD property, and employee injury, to the Installation Safety Office telephonically within four (4) hours after initial notification. Written report shall be submitted within three (3) calendar days of mishap. (CDRL A005, DI-SAFT-81563, Accident/Incident Report - Mishap Notification and Reporting)

4.9.6 The contractor shall provide to the government, on an annual basis, TCIR/DART rates or injury and illness rates for the Standard Industrial Classification (SIC) code or the North American Industrial Classification Systems (NAICS) code for the applicable industry.

(CDRL A006, DI-SAFT-81563/T, Accident/Incident Report - TICR/DART (Total Incident Case Rate/Days Away Restricted Transfer))

GRSKA POC: LaToya Brown Date: 22 March 2012

FILE NUMBER: FD2060-12-31240/REV 0 Page 15 of 22

4.10 Environmental Management System (EMS)

4.10.1 Executive Order (E.O.) 13423, Strengthening Federal Environmental, Energy, and Transportation Management, and E.O. 13514, Federal Leadership in Environment, Energy, and Economic Performance, establish the requirements for an Environmental Management System (EMS) and obligate federal agencies to implement sustainable practices.

4.10.2 In accordance with the Secretary of the Air Force (SAF) Policy Letter, Conformance with Air Force Environmental Management System (EMS) Requirements for Contracts Performed on Air Force Installations, dated 11 Dec 06, and the Air Force Material Command/Vice Commander (AFMC/CV) Policy Letter, Conformance with Air Force Environmental Management System (EMS) Requirements for contracts performed on Air Force installations, dated 1 Aug 07, Contractor personnel who perform work on any Air Force installation shall comply with the EMS requirements established by the installation.

4.10.3 Contractor personnel who perform work on WR-ALC shall complete EMS General Awareness Training prior to beginning work. EMS General Awareness Training will be provided by the 78th Civil Engineering Group Environmental Management Division (78 CEG/CEV). The prime Contractor shall ensure subcontractors comply with the EMS requirement. Contractor personnel can satisfy the EMS General Awareness Training requirement by any of the following means:

(1) With a Common Access Card (CAC), access the 78 CEG/CEV website, select EMS General Awareness Training, choose option 1.

https://geobase.robins.af.mil/emstraining/EMSTrainingOptions.aspx.

(2) Without a CAC, request a copy of RAFB EMS General Awareness Training via the 78 CEG/CEV Workflow Mailbox.

78ceg.cev.FrontOfc@robins.af.mil.

(3) If a company is ISO 14000 certified, Contractor personnel do not have to complete RAFB EMS General Awareness Training; however, the Contractor must provide documentation of ISO 14000 certification to the COR.

4.11 Green Procurement Program (GPP)

4.11.1 Under Secretary of Defense Memorandum, Establishment of the DoD Green Procurement Program, dated August 27, 2004, establishes the requirement for a GPP. The GPP requirement applies to all acquisitions including services. The GPP is a mandatory federal acquisition program that focuses on the purchase and use of environmentally-preferable products and services. In accordance with FAR 23.404, Agency Affirmative Procurement Programs, the GPP requires 100% of purchases of Environmental Protection Agency (EPA)-designated products, included in the Comprehensive Procurement Guidelines (CPG) list, contain recovered materials unless the item cannot be acquired competitively within a reasonable timeframe, meet appropriate performance standards, or be acquired at a reasonable price.

https://geobase.robins.af.mil/emstraining/EMSTrainingOptions.aspx� mailto:78ceg.cev.FrontOfc@robins.af.mil�

GRSKA POC: LaToya Brown Date: 22 March 2012

FILE NUMBER: FD2060-12-31240/REV 0 Page 16 of 22

4.11.2 The prime Contractor shall ensure subcontractors comply with the GPP requirement.

4.12 Security Requirements

4.12.1 Actual knowledge or generation of classified and/or sensitive information is not required for performance of the contract. Contractor personnel are required to comply with security requirements to preclude potential security incidents or violations including potential unauthorized disclosure or compromise of classified and/or sensitive information.

4.12.2 Security Regulations

The Contractor shall ensure personnel, information, system, facility, and international security requirements are met in accordance with DoD 5200.2-R, DoD 5200.22-M, National Industrial Security Program Operating Manual (NISPOM), AFI 31-101, Integrated Defense, and Robins Air Force Base Instruction (RAFBI) 31-101, Installation Security.

4.12.3 Security Clearance

4.12.3.1 Contractor personnel are not required to have a security clearance. Contractor personnel shall not be authorized access to classified and/or sensitive information and/or materials or be permitted to work on classified and/or sensitive projects and/or programs without a proper security clearance and a need-to-know.

4.12.3.2 The Contractor shall ensure Contractor personnel submit a United States (U.S.) Office of Personnel Management Standard Form 85P, Questionnaire For Public Trust Positions, (fingerprint card if available) to the Government Security Office.

4.12.4 Communications Security (COMSEC)

The Contractor shall use only secure communications methods and equipment to transmit or otherwise transfer classified and/or sensitive information in accordance with DoD 5200.22-M.

4.12.5 Access to Government System

The Government will provide Contractor personnel access to systems required to perform tasks under the contract. The Contractor shall ensure Contractor personnel who require access to a Government AIS have a DNACI conducted in accordance with DoD 5200.2-R. The Contractor shall ensure that Contractor personnel submit a United States (U.S.) Office of Personnel Management Standard Form 85P, Questionnaire For Public Trust Positions, (fingerprint card if available) to the Government Security Office. The Government will provide system access subject to approval of the DD Forms 2875. Upon completion/termination of the contract or transfer/termination of the Contractor personnel, the system accounts will be closed.

GRSKA POC: LaToya Brown Date: 22 March 2012

FILE NUMBER: FD2060-12-31240/REV 0 Page 17 of 22

4.12.6 External Certification Authority for Network Access

For Contractor personnel who require access to Government websites, but who do not work on a Government facility, the Contractor shall obtain a Public Key Infrastructure (PKI) Certificate from an External Certification Authority (ECA). As of the PWS date, Operational Research Consultants, Inc.; VeriSign, Inc.; and IdenTrust, Inc. are the three ECA vendors approved by the DoD. The COR(s) will provide a list of current DoD-approved ECA vendors upon Contractor request.

4.12.7 Access to Government Facility

4.12.7.1 The Contractor shall ensure Contractor personnel who require access to a Government facility comply with the security procedures of the facility.

4.12.7.2 If Contractor personnel require repeated access to a Government facility over the life of the contract, the Contractor shall ensure they complete, as applicable, a DD Form 1172-2 (Application for Department of Defense Common Access Card – DEERS Enrollment) to obtain a CAC, an AFMC Form 496 (Application for AFMC Identification Card) to obtain an AFMC Identification Card, or an AFMC Form 387 (Contractor ID Card/Badge) to obtain a Contractor Identification (ID) Card/Badge. The DD Form 1172-2, AFMC Form 496 or AFMC Form 387 shall be submitted to the PCO or as directed by the COR. Upon completion/termination of the contract/order or transfer/termination of the Contractor personnel, the CAC, AFMC Identification Card, or Contractor ID Card/Badge shall be returned to the PCO or as directed by the COR.

4.12.7.3 Access to RAFB

4.12.7.3.1 If Contractor personnel require a Contractor ID Badge, the Contractor’s Contract Administrator shall send a request for a Contractor ID Badge to the PCO for approval.

The request shall contain the following information:

Contractor's Company Name and Address Contractor Personnel's Name Contractor Personnel's Social Security Number Contractor Personnel's Date of Birth Contractor Personnel's Home Address Contractor Personnel's Work Phone Number Contract Number Contract Expiration Date

The PCO will forward the approved request to the 78 Security Forces Squadron for processing.

The PCO will notify the Contractor’s contract administrator by e-mail once the request has been submitted to security forces. The PCO will return the approved request to the Contractor’s contract administrator. The Contractor shall have 30 calendar days to comply with the PCO’s

GRSKA POC: LaToya Brown Date: 22 March 2012

FILE NUMBER: FD2060-12-31240/REV 0 Page 18 of 22 instructions. Upon completion/termination of the contract/order or transfer/termination of Contractor personnel, the Contractor ID badge shall be returned to the PCO.

4.12.7.3.2 CAC

If Contractor personnel require a CAC, the Contractor’s contract administrator shall send a DD Form 1172-2 to the COR(s) for approval. The COR(s) will return the approved DD Form 1172- 2 to the Contractor’s contract administrator. The Contractor shall have 30 calendar days to comply with the COR(s)’s instructions. The Contractor’s contract administrator shall forward the approved DD Form 1172-2 to the Government Trusted Agent (TA) for processing. The TA will notify the Contractor personnel by e-mail once the information is loaded in the Contractor Validation System (CVS). Contractor personnel shall have 30 calendar days to complete the application process. A User ID and temporary password will be provided. Contractor personnel shall have seven calendar days to initially log into the CVS system. Upon completion/termination of the contract/order or transfer/termination of the Contractor personnel, the CAC shall be returned to the TA.

4.12.8 Operations Security (OPSEC)

The Contractor shall ensure compliance with OPSEC requirements including procedures to protect classified and/or sensitive Government projects and/or programs. The Contractor shall ensure Contractor personnel who perform work at WR-ALC or another Government facility comply with the OPSEC procedures of the facility and participate in the locally administered OPSEC program.

4.12.9 Security Incident or Violation

The Contractor shall immediately notify the Government Security Office of any potential or actual security incidents or violations including potential or actual unauthorized disclosure or compromise of classified and/or sensitive, but unclassified, information.

4.13 SAFETY REQUIREMENTS: The contractor shall comply 100 percent of the time.

4.13.1 Contractor Compliance:

Contractors shall comply with Occupational Safety and Health Act (OSHA) Public Law 91-596, OSHA Standard 29 CFR 1910, and OSHA Standard 29 CFR 1926 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 and OSHA Standards 29 CFR 1926, 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. The Air Force is part of the OSHA Voluntary Protection Program (VPP). All shall familiarize themselves with the requirements of VPP. Information on http://www.osha.gov/pls/oshaweb/owasrch.search_form?p_doc_type=STANDARDS&p_toc_level=0�

GRSKA POC: LaToya Brown Date: 22 March 2012

FILE NUMBER: FD2060-12-31240/REV 0 Page 19 of 22 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.

4.13.2 Mishap Notification/ Mishap Investigation:

No more than two Class C mishaps per contract year and Zero Class A or B mishaps will be tolerated. The contractor shall telephonically notify the Safety office within four (4) hours of all mishaps or incidents to DoD property entrusted by this contract operation. No more than one instance of late mishap notification per calendar year is acceptable. Follow all other reporting requirements as identified on the DD1423, CDRL A005 for Accident/Incident Report (Mishap Notification & Reporting) Data Acquisition Document Number DI-SAFT-81563. 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.

4.13.3 Contractor Safety Program:

The contractor shall establish and maintain an acceptable safety program in accordance with their accepted Safety and Health Plan. All changes to the plan must also be submitted in writing and approved by the government via the DD 1423 Data Item Number A003 Data Acquisition Document Number DI-ENVR-81375 for Contractor’s Standard Operating Procedures (SOP) to receive the Contractor’s Safety and Health Plan Update.

4.13.4 Total Case Injury Rate (TCIR) and Days Away, Restricted and/or Transferred (DART) Rates:

The contractor shall provide to the government, on an annual basis, TCIR/DART rates or injury and illness rates for the Standard…