JCTMI RWP Request for White Papers 17 June 2026.pdf

Joint Clothing Textile Modernization Initiative (JCTMI) Apparel Product Lifecycle Management (PLM) Solution Request for White Papers (RWP)

Vendors’ white paper submissions shall address the requested contents of the White Paper, the draft Statement of Work (SOW) and shall be structured as follows. See detailed section descriptions following this table. NOTE: White paper SHALL NOT CONTAIN CLASSIFIED INFORMATION and proprietary information shall be clearly marked as such.

Section Page Limit File Format

Cover Sheet 1 page Adobe Portable Format (*.pdf)

Executive Summary 1 page Adobe Portable Format (*.pdf)

Narrative (see White Paper Contents, Attachment A) 25 pages Adobe Portable Format (*.pdf)

Annex A – System Design Architecture* n/a Exported as Adobe Portable Format (*.pdf)

Annex B –Rough Order of Magnitude (ROM) Cost* n/a Adobe Portable Format (*pdf)

Annex C – Project Milestone Schedule n/a Adobe Portable Format (*pdf)

Annex D - Data Right Assertions n/a Adobe Portable Format (*pdf)

1. Cover Sheet: Vendors shall include the following information on the cover sheet of their white paper:

Vendor's company name

Vendor’s address

Points of contact name, phone number, and e-mail address

Commercial and Government Entity (CAGE) Code

Unique Entity ID (created in SAM.gov)

Business size/type (large business, small business, small-disadvantaged business, 8(a) certified small-disadvantaged business, HUBZone small business, woman-owned small business, very small business, veteran-owned small business, service-disabled veteran-owned small business)

Primary NAICS code.

Non-Traditional Defense Contractor (NTDC) designation, as defined in section 3014 of Title 10 US Code §3014? (Yes or No)

2. Executive Summary: The Executive Summary shall provide a one-page digest of the offeror’s white paper contents and proposed JCTMI Apparel PLM solution. The Executive Summary shall only summarize information provided in further detail in the white paper submission and shall not be used to supplement or add to the information provided elsewhere in the white paper.

3. White Paper Narrative: The White Paper Narrative shall address all requested details identified in the White Paper Contents document, and may refer to the associated White Paper Annexes where appropriate (Attachment A).

4. Annexes:

Annexes shall address the required Annex topics/contents but should not be used to circumvent the page limits identified for the White Paper Cover Sheet, Executive Summary, or Narrative sections.

Annex A –System Design Architecture: Vendor shall provide a system architecture drawing of the proposed solution.

Annex B – Cost Proposal - ROM: Table 1 below should be used as the base framework for one (1) stakeholder in Annex B. Table 2 below should show the vendors detailed methodology for scaling operations to support up to six (6) stakeholder groups assuming one (1) stakeholder at a time. Reference the draft SOW for details on the phases for the tables below.

Vendors may expand on either table to provide additional details, features, and costs as they see fit, however the table below identifies the minimum information that the Government desires in the white paper ROMs.

ROM Table 1: Army (Base)

Cost Category Phase 1 Phase 2 Phase 3 Phase 4 Phase 5 Total Licenses Support & Maintenance

Plug-In Services Implementation Services

Cloud Hosting Sub Total Costs

Optional Module(s)

Additional Hosting Fee (Annual)

Requirements

Total Costs

ROM Table 2: Iterative Scaling up to six (6) Stakeholders: Vendor shall detail their methodology for scaling operations to support six (6) stakeholder groups assuming one

(1) stakeholder at a time. See Schedule in the draft SOW. Table 2 shall reflect the cost to add each additional stakeholder, and a separate copy of Table 2 shall also be included reflecting a total price for all 6 additional stakeholders.

Cost Category Phase 1 Phase 2 Phase 3 Phase 4 Phase 5 Total Licenses Support & Maintenance

Plug-In Services

Cloud Hosting Sub Total Costs

Optional Module(s)

Hosting Fee (Annual)

Requirements

Total Costs

Annex C – Project Milestone Schedule: Vendor shall provide a milestone schedule, in vendor format, of the proposed solution. The schedule should depict the implementation of the base PLM, including major milestones of the additional stakeholders. The vendor shall describe the expanding of the system up to six stakeholders for this scaled configuration. Schedules should use 01 October 2026 as a start date.

Annex D – Data Rights Assertions: Vendors shall provide a description of their Data Rights approach for their proposed solution. Narrative shall describe how their data rights approach:

• Supports MOSA objectives.

• Supports unlimited government rights to data and workflow configurations and a documented, non-proprietary method for completing data exports

In addition, the vendor shall identify any software license and/or software subscriptions that the Government would be expected to pay, either during the project or in follow-on sustainment.

Vendors shall extract and fill out the Data Rights Assertion Table and submit as part of Annex D. As appropriate, vendors may add rows to address additional data types and assertions for Government consideration.

Data Rights Assertion Table

Data Rights Assertion Table

Data Type Government Desired (Objective) Data Rights

Vendor Asserted Data Rights

Rationale for Vendor Assertion

Form, Fit, Function Data

Government Purpose Rights

Technical Data Package

Interface Control Documents (to include all modular interfaces)

Software Documentation

Data Configuration & Workflow Process Configuration

Unlimited Government Rights

For definitions of Data Types and Data Rights refer to DFARS 252.227-7013, -7014, - 7018, available at https://www.acquisition.gov