Sequence | Entity | Description |
1 | Defines the information required for various asset configurations with other assets, components, firmware, and other data. | |
1 | Used to guide workers through corrective and preventive inspection processes as part of an asset’s service history. | |
1 | Defines the main attributes for service history of a certain type. Types might include maintenance, inspection, service, test, measurement, and so on. | |
2 | Defines the details of asset or component locations of a certain type. Valid types of asset locations can include service points, other locations for installed assets, or any other location as defined by your organization. | |
2 | Defines attributes of types of locations where assets that are out of service are stored and maintained. Examples of out of service locations include warehouses, storerooms, and repair shops. | |
2 | Used for categorization and reporting for locations. | |
2 | Documents and manages valid setups for assets and components. This includes a specification for each asset or component in the configuration as well as the valid value for each parameter, such as the firmware version of each asset. | |
3 | Defines physical locations where assets are stored or repaired such as a storeroom, warehouse, or service facility. When assets are changed to statuses such as “In Repair” or “Pending Disposition” the asset location is typically moved to an out of service location. | |
3 | Provides a summary of currently installed configurations. | |
4 | Defines the attributes for assets and components of a certain type, including information such as the valid location types and service history types for the assets and whether or not such assets can have attached components. When setting up Asset Types, asset type codes should match corresponding device type codes in Meter Data Management (see Meter Data Management Table Setup Sequence). | |
5 | Defines the attributes for asset activities of a certain type, including scheduling information , exception handling, attachments, and related completion event types. Note: Asset activity types are automatically created when Service Order Management Field Task Types are created (values for the Field Task Type extendable lookup). | |
5 | Define various processes or events to be executed when completing an asset activity such as asset replication, service history creation, attachment creation, and activity creation. | |
5 | Defines the information required for the system to receive messages from external systems. |