a. General. The ADMP is prescribed in Army Directive 2009–03. For more information on the ADMP, see DA Pam 25–1–1.
b. Army data standards management.
(1) Data standards. Data standards (specified in the DISR and other guidance documents and their associated authoritative data sources (ADSs), IESS, unique identifiers (UIDs), eXtensible markup language (XML), resource description framework (RDF), RDF vocabulary description language, RDF schema, and RDF schema derivatives) will be used to guide all data exchanges ENTERPRISE-EMAIL, including those needed to support legacy systems. DM requirements will be included in IT planning documents.
(2) Army organizations. All Army organizations producing or using data standards (such as ADS, IESS, UID, and XML) will ensure that—
(a) Only Army-approved data standards are used in systems.
(b) New data standards are registered in the appropriate part of the Data Performance Plan System (DPPS) as needed.
(c) Input is provided to Army data standards reviews.
(d) Data standards used for information exchanges are identified during Army and Joint interoperability certification processes.
(e) Only organizations identified by the data stewards as data standards producers will create or update DPPS content exchanged with or disseminated to any other organization.
(f) Valid implementation of data standards Armywide. Functional data managers will manage ADSs, IESS, UIDs, and XML.
(g) Their data is categorized as public, public restricted, or private. DOD requires protection requirements and accessibility requirements based upon the type of data. Public data that must be accessible from outside the .mil domain must reside in a DOD-approved shared space. Public data cannot be mixed or stored with public restricted or private data. Public restricted data must use some access-control method to restrict access to the data. Examples are CAC or user ID and password. Private data cannot be accessed outside the .mil domain. Private data must be separate from public and public restricted data in accordance with DOD policy, directives, and Chief Technology Offices.
(3) Army data quality management. All Army organizations producing or maintaining enterprise data must incorpo-rate a comprehensive data quality management process (DQMP) as part of their data production and maintenance activities. For more information on DQMP, see https://www.milsuite.mil/wiki/Data_Product_Catalog. The DQMP comprises the policies and procedures for selecting and implementing data-quality standards. These ensure that Army information products achieve and maintain the necessary level of data quality necessary to support all Army enterprise-wide operations and processes. All organizations producing or maintaining enterprise data will—
(a) Create an environment and support the infrastructure needs to facilitate the exchange of lessons learned and best practices, so that all information products are brought to specified data-quality levels, regardless of operational environment.
(b) Ensure that data-quality management procedures are adopted and applied to the Army data assets under their control.
(c) Ensure that information products are objectively assessed by the DQMP for conformance to the necessary quality levels.
b. Army data standards management.
(1) Data standards. Data standards (specified in the DISR and other guidance documents and their associated authoritative data sources (ADSs), IESS, unique identifiers (UIDs), eXtensible markup language (XML), resource description framework (RDF), RDF vocabulary description language, RDF schema, and RDF schema derivatives) will be used to guide all data exchanges ENTERPRISE-EMAIL, including those needed to support legacy systems. DM requirements will be included in IT planning documents.
(2) Army organizations. All Army organizations producing or using data standards (such as ADS, IESS, UID, and XML) will ensure that—
(a) Only Army-approved data standards are used in systems.
(b) New data standards are registered in the appropriate part of the Data Performance Plan System (DPPS) as needed.
(c) Input is provided to Army data standards reviews.
(d) Data standards used for information exchanges are identified during Army and Joint interoperability certification processes.
(e) Only organizations identified by the data stewards as data standards producers will create or update DPPS content exchanged with or disseminated to any other organization.
(f) Valid implementation of data standards Armywide. Functional data managers will manage ADSs, IESS, UIDs, and XML.
(g) Their data is categorized as public, public restricted, or private. DOD requires protection requirements and accessibility requirements based upon the type of data. Public data that must be accessible from outside the .mil domain must reside in a DOD-approved shared space. Public data cannot be mixed or stored with public restricted or private data. Public restricted data must use some access-control method to restrict access to the data. Examples are CAC or user ID and password. Private data cannot be accessed outside the .mil domain. Private data must be separate from public and public restricted data in accordance with DOD policy, directives, and Chief Technology Offices.
(3) Army data quality management. All Army organizations producing or maintaining enterprise data must incorpo-rate a comprehensive data quality management process (DQMP) as part of their data production and maintenance activities. For more information on DQMP, see https://www.milsuite.mil/wiki/Data_Product_Catalog. The DQMP comprises the policies and procedures for selecting and implementing data-quality standards. These ensure that Army information products achieve and maintain the necessary level of data quality necessary to support all Army enterprise-wide operations and processes. All organizations producing or maintaining enterprise data will—
(a) Create an environment and support the infrastructure needs to facilitate the exchange of lessons learned and best practices, so that all information products are brought to specified data-quality levels, regardless of operational environment.
(b) Ensure that data-quality management procedures are adopted and applied to the Army data assets under their control.
(c) Ensure that information products are objectively assessed by the DQMP for conformance to the necessary quality levels.
No comments:
Post a Comment