JCTMI RWP Attch A_White Paper Contents_17 June 2026.pdf

RWP Attachment A

White Paper Contents

Vendors shall submit a white paper describing their apparel Product Lifecycle Management (PLM) solution in accordance with the Call for Solutions (CFS). Instructions for the content of the white paper are contained within this attachment and outlined below.

Vendors shall provide a one (1) page Executive Summary digest of the offeror’s white paper contents and proposed a PLM solution.

Vendors shall provide a detailed narrative of their proposed apparel PLM solution addressing the key areas outlined below.

1.0 Alignment with Army Requirements. Vendor shall provide a narrative describing how their proposed apparel PLM solution directly addresses the Army’s minimum base requirements as detailed in the draft Statement of Work (SOW) and outlined below for an apparel PLM solution.

• Federal Risk and Authorization Management Program (FedRAMP) and Capability Maturity Model Integration (CMMI) Level certifications

• Cloud hosting abilities

• Authorization to Operate (ATO) security Impact Level (IL) four (4) with privacy overlay or a clear plan to achieve compliance within 15 months of award

• Low-code/no-code a search-based design

• Integration capabilities with other software systems including but not limited to Adobe Illustrator, and Browzwear or Clo or other 3D visualization software

• Multi-tenants user license capability and scalability of licenses

2.0 Alignment with Army Needs. Vendor shall provide a narrative describing how their proposed apparel PLM solution directly addresses the Army’s stated needs and objectives detailed in the draft SOW and outlined below for an apparel focused PLM system.

• Ability to remain commercially available, vendor-supported product that continues to receive regular updates and enhancements.

• Encompass information covered in Department of War product specifications (requirements, verifications, testing, material and components, etc.) and development process.

• Automation of processes across functional areas, incorporating technological advancements in product development, and managing product information for Clothing and Textile (C&T) items.

• User onboarding, training, and ongoing support, as well as an ability for introducing new capabilities or modules

• Demonstrated process maturity, reliability, and the ability to provide consistent updates and support.

• Compliance with all applicable federal security standards, both current and future, to ensure ongoing data protection and regulatory adherence.

3.0 Technical Approach.

3.1. System Design & Features. Vendor shall provide a narrative describing the system design and features for their Joint Clothing Textile Modernization Initiative (JCTMI) apparel PLM solution. The narrative shall include, but is not limited to, the following in no order of precedence:

• Configurability, built in tools, settings and user interfaces for different users/entities without custom coding

• Automated backup, routine maintenance, and disaster recovery procedures.

• Configuration functionality to capture and log changes within the system and version history for audit and traceability purposes.

• User-interface and features such as workflows, templates, libraries, and dashboards

• Integration capabilities with existing and future-related software systems. (Application

Programming Interfaces (APIs), web services, plug-ins and interoperability with third-party platforms.)

• Security and permissions controls for different user roles

• Search and reporting capabilities (out-of-the-box and customizable, exportable reports in multiple formats)

• Ability and methodology to capture costing, product development and vendor activities across the lifecycle

3.1.1. System Design Architecture Drawing. Vendor shall prepare a system design architecture drawing exported as a pdf, and submitted as Annex A.

3.2.2. Modular Open Systems Approach (MOSA). Vendor shall provide a narrative describing how their solution uses modular design, open standards, and supports future upgrades

4.0. Uniqueness & Innovative Approach to Future Capabilities & Challenge Areas. Vendor shall provide a narrative describing any innovative, unique or creative solutions for the most complex and critical challenge areas relevant to a JCTMI PLM system that the vendor intends to incorporate into their proposed technical solution. Narrative may cover any of the specified challenge areas below, as well as any unspecified challenge areas not listed:

• Scalability and modularity

• User interface and workflow automation

• Integration with existing/developing industry capabilities (e.g., body scanning, 3D visualization, size prediction, block pattern management, 3D designs, avatar creation, technical design, supply chain)

• Interoperability with supply chain management systems and processes for data exchange and end-to-end visibility

• Enabling capabilities and features (e.g., Artificial Intelligence and Machine Learning (AI/ML), digital twin technology, advanced collaboration tools).

• Novel approaches to interoperability and data exchange

5.0. Cost Proposal (Rough Order of Magnitude –(ROM))

5.1. The vendor must provide a realistic and competitive ROM cost/price for the proposed solution in Annex B. Pricing should be broken down in phases driven by technical outcomes within the objective timeline detailed in the draft SOW. The cost proposal must include all relevant components such as licensing, cloud hosting, maintenance, and support. Vendor shall detail their methodology for scaling operations to support six (6) stakeholder groups assuming one (1) stakeholder at a time and provide a corresponding ROM cost estimate. Additionally, the pricing should be structured to allow maximum flexibility, including options for the introduction of new modules, features, or user groups over time, so that the solution can scale and adapt to evolving requirements.

6.0. Program Management Approach. Vendors shall provide a narrative describing their Program Management approach to meet requirements outlined in the draft JCTMI draft SOW for their JCTMI PLM solution. Narrative should include, but is not limited to, the following:

• Defining the program management structure.

• Identifying key personnel and summarize their professional backgrounds and experience.

• Identifying teaming arrangements and key subcontractors and suppliers.

• Describe your approach to reporting project status

6.1. Program Plan. Vendors shall provide a narrative describing their approach to completing the tasks and meeting the JCTMI objectives outlines in Attachment #1 Draft JCTMI draft SOW.

6.2. Program Schedule. Vendor shall provide a JCTMI PLM solution milestone schedule, in vendor format, as Annex C. The milestone schedule shall include all major activities identified in the draft JCTMI draft SOW plus the vendor’s concurrent internal major activities. Vendors shall use 01 October 2026 as the tentative award date.

6.3. Data Rights. Vendors shall describe their Data Rights approach for their JCTMI PLM solution.

Narrative shall describe how their data rights approach:

• Supports Modular Open Systems Approach (MOSA) objectives.

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

In addition, vendors shall extract and fill out the Data Rights Assertion Table and submit as Annex D.

Table 1. 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 Government Purpose

Interface Control Documents (to include all modular interfaces)

Government Purpose

Software Documentation Government Purpose

Data & Workflow Configuration

Unlimited Government

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

6.4. Program Risk. Vendor shall provide a narrative response which describes the following:

6.4.1 Risk Management and Initial Risk Assessment. Vendor shall provide a narrative response describing their approach to documenting, tracking, and managing areas of program risk. In addition, narrative shall include a table with the vendor’s initial assessment of program risks.

6.4.2 Relevant Experience. Vendor shall provide a narrative, not to exceed two (1) pages, summarizing their relevant experience within the last three (3) years.