ASTM E2675-22 PDF

SIGNIFICANCE AND USE 4.1 This practice establishes expected outcomes associated with an asset management system. 4.2 Understand the difference between performance standards and design standards—these are primarily performance statements versus design statements. What is being measured is achievement, not process. 4.3 This practice encourages an inclusive understanding and communication of the outcomes associated with an asset management system. As additional standards are added, comparisons on this basis to other asset management systems can be further enabled. 4.4 This practice, in combination with Practice E2279, should provide an enhanced basis for making decisions surrounding both assets and asset management systems. 4.5 This practice is intended to foster and enable additional standard practices related to or based on the terms and concepts in the outcomes and outcome components. In particular, this practice may suggest a standard for personal and management skills useful in efforts to achieve these outcomes. 4.6 This practice is to evaluate how robust the asset management system is, and guide future corrections and improvements. SCOPE 1.1 This practice describes expected outcomes associated with an asset management system. It is a measure of achievement rather than process and is performance oriented rather than design oriented. 1.2 Outcomes are defined as information, events, objects, or states of being produced as a result or consequence of an objective, plan, process, accident, effort, or other similar action or occurrence and can be expressed in a quantitative or qualitative manner. 1.3 An output measure is the tabulation, calculation, or recording of activity or effort and can be expressed in a quantitative or qualitative manner. For example, an output is driving 100 mph; an outcome is arriving safely. 1.4 An outcome measure is an assessment of the results of a program activity compared to its intended purpose. This practice assumes that inputs are correlated to known or declared outputs of the system or system component being assessed. 1.5 Consistent with Practice E2452 (EMPM), these outcomes are grouped into process management outcomes and operational outcomes. 1.5.1 Although they may be directly related, strategies and tactics should not be confused with outcomes. Strategies are long-term plans of action designed to achieve a particular goal. Tactics are maneuvers or actions calculated to achieve some end. For example, increasing exercise is a strategy to attain the goal or outcome of fitness. Running is a supporting tactic to achieve the goal or outcome of fitness. Other tactics or groups of tactics may achieve the same outcome. On the other hand, as the definition of outcome indicates, tactics are not required for attaining outcomes. For example, fitness may be an unplanned result of a job requiring physical exertion. 1.6 This practice describes the outcomes at a high level, with limited discussion of each outcome or components of each outcome. The intent is to provide a framework for current and potential additional standards. A cross reference relating current standards to the outcomes is provided in Section 5. 1.7 The outcomes further described in Section 5 are listed in the following: 1.7.1 Process Management Outcomes: 1.7.1.1 Outcome 1—Mission Support 1.7.1.2 Outcome 2—Accounting and Accountability 1.7.1.3 Outcome 3—Information Management 1.7.1.4 Outcome 4—Planning 1.7.1.5 Outcome 5—Relationships 1.7.2 Operational Outcomes: 1.7.2.1 Outcome 6—Asset Functionality for Intended Purpose 1.7.2.2 Outcome 7—Resource Optimization 1.7.2.3 Outcome 8—Asset Visibility 1.7.2.4 Outcome 9—Safety and Security 1.7.2.5 Outcome 10—Installation, Movement, and Storage 1.8 In Section 5, a rating scale is provided to quantify in a uniform manner achievement of outcomes and outcome components. 1.9 This practice, in combination with Practice E2279,...