UX / Product Design / Design System

Mod-X Engineering Change Control

A guided Engineering Change Control System revolutionizing how Bruce Power handles change processes within engineering programs

Client

Bruce Power

Sector

Nuclear Energy Generation

My Role

Product Design Lead

Timeline

8 months

Introduction

Mod-X is an Engineering Change Control system, designed to revolutionize how Bruce Power handles the change processes within its engineering programs. This design report outlines the key design principles, considerations, and features that contributed to making the Mod-X app an intuitive and efficient tool for enhancing collaboration and streamlining change management.

Background

Bruce Power is a major energy provider in Ontario. They are Canada's only private sector nuclear generator, annually producing 30% of Ontario's power.

The main goal of Mod-X is to allow engineers to focus on core engineering tasks by reducing the administrative tasks/burden related to the change process by 20%.

Project Objectives

Efficiency

Eliminate the paper-based Engineering change process to increase efficiency

Accelerate Change Approval

Reduce the time taken for change requests to be reviewed, approved, and implemented

Improve Communication

Enhance communication among cross-functional teams involved in the change process

Enhance Traceability

Establish a robust system to trace changes back to their origins, providing a clear audit trail

Minimize Errors

Reduce the likelihood of errors associated with manual data entry and communication gaps

Quality & Compliance

Add quality and compliance checks to the process, digitizing all forms and reference documents

User Struggles

01

Complicated Process Documentation

The document used as a guide for the change process was a 500 page manual that detailed the tasks that needs to be completed in order to make an engineering change. This was not a straight forward process because depending on the type of engineering change being made, the engineer needed to go through a complex matrix to determine the relevant tasks to be completed.

02

Process Breakdown

Due to the manual nature of the process, engineering changes tend to get lost during the review and approval stage leading to a lot of rework. Most of the comments made by the reviewers were usually made via email or stickies which were not able to be tracked and often lost.

03

Lack of Oversight

Engineering managers where not able to view all engineering changes being processed and their current status. They had to rely on individual reports which were not always frequent or detailed enough.

Getting To Know The Users

Three primary user personas were identified to guide the design process:

👨‍💻

Engineer (Initiator)

Responsible for initiating change requests and providing detailed information about proposed modifications.

Approver (Reviewer/Approver)

Involved in reviewing and approving or rejecting change requests based on technical, financial, or other criteria.

⚙️

Administrator

Manages system settings, user roles, and oversees the overall change management process.

Key Features

Guided Workflow

The system provides a set of questions that when answered, recommends the specific engineering change to be completed by the user. Once that is confirmed by the engineer, the system collates all the necessary forms into a task list and guides the user through completing them.

Intuitive Dashboard Layout

The dashboard provides a quick overview of the ongoing engineering change, the task completed, their statuses, and any pending actions (deliverables). Each user persona sees tailored information relevant to their role, promoting a personalized experience.

Automated Workflow

The system automates the approval workflow, ensuring change requests are routed to the appropriate stakeholders based on predefined criteria. This not only accelerates the approval process but also reduces the likelihood of errors associated with manual routing.

Document Management

A centralized repository for all relevant documents, including design specifications, drawings, and impact assessments, ensures that team members have easy access to essential information during the change management process.

Design Considerations

User-Centric Design

The design prioritizes the needs of end-users, ensuring a seamless and intuitive experience throughout the change management process. User feedback was actively sought and incorporated into the design, promoting a user-centric approach.

Accessibility

The app adheres to accessibility standards, making it inclusive and usable for all team members regardless of their abilities. This includes considerations for color contrast, keyboard navigation, and screen reader compatibility.

Consistency

A consistent design language is employed throughout the app to reduce cognitive load on users. Consistent navigation, layout, and visual elements create a cohesive and familiar experience, enhancing usability. A custom design system was created and implemented.

Efficiency

The design focuses on minimizing the number of steps and interactions required to complete tasks. Streamlined workflows and intuitive navigation contribute to increased efficiency in initiating, reviewing, and approving change requests.

Conclusion

The design of the Mod-X app is centered on providing an intuitive, efficient, and collaborative experience for users. By adhering to user-centric design principles and incorporating feedback from diverse user personas, the app aims to transform how Bruce Power manages change processes, ultimately enhancing productivity and transparency within the organization.