Use case
ERP data entry — from manual typing to touchless updates.
Accelerate Shared Service Center keying with automated, validated write-back to your ERP/MES. Werk24 extracts structured data from drawings and RFQs, checks it against your rules, and populates item masters, quotes, and routings — with an audit trail.
The status quo: swivel-chair data entry
Teams copy data from PDFs and emails into ERP screens — item numbers, materials, finishes, tolerances, and supplier quote lines. It is slow, error-prone, and hard to audit. Shared Service Centers soak up repetitive work that could be automated with higher consistency and lower latency.
What it writes — structured, validated fields
- Item master — part number, description, revision, units, weight (if derivable).
- Attributes — material/grade, finish/coating, surface roughness, tolerances.
- Dimensions & threads — normalized units, GD&T essentials, hole/thread tables.
- Quote lines — quantities, lead times, unit prices, validity, supplier IDs.
- Routings (hints) — primary process tags to seed work centers or templates.
- Links & files — source drawing/RFQ, annotated PDFs, confidence, reason codes.
Every field is unit-aware and validated. Low-confidence items are routed to a human queue.
How it works
Map fields, connect, validate, publish — and keep humans in the loop for the edge cases.
Field mapping You
Choose which ERP tables/fields to populate. Define allowed values, rounding ladders, and normalization rules. Provide 30 examples for QA.
Integration Werk24
Connect ingestion (mailbox/SFTP/API) and write-back (REST/ODBC/BAPI). Configure authentication, roles, and regions.
Validation & QA Configurable
Run syntax, unit, and business-rule checks. Low-confidence items go to a review queue with annotated PDFs and suggested fixes.
Typical business rules
- Material in approved list (per customer/category)
- Thread min/max diameter & pitch; class present
- General tolerance detected or explicit per dimension
- Finish/coat specified if corrosion class requires it
- Revision bumps create new item versions
Publish & learn
Write back to ERP, attach sources, and track exceptions.
Outcomes
Touchless where safe, human where it matters — with full traceability.
Cycle time in minutes
Auto-populate fields and generate records quickly; reviewers only handle exceptions.
Lower cost per document
Shift from manual typing to automation; SSCs focus on higher-value work.
Higher data quality
Unit-aware parsing and rule checks reduce typos and mismatched fields.
Full audit trail
Each write-back includes sources, confidence, and reason codes for compliance.
Metrics that matter
Demonstrate impact vs. manual entry and SSC baselines.
- Touchless rate (by field/table and overall).
- Time-to-record (P50/P90 from ingest to ERP write-back).
- Error rate (syntax/unit/business-rule violations).
- Cost per document vs. SSC baseline.
- Exception rate & reviewer throughput.
- Master data freshness (lag from RFQ/drawing to ERP update).
- Audit completeness (share of records with sources & reason codes).
FAQ
Which documents can we ingest?
Native PDFs and scans of drawings, RFQs, supplier quote PDFs, and CSVs. Units are normalized and confidence is provided per item.
Can we block writes for specific fields?
Yes. Configure allow/deny per field and minimum confidence thresholds. Everything else routes to review.
How are revisions handled?
Revision detection triggers versioned updates. Prior values are preserved; differences and sources are attached.
How do we roll this out?
Start with a narrow scope (e.g., fasteners or turned parts) and a single ERP entity. Prove touchless rates & accuracy, then expand coverage.