Here the starting point is a specific product version that is already in use. New customer requirements and changed guidelines are checked against exactly this version.
Different product versions
Different revisions run at customers. Which evidence belongs to which version is scattered.
Unclear assignment
New requirements are hard to assign to solutions already in use.
Repeated research
Whether action is needed is researched anew with every inquiry.
GUIDED WORKFLOW
One product version is at the center. Below it, three requirements with source, existing assessment, and new review needs. Select a requirement to see the details.
INPUT
{{ cur.eingabe }}
SUPPORT FROM DECOTA
{{ cur.decota }}
YOUR TEAM’S ACTION
{{ cur.team }}
RESULT
{{ cur.ergebnis }}
HERE · STARTING POINT PRODUCT VERSION
You select a product version and see all requirements and guidelines that need to be reviewed again for it.
FOR COMPARISON · STARTING POINT CHANGE
On the guideline page, you start with a changed passage and see the affected product versions and projects.
Review guideline changes →WORK RESULT
For every recorded product version, service, product management, and quality management see the same status. They see what has been verified, what is open, and who is taking care of it.
SERIES P / REVISION 2 · CUSTOMER SITE A
ILLUSTRATIVE EXAMPLEEVIDENCE AVAILABLE
R-019 protection class IP54 · R-044 emergency stop PL d
OPEN REVIEWS
R-027 cold operation −30 °C · R-044 emergency stop PL e
ADAPTATION NEEDS
To be assessed after the open reviews are completed
RESPONSIBILITIES
R-027: quality management, K. Bauer · R-044: control engineering, K. Bauer · Customer information: service engineering, T. RothMeasures such as retrofits or customer information are decided and documented by your team.
BENEFITS
BEFORE
With a new requirement, all product versions are called into question across the board.
AFTER
Only the features with new review needs are reassessed.
Metric: research time per product version
BEFORE
Evidence for a product version is gathered from folders, test reports, and emails.
AFTER
Evidence, assessments, and open items sit with the product version.
Metric: open evidence and repeated reviews
BEFORE
Why a product continues to run at the customer or was adapted is hard to trace later.
AFTER
Review question, assessment, measure, and responsibility are documented per product version.
Metric: product versions with complete review documentation
Your potential time savings
Run your own scenario with your own assumptions in the ROI calculator.
BEFORE THIS
The new review need for R-027 arises from the changed cold operation guideline.
To the application →WHAT COMES NEXT
If the review shows adaptation needs for the product version, it becomes a development task with an owner.
To the application →No. There is no live access, no sensors, and no predictive maintenance. Documented product versions are assessed.
Only the recorded product versions with customer and site. The installed base is not automatically mapped in full.
No. Measures and responsibilities are decided and documented by your team. DECOTA shows what needs to be reviewed and what has already been verified.
Bring a product version that runs at several customers. We show the workflow with your documents or with prepared sample data.
Book a demo