How to Deploy PCS 7 Process Picture Changes Without Stopping the OS

Use the engineering station's changes-only OS download to deploy process-picture modifications when the installed PCS 7 version and project state support it. For PCS 7 V9.0 SP1, Siemens explicitly permits process-picture and associated-script changes without an OS stop and documents client updating. Copying a PDL directly to one server is not a verified distribution method for a two-server, three-client installation, and direct OS project edits jeopardize the documented changes-only workflow.

Choose the Engineering-Station Deployment Path

For PCS 7 V9.0 SP1, Siemens documents process pictures and their associated scripts as changes that can be downloaded without stopping the OS. The same manual explicitly warns that changing the project directly on the OS prevents subsequent use of Download changes until an entire-project download is performed.

Consequently, copying a modified PDL only to one server is not an established substitute for project deployment. A two-server, three-client arrangement must be classified correctly: two servers are not necessarily a configured redundant pair. The installed PCS 7 release and server/client assignments must be identified before applying this V9.0 SP1 procedure. Operator Station manual, chapters 19.1 and 19.7

Prerequisites

Establish a recoverable engineering-project backup and a record of the current target projects. Use a test environment to check the edited picture's object references, scripts and navigation before live deployment.

The documented changes-only function requires an earlier complete compilation and download. Check that it remains available; do not perform a full compilation merely to deploy a small picture change, because the manual lists full OS compilation among actions that remove changes-only availability.

For a configured redundant pair, both partners must be in Runtime for Download changes. Confirm the actual standby assignment rather than deciding the order from computer names. These are deployment prerequisites, not proof that the modified picture itself is correct.

Procedure for an Individual OS

The following menu sequence is documented for PCS 7 V9.0 SP1, chapter 18.5:

In SIMATIC Manager, open the component view or plant view.
Select the OS object to be updated and choose PLC > Download.
In the download dialog, select Changes, not The entire WinCC project.
Review the selected target and scope before confirming with OK.

Make the picture change in the engineering project and retain that project as the controlled source. If Changes is unavailable, establish the reason before proceeding; a complete download requires its own operational plan.

Do not cancel a changes download casually: the manual warns that cancellation leaves only a complete download available. Use the generated download information together with Runtime checks to assess the result.

Server and Client Handling

The documented changes workflow updates server data and supplies current data to OS clients. A client that was not in Runtime during the download needs its relevant OS servers in Runtime when that client starts so its data can update.

For a configured redundant OS pair, PCS 7 downloads the standby application before the other partner rather than downloading both simultaneously. This documented coordination is a reason to use the project download workflow instead of manually replacing files independently on several computers.

Client-specific content and deployment targets still require project review. Automatic server-data updating must not be expanded into a guarantee that an arbitrary manually copied PDL, local client picture or script dependency has been distributed correctly.

Verification

After deployment, open the changed process picture through its normal navigation on every affected client. Inspect the actual modified objects, dynamic values and permitted operator interactions. Check that associated scripts and picture transitions behave as intended in the approved test scope.

For redundant systems, verify the picture from the required server paths and confirm that redundancy remains healthy. Record deployment results for each target. A copied file timestamp or successful download message alone does not prove that clients display and execute the intended revision.

Limitations and Operational Precautions

The verified procedure is for PCS 7 V9.0 SP1; the affected installation's version was not specified. Exact behavior of direct PDL copying, including any client caching or local-picture arrangements, was not independently established.

Do not make direct OS project edits as a shortcut while relying on future changes-only downloads. Avoid simultaneous server maintenance, preserve a recoverable previous project, and schedule rollback with awareness that a full download may require an OS stop. For a picture-only change, do not introduce an unrelated AS download; AS-changing work must be reviewed separately.

Engineer FAQ

Must every picture modification stop the OS?
No. V9.0 SP1 documents process-picture and associated-script changes among changes downloadable without an OS stop, subject to the function's prerequisites.

Can I simply copy the PDL to server 1 and assume all clients update?
That behavior was not established. Use the applicable engineering-project deployment workflow and verify each affected client.

Technical References

Siemens — Operator Station (V9.0 SP1), October 2017, A5E39219159-AB — chapter 18.5 individual OS download; chapter 19.1 prerequisites, direct-edit warning, client updating and redundancy; chapter 19.7 process pictures; chapter 19.8 loss of changes-only availability.

PCS 7 download changes

How to Deploy PCS 7 Process Picture Changes Without Stopping the OS