Make the Monitoring System Useful After Commissioning.
Rekacipta helps operators, engineers, maintenance teams and system administrators understand how to use Siteplore effectively — from dashboards and historical trends to alerts, field devices, basic troubleshooting and continuous improvement of the monitoring workflow.
A monitoring platform can be technically successful and still create little operational value.
A commissioned system only becomes useful when the people responsible for operations and maintenance understand what is being measured, how to interpret changes, which limitations matter and what action should follow when the monitoring system identifies something unusual.
Dashboard Without Understanding
Users can see values and charts but may not understand the engineering meaning behind them.
Alerts Without Response
Notifications create little value when the team does not know how they should be investigated.
Knowledge Stays With the Project Team
Important system knowledge may disappear when the commissioning team leaves.
Minor Problems Become Support Tickets
Basic communication or device issues may require external assistance when the local team lacks troubleshooting knowledge.
Configuration Becomes Forgotten
Asset mapping, sensor locations, alert logic and monitoring assumptions can become difficult to remember over time.
Technology Changes but Workflow Does Not
A new monitoring platform creates value only when operational routines evolve to use the new information.
Different users need different levels of Siteplore knowledge.
Training should match the responsibilities of the people using the system instead of giving every participant the same technical material.
Operators
Focus on dashboards, current condition, trends and escalation awareness.
Maintenance Teams
Focus on equipment trends, alerts, field verification and maintenance investigation.
Engineers
Focus on historical analysis, measurement context and engineering interpretation.
System Administrators
Focus on configured assets, users, monitoring structure and approved administration activities.
Learn the complete monitoring workflow, not only where to click.
Siteplore Fundamentals
Understand the relationship between field measurement, edge device, connectivity and the monitoring platform.
Dashboard Navigation
Use configured Siteplore views to review selected operational information.
Historical Trends
Understand how to use historical information to compare equipment or operating periods.
Alerts & Investigation
Understand configured alerts and the intended first step when they occur.
Measurement Context
Understand units, sensor locations, operating context and known measurement limitations.
Basic Troubleshooting
Identify whether an issue may originate from the field device, communication, edge layer or platform.
Product-Specific Use
Apply the workflow to RekaSense, PowerWatch or MachineGuard where included in the deployment.
Operational Workflow
Connect monitoring information to the customer’s existing inspection, maintenance or engineering process.
System Limitations
Understand what Siteplore does, what it does not do and when additional engineering is required.
Teach each team what they need to operate the monitoring workflow effectively.
Operator Training
For people who primarily use Siteplore to understand current operating conditions.
- Dashboard navigation
- Current status review
- Historical trend basics
- Alert awareness
- Escalation workflow
Engineer & Maintenance Training
For personnel responsible for investigating changes and planning action.
- Measurement interpretation
- Trend comparison
- Condition review
- Basic troubleshooting
- Engineering limitations
Administrator Training
For designated personnel responsible for approved Siteplore administration activities.
- System structure
- Asset and measurement context
- User-management concepts
- Configuration awareness
- Support escalation
Support the monitoring system after project handover.
Support can be structured around the deployed Siteplore scope, customer responsibilities and level of assistance required. Response commitments and service windows are defined only when included in the commercial agreement.
Monitoring Support
Assistance with agreed Siteplore monitoring functions and configuration questions.
Troubleshooting Support
Support structured investigation when selected field-to-platform monitoring paths stop behaving as expected.
Refresher Training
Repeat or update training for new personnel or changed monitoring workflows.
Monitoring Review
Review whether configured monitoring remains aligned with the operational objective.
Expansion Support
Evaluate additional assets, sensors or monitoring domains as the deployment grows.
Documentation Support
Maintain appropriate knowledge of configured monitoring scope as agreed for the project.
Troubleshoot systematically — from measurement source to user view.
Identify the Issue
Define what has changed or is no longer behaving as expected.
Check Measurement
Review sensor, meter or original data source.
Check Connectivity
Review edge device and communication path.
Check Siteplore
Review configured monitoring and historical data.
Correct or Escalate
Apply approved action or escalate for further engineering.
Help the local team distinguish a monitoring issue from a real equipment issue.
Sensor Reading Review
Check whether a suspicious value is plausible for the actual condition.
Communication Status
Distinguish missing data from a genuine process or asset change.
Historical Comparison
Compare current behavior with recent or relevant historical trends.
Operating Context
Review whether load, state or process conditions have changed.
Configuration Awareness
Understand configured units, mapping and alert assumptions.
Escalation Criteria
Recognize when the issue requires engineering, instrumentation, network or OEM support.
Train users around the actual Siteplore products deployed at the site.
RekaSense
Understand connected sensors, measurement context, field communication and monitoring views.
Explore RekaSense →PowerWatch
Understand electrical measurements, energy trends, load behavior and relevant meter limitations.
Explore PowerWatch →MachineGuard
Understand condition trends, warnings, operating context and the boundary between monitoring and machinery protection.
Explore MachineGuard →Training should transfer useful operational knowledge.
Exact deliverables depend on the deployed Siteplore configuration, participant roles and agreed support scope.
Training Plan
Role-based training scope aligned with the deployed system.
System Orientation
Explanation of the configured Siteplore monitoring architecture.
Operational Walkthrough
Demonstration of relevant dashboards, trends and monitoring workflows.
Alert Interpretation Guidance
Explanation of configured monitoring alerts and intended response.
Troubleshooting Guidance
Basic structured approach for common monitoring issues.
Reference Material
Appropriate operating or training material where included in scope.
Known Limitation Review
Explanation of important technical boundaries affecting interpretation.
Support Escalation Path
Defined path for requesting additional technical assistance where included.
The system should remain understandable even when personnel change.
Operational monitoring is a long-term capability. Training, documentation and structured support help prevent the Siteplore deployment from becoming a system that only the original project team understands.
A better-trained team extracts more value from the same monitoring infrastructure.
Faster User Adoption
Help teams become comfortable using the deployed monitoring workflow.
Better Data Interpretation
Reduce confusion around measurements, trends and alerts.
More Effective Investigation
Improve the first response to meaningful monitoring changes.
Reduced Knowledge Dependency
Reduce dependence on one individual who understands the system.
Better Support Escalation
Help local teams provide more useful information when support is required.
Longer-Term Monitoring Value
Keep the monitoring workflow aligned with operational use after commissioning.
Transfer knowledge, validate understanding, then support continued use.
Assess
Identify user roles and required knowledge.
Prepare
Align training with the deployed configuration.
Train
Deliver role-appropriate operational learning.
Handover
Transfer relevant operating knowledge and references.
Support
Provide agreed assistance as the system remains in use.
Match training and support to the maturity of your Siteplore deployment.
Commercial scope depends on the deployed products, number and roles of participants, delivery format, site requirements, documentation needs and level of continuing support requested.
Handover Training
For new Siteplore deployments transitioning from project implementation into normal operational use.
- System orientation
- Dashboard walkthrough
- Configured alert explanation
- Basic troubleshooting
- Support escalation overview
Role-Based Training
For organizations requiring more structured training for operators, engineers, maintenance teams or administrators.
- Role-based learning plan
- Site-specific monitoring context
- Trend & alert interpretation
- Troubleshooting workflow
- Operational use cases
Ongoing Support
For customers requiring continuing technical assistance after deployment.
- Technical support scope
- Monitoring troubleshooting
- Configuration assistance
- Refresher knowledge transfer
- Expansion discussion
Training enables users. Support does not replace plant responsibility or specialist systems.
Training and support cover the agreed Siteplore scope. They should not be assumed to replace customer operations, maintenance responsibilities, OEM support, safety systems or specialist engineering services.
| Activity | Training & Support | Important Boundary |
|---|---|---|
| Siteplore user training | Yes | Aligned with agreed deployment scope |
| Dashboard & trend interpretation | Yes | Within available measurement context |
| Basic monitoring troubleshooting | Yes | Further engineering may be required |
| Product-specific training | Where deployed | Depends on project configuration |
| Formal professional certification | Not automatically | Requires separately defined certification program |
| 24/7 support | Not implied | Service window must be contractually defined |
| Guaranteed response time | Not implied | SLA must be explicitly agreed |
| OEM equipment repair | Not automatically | OEM / specialist support may be required |
| Plant operational responsibility | No | Remains with customer’s authorized organization |
| Safety / protection system responsibility | No | Dedicated engineered systems remain responsible |
Training & Support FAQ
Is training included with every Siteplore project?
Training scope depends on the commercial agreement. Basic handover may be included in some implementation scopes, while more structured role-based training should be explicitly defined where required.
Can training be customized to our facility?
Yes. Training is most useful when it reflects the actual assets, measurements, dashboards and workflows configured for the site.
Can operators and engineers receive different training?
Yes. Operator, maintenance, engineering and administrator roles can have different learning objectives and technical depth.
Can you train our team on MachineGuard?
Yes where MachineGuard is part of the deployed scope. Training can cover condition-monitoring views, trends, warnings, operating context and important system limitations.
Can you train our team on PowerWatch?
Yes where PowerWatch is deployed. Training can cover relevant electrical measurements, energy trends, comparison and interpretation within the available metering scope.
Can you train our team on RekaSense?
Yes. Training can include sensor context, field-device communication, monitoring views and basic troubleshooting appropriate to the deployed configuration.
Does training certify our technicians?
Not automatically. Siteplore training is intended for knowledge transfer and operational enablement. Formal certification requires a separately defined certification framework where applicable.
Can support be provided remotely?
Remote support can be considered where the issue, system access, customer policy and technical conditions permit it.
Can Rekacipta provide on-site support?
On-site support can be scoped where physical inspection or field work is required. Travel, access and site requirements should be included in the commercial scope.
Is 24/7 support available?
No 24/7 commitment should be assumed unless a specific support arrangement, service window and commercial agreement explicitly define it.
What happens if a sensor stops sending data?
Troubleshooting can begin by checking the measurement source, power, communication, edge device and Siteplore data path. Field intervention or specialist support may be required depending on the cause.
Does support include replacing failed hardware?
Hardware replacement should only be considered included where it is explicitly part of the agreed support scope.
Can training be repeated when new employees join?
Yes. Refresher or onboarding training can be arranged as a separate or ongoing support activity.
Can the training include data analytics?
Yes where the deployed Siteplore scope includes analytical workflows and suitable data. The training depth can be adjusted for engineering or management users.
Can support include changing dashboards or alerts?
Configuration changes can be considered within an agreed support or improvement scope. Changes should be reviewed against the operational objective before implementation.
How should we start?
Identify the Siteplore products already deployed, the people who will use them, the level of technical knowledge required and whether the need is initial handover, structured role-based training, troubleshooting support or ongoing assistance.
Do not let your monitoring system become a dashboard nobody fully understands.
Rekacipta can help your operators, maintenance teams and engineers understand the deployed Siteplore system, interpret its information, troubleshoot the monitoring path and continue improving how operational data is used after commissioning.