AssetOpsBench

AssetOpsBench - Industry 4.0: A unified benchmark and framework for building, orchestrating, and evaluating domain-specific AI agents for Industry 4.0 asset operations and maintenance, with 460+ scenarios, 5 specialist agents (IoT, FMSR, TSFM, Work Order,...), and multi-agent orchestration blueprints (MetaAgent, AgentHive) over MCP.

Runs with mockssource: GitHubPythonApache-2.0commit 81265cbbd36d

Python, Apache-2.0 licensed. The project labels itself: ai for physical assets, condition based maintenance, hvac maintenance, iot, llm agents, model context protocol, predictive maintenance and time series forecasting.

AssetOpsBench runs, with stand-ins for the services it depends on. An Argusic agent installed it in 12 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

All 6 MCP servers (iot, utilities, fmsr, wo, tsfm, vibration) install, import, and register their tools successfully. 559 tests pass with mocked CouchDB; the 16 skipped tests require a live CouchDB instance. CLI entrypoints (plan-execute, evaluate, and all *-agent/*-mcp-server commands) respond to --help.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.17 (measured)
recorded runs
2
last tested
stars
2,437
forks
360
open issues
74
watchers
15
size
113 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing AssetOpsBench, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • couchdb3.Database.__bool__() raises httpx.ConnectError instead of returning False when CouchDB unreachable, crashing test_invalid_site tests4 minutes
  • mcp 2.x installed but project uses FastMCP (renamed in v2). Pinned to mcp<2.2 minutes
  • requires_couchdb marker only checked env var, not connectivity1 minute
  • Missing pytest, opentelemetry-sdk, opentelemetry-exporter-otlp-proto-http, protobuf1 minute
Install time
12 minutes
Cold machine to finish
23 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
pytest test suite: 559 passed, 16 skipped, 6 pre-existing failures in 16.89s. All MCP servers confirmed to import, register tools, and respond to mock tool calls. CLI entrypoints functional.
Model tokens used
249,820
Exact commit tested
81265cbbd36d
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- **FMSR server**: 22 passed, 1 skipped
- **WO server**: 12 passed
- **Utilities server**: 12 passed
- **TSFM server**: 115 passed (all ML pipeline tests including model catalog, feature extraction, r…
- **Agent tests**: 87 passed (stirrup, claude, openai, deep, direct-llm)
- **OpenCode agent**: 18 passed
- **Benchmark**: 1 passed
- **CouchDB loader**: 3 passed
- **Evaluation (excluding pre-existing failures)**: 102 passed
- **LLM/routers**: 18 passed
- **MCPhub**: 3 passed
- **Observability**: 22 passed

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 12 minutes.
  • Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks92.000.17
Argusic Runner1/3Runs with mocks92.000.25

Topics (from GitHub)

ai-for-physical-assetscondition-based-maintenancehvac-maintenanceiotllm-agentsmodel-context-protocolpredictive-maintenancetime-series-forecasting

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/AssetOpsBench.svg)](https://argusic.com/subject/assetopsbench)

Questions

Does AssetOpsBench run?
AssetOpsBench runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 12 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test AssetOpsBench?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 81265cbbd36d. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test AssetOpsBench?
The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does AssetOpsBench take to install?
12 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does AssetOpsBench need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing AssetOpsBench?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for AssetOpsBench?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion