|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The NCoO must provide potential bidders an understanding of specific customer needs for technical information throughout all relevant life-cycle activities of the defence system. The NCoO must be thoroughly developed for potential bidders to respond with a proper CAC. Therefore, the acquisition of technical data by the Programme Manager requires a detailed definition of data requirements. The effective definition of these technical data requirements necessitates the complete identification of data needs and uses. A flow chart of the entire process is shown in figure 1-2.
Data type deliverables are the data requirements specified on the Contract Data Requirements List (CDRL) for a typical program categorized by program function and type. A survey of supporting defence system activities during the requirements determination process will establish data requirements. Sample data types to be digitally developed, accessed and/or delivered, and maintained are listed in table 1-1. Note that this table is not intended to be all inclusive, nor are all deliverables listed required for all projects; the list of deliverables must be tailored to the project requirements. TABLE 1-1 Typical Data Type Deliverables
The data deliverables should be categorized by discipline, functional activity, type, or other such groupings to facilitate a standardized approach to applying the CALS digital data standards and specifications. The data users, as shown in figure 1-2, are the functional organizations that will require access to the program data. These organizational areas typically include: acquisition, engineering/design, supply, training, manufacturing, and maintenance. In addition to their functional responsibilities, these organizations are defined by their location and the specific disciplines involved and may be different from nation to nation. The data use requirements are the ways in which the chosen data types may be considered for processing. The project manager will need to identify the use of the data types by the support organizations chosen for the program. The five defined methods of data processing typical of most defence systems are described below.
The availability of digital data processing and telecommunications technology and approved standards for creation, storage, 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 of defence agencies must be assessed with respect to program needs and schedules. The NCoO is an excellent vehicle for making these determinations. Project managers should plan to access or acquire digital data products rather than hard copy unless a clear case can be made that the costs will outweigh the life-cycle benefits. The data user infrastructure is the computing environment available to a particular user. This environment establishes the data processing capabilities of that user. The following areas identify a user's infrastructure:
TABLE 1-2
Following are types of digital deliverables supported by delivery and access methods specified by project managers. Composed Products: Human interpretable documents in digital image format. These items cannot be further processed since they are complete, published entities. Examples of data products that could be delivered or accessed in this format include legacy engineering drawings, technical reports, and test plans. Processable Data Files: Machine readable dynamic information that includes revisable source data for multiple data applications, thus enabling standard and custom documents to be generated and the source data to be manipulated. Examples of processable files are LSAR files, files extracted as subsets of computer-aided design files, and technical manual text files delivered in Standard Generalized Markup Language (SGML) format. The following data formats are the forms in which each of the types of data deliverables can be procured. Refer to figure 1-2 for their relationships to the type of data deliverable.
In order to ensure the proper sharing and exchanging of information across dissimilar systems, the project manager should consider the possible loss of intelligence when translating information from one data format to another (whether the format is standard or not). The following types of interchange standards are used with data formats:
The two options that an project manager may use to support digital delivery requirements are physical delivery and on-line delivery via telecommunications. Digital delivery and access requirements are specified through the SOW, the CDRL, and specific Data Item Descriptions (DID). Magnetic tape is a mature, stable technology that is able to handle the large volumes of data typically associated with a major defence system acquisition. Magnetic tape standards are well defined, and little additional investment cost will be involved. However, other media may be more efficient and, therefore, preferred. Magnetic disk is also widely implemented on personal computers and work stations and may be the physical medium of choice for small business contractors. Several primary de facto magnetic disk formats are available but no official standard has been accepted. Compatibility problems exist, but can be overcome with only moderate effort. Optical media is used here as a generic term to include Compact Disk-Read Only Memory (CD-ROM), Compact Disk Interactive (CDI) and Digital Video Interactive (DVI), Write Once and Read Many Times (WORM), and erasable optical disk. These media are ideal for mass distribution and archival purposes for large volumes of data. On-line delivery may be achieved via two methods:
On-line access, as distinguished from on-line delivery, refers to the situation in which an organization accesses data items through CITIS services, or other similar information management services, as negotiated in the contract. Secure, on-line transmission of the full volume of data for defence systems is technically feasible but severely taxes current telecommunication networks. In the near term, telecommunications may be limited to electronic mail exchange of high-priority technical data, the use of mutually agreed EDI transactions, or other clearly defined uses such as CITIS access. On-line interactive access provides immediate and timely data access for custom report generation, document generation, and on-line request of information transmitted as composed products and processable data files. Project managers should give preference to use of CITIS for performing the functions of updating, storing, controlling, reproducing, and distributing data items. As an interim standard, MIL-STD-974 provides information concerning core and tailorable CITIS functions which should be specified in the SOW and listed as contract line items. In the long term, cost effectiveness will be essential for successful implementation of a totally integrated defence system database. Upon completion of the NCoO, the logistics manager responsible for technical data will be prepared to enter the solicitation and source selection process with a firm CALS implementation strategy and knowledge of the needs and capabilities for acquiring and using digital data |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||