PERFORMANCE WORK STATEMENT (PWS) AIR COMBAT COMMAND

AIR OPERATIONS SQUADRON MISSION CONTROL CENTER

DRAFT Version 24 Jun 2026

TABLE OF CONTENTS PAGE

SECTION 1 – DESCRIPTION OF SERVICES 3

1.1. Scope of Work 3

1.2. Mission Control Center Management 3

1.3. Mission Planning 5

1.4. Mission Execution 6

1.5. Mission Reporting, Documentation and Administration 7

SECTION 2 – SERVICE SUMMARY/DELIVERABLES TABLE 9

2.1. Purpose 9

2.2. Components 9

2.3. Performance Threshold 9

2.4. Quality Assurance 10

2.5. Government Remedies 10

2.6. Quality Control 11

2.7. Deliverables Table 11

SECTION 3 – GOVERNMENT PROPERTY AND SERVICES 12

3.1. General Information 12

3.2. Government Furnished Property 12

3.3. Government Furnished Services 13

SECTION 4 – CONTRACTOR FURNISHED ITEMS AND SERVICES 14

SECTION 5 - GENERAL INFORMATION 15

5.1. Contractor Personnel 15

5.2. Employee Training and Certification 15

5.3. Contractor Force Protection Requirements 16

5.4. Hours of Operation 19

5.5. Special Qualifications 19

5.6. Qualifications Review 20

5.7. Performance of Services during Crisis Declared by the National Command Authority, Overseas Combatant Commander or Base Commander 20

5.8. Transition Plan 21

APPENDICES 22

A. Contractor Fulltime Equivalent Reporting 22 B. Government Furnished Property/Equipment Services 23 C. Acronym and Term Definitions 24 D. Applicable Publications and Forms 26

SECTION 1

DESCRIPTION OF SERVICES

1.1. SCOPE OF WORK. This contract provides for the operation of the Air Combat Command (ACC) Air Operations Squadron (AOS) Mission Control Center (MCC). The contractor shall provide all management, supervision, labor, training, tools, equipment, transportation, and mission materials required to operate the MCC as outlined in this Performance Work Statement (PWS) at Langley Air Force Base, Virginia and a designated alternate location. The contractor shall meet the standards specified within this PWS.

Services provided by the MCC directly support the AOS mission to provide safe and timely worldwide CORONET delivery of aircraft. During FY21-25, the AOS conducted an annual average of 236 missions to deliver 1,525 aircraft for the Department of War, as well as United States coalition and partner nation aircraft. The MCC reports directly to the AOS Commander and serves a mission-essential command and control function for continuous coordination and monitoring of world-wide aircraft deliveries. The MCC is required to coordinate with senior military leaders, national and international aviation agencies, enroute military support installations, Major Commands (MAJCOMs) and Service Components, and Delivery Control Officers (DCOs) to affect safe aircraft delivery. The MCC makes time-sensitive inputs concerning navigation planning, deployment timing, refueling support, and operational factors to support mission success. MCC contractor personnel, on-duty and those scheduled for duty, are considered mission essential.

For the purposes of this contract, the AOS Deputy (AOS/CD) and AOS Director of Staff (AOS/DS) are the AOS commander’s designated representatives. Collectively, these positions are referred to as the “AOS Top 3”.

1.2. MISSION CONTROL CENTER MANAGEMENT. The primary responsibilities for site management include scheduling personnel for 24/7 MCC operations, developing and administering a training program, ensuring standardized execution of MCC procedures, and liaising with government personnel. Specifically, the MCC will accomplish the below listed duties.

1.2.1. Prepare and publish a yearly schedule that is continuously updated to operate the 24-hour aircraft delivery operations command and control function to execute, monitor and expedite aircraft delivery missions that are associated with air refueling support as directed by the AOS Commander.

1.2.2. Ensure that Senior Controller work schedules do not exceed 12.5 hours of work (to include changeover briefings) within a 24-hour period, with a 24-hour rest period after a maximum of four consecutive work shifts. Additionally, Senior Controllers will not perform more than 15 shifts in a rolling 30-day period. The purpose of these restrictions is to afford adequate rest for Senior Controllers to facilitate proper decision making. Deviations to this work schedule must be approved by the AOS Top 3, in writing.

1.2.2.1. “On-call” duty status is considered as work hours for these scheduling parameters.

1.2.2.2. On-call is defined as a status in which the senior, and/or technical controllers, based on a lengthy period of mission inactivity, are not physically present in the MCC, but instead available on a mobile device and the senior controller is required to check the MCC Org Box.

1.2.2.3. During normal duty hours, defined as 0700-1700L Monday through Friday, the MCC will be physically manned regardless of mission activity. From 1700L-0700L M-F, and on weekends and holidays, the senior controller is authorized to transition the MCC to on-call status when there is a minimum of 16 hours between the last landing of the current Coronet mission and the next scheduled Coronet mission.

1.2.2.4. In addition, during normal duty hours, defined as 0700-1700L Monday through Friday, once mission activity has sufficiently diminished, the senior controller may place the technical controller in an on-call status.

1.2.2.5. After the initiation of on-call status, the scheduled controllers will transition back to normal in-place operations and re-open the MCC NLT 10.5 hours prior to the next scheduled departure, to enable prompt production of the L-10 winded products.

1.2.2.6. During on-call status, controllers must continue to accomplish performance tasks as outlined in the PWS. If the performance task requires a physical presence in the MCC, then the applicable controller(s) must transition from on-call status to normal operations within 60 minutes of notification. The senior controller is responsible to ensure that no mission degradation occurs as a result of being displaced from the Ryan Center.

1.2.2.7. When transitioning the MCC to on-call status, the senior controller must ensure applicable individuals are notified of the expected duration that the MCC will be on-call and provide instructions on how to contact the senior controller in case of unexpected mission changes.

1.2.2.8. Any circumstance outside of this section may be approved on a case-by-case basis by the AOS Top 3.

1.2.3. Ensure there is a sufficient number of augmentation (part-time) personnel to cover MCC mission requirements during scheduled or unscheduled Senior Controller absences.

Augmentees will be current and qualified per the Senior Controller training program and have at least one year of full-time senior controller experience in the AOS MCC. A waiver of the time-in-position requirement requires a written recommendation from the MCC site leader and approval by the AOS Commander. MCC augmentees will be annotated on the MCC qualification table for tracking purposes. Augmentees will be compensated at an hourly rate equivalent to full-time senior controllers.

1.2.4. Senior Controllers, to include augmentee(s) if employed, will maintain currency by performing a minimum of 12 shifts over a 3-month rolling period. To regain currency, personnel will perform Senior Controller duties for half a shift during mission execution, under the supervision of a Senior Controller that is designated in writing by the site leader to conduct recertification training.

1.2.5. The contractor shall fill a position that becomes vacant within 14 days. If senior controllers are required to perform greater than 15 shifts in a rolling 30-day period during the training and certification process of a new hire, the contractor will provide additional compensation to affected senior controllers, at a rate that is equivalent to the full-time rate.

1.2.6. Two Coronet Navigation planners will typically complete work assignments in five 8-hour shifts during the seven-day week, as needed by the ACC AOS. During surge operations, they will be expected to work up to 12-hour shifts in a 24-hour window, according to the needs of the situation, defined by the ACC AOS/CC or designated representatives.

1.2.6. The senior controller and Coronet navigation planners minimum hourly pay rate will be equivalent to a GS-13 Step 10, with locality pay, for Hampton, VA. The technical controller minimum hourly pay rate will be equivalent to a GS-11 Step 10, with locality pay, for Hampton, VA. This will include any cost-of-living increases that occur during the length of the contract.

1.2.7. AOS initiated changes that affect MCC operations or procedures will only be implemented via a formal policy letter to the site leader, signed by the AOS Commander.

1.3. MISSION PLANNING. The mission planning process begins five days prior to the first scheduled launch of a mission and continues until the production of winded flight products 10-hours prior to launch. Specifically, the MCC will accomplish the below listed duties.

1.3.1. Serve as the primary coordinating agency and point of contact for the agencies controlling tanker support.

1.3.2. Acquire all materials concerning a scheduled aircraft mission from AOS XP (Long-Range Plans and Nav Plans). Receive, review, and update physical and electronic mission folders for each scheduled aircraft delivery to ensure accurate mission disposition. Update mission folders during any update of these materials.

1.3.3. Coordinate, prepare, and disseminate Air Tasking Order (ATO) changes.

1.3.4. Transfer and update mission data to ADIS and make appropriate corrections when necessary.

1.3.5. Complete the Mission Folder setup sheet referenced in Appendix D upon initial transfer of the mission from XP to the MCC as well as the Mission Change setup sheet after any change that requires an updated ATO. Provide a copy of the mission setup sheet to the AOS Weather Flight.

1.3.6. The MCC will implement DCO requests for new mission profile(s) with Navigation Plans.

1.3.7. Post new profiles to appropriate NIPR/SIPR locations.

1.3.8. Assist DCOs to ensure that mission pre-launch coordination is accomplished according to current and subsequent ATO(s).

1.3.9. Order winded flight planning profiles using the current mission planning software to publish winded products at launch minus 48/24/10 hours. These products may be published up to 4 hours early in each case, but not later than the L-48/24/10 timeline.

1.3.10. With regard to the L-48/L-24 winded products, provide the DCO with the Key Results/MRB Log and Form 70. For the L-10 winded products, provide the DCO with the Key Results/MRB Log, Form 70, MRB Bingo document and the MRB Route document. Upon DCO request, produce an additional (“Immediate”) winded mission profile and provide all four winded products.

1.3.11. Analyze the L-10 products to validate DCO decisions. In addition, analyze the weather forecast for each MRB to determine suitability as well as the MRB Log to verify that the fuel available to divert to each MRB is adequate. Senior controllers must be trained and certified to access, reference, and operationally apply mission planning profile documents produced by AOS Plans (XP) and be prepared to recommend changes to Delivery Control Officers that affect safe and timely aircraft delivery. These products include, at a minimum, the Profile Master (Form 70), Key Results Summary, MRB Log 50/90, MRB Fuel Bingos, and MRB Routes.

1.3.12. Immediately notify the DCOs in writing or verbally when fuel consumption exceeds the 90% of the planning profile. Obtain DCO acknowledgement.

1.3.13. Receive and retain ALTRV APVLs, mission crew qualification documents, crew line up, flight duty period waivers, single ship waivers, night landing waivers and any other documentation required by the ATO and/or ACC AOS regulations. File all information/documents in the mission folder.

1.3.14. Review and validate all documents and information that are relevant to the mission Go/No-Go checklist and be prepared for the Go/No-Go brief following receipt and evaluation of the weather forecast at approximately six hours prior to launch.

1.3.15. Coronet navigation planners will serve as a supplement to the ACC AOS Navigation planning staff on a full-time basis to create accurate Navigation flight products for Coronet missions under typical lead-time conditions during the mission planning phase. Specific duties are listed at 5.1.4.

1.4. MISSION EXECUTION. The mission execution process begins upon publishing the L-10 winded products and continues until landing for each leg. Specifically, the MCC will accomplish the below listed duties.

1.4.1. Upon receipt, review and evaluate the controlling mission weather product to determine the suitability of the mission route, MRBs, departure and destination bases, and destination alternates. Document any identified mission weather issues in the respective mission folder.

1.4.2. Assemble information to support Go/No-Go launch decisions for scheduled missions.

Analyze and consider all launch decision factors IAW AFI 11-207 prior to the DCO Go/No-Go brief. Be prepared to support and validate a Go/No-Go decision based on factors such as weather forecasts, pilot weather categories, NOTAM impacts, fuel requirements, availability of MRBs and destination alternates, latest takeoff time (based on factors such as end of evening civil twilight, flight duty period, and ALTRV limitations), and tanker status.

1.4.3. Obtain and record primary and air spare aircraft landing information in ADIS. Update any aircrew and aircraft tail number substitutions provided by DCOs.

1.4.4. Prepare the Go/No-Go launch decision checklist referenced in Appendix D.

1.4.5. Input pre-launch checklist information into ADIS.

1.4.6. Accomplish the Go/No-Go brief. Only the Senior Controller may accomplish the Go/No- Go brief.

1.4.7. Launch decisions are made by the DCO. However, the MCC is an integral partner in the decision process. The Senior Controller is responsible to gather and apply real-time mission information to validate that DCO decisions are in compliance with AFI 11-207. Communicate any non-concurrence with DCO decisions to the AOS Top 3.

1.4.8. The MCC will ensure that the AOS Top 3 is informed if there are any non-standard events requested by the DCO, such as adding an Alpha refueling, adding an MRB that is not on the profile, canceling a mission prior to the ETD, or changing the destination.

1.4.6. Following the Go/No-Go brief, communicate the primary MRBs to the AOS Weather Flight for Mission Watch purposes.

1.4.10. Call the DCO to report any changes that adversely impact primary MRBs, the destination, and the destination alternate NLT 15 minutes after receipt of notification. This will primarily be adverse weather forecast changes but may include any adverse information.

1.4.11. Ensure that launch and arrival times are documented and relayed to appropriate agencies. Monitor all scheduled aircraft until arrival at the final destination.

1.4.12. Complete the After Landing checklist referenced in Appendix D.

1.4.13. When fighter aircraft deviate from the original itinerary, notify the AOS Top 3 and ensure the DCO is informed.

1.4.14. Develop, coordinate, and implement follow-on plans for missions that do not launch on schedule, are substantially delayed, divert to an MRB, return to the departure base due to an in-flight emergency (IFE), abort due to maintenance, or otherwise deviate from mission itineraries. Initiate coordination with the DCO. Maintain close coordination with the DCO and the Tanker Airlift Control Center (TACC) until the mission is fully reset and ensure ATO changes are published to reflect the current status of delayed or diverted missionscom.

1.4.15. Complete and distribute the Aircraft Divert Report checklist referenced in Appendix D.

1.4.16. Complete the Mission Change Setup checklist referenced in Appendix D.

1.4.17. Coordinate and publish ATOs to support diverted aircraft

1.4.18. The division of task accomplishment between Senior Controllers and Technical Controllers is at the discretion of the contractor, with the exception that Senior Controllers alone are required to analyze mission parameters (Flight products, weather, fuels, MRB viability, etc) to effectively conduct the DCO Go/No-Go brief and validate DCO decisions. The Senior Controller is responsible for the accuracy of all tasks accomplished by the MCC.

1.4.19. Coronet navigation planners will also serve as the primary resource to accomplish short notice replanning of Coronet flight profiles during mission execution. Specific duties are listed at 5.1.4.

1.5. MISSION REPORTING, DOCUMENTATION AND ADMINISTRATION. Functional responsibilities include preparing, tracking and maintaining records on all scheduled current missions, completing checklists, compiling, editing and transmitting mission reports detailing aircraft delivery activity, posting and updating web page information, responding to requests for mission data, completing data entry into ADIS, completing post mission reports, filing records and archiving ADIS information, destroying hard copy mission materials not earlier than 10 days and electronic mission materials not earlier than 90 days after the mission is delivered.

Specifically, the MCC will accomplish the below listed duties.

1.5.1. Prepare and maintain Coronet mission folders.

1.5.2. Review and verify the accuracy of all mission folder contents to include the mission folder checklist, mission setup spreadsheet, mission itinerary, crew lineup (updating crew and/or aircraft substitutions during execution), prelaunch mission changes, altitude reservation approvals, mission crew qualifications documents (e.g. letter of Xs), flight duty period waivers, single ship waivers, night landing waivers, crew lineup data, air refueling support tasking messages, flight planning profiles, Go/No Go decisions, weather forecasts, missed refueling base information, divert checklists, safety reports, in-flight emergency reports and any other documentation from aircraft delivery activity.

1.5.3. Compile, edit, and electronically post mission reports to keep headquarters elements and appropriate agencies informed regarding delivery flight activity. The reports identified below are required at the frequency indicated.

1.5.4. Prepare the approved format deliverable “Current Mission Summary” slide and the AOS six-month web schedule with cell/leg schedule (classified/unclassified) with detail including the current disposition of aircraft delivery activity by the end of each work shift, post to the appropriate webpage, and send to agencies and/or individuals as directed by the AOS Top 3.

1.5.5. Provide real-time updates and maintain system integrity of ADIS. Input/update data promptly following the receipt of mission information. Document deviations and actions taken in ADIS allowing for accurate mission reconstruction and disposition.

1.5.6. Be familiar with the current and approved flight planning applications and software. Be fully competent in the process of downloading, moving, saving, printing and properly disseminating flight plan materials on unclassified and secure network systems.

1.5.7. Prepare and post (classified and unclassified) updates to applicable agency web sites as directed by the AOS Top 3.

1.5.8. Access and reference Flight Information Publications in order to provide information to assist in mission execution.

1.5.9. Access and reference applicable regulations to include AFI 11-207, ACC AOS OI, ACC AOS Read File items, TACC SPINS and Business rules, AFI 11-202V3, AFI 11-202V3, and other guidance, as required to provide information to assist in mission execution.

1.5.10. Coordinate with the DCO, TACC, the AOS Plans shop and/or squadron leadership to prepare, edit and transmit ATO change messages via e-mail within a reasonable time. Prior to transmitting the ATO (e.g. ETDs, stopover bases, number of aircraft, etc), update the mission statement, and (add to/delete from) the distribution list as necessary to ensure receipt by all applicable recipients.

1.5.11. Provide in-depth mission knowledge of key principles to assist with successful AOS CORONET mission outcomes.

1.5.12. Inform squadron leadership of potential mission failure due to emerging circumstances affecting AOS CORONET missions. Provide squadron leadership decision space to engage with appropriate principals to affect an acceptable outcome that complies with applicable instructions and guidance.

1.5.13. Monitor, prepare, edit and transmit, in a timely manner, NIPR and SIPR correspondence as required to enable effective AOS CORONET mission coordination.

1.5.14. Establish, participate in, and/or monitor mission required conference calls to enable effective AOS CORONET mission coordination. Be capable of providing phone transfers for mission required coordination, when requested.

1.5.15. Provide a monthly status report to squadron leadership and the contracting officer’s representative (COR) that summarizes MCC monthly activities and significant events.

SECTION 2

SERVICE SUMMARY /DELIVERABLES TABLE

SERVICE SUMMARY NARRATIVE. This Service Summary identifies critical success factors for the contract.

2.1. PURPOSE. The Service Summary lists performance objectives for the required services the Government will surveil. The absence of any contract requirement from the SS shall not detract from its enforceability nor limit the rights or remedies of the Government under any other provision of the contract, including the clauses entitled “Inspection of Services” and “Default.”

2.2. COMPONENTS. The Service Summary states the performance objective (required service), and threshold (performance standard, accept and reject points (if applicable) in either a qualitative or quantitative fashion for each critical success factor.

2.3. PERFORMANCE THRESHOLD

2.3.1. Contractor provides appropriately qualified workforce to support 24/7 MCC operations (Related CPARS Elements: Management, Schedule, Regulatory Compliance)

Performance is acceptable when the contractor:

- Prepares and publishes executable labor work force schedules, and,

- Continuously staffs the MCC in accordance with the AOS Commander’s requirements as listed in paragraph 1.2.2., and,

- Maintains appropriate clearances, and,

- Employees are task-qualified, certified, and meet position currency requirements, and,

- Fills position vacancies within 14 calendar days, and,

- Provides services at the designated AOS alternate operating location, as directed by the government.

2.3.2. Contractor employees maintain technical performance and work quality meets all service and security requirements and timelines (Related CPARS Elements: Quality, Schedule)

Performance is acceptable when the contractor:

- Conducts mission planning and preparation to enable timely mission execution, and,

- Coordinates with all appropriate entities until mission completion, and,

- Accomplishes the Go/No-Go checklist with no uncorrected errors or omissions, and,

- Provides services do not result in deviations from security requirements, practices dangerous to security, or results in a security infraction.

Performance is unacceptable when, due to contractor delay, error and/or omission, such action or inaction resulted in mission delay past latest take-off time or mission cancellation.

2.3.3. Contractor deliverables are received on time, by agreed upon method, to appropriate parties, and all critical information is accurate.

Performance is acceptable when the Contractor:

- Receives no more than two customer complaints, validated by the contracting officer, per month, and,

- Successfully corrects identified deficiencies before negative mission impact, and,

- Creates and maintains mission folders, post-mission reports, and provides near real-time updates, as directed, and,

- Accurately reflects, within 2 hours of change in mission deposition, all aircraft movements from CORONET origin to destination, and,

- Provides sufficient knowledge to squadron leadership as to enable effective decision space.

Note: Deviations from Acceptable Performance Thresholds shall be coordinated through the AOS Top 3 or contracting officer representative and approved by the contracting officer.

2.4. QUALITY ASSURANCE. The Government reserves the right to surveil all services and requirements called for in this PWS to determine whether the Contractor is meeting performance objectives and goals. The government will periodically evaluate the contractor’s performance in accordance with the Quality Assurance Surveillance Plan. Additionally, the site leader will meet with squadron leadership quarterly or Contracting Officer Representative (COR) as directed by the AOS/CC to report on the health and welfare of MCC operations and personnel.

2.5. GOVERNMENT REMEDIES. The contracting officer shall follow FAR 52.212-4, Contract Terms and Conditions-Commercial Items (Oct 2018), for contractor’s failure to perform satisfactorily services or failure to correct nonconforming services.

2.5.1. Major Non-Conformance. A non-conformance that adversely affects or has the potential to affect the mission, safety of personnel and/or equipment, environment, performance (quality), schedule (delivery), and/or cost. The Contracting Officer will communicate major non-conformances to the Contractor using a Corrective Action Request (CAR) form with a suspense date for the Contractor’s corrective action plan. As a minimum, the Contractor’s action plan will address:

2.5.1.1. Action taken to fix the problem (correction)

2.5.1.2. Root cause analysis of the problem

2.5.1.3. Corrective action on the cause of the problem

2.5.1.4. Actions taken to prevent recurrence to include the follow-up plan (how and when)

2.5.1.5. Action(s) required by the Contractor’s Quality Plan

2.5.1.6. All supporting evidence to support actions taken such as updated manuals, instructions, procedures, etc. Embed supporting evidence in this section to maintain a single document.

2.5.2. Minor Non-Conformance. A minor non-conformance is a non-conformance, which by itself does not adversely impact mission, safety of personnel and/or equipment, performance (quality), schedule (delivery), or cost.

Minor non-conformances are communicated through Notices; First Notices are issued for any identified minor nonconformance, Second Notices are issued for repeat minor non-conformances or failing to correct minor nonconformances within a reasonable amount of time. A formal corrective action plan is not required for Notices.

2.6. QUALITY CONTROL. The contractor shall develop, submit and maintain an approved Quality Control Plan (QCP) to ensure operation of the MCC is performed in accordance with established performance standards. The draft plan shall be submitted as part of the Technical Volume and a final plan submitted 14 days prior to contract start date. The contractor shall make appropriate modifications and shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. As a minimum, the contractor shall develop quality control procedures addressing the areas identified in Section 2, Service Summary.

Note: The plan shall include (1) a description of the inspection system to cover all services listed on the Service Summary, (2) areas to be inspected; both scheduled and unscheduled, (3) frequency of inspections, (4) title and organizational placement of inspectors, (5) description of methods to be used for identifying and preventing defects in the quality of service performed, and, (6) description of records to be kept to document inspections and corrective or preventative actions taken. The record of inspections shall be kept and made available to the contracting officer, when requested, throughout the contract performance period and for the period after contract completion until final settlement of any claims under this contract.

2.7. DELIVERABLES TABLE. The Contractor shall provide contract deliverable(s) in a format mutually agreed upon by the Government and the Contractor. All deliverables will be reviewed for timeliness, accuracy and format. If a deliverable due date falls on a weekend or holiday, the Contractor shall submit the deliverable on the last work-day prior to the due date.

2.7.1. Deliverables.

Quality Control Plan Draft (Para 2.6) - concurrent with the proposal Final - 14 days prior to contract start date Transition Plan (Para. 5.8) - Concurrent with the proposal Training Plan (Para 5.2 and 1.2) - Within three months from contract start date Senior Controller / Technical Controller Qualification (Para 5.5 and 5.6) - Within 14 days of position vacancy Senior Controller / Technical Controller Certification (Para 5.2) - Prior to performing duties unsupervised

SECTION 3

GOVERNMENT FURNISHED PROPERTY AND SERVICES.

3.1. GENERAL INFORMATION. This section of the PWS specifies what the Government shall provide the contractor (facilities, equipment, and materials) to accomplish the requirements of this PWS. The contractor shall provide any other facilities, equipment, or services that the contractor determines necessary to accomplish this contract effort.

3.2. GOVERNMENT FURNISHED PROPERTY. There is no GFP that will be provided under the scope of this contract.

3.2.1. Government-Furnished Facilities, Government-Maintained. The government shall furnish or make available office space within government facilities as described in Appendix B.

Government facilities have been inspected for compliance with the Occupational Safety and Health Act (OSHA). No hazards have been identified for which workarounds are needed. Should a hazard be subsequently identified, the government will correct OSHA hazards according to government developed and approved plans of abatement. A higher priority for correction will not be assigned to the facilities provided hereunder merely because of this contracting initiative. The fact that no such conditions have been identified does not warrant or guarantee that no possible hazards exist, or that workaround procedures will not be necessary, or that the facilities, as furnished, will be adequate to meet the responsibilities of the contractor. Before any modification of the facilities is performed by the contractor at his or her expense, the contractor must furnish the contracting officer documentation describing, in detail, the modification requested. No alterations to the facilities shall be made without specific written permission from the contracting officer (CO). In the case of alterations necessary for compliance with OSHA, such permission shall not be unreasonably withheld. The contractor shall return the facilities to the government in the same condition as received, fair wear and tear and approved modifications excepted. These facilities shall only be used in the performance of this contract.

3.2.2. Government-Furnished Equipment, Government-Maintained. The government shall provide items considered to be incidental to the place of performance located on Government installations; these items are not GFP according to FAR 45.000(b). The Government shall retain accountability of these items and shall be responsible for the maintenance of Government-owned equipment. The contractor shall be responsible for the proper use of this equipment and shall report any problems to the Government COR. See Appendix B.

3.2.2.1. Equipment Inventory. The local unit may require an inventory of GFE that is not classified as GFP. If this occurs, it must be done not later than 15 calendar days upon written request from the local unit. The contractor and a Government representative (identified by the CO) shall conduct a joint inventory of all GFE and the contractor shall sign a receipt for all equipment provided by the Government. Items of equipment missing or not in working order shall be recorded and the CO notified in writing. The contractor and the Government representative shall jointly determine the working order and condition of all equipment and document their findings on the inventory.

3.2.2.2. Replacement of Government-Furnished Equipment, Government-Maintained Equipment. The contractor shall submit written requests for replacement of government-maintained equipment to the contracting officer or his/her designated representative for processing. Such requests will specify the reason for the replacement request.

3.2.3. Government Furnished Records. The applicable government records will be provided to the contractor as required. These records may include pending requisitions for equipment to be furnished to the contractor, pending project case files required for contract performance or control logs or registers on which the serially sequenced entries must be continued by the contractor. SF 135, Records Transmittal and Receipt, will be prepared for all records transferred, unless a duplicate record copy is kept by the government. Records transferred to the contractor will be returned to the government only if specifically required by this PWS.

3.3. GOVERNMENT FURNISHED SERVICES.

3.3.1. Custodial Service. As provided by the Government but shall not exceed those services normally provided at that Government facility. The contractor is ultimately responsible for interior cleanliness of the facility.

3.3.2. Communication, Telephone Services and Electronic Media. The government will provide the contractor telephone equipment, the appropriate classification of telephone lines and connectivity to email, internet, and LANs to effectively conduct aircraft delivery operations.

3.3.3. Distribution. The government will provide distribution networks as necessary to conduct aircraft delivery operations. The government will also ensure the timely provision of CAC card support, SIPR tokens, and Information Technology support in the event of system degradation.

3.3.4. Training. The government will ensure that MCC personnel receive sufficient training to operate new software and hardware provided to the MCC for performing mission functions.

SECTION 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

Except for the property and services specifically stated as Government-furnished in this PWS, the contractor shall furnish everything necessary to perform the requirements in this contract.

Contractor equipment shall be compatible with Government systems. All equipment provided by the contractor for contractor business use shall be fully owned and maintained by the contractor and removed from the site upon expiration of this contract. Any of these items requiring repair/replacement or upgrade during the life of the contract shall be the responsibility of the contractor.

SECTION 5

GENERAL INFORMATION

5.1. CONTRACTOR PERSONNEL. The contractor shall provide a site leader (supervisor/team leader) who shall be responsible for the performance of work. The name of this individual shall be designated in writing to the contracting officer.

5.1.1. The site leader shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract.

5.1.2. The site leader shall be available during normal duty hours within 30 minutes to meet on the installation with government personnel (designated by the contracting officer) to discuss problem areas. After normal duty hours, the site leader shall be available within one hour. In the event the site leader is not available, the on-duty Senior Mission Controller will act as the site leader’s designated alternate.

5.1.3. The site leader will allocate a maximum average of 100 hours per month to MCC management, MCC projects, and MCC training with the balance of time dedicated to serving shifts as a Senior Controller. The average of 100 hours per month will be met and calculated on a semi-annual basis (Jan-Jun and Jul-Dec) to provide flexibility. The number of shifts served, as well as the MCC management, project, and training activities and accomplishments will be documented in the monthly report.

5.1.4. The Coronet Navigation Planner will use the AOS mission planning system to create coronet flight profiles. Profiles must conform to mission aircraft specifications, Federal Aviation Administration and International Civil Aviation Organization requirements, and diplomatic clearance requirements of departure, destination, and enroute host nation airspace. Following the creation of flight profiles, upload products to the AOS shared drive for validation and feedback from squadron leadership and adjust profiles as directed. Update the Air Delivery Information System with flight products for each mission created.

5.1.5. The contractor shall not employ persons for work on this contract if such employee is considered by the contracting officer to be a potential threat to the health, safety, security, general well-being or operational mission of the installation and its population.

5.1.6. Contractor personnel shall present a neat appearance, be easily recognized as a contractor employee, and display a credential that identifies the employee as a contractor at all times while involved in aircraft delivery operations.

5.1.7. Contractor personnel that are separating must return the Common Access Card (CAC), Ryan Center access badge, and SIPR token.

5.2. EMPLOYEE TRAINING AND CERTIFICATION.

5.2.1. The contractor will develop a comprehensive training program that encompasses all aspects of the MCC scope of work and provide initial certification training as well as annual refresher training of all assigned contractor personnel, to include augmentee(s), for the purpose of performing AOS CORONET aircraft delivery operations.

5.2.2. Senior controllers must be trained and certified to access, reference, and operationally apply the publications and forms (checklists) in paragraph D-1 as well as publications and forms that replace these items during the length of the contract.

5.2.3. Senior controllers will be trained to operate all classified and unclassified equipment listed in Appendix B as well as equipment that replaces these items during the length of the contract.

5.2.4. The incumbent contractor will train incoming contractor personnel in accordance with their approved transition plan. The incoming contractor will provide qualified personnel in accordance with section 5.5. These individuals will be trained by incumbent onsite contract personnel until certified as proficient in all functional areas of MCC operations.

5.2.5. The site leader is responsible for accomplishing all MCC training, certifications, and recertifications.

5.2.6. The AOS Commander will be the final approval authority to certify contractor personnel.

Initially trained personnel must be certified by the AOS Commander prior to assuming duties without the oversight of a senior controller.

5.2.7. The incoming contractor will be responsible for all subsequent training and certification of employees to include initial training of new hires, annual refresher training for existing hires after the transition period, and all currency requirements for the purpose of performing AOS CORONET aircraft delivery operations.

5.2.8. The contractor will prepare and submit a training plan to the government within three months from the contract start date detailing their methodology for ensuring training and certification requirements.

5.2.9. The AOS Commander is the approval authority for all aspects of the training program.

5.3. CONTRACTOR FORCE PROTECTION REQUIREMENTS.

5.3.1. General. The Contractor and all Contractor personnel shall abide by all AF and local rules, procedures and standards of conduct. A Department of Defense Contract Security Classification Specification (DD Form 254) is required for access to classified material. The Contractor shall also perform in accordance with the Compliance with National Industrial Security Program Operating Manual (NISPOM--DoD5220.22M).

5.3.2. Contract Performance. Contract performance is restricted to the Mission Control Center located at Langley Air Force Base, VA or an alternate location during a crisis as communicated by the ACC AOS Top 3. The highest level of security clearance required for contract performance is SECRET.

5.3.3. Security Assistant Appointment. The contractor shall appoint a Security Assistant for the on-base Visitor Group. The Security Assistant may be a full-time position or an additional duty position. The Security Assistant and sponsoring agency's Security Manager shall ensure all contractor personnel are integrated into sponsoring agencies Information Protection Program and receive initial and recurring security education training IAW DOD 5200.01, the DOD Information Security Program Manual, and AFI 16-1404, Air Force Information Security Program.

5.3.4. Facility and Security Clearance Requirements. Contractor must possess a minimum of a Secret Facility Clearance prior to award in order to perform on this contract. All personnel performing on this PWS require minimum of a favorable completed investigation (Secret eligibility). Contractors shall request personnel security clearances (submit Clearance paperwork through Defense Counterintelligence Security Agency (DCSA) to the National Background Investigations Bureau (NBIB) for personnel requiring access to classified information within 15 days of contract award. Due to the costs involved with security investigations, requests for Contractor security clearances shall be kept to an absolute minimum necessary to perform contract requirements. Contractor personnel shall have appropriate clearances prior to commencing work on any contract unless otherwise approved in writing by the CO. The Contractor shall also complete visit requests for each individual that will be performing work on a contract in the Defense Manpower Data Center (DMDC) Joint Personnel Adjudication System (JPAS) or The Defense Information System for Security (DISS) prior to performance start unless otherwise approved in writing. All personnel performing on this PWS shall be U.S. Citizen. The Prime Contractor shall ensure that any teaming partners or subcontractors have the appropriate clearances prior to beginning performance.

5.3.5. Visitor Group Security Agreement (VGSA). The new AFMAN 16-1406 no longer requires the contractor to sign the VGSA. A Contractor becomes a visitor group when they will perform on base for 90 days or more. Upon notification of the presence of the visitor group, the Information Protection Office will contact the Facility Security Officer vie email, letter or telephone and inform them of the local security policies when classified performance will occur. This agreement shall outline how the contractor integrates security requirements for contract operations with the Air Force to ensure effective and economical operation on the installation. The agreement should address the below listed items.

5.3.5.1. Security support provided by the Air Force to the contractor will include storage containers for classified information/material, use of base destruction facilities, classified reproduction facilities, use of base classified mail services, security badging, base visitor control, investigation of security incidents, base traffic regulations, the use of security forms, conducting inspections required by DOD 5220.22R, Industrial Security Regulation, and AFI 31-601, Industrial Security Program Management.

5.3.5.2. Security support requiring joint Air Force and contractor coordination includes the packaging of classified information, mailing and receiving classified materials, transportation of classified materials up to SECRET information, implementing emergency procedures for protection of classified information, security checks, and internal security controls for protection of classified material and high value pilferage property.

5.3.5.3. On base, the long-term visitor group security agreement may take the place of a Standard Practice Procedure (SPP).

5.3.6. Information Security. The contractor shall comply with all security requirements as identified in the DD Form 254. The contractor shall provide for the protection of classified information from UNCLASS to SECRET level for classified information and materials received or generated as a part of the execution of this contract. The contractor shall not reproduce or distribute classified information without the written approval of the Government.

5.3.7. Listing of Employees. Prior to contract start, and as changes occur, the contractor shall provide the CO/PM and COR, a list of all company employees assigned to this contract. The list shall include the employee's name, social security number and level of security clearance and location of performance. The list shall be validated and signed by the company Facility Security Officer (FSO) and provided also to the Sponsoring Agencies Security Manager. An updated listing shall be provided when an employee's status or information changes.

5.3.8. Pass and Identification. The contractor shall ensure pass and identification items required for contract performance are obtained for employees and non-Government owned vehicles.

5.3.9. Retrieving Identification Media. The contractor shall retrieve all identification media from employees who depart for any reason before the contract expires; e.g. terminated for cause, retirement, etc.

5.3.10. Traffic Laws. The contractor and its employees shall comply with base traffic regulations.

5.3.11. Weapons, Firearms, and Ammunition. Contractor employees are prohibited from having weapons, firearms, or ammunition on themselves or in their contractor or privately-owned vehicle while on any government installation.

5.3.12. Controlled Unclassified Information (CUI). The contractor shall comply with DoDI 5200.48, Controlled Unclassified Information (CUI) requirements. This regulation sets policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding CUI material.

5.3.13. Reporting Requirements. The contractor shall report to an appropriate authority any information or circumstances they may be aware of that may pose a threat to the security of DOD personnel, contractor personnel, resources, and classified or unclassified defense information. Contractor employees shall be briefed by their immediate supervisor upon initial on-base assignment.

5.3.14. Physical Security. The contractor shall be responsible for safeguarding all government property and controlled forms provided for contractor use. Should the MCC be unmanned, either the Senior Controller or Technical Controller will complete the AOS closing checklist.

5.3.15. Controlled/Restricted Areas. The facility Security Manager shall implement local base procedures for entry to Air Force controlled/restricted areas where contractor personnel will work.

5.3.16. Communications Security (COMSEC). Contractors may require access to COMSEC information. The DD FM 254 will give further instructions on safeguarding and managing COMSEC material.

5.3.17. Computer Security. The Contractor shall complete IA training (e.g. Cyber Awareness) prior to gaining access to ".mil" or ".smil" (Secure .mil) domains IAW Air Force Instruction (AFI) 33-200 IA Management, AFI 16-1404, AF Information Security Program, and AFI 17-100 Air Force Information Technology (IT) Service Management. Additional user training may be developed locally to reflect local needs and concerns.

5.3.18. Non-Government Networks. The contractor is prohibited from establishing their own Information Technology (IT) systems/networks (Local Area Networks (LAN), Wide Area Networks (WAN), Cellular phone/USB Modem as WAN, Wi-Fi as WAN etc.) without the direct permission of governing communications and responsible information systems office and direction by the Government CO. If permission is granted, the Government office approving the request is responsible for providing oversight to ensure the system is properly accredited and authorized and all DoD/AF IT requirements are met. The Contractor shall provide point of contact information of such government office to the Government PM. Contractor employees who need access to government IT systems are determined to be trustworthy by the completion of a favorable personnel security investigation commensurate with assigned duties and by a designated government official prior to IT access being granted. This is accomplished through the system authorization access request, DD Form 2875, process. This does not preclude the contractor from forwarding MCC phones to personal cell phones when performing MCC “on call” operations or other official business.

5.3.19. Automatic Data Processing Equipment (ADPE). Visitor groups are prohibited from establishing their own Information Technology (IT) systems/networks (Local Area Networks (LAN), Wide Area Networks (WAN), Cellular phone/USB Modem as WAN, Wi-Fi as WAN etc.)

without the direct permission of governing communications and responsible information systems office. If permission is granted, the Government office approving request is responsible for providing oversight to ensure the system is properly accredited and authorized and all DoD/AF IT requirements are met. Contractor employees who need access to government IT systems must be determined to be trustworthy by the completion of a favorable personnel security investigation commensurate with assigned duties and by a designated government official prior to IT access being granted. This is accomplished through the system authorization access request, DD Form 2875, process. The Contractor shall establish and implement procedures to ensure all ADPE, to include laptops and other data processing devices, issued to the Contractor by the Government are not lost or misplaced, are not used by unauthorized persons or are not subject to unauthorized external devices. The Contractor shall immediately report to the CO or PM any occurrences of lost ADPE within two (2) hours of discovery of occurrence. In the event that ADPE is lost, the Contractor may be required, upon written direction of the CO, to replace the equipment at no additional cost to the Government.