TRIDENT_PWS_DRAFT_UNCLASS.docx

THREAT REDUTION THROUGH INTEGRATED DEFENSE & EXPERT NETWORK TACTICS (TRIDENT)

PERFORMANCE WORK STATEMENT (PWS)

DEFENSE THREAT REDUCTION AGANCY (DTRA)

COMBAT SUPPORT DIRECTORATE (CZ)

1. INTRODUCTION

DTRA requires support services to provide a wide range of professional analytical services to assist with its mission of countering and deterring Weapons of Mass Destruction (WMD) and emerging threats in the Continental United States (CONUS) and Outside the Continental United States (OCONUS).

The DTRA Combat Support (CZ) Directorate provides advisory and operational support to Combatant Commands (CCMDs), Interagency partners, and Special Operations Forces (SOF) to enhance Countering Weapons of Mass Destruction (CWMD) capabilities. This support includes campaign management, operational planning, irregular warfare support, and WMD defeat advisory services.

These efforts will enhance DTRA’s situational understanding of Combatant Commands (CCMDs) with the integration of analysis, capabilities, technologies, and lessons learned to defeat the enemy networks that employ emerging threat weapons and WMD for strategic effect.

To accomplish this mission, DTRA CZ requires highly specialized contracted support with expertise in WMD, CWMD operations, special access planning, irregular warfare, military deception (MILDEC), and advisory services.

2. SCOPE

The scope of this requirement will provide effective support for globally integrated operations, timely responses to WMD threats and activities, and enhanced collaboration with interagency and international partners. The requirements of this effort will provide Professional Services to DTRA CZ across multiple tasks to include classified and compartmented support, operational and strategic planning, data-driven decision support, and campaign management.

3. PLACE OF PERFORMANCE

The primary place of performance for this effort will be Ft Belvoir, VA with additional customer sites, both CONUS and OCONUS.

TASK 1: PROGRAM MANAGEMENT

1.1 OBJECTIVE

The contractor shall ensure all contract requirements are met, provide cost tracking and financial transparency, and facilitate coordination with Government stakeholders. The contractor shall designate a Program Manager (PM) to serve as the primary interface with the Contracting Officer (KO), Contracting Officer’s Representative (COR), Alternate Contracting Officer’s Representative (ACOR), or Technical Point of Contact (TPOC). Contractor shall fully empower its PM to manage resources and make program decisions that are within the scope of the TRIDENT contract. Contractor’s PM shall provide management oversight of all program activities, inclusive of the processes, procedures, reports, checks, audits, and systems put in place to ensure the quality of work effort and deliverables.

The contractor’s PM shall be responsible for:

· Managing contract personnel, including subcontractors.

· Overseeing contract execution, ensuring compliance with contract objectives.

· Identifying and mitigating schedule, performance, technical, and financial risks.

· Conducting cost monitoring and variance analysis.

· Implementing quality assurance measures to maintain performance standards, including timely and accurate submission of all contract deliverables.

1.2 SUBTASKS

1.2.1 PROGRAM MANAGEMENT PLAN (PMP)

The contractor shall develop and submit a Program Management Plan (PMP) in accordance with (IAW) CDRL A001 for government approval that achieves performance outcomes in accordance with the Acceptable Quality Levels (AQLs) described in performance requirements summary (PRS).

The contractor shall address, at a minimum, the following in their PMP:

· Organizational structure.

· Staffing plan.

· Communications plan.

· Business processes and procedures.

· Task area management.

· Describe how contractor support services will be matrixed across task areas.

· Functional area management.

· Describe how contractor will integrate functional areas

· Subcontractor(s) management.

· Scheduling and monitoring of global mission support operations.

· Prioritizing Requests.

· Problem solving.

· Travel.

· Procurement function.

· Property management.

· Contract management.

· Financial management.

· Reporting.

· Deliverable management.

After government approval and acceptance of the PMP, the contractor shall receive the COR’s acceptance in writing of the proposed change to the PMP. Contractor shall provide to the government any revisions to PMP within five business days of when changes are agreed.

1.2.2 MEETINGS, CONFERENCES, REVIEWS, AND EVALUATIONS

The contractor shall support recurring status meetings, Technical Interchange Meetings (TIMs), conferences, In-Progress Reviews (IPRs), and other performance evaluations with the government to discuss program progress, identify potential obstacles or risks to continued progress, and proactively apply resources to mitigate risk or resolve identified problems (realized risks).

The contractor shall prepare agendas, meeting minutes, action item lists, and presentation materials for meetings, conferences, reviews, and evaluations. Contractor shall notify the government of its readiness prior to the start of any meeting, review, conference, or evaluation.

The following instructions are applicable to all meetings, reviews, conferences, and/or evaluations:

· All meetings, reviews, conferences, and evaluations will be held at DTRA’s facility unless otherwise directed by the government. Contractor shall provide teleconferencing capability, internet access, and facility location (within 25 miles of the DTRA facility) to accommodate necessary participation. Contractor shall propose a date for the meeting, review, conference, and/or evaluation for the COR's approval.

· For all presentations, the government reserves the right to revise the agenda and/or presentation. Contractor shall provide contractor personnel who are knowledgeable of the topic when responding to government questions. Contractor shall prepare and deliver a summary of open, pending, and closed action items and presentation materials prior to the start of each scheduled conference, meeting, review, or evaluation in accordance with CDRL A002. The COR will revise the lead time between delivery of presentation materials and the subject conference, meeting, review, or evaluation to balance adequate government review time and currency of the subject material.

· The contractor shall record and submit minutes in accordance with CDRL A002 following the event for government review and concurrence. Contractor shall track action items. Each assigned action item shall have a due date and responsible person(s) assigned, who shall provide the status of the action at agreed upon intervals until the action is closed. Unless otherwise specified by the government, the contractor shall respond to all action items with a written closure statement. In the event an action item cannot be closed promptly, the contractor shall develop a plan of action and milestones (POAM) for closure. Contractor shall update presentation material, action items, and meeting minutes based on government comments and feedback on draft minutes. Contractor shall submit final documents to the government in accordance with CDRL A002 after receiving government comments and feedback. If government has no comments or feedback, then the initial draft will become the final and no further submissions are required.

1.2.3 PROGRAM KICKOFF MEETING

The contractor shall schedule, coordinate, and host a Program Kick-Off Meeting at a location approved by the government within seven calendar days after contract award. The meeting is to provide an introduction between the contractor personnel and government personnel who will be involved with the contract. The meeting will also provide an opportunity to discuss technical, management, and security issues, and travel authorization and reporting procedures. At a minimum, the attendees shall include the contractor’s PM, contract manager, and other contractor key personnel, as well as DTRA’s PM, COR, ACOR, and KO.

At least three days prior to the Program Kick-Off Meeting, the contractor shall provide a Program Kick-Off Meeting Agenda for review and approval by the PM, COR, and ACOR prior to finalizing (CDRL A002). The Program Kick-Off agenda shall include, at a minimum, the following topics:

· Program Management Plan (PMP) that contains contractor’s approach for providing and ensuring performance.

· Points of Contact (POCs) for all parties

· Performance reporting (web-portal)

· Financial reporting and invoicing

· Quality Controls

· Transition-In Plan.

· Staffing Plan and status, to include Time Phase Labor Matrix (TPLM)

· Security discussion and requirements (i.e., building access, badges, Common Access Cards [CAC]).

· Personnel discussion (i.e., roles and responsibilities and lines of communication between contractor and government).

1.2.4 TECHNICAL MEETINGS

The contractor shall participate in technical working groups, technical interchange meetings, and support technical requirements review meetings throughout the period of performance. Examples include non-recurring and recurring (on a daily, weekly, or monthly basis) stand-up meetings, TRIDENT leadership meetings, project and technical status briefings, requirements reviews, technical exchanges meetings with internal and external organizations, recurring briefings to government leadership, and other briefings and meeting support as required.

The contractor shall be responsible for coordination of working group activities that cross task areas and for representation on integrated project teams to ensure collaborative TRIDENT mission activities are properly supported. The contractor shall also develop briefings, presentations, agendas, materials, and minutes (CDRL A002) and communicate open action item statuses and issues to COR, ACOR, and other stakeholders as appropriate.

1.2.5 IN PROGRESS REVIEWS (IPR)

The contractor shall present the Monthly Status Report (MSR) at a monthly IPR meeting to the DTRA PM, COR, ACOR and other representatives from the TRIDENT team. IPR shall be scheduled within five business days after MSR delivery, pending availability of government personnel.

The contractor shall provide a status of work being performed, any open action items, ongoing risk mitigation efforts, quality control issues, and the financials under this contract. Contractor shall use IPRs to provide program insight to government representatives to facilitate informed decision making by TRIDENT leadership. Contractor shall also develop briefings, presentations, agendas, materials, and minutes (CDRL A002) and communicate open action item statuses and issues to DTRA COR, ACOR, and other stakeholders as appropriate.

1.2.6 FINANCIAL MANAGEMENT

The contractor shall maintain and provide financial reports as requested by the KO/COR for “funding spend plans” for special projects and specific fund types, estimate-at-completion (EAC) for all funding categories, labor, and other direct costs (ODC) breakouts for contract funding modifications, Rough Order of Magnitude (ROM) cost estimates for pending projects. The contractor shall develop impact statements that illustrate funding constraints based on budget reductions and other funding restrictions. Contractor shall assist and provide recommendations to maintain and achieve government resource obligation objectives.

By the 15th of every month the Contractor shall prepare and provide monthly financial reports detailing labor costs and ODCs that support DTRA planning, programming, budgeting, and execution. Contractor’s cost and accounting system shall be capable of tracking multiple Accounting Classification Reference Numbers (ACRNs) and Contract Line-Item Numbers (CLIN). At a minimum, this monthly report shall depict (by CLIN and ACRN cumulative and monthly) to include ceiling, funded, invoiced costs, obligated costs not invoiced, obligated sub-contractor labor (invoiced as well as reported/not invoiced), and remaining funding. Further, the contractor shall provide its assessment of labor and ODC burn rate, projected date the contract/CLINs will be 75% spent, and an EAC (CDRL A003)

1.2.7 TRANSITION IN

The contractor shall develop and submit a Transition-In Plan to the government for approval within seven (7) days of contract award (CDRL A005). Transition shall begin immediately following contract award. Initial Operational Capability (IOC) is achieved within seven (7) days of contract award (on or before the Project Kick-Off meeting). Full Operational Capability (FOC) is achieved as soon as possible, but no later than (NLT) sixty (60) calendar days from award.

IOC is defined as follows:

· All required personnel to accomplish transition-in activities are in place.

· Initial baseline Time Phased Labor Mix (TPLM) has been submitted to the government and required staffing in-processing activities are in progress.

· Coordination efforts are established and synchronized with legacy contractors for their transition-out activities (facilitated by government).

· Contractor is in full control of transition-in activities.

FOC is defined as follows:

· All task areas are fully staffed with fully qualified and trained personnel.

· Contractor assumes full responsibility for management of all contract requirements.

· All performance measures are fully accepted and are being reported.

The contractor shall ensure a smooth transition of support services with no degradation in TRIDENT’s mission capabilities during transition. Contractor shall ensure mission continuity and mitigate risks to mission-critical activities during the transition period. Contractor shall plan for all contingencies from gradual to immediate staffing for time sensitive missions.

1.2.8 STAFFING

The contractor shall identify and assign ample contractor resources to meet competing priorities of task areas and projects assigned; however, where trade-offs are necessary (e.g., later delivery of other tasks / projects because of prioritization decisions), the contractor shall apprise the COR of trade-offs and impacts. It is expected that contractor resources will be multi-functional / disciplined in satisfying staffing needed for executing requirement support (task / project work efforts) in a timely manner.

The contractor shall maintain and administer a security program in accordance with the National Industrial Security Program Operations Manual (NISPOM) DoD 5220.22M. Loss or suspension of required security clearance as set forth on the DD Form 254, “Contract Security Classification Specifications,” would result in the contractor’s inability to perform in accordance with the terms and conditions of this contract. As a result, the contractor would be subject to termination under the appropriate termination clause herein.

Government reserves the right to direct any contractor employee to be removed from performance, directly or indirectly, whenever there is probable cause to believe, based on all facts available, that such action is warranted in the interest of national security. This action shall be made whether the cause is deemed sufficient severity to warrant action to terminate the contractor’s or individual’s security clearance. Government also reserves the right to remove any contractor for the purpose of conducting any investigation of alleged misconduct that may, in the opinion of the Contracting Officer, jeopardize the security of the project. Loss or suspension of required facility security clearance as set forth on the DD 254, “Contract Security Classification Specifications,” would result in the contractor’s inability to perform in accordance with the terms and conditions of this contract. As a result, the contractor would be subject to termination under the appropriate termination clause herein.

All contractor performing work under this contract at a DTRA location, or performing functions deemed applicable, must meet the following security requirements:

· Possess a current Top Secret (TS) clearance with a current Sensitive Compartmented Information (SCI) eligibility determination reflected in the Joint Personnel Adjudication System (JPAS).

· Maintain all minimum required Special Access Program (SAP) read-in and Special Technical Operations (STO) access.

· Obtain and maintain Alternative Compensatory Control Measures (ACCM) access, as required.

· As required by specific mission partners, personnel may be required to successfully complete a Counterintelligence (CI) Polygraph examination.

· As required by specific mission partners, personnel may be required to obtain and maintain Sub-Gamma access.

1.2.9 KEY POSITIONS

The contractor shall identify and provide resumes of all proposed personnel identified for key positions. The COR and representatives from TRIDENT will review and approve resumes prior to personnel starting work in key positions.

Key positions for this requirement are:

· X

· XX

· XXX

Government desires that personnel filling key positions be assigned for the duration of the contract period, to ensure a consistent approach for management and execution of mission performance. All personnel assigned to key positions shall possess a current Top Secret (TS) clearance with current Sensitive Compartmented Information (SCI) determination reflected in the Joint Personnel Adjudication System (JPAS) or eligibility for SCI in JPAS.

The contractor shall not replace any personnel filling a key position without written notification to and concurrence from the KO. Notification shall be NLT ten (10) calendar days in advance of all proposed substitution and shall include justification (including resume(s) and labor category of proposed substitution(s)) in sufficient detail to permit evaluation of the potential impact on mission performance. Substitute personnel for key positions shall meet or exceed required qualifications.

1.2.10 NON-KEY POSITIONS

All contractor personnel shall maintain certifications as required by DoD Directive 8140.01 and DoD Instruction 8570.01-M, as amended. Contractor personnel shall comply with DTRA requirements to execute and comply with privileged and/or non-privileged IT access and user agreements. All contractor personnel whose duties require privileged access to DTRA IT assets shall have required cybersecurity workforce certifications and qualifications on the first day of duty and shall provide supporting documentation upon request. All personnel filling non-key positions whose performance of work is required at DTRA location or performing applicable functions shall possess a current TS clearance with current SCI determination reflected in JPAS or eligibility for SCI in JPAS.

1.2.11 TRANSITION OUT

The contractor shall develop and submit a Transition-Out Plan (CDRL A006) to the government for approval ninety (90) days prior to end of contract. Contractor shall begin transition-out activities no earlier than sixty (60) days prior to contract completion or upon government acceptance of Transition-Out Plan, whichever comes first. Contractor shall follow the plan to transfer all material, information, and rights thereto to the government prior to contract completion. The contractor shall ensure transition-out is planned and managed effectively; support is sustained in a controlled and deliberate manner throughout transition with no degradation in capabilities.

At a minimum, the contractor’s Transition-Out Plan shall:

· Identify all Government-Furnished Material (GFM) and Contractor-Furnished Material (CFM) as well as information and material developed during contract performance that was used in execution of TRIDENT’s mission.

· Describe contractor’s plan for updating system descriptions and technical descriptions of all software, systems, and mission support activities delivered or performed under the contract.

· Facilitate transition of administrative and privileged access to incoming contractor, ensuring that no administrative access is lost.

· Describe contractor’s plan for submitting a Final Contract Report documenting status of all ongoing efforts and projects and a Smart book/turnover binder containing copies of all plans, policies, procedures, points of contact, file storage locations for documentation and other information.

· Identify and manage transition-out risks in such a way as to ensure no disruption to vital government business functions or mission operations.

· Describe contractor’s plan for effective communications/meetings with incoming contractor and government personnel throughout the transition-out period.

· Pledge its full cooperation in providing necessary operational knowledge to incoming contractor.

The Transition-Out Plan shall also address the following for knowledge transfer:

· Project management processes.

· Identification of points of contact.

· Location of technical and project management documentation

· Status of ongoing initiatives and projects.

· Incoming contractor coordination to ensure a seamless transition.

· Transition of Key Personnel roles and responsibilities.

· Identification of schedules and milestones.

· Identification of actions required of the government.

The contractor shall facilitate the accomplishment of a seamless transition to an incoming contractor and/or government personnel prior to expiration of the contract.

1.2.12 REPORTING

The contractor shall submit reports and data as required by appropriate Contract Data Requirements Lists (CDRLs) and as requested by the KO, COR, or ACOR. When formats are not specified, contractor developed formats are allowed. Contractor shall ensure standard formats are used throughout the contract period. All reports and data shall be posted to the appropriate task area within the TRIDENT web portal. All reports and submission requirements shall be posted IAW established CDRL requirements. In concert with the QCP, the contractor shall establish a process for review and submittal of all contract requirements. Contractor shall provide draft submission IAW CDRL requirements and shall make any corrections and adjustments necessary as identified by the government. Any report submitted shall become the “final” report if no government comment and/or corrections are provided to contractor within 30 days or timelines outlined in the CDRL.

1.2.13 MONTHLY STATUS REPORT

The contractor shall prepare and coordinate monthly status reports (MSR) in accordance with CDRL A007. The report shall contain actual hours expended, projected hours to be expended, delta between actual and projected hours/spend plan and cumulative totals by CLIN. In addition, workload status will be identified to include acquisition support performed; Purchase Request (PR)/Contract identification, description of action and action status. The report will also contain on-going and long-term projects; projects pending review and approval, policy, and procedures reviews. This report will identify training attended, projected training, core hours and projected leave of absence for next calendar month. Report format is at the discretion of the contractor, however; report should be at an operational level for use as a planning and management tool. The report shall be submitted not later than close of business on fifteenth day following first of the month. Dissemination and release of information contained in monthly report is at discretion of the COR.

MSR shall also include monthly TRIDENT system metrics detailing technical mission metrics directed by the COR or ACOR. Metrics reporting includes users, organizations, and tool usage breakdown by network, user organization, or user group, or other metrics as directed by COR or ACOR when supportable by automation or other statistical collection methods.

The contractor shall deliver a MSR that includes, at a minimum, the following:

· Overview depicting trends for performance, financial, schedule, staffing, and risks.

· Performance

· Executive-level summary of work accomplished by task area during reporting period.

· Program and project issues, risks, mitigations and any actions required by the government.

· A personnel roster in organizational chart format of individuals assigned to the contract and whether each is a Full-Time Equivalent (FTE) or a fraction of an FTE. Identify FTE count by task area and provide a combined total for the contract.

· TRIDENT system metrics, identifying trends over previous periods.

· Scorecard depicting monthly performance against AQLs for each task area.

· Financial

· Ceiling value, funds obligated, funds expended per CLIN.

· Percentage of obligated funding expended.

· Estimate at Completion (EAC) costs per CLIN

· Projected funding exhaustion date per CLIN.

· Actual travel costs for the month and planned travel costs for the following month.

· Financial overview by CLIN and task area, and by funding source and appropriation type, including actual expenditures, accrued non-invoiced expenditures, and projected expenditures compared to funded and ceiling value.

· Invoice (e.g., invoice number, submittal date, amount, etc.) and payment history.

· Cost, expenditure, and percentage of completion reporting for designated projects, efforts, and initiatives (i.e., tracking of projects designated by DTRA ACOR or COR for separate project-level tracking).

· Labor CLIN(s) EAC that details total estimated labor cost per funding source through the end of current period of performance.

· Account for expenditures of each funding source and each appropriation type to ensure that labor and non-labor expenditures adhere to DoD and DTRA financial management requirements. Each funding source and appropriation type shall be accounted for as a separate line item under appropriate CLIN.

1.2.14 TRIP REPORTS

The contractor shall submit travel reports no later than seven (7) calendar days after contractor travel has been completed. When request for travel (CDRL A008) is submitted, the contractor shall keep a summary of all long-distance travel including, but not limited to, name of employee, location of travel, duration of trip, and point of contact at travel location. Trip reports shall also contain government approval authority, total cost of trip, a detailed description of purpose of trip, and any knowledge gained.

TASK 2: CWMD SUPPORT

2.1.0 OBJECTIVE

The contractor shall provide specialized advisory support to the warfighter by assisting in the planning, coordination, and integration of CWMD related operations to support DTRA’s CWMD mission. This includes sensitive activity planning that could encompass the following:

· Providing subject matter expertise on Irregular Warfare (IW), Military Deception (MILDEC), and Information Operations (IO) to enhance CWMD mission planning.

· Offering advisory support for the development of non-attributable activities to deter adversary WMD proliferation.

· Assisting in the development and refinement of sensitive operational concepts for combatant commands (CCMDs), interagency partners, and SOF components.

· Preventing WMD acquisition, containing and reducing WMD threats, and executing crisis response to international and domestic WMD incidents.

· Partnering with SOCOM tactical units to develop, maintain, and implement reliable, resilient CWMD operational and technical capabilities across the spectrum of conflict.

· Extending DTRA’s technical reach with CWMD operational expertise, reach-back capability, capability development, and exercise support.

· Advocating for DTRA equities with SOCOM partners to enhance operational effectiveness in CWMD efforts.

2.2.0 SUBTASKS

2.2.1 SENSITIVE ACTIVITY OPERATIONS PLANNING

· Provide analytical and technical support to identify and assess irregular warfare environments that affect adversary WMD proliferation networks.

· Assist in the development of operational approaches for non-attributable activities, including:

· Influence operations affecting WMD supply chains.

· Adversary deception methodologies related to WMD pathways.

· Counter-proliferation deterrence efforts in denied environments.

· Support CCMDs, TSOCs, and interagency partners by providing subject matter expertise to refine classified plans and options for sensitive CWMD operations.

· Assist in all aspects of operational planning, including:

· Development and refinement of Course of Action (CoA) plans for IW scenarios.

· Generation of Fragmentary Orders (FRAGOs) to adjust mission execution parameters.

· Application of the Decide, Detect, Deliver, Assess (D3A) methodology for targeting

· Assist in conducting operational risk assessments for discreet CWMD options.

· Provide analytical input to DTRA’s participation in partner-driven initiatives related to CWMD.

· Develop rapid-response operational concepts (CONOPs) for emerging WMD proliferation threats in denied or contested environments, ensuring that sensitive activity planning remains adaptive to real-world threat changes.

2.2.2 MILITARY DECEPTION (MILDEC) & INFORMATION OPERATIONS (IO) SUPPORT

· Support the development and refinement of MILDEC concepts for CWMD-related campaigns.

· Provide advisory expertise on adversary influence strategies, counterpropaganda, and cognitive domain shaping related to WMD narratives.

· Assist in identifying IO and strategic messaging approaches that could contribute to deterring adversary WMD programs.

· Support CCMD and interagency planning efforts by providing technical recommendations on deception methodologies.

2.2.3 SENSITIVE OPERATIONAL PLANNING & INTERAGENCY COORDINATION

· Provide expertise in the integration of special access capabilities into CWMD mission planning.

· Assist in the development of Sensitive Activities CONOPs and Mission Concepts (MICONs), ensuring alignment with SOF, CCMD J3/J5 elements, and interagency partners.

· Offer planning expertise for low-visibility and compartmentalized counterproliferation operations in denied or contested environments.

· Provide recommendations to integrate CWMD-related irregular warfare capabilities into interagency frameworks (e.g., DoS, CIA, FBI, SOCOM).

· Assist CCMDs in refining classified and compartmentalized CWMD campaign options, ensuring compliance with U.S. government policies.

2.2.4 SPECIAL ACCESS PROGRAM (SAP) & COMPARTMENTED PLANNING SUPPORT

· Provide technical expertise to support CWMD-related Special Access Programs (SAPs), Special Technical Operations (STO), and Alternative Compensatory Control Measures (ACCM) planning efforts.

· Assist in developing and refining compartmented planning methodologies to ensure the secure execution of SAP/STO/ACCM-protected capabilities within CWMD-sensitive activities.

· Support the development of SAP/ACCM-approved CONOPs and MICONs, ensuring proper classification handling and integration of highly sensitive capabilities into operational plans.

· Assist in the management and deconfliction of interagency SAP/STO initiatives, ensuring alignment with DoD policy and CWMD objectives.

· Develop risk mitigation strategies for the employment of compartmented capabilities in denied environments, ensuring compliance with operational security (OPSEC) and legal frameworks.

· Provide recommendations on the operational feasibility of emerging SAP-protected capabilities in CWMD-sensitive activities.

· Coordinate with DTRA’s interagency partners to deconflict and enhance STO/ACCM-enabled CWMD operational efforts.

2.2.5 CWMD OPERATIONAL PLANNING & TECHNICAL EXPERTISe

· The contractor shall provide technical expertise, operational planning, and advisory support to ensure the successful execution of CWMD mission sets in collaboration with DTRA and SOCOM tactical units.

· Provide technical planning support to support DTRA’s CWMD objectives in collaboration with partnered SOCOM tactical units.

· Develop integration plans for DTRA R&D resources to address identified technical capability gaps.

· Produce capability gap solution reports that document mission requirements, preliminary validation criteria, preliminary Measures of Effectiveness (MOE), and traceability to operational requirements.

· Provide operational planning support for Deeply Buried and Hardened Targets (DD/HDBT), ensuring specialized expertise in WMD target vulnerabilities.

· Provide analytical support to identify technical and operational capability gaps that impact mission execution.

2.2.6 GLOBAL COMPETITION & MULTI-DOMAIN PLANNING

· The contractor shall support multi-domain planning efforts to counter adversarial WMD capabilities, activities, facilities, networks, and pathways.

· Provide operational planning expertise to support DTRA objectives, collaborating with SOCOM tactical units.

· Conduct multi-domain operational planning against adversarial WMD networks, integrating intelligence, cyber, special operations, and conventional force considerations.

· Support partnered planning activities using advanced planning tools to enhance mission effectiveness.

· Produce graphical and narrative Mission Concepts (MICONs), Concepts of Operations (CONOPs), and other planning artifacts to document collaborative planning outputs.

· Provide sensitive technical operational and Special Access Program (SAP) integration planning support to ensure compartmented capabilities are appropriately leveraged.

· Identify and assess technical and operational capability gaps, ensuring traceability to CWMD operational needs.

· Develop capability gap reports documenting mission requirements, validation criteria, MOEs, and operational feasibility.

Task 3: Global Engagements (GE) Department Support

3.1 Objective

The contractor shall provide administrative, analytical, and coordination support to the Global Engagement Department (GE) to enhance DTRA’s ability to facilitate collaboration with external partners, enable unified action against WMD and emerging threats, and support operational integration with Combatant Commands (CCMDs), interagency partners, and foreign stakeholders.

The contractor shall provide support to the following GE Divisions:

· Global Engagements Functional- FVEY (GEF-F): Supports engagement and collaboration with FVEY, interagency, and foreign partners to identify and enable collective solutions.

· Global Engagements Regional (GER): Integrates agency-wide capabilities in support of CCMD operations to enable CWMD unity of effort.

· Support shall be provided at CONUS and OCONUS forward-deployed locations, including the National Capital Region (NCR), as required by the Government.

3.2 Subtasks

3.2.1 Coordination and Engagement Support

The contractor shall:

· Facilitate scheduling, logistics, and administrative support for GE engagements with CCMDs, interagency, and foreign partners.

· Develop and maintain databases and tracking systems to monitor partner engagements, agreements, and strategic initiatives.

· Assist in the preparation of reports, briefing materials, and correspondence for senior leadership engagement.

· Support the planning and execution of GE-hosted events, working groups, and information-sharing initiatives.

3.2.2 Operational Support

The contractor shall:

· Provide document management support, including drafting, editing, and maintaining records related to GE operations.

· Assist in the development, refinement, and maintenance of GE plans, regional strategies, and operational frameworks.

· Support the generation, staffing, and tracking of policy documents, reports, and operational planning materials.

· Maintain and update internal knowledge management repositories to ensure continuity of operations and historical reference.

3.2.3 Strategic Analysis and Reporting

The contractor shall:

· Conduct structured data collection and analysis to assess the effectiveness of GE’s operational engagements and support initiatives.

· Support after-action reviews (AARs), lessons learned integration, and process improvement efforts.

· Provide analytical input and structured recommendations to enhance GE’s coordination and integration with CCMDs and interagency partners.

3.2.4 Forward-Deployed and Reach-Back Support

The contractor shall:

· Provide operational support at forward-deployed locations, as required.

· Assist in tracking and reporting mission activities, engagement efforts, and operational coordination at forward-deployed sites.

· Ensure consistency in reporting and alignment with GE’s mission objectives across all CONUS and OCONUS locations.

Task 4 – Contingency Operations (CO) Department Support

4.1 Objective

The contractor shall provide comprehensive support to the Contingency Operations Department (CZ-CO) by managing facilities, delivering operational and policy assistance, and developing and evaluating training programs. This support also includes communications, logistics, and property accountability. Furthermore, the contractor is responsible for the operation, maintenance, and training of uncrewed systems for both testing and operational missions.

4.2 Subtasks

4.2.1 Facility Management Support

The contractor shall:

· Conduct routine (daily, weekly, monthly) assessments of facility components and equipment to identify maintenance needs. Perform corrective actions and immediately address any Life/Health/Safety issues. Maintain detailed records of all maintenance activities.

· Develop Statements of Work (SOWs) and associated cost estimates for corrective actions. Prepare and submit draft DA Form 4283 for approval and forwarding to the DTRA Engineering and Logistics Department (AL-EL).

· Support CZ-CO leadership in identifying the relative priority of projects. Assist in developing justifications for project rankings to be used in defending projects before the Agency’s Facilities Utilization Board.

· Act as the technical Point of Contact (POC) for submitted projects. Upon project award, provide oversight support, including personnel escort and management of repairs. Maintain all contractual documentation, financial records, specifications, cost estimates, and inspection records.

· Maintain proper inventory levels of routine maintenance items. Support improvements to the facility, equipment, and government vehicle fleet.

· Manage CZ-CO vehicles in accordance with DTRA guidance, including daily use and monthly reporting. Maintain current certifications in Forklift, ATV, and Snow Plow operations.

4.2.2 Operational and Policy Support

The contractor shall:

· Provide operational and policy support for all CZ-CO activities, including weapons range management, OI mission support, and the joint management of high-sensitivity operational missions alongside senior government personnel.

· Assist in the preparation and coordination of joint operational teams (military, civilian, contractor) for exercises and real-world missions. Develop, implement, and maintain procedures to track and ensure the operational readiness of all personnel for both peacetime and contingency deployments.

· Strategic Planning & Forecasting: Assist in the preparation of detailed operational plans that align with and support the execution of established policies and strategies. This includes supporting planning for evolving capabilities and forecasting future operational needs.

· Inter-Agency Liaison: Interface with OSD, the Joint Staff, GCCs, other DoD components, and federal/civilian crisis management agencies to support strategic planning, joint doctrine, and policy development.

· Requirements & Doctrinal Analysis: Assist in identifying and validating DoD requirement shortfalls and provide support to leadership in advocating for necessary changes across doctrine, organization, training, material, leadership, education, personnel, and facilities.

· Task Management: Lead the management and response to all organizational taskings using the DTRA Enterprise Task Management Software Solution (ETMS2).

4.2.3 Training Support

The contractor shall:

· Support the development of plans for program planning and resource utilization to meet training and readiness requirements.

· Assist in establishing criteria to measure the attainment of department goals and assess the effectiveness of personnel training.

4.2.4 Deployment and Coordination Support

The contractor shall:

· Prepare and process all required documentation for personnel and equipment deployment. This includes preparing HAZMAT reports, aircraft load plans, Aircraft and Personnel Automated Clearance System (APACS) requests, and assisting with the coordination of passports, visas, and Letters of Authorization (LOAs).

· Prepare, coordinate, and synchronize operation orders (OPORDs) and fragmentary orders (FRAGOs) for the CZ-CO staff. Support the planning and publication of deployment training programs and assist in the integration of all battlefield operating systems (BOS) into tactical plans.

· Assist CZ-CO leadership with operations, organization, and training related to deployments and weapons qualifications. Produce and monitor all deployment reports, assist in managing Department training meetings, and prepare Significant Activities Reports (SIGACTS) and DRRS reports for leadership.

· Maintain exercise and deployment situational awareness to ensure CZ-CO assets are provided when and where required and to anticipate developing situations. Coordinate closely with AL-EL and IT-SA to ensure all operational plans are logistically supportable.

4.2.5 Logistics Support

The contractor shall:

· Provide comprehensive logistics support, including the management and accountability for department property using the Defense Property Accountability System (DPAS). The contractor shall track and record equipment, including communications gear, Chemical/Biological equipment, and Personal Protective Equipment (PPE), while also managing unassigned equipment and maintaining on-hand spares. This includes establishing and maintaining all associated equipment records, such as annual inventories and preventative maintenance schedules.

· Manage the equipment and vehicle fleet by executing the vehicle maintenance program, overseeing fuel cards and licensing, and coordinating maintenance for vehicles, weapons, and night vision equipment. Perform regular operations checks to ensure equipment readiness and advise leadership on logistics best practices.

· Provide shipping and mail coordination, with responsibilities including material acquisition and control, customs paperwork, and serving as an Alternate HAZMAT shipper.

4.2.6 Uncrewed Systems Support

The contractor shall:

· Operate uncrewed systems for test, evaluation, and in operational environments, both CONUS and OCONUS.

· Troubleshoot, maintain, and fine-tune uncrewed systems in the field, including the research and integration of new components and training to fielded team operators.

· Plan and analyze test results, create and maintain uncrewed system architecture, and train personnel on the use of these systems.

· Perform administrative duties such as standardization and training, logs and records, and the preparation of periodic reports.

4.2.7 Communications Support

The contractor shall:

· Provide for Senior Level Communications Engineer and Communications Technician support. This support includes, but is not limited to, communication system evaluation, testing, setup, research, maintenance, and ability to act as COMSEC support custodian for NSA-provided authorized COMSEC account.

· Provide support to DTRA and/or COCOM CBRN WMD search training, exercises, and operations in all operational and physical environments (air, land, and sea).

· Support requirements in planning, development, and assessment of equipment as required, meeting mission requirements in support of NIMBLE ELDER Modernization efforts in the area of WMD search.

· Perform duties related to the application, integration, design, development, modification, and installation and maintenance of Technical Support Group deployable communications systems.

· Troubleshoot repairs, modify, test circuits, replace defective parts and/or components, certify, and maintain the communications systems. Provide comprehensive advice to the Department and Technical Support Group Chiefs on the adequacy of available services to support the mission. Identify inoperative equipment modules, determine applicable substitution, and coordinate integration of new or additional items into existing data transmission components taking into consideration site location, availability and compatibility of protocols generated based upon requirements and objectives to be accomplished.

· Instruct members of the Department and supported forces how to use fielded communications systems to accomplish tactical missions. Perform duties as COMSEC user responsible for the receipt, utilization, loading, maintenance, and destruction of COMSEC keys and the maintenance of associated COMSEC paperwork.

Task 5 – Systems Engineering and Operational Planning Support

5.1 Objective

The Contractor shall provide support services to enable DTRA and select partnered unit missions. Required support includes operational planning support embedded with partner unit planning teams and systems engineering support. Engineering support includes monitoring current commercial-of-the-shelf / government-off-the-shelf state-of-the-art and niche technologies, developing prototype key performance parameters decomposed from mission planning, and technology / capability validation event planning support.

The scope of Task 5 is to obtain systems engineering and integration (SE&I) activities necessary to support DTRA CZ and select partner units. This includes scientific and technical analysis and evaluation of vulnerabilities. Developed technical solutions shall address capability gaps identified by planners during concept development.

image1.png