|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
10.7 INFORMATION MANAGEMENT10.7.1 Electronic Data Interchange Agreement10.7.2 Data Dictionary10.7.3 Integrated Product Database10.7.4 Database Query Language10.7.5 Contractor Integrated Technical Information Service (CITIS)10.7.6 Automated Interchange of Information10.7.7 Technical Data Packages10.7.8 Database Manager10.7 INFORMATION MANAGEMENT10.7.1 Electronic Data Interchange AgreementAn Electronic Data Interchange Agreement records the understanding between two or more parties in a joint project or acquisition programme as to the type and level of services to be provided for the transfer of data.
Notes: See Note to Sect 10.3.2 AECMA 2000M Chapter 4 contains an outline Data Interchange Agreement. AC/313 has published a draft NATO Data Interchange Agreement and this has been used as the basis for Section 8 of this Handbook. 10.7.2 Data DictionaryThe NATO CALS Office is compiling a standard data dictionary to support logistics information processing. Whilst there is no definitive standard for a data dictionary, a number of supporting standards exist:
Note: The International Standards Community, as a joint ISO, UN/ECE, and ISO/IEC activity, is currently engaged in the development of a Basic Semantic Repository (BSR). The BSR is a tool to aid in the rationalisation and alignment of existing data dictionaries in line with international standards and to enable future alignment of internal data and external communication requirements. The NATO CALS Office is monitoring the work of the BSR and may adopt the BSR principles as an aid to the development of a NATA Data Dictionary. The representation of the Data Elements in the NATO Data Dictionary will be in accordance with ISO 11179. 10.7.3 Integrated Product DatabaseThe use of a single coherent set of CALS standards, the acquisition of data in digital form, and the exchange of data electronically does not, in itself, fully exploit the advantages of CALS. To obtain added value, all project data should be stored on a single database organised in such a way that all authorised used can have optimum access. Such a database, which may be physically distributed between several locations, should permit data to be created once and used many times. The creation of the Integrated Product Data Base should use the standards defined above under Data Dictionary. 10.7.4 Database Query LanguageSQL is based on a relational database model. It is used to define data in relational databases within a data dictionary component of SQL and to manipulate data.
Note: So far as we are aware, NATO has not yet adopted any International Standard for use within NATO as a Standard Query Language. 10.7.4.1 SQL Conformance TestingFormal SQL conformance testing is available through the US National Institute of Standards and Technology (NIST) which instituted a test service in 1990. Version 4.0 of the NIST SQL test suite, which is designed to test the required features of the new planned US Federal Information Processing Standard (FIPS) PUB 127-2 based on SQL Version 2 is expected in the near future. NIST publishes a quarterly list of FIPS-validated processors, but requiring compliance with the NIST conformance test procedure may well limit choice to US products. The Policy and applicable standards for NATO have not yet been confirmed or validated in the NATO CALS context. 10.58. Contractor Integrated Technical Information Service (CITIS)CITIS is intended to be an efficient, contractually implementable means for providing Purchasers with on-line access to, and exchange of, Contractor-generated and maintained data specified in a Contract Data Requirements List (CDRL).
The initial US concept described in MIL-STD-974 specified requirements within a US legal framework; such a framework does not necessarily exist outside the US. Intellectual Property Rights and other legal issues may inhibit the implementation of a CITIS approach within NATO unless clear contractual agreements can be reached within each project, and therefore it has not yet been possible to determine the NATO Policy towards CITIS or to define a standards for its implementation. Section 5 of this Handbook addresses the use of CITIS. 10.7.6 Automated Interchange of InformationMIL-STD-1840 defines the procedures for handling several forms of document transmittal and for the transmittal of product data that does not consist of documents. However, it prescribes that the primary and only required form is that of SGML encoded text with graphics in separate (linked)files.
Note: The Policy and applicable standards for Automated Interchange of Information for NATO, and the status of the above Standards has not yet been confirmed or validated in the NATO CALS context. Although there are legacy systems based on this US DoD Military Standard in use within NATO, it should be noted that this Standard may not reflect NATO CALS requirements. 10.7.7 Technical Data PackagesTechnical Data Packages (TDPs) contain the information necessary to describe a defence system and its componenets in terms of design, engineering, manufacturing, and logistics support. The application of CALS principles to the creation, management, and use of TDPs is addressed in Section 3 of this Handbook.
Note: The Policy and applicable standards for Technical Data Packages for NATO, and the status of the above Standard has not yet been confirmed or validated in the NATO CALS context; it should be noted that the above US DoD Military Standard may not yet reflect CALS requirements. 10.7.8 Database ManagerTo facilitate such database development, a database manager with a clear understanding of CALS principles, should be appointed for each project. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||