TM Availability

TM Development

TM Permanent Change Page Development

TM Update Revision Development

New TM or Complete Revision

Source and Legacy Data Considerations

Defence System Configuration Considerations

Program Life Cycle Considerations

Additional TM Update Revision Decisions

Conversion of Illustrations

Utilization of existing TMs and legacy data is likely in the development of completely new systems with similar features. The project manager should be aware that even on completely new defence system programs some portion of the TMs may exist in both digital and non digital formats. This is most relevant when a program is entering the earlier life cycle phases. An important point to remember here is that acquisition of the proper level and type of digital data is most cost effective when defined early in the program's life cycle.

TM Availability

Another consideration the project manager must address is whether existing off-the-shelf TMs will satisfy the program's TM requirements. If more than 90 percent of the TM conforms to the technical requirements and supports the maintenance concept of the equipment, the TM may be used. However, if more than 10 percent of the proposed TM fails to meet the necessary requirements to support the equipment, a new TM should be developed.

TM Development

Once it has been determined that a TM will satisfy the technical requirements and maintenance concept of the equipment, the project manager must determine the present format of the TM and whether change pages and/or a TM supplement will be required. If the "basic" TM is available in a word processor format, the TM may be delivered in its present format providing that this is mutually compatible with the existing infrastructures. If it is not, the TM should be delivered in raster format. Also, if change pages and/or a TM supplement will be required in addition to, or instead of, the "basic" TM, then the development of these items is the same as that required for a new TM except that the format and style of the newly developed items may remain the same as the "basic" TM.

The project manager must now determine how well the existing military TMs cover the maintenance concepts of the equipment. Changes to the hardware configuration or equipment components of the defence system may impact the accuracy of the TM's information. If more than 25 percent of the existing TM is affected by these configuration changes, complete revision of the TM is recommended.

TM Permanent Change Page Development

Once it has been determined that less than 25 percent of the TM needs revision, only change pages will be developed. The basic TM will be converted to raster if it is not already digitized. Change page development will follow the same decision path as the development of a new TM, but the newly created change pages will retain the format and style of the original TM.

TM Update Revision Development

Once it has been determined that more than 25 percent of the TM must be changed, the project manager must decide how the final product will be delivered. The decision process follows the same basic path as that stated for a newly developed TM; the difference is the revised TM may retain the format and style of the original TM.

New TM or Complete Revision

Source and Legacy Data Considerations

The project manager must now consider whether any of the TM source data presently exists as legacy data. Legacy data developed from existing defence systems or from the creation of LSA data may contain enough information to warrant inclusion into the new defence system program.

For newer defence system programs, this legacy data may exist in both digital and Non digital formats. If legacy data does exist in a digital format, the project manager should address life cycle considerations. If no legacy data is to be procured for the defence system's TMs or no digital legacy data exists, the project manager should consider whether configuration changes and/or multiple configurations are anticipated for the end item or defence system.

Defence System Configuration Considerations

Configuration differences may play an important part in the acquisition of defence system TMs. The differences may be as small as printed circuit card modifications or as large as entire equipment changes. The project manager must determine whether multiple configurations will exist, and whether different TMs will be procured for each configuration. Another consideration is whether future changes to the TM are anticipated. If multiple configurations and/or configuration changes are anticipated, conversion of the source or legacy data to digital format is recommended. Specific conversion format may be based on an economic analysis that may recommend that some paper legacy and source data simply be scanned into a raster format and other illustrations be recreated/converted to a vector format. If this is not the case, the defence system program should consider delivery of the TM in raster format for both text and graphics.

Program Life Cycle Considerations

The project manager must now consider the current phase of the end item or defence system program and the anticipated requirements for the TMs. If the end item or defence system program is currently in the later phase(s) of its life cycle and the TM requirements are anticipated to be fewer than five years, the need to deliver SGML-formatted TMs is not recommended, especially since most of the data for the TMs may be in hard copy or proprietary digital format.

If this is indeed the case, delivery of both review and Final Reproducible Copies (FRC) of the TMs in a mutually agreeable format is recommended. If the TM requirements are anticipated to be at least five years and this TM development process is concerned with a TM Update Revision, SGML-formatted TMs are recommended.

Additional TM Update Revision Decisions

A TM Update Revision may retain the style and format of the original TM. With this in mind, additional considerations concerning SGML formatting arise. DTDs and FOSIs may exist that support the modification of the original TM while retaining the original style and format.

If these DTDs do not exist, then the project manager must consider, through economic analysis, whether it is cost effective to modify or create a DTD and FOSI to satisfy the style and format requirements of the original TM. If economic analysis determines that it is not practical, it is recommended that the new TM Update Revision be delivered in a mutually agreeable format for both text and illustrations.

Conversion of Illustrations

The project manager must now determine, through economic analysis, whether conversion of all existing illustrations is justified. Conversion in this case means converting nonvector illustrations, both source and legacy data that currently exists in raster and hard copy formats, into a vector format.

If it is determined that conversion of all existing nonvector illustrations to a vector format is cost effective or if no source or legacy illustrations exist, then the recommended solution is to convert and/or create all applicable illustrations to a vector format such as IGES and/or CGM. If economic analysis determines that conversion of all existing illustrations is not practical, it is recommended that only selected source or legacy illustrations (those with a high likelihood of being revised at a later date) be converted to a vector format. Remaining illustrations should be delivered in raster format.