DI-TMSS-81810

Technical Manual Organization Plan (TMOP)

Describes the requirements for a Technical Manual Organization Plan that gives the Government a description of the overall technical manual development plan for a ship or major/complex system acquisition.

Approval DateMay 25, 2010

AMSC NumberN9133

Preparing Activity—

Project Number—

OPRSH/SEA 04L2

DTIC Applicable—

GIDEP Applicable—

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatdd_form_1664

963C CompliantNo

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

Supersedes

—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

The Technical Manual Organization Plan (TMOP) provides the Government program manager with a description of the overall TM development plan for a ship or major/complex system acquisition. The TMOP is submitted to the Government for review and acceptance prior to the development of the TMs.

This Data Item Description (DID) contains the format and content preparation instruction for the data product generated by the specific and discrete task requirement as delineated in the contract.

This data item shall not be procured when this information is provided by any other document.

Preparation Instructions

1FormatThe TMOP shall be in the contractor's format.

2ContentThe TMOP shall describe the general processes, procedures, terms, and conditions governing the planning, selection, preparation, and submission of TMs required for a ship or major/complex system acquisition. The TMOP shall include a cover page which identifies the scope and applicability of the plan, including the following:

aName and address of contractor and contract number

bThe ship/system name covered by the plan

cThe Technical Manual Contract Requirement (TMCR) number covering development of the TMOP

dDocument Type Definition (DTD) Public Identifier(s) used to develop the TM(s) covered by the plan

eSubmittal date for the plan

2.1The TMOP shall identify the scope of the TM program for the ship/system and equipment being acquiredThis shall also include a summary of any assumptions, conditions, or limitations affecting TM development.

2.2The TMOP shall identify the approach to satisfying the TM requirements of the contract and applicable TMCRsThe plan shall identify the types of TMs planned and needed for the ship/system and the preparing activity that will be developing each TM. The plan shall also identify the intent to use non-developmental or Government-furnished manuals and commercial-off-the-shelf manuals. The plan shall contain the scope, interfaces, and overlaps of the TMs planned for the ship/system. The plan shall list the current applicable TMCRs to be used for development of the TMs cited in the plan as well as identify any additional TMCRs that will be required. Anticipated tailoring of TMCR requirements shall be also identified.

2.3The TMOP shall list the current applicable DTDs to be used for development of the TMs cited in the plan as well as identify any additional DTDs that will be required

2.4The plan shall identify any intended use of special features, functionalities, or innovations planned for the TM program (e.g., software-driven diagnostics or maintenance data collection functionality within an IETM)

2.5The TMOP shall include a proposed schedule to include the major steps required for progressive transition of the TM-data from the conceptual phase through definition phase to the acquisition phaseThe schedule shall also include TM development, review, and delivery relative to acquisition milestones and other programmatic events (e.g., design schedules, ship delivery dates, equipment installation, initial training conduct, equipment production schedules).

2.6The TMOP shall include a general description of TM product delivery and recordkeeping methods (e.g., integrated data environment, comment tracking database)

2.7The TMOP shall identify the integration and coordination of TM development efforts between contractors and subcontractorsThe plan shall also include an explanation of the methods to be used to affect standardization and data control for the TM program. The plan shall identify methods for:

2.7.1Achieving maximum standardization in writing style, artwork, nomenclature, abbreviations, symbols, etc., and reuse of data

2.7.2Ensuring maximum use/reuse of design, manufacturing, and engineering drawings in TM development

2.7.3Collection, control, and use of source dataExamples of source data elements include system maintenance plan, supportability analyses, and logistics management information.

2.7.4TM configuration control, including tracking and incorporating data affecting one or multiple interrelated TMs

2.8The TMOP shall specify development of supplements for technical information that will be published in hard copy format (e.g., large wiring diagrams, schematics, or classified material) needed to support fleet users, training commands, maintenance centers, and overhaul facilities

2.9The TMOP shall specify the strategy for validation of contractor-developed TMs showing intent to comply with quality assurance requirements of the contract and applicable TMCRsThe plan shall also include specific reference to validation plans used in past contracts.

2.10The TMOP shall identify the process that will be used to review and comment on verification plans prepared by the GovernmentThe plan shall also identify any anticipated intent to support verification.

2.11The TMOP shall identify the contractors' intent to resolve and incorporate validation, verification, and other review findings

References

—

Schema v3.0Community-maintained · Verify against ASSIST

Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer