|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
10.6 DATA FORMATS AND DELIVERY STANDARDS10.6.1 Contract Data Requirements Lists10.6.2 Classified Data10.6.3 Data Encryption10.6.4 Digital Signatures10.6.5 Digital Data Delivery10.6.6 Electronic Data Interchange (EDI)10.6 DATA FORMATS AND DELIVERY STANDARDS10.6.1 Contract Data Requirements ListsSpecific data requirements, formats, and delivery modes will have to be specified for each project on one or more Contract Data Requirements Lists (CDRLs). Generic guidelines for multi-national projects have been prepared by AC/313 (Committee on Acquisition Practices) and this subject is being considered in detail in the NCMB/NICG-sponsored Acquisition Workshop (1994-1996)
10.6.2 Classified DataClassified data will be safeguarded in accordance with the NATO Regulations appropriate to each Project. [ C-M (55)15(FINAL) ]. 10.6.3 Data EncryptionIn the past, data encryption needs could only be met, legally, through the use of Government-approved encryption methods. More recently, however, commercial encryption methods have been developed and are now in use within NATO although the approval for such activity has not yet been confirmed as being generally applicable.
10.6.4 Digital SignaturesDigital signatures may be specified in accordance with Electronic Data Interchange agreements which form part of the contractual negotiations on a project. Although this subject is still in its infancy, guidelines are under development by AC/313 together with suitable sample clauses for use in Electronic Data Interchange agreements. The following standards currently apply.
10.6.5 Digital Data DeliveryData will be acquired in digital form unless specific operational reasons dictate otherwise.
In general it should be noted that, in principle, CALS products should be software and hardware independent. Any departure from this principle must take into account the eventual use of the data so acquired and management should consider not only Project Office requirements but also the needs of the users during the whole of the life-cycle, so far as these may be ascertained. 10.51. Electronic Data Interchange (EDI)Data Exchange should be specified by electronic means unless operational requirements have determined that such means are inappropriate or not cost-effective.
Note: An EDIFACT-compliant version of AECMA Specification 2000M was issued in DRAFT in late-1995 and will be formally issued in 1996.. Whereas X.12 is the current Requirement of US CALS DoD, it should also be noted that MIL-HDBK-59B and MIL-STD-974(CITIS) explicitly reference FIPS 161-1 EDIFACT for CALS applications and ANSI have submitted appropriate change requests to facilitate migration to EDIFACT . UN/ECE EDIFACT is expected to be adopted as the NATO standard in the near future. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||