Attachment 6 - PWS CDSS III - Final 27 Oct 21.pdf

Air Education & Training Command (AETC) Air Force Special Warfare and Combat Support

Performance Work Statement (PWS) for

Candidate Development Support Services (CDSS) III

27 Oct 2021

TABLE OF CONTENTS

SECTION 1 - DESCRIPTION OF SERVICES

1.1. SCOPE OF WORK

1.2. CONTRACTED PROGRAM MANAGER/DEPUTY PROGRAM MANAGER

1.3. REGIONAL LEAD FIELD DEVELOPER

1.4. PRE-ACCESSION DEVELOPMENT

1.5. POST-ACCESSION DEVELOPMENT

1.6. VOLUME OF WORK

1.7. VOLUME OF WORK BY WING DEVELOPER (WD) TRAINING LOCATION

1.8. PERIOD OF PERFORMANCE

1.9. PLACE OF PERFORMANCE

1.10. TYPE OF CONTRACT

1.11. OTHER DIRECT COSTS

1.12. WORK SCHEDULE

1.13. FEDERAL HOLIDAY’S

SECTION 2 - Definitions and Acronyms

SECTION 3 - QUALITY ASSURANCE

3.1. QUALITY ASSURANCE

3.1.1. QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

3.1.2. DEFICIENCES

3.1.3. CONTRACT DISCREPANCY REPORT (CDR)

3.1.4. PROGRMAN MANAGEMENT REVIEW (PMR)

3.1.5. QUALITY CONTROL

3.1.6. QUALITY CONTROL PLAN (QCP)

SECTION 4 - CONTRACT REQUIREMENTS

4.1. DESCRIPTION OF DUTIES

4.2. DELIVERABLES

SECTION 5 - ACCOUNTING FOR PROGRESS

SECTION 6 – PHASE-IN/PHASE-OUT

SECTION 7 - PERSONNEL QUALIFICATIONS

SECTION 8. GENERAL INFORMATION

8.20. POST–AWARD

8.20.1. POST-AWARD MEETING

8.21.1. SERVICES SUMMARY (SS)

Table 4: SERVICES SUMMARY - MEASUREABLE TERMS ATTACHMENT 1: AIR FORCE SPECIAL WARFARE/SERE/EOD Physical Ability and Stamina Test (PAST) WORKSHEET

ATTACHMENT 2: PERSONAL TRAINER CERTIFICATION

ATTACHMENT 3. SAMPLE LESSON PLAN

GENERAL. This Performance Work Statement (PWS) defines the requirement for professionally and technically experienced personnel, with service in the Special Warfare/Combat Support (SW/CS) career fields, to provide the candidate’s with career field knowledge and guidance on:

nutrition, strength/conditioning, mental resiliency, and a targeted fitness plan.

BACKGROUND. The mission of Air Education & Training Command (AETC) is to recruit, educate, and train the highest quality men and women from the diverse population of our country to fill the Air Force’s requirements and focus on the outcomes by executing adaptable business practices and maintaining an effective, motivated, integrated force. Additionally, candidates are typically unprepared for the rigors and stress of the career fields which have an intense ops tempo (long and/or multiple deployments often into hostile areas).

SECTION 1 - DESCRIPTION OF SERVICES

1.1. SCOPE OF WORK: Regionally deliver SW/CS professionally and technically experienced personnel to inspire SW/CS candidates through mentorship and a structured development process.

Contracted personnel shall provide Air Force Specialty Code (AFSC) insight and job knowledge to better inform the candidate on their Air Force career choice. Contractor shall provide coaching on nutrition, strength/conditioning training, and mental resiliency as well as set and monitor targeted fitness goals/expectations for the candidates. The candidate development program is aimed to both regionally enhance first-contact with accessions as well as mentally/physically prepare individual candidates for the enduring demands of the SW/CS initial skills training.

1.1.1. The Contractor shall provide Full Time Equivalents (FTE’s) for CDSS program management and CDSS Wing and Field Developers at various locations identified in Tables 1.

Through.

1.1.1.1. Contracted oversight for the CDSS III contract.

- Program Manager (PM) (1 FTE)

- Deputy Program Manager (DPM) (1 FTE)

1.1.1.2. Regional Lead Field Developers (RLFD) (3 FTE’s)

- Field Developer (FD) (36 FTE’s)

- Wing Developers (WD) (20 FTE’s)

- 14 WD’s will be located at Special Warfare Training Wing (SWTW) JBSA- Lackland

1.2. CONTRACTED PROGRAM MANAGER/DEPUTY PROGRAM MANAGER:

The CDSS contract PM/DPM has the overall responsibility for managing and tracking the program that supports the contract. The contract PM/DPM is the primary liaison between the Military Site Lead, Contract PM (Government), Contracting Officer (CO), and the Contracting Officer Representative (COR). The contract PM/DPM act as the Contractor’s Subject Matter Expert (SME) on all of the SW/CS career fields and ensure FD and WD knowledge levels are adequate to fulfill the contract’s educational requirements. The contract PM has overall authority on matters relating to contract employees and contract performance and oversees all planning and execution of the program. The Contract PM shall ensure program requirements and definitions are understood and complied with across all contract employees, at all training locations. Contract PM/DPM submits monthly travel plans for mission funding to Government PM. The Contract PM/DPM is responsible for ensuring all CDSS Regional Lead Field Developers, Field Developers and Wing Developers are properly trained and in place upon the conclusion of the Phase-In/Phase- Out period. Identify and address issues within five (5) business days after issue is identified by the Government. Resolve issue(s) from CDSS Developers within 30 calendar days after issue is identified. Safety issues and concerns will be addressed immediately with the On-Site Government Lead as well as the COR that duty day.

1.3. REGIONAL LEAD FIELD DEVELOPER: (RLFD) The RLFD’s (East, West, Central United States) provide SW/CS subject matter expertise to track and employ FDs activities within their region. RLFD shall direct FDs to in-person/on-site asses and influence organizations of high candidacy. A regional monthly Surveillance/Approach Plan is required identifying each region’s actions facilitating Recruiter First-Contact for the next calendar month. The Surveillance/Approach Plan shall be submitted with the Monthly Status Report (MSR) each month, no later than 10 business days after the end of each month, to the Government PM/COR.

1.4. PRE-ACCESSION DEVELOPMENT:

1.4.1. CDSS FIELD DEVELOPERS:

1.4.1.1. Contractor shall provide Pre-accession Field Developers: Each FD shall provide distinct pre-accession services.

1.4.1.2. The FD shall assess areas/activities of high-interest. Areas of high interest, include but are not limited to; sporting clubs, sporting events, sports teams, fitness facilities, physical fitness events, extreme sporting events, and/or any organization with a high demographic of potential targeted candidates. The on-site actions of the FD are to assess, influence, and inspire local managers, leaders, and organizations to grow their military connection by meeting with an SW/CS Recruiter. FD shall facilitate leads for the RLFD meeting requirements.

1.4.1.3. RLFD minimum requirements:

- RLFD through independent actions and research shall plan, host, and attend no less than three (3) meetings/events between SW/CS Recruiters and local high interest organizational leaders, and representatives per region monthly.

- Provide status on individuals, organizations, and influencers in which first-contact recruiting is required.

- Track the number of leads/applicants attributable to a specific location, organization or individual.

- Meeting/Event locations must be distributed throughout the various field locations to accommodate all geographic regions.

1.4.1.4. The FD shall provide the pool of approved candidates (Non-Prior Service (NPS)/Prior Service Civilians, Officer crossflow, enlisted retrainees, Guard, and Reserve personnel) with;

SW/CS career field knowledge, as well as guidance on nutrition, strength/conditioning, mental resiliency, and targeted fitness techniques. The FD shall identify, inspire, and develop future

SW/CS Operators for the demands of initial skills training and follow-on career fields. The FD, using transparent data collection and targeted strength and conditioning plans, will prepare and qualify SW/CS candidates for success in the SW/CS Pipeline. The FD shall administer and document all physical assessment testing IAW Government furnished standards and direction.

Finally, the FD shall work and schedule candidate development sessions/testing to best accommodate the applicant’s availability, to include weekends, if required.

1.4.1.5. Field Development requirements:

- Mandatory four (4) candidate development sessions with a candidate prior to the Field Developer’s “Ready-to-Ship” recommendation. Reference para 1.6.1.

- Administer initial physical entry standard test when applicant is entering into the pre-accession development program.

- Administer final physical entry standard test no earlier than 45 days, and no later than 15 days prior to Basic Military Training (BMT) Shipment.

- Document PAST within one (1) business day of completion into the Government online web based tool.

1.5. POST-ACCESSION DEVELOPMENT:

1.5.1. CDSS WING DEVELOPERS (WD)

The Wing Developer Contractor sometimes referred to as a Coach, shall inspire and develop future SW/CS Operators for the physical and mental demands of their selected pipeline courses and career fields, by use of transparent, objective-based resiliency programs.

- WD shall provide physical fitness coaching, human performance academics, remedial skills, and mental resiliency training to support students IAW approved Government lesson plans. This support is required to provide continued physical and mental development, thus enabling the Air Force to effectively develop candidates to their fullest potential to meet increased SW/CS requirements.

- WD Contractor (if requested) shall develop Strength and Conditioning, mentoring, combat skills, and troop leading Lesson Plans (LP’s).

- Location specific Lesson Plans will be developed and implemented under the oversight of the government site lead.

- LP’s will be drafted and administered IAW Air Force and organizational guidance provided by the Government PM. LP’s will be submitted to the Site Government Lead for approval no later than 45 days after the completion of the Phase-In/Phase-Out period for review/approval and will be implemented by all Wing Developers within 1 (one) business day after notification of Government approval at the Wing Development training locations.

If Government furnished LP’s are provided the Contractor shall review and acknowledge receipt. Initial LP’s and any future updates or improvements to LP’s will be coordinated between the Government and Contractor and modified documents will be submitted to the COR for acceptance. Contractor shall acknowledge in writing receipt of all LP modifications.

- The Contractor shall comply with technical training location physical training and mentorship lesson plans and programming.

- When directed by the Government contracted developers shall use furnished lesson plans for all training evolutions.

- Any conflicting instructional guidance will be adjudicated by the CDSS III Government

PM/COR.

1.6. VOLUME OF WORK: Approximately 2200 SW/CS candidates are programmed to enter the Air Force in FY22. The candidates will either enter the Air Force through the Delayed Entry Program (DEP), Officer Special Warfare Airman Program (SWAP) process, Enlisted Retrainee process, or Air Reserve Component recruiting process. Expected average daily development pool size is approximately 1500 candidates.

1.6.1. When Administrating the Pre-Accession Physical Ability Stamina Test (PAST) for non-prior service, Special Warfare Operator Enlistment, and select Guard and Reserve candidates, Field Developers shall secure locations and provide a minimum of three (3) scheduled PAST sessions per month. The Contractor shall administer a PAST no earlier than 45 days and no later than 15 days prior to a candidate shipping to BMT. Candidates not meeting PAST standards will not be recommended as ready-to-ship. The Contractor (at a minimum) shall document four (4) developmental training sessions prior to the candidate receiving a ready-to-ship remark. Two of the four documented sessions shall be in person and in excess of 3 hours.

1.6.2. The Contractor shall begin PAST testing for pre-accession candidates as designated by the official contract start date. The Contractor shall administer a PAST Worksheet IAW the standards documented in the Air Force Special Warfare/SERE/EOD PAST Worksheet (Attachment 1) for all enlisted SW/CS programs. In addition, the Contractor may administer the PAST for CRO, STO, or TACPO as part of the candidate’s Phase I application for their corresponding officer program.

Testing sessions can involve multiple candidates at the same testing time/location.

1.6.2.1. The PAST standards are subject to change based on USAF policies and directives.

If a future change in physical entry standard test procedures requires the Contractor to obtain additional training for developers or procure additional equipment to administer the new/updated physical entry standard. The Contractor shall have 14 calendar days to make the adjustment.

1.6.2.2. Any updates or modifications to the PAST will not require a modification to the contract.

An updated PAST will be provided by the COR to the Contract PM/DPM.

1.6.3. A PAST is required within 30 calendar days after the applicant is identified by the recruiter as a candidate for a SW/CS specialty. If the PAST cannot be performed within 30 calendar days, extensions will require CDSS Program Manager approval.

1.6.4. Upon completion of a PAST, CDSS Developers shall upload results to the Government provided on-line web based tool within one (1) business day in order for the recruiter to make a classification decision.

1.6.5. Due to PAST failures, multiple individual candidate re/tests may be required resulting in approximately 8,000 tests per year.

1.6.6. Candidates can ship with one successful PAST IAW the Air Force Enlisted Classification

Directory and AFRS/330 RCS policy.

1.6.7. Due to the unique challenges with overseas recruiting (Europe, Asia, Alaska, Hawaii, and the Caribbean), if the Field Developer will not be in the overseas Area of Responsibility (AOR) within 30 calendar days prior to a candidate’s BMT ship date, the requirement for an Entry on Active Duty (EAD) PAST’s may be waived by the assigned 330 RCS Leadership.

1.6.8. The Contractor shall provide (CONUS U.S.) a minimum of thirty-six (36) Field Developers and three (3) Regional Lead Field Developers on location upon completion of the Phase-In/Phase- Out period.

1.6.9. The Contractor shall provide (CONUS U.S.) a minimum of twenty (20) Wing Developers on location (see para 1.7) upon completion of the Phase-In/Phase-Out period.

1.7. VOLUME OF WORK BY WING DEVELOPER (WD) TRAINING LOCATION:

1.7.2. 66 TRS, Fairchild AFB, WA: SERE Average Daily Student Load (ADSL) of approximately up to 60 SERE students will require Wing Developmental Training daily. Two (2) Wing Developers are required to accommodate course ADSL factoring risk mitigation safety requirements. Each Wing Developer shall be on-site and available no less than 40 hours a week (to include non-duty hours, weekends, and evenings). Due to the high self-initiated elimination rate these positions drive an increased mentor role specific to SERE. One (1) of these two (2) Wing Developers must be a graduate the Air Force S-V81-A SERE Specialist Training Apprentice Course and have six (6) or more years of experience as a former SERE Specialist/Instructor.

1.7.3. 366 TRS Sheppard AFB, TX: Explosive Ordinance Disposal (EOD) Training Course:

ADSL approximately 20 to 50 EOD students will require Wing Developmental Training daily.

Two (2) Wing Developers are required to accommodate course ADSL factoring risk mitigation safety requirements. Each Wing Developer shall be on-site and available no less than 40 hours a week (to include non-duty hours, weekends, and evenings).

1.7.4. United States Air Force Academy (USAFA) Colorado Springs, Colorado: USAFA Wing Developers shall work directly with a revolving baseline of ~100 USAFA/ROTC cadets requiring dedicated coaching each week. Cadet availability starts at approximately 0530 and ends at 1900 on weekdays, with extended availability on weekends. Contractor must work around the academic schedule of cadets, and work with groups/individuals before class, during periods they do not have class, after class, and on weekends. Two (2) Wing Developers are required to accommodate course ADSL factoring risk mitigation safety requirements. Each Wing Developer shall be on-site and available no less than 40 hours a week (to include non-duty hours, weekends, and evenings).

- Specific USAFA requirements in addition to para 1.5.1. (Contractor shall):

o Site Lead/Instruct Leadership Reaction events o Site Lead/Instruct Small Unit Tactics, Basic weapon handling (Inert weapons only), and Tactical Radio Communications o Collaborate with the USAFA Human Performance Lab on curriculum development

1.7.5. SWTW JBSA-Lackland AFB, Chapman Annex, TX: ADSL approximately 150 to 250 SW students will require Wing Developmental Training daily. 14 Wing Developers are required to accommodate course ADSL. Each Wing Developer shall be on-site and available no less than 40 hours a week.

1.8. PERIOD OF PERFORMANCE: One Base Year with four (4) Option Years.

1.8.1. Phase-In/Phase-Out: 3 December 2021 – 31 January 2022

1.8.2. Base Year: 1 February 2022 – 30 November 2022

1.8.3. Option Year One: 1 December 2022 – 30 November 2023

1.8.4. Option Year Two: 1 December 2023 – 30 November 2024

1.8.5. Option Year Three: 1 December 2024 – 30 November 2025

1.8.6. Option Year Four: 1 December 2025 – 30 November 2026

1.9. PLACE OF PERFORMANCE:

1.9.1. CDSS Program Manager: Determined by Contractor

1.9.2. CDSS Deputy Program Manager: Determined by Contractor

1.9.3. CDSS Regional Lead Field Developers:

Table 1. RLFD Locations CDSS III 1 FEB 22:

1. Dallas, TX (RLFD Regional Manager) – (Central)

2. Portland, OR (RLFD Regional Manager) – (West)

3. Lexington, KY (RLFD Regional Manager) - (East)

1.9.4 Field Developers locations:

Table 1.1. FD Locations CDSS III 1 FEB 22:

1. San Diego, CA

2. Salt Lake City, UT

3. Kansas City, MO

4. Omaha, NE

5. San Antonio, TX

6. Green Bay, WI

7. Lansing, MI

8. Tampa, FL

9. Louisville, KY

10. Montgomery, AL

11. Fort Dix, NJ

12. Long Island, NY

13. Denver, CO

14. Richmond, VA

15. Raleigh, NC

16. Boston, MA

17. Nashville, TN

18. Phoenix, AZ

19. Albuquerque, NM

20. Los Angeles, CA

21. Spokane, WA

22. New Orleans, LA

23. Dallas, TX

24. Seattle, WA

25. Orlando, FL

26. Syracuse, NY

27. Minneapolis, MN

28. Jacksonville, FL

29. Dayton, OH

30. San Jose, CA

31. Sacramento, CA

32. St. Louis, MO

33. Little Rock, AR

34. Oklahoma City, OK

35. Norfolk, VA

36. Atlanta, GA

1.9.5. CDSS Wing Developers locations:

Table 1.3. WD Locations CDSS III 1 FEB 22:

1. JBSA-Lackland AFB, TX

2. Sheppard AFB, TX

3. Fairchild AFB, WA

4. USAFA Colorado Springs, Co

1.10. TYPE OF CONTRACT: The Government will award a Firm Fixed Priced (FFP) type contract.

1.11. OTHER DIRECT COSTS: The COR does not have authority to authorize the Government beyond the scope of this FFP type contract. Any additional cost must be pre-approved by the contracting officer.

1.12. WORK SCHEDULE: Pre/Post Accession Candidate availability to training will drive the Contractor weekly scheduling priority. The Contractor’s on-site work week normally will not exceed 40 hours to include non-duty hours, weekends, and evenings.

Field Developers need to be available to their candidates primarily in-person. If not in person then via text, telephone, e-mail, or face-to-face video.

- Wing Developer shall be on-site and available to coach/train no less than 40 hours a week.

1.13. FEDERAL HOLIDAY’S: IAW Office of Personnel Management federal holiday policy https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/ https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/

SECTION 2 - Definitions and Acronyms

2.1. DEFINITIONS:

2.1.1. CONTRACTOR: A supplier or vendor awarded a contract to provide specific supplies or service to the Government. The term used in this contract refers to the prime.

2.1.2. CONTRACTING OFFICER: A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the Government.

Note: The only individual who can legally bind the Government.

2.1.3. CONTRACTING OFFICER’S REPRESENTATIVE (COR): An employee of the U.S.

Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.4. AIR FORCE COMBAT SUPPORT (CS): Are considered EOD and SERE Specialist career fields.

2.1.5. AIR FORCE SPECIAL WARFARE (SW): Are considered Pararescue (PJ)/Combat Rescue Officer (CRO)/Combat Control (CCT)/Special Tactics Officer (STO)/Special Reconnaissance (SR)/Tactical Air Control Party (TACP)/ and Tactical Air Control Party Officer (TACPO) career fields.

2.1.6. FIELD DEVELOPER (FD): Contracted personnel providing support and services to SW/CS pre-accession development.

2.1.7. PRE-ACCESSION DEVELOPMENT: Candidate development or influencing prior to candidate day 1 arrival to Basic Military Training.

2.1.8. PRE-ACCESSION CANDIDATE POOL: Non-Prior Service/Prior Service Civilians, Officer Crossflows, Enlisted Retrainees, Guard, and Reserve personnel.

2.1.9. POST-ACCESSION: Defined as Uniformed Military Personnel (Student, Candidate, or Cadet).

2.1.10. WING DEVELOPERS (WD): Contracted personnel providing support and services to Commissioning Institution (USAFA/ROTC) and Post-Accession military candidates.

2.1.11. REGIONAL: Three sections of CONUS United States (East, Central, and West).

2.1.12. KEY PERSONNEL: The following personnel are considered key personnel by the Government:

2.1.12.1. CONTRACTING OFFICER REPRESENTITIVE (COR): Mr. Alan Price, alan.price.9@us.af.mil, 210-652-4925.

2.1.12.2. GOVERNMENT PROGRAM MANAGER (GPM): Mr. Michael Erdley, Michael.Erdley.1@us.af.mil, 210-652-2874

SECTION 3 - QUALITY ASSURANCE

3.1. QUALITY ASSURANCE: The Government procedures identified in paragraph 3.1 and its sub-paragraphs are intended to verify that services are being performed by the Contractor IAW published standards.

3.1.1. QUALITY ASSURANCE SURVEILLANCE PLAN (QASP): The Government will monitor and assess the Contractor’s quality of performance using the accepted quality levels specified in the contract. All actions taken by the Contractor to correct deficiencies found by the Government as a result of quality assurance surveillance, and by the Contractor as a result of quality control, shall be at the Contractor’s own expense.

3.1.2. DEFICIENCES: A deficiency is any Government-identified non-compliance with the Services Summary (SS) or other contract requirements that specifies an activity or action did not take place, or did not meet the quality standards or performance timeline required.

3.1.3.CONTRACT DISCREPANCY REPORT (CDR): A CDR or electronic equivalent will be initiated by the COR or CO when contract requirement deficiencies are found and subsequent corrective actions are to be taken. The Contractor shall take immediate action to correct all Government reported deficiencies and to prevent recurrence of the deficiency.

3.1.4. PROGRMAN MANAGEMENT REVIEW (PMR): PMRs will be conducted at the request of the Government and provide a forum to review Contractor performance, corrective action items from previous PMRs, and any CDSS Program concerns raised by the Contractor or the Government. PMRs shall be scheduled at AETC/A3S (Government) facilities at JBSA- Randolph, TX and can be in-person or virtual meetings.

3.1.5. QUALITY CONTROL: It shall be the Contractor’s responsibility to ensure all necessary measures are taken to assure that the quality of an end product or service shall meet contract requirements.

3.1.6. QUALITY CONTROL PLAN (QCP): Ten (10) business days after the post award meeting, the Contractor shall be responsible for a current QCP. The Contractor’s QCP shall identify the standards, processes, procedures, and checklists for all tasks performed. The Contractor shall develop and maintain a QCP to identify, prevent and correct any deficiencies for all services (including all Performance Objectives and deliverables) set forth in this PWS and shall assure the requirements of this contract are provided as specified. The Contractor shall submit their QCP as part of their technical proposal for evaluation. The QCP must illustrate proposed method(s) of inspection, and actions to be taken to correct deficiencies discovered during the inspection process. The plan shall become a compliance document after acceptance by the CO upon contract award.

3.1.6.1. The Contractor shall monitor quality processes and perform technical audits and reviews IAW the QCP to verify adherence to organizational standards, processes, and procedures. Changes to the QCP during contract performance shall be submitted to the CO for acceptance not later than 10 business days prior to implementation.

3.1.6.2. The Contractor's quality inspection documentation (i.e., metrics, reports, etc.) shall be made available to the COR or CO within two (2) business days, if requested. The reports should provide information on the methods of inspection, what was inspected, discrepancies found, and actions taken to correct and preclude recurrence.

SECTION 4 - CONTRACT REQUIREMENTS

4.1. DESCRIPTION OF DUTIES: The Contractor shall work within the USAF CDSS Special Warfare/ Combat Support Development contract, under the oversight of Government lead personnel. The Contractor shall influence, inspire, and develop future SW/CS operators for the demands of their training pipeline courses and follow-on career requirements. Contractor shall provide oversight from qualified developers, and safe objective-based programs. The Contractor shall evaluate and train candidates to the following SW/CS attributes: stress tolerance, drive, problem solving, teamwork, communication, trainability, integrity, and physical fitness. The Contractor shall furnish all personnel, equipment, tools, materials, transportation, supervision, and other items necessary (unless otherwise noted in this PWS as Government furnished) to perform to the standards identified in the Services Summary.

4.1.1. The Developer to student ratio is event driven and will be identified in the approved Lesson Plan/Risk Management (RM) for each training event. All Developmental physical training plans will include a Risk Management Assessment Worksheet (AF Form 4437, Deliberate Risk Assessment Worksheet) that describes how activities will be mitigated to acceptable risk levels.

4.1.2. The onsite WD shall comply with Air Force safety regulations, and local governing RM procedures, and emergency action policies for all training events. These regulations/policies will affect the Developer to student ratios based on trends, higher thermal injury risk periods, and specific event sub-category types (e.g. trail-run versus 1/4 mile track run). The Developer to student ratio will be annotated on each Lesson Plan/RM for each training event.

4.1.3. Generally accepted instructor to student ratios are subject to change as lesson plans are created/approved and ORM matrixes established.

4.2. DELIVERABLES:

4.2.1. Phase-In/Phase-Out IAW Section 6

4.2.2. Phase-In/Phase-Out +45 Days

- Field Developer Site Specific Lesson Plans/RM

- Wing Developer training location (installation) specific Lesson Plans/RM

4.2.3. RECURRING:

- Monthly Status Report IAW para 5.5.

- Monthly Surveillance/Approach Plan IAW para 5.4.

- Monthly Travel Plan IAW para 5.3.

4.2.4. All Contractor Lesson Plans shall be provided to the On-site Government lead within 45 days after Phase-In/Phase-Out for organizational review and staffing to AETC/A3S COR for acceptance.

4.2.5. Government acceptance will be based upon physical training plans having comprehensive emergency action procedures, risk management mitigations for possible injuries and training that seems logical and encompassing of all trainees at that level of instruction.

4.2.6. LP shall be implemented by all Wing Developers within one (1) business day after Government approval/COR acceptance at the wing technical training locations to guide training sessions.

4.2.7. If provided, all Government furnished training-plans and Risk Management Worksheets will be the primary instructional material used for training.

4.2.8. The order and amount of training on each subject area must adhere with Government provided guidance, procedures, and techniques. Any needed future updates or improvements to the physical training plans or lesson plans shall be coordinated between the Government and Contractor and modified documents shall be submitted to the COR for acceptance.

SECTION 5 - ACCOUNTING FOR PROGRESS

5.1. The Government will provide an on-line, web-based tracking tool to the Contractor to provide both physical performance and mental resiliency updates on all candidate progress.

5.1.1. The Contractor must utilize the Government furnished Web-Based Tracking Tool as soon as practicable, but NLT 30 calendar days after Phase-In/Phase-Out.

5.1.2. The Government will provide the Contractor training on the Government furnished Web- Based Tracking Tool.

5.2. The Contractor shall use the Government provided on-line web-based tool to track and account for:

- The total number of AF SW/CS candidates

- Location of candidates

- Developer comments on candidates -- Training and development goals

-- Performance progression/regression of each candidate

- All candidates successful/unsuccessful PAST data

- Ready-to-ship recommendation

5.3. Provide a monthly Travel Plan to the AF SW/CS Government PM/COR no later than the 25th day of the prior month. CDSS contract PM/DPM shall include a schedule of all planned travel (can be tentative), PAST testing, and training sessions with candidates. The inclusive dates of the plan will include dates from the first to the end of the month. The Contractor shall submit a finalized travel plan to the AF SW/CS Government PM/COR within 10 business days after the end of the month. Any changes in the finalized travel plan will be highlighted.

5.4. Surveillance/Approach Plan is required identifying each regions actions facilitating Recruiter First-Contact for the next calendar month.

5.5. Monthly Status Report shall include the following:

- Current Manpower Positions

- Personnel Actions/Movements

- Wing Development: Students trained by location with SW and SERE identified separately for JBSA-Lackland.

- Monthly Statistics

-- Total Individual PASTs -- Total Individuals in Development -- Passing PAST -- Total Candidates Pre-Accession

- Impact on Facilities and Testing

- Program Manager Comments

5.6. NLT 45 days after Phase-In/Phase-Out the Contractor shall be expected to merge all existing pre accession candidate data to the Government furnished on-line web-based tracking tool. The initial (one-time) data transfer requirement will include the following: name, location, and all PAST scores for an estimated 1100 candidates.

5.7. US Government retains all rights to data collected on all candidates.

SECTION 6 – PHASE-IN/PHASE-OUT

6.1. Phase-In/Phase-Out: This contract includes a Phase-In/Phase-Out period of 3 December 2021 – 31 January 2022 to coordinate and meet any requirements necessary to begin operations to include the following:

6.2. Ensure all Field and Wing Developers are in place, properly trained and certified.

6.3. The Contractor shall provide the name(s) and contact information of the CDSS contract PM, DPM, and all three RFLD’s to the COR and CO at the Post-Award meeting.

6.4. All CDSS III contracted personnel shall be in place after the conclusion of Phase- In/Phase-Out.

6.4.1. Any Contract position that becomes vacant must be filled with a properly trained and certified personnel within 30 calendar days after position being vacated. The COR must be notified in writing if any positions remain vacant longer than 30 calendar days.

6.5. During Phase-In/Phase-Out: The Contractor shall bring all required CDSS Field and Wing Developers to Joint Base San Antonio to receive the following: Training on PAST, proper guidance, procedures, and techniques expected from the Field and Wing Developers to ensure standardization. The Contractor is responsible for notifying the Government of any employee’s needing training. At the Government’s request, the Contractor shall bring CDSS Field and/or Wing Developers to a Government determined location to address significant pre- accession and/or post-accession pipeline changes that require in-person training to ensure standardization and proper execution.

6.6. The Contractor shall complete all preliminary paperwork to obtain a CAC and access to Government furnished database by the last day of the Phase-In/Phase-Out period.

SECTION 7 - PERSONNEL QUALIFICATIONS

7.1. A general understanding of all SW/CS career fields being necessary to accomplishing Contract objectives, all personnel must have personal experience serving in an SW/CS career field.

7.2. The Contractor shall be responsible for employing qualified personnel to safely perform the requirements in this PWS. The Contractor shall maintain the personnel, organization, and administrative control necessary to ensure that the work delivered meets the contract requirements. The work history of each Contractor employee must contain experience directly related to the task and functions he/she is intended to perform under this contract.

7.3. Specific Personnel Qualification Requirements:

7.3.1. The CDSS PM/DPM shall have Leadership and Management experience with focus on SW/CS career fields.

7.3.2. All CDSS Developers shall possess American Heart Association (AHA) or American Red Cross CPR/First Aid Certification.

7.3.3. All CDSS Developers shall possess Personal Trainer Certification from any accredited certification credential program listing (Attachment 2). CrossFit ‘certifications’ do not qualify as a certification substitute. The Contractor is responsible for personal trainer certification renewal frequency and any continuing education credits and re-certifications shall be at no additional cost to the Government.

7.3.4. All CDSS Developers must possess a valid state driver’s license. Wing developers may use Government vehicles to support training activities (e.g. trail student formations, transport students with injuries, thermal injury intervention), provided the unit commander authorizes such use and all prescribed AFI procedures have been followed to authorize Contractor use.

7.3.5. All CDSS Developers must possess a Lifeguard Certification.

7.4. The Contractor shall be responsible for providing their own transportation (including fuel) in the conduct of their contracted duties. To drive on base, Contractors shall have a valid state driver’s license and proof of insurance. At no time shall Contractor personnel share transportation with candidates.

7.5. Maintain a professional appearance while actively developing SW/CS candidates and practice high standards of personal hygiene and wear neat/clean fitness clothing/apparel that clearly identifies the Contractor’s business name and CDSS Developer’s name while performing screening and developmental exercise sessions. Effective communicator both verbally and written.

7.6. CDSS Developers must maintain their personal fitness to be an example of what is expected of SW/CS recruits. Specifically, the Contractor must be able to maintain a level of fitness to physically demonstrate proper techniques and exercises at all PAST and Development events.

7.7. Contractor must possess the ability to demonstrate and explain all points of performance for exercises included in the PAST.

7.8. Contractor personnel shall be either a former PJ or CRO, CCT or STO, SR (or the former Special Operations Weather Team (SOWT) career field), TACP or TACPO, EOD, or SERE Specialist who served in various operational positions for a minimum of six (6) years (post training). Contractor personnel shall include at least:

- One employee with six (6) or more years of experience as a former PJ or CRO.

- One employee with six (6) or more years of experience as a former CCT or STO.

- One employee with six (6) or more years of experience as a former SR (or SOWT).

- One employee with six (6) or more years of experience as a former TACP or TACPO.

- One employee with six (6) or more years of experience as a former EOD Technician.

- One employee with six (6) or more years of experience as a former SERE

Specialist/Instructor.

7.9. Regional Lead Field Developer personnel shall be either a former PJ or CRO, CCT or STO, SR (or former SOWT career field), TACP or TACPO, EOD Technician, or SERE Specialist who served in various operational positions for a minimum of ten (10) years (post training).

7.10. Contract personnel shall have a minimum of one operational tour in their AFSC while on active duty (or equivalent Guard/Reserve time) and either retired or left their respective community in good standing with a minimum of an Honorable Discharge.

7.11. Have a proficient understanding and working knowledge of e-mail, voice mail, video conferencing and text messaging to perform duties.

7.12. SECURITY REQUIREMENTS.

7.12.1. Obtaining and Retrieving Identification Media. As prescribed by the AFFARS 5352.242- 9000, Contractor access to Air Force installations, the contractor shall comply with the following requirements:

7.12.1.1. The contractor shall obtain base identification and vehicle passes for all contractor personnel who make frequent visits to or perform work on the Air Force installation(s) cited in the contract.

7.12.1.2. No later than three (3) working days prior to start of contract work, the contractor shall submit a written request on company letterhead (or e-mail correspondence) to the project manager (with copy to contract administrator) listing the following: project title, project number, contract number, location of work site, contract start and stop dates, work schedule, and names of contractor employees needing access to the base, including full legal name, date of birth, sex, race, SSAN, state issued I.D. Card/Driver License number, and name of sub-contractor if not employed directly by contractor (Government will provide template to be used in submitting visitor pass request). The authorized program manager will endorse the request and forward it to the issuing base pass and registration office or security forces for processing. Contractors will present government (state or federal) issued ID, and INS Form 9 (I9), before being issued a pass to enter the installation. A Wants and Warrants check is conducted for every person before a pass is issued. Personnel employed by the contractor must get a pass for their privately owned vehicles at the installation Visitor Reception Center, with proof of following:

- Liability Insurance

- Current License Plates

- Current State Inspection Sticker (If Required)

- Valid State Driver License

- A phone number for sponsor on base

7.12.1.3. Vehicles owned by the contractor with the company name permanently printed on them are not required to obtain a pass as long as a current work order is presented at the time of entry.

However, current liability insurance, state inspection sticker, and registration is required. The person driving the vehicle must have a valid operator license for the type of vehicle.

7.12.1.4. The contractor is responsible for ensuring employees report to the installation Visitor Reception Center, to present their Form I-9 (Employment Eligibility Verification).

7.12.1.5. Upon completion or termination of the contract or expiration of the identification passes, the contractor shall ensure that all base identification passes issued to contractor employees are returned to the issuing office. If a contractor employee has been terminated, the pass will need to be retrieved and returned to Security Forces so that employee does not have base access. If the pass is not retrieved then Security Forces will need to be notified so base access is not allowed. Upon completion of the contract return all issued installation access passes to the issuing authority.

7.12.1.6. Failure to comply with these requirements may result in withholding of final payment.

7.12.2. Pass and Identification Items. The Host Unit shall ensure the following pass and identification items required for contract performance are obtained for employees and non-government owned vehicles:

7.12.2.1. Installation Access Pass (IAP) (DBIDS), Visitor/Vehicle Pass (DoDM 5200.08, Volume 3, DoD Physical Security Program: Access to DoD Installations), used for contracts for less than one year to include one-day visits (i.e. warranty work).

7.12.2.2. Installation Access Card (IAC) (DBIDS), Civilian Identification Card (DoDM 5200.08, Volume 3, DoD Physical Security Program: Access to DoD Installations), used for contracts for more than one year or more which do not require access to controlled areas or government computer systems.

7.12.2.3. DoD Common Access Card (CAC), (AFI 36-3026), used for contracts for more than one year and requirement exists for access to the government computer systems and software.

CAC applications are accomplished by Trusted Agents via the Trusted Agent Sponsorship System (TASS).

7.12.2.4. All Contractor personnel shall obtain CAC’s for access to installations and the Government online web based tool.

7.12.2.5. The contractor shall be responsible for equipment required to enable CAC access.

7.12.3. Contractors and their personnel shall use the following procedures to obtain CACs:

- Contractors shall provide a listing of personnel who require a CAC to the contracting officer. The government will provide the contractor instruction on how to complete the Contractor Verification System (CVS) application and then notify the contractor when approved.

- Contractor personnel shall obtain a CAC from the nearest Real Time Automated Personnel Identification Documentation System (RAPIDS) Issuing Facility (typically the local Military Personnel Flight (MPF))

7.12.4. While visiting or performing work on installation(s)/location(s), contractor personnel shall wear or prominently display the CAC as required by the governing local policy

7.12.5. During the performance period of the contract, the contractor shall:

7.12.5.1. Within 7 working days after any changes to the listing of the contract personnel authorized a CAC, provide an updated listing to the contracting officer who will provide the updated listing to the authorizing government official; Return CACs in accordance with local policy/directives within 7 working days after a change in status for contractor personnel who no longer require logical or physical access; Report lost or stolen CACs in accordance with local policy/directives.

7.12.6. Within 7 working days following termination of a contractor or completion/termination of the contract, the contractor shall return all CACs issued to their personnel to the issuing office or the location specified by local policy/directives.

7.12.7. Suitability Investigations.

7.12.7.1. For contracts requiring IT-Level III computer access, contractor personnel shall successfully complete, as a minimum, a Tier 1 background investigation (formerly known as a NACI), before being issued a CAC and operating government furnished workstations. The contractor shall comply with the DoDM 5200.02, Procedures for the Department of Defense Personnel Security Program, AFPD 17-1 Information Dominance Governance and Management, AFMAN 17-1301, Computer Security and AFI 17-130, Cybersecurity Program Management, requirements. Tier 1 investigations requests are initiated using the Standard Form (SF) 85 and are submitted to the installation Information Protection Office through the using agency’s Security Assistant (SA) within five (5) working days after contract start. Tier 1 investigations are provided by the government at no additional cost to the contractor.

7.12.7.2. For contracts requiring IT-Level I and II access with no access to classified material, the contractor shall complete a Tier 5 (formerly SSBI) or Tier 3 (formerly NACLC and ANACI) investigations, respectively. These investigations are submitted using the SF 86, and are submitted to the Information Protection Office through the using agency’s SA within five working days after contract start. These investigations are provided by the government at no additional cost to the contractor.

7.12.7.3. For contracts requiring routine access to the installation in excess of 180 days, the contractor shall complete a Tier 1 investigation. These investigations are submitted using the SF 85, and are submitted to the Information Protection Office through the using agency’s SA within five working days after contract start.

7.12.8. Listing of Employees. The contractor shall maintain a current listing of employees. The list shall include employee's name, social security number, and date of investigation if service work involves unescorted entry to Air Force restricted or other sensitive areas designated by the installation commander. The list shall be validated and signed by the company supervisor, and provided to the contracting officer prior to the contract start date. Updated listings shall be provided when an employee's status or information changes.

7.12.9. Freedom of Information Act Program (FOIA). The contractor shall comply with DoD Manual 5400.07_AFMAN33-302, DoD Freedom of Information Act Program, requirements.

The regulation sets policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding Controlled Unclassified Information (CUI) material. The contractor shall comply with AFI 33-332, Privacy and Civil Liberties Program, when collecting and maintaining information protected by the Privacy Act of 1974 authorized by Title 10, United States Code, Section 8013. The contractor shall remove or destroy official records only in accordance with AFI 33-322, Records Management and Disposition of Records Program.

7.12.10. Reporting Requirements. The contractor shall comply with AFI 71-101, Volume- 1, Criminal Investigations, and Volume-4 Counterintelligence. 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 and as required thereafter.

7.12.11. Entry Procedures to Controlled/Restricted Areas. Contractor personnel requiring unescorted entry to areas designated as controlled or restricted areas by the installation commander shall comply with installation’s access requirements and will possess, as a minimum, a favorable suitability determination. These requirements are contained in AFI 31-101, Integrated Defense for installation access procedures and AFMAN 16-1405, for suitability determinations. The contractor shall comply and implement local base procedures for entry to Air Force controlled areas.

SECTION 8. GENERAL INFORMATION

8.1. Interaction with News Media: Contractor personnel shall not discuss the AF CDSS contract or other related information with the news media. The Contractor must notify the CO, and COR regarding any media or public inquiries concerning this contract.

8.2. Manpower Reporting Requirements: The Contractor shall report ALL contract labor hours (including subcontracted labor hours) required for performance of services provided under this contract for the Air Force via a secure data collection site. The Contractor is required to completely fill in all required data fields at http://www.ecmra.mil. Reporting inputs will 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 at any time during the FY, all data shall be reported no later than 31 October of each fiscal year. Contractors may direct questions to the Contractor Manpower Reporting Application (CMRA) help desk.

8.3. Position Fill/Lapse Rates: The Contractor is responsible for sufficient employees to execute duties outlined in this PWS to continuously fulfill and satisfy mission requirements. Any position becoming vacant shall be filled within 30 calendar days.

8.4. Supervision of Personnel: The Government will not supervise or otherwise direct Contractor employees. The Contractor shall not supervise or otherwise direct Government employees, nor shall the Contractor supervise employees of other Contractors outside the Contractors’ own subcontracting/teaming arrangements.

8.5. Contractor Identification: Contractor employees shall be readily identifiable as such. At no time shall they present themselves as active duty or Government personnel in person, in writing, via email or over the phone.

8.6. Conflict of Interest: The Contractor shall not employ, hire, or contract with employees of the United States Government or the DoD, either military or civilian, if such employment would create a conflict of interest. The Contractor shall not employ any person who is an employee of the DoD, unless such person receives prior approval, in writing, from the base legal office.

8.7. Conduct of Personnel: The CO may require the Contractor to remove from the contract any Contractor employee working under this contract for reasons of misconduct, security violations, or found to be or suspected to be under the influence of alcohol, drugs, or other incapacitating agent. The Installation Commander has the authority to bar individuals from the installation.

Such removal from the contract or dismissal from the premises shall not relieve the Contractor of the contract requirements.

8.8. Professional Relationships: Contractors are considered “trainers providing entry-level training” as defined under DODI 1304.33, Protecting Against Inappropriate Relations during Recruiting and Entry Level Training and “faculty and staff of initial skills training” as defined under AFI…