《BS-ISO-13374-2-2007.pdf》由会员分享，可在线阅读，更多相关《BS-ISO-13374-2-2007.pdf（42页珍藏版）》请在三一文库上搜索。
1、BRITISH STANDARD BS ISO 13374-2:2007 Condition monitoring and diagnostics of machines Data processing, communication and presentation Part 2: Data processing ICS 17.160; 35.240.99 ? Licensed Copy: London South Bank University, London South Bank University, Wed Oct 17 01:13:35 GMT+00:00 2007, Uncontr
2、olled Copy, (c) BSI BS ISO 13374-2:2007 This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 October 2007 BSI 2007 ISBN 978 0 580 55407 0 National foreword This British Standard is the UK implementation of ISO 13374-2:2007. The UK participation
3、 in its preparation was entrusted by Technical Committee GME/21, Mechanical vibration, shock and condition monitoring, to Subcommittee GME/21/7, Condition monitoring. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport
4、to include all the necessary provisions of a contract. Users are responsible for its correct application. Compliance with a British Standard cannot confer immunity from legal obligations. Amendments issued since publication Amd. No. DateComments Licensed Copy: London South Bank University, London So
5、uth Bank University, Wed Oct 17 01:13:35 GMT+00:00 2007, Uncontrolled Copy, (c) BSI Reference number ISO 13374-2:2007(E) INTERNATIONAL STANDARD ISO 13374-2 First edition 2007-07-15 Condition monitoring and diagnostics of machines Data processing, communication and presentation Part 2: Data processin
6、g Surveillance et diagnostic dtat des machines Traitement, change et prsentation des donnes Partie 2: Traitement des donnes BS ISO 13374-2:2007 Licensed Copy: London South Bank University, London South Bank University, Wed Oct 17 01:13:35 GMT+00:00 2007, Uncontrolled Copy, (c) BSI ii Licensed Copy:
7、London South Bank University, London South Bank University, Wed Oct 17 01:13:35 GMT+00:00 2007, Uncontrolled Copy, (c) BSI iii Contents Page Foreword iv Introduction v 1 Scope . 1 2 Normative references. 1 3 CM time-order/time-reference data, normally referenced with UTC and local time zone; data qu
8、ality indicator (e.g. “bad”, “good”, “unknown”, “under review”, etc.). Examples of digitized data include: floating point values for scalar data; magnitude and time series for dynamic data; thermal radiation data with digitized image for thermographic data; sample test results for lubricating fluid/
9、air/water sample data. BS ISO 13374-2:2007 Licensed Copy: London South Bank University, London South Bank University, Wed Oct 17 01:13:35 GMT+00:00 2007, Uncontrolled Copy, (c) BSI 7 4.3 Data Manipulation (DM) blocks As detailed in Figure 4, the DM block processes the digital data from the DA block
10、to convert it to a desired form which characterizes specific descriptors (features) of interest in the machine condition monitoring and diagnostic process. Often the functionality within this layer consists of some signal processing algorithms. Figure 4 Data Manipulation block This block may contain
11、 speciality processing functions such as Fast Fourier Transforms, wavelets or simple average values over a time interval. Examples of the descriptor outputs of the DM block include: extracted feature; conversion from time domain to frequency domain and vice versa; calculated, non-interpretative valu
12、es; virtual sensor (differential pressure from inlet and outlet pressures); integrating acceleration to velocity/double integration to displacement; filtering; normalization; time series including sample rate. BS ISO 13374-2:2007 Licensed Copy: London South Bank University, London South Bank Univers
13、ity, Wed Oct 17 01:13:35 GMT+00:00 2007, Uncontrolled Copy, (c) BSI 8 4.4 State Detection (SD) blocks As shown in Figure 5, the primary function of the SD block (sometimes referred to as “state awareness”) is to compare DM and/or DA outputs against expected baseline profile values or operational lim
14、its, in order to generate enumerated state indicators with respective boundary exceedances. The SD block generates indicators which may be utilized by the Health Assessment block to generate alerts and alarms. When appropriate data are available, the SD block should generate assessments based on ope
15、rational context, sensitive to the current operational state or operational environment. Figure 5 State Detection block Typically, this block of processing provides data which will contribute to a diagnosis in the health assessment block. The SD block may make use of current and historical DA and DM
16、 outputs to evaluate the current state. It may provide data manipulation and sensor module control signals, such as acquisition scheduling commands, data triggers and processing instructions. Examples of outputs of the SD block include: enumerated state indicator; threshold boundary alerts; severity
17、 of threshold boundary deviation above/below; rate of change alert; BS ISO 13374-2:2007 Licensed Copy: London South Bank University, London South Bank University, Wed Oct 17 01:13:35 GMT+00:00 2007, Uncontrolled Copy, (c) BSI 9 degree of abnormality; statistical analysis using parametric and non-par
18、ametric approaches, e.g. Weibull and Gaussian distribution. 4.5 Health Assessment (HA) blocks As shown in Figure 6, the HA block is an information block which utilizes expertise from a human or automated agent to determine the current health of the equipment and to diagnose existing fault conditions
19、. It determines the state of health and potential failures by fusing the outputs of the DA, DM, SD and other HA blocks. Figure 6 Health Assessment block An output of this block includes the component/systems current health grade and diagnosed faults and failures with associated likelihood probabilit
20、y. A calculation of the current risk priority number (RPN) may also be performed. Modelling of ambiguity groups and multiple hypotheses may be included in the output data structures. The HA block may also output an explanation detailing the evidence for a diagnosis or health grade. BS ISO 13374-2:20
21、07 Licensed Copy: London South Bank University, London South Bank University, Wed Oct 17 01:13:35 GMT+00:00 2007, Uncontrolled Copy, (c) BSI 10 4.6 Prognostic Assessment (PA) blocks As shown in Figure 7, the primary function of the PA block is to project the future state of the monitored equipment u
22、sing a combination of prognostic models and their algorithms, including future operational usage model(s). This block determines the future state of health and failure modes by combining the relevant outputs of the DA, DM, SD, HA and other PA blocks and applying a prognostic algorithm or model based
23、 on supplied projected operational utilization. To aid the algorithm or model, the HA block may also retrieve account historical failure data and operational history, along with projected failure rates related to operational utilization. The prognostics layer may report health grade at a future time
24、 or may estimate the remaining life of an asset given its projected usage profile. Assessments of future health or remaining life may also have an associated prognosis of the projected fault condition. A calculation of the future risk priority number (RPN) may also be performed. An output of this bl
25、ock includes the component/systems future health grade and future failure events with associated likelihood probability. Modelling of ambiguity groups and multiple hypotheses may be included in the output data structures. The PA block may also output an explanation detailing the evidence for a propo
26、sed failure event or health grade. Figure 7 Prognostic Assessment block BS ISO 13374-2:2007 Licensed Copy: London South Bank University, London South Bank University, Wed Oct 17 01:13:35 GMT+00:00 2007, Uncontrolled Copy, (c) BSI 11 4.7 Advisory Generation (AG) blocks As detailed in Figure 8, the pr
27、imary function of the AG block is to integrate information from DA, DM, SD, HA, PA and other AG blocks and external constraints (safety, environmental, budgetary, etc.), and to provide optimized recommended actions and alternatives to applicable personnel or external systems. Recommendations may inc
28、lude prioritized operational and maintenance actions and capability forecast assessments or modifying operational profiles to allow mission completion. The decision support module needs to take into account the operational history (including usage and maintenance), current and future mission profile
29、s, high-level unit objectives and resource constraints. Maintenance advisories from this block should detail future maintenance work required, which may include the verification of monitoring data or the performance of additional monitoring. The structure of these advisories should be put into a “wo
30、rk request” format for external maintenance work management systems. Based on this request, maintenance work management systems can schedule work in advance and locate spare parts and tools required for these jobs. Operational advisories from this block can be immediate in nature, such as the curren
31、t notification of operators of alerts and resulting action steps. Other production-related advisories can be more strategic, such as sending a notice to a production planning system about the high risk of failure on a production line due to a soon-to-fail critical piece of equipment. Capability fore
32、cast assessments from this block provide the results for requests about the likelihood of accomplishing a specific mission or production run. These assessments are critical to production forecasting systems when evaluating whether or not to accept certain missions/orders and where to assign the work
33、, based on asset optimization principles. Figure 8 Advisory Generation block BS ISO 13374-2:2007 Licensed Copy: London South Bank University, London South Bank University, Wed Oct 17 01:13:35 GMT+00:00 2007, Uncontrolled Copy, (c) BSI 12 4.8 Block configuration Each data processing block requires co
34、nfiguration information, some of which may be static data, and other parameters may be changed dynamically by the system during operation. As an example, the following is a sample of the configuration of the Data Acquisition block: a) measurement location description (measurement location table) 1)
35、orientation and relative position, 2) location description; b) monitoring intervals dynamic vs. static 1) on-line continuous, 2) on-line polled, default polling rate, default parameters; c) triggered vs. non-triggered 1) set points, 2) deadband; d) asynchronous vs. synchronous; e) transducer informa
36、tion 1) response curve, 2) measurement confidence, 3) transducer electronic data sheet (TEDS) information; f) calibration; g) channels 1) single or multiple channel collection. 4.9 External systems Retrieval of previous work histories from the maintenance system and previous operational data (starts
37、/stops/loads) from a process data historian is important in the assessment of machinery health. After a health assessment is made, the maintenance action to be taken can range from increasing the frequency of inspection, to repair or replacement of the damaged machinery or component. The effect on o
38、perations may be an adjustment of operating procedures or a request to shutdown the equipment immediately. This need for rapid communication to maintenance and operational systems requires software interfaces to maintenance management systems and operational control systems. These interfaces are use
39、ful in order to communicate recommended actions in the form of maintenance work requests and operational change requests. BS ISO 13374-2:2007 Licensed Copy: London South Bank University, London South Bank University, Wed Oct 17 01:13:35 GMT+00:00 2007, Uncontrolled Copy, (c) BSI 13 4.10 Data archivi
40、ng Data archiving is an important feature during all processing of a machine condition monitoring program. Previous data trends can be analysed for statistical relevance. The data archiving system should provide rules for the archiving rate and amount of data stored. Previous advisories should be au
41、dited for accuracy and root cause information added upon its discovery. 4.11 Technical displays Relevant technical displays showing data from each block are necessary to facilitate analysis by qualified personnel. These displays should provide the analyst with the data required to identify, confirm
42、or understand an abnormal state. 4.12 Information presentation Information from the HA, PA and AG blocks is displayed by this processing block. It is important that the data be converted to a form that clearly represents the information necessary to make corrective action decisions. In some cases, t
43、he user will need the ability to drill down into the SD, DM and DA technical displays when abnormalities are reported. 4.13 Compliant specifications An open CM no interfaces are therefore defined in this part of ISO 13374. The first step was defining an object-oriented data model in Unified Modeling
44、 Language (UML) for each layer that was then converted into an abstract interface specification. The abstract specification can then be converted to the desired middleware language for a specific interface definition. The UML object model defines interfaces only. For a given layer of the architectur
45、e, the data model does not prescribe the object classes that would be required for a software implementation. The focus is on describing the structure of the information that might be of interest to clients of that layer. OSA-CBM does not impose any requirements on the internal structure of complian
46、t software modules. The architectural constraints are applied to the structure of the public interface and to the behaviour of the modules. This approach allows complete encapsulation of proprietary algorithms and software design approaches within the software module. BS ISO 13374-2:2007 Licensed Co
47、py: London South Bank University, London South Bank University, Wed Oct 17 01:13:35 GMT+00:00 2007, Uncontrolled Copy, (c) BSI 22 Annex B (informative) References to UML, XML and Middleware B.1 Purpose This annex provides a simple reference of definitions and glossary of terms on Unified Modelling L
48、anguage (UML), eXtensible Markup Language (XML) and middleware services. In addition, a number of useful references have been provided along with pointers for simple tutorials and detailed tutorials on these topics. B.2 Unified Modeling Language (UML) B.2.1 Definition of UML The Unified Modeling Lan
49、guage (UML) is a graphical language for visualizing, specifying, constructing and documenting the artifacts of a software system. UML offers a standard way to write a systems blueprints including conceptual entities, such as business processes and system functions, as well as concrete entities, such as programming language statements, database schemas and reusable software components 27. B.2.2 Glossary of Terms Terms and their definitions have