Appendix: Device Type Codes and File Naming
This appendix defines standard conventions for device type identification and file naming. These conventions are supplementary to the core versioning specification.
Device Type Codes
The following codes identify the type of device or software being versioned:
| Code | Description |
|---|---|
CTL |
Controller (other than PLC) |
DRV |
Drive unit, variable-frequency drive, or soft starter |
HMI |
User interface device program or configuration (e.g. text console, graphic panel, SCADA software) |
INS |
Instrumentation (e.g. programmable sensor, signal transmitter, safety barrier) |
PLC |
Programmable Logic Controller |
PRJ |
Project encompassing multiple devices (e.g. a TIA Portal project containing PLC and HMI) |
MIS |
Miscellaneous - any device not covered by the categories above |
Organisations MAY define additional device type codes to cover device types not listed above. Custom codes SHOULD be documented in project-level conventions and MUST NOT conflict with the codes defined here.
File Naming
Versioned files MUST follow this naming format:
<project_id>_<device_code>_v<version>.<ext>
Where <project_id> is a unique project identifier, <device_code> is one of the codes defined above, <version> is the version string, and <ext> is the appropriate file extension or archive format.
Examples:
| File | Description |
|---|---|
P001_PLC_v0.5.1.zip |
PLC archive with backwards-compatible changes, pre-FAT |
P001_HMI_v1.3.0.zip |
HMI archive with functional changes after FAT |
P001_DRV_v2.0.zip |
Drive configuration released for SAT (Patch omitted per item 5) |
P001_PRJ_v1.0.0.zip |
Full project archive released at FAT |