1、Beneficial comments (recommendations, additions, deletions) and any pertinent data which maybe of use in improving this document should be addressed to: Commander, U.S. Army Aviationand Missile Command, ATTN: AMSAM-RD-SE-TD-ST, Redstone Arsenal, AL 35898-5000,by using the Standardization Document Im
2、provement Proposal (DD Form 1426) appearing at theend of this document or by letter.AMSC N/A FSC 5963DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.NOTMEASUREMENTSENSITIVEMIL-PRF-32029(MI)30 June 1998PERFORMANCE SPECIFICATIONAutomated Configuration Management System
3、 (ACMS)This specification is approved for use by the Department of the Army and is available foruse by all Departments and Agencies of the Department of Defense.1. SCOPE1.1 Scope. This specification covers performance requirements for the U.S. ArmysAutomated Configuration Management System (ACMS). I
4、t defines the functional requirementsfor ACMS, interface characteristics, and the environment in which it must operate.1.2 ACMS overview1.2.1 ACMS purpose. The ACMS will provide the Army with a next-generationconfiguration management and product data management system. It will enable greater access
5、toand sharing of enterprise product data1 in support of Integrated Product Teams (IPTs);engineering change action processing; and reprocurement, operations, maintenance, and disposalactivities. The primary enhancements ACMS will provide include the following:a. Storage and use. ACMS will extend the
6、data types stored and managed, for exampleengineering models, simulations, and other forms of intelligent product data.b. Rapid retrieval. ACMS will enhance the users ability to rapidly find, retrieve, andcontrol access to product data._1 This performance specification uses the term “product data” t
7、o refer to all documents and metadata related to a productsrequirements, design, implementation, and support. The term “document” has the same meaning as that used in MIL-STD-2549: A self-contained body of information or data which can be packaged for delivery on a single medium. Examples ofdocument
8、s include drawings, reports, standards, databases, application software, and engineering designs. “Metadata” areelements of information that describe data, such as document identifier, date, owner, release level, format, keywords, datalocation, approval authorizations, part identifier, and part name
9、.Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-PRF-32029(MI)2c. Process automation. ACMS will support automation of business processes such asbaseline and release approval, engineering change processing, Technical Data Package(TDP) validation,
10、and integrated product development as supported by IPTs.d. Year 2000 compliant. ACMS will provide the Army with a Year 2000 compliantconfiguration and product data management capability.1.2.2 ACMS scope. ACMS will be the Armys enterprise configuration management andproduct data management system. Th
11、e capabilities of ACMS will support traditionalconfiguration management functions; product structure management; product data management;the assembly, review, validation, update, and dissemination of TDPs; and interfaces with the JointComputer-aided Acquisition and Logistic Support (JCALS) Workflow
12、Manager and multiplerepository systems such as the Joint Engineering Data Management Information and ControlSystem (JEDMICS) and Contractor Integrated Technical Information Service (CITIS) systems.ACMS will enable management of the Armys product data throughout the system life cycle -from program de
13、velopment through production, sustainment, modification, and, ultimately,disposal.1.2.3 ACMS vision. ACMS will provide the required data when it is needed and in aform that the user can apply to accomplish the mission. The required data consists of all theproduct data necessary to completely define
14、an item for the intended purpose of specifying,designing, analyzing, manufacturing, maintaining, sustaining, testing, inspecting, packaging, anddispositioning that item over its entire life span. The ACMS also must operate in a diverse Armyenvironment, integrate with other Army major subordinate com
15、mand (MSC) business processes,and communicate with other MSC, government, and industry information management systems.1.2.4 ACMS users, support agencies, and implementing sites. The Army MaterielCommand (AMC) Engineering Data Management System (EDMS) Functional CoordinatingGroup (FCG) ACMS Task Forc
16、e, as established by the AMC Deputy Chief of Staff for Research,Development and Acquisition, is responsible for defining ACMS and developing this performancespecification, which describes the target ACMS.The EDMS Program Management Office will monitor implementations and recorddifferences. Potential
17、 implementation sites include all MSCs and their installations.The ACMS user community includes, but is not limited to, program managers,configuration managers, design engineers, developers, testers, trainers, logisticians, materielmanagers, packaging specialists, and manufacturers to include organi
18、c depots and arsenals.Potentially, anyone involved in an IPT, evaluating engineering change actions, or retrievingproduct data for any reason, is an ACMS user. These users may be located at the MSCs; theResearch, Development and Engineering Centers (RDECs); the depots and arsenals; the DefenseLogist
19、ics Agency (DLA) sites; and at Army product developer sites.1.2.5 ACMS operation. ACMS will be a federated system of systems. It will befederated in the sense that local sites will manage their own data and support their site uniquebusiness processes. It is a system of systems in the sense that all
20、sites will share metadata (seeAppendix D - Glossary) that describe the managed product data and will possess capabilities thatare common to the whole of ACMS.Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-PRF-32029(MI)3As the Armys enterprise pr
21、oduct data management system, ACMS will provide visibilityinto the identity and location of all controlled product data, to include configuration managementdata, whether the Army has change control authority or not.ACMS represents a shift in the Army from document-centric data management toproduct-c
22、entric data management. Users will locate and retrieve data from a product structureperspective rather than from a document perspective. This change will enable users to identifydesired product data by navigating product structures, searching for and through part families, aswell as by traditional a
23、pproaches such as querying data grouping or classification attributes.Product-centric data management also means that the product structure is a controlled item inaddition to, or in place of, documents describing the product structure (for example, the Bill ofMaterials).The target ACMS will provide
24、a common set of Army-wide capabilities to include thefollowing:a. Provide a single access and control point. ACMS will provide users with a single,common means of finding, accessing and controlling Army enterprise-level productdata for which the Army has change control authority.b. Promote sharing o
25、f data. ACMS will provide users with concurrent access to productdata where the data and the users may be geographically dispersed.c. Implement data standards. ACMS will read and write MIL-STD-2549 datainformation packets as a means for exchanging product configuration managementmetadata, product st
26、ructure relationships, and documents with Product DataManagement (PDM), Configuration Management (CM), authoring, CITIS, andrepository systems.d. Manage multiple formats. ACMS will provide for the management of a wide varietyof product data formats in accordance with international and industry stand
27、ards, toinclude Computer Aided Design (CAD) model formats, so that government- andcontractor-created data can be maintained, located, and used with no loss of dataintelligence.e. Automate product data management. ACMS will automate Army product datamanagement functions to include data capture, stora
28、ge, location, retrieval, accesscontrol, and transmittal, as well as configuration management of data, quality controlof data, and system administration.f. Manage Army-controlled product structures. ACMS will provide for creating,storing, maintaining, and managing changes to links (relationships) bet
29、ween elementsof product structures (for example, parts, components, and assemblies) for which theArmy is the Current Document Change Authority (CDCA).g. Access contractor-controlled product structures and product data. ACMS willprovide the ability to find, copy, view, and print product structures an
30、d product datawhen the Army is not the CDCA.h. Associate product structure elements with appropriate product data. ACMS willprovide for creating, storing, and controlling the associations between productProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,
31、-MIL-PRF-32029(MI)4structure elements and the product data that describe those elements for which theArmy is the CDCA. ACMS will provide the ability to find, copy, view, and print theassociations for which the Army is not the CDCA.i. Manage workflow. ACMS will provide for work process definition, ro
32、uting, statustracking, and performance analyses of modeled processes.j. Provide configuring capabilities. ACMS will be flexible and customizable in its abilityto meet the unique information needs of individual MSCs. ACMS will provide systemadministrator-level tools for configuring ACMS to support in
33、formation interchangewithin an Army site in accordance with each sites business processes and product dataneeds, while providing information to off-site users. These tools will permitconfiguring the system without writing source code or recompiling unaffectedsoftware modules.k. Provide customization
34、 and integration capabilities. ACMS will be flexible andcustomizable in its ability to meet the unique functional needs of individual MSCs andto interact with other data management systems. ACMS will provide customizationand integration tools for tailoring ACMS to extend existing functionality, add
35、newfunctions, provide new methods for interacting with users, and interface with otherdata management systems, data authoring systems, and viewing systems.Specific applications of ACMS are discussed further in the appendices. Appendix A,ACMS Concept Overview, provides information relative to the nat
36、ure and roles of the ACMS.Appendix B, ACMS Support of Army Products and Data Life Cycles, and Appendix C, ACMSSupport to Selected Business Processes, provide information relative to the use of the ACMS.2. APPLICABLE DOCUMENTS2.1 General. The documents listed in this section are specified in Sections
37、 3 and 4 of thisspecification. This section does not include documents cited in other sections of this specificationor recommended for additional information or as examples. While every effort has been made toensure the completeness of this list, document users are cautioned that they must meet alls
38、pecified requirements documents cited in Sections 3 and 4 of this specification, whether or notthey are listed.2.2 Government documents2.2.1 Specifications, standards, and handbooks. The following specifications, standards,and handbooks form a part of this document to the extent specified herein. Un
39、less otherwisespecified, the issues of these documents are those listed in the issue of the Department of DefenseIndex of Specifications and Standards (DoDISS) and supplement there to, cited in the solicitation(see 6.2).DEPARTMENT OF DEFENSE STANDARDSMIL-STD-2549 - Configuration Management Data Inte
40、rfaceDEPARTMENT OF DEFENSE HANDBOOKSMIL-HDBK-881 - Work Breakdown StructuresProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-PRF-32029(MI)5(Unless otherwise indicated, copies of the above specifications, standards, and handbooksare available from
41、the Standardization Document Order Desk, 700 Robbins Avenue, Building 4D,Philadelphia, PA 19111-5094.)2.3 Order of precedence. In the event of a conflict between the text of this document andthe references cited herein, the text of this document takes precedence. Nothing in this document,however, su
42、persedes applicable laws and regulations unless a specific exemption has beenobtained.3. REQUIREMENTS3.1 Operating requirements. This section describes the functional features of the ACMSas seen from a users point of view. It communicates an ACMS in terms of the user needs it willfulfill, its relati
43、onship to existing systems or procedures, and the ways it will be used. A strategyfor tailoring the following requirements to meet Army interoperability and unique environmentalconstraints and performance requirements is given in section 6.2.4.3.1.1 Product data management requirements3.1.1.1 Produc
44、t data control requirements3.1.1.1.1 Data storage requirements3.1.1.1.1.1 Provide secure data storage. ACMS shall provide for secure storage ofproduct data (see Appendix D) in accordance with defined access control permissions and rules(see Access Control Requirements and User Authorization and Mana
45、gement Requirements).Secure storage is defined as the ability to preclude stored information from being viewed, reused,updated, or deleted without invoking system rules.3.1.1.1.1.2 Store product data. ACMS shall provide the ability to store both CM andnon-CM controlled product data in a single and d
46、istributed vault.3.1.1.1.1.3 Store CM-controlled product data. ACMS shall store configurationcontrolled product data in a vault that does not allow the user to overwrite data.3.1.1.1.1.4 Store non-CM controlled product data. ACMS shall allow the user to choosewhether to store non-configuration contr
47、olled product data in a vault that does not overwrite dataor in a vault that does overwrite data.3.1.1.1.2 Access control requirements3.1.1.1.2.1 Check identity and authorizations. ACMS shall provide for checking theidentity and authorizations of users and restrict access as defined by access contro
48、l permissionsand rules (see User Authorization and Management Requirements).3.1.1.1.2.2 Suppress unauthorized functions. ACMS shall suppress functions notavailable to a user due to access restrictions. For example, an administrative menu tree may beaccessible (that is, highlighted and active) only t
49、o users with administrator permission or theability to modify a workflow may be suppressed for users who are not authorized to modifyworkflows.3.1.1.1.2.3 Provide user feedback. ACMS shall provide a message box that notifies auser that the user has been denied access to controlled product data or to restricted functions.Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-PRF-32029(MI)6
