From data to action, in five steps.
Stratforth does more than hold your data. It combines it, shapes it into something new, and turns it into decisions and actions.
01
Combine
Bring in your own data and the outside risk picture, including Stratforth's own risk feed.
- Every source becomes versioned objects.
- You keep the credentials to your own systems.
Upload
- Site register1,240 rows
- Supplier list318 rows
- Inspection results96 rows
Becomes: Sites Suppliers Inspections
Each upload adds a new version. Nothing is overwritten.
Stream
- Platform sensors60 a minute
- Vessel positionsEvery 30 s
- Vehicle positionsEvery 10 s
Becomes: Assets Vessels Vehicles
Events arrive as they happen.
Push
- Maintenance systemWork orders
- Booking systemTrips
- Incident systemReports
Becomes: Work orders Travellers Incidents
Your systems push records with keys you issue and can revoke.
Sync
- Asset registerIn step
- Staff directoryIn step
- Supplier register3 changes
Becomes: Assets People Suppliers
Your registers send their changes, so they stay in step with their source.
Risk feeds
- EventPort strike called, Rotterdam
- AnalysisLikely three days; road freight unaffected
- Impact on you1 site, 2 routes, 1 supplier
Stratforth's own open-source-intelligence (OSINT) risk feed, with geopolitical analysis and impact assessments, alongside any feeds you bring.
02
Shape
Pipelines join, calculate and score, with scripts and AI steps inside them, and create data you did not have before.
- Built on a visual canvas, block by block.
- AI drafts a pipeline from a sentence; you review it.
Join
- Left
- Shipments
- Right
- Weather warnings
- Match
- The route crosses the warning area
Blocks to join, filter, calculate, score and measure distance.
Script
hours = distance_km / speed_kmh
risk = wind_force * hours
level = "high" if risk > 40 else "normal"
SQL or Python, for the steps a block cannot express.
AI step
Summarise today's port notices for the Humber.
AIPilotage suspended above force 8. Two berths closed until Thursday.
An AI step reads text and returns data the next step can use.
New data
Route risk v14
- Level
- High
- Built from
- 4 sources and a script
- Feeds
- 2 rules, 1 dashboard
The result is a new dataset, versioned, with its lineage.
03
See
Live objects on maps and dashboards, each with its full history.
- Sites, assets, vehicles, shipments and people.
- Every version names the sources that built it.
Map
Everything with a location on one map, with risk zones drawn over it.
Dashboard
- Shipments at sea
- 12
- Routes at risk
- 1
- Inspections due
- 4
Dashboards are built from the same objects, so they never disagree with the map.
History
- v14Route risk: High Run 2291, 4 sources and a script
- v13Route risk: Normal Run 2284, 4 sources and a script
- v12Route risk: Normal Run 2270, 3 sources and a script
New data adds a version; earlier versions stay as they were.
04
Decide
Rules watch the data. You choose, rule by rule, who decides: the rule itself, AI, or a named person.
- Simulated on your data before it is switched on.
- Kill switches, and a ceiling on how many actions rules may raise.
Automatic
- When
- a sensor reading arrives
- If
- vibration stays above its limit for ten minutes
- Then
- raise a maintenance task
AutomaticAI-assistedHeld
No approval needed. The rule acts and records what it did.
AI-assisted
- When
- a travel advisory is issued
- If
- it covers a city where your people are
- Then
- move their travel, and tell the travel desk
AutomaticAI-assistedHeld
AI recommendsAI decides
You choose per rule: AI recommends and a person decides, or AI decides and acts within limits you set. Either way, everything is recorded.
Held for a person
- When
- route risk changes
- If
- the route crosses a storm warning
- Then
- hold the sailing
AutomaticAI-assistedHeld
The operations lead approves or declines. If nobody answers in two hours, it goes to the duty manager.
05
Act
The right action, done quickly and correctly, and the right people informed: tasks, alerts and updates to your other systems.
- Every action is written to an append-only record.
- Each traces back to its rule and its data.
Task
Replace the door closer Open
- For
- Site manager, Teesside
- Due
- Friday
- From
- Fire-door inspection, one finding
A task for a named person, group or role.
Alert
Storm warning on the SH-205 route 14:31
- To
- Operations lead
- Sent
- In the app and by email
- Because
- Route risk, version 14
Each alert links to the data version that triggered it.
Update a system
Order system Sent
- Change
- SH-205 arrival moved to Thursday
- Sent as
- Webhook
- Approved by
- Operations lead
Your other systems are told the moment a decision is made.
Record
- Carrier notified, order system updated
- Hold approved by the operations lead
- Rule: Esbjerg to Humber route at risk
- Weather feed: amber storm warning
Nothing in the record can be edited or removed.