Attachment B - SmartCBM Technical Requirements.pdf
PDF 86 KB Posted
- Attached to
- SmartCBM
- Solicitation number
- PR457112
- Issued by
-
Department of Energy
About this file
This document contains technical requirements and acceptance criteria for a Condition-Based Maintenance (CBM) software solution procurement for a nuclear laboratory facility.
The solution must provide native, bidirectional integration with Hexagon HxGN EAM (Enterprise Asset Management) and APM (Asset Performance Management) modules, supporting seamless data exchange of assets, work orders, maintenance histories, and condition data with automated work order generation from condition alerts. The system requires an API-first architecture with RESTful APIs, webhooks, and third-party integration frameworks, demonstrating successful production-level implementations in nuclear or highly regulated industries with data synchronization latency under five minutes for critical alerts. The CBM platform must support multiple data collection methods (route-based manual/portable, continuous online IIoT/sensor-based, and hybrid approaches) and integrate with vibration analysis, infrared thermography, ultrasound, oil analysis, motor circuit analysis, and process parameters. The solution must deliver prescriptive analytics generating specific repair recommendations for at least 80% of common defect types, include iOS and Android mobile applications with offline capabilities and route management features, and provide enterprise/site/department-level dashboards with customizable alerts and notifications across email, SMS, and in-app channels. The platform must function as a centralized reliability management system supporting Reliability-Centered Maintenance (RCM) principles with a comprehensive, pre-populated failure mode library containing several thousand entries with causes, detection methods, and recommended mitigations specific to nuclear/power generation assets, alongside asset hierarchy management, criticality ranking tools, and integration with existing EAM asset registers.
The solution must meet cybersecurity standards for non-reactor nuclear facilities including NIST 800-53 compliance, role-based access control, audit logging, and data encryption, supporting on-premise, cloud, or hybrid deployments with data residency controls and scaling to support 5,000+ assets with concurrent users. Bidders must provide comprehensive audit trails, version control, data export capabilities (CSV, PDF, API), and third-party security certifications (SOC 2 or ISO 27001). Implementation must include a detailed project plan with milestones targeting 6-9 months for full rollout, 12-24 months of post-go-live support with 99% uptime SLAs and <4 hour response times for critical issues, and at least two reference customers from government, DOE/nuclear, or similarly regulated industries confirming successful implementation and ongoing support.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Core Integration Requirements (Key Differentiator)
• The solution must provide native, bidirectional integration with Hexagon HxGN EAM for seamless data exchange of assets, work orders, maintenance histories, and condition data. Integration should support automated work order generation/triggering based on condition alerts.
• The solution must integrate directly with Hexagon HxGN APM (or equivalent modules) for risk-based analytics, asset health scoring, and strategy optimization.
• Provide API-first architecture with support for RESTful APIs, webhooks, and third-party integration frameworks. The bidder must demonstrate successful integrations with Hexagon EAM/APM in production environments (preferably in nuclear or highly regulated industries).
• Support real-time or near-real-time data synchronization between the CBM system and EAM/APM.
Acceptance Criteria:
• Bidder provides evidence (case studies, references, or live demonstration) of a successfully deployed bidirectional integration with Hexagon HxGN EAM, including automated work order creation from condition alerts.
• Bidder demonstrates direct integration with Hexagon HxGN APM during a proof-of-concept session using the laboratory’s environment or a sandbox instance.
• Solution must pass integration testing showing successful data synchronization (asset data, alerts, and work orders) with less than 5-minute latency for critical alerts.
• Bidder supplies API documentation and sample integration code/configurations.
2. Condition Monitoring & Data Collection
• Support multiple data collection methods: route-based (manual/portable), continuous/online (IIoT/sensor-based), and hybrid.
• Integrate with common condition monitoring technologies, including vibration analysis, infrared thermography, ultrasound, oil/lubrication analysis, motor circuit analysis, and process parameters.
• Provide prescriptive analytics that not only detect defects but recommend specific corrective actions, prioritized by risk and severity.
• Include mobile application for field technicians with offline capability, real-time asset health views, route management, and data upload.
Acceptance Criteria:
• System supports all three data collection methods (route-based, continuous, hybrid) as demonstrated in a vendor presentation or PoC.
• Mobile app is available on iOS and Android, supports offline data collection with automatic sync, and includes route planning/execution features.
• Prescriptive analytics engine must generate specific repair recommendations (not just alarms) for at least 80% of common defect types in a test dataset.
• Integration with at least four of the listed condition monitoring technologies (vibration, IR, ultrasound, oil analysis, etc.) is shown via live demo or reference installations.
3. Analytics, Dashboards & Reporting
• Deliver enterprise-level, site-level, and department-level dashboards for asset health, program KPIs, and reliability metrics.
• Support connected infrastructure monitoring (e.g., sensor/gateway health, installation issue detection like orientation changes or dislodged sensors).
• Provide lubrication program management module or equivalent functionality for oil analysis tracking and scheduling.
• Enable customizable alerts, notifications (email, mobile), and automated workflows triggered by condition thresholds.
Acceptance Criteria:
• Dashboards must include configurable views at enterprise, site, and department levels, with drill-down capability, as verified during a software demonstration.
• Connected infrastructure monitoring features (sensor health, orientation change detection, gateway status) are demonstrated with sample alerts.
• Lubrication management functionality allows tracking, scheduling, and trending of oil analysis results with integration to overall asset health scoring.
• Alert system supports user-configurable thresholds and multi-channel notifications (email, SMS, in-app), with audit logs of all triggered actions.
4. Reliability & Asset Management Features
• Function as a centralized reliability platform supporting Reliability-Centered Maintenance (RCM) principles, failure mode tracking, and strategy optimization.
• Provide a comprehensive, detailed failure mode library (including failure modes, effects, and criticality analysis) to support efficient RCM studies, FMEA development, and maintenance strategy creation. The library should be industry-specific or extensible for nuclear/power generation assets.
• Include tools for asset hierarchy management, criticality ranking, and integration with existing asset registers in Hexagon EAM.
• Support predictive and condition-based maintenance strategies that reduce unplanned downtime and integrate with preventive maintenance schedules.
Acceptance Criteria:
• The platform includes a pre-populated, searchable failure mode library containing at least several thousand failure modes with associated causes, detection methods, and recommended mitigations (verified via documentation and demo).
• Bidder demonstrates the ability to import, customize, and apply the failure mode library to RCM/FMEA processes for sample nuclear-related assets (e.g., pumps, motors, compressors).
• Asset hierarchy and criticality tools allow full synchronization with Hexagon EAM asset registers, with risk indexing and strategy optimization features shown in a test scenario.
• System supports creation and tracking of predictive/CBM tasks that link directly to work orders in the EAM.
5. Technical & Security Requirements (Nuclear Context)
• Must meet cybersecurity standards appropriate for non-reactor nuclear facilities (e.g., compliance with NRC guidelines, NIST, or equivalent; role-based access control, audit logging, data encryption).
• Support on-premise, cloud, or hybrid deployment with robust data sovereignty and backup options.
• Scalable architecture suitable for enterprise use across multiple facilities/sites.
• Provide comprehensive audit trails, version control for configurations, and data export capabilities for regulatory reporting.
• Offer training, documentation, and support services for implementation, including knowledge transfer for internal teams.
Acceptance Criteria:
• Solution complies with NIST 800-53 or equivalent standards relevant to nuclear facilities; bidder provides third-party security assessment reports or SOC 2 / ISO 27001 certification.
• Deployment options (on-prem, cloud, hybrid) are fully supported with data residency controls; successful backup/restore is demonstrated.
• System scales to support at least 5,000+ assets with concurrent users, as shown in performance documentation or references.
• Full audit logging, role-based access, and export capabilities (CSV, PDF, API) for regulatory use are verified.
• Comprehensive user/admin documentation, training materials, and a knowledge transfer plan are provided as deliverables.
6. Implementation & Support
• Bidder must provide a detailed implementation plan with timeline, including integration testing with existing Hexagon EAM/APM instance.
• Include post-go-live support, maintenance, and software updates for a minimum of X years.
• Demonstrate prior experience with similar implementations in government, laboratory, or highly regulated industrial environments.
Acceptance Criteria:
• Bidder submits a project plan including milestones, resource allocation, integration testing phases, and go-live criteria (maximum 6–9 months for full rollout preferred).
• Minimum 12–24 months of post-go-live support with defined SLAs (e.g., 99% uptime, <4 hour response for critical issues) and included software updates.
• At least two reference customers in government, DOE/nuclear, or similarly regulated industries are provided with contactable references confirming successful implementation and ongoing support.
File details come from the government source that posted it. Updated .