Data published to CONNECT data services

The AVEVA Production Management on-premises data published to CONNECT data services includes project configurations mapped to these specific types:

• Assets - These are equipment and application folders in the hierarchy.

• Asset type - This is the equipment, and AVEVA Production Management has only one asset type.

• Enumerations - These are the runtime, downtime, and idle time utilization state types in the CONNECT data services common data model, with downtime representing all the AVEVA Production Management event data.

• Event types - These can be reporting points for Downtime, Production, and Metrics modules.

• Reference data types - These are cause, classification, and effects

  Note: Cause is mapped to utilization reason, and Classification is utilization state to follow the CONNECT data services common data model. When these reference data types are pushed to the cloud service, they are shown as utilization reasons and utilization states.

• Reference data - The actual value for the cause, classification, and effects

Each of the listed data types has its corresponding JSON configuration file, which is stored in a directory accessible only with administrative privileges. The default file path for the these persisted configuration files is %ProgramData%\Citect\Ampla\ADHConfig\<ProjectName>.

If the project configuration data has already been published to the CONNECT data services and the Studio configuration is changed, the curator detects and sends only the recent changes to the CONNECT data services.

For the change tracking to work, restarting the Production Management Data Curator and Events to CONNECT services is required. To verify that your changes are published, see the log files (%ProgramData%\OSIsoft\Adapters\EventstoCONNECT) or access the CONNECT data services. For more information, refer to Verify that the data is published to the CONNECT data services.

When you need to resend the whole AVEVA Production Management configuration to the CONNECT data services from scratch, such as after adding a new egress endpoint or changing the namespace ID in the Events to CONNECT agent settings, delete the persisted files from the project folder.