2A-7. (VDOPS) 2nd Draft PWS_20231116_2106.docx

VDOPS PWS

Contract FA4890-XXXXXXX(P00014)

(Draft) PERFORMANCE WORK STATEMENT (PWS)

FOR

Contract No. FA4890-XXXXXXX

VECTOR DOPPLER SCORING SYSTEM SERVICES

XX Mon Yr OPR: ACC AMIC/PMA

LANGLEY AFB, VIRGINIA

TABLE OF CONTENTS

4.6 Ground Station Unit Cybersecurity (CLIN X003)……………………………………….14

4.7 Information Technology Asset and Software Management……………………………..14

5.8 Environmental, Safety, and Occupational Health (ESOH) Program………………..…...23

5.9 Vehicles………………………………………………………………………..…………24

SECTION A

DESCRIPTION OF SERVICES

1.0 SCOPE OF WORK

1.1 Background. The 53d Weapons Evaluation Group (WEG) provides aerial targets for lethality testing of major weapons systems and munitions programs under U.S. Code Title 10, Sec 2366. The 53 WEG evaluates all USAF fighters and air-to-air missiles supporting DoD and Foreign Military Sales customers. It also hosts live-fire Weapons System Evaluation Program (WSEP) exercises. The Vector Scoring System (VSS) is the end-game missile scoring system on the QF-16 Full-Scale Aerial Target (FSAT) at Tyndall AFB (TAFB) and Holloman AFB (HAFB). Vector Doppler Scorer (VDOPS) is the end-game missile scoring system on the Subscale Aerial Targets (SSAT) (BQM-167A) at Tyndall AFB (TAFB).

1.2 Scope. Services non-personal; the Contractor shall supply all management, personnel, equipment, and supplies, necessary to perform the services as defined in this PWS. Provide VDOPS/VSS program management, mission scoring, scoring data reports, depot support, engineering support, lifecycle management, and security. Operate Ground Station Units (GSU) and perform Organizational Level (O-Level), Intermediate (I-Level), and Depot (D- level) maintenance/repair/replacement for GSUs and scoring support equipment. Perform Aerial Gunnery Target Sets (AGTS) engineering support, depot-level repairs, and associated equipment replacement/repairs/replacement. Ensure work, services, operations, safety, security, and environmental requirements comply with local, state, and federal laws and regulations, publications, and applicable technical orders (TOs). The nature of this work will demand that the Contractor be capable of quick response to stringent deadlines as specified in this PWS.

1.2.1 Provide services at TAFB and HAFB with periodic deployments to the Utah Test and Training Range (UTTR), UT (Dugway/Wendover), and/or other locations as directed by the Government. Costs associated with these deployments will be IAW CLIN X004.

1.2.2 Unless otherwise stated in this contract, all work and purchases are part of the baseline Firm Fixed Price (FFP) portion of the contract. The Contractor shall be responsible for performing all services and meeting all directives noted in this PWS by imperative verbs regardless of whether such services and directives are preceded by the words “the Contractor shall.”

1.2.3 Additional Maintenance Support. The Government reserves the right to incorporate additional maintenance support, including on equipment maintenance of full scale or sub-scale aerial targets to the O-Level, I-Level, and D-Level, to support the missions of the 53 WEG. If such change should become necessary, an equitable adjustment in cost would be negotiated IAW the “Changes” clause.

2.0 PROGRAM MANAGEMENT

2.1 Contractor Program Management (CLIN X001).

2.1.1 Exercise management and operational control over, and retain full responsibility for, the performance requirement set forth in this PWS. Both the Government and the Contractor recognize that no employer-employee relationship, between Government and Contractor personnel exists or will exist under this contract. The Government will not exercise any direct supervision over the Contractor’s employees performing services under this contract. The Contractor’s employees shall remain under the Contractor’s direct supervision at all times. Although the Program Manager (PM), Deputy Program Manager (DPM), and Contracting Officer’s Representative (COR) will coordinate directions within the scope of the contract, detailed instructions for the Contractor’s employees and supervision shall remain the sole responsibility of the Contractor.

2.1.2 Contractor shall not perform any tasks that are inherently Governmental functions.

2.1.3 While Contractor management and personnel will have daily exchanges with various Government personnel in performance of their duties, contract administration rests with the Contracting Officer (CO) and any conflicts in directions should be brought to his/her attention directly or via the PM and COR.

2.1.2 Contractor Human Resources. The Contractor shall provide a qualified workforce sufficient to support all mission requirements.

2.1.2.1 Contractor Program Manager (CPM). Designate a CPM responsible for the performance of all work required under this contract. The CPM serves as the daily on-site focal point and single interface between the Government and Contractor personnel. The CPM shall maintain overall responsibility for all operating locations. The CPM shall establish Contractor management functions, as necessary, to ensure organizational functions at each operating location operate with standardized processes and discipline. The CPM shall exercise management and operational control for all contract requirements and have full authority to act for the Contractor on all matters relating to daily operations. The CPM shall be identified in writing at contract start. The CPM shall maintain COMSEC control and appoint a COMSEC Responsible Officer (CRO) and establish user accounts IAW AFMAN 17-1302-O, Communications Security (COMSEC) Operations. Comment by STOODT, ERIC C CIV USAF ACC 82 ATRS/DRQA: Does this highlighted section need to be moved down into security/COMSEC paragraphs As its own requirment instead of lumped under CPM?

2.1.2.2 Key Personnel. The CPM shall designate key personnel at each operating location responsible for daily operations at each site. Designated key personnel shall be in place at contract start. Provide designated key personnel listing NLT 45 days after transition start for Government review and approval. Send any changes of key personnel to CO within 45 days for review and approval.

2.2 Contract Administration (CLIN X001). The Contractor shall provide all data and information to the Government in electronic format compatible with Microsoft Office software unless otherwise directed by the Government. All data developed by the Contractor during performance of this contract becomes the property of the Government.

2.2.1 Operating Instructions (OI) and Operating Procedures (OP). Develop, maintain, implement, and continuously improve a set of OIs/OPs (CDRL A008) that all Contractor personnel will be held accountable to, which provide guidance and establish procedures to standardize O&M at all operating locations. Contractor OIs/OPs will be reviewed and accepted by the Government prior to implementation. In addition, a biennial review of OIs/OPs shall be conducted by the Contractor and approved by the Government. Craft and/or revise OIs/OPs to reflect new and/or evolving guidance present in applicable governing DoD documentation, instructions, publications, policies, directives, supplements, addendums, etc.

2.2.2 Contractor Checklists, Job Guides and Work cards. Develop Job Guides, work cards, Standard Operating Procedures (SOPs), checklists, etc., to supplement TOs, as required, and to provide procedures for areas that do not have TO instructions. Local checklists, job guides, and work cards shall be published and utilized IAW TO 00-20-1, TO 00-5-1, and DAFI 21-101. Contractor checklists, job guides and work cards will be reviewed and accepted by the Government prior to implementation (CDRL A008). Approval is the responsibility of the CPM. Review checklists, job guides and work cards every 2 years for currency.

2.2.3 Records Management and Administrative Support. Establish an information management system/process to control, distribute, file, and suspense all maintenance reports, technical publications, and correspondence. Ensure disposition of records IAW AFI 33-322, Records Management and Information Governance Program. All Contractor-generated records, documents, databases, other electronic media, and associated papers shall become Government property and will remain in place upon contract termination or completion. Records, documents, databases, other electronic media, and associated papers shall be available for Government review at all times. They shall be easy to locate, easy to read, and shall be kept current. Provide correspondence and reports using official formats approved by Government. At the time of disposition, the Contractor shall box, label contents, and turn over documentation to the PMO.

2.2.3.1 Contract Data Requirements List (CDRL). Make all current and archived/historical CDRLs available and provide via other means if directed to do so in the Block 16 of each CDRL. The Contractor shall notify those on the distribution list in Block 14 of each CDRL via e-mail when a new CDRL is posted. The Contractor shall incorporate appropriate security measures so that only authorized recipients have access to the CDRLs.

2.2.3.2 Provide the Government unlimited rights to use, duplicate or disclose such records, files, documents, data, and working papers and reports in whole or in part, in any manner and for any purpose whatsoever.

2.2.3.3 Use software compatible with the USAF standard (subject to change), currently Microsoft Office. All Contractor data exchange shall be via electronic means, unless prior CO approval or direction is received for hard copy transmission. The Government will consider any cost-effective proposals submitted by the Contractor detailing alternative and supplemental methods of data interchange.

2.2.3.4 Provide technical assistance to all Government officials (designated decision authorities & Base Records Manager) in support of the Records Management (RM) Program, which includes Electronic Records, Privacy Act (PA), and Freedom of Information Act (FOIA) programs.

2.2.3.5 Segment and control access security and safety of records according to record sensitivity IAW AFI 33-322.

2.2.3.6 Identify and establish procedures to protect or remove all vital records in the event of a disaster, natural or otherwise.

2.2.4 Correspondence. Prepare all correspondence relating to management required in the execution of the services required by this PWS. The correspondence that is PWS- related shall consist of, but not be limited to: replies, requests for assistance, reports, and routine correspondence to the base/installation or other activities. All correspondence between the Contractor and Government, to include all electronic correspondence (e-mail and fax) shall be courtesy copied (Cc’d) to the Government PM office.

2.2.6 Continuity of Performance. Continuity of performance and uninterrupted mission support must be maintained during any contract transition without degradation of performance/support occurring. This means the Contractor must have sufficient number of fully qualified personnel on the start date of the Basic Period to accomplish the requirements of the contract without adverse mission impact to any area. Such fully qualified personnel shall have the necessary knowledge, skills, and abilities to perform the requirements of the contract.

2.2.6.1 Prior to contract completion, if applicable, the incumbent shall provide sufficient orientation, training, and equipment/system familiarization information required by the follow-on Contractor. The incumbent agrees to cooperate fully with the Government and the follow-on Contractor to ensure an orderly transition and continuity is maintained. During the transition period, the Contractor shall make available all official files, manuals, charts, records, drawings, and other official documentation that are the property of the Government and shall remain on location for use by the Government or follow-on Contractor during the transition period.

2.2.7 Periodic Progress Meetings. The Contracting Officer and other Government personnel, as appropriate, will meet periodically with the Contractor to review the Contractor’s performance. At these meetings, the Contracting Officer will apprise the Contractor of how the Government views the Contractor’s performance and the Contractor will apprise the Government of problems, if any, being experienced.

2.2.7.1 The Contractor will also notify the Contracting Officer in writing of any work that the Contractor considers over and above the requirements of the contract prior to starting performance. Appropriate action shall be taken to resolve outstanding issues.

2.2.7.2 The minutes of these meetings will be developed by the Government and approved by the Contracting Officer and distributed to the Government’s functional area(s) and Contractor. Should the Contractor not concur with the minutes, the Contractor will respond in writing to the Contracting Officer any areas of non-concurrence.

2.3 Quality Program.

2.3.1 Quality Management System (QMS) (CDRL A001). Develop, document, implement, maintain, and continuously improve a comprehensive QMS that assures compliance with all requirements of this PWS.

2.3.2 Performance Evaluation. Contractor performance outputs are subject to surveillance by Government COR(s) to ensure compliance with this PWS. At a minimum, the Contractor shall:

2.3.2.1 COR/CO/PM Access. Allow COR(s)/CO/PM access to work areas and data, provide support, and do not interfere with the CORs and other designated personnel in the performance of their official duties. Permit the CO or authorized representative access to all records, data, and facilities used in the performance of the contracted services. Access shall be provided as soon as possible (unless the CO agrees to an extended time). Comment by STOODT, ERIC C NH-03 USAF ACC 82 ATRS/DRQA: Keping with our other contracts, are we wanting to keep the verbiage that’s highlighted? I say delete it as its not verbalized in our other contracts that way.

2.3.2.2 Non-Conformance. Take immediate corrective action(s) for all non-conformances identified during Government surveillance.

2.3.2.3 Audit Reports/ Non-Conformance Report (NCR). Upon receipt of an audit report and/or NCR, complete applicable sections of the NCR and return it to the CO within time constraints issued by the CO. Provide Corrective Action Plan as specified within the NCR.

2.3.3 Performance Evaluation Meetings, Conferences, and Workshops. Meet with Government personnel as necessary to discuss contract compliance, performance improvement, quality strategic planning, teamwork, and training opportunities. The Contractor may request a meeting with the Government at any time.

2.3.4 Inspections/Assessments/Exercises. Participate in inspections, audits, or exercises as deemed necessary by the CO. Perform required preparations to ensure a satisfactory rating is received during any required Air Force inspection, review, assessment, or staff assistant visit.

2.4 Publications, Technical Orders (TO) and Supplements. All publications, instructions and documents referenced in this PWS are mandatory and shall be adhered to without deviation.

2.5 Foreign Object Damage (FOD) Program. When working in, on, around, or traveling through areas near aircraft, Aerospace Ground Equipment (AGE), engines, or components thereof, adhere to host base FOD instructions, and implement any specific requirements outlined in the O&M Contractor’s FOD briefing as necessary to mitigate FOD hazards to Aircraft and AGE.

2.6 Contractor Personnel Qualification/Training. Select and employ qualified and motivated personnel in sufficient numbers to manage, supervise, and perform all tasks required by this PWS. All costs associated with providing training to employees in order to meet the requirements of this PWS are the sole responsibility of the Contractor unless otherwise approved by the CO. Contractor personnel shall be properly trained, qualified, and certified. A qualified individual is one who has the expertise necessary to predict, identify, and resolve problems and take required actions quickly and accurately on assigned tasks. Contractor training standards shall meet or exceed those acceptable to the Air Force, commercial aircraft and/or avionics industry and are subject to review by the PM and CORs.

2.6.1 Training Plan. Prior to performance of assigned duties under this contract, develop and provide a comprehensive Training Plan (CDRL A008) that documents all procedures for training, qualification, certification and decertification of employees. This plan must be reviewed and accepted by the Government prior to implementation.

2.6.2 Personnel Training Records. Develop and maintain individual training records to document training. Make records available to Government representatives upon request. Document initial, recurring, and supplemental training accomplished within each employee’s training record. Experience and training records shall be maintained on file at both TAFB and HAFB. Training records shall be available to the CO, PM and/or COR(s) at any time.

2.6.3 Cybersecurity Workforce (CSWF) Requirements. The Contractor shall provide all Cybersecurity/IT support required under this contract IAW DoDM 8140.03 and AFMAN 17-1303, Cybersecurity Workforce Improvement Program. The Contractor will comply with the Defense Acquisition Regulations (DFARS) 252.239-7001 and all CS requirements stipulated in the contract. All Contractor workforce performing one or more CS functions must be identified, managed, and tracked as part of the DoD CSWF IAW DoDM 8140.03 (CDRL A006). Individuals occupying these positions will attain and maintain a DoD approved CS baseline certification(s) as outlined in DoDM 8140.03 and AFMAN 17-1303. Comment by URIAH: Moved this requirement into certification and Training area of PWS. This is more focused on training requirements for duties rather than attached to duties.

2.6.3.1 Contractor CSWF personnel shall be certified no later than the first day of contract work. The Contractor is solely responsible for training costs, certification fees, maintenance fees, exam fees and all other costs for Contractor Cybersecurity Workforce personnel.

2.6.3.2 Contractor CSWF positions shall be annotated as Primary Duty, Additional Duty or Embedded Duty IAW AFMAN 17-1303.

2.6.3.3 Contractor CSWF personnel requiring privileged access shall complete and sign a Privileged Access Agreement. Contractor Privileged Access Users shall attain and maintain a cybersecurity baseline certification commensurate to the category and level from the DoD approved listing.

2.6.3.4 Contractor shall ensure personnel assigned to CSWF privileged positions possess IAT level II or greater. Comment by URIAH: IAT Level II is spelled out as we've had several companies ask what they're allowed to operate on or work around this. IAT Level II provides a high level of surety that the contractor can meet requirements. It must be upon hire. Comment by BEAGLE, URIAH J MSgt USAF ACC ACC AMIC/PCYM: Moved to 2.6.3. and outlined with correct certification level and DODI reference.

2.7 Technical and Test Support, and Meetings. Attend meetings, as required, by the Government. Proactively provide information and be prepared to discuss Contractor activities that have or may have an impact on 53 WEG support activities, missions and/or programs. Support Government seminars and conferences, test and other evaluations, technical interchange meetings, reviews, working groups, and Program Management Reviews (PMR) specified herein and in support of current and future efforts. Act as a Government technical advisor and subject matter expert (SME) at such meetings. The support shall include preparation of support documentation, briefing slides and materials, resolution of action items and taskers, and presenting the material in the performance of contractual requirements. Interface through ad hoc meetings, discussions (in person and over-the phone or radio), and electronic correspondence with the Government, including the PM and 53 WEG representatives, as necessary to meet flying schedule, test support and PWS requirements. Expect these communications and Government interfaces to occur on a daily basis. Support staff assistance visits (SAVs), working groups, briefings, inspections, and prepare, maintain, submit or make accessible correspondence, records, reports, and data associated with all work requirements.

3.0 ENGINEERING SUPPORT

3.1 Engineering Support (CLIN X003). Provide engineering support as follows: Hardware (HW) and software (SW) maintenance, frequency migration research and implementation, antenna pattern studies (CDRL A002), product improvements, on-aircraft scoring system (to I-Level and D- Level), GSU, AGTS, aircraft support equipment modifications and engineering change proposal development (CDRL A003) as directed by the Government. Prepare drawings, graphics, test/analysis procedures and reports. These services also include support of any follow-on system, such as QF-16 integration.

4.0 GROUND STATION AND SUPPORT EQUIPMENT MAINTENANCE

4.1 Scoring and Maintenance (CLIN X002/X003). Accomplish all activities necessary to capture vector and scalar scoring including GSU operation, final score capture and processing, and score delivery to the designated Government recipient. Support all scheduled missions and levels of effort. Provide monthly report of Mission Availability (Ma) (CDRL A004). Ma is defined as the number of score reports provided divided by the number of scoring reports required expressed as a percentage.

4.1.1 Levels of Effort. The Contractor shall provide scores for all scheduled scoring missions not to exceed 245 annually. The Government reserves the right to schedule and utilize the types of sortie scores (FSAT or SSAT) at all operating locations to meet mission requirements.

4.1.1.1 TAFB FSAT Level of Effort. Provide scoring for up to two (2) NULLO missions per week, up to a maximum of 80 NULLO sorties per year. The Government will provide the Contractor 72-hour notification of multiple drone missions and the total number of flights will be determined by mission requirements. The Government may direct the Contractor to provide FSAT missions in excess of two (2) NULLO missions per week and 90 NULLO sorties per year, provided the PM and the Contractor agree that such support is within the Contractor’s on-site capability.

4.1.1.2 HAFB FSAT Level of Effort. Provide scoring for up to two (2) NULLO missions per week up to a maximum of 20 NULLO sorties per year. The Government will provide the Contractor 72 hours notification of multiple drone missions. The Government may direct the Contractor to provide FSAT missions in excess of two (2) NULLO missions per week up to a maximum of 30 NULLO sorties per year, provided the PM and the Contractor agree that such support is within the Contractor’s on-site capability.

4.1.1.2.1 Range checks. Transmit VSS signal during White Sands Missile Range periodic range checks. Range checks will be coordinated/scheduled by the Range Controller.

4.1.1.2.2 Pre-mission checks. Perform VSS signal bit error rate check with Range Controller two hours prior to each scoring mission.

4.1.1.2.3 Scoring Mission Support. Operate and maintain multiplex/demultiplex units, Apogee recorder, and decryption equipment during each scoring mission.

4.1.1.3 SSAT Level of Effort. The Contractor shall be capable of scoring a maximum of 16 SSATs in a two (2) week period, not to exceed 145 SSAT sorties per year (inclusive of all SSAT operating locations). Due to limited range availability, the Government may schedule up to three (3) primary drones in a single range period. If more than one target is launched in a range period, each target that flies a minimum of one valid presentation shall count toward the total subscale target missions. The Government may direct the Contractor to provide SSAT missions in excess of 16 SSATs in a two (2) week period provided the PM and the Contractor agree that such support is within the Contractor’s onsite capability.

4.1.1.4 Deployed Scoring O&M. Support deployed drone missions. The deployment length shall be approximately two (2) weeks in duration. The support shall include scoring of 16 SSAT missions. The Contractor shall be responsible for all logistics activities for deployment and redeployment of necessary equipment and Contractor support personnel. This level of effort is expected to occur one (1) to two (2) times annually. The Government will provide the Contractor 30-day notification to move personnel and equipment between TAFB and HAFB or other operating locations such as the UTTR as designated by the PM to support mission requirements. Travel and logistics cost will be reimbursed per CLIN X004.

4.1.2 Score Reporting.

4.1.2.1 High/Medium/Low Score Reporting. The Contractor shall provide the 83 FWS Missile Analysis Flight (MAF) no later than (NLT) 2 hours after mission period (with a goal of 90 minutes after the last missile has been fired), a documented report which includes the following:

· Date, drone type, aces, mission number, missile type, document classification

· Score quality

· Miss Distance

· Missile orientation relative to drone

4.1.2.2 Low Quality Score. In addition, the Contractor will annotate all observations in the “note” area of the “scoring database” in accordance with the requirements of 4.1.2.6 below for that particular drone/mission.

4.1.2.3 Scalar Score Reporting. For Scalar scores, the Contractor shall provide the 83 FWS/MAF NLT 2 hours after mission period (with a goal of 90 minutes after the last missile has been fired), a documented report which includes the following:

· Date, drone type, aces, mission number, missile type, document classification

· Score quality

· Miss distance

4.1.2.4 In addition, the Contractor will annotate all observations in the “note” area of the “scoring database” in accordance with the requirements of para 4.1.2.6 for that particular drone/mission.

4.1.2.5 No Score Reporting. The Contractor will enter “NS” in the “scoring database” and annotate all observations in the “note” area of the “scoring database” in accordance with the requirements of para 4.1.2.6 for that particular drone/mission.

4.1.2.6 Scoring Database. The Contractor shall load all scores onto Excel spreadsheet (High, Medium, Low, Scalar, No Score, No Score Expected, No Score Required) that can be viewed by 83 FWS/MAF. The spreadsheet will include the following scoring info: date, drone type, aces, missile type, score quality, detailed notes. This data shall be updated weekly and made available through a Government- owned shared, unclassified drive. Provide database information to PM via Monthly Status Report (CDRL A004).

4.2 Ground Station, VDOPS/VSS and AGTS Equipment Repair/Replacement, and Spares (CLIN X004). Provide all services and materials necessary to maintain the GSU and aircraft support equipment to the depot level. Provide depot level component repairs/replacement for VSS and AGTS equipment as directed by the Government. Accomplish all warranty and non-warranty repairs. Provide sufficient spares, for items not covered by a warranty, to maintain the GSU and support equipment. Obtain CO approval before initiating repair action in excess of $3,000 for equipment items.

4.3 Lifecycle Management. Provide VDOPS/VSS and AGTS equipment lifecycle management including configuration control, spares forecasting, documentation, technical manual and drawing updates, technical research and investigations, equipment and component obsolescence and replacement planning. Identify HW/SW projected to be affected by diminishing manufacturing sources (DMS), forecast obsolete or cost prohibitive HW/SW and identify replacement sources via the Monthly Status Report (CDRL A004). Identify HW/SW, and documentation deficiencies. Propose and justify changes, suitability, perform cost comparisons, engineering studies and testing. Prepare drawings, graphics, test/analysis procedures and reports. Support new systems once approved by Government. Assist other Government and contract agencies as directed by the Government.

4.4 GSU Upgrade. The GSU shall be updated to comply with DoD Chief Information Officer (CIO) mandate for Windows 11 integration, and sustainment. All GSU systems must meet this requirement by 14 October 2025. The upgrade will occur in two phases.

4.4.1 Phase 1. Design, and build if required, a GSU that uses Windows 11 operating system. The new system must have the capability of being upgraded and modernized to meet future DoD system requirements. Phase I lab-based equivalent GSU shall retain current functionality and mission support capability to include auto-detection feature. Upgraded GSU model will change from GSQ-106D to GSQ-106E.

4.4.1.1 First Article Testing. Contractor shall accomplish First Article Testing (FAT) of Phase I lab-based equivalent GSU. Phase I will end when testing at Tyndall AFB, FL successfully demonstrates (under Government oversight) Phase I lab-based equivalent GSU functionality and mission support capability is equal to or greater than Windows 11 GSU and the Government accepted performance of the system.

4.4.1.2 Warranty. Lab-based equivalent GSU shall have a warranty for at least five (5) years from Government acceptance to include hardware (exception: legacy Digital Signal Processor (DSP) card), software, and labor. Contractor shall provide copies of all warranties, and documentation from all applicable vendors.

4.4.1.3 Delivery and Acceptance. Delivery and acceptance shall occur before or after contract start.

4.4.1.4 Equivalent GSU Disposition. The lab-based equivalent GSU shall reside at MDSI facility for configuration management and cybersecurity update impact testing.

4.4.1.5 Periodic Updates. Provide the Government with progress updates monthly and upon Government request. Additionally, notify the Government immediately upon discovery of circumstances impacting the 180-day delivery and acceptance date.

4.4.2 Phase 2. Modify six fielded GSQ-106D GSUs to comply with DoD CIO mandate for Windows 11 integration. Upgrade shall be accomplished for all units to the GSQ-106E configuration in accordance with para 4.4.1. Complete independent verification of all applicable software configuration items in accordance with their corresponding Software Test Description (STD) and document test results in a Software Test Report (STR). Provide engineering coordination, planning support. Migrate GSQ-106D User Guide TO GSQ-106E configuration.

4.4.2.1 Incorporate most recent Security Technical Implementation Guides (STIGs) from DISA for the current Windows operating systems installed for all upgraded GSUs.

4.4.2.2 Warranty. Upgraded GSUs (GSQ-106E) shall have a warranty for at least five (5) years from Government acceptance date to include hardware (exception: legacy Bittware Digital Signal Processor (DSP) card), GEForce Graphics Card, software, and labor. Contractor shall provide copies of all warranties, and documentation from all applicable vendors.

4.4.2.3 Delivery and Acceptance. Delivery and acceptance shall occur by the DoD CIO mandated date of 14 Oct 2025. Ship, deploy, configure, and test all units.

4.4.2.4 Periodic Updates. Provide the Government with progress updates monthly (CDRL A004) and upon Government request. Additionally, notify the Government immediately upon discovery of circumstances impacting the delivery and acceptance date.

4.5 GSU Cybersecurity (CLIN X005). The Contractor shall support VDOPS/VSS GSU cybersecurity requirements as determined by the Government-assigned Information System Security Manager (ISSM) and approved by the Government Program Management Office (PMO). These efforts are expected not to exceed 20 hours per month.

4.5.1 Risk Management Framework (CLIN X005). The Contractor shall provide technical information to the Government-assigned ISSM and ISSO to support and maintain Authority to Operate (ATO). Implement physical and cybersecurity controls established as requirements for system ATO as approved by the Government PMO. These controls will include but are not limited to:

4.5.1.1 Mitigate vulnerabilities on machines found through Assured Compliance Assessment Solution (ACAS) scans. If unable to mitigate, explanation is needed as to why risk must be accepted.

4.5.1.2 Provide all software code to the Air Force Software Evaluation Review Team (SERT) to be analyzed and certified IAW AFI 17-101. Application software must be approved for use within the Operational Test and Training Infrastructure (OTTI) and placed on the OTTI Evaluated Products List (OTTI E/APL).

4.5.1.3 Information systems will need to maintain minimum hardware and software requirements as set forth by DoD.

4.5.1.4 Obtain appropriate DoD-approved baseline Information Assurance certification for all personnel.

4.5.1.5 Adhere to the OTTI cybersecurity policies and the ATO requirements set forth by the Authorizing Official.

4.5.1.6 Provide authorized and appointed cybersecurity personnel (ISSM/ISSO) administrative-level access to information systems to view configurations, identify potential vulnerabilities, and verify hardware and software inventories. Comment by URIAH: If the contractor is performing these, then they need IAM II certification. However, from what you provided, the contractor isn't required to be an ISSM, they just need to create ATO artifacts for the ISSM. This is more in line with IAT II and is about $30K cheaper on average.

4.5.1.7 Adhere to established DoD and Air Force directives/policies.

4.5.2 System Security Plan (CLIN X005). The Contractor shall comply with security plan requirements for GSU systems security as per Appendix III to OMB Circular A-130.

4.5.3 Cybersecurity Updates (CLIN X005). Implement and maintain all Government-directed security updates. Establish and execute a Government-approved process to update all fielded GSUs with OS security patches.

4.6. Information Technology Asset and Software Management Comment by STOODT, ERIC C CIV USAF ACC 82 ATRS/DRQA: Is this area we want to reference CDRL A006? Its only CDRL not referenced in this PWS...

4.6.1. Information Technology Asset Management. The Contractor shall administer, maintain, and use computer systems as developed and/or provided by the Government. Appoint, in writing, a primary and alternate Property Custodian (PC) responsible for IT hardware (HW) asset management (CDRL A006). Permit complete access to all Government IT hardware and software (HW/SW) assets used to perform this contract to anyone designated by the PM. HW/SW shall be maintained IAW DAFMAN 17-1203. Comment by URIAH: ITAM and Commercial Software verbiage updated and added.

4.6.2 Commercial Software (SW) (CLIN X006). The Contractor shall appoint, in writing, a primary and alternate Unit Software License Manager (USLM) responsible for maintaining application/ operating system SW library (CDRL A006). Provide commercial software on a cost-reimbursable basis, as authorized by the Government. Purchase Orders for commercial software shall be approved by the PM or CO prior to purchase. Software paid for by the Government shall be considered Government property. All data contained within automated information systems pertaining to contract performance shall be made available in a non-proprietary format upon contract termination or PCO request. Manage all commercial off the shelf (COTS) and AF-unique software acquired by the USG IAW DAFMAN 17-1203.

5.0 MISSION SUPPORT

5.1 Emergency Management Response. All VDOPS employees shall familiarize themselves with TAFB and HAFB Plan 10-2, both titled Contingency Emergency Response Plan. Copy of plans shall be maintained in the workplace in a readily accessible location. Develop a plan (CDRL A008) and establish specific emergency action procedures for Contractor employees to effectively respond to mishaps, disaster control events and severe weather titled Contingency Emergency Response Plan.

5.1.1 Support disaster response exercises and real-world events, when directed by the CO.

5.1.2 Safeguard Government records, sensitive equipment/software, information, and facilities to prevent damage, unauthorized access or release.

5.2 Classified Material Handling. Develop a plan for the protection, removal, or destruction of classified materials in case of fire, natural disaster, civil disturbance, terrorist activities or enemy action, to minimize the risks of its compromise (CDRL A006). The level of detail and amount of testing and rehearsal of these plans should be determined by an assessment of the risk of hostile action, natural disaster, or terrorist activity that might place the information in jeopardy IAW DoD 5200.1R, Para C.6.3.4.1.

5.3 Electronic Mail Policy. Adhere to local Network Control Center (NCC) policies.

5.4 Communications.

5.4.1 Current Communications. Maintain effective and efficient communications throughout the maintenance complex. Contractor employees shall be readily identified in correspondence, in telephone conversations and in meetings they attend.

5.4.2 New Communications Requirements, Upgrades and Changes. Submit all recommendations for new, upgraded or changed communications requirements to the CO.

5.4.3 Personal Electronic or Communication Devices. Personal electronic or communication devices (e.g., cell phones, beepers, pagers, portable music/video players, electronic games, etc.) are prohibited on the flightline and hangars and/or other industrial work areas except for key mission essential and senior management personnel for official business only. Personnel authorized shall be approved by the CPM and identified on a CPM designation letter. All use of these devices must follow the appropriate safety precautions such as Hazards of Electromagnetic Radiation to Ordnance (HERO) distances etc., when used in these areas. This prohibition does not include common areas such as office areas, break or locker/ready rooms.

5.5 SECURITY

5.5.1 Visitor Group Security Agreement (VGSA). The Contractor shall enter into a long-term VGSA with the host base Security Office if contract performance is on base for 90 days or more. This agreement shall outline how the Contractor integrates security requirements for contract operations with the Air Force to ensure effective and economical operation on the installation.

5.5.1.1 Security support provided by the Air Force to the Contractor to include storage containers for classified information/material, use of base destruction facilities, classified reproduction facilities, use of base classified mail services, security badging, base visitor control, investigation of security incidents, base traffic regulations, the use of security forms, and conducting inspections required by DoDM 5220.22V2_AFMAN16-1406V2, National Industrial Security Program: Industrial Security Procedures for Government Activities.

5.5.1.2 Security support requiring joint Air Force and Contractor coordination includes packaging classified information, mailing and receiving classified materials, implementing emergency procedures for protection of classified information, security checks, and internal security controls for protection of classified material and high value pilfer able property.

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

5.5.2 Clearance Requirements. The Contractor shall possess or obtain a facility security clearance at the classification level of Secret prior to performing contract work. If the Contractor does not possess a facility clearance, the Government (Contracting Office) will request one. The Government (DISCO) assumes costs and conducts security investigations for Top Secret, Secret, and Confidential facility security clearances. The Contractor shall request security clearances (Submit Clearance Paperwork through DISCO to the Office of Personnel Management) for personnel requiring access to classified information within 15 days after receiving a facility clearance or, if the Contractor is already cleared, within 15 days after contract award. Due to costs involved with security investigations, requests for Contractor security clearances shall be kept to an absolute minimum necessary to perform contract requirements.

5.5.3 Notification. The Contractor shall notify 53 TSS Security Manager 6097 Florida Ave, Suite 101, TAFB FL, 32403-5207, 30 days before contract start. The notification shall include:

· Name, address, and telephone number of company representatives

· Contract number and contracting agency

· Highest level of classified information to which Contractor employees require access

· Location(s) of contract performance

· Date contract performance begins

· Any changes to information previously provided under this paragraph

5.5.4 Identification/Apparel. All on-site Contractor employees shall wear clothing appropriate to the task assigned and readily identifying them as Contractor personnel. Recognition will be accomplished by distinctive clothing or badges (e.g., uniforms, name tags, company name and/or logo or company identification badges). If badges are worn, the Contractor shall comply with host base policy. All clothing worn by Contractor personnel shall conform to TO 00-25-172, AF Directives, applicable technical data and OSHA Standards. Uniform designs must be approved by the Government.

5.5.5 Listing of Employees. Maintain a current listing of employees. The list shall include the employee's name, social security number and level of security clearance. The list shall be validated and signed by the company Facility Security Officer (FSO) and provided to the Sponsoring Agencies Security Manager at contract start. An updated listing shall be provided when an employee's status or information changes.

5.5.6 Security Manager Appointment. Appoint a security manager for the on base Visitor Group (CDRL A006). The security manager shall provide employees with training required by DoDM 5200.01V1_AFMAN16-1404V1, Information Security Program: Overview Classification and Declassification. The Contractor shall also provide initial and follow-on training to Contractor personnel who work in Air Force controlled/restricted areas. Air Force restricted areas and controlled areas are explained in DAFI 31-101, The Air Force Installation Security Program. Comment by HEAD, KENNETH CIV USAF ACC ACC AMIC/PMAO: CDRL?

5.5.7 Pass and Identification Items. Ensure the pass and identification items required for contract performance are obtained for employees and non-Government owned vehicles.

5.5.8 Retrieving Identification Media. Retrieve all identification media, including vehicle passes from employees who depart for any reason before the contract expires; e.g., terminated for cause, retirement, etc.

5.5.9 Traffic Laws. Comply with base traffic regulations.

5.5.10 Weapons, Firearms, and Ammunition. Contractor employees are prohibited from possessing weapons, firearms, or ammunition, on themselves or within their Contractor-owned vehicle or privately owned vehicle while on Tyndall and Holloman AFBs.

5.5.11 Reporting Requirements. Contractor personnel shall immediately report to an appropriate authority any information or circumstances which may pose a threat to the security of DoD personnel, Contractor personnel, resources, and classified or unclassified defense information. Contractor employees shall be briefed by their immediate supervisor upon initial on-base assignment.

5.5.12 Physical Security. Safeguard all Government property and controlled forms provided for Contractor use. At the end of each work period, all Government facilities, equipment, and materials shall be secured.

5.5.13 Controlled/Restricted Areas. Implement local base procedures for entry to Air Force controlled/restricted areas where Contractor personnel will work. An AF Form 2586, Unescorted Entry Authorization Certificate, shall be completed and signed by the sponsoring agency’s Security Manager before a Restricted Area Badge will be issued. Contractor employees shall have a favorably completed National Agency Check Plus Written Inquiries (NACI) investigation before receiving a Restricted Area Badge. Interim access can be granted IAW DoDMAN5200.02_AFMAN16-1405, Personnel Security Program Management. Contractor employees requiring a security clearance shall have a minimum of a SECRET, current within 5 years or a documented request for TOP SECRET SSBI clearance and be eligible for clearance into Special Access Programs such as F-22.

5.5.14 Key Control. Establish and implement control procedures to account for Government issued keys. Government keys will not be duplicated without approval of the CO. All keys issued and received shall be signed and annotated on AF Form 2427 or equivalent form approved by the PM. Immediately report to the PM any occurrences of lost, stolen, or duplicated keys. The Contractor shall prohibit the use of Government-issued keys by any persons other than the Contractor employees except when authorized by the CO.

5.5.14.1 Replacement. In the event that Government-issued keys (other than master keys) are lost, stolen, or duplicated, the Contractor shall be required to re-key or replace the affected lock or locks at no cost to the Government. In the event that a Government-issued master key is lost or duplicated due to fault or negligence by Contractor employees, replace all locks and keys for that system at Contractor expense.

5.5.15 Lock Combinations. Control access to all Government-provided lock combinations to preclude unauthorized entry. The Contractor is not authorized to record lock combinations without CO or PM approval. Records with written combinations for authorized secure storage containers, secure storage rooms, or certified vaults, shall be marked and safeguarded at the highest classification level as the classified material maintained inside the secure storage container(s). Change combinations to locks and safes whenever an individual knowing the combination no longer requires access. Comply with DoD Instruction 5200.1-R security requirements for changing combinations to storage containers used to maintain classified materials.

5.5.16 Computer Security (COMPUSEC). Ensure all individuals obtain and maintain a favorable National Agency Check Plus Written Inquiries (NACI) and complete Cyber Awareness Challenge training, formerly Information Assurance Awareness Training, prior to gaining access to “.mil” domains IAW DoDM5200.02_AFMAN16-1405V1, and AFMAN 17-1301. The Contractor shall comply with DoDI 5200.2-R and local host base COMPUSEC procedures. Ensure employees complete any additional computer security training requirements mandated by the host base. Comment by BEAGLE, URIAH J MSgt USAF ACC ACC AMIC/PCYM: Corrected Reference.

5.5.17 Information Security (INFOSEC). Information, irrespective of media, shall be controlled and maintained IAW DoDM 5200.01V1_AFMAN16-1404V1 Air Force Policy Directive (AFPD) 31-4 and DoDM 5200.1, Enclosure 3.

5.5.18 Freedom of Information Act (FOIA). The Contractor shall comply with Freedom of Information Act (FOIA) requirements IAW DoDM 5400.07_AFMAN 33-302 Freedom of Information Act. The Contractor shall refer all inquiries under the Freedom of Information Act of 1975, as amended by Public Law 93-502, 5 U.S.C. Section 552, received by the contractor to the CO or designated Government official.

5.5.19 Privacy Act Information. In performance of this contract, Contractor personnel may have access to Personally Identifiable Information (PII). The provisions of the Privacy Act of 1974, Public Law 93-579, 5 U.S.C., Section 552a, DoD 5400.11-R DoD Privacy Program, AFI 33-332 AF Privacy and Civil Liberties Program, and other applicable agency rules and regulations shall apply. The Contractor shall adhere to rules and regulations for safeguarding PII, to include the reporting and notification requirements when PII is lost, stolen, or compromised.

5.5.20 Controlled Unclassified Information (CUI). The Contractor shall comply with Controlled Unclassified Information (CUI) requirements for access, designation, material marking, handling, transmitting, dissemination and safeguarding of CUI IAW DoDI 5200.48_DAFI 16-1403, Controlled Unclassified Information (CUI). (formerly For Official Use Only).

5.5.21 Communications Security (COMSEC) Materials. Obtain, remove, replace, operate, store, secure, inventory, transport, support, and manage all COMSEC items such as keying devices. Appoint a COMSEC Responsible Officer (CRO) and establish user accounts IAW User Requirements AFMAN 17-1302-O, Communications Security (COMSEC) Operations (CDRL A006).

5.5.21.1 COMSEC Local Elements. Establish and manage a local element and perform CRO duties IAW AFMAN 17-1302-O.