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.

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.

PowerNet is a New Zealand Electrical Distribution Business (EDB) and a partner client of Risk Mentor. They have agreed that RM can share some information about how working with RM delivers multiple business improvements.

The use case for the PowerNet Critical Control Framework Project deployment was to:

• Engage with all employees
• Improve the management of critical risks
• Declutter health and safety management systems for field use
• Streamline due diligence reporting and decision making

Linking critical risks, their controls and verification:

• The status of controls for critical risks is generated directly from the operationally integrated workflows used daily by field staff.
• The workflows were developed with and for field staff and support them to plan and execute assigned tasks.
• For each task phase there are prompts for field staff to apply required controls.
• Their decisions through task planning and execution steps are captured for reporting and analysis.
• This means that performance reporting and verification of controls is constant and is based on a ‘work as done’ reality.

Design and logic details are explained in the following video.

Yes. Once the digital infrastructure with a default EDB configuration is deployed, existing digital workflows can be rapidly configured for clients, 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 client 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.

PowerNet is a New Zealand Electrical Distribution Business (EDB)and a partner client of Risk Mentor. They have agreed that RM can share some information about how working with RM delivers multiple business improvements. The RM Configured Digital Systems Model develops and applies low-cost bidirectional data bridges that link to existing company systems e.g. HR training records, Learning Management Systems etc. In the PowerNet deployment, training and competency status for each system user is regularly updated directly from their HR database. This information is sorted and pushed to Field Portals for use during task planning and role assignment. Only field staff with the required competency can be assigned to specific roles in the workflows e.g. for live line work, crane operations etc. This includes recording that a competent person has directly supervised another crew member in carrying out a task. Also there are periodic updates for third-party contractors. For efficiency a regular workgroup subset can be set up for as the first screen for role assignments when using the Field Portal. This saves users scrolling through lists of all personnel in that business unit with the required competency. In addition, field records of role assignments (operational logs) are searchable by individual profile. This means that this information can be actively linked to profiles in Learning Management Systems and HR Training systems. This capability is expected to be useful to clients who commit to training new staff and apprentices.

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.

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.

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.

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,

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.

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

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 a customised 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.

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. 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 then performance improves. There is a two-way benefit: • Field teams get info they need to make the right decisions • Management, the Senior Leadership Team and the Board in turn get structured, contextual, and trustworthy data to inform their decisions. • Success requires a high-trust and primary focus on assisting field staff and the careful use of the generated field data. Once established a digital platform can be incorporate proven approaches to set reminders and track follow-ups, access information e.g. through QR codes, capture and sort voice inputs etc. Once the technical infrastructure is in place subsequent steps to link to and expand the client's business ecosystem are low-cost and can be rapidly prototyped (fail forward approach). PowerNet is a New Zealand Electrical Distribution Business (EDB)and a partner client of Risk Mentor. They have agreed that RM can share some information about how working with RM delivers multiple business improvements.

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.

Yes, a prequalified contractor confirmation is provided as a drop down list that confirms status during task planning. This is information is routinely updated. A bulk upload capability with regular update reminders is part of the default EDB configuration. Using an operationally integrated system module makes further low-cost enhancements for the contractor prequalification process possible e.g. developing an input interface for direct use by contractor companies or the use of auto upload Pdf forms.

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

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.

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.

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. As required, links to dashboards and reports configured for assurance reporting can be rapidly delivered.

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

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).

Our client 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.

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 the client's 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 client requirements to be fully operational by week 26. Click here to view the Work Breakdown Structure for a Typical Electrical Distribution Business deployment.

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.

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

RM charges are calculated on user seats defined across three user categories based on the total number of employees (direct and indirect). We work in bands of 50 personnel.

Importantly, RM clients report a positive return on investment (ROI) from year one that includes configuration and implementation steps. Tangible savings from year two onwards are reported as being between 3 to 5 times costs based on these conservative estimates:

• Employee tool time – 1 hour per week
• Supervisor hours – 2 hours per week
• Support functions – 0.5 hours per week
• Manager monitoring – 1 hour per week
• Director (due diligence) – 0.5 hours per week
• Systems integration – 1 hour per week

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.

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).

Generally, we co-develop a specific innovation roadmap with our clients to fit into and increase the usefulness of their 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.

The RM data model schematic is reproduced below. Our next innovation based on using a bounded AI agent has already been prototyped. Other upgrade examples being explored include using equipment QR codes in workflows to provide the right information at the right time to field staff. This innovation will further streamline how task step relevant information, manuals, and other information is provided for field users using the RM Field Portal. While the concept has been proven in our staging platform, an offline information syncing capability is required before production deployment.

Click here to view the RM Integrated Solution Components with Content Sources and Data Flows schematic.

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 to other field operations e.g. asset maintenance, gas management, service contracting etc.