Many plants still run production on Camstar, the MES that Siemens acquired in 2014 and has since developed as Siemens Opcenter Execution. Camstar has served these sites well, but older releases sit on aging infrastructure, carry years of custom code, and fall further behind the product Siemens is investing in. Sooner or later, the upgrade has to happen.
This guide walks through how we approach a Camstar to Opcenter Execution upgrade at Conseptis, the decisions you need to make early, and the pitfalls that most often cause delays.
Why upgrade from Camstar now?
- Supportability. Older Camstar versions no longer receive the same level of fixes and updates as current Opcenter releases. Check the Siemens support lifecycle for your exact version.
- Infrastructure end-of-life. Legacy MES servers are often tied to Windows Server, SQL Server or Oracle versions that are out of support, which becomes a security and audit finding.
- Modern user experience. Current Opcenter releases offer a modernized, browser-based operator experience that is easier to train on and use on the line.
- The digital thread. Opcenter is designed to work alongside Teamcenter PLM and the rest of the Siemens Xcelerator portfolio, which makes closed-loop manufacturing and quality much easier to build.
- Lower cost of change. Every year on an old platform adds custom code that someone has to maintain, re-test and eventually migrate.
Upgrade or re-implement?
The first decision is whether to upgrade (carry your existing model, configuration and customizations forward) or re-implement (rebuild on Opcenter using standard functionality and migrate only the data you need).
- Upgrade when your processes are stable, customization is modest, and the main driver is supportability.
- Re-implement when the system is heavily customized, processes have changed, or many customizations duplicate features that Opcenter now provides out of the box.
Most real projects are a hybrid: the core model is carried forward, while the most problematic customizations are retired or rebuilt.
Step 1: Assess your current Camstar system
A good assessment saves more time than any other step. Build an inventory of:
- Version, modules and licenses in use, per site
- Custom objects, services, UI pages, reports and labels
- Integrations with ERP (SAP, Oracle, Dynamics), PLM, LIMS, quality systems, label printers and equipment
- Database size, history retention needs and archiving rules
- Validation documentation and the regulatory requirements that apply (for example 21 CFR Part 11)
- Pain points users report today
Rate each customization: keep, replace with standard, rebuild or retire. This list becomes the backbone of your plan and estimate.
Step 2: Design the target architecture
Decide on the target Opcenter version, server and database platform, high availability, and environments (development, test, validation and production). Plan for performance from day one: size the database and application tier using your real transaction volumes, not defaults.
Step 3: Remediate customizations
Work through the customization inventory. Retire what is no longer used, switch to standard Opcenter functionality where it now covers the requirement, and refactor what must remain so that it follows current Siemens extension practices. Fewer customizations mean faster future upgrades.
Step 4: Plan the data migration
- Master and modeling data: products, specifications, workflows, resources, users and roles.
- Work in progress: open lots, containers or serial numbers that must continue on the new system after cutover.
- History: decide what moves to Opcenter, what stays in a read-only archive, and how auditors and quality will query it. Device history and batch records often have long retention requirements.
Run several full migration rehearsals on production-sized copies, and reconcile record counts and key values each time.
Step 5: Rebuild and test integrations
Integrations are where upgrades most often slip. Document each interface (trigger, payload, error handling), rebuild or adapt it for the new version, and test it end to end with the real ERP, PLM and equipment test systems, including failure and retry scenarios.
Step 6: Test and validate
For regulated manufacturers, the upgrade must be validated. Use a risk-based approach, such as GAMP 5 and the FDA's Computer Software Assurance (CSA) thinking, so that testing effort goes into the functions that affect product quality and patient safety. Combine scripted testing for high-risk functions with unscripted and exploratory testing elsewhere, and involve shop-floor users early through user acceptance testing.
Step 7: Cut over and stabilize
- Choose a cutover window with the least production impact, such as a planned shutdown.
- Freeze modeling changes and reduce WIP before cutover.
- Use a minute-by-minute cutover runbook with go/no-go checkpoints and a tested rollback plan.
- Provide on-floor hypercare support for the first weeks, and track issues daily.
Common pitfalls to avoid
- Underestimating the number of undocumented customizations and reports.
- Testing integrations only with mock systems.
- Treating history data as an afterthought.
- Training users too early, or too late, for go-live.
- Skipping performance testing with realistic volumes.
Camstar to Opcenter upgrade checklist
- Inventory version, modules, customizations and integrations
- Decide upgrade, re-implement or hybrid
- Define target version, architecture and environments
- Remediate customizations
- Rehearse and reconcile data migration
- Rebuild and test integrations end to end
- Validate with a risk-based approach
- Execute cutover runbook and hypercare
Frequently asked questions
How long does a Camstar to Opcenter upgrade take?
It depends mostly on the amount of customization, the number of integrations and sites, and validation requirements. A focused assessment is the fastest way to get a reliable estimate for your system.
Can we upgrade without stopping production?
Production must pause briefly during cutover, but careful WIP planning, rehearsed migrations and a tested runbook keep that window short.
Do we need to re-validate the whole system?
Not necessarily. A risk-based approach focuses validation effort on changed, high-risk functionality and leverages existing documentation and supplier testing where appropriate.
Planning a Camstar upgrade? Our team has implemented, upgraded and supported Camstar and Opcenter across semiconductor, electronics and medical device plants.