SSN PWS Draft_EMS IT MOD Support Contract.docx

Electromagnetic Spectrum Information Technology Modernization (EMS-IT Mod) Support Contract

PERFORMANCE WORK STATEMENT (PWS)

Award

Tracking Number

1. Contracting Officer’s Representative (COR) Primary COR: See DITCO Additional Text G1 – Point of Contact (To be designated at TO award) Alternate COR: See DITCO Additional Text G1 – Point of Contact (To be designated at TO award)

2. Contract or TO Title Electromagnetic Spectrum (EMS) Information Technology (IT) Modernization Support Contract.

3. Background The Department of War (DoW) is modernizing its Electromagnetic Spectrum (EMS) Information Technology environment to achieve spectrum superiority in contested and congested electromagnetic environments. This initiative is driven by the Fiscal Year 2027 Program Decision Memorandum (PDM) and validated Joint Force requirements (JROCM 070-25).

The current environment relies on manual, siloed, and non-interoperable legacy systems (including the Global Electromagnetic Spectrum Information System (GEMSIS) suite and Spectrum XXI (SXXI)), which limit the Joint Force’s ability to conduct effective Electromagnetic Spectrum Operations (EMSO) and Joint Electromagnetic Spectrum Operations (JEMSO).

To address these gaps, the EMS IT Modernization effort will transition legacy spectrum management, situational awareness, command and control, and training capabilities into a unified, cloud-native, AI-assisted ecosystem on the Maven Smart System (MSS), leveraging the Edge Data Mesh (EDM) and Joint Operational Edge (JOE) Cloud. The effort will establish an End-to-End EMS data layer, integrate Electromagnetic Battle Management-Joint (EMBM-J) capabilities, and begin the phased sunset of legacy GEMSIS tools, starting with SXXI at the end of FY28.

This support contract will provide advisory, systems engineering, technical assistance, and program management support to the EMS IT Modernization Program Management Office (PMO). To avoid Organizational Conflicts of Interest (OCI), contractors under this TO will not perform hands-on platform coding, software development, or integration on the MSS baseline. All development work will be executed under separate CDAO MSS development contracts.

4. Objectives The primary objective of this contract is to provide highly specialized advisory support across the full spectrum of EMS IT Modernization activities. The contractor shall deliver subject matter expertise, systems engineering, product management support, mission analysis, modeling and simulation validation, testing, training coordination, interoperability planning, and business operations support. Key objectives include:

Supporting the transition of legacy spectrum workflows into AI-assisted, automated workflows on MSS.

Providing technical and mathematical validation of Radio Frequency (RF) propagation and electronic warfare models.

Enabling seamless data exchange and interoperability between the MSS, Joint Command and Control (JC2), and Joint Tactical Fires systems.

Supporting the design and validation of resilient capabilities for Denied, Disrupted, Intermittent, and Limited (DDIL) environments via the JOE Cloud.

Evaluating the data pipeline, supporting ontology development, analyzing requirements, and roadmap development Supporting requirements analysis, roadmap development, and acquisition documentation in accordance with DoDI 5000.87 (Software Acquisition Pathway). Providing technical and analytical support for the establishment of a unified End-to-End EMS data layer and ontology.

Assisting with the planning and execution of legacy system migration and decommissioning activities.

5. Scope The contractor shall provide qualified technical, engineering, and administrative personnel to fulfill the tasks defined in Section 6. The requirements are structured across Integrated Product Teams (IPTs) and sub-teams, all to support the overarching EMS IT Mod strategy:

Task Area 1: TO Management (FFP) Task Area 2: Product Management, Product Strategy, Spectrum Mission Analysis, User Experience, & Training (CPFF) Task Area 3: Tenant Integration, Modeling & Simulation, Data, & Interoperability (CPFF) Task Area 4: Mission Assurance, Testing, & Product Support (CPFF)

The Government may require surge support during the base period and all three option periods, and surge modification will be within the scope of the TO and shall provide increased support for the defined task areas of this PWS. Surge support over the life of this TO will not exceed 10% of the contractor’s total proposed cost/price for the base and all option periods, excluding any six-month extension of services pursuant to FAR 52.217-8.

6. Performance Requirements

6.1 Task Area 1 – TO Management

The contractor shall provide comprehensive program management, administrative, financial, and acquisition support to ensure all requirements of this PWS are executed on time, within budget, and in accordance with DoD and DISA policies.

The contractor shall prepare a TO Management Plan describing the technical approach, organizational resources and management controls to be employed to meet the cost, performance, and schedule requirements throughout the TO execution in accordance with CDRL A005. The contractor shall participate in a formal Post-Award Kickoff Meeting within 15 working days of award.

The contractor shall ensure that all key personnel are onboarded at start of the period of performance. Key personnel shall be documented in the monthly CPR. No changes in key personnel shall be made unless the contractor can demonstrate that the qualification of the prospective replacement personnel meets the minimum qualifications. All proposed substitutes shall have qualifications equal to or higher than the qualifications listed below. The contractor shall notify the COR and the Contracting Officer of any key personnel changes within three business days and provide a copy of the individual’s resume for Government approval. All changes in key personnel must be approved by the Government.

Key personnel shall include the following:

Program Manager (PM): The contractor shall designate a PM to serve as the single management interface to the Government. The designated PM must possess the experience and qualifications necessary to manage the cost, schedule, and performance parameters of the contract. Key responsibilities include monitoring and executing agile development methodologies, staffing the program with properly trained and qualified personnel, and ensuring the timely delivery of all required material and data. The PM must hold a Project Management Institute (PMI) Project Management Professional (PMP) certification or have a minimum of eight (8) years of progressive project management experience.

Senior Spectrum Subject Matter Expert (SME): The contractor shall provide a Senior Spectrum SME with in-depth knowledge of electromagnetic spectrum (EMS) operations, spectrum management, and spectrum-dependent mission applications. The SME shall provide technical and functional systems analysis, design, integration, documentation, and implementation advice for complex EMS operational requirements. This includes frequency assignment and allocation, spectrum certification, host-nation coordination, electromagnetic interference (EMI) resolution, Joint Communications-Electronics Operating Instructions (JCEOI), Joint Restricted Frequency List (JRFL) management, and electromagnetic warfare (EW) support. Additionally, the SME shall support all software development phases, emphasizing planning, requirements analysis, testing, integration, documentation, and user presentation. The SME must apply advanced technical knowledge to define problems, support the development of system-enabled solutions, and provide expert advice on emerging capabilities. The candidate must possess a minimum of eight (8) years of progressive experience in spectrum engineering.

Senior Systems Engineer: The contractor shall provide a Senior Systems Engineer to analyze and document user functional data requirements, conduct technical research, and assess technologies relevant to assigned tasks. The Senior Systems Engineer shall support the installation, maintenance, servicing, and troubleshooting of systems and software to ensure operational performance matches design specifications. Key responsibilities include supporting the customization of systems and commercial products, developing and executing test plans, preparing system requirements and design documentation, estimating development costs and schedules, and overseeing software configuration management. Specialized experience must include the proven use of interactive, real-time information technology engineering capabilities, alongside the application of formal specifications, data-flow diagrams, and computer-aided software engineering (CASE) tools. The candidate must possess a Master of Science in Systems Engineering (or a closely related technical field) and a minimum of eight (8) years of progressive experience in systems engineering, software development, and technical support for complex IT and integrated data platforms.

6.1.1 Control Progress and Status Reporting: The contractor shall provide a Contractor Performance Review (CPR) in accordance with CDRL A001. The CPR shall address quality assurance monitoring, technical and programmatic progress/status reporting, and achievements since the last review to include the following: results of risk assessments, conduct and success of risk management activities, unresolved issues, action items, status of fund execution and any known problems. Additionally, the CPR shall include personnel reassignments including all personnel added or removed from the contract, and a breakout of labor categories and hours per month across the entire period of performance.

These reviews are a team effort between the COR and contractor and are an opportunity for both parties to review the status of contract performance. The contractor shall provide the COR with electronic copies of data generated for the CPR to include all briefing slides, lists of action items generated, and an updated status of all previous CPR action items.

CPR inputs are at the Accounting Classification Reference Number (ACRN) and task level; however, if issues arise at levels below the task level, the contractor shall provide CPR inputs for the subtasks associated with the issues. In addition, the contractor shall provide a monthly status and projected requirements of funds and work completion for evaluation of the contractor’s progress based on the PWS tasks and subtasks, in accordance with CDRL A001. In the CPR, the contractor shall prepare and maintain a Work Breakdown Structure (WBS) and project schedule for the overall support requirement to include schedules for each subtask. The WBS and schedules shall be developed and baselined, to include:

· The project schedule showing any proposed changes, the reasons for changes and the potential impact on the program

· Descriptions of activities and deliverables for the contract during the current month. The descriptions shall include problem definitions and recommendations for problem resolutions. Particular attention shall be given to risk management associated with the program’s strategic planning activities.

· The CPR shall provide a monthly status of work completed against the WBS baselined plan and projected funding requirements for the remainder of the period (by month). These totals shall be broken out by task, subtask, and person. Other Direct Costs (ODCs) are to be included in their task totals, respectively.

· Trips, technical visits, and related results (outcomes) for the reporting period.

· Personnel reassignments (In accordance with the key personnel clause of the contract)

· The contractor shall also indicate on each month’s CPR where there is coordination and issue resolution

CPR meeting minutes shall be delivered to the Government within two working days after the meeting in accordance with CDRL A002.

6.1.2 Acquisition Support: The contractor shall develop and update all DoDI 5000.87 statutory/regulatory documentation (e.g., Acquisition Strategy, User Agreements, Value Assessments). Additionally, they will maintain the PMO’s internal battle rhythm, draft executive briefings for DISA/DoW Chief Information Office (CIO)/DoW Chief Digital and Artificial Intelligence Office (CDAO) leadership, manage the formal Risk Register/Issue tracking processes, and map Agile metrics to DoD compliance requirements.

6.1.3 Statutory Value Assessment Support: The contractor shall support the Government in planning, preparing, and executing the statutory Annual Value Assessment as required by DoDI 5000.87. The contractor shall assist in collecting and analyzing objective evidence of program performance, including test and evaluation results, user feedback, operational metrics, and technical performance measures. Specific support tasks shall include:

Coordinating with the Chief Developmental Tester, Product Owner, and other government stakeholders to gather required assessment data;

Supporting the development of Value Assessment briefing materials and reports for presentation to the EMS Senior Steering Group (SSG), Component Acquisition Executive (CAE), and other senior leadership;

Analyzing program progress against established metrics and performance objectives;

Identifying and documenting program risks, issues, and recommended courses of action within the Value Assessment;

Maintaining traceability between the Value Assessment and other program documentation (e.g., Acquisition Strategy, Product Roadmap, and Risk Register).

All Value Assessments shall be conducted in accordance with DoDI 5000.87 and applicable DISA and DoW guidance.

6.1.4 Risk, Issue, and Opportunity Management Support: The contractor shall support the EMS IT Modernization PMO in developing and maintaining an effective Risk, Issue, and Opportunity (RIO) management process for the overall program. The contractor shall:

· Assist in the development and maintenance of a Program Risk Management Plan;

· Maintain the official program Risk Register, capturing for each risk at a minimum: risk number, date identified, status, description, impact, probability, mitigation plan, owner, and required resolution date;

· Update the program Risk Register twice per month (or more frequently as directed by the Government);

· Ensure alignment and synchronization between the internal PMO risk register and all official DISA risk tracking systems.

6.1.5 Information Management Support: The contractor shall support the organization in overseeing the lifecycle management and governance of digital knowledge repositories and operational data assets across the enterprise. The contractor will design, implement, and maintain structured information architectures, access permissions, metadata tagging, and archiving workflows to facilitate efficient knowledge sharing and data discovery. The contractor shall enforce DoD records management policies, the optimization of digital workflows, provide support in audit readiness, and ensure seamless collaboration across cross-functional units while maintaining data integrity and security boundaries.

· 6.1.6 Transition In/Out:

· Transition-In (Phase In). All key personnel/key positions must be onboard at start of the period of performance. 75% percent total staffing must be complete within two weeks of the start of the PoP and 100 percent within 30 days.

· Transition-Out (Phase Out) (OPTIONAL). The contractor shall collaborate with the COR at least 120 days or sooner, prior to the end of the contract, to develop a transition-out plan IAW FAR 52.237-3.

6.2 Task Area 2 – Product Management, Product Strategy & Sustainment, Spectrum Mission Analysis, User Experience, and Training The contractor shall provide advisory support to the Government EMS IT Modernization Product Owners and operational users to translate strategic objectives into executable agile development efforts. This includes mapping legacy spectrum workflows to the MSS environment, optimizing user experience for operational environments, and supporting joint training activities.

6.2.1 Agile Product Management Support: At the direction of the EMS IT Modernization product manager, the contractor shall support the mapping of the overall strategic vision into actionable agile sprints across diverse capability areas (e.g., spectrum dependent system certification, frequency assignment and scheduling, host-nation coordination, interference resolution, joint planning, electromagnetic warfare (EW) reprogramming, modeling and simulation (M&S), and strategic decision-making). This shall include working with the EMS IT Modernization product manager and the MSS development team to translate operational needs into actionable backlog tasks. In conjunction, they will support the active management of backlogs tailored to specific EMS workflows. They shall also support the on-going management of product roadmaps and assist the EMS IT Modernization product manager with aligning product roadmaps with the overarching PMO roadmap (e.g., aligning product releases with exercise planning and execution cycles). The contractor shall perform these tasks within the MSS (IL6)-hosted EMS IT Modernization PMO management environment.

6.2.2 Product Strategy & Sustainment Support: The contractor shall support the development and implementation of a comprehensive Product Support Strategy for the EMS IT Modernization program. This strategy shall address both the sustainment of cloud-based software and physical edge hardware, as well as the configuration management approach for development and sustainment. The contractor shall:

Develop a Product Support Strategy that defines how the program will sustain over-the-air software updates on the MSS platform and provide physical hardware support for edge devices;

Support the development of a Configuration Management Strategy that defines how configuration items, baselines, changes, and versioning will be controlled throughout development and sustainment;

Support the identification of sustainment requirements, spares planning, maintenance concepts, and long-term supportability for JOE hardware;

Assist in the development of product support plans, including lifecycle cost estimates and supportability analysis;

Coordinate with the Government Product Support Manager to ensure alignment between the product support strategy, configuration management approach, and overall program objectives;

Support the transition from development to sustainment activities as new capabilities are fielded.

6.2.3 User Engagement Support: The contractor shall support user engagement activities to identify, validate, and prioritize development requirements. This includes facilitating user stories gathering sessions to inform EMS IT modernization product decisions. This could include but would not be limited to; conducting tabletop exercises (TTXs), hosting regular stakeholder engagement meetings, conducting one-on-one user interviews, and participating in Combatant Command (CCMD)/DoW exercises where EMS applications are used.

6.2.4 Spectrum Mission Analysis: The contractor shall support mission analysis and workflow optimization across core EMS functional areas, including but not limited to frequency assignment and allocation, spectrum certification, host nation coordination, electromagnetic interference (EMI) resolution, Joint Communication Electronics Operating Instructions (JCEOI), and Joint Restricted Frequency List (JRFL) management. The contractor shall work with Government stakeholders and the MSS development team to document “As-Is” processes, define “To-Be” workflows, and identify opportunities for automation and efficiency improvements.

6.2.5 User Experience Support: The contractor shall support user-centered design efforts focused on reducing cognitive load and improving usability of the MSS interface for operators in high-stress tactical environments and DDIL conditions.

6.2.6 Joint Training Coordination: The contractor shall support the development and execution of a comprehensive training program for the EMS IT Modernization effort. The contractor shall assess both user training needs across the Joint Force and internal PMO/team training requirements. The contractor shall:

Identify and document user training requirements for operators and analysts transitioning from legacy systems to the modernized MSS environment;

Support the development and maintenance of a Joint Training Plan and updated operator TTPs.

Coordinate with Service schoolhouses and training commands to integrate new EMS capabilities into formal training curricula Assess internal PMO and support team training needs, including familiarization with MSS platform, tools, and development environment.

Support the coordination of training ranging from foundational platform familiarization to advanced technical training on CDAO MSS tools and capabilities.

6.3 Task Area 3 – Tenant Integration, M&S, Data, & Interoperability The contractor shall provide technical advisory and engineering support for the integration of M&S capabilities, data standardization, system interoperability, and edge operations within the Maven Smart System (MSS) environment.

· 6.3.1 EMS M&S Technical Support: The contractor shall provide technical support and analysis to the Government M&S Integration Lead for the evaluation and integration of physics-based models into the MSS environment. The contractor shall:

Develop and maintain an initial prioritized list of non-proprietary, peer reviewed physics models and engines recommended for integration into the MSS environment;

Coordinate the initial list of models with the Government M&S integration Lead for review, refinement, and formal approval;

Conduct detailed technical studies on the approved models to assess technical maturity, suitability, limitations, data requirements, interoperability, performance, and supportability;

Provide substantiated recommendations and documented trade-off analyses to support Government decision-making Update and maintain the approved models list throughout the program as new requirements or capabilities emerge.

6.3.2 EMS M&S Development and Integration Support: The contractor shall provide technical advisory and engineering support for the integration of physics engines and models from the Government-approved M&S Model List (developed under Section 6.3.1) into the MSS tenant space. The contractor shall:

Assist with the definition of technical requirements and interface control documents (ICDs) for connecting the approved physics engines to MSS via Application Programming Interfaces (APIs).

Support the design and validation of methods for rendering mathematical outputs (such as electromagnetic propagation contours, jamming footprints, and interference heatmaps) onto the MSS map interface;

Develop proof cases and test scenarios to verify that MSS implementations produce results consistent with known good models;

Provide subject matter expertise on optimizing model performance and outputs for use in DDIL edge environments on JOE nodes;

Support integration testing, verification, and troubleshooting efforts between the approved physics engines and the MSS platform, including participation in the development of testing and evaluation plans.

6.3.3 Joint C2 & Fires Integration: The contractor shall provide technical advisory support for the integration of EMS capabilities with JC2 and Joint Tactical Fires systems. The contractor shall:

Support the development of technical requirements and architectures for spectrum data exchange between MSS and JC2/Fires platforms;

Assist in the definition and documentation of standardized data formats, interfaces, and protocols;

Support the identification and resolution of interoperability issues between EMS data and external Command and Control (C2) and Fires systems;

Provide subject matter expertise during integration events, exercises, and technical working groups.

6.3.4 Edge (DDIL) / JOE Architecture: The contractor shall provide technical advisory support for the design and implementation of resilient EMS capabilities in DDIL environments. The contractor shall:

Support the development of architecture and requirements for “store-and-forward” synchronization logic on JOE nodes;

Assist in the definition of form, fit, and function impacts of integrating EMS capabilities onto JOE platforms;

Support the design of data synchronization methods that ensure reliability and accuracy when operating in disconnected or degraded network conditions;

Provide subject matter expertise on edge computing constraints, bandwidth optimization, and tactical data handling for spectrum-related information.

6.3.5 Legacy Data Remediation & Profiling: The contractor shall support the identification of data cleansing resource requirements and development of a detailed legacy data remediation workflow for SXXI and End-to-End Supportability System (E2ESS) datasets. The contractor shall:

Conduct programmatic data profiling and quality analysis of legacy datasets, including large volumes of PDF records contained in the E2ESS dataset;

Leverage Large Language Models (LLMs) and Machine Learning (ML) techniques to assist in the identification, extraction, cleansing, and remediation of data from unstructured and semi-structured PDF records;

Support the development and documentation of data remediation rules, workflows, quality acceptance criteria, and automated remediation processes;

Assist in the execution of data cleansing, standardization, and quality remediation activities in accordance with Government-approved remediation plans;

Document data quality issues, remediation actions taken, and resulting improvements to support downstream migration and integration efforts.

6.3.6 Data Standardization & Ontology: The contractor shall support the definition and documentation of an initial EMS Data Standard and Ontology on MSS and continue to iterate on that ontology as the system and its architecture evolve over time. The contractor shall:

Provide subject matter expertise in the development of a comprehensive EMS data taxonomy and ontology that makes electromagnetic effects computable, searchable, comparable, and traceable across integrated C2 planning, execution monitoring, and assessment systems;

Support the mapping of legacy data structures and formats to the new unified EMS data standard;

Collaborate with Government stakeholders and development teams to refine and validate the ontology;

Document the data standard, ontology, and associated governance processes to enable consistent implementation across the program.

6.3.7 Legacy System Migration: The contractor shall support planning, oversight, and execution of a phased migration of legacy datasets and capabilities onto the unified MSS environment. The contractor shall:

Support the development of a detailed legacy system migration plan and strategy;

Assist in the identification, prioritization, and scheduling of legacy datasets and functionalities to be migrated, specifically including E2ESS, the Joint Spectrum Data Repository (JSDR), JSDR Strategic Planning and Analysis Dashboard Extensions (JSPADE), and Joint spectrum Interference Reporting Online (JSIRO);

Support the re-engineering and onboarding of legacy data and workflows into the MSS data standard ontology;

Provide subject matter expertise and coordination support during migration activates to ensure data integrity, completeness, and operational continuity;

Support the development of migration verification and validation procedures.

6.3.8 Legacy System Decommissioning & Sunset: The contractor shall support the Development and execution of decommissioning plans for legacy EMS systems. The contractor shall:

Support the development of formal decommissioning plans and schedules for the legacy SXXI system and the entire GEMSIS suite (including E2ESS, JSDR, JSPADE, and JSIRO);

Assist in the identification of operational risks and mitigation strategies associated with sunsetting legacy systems;

Support the development of verification methods to ensure that migrated capabilities on MSS meet or exceed the performance of the legacy systems prior to final decommissioning;

Coordinate with stakeholders to ensure a smooth transition and to prevent operational gaps during the sunset process;

Provide subject matter expertise and documentation support for all legacy system decommissioning activities.

6.4 Task Area 4 – Mission Assurance, Testing, and Product Support The contractor shall support mission readiness, system validation, testing, and sustainment activities to ensure that delivered capabilities meet operational, technical, and statutory requirements.

6.4.1 AI & Edge Test Engineer Support: The contractor shall support the testing and evaluation of AI models and edge capabilities. The contractor shall:

Execute automated and hands-on testing of AI models for accuracy, bias, and performance;

Support the validation of software performance on physical JOE hardware;

Support the development and execution of test plans, test cases, and evaluation procedures;

Document test results, deficiencies, and recommended corrective actions.

Deliverables All deliverables must be submitted to the government COR in the specified format by the due dates specified in each CDRL.

7. Performance Standards.

The COR will monitor the contractor’s performance in accordance with the Quality Assurance Surveillance Plan (QASP). The standards, acceptable quality levels (AQL), and surveillance methods are detailed in Table 2.

Task 6.1

· Kick-Off Meeting

· Meeting Minutes

· Monthly Status Report

· Monthly Contractor Performance Report

· Monthly NDA Status Report

· TO Management Plan

· Annual Value Assessment

· Program Risk Management Plan

· Acquisition Support Documentation

Target Criteria: 100% of the deliverables are submitted complete, accurate, and free of defects on first submission. 100% of the deliverables are submitted IAW the schedules specified in the correlating CDRL or the approved sprint roadmap. No revisions are needed.

Minimum Acceptable: of deliverables are submitted complete, accurate, and free of defects on first submission.

of deliverables are submitted in accordance with the schedules specified in the correlating CDRL or the approved sprint roadmap.

Revisions must be resolved within 5 business days.

The total number of deliverables completed for task 6.1 IAW the TO PWS divided by the number of deliverables required under this TO for task 6.1 IAW the TO PWS.

Task 6.1

· Key Personnel Target Criteria: Key Personnel positions are occupied 100% of the time by qualified personnel. No vacancies in key positions.

Minimum Acceptable: Key Personnel positions are occupied 75% of the time. Vacancies in key positions must be filled with qualified personnel within 30 days of vacancy.

The total key personnel positions filled based on roster audits and review of monthly status reports divided by the total key personnel positions required IAW section 13.9 of the TO PWS.

Task 6.3

· M&S Technical Support Target Criteria: Independent technical validations are conducted with zero mathematical or parameter-mapping errors; API specifications are 100% compliant with CDAO environments.

Minimum Acceptable: Independent technical validations are conducted with no critical or major mathematical or parameter-mapping errors. Any minor errors that are documented do not affect required functionality and have an approved correction plan. API specifications are 100% compliant with CDAO environments.

Cost Requirement: AQL is achieved when the invoices charged do not exceed 105% of planned costs.

The total number of independent technical validations that meet target/minimum criteria IAW task 6.3 of the TO PWS divided by the total technical analyses and validation reports selected for the independent technical validation review.

Task 6.4

· T&E Evaluation Target Criteria: Automated test cases are successfully run on 100% of major software releases; test logs and edge node verification are documented with no missing data fields.

Minimum Acceptable: Automated test cases are successfully executed for at least 90% of major software releases. At least 95% of test logs and edge-node verification records contain all required data fields; missing fields are documented and do not prevent validation of release performance or edge-node functionality.

Cost Requirement: AQL is achieved when the invoices charged do not exceed 105% of planned costs.

The total number inspection of test reports and edge verification logs that meet target/minimum criteria IAW task 6.4 of the TO PWS divided by the total number of test reports and edge verification logs required under this TO.

Tasks 6.2, 6.3, and 6.4

· Joint Training Plan

· System/Subsystem Design Description

· “As-Is” to “To-Be” Workflow Analysis

· Software Center Operator Manual // Software User Manual (Operator TTP)

· Interface Requirements Specification

· Interface Design Description

· Test Plan (AI & Edge Test and Evaluation Master Plan) Target Criteria: 100% of the deliverables are submitted complete, accurate, and free of defects on first submission. 100% of the deliverables are submitted IAW the schedules specified in the correlating CDRL or the approved sprint roadmap. No revisions are needed.

Minimum Acceptable: of deliverables are submitted complete, accurate, and free of defects on first submission.

of deliverables are submitted in accordance with the schedules specified in the correlating CDRL or the approved sprint roadmap.

Revisions must be resolved within 5 business days.

Cost Requirement: AQL is achieved when the invoices charged do not exceed 105% of planned costs.

The total number of deliverables completed for tasks 6.2 through 6.4 IAW the TO PWS divided by the number of deliverables the number of deliverables required for tasks 6.2 – 6.4 IAW the TO PWS.

8. Incentives.

This TO is hybrid requirement with both Cost-Plus-Fixed Fee and Firm-Fixed-Price CLINs. Performance will be documented in the Contractor Performance Assessment Reporting System (CPARS).

· Positive Incentives:

· Quality services and deliverables with this TO will be accepted by the Government, allowing the contractor to invoice for services rendered.

· Positive CPAR.

· Contractor will realize a higher rate of return in fee as total costs decrease.

· Negative Incentives:

· Negative CPAR.

· Letter of concern, show cause letters, cure notices, and termination.

· When unacceptable performance occurs, payment will be withheld for services until satisfactory corrective action is taken.

· Failure to meet all mandatory requirements at contract close-out will assess a 10.00% withholding of final payment until all close-out actions are completed.

9. Place of Performance Work is to be performed on-site at the specified mission location listed below, at an alternate work site, at the contractor’s facilities, or at any other designated location(s). Unclassified work may be performed at both the contractor and Government facilities. Classified work shall be performed at the Government facilities.

Government Facilities (Mission Locations):

1. DISA Headquarters 6910 Cooper Ave, Ft. George G. Meade, MD 20755 Alternative work sites allow for regular telework or remote work flexibilities and may be applicable. Regardless of where work is performed, the contractor shall ensure that work is completed effectively and that mission needs and requirements are met, without degradation of services. Also, the contractor may be required to account for the physical location of their personnel should this information be requested. The contractor shall propose Government site rates for all work performed at an alternative work site. Incidental charges incurred while working at an alternative work site (e.g., electricity, internet) are not allocable to the contract and associated TOs and shall not be billed to the Government.

All local travel is defined as travel within fifty miles of the contractor’s primary place of performance. Local travel will not be reimbursed. Long distance travel within Continental United States (CONUS) may be required to support the requirements of this PWS. Long-distance travel within CONUS shall be planned and conducted in support of the individual tasks contained in the contract. Long distance travel must be pre-approved in writing by the COR prior to the contractor incurring the cost in support of the applicable TO.

The maximum number of seats available in the government site for this effort is three (space waiver tracking # TBD for Government use only).

Secondary Place of Performance – Contingency Only. As determined by the Contracting Officer’s Representative (COR), contractor employees may be required to work at a secondary place of performance (e.g., home, the contractor's facility, or another approved activity within the local travel area) in cases of unforeseen conditions or contingencies (e.g., pandemic conditions, exercises, government closure due to inclement weather). Additionally, the contractor may be required to account for the physical location of their personnel should this information be requested by the COR. Non-emergency/non-essential contractors should not report to a closed government facility. Contractor shall prepare all deliverables and other contract documentation utilizing contractor resources. To the extent possible, the contractor shall use best efforts to provide the same level of support as stated in the PWS. In the event the services are impacted, reduced, compromised, etc., the Contracting Officer or the contractor may request an equitable adjustment pursuant to the Changes clause of the contract.

10. Period of Performance The period of performance shall consist of one (1) 12-month base period, and three (3) consecutive 12-month option periods, as follows:

Base Period: Award +12 months Option Period 1: 12 months Option Period 2: 12 months Option Period 3: 12 months

Recognized Federal Holidays: The contractor is not required to perform services on Federal Holidays (as specified on the U.S. Office of Personnel Management website), unless otherwise specified by the COR.

Unplanned Federal Government Closure: In the event an authorized official, by either executive or legislative order, declares Federal offices closed (treated as a holiday for pay and leave purposes), the order only applies to Federal employees (unless otherwise stated in the order).

11. Security Requirements This section supplements Block 13 of the Government provided DD Form 254, Contract Security Classification Specification. The following security requirements shall apply to this effort.

The contractor shall coordinate visits with site Point of Contract (POC)s providing at least a 72-hour notice (or according to each site security requirements) prior to any site access. Contractor personnel without security clearances performing any task under this PWS must be escorted by cleared DISA personnel (civilian, military, or contractor).

References:

a. DISA End User Access Agreement

b. DISA Instruction 240-240-01, External Peripheral Devices Authorized for Network Connectivity

c. DISA Instruction 240-110-8, Information Security

d. DISA Instruction 240-110-34, Controlled Unclassified Information (CUI)

e. DISA Instruction 240-110-36, Personnel Security

f. DISA Instruction 240-110-38, Industrial Security

g. DISA Instruction 240-110-43, Counterintelligence

h. DISA Instruction 240-110-43, Insider Threat Program

i. DISA Instruction 630-230-19, Cybersecurity

j. DoD Manual 5200.01, Vol. 1 and 3, DoD Information Security Program, 17 January 2025

k. DoD Manual 5200.01, Vol. 2, DoD Information Security Program, 28 July 2020

l. DoD Instruction 5200.48, Controlled Unclassified Information (CUI), 6 March 2020

m. DoD Manual 5200.02, Procedures for the DoD Personnel Security Program (PSP), 3 April 2017, Change 1, 29 October 2020

n. 32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM), 24 February 2021

o. DoD Directive 5240.06, Counterintelligence Awareness and Reporting (CIAR), 17 May 2011, Change 3, 31 August 2020

p. DoD Instruction O-5240.24, Counterintelligence (CI) Activities Supporting Research, Development, and Acquisition (RDA), 8 June 2011, Change 2, 15 July 2020

q. DoD Instruction 5205.16, “The DoD Insider Threat Program,” December 20, 2024

r. DoD Instruction 5230.24, Distribution Statements for DoD Technical Information, 10 January 2023

s. DoD Instruction 8510.01, Risk Management Framework for DoD Systems, 19 July 2022

t. DoD Manuel 5400.07, DoD Freedom of Information Act (FOIA) Program, 25 January 2017

u. Security Executive Agent Directive 3 (SEAD 3) Reporting Requirements for Personnel With Access To Classified Information or Who Hold Sensitive Position, 12 June 2017

v. Security Executive Agent Directive 4 (SEAD 4), National Security Adjudicative Guidelines, 8 June 2017

w. DISA Instruction 240-15-4 United States Security Authority for North Atlantic Treaty Organization Affairs

11.1 Facility Security Clearance. Work performed under this contract/order is up to the Secret level. Therefore, the company must have a final Secret Facility Clearance from the Defense Counterintelligence and Security Agency (DCSA) Facility Clearance Branch.

11.1.2 Invalidated Facility Clearance. Companies with invalidated facility clearances (including those in partnerships, subcontracts, and Joint Ventures) are not eligible to bid on or be awarded any new or additional DISA classified contracts, subcontracts, or receive additional classified information except for information necessary for the completion of your current classified contracts. In addition, those companies with invalidated facility clearances will not be permitted access to all DISA networks. Performance on any DISA classified contracts, at any location, will not be authorized until it has been granted a Facility Security Clearance (FCL) at the appropriate level by DCSA.

11.2 Security Clearance. All personnel performing on or supporting a DISA contract/order in any way shall be United States citizens. The personnel security requirements for this contract/order cover the individuals supporting the Task Areas delineated in the table below. Contractor personnel must possess the interim or final security clearance eligibility delineated in the table below when performance starts.

Table 3 – Security Clearance Levels and Justifications

6.1 Task 1

6.2 Task 2

6.3 Task 3

6.4 Task 4

Security clearance levels required:

(6) SECRET

11.3 Investigation Requirements. All personnel requiring Secret access under this contract/order shall undergo a favorably adjudicated Tier 3 (T3) Investigation formerly known as a National Agency Check, Local Agency Check and Credit Check or Access National Agency Check and Inquiries as a minimum investigation. Enrollment into Continuous Evaluation current within 5 years and, reflected in DISS, would meet the requirement for current PR.

11.3.1 The contractor is required to have personnel cleared with an interim or final Secret (as specified in the table located in section 11.2) at contract start date. If contractor personnel are replaced during performance of the contract, replacement personnel should also have interim or final clearance Secret (as specified in the table located in section 11.2).

11.4 Visit Authorization. Visit requests shall be processed and verified through the DISS to the Security Management Office (SMO) DKABAA10 for DISA HQs. DISS visits for contracts/orders are identified as “Other” or “Temporary Additional Duty (TAD)/Temporary Duty (TDY)” and will include the Contract/Order Number of the contract/order in the Additional Information section. Contractors that do not have access to DISS may submit visit authorizations by e-mail in a password protected portable document format file (.pdf) to the COR/ACOR specified in PWS/SOW Section 1.0.

*Prior coordination with the DISA COR should be made via email to ensure the Visit Authorization Letter (VAL)/ Visit Authorization Request (VAR)/ Visit Termination Notification (VTN) process is agreed upon and properly secure.

11.4.1 VAR Package. VAR Centers must receive VAR packages from the Security Manager (via email and require pre-approval from the assigned DISA COR) at a minimum of five business days in advance of the initial report date or renewal. For option years, VARs should be renewed 30-90 days prior to the expiration date unless modified sooner for changes such as name, COR/sponsor, contract modification, etc. As an option, a VAR can be approved for up to a maximum of three (3) years within the POP for contractors. The VAL/VAR/VTN should be sent via email to the appropriate COR. The VAL/VAR/VTN should be sent using in a locked “Zip” file in one e-mail and then followed up by another e-mail with the password to unlock the Zipped file, because it contains sensitive information covered by the Privacy Act.

Documents to include in the VAR Package (DISA Field Sites may have site specific VAR requirements):

1. Inter-office Memorandum (IOM)

2. DD Form 254 Prime and/or Sub (Good Standing approval emails for current option year)

3. PWS/SOW/Sub Memo

4. DISS verification of Visit Authorization by Security Manager

5. (Optional: see NOTE below) Contractor VAL signed by the Contractor Facility Security Officer (FSO)

NOTE: If DISS is not available, the VAL must contain the following information on company letterhead:

· Company name, address, telephone number, facility security clearance

· Commercial and Government Entity Code (CAGE CODE)

· Contract/Order Number

· Name, Social Security Number (SSN), date and place of birth, and citizenship of the employee intending to visit, email address, and phone number

· Certification of personnel security clearance and any special access authorizations required for the visit (type of investigation & date and adjudication date & agency)

· Name of COR/Alt COR

· Dates or period the VAL is to be valid (i.e., Start date / End date)

11.4.2 VTN Package. The Contractor FSO will forward a VTN letter to the DISA COR identified in the PWS/TO/Sub for all employees leaving the contract/TO/subcontract.

11.4.2.1 In addition, the DISA CORs and security managers shall inform the DISA Security Office when contractor personnel are removed for cause from a contract supporting DISA. This step is to identify contractor personnel removed for security related issues in case of a return to DISA without appropriate vetting. This step will also provide security with pertinent information to make an informed decision regarding potential contractor employees’ access to secure facilities and sensitive information. “For Cause” is information regarding an individual that falls into one or more of the actions or incidents that are within one of the 13 adjudicative guidelines as cited in the Security Executive Agent Directive (SEAD) 4:

a. Allegiance to the United States

b. Foreign Influence

c. Foreign Preference

d. Sexual Behavior

e. Personal Conduct

f. Financial Considerations

g. Alcohol Consumption

h. Drug Involvement and Substance Misuse

i. Psychological Conditions

j. Criminal Conduct

k. Handling Protected Information

l. Outside Activities

m. Use of Information Technology

Other actions:

· Incidents involving violence in the workplace or harassment.

· Misuse of time.

· Inspector General or General Counsel related inquiries.

· Failure to comply with security policies and procedures.

· Other reasons that prompted removal of a contractor.

The VTN must contain the following information on company letterhead:

· Company name, address, telephone number, facility security clearance

· CAGE CODE

· Contract/Order Number

· Name, SSN, date and place of birth, and citizenship of the employee, email address, phone number

· Date contractor Common Access Card (CAC) was collected

· Name of COR/Alt COR

· Termination Date

· Reason for Termination: <insert reason from the 13 adjudicative guidelines, other actions, or type “No longer working on contract”>

*Any VAL/VAR submitted without the above information will be denied.*

11.5 Security Contacts. DISA Security Personnel can be contacted for Industrial or Personnel Security related issues at the following:

For Center or Directorate-specific security related matters,…