RiskMentor Header
Risk Mentor × Horizon Energy Group | ToR Response

Executive Summary

HEG seeks: (A) a field-friendly, mobile-first risk tool supporting Take Five, JSEA and SSSP with live variation management; (B) a competency system aligned to the Common Competency Framework with alerts and real-time reporting; and (C) an equipment/PPE compliance system with certification, calibration and expiry alerts. Risk Mentor proposes Field Portal (FP) + Governance & Performance Reporting (GPR), underpinned by our Control Framework Architecture (CFW), to deliver all three streams across Utilities Group and Horizon Networks.

Mobile & Offline

Android/iOS, full offline capture, auto-sync with conflict resolution; downloadable forms and cached libraries.

Variation Management

“This job has changed” prompts, pause/update/re-approve JSEA/SSSP, hazard flags, escalation.

Decision Intelligence

Live dashboards, audit trails, leading indicators, export to Power BI/Excel.

Timetable: Start 8 Sept 2025 → Proposal due 19 Sept 2025 → Demos 23–25 Sept 2025. Thin-slice discovery-to-pilot in 12–16 weeks with measurable adoption and data-quality KPIs in Q1.

Part A — Operational Risk Management Software Tool

Context & Objectives

The use case for deploying the Risk Mentor (RM) approach at PowerNet focused on supporting field staff to improve the management of critical risks and developing a reliable process to deliver outcomes effectively. The structured digital workflows are designed for and with field crews and incorporate task planning, hazard identification and control, and management of variations.

Fit to Terms of Reference

Table 1 in Appendix 3 and our supporting web page provide details of how this integrated digital approach meets and exceeds the ToR requirements for Part A - Operational Risk Management Software Tool.

Risk Mentor | Part A Features
Operational Risk Features
Field Staff - Mobile and Offline Capable Platform

RM inForms — Built with Frontline Teams

The RM inForms application runs on both Android and iOS, designed hand-in-hand with frontline teams. It ensures workers receive the right resources to complete their workflows, while also capturing the key information they return — demonstrating professionalism and accountability in task execution.

Risk Mentor inForms Application
Capturing Variations

Structured Workflows — Handling Challenges

Structured workflows immediately flag when there is a challenge in executing an activity in line with requirements. This ensures teams can respond quickly and apply safe, compliant alternatives.

Strengthening Control Implementation

Reinforcement of Control Implementation

Field and leadership reinforcement of the requirement to implement controls is achieved through:

  • Reminders for field crews on the control expectations
  • Records (and photographs) by field crews of controls implemented as tasks are performed
  • Field inspections by supervisors and leaders with prompts to confirm controls in place
Digital Record of Risk Conversations

Capturing Conversations & Considerations

Conversations and considerations are captured directly in text fields within relevant forms completed by field teams and leadership during in-field inspections. This ensures that risk decisions and justifications are recorded consistently for accountability and future review.

The second video shows how RM clients have used the platform in a different setting. A pre-start briefing form was developed and the shift supervisor would work with the crew at start-of-shift to discuss all of the expected hazards, required responses, and activities occurring during the shift. Workers either sign on directly to the form or the supervisor takes a photograph of a sign-on sheet to create the digital record of presence in the briefing.

Usability under field conditions

Digital Workflows with Ruggedised Devices

Ruggedised or protected mobile devices replace paper-based activity recording, providing frontline teams, supervisors, and leaders with a reliable digital solution. This ensures that up-to-date information is always available, supporting better decision making in the field.

Capturing risks and variations

Recording Task Execution & Managing Variations

In-field team members can record their execution of tasks and identify conditions that require attention. Changes in equipment state, skilled personnel availability, or shifts in the work environment are logged, with guidance provided on the best responses to different levels of variation. Risk consideration workflows support structured decision-making — for example, describing an unwanted situation and referencing a TARP (Trigger Action Response Plan) review process.

Synching Information to and from the mobile devices

Offline Operation & Sync Process

The default configuration is designed for offline operation. Data is stored safely in-field and exchanged automatically when devices connect at Wi-Fi–enabled offices or workshops. This approach avoids corruption of data caused by patchy mobile coverage, ensuring reliability for teams working in remote or dynamic environments.

Integration with Business Systems and Ease of Use

Integration with Business Systems

Risk Mentor integrates seamlessly with existing business systems to reduce duplication and make data easier to use in the field. Information is updated directly from trusted sources, ensuring frontline teams always have the latest job lists, competencies, and equipment records at their fingertips.

  • Daily or scheduled updates from HR, maintenance, and financial systems
  • APIs and secure bridges connect master databases with RM workflows
  • Field teams see contextualised information where and when they need it
Integration with business systems
Functionality on mobile devices

User-Centred Workflow Templates

Workflow templates are designed with in-field users to ensure usability and relevance. Depending on the application, the questions, responses, and overall look-and-feel are adapted to match the task and context. The native application, available on both Android and iOS, as well as an online form tool, is compliant with platform requirements — ensuring smooth operation on whatever device is being used.

Workflow template functionality
Offline capabilities and auto-sync feature

Offline Functionality

The Risk Mentor platform is built for offline operation, ensuring teams can work without interruption in remote or low-connectivity environments. Data is stored locally on the device and synchronises automatically when a stable Wi-Fi or network connection becomes available. This guarantees that no records are lost and frontline staff can continue working productively, regardless of coverage conditions.

Downloaded information as a decision making aid

Flexible In-Field Information

The types of information downloaded to the app are completely flexible and tailored to the requirements of in-field users, helping them make better real-time decisions.

  • Traffic management plans for relevant work areas
  • Competency records for frontline workers
  • Compliance dates for equipment (e.g. roadworthiness certificates)
  • Approved contractor information
  • Procedures and key references (e.g. TARPs)

Screenshot to come

Prompts for changes to expected site conditions

Key Questions in Workflows

Key questions are included in workflows to prompt in-field workers to rethink their decisions. Prompts around prevailing weather conditions, road conditions, equipment status, and the presence of public or third parties in proximity are all included to help workers make the best decision about how to progress their tasks. In some cases — where conditions are unfavourable — the best decision is to defer to senior team members, who may provide additional resources or endorse rescheduling until conditions improve.

The second video shows how the App can be used to access source material from the database. In this case - the video shows a user accessing a Trigger Action Response Plan (TARP) for weather conditions. The TARP provides guidance on expected responses by field-workers based on the prevailing conditions.

Options to pause, update, or reapprove a workflow

Approval Gates in Workflows

Workflows embed all the requirements of Job Safety and Environment Analyses (JSEAs) and Site-Specific Safety Plans (SSSP). They include structured trigger point questions that, if they cannot be confirmed, prompt workers to seek formal approval before proceeding with the task. When a workflow reaches an approval gate, guidance is provided on the next steps. If the requirements cannot be met, the workflow triggers a reapproval process, typically involving supervisor or manager sign-off before work can continue.

Flagging of new hazards, allowance for environment changes, changes to crews

Key Checks in Workflows

Particularly when a workflow is being used to guide a work team, there are some key checks required. The responses to these checks help frontline team members determine the appropriate next steps. These checks may include direct links to Trigger Action Response Plans (TARPs), ensuring decisions are informed and aligned with safety expectations.

Beyond the application of text information in available form fields - an option is available to enable an actions module on the app. With this enabled, in-field users can create and close out actions - providing commentary and photographic records of the actions taken. The video shows an action being raised and closed out.

Live Dashboards

Dashboards & Drill-Down Insights

Dashboards provide real-time visibility across the portal and the connected Metabase platform. They allow users to drill down into detail on a wide range of items, ensuring leadership and field teams have the insights they need to act decisively.

Review and sign-off of variations

Supervisor Sign-Off & Permit Integration

Workflows include dedicated sections for supervisor sign-off, ensuring critical tasks and permits are formally approved before work proceeds. This provides accountability, traceability, and compliance at every stage of operations.

Review of identified hazards - risk registers

Hazard Controls & Strategic Risk Tools

Hazards in most work environments are generally known. The workflows guide teams in confirming the adequacy of controls in place for those hazards, ensuring they remain effective and relevant. Beyond day-to-day hazard checks, Risk Mentor supports the use of Credible Failure Modes (CFMs) as a strategic tool — offering a more practical and structured approach than continually expanding risk registers. The companion video shows an implementation of identifying hazards during a workflow completion - and then allocating appropriate controls to prevent harm.

Audit Trail

Access to Multiple Sets of Information

Risk Mentor provides access to multiple sets of information, ensuring that users can view dashboards, monitor records, and generate device logs directly within the app. This functionality supports traceability, accountability, and insight into field activities.

Integration with Existing Systems

Training Record Updates

Updates to training records are readily achieved, with changes reflected directly within the app. This ensures that frontline teams always have access to the most current competency information.

Exporting Records

Data Export & Reporting

Risk Mentor supports data export and reporting across platforms. Teams can generate CSV, XLSX, JSON, PNG exports from Metabase, output management plans directly from source information, and produce audit logs for compliance and oversight.

Analytics for Leading Indicators

Activity Records & Leadership Oversight

The platform enables the generation of records of activity, inspections, and leadership interventions. Reports can be configured to deliver value-adding insights that support leadership decision-making, ensuring flexibility while maintaining compliance.

Change Management

Workflow Triggers & Change Management

Workflows include triggers for identifying changes in conditions or requirements. These may introduce stop-points that require a decision before work continues, ensuring safety and compliance. Customisation options allow integration with a dedicated Change Management form or direct connection with external systems, providing flexibility in how changes are managed.

Training - User Guide

Online and static resources available. Frontline build of workflows reduces training and complexity requirements for learning how to use the RM platform.

Role Based Access controls

Role-Based Permissions

The database is structured so that roles define the point of control for create, read, modify, and delete (CRUD) permissions. This ensures that different logged-in users can only access workflows and data relevant to their responsibilities, strengthening both security and operational clarity.

Additional Features

End-to-End Risk Management Lifecycle

Risk Mentor combines all key elements of effective governance into a single system: establishing baselines, guiding safe work through structured workflows, capturing records of activity, and enabling auditing & drift detection. This integrated approach ensures traceability and continuous improvement across the entire safety and compliance lifecycle. Coming soon - video which demonstrates how clauses of relevant statute and standards are connected with workflows in the system.

×
×

Part B — Interactive Competency-Based Training Management Tool

Context & Objectives

The RM integrated solution meets the requirements of Part B by embedding a competency verification step in relevant Field Portal workflows. The status of competencies by person is updated daily from company systems and pushed to the Field Portal, including the NZ EDB Common Competency Framework (CCF) for those working on network assets. Competency details can be organised by work group and depot for efficient field use.

The RM Configured Digital Systems Model provides low-cost bidirectional data bridges to company systems (e.g. HR training records, Learning Management Systems). This enables linking field records to individual profiles, which may be particularly valuable for HEG’s focus on training apprentices.

Fit to Terms of Reference & Options

During pilot work, HEG Utilities Group leaders will advise on the preferred approach from the following options:

  • Option 1: Develop a bidirectional bridge between existing Company LMS or training databases (multiple systems). Records maintained through existing system interfaces.
  • Option 2: Develop a bidirectional bridge with a single Company LMS or training database. Records maintained via the existing system interface.
  • Option 3: Develop an integrated LMS within the RM ecosystem. RM provides infrastructure; records maintained via a new interface across HEG. Not costed in this proposal, but expected to be a low-cost and flexible option compared to standalone LMS.

Table 2 in Appendix 3 and our supporting web page provide further details on how the RM approach addresses the ToR requirements for Part B — Interactive Competency-Based Training Management Tool.

Risk Mentor | Part B Features - Competency Framework
Competency Framework Features
Competency Framework - setup and maintenance

Interlinked process map with relative competencies that can be clicked through as needed. Dashboards generated on training matrix as loaded through the portal or generated from legacy records of training. Refresher requirements provided by automated report or app-based actions.

Competency Framework Setup
Worker skill tracking

Skills Setup & Workflow Integration

The platform provides the ability to set up and manage skills, then integrate these skills into workflows where they are required. This ensures that only competent workers perform tasks requiring specific qualifications or training.

Refresher Training requirements

Refresher Training Requirements

Dynamic training matrix can be used to automatically generate refresher training requirements. This is pushed to management teams via email summaries or immediate alerts via actions module on app.

Compliance management

Compliance Management

Workflows incorporate compliance management controls by ensuring that only people with the requisite skills are able to progress the workflow. If the required skills are not available, the workflow will stop and require external approval to continue.

Skills Expiry alerts

Skill Expiry Alerts & Actions

The system can automatically flag expiring and expired skills across the workforce. These alerts can be delivered via dashboards, email notifications, or through actions generated within the mobile app for immediate attention.

Skills status reports

With all of the information on workers skills loaded into the database - it is then a straightforward process to generate skills reports for the RM site. Skills reports - as a PDF or a data table will provide a summary of skills that would historically be loaded to the organisation's intranet or safety website.

Ease of maintaining competency requirements

Competency records are maintained as top-level objects in the RM system. (Typically using document metadata in the backend). This makes the creation, editing and updating of records very simple. So when a new person arrives or an existing person completes a qualification - it can be captured very quickly.

Training dashboard information

Training dashboards provide guidance on the status of skills. These are flexibly generated from the RM database.

Trainer provider records

Training records are stored as objects (document metadata) in the RM platform. Information provided by training organisations can be held for auditing - or, in some circumstances, training records from providers could be exchanged by the application of Application Programming Interface (API).

Realtime reporting for workers and teams

In the first instance drop downs provide guidance for frontline teams that the people being deployed to jobs are appropriately skilled for that job. Additionally, live dashboards can be used to provide real-time visibility of skills status across teams.

Management of variation

Where workers present on a job do not have the required skills - then this triggers a stop-job action and escalation to management. Management (supervisors or managers) can then provide an approval if other risk mitigations are deployed to manage the situation.

Synching functionality

Mobile devices, when synched, are updated with all relevant training records. Also, records of skills used in the execution of a job in-field are synched back to the RM database.

Integration options

Similar to records from systems such as SAP and Maximo - scheduled data summaries from other applications can be delivered to the RM database for consumption and deployment to field teams.

Information and Summaries for team members

Multiple summaries are possible.

Worker skills currencies. Supervisor summaries of skills mix and upcoming refresher requirements. Management summaries on trends in skills acquisition and current capability within the organisation.

Alignment with Electrical Distribution Industry

The PowerNet sample shown in the video references the EDI skills codes and their application.

Real time variation management

Similar to information and summaries - absence of available skills can be readily highlighted and addressed with appropriate in-field interventions.

Ease of use

Training currency records are available as drop-down items in workflow forms. Training records can also be reviewed and updated directly via the web portal, making administration straightforward.

Compatiblity with other systems

The RM solution allows for low-resource integration with other systems. In the sample video drop-downs are generated from SAP and Maximo data sources - allowing RM workflows to reference the external information.

Implementation overview

RM have worked with other clients in the preparation of online courses. If HEG are interested in this - then these courses can be linked to within the RM app. On completion of a micro-course certificate of completion records can be loaded to the platform. This aligns with HEG practice and ensures that workers who have attended the online micro-courses as a component of the skills development and refreshers have been verified as competent to exercise those skills.

×

Part C — Equipment Safety, Certification & Compliance Management System

Context & Objectives

RM Integrated Solutions in other sectors have been successfully configured to manage all aspects described in the Terms of Reference. This includes equipment safety, certification tracking, calibration management, and compliance monitoring, ensuring assets remain safe, reliable, and audit-ready.

Fit to Terms of Reference

Table 2 in Appendix 3 and our supporting web page provide details on how the RM integrated digital approach can meet and exceed the ToR requirements for Part C — Equipment Safety, Certification, and Compliance Management System.

Risk Mentor | Part C Features - Equipment Management
Equipment Management Features
List of equipment and categories

The RM Platform has a class of objects - Machines - which can contain any number of components. Other classes of objects are Users - Organisations - Actions - Workflow Templates - Workflow Instances - Groups - Dashboards - Files - Reports. The video demonstrates the navigation to the machines class, and from there - the selection of one machine to show associated components. The list of machinery and components is available on the App as a drop down and to desktop users through the web portal.

Compliance testing dates

From the listing of components the various certificates and documents connected can be analysed. The video shows a compliance status report on components.

Compliance certificates and calibration certificates

The video shows how the additional information on the supporting documents for each component can also be extracted from the report. This opens to the actual certificate or stored information for audit or regulatory purposes.

Compliance and Calibration expiry alerts

The compliance status report can be used to trigger expiry alerts from the system. These can take the form of emails or automatically generated actions on the app.

Assignment of equipment (to people or vehicles)

RM components and machines have an ability to be assigned to one or more role holders. The video shows the assignment of ownership to equipment and the follow on to creation of drop-down lists in workflows.

Bulk uploads to maintain data

As for other similar questions - the system allows for multiple ways to enter information. Where there is an existing equipment register - this can be uploaded to create the RM machines and components classes. Where SAP or similar applications already have the information - then records can be integrated by scheduled updates from the external applications. Where training providers or calibration companies can be engaged - they can supply data files to be upload from existing structures.

Realtime reporting of equipment state

The component status report addresses the known information on the equipment. In-field reports on equipment state occur through the workflow functionality. For instance, if a workflow has a trigger-point question about the safety rating of a harness, and upon checking, it is found that the safety certification is out-of-date or that the harness is damaged - then this can be reported back for action.

Management of variations

As for variations to training and process steps - the in-field mobile app can provide reminders and checks on equipment at critical steps. If these checks cannot be satisfied (or there are variations present) then these are captured in the workflows - or trigger escalation or actions to be completed. In this way - variations are able to be actively managed. For instance, if harnesses are required for working at height, a workflow can check that harnesses are present and in-certification. If not, the workflow stops and requires additional harnesses to be brought to site before the task continues.

Synching

Synching of component and equipment information occurs in a similar way as for other aspects of the RM platform. Records are synchronized between the mobile devices and the central database, ensuring all teams have access to the latest equipment status and certification information.

Synching functionality
Integration for field and supervisory staff

Dashboards and updated drop downs achieve integration of information across the organisation.

Information for key role holders

As for other points - information is available via dashboards and can also be the source of follow up actions for any organisational role.

Equipment compliance with Electricity Industry requirements

RM achieves demonstrable compliance in a number of ways.

  1. Specific requirements of the SMEI are codified into workflows (i.e., a ladder workflow would only permit one worker on a ladder at a time, and that workers must have completed BSAFE height training).
  2. Source information for regulatory requirements is preloaded on the mobile devices, available for reference by all field staff.
  3. The database can be used to query the linkages between procedural requirements and the practices to test that they are linked effectively (this is done through the desktop portal). This is particularly relevant for Electricity Industry requirements and other regulated industries.
Real-time variation management

Where equipment is non-conforming (as for management of variations) it can be flagged for frontline teams. Escalation and intervention pathways are then available.

Escalation pathways to supervisors

Workflows have trigger points to communicate with supervisors. There is also the ability to add a communications layer within the Risk Mentor platform to allow for secure notifications being raised and addressed. This can integrate with email and actions modules as required.

Compatibility of information flows to and from other systems

Similar to other aspects - where other systems are the location for single-point-of-truth data, then scheduled updates can populate the RM database. This allows RM mobile devices to present the correct information to field teams. If errors are found, they can be corrected and fed back.

Implementation overview

This is covered in the WBS in more detail. In brief, the intent would be to:

  1. Generate equipment and components lists
  2. Upload current certification information
  3. Update workflows to reference relevant equipment where required
  4. Develop maintenance of information processes so that fresh certifications are captured when they occur
×

Part D - Further Questions from HEG - 30/09/2025

Addressing HEG's Inquiries

We welcome the opportunity to provide further clarification on the points raised by the Horizon Energy Group (HEG). Our approach is to address each question directly and transparently, ensuring our proposed solution aligns with the group's objectives and environmental considerations.

Comprehensive Responses

This section is dedicated to providing detailed responses to the specific questions posed by HEG. We aim to demonstrate a thorough understanding of the concerns and illustrate how our integrated system is designed to meet these specific challenges effectively and responsibly. Further details will be elaborated upon below.

Risk Mentor | Part D - System Capabilities
Core Functionality Risk Management
How does the system support Take 5 / dynamic risk assessments?

The RM integrated digital system supports all the outcomes delivered by using paper and digital paper approaches for pre-task (e.g. Take 5) and dynamic risk assessments through using task workflows. This approach centres on supporting field staff with tailored workflows that have been developed for and with them and it has multiple other business benefits. A digital workflow approach is both tailored and flexible and its primary purpose is to assist field staff to plan and execute their assigned tasks safely and productively across their workday. This includes adjusting and adapting as things change e.g. identifying additional critical risks and new hazards and confirming that required controls are in place. Overview: • Pretask planning and risk management processes are configured into each workflow in ways that are directly relevant to the activities being undertaken. • This means that field staff do not have to adapt and apply a generic paper format, instead the specific activity related critical risks, hazards and control details are built-in. • Critical risks, hazards and their controls covered in the default EDB configuration include electricity (isolation, MAD, and working live), working at height, vehicle movements, load shifting, off road access, noise, dust, temperature, etc. • Importantly, the workflows also capture work environment variables arising from location, weather, time of day, and interactions with other workgroups, members of the public etc. • Also included is a simple task planning workflow that allows users to identify hazards and confirm that controls are in place before commencing work. This option is used for short-duration and low risk tasks e.g. by planners confirming access for future construction works. If a task is repeated several times then a specific workflow is usually built. Further details: Task specific planning prompts and information are built into workflows to assist field staff identify and control critical risks and hazards across their workday, for example: • Start-of-day workflows assist crews confirm that required equipment and materials are onboard and that vehicles and trailers are fit for use with loads are secured. • As required, a workflow for off-road travel may be used, followed by site set-up, electricity isolation and reenergising, use of cranes, working at heights, lifting, phase checking, and making good the site at the end of the job. Each workflow prompts field staff to systematically consider and control risks and hazards for present for the task or task phase. The workflow is an ongoing good practice reference that supports and captures ‘work as done’ decisions and the status of controls through each task phase across the workday i.e. there is a comprehensive operational log of task planning and hazard control decisions. • Ongoing support for decisions across each task phase through the day differs significantly from typical paper or digital paper JSEA, Take 5s, or equivalent processes. These are usually based on generic forms and once completed are are rarely referenced through the workday. • A digital approach also supports staff to pause and reassess control adequacy and make necessary changes during task execution. • It also makes important references and details of standard work processes available when required. This provides default direction in defined situations. Some examples include Trigger Action Response Plans (TARPs) for pole top rescue, COVID19 responses, and interactions with members of the public. Others include providing immediate access to structured task instructions e.g. when recovering stuck vehicles or making changes to lifting plans because of space restrictions requiring short jacking etc.

Can it handle JSEAs / energy wheel or other structured risk tools?

Yes. The RM Form Builder tool allows the addition of graphic information added to digital workflows for field staff. An embedded example is provided on the companion webpage. The application of this approach and others can be field tested during the project pilot phase. Further, once included and identified in task workflows, hazardous energy data points can be used for reporting and analysis e.g. when and how controls are applied and potentially with field staff feedback on control effectiveness. The Energy Wheel graphic or other supporting information can be added to any assessment as a subform with immediate deployment.

How does it link critical risks to controls and verification?

Please note that the PowerNet Critical Control Framework Project Use Case behind the development of the default EDB configured integrated system offered in this proposal, was to improve the management of critical risks, along with streamlining of health and safety management systems for field use. Information on the management of critical risks is derived directly from the use of Field Portal digital workflows. Importantly, the workflows were developed with and for Field Staff and are based on their needs. This means that application of controls for critical risks and hazards are operationally integrated across work planning and execution processes. Importantly this information is captured.

Can incidents, near misses, hazards, audits, and compliance tasks all be logged in one place?

Yes. Once the digital infrastructure with a default EDB configuration is deployed, existing digital workflows can be rapidly configured for HEG, and new workflows developed using RM Form Builder tool, as required. Potential approaches relevant to this question are developed below: • RM can rapidly develop and test a workflow, or workflows, that deliver all HEG requirements for incident reporting and management, along with near miss, hazard, and defect reporting • Field audits - RM can build from already deployed senior management observation workflows. • In addition other workflows e.g. for asset inspections can be rapidly developed, prototyped and iterated following this approach: develop the use case, confirm information required, set up bridges to and from other business systems, (or build a new module). • Recording compliance outcomes and processes - through adapting existing workflows or developing new options as required e.g. test dates for equipment through to actively deploying actions plans from systems audits. Notes: • Further options for capturing, sorting, and using data can be developed rapidly depending on the use case. • The Field Portal App already has a built-in action generator that links to an action escalation and status tracking capability in the Digital Systems Model Platform. • There is also a capability to link and group multiple actions as a single project, or by role, function etc.

How does the system ensure workers are trained and competent before work starts? (integration with training/competency records)

The RM integrated digital system supports all the outcomes delivered by using paper and digital paper approaches for pre-task (e.g. Take 5) and dynamic risk assessments through using task workflows. This approach centres on supporting field staff with tailored workflows that have been developed for and with them and it has multiple other business benefits. A digital workflow approach is both tailored and flexible and its primary purpose is to assist field staff to plan and execute their assigned tasks safely and productively across their workday. This includes adjusting and adapting as things change e.g. identifying additional critical risks and new hazards and confirming that required controls are in place. Overview: • Pretask planning and risk management processes are configured into each workflow in ways that are directly relevant to the activities being undertaken. • This means that field staff do not have to adapt and apply a generic paper format, instead the specific activity related critical risks, hazards and control details are built-in. • Critical risks, hazards, and their controls covered in the default EDB configuration include electricity (isolation, MAD, and working live), working at height, vehicle movements, load shifting, off road access, noise, dust, temperature, etc. • Importantly, the workflows also capture work environment variables arising from location, weather, time of day, and interactions with other workgroups, members of the public etc. • Also included is a simple task planning workflow that allows users to identify hazards and confirm that controls are in place before commencing work. This option is used for short-duration and low risk tasks e.g. by planners confirming access for future construction works. If a task is repeated several times then a specific workflow is usually built. Further details: Task specific planning prompts and information are built into workflows to assist field staff identify and control critical risks and hazards across their workday, for example: • Start-of-day workflows assist crews confirm that required equipment and materials are onboard and that vehicles and trailers are fit for use with loads are secured. • As required, a workflow for off-road travel may be used, followed by site set-up, electricity isolation and reenergising, use of cranes, working at heights, lifting, phase checking, and making good the site at the end of the job. Each workflow prompts field staff to systematically consider and control risks and hazards for present for the task or task phase. The workflow is an ongoing good practice reference that supports and captures ‘work as done’ decisions and the status of controls through each task phase across the workday i.e. there is a comprehensive operational log of task planning and hazard control decisions. • Ongoing support for decisions across each task phase through the day differs significantly from typical paper or digital paper JSEA, Take 5s, or equivalent processes. These are usually based on generic forms and once completed are are rarely referenced through the workday. • A digital approach also supports staff to pause and reassess control adequacy and make necessary changes during task execution. • It also makes important references and details of standard work processes available when required. This provides default direction in defined situations. Some examples include Trigger Action Response Plans (TARPs) for pole top rescue, COVID19 responses, and interactions with members of the public. Others include providing immediate access to structured task instructions e.g. when recovering stuck vehicles or making changes to lifting plans because of space restrictions requiring short jacking etc.

Reporting & Analytics
What dashboards are standard?

The default EDB configuration has over 20 dashboards with drill down capability and parameter search setting including: • Reporting on the management of critical risks through to Board level • Field crew performance monitoring for supervisors (partially provided) • Governance monitoring field deployment with advice and feedback to individual field staff. • Analysis and review of business processes. • Specific operational improvement campaigns e.g. short jacking. • Reports on Senior Manager and Board field activities. • Individual work summaries for training log purposes. • Ad-hoc enquires e.g. comments on vehicle inspections. Additional dashboards and reports can be built rapidly, providing the data is available. Note: RM choses to work using a Metabase platform but data streams are exportable to other company data management systems.

Can we build custom dashboards (e.g., risk profiles, heatmaps, leading vs lagging indicators)?

Yes, usually the build is not the challenge. The challenge is finding or capturing and then applying data required to inform decisions. Importantly the RM Integrated Solution supports aggregating data from other sources beyond that generated by the Field Portal. These additional task level data sources can include vehicle speed monitoring, personnel assigned depot, contractor information etc. RM can also provide structured, contextual, trustworthy field data for use with other analytical tool e.g. Power BI. Clients are then able to build their own decision intelligence products independently of third-party vendors.

Can reports be scheduled and automatically emailed to managers/Board?

Yes, sample emails are provided. Note: for governance purposes reports are usually reviewed by a person before sending out. We are also exploring using a bounded AI agent that is able to review reports for errors while comparing current performance to historic (requires about 6 months data before being deployed). It is also possible to send links to reporting intranet password protected web pages with drill down dashboards.

How does it track training compliance vs actual site risk exposure?

As previously explained, there is a built-in function in workflows that prevents the selection of non-competent personnel for prescribed tasks. A secondary assurance and tracking report can be built that confirms • All instances where competent personnel has been assigned (work as documented = work as done) • All instances when roles have not been allocated to any personnel (blank field), and • Processes for immediate notification (on tablet synching) if personnel who are not competent have been manually assigned. The report will provide structured and contextual data based on: • Date, time, location and activity being undertaken by user selected. • Links based on Task Critical Controls • Log on and log off fields • Worked orders for planned jobs,

Usability & Adoption
What does the mobile app look like? Can frontline staff complete a Take 5 / JSEA in <2 minutes?

They can plan out their entire day in this time frame and then update rapidly through the day as required. The FP is a constant companion that supports Frontline Staff decision making across their workday. Workflow templates can be simple e.g. A simple Single Site Assessment for short-duration, low-risk tasks. As required the use of subforms allows a tailored layer build-up based on task complexity e.g. multiple work crews stringing with live aircraft.

Is offline capability available (critical for field work)?

Yes. This capability has been operationally deployed for over 5 years across several industrial sectors.

How many clicks does it take to log a hazard or incident?

One click to open the form if it is set up as an onscreen default. Otherwise two clicks to find and then open the form. Users then move sequentially through relevant fields. Default build-ins are possible e.g. date, time, unique identifying number etc. The form is a dedicated workflow that uses a combination of radio buttons, check box, photograph, and free text entries (with voice to text capability). Concurrent work required during the pilot phase will be the codesign of an HEG module and reporting platform for incident and hazard management. Alternatively, as required workflows can be built to capture information in a format suitable for pushing to an existing legacy hazard and incident management system i.e. the Field Portal can provide an option for information capture. Each reporting form builds depending on the scale of the hazard or incident. This form build-as-required approach supports both straight forward reporting i.e. capturing default information and a few lines of text with some photos while supporting more detailed reporting. More complex workflows capture additional information by adding relevant subforms e.g. for the capture of detailed incident scene data. Personnel are also guided by built-in Trigger Action Response Plans (TARPs) and other resources.

How does the system encourage adoption (QR codes, voice input, reminders)?

The Field Portal assists with task planning and execution. Users report that it is easier to apply than previous approaches (paper or digital paper). Notably, this includes feedback from personnel who have reading and writing difficulties, or for those where English is a second language. System take-up and adoption is designed into the pilot and deployment to full production phases: • Natural and influential field crew leaders are selected for the pilot work. • Key users with extensive field experience work through the pilot phase and graduate into rolling out across the business. • Key users provide coaching on Field Portal use and monitor the forms being synched, as required they follow-up in the field to assist personnel who have questions or who are making mistakes. • Senior leaders through to the Board begin to use their field workflows from week 4 of the pilot. • Updates and the development of new workflows suggested by filed staff are well publicised to emphasise that the tool is designed for field staff. The PowerNet experience is that when previously difficult to access, and task-relevant information such as work order numbers, individual competency status, contractor pre-qualifications etc. is provided to work crews to assist them to do their job then performance improves. There is a two-way benefit: • Field teams get info within a tool that assists them make the right decisions through their working day, the tool makes their workdays easier and more efficient. • Management, the Senior Leadership Team, and the Board in turn get structured, contextual, and trustworthy field data that informs their decisions. • Success requires a high-trust and primary focus on assisting field staff and the careful use of the generated field data. • Once in production, the capacity to record 'work as done' and outcomes achieved supports field staff to self-monitor and demonstrate both their individual and joint professionalism. Once established a digital platform can further incorporate proven approaches that assist people to get their work done. This includes using voice inputs, setting reminders, tracking follow-ups, and the capability to access information e.g. through QR codes, etc. Once the technical infrastructure is in place, subsequent steps to link to and expand the HEG business ecosystem are low-cost and can be rapidly prototyped using a fail forward approach.

Integration
Can it integrate with our HRIS (competency), finance (contractor holds), or LMS?

Yes, the RM technical team have a great track record in developing low-cost bidirectional bridges to existing company ERP systems. This includes developing the capacity to bulk uploads from spreadsheets and databases.

How flexible is API integration?

Developed and deployed. All data gathered is made accessible to client data analysts via a JSON database containing all completed (and synched) forms.

Governance & Compliance
Is the system aligned with ISO 45001, ISO 14001, ISO 9001 requirements?

The operationally integrated digital system enables the operationalisation of company processes used by field staff and other staff working in the field. Therefore, if company processes meet ISO and other requirements, then the outputs from planning and executing tasks using the workflows in turn provides content and process evidence of compliance. This process is supported by mapping all active clauses of each Standard, Legislation, Regulations, Sector Relevant good practice, and company requirements to elements in the Configured Digital Systems Model. This means that a summary of how each compliance outcome is achieved, supported by field records is available. An operationally integrated digital system approach supports this content linking and delivers almost frictionless compliance and assurance outcomes. Please see examples provided. An additional sample document is available on this link.

Can it manage audit trails and version control?

Forms have an audit trail - and all actions inside the system leave a digital footprint that is reviewable. Objects in the system have a persistent version control capability. Further, audits against external instruments (statute and standard) can be readily generated to demonstrate the activity which is occurring to address these external requirements.

How does it support Board-level assurance reporting?

Reports on activities are summarised in reports for Board level review prepared by functional managers. Usually these reports include control status for the management of critical risks and senior manager field activities. David Stevens GM People, Safety and Communications at PowerNet will provide a Board-level assurance example on request. As required, links to dashboards and reports configured for assurance reporting can be rapidly delivered.

Security & Data
Where is the data hosted? (onshore/offshore)

AWS Asia Pacific, we are considering moving to NZ data centre T4 for NZ clients.

What are the cybersecurity certifications (ISO 27001, SOC2, etc.)?

There is a data management policy in place for RM with an additional layer through our current provider (AWS). The primary cyber security control is to limit the collection of sensitive data (personnel information, phone numbers, addresses, etc.) to only to that necessary to achieve outcomes. As required, further security can be applied for sensitive data required for new or expanded modules (e.g. injury details, medical records and insurance etc. for incident management).

Who owns the data if we exit the system?

HEG owns all data collected and stored on their behalf. RM owns the configured foundational data assets (e.g. workflow designs) and platform decision intelligence products, Collectively these are called the RM software in our services and support agreement.

Implementation & Support
Typical implementation timeline?

Default EDB deployment ready for pilot from end of week 2, pilot configuration trials and adjustments until end of week 12, production deployment from week 13, EDB functionality fully operational from week 26. (Subject to HEG project plan and team availability). Reporting with default dashboards from the end of week 2 (once data begins to become available) with ongoing refinement to suit HEG requirements to be fully operational by week 26.

Who configures workflows — vendor or in-house admin?

Our approach is to adapt default EDB workflows as vendor in first instance working with nominated key users and pilot field staff. Ongoing collaborative default EDB modification using vendor support will be flexible and unlimited during the pilot phase. Post pilot through to full production a change management process will be followed to maintain data integrity and systems integration (internal and external). Subject to this change management process, in-house key users will develop the capability for workflow configuration and importantly for content management in the Configure Digital Systems Model.

What training & support is included (e.g., 24/7 helpdesk, account manager)?

Please see an extract from our standard subscription and services agreement.

What is the licensing model (per user, per site, per module)?

RM charges are calculated on user seats defined across three user categories based on total number of employees (direct and indirect). We work in bands of 50 personnel. Our September 2025 proposal assumes 350 personnel providing EDB services as part of this project (band 301-350) When new modules are co-developed such as an LMS or for comprehensive incident management, our approach is to develop at cost plus and negotiate any user seat increases based on ongoing maintenance costs. For further information, please see proposal section 4.2.2. Ongoing Subscription and Services Charges and Annexure C from our standard services and subscription agreement below.

Future-Proofing
How often are updates released, and do they cost extra?

Platform updates are ongoing (happening as needed - typically several times per year and this is included in the subscription). Content updates, such as additional workflow creation or changes to existing workflows are made as per user's change management processes. Simple changes are included and more complex requests are quoted and addressed on a case-by-case basis. As a rule of thumb (based on PowerNet's experience) complex changes can cost up to $5,000 and simpler changes are completed either without charge or for less than $1k. For workflows outside the RM library for EDB's - RM would seek to partner with clients to build the resources on a cost-plus arrangement (acknowledging that the domain expertise is either coming from the client - or drawn from an RM paid third party).

What innovation roadmap is in place (AI, predictive analytics, automation)?

The RM data model is referenced in the proposal, our next innovation based on using a bounded AI agent has been prototyped. Generally we co-develop an innovation road map with our clients to fit into and increase the usefulness of current company data stacks and/or digital business ecosystems. The first step is to confirm where the RM digital integrated system fits and how to link data flows between it and existing company data assets (e.g. ERP systems) and other decision intelligence products. This includes meeting data and privacy requirements for company data and putting in place processes to continually improve component interfaces, data flows, data quality, and how data is used to make better decisions. Upgrades to use equipment QR codes in workflows has been tested in staging. This capability can assist with providing the right information at the right time and streamline now task step relevant information, manuals, and other user information can be made available for field users working on a device. Some of the challenges here are locally synching information for use when working off-line.

Can the system scale across multiple business units and geographies?

Yes, data topology is Enterprise layer with subsidiary business units below this. Unlimited number of business units per enterprise. Business units are not geographically constrained with ability to map multiple time zones across the Enterprise. This included moving beyond EDB workflows i.e. for gas, roofing, HVAC etc.

×
RiskMentor Footer x