Define how device to WFM API interactions should be handled for intermittently connected devices

[ajcraig]

Feature description

Goal: Provide details on how device to WFM API interactions handle intermittent connections within industrial automation networks.

Category

• Device & WFM Interactions

Provide adequate technical acceptance criteria(s) associated with this feature below:

• Define the proper way to handle intermittent connections
  • Impacts deployment status
  • Device capabilities
  • to a lesser extent deployment specifications
• Ensure Open API specification is updated to address this hole in definition
• Provide best practices for vendors within this interaction

Although not required, it is highly encouraged to provide feature use-cases below:

• It is common within Industrial automation networks, especially when spanning edge to cloud, for the connection to be intermittent.
• This feature enables the communication patterns outlined in the management interface to survive these outages(planned or unplanned) in a consistent manor between vendors.

Additional information

Possible solution:

• A PR needs to be created to update the specification to indicate the device must apply recommended practice for retry and backoff logic to ensure the required information is eventually transmitted and not lost if there are connection issues

[HAHermsen]

See related use case: #171 - Workload Pinning During Network Outages

This demonstrates the real-world impact and need of defining device-WFM API interactions for intermittent connections.