Intelligent Operations Platform
Seqonis (formerly Shiftconnector) marks a major milestone in our 20‑year journey from a digital shift‑handover tool to a full Intelligent Operations Platform and operational backbone for pharmaceutical, chemical, and process manufacturers
Frequently Asked Questions (FAQs)
Shop-floor operators / frontline users
Does anything in my daily work actually change, or is it really “just the name”?
No changes are planned to how you work in the system. The name and logo will look different, but the way you create entries, view information, and complete your tasks stays the same.
Will the user interface (look & feel, buttons, menu labels) change because of the new name?
Only very small visual elements will change, such as the product name and logo. The layout, buttons, and navigation you use every day will remain as they are, so you won’t have to relearn anything.
Do I need any new training to use the system under the new product name?
No additional training is required. The system will work as it does today. If you’d like, we can provide a short information sheet or slide to explain the new name to your team.
Will my existing log entries, comments, and attachments still be available exactly as before?
Yes. All your existing data—including logs, comments, attachments, actions, and history—remains unchanged and fully accessible. Only the product name displayed in the interface changes.
Do I need to log in differently (new URL, app icon, bookmarks, or credentials)?
For the moment, your login process, URL, and credentials will stay exactly the same. We will contact you individually regarding future changes of your URL.
Shift leaders / line supervisors
Will any report names, forms, or checklists we use in daily operations change because of the rebranding?
The content and structure of your reports, forms, and checklists will stay the same. In some places, the product name in headers or footers may appear with the new name, but the underlying templates and workflows will not change.
How do I explain this name change quickly and clearly to my team so they don’t get confused?
You can say: “Our existing system from eschbach is getting a new product name and logo, to better reflect what the product has evolved into over the years. Only the name and the logo change, everything else stays the same, and the way we work with it stays the same.”
Are there any changes to support contact details or escalation paths we use during shifts?
No. Your support contacts, escalation paths, and service processes stay the same. If you currently contact eschbach support through a known channel, you can continue to use that as before.
Will our existing shortcuts, QR codes, or workstation links still work after the name change?
Yes. Existing links, QR codes, and shortcuts will continue to work. If any technical endpoint must change in the future, it will be handled with redirects and clear communication so your operations are not disrupted.
Will the change affect ongoing audits, investigations, or open actions documented in the system?
No. All open actions, investigations, and audit-related records remain exactly as they are. The system will continue to track and document everything as before; only the displayed product name changes.
Plant / site managers
Is this purely a cosmetic/branding change, or does it signal upcoming functional, pricing, or roadmap changes?
This change is focused on branding: a new product name and visual identity. The current functionality, licensing, and agreed roadmap remain unchanged. As always, we will communicate any future functional or pricing changes separately through our usual channels.
Do we need to update any internal SOPs, work instructions, or training materials that reference the old product name?
Over time, we recommend updating internal documents to reflect the new product name to avoid confusion. We will provide you with the exact new naming, a short description, and a transition note you can add to your SOPs (e.g., “formerly known as …”).
Will KPIs, dashboards, and exported reports we present in meetings be impacted (e.g., logo, headers, references)?
The data, KPIs, and dashboards won’t change. Some visual elements (like the logo or product name in report headers) may show the new branding. The content and data integrity remain exactly the same.
Does the name change affect our licenses, contract terms, or number of seats in any way?
No. Your contract, license scope, user numbers, and SLAs remain unchanged. The name change does not alter your legal or commercial agreement with eschbach.
Is there a migration or cutover plan, and what risks or disruptions should we anticipate for operations?
The change is implemented as a standard update, with minimal risk and no functional migration required. We will share the go-live date, what exactly will change visually, and when you can expect to see the new name, so you can inform your teams in advance.
Quality, EHS, and Regulatory (QA/QC, HSE, Validation)
Do we need to update validation documentation, URS/FS/DS, or qualification/validation reports because of the new name?
A full re-validation is generally not required as long as only the product name changes from Shiftconnector to Seqonis and no functional changes are introduced. Existing documentation remains valid; adding a clarifying reference (e.g., via change control or an addendum) to reflect the new name is recommended.
Will the product name change affect any regulatory filings, audit trails, or GxP documentation that mention the old name?
Regulatory filings and GxP documentation remain valid as long as it is clearly documented that Seqonis is the new name of the system previously validated as Shiftconnector. We recommend adding a formal note/change notification describing the name change and confirming that functionality is unchanged.
Is there an official statement or change notification we can file in our change control system (e.g., for GMP compliance)?
Yes, eschbach will provide an official statement/change notification regarding the product name change that customers can use in their change control systems. This document will clarify that the underlying software platform and functionality are not changed by the renaming.
Will system identifiers (e.g., in audit trails, electronic signatures, or CFR Part 11–relevant records) remain exactly the same?
Yes, technical system identifiers such as system IDs, database IDs, audit trail entries, and electronic signature mechanisms will remain unchanged. Only visible product labels in the user interface and product communication will gradually be updated from Shiftconnector to Seqonis.
IT, Security, and Integration Owners
Will any technical endpoints change (APIs, SSO metadata, IPs, certificates, connectors to SAP/AVEVA/etc.)?
The name change is not intended to modify technical endpoints or integration mechanisms. Your APIs, and SSO configuration will continue to work as configured today. If any endpoint adjustments are needed now or in the future, we will coordinate them with you well in advance.
Do we need to update references to the product name in our CMDB, architecture diagrams, or service catalogs?
Functionally, nothing breaks if you don’t update these immediately. However, for clarity and consistency, we recommend updating your documentation over time to show the new product name (optionally with “formerly [Old Product Name]”) so stakeholders can easily recognize the system.
Will the name change impact our security assessments, vendor risk profiles, or SOC/ISO documentation?
No. The vendor (eschbach), hosting, certifications, controls, and security posture remain the same. Only the product name changes.