SteelSync
One hub for the operational work a dealer management system leaves to spreadsheets, email and memory.
What dealers use it for
Shop-floor display boards
Wall screens in every store showing which technician is on which work order, open work orders by age, parts requests waiting, and labor performance, fed live from the dealer management system.
Parts requests
Technicians request parts against an open work order from a tablet. The parts counter sees every request by store, marks it ordered, and the requester is notified.
Approvals
Invoice approval numbers for over-threshold house-account sales, with backups when the approver is out, and a searchable record of every decision.
Expense reports
Receipts photographed as they happen, coded to the general ledger, submitted monthly, routed to the manager and then to accounts payable, and exported as one PDF.
Technician hours and labor analysis
Hours by pay period, billing efficiency and work-order accuracy by store and by technician, and a tool-allowance bonus ledger that pays out from the numbers.
Timecards
Punch in and out, paid time off, store-level approval and a payroll export, with each store in its own time zone.
Telematics and portals
Fleet data from manufacturer telematics, machine activation on manufacturer portals, and phone-system performance by store.
Administration
Users and permissions by store and role, Microsoft 365 single sign-on, an audit log, email delivery records, and data export.
Connectors
SteelSync reads from and, where appropriate, writes to the systems a dealership already runs. Connectors in use today include the DIS Altura dealer management system, CNH FieldOps telematics, Manitou and Tenna fleet data, 3CX phone systems and Microsoft 365. New connectors are built as a dealer needs them.
How it is built and run
- A core platform and a module per dealer. The core provides sign-in, permissions, navigation, scheduled jobs, email, document storage and the connector libraries. Your dealership's features live in a module written for it, in your own code repository.
- Your developer or ours. A dealer with its own developer gets the tools, the template and a staging environment, and ships changes through a reviewed promotion to production. A dealer without one has IronBridge build the module.
- Hosted on Google Cloud. Each environment is isolated, served through Cloudflare, backed up nightly with 30-day retention on top of the cloud provider's own backups, and monitored by IronBridge.
- Supported by the people who built it. Email support during business hours, Mountain Time.