I1.0  INFRASTRUCTURE REQUIREMENTS FOR THE CREATION, MANAGEMENT, AND USE OF DIGITAL DATA

The hardware guidelines provided in this section reflect the current state of art of computer technology. Project managers, however, should understand that the computer technology is constantly changing, and that the items addressed below are provided as a guideline but do not imply that only the following technology should be used in building infrastructure.

I1.1 Introduction
The NATO CALS Handbook provides decision templates for selecting the most effective digital data formats and media formats. Digital data includes the Technical Data Package (TDP), Technical Manuals (TM), and the Logistic Support Analysis Record (LSAR). Effective acquisition and use of digital data can only be accomplished with full consideration of the ability of NATO/NATO nations to receive, store, distribute, and use the digital data.

The infrastructure requirement is a key consideration in implementing the CALS strategy on any defense system acquisition. Do not buy digital data if there is not an adequate digital data infrastructure capability.

The project manager should ensure that all recipients of digital data will have the capability to receive, store, and maintain the provided data. The materials and equipment required for receiving, storing, and maintaining data constitutes the infrastructure requirements of CALS. This infrastructure requirement is a key consideration in implementing the CALS strategy on any defense system acquisition. Deficiencies in the NATO/NATO nations' infrastructure may require investments by the project manager to implement the CALS strategy effectively.

I1.1.1  Purpose
This section is intended to provide NATO/NATO nations project managers with an overview of hardware and telecommunications requirements for the creation, management, and use of digital technical data. Paragraph 7.2 discusses the general considerations and requirements of a computer system infrastructure. Paragraph 7.3 describes the specific requirements that are dependent on the data type, data format, and user function.

I1.1.2  Infrastructure Resource Planning
The project manager should plan to fund an infrastructure modernization program. The project manager should plan infrastructure requirements such that funding can be set aside to be used when the infrastructure investment is required. This approach will utilize program funding and resources better.

I1.2  General Considerations

If data users do not have access to the appropriate hardware, software, and telecommunications equipment, working in a digital data environment can become an obstacle course.

The computer hardware must have the appropriate processing speed and display capability to run the application software adequately. The application software must perform specific tasks on the digital data that are required by the user. Rather than recreate the data, the appropriate computer networking system should allow the users to share data and resources, and telecommunications equipment should allow users to transfer digital data easily. After reading the NATO CALS Handbook, the project manager should have an implementation approach for data type, process, format, and delivery/access method. With this information, infrastructure requirements can be identified. Each decision will affect the life-cycle costs of a program and the cost of the program's computer infrastructure. Human- interpretable data formats, such as Page Description Language (PDL) and raster, may not be suitable as source data for other applications. Processable data formats can be integrated with other digital data to reduce the total life-cycle costs. The following topics are addressed as considerations for a computer infrastructure:

· Computer Architecture
· Computer Operating System
· Storage Devices
· Output Devices
· Computer Graphics and Monitors
· Network Devices
· Application Software
· Software Licensing
· Network Protocols
· Local Area Networks (LANs)
· Wide Area Networks (WAN)
· Data Process

The above topics are the basis of discussion in Paragraph 7.3, Infrastructure Requirements, for specific hardware, software, and telecommunication requirements of a program. Also included are several decision diagrams to help the project manager.

I1.2.1  Hardware Considerations
Computer hardware consists of the computer processor, memory, monitor, storage devices, and input devices. Each computer should be tailored to fit the need of the main application. Computational intensive applications such as mechanical solid modeling or engineering simulation will require a larger amount of memory than general text and 2-D graphics-based applications. Each application requires a distinct amount of hard disk space for data storage. Raster images and simulation models tend to require more disk space than vector-based databases such as Computer Graphics Metafile (CGM) or Computer Aided Design (CAD) files.

I1.2.1.1  Computer Architecture

Computer technology is constantly changing, and the project manager should understand that the items addressed below are provided as a guideline but do not imply that only the following technology should be used in building infrastructure.

Each computer is designed to meet a specific requirement. In many cases, the computer architecture is driven by the choice of application software needed to perform a specific task. For this reason, the software selected may be the most important decision made. The Personal Computers (PC) are the most widely used computers and are ideal for non-intensive applications that require low-to-medium graphic displays. The RISC workstations are widely used in engineering and technical publishing applications that require either a powerful processor for extensive calculations or a high-resolution graphics display for document editing. A "diskless" RISC workstation may provide a low-cost solution to some engineering computing needs. These workstations typically have a small hard disk for the operating system while the application software and user files are loaded from a server workstation that is connected by a network. A third option is a graphic display workstation that supports the X-window Motif standard. However, a PC with X-window emulation software may provide the same features at a lower cost. The standard options for each type of computer are presented in Table I-1.

Table I-1 Standard Options for PC Types

I1.2.1.2  Computer Operating System
The operating system is the shell that interprets the user's commands and translates them into machine code to control the computer's resources. The computer's internal clock, memory, Central Processing Unit (CPU), terminal, and other peripherals are controlled by the operating system. The three major distinctions among operating systems are the internal throughput bit size, the amount of available memory, and the ability for multitasking. Each of these factors controls the effectiveness of a computer for a particular user. The Pentium PCs have a 32-bit internal bus as do most RISC workstations. A few of the high-end RISC workstations have a 64-bit internal bus and will be compatible with a 64-bit operating system. Two operating systems are available for Pentium-based PCs. Disk Operating System (DOS) was the first major operating system for a PC and continues to be the standard. DOS is only an 8-bit or 16-bit operating system and does not offer true multitasking. OS/2 was introduced a few years ago and offered users multitasking and a 32-bit operating system. Windows 95 and Windows NT are similar to System 7, discussed in following paragraph and offers many advantages compared to DOS. The largest benefit is that Windows NT is available on PCs and RISC-based workstations. This will allow the engineering users access to the same application software on a RISC workstation that most business users have on a PC.

A popular operating system used for the 68000 series processor is System 7, which is a true windowing system with 32-bit multitasking capabilities. This operating system has attained popularity due to its ability to meet the demands of both beginner and expert computer users. The operating system has strict hardware/software standards that reduce compatibility and installation problems, although the cost of this system is generally higher than similar Windowing systems. Most RISC workstations currently have a UNIX operating system based on System V UNIX or Berkeley BSD 4.4 UNIX that is POSIX compliant. Each operating system provided with RISC workstations is unique, but most will run application programs that were compiled using System V or Berkeley BSD UNIX. The CAD2 program specifies a POSIX operating system with a Motif standard graphical user interface. OSF/1.0, OPEN VMS, and Windows NT are new operating systems that are designed to allow users a greater variety of application software. Windows NT is designed to allow users of the RISC-based computer and 80486-processor-based-computer to run the same operating system and the same versions of application software.

I1.2.1.3  System Backup
System backup is very important to the project manager. If managed properly, systems can be designed such that even a catastrophic loss of data can be recovered in a relatively short period. To do this, the project manager should address areas such as hard drive or CPU failure, lightning strike, fire, or damaging storm in a disaster recovery plan. Backup of a system should include a practical means to back up system data. This is a function that should be easy to accomplish and convenient to the users. If a system does not have a convenient backup system, the user will be unlikely to back up regularly and, thus, risk catastrophic loss of program data. An acceptable means to archive system and program data is to use a tape backup system.

I1.2.1.4  Physical Media
Each computer system needs the appropriate amount of data storage capacity to allow users access to all areas of project data. This disk space can reside on each computer or on a network file server. Storage technology is constantly changing, and the project manager should understand that the physical media addressed below is provided as a guideline but does not necessarily imply that only the following technology should be used in building infrastructure. When evaluating whether to use new technology, the project manager should assure compatibility with other equipment of the same technology or with older, less sophisticated media.

I1.2.1.4.1  Magnetic Media
Magnetic disk drives are available for most computer systems. Magnetic disk drives can store from 200 to 4,000 megabytes and should be American National Standard Institute (ANSI), SCSI, or IDE compatible. SCSI provides compatibility and allows for expansion when greater disk space is required. Magnetic disks can be used to transfer data when required. The most common magnetic disk used to transfer data is the 3.5-inch diskette that can hold up to 1.44 MB of data. Using magnetic disks to transfer data should only be considered when the total data does not exceed 10 MB. When transferring over 10 MB of data, a 9-track computer tape or Quarter Inch Cartridge (QIC) tape would be better suited (MIL-STD-1840). The standard 9-track tape can store approximately 240 MB of data compared to 500 MB with the QIC. The exact configuration of the tape format can greatly affect the capacity of the tape. Tape drives that accept tape cartridges are easier to obtain and integrate into a desktop computer system. However, the project manager should confirm that tape formats are compatible. An alternative technology to 9-track tape or an optical drive is the Digital Audio Tape (DAT) drive. DAT drives can store up to 5 Gigabytes (G-byte) of data. The tapes are small and are easily integrated into the desktop environment. This avoids capacity problems that are sometimes encountered in 9-track and optical drives.

I1.2.1.4.2  Optical Media
Optical drives are readily available and come in many different types and sizes. The most common optical drive is the 5.25-inch Compact Disk (CD) Read Only Memory (ROM) drive. These drives are used for end user systems similar to the Advanced Technical Information Support (ATIS) system. A Write Once/Read Many (WORM) optical disk system should be considered for storing the final deliverable digital data for a large project. Optical disks can store up to 200 G-bytes. This will provide the project with a non-erasable copy of the data that can help in configuration control. However, not all WORM optical disk systems produce the same format as CD, and compatibility with the end user should be verified.

I1.2.1.5  Output Devices
Each computer user will need access to a printer and/or a plotter. These devices can be set up on a LAN rather than directly to a specific computer, so that network users can share the devices. Printers are generally used to produce "A" or "B" (ANSI Y14.1-80) size documents. Plotters are used to create up to "J" size documents. An "A" size PostScript compatible laser printer is the standard printer recommended for general use. The printer should have a minimum resolution of 300 by 300 Dots Per Inch (DPI) and a minimum print speed of four to eight pages per minute. An "A/B" size laser printer would be better suited to print engineering drawings. Most drawings are legible when printed on "B" size paper. The two main types of plotters are electrostatic and pen plotters. Electrostatic "E" size plotters are recommended for engineers involved in the creation and review of engineering documents or when there is a requirement to plot up to "E" size raster drawings. A pen plotter may suffice, but these plotters can take up to 30 minutes to print a vector drawing versus only 1 to 2 minutes for an electrostatic plotter. Pen plotters cannot be used to plot raster images.

I1.2.1.6  Computer Graphics and Monitors
The resolution and monitor size are important considerations when choosing the proper monitor. Most users who work with graphical data such as engineering drawings or technical illustrations will be more efficient with a high-resolution, 19-inch monitor. This is especially true when working with raster files. A larger monitor may eliminate the need to zoom in on a section of the drawing or illustration. A 14- to 16-inch monitor is suited only for general Windows applications and is not recommended for reviewing drawings or illustrations. An option for some RISC-based workstations is real-time, 3-D graphic manipulations. This allows the user to rotate and/or scale the view of the object in real time. Any engineer performing solid modeling or finite element analysis will increase productivity on the workstation with this option. Screen redraws for complex images can take up to several minutes with a standard graphics option but can be performed instantaneously with the 3-D graphic processors.

I1.2.1.7  Network Devices
Network devices include equipment that is required to connect a single user station to an existing network or to connect two or more networks together. Examples of this type of equipment usually are network cards, bridges, and routers. The basic requirements for creating a single LAN are a Network Interface Card (NIC) and the appropriate cable; for example, an Ethernet board for each computer and the coaxial or twisted-pair cable to connect each computer. Network bridges can be added to the LAN, to connect to other LANs or manage the LAN electronic message traffic. Network terminal servers allow terminals, modems, and printers to be connected into the LAN. Network routers enable remote LANs to be connected or the LAN to connect to a WAN. All network devices should support the Ethernet V2.0 and Institute of Electrical and Electronic Engineers (IEEE) 802.3 standards. Due to LAN configuration complexity and variety, the project manager should discuss infrastructure requirements with the supporting activity Automated Data Processing (ADP) manager before purchasing any LAN equipment.

I1.2.1.8  Input Devices
There are many different ways to provide input to a computer system. One of the most basic input devices is a keyboard. There are many different arrangements; however, the industry standard is the 101-key type. Additional devices include mice, track balls, digitizing tablets, light pens, and scanners. With the exception of the scanner, all the previous devices generate data with the user's guidance. The technology of scanners has greatly increased in the past few years and can add speed in the generation of technical data.

Scanners can have many features including color, gray scale, line art, and a host of others. As a general rule, the more features and higher detail of the image, the more disk space is required. There are definite ranges where there is a point of diminishing return comparing quality of image vs. size of image. Attention should be made to this aspect, because, not only will a large image consume a large amount of disk space, but it will also slow the speed of the computer when the graphic is to be displayed. There are many different types and sizes of scanners available to the project manager.

The two basic types of scanners are page scanners and large-format scanners. Page scanners are designed to be implemented with text or graphics up to 8.5 by 11 inches. When scanning images for documents that are currently being created or updated, a single-page scanner should work well. Features for a single-page scanner include quality of scan and moderate speed. Sheet-fed scanners are generally used to archive large amounts of paper data. The features required are speed of scan and moderate resolution. Large-format scanners are used to generate raster images from paper drawings up to 60 inches wide with an unlimited length. The scanners are monochrome/gray scale and are a single-sheet feed operation. In recent years, the speed and cost have been significantly reduced while quality has been enhanced.

Large-format scanners can provide a means of converting old, deteriorating paper drawings into an electronic form that can be edited and restored, if required. Many activities and sites are currently using scanners. Although the cost has been reduced significantly, a large-format scanner is a major investment and is usually purchased by the software support activity as a shared resource.

I1.2.2  Software Considerations
The project manager must consider how a specific software application fits into the complete data process. Configuration management software may be needed to control the access and revision of digital data files as well as the specific application software. Software applications and repository services already available should be considered before different software applications are examined. Another important question is whether the software import and export files are in a CALS format such as MIL-D-28000 Initial Graphics Exchange Specification (IGES) and MIL-M-28001 Standard Generalized Markup Language (SGML). This will ensure the data will be accessible by other users.

I1.2.2.1  Data Formats
Digital data deliverables available in the CALS environment are extensive. The NATO/NATO nations project manager must evaluate the need to determine which format is appropriate at each stage of a specific program. The final deliverables must be in a standard CALS format while preliminary digital data may be in a format that is agreeable to the project manager and the contractor. Commercial word processing software with the capability of text attribute, style sheets, and imbedded graphics may be used to view and annotate preliminary TMs. A list of various digital data formats is shown in Table I-2.

Table I-2 Standard Digital Data Formats

The project manager must consider who is going to use the data in the armed forces and ensure that the infrastructure matches each user's requirements and the function of the requirements. The required infrastructure will vary depending on the data use and the data format. Formats, such as Raster, will require a higher resolution monitor but less processing capability to view and modify compared to a solid-model-based CAD system. Raster and IGES data formats generally necessitate larger disk memory. Some data functions cannot be performed on all digital data formats.

I1.2.2.2  Operating System Compatibility
The first consideration is which operating systems the program uses. A software application that supports both Disk Operating System (DOS) for the PCS and UNIX for the RISC-based workstations will allow greater flexibility than a program tied to a single operating system. This is especially true when business and engineering personnel need to review the digital data. Most business applications operate on a PC while most engineering applications operate on RISC-based workstation. X-window emulation software may solve some problems. The current generation of X-window emulation programs are quite robust and can be used to allow PC users access to UNIX X-window software from a PC. The PC emulation packages for RISC-based workstations are not as sophisticated as the X-window emulation programs.

I1.2.2.3  Application Packages
General types of packages of application packages are shown in Table I-3.

Table I-3 General Types of Application Packages

I1.2.2.4  Software Licensing
The type of software licensing available can affect the total cost to implement a software system. The four types of software licensing that are prevalent today are single-user license, single-computer license, network license, and a site license. Each licensing option has a proper use and can greatly affect the total life-cycle costs associated with the software procurement. A single-user license allows the software to be loaded on one computer, and one person has access to the program at a time. Most PC software programs are licensed to a single user. A single-computer license is licensed for a specific computer, and the vendor may charge to move the license to a different computer. This type of license can allow either a single user or multiple users access to the program. The multiple-user option is generally used when the software is operating on a mainframe computer or network server. A network license will allow a specific number of simultaneous users, who share a common network, access to the program. Single-computer and network licenses are usually offered on software available on UNIX workstations. These licenses can reduce the total cost of supplying the needed software for all of the users of an acquisition program. A site license allows the software to be used on any computer at a particular location.

I1.2.3  Telecommunications
The standard equipment required for telecommunications is a modem. The modem is used to link two or more computer systems via a phone line. Normal uses could include connection to larger computer systems via a terminal emulation program, connection to a remote site to send/receive files, or to access Contractor Integrated Technical Information Service (CITIS). A more specialized modem that has become readily available is a modem capable of sending and receiving Facsimile (FAX) data as well as the standard CCITT (Consultative Committee for International Telegraphy and Telephony) information. The speed requirement of the modem is directly related to the size of the data files that will be transferred and frequency that the modem will be used. If data is only to be accessed and viewed remotely, using a terminal emulation program, then a 9600-baud (character per second) modem is probably acceptable. However, if there is a requirement to send/receive large data files, a faster modem with built-in data compression is required. Before purchasing a modem, the project manager should assure compatibility with the remote location.

I1.2.3.1  Network Protocols
Network protocols are essentially the software standards that enable users to communicate over LANs or WANs. There are several types of network protocols that are acceptable in the CALS community. Factors to consider when choosing the type of network protocol needed include current facility LAN/WAN compatibility, interface requirements, data to be transferred, and distance of network. The following are common protocols and their capabilities.

· GOSIP: The Government nations Open Systems Interconnection Profile (GOSIP) is the standard for networking protocols. Its function is to provide interoperability among different equipment manufacturers.
· TCP/IP: Transmission Control Protocol/Internet Protocol (TCP/IP) is the general protocol (IEEE 802.3) for most engineering workstations and servers. It allows UNIX computers to connect to each other for remote login with 'rlogin' and 'rsh' UNIX commands. It also allows a PC with X-windowing software to establish an X-window session on a UNIX server.

I1.2.3.2  LAN
A LAN is required when there are several users who need to share data, application software, and equipment. The LAN network devices commonly used are printers, disk drives, modems, and other Management Information System (MIS) equipment. As the name LAN suggests, this type of network is contained within a small area (usually within the same building or floor). LANs are based on the needs of the user. Some LANs may only need to be connected to share resources such as modems or printers. Another LAN function could be used for configuration management of large CALS databases. A common need for organizations is to transfer data from one LAN to another or to connect to a large mainframe computer. These functions can be achieved with what is commonly referred to as a bridge.

A LAN is required when there are several users who need to share data, application software, and equipment. The LAN network devices commonly used are printers, disk drives, modems, and other Management Information System (MIS) equipment. As the name LAN suggests, this type of network is contained within a small area (usually within the same building or floor). LANs are based on the needs of the user. Some LANs may only need to be connected to share resources such as modems or printers. Another LAN function could be used for configuration management of large CALS databases. A common need for organizations is to transfer data from one LAN to another or to connect to a large mainframe computer. These functions can be achieved with what is commonly referred to as a bridge.

I1.2.3.3  WAN
A WAN is required when there are several users who need to share data or equipment over a large area (usually many miles). A WAN should only be considered if there is a need to transfer large amounts of data for long periods. If occasional or limited use of access to remote data or equipment is needed, then a modem will suffice.

I1.2.4  Data Processes
The project manager needs to determine what digital data functions are required and who is the data user. The infrastructure may vary for each use of the data, if the hardware, software, and network cost are to be minimized. Generally, certain data functions are performed with a specific format. Conversion software may need to be procured to ensure that the format of the data is also compatible with the end user's requirements. The user functions are divided in the following areas.

· View: Acceptance, verification, and review of acquired digital data sets.
· Comment/Annotate: Annotate or highlight for future reference, or make annotations and comments without the ability to change the original file. The annotations are associated with a specific item or location within a document.
· Update/ Maintain: Update and modification of digital data.
· Process/Transform: Categorize, extract, cross-reference, and modify the format, composition, and structure of the data into another usable form.
· Archive: Storage of the accepted data into a repository, managed by a central index or locator.

I1.3  Hardware Requirements for Processing Digital Data

I1.3.1  Hardware Requirements for Processing TMs
The hardware requirements for processing TMs are dependent on the specific requirements of the user. However, if the project manager chooses to retain a separate archive master, the suggested system hardware on Table 4-12 provides TM archive capability. The view only function requires the basic equipment to reference TMs. The equipment can be as simple as a machine that can display ASCII characters or as complex as reading CD ROM over a network. The hardware in Table 4-12 displays the equipment required for accessing TMs from a CD ROM. The comment/annotate function for processing TMs is used primarily during the review process prior to and during validation. This is to allow technical personnel the capability to include additional information, if required. To accomplish this task, there must be a link between CD ROM data and additional information stored remotely. If there is no direct link between the CD and the additional information, then there is no requirement to supply CD ROM drives with a system required to comment/annotate TMs. The hardware requirements for updating and maintaining TMs include the capability to work with tagged SGML documents. The system requirements for using an SGML editor can be found in Table I-4. Specific requirements, including CD ROM, scanners, and WORM drives, should be addressed on a case-by-case basis depending on the type and amount of data being processed. The hardware requirements for extracting, processing, and transforming TM data depend on the data being generated. The TM can be generated in a commercial editor and translated into SGML later. This can reduce the infrastructure requirements if there is a basic infrastructure already in place. If the requirement is to transform an approved TM into an Interactive Electronic Technical Manual (IETM), then the hardware should reflect standard equipment that will support an IETM.

Table I-4 Matrix of Infrastructure Requirements

I1.3.2  Hardware Requirements for Processing TDPs
Two decisions that affect the hardware requirements are whether the final engineering drawings will be stored in the native CAD files or an equivalent vector format versus raster and whether the engineers will be performing simulation. Engineering analysis cannot be performed on raster data; thus, the processing requirement to work with only raster data can be significantly less than with processable vector format, such as Initial Graphics Exchange Specification (IGES) or VHDL. Processing TDPs with raster is limited to changes that would be accomplished on a paper or 2-D drawing. This type of processing could make basic changes relatively quickly and easily. However, modeling and simulation are best suited for 3-D vector data. The hardware requirements differ among the disciplines of engineering required to be processed. Some basic commercial IGES drawing packages can produce 3-D models on an 80486 computer. If the project manager plans to simulate the stresses of a mechanical part or the multi layer printed circuit board (PCB) layout, a RISC-based workstation should be considered. In addition to the basic workstation, the project manager should address the procurement of the following equipment:

· Database Server (required for large, drawing databases)
· MIL-STD-1840 tape drive (standard for large, data delivery)
· Other media drives, including DAT, cartridge tape, and QIC (provide large storage capacity)
· PostScript printer (required for A size drawing and documentation)
· A to D size electrostatic plotter (large volume of drawings or for raster drawings)
· A to D size pen plotter (low volume vector drawings)

I1.3.3  Hardware Requirements for Processing ILS/LSAR
The specific hardware requirement for processing ILS/LSAR is directly dependent on the software requirements. Several configurations can be made depending on the number of users who need to access LSAR data. With multiple users sharing data, it is recommended that a LAN-based LSAR system be installed. However, if the need is for a single user only, refer to Table 7-4 for a guideline of the equipment required.

I1.3.4  Software Requirements for Processing Digital Data
The software requirements for processing digital data will be dependent on how the digital data is received: on magnetic, via LAN/WAN or modem, or by other data transfer means. All of these options will carry with them specific software needs and operating system requirements. The project manager should procure systems that are compatible with not only end user output requirements but also with both known and possible future digital data sources.

I1.3.5  Software Requirements for Processing TMs
The typical TM creation process consists of authoring, reviewing, updating, and inspecting the technical manual or publication. Each program can accomplish these tasks by various methods.
The first decision of the project manager is whether the TM will be an illustrated text data file technical manual or an IETM. This decision, along with the data use and the data format, will determine the specific infrastructure individuals involved will require in the creation, management, and use of a TM.

I1.3.5.1  Software Requirements for Creating SGML Format TMs
The preliminary TM may be authored in a variety of software programs. Commercial word processing software, desktop publishing software, or an SGML editor all have ability to author technical documents with imbedded tables and figures. Therefore, the project manager must ensure that the TM reviewers have software compatible with the contractor's TM-authoring software unless the contractor is providing the viewing and commenting/annotating capabilities through a CITIS. The TM reviewer must be able to view and annotate the TM file rather than edit the existing file. Once the preliminary version is complete, commercial software is available to convert a word processing or desktop publishing document into a MIL-M-28001 SGML format file.

These programs try to add all the appropriate tags to the SGML text file. If the preliminary TM is in SGML format, several options exist to allow users to view and annotate the manual. Low-cost SGML document editors are available for PCS and UNIX workstations. PDL viewers and annotator translators can be purchased to convert the entire SGML file into raster format, word processing file formats, and desktop publishing file formats. Network software licensing and data translators can minimize the cost of procuring the required software products. Since most users involved in the review of a TM will not need an SGML editor all the time, a single network license may provide five to ten users access to the software. As a final option, translators can also be purchased to convert the document format into a format compatible with their existing software. Data files can be translated among SGML and raster format, word processing file formats, and desktop publishing file formats.

I1.3.5.2  Software Requirements for Creating IETMs
The preliminary IETM may be developed in a commercial word processing software or SGML editor. Once the preliminary version is complete, the data must be converted such that a Hypertext system can retrieve the data and display the information requested. IETMs should be developed on systems that are capable of executing complex graphical user interface processes immediately.

I1.3.5.3  Software Requirements for Managing TMs
Once the final reproducible copy of the TM is accepted, the cognizant life-cycle maintenance activity is responsible for the configuration management of the document. To properly implement configuration management, the following software packages should be available to the configuration manager.

· SGML editor
· DTD editor
· Illustrator editor for vector and raster
· Configuration management database

I1.3.5.4  Software Requirements for Using TMs
The software requirements for using TMs are based on the user's receiving electronic data containing the TM and having the needed software to utilize the TM. Depending on the format that the TM was delivered in, the end user could require any part of the following software to utilize the TM.

· SGML parser
· illustrator editor for vector and raster
· Database query application

I1.3.6  Software Requirements for Processing TDPs
The first decision that affects the software requirements is whether the final engineering drawings will be stored in the native CAD files or an equivalent vector format versus raster. Raster data does not allow the ability to utilize the data for engineering analysis; thus, the processing requirement to work with only raster data can be significantly less than with processable vector format, such as IGES or VHDL.

I1.3.6.1  Software Requirements for Creating TDPs
The software requirements for creating TDPs can be in several formats. The specific format used depends on the type of data being generated and the way the data will be managed throughout its life-cycle. The following formats may be used:

· Native CAD
· CAD2
· IGES view
· FEM (VHDL simulation)

I1.3.6.2  Software Requirements for Managing TDPs
Managing the TDP after its distribution to the field forces will entail all of the same software requirements needed during its creation. The following list of software applications may be required to meet these needs:

· CAD2
· Fluid flow analysis
· PWB layout
· SPICE simulator
· VHDL simulator
· PLD software
· Hybrid/Application Specific Integrated Circuit (ASIC) software
· Configuration management
· Relational database

I1.3.6.3  Software Requirements for Using TDPs
The requirements for using TDPs are limited by the fact that users will not edit or change the content of the TDP. Therefore, only the software necessary to view and print the TDP data will be required. This will then depend on the type of TDP being used and the formats in which it was distributed. The manager will have to determine what TDP formats are likely to be encountered and develop a system appropriate to the end users' requirements. This will include all or part, but not limited to, the following programs:

· GES translators
· Configuration management
· Relational database
· CAD2 - PWB layout

I1.3.7  Telecommunications Requirements for Processing Digital Data
The telecommunications requirements for processing digital data have been briefly discussed in Paragraph 7.3. These requirements should be based on how data is to be shared or manipulated and what current telecommunications infrastructure is available. Specifically, the project manager should determine the average number and size of data transfers to determine the type and size of the communication systems needed. Considerations are the number of modems or outside lines being supported, baud rate of the modem, error detection/correction performance, and compatibility to data sources. Will the telecommunications system be installed using standard, conditioned, trunk, or uninterruptible lines, or will fiber optics be used, if available? Once the data is coming into the facility, how and where will it be stored, and will other outside sources be allowed access? All these factors need to be given careful consideration. The initial decisions will affect the current operation and future expansion of the system.