Package Unit integration

SIMATIC PCS neo as process control system offers you a convenient way to integrate a Package Unit in line with the standard VDI/VDE/NAMUR 2658. At the time of release of SIMATIC PCS neo V4.0, this standard is still being developed further. New versions of the respective documents will be published (VDI/VDE/NAMUR 2658-1 to -4). For this reason, statements regarding compliance with the standard should only be considered in relation to the status quo at the time of release and are therefore only valid to a limited extent.

According to the VDI/VDE/NAMUR 2658 definition, the SIMATIC PCS neo system as a whole represents the POL (Process Orchestration Layer). The Package Units or modules are referred to hereinafter as PEA (Process Equipment Assembly).

In SIMATIC PCS neo V4.0, the following sheets of the standard in the respective version are supported:

¹⁾ Optional use of the PEA Information Label and consideration of corrections in the AML description according to Version 1.1.0 as part of the MTP.

Newer versions of existing MTP sheets as well as new MTP sheets are always only considered in future PCS neo versions. Older versions of MTP sheets are only supported in newer PCS neo versions if they have not already been discontinued by Siemens AG. Generally, pre-release versions of the aspect models are replaced by the next release version of these models. Using functions of an unpublished version poses the risk of later modification, both on the module and on the PCS neo side.

Example:

In PCS neo V4.0, Manifest V1.0.0 and V1.1.0 of VDI/VDE/NAMUR 2658-1 is supported. As soon as the manifest is available in a new published version, e.g. V2.0.0, the intermediate version is no longer supported in future PCS neo versions.

In general, SIMATIC PCS neo in V4.0 supports the following aspects:

• MTP import and subsequent instantiation
• MTP versioning
• Visualization of PEA operating screens
• Support of library and data objects
• Manual control of module services
• Connection of module services to SIMATIC PCS neo Batch

The following overview display shows the division of the different parts of a modular process plant with respect to MTP.

SIMATIC PCS neo as POL in the sense of a module plant according to VDI/VDE/NAMUR 2658-x has implemented the following workflow at this time.

Range of functions in SIMATIC PCS neo Templates editing:

• Importing an MTP file as new template (referred to as CNY module template hereinafter)
• Versioning the CNY module template using SIMATIC PCS neo version designation. When the PEA Information Label³⁾ is used, a consistency check also takes place during the import
• Editing of imported process pictures directly in the template

Range of functions in SIMATIC PCS neo Engineering:

• Instantiation of CNY module templates directly into the equipment hierarchy of SIMATIC PCS neo
• CNY module instantiation can take place with and without reference to an ISA-88 structure. If the ISA-88 structure is used, integration into SIMATIC PCS neo Batch is possible
• The following assignment applies when using SIMATIC PCS neo Batch:
  • EM (Equipment Module) corresponds to an MTP service according to VDI/VDE/NAMUR 2658-4
  • EPH (Equipment Phase) corresponds to an MTP procedure according to VDI/VDE/NAMUR 2658-4
• Multiple instantiation of CNY modules both with and without reference to an ISA-88 structure
• Selective instance update through a newer version of the CNY module template
• Editing of imported process pictures in the CNY module
• Automatic creation of the CNYResource and the associated assignment
• Verification of the optional PEA Information Label with assignment to specific hardware (PEA device assignment to a CNYResource)
• Automatic creation of the relevant hardware representative and automatic assignment to the instance if it has been globally defined in the project settings
• Additional optimization with respect to the engineering sequence with the objective of highly efficient engineering
• Configuration of bit-triggered (M&C Managed Alarms) alarms only in the so-called MTP Monitoring blocks⁴⁾, if this function is supported by the PEA
• PEA – PEA process value interconnection within the POL (PCS neo M&C)

Range of functions in SIMATIC PCS neo operator control & monitoring:

• Visualization of PEA operating screens, both as a stand-alone operating screen of a PEA and as visualization of user-created or combined operating screens in SIMATIC PCS neo
• Manual MTP service operation via a stand-alone faceplate
• Visualization of PEA alarms that are generated in the runtime systems of PCS neo (OsBasedAlarms)

The following restrictions must be taken into consideration for SIMATIC PCS neo V4.0:

• The standard VDI/VDE/NAMUR2658-x is currently undergoing significant changes, so new functions of future sheets and also new versions of sheets 1-4 will only be considered in future SIMATIC PCS neo versions
• Multilingual support of the MTP description (TagName, TagDescription) directly from the MTP file will be considered in future PCS neo versions

The following preliminary functions should be taken into consideration in connection with MTP in SIMATIC PCS neo V4.0:

• Verification of the PEA Information Label (also referred to as nameplate) only takes place in the engineering of SIMATIC PCS neo
• PEA alarming via M&C Managed Alarms represents a solution approach outside of standardization. In this context, note that complete synchronization of alarm states (e.g. acknowledgments POL <-> PEA) does not take place

These functions will be adapted to the respective standard solution in future SIMATIC PCS neo versions and may remain available as proprietary solution outside of the standard.

³⁾ An evaluation of ManufacturerURI, ProductCode and DeviceRevision currently takes place.

⁴⁾ Bit-triggered alarms are supported by the following blocks: MonAnaDrv, MonAnaVlv, MonBinDrv, MonBinVlv, AnaMon, BinMon, DIntMon.