Manufacturing management system case study · Power Apps · SYSPRO · Flexible Metal

A manufacturing management system that puts SYSPRO on the shop floor.

Flexible Metal, part of the Hyspan group, makes metal bellows, hose and tubular assemblies for Tier-1 automotive and off-highway customers. Its ERP processes were disconnected from the floor: inventory updates were manual, PO status was opaque, and scrap reporting needed SYSPRO access most staff didn't have. We built a Power Apps manufacturing management system that posts to SYSPRO through a .NET API and a WCF bridge. It's live and still being enhanced, and a person approves every PO and every supervisor transaction.

Shop-floor run · Scrap reportRunning
Sign-in
Transaction
API
SYSPRO
Audit
Scrap report from work in progress
Defect reason
Bad weld
Source
WIP
Entered by
Floor operator
S
DoneSupervisor
ApproveHold
Nothing posts until a person approvesIllustrative
Before and after

What changed for the shop floor.

BeforeWith the Power Apps system
Inventory updatesManual entry, with errorsFloor staff post their own transactions
PO statusOpaque, chased by phone and spreadsheetVisible in real time
Scrap reportingNeeded direct SYSPRO accessCaptured at source with a standard reason code
Defect dataRecorded on paper, nobody could analyse itDefect trends analysable for the first time
Transfers and cycle countsQueued behind someone with ERP accessPosted by the operator who does the work
ERP integrationWorkarounds creating a second version of the truthOne bridge into SYSPRO business objects
How it works

One app on the floor, SYSPRO behind it.

Operators sign in with Microsoft SSO and see only the modules they're permitted. They pick a transaction on a tablet or desktop, and the app calls a .NET REST API. The API turns the call into SYSPRO business-object XML and posts it through a WCF bridge.

1 · What comes in
Operator signs in with Azure AD SSO
Transfer, cycle count, scrap, PO receipt or inspection
Tablet or admin desktop
2 · Power Apps, .NET API and WCF bridge
Power Apps canvas app, branded to the client
Domain-organised REST endpoints: inventory, purchasing, receiving, supervisor
WCF bridge to SYSPRO e.net, XML both ways
JWT with module-level role-based access
3 · Approvals and notifications in Power Automate
PO approval routing
Scrap reporting notification
Supervisor-only transaction
Supervisor
4 · Posted in
SYSPRO
SQL Server
Power Automate
Azure AD
Transactions, user access records and audit logs are kept in SQL Server for reporting, and labels and QR codes print from the app.
Results

What the floor gets now.

Fewer manual entry errors

Staff record transactions in the app, with warehouse and bin lookups, instead of keying them twice. The project team saw fewer manual entry errors.

Live inventory and PO visibility

Inventory and PO status are visible across all production lines, replacing phone calls and spreadsheet chasing.

Data consistency with SYSPRO

Data consistency is maintained with SYSPRO, because every transaction goes through the business-object bridge rather than around the ERP.

Scrap captured at source

Scrap is reported against eight standard defect reasons, which makes defect trends analysable for the first time.

Quality checks on receipt

PO inspection uses multi-point checklists, with disposition tracking for non-conforming material.

Floor staff post their own work

Transfers, scrap and cycle counts no longer wait for someone with ERP access.

Why it worked

Built around the ERP, not against it.

A bridge, not a workaround

SYSPRO exposes WCF business objects and XML, not REST. The API translates between the two, so the ERP's configuration and data structures stay untouched.

People stay in control

POs route through Power Automate for approval, supervisor transactions are limited to supervisors, and admins grant module access per user.

Simple for the floor

A browser-based app on tablets means operators don't need ERP expertise or licences, and no separate IT ticket is needed to grant access.

FAQ

About this project.

Is the system live?

Yes. It's in production and still being enhanced.

How does Power Apps connect to SYSPRO?

Power Apps calls a .NET Web API. The API sends SYSPRO business-object XML through a WCF bridge to SYSPRO e.net, in both directions, without changing the existing ERP configuration or data structures.

Who approves what?

POs are routed for approval through Power Automate. Supervisor-only transactions are limited to supervisors, and admins decide which modules each person can use.

Talk to us

Want your ERP on the shop floor?

Tell us which transactions your operators can't reach today. We'll show you how a Power Apps layer can post them to your ERP.

Book Appointment
Sahil kataria (1)
Sahil Kataria

Founder and CEO

amit Kumar
Amit Kumar

Chief Sales Officer

Talk To Sales

USA

+1 270-550-1166

flag

+1 270-550-1166

Phil J.
Phil J.Head of Engineering & Technology​
QServices Inc. undertakes every project with a high degree of professionalism. Their communication style is unmatched and they are always available to resolve issues or just discuss the project.​
Assured

Thank You

Thanks, we’ve got your details. A named member of our team will reply within one business day.