ADS Best Practices

Change Control & Management

ADS is designed to simplify the change control and management processes. Once a firmware is released - internally or externally depending on the development process- , the state of the associated device profile will be set to Production, hence setting the device profile in read-only mode. This guarantees that the device definition cannot be changed by the testing or field teams, since its associated firmware is not deployed on devices in testing phase or to the field. See section Device Profile Versioning and State.

 
 

The following table summarized the multiple mechanisms to manage change and access to device definition and data.

Examples of Controls	Solution
Control user privileges	Set the appropriate user roles to control what an individual user can do.
Restrict device profile changes after deployment and separate data between development and production	Set the device profile to the Production state. In Production state, a device profile cannot be modified like its associated released firmware.
Manage devices in different business units or development stages	Use a separate device profile or device profile version for each group or development stage.
Implement physical separation of device profiles and data between development and production	Use a separate ADS instance to isolate development and production environments. Note: ADS can be deployed in-prem or on a private cloud. Consult with Sternum for more information.