Software shouldn’t require consultants to make it yours.
Implementation is not a statement of work in this product. It is a screen inside it — one you can open on day one and come back to whenever your business changes.
- Create your companyYour organisation, your province, your programme type.
- Choose your productsOperations, Safety & Compliance, or both. Enable the other later.
- Configure your organisationDivisions, branches, departments, roles and permissions.
- Add your peopleWorkers and technicians; user accounts arrive by invitation.
- Import your dataCustomers, sites, assets, people, competencies, training, certificates, price book.
- Configure Operations & SafetyJob types, lifecycle, close-out, hazards, forms, requirements, alerts.
- ValidateOrientra checks your data and names what is wrong, with the record that fixes it.
- Go liveRefused, with the outstanding steps named, until each blocking step is met or deliberately skipped.
Nothing on the checklist can be ticked off
Every step counts real records each time the page loads. “Three people active, two marked as field technicians.” “Two customers, two sites.” “Eleven alert rules active, none evaluated yet.”
Only two things are ever stored: a deliberate skip, recorded with who decided and why, and an acknowledgement for the handful of judgement calls no measurement can answer — nothing can count whether anybody has actually read the safety program.
Your data moves in, and you can undo it
- Nothing is written until you have seen it. The preview and the commit run the same code over the same rows; the only difference is whether it saves.
- A rejected row says why, by line number. One bad row never stops the good ones.
- The same record twice is updated, not duplicated. Every target declares what makes it the same real thing.
- It can be undone. A batch records exactly what it created, and a rollback removes those and nothing else.
Column mapping is suggested by name — and offers nothing when it is unsure, because a wrong guess nobody notices puts a phone number in four hundred serial-number fields.
Row 43: Customer reads “Northgate Propertyy”, which is not one of your customers — create it first, or correct the spelling.
Being straight about implementation
Every vendor in this category promises a fast implementation. We would rather tell you how it actually works.
We do not quote a timeline yet
Orientra does not have enough implementation history to promise you a number of weeks. When we do, it will come from real customers rather than from a marketing page.
The work is mostly your data
Configuration is quick. Getting customers, sites, assets and people in — and correct — is the part that takes real effort, and it depends on what shape your records are in today.
Help is available and it is not mandatory
You can do all of this yourself. If you would rather we did some of it with you, ask — and we will tell you what it costs before you commit to anything.
See the implementation environment before you buy.
It is a real screen in the product, not a slide. We will walk you through it with your own kind of data.