Performance_Work_Statement_(PWS)_-_MARFORRES_FDET_Engineer_Support_Services_Oct2026.docx

PERFORMANCE WORK STATEMENT (PWS)

MARINE FORCES RESERVE

FORWARD DEPLOYED ENGINEER & TRAINER (FDET) SUPPORT SERVICES

1.0 PURPOSE

The purpose of this Performance Work Statement (PWS) is to obtain contractor support for a cleared Forward Deployed Engineer & Trainer (FDET) to provide specialized information technology systems architecture, data engineering, artificial intelligence (AI) enablement, and operational application delivery services in support of the Marine Forces Reserve (MARFORRES) mission. This includes, but is not limited to, Maven Smart System (MSS) and War Data Platform build and sustainment, governed ontology engineering, Databricks-native pipeline development, AIP Logic and agentic workflow integration, rapid operational prototyping, and organic workforce training for reserve Marines and civilian personnel.

2.0 BACKGROUND

The Marine Forces Reserve is a three-star General level command responsible for training and equipping approximately 158 geographically dispersed Marine Reserve units across the United States to augment and reinforce active Marine forces in time of war, national emergency, or contingency operations, provide personnel and operational tempo relief for the active forces in peacetime, and provide service to the community.

The geographical disbursement of Marine Forces Reserve units requires significant investment in Command-and-Control (C2) IT solutions. The IT and data services identified in this PWS are critical to maintaining, sustaining, and evolving the Command-and-Control platforms for the Commander, Marine Forces Reserve.

To accelerate operational decision-making, bridge data silos, and field modern data/AI capabilities across the Total Force, MARFORRES requires one cleared forward-deployed engineer embedded directly with MARFORRES staff. This individual represents the advanced engineering equivalent of a Palantir Maven Field Service Representative (FSR), possessing the technical depth not only to operate and support fielded software platforms, but to actively build, integrate, and deploy data pipelines, ontologies, and operational applications on live operational networks.

3.0 SCOPE AND OBJECTIVES

The scope of this contract is to provide the necessary level of professional and technical engineering support to facilitate the shared objectives of the MARFORRES Command Team, Principal Staff Directorates (e.g., G-1, G-2, G-3, G-4, G-6, G-9), Major Subordinate Commands (MSCs), and external stakeholders to meet the Command-and-Control mission of the force.

Marine Corps Technical Publication (MCTP 3-30B) defines Information Management (IM) as "all activities involved in the identification, collection, filtering, fusing, processing, focusing, dissemination, and usage of information. IM is an essential process by which information is obtained, manipulated, directed, and controlled. It facilitates information availability to relevant users to promote understanding of the battlespace." Fleet Marine Force Reference Publication (FMFRP 6-01.1) defines Knowledge Management (KM) as "the art of creating, organizing, applying, and transferring knowledge to facilitate situational understanding and decision making."

The embedded FDET Engineer works within the framework of MARFORRES IM/KM lines of effort:

Data & Information: Identifying, extracting, and synthesizing authoritative sources of data to deliver timely, actionable readiness information to commanders.

Process Improvement & Automation: Streamlining transactional workflows and replacing manual data stitching with automated, repeatable pipelines.

Knowledge Management & Force Enablement: Reducing the "time to competency" for staff and drilling Marines through live training, runbooks, and cohort instruction.

Artificial Intelligence Enablement: Applying responsible, human-in-the-loop AI agents, agentic workflows, and predictive models to accelerate C2 and decision velocity.

The FDET requirement centers on three integrated core pillars:

01 · Engineer (Build & Sustain on MSS): Workshop apps, AIP Logic agents, governed ontology, and resilient data pipelines built upon live MARFORRES data.

02 · Train (Grow Organic Talent): Cultivate MSS tradecraft, Foundry / AIP fluency, and administrative capability across permanent civilian/military staff and drilling Reserve Marines.

03 · Rapid Solutioning (Whiteboard to App in Days): Execute joint sprints directly alongside MARFORRES operators to scope, prototype, and field operational tools on real data with writeback capability to source systems.

4.0 GENERAL REQUIREMENTS

4.1 Applicable Directives

The Contractor shall comply with all applicable Department of Defense (DoD), Department of the Navy (DON), United States Marine Corps (USMC), and MARFORRES policies, directives, instructions, manuals, and standards, including but not limited to the following:

Marine Forces Reserve Knowledge Management Strategy Marine Forces Reserve SharePoint Governance Marine Forces Reserve Cybersecurity Directive (current version) MARFORRES Force Order 2000-1.4 FORO 3440.1H Continuity of Operations (COOP) Program Management FORO P5510.1B Standard Operating Procedures for the Information and Personnel Security Program Marine Forces Reserve Standard Operating Procedures (SOP) United States Marine Corps Artificial Intelligence Strategy Guide MCO 5231.4 Marine Corps Data and Artificial Intelligence (AI) MCO 5239.2B Marine Corps Cybersecurity MCO 3305.2E Marine Corps Antiterrorism Program MCO 3501.36A Marine Corps Critical Infrastructure Program MCO 3504.2 Marine Corps Lessons Learned Program and The Marine Corps Center for Lessons Learned MCO P5530.14A Marine Corps Physical Security Program MCO 3440.8 Installation Chemical, Biological, Radiological, Nuclear and High-Yield Explosive (CBRNE) Protection Program MCO 3440.9 Installation Emergency Management MCO 5000 Series (Policy Guidance for Marine Corps Organization and Administration) MCO P5090.2A Environmental Protection and Compliance Program Marine Corps Order P7300.21B Marine Corps Financial Management Standard Operating Procedures Manual Current Marine Corps Enterprise Cyber Security Directives (ECSD) for Information Assurance Vulnerability Management (IAVM) Current Marine Corps Enterprise Cyber Security Directives (ECSD) for Ports, Protocols, and Services Management Current Marine Corps Enterprise Cyber Security Manual (ECSM) for Assessment and Authorization Process MCIP 3-40.02 Marine Corps Cyberspace Operations MCWP 3-40.4 MAGTF Information Operations NAVMC 3500.103 Marine Corps Antiterrorism Manual SECNAVINST 5000.2 (series) Implementation and Operation of the Defense Acquisition System (current version) SECNAVINST 5230.15 Information Management IT Policy for Fielding of COTS Software SECNAVINST 5239.20 DON Cybersecurity and IA Workforce Management SECNAV M-5239.2 Cyberspace Info Tech and Cybersecurity Workforce Management and Qualification DoD Financial Management Regulations 7000.14-R DoD 5400.11 Department of Defense Privacy Program DoDM 8140.03 Cyberspace Workforce Qualification and Management Program DoDD 2000.12 DoD Antiterrorism Program DoDI 2000.16 DoD Antiterrorism Standards DoD 2000.12-H DoD Antiterrorism Handbook DoDI 3001.02 Personnel Accountability in Conjunction with Natural or Manmade Disasters DoD 3020.45-M, Volume 3, Defense Critical Infrastructure Program (DCIP) Security Classification Manual (SCM) DoDI 3020.52 DoD Installation CBRNE Preparedness Standards DoDD 4500.54-G DoD Foreign Clearance Guide DoDD 6490.2 Joint Medical Surveillance DoDI 6055.17 Installation Emergency Management (IEM) Program DoDI 6500.17 DoD Installation Emergency Management Program DoDD 3020.26 Department of Defense Continuity Programs DoDI 8100.4 DoD Unified Capabilities DoDI 8500.01 Cybersecurity DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology (IT) DoDI 8550.01 DoD Internet Services and Internet-Based Capabilities DoDI 8551.01 Ports, Protocols, and Services Management (PPSM) DoDI 8560.01 Communication Security (COMSEC) Monitoring and Information Assurance (IA) Readiness Testing 32 CFR Part 117 National Industrial Security Program Operating Manual (NISPOM) DOD CIO Memorandum - Guidance for Cybersecurity Workforce Certification Compliance Process Committee on National Security Systems Instruction (CNSSI) No. 4009 National Information Assurance (IA) Glossary CJCSI 6215.01C Policy for Department of Defense (DOD) Voice Networks with Real Time Services (RTS) CJCSI 6211.02C Defense Information System Network (DISN): Policy and Responsibilities NIST Special Publication 800-18 Guide for Developing Security Plans for Federal Information Systems DISA Field Security Operations (FSO) Security Technical Implementation Guides (STIGs) and Checklists DISA PPSM Security Classification Guide and PPSM User Guide National Information Assurance Partnership (NIAP) Standards Unified Capabilities Certification Office (UCCO) Approved Products List (APL) DISA Joint Interoperability Test Command (JITC) Unified Capabilities Requirements UFC 4-010-01 DoD Minimum Antiterrorism Standards for Buildings UFC 4-010-02 DoD Minimum Antiterrorism Standoff Distances for Buildings UFC 4-021-01 Design and O&M: Mass Notification Facilities UFC 4-030-01 Sustainable Development Energy Independence and Security Act of 2007 (EISA) DHS National Response Framework (NRF) DTRA Security Classification Guide USPACOM Instruction 0614.1 Theater Travel Requirements in U.S. Pacific Command MCCRAM 1009.1K Foreign Travel Policy Standing ALNAVs, NAVADMINs, ALMARs, and MARADMINs

4.2 Working on a Government Installation

4.2.1 Identification: Contractor employees must be clearly identifiable while on Government property by wearing a Government-issued badge at all times. Badges shall be visibly displayed and presented for examination upon request from the Contracting Officer, Contracting Officer’s Representative (COR), Quality Assurance Personnel, Military Police, or other authorized Government officials.

4.2.2 Regulations: The Contractor and contractor employees shall comply with all traffic, security, environmental, safety, and registration regulations for personnel and vehicles on Government installations.

4.2.3 Representation & Disclosures: All Contractor personnel attending meetings, answering Government telephones, sending electronic correspondence, or interacting in environments where their status is not obvious to third parties must clearly identify themselves as Contractor personnel. Contractor computer profiles, signatures, and directory entries shall clearly state their contractor affiliation. All documents, code repositories, runbooks, and briefs generated by the Contractor must be clearly marked as “Contractor Generated Documents.”

4.2.4 Facility Identification: Contractor-occupied facilities (offices, workstations, cubicles) on Government installations must be clearly labeled with signage identifying them as Contractor work areas.

4.3 Security Requirements

4.3.1 Security Clearance: The Contractor personnel assigned to this effort must possess an active DoD Secret security clearance at the start of contract performance. Interim Secret clearances are acceptable provided they are maintained continuously until final adjudication is granted. The contractor facility must maintain an active DoD Secret facility clearance.

4.3.2 Common Access Card (CAC): The personnel performing tasks under this contract must be eligible for, obtain, and maintain a DoD Common Access Card (CAC) and associated DoD Public Key Infrastructure (PKI) certificates for identity verification, physical and logical network access, and email encryption.

4.3.3 Position Designation: The FDET Engineer billet is designated as an Information Technology Level II (IT-II) position requiring a favorably adjudicated Secret clearance based on a National Agency Check with Local Agency and Credit Checks (NACLC) or equivalent investigation, updated every 10 years.

4.3.4 Physical Facility Security: When working after hours or outside standard duty windows, the Contractor personnel shall follow all local physical and facility security procedures, ensuring perimeter doors remain locked and classified/controlled spaces are properly secured.

4.3.5 Remote Work: Remote work is authorized when coordinated with and formally approved by the Government Lead/COR. When operating remotely, the Contractor must maintain secure, reliable connectivity conforming to DoD cybersecurity policies, remain fully accessible and responsive to MARFORRES leadership during normal operational duty hours, and possess the ability to travel on-site when mission requirements dictate.

4.4 Staffing and Key Personnel

The Government requirement is based on one (1) dedicated, embedded Full-Time Equivalent (FTE) Forward Deployed Engineer & Trainer (FDET).

4.4.1 Key Personnel Designation: The FDET Engineer is designated as "Key Personnel." Key personnel are considered uniquely essential to the successful accomplishment of the work. Resumes evaluated during the proposal process establish the baseline qualifications.

4.4.2 Key Personnel Substitution:

4.4.2.1 Guidance on Substitutions: During the first ninety (90) calendar days of performance, no substitution of Key Personnel shall be permitted unless necessitated by sudden illness, death, or immediate termination of employment. Following the initial 90-day period, proposed substitutions must be submitted in writing to the Contracting Officer at least ten (10) business days prior to the proposed replacement. If Key Personnel become unavailable for more than thirty (30) consecutive work days, the Contractor shall immediately notify the Contracting Officer and provide an equally or better-qualified candidate.

4.4.2.2 Substitution Approval & Qualifications: All substitution requests must detail the reason for departure, include a comprehensive resume demonstrating qualifications equal to or exceeding those established herein, and receive written concurrence from the Contracting Officer prior to placement. If timely or suitable replacement is not achieved, the Government may equitably adjust contract funding downward or terminate for default/convenience.

4.5 Quality Assurance Surveillance Plan (QASP)

The Contractor shall perform work in accordance with the Quality Assurance Surveillance Plan (QASP). The Government will monitor performance using surveillance methods including random sampling, COR reviews, customer feedback, and delivery milestone tracking against the Performance Requirements Summary (PRS).

5.0 PERFORMANCE TASKS

The Contractor shall participate in a Post-Award Kick-off Meeting within ten (10) business days of contract award, held at the Marine Forces Reserve Regional Contracting Office (MFR-RCO) or virtually as designated by the COR.

5.1 Billet Title: Forward Deployed Engineer & Trainer (FDET) Engineer Quantity: One (1) Full-Time Equivalent (FTE) Organizational Alignment: Embedded with MARFORRES Headquarters (IM/KM & Principal Staff Sections), Marine Corps Support Facility, New Orleans, LA.

5.1.1 General Overview

The FDE&T Engineer is a cleared, Palantir-fluent forward-deployed engineer who delivers the operational integration of a Maven Field Service Representative combined with high-level software and data engineering depth. Embedded directly alongside MARFORRES operational staff, the engineer designs, deploys, and maintains live data pipelines across unclassified and classified enclaves; models complex reserve readiness data into an enterprise-governed ontology; builds AI agents and agentic workflows that operate with a human in the loop; and develops responsive operational applications and dashboards that reflect live reserve force posture with direct writeback into authoritative source records. Recognizing the natural rotation of reserve military personnel through drill cycles, activations, and permanent changes of station (PCS), the engineer delivers robust technical documentation, runbooks, and hands-on training to ensure organic Marines independently operate and sustain all fielded capabilities.

5.1.2 Minimum Qualifications and Certifications

Active DoD Secret Security Clearance.

CompTIA Security+ (IAT Level II baseline certification) or higher.

Demonstrated fluency in Palantir platforms (Palantir Foundry, Maven Smart System / MSS, AIP).

Advanced software engineering proficiency in TypeScript and Python within Palantir Code Workspaces and Code Repositories.

Proven experience architecting and managing data pipelines utilizing Databricks and Apache Spark.

Demonstrated expertise in building, optimizing, and governing enterprise data ontologies (object types, relations, and action types).

Direct experience developing artificial intelligence workflows, Large Language Model (LLM) prompts, and AIP Logic agents with human-in-the-loop controls.

Experience integrating data pipelines across hybrid environments, including Microsoft Azure Government, relational databases (SQL Server), and enterprise cloud endpoints.

5.1.3 Performance Tasks

The Contractor shall execute the following performance tasks:

Pillar 1: Data Pipeline & Ingestion Engineering Design, construct, monitor, and sustain automated data pipelines ingesting, cleansing, validating, and transforming complex datasets across unclassified (MCEN-N) and classified (MCEN-S / SIPR / JWICS as authorized) environments.

Build Databricks-native pipelines and data transformations using Python and PySpark to process massive operational datasets into clean, structured tables.

Automate scheduling, health checks, dependency checks, and error handling for all pipeline data flows connecting to DoD/DON/USMC authoritative systems of record (e.g., MCTFS, MDATT, MarineLink, C2PC).

Coordinate with enterprise data administrators, Mission Owner Landing Zone (MOLZ) engineers, and cloud database administrators to ensure data feeds adhere to enterprise governance, ports/protocols, and security directives.

Pillar 2: Governed Ontology Modeling & Architecture Architect, deploy, and curate an enterprise-governed data ontology capturing the foundational objects, relationships, and executable actions defining MARFORRES readiness.

Define ontology objects representing Marines, billet structures, Major Subordinate Commands, subordinate units, ground and aviation equipment, supply classes, training events, annual training (AT) / drill execution, and contingency mission taskings.

Engineer multi-object relationships and link types that establish end-to-end data lineage from individual tactical readiness to high-level C2 decision matrices.

Configure secure, governed Action Types within the ontology that enable authorized operators to execute real-time modifications, approvals, and data state changes directly from operational user interfaces.

Pillar 3: AI Agents & Agentic Workflow Development Design, test, and deploy artificial intelligence agents and agentic workflows utilizing Palantir AIP (Artificial Intelligence Platform) Logic and large language model tooling.

Develop autonomous and semi-autonomous AI workflows that ingest operational feeds, triage personnel and logistics gaps, generate predictive readiness courses of action, and suggest optimal resource allocations.

Enforce strict human-in-the-loop (HITL) guardrails, validation boundaries, and audit logging for all AI-assisted recommendations and action triggers.

Align AI agent designs with the USMC Artificial Intelligence Strategy Guide and MCO 5231.4 to ensure ethical, explainable, and secure AI fielding.

Pillar 4: Operational Dashboard & Application Development Develop, configure, and sustain intuitive, interactive operational applications and command dashboards within MSS Workshop and Slate.

Provide General Officers, directorate leads, and commanders with a real-time, fused Common Operating Picture (COP) of personnel, training, and logistics readiness across all 158 geographically dispersed Reserve Training Centers.

Implement two-way writeback capabilities from front-end applications to backend authoritative databases and source platforms, eliminating static report generation and redundant manual record updates.

Write clean, maintainable, modular front-end code using TypeScript and backend code in Python within version-controlled Code Repositories.

Pillar 5: Rapid Sprints & Mission Prototyping Facilitate rapid-turn collaborative sprints directly with MARFORRES action officers, analysts, and branch heads to transition requirements from concept/whiteboard to working production application within days.

Refine user stories, backlog items, and acceptance criteria in alignment with Agile/SCRUM development methodologies and MARFORRES sprint rhythms.

Rapidly adapt fielded applications in response to emergent real-world mobilizations, crisis action planning, defense support of civil authorities (DSCA), or contingency exercise taskings.

Pillar 6: Organic Talent Cultivation, Training & Sustainment Conduct hands-on technical training, workshops, and cohort learning programs for active-duty, civilian, and drilling Reserve Marines in MSS tradecraft, Foundry navigation, AIP Logic, and platform administration.

Author comprehensive, step-by-step standard operating procedures, architectural schematics, user guides, and system runbooks for every fielded application, pipeline, and ontology component.

Establish operational knowledge transfer protocols ensuring total command ownership of all tools and mitigating single-point contractor dependency during military personnel turnover.

5.1.4 Task Area Deliverables

The Contractor shall deliver the following artifacts to the COR and designated MARFORRES Government Lead:

6.0 PERFORMANCE STANDARDS

This is a Performance-Based Service Acquisition in accordance with Federal Acquisition Regulation (FAR) 37.6. The Contractor shall be evaluated against the specific performance measures, standards, acceptable quality levels (AQL), and surveillance methods outlined in the Performance Requirements Summary (PRS) set forth in Attachment 2.

The Government will regularly evaluate the Contractor’s performance through COR inspections, direct review of coded solutions and runbooks, feedback from supported military directorates, and review of deliverable timeliness and technical accuracy.

7.0 PLACE AND PERIOD OF PERFORMANCE

7.1 Place of Performance

Primary performance of work shall be accomplished on-site at Marine Corps Support Facility, 2000 Opelousas Avenue, New Orleans, LA 70114.

The Contractor shall maintain a standard 40-hour work week, Monday through Friday, excluding the eleven (11) recognized U.S. Federal Holidays (New Year’s Day, Martin Luther King Jr. Birthday, Washington’s Birthday, Memorial Day, Juneteenth National Independence Day, Independence Day, Labor Day, Columbus Day, Veterans Day, Thanksgiving Day, Christmas Day). Core operating hours are between 0700 and 1800.

Occasional after-hours or weekend maintenance and exercise support may be required to accommodate operational battle rhythms and Reserve drill weekends, coordinated in advance with the COR.

7.2 Period of Performance

The period of performance consists of a twelve (12) month base period and four (4) one-year optional ordering periods:

8.0 GOVERNMENT FURNISHED EQUIPMENT (GFE) AND INFORMATION (GFI)

The Government will provide the Contractor with necessary workspace, desk facilities, and standard Marine Corps Enterprise Network (MCEN) unclassified and classified workstations/laptops equipped with required software, peripherals, and CAC readers. The Government will grant authorized electronic access to DoD/DON/USMC databases, Maven Smart System / War Data Platform environments, Databricks workspaces, cloud landing zones, and developmental repositories required to execute this PWS.

All GFE remains the property of the U.S. Government and shall be managed, tracked, and returned in accordance with applicable property management regulations.

9.0 TRAVEL

Travel may be required under this contract to support training events, Reserve unit site visits, and operational exercises across Continental United States (CONUS) locations. The local travel area is defined as travel within a 50-mile radius of Marine Corps Support Facility New Orleans, LA. Travel within the local area is non-reimbursable.

10.0 TRAVEL REIMBURSEMENT PROCEDURES

10.1 Contractor Request and Approval of Travel: Any travel outside the local area must be requested in writing and receive formal written pre-approval from the COR at least fourteen (14) business days prior to incurring travel expenses. The written request must contain:

Contract number and task order title.

Inclusive travel dates, itinerary, and destination.

Purpose of travel and operational requirement supported.

Detailed cost estimate breakdown (airfare, lodging, meals and incidentals, rental car/mileage).

Name and security clearance level of traveler.

10.2 Reimbursement Standards: The Contractor shall be reimbursed for reasonable, actual travel costs in strict compliance with the DoD Joint Travel Regulations (JTR) per diem rates. Reimbursable travel expenses exclude handling charges, general and administrative (G&A) expenses, overhead, profit, or fee. Airfare shall not exceed the lowest available coach/economy commercial rate.

10.3 Invoicing & Documentation: The Contractor must submit itemized, original receipts for all lodging, airfare, rental vehicle, and individual expenses exceeding $75.00 with the monthly invoice voucher.

10.4 Travel Funding Limitation: Travel will be funded under a separate Cost-Reimbursable (No Fee) CLIN with an established Not-to-Exceed (NTE) cap. The Contractor shall notify the Contracting Officer and COR when travel expenditures reach 85 percent of the allocated CLIN funding. The Contractor is not authorized to exceed the funded CLIN ceiling without a formal bilateral contract modification.

11.0 CONTRACT DELIVERABLES

All contract deliverables shall be submitted directly to the COR in designated professional formats (MS Word, MS Excel, MS PowerPoint, PDF, or direct code pull requests into approved DoD repositories).

12.0 SERVICE CONTRACT REPORTING (SCR) / SAM.GOV

The Contractor shall report all contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via the System for Award Management (SAM.gov). Reporting inputs shall include all labor hours executed during the period of performance for each Government Fiscal Year (FY), running October 1 through September 30. Inputs may be entered continuously, but all data must be submitted no later than October 31 of each calendar year.

13.0 LIST OF ATTACHMENTS

Attachment 1: Contract Security Classification Specification (DoD Form DD-254) Attachment 2: Performance Requirements Summary (PRS)

ATTACHMENT 1: DD-254 FORM

(Department of Defense Contract Security Classification Specification — attached separately as required by DoD 5220.22-M).

ATTACHMENT 2: PERFORMANCE REQUIREMENTS SUMMARY (PRS)

The Contractor service requirements are summarized into performance objectives that relate directly to mission-critical outcomes.

DISTRIBUTION: DoW COMMUNITY ONLY