You are on page 1of 17

CONTRACTOR

SAFETY SOLUTION
(CSS)
A WEB BASED APPLICATION FOR CONTRACTORS
Purpose And Scope

 CSS is launched by SAUDI ARAMCO (SA) for contractors safety and inspection
reporting.

 This will be utilized across all SA organizations and their contractors.


Objectives

 To achieve an incident / injury free work environment.


 To provide single-access point to relevant HSE data to contractors, HSE
performances and compliance.
 To provide a glance to senior / top management through DASH BOARDS and
ANALYTICAL REPORTS.
 To help top management of SA to determine future contractor awards by
comparing contractors efficiency and performance.
 Overall objective is to be able to “PREDICT” potential incidents before they
occur.
Access & Navigation

 Accessing the CSS application via the EXTRANET link;


 http://potable.Aramco.com/
 Enter extranet User Name, Password and SMS code form mobile.
High Level Navigation
 Worklist
❑ All the tasks pending with the user will be available within the worklist.
 Pending And Submission
❑ All the records saved in draft will be available under Pending & Submission.
 User References
❑ Safety-related General Instructions (GIs) related to contractor safety will be
available here.
 Announcement
❑ Contractor-related announcements will be available here.
 Safety Bulletins
❑ Safety bulletins will be visible here.
Incident Reporting

 Reporting Incidents and Injuries within the CSS shall be a guided process or flow
where conditional logic is applied to forms, fields, and dropdown picklists as well
as from submission buttons and radio controls.

CREATE INCIDENT

 Required Data
 Basic Information (What / When/ Where / How)
 Tools involved,
 User group detail like Vendor ID, Contract #)
Different Consequences Types

 Injury / Illness (Who, How, Select body parts)


 MVA (Influencing factors, Driver / Vehicle detail)
 Heavy Equipment (Contributing factors, operator / Equipment detail)
 Dropped Objects (Information about dropped object, system will
calculate fall energy / potential severity)
 Fire (Detail / Type of fire)
 Property Damage (Detail of property / type etc.)
 Material Release (Detail, if chemical involved click “New” tab)
 Attachment (Add all supporting files)
 Witnesses (Detail, add witness if more than one)
Near Miss Reporting

 Basic information
 What happened (Description), potential loss description.
 Add tool (s) if involved (any)
 Enter location / date / time
 Enter contractor / Vendor details, IDs &
 Submit

** If a near miss recorded in the system is identified as a “Safety Observation”


then its category will be changed to “Safety Observation” by Incident Processor
and system shall copy all recorded detail in the near miss to the “Safety
Observation” form.
Dropped Objects

 A reporter can enter dropped objects by clicking “Gear” on top left of the
screen.

 Switch dropped objects option to “Yes”.

 Enter dropped object information like type, weight, distance of falling, object
diameter, length etc.

 Enter the RIGZONE as per image provided in the system screen.

 Enter the RIGZONE impact area.


Corrective Actions
( and assignment to person / vendor)
 This activity is to be handled by “Safety Coordinator”.
 A reporter can also perform this task if he / she is authorized to do so.

 By clicking corrective action tab, we have to


❑ Enter details of corrective actions
❑ More corrective actions can be added by clicking on “Add”.

 By clicking attachment tab, we can


❑ Upload attachment from local machine
❑ Submit near miss
SAFETY OBSERVATION REPORTING

 Creating safety by clicking “Safety Observation”.


 Add ‘Basic Information’.
 Further detail can be added in ‘What Happened’ section.
 Can enter detail of any tool involved (if any).
 Enter contractor, vendor and subcontractor IDs (if available).

ATTACHEMENT
 Attachment can be uploaded from local machine.

CORRECTIVE ACTIONS ( AND ASSIGNMENT TO PERSON / VENDOR)


 Click the Corrective Actions tab.
 Enter details of corrective actions.
 Click ‘Add’ to add additional corrective actions.
Incident / Near Miss Investigation

 Incident Investigation Process


❑ Plan Investigation
❑ Gather Information
❑ Analyze Incident
❑ Determine & Define Tasks
❑ Close Investigation

1 of 3
Incident / Near Miss Investigation

Following sections that shall be available for the investigation


coordinator.

1. Investigation Team Formation (SME Required)


2. Evidence Mapping and Data Collection
3. Casual Factor
4. Root Causes
5. Corrective Actions

2 of 3
Incident / Near Miss Investigation

 Click on ‘Worklist’ on Application Homepage.


 Locate and click on the investigation record assigned to the user.
 Click on the ‘Investigation’ tab.
 Add the Investigation Team by clicking on “Add New”
 Add evidences by clicking on ‘ Upload’ option.
 Enter the Casual Factor comments in the casual factor identification section.
 Select the relevant ‘Root Causes’.
 Click Add to add additional corrective actions.
 Click on ‘Submit’ Investigation to submit the investigation to ‘Specialty
Group/Safety Coordinator’
3 of 3
Searching Incidents

 Click on ‘Search Incidents’.

 Apply appropriate search criteria and click on search


Implementing Corrective Actions

Corrective Actions may be assigned to a person / vendor to mitigate the safety


risk posed by the reported situation for future.

 All Corrective Actions activities are accessed via the CSS Homepage worklist.
 Process Corrective Actions –Action Implementer
❑ Click on ‘Worklist’ on the Application’s Homepage.
❑ Click on the Corrective Actions record.
❑ Enter the Implementation Comments in the comments field.
❑ Upload attachments (if any).
❑ Click on Implement.
Verifying Corrective Actions

 Click on ‘Worklist’ on the Application Homepage.


 Select on the Corrective Action record.
 Click on verify to ‘Verify’ the Corrective Action taken by Action Implementer.

You might also like