Why SIMATIC PCS 7 CFC Lacks a Manual 'Save' Command - Real-Time Relational Database Architecture

In SIMATIC PCS 7, the Continuous Function Chart (CFC) editor intentionally omits a traditional 'File -> Save' command because CFC does not operate as a disconnected file-based graphic drawing tool. Instead, CFC operates as a direct graphical front-end to a shared, transactional relational database. Every block insertion, parameter modification, and chart interconnection commits instantly to the project database to maintain absolute multi-user data integrity, global cross-references, and compiler timestamp synchronization across the multiproject. To protect against unintended changes or track modifications, engineers must use Version Trail, Version Cross Manager (VXM), or project archiving.

The Architectural Reality of the CFC Editor

Engineers transitioning to SIMATIC PCS 7 from standard ladder logic environments or CAD packages frequently search the menus of the Continuous Function Chart (CFC) editor for a Save button. When they discover that closing a CFC chart never asks Do you want to save changes? and that edits are permanently retained the moment they are made, they often express concern regarding accidental modifications.

This behavior is not an oversight by Siemens software architects; it is a foundational pillar of distributed control system (DCS) engineering:
* A PCS 7 project is not a loose collection of standalone text files or drawings.
* It is a unified, multi-layered relational database (historically Microsoft Access/Jet engine, Sybase, and Microsoft SQL Server) managing thousands of interdependent objects across automation controllers, remote I/O racks, and WinCC operator stations.
* In this architecture, CFC acts as a visual query and transaction window directly into the database.

Why Traditional File-Based Saving is Incompatible with PCS 7

Allowing an engineer to modify a chart and choose 'Exit without Saving' would catastrophically break the data integrity of a process control system:

1. Global Symbolic and Interconnection Integrity

When you connect output pin TI101.PV_Out in Chart A to input pin PID_Feed.PV_In in Chart B, the database immediately generates cross-chart relationship pointers. If Chart A could be closed without saving while Chart B was saved, orphaned pointers and broken database foreign keys would corrupt the multiproject.

2. Time-Stamp Consistency and Change in RUN (CiR)

SIMATIC Manager tracks every parameter change, symbol update, and block addition using cryptographic internal timestamps. When you initiate Compile -> Changes only, the compiler compares database object timestamps against the target CPU's online load memory. Decoupling visual edits from immediate database commits would make Change in RUN differential compiling mathematically impossible.

3. Master Data Library Synchronization

When you execute Options -> Update Block Types, SIMATIC Manager updates hundreds of block instances across dozens of charts simultaneously. A manual save requirement would demand tracking memory rollbacks across thousands of parameters simultaneously, introducing severe database instability and performance degradation.

Comparison Table - File-Based Editors vs Database-Driven CFC

The following table contrasts traditional file-based PLC editors with the database-driven architecture of SIMATIC PCS 7 CFC.

Architectural DimensionTraditional File-Based Editors (LAD/FBD)SIMATIC PCS 7 CFC EditorData Storage ModelDisconnected file buffer in RAMLive transactional relational databaseCommit TimingUser clicks 'File -> Save'Instantaneous on every user actionExit Without Saving?Permitted (Discards RAM buffer)Prohibited by designCross-Chart ReferencesResolved only during full project buildLive cross-reference pointers maintained instantlyMulti-User EngineeringFile-level locking; high risk of merge conflictsObject-level record locking across multiprojectChange Tracking MechanismGit / External file diffSIMATIC Version Trail & Version Cross Manager (VXM)

Engineering Safeguards and Change Tracking Workflows

Because CFC commits changes instantly, professional automation engineers employ specific engineering methodologies to manage risk and audit modifications:

Milestone Archiving via SIMATIC Manager:
* Prior to making major structural changes or running Update Block Types, perform a complete project archive: File -> Archive.
Deploying SIMATIC Version Trail:
* Use Version Trail to take quick, timestamped snapshots of individual S7 projects or the entire Multiproject prior to commissioning sessions.
Auditing Changes via Version Cross Manager (VXM):
* If an unintended change was made and you are unsure what was altered, open SIMATIC Version Cross Manager.
* Compare the current offline project against your pre-modification Version Trail archive.
* VXM highlights every modified parameter, moved block, or deleted interconnection in a clear graphical comparison tree.
Inspecting the Download Change Log (XML):
* Enable the generation of the download log. Before downloading to the AS, review the generated XML delta file to inspect exact parameter and block additions.

Verification

Confirm understanding of database commit behavior through practical verification:

Verify Instantaneous Database Commit:
* Open any test CFC chart. Place a simple standard block (e.g., ADD_R).
* Do not click any menu items; immediately close the CFC editor using the top-right X.
* Reopen the chart. Confirm that the block exists exactly where placed.
Verify Cross-Reference Generation:
* Interconnect two blocks across separate charts.
* Open Process Object View (PO View). Confirm that the signal interconnection appears immediately in the Signals tab without requiring any save operation.
Verify Timestamp Update:
* Check the offline block folder. Confirm that the date and timestamp of the chart container updated at the exact second the edit occurred.

Limitations and Operational Precautions

Experimental Logic Precaution: Never test unverified logic directly inside production plant charts. Create an isolated scratch chart (e.g., _Test_Scratch) or an offline copy of the project to test complex algorithms.
Avoid Killing Process via Task Manager: Terminating cfc.exe or s7tgtopx.exe via Windows Task Manager during an active block insertion or database write can leave an open database lock. Always close editors normally.
Network Share Hosting: Avoid hosting live PCS 7 database folders over unstable Wi-Fi or slow VPN connections; database write latency can cause editor timeouts.

Engineer FAQ

Can I undo a change in CFC if there is no save button?

CFC provides a multi-level Undo function (Ctrl+Z) within the active editing session for recent block placements and interconnections. However, once the chart is closed, the undo history is purged because database transactions are finalized.

What happens if my computer loses power while editing a CFC chart?

Because CFC writes transactions incrementally, work completed up to the last successful action is safely stored in the database. When the PC restarts, SIMATIC Manager runs an automatic database integrity check upon opening.

Why does changing a single symbol name require an AS compile?

Symbols are registered globally in the database. Changing a symbol updates the variable's cross-reference record and updates the timestamp, signaling the differential compiler that an address or name descriptor changed.

Can two engineers edit the same CFC chart at the same time?

In multi-user engineering, PCS 7 allows engineers to edit different charts simultaneously. However, two engineers cannot open the exact same CFC chart simultaneously; the second user receives a chart lock notification.