Solicitation - N0018926QD216.pdf

WOMEN-OWNED SMALL

BUSINESS (WOSB)

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

1. REQUISITION NUMBER PAGE 1 OF

2. CONTRACT NUMBER 3. AWARD/EFFECTIVE

DATE

4. ORDER NUMBER 5. SOLICITATION NUMBER 6. SOLICITATION ISSUE

DATE

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME b. TELEPHONE NUMBER (No collect calls)

8. OFFER DUE DATE/

LOCAL TIME

9. ISSUED BY

13b. RATING

14. METHOD OF SOLICITATION

CODE

15. DELIVER TO 16. ADMINISTERED BY CODE

18a. PAYMENT WILL BE MADE BY CODE17a. CONTRACTOR/

OFFEROR

CODE

FACILITY

CODE

CODE

TELEPHONE NUMBER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN

OFFER

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK

BELOW IS CHECKED

REQUEST

FOR QUOTE

(RFQ)

INVITATION

FOR BID

(IFB)

REQUEST

FOR

PROPOSAL

(RFP)

SEE ADDENDUM

19.

ITEM NUMBER

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA 26. TOTAL AWARD AMOUNT (For Government Use Only)

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH

AND DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND

ON ANY ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS

SPECIFIED

29. AWARD OF CONTRACT: REFERENCE OFFER

DATED . . YOUR OFFER ON SOLICITATION

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR

30b. NAME AND TITLE OF SIGNER (Type or print) 30c. DATE SIGNED

31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

31b. NAME OF CONTRACTING OFFICER (Type or print) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 11/2021)

Prescribed by GSA - FAR (48 CFR) 53.212

10. THIS ACQUISITION IS UNRESTRICTED OR

NORTH AMERICAN

INDUSTRY CLASSIFICATION

STANDARD (NAICS):

SIZE STANDARD:

13a. THIS CONTRACT IS A

RATED ORDER UNDER

THE DEFENSE PRIORITIES

AND ALLOCATIONS

SYSTEM - DPAS (15 CFR 700)

SET ASIDE: % FOR:

11. DELIVERY FOR FREE ON

BOARD (FOB) DESTINATION

UNLESS BLOCK IS MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

ARE ARE NOT ATTACHED

ARE ARE NOT ATTACHED

27a. SOLICITATION INCORPORATES BY REFERENCE (FEDERAL ACQUISITION REGULATION) FAR 52.212-1, 52.212-4. FAR 52.212-3

AND 52.212-5 ARE ATTACHED. ADDENDA

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA

8(A)

ECONOMICALLY

DISADVANTAGED

WOMEN-OWNED SMALL

BUSINESS (EDWOSB)

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

(SDVOSB)

HUBZONE SMALL

BUSINESS

SMALL BUSINESS

NOTE: OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30.

Solicitation/Contract Form Continuation

N0018926QD216

Product Service Code: DA10

Option Line Item

Product Service Code: DA10

Continuation of Supplies or Services and Prices/Costs

Additional Information/Notes

Item Supplies/Service Quantity Unit Unit Price Amount

Pytho Artificial Intelligence (AI) platform services tailored for wargaming operations in accordance with the Performance Work Statement.

Pricing Arrangement: Firm Fixed Price

12 Months

Option Line Item

OPTION - Pytho AI engineering and integration services tailored for wargaming operations in accordance with the PWS. This is an Option CLIN subject to clause FAR 52.217-9. The contractor shall bill for this CLIN only after the completion of services at the end of the period of performance. The Government may exercise this CLIN at any time during the period of performance for up to 12 months, with services to conclude on 29 Sep 2027.

Pricing Arrangement: Firm Fixed Price

12 Months

Continuation of Description

PERFORMANCE WORK STATEMENT

AI-Enabled Wargaming Platform and Mission AI Engineering, Integration, and Application Development Services

1.0 INTRODUCTION

The National Defense Wargaming Center (NDWC) is the National Defense University's (NDU) center for educational wargaming and experiential learning. NDWC develops challenging and complex wargames and exercises designed to support the Officer Professional Military Education Policy (OPMEP), Outcomes-Based Military Education (OBME), NDU and college learning outcomes, and other applicable strategic and educational guidance. These activities allow students, faculty, and national security practitioners to apply concepts, test assumptions, and examine complex strategic and operational problems in realistic, low-risk environments.

NDWC supports NDU's six component colleges, including the National War College, Joint Forces Staff College, College of International Security Affairs, Dwight D. Eisenhower School for National Security and Resource Strategy, College of Information and Cyberspace, and National Intelligence College. NDWC also collaborates with other Department organizations, interagency partners, allies, academic institutions, and national security stakeholders. Through this work, NDWC enables authentic assessment, professional judgment, critical thinking, and the creative application of military power across competition, crisis, and conflict.

2.0 BACKGROUND

NDU is an institution of higher education chartered to deliver Joint Professional Military Education. NDU educates joint warfighters and other national security leaders to apply critical thinking and military power in support of national strategy and globally integrated operations.

Artificial intelligence and machine learning are rapidly transforming military planning, operational analysis, decision support, and force development.

Department-level guidance emphasizes expanded adoption of AI as an enabler for accelerating decision-making, improving operational effectiveness, and maintaining decision advantage. As a principal institution for Joint Professional Military Education, NDU must prepare future leaders to understand, employ, and critically evaluate these technologies before encountering them in operational assignments.

During the preceding two years, NDWC used commercial AI applications and contractor-supported development services to support educational wargaming, campaign planning, exercise design, faculty development, and AI experimentation. This operational experience demonstrated that an AI-enabled platform can improve the speed, consistency, analytical rigor, and educational value of wargame development and execution.

The experience established an enduring requirement for continued access to a secure commercial AI application. It also established a potential requirement, subject to mission need and availability of funds, for mission AI engineering, integration, and application development services supporting Government-prioritized capabilities.

3.0 SCOPE

The Contractor shall provide non-personal commercial application access and technical services to NDWC under three Contract Line Item Numbers.

The CLIN structure separates recurring access to the Contractor's existing commercial AI application from optional mission AI engineering, integration, and application development services.

The anticipated contract structure is one 5-month period of performance and one 7-month option period.

3.1 CLIN 0001: AI Application Access, Hosting, Maintenance, and Support

The Contractor shall provide authorized NDU users continuous access to the Contractor's commercial AI-enabled application throughout the period of performance. The service shall include secure hosting, user-account administration, routine maintenance, commercially released updates, corrective maintenance, technical support, and access to generally available application capabilities relevant to educational wargaming and operational planning.

The application shall support the end-to-end wargaming lifecycle, including planning and design, exercise execution, analysis, and assessment.

Access under CLIN 0001 shall not, by itself, require the Contractor to develop Government-unique software features or integrations. Government-unique engineering, development, and integration will be performed only if optional CLIN 0002 is exercised.

3.2 Option CLIN 0002: Mission AI Engineering, Integration, and Application Development Services

Option CLIN 0002 may be exercised based on mission need, availability of funds, and a determination by the Contracting Officer that exercise of the option is in the Government's best interest.

If exercised, the Contractor shall provide mission AI engineering, software development, systems engineering, business analysis, rapid prototyping, systems integration, testing, documentation, and related technical services for Government-prioritized capabilities.

Work may include new features, AI agents, workflows, interfaces, application programming interfaces, plugins, middleware, connectors, data integrations, analytical tools, or enhancements designed to meet specific NDWC wargaming, Joint Professional Military Education, campaign-planning, modeling and simulation, and exercise-support requirements.

Development work shall be managed through Government-approved capability requests, product requirements documents, prioritized backlogs, sprint plans, or comparable written task descriptions that define the intended outcome, acceptance criteria, schedule, and required deliverables.

The Contractor shall not begin work under CLIN 0002 unless the Contracting Officer exercises the option in writing. Inclusion of a capability in a Government backlog, planning document, meeting record, or technical discussion does not authorize performance.

The Contractor shall not begin development that changes contract scope, price, or schedule without written authorization from the Contracting Officer.

4.0 PERFORMANCE REQUIREMENTS AND TASKS

4.1 CLIN 0001: Application Access and Core Services

4.1.1 Application Availability and User Access

The Contractor shall provide secure, browser-accessible application availability to authorized Government users throughout the period of performance, except during scheduled maintenance or events beyond the Contractor's reasonable control. The contractor shall maintain application availability of 99.5% per calendar month, excluding scheduled maintenance approved by the Government

The Contractor shall establish, modify, and deactivate user accounts at the Government's request and shall provide user-access instructions and onboarding materials. The contractor shall create or modify user accounts within 2 business days of receiving a valid Government request.

Scheduled maintenance shall be coordinated with the Government at least five business days in advance unless emergency maintenance is required.

4.1.2 Core AI-Enabled Capabilities

The commercially available application shall provide capabilities that support the full lifecycle of educational wargaming and operational planning.

Capabilities may include, but are not limited to:

Search, retrieval, summarization, and analysis of structured and unstructured information, including doctrine, policy, historical references, orders of battle, and Government-provided source material.

Generation and refinement of scenarios, vignettes, role-player guidance, exercise injects, plans, reports, briefings, and other operational or educational products.

Support to mission analysis, course-of-action development, course-of-action comparison, plan refinement, red teaming, and identification of assumptions and operational risk.

Assistance to facilitators, exercise-control personnel, role players, faculty, students, and analysts during exercise execution.

Synthesis of exercise observations, decisions, participant inputs, trends, lessons learned, after-action reviews, and executive summaries.

Multimodal and multilingual capabilities, when available within the commercial application, to enhance exercise realism and coalition or international engagement.

4.1.3 Hosting, Maintenance, and Commercial Updates

The Contractor shall host and maintain the application in an environment appropriate for handling authorized unclassified Government information and consistent with applicable security requirements.

The Contractor shall perform routine corrective maintenance and provide generally available commercial software updates, model improvements, and feature releases at no additional charge when those updates are included in the commercial subscription.

4.1.4 Technical Support

The Contractor shall provide responsive technical support for account access, application functionality, user issues, and service interruptions.

The Contractor shall acknowledge reported high priority issues within one business day and shall communicate status and planned resolution until the issue is closed. Critical service interruptions shall require a 4-hour response time. Normal service interruptions require a response in 2 business days.

Priority Response

Critical outage 4 hours

High 1 business day

Normal 2 business days

4.1.5 User Enablement

The Contractor shall provide current user guides, quick-reference materials, demonstrations, or orientation sessions sufficient for authorized users to operate the application effectively and understand applicable strengths, limitations, and responsible-use considerations.

4.2 OPTION CLIN 0002: MISSION AI ENGINEERING, INTEGRATION, AND APPLICATION DEVELOPMENT SERVICES

The requirements of this section apply only if CLIN 0002 is exercised in writing by the Contracting Officer.

4.2.1 Requirements Analysis and Product Definition

For each Government-prioritized development effort, the Contractor shall collaborate with NDWC stakeholders to clarify the operational or educational problem, identify users and workflows, define the desired end state, and document functional and nonfunctional requirements.

The resulting product requirements document or equivalent artifact shall include:

Problem statement Proposed capability Inputs and outputs User experience Dependencies Security considerations Testing approach Acceptance criteria Estimated delivery schedule

4.2.2 Iterative Development and Prototyping

The Contractor shall use an iterative development approach that allows the Government to review demonstrations, provide feedback, and refine requirements before final delivery.

Development may include:

Mission-specific AI agents and workflows for wargame design, campaign planning, red teaming, adjudication support, role playing, information-environment simulation, and after-action analysis.

User interfaces, APIs, plugins, middleware, connectors, adapters, backend services, databases, and data-processing pipelines required to support approved capabilities and interoperability.

Integration of Government-authorized data sources, reference materials, modeling and simulation environments, wargaming tools, geospatial systems, and collaboration platforms.

Multimodal capabilities involving text, voice, imagery, video, geospatial information, or synthetic media when specifically authorized.

Dashboards, visualizations, reports, export functions, and analytical tools that support exercise control, assessment, and decision-making.

Enhancements that improve explainability, transparency, traceability, accessibility, usability, and human-machine teaming.

4.2.3 Modeling, Simulation, and Wargaming Integration

When authorized, the Contractor shall design, develop, configure, test, deploy, and maintain interfaces that enable the AI application to exchange information with or provide AI-assisted functions within Government-selected modeling, simulation, wargaming, planning, geospatial, educational, and collaboration systems.

Integration methods may include APIs, plugins, middleware, connectors, adapters, or other approved approaches.

Potential efforts include an AI assistant supporting the OWS/DIGICAT operational wargaming environment, as well as integration with ArcGIS, Microsoft 365, SharePoint, Teams, and future Government-selected systems.

Specific integrations will be defined through approved capability requests and acceptance criteria.

4.2.4 Testing, Demonstration, and Acceptance

The Contractor shall conduct functional testing before presenting a capability for Government acceptance.

The Contractor shall demonstrate completed work to designated Government stakeholders and provide sufficient documentation for the Government to determine whether the capability meets approved acceptance criteria.

Deficiencies identified during acceptance testing shall be corrected within a mutually agreed written schedule.

Government acceptance occurs when:

required functionality is demonstrated;

acceptance criteria are met;

required documentation is delivered;

critical deficiencies are corrected;

the COR or designated acceptance official documents acceptance.

4.2.5 Deployment and Integration

The Contractor shall deploy accepted capabilities into the application environment or another Government-approved environment, as applicable.

The Contractor shall coordinate deployment to minimize disruption to users and shall provide:

Release notes Configuration information Interface or API documentation, when applicable User documentation appropriate to the capability delivered

4.2.6 Development Backlog and Technology Review

The Contractor shall maintain a transparent, prioritized development backlog for authorized work.

The backlog shall identify:

Capability request Government priority Status Dependencies Estimated effort Responsible personnel Target delivery date

The Government will establish priorities based on mission need, available funding, technical feasibility, and exercise schedules.

CLIN 0002 is intended to be priced as a fixed service supporting performance against the Government-prioritized backlog rather than as individually invoiced labor hours or separately priced development tasks.

The backlog is a prioritization and management mechanism. It does not require the Contractor to complete every backlog item during the period of performance. It does not authorize work outside the scope, funding, technical capacity, or period established by the contract.

The backlog does not independently obligate funds or authorize changes to contract scope, price, or schedule.

If CLIN 0002 is exercised, the Contractor shall support a technology review addressing relevant commercial AI developments, integration opportunities, emerging models and tools, cybersecurity considerations, user feedback, and recommended capability priorities.

The technology review is a planning activity and does not independently authorize additional work or obligate funds.

4.2.7 Exercise and Faculty Support

When authorized under CLIN 0002, the Contractor shall provide technical expertise during selected wargames, planning events, demonstrations, faculty-development activities, or experimentation efforts.

Support may include:

Configuration Data preparation Workflow development Troubleshooting Prototype assessment Collection of user feedback for future development

5.0 DATA AND CONTENT CONSIDERATIONS

5.1 Government-Provided Information

The Government may provide unclassified doctrine, publications, scenarios, data, exercise materials, or other information needed to configure or evaluate application capabilities.

The Contractor shall use Government-provided information only for performance of this contract and shall protect it in accordance with applicable markings, handling instructions, and contract requirements.

5.2 Preparatory and User Materials

The Contractor shall provide preparatory materials sufficient to support wargame developers, faculty, facilitators, analysts, and student role players in the effective use of AI-enabled tools.

Materials may include:

User guides Quick-reference guides Workflow instructions Demonstrations Descriptions of AI strengths and limitations Relevant reference information

5.3 Responsible Human Use

AI-generated content shall be treated as decision-support material and shall remain subject to human review, validation, and approval.

The Contractor shall not represent AI-generated analysis as authoritative Government judgment.

The application shall support human-machine teaming and shall not replace the professional judgment of Government personnel, faculty, students, or operational planners.

6.0 DELIVERABLES AND DUE DATES

The Contractor shall provide the following deliverables. Capability-specific deadlines may vary based on Government requirements and shall be documented in an approved project schedule, product requirements document, development backlog, or plan of action and milestones.

CLIN Deliverable Description Due Date

Application Access and User Onboarding

Provide application access, establish authorized user accounts, and furnish current onboarding instructions.

Within 5 business days after award;

thereafter, as requested

Application Support and Maintenance

Maintain the application, provide technical support, correct service issues, and provide generally available commercial updates.

Throughout the period of performance

Release Notes and Service Notifications

Provide notice of material updates, scheduled maintenance, service interruptions, and significant changes affecting Government users.

As changes occur

Monthly Service Summary

Summarize availability, user-support activity, significant issues, updates, and planned maintenance.

Monthly

Kickoff and Problem Refinement

Confirm initial development priorities, stakeholders, intended outcomes, constraints, and preliminary schedule.

Within 10 business days after exercise of

CLIN 0002

Product Requirements Document or Equivalent

Document the approved problem statement, requirements, proposed capability, acceptance criteria, dependencies, integration approach, testing approach, and delivery schedule.

As established for each authorized capability

Development Backlog and Status

Maintain the prioritized backlog and report status, risks, dependencies, accomplishments, and next steps.

Updated at least monthly while CLIN 0002 work is active

Capability Demonstration

Demonstrate a prototype or completed capability to designated Government stakeholders for review and feedback.

At agreed development milestones

Capability Delivery and Documentation

Deliver the accepted capability with release notes, user instructions, configuration information, interface or API documentation when applicable, and other agreed documentation.

In accordance with the approved schedule

Final Development Summary

Summarize completed work, delivered capabilities and integrations, unresolved issues, recommendations, technology-review observations, and transition considerations.

Within 10 business days after completion of each major development effort or at contract closeout

Deliverables identified for CLIN 0002 are required only if CLIN 0002 is exercised.

7.0 RELEASE OF INFORMATION

Project-related documentation and information developed or obtained in support of this PWS shall not be publicly released unless authorized in writing by the Government.

The Government will assign the appropriate distribution statement in accordance with DoDI 5230.24 or other applicable guidance, and the Contractor shall mark documents as directed.

8.0 DATA RIGHTS AND INTELLECTUAL PROPERTY

The Contractor retains ownership of its pre-existing commercial application, proprietary software, source code, models, architectures, development tools, and other intellectual property developed at private expense, except as otherwise provided by the contract.

The Government shall retain the rights provided by applicable FAR and DFARS clauses in Government-funded deliverables. It shall have unlimited rights in Government-provided data and Government-authored or Government-generated materials.

This includes scenarios, exercise injects, courses of action, student and faculty products, observations, after-action reviews, analytics, training materials, and other Government content used or created in performance of this contract.

Rights in custom-developed software, AI agents, workflows, interfaces, APIs, plugins, integration artifacts, technical data, and documentation delivered under optional CLIN 0002 shall be governed by applicable contract clauses and any specifically negotiated license terms.

The Contractor shall identify proprietary or restricted-rights material incorporated into a deliverable before Government acceptance.

9.0 MEETINGS AND COORDINATION

Most coordination shall occur through email, virtual collaboration tools, demonstrations, and document review.

The Contractor shall participate in a virtual kickoff meeting after award and in additional meetings when necessary to address major milestones, requirements, risks, testing, or acceptance.

If CLIN 0002 is exercised after contract award, the Contractor shall participate in a CLIN 0002 kickoff or requirements-refinement meeting within 10 business days after exercise.

No standing recurring meeting is required unless mutually agreed.

Only the Contracting Officer may change contract scope, price, terms, or period of performance.

10.0 EXIT / TRANSITION SUPPORT

The Contractor shall support exit / transition upon completion of this contract or follow-on contract(s). That shall include an export and deletion of all Government-owned data.

11.0 MONTHLY PROGRESS REPORTS

The Contractor shall submit a consolidated Monthly Progress Report in a Government-approved format.

The report shall include:

Contractor name, contract number, order number, and reporting period.

CLIN 0001 service availability, user-account activity, support requests, significant incidents, maintenance, and commercial releases.

Problem areas encountered, corrective actions, decisions required from the Government, and anticipated effects on cost or schedule.

Amounts invoiced and cumulative funding status, when requested by the Government.

If CLIN 0002 is exercised, the report shall clearly distinguish CLIN 0001 service performance from CLIN 0002 development activity and shall also include:

CLIN 0002 accomplishments Deliverable status Backlog status Development milestones Testing results Risks and dependencies Planned activities Amount invoiced under CLIN 0002

12.0 QUALITY ASSURANCE AND CONTRACTOR QUALITY CONTROL

The Government will perform surveillance in accordance with its Quality Assurance Surveillance Plan.

Within 10 business days after award, the Contractor shall provide a concise Quality Control Summary describing the internal processes used to review application services for accuracy, completeness, security, timeliness, and conformance with contract requirements.

If CLIN 0002 is exercised, the Quality Control Summary shall also address development, integration, testing, documentation, and acceptance-support activities.

The Contractor shall promptly correct deficiencies identified through its quality-control process or Government surveillance.

13.0 PLACE OF PERFORMANCE

The Contractor shall perform most work remotely at Contractor facilities or within the Contractor-hosted environment.

In-person support may be required at NDU campuses in Washington, DC, or Norfolk, Virginia, when authorized by the Government.

Off-site work shall be performed in accordance with applicable Contractor and Government requirements for a safe and secure work environment.

Washington, DC location:

300 5th Avenue SW Washington, DC 20319

Norfolk, Virginia location:

7800 Hampton Boulevard Norfolk, VA 23511

Any travel necessary to perform this requirement shall be included in the Contractor's fixed price.

Travel will not be separately reimbursable unless specifically authorized in writing by the Contracting Officer through a contract modification.

14.0 PERIOD OF PERFORMANCE

The period of performance is for 12 months, anticipated to be 30 Sep 2026 through 29 Sep 2027.

Option CLIN 0002 may be exercised at contract award or later during the 12 months in accordance with clause FAR 52.217-9, subject to mission need, availability of funds, and Contracting Officer approval. Exercise of CLIN 0002 will not extend the overall contract period unless otherwise authorized through a contract modification. The Contractor shall not perform CLIN 0002 work before the written exercise of the option by the Contracting Officer.

15.0 SECURITY REQUIREMENTS

Performance under this PWS is unclassified.

The application and associated Contractor systems shall be used only for unclassified information authorized for release to participating U.S.

personnel, international fellows, and other approved users.

Classified information and Controlled Unclassified Information shall not be entered, uploaded, stored, processed, transmitted, or otherwise introduced into the application or supporting systems.

The Contractor shall protect Government-provided and Government-generated information from unauthorized access, disclosure, alteration, loss, or misuse.

Application users, data repositories, integrations, and development environments shall employ appropriate access controls, authentication, logging, data separation, backup, and cybersecurity safeguards consistent with applicable contract requirements and commercially reasonable security practices.

The Contractor shall immediately report any actual or suspected unauthorized disclosure, data loss, cybersecurity incident, or compromise involving Government information.

Government data shall not be used to train publicly available models, improve unrelated commercial products, or for any purpose outside contract performance without prior written Government authorization.

16.0 CONTRACTOR-FURNISHED ITEMS

Unless expressly identified as Government-furnished property or information, the Contractor shall furnish all labor, supervision, software, hosting, licenses, equipment, development tools, materials, and incidental items necessary to perform this PWS.

17.0 CONTRACTOR IDENTIFICATION

Contractor personnel shall identify themselves as Contractor employees when attending meetings, responding by telephone, communicating by email, or otherwise interacting with Government personnel or third parties when their status is not apparent.

Contractor-prepared documents shall be marked as such when appropriate.

18.0 PAYMENT PROCEDURES, INVOICING, AND INVOICE REQUIREMENTS

The Contractor shall submit invoices through Wide Area Workflow in accordance with the payment instructions established in the contract.

CLIN 0001 is priced on a monthly basis and shall be invoiced monthly. Invoices shall identify the month or service period covered and the amount billed.

No CLIN 0002 invoice may be submitted before the Contracting Officer exercises CLIN 0002 in writing.

If CLIN 0002 is exercised, the Contractor shall invoice in accordance with the payment schedule established in the contract. CLIN 0002 invoices shall reflect the fixed-price mission AI engineering, integration, and application development services provided during the applicable invoicing period or milestone.

Invoices shall:

Identify the applicable CLIN.

Identify the period of service or deliverable covered.

Match the contract pricing schedule.

Be supported by required monthly reporting.

Exclude separately invoiced labor hours unless expressly authorized by the contract.

Exclude separately reimbursed travel unless authorized through contract modification.

19.0 POINTS OF CONTACT

19.1 NDU Primary Technical Point of Contact

Major Gary Roach, U.S. Army National Defense Wargaming Center National Defense University Fort Lesley J. McNair Washington, DC 20319 Voice: (202) 685-4681 Email: gary.r.roach.mil@ndu.edu

Major Roach is the proposed Contracting Officer's Representative, subject to formal written designation by the Contracting Officer.

The COR will perform surveillance, review deliverables and invoices, document acceptance, maintain contract-administration records, and notify the Contracting Officer of actual or potential performance issues in accordance with the COR designation letter.

Only the Contracting Officer may authorize changes to contract scope, price, funding, terms, or period of performance or exercise option CLIN 0002.

19.2 NDU Secondary Technical Point of Contact

Michael G. Ferguson, AD-04 National Defense Wargaming Center National Defense University 7800 Hampton Boulevard Norfolk, VA 23511 Voice: (757) 443-6359 Email: fergusonm@ndu.edu

The Technical Point of Contact is responsible for monitoring the Contractor's technical performance and responding to technical questions within the scope of the contract.

The Technical Point of Contact may provide technical clarification, coordinate Government stakeholders, support backlog prioritization, and participate in technical review, testing, and acceptance recommendations.

The Technical Point of Contact may not change contract scope, price, funding, terms, or period of performance, and may not authorize the Contractor to begin work under optional CLIN 0002.

20.0 CONDUCT OF CONTRACTOR PERSONNEL

The Contracting Officer may require the Contractor to remove personnel from performance when removal is in the Government's best interest, including for security concerns, misconduct, conflicts of interest, unethical conduct, or violation of installation regulations.

The Contractor shall provide qualified replacement personnel without additional cost to the Government when removal results from Contractor personnel conduct or performance.

21.0 ACCIDENT REPORTING PROCEDURES

For an accident occurring on Government property or involving Government personnel or property, the Contractor shall submit a written report to the Contracting Officer within 72 hours.

The report shall include:

Date and time of occurrence Place of occurrence List of personnel directly involved Chronological description of the event Circumstances and known effects Immediate corrective actions

N0018926QD216

mailto:gary.r.roach.mil@ndu.edu mailto:fergusonm@ndu.edu

Requirements Pytho Artificial Intelligence (AI) platform services, engineering services, and integration services tailored for wargaming operations for the National Defense University

Continuation of Packaging and Marking

Continuation of Inspection and Acceptance

Overall Contract Inspection/Acceptance Locations

Inspection and Acceptance Location

Both Destination Instructions: Inspection and Acceptance will be performed by the NDU Technical Point of Contact (TPOC)

DoDAAC: HQ0100 CountryCode: USA

NATIONAL DEFENSE UNIVERSITY

300 5TH AVE SW BLDG 62 ROOM 174, FORT LESLEY J MCNAIR

WASHINGTON, DC 20319-5066

UNITED STATES

Major Gary Roach, U.S. Army, NDU Technical Point of Contact Email: gary.r.roach.mil@ndu.edu Telephone: (202) 685-4681

Option Line Item

Inspection and Acceptance Location

Both Destination Instructions: Inspection and Acceptance will be performed by the NDU TPOC

DoDAAC: HQ0100 CountryCode: USA

NATIONAL DEFENSE UNIVERSITY

300 5TH AVE SW BLDG 62 ROOM 174, FORT LESLEY J MCNAIR

WASHINGTON, DC 20319-5066

UNITED STATES

Major Gary Roach, U.S. Army, NDU Technical Point of Contact Email: gary.r.roach.mil@ndu.edu Telephone: (202) 685-4681

Continuation of Deliveries or Performance

Overall Contract Delivery Period

Contractor Destination

Line Item Delivery Schedule Quantity Address and POC

Period of Performance From 30 Sep 2026 To 29 Sep 2027

12 Months

Option Line Item

Period of Performance From 30 Sep 2026 To 29 Sep 2027

12 Months

Continuation of Accounting and Appropriation Data

Contract Clauses

FAR Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

52.203-19 Prohibition on Requiring Certain Internal Confidentiality Agreements or Statements. Jan 2017 52.204-13 System for Award Management-Maintenance. (Deviation 2026-O0038) Feb 2026

52.212-4 Terms and Conditions-Commercial Products and Commercial Services. (Deviation 2026- O0038)

Feb 2026

52.222-19 Child Labor-Cooperation with Authorities and Remedies. (Deviation 2026-O0038) Mar 2026 52.222-35 Equal Opportunity for Veterans. (Deviation 2026-O0038) Feb 2026 52.222-36 Equal Opportunity for Workers with Disabilities. (Deviation 2026-O0038) Feb 2026 52.222-37 Employment Reports on Veterans. (Deviation 2026-O0038) Feb 2026 52.226-8 Encouraging Contractor Policies to Ban Text Messaging While Driving. May 2024 52.232-33 Payment by Electronic Funds Transfer-System for Award Management. Oct 2018 52.232-40 Providing Accelerated Payments to Small Business Subcontractors. Mar 2023 52.233-3 Protest after Award. (Deviation 2026-O0038) Feb 2026 52.233-4 Applicable Law for Breach of Contract Claim. (Deviation 2026-O0038) Feb 2026 52.224-3 Privacy Training. Jan 2017

DFARS Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

252.203-7000 Requirements Relating to Compensation of Former DoD Officials. Sep 2011 252.203-7002 Requirement to Inform Employees of Whistleblower Rights. Dec 2022 252.223-7008 Prohibition of Hexavalent Chromium. Jan 2023 252.225-7056 Prohibition Regarding Business Operations with the Maduro Regime. Jan 2023 252.225-7060 Prohibition on Certain Procurements from the Xinjiang Uyghur Autonomous Region. Jun 2023 252.232-7003 Electronic Submission of Payment Requests and Receiving Reports. Dec 2018 252.232-7010 Levies on Contract Payments. Dec 2006 252.247-7023 Transportation of Supplies by Sea. Oct 2024 252.204-7004 Antiterrorism Awareness Training for Contractors. Jan 2023 252.204-7015 Notice of Authorized Disclosure of Information for Litigation Support. Jan 2023

252.209-7004 Subcontracting with Firms that are Owned or Controlled by the Government of a Country that is a State Sponsor of Terrorism.

May 2019

252.243-7002 Requests for Equitable Adjustment. Dec 2022 252.239-7018 Supply Chain Risk. Dec 2022

FAR Clauses Incorporated by Full Text

52.219-28 Postaward Small Business Program Rerepresentation. (Deviation 2026-O0038) (Feb 2026)

POSTAWARD SMALL BUSINESS PROGRAM REREPRESENTATION (FEB 2026) (DEVIATION 2026-O0038)

(a) . As used in this clause-Definitions

Long-term contract means a contract of more than five years in duration, including options. However, the term does not include contracts that exceed five years in duration because the period of performance has been extended for a cumulative period not to exceed six months under the clause at 52.217-8, Option to Extend Services, or other appropriate authority.

Small business concern-

(1) Means a concern, including its affiliates, that is independently owned and operated, not dominant in its field of operation, and qualified as a small business under the criteria in 13 CFR part 121 and the size standard in paragraph (c) of this clause.

(2) , as used in this definition, means business concerns, one of whom directly or indirectly controls or has the power to control the others, Affiliates or a third party or parties control or have the power to control the others. In determining whether affiliation exists, consideration is given to all appropriate factors including common ownership, common management, and contractual relationships. SBA determines affiliation based on the factors set forth at 13 CFR 121.103.

(b) If the Contractor represented that it was a small business concern, a small disadvantaged business concern, or a joint venture that was any of the small business concerns identified in 19.000(a)(3) prior to award of this contract, the Contractor shall rerepresent its size and socioeconomic status according to paragraph (e) of this clause or, if applicable, paragraph (g) of this clause, upon occurrence of any of the following:

(1) Within 30 days after execution of a novation agreement or within 30 days after modification of the contract to include this clause, if the novation agreement was executed prior to inclusion of this clause in the contract.

(2) Within 30 days after a merger or acquisition that does not require a novation or within 30 days after modification of the contract to include this clause, if the merger or acquisition occurred prior to inclusion of this clause in the contract.

(3) For long-term contracts-

(i) Within 60 to 120 days prior to the end of the fifth year of the contract; and

(ii) Within 60 to 120 days prior to the date specified in the contract for exercising any option thereafter.

(c) The Contractor shall rerepresent its size status in accordance with the size standard in effect at the time of this rerepresentation that corresponds to the North American Industry Classification System (NAICS) code(s) assigned to this contract. The small business size standard corresponding to this NAICS code(s) can be found at https://www.sba.gov/document/support--table-size-standards.

(d) The small business size standard for a Contractor providing an end item that it does not manufacture, process, or produce itself, for a contract other than a construction or service contract, is 500 employees, or 150 employees for information technology value-added resellers under NAICS code 541519, if the acquisition-

(1) Was set aside for small business and has a value above the simplified acquisition threshold;

(2) Used the HUBZone price evaluation preference regardless of dollar value, unless the Contractor waived the price evaluation preference; or

(3) Was an 8(a), HUBZone, service-disabled veteran-owned, economically disadvantaged women-owned, or women-owned small business set-aside or sole-source award regardless of dollar value.

(e) Except as provided in paragraph (g) of this clause, the Contractor shall make the representation(s) required by paragraph (b) of this clause by validating or updating all its representations in the Representations and Certifications section of the System for Award Management (SAM) and its other data in SAM, as necessary, to ensure that they reflect the Contractor's current status. The Contractor shall notify the contracting officer in writing within the timeframes specified in paragraph (b) of this clause, that the data have been validated or updated, and provide the date of the validation or update.

(f) If the Contractor represented that it was other than a small business concern prior to award of this contract, the Contractor may, but is not required to, take the actions required by paragraphs (e) or (g) of this clause.

(g) If the Contractor does not have representations and certifications in SAM, or does not have a representation in SAM for the NAICS code applicable to this contract, the Contractor is required to complete the following rerepresentation and submit it to the contracting office, along with the contract number and the date on which the rerepresentation was completed:

(1) The Contractor represents that it is, is not a small business concern under NAICS Code assigned to contract number.____ ____

(2) [ .] The Contractor represents Complete only if the Contractor represented itself as a small business concern in paragraph (g)(1) of this clause that it is, is not, a small disadvantaged business concern as defined in .13 CFR 124.1001

(3) . The Contractor represents that it is, is not a Women-owned small business (WOSB) joint venture eligible under the WOSB Program joint venture that complies with the requirements of 13 CFR 127.506(a) through (c). [ The Contractor shall enter the name and unique entity ____ identifier of each party to the joint venture: __.]

(4) . The Contractor represents that it is, is not a joint Economically disadvantaged women-owned small business (EDWOSB) joint venture venture that complies with the requirements of 13 CFR 127.506(a) through (c). [ The Contractor shall enter the name and unique entity identifier ____ of each party to the joint venture: __ .]

(5) . The Contractor represents that it Service-disabled veteran-owned small business (SDVOSB) joint venture eligible under the SDVOSB Program is, is not an SDVOSB joint venture eligible under the SDVOSB Program that complies with the requirements of 13 CFR 128.402. [ The ____ Contractor shall enter the name and unique entity identifier of each party to the joint venture: __.]

(6) [ ] The HUBZone joint venture eligible under the HUBZone Program. Complete only if the offeror is a HUBZone small business concern.

offeror represents, as part of its offer, that It is, is not a HUBZone joint venture that complies with the requirements of 13 CFR 126.616(a) through (c). [ The Contractor shall enter the name and unique entity identifier of each party to the joint venture: .] Each HUBZone small business ____ concern participating in the HUBZone joint venture must be certified as a HUBZone concern. [ Contractor to sign and date and insert authorized ____ signer's name and title.]

(End of clause)

DFARS Clauses Incorporated by Full Text

252.232-7006 Wide Area WorkFlow Payment Instructions. (Tailored) (Jan 2023)

WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (JAN 2023)

(a) As used in this clause- Definitions.

"Department of Defense Activity Address Code (DoDAAC)" is a six position code that uniquely identifies a unit, activity, or organization.

"Document type" means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF).

"Local processing office (LPO)" is the office responsible for payment certification when payment certification is done external to the entitlement system.

"Payment request" and "receiving report" are defined in the clause at 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(b) The WAWF system provides the method to electronically process vendor payment requests and receiving reports, as Electronic invoicing.

authorized by Defense Federal Acquisition Regulation Supplement (DFARS) 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(c) To access WAWF, the Contractor shall- WAWF access.

(1) Have a designated electronic business point of contact in the System for Award Management at https://www.sam.gov; and

(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this web site.

(d) The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice WAWF training.

Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the "Web Based Training" link on the WAWF home page at https://wawf.eb.mil/

(e) Document submissions may be via web entry, Electronic Data Interchange, or File Transfer WAWF methods of document submission.

Protocol.

(f) The Contractor shall use the following information when submitting payment requests and receiving reports in WAWF payment instructions.

WAWF for this contract or task or delivery order:

(1) The Contractor shall submit payment requests using the following document type(s): Document type.

(i) For cost-type line items, including labor-hour or time-and-materials, submit a cost voucher.

(ii) For fixed price line items-

(A) That require shipment of a deliverable, submit the invoice and receiving report specified by the Contracting Officer.

____N/A

(B) For services that do not require shipment of a deliverable, submit either the Invoice 2in1, which meets the requirements for the invoice and receiving report, or the applicable invoice and receiving report, as specified by the Contracting Officer.

____Invoice 2-in-1

(iii) For customary progress payments based on costs incurred, submit a progress payment request.

(iv) For performance based payments, submit a performance based payment request.

(v) For commercial financing, submit a commercial financing request.

(2) ) Fast Pay requests are only permitted when Federal Acquisition Regulation (FAR) 52.213-1 is included in the contract.

[Note: The Contractor may use a WAWF "combo" document type to create some combinations of invoice and receiving report in one step.]

(3) The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF Document routing.

when creating payment requests and receiving reports in the system.

Routing Data Table*

Field Name in WAWF Data to be entered in WAWF

Pay Official DoDAAC HQ0762

Issue By DoDAAC N00189

Admin DoDAAC N00189

Inspect By DoDAAC HQ0100

Ship To Code ____

Ship From Code ____

Mark For Code ____

Service Approver (DoDAAC) HQ0100

Service Acceptor (DoDAAC) HQ0100

Accept at Other DoDAAC ____

LPO DoDAAC HQ0100

DCAA Auditor DoDAAC ____

Other DoDAAC(s) ____

(4) The Contractor shall ensure a payment request includes documentation appropriate to the type of payment request in Payment request.

accordance with the payment clause, contract financing clause, or Federal Acquisition Regulation 52.216-7, Allowable Cost and Payment, as applicable.

(5) The Contractor shall ensure a receiving report meets the requirements of DFARS Appendix F. Receiving report.

(g) WAWF point of contact.

(1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity's WAWF point of contact.

____Michael G. Ferguson, AD-04, National Defense Wargaming Center, National Defense University, (757) 443-6359, fergusonm@ndu.edu

(2) Contact the WAWF helpdesk at 866-618-5988, if assistance is needed.

(End of clause)

Addendum to 52.212-4, Contract Terms and Conditions - Commercial Products and Commercial Services

Contract Terms and Conditions Required To Implement Statutes or Executive Orders — Commercial Products and Commercial Services

Addendum to Contract Clauses

Contract Clauses

FAR Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

52.209-6 Protecting the Government's Interest When Subcontracting With Contractors Debarred, Suspended, Proposed for Debarment, or Voluntarily Excluded. (Deviation 2026-O0038)

Feb 2026

52.222-3 Convict Labor. (Deviation 2026-O0038) Feb 2026

52.222-90 Addressing DEI Discrimination by Federal Contractors. (Deviation 2026-O0040, Revision 1)

Apr 2026

52.240-91 Security Prohibitions and Exclusions. (Deviation 2026-O0038) Feb 2026

52.244-6 Subcontracts for Commercial Products and Commercial Services. (Deviation 2026- O0038)

Apr 2026

52.203-12 Limitation on Payments to Influence Certain Federal Transactions. Jun 2020 52.204-9 Personal Identity Verification of Contractor Personnel. Jan 2011 52.223-5 Pollution Prevention and Right-to-Know Information. May 2024 52.224-1 Privacy Act Notification. Apr 1984 52.224-2 Privacy Act. Apr 1984 52.232-39 Unenforceability of Unauthorized Obligations. Jun 2013 52.237-2 Protection of Government Buildings, Equipment, and Vegetation. Apr 1984 52.247-34 F.o.b. Destination. Jan 1991 52.240-93 Basic Safeguarding of Covered Contractor Information Systems. (Deviation 2026-O0038) Feb 2026

DFARS Clauses Incorporated by Reference

Number Title Effective Date

Alternate/…