Embedding Readable Documentation and License Requirements in Compressed PCS 7 Archives

To embed human-readable documentation, software version requirements, and license prerequisites inside a compressed SIMATIC PCS 7 project archive—accessible without decompressing the entire multiproject database—engineers should utilize the 'Additional Document' object within SIMATIC Manager Plant View. In the Plant View under Process Tag Types or Plant Hierarchy folders, inserting an 'Additional Document' generates a plain text, Word, or Excel document stored in the predictable project subfolder AMOBJS\. When the project is archived using PKZIP (File -> Archive), standard ZIP utilities can extract and view this document directly from the archive root without unpacking gigabytes of SQL and CFC databases.

PCS 7 Multiproject Archive Architecture and Handover Challenges

In industrial automation maintenance and lifecycle management, transferring SIMATIC PCS 7 multiprojects between engineering firms, plant owners, and field service teams frequently creates operational bottlenecks. A full PCS 7 multiproject archive (.zip format generated via File -> Archive in SIMATIC Manager) routinely spans 2 GB to 20 GB and contains hundreds of thousands of individual files across WinCC SQL databases, CFC chart structures, and hardware definitions.

When a maintenance engineer or system integrator receives a compressed archive, they must know which exact PCS 7 version, Service Pack, Update rollup, optional packages (such as S7 F-Systems, SIMATIC BATCH, or CEMAT), and Virtual Machine (VM) configuration are required before attempting decompression. Opening or decompressing an archive in the wrong engineering environment can silently corrupt database cross-references or cause library mismatch errors.

Embedding Files via SIMATIC Manager Plant View Additional Documents

SIMATIC PCS 7 provides a built-in mechanism to associate external documentation directly with the technological project hierarchy:

Plant View Architecture: In SIMATIC Manager, the Plant View (View -> Plant view) organizes the automation project according to ISA-88 equipment levels (Plant -> Unit -> Equipment Module -> Control Module).
Additional Document Objects: Users can insert native document objects into any plant folder or Master Library folder (Insert New Object -> Additional Document). Supported document types include plain text (.txt), rich text (.rtf), Microsoft Word (.docx), and Excel (.xlsx).
Predictable Storage Location: PCS 7 physically stores these attached documents in a dedicated directory located at <Multiproject_Directory>\<MasterLib_Project_Name>\AMOBJS\.

Because SIMATIC Manager uses standard ZIP compression algorithms, anyone receiving the compressed .zip file can open it using standard Windows Explorer, 7-Zip, or WinRAR, browse directly into the AMOBJS subfolder, and double-click the specification document without decompressing the project or launching SIMATIC Manager.

Comparison of Project Documentation Embedding Methods in PCS 7

The following table compares different methods for embedding release notes and system prerequisites inside PCS 7 archives:

Documentation MethodAccessibility Without ExtractionIntegrated in SIMATIC Manager?Maintenance RiskRecommended ContentPlant View 'Additional Document' (AMOBJS\)Yes (browseable in ZIP viewer)Yes (integrated in project tree)Low; managed by STEP 7Detailed VM requirements, required license list, installed software releasesRoot-level README.txt Added to ZIPYes (located in archive root)No (external to STEP 7 database)Moderate; may be omitted during re-archiveQuick-start guide, author contact, master library versionProject Properties 'Comment' FieldNo (requires SIMATIC Manager)Yes (right-click Project -> Properties)Low; cannot be lostShort summary of changes, project title, order numberSCL Source Code CommentsNo (requires full project decompression)Yes (located in S7 Program sources)High; invisible to maintenance staffInternal algorithm logic and developer notesAutomation License Manager Export (.csv)Yes (if stored in AMOBJS\)Optional (ALM export)LowComplete list of required engineering and runtime licenses

Step-by-Step Procedure to Embed Documentation in PKZIP Archives

Follow this procedure to embed readable project and license specifications inside your PCS 7 archive:

Open Plant View in SIMATIC Manager:
- Launch SIMATIC Manager and open the target Multiproject.
- Select View -> Plant view from the top menu bar (or press Ctrl+Shift+P).
Insert the Additional Document:
- Expand the project hierarchy to locate the Master Library or top-level Plant Folder.
- Right-click the folder, select Insert New Object -> Additional Document.
- In the file dialog, choose whether to create a new text document (Notepad) or link an existing specification document (README_REQUIREMENTS.txt).
Populate System and License Requirements:
- Open the embedded document and record mandatory commissioning data:
- Exact SIMATIC PCS 7 Version and Service Pack (e.g. PCS 7 V8.2 SP1).
- Installed Add-on packages with versions (e.g. S7 F-Systems V6.2, SIMATIC BATCH V8.2).
- Compatible Operating System (e.g. Windows 10 Enterprise 2016 LTSB 64-bit).
- Full equipment schedule of engineering licenses required in Automation License Manager.
- VM hypervisor specifications and IP configuration.
Archive the Multiproject:
- In SIMATIC Manager, select File -> Archive....
- Select the 'Multiprojects' tab, highlight your project, and choose the target archive directory.
- Ensure archive format is set to PKZIP and click OK.
Verify Archive Readability:
- Without using SIMATIC Manager, open the resulting .zip file in Windows Explorer or 7-Zip.
- Navigate to the subfolder ...\AMOBJS\ and confirm that README_REQUIREMENTS.txt can be read and edited directly.

Verification

Verify documentation accessibility through the following steps:
1. Transfer the generated .zip archive to an isolated test computer that does not have SIMATIC PCS 7 or STEP 7 installed.
2. Double-click the .zip archive in Windows Explorer.
3. Search for or navigate directly to the AMOBJS folder within the archive tree.
4. Double-click the embedded text or Excel document and verify that all software version requirements, license lists, and author contacts are clearly legible.
5. Decompress the archive using SIMATIC Manager (File -> Retrieve...) on an engineering station and verify that the document remains accessible in the Plant View hierarchy.

Limitations and Operational Precautions

Never Manually Inject Files into an Existing ZIP Without STEP 7: Injecting files into the root of an archive using third-party ZIP tools can occasionally alter file headers or paths, causing SIMATIC Manager's 'Retrieve' function to report archive integrity errors. Always insert files via SIMATIC Manager before executing File -> Archive.
Avoid Proprietary Formats: Use plain text (.txt), Portable Document Format (.pdf), or universally supported CSV formats for embedded documentation. Proprietary word processing formats may not render correctly on clean industrial virtual machines lacking office productivity software.
File Size Optimization: Do not embed massive video tutorials or high-resolution CAD models into AMOBJS, as this inflates the multiproject archive and slows down automated daily backup cycles.

Engineer FAQ

Where does SIMATIC Manager store 'Additional Documents' physically?

SIMATIC Manager physically stores inserted additional documents in a subfolder named AMOBJS located inside the respective project or master library folder directory structure (C:\[Project]\[Subproject]\AMOBJS\).

Can I view the Plant View if I am only using standard STEP 7 without PCS 7?

Plant View is an integrated feature of SIMATIC PCS 7 and standard STEP 7 with engineering toolsets. However, if opening a raw STEP 7 project that lacks plant hierarchy configuration, the user must first enable the Plant View under View -> Plant view or insert the document in Component View via the project root properties.

Why does SIMATIC Manager 'Retrieve' fail if I modify the ZIP externally?

SIMATIC Manager validates internal checksums and directory tables during project retrieval. If third-party compression software alters archive headers or file timestamps during external file injection, STEP 7 may flag the archive as corrupted.