TDP Data

TDPs in the CALS Environment

Digital Data Deliverables

Life Cycle Considerations

Infrastructure Development

Data Uses

The development of an acquisition strategy for TDPs needs to be carefully examined to maximize the value for a specific defence system programme. Programme development elements such as technology, costs, end-item quantities, and schedules have a profound effect on the delivery requirements for supporting TDPs. Therefore, project managers must consider the life cycle of the procurement and the existing and planned Defence infrastructure to support the TDPs for their programme.

The following paragraphs discuss topics of consideration that must be addressed:

• TDP Data;
• TDPs in the CALS Environment;
• Life Cycle Considerations;
• Infrastructure Development;
• Data Uses.

TDP Data

TDP data consists of: TDP elements, TDP management data, and TDP intelligent product data. The same TDP data may be re-grouped in terms of data construction as: Engineering drawings (without or with integral parts lists), Illustrated text documentation, or Intelligent product data.

Engineering Drawings and Integral Parts Lists (PL)

These data mainly consist of illustrations that describe a product or process interspersed with small amounts of text that help explain the features of the product or process. However, in terms of digital data delivery, all of these data may be delivered by either of the following methods:

• raster image files;
• Processable data files, which in this case refers to vector data files, e.g. native
• Computer Aided Design (CAD);
• Initial Graphics Exchange Specification (IGES).

Types of engineering drawings (without or with integral parts lists) are as follows:

• Conceptual Design Drawings and Integral PLs;
• Developmental Design Drawings and Integral PLs;
• Product Drawings and Integral PLs;
• Commercial Drawings and Integral PLs;
• Special Inspection Equipment (SIE);
• Drawings and Integral PLs;
• Special Tooling Drawings and Integral Pls.

Illustrated Text Documentation

Illustrated text documentation is data that mainly consists of text. Sometimes graphics are present, but they usually consist of simple illustrations, figures, or tables. However, in terms of digital data delivery, all of these documents may be delivered by any of the following methods:

• raster image files;
• Processable data files, which in this case means text files;
• Contractor Integrated Technical Information Service (CITIS).

Types of illustrated text documentation are as follows:

TDP Elements

• Conceptual Design Separate PLs;
• Data Lists (DL), or Index Lists (IL);
• Developmental Design Separate PLs;
• DLs, or ILs Product Separate PLs;
• DLs, ILs Commercial Separate PLs;
• DLs, ILs Special Inspection Equipment (SIE) PLs;
• DLs, ILs Special Tooling Separate PLs;
• DLs, ILs Specifications Software and Software Documentation;
• Test Requirements Documents;
• SIE Operating Instructions;
• SIE Description Documentation;
• SIE Calibration Procedures;
• Preservation, Packaging, Packing, and Marking Data;

TDP Management Data:

• Source control drawing approval request;
• Drawing number assignment report;
• Proposed critical manufacturing process description;
• TDP quality control programme plan;
• TDP validation report;
• Quality engineering planning list.

Product Description

Data Product description data or intelligent data includes 3-D information, such as product models that contain the digital information required for full product definition. Intelligent product data are the totality of data required to completely define a product throughout its entire life cycle. Engineering drawings make up a very small portion of intelligent product data and provide only the human interpretable information for a system. Standards are currently being developed to define more completely this form of data for the following.

Types of product description data are as follows:

• VHSIC hardware description language;
• Electronic Design Interchange Format (EDIF);
• IPC-D-350;
• Native CAD format;
• Gerber data.

TDPs in the CALS Environment

The CALS strategy provides the project manager with a framework of standards, specifications, and systems to create, manage, and use information in a digital environment. The project manager should recognize the importance of requiring digital data deliverables. The benefits associated with using digital data far exceed what is being discussed in this section .

For TDPs, two benefits of digital data include:

• Improving the handling and reducing the storage of TDP data, primarily engineering drawings, with electronic filing and archiving, ideally creating a data repository.
• Reducing the costs associated with printing and distributing TDP data, especially during the development stages, by providing on-line access (CITIS) (see Section 5 - CITIS) to contractor databases, so that the NATO/NATO nations procuring agency could access specific TDP data required.

Please note that this section does not consider delivery of a TDP in other than digital format justifiable. References to nondigital data deliverables are only made in conjunction with the delivery of a digital product and for the sole purpose of verifying the quality and accuracy of the digital transfer of data between the various digital systems.

A brief discussion of both nondigital and digital data deliverables is provided. The nondigital deliverables will not be addressed again in this section since their importance in a CALS environment is minimal. The digital deliverables will be mentioned here providing a brief overview of options available to the project manager.

Paper, Mylar Hardcopy

Digital Data Deliverables

Digital data deliverables available in the CALS environment are extensive. Digital data provides the project manager with a variety of digital data content, formats and media option (Table 3-1).

Life Cycle Considerations

As a defence system develops through its life cycle, TDP deliverable requirements may vary. In addition, the availability as well as the volume and format of the data generated by the contractor changes. The project manager must be prepared to adjust the contract data requirements to meet the needs of all organizations involved in the procurement and support of the defence system. The project manager must anticipate the upcoming contract and be prepared to alter the data requirements in the procurement documents.

The project manager must also consider the information volume and typical use of the particular TDP element selected. To take advantage of the CALS strategy, data must be created and/or obtained in a digital form during the earliest possible programme phase . By starting early, product information may be used repeatedly throughout the life cycle. Failure to develop data in a digital form early in a programme can lead to requirements for costly data conversion and will deny potential benefits from digital data exchange.

Infrastructure Development

Effective acquisition of digital data can only be done with full consideration of the ability of Defence activities to receive, store, distribute, and use the digital data that complies with the CALS standards. The project manager must establish the uses for which the data is required and the infrastructure modernization programmes available to support this data.

The evolution of infrastructure is a key consideration in implementing the CALS strategy on any given acquisition. Deficiencies in programme related infrastructure may require cost investments to effectively implement the CALS strategy. The availability of digital data processing and telecommunications technology and approved standards for creation management, storage management, transmission, data protection, and integrity of data at the time of delivery or access are important criteria for acquisition decisions.

The current and projected capabilities of both the contractor and NATO Armed Forces components must be assessed with respect to programme needs and schedules. The NATO/NATO nations Concept of Operation (NCoO), its 'Contractor's approach to CALS Implementation' counterpart, and CALSIP (when required), are excellent vehicles for making these determinations. Project managers must plan to acquire and/or access digital data products. The data user infrastructure, the computing environment available to a particular user, must be considered when acquiring digital data. This environment establishes the data processing capabilities of that user.

The following areas identify a user's infrastructure:

• Hardware: Determine the current and planned hardware available to support the defence system programme.
• Software: This is the most critical element. Interoperability will normally be achieved through the use of software. Again, determine both present and future software applications and availability.
• Networks: Determine the local- and wide-area networking (LAN and WAN) capabilities and whether CITIS will be used.

Data Uses

The project manager will need to identify the use of the data by all organizations involved in the acquisition programme. Identification and establishment of data requirements are generally determined by conducting a data call. The project manager must consider how data will be processed in order to make good decisions on digital data requirements. The five categories of data processing typical of most defence system programmes are:

• View only: The ability to examine a data file without the ability to change it. This includes viewing selected portions of one or several documents as well as side-by-side comparisons of documents.
• Comment/Annotate: The ability to evaluate and highlight for future reference or to make annotations, approvals, and comments without the ability to change the original file.
• Annotations are associated with a specific item or location within a document and are displayed whenever that point or area of the document is displayed.
• Update/Maintain: The ability to change data either directly or through controlling software in the active files on the host computer.
• Extract/Process/Transform: The ability to extract and modify the format, composition, and structure of the data into another usable form. Archive: The placing of data into a repository to preserve it for future use. The interchange of text type data that traditionally has been conveyed on paper can be transmitted or communicated electronically using the established rules and formats of Electronic Data Interchange (EDI).