Add Specialized Diagnostic Workflow in AssetOpsBench

[DhavalRepo18]

• Bring a vertical MCP Server for the specific diagnostic workflows
• Add a focused scenario around motor current signature analysis, or vibration analysis, such as "Get the current sensor data for Chiller 6 and check for motor faults."
• Build a benchmark around it.
• Add additional Skill to improve the Agent Performance

[LGDiMaggio]

I can take this on. I’ll start by including a vertical MCP server around the vibration-analysis diagnostic workflow, using a focused scenario. I’ll then add this as a benchmark scenario (plan + execute) and introduce an additional “skill”. Once the vibration workflow is in place, we can extend the same pattern to Motor Current Signature Analysis.

[DhavalRepo18]

Given the Work is in progress, we will prepare the documentation that enable you to contribute on timely manner.

[LGDiMaggio]

Progress update — VibrationAgent MCP Server

Draft Implementation is ready locally. Here's what's been done:

New files (14):

• src/servers/vibration/main.py — FastMCP("VibrationAgent") with 8 tools: get_vibration_data, list_vibration_sensors, compute_fft_spectrum, compute_envelope_spectrum, assess_vibration_severity, calculate_bearing_frequencies, list_known_bearings, diagnose_vibration
• src/servers/vibration/dsp/ — pure DSP modules (FFT, envelope analysis, bearing frequency calculator, ISO 10816 + fault classification), adapted from vibration-analysis-mcp (Apache-2.0)
• src/servers/vibration/data_store.py — server-side signal store (same pattern as TSFM file handles)
• src/servers/vibration/couchdb_client.py — CouchDB fetcher reusing existing IoT env vars
• src/servers/vibration/tests/ — 26 DSP unit tests passing, MCP tool tests ready
• src/tmp/assetopsbench/scenarios/single_agent/vibration_utterance.json — 20 benchmark scenarios (IDs 301–320)

Modified files (2):

• pyproject.toml — added scipy>=1.10.0 dep + vibration-mcp-server script entry
• INSTRUCTIONS.md — added VibrationAgent documentation section

Questions before opening the PR:

1. Contribution process — I didn't find a CONTRIBUTING.md or DCO/CLA requirements. Is there anything specific I need to follow for commits (e.g. Signed-off-by lines)?
2. Scenario ID range — I used 301–320 for vibration scenarios. Does this conflict with any planned ranges?
3. DEFAULT_SERVER_PATHS in executor.py — should VibrationAgent be registered there, or remain opt-in via --server for now?
4. Vibration sample data — the existing chiller6_june2020 dataset only has process variables (temperatures, flow, power) sampled at 15-min intervals — no high-frequency accelerometer data suitable for FFT/envelope analysis. I can provide a synthetic vibration sample dataset for CouchDB to enable integration tests. Would that be welcome, or do you have real vibration data planned?
5. Contribution docs — you mentioned preparing documentation to enable contributions. Should I wait for that, or go ahead with a draft PR?

Note: Development was assisted by Code Copilot for the integration work. The DSP core is adapted from vibration-analysis-mcp project.

Happy to open a draft PR whenever you're ready.

[DhavalRepo18]

@LGDiMaggio Pls go ahead with draft PR.

[DhavalRepo18]

@ShuxinLin if you have any comment on these incoming new MCP Server, I can look into the code (DSP side) but other than that does overall organization looks okay?

[LGDiMaggio]

Draft PR submitted: #190

Includes VibrationAgent MCP server (8 tools), DSP core, 20 benchmark scenarios, 26+17 tests, and full documentation.

Ready for review when convenient. Happy to address any feedback.