cdf_idm system space.
Process industries concepts
The extended process industries concepts come with matching containers and views.CogniteMaintenanceOrder
The CogniteMaintenanceOrder concept has properties to represent maintenance orders. A maintenance order is a request or directive to perform maintenance tasks such as repair, inspection, or servicing of equipment or assets. It’s often called a ‘work order’.| Property | Type | Description |
|---|---|---|
| mainAsset | Direct relation to CogniteAsset | The primary asset (functional location) the maintenance order refers to. |
| type | String | The code for the type of maintenance order, for example, ‘PM01’ for ‘Corrective maintenance’. |
| status | String | The lifecycle status of the maintenance order, for example, ‘Partially complete’. It’s often derived from the ‘SystemStatus’ field in SAP. |
| priority | Int64 | A number that shows how important this maintenance order is. Lower numbers mean it’s more important, and 0 means it’s the most important. |
| operations | Reverse direct relation list | Lists the individual work items on the maintenance order. An automatically populated list of operations related to the maintenance order. |
CogniteOperation
The CogniteOperation concept has properties to represent operations, a specific part of the work included in a maintenance order. Often called a “work order item”.| Property | Type | Description |
|---|---|---|
| maintenanceOrder | Direct relation to CogniteMaintenanceOrder | The maintenance order the operation is related to. |
| mainAsset | Direct relation to CogniteAsset | The primary asset (functional location) the operation is related to. |
| phase | String | The code for the phase the operation belongs to. Each operation belongs to a single phase, for example, ‘Scaffolding’. |
| status | String | The lifecycle status of the operation, for example, ‘Partially complete’. It’s often derived from the UserStatus field in SAP. |
| sequence | Int64 | A number that shows the order in which the operations are performed. Lower numbers mean they happen earlier, and 0 means it’s the first operation. |
| mainDiscipline | String | The primary skill or resource required to perform the operation, for example, “maintenance technician”. |
| numberOfMainDiscipline | Int64 | The number of resources required to perform the operation, for example, the number of required maintenance technicians. |
| personHours | Float64 | The number of hours required to perform the maintenance operation. The duration is calculated by dividing the personHours by the numberOfMainDiscipline. |
CogniteNotification
The CogniteNotification concept has properties to represent maintenance notifications. Notifications are formal records to report maintenance issues, defects, or requests, starting the process for planning and running maintenance activities.| Property | Type | Description |
|---|---|---|
| maintenanceOrder | Direct relation to CogniteMaintenanceOrder | The maintenance order that was created from the notification. |
| asset | Direct relation to CogniteAsset | The asset (functional location) the notification is related to. |
| type | String | The code for the notification type, for example, “M1” for “Maintenance request”. |
| status | String | The current lifecycle status of the notification, for example, “order created”. |
| priority | Int64 | A number that shows how important the notification is. Lower numbers mean it’s more important, and 0 means it’s the most important. |
| priorityDescription | String | Describes the priority of the notification. |