—

F U NC T I O NA L D E S CR I P T I ON

ABB AbilityTM Operations

Management System
Functional Description
9AKK107680A1627
 F U NCT IO NA L D ESCR IPT IO N

TRADEMARKS
Ability, Advant, AdvaBuild, AdvaCommand, AdvaInform, IndustrialIT, 800xA are registered trademarks of ABB Asea Brown
Boveri Ltd.
Chrome is a trademark of Google Inc.
Digital, DEC, VAX, VMS and all Digital-products mentioned in this publication are registered trademarks of Digital Equip-
ment Corporation.
Firefox and Mozilla are trademarks of the Mozilla Foundation.
HP and all HP products mentioned in this publication are registered trademarks of Hewlett-Packard Company.
IBM and all IBM products mentioned in this publication are registered trademarks of International Business Machines Corpo-
ration.
Microsoft, MS, MS-DOS, Microsoft Office, Microsoft Access, Microsoft Excel, Microsoft Word, Microsoft Internet Explorer,
Microsoft Edge are registered trademarks, and ODBC, Windows, Windows NT, Windows 2000, Windows 2003, Windows
2008, Windows 2012, Windows 2016, Windows 7, Windows 8, Windows 10, Windows Vista are trademarks of Microsoft Cor-
poration.
OPC is a registered trademark of the OPC Foundation.
Oracle, SQL*Net, SQL*Plus and SQL*Connect are trademarks of Oracle Corporation.
SAP, NetWeaver, SAP Web Application Server, SAP business Connector, SAP-XI are registered trademarks of SAP AG in Ger-
many.
InfoPlus21 is a trademark and brand of Aspen Technology, Inc.
PI System is a registered trademark of OSIsoft, Inc.
All other copyrights, trademarks or trade names used herein are the property of their respective owners.

Use of DANGER, WARNING, CAUTION and NOTE

This publication includes DANGER, WARNING, CAUTION and NOTE information where appropriate to point out safety related
or other important information.
DANGER Hazards which could result in severe personal injury or death.
WARNING Hazards which could result in personal injury.
CAUTION Hazards which could result in equipment or property damage.
NOTE Alert users to pertinent facts and conditions.
Although DANGER and WARNING hazards are related to personal injury, and CAUTION hazards are associated with equip-
ment or property damage, it should be understood that operation of damaged equipment could, under certain operational
conditions, result in degraded process performance leading to personal injury or death. Therefore, comply fully with all
DANGER, WARNING and CAUTION notices.

NOTICES AND DISCLAIMERS

ABB may have one or more patents or pending patent applications protecting the intellectual property in the ABB products
described in this document.
The information in this document is subject to change without notice and should not be construed as a commitment by
ABB. ABB assumes no responsibility for any errors that may appear in this document. In no event shall ABB be liable for di-
rect, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document nor
shall ABB be liable for incidental or consequential damages arising from the use of any software or hardware described in
this document.
This document and parts thereof must not be reproduced or copied without written permission from ABB, and the contents
thereof must not be imparted to a third party nor used for any unauthorized purpose.
The software described in this document is furnished under a license and may be used, copied, or disclosed only in accord-
ance with the terms of such license.
The products described or referenced in this document are designed to be connected and to communicate information and
data via network interfaces, which should be connected to a secure net-work. It is your sole responsibility to provide and
continuously ensure a secure connection between the products and your network or any other networks that may be con-
nected.
You must establish and maintain appropriate measures (including, but not limited to: the installation of firewalls, applica-
tion of authentication measures, encryption of data, and installation of antivirus programs) to protect these products, the
network, its system, and interfaces against security breaches, unauthorized access, interference, intrusion, leakage, and
theft of data or information.
ABB performs functionality testing on the products and updates that we release. However, you are ultimately responsible for
ensuring that any product updates or other major system updates (including, but not limited to: code changes, configura-
tion file changes, third-party software updates or patches, and hardware change out) are compatible with the security
measures implemented. You must verify that the system and associated products function as expected in the environment
in which they are deployed.
ABB and its affiliates are not liable for damages and/or losses related to such security breaches, any unauthorized access,
interference, intrusion, leakage and/or theft of data or information.

Copyright © 2018 ABB. All rights reserved.

9AKK107680A1627 2/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Contents
Introduction.........................................................................................................................................................6
Audience ........................................................................................................................................................................ 6
Related Documentation ............................................................................................................................................. 6

Operations Management systems ....................................................................................................................6

Introduction .................................................................................................................................................................. 6
Solution ......................................................................................................................................................................... 8
The Product .................................................................................................................................................................. 8
Technical Summary ..................................................................................................................................................... 9
Components and architecture ................................................................................................................................10
ISA 95 Store ................................................................................................................................................................. 11
Concepts of ISA 95 used in OMS ....................................................................................................................... 11
Configuration of ISA 95 Models in OMS .......................................................................................................... 12
Use of ISA 95 Store ............................................................................................................................................... 13
Interaction with ISA 95 via Web Client .............................................................................................................14
Dispatcher (main control room) screen ................................................................................................................14
Remote clients HMI .................................................................................................................................................... 16
Mobile equipment with no reliable connection to ISA 95 Store ................................................................18
Auto-Scheduling engine............................................................................................................................................18
Connectivity to real time data .................................................................................................................................18
Connectivity to ERP systems ...................................................................................................................................18

Functions available to dispatchers ................................................................................................................ 20

Scheduling views ....................................................................................................................................................... 20
Visualizing status of tasks ................................................................................................................................. 21
Interacting with the current schedule .............................................................................................................23
Identifying violation of usage constraint ...................................................................................................... 24
Web Views ................................................................................................................................................................... 25
Rescheduling example.............................................................................................................................................. 28
Configuration Capabilities ...................................................................................................................................... 30
Location editor..................................................................................................................................................... 30
Equipment.............................................................................................................................................................. 31
Recipe ...................................................................................................................................................................... 31
Order execution sequence..................................................................................................................................32
Capability rules editor ...............................................................................................................................................33
Handling process responses .................................................................................................................................. 34
Handling of segment failure ............................................................................................................................. 34
Flexible recipe assignment...................................................................................................................................... 35
Adhoc recipe ......................................................................................................................................................... 36
KPI Displays .................................................................................................................................................................37

Summary ............................................................................................................................................................38

REVISION HISTORY ............................................................................................................................................39

9AKK107680A1627 3/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Figures
Figure 1: System overview – Scheduling, Dispatching and execution ................................................................... 8
Figure 2: System Hierarchy Overview ........................................................................................................................... 9
Figure 3: OMS system architecture .............................................................................................................................. 11
Figure 4: High level view of ISA-95 ............................................................................................................................... 11
Figure 5: Objects in ISA-95 ............................................................................................................................................. 12
Figure 6: ISA95 Store showing example of equipment class configuration ....................................................... 13
Figure 7: ISA95 Store Web client showing example of operations schedule ......................................................14
Figure 8: ISA95 Store Web Client showing example of production rule details.................................................14
Figure 9: Dispatcher screen showing activities example by location and electricity usage summary ........ 15
Figure 10: Remote client with example of a task list................................................................................................ 16
Figure 11: Remote client with example of a task’s details ...................................................................................... 17
Figure 12: Remote client with example to report an interruption ......................................................................... 17
Figure 13: Auto Update Modes ......................................................................................................................................18
Figure 14: Dispatcher screen showing Equipment view.......................................................................................... 21
Figure 15: Dispatcher screen showing Locations view ............................................................................................ 21
Figure 16: Dispatcher screen showing Personnel view ............................................................................................ 21
Figure 17: Dispatcher screen showing example of section with electricity usage ............................................ 21
Figure 17: Recognizing tasks’ status ............................................................................................................................22
Figure 18: Dispatcher screen showing activity icons ...............................................................................................23
Figure 19: Dispatcher screen showing relationships between tasks ...................................................................23
Figure 20: Recognizing violation of a constraint in resource usage .................................................................... 24
Figure 21: Scheduler Web Views in ISA95 web client ............................................................................................... 25
Figure 22: Task details tooltip ...................................................................................................................................... 25
Figure 23: 24 hours timeline.......................................................................................................................................... 26
Figure 24: 7 days timeline .............................................................................................................................................. 26
Figure 25: Date-time picker for web views ................................................................................................................ 26
Figure 26: Equipment view ............................................................................................................................................. 27
Figure 27: Equipment by Location view ...................................................................................................................... 27
Figure 28: Locations view .............................................................................................................................................. 28
Figure 29: Orders view ................................................................................................................................................... 28
Figure 30: Planned activities before applying energy constraints ...................................................................... 28
Figure 31: Planned activities after applying energy constraints .......................................................................... 29
Figure 32: Planned orders before rescheduling ........................................................................................................ 29
Figure 33: Planned orders after rescheduling ........................................................................................................... 30
Figure 34: Locations editor showing an item selected for editing ...................................................................... 30
Figure 35: Equipment editor showing an item selected for editing ..................................................................... 31
Figure 36: List of recipes available ............................................................................................................................... 31
Figure 37: Example creating a recipe based on an existing one ............................................................................32
Figure 38 Orders initially in backlog. No sequence enforced. ................................................................................32
Figure 39: Scheduler enforces the defined sequence ..............................................................................................33
Figure 40: Locations view showing a drift unavailable for a period.....................................................................33
Figure 41: Capability editor showing the rule keeping the Drift20 unavailable for an inspection ............... 34
Figure 42: Order’s view showing how to insert an additional step after an aborted activity. ...................... 34
Figure 43: Order’s view showing how to create an unavailability rule for a broken equipment. .................. 35
Figure 44: Order’s view showing how to reassign a recipe to a request............................................................ 35
Figure 45: Order’s view showing how to reassign an ad-hoc recipe to a request............................................ 36
Figure 46: Ad-hoc recipe dialogue............................................................................................................................... 36
Figure 47: Example of KPI display .................................................................................................................................37

9AKK107680A1627 4/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

List of Tables
Table 1: OMS Technical Summary .................................................................................................................................10

9AKK107680A1627 5/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Introduction
This document presents the Functional Description for the following systems:
• ABB AbilityTM Operations Management System (OMS) for Mining version 1.0

To offer the latest technology, ABB Switzerland Ltd reserves the right to substitute alternative
hardware of equal or better performance.

Audience
This document is intended for mine operators that need to receive their tasks electronically and update
the mine operation center about task execution during the shift.

Related Documentation

Document ID Description

Document [1] describes the Operations Management

System (OMS) system and gives an overview of the
various components as well as of the main
functionalities.
Document [2] describes the B2MML V5 (Business to
Manufacturing Language), which is an XML based
message exchange format for ISA-95.

Document [3] describes the interface between OMS

and the scheduling part. The scheduler requires the
ISA-95 model to follow certain model conventions to
be able to do scheduling.

Document [4] describes installation of OMS, but also

contains information on how to configure DCOM for
Model Configurator.

Document [5] describes how to extend OMS

functionality by adding custom scripts.

Operations Management systems

Introduction
Mine operations start with careful (medium to long term) planning, that uses information about the ore
body, the market economics and the available physical and human resources to produce a production
plant that maximizes stakeholder value.

Once this optimal plan stands, production scheduling in real time is the most important activities in the
mine managers. The manager must deliver adherence to this plan, while maximizing operational effi-
ciency and keeping the costs at their minimum. This task requires evaluating a complex set of opera-
tional constraints, while adjusting to ever changing day to day, hour to hour situations.

Among many others, the production management team must constantly consider variables such as

– Current ore body properties

9AKK107680A1627 6/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

– Restrictions in equipment availability

– Material transport systems

– Storage levels

– Planned maintenance activities

Operations Management Systems (OMS) can be applied to processes that can be modelled using the ISA
95 standard. This means that one can sensibly define the following elements:

– Production orders

– Production recipes structured in production segments

– Production segments defined by

• location requirements
• equipment requirements
• personnel requirements
• material requirements (consumed, consumable and produced)

Availablity of resources given by the so-called capability models

Many logistic processes that are relevant in mining can be represented with these elements, for example

– Underground mine operations

– Open pit mine haulage with trucks and conveyors

– Transport and logistic operations related to port and other deliveries to customers.

9AKK107680A1627 7/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Solution

OMS is a real time scheduling, dispatch and track software application suitable for short interval control
of mine operations. The scheduling & production execution modules can import the production plans
from the mine production planning system. The Scheduler tool enables efficient creation of single tasks
or from standard operation cycles. Scheduler supports real-time update of progress and tools for re-
planning of machines and equipment depending on the actual situation in the mine.

Figure 1: System overview – Scheduling, Dispatching and execution

Scheduled tasks automatically get synchronized with dispatch & work management and distributed to
the on-board interface at each machine or operator. Operators manage their tasks, report progress and
required production data from the on-board Vehicle client.

Disturbances, like machine failure or other disturbances can be reported directly on-board the mobile
machine. Both mine operator and the shift manager have updated information about the progress and
disturbances, which enables them to take necessary actions to make the production run smoothly.

The remote monitoring module collects data on-board the mobile machines with the Vehicle on-board
data logger. Data is stored onboard and forwarded to the Remote Monitoring History server. Remote
monitoring data from the vehicles are visualized in System 800xA. 3 rd party remote monitoring systems
can also be integrated and visualized in System 800xA.

Shift Manager Clients and Vehicle Clients have the possibility to act as data carrier for other clients
which enables data from one client to be transferred to second client. When the second client interfaces
with the network, data is synchronized with the server.

* ABB Ability System 800xA not included.

* ABB Ability OMS Fleet Manager not included.

The Product
OMS is a software package, where mine operator’s schedule, dispatch and track operations in real time,
increasing operational transparency and enabling decisions for best operations in real time.

OMS offers the following functionality:

– Real time visibility of resources across the mine operations,

– Schedule continuously updated, based on truly existent resources.

9AKK107680A1627 8/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

– Optimal response to disturbances in real time

– Scheduling engine, supporting optimal decision-making including constraint checking mechanisms

to enforce resource availability (for example: energy, water and equipment availability)

– ISA 95 based data store that holds mine’s past present and planned activities

OMS also supports collecting, organizing and distributing production and quality information through-
out a mine. The system manages data collected from your process via different sources and provides
focused information presentation through functions and components needed for mining specific activi-
ties.

Figure 2: System Hierarchy Overview

OMS enable the ability to operate in closed loop, delivering true integration of the OT and IT levels. The
details of the Operations Management Systems package are described in the next sections.

Technical Summary
Item Specification
Server Functions for
– data retrieval
– optimization model
– data presentation

Thin Web Functions for

Based Client
– defining requests
– display and update of selected ISA 95 model aspects

Dispatcher Functions for:

Application – Visualization of Production plan data
– Visualization of detailed schedule
– Visualization of process responses
–
– Manual trigger of scheduling engine
– Handling of equipment failures

9AKK107680A1627 9/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

– Export of schedule to ISA 95 store

– Forecasting inventories consumed and produced
– Forecasting energy consumption
– Forecasting water consumption
– Forecasting production

Configuration of:
– locations
– equipment capability
– recipes
– order execution sequences
– inventory limits

ISA 95 Store Functions for:

Configuratio
n Tool – ISA95 model configuration

Table 1: OMS Technical Summary

Components and architecture

The OMS system has the following components:

– ISA95 Store

• Configuration of ISA-95 model

• Connectivity to real time data
• Connectivity to ERP systems

– Dispatcher (main control room) HMI

– Remote clients HMI:

• Fixed stations
• Mobile equipment

– Scheduling engine

The OMS architecture is shown in the figure below.

9AKK107680A1627 10/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Figure 3: OMS system architecture

ISA 95 Store

Concepts of ISA 95 used in OMS

ISA-95 covers a set of specifications (or models) and terminology that capture the manufacturing pro-
cess and provide a standardized message exchange format specification. The message format is based
on XML and is referred to as B2MML (Business to Manufacturing Markup Language)

The next image shows a high-level view of ISA-95 (gray areas) and the typical context where it is used:

Figure 4: High level view of ISA-95

9AKK107680A1627 11/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

The production capability model describes what is available in terms of resources like equipment, mate-
rial, personnel and production areas. It also describes when resources are available and when not.

The product definition information model describes the production workflows, i.e. the recipes based on
the production capability model.

Finally, the product information model describes what to produce and when. The main part of this
model is the schedule and a set of orders that will be later dispatched. Part of this model is also the re-
sponse model, which captures the production feedback.

Configuration of ISA 95 Models in OMS

Users can configure the ISA-95 classes and define instances for:

– Process segments

• loading, drilling
• blasting, bolting

– Equipment classes

• trucks, loaders
• drilling machine

– Materials (consumables, consumed and produced)

• electricity, water
• ore, waste

Figure 5: Objects in ISA-95

9AKK107680A1627 12/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Use of ISA 95 Store

The ISA95 Store provides the users with the means to persist the configuration and run-time compo-
nents of the ISA-95 model for their processes.

The Server part also takes care of providing the necessary information to other components of the OMS
system like, for example, the main dispatcher screen or the scheduler.

Figure 6: ISA95 Store showing example of equipment class configuration

The ISA95 server component takes care of storing the configuration and real time data for the ISA95
model, as well as other connectivity functions:

– ISA 95 model

• Configuration, storage and archiving of components of the ISA 95 model

– Connectivity towards

• DCS, with seamless integration for ABB’s 800xA system

• Mobile equipment
• ERP systems (collecting orders and sending production results)
• Maintenance system (collecting equipment availability and sending maintenance request)

– Interface to the schedule engine

• Generates ISA-95 information, including operations response

• Receives schedule

– Dispatches approved schedule to stakeholders, acting as a data server for

• The Operator HMI client

• The Mobile equipment HMI

9AKK107680A1627 13/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Interaction with ISA 95 via Web Client

The user can also interact with the ISA 95 store using a Web Client.

For instance, it is possible to:

Place operations requests in ISA 95:

Figure 7: ISA95 Store Web client showing example of operations schedule

Analyze existent recipes or production rules:

Figure 8: ISA95 Store Web Client showing example of production rule details

The Web client functionality can be extended with project specific items to cover functionality such as
entering maintenance schedules, ore quality information, etc.

Dispatcher (main control room) screen

The Timeline view is the main system interface towards the mine dispatcher operators in the control
room.

– Users can visualize the mining activities and monitor their progress in progress bars. The following
views are available to group activities:

• Equipment
• Location
• Personnel

– At the bottom of the screen the user can show the usage of a selected resource, where constraint vi-
olations are displayed.

9AKK107680A1627 14/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

– In the current version the operator must initiate the optimization command in the desktop applica-
tion.

Figure 9: Dispatcher screen showing activities example by location and electricity usage summary

Web services are used to obtain the main information for this screen from the ISA95 Store. It also ex-
changes data with the scheduling engine receiving results from the algorithms.

The information is then presented to the users in an interactive timeline view, where the operators can
perform manual changes, like moving a task from one location to another.

The system takes care of updating the timeline view using the input from mobile operation stations, up-
dating the usage of resources and checking for constraint violations, like a due date reached or too
much electricity consumed.

9AKK107680A1627 15/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Remote clients HMI

Special web-based screens have been designed for collecting information from operators working at re-
mote stations, either fixed or mobile.

These screens present the current plan and current task status (using the information from the ISA95
Store) and the operators can report at any time the estimated completion time for a selected task. Oper-
ators can also report interruptions of a task indicating a reason, duration and other message.

Figure 10: Remote client with example of a task list

9AKK107680A1627 16/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Figure 11: Remote client with example of a task’s details

Figure 1: Remote client with example to report an interruption

9AKK107680A1627 17/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Mobile equipment with no reliable connection to ISA 95 Store

Mobile stations might not have a constant reliable connection to the ISA95 server due to unavailability of
the data network. For these cases it is required to use special off-line units that act as a data collector
node, keeping in local storage any updated transactions until a reconnection takes place. Only then the
data can be sent to the main OMS system, synchronized with other transactions and the Dispatcher
main screen can be updated accordingly. The operator would use these mobile clients to see the current
plan and update the status of tasks, even when the main system is not reachable on-line.

Contact ABB for information on handling these cases with ABB’s Fleet Manager.

Auto-Scheduling engine
Backbone of OMS system is scheduling engine used to optimize production schedule based on current
requests, resource availability and responses from the field. Its operation can be broken down into three
crucial steps:

– Import model (requests, resources, etc.) and feedback (responses) from OMS data store

– Perform optimization

– Export optimized data back to OMS data store

The Mine Planer can choose to perform tasks either through the Auto-Scheduler or manually through the
Gannt Application. Manually invoking steps in optimization process refers to operator overseeing initiat-
ing each action by using Gantt application. However, Auto-Scheduling will be used in most cases and it
ensures that no human intervention is required to run the import, optimize, and export cycle. In addition
to this, automatic mode can be:

– Automatic via dedicated service

Figure 23: Auto Update Modes

Connectivity to real time data

The following systems should be interfaced to get real time data relevant for scheduling the activities:

– MIne real time data

– Storage levels

– Equipment status

Connectivity to ERP systems

– The following systems should be interfaced to get business level data relevant for scheduling the ac-
tivities:

– ERP and/or Mine Planning System

• Generates production plan

• Receives plant status

9AKK107680A1627 18/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

– Receives production results

• Maintenance system
• Generates maintenance plan
• Receives equipment status

9AKK107680A1627 19/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Functions available to dispatchers

The OMS system calculates the optimal schedule considering the ISA95 model, the real time data and
any defined constraints. The desktop application screen shows the current schedule displayed in a Gantt
chart with the following information sections:

– Scheduling views per:

• Equipment
• Locations
• Personnel
• Materials (resources usage)

– Configuration of:

• Locations
• Equipment
• Personnel
• Recipe/Cycle

– Capability rules editor

– Closed loops between plan and execution

• Screen auto update

• Handling of segment failures

– Recipe Handling

• Request recipe change

• Adhoc recipe

– Displays Customization

Scheduling views

Users can choose how they want to visualize the current Schedule by:

– Equipment

– Locations

– Orders

– Materials (resources usage)

Each of these screens allows visualizing what has been planned against what has been done.

9AKK107680A1627 20/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Figure 34: Dispatcher screen showing Equipment view

Figure 45: Dispatcher screen showing Locations view

Figure 56: Dispatcher screen showing Personnel view

Figure 67: Dispatcher screen showing example of section with electricity usage

In all these views, multiple settings can be customized, for example: status colors, providing visual focus
on the plan or on the response.

Visualizing status of tasks

The operators can easily identify the current tasks’ status in the main screen:

– A hair line with the current time (Now) is clearly shown

– A narrow box on top of each task indicates how it was planned

9AKK107680A1627 21/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

– The reported progress of each task is indicated in two dimensions:

• the progress is indicated by filling the task box in color up to the current time, while aborted tasks
will show filling only until when they were placed on hold
• the color of the box indicates the status of the task: running (blue), holding (yellow), finished
(green) and aborted (red)

– A grey shaded box indicates periods of unknown status: tasks might or might not have been com-
pleted during that time

– The last time when an update was received is then easily recognized by the division between the col-
ored and the greyed sections of the task box

Every time the operators report the progress of tasks from their remote stations the Dispatcher screen
updates the view accordingly.

Figure 17: Recognizing tasks’ status

9AKK107680A1627 22/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Interacting with the current schedule

Users can use drag and drop operations to:

– Fix tasks in time

– Reassign orders to different equipment

– Edit the capability of the different resources

Furthermore, the system provides a large set of options allowing the users to customize their user expe-
rience and the scheduling algorithms to be deployed.

Figure 18: Dispatcher screen showing activity icons

Figure 19: Dispatcher screen showing relationships between tasks

9AKK107680A1627 23/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Identifying violation of usage constraint

When material constraint violations are identified and the operators are not satisfied with the current
schedule, they can initiate an optimization task and the system will evaluate the situation and propose a
better plan.

Figure 7: Recognizing violation of a constraint in resource usage

9AKK107680A1627 24/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Web Views
OMS system provides a way for the operator to have insight on current scheduling status. This is
achieved by having web based representation of before mentioned scheduler views from Gantt applica-
tion.

– Equipment (Equipment view in Gantt app.)

– Equipment by Location (Equipment Locator view in Gantt app.)

– Locations (Locations view in Gantt app.)

– Orders (Orders view in Gantt app.)

All of these are accessible via ISA95 web client application and are located in “Reports” section under
“Scheduler” subfolder.

Figure 81: Scheduler Web Views in ISA95 web client

Task details are shown in a form of a tooltip shown when hovering a mouse over the particular section.

Figure 22: Task details tooltip

Each of the views have couple of time scales to chose from:

– Timeline 24hours

– Timeline Week

Week and a Month timelines are simply showing a week or month of a schedule. Work Week view is
similar to a regular Week view but with only the work hours shown (eg. 09:00 to 17:00). This feature can
be configured to support different work hours.

9AKK107680A1627 25/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Figure 23: 24 hours timeline

Figure 24: 7 days timeline

Vertical blue line is the “now” line and represents present moment on a chart.

If operator wants to see particular date, he can choose the specific one from date-time picker to the
right

Figure 25: Date-time picker for web views

9AKK107680A1627 26/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Equipment Web View

Equipment view is web-based representation of Gantt applications Equipment view. Color scheme is
made the same between the versions meaning task from is of the same color in Gantt client and ISA95
web client. This stands for the rest of the web schedule views as well.

In Equipment view we have list of equipment on the left and tasks spread across the time line.

Figure 26: Equipment view

Equipment by Location Web View

Like “Equipment Locator” in Gantt application, this way of looking at a schedule indicates current loca-
tion of an equipment. Like the Equipment view, on the left we have all the equipment listed vertically. On
the chart itself each “box” represents a location that equipment is in at the given moment in time.

Figure 27: Equipment by Location view

Locations Web View

This view is the same as the one in Gantt application and is somewhat reversed Equipment view. Loca-
tions are listed on the left vertically and time chart has equipment that occupies location for certain
amount of time.

9AKK107680A1627 27/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Figure 28: Locations view

Orders Web View

Orders view is the one showing the schedule from the production order perspective. Orders are listed on
the left and can be expanded or collapsed so that individual steps within a production process are
shown or hidden. Chart shows the time span that is required for order to be executed. If expanded, each
of the steps is also shown right beneath the production order block.

Figure 29: Orders view

Rescheduling example
In the example form Figure 7 above there are some violations on the usage of energy. The operator can
check the different views and initiate a rescheduling form the Dispatcher screen.

The figures below show the plan for the activities before and after the system performs the reschedul-
ing optimizing the plan to satisfy the constraints of energy consumption.

Figure 30: Planned activities before applying energy constraints

9AKK107680A1627 28/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Figure 31: Planned activities after applying energy constraints

While in the Equipment view above it might not be so clear to some users the overall effect of the new
plan, in the Orders view it can be quickly identified that certain orders are now postponed to a later pe-
riod.

Figure 32: Planned orders before rescheduling

9AKK107680A1627 29/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Figure 33: Planned orders after rescheduling

Configuration Capabilities
Additionally to the operational activities, the Dispatcher application also allows to complete some con-
figuration tasks:

– Locations

– Equipment instance

– Recipes

– Order execution sequence

Location editor
In this view the user can update the mine locations by adding, deleting or editing items and their details.

Figure 34: Locations editor showing an item selected for editing

9AKK107680A1627 30/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Equipment
In this view the user can update the mine equipment by adding, deleting or editing items and their de-
tails.

Figure 35: Equipment editor showing an item selected for editing

Recipe
In this view the user can update the recipes by adding and deleting items and their details.

Figure 36: List of recipes available

9AKK107680A1627 31/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Figure 37: Example creating a recipe based on an existing one

Order execution sequence

In this screen the user can view and update the order in which the production requests will be scheduled
(execution sequence).

Figure 38 Orders initially in backlog. No sequence enforced.

9AKK107680A1627 32/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Figure 39: Scheduler enforces the defined sequence

Capability rules editor

The capability rules editor allows the user to update the availability or unavailability (capacity) on equip-
ment and locations, by adding, editing and deleting availability intervals.

Figure 40: Locations view showing a drift unavailable for a period

9AKK107680A1627 33/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Figure 41: Capability editor showing the rule keeping the Drift20 unavailable for an inspection

Handling process responses

The Dispatcher can decide whether process reponses are to be updated automatically or manually. This
is done with a simple checkbox from the main Dispatcher screen.

Handling of segment failure

When an activity in a sequence fails the Dispatcher provides some ways to deal with the situation.

For example, an additional step might be introduced to overcome an aborted task:

Figure 42: Order’s view showing how to insert an additional step after an aborted activity.

Another example, if an equipment has a problem the user can create a rule to indicate that an equipment
will not be available for some time:

9AKK107680A1627 34/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Figure 43: Order’s view showing how to create an unavailability rule for a broken equipment.

Flexible recipe assignment

The dispatcher can modify the production cycle (recipe) attached to a request

Request recipe change

The dispatcher can select a planned request and reassign its recipe, when the request is not in execution
yet.

Figure 44: Order’s view showing how to reassign a recipe to a request.

The new recipe is applied to the request, and the schedule is adapted and considers the new sequence
of activities.

9AKK107680A1627 35/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Adhoc recipe
For a request already in execution, the dispatcher is still allowed to modify the recipe, except for the
steps which are or have been in execution.

Figure 45: Order’s view showing how to reassign an ad-hoc recipe to a request.

Here for example the first step cannot be modified or removed, given that it is already in execution. The
subsequent activities can be freely modified or expanded.

Figure 46: Ad-hoc recipe dialogue

9AKK107680A1627 36/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

KPI Displays
Dispatchers can see the status of the system in a radar diagram that displays multiple KPIs for equip-
ment and locations.

The user can choose what to visualize in the radar diagrams:

– by row: which equipment or location

– or by column: which KPI

Figure 47: Example of KPI display

9AKK107680A1627 37/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

Summary
Operations Management System (OMS) is the ultimate decision support tool for the scheduling task. It
provides:

• Real time visibility on the plan,

• Shows the extent to which this plan is being fulfilled

– Status of the resources available to get there.

Moreover, OMS show not just the past and the present situation, but also the future of these operations
and how different corrective actions will influence the outcomes. OMS enables miners to increase their
operational agility, yield and equipment utilization, generating inmense value. Several processes relevant
in mining can profit from using OMS as operational platform, for example:

• Underground mine operations

• Open pit mine auxiliary equipment, drill rig, shovels, conveyors and crushers

– Transport and logistic operations related to port and other deliveries to customers

9AKK107680A1627 38/39
7 January 2020
 F U NCT IO NA L D ESCR IPT IO N

REVISION HISTORY
Item Description File Names

9AKK107680A1627 39/39
7 January 2020