|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 7-4 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 7-4 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 7-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 at a later time. 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 which will support an IETM.
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, modelling and simulation are best suited for 3-D vector data. The hardware requirements differ among the disciplines of engineering required to be processed. There are some basic commercial IGES drawing packages that 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:
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.
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.
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 be needing 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.
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 without delay.
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.
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.
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.
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:
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:
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:
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 uninterruptable lines, or will fibre 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. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||