Features
Everything your field operation needs, in one platform
Flacron Energy replaces the paper checklists, spreadsheets, and shared drives behind field inspection, maintenance, and safety with one auditable record per asset. Here is every module, grouped by the work it supports.
7-day free trial · card required · nothing charged until day 7
The workflow every module serves
- Asset registry
- Inspection
- Deficiency
- Work order
- Repair
- Verification
- Audit
Area 1
The register
What you own, where it is, and how to find it again from the equipment itself.
Your estate in its real shape
Regions, facilities, areas, assets, and sub-assets — each its own record, each with its own history.
Actual product screen · Acme Energy demo workspace
- OrganizationABC Energy
Your tenant. Every record below it is scoped to it and invisible to anyone else.
- RegionWashington Region
Optional. Group sites geographically, then filter and report on the group.
- FacilityTacoma Plant
Its own address, GPS, timezone, sector, and active/inactive status.
- AreaCompressor Station 2
A named, coded subdivision of a facility — a unit, a deck, a yard.
- AssetCompressor C-204
The equipment itself, with its tag, QR label, and full history.
- Sub-assetRelief valve PSV-114
Hung off its parent, so a component's record rolls up to the unit it serves.
Region is optional, and a facility without one is a perfectly valid facility — a single-site tenant never has to invent a tier it does not have. Regions can be added to an estate that already exists: the facility register can be filtered to exactly the sites not yet filed under one.
Asset management
One record per piece of equipment, holding everything the rest of the platform hangs off.
- Tag, category, manufacturer, model, serial number, and installation date
- Operational status (healthy, warning, critical) and condition, set by a person
- A single history of inspections, work orders, readings, and status changes
Sites and hierarchy
Your estate in its real shape rather than a flat list of equipment.
- Organization → optional region → facility → area → asset → sub-asset
- Facilities carry address, GPS, timezone, sector, and active status
- Sub-assets roll up to the unit they serve
QR identification
Scan the label on the equipment and land on its record.
- A QR label generated per asset — print it or download the SVG
- Opens the asset's history, open work, and the inspection to run
- A scan from outside your company answers as if the asset did not exist
3D facility view
A static digital twin of the site, with hotspots that open the asset behind them.
- A 3D scene per facility, on the web and in the mobile app
- Hotspots placed on equipment link straight to its asset record
- Static by design — no live telemetry is claimed or implied
Every field on an asset record
- Asset tag
- Unique within the company, and what the QR label resolves to
- Category
- From the standard list, or your own value
- Manufacturer · Model
- Free text, searchable across the register
- Serial number
- Recorded per unit, not per model
- Installation date
- The clock every age-based judgement runs off
- Facility · Area
- Where it physically sits in the hierarchy
- GPS coordinates
- Latitude and longitude, set on the asset itself
- Parent asset
- Sub-assemblies hang off the unit they belong to
- Operational status
- Healthy, Warning, or Critical
- Condition
- Excellent, Good, Fair, Poor, or Critical
- Photos
- Uploaded to the asset and served over short-lived signed URLs
- Manuals & documents
- Linked from the controlled document library
- QR / barcode label
- Generated per asset — print it or download the SVG, and it stays opaque to outsiders
- History
- Inspections, work orders, readings, and status changes in order
Area 2
In the field
The work done standing in front of the asset — with gloves on and, often, no signal.
Inspections that work where the equipment is
Run on a phone or tablet at the asset, with or without signal, and reviewed on the web.
Actual product screen · Acme Energy demo workspace
Field app sync queue
Inspections and checklists
Your own procedure as a checklist, run against a specific asset.
- Custom, versioned templates with pass/fail, numeric, text, and select items
- Photos, video, voice notes, and meter readings captured on the run
- Completed with a digital signature, GPS, and timestamps
Offline-first mobile app
A full inspection round with the radio off, synchronised when signal returns.
- Work is written to a real on-device database first, not a cached page
- Pending changes sit in a visible outbox — nothing is silently dropped
- Sync reconciles against the server record instead of overwriting it
AI photo and video analysis
The model looks at the evidence on the way in and hands a person a shorter list.
- Corrosion, damage, and possible leaks identified, each with a confidence
- Findings drawn as annotations on the image, where the model saw them
- Advisory only — a person confirms or overrides every result
AR measurement and annotation
Measure and mark up the equipment instead of describing it in a comment.
- Take an AR or manual dimension and attach it to the inspection
- Draw the defect directly on the photo
- Tag captured media as before or after
Everything an inspection can capture
- Custom templates
- Build your own checklist and version it. Each run stores a snapshot of the template it used, so editing a template never rewrites history.
- Four response types
- Pass/fail, numeric measurement, free text, and select-one — each item optionally required before the inspection can be completed.
- Photos and video
- Captured against a specific checklist item, tagged before or after, with their own GPS and capture time.
- On-photo annotation
- Draw the defect on the image itself rather than describing it in a comment.
- AR and manual measurement
- Take a dimension on the equipment and attach it to the record.
- Voice notes
- For the things nobody types with gloves on. Queued and uploaded like any other media.
- Meter readings
- Pressure, temperature, vibration, noise, leak observed, operational status, and condition, with recommendations and a priority.
- Digital signature
- Captured at completion and held against the inspector who gave it.
- GPS and timestamps
- Location, device id, start and completion times, and the client's own clock, recorded on every run.
- Offline from end to end
- The whole round works with the radio off. Nothing waits for a network to be accepted.
- Findings become work
- A work order raised from an inspection keeps a link back to it, so the fix and the failure stay one story.
The rule the AI is built on
Every AI result is advisory and reviewable. It arrives unreviewed, is marked as the model's output with the model name recorded against it, and an authorised user confirms or overrides it. A report cannot be finalised on the model's say-so.
Area 3
Maintenance and permits
How a finding becomes authorised, assigned, and signed-off work.
How a failed check becomes closed-out work
One asset, five records, and a different accountable person at each step.
- 1
Inspections
INS-2291
Seat leak fails on PSV-114
A monthly PSV round is completed offline at Tank Farm A. The failed step captures two photos, an 11.9 bar reading, and the inspector's signature.
- who
- Field Inspector
- gate
- inspections.write
- 2
Work orders
WO-1042
The finding becomes assigned work
Operations raises a work order against the same asset and assigns it. The technician accepts, progresses it, and submits it for review — but cannot close it.
- who
- Operations Manager
- gate
- work_orders.write
- 3
Permits
PTW-118
Hot work is authorised in writing
The valve replacement needs isolation and hot work, so a permit is raised from a template and approved before anyone lifts a spanner.
- who
- HSE Manager
- gate
- permits.approve
- 4
Work orders
WO-1042
Someone other than the doer signs it off
Closure is a separate permission from doing the work. The person who turned the bolts is not the person who accepts the job as finished.
- who
- Operations Manager
- gate
- work_orders.close
- 5
Reports
RPT-0043
The whole chain exports as one artifact
A report is generated from the actual records — not retyped — reviewed by a human, attested, and frozen as a PDF, Word, or Excel file.
- who
- HSE Manager
- gate
- reports.generate
Work orders
A failed check turned into assigned work, with a link back to what found it.
- Raised from an inspection or on its own, with priority and due date
- Assigned to a named technician, who accepts and progresses it
- Closure is a separate permission — the doer never signs it off
Preventive maintenance plans
Recurring plans that raise the inspection or work order themselves.
- Daily, weekly, or calendar-monthly intervals
- A missed plan raises one overdue record, never a backlog of backdated ones
- Generated work is ordinary work — permits and sign-off still apply
Permit to work
The written authorisation that has to exist before the job starts.
- Hot work, confined space, electrical isolation, excavation, height, and general maintenance
- Approved, acknowledged, activated, suspended, resumed, revoked, and closed
- Approval is its own permission, separate from raising the permit
What maintenance plans and work orders record
- Recurring plans
- A plan repeats on a daily, weekly, or calendar-monthly interval and raises the record itself — an inspection against a checklist, or a work order.
- Calendar months, not 30 days
- A monthly round stays in the month it covers. Thirty-day arithmetic drifts it about five days a year until the record no longer says what it was meant to.
- Notice before the due date
- Set how many days early a plan raises its record, so a crew has warning instead of finding the job on the morning it is due.
- Catches up, never backfills
- A plan that has been missed raises one overdue record and moves on, rather than a month of backdated ones nobody will action.
- Raised from the failure
- A work order created from an inspection keeps the link back to the run that found it.
- Assigned to a technician
- A named assignee, with the assignment recorded as its own event.
- Priority and due date
- Set when it is raised and changeable with an audit entry.
- Accepted, then progressed
- The technician accepts the job and moves it forward — the status is theirs to advance.
- Permit first, where it is needed
- Hot work, confined space, electrical isolation, excavation, work at height, and general maintenance permits, approved before the spanner comes out.
- Labor hours and materials
- Recorded on the order, so the cost of the fix sits next to the fix.
- Submitted for review, not self-closed
- Closure is a separate permission. Doing the work never includes signing it off.
- Downtime recorded on the job
- When the asset went out of service and when it came back, held on the order that took it down.
- Kept on the asset
- Every order stays in that asset's history and feeds the maintenance report.
Area 4
Safety and compliance
Incidents, their corrective actions, and the documents an auditor will ask for.
From finding to verified closure
The states an incident moves through, with the separate person who accepts the fix.
- 1
Finding detected
reportedA failed checklist step, an out-of-range reading, or a hazard raised straight from the phone — near miss, unsafe condition, gas leak, spill, equipment failure, injury.
- 2
Risk level assigned
under_reviewLow, medium, high, or critical. Set by the person triaging it, and filterable, so the critical ones are never buried in a list sorted by date.
- 3
Corrective action created
corrective_actionA described piece of work attached to the finding, with its own priority — not a comment thread that somebody has to interpret later.
- 4
Owner assigned
A named person, not a team inbox. The assignment itself is a recorded event with who made it and when.
- 5
Due date established
A date the action is measured against, so overdue is a fact rather than an opinion.
- 6
Evidence uploaded
Photos and files attached to the finding, stored in your own bucket and served through short-lived signed URLs rather than public links.
- 7
Verified by someone else
verificationOnce the corrective actions are complete, a safety manager records whether they were effective, with notes and evidence. Whoever completed the work cannot sign it off, an ineffective result sends it back for rework, and the incident cannot be resolved without a passing check.
- 8
Finding closed
closedClosure is its own gate, its own timestamp, and its own actor.
- 9
Audit trail preserved
Every transition above is written to the audit log with the actor, the target record, and the time — readable by your own administrators and exportable as CSV.
Safety reporting
Incidents and hazards logged from the field and driven to closure.
- Near miss, unsafe condition, gas leak, spill, equipment failure, and injury
- Low, medium, high, or critical risk, set during triage
- Reported → under review → corrective action → resolved → closed
Corrective actions
The work a finding demands, owned by one person and verified by another.
- Attached to the finding with a description, priority, and due date
- Assigned to a named owner, with the assignment recorded
- Completion notes accepted under a separate permission
Controlled documents
SOPs, manuals, policies, drawings, and certificates in one library.
- The real file stored and served through expiring links
- Linked from the assets they describe
- Scoped to your company like every other record
Training modules
Step-by-step modules with per-user progress, recorded alongside the work.
- Structured modules a user works through step by step
- Progress tracked per person
- Competence kept in the same system as the jobs
Area 5
Insight and reporting
The records turned into something a manager, a client, or a regulator can read.
Reports generated from the record
A real, finalized inspection report — generated, attested by a named person, and frozen.
A finalized inspection report generated by Flacron Energy
Dashboards
The state of the estate computed from live records, not last month's spreadsheet.
- Inspection compliance, completion and finding-closure rates
- Open, overdue and completed work, with average resolution time
- Filter by facility, area, asset, category, status, person, severity, and date
AI report generation
Audit-ready reports generated from the stored records, never retyped.
- An AI-drafted summary, findings, recommendations, and risk score — except the audit report, whose summary is counted from the log
- Attested by a named person, then frozen — changes become revisions
- Exported as PDF, Word, Excel, or CSV
Notifications
Assignments reach people without anybody refreshing a list.
- Push to registered devices
- An in-app inbox of what needs attention
All ten report types, and what every export carries
- Inspection report
- One inspection run, with its checklist responses, readings, attached-media records, and signature.
- Maintenance report
- One work order: what was raised, who did it, hours and materials, how it closed.
- Safety report
- One incident or observation, with its category, severity, and corrective actions.
- Asset health report
- One asset: its condition and status, with the inspections and work orders behind both.
- Asset history report
- One asset's timeline — inspections, work orders, status and condition changes, and readings.
- Findings report
- Failed Pass/Fail checks on inspections completed in a date range, for one site or all, and whether a work order raised from each has closed.
- Corrective action report
- Safety corrective actions raised in a date range, with owner, due date, status, an overdue flag, and completion.
- Site compliance report
- Per facility over the last 7, 30, or 90 days: scheduled inspections due against those done on time, overdue inspections, and open findings.
- Audit report
- The audit log for a date range, filtered like the audit viewer. Its summary is counted, not AI-written. Needs a plan with audit export.
- Executive summary
- The version for people who will not open the detail — written from the same records.
- Exported as PDF, Word, Excel, or CSV
- Carries your company details, taken from the record rather than typed in
- Single-record reports list every timestamp, reading, signature, and attached photo on the source record
- Generated from the stored records — never retyped from them
- Attested by a named person before it can be finalized
- Frozen once finalized: a change means a new revision, not a quiet edit
- The audit trail exports separately as CSV
Every dashboard metric and filter
On the dashboard today
- Total assets
- Critical assets
- Asset condition split
- Assets by category
- Assets by facility
- Pending inspections
- Inspection compliance
- Inspection completion rate
- Finding closure rate
- Inspections by status
- Open and overdue work orders
- Completed work orders
- Average resolution time
- Work orders by status
- Overdue corrective actions
- Monthly activity
- Active permits
- Safety incidents
- Incidents by type
- Reports generated
- Draft vs finalized reports
- Users and active users
- Roles configured
- Audit events over time
Filter by
- Facility
- Area
- Asset
- Category
- Status
- Inspector
- Technician
- Severity
- Reporter
- Date range
Compliance is on-time completion of scheduled inspections; a finding closes when a work order raised from it closes. When nothing was due in the period a rate shows a dash, not 0% — the two are different facts. Each tile is shown only to roles with permission for its module.
Area 6
Administration
Who can do what, and the record of what they did.
Users, roles, and permissions
Seven role templates over a published permission catalog, and your own on top.
- Invite users and set their status
- Roles are data — build and name your own without a release
- Every route checked by the API, never only hidden in the interface
Audit trail
Who did what, to which record, and when — readable by your own administrators.
- Creates, updates, transitions, and refused access attempts
- Filterable by actor, action, target, and date
- CSV export of the trail on Enterprise
Company settings and billing
Your organization's details, logo, and subscription in one place.
- Company profile and logo
- Require two-step verification for everyone
- Plan, trial, and usage against each allowance
The seven built-in roles, the permission each module checks, and how separation of duties is enforced are on the security overview.
Not yet
On the roadmap — not shipped
The architecture keeps the boundaries these would attach to, so they are additions rather than a redesign. None of them exists today, and we would rather you read that here than discover it later.
On the roadmap — not shipped
- Outbound webhooks
- ERP and CMMS connectors
- GIS and mapping systems
- IoT sensors and SCADA telemetry
- Power BI and warehouse connectors
- Predictive maintenance insights
- Natural-language search across inspections
If one of these decides your purchase, tell us which one — it is the fastest way to move it up the list.
Check the list against your own site
Register an asset and run an inspection against it, or have us show your team the modules that matter to your site. A tag on a card above means that module needs a higher plan.
7-day free trial · card required · nothing charged until day 7