Operational ERP software
Run the work your ERP was never built to manage.
Tansi is the operational layer between your ERP and the service outcomes you are accountable for — built to work with the system you have already invested in.
Certifications and independent audit
- SOC 2 Type IIIndependently audited. The report is available on request.
- US data residencyHosted in Azure South Central US, San Antonio, Texas.
Operational ERP
Two systems, two jobs
You already own one of these. You probably do not own the other.
Tansi does not compete with your ERP for the same ground. It picks up where the ledger stops.
Your ERP ownsMoney and people
- General ledger, budgets and cost centers
- Payroll and employee records
- Purchasing, invoices and accounts payable
- Fixed-asset value and depreciation
Tansi ownsThe work
- Where the asset is, and what condition it is in
- Who is qualified to touch it today, and who is not
- The inspection, the finding and the corrective action
- Stock on hand, consumption, lot and expiry
- The evidence that all of it actually happened
Your ERP answers what it cost and who is on staff. It answers those questions well. It was never asked what happened in the field on Tuesday.
What an operational ERP is
A traditional ERP is the system of record for money and people. General ledger, payroll, purchasing, budgets. It answers what something cost and who is on staff, and it answers those questions well.
An operational ERP is the system of record for the work itself. What you own and where it is. Who is qualified to touch it. What was inspected, what was found, what was fixed, what is on the shelf — and whether any of it can be proven six months later when somebody asks.
Most agencies already run the first one. Almost nobody runs the second. That work lives in spreadsheets, paper forms, inboxes and a handful of single-purpose tools, and it gets reassembled by hand every time a regulator, an auditor or a council member asks a question. Tansi is the second system, and it is built to sit on top of the first rather than replace it.
What that changes on an ordinary Tuesday
The field and the office see the same thing
What a crew records on a tablet at seven in the morning is what leadership sees a minute later. No overnight batch, no one retyping it, no spreadsheet sitting in the middle of it.
One platform instead of nine
Mobile assets, workforce readiness, field execution and safety compliance in one place. Most agencies get here by buying a tool per problem, then buying integrations to make them speak.
Nothing gets replaced
Your ERP keeps doing what it does well. Tansi is configured rather than custom-built — deployed rapidly, hosted in the United States, and live without a consulting engagement or a new procurement.
In practice
Pick one and see how it actually works.
Create and manage projects, and the duties inside them
A project is set up once: its locations, its phases, the crews and organizations working on it, and the duties the work breaks down into. Assign someone a duty and every requirement it carries comes with it — licenses, training, clearances. Change a requirement once and it reaches everyone holding that duty. Nobody rebuilds a list.
Track every asset and who it is assigned to
One register for everything you own and everything you hold — where it is, what condition it is in, its service history, and the crew or person responsible for it right now. Assignments are records rather than notes, so “who had it last” has an answer, and an asset that carries a requirement cannot be handed to somebody who does not hold it.
Manage contractor compliance and assign them to work
On most operations the people who are not on your payroll outnumber the people who are, and they are the ones you know least about. Most systems treat them as additional user accounts. Tansi onboards a contractor as an organization — its insurance, its prequalification, its safety program — and then its workers, their duties, and the requirements each duty carries. You can answer “is this crew cleared to be on site today” without making a phone call. Once the organization is compliant, its crews are assigned to projects and duties the same way your own people are.
Deliver training and hold the evidence it landed
Orientation, mandatory training and refreshers delivered in the platform, with a completion record per person, per module, per date. Certifications carry expiry dates, so a renewal surfaces before it lapses rather than after. Training attached to a duty is assigned the moment the duty is.
Assign documents, forms and workflows
Build the form once, then decide who completes it and what happens when they do. Routing by role, organization, status or priority. Sequential and parallel approvals, escalation when something sits too long, and time tracked against the project on the same record as the work.
It works where there is no signal
Forms and inspections run fully offline and sync when a connection returns. Proven on a mountain corridor where competency had to be verified in the field with no network at all.
One record, not four
An incident report on its own is a note that something went wrong. The value is in what follows, and that is usually where it falls apart: the investigation lives in a document, the photographs on somebody’s phone, and the corrective action in a spreadsheet nobody revisits. In Tansi they are one record, attached to the asset it happened to and closed out by a named person on a date.
Every report in one place, produced from the record
Role-based dashboards, saved reports, exception reporting and scheduled exports — all built from the operational record rather than assembled by hand when somebody asks. When a funder, a regulator or a council member wants an answer, it is a filter rather than a three-week project.
Reach everyone who needs to know, and show that they got it
SMS, email and in-app messages to your whole workforce or any segment of it — one site, one shift, a contractor’s crew, or everyone holding a certificate that expires this month. Delivery comes back to the record, so “they were notified” is something you can produce rather than something you assert. The same lists serve an emergency and the routine notice, so nobody maintains two of them.
Score a document against your own standard, then work the gaps to closure
Upload a contractor’s safety program, a policy or a procedure and Tansi checks it against your source of truth — your standard, not a generic checklist. What is missing comes back as findings, and each finding is assigned and tracked, so a gap analysis ends in corrective actions that close rather than a report nobody reads.
The platform
What is in the platform
Asset and inventory management
Know what you own, where it is and who is qualified to operate it.
Maintenance management (CMMS)
Preventive schedules, work orders and defect reporting on the asset record.
Client and constituent management (CRM)
Contacts, outreach and member communication on the operational record.
Contractor compliance management
Contractor organizations onboarded as entities, with their workers and duties.
Digital forms and workflow automation
Capture and routing that runs offline and syncs when signal returns.
Gap analysis and compliance readiness (GAPit)
Upload a document, let AI score it against your standard, and close the gaps it finds.
Human resources and workforce management
Job board, applicant onboarding and employee records through to duties.
Incident reporting and investigation
Report, investigate, find root cause and close the action in one record.
Learning management system (LMS)
Training delivered, with a record per person, module and date.
Mass notification and communications
SMS and email to your whole workforce or any segment of it.
Purchasing and inventory replenishment
Predictive ordering, purchase orders, transfers and warehouse operations.
Regulatory compliance and audit evidence
Registers and corrective actions held in the operational record.
Reporting and business intelligence
KPIs, geographic reporting and workforce analytics, drawn from the live record.
Safety data sheets (SDS) and chemical management
Upload a sheet, get a register, print the labels and put the right SDS in front of the right crew.
Scheduling and dispatch
Assignment that respects who is actually certified.
Service requests and help desk
Service requests and escalation, not an inbox nobody owns.
Vendor directory and public portal
A public directory, profiles and a mobile app on your operational data.
Workforce participation and demographics
Who is working, where, and what the funder or the regulator needs reported.
Templates
Existing Tansi modules, already configured for a type of organization. Same platform and the same record, set up for the way that organization works.
Property management
Buildings, units, tenants, repairs and inspections on one record.
What stays, what moves
Keep your ERP
What stays where it is, and what moves.
Four of these your ERP does better than we would, and four you already half-own. The rest it was never built to run. Select a band to fold it away.
| Need | Your ERP | Tansi |
|---|---|---|
| Finance and accounting | Strong core capability | No ledger, no journal entries. Tansi reads cost codes from it. |
| Payables and invoicing | Strong | Tansi issues the operational PO and the transfer. Your ERP carries the commitment and pays the invoice. |
| Payroll, benefits and HRIS | Strong | Tansi holds duties and qualifications, not compensation. |
| Budgets and cost centers | Strong | Tansi tags work to them so cost lands in the right place. |
| Assets | Book value, capitalization and depreciation | Where it is, what condition it is in, who is qualified to operate it and what it is due for — a register crews work from rather than one reconciled once a year. |
| Inventory | Warehouse valuation and the effect on the ledger | Operational stock at the point of use — lot, expiry, consumption and cold chain. |
| Purchasing and replenishment | The financial commitment, the approval and the payment | Predictive ordering from real consumption, operational purchase orders and transfers between sites — so stock moves before a location runs out. |
| Workforce | The person, the position and the pay | The duty, the qualifications it requires, whether they are current today, and the expiry notification that goes out before one lapses. |
| Maintenance management (CMMS) | Varies by vendor, usually a bolt-on | Preventive schedules, work orders and defect reporting on the asset record. |
| Field execution | Limited, or built as custom development | Mobile-first capture, built for how crews actually work. |
| Inspections and forms | Usually custom development or a separate tool | Configurable forms with routing, approvals and signatures. |
| Offline capability | Rare, or partial | Full offline capture, syncing in order on reconnection. |
| Safety compliance and audit evidence | Usually needs add-ons | Registers built from live operational data, exportable on demand. |
| Safety data sheets and chemical management | Not addressed | Upload a sheet, get the register, print the labels and put the right SDS in front of the right crew. |
| Gap analysis and compliance readiness | Not addressed | Score a document against your own standard, then work the gaps through to closure. |
| Training and certification expiry | Basic, or a separate module | Native LMS, with a record per person, module and date, and expiry surfaced before it lapses. |
| Scheduling and dispatch | Knows availability | Assignment that respects who is actually certified. |
| Contractor compliance | Contractors treated as extra user accounts | Organizations, insurance, prequalification, their workers and the duties they hold. |
| Incident to corrective action | Reporting only, if present | Investigation, root cause and closure on one record. |
| Mass notification | Basic workflow alerts | SMS, email and in-app to any segment, with delivery confirmed rather than assumed. |
| Workforce participation and demographics | Custom reports, assembled after the fact | Tribal and local participation reported from the work itself, on any day of the month. |
| Time to live | Months to years | Days to weeks, configured rather than developed. |
Can integrate with PeopleSoft today, and with other systems of record on the same pattern — Tansi reads what it needs and writes back what your ERP expects.
After you sign
What working with us is like
The software is half of it. The other half is what happens after you sign.
It gets built the way you work
Roles, forms, routing, approval chains, certification rules, dashboards and reports are configured without a developer. Your policy changes the day you decide it.
When something genuinely is not there, it gets built. That is not a promise, it is the record: the platform was adapted inside weeks during a public health emergency to run testing administration and vaccination verification, and a meaningful share of what is in Tansi today exists because a client asked for it.
The training is built for your operation, not bought off a shelf
Courses are written around your operations, your roles and the way your workforce actually uses the platform — then loaded into the LMS during setup, rather than handed over as a slide deck somebody has to deliver.
Existing crews work through it at their own pace, on shift or off. A new hire arrives to a path that is already laid out: what their duties require, in order, with completion recorded per person, module and date.
Support that reaches someone who can act
Support is handled in-house. Calls are answered by a person in the United States and go directly to the people who build and maintain the platform.
Not outsourced, not a script, not a chatbot standing between you and an answer.
Four severity levels · 24/7
Escalation that ends with a person
Issues are triaged across four severity levels and supported around the clock. Escalation runs to engineering and then to leadership, and unresolved issues do not get parked.
You get the people who wrote the code instead of four layers of account management.
There is no version of Tansi where your agency is too small to matter.
Who it is for
Built for how public sector work actually gets done
From cities and public works to utilities, public safety, healthcare, energy and Tribal governments, Tansi runs the work your ERP and point tools leave on the table.
- Cities and municipalitiesCrews, facilities, permits, contractor oversight and the report that goes to council.
- Public worksFleet, facilities, seasonal crews and contractors on one register.
- UtilitiesDistributed assets, credentialed work and the evidence a regulator expects.
- Public safetyCertification currency, training evidence and reaching people in minutes.
- Tribal governmentsProgram operations, assets and workforce, with data governance taken seriously.
- K-12 and higher educationBackground checks, contractor access, mandatory training and facilities.
- Healthcare and health authoritiesMedical supplies, medications and the ordering that keeps service points stocked.
- Nonprofits and NGOsVolunteers and staff on one standard, and reporting a funder will accept.
- Industrial and constructionLarge mobile workforces, multi-site projects and heavy regulatory exposure.
- Oil, gas and energyContractor-heavy workforces, remote sites and competency verified in the field.
- Property managementBuildings, units, tenants, repairs and inspections on one record.
- Everything in betweenNot sector software. An operational layer, configured to the work you do.
Where ERP ends, Tansi begins.
See it running on your own operation
Bring us a workflow that is currently held together by a spreadsheet and a shared drive, and we will show you what it looks like in Tansi. No scripted demo. No discovery fee.