Professional Documents
Culture Documents
DOC01067198-En-B VelocityEHS - Manual For General Users
DOC01067198-En-B VelocityEHS - Manual For General Users
Owner
Daniela Angioletti
Department
Corporate HSE
Date
07-2023
Document state
Released
Version
B
REVISIONS
1. TABLE OF CONTENTS
2. INTRODUCTION .......................................................................................................... 6
2. INTRODUCTION
- General users
- Auditor coordinator (for persons that hold this role in VelocityEHS)
- Risk coordinator (for persons that hold this role in VelocityEHS)
- Incident Investigation member (for persons who have been nominated to perform an incident investigation)
- Action owner (for persons who have been nominated as responsible for an action)
-
Note: for system administrators, please refer to ‘How to operate VelocityEHS tooling - Manual for System administrators’ –
DOC01067197 (LINK HERE).
The scope covered by VelocityEHS global tooling refers to the modules included in the formal contract
Vanderlande Industries holds with VelocityEHS. These modules are:
Incident Management Module
Audit & Inspection Module
Risk Assessment Module
Compliance Module
Sustainability Module (to be included in this manual later)
Training Module (to be included in this manual later depends on final decision)
All modules are available through web version application and most of them also available through mobile
version application.
Note: VelocityEHS app is offered through the Apple and Google Play stores. However, currently, Google Play store is not
allowed in China and, therefore, Android users in China are not able to download the app and must use only the web version
application.
The table below provides with an overview of the current accessibility via the app version application.
App version
Incident Available for the registering an incident, near miss or
Management hazard report. Investigation should be done via web
Module version application.
Audit & Inspection Inspection, Observation and Safety Walk can be done
Module via app version application. Audit is only possible via
web version application.
Risk Assessment Not available for the app version application.
Module
Compliance Module Not available for the app version application.
VelocityEHS global tooling is applicable to all Vanderlande Industries sites, such as:
Project Site
Service Site
Manufacturing Site
Office Site
Distribution Centre Site
Test Centre Site
The VelocityEHS global tooling is the one way of working within Vanderlande Industries with regards to managing
HSE processes shown on Chapter 3 (Scope).
The table below shows the main responsibility for general users.
Incident Module: report any incident, near miss and/or hazard you identify within all Vanderlande sites;
review, approve, investigate incidents if nominated as responsible for it.
Audit & Inspection Module: register any HSE inspection, safety walk and/or observation; run HSE audits
if nominated as Auditor Coordinator or member of the audit team.
Risk Assessment Module: perform risk assessments and environmental aspects and impacts if
nominated as Risk Coordinator or member to perfom the risk assessment.
Compliance Module: register external regulation, internal policy and/or permit and related actions to
ensure compliance if nominated as Compliance Manager.
Sustainability Module: (will be added when this module is implemented)
Training Module: (will be added if this module is decided to be implemented)
VelocityEHS global tooling is interfaced with Vanderlande’s HR system (Workday) and uses Single Sign On (SSO),
therefore just by clicking on the VelocityEHS app, general users can access VelocityEHS withou the need to add
username and password.
VelocityEHS is listed on ‘All apps’ list. To access VelocityEHS through ‘All apps’list follow the steps below:
The VelocityEHS Vikipedia page (LINK HERE) contains all the information needed to support general users on how
to proper use this global tooling.
→ Click on the picture (as shown below) and you will be taken to VelocityEHS
General users will be trained on VelocityEHS global tooling according to their roles in system. Most of
Vanderlande employees will be granted as ‘general user’ access only. However there are additional roles that will
be granted depends on person’s responsibilities in the system.
Training package addressed to general users consists in short videos which explains how to use the VelocityEHS
global tooling and/or how to perform additional roles depends on person’s responsibilities. Most of these short
videos are available in multiple languages, however they were prepared based in British-English language,
therefore videos in other languages than English can have differences on its synchronization.
Current available languages are:
English
Dutch
German
French
Italian
Spanish
Portuguese
Polish
Turkish
Chinese
Japanese
Additionally to the short videos, guidance (as PDF format) are also made available as part of the training material
for General Users.
These short videos can be accessed in three main ways:
1. VelocityEHS – through ‘Monitor’ / ‘Documents & Links’
2. Vanderlande Stream – through the channel ‘VelocityEHS’ (LINK HERE)
3. Vikipedia – through the VelocityEHS Vikipedia page (LINK HERE)
To access training material on how to use VelocityEHS through VelocityEHS tooling, follow the steps below:
→ Once on VelocityEHS – Vikipedia page, select ‘Academy training’ and check the training material
applicable to your need.
All short videos prepared as part of training material on how to use VelocityEHS global tooling are stored on
Stream and are accessible to all Vanderlande employees.
Note: some videos are addressed to super users only and, therefore require access to be granted.
The preferable option to access the short videos is through the VelocityEHS Vikipedia page since this is the
official page to provide content for General Users.
Short videos (and additional guidance) are organized per topic. Below the overview of what is current available
per main topic.
6.3.1. General
No short videos will be organize for the Compliance Module. Please refer to this manual to know how to use this
module.
7. INCIDENT MODULE
The information below will guide you on how to use each one of the topics available on the Incident Module of
VelocityEHS.
7.1. Incident
It is important to know how the incident workflow looks like because these are the steps in which an incident
reported in VelocityEHS will follow.
Note: For the ‘What’ field, multiple selection is possible, for instance, if you want to report an incident which involves an
injury person and an environmental release, you can select these two options.
→ Select the ‘Location’ of the incident by scrolling the Vanderlande location tree.
→ Start by selecting the continent, country, site and finally the project site, service site or Vanderlande
site.
Note: If you are not sure which project site, service site or Vanderlande site to select, you may select the level above (site
name) and the person responsible for ‘Review and Approval’ can add the missing level.
Note: VelocityEHS will keep the last location you have selected when you report next time on the Incident Module. Therefore, if
you are reporting for the same location, you don’t need to select it again. However, if you are reporting for a different
location, you must select it by scrolling the Vanderlande location tree again.
Note: The current version of VelocityEHS global tooling does not have the search functionality for the location tree. This
feature will be provided in the upcoming new release of the tooling.
→ Complete the ‘Where’ part by selecting the proper ‘Business Unity’, by iindicating whether the incident
has occurred on Vanderlande premises, by selecting the Customer Center’ and the ‘Type of Site’.
→ Complete the ‘When’ part by adding the date of occurrence and approximate time of occurrence.
→ For the ‘Who’ part (applicable when there is an injured person), add the information for the applicable
fields.
→ Add a ‘Witness’ name (if applicable).
Note: Depends on your selection of ‘Relationship’, additional fields will pop up. For instance, if ‘Contractor’ is selected,
information about ‘Contact’ and ‘Contracting Company’ will be required.
→ Inform whether any immediate action has been taken (if applicable) on the ‘Event Details’ part.
→ The ‘Internal Reporting’ part is prepopulated with your name (as reported by) and the date you are
reporting the incident.
→ The ‘Follow Up Responsibilities’ are (normally) prepopulated fields as well. This will be based on the
location of which the incident occurred. You can overwrite the names prepopulated in these fields to
another name (whenever necessary).
→ You can attached a file (e.g. photo, document, etc.) or a add a link that relates to the reported incident.
Note: When adding a photo, do not include photo which could identify person’s identity in compliance with privacy data
protection.
If any compulsory field is missing, the VelocityEHS global tooling will indicate the issues, as shown in the example
below.
→ Click on each one of the issues to be taken straight to the missing field, complete with the required
information and, again, click on ‘Submit First Report’.
This incident has been reported and will follow the next step on the workflow, which is the ‘Review and
Approval’ step.
As soon as an incident is reported, the person responsible for the ‘Review and Approval’ step will be notified by
email. Below an example of how this notification looks like.
In order to start the ‘Review and Approval’ step, follow the steps below:
→ Through the notification received by email, click on the link (incident number) to be taken to the review
page.
→ Alternativelly, you can also access the same information through ‘My Open Actions’ part available on
the main page of VelocityEHS global tooling.
→ Click on ‘Incident’ and then select the one you need to review and approve.
→ Make sure you are at the ‘Review and Approval’ step (1).
→ Check and review all information added in all fields and make the necessary adjustment. For instance
you should add translation into English for the ‘Title’ and ‘Description’ if these fields were reported in
other language than English (2).
→ Click on ‘Review and Approval’ (3).
Some additional things you may consider when reviewing and approving an incident are explained below.
You may consider adding a new notification for this specific incident. For this, follow the steps below:
→ Click on the ‘Email notification’ part (1).
→ Click on ‘Add New Notification’ (2).
→ Define the new notification by adding the required informantion on the field ‘Add New Notification’ (3).
It is also possible (whenever applicable) to convert an incident reported to a near miss or a hazard report. For
this, follow the steps below:
→ Click on the ‘hamburguer’ menu.
→ Select the desired option ‘Convert to Near Miss’ or ‘Convert to Hazard ID’.
→ Check all the fields and click on ‘Save and Exit’.
This incident has been rewied and approved and will follow the next step on the workflow, which is the
‘Investigation’ step.
If you have been nominated as responsible to perform an incident investigation, you should follow the steps
described below.
Note: Depending on the specificity of each incident, it might be that, during the investigation of an incident, additional
information will be required and, therefore other fields than the ones shown below will pop up automatically based on your
selection. You should add information for all fields shown during the investigation step.
→ Select the ‘Investigation’ part and complete with all required information.
→ Indicate whether the incident is classified as ‘Restricted Days’; ‘Lost Days’; ‘Fatality’.
Note: By hoving over the mouse in some fields, you will see the definition of that specific field (e.g. ‘Lost Work’). This may
help you on defining the proper selection.
Note: For other definitions, consider consulting the ‘Glossary applicable to VelocityEHS’ (DOC01067847).
→ Complete the required informaiton for the ‘Injury / Illness Details’ part.
→ If needed (applicable to ‘Body part’), you can add more items by selecting the plus button.
→ Add the information for the ‘Safe Work Practices’ and ‘Insurance Rerpoting’.
→ Complete the Risk Assessment by applying the Risk Matrix. Click on the link to access the Vanderlande
Risk Matrix 5X5 to support your selection on ‘Exposure’, ‘Occurrence’, ‘Avoidance’ and ‘Severity’.
→ Run the ‘Root Cause Analysis’ by accessing the supportive material available through the links.
→ Determine the ‘Root Cause’ by selecting one (or more) options.
→ On the ‘Corrective Actions’ part, add the actions defined during the investigation of the reported
incident. Determine responsible for those actions.
→ Check and review (if needed) all other fields ‘Attachements’; ‘Email notifications’ and ‘Audit Trail’.
→ Once done, click on ‘Complete Investigation’.
This incident has been investigated and will follow the next step on the workflow, which is the ‘Review’ step.
If you have been nominated as responsible to review an incident after its investigation, you should follow the
steps described below.
Note: There is no short video available which demonstrate this step.
It is especially important to review the root cause determined through the ‘Investigation’ part and the associated
‘Corrective Actions’ target to the defined root cause(s).
The pictures below provide you with an example on how to perform this review.
→ On the ‘Investigation’ part shown below, you can see that one root cause has been identified
(Processes/Procedure).
→ On the ‘Corrective Actions’ part, you can see the corrective action targeted to the root cause
‘Processes/Procudere’ (1).
→ By clicking on the action ID (2), you will be taken to the deatiled information about this corrective
action.
→ On the ‘Action Item’ part shown below, you can review all the fields related to this action.
This incident has been reviewed and will follow the next step on the workflow, which is the ‘Pending Closure’
step.
After the ‘Review’ step, the next step on the Incident workflow is the ‘Pending Closure’ step. Here all the
corrective actions related to the incident should be closed in order to allow the incident to be closed as well.
→ On the ‘Pending Closure’ step, review all information and current status of all actions related to the
incident.
→ Once complete, click on ‘Close Incident’.
If any action is still open, the system will indicate that there is an issue.
→ By clicking on the ‘Correcitve Actions’ link, you can check the information related to this action including
who is responsible for its completion.
Note: For additional support of action workflow, check the chapter ‘Standalone action’ which follows the same workflow for
any action within VelocityEHS global tooling.
→ Once all actions are closed, you can then close the incedent bu clicking on ‘Close Incident’.
The incident has been closed which is the last step on the Incident workflow.
Additionally, through the ‘hamburguer’ menu, you have some options, for instance, to print the incident.
It is important to know how the Near Miss workflow looks like because these are the steps in which an Near Miss
reported in VelocityEHS will follow.
Differently from the Incident workflow, for the Near Miss, there are no ‘Review and Approval’ and ‘Review’
steps.
This near miss has been reported and will follow the next step on the workflow, which is the ‘Investigation’ step.
If you have been nominated as responsible to investigate a near miss, you should follow the steps described
below.
Note: Check the explanation on how to investigate an incident since the fileds are similar for investigating a near miss (specific
remarks related to near miss will be mentioned below).
Note: There is no short video specific for a near miss investigation, consider watching the ‘How to perform an incident
investigation’ instead since it is the same approach as for near miss.
This near miss has been investigated and will follow the next step on the workflow, which is the ‘Pending
Closure’ step.
After the ‘Investigation’ step, the next step on the Near Miss workflow is the ‘Pending Closure’ step. Here all the
corrective actions related to the near miss should be closed in order to allow the near miss to be closed as well.
→ On the ‘Pending Closure’ step, review all information and current status of all actions related to the near
miss.
→ Once complete, click on ‘Close Near Miss’.
The near miss has been closed which is the last step on the Near Miss workflow.
It is important to know how the Hazard Report workflow looks like because these are the steps in which an
Hazard reported in VelocityEHS will follow.
Differently from the Incident workflow, for the Hazard Report, there are no ‘Review and Approval’,
‘Investigation’ and ‘Pending Closure’ steps. This is to facilitate the report of any hazard identified within
Vanderlande Industries and to make it simple for the users to report them.
→ Define the ‘Hazard Type’ if the report is related to an ‘Unsafe Act’ or an ‘Unsafe Situation’.
Differently from incident, when reporting a hazard, the ‘What’ field is answered based on ‘What could have
resulted’, otherwise it would be an incident and not a hazard to be reported.
This hazard has been reported and will follow the next step on the workflow, which is the ‘Review’ step.
If you have been nominated as responsible to review a hazard, you should follow the steps described below.
Note: Check the explanation on how to review an incident since the fileds are similar for reviewing a hazard (specific remarks
related to hazard report only will be mentioned below).
If none ‘Corretive Actions’ were added during the hazard report step, you (as responsible for the ‘Review’ step)
should add, at least, one corrective action addressed to the hazard reported.
→ Complete the fields applicable for the corrective action shown below.
It is possible that the corrective action addressed to the reported hazard is already completed by the time the
review step is taking place, in that case, you may consider selecting the ‘Action is Complete’ option. Otherwise
the corrective action must be completed before the hazard can be closed.
Since there is no ‘Pending Closure’ step for the Hazard Report, once the ‘Review’ step is completed, the hazard
goes to the last step on its workflow which is the ‘Closed’ step.
The hazard report has been closed which is the last step on the Hazard Report workflow.
8. AUDIT MODULE
The information below will guide you on how to use each one of the topics available on the Audit Module of
VelocityEHS.
8.1. Audit
It is important to know how the audit workflow looks like because these are the steps in which an audit in
VelocityEHS will follow.
→ Complete the information required for all fields as shown in the example below.
Note: Depending on the type of audit to be performed, few days might be necessary to complete the audit (e.g. internal audit
based on ISO standard normally is organized in one or two weeks).
Note: Depending on the type of audit, you can select as a ‘reocurring event’ and determine the reocurrence pattern.
→ Select ‘Schedule Audit’ or, alternatively through the hamburger menu, you can also select ‘Begin Audit’
or ‘Save Draft’.
Same as the Incident Module, whenever a missing information is identified, the VelocityEHS system will indicate
the issue.
→ Solve the issue (if applicable) and click on ‘Schedule Audit’.
This audit has been scheduled and will follow the next step on the workflow, which is the ‘In Progress’ step.
If you have been nominated as audit leader or part of the audit team, you can see the scheduled audit through
the ‘Monitor’ part.
→ Click on ‘Monitor’ and ‘Audit’
→ Identify the audit you want to perform and click on the link associated to it.
→ Alternatively, through the hamburger menu, you may also select ‘Save and Exit’ in case the audit will be
continued.
This audit has been performed and will follow the next step on the workflow, which is the ‘Review’ step.
The overview shown below can be seen by clicking ‘Monitor’ and then ‘Audit’.
After all scope of the audit is completed, the lead auditor with or without the audit team, can perform the review
step. For that, the following steps should be taken.
→ Make sure you are on ‘Review’ step (1)
→ Check the answers provided for the selected checklist (if needed)
→ Select the ‘General Results’ part (2)
→ If no information has been added by the audit team for the finding part, add the ‘Finding’ description
and determine the ‘Finding Type’ applicable to this audit and complete all fields in this part (3) as shown
in the example below. You can add another finding by clicking on the ‘plus’ button
Note: It is not the audit team’s responsibility to determine the actions to be addressed to each finding. This is the responsibility
defined in the ‘Draft’ step.
The Audit Report has been submitted and will follow the next step on the workflow, which is the ‘Pending Action
Plan’ step.
The overview shown below can be seen by clicking ‘Monitor’ and then ‘Audit’.
If you have been nominated as ‘Responsible for Action Plan’, you will receive a notification that you have to
complete the action plan. For that, the following steps should be taken.
→ Make sure you are on ‘Pending Action Plan’ step (1)
→ Review all information added for this audit by checking the ‘Audit Information’ part (2)
→ Determine the actions needed for each one of the findings. You can add actions by clicking the ‘plus’
button (3)
→ Once completed, click on ‘Submit Action Plan’ (4)
The Action Plan has been submitted and will follow the next step on the workflow, which is the ‘Action Plan
Review’ step.
The overview shown below can be seen by clicking ‘Monitor’ and then ‘Audit’.
If you have been nominated as ‘Responsible for Action Plan Review’, you will receive a notification that you have
to review the action plan. For that, the following steps should be taken.
→ Make sure you are on ‘Action Plan Review’ step (1)
→ You may consider reviewing all information added for this audit by checking the ‘Audit Information’ part
(2). As responsible for the Action Plan Review, you should make sure that the actions addressed to the
findings (shown on the ‘General Results’ part) are properly defined.
Note: Improtant to notice that an audit can be close even if an action is still open. This is because sometimes it might take
months to close an action and, therefore the audit itself can be closed and the completion of an open action will be checked in
the next audit cycle.
This Audit has been closed and this is the last step of the workflow.
The overview shown below can be seen by clicking ‘Monitor’ and then ‘Audit’.
8.2. Inspection
It is important to know how the inspection workflow looks like because these are the steps in which an
inspection in VelocityEHS will follow.
The Inspection has been scheduled and will follow the next step on the workflow, which is the ‘In Progress’ step.
The overview shown below can be seen by clicking ‘Monitor’ and then ‘Inspection’.
The Inspection has been performed and will follow the next step on the workflow, which is the ‘Review’ step.
Note: Check the ‘Standalone Action’ chapter to know how an action workflow is applicable on VelocityEHS.
This Inspection has been closed and this is the last step of the workflow.
8.3. Observation
It is important to know how the observation workflow looks like because these are the steps in which an
observation in VelocityEHS will follow.
The Observation has been closed and this is the last step on the workflow.
The overview shown below can be seen by clicking ‘Monitor’ and then ‘Observation’.
It is important to know how the safety walk workflow looks like because these are the steps in which a safety
walk in VelocityEHS will follow.
The Safety Walk has been performed and will follow the next step on the workflow which is the ‘Review’ step.
The overview shown below can be seen by clicking ‘Monitor’ and then ‘Safety Walk’.
If you have been nominated as responsible for review a safety walk, you should follow the steps below.
The Safety Walk has been closed and this is the last step on the workflow.
It is important to know how the risk assessment workflow looks like because these are the steps in which a risk
assessment in VelocityEHS will follow.
Note: The instruction below also apply to the Aspects & Impacts.
Note: The schedule step will be skiped and not shown in this manual.
→ Determine the ‘Residual Risk’ (whenever applicable) after the safety controls are in place.
After completing all fields, the added information will be placed in the tab ‘Analysis’ as shown by the example
below.
Note: For the example shown below, the ‘Residual Risk’ is calculated after the action to ‘replace damaged ladder’ has
progressed.
Note: The application of the Vanderlande Matrix 5X5 is part of the Corporate HSE Standard ‘HSE Planning, Hazard
identification & Risk assessment - CS-HSE-04’ (DOC01054505). Check this standard to understand how to apply the Matrix
5X5.
Note 1: Only users who hold ‘Compliance Manager’ role or System Administrators can have access to the Compliance Module.
Note 2: There is no workflow associated to the Compliance Module.
The information below will guide you on how to use each one of the topics available on the Compliance Module
of VelocityEHS.
External Regulation is a mandate issued by a governing body which the company must abide by. The Compliance
Module of VelocityEHS does not indicate to a Vanderlande site which external regulation is applicable to it.
However this module can be used to register not only an already known applicable external regulation but also
the required actions needed to ensure its compliance.
→ If needed, additional files and links can be registered through the ‘Attachments’.
→ To conclude this process, you can add a ‘permit’ (whenever applicable to the external regulation) or,
through the ‘hamburger’ menu, you can ‘Add Action’ related to the compliance of the external
regulation or, alternatively, you can ‘Save and Exit’.
Note: Refer to ‘Action Item’ to know how to register an action.
An Internal Policy is a standard that is developed and mandated by the Vanderlande Industries itself. Internal
policies can be applicable companywide or at lower level such as at business unity level, at customer centre level
or even at site level. The Compliance Module of VelocityEHS can support locations on registering and managing
internal policies.
→ Select which topics this internal policy is related to (multiple selection is possible).
→ Indicate the source of the Internal Policy.
→ Indicate for each Vanderlande level/site the internal policy is applicable to.
→ Indicate (whenever applicable) the initial applicability date and last revision date.
→ If needed, additional files and links can be registered through the ‘Attachments’.
→ To conclude this process, you can ‘Add Action’ related to the compliance of the internal policy or,
alternatively, you can ‘Save and Exit’.
Note: Refer to ‘Action Item’ to know how to register an action.
10.3. Permit
A Permit is a license issued by a governing body to implement the requirements of a regulation. Within the
Compliance Module of VelocityEHS, a permit it is normally (if not always) associated to an external regulation.
Therefore, although it is possible to register only a permit, it is expected that all permits are associated to the
external regulation which requires a Vanderlande site to obtain certain permit.
→ If needed, additional files and links can be registered through the ‘Attachments’.
→ To conclude this process, you can ‘Add Action’ related to the permit or, alternatively, you can ‘Save and
Exit’.
Note: Refer to ‘Action Item’ to know how to register an action.
The Action Item part of the Compliance Module of VelocityEHS is to support registering actions needed to ensure
compliance to any ‘External Regulation’, ‘Internal Policy’ and/or ‘Permit’. An action item can be registered while
registering one of the above mentioned topics or at any moment necessary.
As previously indicated, it is possible to register an action item while registering an external regulation, internal
policy and/or permit. In order to do that, follow the steps below:
→ After completing the fields on the ‘DRAFT’ step for one of the topics below, select ‘Add Action’.
→ If needed, additional files and links can be registered through the ‘Attachments’.
→ To conclude this process, select ‘Submit’.
Note: The system will indicate whenever there is an issue (missing information on compulsory fields) as shown below.
→ Solve the issues by adding information on the compulsory fields and select ‘Submit’ again.
The Action Item has been registered.
As Compliance Manager at a Vanderlande site, it is important to manage all actions related to external
regulations, internal policies and permits applicable to a certain location. The Compliance Actions Items –
Calendar is an interesting option which provides the Compliance Manager with o good overview of these actions.
A list of all actions the specific Compliance Manager is allowed to see will be shown.
→ Click on ‘Calendar’.
All actions related to a specific external regulation, internal policy and/or permit are registered as a Compliance
Plan for that specific case. For example, for an ISO certified location it is necessary to take some action to be in
compliance with the ISO requirement about the Company’s policy (such as the ‘Environmental Policy). The same
actions will also be applicable to another ISO certified location. Therefore, copying an existing Compliance Plan
from one location to another, is an useful feature of the Compliance Module of VelocityEHS.
In order to copy an Compliance Plan from one location to another, follow the steps below:
→ On the home page, click ‘Admin’ and then ‘Copy Compliance Plan’.
→ Select the ‘Source Location’ and tick the actions you want to copy to the new location.
→ Define one role as ‘Responsible for Action Items’.
→ Select the ‘Destination Location’ (multiple selection is possible) and click on ‘Copy.
→ Select ‘Copy’ or ‘Copy & Assign’ depending on the definition shown on the box below.
It is important to know how the Action workflow looks like because these are the steps in which an action in
VelocityEHS will follow.
Note: Many actions in VelocityEHS will be linked to specific modules (e.g. Incident Module, Audit Module, etc). However it is
also possible to use the ‘Standalone Action’ to register an action not linked to any specific module. Nevertheless any action
within VelocityEHS system will follow the workflow shown above.
The Standalone Action has been registered and will follow the next step on the workflow which is the ‘Closed’
step.
The overview shown below can be seen by clicking ‘Monitor’ and then ‘Action Items’.
The (Standalone) Action has been closed and this is the last step on the workflow.
ANNOUNCEMENTS – this webpart displays all announcements that have been set up in the system and are not
yet expired. This webpart includes the description and attachment(s) associated to that announcement along
with extra information such as the author and date it was published.
Note: There is no option to publish an announcement for a specific location only. Announcements are always visible
companywide.
STATUS OF YOUR OPEN ACTIONS BY LOCATION – this webpart shows the user’s action items for multiple
locations at a time. It is setting as seven days until due date, therefore it shows when an action is coming due or
is overdue.
STATUS OF YOUR OPEN ACTIONS BY LOCATION – this webpart monitors your action items by source for a
location. It is setting as seven days until due date, it displays when an action is coming due or is overdue.
STATUS OF INCIDENTS REPORTED AT VANDERLANDE INDUSTRIES – this webpart displays the average time
incidents are currently spending in a workflow stage for Vanderlande Industries at a time.
STATUS OF AUDITS & INSPECTIONS & SAFETY WALKS & OBSERVATIONS AT VANDERLANDE INDUSTRIES – this
webpart displays the average time audits, inspections, safety walks and observations are currently spending in a
workflow stage across Vanderlande Industries at a time.
This webpart shows the rate of recordable incident at Vanderlande Industries in the previous month.
Note: Recordable incidents are classified as any ‘Lost time case’; ‘Restricted time case’ and/or ‘Medical treatment case’.
Additionally, it is considered 200,000 worked hours for employees only.
Same as above, this webpart shows the rate of recordable incident at Vanderlande Industries but for the year to
date (YTD) instead of previous month.
Note: Recordable incidents are classified as any ‘Lost time case’; ‘Restricted time case’ and/or ‘Medical treatment case’.
Additionally, it is considered 200,000 worked hours for employees only.
This webpart shows the six most common incidents across Vanderlande Industries for the year to date (YTD).
This webpart shows the six most common root causes across Vanderlande Industries for the year to date (YTD).
This webpart displays a sparkline for the trend of each preventive activity being presented (e.g., hazard,
observation), along with the total count of the activity over the year to date time period, and a ratio of that
activity compared to the number of incidents.
This webpart provides the users access to tutorials of the most common actions in the VelocityEHS global tooling
straight from the global dashboard.
Any update on the Global dashboard will be organized by the Corporate HSE team and communicated to the HSE
Network within Vanderlande Industries. Additionally an announcement will be published as part of
communication companywide.
To request a change to the Global dashboard use the Topdesk and issue a ‘Change request’ (LINK HERE). Your
request will be managed by the Corporate HSE team.
→ Select the role you want to create a dashboard and the location of it.
→ Click on ‘Open Catalogue’, check the options and drag and drop to the location you want to place it on the
dashboard.
The option to create a Personal dashboard is only available for users who have a primary location listed on the
user’s profile. By using the User’s Primary Location means that all information will be displayed for the user’s
dashboard location. For instance, if the user location is at country level (the level 3 in the current location tree
structure) this option will display Level 3 records and anything below.
Any user who has a primary location will be able to select his/her personal dashboard as favorite by setting it as a
default dashboard.
Management of change regarding VelocityEHS global tooling will be managed by the VelocityEHS Change Control
Board (VCCB). System e Global administrators are members of the Board of Change Team. A calendar of
quarterly meetings with the VelocityEHS Board of Change Team will be organized to discuss the efficiency of
VelocityEHS global tooling and the change request for the period and, whether they will be implemented.
Whenever necessary, general users can request a change on VelocityEHS global tooling by issuing a Topdesk call.
13.1. Topdesk
Any ‘Error’, ‘Question’ or ‘change Request’ related to VelocityEHS will be managed through a Topdesk call.
To issue a Topdesk call, follow the steps below:
→ Open the Topdesk system
→ Select ‘Software & Workplace’
→ Select ‘Software’
→ Select ‘VelocityEHS’
All Topdesk calls will be addressed to Corporate HSE members (initially) and, depends on the content, forwarded
to local HSE team and/or another department.
Internal requests – should be addressed to the Corporate HSE Team or through a Topdesk call. The Corporate
HSE team will ensure the proper resource will be allocated to manage the request. If needed, the request will be
addressed to the VelocityEHS Board of Change Team during the quarterly meetings.
Within the Corporate HSE team, the main contacts for VelocityEHS topics are: