Plant onboarding
The plant onboarding tool provides a structured workspace for configuring renewable plants so that IBM® Maximo® Renewables can ingest, validate, and analyze operational data.
Overview
The plant onboarding tool is a configuration workspace in IBM Maximo Renewables that guides administrators through the process of preparing a solar, wind, or energy‑storage plant for data ingestion and operational monitoring. The tool centralizes all onboarding activities—such as defining plant information, configuring communication protocols, adding devices, mapping meters, and validating telemetry—into a structured, step‑based flow.
A completed onboarding configuration ensures that IBM Maximo Renewables can collect, process, and analyze data from field devices, loggers, and SCADA systems, and can display plant performance accurately in dashboards, alerting workflows, and reporting.
Role of the onboarding tool
The plant onboarding tool provides a standardized way to prepare renewable assets for use in IBM Maximo Renewables. It guides organizations through the information and configuration that must be defined before a plant can be deployed and begin sending operational data to the system. Administrators use the tool to register new plants, enter commercial and geographic information, and define key operational attributes. The tool also supports connecting field devices and data acquisition systems by using FTP, API, or OPC‑UA protocols, depending on the plant’s communication infrastructure. As part of this process, users map plant equipment such as loggers, inverters, weather stations, meters, and string monitoring boxes and establish the relationships and hierarchy between these devices so that data flows can be interpreted correctly.
Device metadata and parameter definitions are added to ensure the system can parse telemetry according to the data formats generated by each manufacturer and logger. After device configuration is complete, administrators can enable dashboards, alerts, and plant‑level access controls that depend on accurate device mapping and parameter alignment. When the onboarding flow is finalized, the plant configuration promotes data integrity, device traceability, and reliable analytics across IBM Maximo Renewables.
Supported plant types
The onboarding tool supports renewable plants across several domains, including solar, wind, and battery energy storage systems (BESS). When you select a domain, the tool displays the corresponding fields, device categories, and parameters that are specific to the technology type. This ensures that each plant, regardless of domain or configuration, is onboarded with the correct structural and technical attributes.
Overview of the onboarding sequence
The onboarding process is divided into sequential configuration areas. Each area focuses on a specific category of information or device layer.
- Plant details
- Captures plant‑level attributes such as project name, location, ownership, contact information, and site geography.
- Technical details
- Defines electrical and operational characteristics such as AC and DC capacity, technology type, mounting configuration, performance factors, and communication protocol settings.
- Devices
- Adds and manages plant equipment. Supported devices include loggers, inverters, weather monitoring systems, multifunction meters, string monitoring boxes, and strings.
- Device metadata
- Stores identifiers, manufacturer information, model details, and plant‑specific metadata required to classify devices within the system.
- Device hierarchy
- Describes how devices are connected physically and logically, such as loggers to inverters, inverters to string monitoring boxes, and string monitoring boxes to strings.
- Device parameters
- Maps telemetry fields, units, and column indexes that are required for data ingestion and validation.
- Custom alert enablement
- Enables alert types that apply to the plant based on the devices and parameters configured.
- Dashboard enablement
- Configures which dashboards and widgets are available for operators after the plant is deployed.
- User management
- Adds users and assigns roles or permissions that apply to the plant after onboarding.
Communication protocols
The onboarding tool supports multiple communication mechanisms for integrating plant data:
- FTP for scheduled file‑based ingestion.
- API for direct system‑to‑system data transfer.
- OPC‑UA for device‑level communication, where applicable.
- Modbus for device‑level communication, where applicable.
The selected protocol determines the required device metadata, mapping rules, and parameter validations that appear in later steps.
Deployment and operational readiness
After all onboarding steps are completed and validated, the plant configuration is deployed to IBM Maximo Renewables. Deployment activates the services required for operational use of the plant, including data ingestion from connected devices and device‑level telemetry processing. Once deployed, the plant becomes available for performance forecasting, KPI tracking, benchmarking, dashboards, and analytical widgets. Alerting rules and operational workflows that depend on device hierarchy and parameter definitions are also enabled, along with reporting capabilities that support performance monitoring and compliance needs.
If deployment issues occur, the onboarding tool highlights the affected configuration areas so that administrators can review, correct, and redeploy the project. This validation‑driven approach helps ensure that data is processed reliably and consistently after deployment.
Scenarios for using the onboarding tool
The plant onboarding tool is used whenever a plant or its configuration must be prepared or updated for operational monitoring in IBM Maximo Renewables. This includes onboarding a new renewable plant, transitioning an existing plant to a different communication protocol, or adding new hardware such as loggers, inverters, meters, or monitoring systems. The tool is also used when restructuring the device hierarchy, updating plant capacity or technology attributes, or resolving data ingestion issues caused by incomplete or incorrect device mapping.