QWorks Integration
Stop entering the same data twice.
The customer can stay in ERP, the product in PLM, production in MES. QWorks uses the context a quality operation needs from the right source.
One case
One case. The right context from five sources.
When a complaint opens, the quality team does not visit five separate systems to collect information. The context comes to the case; where each record lives does not change.
- ERPCustomer · order · shipmentCustomer, shipment and special requirements are not looked up by hand when the case opens.
- PLMPart · revision · configurationThe case opens with the right part and revision; nobody works on the wrong revision.
- MESWork order · operation · lotThe affected lot and production conditions are linked to the root cause.
- QMS · DMSStandard · procedure · controlled documentThe valid procedure and evidence documents stay accessible on the case.
- IAMUser · role · organisationOwner, role and permissions come from the corporate identity infrastructure.
One more system.One more data entry.One more user list.It does not have to be.
Master data stays put
QWorks does not try to become a master data system. The customer stays in ERP, the product in PLM.
Less re-entry
Information that already exists in another system is not retyped by hand for the quality case.
Corporate identity is used
It can work with your existing identity infrastructure; no separate world of users and passwords is created.
What changes
Not a technical connection. Work that disappears.
| Today | The QWorks approach |
|---|---|
| I retype customer information for every case. | ERP context |
| I work with the wrong product revision. | PLM reference |
| I ask production for lot information. | MES context |
| I manage a separate user list. | IAM / SSO |
| My legacy system has no API. | File / batch transfer |
How it connects
Connect the way your infrastructure allows.
API
Data exchange at the moment it is needed.
Event
A notification when something changes at the source.
File · batch
Controlled, scheduled transfer for systems without an API.
SSO · IAM
Existing corporate accounts and organisation context.
From modern APIs to file-based transfer, the integration model that suits your existing infrastructure is agreed together. The method is chosen by business need before technology.
Operating model
Bring the context. Run the work. Link the result.
- 1Bring the context.ERP · PLM · MES · QMS/DMS · IAM
- 2Run the quality work.Owner · SLA · evidence · decision
- 3Link the result.Source system · reporting · learning
Data
Master data stays in the right system.
Source of truth
ERP data stays in ERP, the product stays in PLM. Master data ownership stays with the source system.
Controlled use
QWorks can use the context a quality operation needs through integration, reference or a controlled snapshot approach.
Controlled write-back
Which information flows back to the source system is agreed within the project scope; QWorks does not write on its own.
It can run on-premises; data and integration topology are set up according to your policy. Explore deployment and security →
Let us discuss integration against your own system inventory.
SAP, Logo, Oracle, Teamcenter, 3DEXPERIENCE, a custom MES or an in-house application you have used for years: before any list of brands, let us work out together which context is needed.