UPDATED_Attachment_1-_PWS_23_July.pdf

Performance Work Statement (PWS) for

Squadron Operations Support

At

MacDill AFB, Florida

23 July 2018

1.0 Introduction/Background. The squadron operations support function provide skills such as Aircrew Scheduling, Mission Planning, Training Support, Standardizations & Evaluations (Stan/Eval), and other operational related functions. The focus of work will be done to support non-flying duties in squadrons that traditionally utilized operational aircrew members to accomplish core squadron functions.

2.0 Objective. The objective of this requirement is to provide in-garrison active squadrons with functional support for core squadron functions such as Scheduling, Mission Planning, Training, Stan/Eval, and other required tasks.

3.0 Requirements – Squadron Operations Support. The Contractor shall provide all personnel, supervision and other services necessary to perform operations squadron functional support for two (2) Air Refueling Squadrons. An additional squadron may be added in the future for similar support functions. The required contractor support shall enable assigned active duty aircrew members to fulfill requirements for achieving and maintaining aircraft mission qualification in their assigned weapon system by providing the expertise in this requirement as described in the following subtasks, 4.1 - 4.4. Each of the four subtasks were historically completed by four separate full time active duty military members. The four subtasks are all located in separate geographical offices on MacDill Air Force Base.

If necessary, an additional office located in Birmingham, Alabama will require support. Reference the workload estimate in Appendix B.

3.1 The contractor shall identify a single point of contact who has full authority to act for the Contractor on all matters relating to daily operation of the contract; has full authority to remove/replace personnel at the request of the Contracting Officer; complete all in-processing and indoctrination actions prior to the start of all newly-hired personnel; ensure all personnel receive and maintain documentation of their duties and responsibilities and orientation in these duties and responsibilities prior to performance start. This individual will communicate directly with the CO/COR on matters pertaining to the execution of this PWS.

4.0 Subtasks. The subtasks of this requirement are outlined in 4.1 - 4.4.

4.1 Training Support – Proper training is key to correctly in-process new members, properly meeting continuity training on a periodic basis, and meeting and maintaining upgrade processes. The Contractor shall:

4.1.1 Update data in GTIMS or future equivalent systems to GTIMS, and locally-developed computer database systems as required.

4.1.2 Interface with Host Aviation Resource Management (HARM) and Squadron Aviation Resource Management (SARM) personnel to update the Aviation Resource Management System (ARMS) or future equivalent systems to ARMS as required.

4.1.3 Build, review and update student/permanent party records, folders and grade books per the applicable Air Force Instructions (AFI 11-202V1 and AFI 11-2MDS-V1), associated MAJCOM Installation supplements, and locally- developed guidance. Number of records will vary depending on unit manning/student throughput.

4.1.4 Administer classes and exams as required. Coordinate with scheduling to ensure crewmembers are scheduled for Crew Resource Management, Instructor Crew Resource Management, Instrument Refresher Course, and any other grounding or pre-deployment training requirements. Number of classes/exams will vary depending on unit manning/student throughput.

4.1.5 Perform weekly individual gradebook checks of personnel training and ancillary training requirements.

4.1.6 Prepare and execute periodic training/testing plans for approval and scheduling and coordinates off-site training conferences/seminar attendance.

4.1.7 Provide weekly updates to squadron leadership containing the flight and readiness status of personnel to facilitate tracking of duty status and performance report/decoration accomplishment.

4.1.8 Coordinate with scheduling officer, enabling them to maximize training opportunities in accordance with unit leadership guidance. Scheduling and training will be consistent with AFIs.

4.1.9 Provide daily tracking of upgrade and continuation training accomplishment for the unit Operations Supervisor (or equivalent) as well as weekly summaries for the Operations Officer.

4.1.10 Assist in the implementation and execution of new curriculum and syllabi created by higher AF HQ for aircrew and ground training.

4.1.11 Generate the following reports/forms as required:

4.1.11.1 AF Form 4324, Aircraft Assignment/Aircrew Qualification Worksheet.

4.1.11.2 Training aids.

4.1.11.3 Monthly aircrew qualification level summary (also known as the “Letter of Xs”) and provide a copy of in- work and final documents to OSO and Wing Stan/Eval (OGV) NLT the last day of each month.

4.1.11.4 Monthly and quarterly inputs to OST Training each quarter.

4.1.11.5 Monthly Squadron Training Review Panel (STRP) briefings the Squadron leadership to include training recommendations and status of training on unit members

4.1.11.6 Monthly summary of aircrew probation/regression status.

4.1.11.7 Monthly review of new inbound aircrew members, to include coordination and discussion with Squadrons DOs & CCs to determine Wg/Gp/or Squadron of assignment based upon needs and qualification of the inbound aircrew with needs and qualification across the Wg/Gp/Sqs.

4.1.11.8 Coordinate with FSS/CSS/Personnel systems (i.e. MilPDS) to assign/re-assign new inbound members from the 6 OSS/OST to the 50th/91st/other squadrons, as required.

4.1.11.9 Grade Book report.

4.1.11.10 Conduct monthly meeting with each Squadron Commander to discuss all members’ Upgrade Training. The exception to this is commanders of flying squadrons, this role is fulfilled by Standardization and Evaluation.

4.1.11.11 Conduct SAV’s every 12-18 months, and hold quarterly training meetings with all squadron workcenter supervisors.

4.1.11.12 Be responsible for sending all training RIPS to members across the group, and forwarding to Formal Training office by suspense required

4.1.11.13 Update/monitor all members’ training data in ADLS, and run monthly MilPDS reports on all AFSCs and coordinate for Squadron Commander’s signature to load to MAJCOM SharePoint no later than the 6th of each month.

4.1.11.14 Conduct face-to-face meetings with supervisors and new members upon in-processing, completing upgrade training, CDC orientation, CDC failures, etc.

4.1.11.15 Extremely proficient with TBA, GTIMS, PEX, 623a, and AFTR

4.1.11.16 Perform weekly individual gradebook checks of personnel training and ancillary training requirements.

4.1.11.17 Prepare and execute periodic training/testing plans for approval and scheduling and coordinates off-site training conferences/seminar attendance.

4.1.11.18 Provide weekly updates to squadron leadership containing the flight and readiness status of personnel to facilitate tracking of duty status and performance report/decoration accomplishment.

4.1.12 Knowledge/Experience

4.1.12.1 Training Support must show proficiency and experience working with GTIMs or similar proprietary scheduling program

4.1.12.2 Training Support must show proficiency and experience working with Microsoft Access, Excel, and SharePoint

4.1.12.3 Training Support must show proficiency and experience working in a DoD Flying Squadron/Group/Wing training program

4.2 Scheduling and Mission Execution Support

The Contractor shall:

4.2.1 Coordinate with the training office, standards and evaluation office, squadron aviation resource management (SARM), UDM, and Operations Officer (DO) to arrange a schedule to facilitate operations, qualification, upgrade, test, exercises, and continuation training accomplishment to meet required currency and progression standards, in accordance with Commander and DO priorities.

4.2.2 Build long and short-range shift schedules to ensure full coverage of all aircrew, instructor, evaluator, support personnel, and supervisor positions. Coordinate with senior squadron leadership on a daily and weekly basis. Coordinate with simulator contractors for sim events.

4.2.3 Keep track when crewmembers will be on leave, temporary duty, have scheduled medical appointments or other scheduling commitments. Contractor will deconflict crewmember schedules and work with flight leadership to ensure crews are available to meet assigned sortie taskings.

4.2.4 Track daily flight/ground/academic training requirements and accomplishments to facilitate accurate flight scheduling as directed by leadership. To the maximum extent possible, schedule aircrew based on experience to mitigate Operational Risk Management (ORM) as detailed in AMCI 90-903 Aviation ORM and as outlined by Stan/Eval in conjunction with 11-2KC-135v2 (and appropriate supplements). Updates will be reported to squadron and wing leadership.

4.2.5 Help facilitate last-minute schedule changes with all appropriate partners (such as current operations, command post, receivers) to ensure full coverage by working with the current mission commander/operations supervisor (or equivalent) and flight responsible for the shift that is not fully manned.

4.2.6 Obtain aircraft and equipment availability data from maintenance (MX) and schedule crewmembers for training, exercises, simulators, and operations, as required.

4.2.7 Publish/post scheduling data for unit long-/short-range ground/academic, flying, and simulator training event schedules on GTIMS, GDSS2, or other computer database systems.

4.2.8 Comply with AMC CAAP CONOPS (or current system of record), ADT (or current system of record), Ops Group and Wing Current Operations (OSO), and Group Training (OST) locally-developed guidance when building the schedule; obtain updates / changes to CAAP CONOPS (or system of record) and attend monthly ADT hosted by

AMC.

4.2.9 Determine flight, ground, and simulator schedule requirements for upgrade, initial qualification, requalification, transition, currency, and continuation training based on syllabus requirements, student progression, weather, and daily equipment/training range availability.

4.2.10 Perform daily updates of scheduling data to compensate for changing conditions and training completion rates.

4.2.11 Coordinate with OSO, OST, outside agencies/exercise participants and higher headquarters, for example: RED FLAG, GREEN FLAG, Weapons School support, for reporting and to facilitate exercise and special event schedule coordination.

4.2.12 Provide inputs to Wing Scheduling.

4.2.12.1 The Contractor shall attend and/or coordinate weekly meeting for schedule coordination and deconfliction.

4.2.12.2 Build, monitor, adjust, change, and edit daily flights, as created by the daily/weekly/monthly schedule.

4.2.12.3 Utilize GDSS, GTIMS, and other required programs.

4.2.12.4 Coordinate with 618 AOC (or other AOC, as necessary) to provide occasional assistance to HHQ taskings.

4.2.12.5 Attend operations, maintenance, and wing meetings, as directed.

4.2.12.6 Be responsible to communicate operational requirement to other wing agencies, such as maintenance for fuel loads.

4.2.12.7 Aid current operations in communication with users to determine off-load, Air Refueling track/anchor, and other operational requirements, as directed.

4.2.12.8 Understand AMC operational flying requirements and limitations, and build missions IAW all FAA, AF, AFI, AMC, and other HHQ-directives.

4.2.12.9 Work closely with 6 OSS, 50 ARS, 91 ARS, and 99 ARS Operations Officers (or their representatives) to meet daily flying requirements.

4.2.12.10 Obtain Defense Travel System (DTS) capabilities to build, create, and edit DTS orders and vouchers for operations personnel, including coordination with financial, resource advisor, FSS/CSS, and other agencies, to produce orders and travel arrangements for operations personnel.

4.2.12.11 Be available to act as UCC/GCC support when required.

4.2.13 Knowledge/Experience

4.2.13.1 Scheduling and Mission Execution Support personnel must show proficiency and experience working as a squadron aircrew scheduler or dispatcher, mission planner, or equivalent.

4.2.13.2 Scheduling and Mission Execution Support personnel must show proficiency and experience working with GDSS2 or similar proprietary scheduling program.

4.2.13.3 Scheduling and Mission Execution Support personnel must show proficiency and experience with intermediate-level use/application of Microsoft Office products.

4.2.13.4 Scheduling and Mission Execution Support personnel must show proficiency and experience working with

DTS.

4.2.13.5 Previous experience with GTIMS desirable.

4.3 Mission Planning Support

The Contractor shall:

4.3.1 Coordinate with the Scheduling (DOS), and Current Operations (OSS/OSO), and Operations Officer (DO) to plan real world and exercise missions.

4.3.2 Plan all locally generated sorties to include DD Form 175 or 1801 (electronic flight plans), computer generated flight planning and fuel logs. Provide takeoff and landing planning, notices to airmen, charts, route of flight, G2 extracts.

4.3.3 Help facilitate last-minute mission changes with all appropriate partners (such as current operations, command post, receivers) to ensure complete and accurate mission planning products are presented to the aircrews.

4.3.4 Coordinate with Squadron Aviation Resource Management (SARM) to provide daily go/no-go products to the aircrews.

4.3.5 Coordinates with maintenance to ensure correct model aircraft utilized with correct configuration.

4.3.6 Coordinates with receiver units to develop precise mission plans.

4.3.7 For off-station trainers, pursues diplomatic clearances, checks Giant Reports and ASRR for field limitations to include quiet hours, predicted bird conditions and other hazards, field closures etc.

4.3.8 Coordinates with applicable Air Operations Center (AOC) for both off-station training execution and tasked missions.

4.3.9 Utilize provided mission planning software, such as Portable Flight Planning Software (PFPS) and FalconView, to produce all planning products.

4.3.10 Support off-station aircrews by producing and emailing mission planning products.

4.3.10.1 The Contractor shall attend weekly meetings for schedule coordination and deconfliction.

4.3.10.2 Utilize GDSS, GTIMS, and other required programs.

4.3.10.3 Coordinate with Air Operations Center (AOC) to provide occasional assistance to HHQ taskings.

4.3.10.4 Be responsible to communicate operational requirement to other wing agencies, such as maintenance for fuel loads.

4.3.10.5 Aid current operations in communication with users to determine off-load, Air Refueling track/anchor, and other operational requirements, as directed.

4.3.10.6 Understand AMC operational flying requirements and limitations, and build missions IAW all FAA, AF, AFI, AMC, and other HHQ-directives.

4.3.10.7 Work closely with 6 OSS, 50 ARS, 91 ARS, and 99 ARS Operations Officers (or their representatives) to meet daily flying requirements.

4.3.10.8 Obtain Defense Travel System (DTS) capabilities to build, create, and edit DTS orders and vouchers for operations personnel, including coordination with financial, resource advisor, FSS/CSS, and other agencies, to produce orders and travel arrangements for operations personnel.

4.3.10.9 Be available to act as UCC/GCC support when required.

4.3.11 Knowledge/Experience

4.3.11.1 Mission Planning Support personnel must show proficiency and experience working as a mission planner or equivalent.

4.3.11.2 Mission Planning Support personnel must show proficiency and experience working with PFPS and FalconView or similar mission planning programs.

4.3.11.3 Mission Planning Support personnel must show proficiency and experience working with GDSS2 or similar proprietary scheduling program.

4.3.11.4 Mission Planning Support personnel must show proficiency and experience with intermediate-level use/application of Microsoft Office products.

4.3.11.5 Mission Planning Support personnel must show proficiency and experience working with DTS.

4.3.11.6 Previous experience with GTIMS desirable.

4.4 Standardization and Evaluation (Stan/Eval) Support – Accurate execution of the standards and evaluation program is key for maintaining proper and effective use of any USAF asset. The Contractor shall:

4.4.1 Maintain accountability and control of flight testing materials.

4.4.2 Update data in GTIMS, future equivalent systems to GTIMS, and locally-developed computer database systems as required.

4.4.3 Interface with HARM and SARM and personnel to update the Aviation Resource Management System (ARMS) or future equivalent systems to ARMS as required.

4.4.4 Coordinate with training officer to review and update student/permanent party records, folders and grade books per the applicable AFIs: AFI 11-202V2 and AFI 11-2MDS-V2 as well as associated MAJCOM/Installation supplements, and locally-developed guidance.

4.4.5 Notify crewmembers, scheduling, and unit leadership of upcoming and overdue testing, evaluation, and training requirements via e-mail, telephone or in person.

4.4.6 Generate the following reports/forms as required:

4.4.6.1 Evaluation and testing status and trend data reports.

4.4.6.2 Provide data to OGV for standardization evaluation board (SEB) and as required by leadership.

4.4.6.3 GTIMS shells for AF Form 8, Qualification of Aircrew Qualification.

4.4.6.4 Provide data as required for monthly Squadron Training Review Panels (STRP)

4.4.7 Perform testing administrator duties/function for the unit.

4.4.8 Conduct monthly reviews of assigned/attached crew member evaluation dates and provide updates on completion progress as directed by AFI and locally directed guidance.

4.4.9 Assist personnel assigned to Stan/Eval as requested in the execution of AFIs and provide recommendations to Stan/Eval shops to help track training and readiness status of squadron personnel and attend applicable meetings for training programs (STRP, R&C)

4.4.10 Knowledge/Experience

4.4.10.1 Stan/Eval Support personnel must show proficiency and experience working in a MAF Squadron/Group/Wing Stan/Eval office.

4.4.10.2 Stan/Eval Support personnel must show proficiency and experience working with GTIMS or similar proprietary Stan/Eval programs.

4.5 Deliverables: The Contractor shall provide deliverables as specified below in a format mutually agreed upon by the Government and the Contractor. Contractor personnel shall complete given tasks within timeframe specified;

ensure work products are thorough and accurate; and work and interact professionally and effectively with all levels of management and staff in completing tasks. Due dates for specific deliverables may be changed or waived by the Contracting Officer. 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.

4.5.1 A personnel roster is required and will be given to the COR/CO once all personnel are hired and will be updated as personnel change.

Deliverables

Deliverable

PWS Reference

Gov’t POC

Due Date

Training: Aircrew qualification level summary (Letter of X’s)

4.1 thru 4.1.12.3

Operations Officer or Delegate

1st duty day of each month

Training: 6 month training plan

Operations

Training: Monthly Squadron Training Review Panel (STRP) briefings

4.1 thru 4.1.12.3 Operations

Monthly and Quarterly

Training: Aircrew probation/regression report

Operations

Last duty day of each

Training: Grade book report

Operations

Weekly

Training: Inbound aircrew members assignment

4.1 thru 4.1.12.3 Operations Officer or Delegate;

Commander

Monthly

Scheduling: Weekly Schedule

4.2 thru 4.2.12.11

Baseline Schedule: COB every Friday

Schedule Changes: COB Daily (as req’d)

Scheduling: Flying effectiveness report

COB every Monday (as req’d)

Scheduling: Flying hour program report

Monthly & Annually (dates TBD) (as req’d)

Scheduling: Long Range Flight Schedule (6-12 months)

4.2 thu 4.2.12.11

COB every Friday

Mission Planner: Create Mission Binders

4.3 thru 4.3.10.9

Daily

Stan/Eval: Squadron checkride status report

4.4 thru 4.4.9

5.0 Government Provided Documentation. The Government will provide access to relevant Government organizations’ information, documentation, manuals, texts, briefs and other materials as appropriate to work requirements as contractually outlined.

6.0 Government Provided Equipment / Office. The Government shall provide office space, LAN connections, computer (hardware and software), e-mail and internet access and other standard office equipment necessary to support the Contractor. Laptops may be issued via hand receipt and will be returned to the government following completion of requirements for their use. Access will be granted to classified networks as directed by the COR or his designated representative.

7.0 Security. 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 Fm 254) is required for access to classified material. The Contractor shall also perform in accordance with the National Industrial Security Program Operating Manual (NISPOM--DoD 5220.22M).

7.1 Security Clearances. All personnel performing on this PWS shall require the submission of a T3 personnel security investigation. All contract personnel performing under this contract must maintain a personnel security clearance (PCL) at the Secret level. The contractor must possess a facility security clearance (FCL) at the Secret level at the time of proposal submission, 27 July 2018 at 2:00 PM EST. The contractor assumes costs and request for all PCLs under this contract. The contractor Facility Security Officer (FSO) will be responsible for requesting PCLs for contract personnel within 15 days after contract award. Contractor personnel shall have appropriate clearances prior to commencing work unless otherwise approved in writing by the CO. The Contractor FSO shall also complete visit requests for each individual that will be performing work via Joint Personnel Adjudication System (JPAS) prior to performance start unless otherwise approved in writing by the CO. The Prime Contractor shall ensure that any teaming partners or subcontractors have the appropriate clearances prior to beginning performance

7.1.2 Clearance Requirement. An SF 312 Non-Disclosure Agreement (NDA) must be initiated by the company’s FSO on all personnel performing on this contract.

7.1.3 Clearance Documentation. Prior to performance start, and as changes occur, the Contractor shall provide the primary COR with a list of all company employees assigned to this task order. The list shall include the employees’ Names, Location of Performance and Security Clearance.

7.2 Notification. The contractor shall notify applicable Information Protection Office at the performance locations, within a 60 day transition in period. The notification shall include:

7.2.1 Name, address, and telephone number of company representatives.

7.2.2 The contract number and contracting agency.

7.2.3 The highest level of classified information which contractor employees require access to.

7.2.4 The location(s) of contract performance.

7.2.5 The date contract performance begins.

7.3 Pass and Identification Items. The contractor shall ensure they make contact with the organizations Trusted Agent for TASS to obtain Common Access Cards (CAC).

7.4 Retrieving Identification Media. The contractor shall ensure all identification media from employees who depart for any reason before the contract expires; e.g. terminated for cause, retirement, etc., are turned in prior to departure.

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

7.6 Weapons, Firearms, and Ammunition. Contractor employees are prohibited from possessing weapons, firearms, or ammunition, on themselves or within their contractor-owned vehicle or privately-owned vehicle while on MacDill AFB, FL.

7.7 For Official Use Only (FOUO). The contractor shall comply with DoD 5400.7-R, Chapter 4, DoD Freedom of Information Act (FOIA) Program, and DoDM 5200.01, V4, DoD Information Security Program: Controlled Unclassified Information (CUI), requirements. These regulation sets policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding FOUO material.

7.8 Health Insurance Portability and Accountability Act (HIPPA). The contractor will possess, through completion of annual training as required to comply with requirements, knowledge of medical privacy and confidentiality standards as pertains to HIPAA. This is pertinent in regards to DoD personnel’s service medical status.

7.9 Reporting Requirements. Contractor personnel shall report to an appropriate authority any information or circumstances of which they are aware 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.

7.10 Physical Security. The contractor shall be responsible for safeguarding all government property and controlled forms provided for contractor use. At the end of each work period, all government facilities, equipment, and materials shall be secured.

7.11 Controlled/Restricted Areas. The contractor shall implement local base procedures for entry to Air Force controlled/restricted areas where contractor personnel will work. An AF Form 2586, Unescorted Entry Authorization Certificate, must be completed and signed by the sponsoring agencies Security Manager before a Restricted Area Badge will be issued. Contractor employees, as a minimum, must have a favorably completed National Agency Check plus written Inquiries (NACI) investigation before receiving a Restricted Area Badge. Interim access can be granted IAW AFI 31-501, Personnel Security Program Management

7.12 Key Control/Access Badge Control. The contractor shall establish and implement methods of making sure all keys/badges issued to the contractor by the Government are not lost or misplaced and are not used by unauthorized persons. The contractor shall not duplicate any keys issued by the government.

7.13 Lost Keys. The contractor shall immediately report to the COR or Program Manager any occurrences of lost or duplicated keys. In the event keys, other than master keys, are lost or duplicated, the contractor maybe required, upon written direction of the contracting officer, to re-key or replace the affected lock or locks without cost to the government. The government may, however, at its option, replace the affected lock or locks or perform re- keying and deduct the cost of such from the monthly payment due the contractor. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by the government and the total cost deducted from the monthly payment due the contractor.

7.14 Prohibited Use. The contractor shall prohibit the use of keys, issued by the government, by any persons other than the contractor’s employees and the opening of locked areas by contractor employees to permit entrance of persons other than contractor employees engaged in performance of contract work requirements in those areas.

7.15 Lock Combinations. The contractor shall control access to all government provided lock combinations to preclude unauthorized entry. The contractor is not authorized to record lock combinations without written approval by the government Program Manager. Records with written combinations to authorized secure.

7.16 Visitor Group Security Agreements. The prime contractor and all subcontractors assigned to the contract will enter in to a Visitor Group Security Agreement with the host base.

8.0 Transition Out. Prior to the end of the period of performance, the incumbent Contractor shall support a fifteen (15) business day (120 hours) transition period with incoming personnel supporting the installation in this PWS. During this period, all programs, information, data, etc. will be passed from the incumbent Contractor to the incoming Contractor so that there is no break in Customer or mission support.

9.0 ADMINISTRATION CONSIDERATIONS.

9.1 Contractor Identification. Each Contractor employee shall, while on duty, wear in plain view on the upper portion of his outer garment a metal or plastic identification badge to be furnished by the Contractor, containing the company name, employee name, and the section where the employee works. Contractor employees shall clearly identify themselves as "Contractors" at all times, in all communications and representations, including in the workplace, at meetings, in conversations, telecommunications, mail, electronic mail (e-mail), and faxes, whether with Government personnel, other Contractor personnel, or with the public. Contractors with access to the base Local Area Network (LAN) or with an official Government e-mail address shall include their company name in the signature block and the designation "CTR" in the global address. The Contractor shall notify the Government if the "CTR" designation is not included in the global address.

9.2 Contractor Inventory. In accordance with Section 8108 of Public Law 112-10 of the Department of Defense and Full-Year Continuing Appropriations Action, 2011.

9.2.1 Reporting. The Contractor shall report ALL labor hours required for performance of services provided under this requirement via the secure Contractor Manpower Reporting Application (CMRA) data collection site. The Contractor is required to completely fill in all required data fields at: http://www.ecmra.mil. Reporting inputs shall be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported anytime during the FY, all data shall be reported not later than 31 October of each calendar year. The Contractor may direct questions to the CMRA help desk. The prime Contractor is responsible to ensure all subcontractor data is reported.

9.2.2 Uses and Safeguarding of Information. Information from the secure web site is considered to be proprietary in nature when the contractor number and the Contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the Contractor name and contract number associated with the data.

9.2.3 User Manual. Data for the AF services requirements must be input at the AF CMRA link. However, user manuals for Government personnel and Contractors are available at the U.S. Army CMRA link at http://www.ecmra.mil.

9.3 Subcontractor Input in CMRA. Prime Contractors are responsible to ensure all subcontractor data is reported. Subcontractors will not be able to enter any data into CMRA, but will enter their information into a Bulk Loader spread sheet available from the AF CMRA helpdesk. Subcontractor shall fill in columns A-C then return it to the AF CMRA helpdesk after it's completed and a technician team will enter the information into CMRA.

9.4 Network Access: Contract personnel requiring access to the Air Force network shall have or must be able to obtain a National Agency Check (NAC) verified through the Joint Personnel Adjudication System (JPAS) in order to obtain ADP II designation. This is accomplished by completing the Electronic Personnel Security Questionnaire (EPSQ) or if applicable, completing a SF 85P, Questionnaire for Public Trust Positions. Personnel shall submit all required forms through the base’s Security Forces Squadron for submission to the Office of Personnel Management (OPM) in accordance with AFI 31-501, paragraph 3.24. Upon receipt of proof that contract personnel forms have been submitted to OPM, the commander responsible for the contract can grant interim Local Area Network (LAN) and e-mail access in accordance with AFI 31-501, paragraph 3.27. All personnel requiring access shall comply with the requirements of AFI 33-204, Information Assurance (IA) Awareness Program, paragraph 18.5, AFI 33-115 V2, Licensing Network Users and Certifying Network Professionals, paragraph 5, and AMCI 33-202, Information Assurance, Attachment 2. All contract personnel shall complete initial training in the Information Assurance Awareness Program (IAAP) and perform all refresher training as required.

9.5 Breach of Security: Neither the Contractor nor any of its personnel shall disclose nor cause to be disclosed any information concerning operations which could result in or increase the likelihood of the possibility of a breach of the activity’s security or interrupt the continuity of operations.

9.6 Classified Information: Disclosure of information, to any person not entitled to receive it, or failure to safeguard any classified information that may come to the Contractor, or any person under their control, may subject the Contractor, their agents or employees, to criminal liability under 18 U.S.C. §793 and §798.

9.7 Alternate Work Location. Alternate work locations are not permitted.

http://www.ecmra.mil/ http://www.ecmra.mil/

9.8 Duty Hours. The contractor is responsible for conducting business, between the hours of 0730 – 1630 Monday through Friday except Federal holidays or when the government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.

9.8.1 Schedule Services: Scheduling occurs between Monday through Friday 0730-1630; any schedule changes required must be completed within 10 minutes of notification and posted to GTIMS and GDSS. Federal Holidays will be observed. During Exercise support, contractor will be notified minimum 48 hours prior to additional support required schedule agreed upon by the Contractor and the COR. Estimated 8 exercises per calendar year.

9.8.2 Mission Planning. Planning occurs between Monday through Friday 0730-1630; any mission planning changes required must be initiated within 10 minutes of notification and posted to GDSS and completed within 30 minutes of notification of the change. Federal Holidays will be observed. During Exercise support, contractor will be notified minimum 48 hours prior to additional support required, the schedule will be agreed upon by the Contractor and the COR. Estimated 8 exercises per calendar year.

9.8.3 Training Services: Training occurs between Monday through Friday 0730-1630; trainers need to respond to training requests within 10 minutes of notification and provide answers to unit members, squadron commander, operations officer and/or base training officer. Federal Holidays will be observed.

9.8.4 Evaluation Services: Evaluations occurs between Monday through Friday 0730-1630; evaluators need to respond to requests for evaluations support within 10 minutes of notification. If scheduling is required, coordinate with applicable agencies and schedule the evaluation within an hour. Federal Holidays will be observed.

9.9 Base Shutdown/Inclement Weather. The Contractor will follow guidance of the installation authorities to determine reporting schedules due to a base closure or inclement weather.

9.10 Federal Holidays: The Contractor shall observe the same holidays observed by the Government, as follows:

HOLIDAY WHEN OBSERVED

New Year’s Day January 1 or the Friday preceding or Monday following Martin Luther King’s Birthday 3rd Monday in January President’s Day 3rd Monday in February Memorial Day Last Monday in May Independence Day July 4 or the Friday preceding or Monday following Labor Day First Monday in September Columbus Day 2nd Monday in October Veterans Day November 11 or the Friday preceding or Monday Following Thanksgiving Day 4th Thursday in November Christmas Day December 25 or the Friday preceding or Monday following

9.11 Contractor Personnel: The contractor shall provide a sufficient number of personnel possessing the skills, knowledge, and training to satisfactorily perform the services required by this PWS. Contractor personnel shall meet industry minimum education or experience requirements for each specific service area. The contractor shall not employ persons who are identified to the contractor by the Contracting Officer (CO) as potential threats to the health, safety, security, general well-being, or operational mission of the installation and its population. All contractor personnel shall be able to fluently understand, read, write, and speak English. The CO may require the contractor to remove employees from the workplace for reasons of misconduct or security. The contractor shall ensure employees have current and valid certifications and licenses, as identified by the Government or Federal, State, and local requirements or laws, to accomplish the services of the PWS before starting work. The contractor shall not employ any person who is an employee of the United States Government if employing that person would create a conflict of interest or the appearance of a conflict of interest. The contractor is cautioned that off-duty active military personnel hired to perform work may be subject to permanent change of station, change in duty hours, or deployment. Military

Reservists and National Guard members may be subject to recall to active duty. The abrupt absence of these personnel could adversely affect the contractor’s ability to perform; however their absence at any time shall not constitute an excuse for non-performance.

9.12 Government Supervision of Contractor Employees: The Government will not supervise or otherwise direct contractor employees. The Government will inspect contractor performance in accordance with the Quality Assurance surveillance Plan (QASP) or Management Plan (MP) and any other clauses included in the contract.

9.13 Office Space: The government will provide, and/or make available, administrative office space as described below. Government facilities comply with Occupational Safety and Health Administration (OSHA) work-place standards. Should hazards be identified, the contractor will notify the government in writing, and the government will correct the hazard, taking into account safety and health priorities. Compliance with OSHA and other applicable laws and regulations for the protection of employees is exclusively the obligation of the contractor. The government assumes no liability or responsibility for the contractor's compliance or noncompliance with such responsibilities. The contractor shall not alter or modify the furnished office space without specific written permission from the government.

The contractor shall return all facilities and equipment to the government at the end/termination of the contract. The office space and equipment provided for use in the performance of this contract shall be used only for performance of this contract.

10.0 ENVIRONMENTAL SAFETY AND HEALTH.

10.1 Environmental Requirements. The Contractor shall comply with all applicable federal, state and local environmental statutes, instructions, manuals, handbooks, regulations, guidance, policy letters and rules (including all changes and amendments), and all Presidential Executive Orders in effect on the date of issuance of this contract. The Contractor shall comply with the highest degree of environmental protection where any disagreements exist. For OCONUS work, the Contractor shall also comply with all applicable host nation statutes and agreements. In addition, the Contractor shall comply with the following publications: the DoD Overseas Environmental Baseline Guidance Document (OEBGD) or the Final Governing Standards (FGS), if adopted for a particular location.

10.2 Safety and Health Requirements. The Contractor shall comply with all applicable Occupational Safety and Health Administration (OSHA) and Air Force Occupational Safety and Health (AFOSH) standards, technical orders, regulations and referenced publications both within and outside of the United States. The Contractor shall comply with the highest degree of safety protection where any disagreements exist

APPENDIX A

SERVICES SUMMARY

The Services Summary identifies the performance objectives and performance thresholds for all critical tasks associated with providing the services outlined in this PWS. This section contains only those items considered most important for mission accomplishment. The performance objectives are those services/tasks required in the PWS. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. The thresholds are critical to mission success.

The Government expects the Contractor to perform at the acceptable levels throughout the life of the contract.

Performance Objective

PWS Paragraph

Performance Threshold

Provide qualified people within 30 days of Task Order start

Para 4.1 thru para 4.5.1

Performance is acceptable when

a) qualified personnel are on the job within 30 days of TO Start unless previously negotiated by the

CO

AND

b) the mission is not impacted due to lack of subtask completion or personnel qualifications

Develop and submit all required deliverables

Performance is acceptable when

a) 98% of deliverable requirements are met and received on time

AND

critical information is accurate.

Provide Scheduling Support

Performance is acceptable when:

a) Coordination with all applicable Outside Agencies, Outside Units, and internal Unit Functional Areas is accomplished prior to schedule development.

b) Short and Long Term Schedules are developed in accordance with applicable Air Force Instructions and Unit Leadership Policy.

c) Schedules are published, tracked and amended in accordance with Unit Leadership Policy.

Provide Operations Training Support

a) Coordination with all applicable Outside Agencies, Outside Units, and internal Unit Functional Areas is accomplished prior to Unit Training plan execution.

b) Required Unit Training is accomplished, tracked and reported in accordance with applicable Air Force Instructions and Unit Leadership Policy.

Provide Mission Planning Support

4.5.1.

Performance is acceptable when:

a) Aircrew paperwork and pre-flight materials are correctly prepared and provided for mission planning, such as flight plan, weather, NOTAMs, etc.

b) Short notice changes and updates are accurately completed.

Provide Stan/Eval Support

a) Unit Standardization and Evaluation products are tracked, reviewed, updated and reported in accordance with applicable Air Force Instructions and Unit Leadership Policy.

b) Unit Standardization and Evaluation testing is accomplished in accordance with Air Force Instructions and Unit Leadership Policy

APPENDIX B

WORKLOAD ESTIMATES*

Task

Clearance Required Work Schedule

Number of Personnel

Supported

4.1 Training Secret

M-F

0730 - 1630

50 ARS: 90 personnel 91 ARS: 90 personnel 99 ARS: 130 personnel

4.2 Scheduling Secret

M-F

0730 - 1630

50 ARS: 90 personnel 91 ARS: 90 personnel 99 ARS: 25 personnel

4.3 Mission Planning Secret

M-F

0730 - 1630

50 ARS: 84 personnel 91 ARS: 84 personnel

4.4 Stan/Eval Secret

M-F

0730 - 1630

50 ARS: 84 personnel 91 ARS: 84 personnel

ARS = Air Refueling Squadron

*Appendix B represents a workload estimate for the number of personnel supported. A deviation, either adding or subtracting, from the provided personnel numbers by up to 15% will not warrant an equitable price adjustment for the contractor.

APPENDIX C

OPERATIONS SECURITY

1. Operations Security is a program that protects unclassified yet sensitive information for adversary collection efforts. This sensitive information or critical information (CI) requires protection from potential hostile intelligence collection and exploitation. CI requires protection from inadvertent or unintentional release or exposure to personnel that do not have a valid need-to-know. Any CI that is discovered, found or acquired, must be immediately protected and turned over to either the agency’s security manager, OPSEC representative, or commander/ agency head. The following critical information list identifies specific, critical facts about wing operations and activities that if acquired by adversaries, could accurately assess of our intentions, mission capabilities and limitations, operations, and other activities:

a. Activities concerning current and future operations, exercises, and other sensitive activities.

b. CJCS Alert/Warning Orders, date/time of execution, deployment/routes, staging, and operating locations.

c. Logistical support to an operation.

d. Personal information to include PII of those involved in or supporting an operation.

e. Specific mission nature and objectives.

f. Plan implementation.

g. Implementing Conditions. (i.e., DEFCON, FPCON, INFOCON, weather, etc.)

h. Potential circumstances that generate a particular operation, including planning/execution/reaction times.

i. Generation/alert activities – crews and planes.

j. Deployment/mobility activities.

k. Impact on wing capabilities and limitations.

l. Identity, strength, disposition, readiness, and command relationships of forces involved; (includes personnel/equipment/supplies).

m. Effects of adversary activities and operations.

n. Critical communications and computer systems locations, support, techniques, capabilities and limitations, effectiveness, and outages that support AMC missions.

o. Deception capability, use, and techniques.

p. Exercise participation, results and findings that reveal vulnerabilities and deficiencies.

q. DV/VIP Activities

r. Treaty Activities

s. Base Realignment and Closure (BRAC) Activities. For BRAC-specific CI list, see the 6 AMW Base Realignment and Closure OPSEC Plan.

2. If any papers, documents, notes, etc, that indicate, read, or describe the discovered information or material marked as "For Official Use Only", (FOUO), limited distribution (LIMDIS), Export Restricted under Arms Export Control Act or "Privacy Act", the vendor should contact one of the POC’s listed above and hold and secure the information until it is retrieved. Also, official AF or government forms that do not have the above mentioned marking may contain personal identifiable information (PII) such as full or partial social security numbers, date of birth, home addresses, etc. Examples of these forms are TDY orders and medical forms. This documentation/material must also be held and protected until retrieved by an AF official. If there is any doubt about any the importance of the information that is discovered, surrender it to an AF official.

3. This attachment will accompany all contracting documents. Contact your unit OPSEC Coordinator for additional information.

This procedure will remain in place until further notice.

a. Contractors that discover any papers, documents, notes, etc, that indicate, read, or describe the found information or material as "For Official Use Only" or "Privacy Act" the vendor should contact the unit OPSEC POC and hold and secure the information until it is retrieved. Also, information may have PII such as full or partial SSN's without the caveats such as TDY orders. This documentation/material also needs to be held and protected until retrieved by an AF official.

b. Contractors that work with or that are exposed to FOUO information in the performance of their work must control this information from unauthorized or inadvertent disclosure. Contractors will not discuss or disclose any FOUO information to anyone that does not have a need-to-know. Report the loss of FOUO information to the unit OPSEC POC.

c. Controlled Unclassified Information (CUI) includesU//FOUO, PII, and any other sensitive information. Any CUI that is not required for contractor activities requires protection at all times from inadvertent exposure and collection. Ensure hardcopy and computer screen information containing CUI/FOUO/PII, etc, is protected at all times.

d. Contractors will check all trash receptacles to ensure CUI or classified information is not discarded. Discovery will be reported to the unit’s security manager.