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.
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 61%
Response Time: 1d
First Timer Success: 63%
IBM/AssetOpsBench has a recorded first-timer success rate of 62.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in IBM/AssetOpsBench respond to incoming external pull requests in approximately 27.3 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 65.4 places IBM/AssetOpsBench in the A tier.
The external contributor pull request merge rate for IBM/AssetOpsBench is 60.8%, based on public PR activity from non-core contributors.
IBM/AssetOpsBench currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
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.
Balanced & professional review environment in IBM/AssetOpsBench. Maintains strict focus on technical quality and test standards.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/IBM/AssetOpsBench?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~18 hours (76% approval). Large PRs (>500 lines) take ~131 hours (27% approval). Keep your diff compact for rapid review.
AssetOpsBench comes with MCP Server for Industrial AI. This issue is created to seek help from the community in providing a supporting document (preferably created manually) to assist first-time users or, say, our KDD tutorial participants. We are planning to release a series of Colab Notebook that are easy for any one to experience the MCP Tools for each server. We like to start with IoT. A notebook should assume we have setup a docker locally and uploaded a data as per as document. Now we are try to use MCP tools to explore all site, assets, some data, plot and etc. Ideally a single notebook shoould cover all the tools use MCPHub (workflow) to run tool Tool Universe. If you interested to take up the issue, please drop a note as comment.
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to IBM/AssetOpsBench, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of IBM/AssetOpsBench acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 60.8% were successfully merged into the primary branch.
IBM/AssetOpsBench has a recorded first-timer success rate of 62.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 65.4 places IBM/AssetOpsBench in the Welcoming tier.
The external pull request merge rate is 60.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, IBM/AssetOpsBench currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for IBM/AssetOpsBench are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.