In PackTags version 1.0, an initial set of PackTags sufficient for computing machine performance metrics was defined. In PackTags version 2.0, that initial set was expanded and adapted to support more of the PLCs that are in common use in packaging operations today.
PackTags standardizes how packaging line data--machine states, modes, commands, and data--is communicated. Data stored in each machine's controller can be readily compared only if the field names and data values are consistent. PackTags can be used to represent machine state, such as producing, stopped, or aborted. PackTags can also be used to represent common machine performance metrics, such as total run time, total productive time, total downtime, waste, efficiency, etc.
PackTags furnishes the raw data necessary to calculate machine efficiency and other performance metrics without actually specifying or endorsing a particular calculation for these metrics. That allows each company to continue using its preferred method of calculating metrics, such as Overall Equipment Effectiveness (OEE).
PackTags can be used for machine-to-machine communications (between a filler and a capper, for example); for communications within a machine (between a motion controller and PLC, for example); and for information exchange between machines and higher-level information systems such as SCADA systems, plant databases, and enterprise information systems.
PackTags是PackML规范的一部分，它只是由OMAC（Open Modular Architecture Controls）打包工作组开发的所谓的插件和包[TM]指南的一部分。OMAC是最终用户，机器建设者和控制供应商（www.omac.org）的非营利性集团。
插件和包装是打包机器“即插即用”是计算机的，代表易于使用不同供应商的包装机，无论机器控制器的制造或模型如何轻松地集成包装机。
开发了插件和包装指南以赋予以下优惠：
- Reduce the cost of time required for machine integration
- 允许自动启动和关闭包装线
- 通过更快的故障排除增加机器正常运行时间，并促进导致导致停机时间的问题的根本原因分析
- 通过为运营商和工程师提供更统一的接口来减少操作员和工程培训成本
- Lower the cost of validation of production systems for Good Manufacturing Practices and other FDA regulations
Following a 30-day public comment period, PackTags 2.0 is expected to be approved by the OMAC Packaging Workgroup executive committee at the upcoming OMAC meeting in Orlando, FL, January 29-30, 2004.
