01 / 08EVENT
A new document arrives
Field study notes
- Source document received
- Original retained
- Ready to review
Received
A research document starts the work. The original stays available throughout.
EDGE SYSTEMS
Intelligence where physical operations happen.
Stacx24 combines edge processing, telemetry, cloud software and operational intelligence to connect what happens in the physical world with what needs to happen next.
Not an industry vertical: a kind of operation. Plants, sites, farms, buildings, fleets, labs. Wherever something physical has to be seen and acted on.
- WHAT HAPPENS ON SITE
- Temperatures, doors, pumps, vehicles, people, weather, machines.
- WHAT NEEDS TO HAPPEN NEXT
- An alert, a setpoint, a work order, a decision by the person on shift.
Architecture sequence: PHYSICAL ENVIRONMENT, then SENSORS / CAMERAS, then EDGE DEVICE, then LOCAL PROCESSING, then TELEMETRY, then CLOUD, then INTELLIGENCE, then OPERATIONAL DECISION. Stages marked Human pause the flow until a person decides. Status labels update as the event moves.
PRIMARY ARCHITECTURE · ILLUSTRATIVE SCENARIO · COLD STOREILLUSTRATIVE · COLD STOREPHYSICAL ENVIRONMENT
Cold store · door left open
CONNECTED
SENSORS / CAMERAS
Door contact · temp probe
CONNECTED
EDGE DEVICE
Controller on the unit
CONNECTED
LOCAL PROCESSING
Site gateway · rules
CONNECTED
TELEMETRY
MQTT · TLS · QoS 1
CONNECTED
CLOUD
Ingest · asset record
READY
INTELLIGENCE
Pattern · risk to stock
READY
OPERATIONAL DECISION
Shift supervisor
AWAITING APPROVAL
DISPATCHED · SEAL INSPECTION RAISEDPAUSED · A PERSON DECIDES WHAT HAPPENS ON SITE
WHAT WE ARE USUALLY ASKED TO FIX
Eight problems. One system shape.
They present differently on every site, but they are the same eight gaps between the physical world and the software that is supposed to represent it. Each maps to a stage of the architecture above, which is where it gets engineered.
No visibility between site and cloud
HOW IT SHOWS UP: The dashboard says one thing, the person on site sees another.
WHAT THE SYSTEM DOES: One state model, joined to asset records, updated from the edge.
Stage: TELEMETRY · CLOUD
Too much raw sensor data
HOW IT SHOWS UP: Terabytes of readings nobody looks at; the one that mattered is buried.
WHAT THE SYSTEM DOES: Filter and correlate at the edge. Send events and summaries, not streams.
Stage: LOCAL PROCESSING
Slow response to physical events
HOW IT SHOWS UP: By the time the alert reaches someone, the damage is done.
WHAT THE SYSTEM DOES: Local rules act in milliseconds. The alert reaches the person on site first.
Stage: EDGE DEVICE
Poor connectivity
HOW IT SHOWS UP: Remote sites, metal buildings, shared networks. The link drops daily.
WHAT THE SYSTEM DOES: Local buffering, ordered replay, and logic that does not need the cloud.
Stage: LOCAL PROCESSING
Disconnected devices and applications
HOW IT SHOWS UP: Sensors on one system, work orders on another, nothing in between.
WHAT THE SYSTEM DOES: Telemetry joined to the operational applications that act on it.
Stage: CLOUD
Manual monitoring
HOW IT SHOWS UP: Someone walks the site with a clipboard, or watches a screen all shift.
WHAT THE SYSTEM DOES: Continuous observation with classified alerts and an owner for each.
Stage: TELEMETRY
Weak operational alerts
HOW IT SHOWS UP: Everything alarms, so nothing does. Alerts have no context or owner.
WHAT THE SYSTEM DOES: Alerts carry context, risk and a proposed action, and go to a named person.
Stage: INTELLIGENCE
No unified system state
HOW IT SHOWS UP: Nobody can say, right now, what is connected, healthy and open.
WHAT THE SYSTEM DOES: Device health, readings, alerts and owners in one observable view.
Stage: CLOUD · DECISION
UNIFIED SYSTEM STATE
One place where the site and the software agree.
Inside VFarm: sensor trends, device activity, automation and alert delivery in one view. Explore a captured analytics dashboard from the application.
Temperature · 24h
rack2_dht · captured reading
- 27.1°C
- Current
- 20.7°C
- Min
- 24.7°C
- Avg
- 32.6°C
- Max
- 144
- Samples
CORE SYSTEM MODEL
The system is the product. Technology is a component.
- Not every step needs AI.
- Some need rules.
- Some need software.
- Some need edge processing.
- Some need people.
We engineer the right combination.
Research assistance
IN THE OPERATION
A document arrivesFrom the research team
02 / 08CONTEXT
Bring the background together
Document + background
- Source details attached
- Related records found
- Approved labels loaded
Context attached
Existing records, source details and the approved label list give the document context.
03 / 08PROCESSING
Check the details first
Document checks
- Duplicate check complete
- Required details present
- Text ready for review
Checks complete
Software checks for duplicates and missing information before any AI suggestion.
04 / 08INTELLIGENCE
Suggest a label, within scope
Suggested label
- Field study
- Supporting passage highlighted
- Awaiting researcher review
Suggestion only
AI proposes a label from the approved list. It cannot publish the label itself.
05 / 08DECISION
A researcher makes the decision
Label review
- Source passage checked
- Suggested label reviewed
- Field study approved
Reviewed by researcher
The researcher reads the supporting passage and approves or corrects the suggestion.
06 / 08ACTION
Update the research record
Research record
- Label: Field study
- Source linked
- Review retained
Saved to record
Only the approved label enters the record, alongside its source.
07 / 08OBSERVATION
Record what actually happened
Activity record
- Suggestion recorded
- Reviewer decision recorded
- Save confirmed
Outcome recorded
The system records the suggestion, the review and the saved result so the team can inspect them.
08 / 08IMPROVEMENT
Review the labelling rules
Next-cycle guidance
- Review corrections
- Agree guidance changes
- Use approved guidance next time
Feedback to the next event
The team reviews corrections and agrees changes to the guidance before the next document.
Each outcome informs the next cycle.
- 01 · EVENTA new document arrives
A research document starts the work. The original stays available throughout.
- 02 · CONTEXTBring the background together
Existing records, source details and the approved label list give the document context.
- 03 · PROCESSINGCheck the details first
Software checks for duplicates and missing information before any AI suggestion.
- 04 · INTELLIGENCESuggest a label, within scope
AI proposes a label from the approved list. It cannot publish the label itself.
- 05 · DECISIONA researcher makes the decision
The researcher reads the supporting passage and approves or corrects the suggestion.
- 06 · ACTIONUpdate the research record
Only the approved label enters the record, alongside its source.
- 07 · OBSERVATIONRecord what actually happened
The system records the suggestion, the review and the saved result so the team can inspect them.
- 08 · IMPROVEMENTReview the labelling rules
The team reviews corrections and agrees changes to the guidance before the next document.
Everyday operations
IN THE OPERATION
A request arrivesFrom the operating team
01 / 08EVENT
A request starts the work
New work request
- Request received
- Source application linked
- Handoff opened
Received
An incoming request starts a handoff between the tools your team already uses.
02 / 08CONTEXT
Attach the details once
Request background
- Existing record attached
- Current state checked
- Owner identified
Context attached
The system brings together the request, existing records and its responsible owner.
03 / 08PROCESSING
Let the rules route the work
Connected applications
- Request inbox → work queue
- Required details checked
- Work queue → owner workspace
Handoff prepared
Defined rules check the request and pass its details between connected applications.
04 / 08INTELLIGENCE
Rules are enough here
Routing rule
- A required detail is missing
- Exception route selected
- Named owner notified
No AI needed
This example needs no AI decision. Defined rules identify an exception and send it to its owner.
05 / 08DECISION
The owner resolves the exception
Exception review
- Exception opened
- Missing detail supplied
- Owner confirms next step
Reviewed by owner
A named person supplies the missing detail and confirms that the work can continue.
06 / 08ACTION
Complete the handoff
Completed handoff
- Confirmed details transferred
- Next application updated
- Owner notified
Handoff complete
The confirmed information reaches the next application and the work continues.
07 / 08OBSERVATION
Keep the outcome visible
Activity record
- Exception recorded
- Resolution recorded
- Handoff confirmed
Outcome recorded
The system records completion and exceptions so the team can see what happened.
08 / 08IMPROVEMENT
Review the handoff rules
Next-cycle guidance
- Review recurring exceptions
- Agree routing changes
- Apply approved rules next time
Feedback to the next event
The team reviews repeated exceptions and approves rule changes for future requests.
Each outcome informs the next cycle.
- 01 · EVENTA request starts the work
An incoming request starts a handoff between the tools your team already uses.
- 02 · CONTEXTAttach the details once
The system brings together the request, existing records and its responsible owner.
- 03 · PROCESSINGLet the rules route the work
Defined rules check the request and pass its details between connected applications.
- 04 · INTELLIGENCERules are enough here
This example needs no AI decision. Defined rules identify an exception and send it to its owner.
- 05 · DECISIONThe owner resolves the exception
A named person supplies the missing detail and confirms that the work can continue.
- 06 · ACTIONComplete the handoff
The confirmed information reaches the next application and the work continues.
- 07 · OBSERVATIONKeep the outcome visible
The system records completion and exceptions so the team can see what happened.
- 08 · IMPROVEMENTReview the handoff rules
The team reviews repeated exceptions and approves rule changes for future requests.
Connected fields
IN THE OPERATION
A field reading arrivesFrom a connected sensor
01 / 08EVENT
A sensor reads the field
Incoming field reading
- Sensor reading received
- Field identified
- Reading time attached
Received
A new field reading starts the cycle, connecting conditions on the ground to the system.
02 / 08CONTEXT
Put the reading in context
Field background
- Field history attached
- Recent readings loaded
- Current conditions attached
Context attached
Field history and recent conditions help the team interpret the new reading.
03 / 08PROCESSING
Check the signal near the field
Edge processing
- Local checks run
- Incomplete readings flagged
- Relevant readings forwarded
Local checks complete
Local edge checks validate readings before relevant information reaches the monitoring application.
04 / 08INTELLIGENCE
Prepare a suggested response
Response proposal
- Field context considered
- Suggested response prepared
- Sent for agronomist review
Suggestion only
The system uses the checked information to propose a response within its defined scope.
05 / 08DECISION
The agronomist reviews
Agronomist review
- Conditions reviewed
- Proposal checked
- Response approved
Reviewed by agronomist
The agronomist checks the proposal and approves or adjusts it before it reaches the operator.
06 / 08ACTION
Send the approved proposal
Operator work item
- Approved proposal attached
- Instructions available
- Delivered to operator
Ready for the operator
The approved proposal reaches the operator with the instructions they need.
07 / 08OBSERVATION
Keep watching the conditions
Field activity record
- New readings recorded
- Operator reports attached
- Outcome ready for review
Observation continues
New readings and operator reports help the team understand what happened next.
08 / 08IMPROVEMENT
Review the next field cycle
Next-cycle guidance
- Review field observations
- Agree guidance changes
- Use approved guidance next time
Feedback to the next event
The agronomist reviews the observations and agrees guidance for the next cycle.
Each outcome informs the next cycle.
- 01 · EVENTA sensor reads the field
A new field reading starts the cycle, connecting conditions on the ground to the system.
- 02 · CONTEXTPut the reading in context
Field history and recent conditions help the team interpret the new reading.
- 03 · PROCESSINGCheck the signal near the field
Local edge checks validate readings before relevant information reaches the monitoring application.
- 04 · INTELLIGENCEPrepare a suggested response
The system uses the checked information to propose a response within its defined scope.
- 05 · DECISIONThe agronomist reviews
The agronomist checks the proposal and approves or adjusts it before it reaches the operator.
- 06 · ACTIONSend the approved proposal
The approved proposal reaches the operator with the instructions they need.
- 07 · OBSERVATIONKeep watching the conditions
New readings and operator reports help the team understand what happened next.
- 08 · IMPROVEMENTReview the next field cycle
The agronomist reviews the observations and agrees guidance for the next cycle.
Read the complete system model
- EVENT
Something happens in the operation.
- CONTEXT
Records, history and state are attached.
- PROCESSING
Rules, software and integrations do the deterministic work.
- INTELLIGENCE
One bounded AI component, where judgement can be modelled.
- DECISION
A named person decides where it matters.
- ACTION
Something changes in the world.
- OBSERVATION
Telemetry and monitoring record what happened.
- IMPROVEMENT
The loop feeds back into the next event.
SYSTEMS USED · SERVICES
RELATED WORK
photo: field sensors and edge unit on site
WORK · AI + EDGE · AGRICULTURECASE STUDY
AI + Edge Agriculture
Field sensors and edge inference feeding irrigation and crop-condition decisions, buffered through intermittent connectivity, with an agronomist approving changes before they reach the field.
SENSOR · EDGE · TELEMETRY · AI AGENT · HUMAN APPROVAL
NEXT STEP
Turn physical signals into operational intelligence.
Tell us what happens on site and what you cannot see today. We will propose where to sense, where to process, and who should act.
Discuss an Edge System
No technical specification required. Start with what you cannot see today.