What’s known
- Procedures and rules
- How work is really done
- Judgement people carry
The Nexefy Platform
One engine. Four steps. Everything on the record.
The Intelligence Engine holds your knowledge once, with its sources. This is one client’s map: eight documents, 408 linked items, four findings. Spin it, or open a finding.
8 documents408 linked items4 findings
- Source document
- Knowledge
- Roles
- People
- Evidence
- Finding
Finding
Waiting for a named reviewer
Illustrative example
Held once, with its sources.
The engine reads your documents, procedures, existing training and the wording of the rules you work to, and turns them into linked knowledge. A temperature written in three documents becomes one setting with three statements, and when they disagree, the engine shows it.
- Held onceEvery item keeps the source pages it came from.
- People dataRoles, competence and sign-offs, held as evidence.
- A findings registerEvery conflict and gap, with its owner and sign-off.
- Screens and an APIFor your people, and for Teams, Copilot or any agent.
One map underneath
We don’t map documents. We map what your operation knows.
Each client has one map. It links knowledge to the roles that need it, the people who hold it and the evidence that they can do it. The four steps are four things we do to that one map.
- Findchecks it
- Fixfills it
- Delivermoves it to people
- Improvekeeps it true
What each job needs
- What to know
- What to be able to do
- For every position
Who holds it
- Who can do it
- Who can teach it
- When they might leave
How you know
- Training and assessment
- Sign-offs
- Re-certification
Criticality runs across all four
SafetyQualityEnvironment
The four steps
Find, Fix, Deliver, Improve.
Each step does its own job, a person decides at every step, and the record builds as it goes. Improve feeds the next Find.
Find
Detect and sign. The engine finds documents that disagree, stale versions and missing references. Mapper finds steps no training reaches and assessment questions with no source. Each finding carries its source quote, a severity, an owner and a due date.
- Who decides
- a named reviewer signs each finding.
- On the record
- which version was checked, what was wrong, who signed.
MapperConflict
Two documents disagree on a restart temperature
Pump restart procedure v12, step 14“Restart once below 85°C.”
Training module 3“Restart once below 90°C.”
Signed by a named reviewer · owner: area owner
Illustrative example
Fix
Correct at the source. Creator suggests the change and the document’s owner approves it in their own system. Short interviews capture what experienced people know. Where learning is missing, we start from the task, choose the tool, then build or source it.
- Who decides
- the owner approves; the expert confirms what was captured.
- On the record
- what changed, who approved it.
Creator, with microVerse®Suggested change
Restart once below 90°C.
Restart once below 85°C, as procedure v12 step 14.
Captured from a maintainer, 31 years on site“Listen for a high whine in the first minute after a seal change.”
Approved by the document owner · expert confirmed
Illustrative example
Deliver
Get it to people. The corrected knowledge reaches the people who need it, shaped for the job: a full programme, a guide at the task, practice in a safe world or a daily habit. Tutor answers questions only from approved knowledge.
- Who decides
- an assessor signs who’s ready.
- On the record
- who was trained on which version, how they were assessed, who signed them off.
Launcher, TutorTrainee · haul crew B
- Guide at the taskDigital Guide, on shift
- PractisedmicroVerse, 6 runs
- Assessed on siteAgainst version 13
- Signed offBy a named assessor
Night shift asks Tutor“What temperature before restart?” → 85°C, from procedure v13, step 14.
Illustrative example
Improve
Measure and re-check. InSights shows the effect on capability, safety and compliance. When a document or a person changes, the platform re-checks only what went stale, because every check records the versions it was built on.
- Who decides
- owners close what’s still open.
- On the record
- what was re-checked, what’s open and who owns it.
InSightsChange
Re-checking the 4 things it touches
- Training module 3Still agrees
- Digital Guide, pump restartUpdated · owner approved
- Assessment, question 12Open · training lead
- 14 people signed off on v13Refresher queued
Illustrative example
On the record
Every step signed, dated and pinned to a version.
Every step leaves a record made at the time, signed by competent people and tied to the exact version it used. It’s evidence you can stand behind, for an audit, a regulator or your board.
Record 0314-118Signed
- Who
- Trainee, haul crew B
- Knowledge
- Pump restart procedure, version 3
- How
- Practised in microVerse, assessed on site
- Signed off
- A named assessor
- When
- 14 March
“On 14 March, this person was trained and assessed against version 3 of the procedure, and signed off by a named assessor.”
Underneath the steps
Six products, working as one.
The Intelligence Engine sits under everything, and each of the other five does one job in one step. You don’t buy them separately: they come together as the Nexefy Platform.
- Find
- Fix
- Deliver
- Improve
Mapper
Holds the frameworks you must meet: regulation, standards, units of competency and critical controls. Checks each requirement is evidenced, finds the gaps and hands them to Creator.
Already using Mapper? Talk to us about your account.
Creator
Closes the gaps Mapper finds. Suggests fixes to source documents for their owners to approve, or builds the learning: a microVerse scene, a course or a Digital Guide.
Launcher
Ships the right learning to the right channel, including third-party tools such as simulators, and works out what each person needs next.
Tutor
Answers questions from approved knowledge and shows where every answer came from. Helps inside a course, guides a process or a VR scene, and works in Teams.
InSights
Where the data lands: sessions, findings, risk, competence and compliance evidence, with rubric scoring and reports. In use today with Metro Trains Melbourne.
Intelligence Engine
Reads documents, procedures, training and rules into linked knowledge, held once with its sources, and serves it to every product.
Inside FixmicroVerse®: the same world, every run.
microVerse is our 3D world. It renders the same every time, so hands-on tasks can be practised, assessed and repeated, from a learner’s first intersection to a helicopter on the pad. Every scene is structured data the platform can read and check.
60+VR modules in rail and Defence
85%Lower training costs, at best
67%Fewer incidents
People in the loop
Our platform drafts. People decide.
Nothing we find, create or change counts until a named person has approved it. That means your own people, working inside the software. Built in, always on.
Every piece of knowledge has a standing
Captured experienceObservation
“After a seal change, listen for a high whine in the first minute. That usually means air in the casing: stop and re-prime.”
Captured from a maintainer with 31 years on site
Conflicts go to an owner
Anything that disagrees with another source is raised for a person to resolve. It’s never quietly overwritten.
Experience stays labelled
Captured know-how keeps who said it and who confirmed it, and never quietly becomes an instruction.
Only approved knowledge reaches people
Tutor answers only from what’s been signed, and shows where every answer came from.
- AdministratorsSet it up
- Knowledge ownersApprove
- ExpertsConfirm what they know
- Everyone elseUses it, and gets answers they can trust
+14
Want extra hands? Our analysts, instructional designers and 3D artists work inside the same platform, with the same approvals and the same record. Optional, and always quoted separately.
Talk to usFrom task to tool
Start from the task. Then choose the tool.
“Shaped for the job” needs a method behind it. We profile what each task needs and match the simplest tool that meets it, ours or someone else’s, simulators included.
- Start with the taskThe tasks come from your own procedures, which is exactly what Find produces.
- Profile what it needsHands-on feel, a realistic environment, the consequence of an error, teamwork, how often it’s done and how it’s assessed.
- Match the toolThe simplest tool that meets the profile, and a record of which tool trained which task.
A rail example: a freight academy’s driver training
| Task | What the training must provide | Likely tool |
|---|---|---|
| Roll-by inspection | Seeing many faults, safely and repeatably | VR in microVerse |
| Decoupling and protection steps | Exact steps in the right order, hands on | Digital Guide then VR or part-task practice |
| Train handling at yard access points | Physics, feel and consequence | A simulator from a specialist supplier |
| Final sign-off | Real conditions and a named assessor | On the job, with a mentor |
We stay tool-neutral. Recommending a tool we don’t sell makes every other recommendation more credible. See it in practice in Aurizon Digital Guides and Track Lookout.
Know it’s right.Know they’re ready.
Start with one area and see what it finds.
Tell us where the risk sits. We’ll scope a first pass on the area that matters most to you.