Attach_1_Cyber_Curriculum_PWS_3_May18.pdf

Attachment 1

PR#F2J5358072AW01

3 May 2018

PERFORMANCE WORK STATEMENT

CYBER CURRICULUM DEVELOPMENT

333D TRAINING SQUADRON

KEESLER AFB, MISSISSIPPI

3 MAY 2018

Table of Contents

1. DESCRIPTION OF SERVICES

2. REQUIREMENTS

3. CONTRACT MANAGEMENT:

4. ADDITIONAL INFORMATION

5. SERVICES SUMMARY

6. GOVERNMENT FURNISHED PROPERTY (GFP) AND SERVICES

APPENDIX 1

APPENDIX 2

APPENDIX 3

1. DESCRIPTION OF SERVICES.

1.1. This contract shall provide turnkey cyber operations curricula in support of the 333d Training Squadron

(333 TRS) mission to deliver Cyber Initial Skills Training (IST) by modularizing and updating the 17XX officer and 1B4X1 enlisted cyber operations IST courses (Undergraduate Cyber Training & Cyber Warfare

Operations Apprentice Course, respectively).

1.2. The contractor shall apply the latest research-supported innovations in adult education and training to deliver a collection of training courses featuring interactive team-enabled and mission-focused content.

Courses shall be delivered as flexible “modules” of training covering similar or related subject matter and organized to flow in a logical progression while supporting stand-alone delivery to individualize student learning plans. Course material shall be designed to maximize students’ knowledge and skill retention within the prescribed course lengths.

1.3. Course material shall reflect the current Air Force (AF) and Joint cyber operations environment. The contractor shall incorporate relevant modern and legacy technology as required and appropriate for prescribed training objectives. Additionally, the contractor shall incorporate real-world examples, scenarios and case studies from the AF & Department of Defense (DoD) (e.g. Air Force Space Command, US Cyber Command, 24th Air Force, National Security Agency, etc.).

1.4. Following completion of deliverables, the contractor shall implement the new curricula, train the cadre and assist instructors during the validation of each block (three iterations of each block), per AETC guidance.

1.5. The period of performance shall be up to one year; required milestones are explained below and should be completed within the prescribed phase.

1.5.1. Phase 1: Approximately two months to conduct interviews and preliminary research, establish presence at 333 TRS, gain access to relevant systems, and devise strategy for course modularization.

1.5.1.1. Milestone 1: In coordination with 333 TRS/TRR, contractor shall build a plan for modularization and creation of course.

1.5.1.2. Milestone 2: 333 TRS/CC approves plan for modularization and creation of course blocks.

1.5.2. Phase 2: Approximately six months to create pre-implementation course deliverables

1.5.2.1. Milestone 3: In coordination with 333 TRS/TRR, contractor shall develop deliverables and implementation plan

1.5.2.2. Milestone 4: 333 TRS/CC approves deliverables and implementation plan

1.5.2.3. Milestone 5: Supply new course content to 333 TRS/TRR to be formalized and train 333d cadre on new course material

1.5.3. Phase 3: Approximately four months to implement the course and make adjustments to deliverables

1.5.3.1. Milestone 6: Course implementation and validation complete; 333 TRS cadre qualified on new course blocks

1.5.3.2. Milestone 7: 333 TRS/CC approves final deliverables and final report

1.5.3.3. Milestone 8: Contractors shall train and hand-off artifacts to 333TRS/TDE

2. REQUIREMENTS.

2.1. The contractor shall analyze, plan, design, develop, integrate, modify, update, and deliver the required course material as well as train instructors on all materials to execute the Training Standard (TS) provided in

Appendix 1 & 2. The resulting course material must be executable within existing organizational time, facility, system, and manpower constraints as outlined in Section 3. Currently, both courses are taught in-residence at

Keesler Air Force Base (AFB), see Appendix 1 & 2 for details. Course material developed shall support in-residence and online courses.

2.2. Deliverables: A course Block is a logical subdivision of a previously defined course (e.g., Undergraduate Cyber Training (UCT)). A Module is a self-contained course fragment that may address a single TS, or a collection of very closely related TS, and may be easily utilized in multiple courses or blocks.

All materials shall be provided as modules and shall be easily integrated into Learning Management System

(LMS) agnostic systems as a collection of blocks, ie. Blackboard etc. See Table 1 for required deliverables.

2.2.1. For each module, the contractor shall provide sufficient course content to 333 TRS/TRR for the following course design artifacts as required by Air Education and Training Command Instruction 36-2641 and related guidance memorandums and supplements. It is the 333 TRS/TRR’s responsibility to take the content provided and turn it into the below AETC course design artifacts.

2.2.1.1. Course Chart

2.2.1.2. Measurement Plan

2.2.1.3. Placement Test (consisting of block waiver tests)

2.2.1.4. Block Tests

2.2.1.5. Plan of Instruction Part 1

2.2.1.6. Plan of Instruction Part 2 (Lesson Plan)

2.2.2. Block Requirements: The contractor shall create completely new modules to replace UCT Phase 1, UCT Phase 2, and Cyber Warfare Operations Apprentice Course (CWOAC) course content. These modules may be shared between UCT and CWOAC as appropriate. These logical modules shall be combined into

Blocks, which the 333 TRS/TRR shall combine to formalize into separate Air Education and Training

Command (AETC) courses to replace UCT. CWOAC will maintain its current single-course listing. All performance-based Training Standards shall include interactive multi-media instruction. A minimum of 25% of knowledge-based Training Standards shall include interactive multi-media instruction. Additionally, each block shall include the following:

2.2.2.1. A list of TS items chunked into Blocks for both CWOAC and UCT

2.2.2.2. Block Waiver Test Questions

2.2.2.3. Block Test Questions

2.2.2.4. Module Slides

2.2.2.5. Student Text to support Module’s TS

2.2.2.6. Student Workbook (as necessary)

2.2.2.7. Relevant Case Studies

2.2.2.8. Games

2.2.2.9. Videos

2.2.2.10. Readings

2.2.2.11. Web-Accessible Content

2.2.2.12. Interactive Computer-Based Exercises

2.2.2.13. Online Capable Written and Performance Assessments

2.2.2.14. (Unclassified Material Only): In addition to traditional delivery artifacts, the contractor shall produce comprehensive “Sharable Content Object Reference Model” (SCORM) Package for On-

Demand Learning. SCORM items shall include gamified features such as badges, points, or progress indicators.

2.2.3. Deliverables will be reviewed, coordinated and approved by 333 TRS/TRR prior to submission for 333

TRS/CC for acceptance. Currency of developed content is a critical acceptance factor.

Table 1: Deliverables

Deliverable

Phase Required By: Submit To: For Course

DesignArtifact

Per Course

Consultation on block wise course map

Phase 1 333 TRS/TRR Course Chart

Cyber Skill Placement Evaluation

Metrics

Phase 2 333 TRS/TRR Course Placement Test

Per Block

Consultation on block map with module flow

Phase 2 333 TRS/TRR POI Part I

Interactive & Immersive Evaluation

Metrics

Phase 2 333 TRS/TRR Measurement Plan

Per Module

Interactive & Immersive Training

Content

Phase 2 333 TRS/TRR POI Part I & II

Learner centered exercises Phase 2 333 TRS/TRR POI Part I

Suggested evaluation methods for performance-based TS

Phase 2 333 TRS/TRR Measurement Plan

Interactive Computer-Based

Exercises

Phase 2 333 TRS/TRR POI Part I

Games Phase 2 333 TRS/TRR POI Part I

Instructional Videos Phase 2 333 TRS/TRR POI Part I

Relevant Case Studies or Readings Phase 2 333 TRS/TRR POI Part I

Weekly Activity Report All Phases 333 TRS/TRR N/A

Instructor Module Training Videos Phase 2 333 TRS/TRR N/A

Modular Course Best Practices Phase 2 333 TRS/TRR N/A

Cyber Training Configurations

Guide

Phase 2 333 TRS/TRR N/A

2.2.4. All content students interface with shall be web-accessible and easily incorporated into an LMS. In addition to content posted online, original source files shall be provided in a Microsoft Office, common audio/video or PDF formats and formatted and labeled in accordance with AETCI 36-2641, the Air Force

Handbook 33-337, The Tongue and Quill, 27 May 2015, (to be provided) and the latest 81st Training Wing

Power Point slide template (to be provided) as applicable.

2.2.5. All materials requiring software licenses must include sufficient licenses to sustain projected annual student production numbers (Reference 3.1 & 3.2). The first set of annual licenses will be provided by the contractor and will be transferred to the Government at contract completion.

2.3. Implementation requirements: The contractor shall deliver professional quality video of all course content delivery for instructor training and reference. The contractor shall also provide best practices on how best to manage students and maintain curriculum in the LMS throughout the course lifecycle. Contractors shall assist 333 TRS/TRR throughout the validation process of the completed courses. This includes helping collect validation data, as well as identifying and making corrections to course material and curriculum arrangement as needed in real time. All course development and implementation shall be coordinated with the 333 TRS/TRR.

2.3.1. The contractor shall design, implement, and test a system of enrollment to manage student progress through “Modular” courses to include support for scheduling students to complete one, some, or all of the required modules. The contractor shall also train 333 TRS personnel in these functions.

2.4. Additional content development requirements: Content types as outlined under Section 2.2 must lead students to the TS's proficiency level and objectives outlined in Appendix 1 & 2. Contractor shall use the best available newly created content by the contractor as well as existing commercial and governmental resources.

Content must comply with the Air Education and Training Command Instruction 36-2648, Technical and

Basic Military Training Distance Learning, Interactive Multimedia Instruction and Blended Learning, dated

23 January 2017 and the Americans with Disabilities Act Section 508 Accessibility Requirements. The contractor shall utilize the Instructional System Design (ISD) Process, Analyze, Design, Develop, Implement, and Evaluate (ADDIE) Model, and Bloom’s Taxonomy for all course content creation.

2.4.1. Content must reflect current DoD cyber operations capabilities, Air Force, Joint Information

Environment, and DoD network architectures, and contain industry best practices set by federal and international standards organizations (NIST, IEEE).

2.4.2. Content shall leverage open sourced content freely available to the US Government, the Department of

Defense, and the United States Air Force to the greatest extent possible. Examples include FedVTE, AF E-

Learning, EdX, TED, and training lessons learned and after-action reports from operational cyber units.

2.4.3. Content should cover foundational and historical concepts where necessary to put modern technology and challenges in cyberspace in context. Include Functional Mission Analysis concepts and examples throughout course as appropriate.

2.4.4. A block shall be built to deliver COMPTIA Security + certification training for the most current version of the certification. Testing of the exam will be handled by the 333 TRS.

2.4.5. The resultant courses shall include turnkey LMS-agnostic SCORM packages supporting unclassified modules. SCORM modules shall be robust enough for students to independently engage the content on demand and achieve acceptable levels of comprehension for their intended objectives. All SCORM modules shall be compatible with the current AF Standard Desktop Configurations.

2.4.6. Development need not occur entirely at Keesler Air Force Base. However, we require the contractor maintain a full-time presence at 333 TRS (Stennis Hall) with space provided by the 333 TRS. At a minimum, the assigned Program Manager (PM) and at least one Subject Matter Expert (SME) shall be present at Keesler

Air Force Base for the entire period of performance. Off site development of any classified material must occur within facilities approved by the 81st Training Wing SSO via a DD 254. The 81st Training Wing will not sponsor the contractor’s secured facilities.

2.4.7. All deliverables will become US Air Force property upon delivery. The Government is requesting

Government Purpose Rights with the following additional information. All deliverables outlined in Section

2.2.3. must include copyright releases as applicable. All deliverables must be easily modifiable by the customer. For example, documents delivered in portable document format (PDF) must also be delivered in a format modifiable by applications on the AF Standard Desktop (e.g., Microsoft Word). Software and other courseware (e.g., SCORM packages) must include thorough maintenance documentation and applicable rights to enable updates, changes, modifications, and maintenance by the Government users and may be used in future contract requirements. The contractor must state the rights associated with each software and courseware deliverable in their proposal and upon delivery IAW FAR 27.404.

2.4.8. The contractor shall create exercises, which students will accomplish within the 333 TRS cyber operations training range (“COTR”) enclave. The contractor shall perform in-depth research to design realistic and operationally relevant virtual ranges and training exercises that accomplish prescribed Training

Standards. The contractor shall create and deliver configuration documentation for these range designs/configurations and provide training to 333 TRS personnel on the operation and execution of these training exercises.

2.4.9. Waiver tests must assess skills at the proficiency levels indicated in the TSs (Appendix 1 & 2). These tests must be web-based and constructed in a way to readily assess student proficiency by subject area and provide immediate, graphic feedback to the student showing what they attained and what they did not, with clear hypertext or other graphic links to those subject areas. The tests must be modifiable by 333 TRS staff and should incorporate best practices to prevent test compromise.

2.4.10. Software-based training practice, exercises, and operational scenarios must operate in either self-contained software packages or in the schoolhouse’s virtualized environment. Data and configuration, as well as instructions for system administrators, instructors, and students must be provided.

3. CONTRACT MANAGEMENT:

3.1. The contractor shall provide a face-to-face weekly status update briefing to 333 TRS/TRR, reviewing addressing areas of progress, projected timelines/changes, and areas of concern. The contractor or government may schedule additional formal or informal meetings during duty hours to discuss progress, review deliverables, clarify tasks, address any issues, and review contract status. Additionally:

3.2. The contractor shall identify one primary on-site Program Manager (PM) and one alternate on-site PM as key personnel. The PM is responsible for the overall management of contractor personnel and all contractual issues and is the primary interface between the Government and the contractor. These individuals shall have full contractor authority to act in all contract matters and be responsible and accountable to the Contracting

Officer (CO) in representing the contractor for meeting the performance requirements of this PWS. The PMs shall be available during normal business hours to meet with the Contracting Officer Representative (COR) or

Government team lead to discuss program and/or technical issues. The PM shall attend meetings, as requested by the COR. PMs shall be the daily interface; therefore, PMs must have ongoing knowledge of daily activities within each work section. The PM shall provide accountability of all employees to the

COR/Government team leads no later than 0800L each duty day in a manner prescribed by the government.

The PM is responsible for submitting a weekly summary report. The PM shall ensure that contractor personnel perform daily activities as coordinated with the PM in support of basic office hygiene and maintenance.

3.2.1. In addition to a weekly status update briefing, the PM shall deliver a written weekly activity report addressing areas of progress, projected timelines/changes, and areas of concern. The PM shall document labor hours expended by contractor personnel for the government’s reference and subsequent use in calculating development/maintenance workload. There is no specific weekly (or total) labor input expectation beyond the presence required in section 2.4.6.

3.2.2. The PM shall ensure that contractor (and any sub-contractor) personnel comply with all applicable

DoD, Air Force, and local regulations.

3.3. The contractor shall be responsible for any subcontract management necessary to integrate work performed on this requirement and shall be responsible and accountable for subcontractor performance to the standards levied on the prime contractor herein.

3.4. The contractor shall not employ any person for work on this contract if such employment is identified to the contractor by the CO as a potential threat to the health, safety, security, general well-being, or maintenance mission of the installation and its population. All contractor employees shall be able to read, write, speak and understand the English language to the extent necessary in the performance of the work.

3.5. While working on Keesler AFB contractor employees shall identify themselves as contractor personnel by introducing themselves or being introduced as contractor personnel and displaying distinguishing badges or other visible identification for meetings with Government personnel. In addition, contractor personnel shall appropriately identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence.

3.6. Contractor’s attire shall be business casual. The CO may allow flexibility for this requirement.

Contractor personnel shall present a clean and neat appearance. Contractor shall not permit cut off shorts and clothing with tears, faddish style, revealing/tight clothing or clothing with obscene or inflammatory designs, slogans, or remarks, and clothing representing current or past military attire. The contractor PM/site leads shall ensure personnel wear appropriate clothes suited for their job.

3.7. The contractor shall ensure all employees possess a valid civilian driver’s license.

3.8. The contractor shall ensure all employees submit to drug testing as required by the Government.

3.9. The COR will work with the PM to ensure contractor personnel will be issued a Common Access Card

(CAC). The CAC is required to access any Government base and certain facilities. Contractor personnel indoctrinated for Sensitive Compartmented Information (SCI) access shall be identified by a locally produced

Badge, visible and worn above the belt and below the shoulders when present within the SCI Facility (SCIF).

When exiting the SCIF, contractor personnel shall conceal their credentials from plain view and keep said credentials secure when not inside the SCIF.

3.10. Any travel deemed necessary in the completion of this contract shall be planned and accomplished by the contractor at the contractor’s expense. Government resources are not available to support or coordinate business travel.

3.11. Special Qualifications of Contractor Personnel: Contractor personnel must have expertise and currency in the areas identified by each course’s TSs. Additionally, the following are offered to enhance and clarify both contractor qualifications and course content:

Expertise in Online Course Development and Delivery in common LMS platforms, as exemplified in paragraph 2.2.3. & 2.2.4.

Expertise in current and recent versions of Windows, Linux, and VMWare.

Expertise in Data Network design and configurations (Cisco, Avaya, and Juniper references).

Expertise in Network Security principles & traffic analysis.

Expertise in data and packet forensics.

Expertise in Scripting and Applications in Linux/Windows and their shell environments.

Expertise in Program Languages: Python, Perl, and C.

Expertise in Air Force and DODIN operations.

Expertise in Air Force and DOD Defensive Cyber Operations.

Expertise in Air Force and DOD Offensive Cyber Operations.

Expertise in Cyber Mission Planning, Briefing, Execution and Debriefing.

Expertise in Air Force cyber weapons systems.

Expertise in Air Force cyber organizations, roles and responsibilities.

Expertise in Tactical Datalink concepts and architectures.

Expertise in Industrial Control System concepts and architectures.

Expertise in Telephony and VoIP concepts and architectures.

Expertise in Telecommunication and radio frequency principles and management.

Knowledgeable in procedures as described in AETCI 36-2641 and any supplements.

3.12. All contractor personnel working on courseware or exercises requiring access to SCI or access to the

SCIF will require a TS/SCI clearance. The government will not authorize access to the SCIF or escort non-cleared personnel. At a minimum, at least one of the onsite personnel shall be available with TS/SCI clearance. The government will issue a DD254 and sponsor SI//TK read-ins to facilitate production of this material or to have the contractor view the material in order to formulate a plan to reduce the material to the unclassified level. See 4.10 Security.

4. ADDITIONAL INFORMATION.

4.1. Each classroom will have student workstations (defined below), an instructor workstation (same systems as the student), an overhead projector and a reasonable amount of desktop/tabletop space for taking hardcopy, paper notes and/or use of hardcopy books and reference materials. Classrooms vary in size, location and capability to support classified instruction/discussion. The contractor must deliver a course supported within existing facility constraints:

4.1.1. (13) Thirteen classified 12-person classrooms.

4.1.2. (12) Twelve classified 16-person classrooms.

4.1.3. (10) Ten unclassified 18-person classrooms.

4.1.4. (2) Two Classified Auditoriums for approximately 80 students.

4.2. Classrooms are equipped with a mixture of AF NIPRNet, AF JWICS, and local COTR systems. The training range provides access to a variety of virtualized systems, customizable (to a degree) to meet course requirements.

4.3. UCT Phase 2 and CWOAC contain or are anticipated to contain Top Secret//SI/TK// information.

However, this is not an absolute requirement, and no classified information will exist in the LMS. For efficient utilization of classified training space, reasonable attempts to reduce classified content and/or logically group such content should be made. However, training requirements and review of classified lessons learned and case studies should not be excluded in favor of training time or space utilization.

4.4. The 333 TRS operates on a 9/80 schedule where 80 hours are worked over 9 days. Week one hours are

Monday to Thursday 0700-1700, Friday 0700-1600. Week two is Monday to Thursday, 0700-1700. No work on Federal Holidays. The 333d Training Squadron will make a good faith effort to provide two weeks' notice for any deviations from the schedule outlined above.

4.5. Emergency Services: The Government does not require emergency or after hours support during the performance of this contract.

4.6. Special Prohibitions: Removing objects from refuse for personal use is unauthorized. Contractor

Personnel may request items through unit designee. Violations are grounds for termination. At no time, without authorization, will Contractor Personnel purchase any items from the local economy for any US

Personnel.

4.7. Standards of Conduct: Contractor Personnel must adhere to standards of conduct as established by the

Installation Commander and AETCI 36-2909 (as amended) to include office business professional attire, respectful and courteous behavior, withholding of profanity and slander to the organization, the military services, the Department of Defense and the United States of America.

4.7.1. Contractors shall comply with AETCI 36-2909, Recruiting, Education, Accessions, and Training

Standards of Conduct, and shall take immediate action to resolve violations of the prohibition on unprofessional relationships. Specifically, the following:

4.7.2. Unprofessional relationships include relationships involving recruiters, instructors, staff, applicants, recruits, trainees, cadets, students (to include international military students), and Airmen who participate in the Recruiter Assistance Program (RAP). Whether pursued on-duty or off-duty, relationships are unprofessional when they detract from the authority of superiors or result in (or reasonably create the appearance of) favoritism, misuse of office or position, or the abandonment of organizational goals for personal interests. Unprofessional relationships include relationships between officers; between enlisted members; between officers and enlisted members; between recruiters and recruits, applicants, or RAP participants; between RAP participants and recruits or applicants; and between military personnel and civilian employees or contractor personnel. Violations shall be communicated to the CO and the COR within 48 hours with corrective actions taken.

4.8. SECURITY REQUIREMENTS. All Contractor Personnel employed by the Contractor in the performance of this contract, or any representative of the Contractor entering the Government installation, shall abide by all security regulations of the installation (i.e., 81 TRW Plan 31-101, Integrated Defense, or

AFI 31-101, Integrated Defense.). The Contractor shall sign an agreement stipulating the security requirements of this contract.

4.8.1. Base Access. The Contractor shall obtain personal identification passes for all Contractor Personnel and vehicle passes for all Contractor Personnel’s personal vehicles, to include prospective Contractor

Personnel, requiring entry onto KAFB. Additionally, the Contractor shall keep current, for Government inspection, a list of the names of Contractor Personnel employed on this contract. Contractor Personnel shall complete Keesler AFB Form 299, Application for KAFB Identification Card, and submit it through the CO to the Security Forces and Pass and Registration. Vehicle registration, proof of insurance, and a valid driver’s license must be presented for all vehicles to be registered.

4.8.2. Pass and Identification Requirements. Contractor Personnel whose duties require access to KAFB computer system are required to obtain a Common Access Card (CAC). To obtain a CAC, Contractor

Personnel shall coordinate with their gaining unit’s security manager or the 81st Communications Squadron

Consolidated Client Support Activity (CSA) at 228-376-4335.

4.8.2.1. Applicability.

a. These requirements apply to Contractor Personnel requiring entry/access to KAFB for service contracts with periods of performance (POP) exceeding 60 days when a CAC is not issued.

(1) Contract POP begins at performance start date. The POP end date is based on the contract completion date.

(2) These requirements shall be included (flow down) to subcontracts at every tier.

b. These requirements do not apply to Contractor Personnel requiring entry/access to KAFB with a POP of 60 days or less. Entry/Access to KAFB for Contractor Personnel with a POP of 60 days or less will be coordinated between the Contractor and the 81st Security Forces Squadron (81 SFS).

c. When work under this contract requires unescorted entry to controlled or restricted areas, the

Contractor shall comply with AFI 31-101, Integrated Defense, 8 Oct 09, and AFI 31-501, Personnel Security

Program Management, 27 Jan 05, as applicable.

d. Contractor Personnel are not covered by Federal Acquisition Regulation (FAR) 52.222-3, Convict

Labor, for the purposes of entry/access to installations/locations.

4.8.2.2. Badging System Data Requirements.

a. The Contractor shall provide the following to the Contracting Office:

(1) “Listing of personnel requiring access/entry.” The list shall contain the following:

(a) Contract number.

(b) Contract award date.

(c) POP dates.

(d) Work site(s) or location(s).

(e) Each employee’s full name and Social Security Number (SSN). For those without SSNs, a working visa or Permanent Resident Card with a Resident Alien number must be provided, or base entry will be denied.

(f) Identify up to two (2) Contractor Personnel for designation as “sponsor” authorities.

Badges will identify the Contractor Personnel with sponsorship privileges.

(2) Completed KAFB Form 299 shall authorize Security Forces to fingerprint Contractor Personnel and conduct additional background checks. The consent form will outline the following:

(a) The Contractor Personnel for the purpose of the KAFB Form 299.

(b) The information on the form is collected IAW 18 U.S.C. 1382 and DoD Directive 5200.8, both of which permit installation commanders to limit access to installations for security reasons.

(c) Completion of the form is voluntary.

(d) Agreement to provide a specimen of fingerprints.

(e) Awareness of a list of “disqualifying factors.”

(f) Consent and authorization for Security Forces to conduct background screening and to compare fingerprints against State and Federal criminal databases.

(g) Knowing and willful false statements on the form can be punished by a fine, imprisonment, or both (10 U.S.C. 1001).

(h) The consent form shall remain valid for 24 months after the end of the contract.

b. The Contractor Personnel list and consent form(s) shall be submitted as follows:

(1) 81 SFS/PASS & ID e-mail account: 81 sfs.pass.id@us.af.mil. Personnel list must be submitted

IAW the PWS. The signed KAFB Form 299 must be submitted in person to the 81 SFS/PASS & ID office.

(2) Refer questions regarding the Contractor Personnel list and KAFB Form 299 to 81 SFS/PASS

& ID at 228-377-1845 or 228-377-3844.

4.8.2.3. Background Checks.

4.8.2.3.1. Upon receipt of the KAFB Form 299 with a copy of Driver’s License and Social Security card, a background check will be accomplished. Background checks will be categorized as favorable or unfavorable.

Unfavorable background checks contain any one of the “disqualifying factors.” Any person with an unfavorable background check will be denied entry/access to the installation.

4.8.2.3.2. “Disqualifying factors” include:

a. Barred from entry/access to any military installation or facility.

b. Wanted by federal or civil law enforcement authorities.

c. Name appears on any federal agencies “watch list” or “hit list” for criminal behavior or terrorist activity.

d. Conviction of firearms or explosives violation within the past seven (7) years.

e. Incarcerated regardless of offense or violation.

f. Conviction of aggravated assault, armed robbery, felony drug possession, drug possession with intent to sell, or drug distribution within the past seven (7) years.

g. Conviction of espionage, sabotage, treason, terrorism, murder, sexual assault, rape, or child molestation.

h. Terrorist or terroristic threats or repetitive history of criminal history.

i. Currently serving parole or probation for a felony case.

j. U.S. citizenship, immigration status, or Social Security Account Number cannot be verified.

4.8.2.3.3. An unfavorable background check/denial may be appealed through the 81 SFS/PASS & ID. The appeal shall include a signed letter of rebuttal and any associated supporting documentation to the 81

SFS/PASS & ID.

mailto:81%20sfs.pass.id@us.af.mil

4.8.2.3.4. Given a reasonable cause, condition, or reason, these requirements do not circumvent the installation/location commander’s unilateral authority to deny or withdraw any individual’s entry/access to an installation/location.

4.8.2.3.5. Badge and Fingerprint Schedule. 81 SFS/Pass & ID will notify the Contractor upon completion of background checks. Badging and fingerprinting shall be scheduled by contacting the

Contractor by phone. Contractor Personnel shall report to the 81 SFS/Pass & ID with a photo ID issued by a federal/state organization (i.e. Driver’s License, State ID card, U.S. Passport, etc.). IAW the Real ID Act, Individuals will no longer be able to access Air Force installations with a state-issued identification card or driver's license from Minnesota, Missouri, Washington or American Samoa beginning 15 Aug 2016. If no approved photo ID is shown, a badge will not be issued.

4.8.2.3.6. Change in Employee Entry/Access Status (Deletions).

a. No later than five (5) workdays after a change in status for Contractor Personnel requiring entry/access, the Contractor shall return identified badges to the 81 SFS/Pass & ID.

b. The Contractor shall notify the Contractor Personnel of their change in status for entry/access.

c. Unfavorable fingerprints shall constitute immediate deactivation of the issued badge(s) to the disqualified Contractor Personnel.

(1) 81 SFS may confiscate badge(s) of the Contractor Personnel present on base at the time of the unfavorable result notification. 81 SFS may escort the Contractor Personnel from KAFB IAW Security

Forces guidelines.

(2) 81 SFS/Pass &ID shall notify Contractor of an unfavorable fingerprint result and request the

Contractor to return the badge IAW this PWS (unless already confiscated).

4.8.2.3.7. Badge Loss/Replacement.

a. Contractor Personnel requiring a replacement badge shall contact the 81 SFS/Pass &ID at 228-377-

3844 to schedule a badge appointment.

b. Lost badge(s) require a signed letter from the Contractor and Contractor Personnel that lost the badge requesting replacement of badge(s) due to loss or damage.

4.8.2.3.8. Contract Completion, Return of Badges. No later than five workdays after contract completion, the Contractor shall return all badges to 81 SFS/Pass & ID. All badges are returned collectively by the

Contractor, not incrementally/individually by the Contractor Personnel. The badge turn-in shall identify the contract name.

4.9. RECORDS. The Contractor shall create, maintain, and provide Government-owned/Contractor-held records, regardless of media, in performance of this contract IAW the following directives:

AFI 33-322, Records Management Program, 4 Jun 12, Incorporating Change 2, 25 May 17, AFGM

2018-01, 26 Apr 18, and Keesler AFBGM2017-01, 31 Oct 17

AFMAN 33-363, Management of Records, 1 Mar 08; Incorporating Change 2, 9 Jun 16, AFGM2017-

01, 2 Jun 17, and Keesler AFBGM2018-01, 12 Feb 18

AFI 33-364, Records Disposition—Procedures and Responsibilities, 22 Dec 06, Incorporating Change

1, 6 Nov 14 and AFGM2017-01, 25 May 17

Air Force Information Management System database (AFRIMS) (access through the Air Force Portal at https://www.my.af.mil/afrims/afrims/afrims/rims.cfm)

Air Force Electronic Records Management Solution http://www.e-publishing.af.mil/shared/media/epubs/AFI33-322.pdf http://www.e-publishing.af.mil/shared/media/epubs/AFMAN33-363.pdf http://www.e-publishing.af.mil/shared/media/epubs/AFMAN33-363.pdf https://www.my.af.mil/afrims/afrims/afrims/rims.cfm

4.9.1. The Contractor shall segregate the Government-owned records from the Contractor-owned records and identify all records required to be created by the PWS on the AFRIMS records inventory. The Contractor shall create and maintain paper and electronic records (\\52mahg-fs-106) as appropriate. The Contractor shall maintain the software and background data to retrieve official electronic Government records throughout the lifecycle of the records.

4.9.2. The Contractor maintains and disposes of records IAW the AF records disposition schedules.

4.9.3. Electronically Stored Information (ESI). The Contractor shall maintain Government owned electronic non-official records on the organizational shared network drive according to subjective categories (example:

template, common, reference material, and working files). The Contractor shall grant the base records manager access to all files located on the organizational shared network drive. The Contractor shall maintain the official electronic records on the base designated shared network drive (\\52mahg-fs-106) IAW the Air Force Electronic

Records Management System and AFMAN 33-363, Chapter 6.

4.9.4. Upon completion of this contract, all Government-owned/Contractor-held records (regardless of media) received, created, maintained, or provided in the performance of the PWS shall be turned over to the

Government. Background electronic data and records specified for delivery to the contracting agency must be accompanied by sufficient technical documentation and software to permit the Air Force to use the data. In the event of default or non-performance, the Government will have access to all records in order to ensure mission support is not interrupted.

4.9.5. Contractor-Owned Records. The Contractor shall maintain records that relate exclusively to the

Contractor’s internal business or are of a general nature not specifically related the performance of work under the contract separately from the Government-owned records.

4.9.6. Freedom of Information Act (FOIA) Program. The Contractor shall comply with the requirements of

DoD 5400.7/AFMAN 33-302, Freedom of Information Act Program, 27 Apr 18. If the Contractor receives a

FOIA request, the Contractor shall ensure it is delivered immediately to the base FOIA manager (81

CS/SCOK) for processing. The FOIA manager will task a Government official who, as the authorized official, will make the decision on releasing Government records.

4.9.7. Privacy Act Program. The Contractor shall create, maintain, and destroy Privacy Act data IAW AFI

33-332, The Air Force Privacy and Civil Liberties Program, 12 Jan 15, Incorporating change 1, 17 Nov 16;

and Privacy Act systems of records notice(s) (http://dpcld.defense.gov/Privacy/SORNs.aspx). The Contractor shall not create or maintain a Privacy Act system of records prior to public notice. If the Contractor receives a

Privacy Act request, the Contractor shall be responsible for searching for the records and providing those records to a Government official who, as the authorized official, will make the decision on releasing the

Government records.

4.9.8. Functional Requests. A functional request is a written request for DOD records received from any person (including a member of the public), or a business that does not cite either the FOIA or Privacy Act.

The Contractor shall be responsible for searching for the records and providing those records to a Government official who, as the authorized official, will make the decision on releasing the Government records.

4.10. SECURITY:

4.10.1. Security Clearance: National Agency Check with Written Inquiries (TIER 1). As a minimum, Contractor personnel shall successfully complete a Tier 1 before operating Government-furnished workstations that have access to AF automated information systems. Requests for Contractor personnel hired at the beginning of the contract shall be submitted to the Government not later than 45 workdays from the contract start date. Requests for Contractor personnel hired subsequent to contract start date shall be submitted to the Government not later than 10 workdays from the Contractor personnel’s first duty day.

Contractor personnel receiving unfavorable Tier 1’s shall not be employed. The Government will submit requests for investigations on AF IMT 2583, Request for Personnel Security Action, at no additional cost to the Contractor. Any personnel with access to classified material will be submitted by the Contractor’s

Facility Security Officer (FSO) for a Secret security clearance. The Contractor shall comply with the requirements of DOD 5200.2-R, Personnel Security Program; AFI 31-501, Personnel Security Program

Management, 25 Jan 05; and AFMAN 33-152, User Responsibilities and Guidance for Information Systems, 1 Jun 12.

4.10.2. Contractor personnel shall comply with the requirements of AFI 71-101, Volume 1, Criminal

Investigations, 4 Feb 15 and AFI 71-101, Volume 2, Protective Service Matters, 23 Jan 15. These regulations require Contractor personnel to report any information or circumstances of which they are aware that may pose a threat to the security of DoD personnel, Contractor personnel, resources, and classified or unclassified

Defense information to their immediate supervisor. The immediate supervisor of Contractor personnel shall brief on this requirement during initial on-base assignment and as required thereafter.

4.10.3. The Unit Security Manager will assist the Contractor with any Joint Personnel Adjudication System

(JPAS) Joint Clearance and Access Verification System (JCAVS) and eQIP by Design information for inputting Tier 1’s with assistance from 81 TRW/IP.

4.10.4. Security Monitoring: The Contractor shall comply with all security requirements. Submit reports, classified if appropriate, of any information coming to their attention concerning any of their employees who have been cleared or are in the process of being cleared for access to classified information, which indicates that such access or determination may not be clearly consistent with the national interest. Reports shall be submitted to the Defense Industrial Security Clearance Office (DISCO) immediately upon notification of any adverse information, change in employee’s status, official investigation, or any other reason. In addition, a copy of this report shall be furnished to the Contracting Officer’s Representative(s) (COR(s)) and 81 TRW

Installation Commander (81 TRW/CC).

4.10.5. Listing of Employees: The Contractor shall maintain a current listing of all Contractor personnel.

The list shall include Contractor personnel’s names, Social Security numbers, and level of security clearance.

The list will be validated and signed by the FSO and provided to the CO, COR, Base Visual Information

Manager (BVIM), 81 TRW/IP, Unit Security Manager, and FSO prior to the contract start date. Updated listings shall be provided when a Contractor personnel’s status or information changes. Documents will be marked as FOUO as a minimum.

4.11. PHYSICAL SECURITY: The Contractor shall safeguard all Government property, including controlled forms provided for Contractor use. At the close of each work period, Government equipment, facilities, and other valuable materials shall be secured.

4.11.1. Entry Procedures to Controlled/Restricted Areas: The Contractor shall implement local base procedures for entry to AF controlled/restricted areas where Contractor will work. Off site development of any classified material must occur within facilities approved by the 81st Training Wing SSO via a DD 254.

The 81st Training Wing will not sponsor the contractor’s secured facilities.

4.12. OPERATIONAL SECURITY (OPSEC):

4.12.1. OPSEC Training:

4.12.1.1. All OPSEC training shall be provided by the 333 TRS OPEC Managers.

4.12.1.2. All Contractor personnel and Contractor Management Staff shall complete initial OPSEC training within 30 calendar days of reporting for duty.

4.12.1.3. All Contractor personnel and Contractor Management Staff shall complete annual refresher

OPSEC Awareness Training.

4.12.2. Disclosure of Information:

4.12.2.1. Contractor personnel or Contract Management Staff shall not release any unclassified information to anyone outside the Contractor’s organization. Unclassified information, regardless of medium (e.g., film, tape, document), pertaining to the execution of any part of this contract or any program related to this contract shall not be released unless:

4.12.2.1.1. The CO, the squadron Commander, or OPSEC Coordinator has given prior written approval; or the information is otherwise in the public domain before the date of release.

4.12.2.2. Requests for authorization to release information shall identify the specific information to be released, the medium to be used, and the purpose for the release.

4.12.2.2.1. The Contractor shall submit the request to the CO, the squadron Commander, or

OPSEC Coordinator at least 45 days prior to the proposed release date.

4.12.2.2.2. Contract Management Staff shall submit requests through the prime Contractor to the CO, Squadron Commander, or OPSEC Coordinator.

4.13. LEVEL I ANTI-TERRORISM (AT) AWARENESS: Level I Anti-Terrorism (AT) Awareness

Training is available upon request and will be conducted by the Installation Anti-Terrorism Officer (ATO).

Contact the 81st Security Forces Squadron (81 SFS/S2AT), at 228-376-6613.

4.14. SAFETY

4.14.1. Obligations: Contractors shall comply with the Occupational Safety and Health Act (OSHA, Public

Law 91-596) and the resulting standards, OSHA Standards 29 CFR 1910 and 1926. The detailed provisions of the act for accident prevention are directly applicable to all Contractor operations. Contractors shall comply with applicable AFI 91-203 Air Force Consolidated Occupational Safety Instructions. Prime

Contractors are also responsible for ensuring any sub-contractors also adhere to OSHA Guidance. OSHA compliance officers visit Contractor worksites on the installation.

4.14.2. Responsibilities: Following is a list of responsibilities for Contracting, Contractor, and Wing Safety personnel.

4.14.2.1. Contractor Responsibilities.

4.14.2.1.1. Contractors are responsible for ensuring all industrial safety provisions are followed.

4.14.2.1.2. Contractors must report all accidents involving Air Force people, property, or equipment damage, and any Contractor personnel injured in the performance of the

Air Force contract to the CO.

4.14.2.1.3. Take immediate corrective action to comply with safety regulations if informed of a violation by the CO.

4.14.2.2. Contracting Officer (CO) Responsibilities:

4.14.2.2.1. Inform Contractor of non-compliance with safety regulations, which may c ause injury to Air Force personnel or property.

4.14.2.2.2. Notify Wing Safety of any injuries or damage to AF property reported by the Contractor, in performance of an Air Force contract.

4.14.2.3. Wing Safety Responsibilities.

4.14.2.3.1. 81st Training Wing Safety Personnel will periodically monitor Contractor operations to ensure safety regulation compliance as it applies to Air Force personnel and equipment.

4.14.2.3.2. Wing Safety personnel are available to the CO for technical assistance on matters pertaining to accident prevention.

4.14.2.3.3. Notify the CO if a safety procedure or condition exists which requires correction by the Contractor.

4.15.3. Safety Rules: Contractors shall pay particular attention to the following safety rules and ensure strict compliance while on the installation.

4.15.3.1. General Safety Rules While on the Installation.

4.15.3.1.1. Ensure adequate lighting and barricading is available and used for day and night operations.

4.15.3.1.2. Use proper shoring during trenching operations.

4.15.3.1.3. Post proper warning signs at indoor and outdoor operations.

4.15.3.1.4. Secure materials when doing high work, during high winds, or when high winds are forecasted.

4.15.3.1.5. Use warning signs, barricades, or flagmen when operations present a hazard to drivers, pedestrians, or workers.

4.15.3.2. Traffic Rules While on the Installation. All drivers, mobile equipment, and vehicles must comply with applicable federal, state, and local laws.

4.15.3.2.1. Seat belts are mandatory for all passengers as well as drivers

4.15.3.2.2. An approved bicycle helmet is required to be properly worn while riding bicycles on the installation.

4.15.3.2.3. Drive the speed limit:

4.15.3.2.3.1. Base proper speed limit is 25 mph or as posted.

4.15.3.2.3.2. Housing area speed limit is 15 mph.

4.15.3.2.3.3. Parking lot speed limit is 5 mph.

4.15.3.2.4. Give full attention to the operation of the vehicle. Do not operate any form of electronic device while driving to include cellular phones, iPads, laptops, etc. Mobile electronic devices are only allowed to be utilized while driving if equipped with a hands-free option such as Bluetooth.

4.15.3.2.5. Park in designated areas and IAW Keesler AFB Instruction (KAFBI) 31-218, Installation Traffic Code.

4.15.3.2.6. No riding in the beds of trucks, buckets of front end loaders, or tandem riding on vehicles designed for one-person operation.

4.15.3.2.7. Use safety chains in addition to towing hooks when towing equipment.

4.15.3.2.8. Place a light on the rear of equipment being towed during the hours of darkness.

4.15.3.2.9. Mark overhanging portions of loads with warning flags or lights.

4.15.3.2.10. When driving or using a crane or cherry picker, be cautious around power lines crossing the road and don't position booms closer than 10 feet to overhead high voltage lines.

4.15.3.2.11. Ensure electrical work is IAW the National Electric Code.

4.15.3.2.12. Upon encountering troop formations on the installation:

4.15.3.2.12.1. Maintain 50-foot distance behind formations until signaled to pass by the troop commander. When signed to pass troop formation, do not exceed 10 mph while passing.

4.15.3.2.12.2. When passing from the front, proceed without stopping, but slow to 10 mph while passing.

4.16. SMOKING IN AETC FACILITIES: Contractors are advised that the Commander has placed restrictions on the smoking of tobacco products in AETC facilities. AFI 40-102, Tobacco Free Living, 4 Mar

15, outline the procedures used by the commander to control smoking in our facilities. Contractors and visitors are subject to the same restrictions as Government personnel. Smoking is permitted only in designated smoking areas.

4.17. ENVIRONMENTAL MANAGEMENT SYSTEM (EMS): All Contractor personnel shall complete

Environmental Management System (EMS) Awareness training prior to commencement of any activities.

Training is available through the Air Force Advanced Distributed Learning Service (ADLS), the

Environmental Awareness Course Hub (TEACH), or through the Environmental Office (KBOS/CEV).

4.18. HAZARDOUS MATERIALS: In the event that hazardous materials will be used in the execution of this contract, the Contractor shall be required to obtain authorization from the Installation Hazardous

Materials Management Program before ordering or purchasing the hazardous product, IAW AFI 32-7086, Hazardous Materials Management, 2 Feb 15.