Tech Data Interactive Electronic Technical Manuals Convertor

# Q&A Changes Summary **New questions added (Q1-Q3):** Three new clarifying questions were inserted at the beginning addressing SYSCOM specificity, S1000D 4.x targeting, and XML output requirements for the Navy's viewer. **Key clarifications:** - **Q1 (new):** Confirmed the viewer should be agnostic across all SYSCOMs, not specific to one command - **Q2 (new):** Confirmed S1000D 4.x is the correct canonical output schema version - **Q3 (new):** Reiterated viewer must ingest S1000D, MIL-STD-3001 XML, PDF, and .nci files - **Q4 (renumbered):** Moved from Q1; unchanged guidance on S1000D and NAVY BREX references **No substantive answer changes:** The remaining answers (previously Q2-Q6, now Q5-Q8) were renumbered but contain identical content clarifying that Phase I focuses on viewer development, with BREX/metrics/validation specifics deferred to Phase II, and no Government-furnished source corpus planned for Phase I.

Status changed from Pre-Release to Open

# Q&A Changes Summary **New Answers Provided:** - **Q1**: Clarified to use S1000D and NAVY BREX for Phase I IETM development (previously unanswered reference questions) - **Q2**: Expanded scope clarification—Phase I focuses on agnostic viewer for multiple formats (S1000D, MIL-STD-3001, PDF); AR/XR display out of scope; data rights preservation required; Navy stakeholder involvement via status meetings - **Q3**: Confirmed Phase I deliverable is agnostic viewer (not conversion); specific BREX/business rules deferred to Phase II; conversion accuracy metrics are placeholders to be finalized with selected vendor; XR user experience not required - **Q5**: Vendor responsible for viewer design per S1000D/BREX/3001-XML specs; metrics are placeholders; no Government-furnished documentation in Phase I; graphics/ICN handling expected in vendor proposal - **Q6**: Partially visible—appears to address commercial AI use permissions (content cut off) **Key Shifts**: Government moved from requiring specific metrics/acceptance criteria to deferring these to Phase II with selected vendor input. Scope narrowed to agnostic viewer development rather than full conversion pipeline.

Q&A reorganized and expanded. Q2 replaced with 4 new questions on corpus composition, AR/XR scope, rights assertions, and stakeholder access. New Q3 added requesting clarification on target output standards (S1000D vs. MIL-STD-3001), Phase I deliverables, accuracy metrics definition, and downstream interfaces. Original Q4 on BREX and marking fidelity moved to Q4 with same answer ("Phase II; metrics TBD").

**Q&A Changes Summary:** - **New Q1 added:** Two procedural questions on document source (DTIC availability) and standard version (MIL-DTL-24784C supersession guidance) - **Q2 renumbered** (was Q1): Business rules, BREX data, and marking-fidelity verification—**answer unchanged** ("Phase II delivery; metrics under development") - **Q3 renumbered** (was Q2): Seven technical specification questions on IETM viewer, schema, accuracy metrics, and source corpus—**answer unchanged** (still pending/TBD) - **Q4 renumbered** (was Q3): Seven AI/Phase I implementation questions on commercial AI use, product selection, target format, and search scope—**answer still pending** (no response provided) **Net change:** Added 1 administrative Q&A; reorganized/renumbered 3 substantive Q&As with no new answers. All previously unanswered technical/AI questions remain pending.

Q1 received answers: BREX data and applicability tables provided in Phase II (not Phase I); no verification/acceptance criteria yet established for marking fidelity; conversion metrics still being derived. Q2 and Q3 remain unanswered.

**Summary of Q&A Changes:** New Q1 added addressing three topics: (1) Government furnishing of BREX data modules and applicability tables vs. performer derivation; (2) marking fidelity verification methods and whether it's included in the 95% conversion accuracy metric or evaluated separately. Previous Q1 and Q2 renumbered to Q2 and Q3 respectively with no substantive changes to their content.

# Q&A Changes Summary **New questions added (Q1):** Six detailed requirements questions covering IETM viewer/schema identification, COTS/GOTS tool specifications, Navy organization ownership, conversion accuracy metrics definition, Government-furnished technical data corpus, and graphics/ICN/parts-data conversion scope. **Q2 unchanged:** All seven original AI use, product selection, format definition, viewer access, and search-scope questions remain verbatim. **Key change:** Shift from broad AI policy questions to specific technical specification and requirements clarification, indicating Government is narrowing scope and defining Phase I technical acceptance criteria.

# Summary for Prospective Applicants This Q&A clarifies critical implementation details that applicants must address in proposals: commercial AI use is apparently permitted in Phase I but performers should plan transition strategies to Navy-approved models for Phase II; the Government will coordinate on product selection, XML format specifications, and IETM viewer access rather than pre-defining these, requiring applicants to propose collaborative approaches; and search capabilities should initially focus on performer-converted content with potential expansion to Navy's existing systems.

New opportunity: Tech Data Interactive Electronic Technical Manuals Convertor