Graduate Project in Electrical Engineering – ENEL 687

Project Title: Development of SCADA System for the University of Calgary Electrical Network

Team number: 14

Project Manager:

- Name: Sheheryar Ahmed

- Email: [email protected]
- UCID: 30220459

Members:

Name Email UCID

Muhammad Saribuddin Qadri [email protected] 30229760
Hamza Arshad [email protected] 30205328
Manan Rauf [email protected] 30231067
Muhammad Waqas [email protected] 30219023
Muhammad Sameer Ahmed [email protected] 30220811
CONTENTS
................................................................................................................................................................ 1
1 Glossary ........................................................................................................................................... 4
2 Short Bios ........................................................................................................................................ 6
3 Project Motivation and Objectives.................................................................................................. 7
4 Project Scope and Deliverables ....................................................................................................... 7
4.1 Must-Have Deliverables ......................................................................................................... 7
4.1.1 Development of a comprehensive single-line diagram (SLD) for the university’s electrical
network: .......................................................................................................................................... 7
4.1.2 Identification of field devices and creation of an equipment list: .................................... 7
4.1.3 Generating a typical I/O list with all signals for individual IEDs: ....................................... 8
4.1.4 Development of primary and substation-specific SLDs within the SCADA platform
(Ignition):......................................................................................................................................... 8
4.1.5 Design and implementation of relay faceplates with alarms and input/output
monitoring: ..................................................................................................................................... 8
4.1.6 Comprehensive documentation and report generation: .................................................. 8
4.2 Should-Have Deliverables ...................................................................................................... 8
4.2.1 Integration of predictive maintenance capabilities: ......................................................... 8
4.2.2 Implementation of remote monitoring and control functionalities: ................................ 8
4.2.3 SCADA system user training and knowledge transfer: ...................................................... 8
4.2.4 Historical data logging and trend analysis implementation: ............................................. 9
4.3 Nice-to-Have Deliverables ..................................................................................................... 9
4.3.1 Communication Architecture Design and Implementation: ............................................. 9
4.3.2 Development of a communication health monitoring interface within Ignition: ............. 9
4.3.3 Advanced data analytics and visualization: ....................................................................... 9
4.3.4 Integration with distributed energy resources (DERs): ..................................................... 9
5 Preliminary Design of the Proposed Solution ................................................................................. 9
5.1 System Assessment & Requirement Analysis ........................................................................ 9
5.2 SCADA System Design .......................................................................................................... 10
5.3 Data Acquisition & Communication .................................................................................... 10
5.4 HMI & Visualization Development....................................................................................... 10
5.5 Database & Historian Integration ........................................................................................ 10
5.6 Control & Automation Implementation .............................................................................. 10
5.7 Testing & Validation ............................................................................................................. 11
5.8 Monitoring & Improvements ............................................................................................... 11
6 Alternative Solutions/Methodologies ........................................................................................... 13
 6.1 HMI Software Alternatives: ................................................................................................. 14
6.1.1 Justification for Choosing Ignition: .................................................................................. 14
6.2 Project Site Alternatives: ..................................................................................................... 15
6.2.1 Justification for Choosing University of Calgary Electrical System: ................................. 15
7 IP and Other Legal Agreements .................................................................................................... 15
7.1 Ownership of Intellectual Property ..................................................................................... 15
7.1.1 University-Provided Materials: ........................................................................................ 15
7.1.2 Student-Created Work:.................................................................................................... 16
7.1.3 Software and Platform Licensing:.................................................................................... 16
7.2 Usage Rights and Restrictions.............................................................................................. 16
7.3 Confidentiality and Data Protection .................................................................................... 16
7.4 Publication and Acknowledgment ....................................................................................... 16
8 Technical Specifications................................................................................................................. 17
9 Materials, Supplies, Tools, and Cost Estimates ............................................................................. 18
9.1 Inventory and Cost Estimates Table ..................................................................................... 18
9.2 Cost Summary...................................................................................................................... 18
9.3 Alignment with Project Goals .............................................................................................. 18
10 Risks and Risk Mitigation Plans ................................................................................................ 19
11 Major Technical Tasks and Milestones ..................................................................................... 19
11.1 Sprint-Based Development Approach ................................................................................. 19
11.1.1 Sprint 1 (February 7 – February 28): ........................................................................... 19
11.1.2 Sprint 2 (February 28 – March 28): ............................................................................. 20
11.1.3 Sprint 3 (March 28 – April 11): .................................................................................... 20
12 Roles and Responsibilities ........................................................................................................ 20
13 Measures of Success and Validation Tests ............................................................................... 21
13.1 Measures of Success ............................................................................................................ 22
13.2 Validation Tests .................................................................................................................... 22
13.3 Addressing Potential Deviations .......................................................................................... 23
14 Conclusion ................................................................................................................................ 23
15 Appendix .................................................................................................................................. 24
16 References................................................................................................................................ 25
1 GLOSSARY

SCADA (Supervisory Control and Data Acquisition) – A system used for remote monitoring
and control of industrial processes.
IED (Intelligent Electronic Device) – Devices that provide advanced monitoring, control, and
automation functionalities.
HMI (Human-Machine Interface) – The graphical interface through which operators interact
with the SCADA system.
SLD (Single Line Diagram) – A simplified representation of an electrical system displaying its
main components.
RTU (Remote Terminal Unit) – A device that connects sensors and actuators to SCADA
systems for remote monitoring.
PLC (Programmable Logic Controller) – A digital computer used for automation of industrial
processes.
Modbus – A communication protocol commonly used for connecting industrial electronic
devices.
DNP3 (Distributed Network Protocol 3) – A protocol used for communication in SCADA and
automation systems.
IEC 61850 – An international standard for communication in electrical substation
automation systems.
Historian Database – A database used to store real-time and historical process data for
analysis and reporting.
Relay Faceplate – A graphical representation of a relay’s status, inputs, outputs, and alarms
in an HMI.
Predictive Maintenance – A maintenance strategy that uses data analytics to predict
potential failures before they occur.
DER (Distributed Energy Resource) – Small-scale energy sources such as solar panels, wind
turbines, and battery storage that are integrated into the power grid.
Load Balancing – The process of distributing electrical load across multiple power sources to
optimize efficiency.
Cybersecurity – Measures taken to protect SCADA systems from unauthorized access and
cyber threats.
Data Logging – The process of recording system data over time for analysis and
troubleshooting.
Event Recording – The automatic capture of system events, such as faults and alarms, for
review and analysis.
Fault Detection – The identification of electrical or operational issues in a power system.
Alarms Management – The process of configuring and handling alerts in a SCADA system to
ensure timely response to system abnormalities.
Redundancy – A backup system or component that ensures continued operation in case of a
failure.
2 SHORT BIOS

Sheheryar Ahmed: Sheheryar Ahmed is an aspiring Electrical Engineer with a strong interest in
power systems, automation, and industrial control solutions. He has developed expertise in SCADA
system design, protection relay coordination, and power system analysis. With hands-on experience
in industrial automation, PLC programming, and real-time data acquisition, He is passionate about
integrating intelligent monitoring solutions to enhance electrical network reliability and efficiency.

Muhammad Sarib Uddin Qadri: Muhammad Sarib is an MEng student in Electrical and Computer
Engineering at the University of Calgary with a strong background in industrial and commercial
power systems. He has hands-on experience in SCADA system development, automation, and power
distribution design. His technical expertise includes working with SEL devices, Ignition HMI
development, and real-time data acquisition systems. Sarib’s business interests lie in developing
scalable solutions for energy management and improving the reliability of electrical networks.

Hamza Arshad: Hamza Arshad is an electrical engineer with a strong background in power
distribution, electrical design, and SCADA integration. With over five years of experience, he has
worked on projects ranging from arc flash risk assessments to HV SCADA systems for battery storage
and industrial power networks. Currently, he is deepening his expertise in Distributed Energy
Resources (DERs), focusing on microgrid simulation, renewable energy integration, and real-time
system visualization.

Manan Rauf: Mannan has over a year of experience in integrating embedded systems and designing
HMI and PCBs. His expertise includes microcontroller programming, automation, and digital system
design. With a strong foundation in power systems and renewable energy, he is particularly
interested in sustainable electrical energy solutions and industrial power system optimization.

Muhammad Waqas: Muhammad Waqas has over two years of experience in designing SCADA
systems, specializing in industrial automation, control systems, and remote monitoring solutions. He
is skilled in implementing real-time data acquisition and control strategies to improve system
performance and efficiency.

Muhammad Sameer Ahmed: Sameer Ahmed is an accomplished Electrical Engineer currently

pursuing a Master of Engineering (MEng) at the University of Calgary. With a robust background in
engineering design consultancy and data analytics, he specializes in power systems, circuit design,
and automation. Sameer leverages his analytical skills to extract insights and drive efficiency in
engineering projects.
3 PROJECT MOTIVATION AND OBJECTIVES
The University of Calgary’s electrical network currently lacks an integrated SCADA system, resulting in
inefficiencies in monitoring, fault detection, and real-time operational control. Manual interventions
in critical power distribution scenarios increase the risk of prolonged downtimes and inefficient
energy utilization. The implementation of a SCADA system will address these challenges by providing
centralized control, real-time data acquisition, and automated fault detection.

The primary objective of this project is to develop a scalable and reliable SCADA system that enables
seamless monitoring and control of the university’s electrical infrastructure. The system will leverage
advanced data analytics, real-time event logging, and predictive maintenance strategies to enhance
reliability and operational efficiency. This initiative aligns with the university’s long-term
sustainability and infrastructure optimization goals.

4 PROJECT SCOPE AND DELIVERABLES

The scope of this project is to design and implement a robust SCADA system tailored to the
University of Calgary’s electrical network. The system will integrate real-time monitoring, fault
detection, alarm management, and a user-friendly human-machine interface (HMI). The
development will follow a phased approach, ensuring structured progress from initial data gathering
to system deployment and validation.

To establish clear development priorities, project deliverables are categorized into must-have,
should-have, and nice-to-have features.

4.1 Must-Have Deliverables

These deliverables form the core functionalities of the SCADA system, essential for its successful
deployment and operation.

4.1.1 Development of a comprehensive single-line diagram (SLD) for the university’s electrical
network:

• Requires access to existing SLDs and electrical infrastructure data from the University of
Calgary.
• Ensures a structured representation of power flow and system components.

4.1.2 Identification of field devices and creation of an equipment list:

• Cataloguing all critical components, including circuit breakers, transformers, protection

relays, and metering devices.
 • Defining specifications for data acquisition points.

4.1.3 Generating a typical I/O list with all signals for individual IEDs:

• Ensures proper mapping of input/output signals for real-time data monitoring and
control.

4.1.4 Development of primary and substation-specific SLDs within the SCADA platform
(Ignition):

• Digitizing and integrating the electrical network layout for visualization.

• Configuring real-time monitoring elements for each substation and distribution point.

4.1.5 Design and implementation of relay faceplates with alarms and input/output monitoring:

• Creating graphical interfaces for each IED, displaying operational states, alarms, and key
performance indicators.

4.1.6 Comprehensive documentation and report generation:

• Preparing technical documentation, including user manuals, system architecture

diagrams, and operational procedures.
• Final project report detailing implementation strategies, challenges, and performance
evaluations.

4.2 Should-Have Deliverables

These deliverables enhance system capabilities, improving functionality and future scalability.

4.2.1 Integration of predictive maintenance capabilities:

• Leveraging historical data and analytics to predict potential failures.

• Enabling proactive maintenance scheduling to minimize unexpected outages.

4.2.2 Implementation of remote monitoring and control functionalities:

• Allowing authorized users to access the SCADA system remotely via secure web-based
interfaces.
• Ensuring proper cybersecurity measures for remote accessibility.

4.2.3 SCADA system user training and knowledge transfer:

• Conducting training sessions for university staff and operators.

• Providing hands-on demonstrations for effective system utilization and troubleshooting.
4.2.4 Historical data logging and trend analysis implementation:

• Enabling long-term storage of electrical network performance data.

• Facilitating data-driven decision-making for system optimization.

4.3 Nice-to-Have Deliverables

These advanced features would further enhance the SCADA system’s intelligence, efficiency, and
integration with future developments.

4.3.1 Communication Architecture Design and Implementation:

• Defining a robust network topology for data transmission between field devices and the
SCADA system.
• Ensuring adherence to industry-standard communication protocols such as Modbus, DNP3,
and IEC 61850.

4.3.2 Development of a communication health monitoring interface within Ignition:

• Visualizing communication links and statuses of connected devices.

• Implementing real-time diagnostics to detect network faults and ensure system reliability.

4.3.3 Advanced data analytics and visualization:

• Implementing AI-driven insights for anomaly detection and operational optimization.

• Providing enhanced graphical representations of electrical network behaviour.

4.3.4 Integration with distributed energy resources (DERs):

• Enabling monitoring and control of renewable energy sources, such as solar panels and
microgrids.
• Supporting load balancing and energy efficiency improvements.

5 PRELIMINARY DESIGN OF THE PROPOSED SOLUTION

The SCADA system development follows a structured design process that ensures seamless
integration with the University of Calgary’s electrical infrastructure. The following design framework
outlines key stages of system development:

5.1 System Assessment & Requirement Analysis

Input: Existing SLDs, Electrical Infrastructure Data

Outcome: Comprehensive SLD Development

This phase involves gathering and analysing current network schematics and infrastructure data to
define the functional requirements of the SCADA system.

5.2 SCADA System Design

Input: IEDs Information/Data

Outcome: Equipment List, I/O List

This stage focuses on identifying and cataloguing Intelligent Electronic Devices (IEDs), along with
defining signal inputs and outputs for effective monitoring and control.

5.3 Data Acquisition & Communication

Input: Existing Communication Architecture and Protocols

Outcome: SCADA Architecture

This phase involves establishing a reliable data acquisition framework and designing the SCADA
communication architecture using industry-standard protocols such as Modbus, DNP3, and IEC
61850.

5.4 HMI & Visualization Development

Input: Ignition Software, UI Designing skills, Alarms identification

Outcome: Relay Faceplates, Substation-Specific SLDs

The development of a user-friendly HMI interface ensures clear visualization of electrical network
operations, with relay faceplates and substation SLDs providing interactive control.

5.5 Database & Historian Integration

Input: Alarm/Events/Database Configurations

Outcome: Historical Data Logging, Predictive Maintenance Plan

This phase ensures that system logs, alarms, and operational data are efficiently recorded for long
term analysis and predictive maintenance.

5.6 Control & Automation Implementation

Input: Control Logic

Outcome: Remote Monitoring, System Automation

The system will be equipped with automated control functions, enabling remote monitoring and
optimized operational efficiency.

5.7 Testing & Validation

Input: Designed Prototype and Referenced Documentation

Outcome: Verified SCADA Performance

This stage includes rigorous testing and validation of the SCADA system to ensure reliability, accuracy,
and compliance with design specifications.

5.8 Monitoring & Improvements

Input: System Logs, Performance Reports

Outcome: Future Upgrades, DERs Integration

Continuous monitoring and performance analysis will facilitate system improvements and potential
future integrations, such as Distributed Energy Resources (DERs).

The SCADA system design is structured to ensure seamless data flow, optimal communication, and
real-time system reliability. The proposed architecture enables enhanced network visibility, remote
control, and data-driven decision-making, aligning with the University of Calgary’s
infrastructure goals.
 Input: Existing SLDs, Electrical Infrastructure Data 1. System Assessment & Requirement Analysis Outcome:Comprehensive SLD Development

Input: IEDs Information/Data 2. SCADA System Design Outcome:Equipment List, I/O List

Input: Existing Communication Architecture and Protocols 3. Data Acquisition & Communication Outcome:SCADA Architecture

Input: Ignition Software, UI Designing skills, Alarms identification 4. HMI & Visualization Development Outcome:Relay Faceplates, Substation-Specific SLDs

Input: Alarm/Events/Database Configurations 5. Database & Historian Integration Outcome:Historical Data Logging, Predictive Maintenance Plan

Input: Control Logic 6. Control & Automation Implementation Outcome:Remote Monitoring, System Automation

Input: Designed Prototype and Referenced Documentation 7. Testing & Validation Outcome:Verified SCADA Performance

Input: System Logs, Performance Reports 8. Monitoring & Improvements Outcome:Future Upgrades, DERs Integration

Flowchart for SCADA System Development for University of Calgary

6 ALTERNATIVE SOLUTIONS/METHODOLOGIES
The alternative solutions are based on HMI software alternatives and Project site alternatives. The
Detailed comparison is given below:

HMI Software Alternatives

Criteria Ignition (Current Zenon HMI (COPA-DATA) Wonderware by AVEVA

Choice)
Scalability Highly scalable for Scalable but best suited Highly scalable for
large systems for medium-sized enterprise-level systems
systems
User Interface Modern, web-based Customizable but Intuitive and highly
interface traditional desktop- customizable
based UI
Integration Excellent integration Supports various Strong integration with
Capabilities with SQL, MQTT, and industrial protocols but industrial protocols, SQL,
Python limited Python and cloud services
integration
Cost Lower initial cost with Higher initial cost with High cost, especially for
unlimited tags tag-based licensing large-scale applications
User Community & Large community, Smaller community, less Large community, strong
Support strong support & open resources industrial presence
documentation
Ease of Use Moderate learning Requires specialized User-friendly, but
curve with strong training complex for advanced
support features
Redundancy & Excellent redundancy Good redundancy Industry-standard
Security and cybersecurity features, high security security and redundancy
options options
Time Required for Moderate (well- High (requires High (complex setup for
Implementation documented & easy to specialized knowledge large systems)
customize) and setup)
Resource High availability of Limited availability of High availability of
Availability resources & support experienced trained professionals in
professionals the industry
Project Site Alternatives

Criteria University of Calgary Industrial Plant Commercial

Electrical System Building
(Current Choice)
Data Availability Incomplete but available Readily available Moderate
for collaboration availability
Educational Impact High (opportunity to Low educational Moderate
benefit the university) value educational impact
Implementation Moderate (university High (industrial Low to moderate
Complexity grid systems are systems are more complexity
complex) complex)
Cost and Resource Low to moderate High Moderate
Requirements
Potential for Real-World High (University may High Moderate
Application implement it in the
future)
Time Required for Data High (due to incomplete Moderate to high Moderate
Collection & data)
Implementation
Resource Availability Limited (reliant on High (well- Moderate (easily
university cooperation) documented & accessible
standardized) resources)

6.1 HMI Software Alternatives:

The three HMI software options considered for the SCADA system design are Ignition, Zenon by
COPA-DATA, and Wonderware by AVEVA. The following table compares the tools based on key factors
such as scalability, user interface, cost, integration capabilities, and user community support.

6.1.1 Justification for Choosing Ignition:

Ignition is chosen for the following reasons:

• Scalability and Flexibility: It offers high scalability, making it a good fit for future expansion.
• Integration Capabilities: Its compatibility with a wide range of protocols (such as MQTT and
OPC UA) makes it easier to interface with different devices.
 • Cost-Effectiveness: Ignition provides unlimited tag-based licensing, making it more budget-
friendly in comparison to Zenon and Wonderware.
• Modern Web-Based Interface: This ensures ease of access and user-friendly operation from
multiple devices.

6.2 Project Site Alternatives:

The project site for the SCADA system design is the University of Calgary electrical system, but given
the incomplete data available, we have explored alternative project sites.

6.2.1 Justification for Choosing University of Calgary Electrical System:

• Alignment with Educational Goals: The project site aligns with the university’s goals for
improving its electrical systems.
• Potential for Implementation: If the university management finds the solution feasible, they
may adopt it for real-world use.
• Moderate Complexity: It offers a balance between complexity and practicality, making it an
excellent learning and design opportunity.
• Cost-Effective: Compared to industrial sites, it requires fewer resources and capital for
a design project.

7 IP AND OTHER LEGAL AGREEMENTS

This Intellectual Property (IP) Agreement between the University of Calgary and the student project
team working on the SCADA System Development for the University of Calgary Electrical Network is
provided below. The agreement outlines the ownership, usage rights, and responsibilities regarding
intellectual property developed during the course of this project.

7.1 Ownership of Intellectual Property

7.1.1 University-Provided Materials:

The University of Calgary shall retain full ownership of all existing materials, including but not limited
to single-line diagrams (SLDs), electrical network documentation, historical operational data, and
technical schematics provided to the Project Team. These materials are confidential and are to be
used solely for the purpose of this project.
7.1.2 Student-Created Work:

Intellectual property generated by the Project Team—including but not limited to software code,
reports, system architecture diagrams, and simulation models—shall be jointly owned by the
University of Calgary and the contributing students.

7.1.3 Software and Platform Licensing:

If proprietary software or licensed SCADA platforms (e.g., Ignition SCADA) are used, the licensing
agreements associated with these platforms will govern their ownership and usage rights.

7.2 Usage Rights and Restrictions

• The University of Calgary reserves the right to use, modify, and distribute the developed
SCADA system for academic, research, and operational purposes without seeking additional
permissions from the Project Team.
• The Project Team may use their contributions for portfolio, academic, or research purposes,
provided that appropriate credit is given to the University of Calgary for its resources and
support.
• The Project Team shall not commercially exploit the developed system without written
consent from the University of Calgary. Any commercialization discussions shall involve a
separate agreement outlining revenue-sharing terms.

7.3 Confidentiality and Data Protection

• The Project Team agrees to maintain the confidentiality of any sensitive or proprietary data
provided by the University. No team member shall disclose or distribute confidential
information to external parties without explicit written permission.
• All documentation and code repositories containing confidential university data shall be
securely stored, and access shall be restricted to authorized project members only.

7.4 Publication and Acknowledgment

• If the Project Team publishes academic papers, conference presentations, or technical

reports based on the SCADA system development, proper acknowledgment must be given to
the University of Calgary and any faculty advisors involved.
• The University reserves the right to review and approve publications before submission to
ensure compliance with confidentiality and proprietary considerations.
8 TECHNICAL SPECIFICATIONS
This section outlines the detailed technical specifications and functional requirements of the
proposed SCADA system for the University of Calgary’s Electrical Network. These specifications
define the system’s operational parameters, hardware and software requirements, communication
protocols, data acquisition capabilities, and overall performance expectations to ensure reliable and
efficient monitoring and control of the electrical infrastructure.

Specification Description Requirement/Value

System Architecture Centralized SCADA system with client-server Centralized
architecture
Communication Supports standard protocols for communication Modbus, DNP3, IEC
Protocols with RTUs and IEDs (e.g., Modbus, DNP3, IEC 61850
61850)
Data Acquisition Rate Real-time data acquisition and processing ≤ 1-second interval
capabilities
Data Storage Ability to store historical data for trend analysis Minimum 1 TB
Capacity and reporting
Scalability System must be scalable to accommodate future Up to 200 devices
expansion
Graphical User Web-based user-friendly interface for monitoring HTML5-based GUI
Interface (GUI) and control
Operating System Compatible with modern operating systems Windows/Linux
Power Supply Redundant power supply to ensure uninterrupted 120/240V AC, 24V DC
operation backup
Redundancy System must include redundancy for servers and Full redundancy
communication paths
Security Features Cybersecurity protection, user authentication, Multi-layer security
and encrypted communication (SSL/TLS)
Budgetary Limit No associated cost (academic project) N/A
Response Time Maximum acceptable delay for system response ≤ 1 second
Display Resolution Minimum resolution for HMI displays 1920 × 1080 pixels
Supported Devices Compatible with RTUs, IEDs, and other smart SEL, ABB, Schneider
devices devices
9 MATERIALS, SUPPLIES, TOOLS, AND COST ESTIMATES
The proposed SCADA project is primarily a software-based solution. Therefore, no significant physical
materials or hardware costs are expected at this stage. However, the project requires access to
specific software tools and resources for system design, development, and testing. The following
table outlines the necessary tools and resources along with their cost estimates.

9.1 Inventory and Cost Estimates Table

Category Item/Tool Description Estimated Cost Tolerance

Software Tools Ignition by Inductive SCADA development Academic N/A
Automation platform for HMI/SCADA License (No
design Cost)
Supplies Documentation and Printing, binding, and report $50 ± 10%
Reports preparation
Hardware PC/Workstation High-performance Existing N/A
(Optional) workstation for SCADA University
development and simulation Resources
Network Ethernet Network For connecting simulated Existing N/A
Resources RTUs, IEDs, and SCADA University
servers Resources
Miscellaneous Backup Storage External hard drive or cloud $100 ± 5%
storage for backup

9.2 Cost Summary

• Total Estimated Cost: $150 ± 10%

• Since the project is primarily academic and software-based, most tools are available through
university resources or open-source platforms, minimizing the overall cost. The estimated
cost primarily covers documentation, backup storage, and other minor expenses.

9.3 Alignment with Project Goals

The choice of tools and materials aligns with the goal of developing a scalable and reliable SCADA
system for the University of Calgary’s electrical network. By utilizing industry-standard software tools
and leveraging available university resources, the project ensures cost efficiency without
compromising quality or functionality. The allocated budget tolerance reflects reasonable flexibility
for minor unforeseen expenses.
10 RISKS AND RISK MITIGATION PLANS
The successful delivery of the SCADA system project depends on mitigating potential risks that could
impact timelines, costs, and system performance. Identified risks and their respective mitigation
strategies are as follows:

Delayed access to required data and documentation: If the necessary single-line diagrams and
infrastructure details are not provided on time, the project timeline will be affected. To mitigate this,
early communication with university stakeholders and a phased data acquisition plan will be
implemented.

Software integration challenges: Compatibility issues between the selected SCADA platform and
existing infrastructure could arise. This will be addressed through prototype testing before full-scale
implementation.

Cybersecurity vulnerabilities: The SCADA system is susceptible to cyber threats. Best practices,
including encryption, role-based access controls, and network segmentation, will be adopted to
enhance security.

Knowledge transfer and operator training: Ensuring that university personnel are proficient in
operating the SCADA system is critical. Structured training programs and comprehensive
documentation will be developed to facilitate smooth adoption.

By proactively addressing these risks, the project team aims to ensure successful deployment and
long-term reliability of the SCADA system for the University of Calgary.

11 MAJOR TECHNICAL TASKS AND MILESTONES

The successful implementation of the SCADA system will follow a structured timeline with well-
defined milestones. These milestones align with the project scope, deliverables, and sprint-based
development approach. The major technical tasks and estimated completion timelines are outlined
below:

11.1 Sprint-Based Development Approach

The project will be developed in three iterative sprints, ensuring continuous refinement and
evaluation at each stage:

11.1.1 Sprint 1 (February 7 – February 28):

Goals: Develop the design roadmap, complete SLDs, and establish a database framework.
Outcomes: Verified single-line diagrams, initial database structure.

Evaluation Criteria: Design roadmap approval, successful data collection from field devices.

11.1.2 Sprint 2 (February 28 – March 28):

Goals: Develop SCADA interface, implement communication protocols, and test alarm management.

Outcomes: Functional HMI, working communication framework.

Evaluation Criteria: User interface review, successful alarm triggers.

11.1.3 Sprint 3 (March 28 – April 11):

Goals: Conduct full system validation, performance testing, and final refinements.

Outcomes: Fully operational SCADA system ready for deployment.

Evaluation Criteria: Successful final demonstration, approval of final report.

This structured approach ensures that all critical technical tasks are addressed in a logical sequence,
supporting timely project completion and ensuring a reliable SCADA system for the
University of Calgary.

12 ROLES AND RESPONSIBILITIES

Sheheryar Ahmed (Lead)

• Accountable (A) for overall project execution, ensuring deliverables meet deadlines and
quality standards.
• Responsible (R) for team coordination, delegating tasks, and maintaining project
documentation.
• Consulted (C) for technical decision-making, particularly in SCADA architecture design and
integration.
• Informed (I) about all technical developments and system implementation progress.

Muhammad Saribuddin (Team Member)

• Responsible (R) for designing the system architecture, defining topology, and setting up the
database.
• Accountable (A) for ensuring data flows efficiently and securely across the SCADA system.
• Consulted (C) in decisions regarding communication protocols and system scalability.
• Informed (I) on HMI development and event recording integration.
Hamza Arshad (Team Member)

• Responsible (R) for designing and implementing the Human-Machine Interface (HMI) and
User Interface (UI).
• Accountable (A) for ensuring the interface is user-friendly and properly integrated with the
SCADA system.
• Consulted (C) for database integration and visualization best practices.
• Informed (I) on SCADA architecture and alarm management system requirements.

Mannan Rauf (Team Member)

• Responsible (R) for integrating power system data and ensuring accurate event tracking.
• Accountable (A) for aligning the SCADA system with power system standards and industrial
best practices.
• Consulted (C) for system architecture and event recording design.
• Informed (I) on HMI development and alarm management requirements.

Sameer Ahmed (Team Member)

• Responsible (R) for implementing the alarm management system and defining fault
detection parameters.
• Accountable (A) for ensuring real-time monitoring and response mechanisms are effective.
• Consulted (C) on SCADA system architecture and integration of alarms with HMI.
• Informed (I) about database structures and event recording functionalities.

Muhammad Waqas (Team Member)

• Responsible (R) for testing the SCADA system, troubleshooting, and validating system
performance.
• Accountable (A) for compiling testing results and contributing to final documentation.
• Consulted (C) on system architecture and HMI development for usability testing.
• Informed (I) on fault detection mechanisms and real-time system updates.

13 MEASURES OF SUCCESS AND VALIDATION TESTS

The success of the proposed SCADA system will be determined by its ability to meet the specified
deliverables, including HMI development, alarm management, event recording, user interface
creation, and SCADA architecture design. The following criteria and validation tests will be used to
evaluate project success.
13.1 Measures of Success

The project will be considered successful if it meets the following criteria:

Measure Description
HMI Development Customized and functional HMI created using the Ignition platform
for real-time network monitoring
Alarm Management System Robust alarm system with predefined thresholds and priority levels
for fault detection and resolution
Event Recording System Accurate event tracking with timestamps, categorization, and root
cause analysis tools
User Interface (UI) Responsive and user-friendly visualization dashboard displaying
real-time data and network schematics
SCADA Architecture Design Comprehensive system architecture with well-defined
communication topology and data flow diagrams
Scalability and Future Ability to expand the system for future upgrades and additional
Integration devices
Data Accuracy and Real-Time Data acquisition and visualization at ≤ 1-second intervals with high
Performance accuracy

13.2 Validation Tests

The following tests will ensure that each project deliverable meets its success criteria:

Test Category Test Description Validation Method

HMI Functionality Verify that the HMI correctly visualizes Simulate electrical network data
Test key electrical parameters (voltage, and confirm accurate real-time
current, frequency, power flow) visualization
Alarm Management Ensure that the alarm system triggers Simulate abnormal network
Test alerts at correct thresholds conditions and monitor alarm
behaviour
Event Recording Validate the recording of events with Create and track simulated events,
Test correct timestamps and categorization ensuring detailed root cause
analysis
UI Usability Test Assess the responsiveness and usability Conduct user feedback sessions
of the user interface and adjust based on
 recommendations
Communication Verify compatibility with Modbus, DNP3, Simulate device communication
Protocol Test and IEC 61850 protocols using these protocols
Scalability Test Test the system’s ability to handle Simulate 200 device connections
increased device connections and monitor performance
Data Accuracy and Ensure data acquisition is accurate and Simulate data flow and measure
Latency Test within the required time interval response time for updates

13.3 Addressing Potential Deviations

Although the project aims to meet all specifications, potential deviations may occur due to technical
limitations or unforeseen challenges. The following strategies will be implemented to manage
deviations:

• Data Latency or Performance Issues: Optimize communication protocols and database

queries to reduce response times.
• Scalability Limitations: Introduce load balancing and additional computing resources if
performance degrades with high device connections.
• Alarm Misconfigurations: Refine alarm thresholds and add validation rules to minimize false
positives.
• UI Design Adjustments: Gather continuous user feedback to improve the interface's usability
and functionality.

14 CONCLUSION
The outlined measures and validation tests will ensure that the SCADA system meets its functional
and performance requirements. Regular testing and monitoring during the project lifecycle will help
identify and address any deviations, ensuring a reliable and scalable solution for the University of
Calgary’s electrical network.
15 APPENDIX

None available at this time

16 REFERENCES

1. Arrillaga, J. (1983). High voltage direct current transmission. IEE Power Engineering Series. London.
2. Bendre, A., Divan, D., et al. (2004). Equipment failures caused by power quality disturbances.
Industry Applications Conference, 2004. 39th IAS Annual Meeting. Conference Record of the 2004
IEEE, 1.
3. Bruce Li, P.Eng. (2007, February). SCADA application in water and wastewater industry. Dec1n IWS.
4. Heydt, G. (1991). Electric power quality. Stars in a Circle Publications.
5. Hingorani, N. G., & Gyugyi, L. (2000). Understanding FACTS: Concepts and technology of flexible AC
transmission systems. IEEE Press.
6. Intranet-based SCADA (Supervisory Control and Data Acquisition system) for power system.
(2000). Power Engineering Society Winter Meeting, IEEE, 3, 1656–1661.
7. Kimbark, E. W. (1971). Direct current transmission. Wiley.
8. Kueck, J. D., Kirby, B. J., et al. (2004). Measurement practices for reliability and power quality. Oak
Ridge National Laboratory, Oak Ridge, Tennessee 37831-6285.
9. McClnahan, T. (2003). SCADA and IP: Is network convergence really here? Industry Applications
Magazine, IEEE, 9(2), 29–36.
10. McDonald, J. D. (1993, April 25–27). Developing and defining basic SCADA system concepts. Rural
Electric Power Conference, 37th Annual Conference, B3/1–B3/5.
11. McGranaghan, M., & Mueller, D. (1885). Effects of voltage sags in process industry applications.
IEEE/KTH Power Tech Conference, Stockholm, Sweden, 4–10.
12. Medida, S., Sreekumar, N., & Pasad, K. V. (1998, March 3–5). SCADA-EMS on the Internet. Energy
Management and Power Delivery, Proceedings of EMPD '98. 1998 International Conference on, 2,
656–660.
13. Miklovic, D. T. (1988, October). CIM—Overworked, overused, misunderstood. Automation and
Control—the Journal of the New Zealand Institute of Measurement and Control.
14. Miklovic, D. T. (1992). Real-time control networks for batch and process industries. Instrument
Society of America.
15. Network Planning Criteria—Power and Water Corporation. (2003). Power and Water
Corporation. Retrieved from
[http://www.powerwater.com.au/_data/assets/pdf_file/0009/3501/network_planning_criteria_030
4.pdf](http://www.powerwater.com.au/_data/assets/pdf_file/0009/3501/network_planning_criteria
_0304.pdf).
16. Rudervall, R., Charpentier, J., et al. (2000). High voltage direct current (HVDC) transmission
systems technology review paper. Energy Week 2000.
17. Rune, G. (n.d.). Sustainable virtual utilities based on Microgrids. School of Engineering, Blekinge
Institute of Technology Ronneby, SE-372 25, Sweden.
18. Song, Y. H., & Johns, A. T. (1999). Flexible AC transmission systems (FACTS). IEE Power Engineering
Series 30, London.
19. Uhlman, E. (1975). Power transmission by direct current. Springer.
20. Walski, T. M., et al. (2003, January). Advanced water distribution modeling and management.
Haestad Press.
21. Zecevic, G. (1998, August 18–21). Web-based interface to SCADA system. Power System
Technology, Proceedings. POWERCON '98. 1998 International Conference on, 2, 1218–1221.
22. Listen Think Solve RS Logix500. (2007, January). Getting results guide, publication LG 500-
GR002C-EN-P, 81–83.
23. Listen Think Solve. (2007, August). Product profile RSView32, publication VW32-PP002B-EN-P.