Figure 6: If Example.amlx is used to illustrate both “Descriptor of a Product” and “Descriptor with Configuration Information” (Figure 7) then there need to be additional illustrations that show the expected changes in the descriptor and where in the descriptor structure these changes occur through the process. As a controller vendor it is critical to understand which parts of the descriptor are set at product development time, fixed at product conformance test, and secured to ensure they have not been modified as configuration has been added. Preference is to have two separate example amlx files, one containing only “Descriptor of a Product” {no connection information] with no subsequent user configuration present, and one with only configuration information documenting that which has been added by a user [connection information]. The descriptive text can then define how these may be combines into a single file.

[Submitted on behalf of Rockwell Automation]