Restoring Default Database Templates in PCS 7 Advanced Engineering System (AdvES)

In SIMATIC PCS 7 Advanced Engineering System (AdvES), inadvertently saving modifications made within the tabular Signal List (PLS) into the central AdvES master database alters the default baseline templates for all subsequent engineering projects. While project-specific signal mappings are intended to be accepted without overwriting global templates, saving global changes corrupts the default device and hardware catalogs. Reverting this condition requires restoring the original factory template database from the AdvES installation directory repository, utilizing the AdvES Archive Administration utility to roll back to a clean baseline snapshot, or re-initializing the SQL Server database instance.

AdvES Database Architecture: Global Templates vs Project Data

SIMATIC PCS 7 Advanced Engineering System (AdvES) is an engineering workflow tool that bridges process design data (P&IDs, electrical loops, Excel instrumentation lists) with SIMATIC PCS 7 automation projects.

AdvES relies on a relational database architecture (typically hosted on Microsoft SQL Server or Microsoft Access) divided into two distinct tiers:
1. Global Master Database (AdvES Master Archive): Contains the standardized hardware catalog, default channel driver templates, APL typical definitions, signal types, and standard unit enumerations.
2. Project Database (User Workstation Data): Contains project-specific hardware allocations, tag names, I/O channel addresses, and imported process tags.

When engineers work in the tabular Signal List PLS, AdvES documentation explicitly instructs users to apply changes to the current project, but NOT to click 'Save to Template Database'. Inadvertently saving commits user-specific signal bindings into the permanent master catalog.

Consequences of Overwriting Master Template Databases

Overwriting the global AdvES template repository introduces subtle, system-wide engineering inconsistencies:

Database StateSystem ImpactBehavior on New ProjectsImpact on Existing MultiprojectsClean Master TemplateStandard hardware & signal types generated cleanlyNew projects instantiate default factory typicalsZero cross-project interferenceOverwritten Master DatabaseCustom hardware mappings hardcoded into templatesNew projects inherit customized, incorrect signal listsTemplate drift; standard typicals desynchronizedCorrupted Subnet ReferencesAdvES points to non-standard or missing subnetsExport Wizard fails: 'Subnet not found'Hardware export to STEP 7 HW Config blockedMissing Default TypicalsBase typicals overwritten by project instancesAutomated CFC generation abortsManual intervention required for every loop

When the master template is modified, creating a subsequent new project imports the previous plant's custom tags, I/O addresses, and subnet definitions rather than pristine factory defaults.

Restoring Factory Default Databases via Archive Administration

To restore the default AdvES template database to its original factory state:

Close AdvES and STEP 7: Exit AdvES and close SIMATIC Manager. Open Windows Task Manager and confirm that background database sync processes are stopped.
Access Archive Administration:
- Open AdvES Archive Administration from the Windows Start menu under Siemens Automation -> Advanced Engineering System.
- Select the corrupted database from the repository tree.
Restore Baseline Template Snapshot:
- If an administrative baseline archive was created prior to project engineering, select Restore Database Archive and browse to the baseline backup file (.db / .bak).
- If no backup exists, locate the factory default template installed by the PCS 7 setup:
C:\Program Files (x86)\Siemens\AdvES\Templates\Default_Master.mdf
(or corresponding template in the PCS 7 installation media under AdvES\Data\).
- Replace the active master database with the clean factory file.
Re-Register Database Connection: Open AdvES Project Manager, verify database connectivity, and confirm that the catalog reflects clean factory typicals.

Best Practices for Tabular Signal List Import and Export

To prevent future accidental template corruption during mass signal imports:
* Workflow Discipline: When editing signal parameters in the tabular view, click Apply Changes to Project. Do not invoke the administrative command 'Save as Template'.
* File Permissions: Set the master database template directory to Read-Only for standard project engineers, requiring administrative elevation to commit changes to the master typical catalog.
* Regular Archiving: Before importing large Excel instrumentation schedules, execute AdvES -> Project -> Archive to create a restorable rollback point.

Verification

To verify that AdvES template integrity is restored:
1. Launch AdvES and create a new temporary test project.
2. Open the Hardware Assignment view; verify that default hardware catalogs and standard PROFIBUS/PROFINET subnets appear without lingering tags from previous projects.
3. Import a sample single-point signal list; confirm that AdvES matches signal types against standard APL templates without database warnings.
4. Delete the temporary test project once verification is complete.

Limitations and Operational Precautions

Restoring the factory master database will eliminate any legitimate custom typicals that were engineered across the facility. Always create a manual backup of the current database before performing a database restore. Note that in modern PCS 7 releases (V8.2 and V9.x), AdvES is largely superseded by SIMATIC PCS 7 Plant Automation Accelerator (PAA), which provides integrated object-oriented data management based on COMOS technology.

Engineer FAQ

Can modifying the AdvES database damage the running controller program?

No. AdvES is an offline engineering and planning tool. Database inconsistencies in AdvES only impact the generation of offline STEP 7 and CFC projects; they do not alter running controllers until a project is compiled and downloaded.