ICSS Routine Standard
ICSS Routine Standard
Purpose
This procedure describes the steps required to safely carry out Industrial Control
System Requirements [ICSR] sustainment tasks for Qua Iboe Terminal [QIT] process
control equipment.
Risk Links There are no Risk Links associated with this procedure.
Table of Contents
Purpose ................................................................................................................... 1
Risk Links ............................................................................................................... 1
Equipment ............................................................................................................... 4
Safety Information .................................................................................................. 7
Prerequisites .................................................................................................... 7
Qualifications and Training ............................................................................... 7
Requirements ................................................................................................... 7
Special Tools and Equipment ........................................................................... 7
Personal Protective Equipment ........................................................................ 7
Hazards and Precautions ................................................................................. 8
Tasks........................................................................................................................ 9
1.0 Preparation for Maintenance .................................................................... 9
2.0 3M Virus Definition Update & Drives Scan ............................................... 10
Procedure is UNCONTROLLED and valid for 7 days after printing date 06/08/2020 10:32.
OIMS61-NGJV-QIT-2019-
001 Rev 0
QIT ICSR Sustainment Normal
Equipment
Strategies
ICSR Strategies
The table below lists the equipment strategy and required frequency of preventive
maintenance for the Process Control systems. The procedures on the following pages
details the steps to satisfy the requirements outlined in this table.
Safety Information
Prerequisites
Qualifications This procedure is intended for use by trained technicians who have successfully
and Training completed the competency assessment(s) for use of this procedure, and all
associated safety / work management procedures, to a level consistent with the
requirements of the Competency Assurance Standards (CAS).
Special Tools Due to the nature or location of the work, the following equipment is required:
and Equipment
• Job-specific tools and equipment:
▪ Digital multimeter / Electronic test equipment
▪ Terminal screw drivers (insulated)
▪ Laptop computer / configuration station
▪ Static discharge strap
▪ Approved USB storage media
Personal List of personal protective equipment (PPE) required during the execution of this
Protective procedure includes:
Equipment • PPE as specified by the Upstream Nigeria Safety Manual
Hazards Precautions
The following hazardous conditions are possible: The following precautions are necessary while
performing the tasks in this procedure:
There is a risk of electrical shock or electrocution Use extreme caution when working around the
when working around energized equipment. energized circuitry on Industrial Control Systems.
Exposure to static electrical discharges may occur. Use safe static discharge techniques / static band
when working with ICS hardware to avoid undesired
static discharge to cabinet equipment.
There is a possibility of grounding or short circuiting Prior to performing work, confirm that grounding /
a controller card, which could cause a process earthing straps and/or other grounding / earthing
emergency shutdown (ESD), with a resulting loss of devices are in place, and the terminations are tight
production and financial loss. and corrosion free.
There may be conflict with other activities in the Investigate any Simultaneous Operations (SIMOPS)
immediate vicinity. or other activities in the immediate area that could
affect the performance of the maintenance task.
Existence of virus or malware. Scan removable media for virus or malware.
The work area may be crowded with equipment Ensure that all access and egress routes are
and/or materials, and also may be subject to traffic unobstructed by materials and equipment.
by other workers.
There are no additional hazards foreseen and this procedure, together with existing controls within the Work
Management System, will be sufficient to perform this task.
Operations are conducted in accordance with company and governmental requirements for protection of the
environment.
For applicable safety requirements, refer to the safety manual, company safety bulletins, and the appropriate
Material Safety Data Sheet (MSDS).
Tasks
1.0 Preparation for Maintenance
Reference: All work must be conducted in accordance with the Upstream Nigeria Work Management
system Manual.
CAUTION: • To avoid equipment contamination, cover exposed openings during the maintenance tasks.
• Do not use flammable solvents when cleaning parts and equipment.
1.3 Prepare a Job Safety Analysis (JSA) and conduct a Toolbox Talk with all personnel ICSS
involved in the job.
1.4 Where applicable, prepare the Permit to Work in accordance with the work scope ICSS
requested.
1.6 Inform the Control Room Operator of the intended work and provide the tag number ICSS
of the affected equipment.
1.7 Where applicable, ensure that the area has been checked for flammable gases. ICSS
IF... THEN...
Necessary to remove the source Isolate, and lock and tag the equipment according ICSS
of energy to LOTO guidelines.
IF... THEN...
1.9 Scan all removable media for virus / malware prior to use on Industrial Control ICSS
System.
End of Task
Virus signature definition needs to be updated regularly for the protection to be effective against current
computer virus and worm risk. An IPES based programmed maintenance drives the frequency of anti-virus
definition update.
FOR
• Where computers are in a Windows Domain, an Anti-Virus Management Server deployment approach
may be used and the definition update should be done in the Anti-Virus Management Server, which will
then circulate the definition update to the client in that network automatically,
• In a situation where Client-based anti-virus software is installed then individual definition update should
be done .
• Client-based anti-virus software will be installed and definition update should be carried out on
individual stations.
Complete the following steps to update Symantec Endpoint Protection definition on Workstations and
Laptops.
2.1 Sign out PCS HARD DISK/FLASH DRIVE from the facility custodian ICSS
2.2 Download the latest virus definition update from Symantec website using (EMIT) ICSS
GME Computer
b. Navigate to 'Virus Definitions & Security Updates' page using either of the ICSS
following routes:
or
(Confirm your product version via: control panel - programs - programs and
features. Then check product property)
e. Click on the appropriate file name (confirm the BIT of the system you want to ICSS
apply the antivirus update on) to download the update file (in .exe) format.
where yyyy = Year, mm = month, dd = day, X = number, The last two numbers
before the (.exe) signify the bit
! IMPORTANT: After clicking the indicated bar in the last step, on the pop-up on the
bottom bar, click "Save". Do not click "Run" on a GME computer.
g. Copy it to a scanned (virus free) PCS HARD DISK/FLASH DRIVE using ITPA ICSS
by qualified personnel
Pre-requisite: ITPA End Users need to be a member of the LAN Group - ITPA.
PROD-AFRICA-NI-FLDUNM.UG.
Device enrolment (browser) is required from all users at least once or whenever
one of the conditions below exists:
• User trying to access ITPA for the first time (all user profiles);
• Enrolment expired (no ITPA activities in the last 90 days);
• ITPA authentication using a different browser never enrolled (or using a different
EMIT computer)
a. Access ITPA portal using the link: http://goto/itpa in Web browser ICSS
e. Call Help desk for desktop configuration through the help desk ext 21333 and ICSS
follow the call prompt.
Note:
• For ITPA Check out Procedure, see steps 2.4 a-e below.
• Remember we have only 2 ITPA accounts in UN, so avoid keeping a password
for a long time without checking the account back in
Leave Search field blank and click on Search button to view available ITPA
accounts
b. Select required account by double clicking to open Account details page ICSS
d. On the 'show Password' pop-up window, enter reason for checking out ITPA ICSS
account and Ticket ID (Work Order Number) from ITServices then click OK.
2) Scroll down to the end of the web page and click “Get Assistance” ICSS
3) Click the “What can we help you with?” drop the box and select “other” as ICSS
seen below. Under availability input GMT +1
4) Fill every other data’s as found in the image below, then click submit ICSS
Note the ticket number as this will be entered in the "show password" page
2.5 Log on to GME computer using ITPA account and password. If already ICSS
logged on with user XOM profile, sign out and login as other user.
a. Open GME User Tools and select Enable Unencrypted Write access under ICSS
Encryption category
b. Insert external media device when Ready for Unencrypted Removable Media ICSS
prompts for insertion. And click OK
b. Leave Search field blank and click on Search button to view available ITPA ICSS
accounts
c. Select the account you checked out (account with lock symbol) to open ICSS
Account details page by double clicking it.
e. Select Change the password immediately (by the CPM) and click OK ICSS
a. Insert the removable device into the system, whose antivirus you want to ICSS
update and Locate the file inside they disk
b. Double click the file to install update, then Click yes and wait for few seconds ICSS
for the update to take effect
d. Launch the antivirus software and confirm that the virus definition is up to date ICSS
and that your computer is secured
a. Sign out the removable drive from the facility custodian ICSS
b. Insert the removable drive in a system with up to date anti-virus definition ICSS
e. Right click on the removable drive and click “scan for viruses” to start ICSS
scanning
f. Review the scan result for any risk/virus detected when the scan is ICSS
complete
End of Task
3.1 Contact terminal superintendent and discuss task requirement to verify personnel ICSS
movement.
3.2 Check with the terminal superintendent with the current/subsisting authorized ICSS
personnel list to confirm changes of personnel within the quarter under review.
Example
3.3 If there is/are personnel change(s), identify personnel who have left location. ICSS
Request for or raise notification for corrective workorder to effect necessary changes
- specify changes to be effected, including specific username(s)/account(s) to be
updated/deleted.
3.4 Document the required changes to be made and the corrective notification to be ICSS
used to effect such changes on the PM work order before closeout.
End of Task
4.1 Obtain materials/removable media movement logbook from the location ICSS
Maintenance Supervisor or designate.
4.2 Check on site ICSR documentation for a listing of materials [e.g. processor keys, ICSS
removable media, etc. for the site].
Create one if the list is not available and obtain sign-off by the Maintenance
Supervisor.
4.3 Check logbook entries for materials/removable media usage covering the duration ICSS
under review. Ensure:
4.4 Obtain signature of Superintendent or Maintenance Supervisor for completed rows. ICSS
4.5 Document corrective work order for findings that could not be closed during this ICSS
review.
4.6 Return logbook and material list to safe storage with location Maintenance ICSS
Supervisor/designate.
End of Task
5.1 ICSS
Open the approved and current removable media users list on I-Drive.
Example: I:\MPN\ORG\AFSS & DCS\.I C S R\2019 UN PCS SECURITY
DOCUMENTS\2019 REMOVABLE MEDIA USERS' & PHYSICAL KEY MGT REVIEW
5.2 ICSS
Open the approved and current firecall users list on I-Drive.
Example: I:\MPN\ORG\AFSS & DCS\.I C S R\2019 UN PCS SECURITY
DOCUMENTS\2019 FIRECALL USERS' LIST (PER LOCATION)
5.5 Obtain approval via DocuSign or email from Terminal Superintendent. ICSS
5.6 Save the updated and approved lists in pdf format in I-Drive for the applicable ICSS
quarter.
End of Task
Complete the following steps to perform routine surveillance of the PLC Control System to check the
complete system for active alarms and faults.
! IMPORTANT: If an abnormal condition is detected during any of the steps below, refer to the "Vendor documents"
section of this procedure for fault details and action.
! IMPORTANT: Record and report any unresolved fault recorded in the any module in the steps below to
maintenance supervisor and raise notification for correction.
b. Using the table below, confirm the status of the CPU. ICSS
*LED is steady when error is detected at the MPI/DP interface. LED flashes when
PROFIBUS DP interface is not replying (for master) or is not addressed by the DP
master (for slave).
**LED is steady when error is detected at module interface 1/2. LED flashes when
PROFIBUS DP interface module inserted in module slot 1/2 is not replying (for
master) or is not addressed by the DP master (for slave).
c. Observe the condition of the communication processor on the PLC Processor Rack ICSS
(slot 4, 5) and confirm the status indicators following the tables below.
d. Observe the condition of the Power Supply Module on the PLC Processor Rack slots ICSS
1 and 2, and record the status indicators following the tables below.
e. Replace batteries either every year or when the BAF light-emitting diode (LED) (Red) ICSS
on the Power Supply is ON.
CAUTION: Replace the battery only with the type recommended by the
manufacturer.
• Do not throw a new or low battery into an open fire and do not
perform any soldering work on the cell casing (maximum
temperature 100°C).
• Do not recharge the battery due to the risk of explosion! Do not
open a battery. Replace a faulty battery only with the same type.
Replacement batteries can be ordered from Siemens (Check
Siemens documentation for ordering information). This ensures that
a short circuit-proof type battery is installed.
• Always try to return low batteries to the manufacturer or deliver
them to a registered recycling company.
f. Observe the condition of the Industrial Ethernet Switch, Scalance X 208 and record ICSS
the status indicators following the tables below.
Scalace X 200
g. Observe the condition of the ET 200M Modules on the distributed I/O system and ICSS
record the status indicators following the tables below:
ET200M
h. Observe the condition of the Digital Input Modules on the distributed I/O system and ICSS
record the status indicators following the tables below:
i. Observe the condition of the Digital Output Modules on the distributed I/O system ICSS
and record the status indicators following the tables below:
j. Observe the condition of the Analog Input Modules on the distributed I/O system. ICSS
• Group error display: Red LED (SF), reported in its corresponding ET 200M
Module
• Reading diagnostic information: supported
• At the channel configured for current measurements, connect the shunt resistor
to the adjacent channel terminals in order to achieve the specified precision.
k. Observe the condition of the Analog Output on the distributed I/O system. ICSS
Group error display: Red LED (SF), reported in its corresponding ET 200M Module
and in front of module.
l. Record and report any unresolved fault in any of the modules to maintenance ICSS
supervisor and raise notification for correction.
1) Log off operator and log on to the WinCC with authorized user account. ICSS
2) To exit the Process Mode and close WINCC, access the Control Functions in ICSS
Button Set 2. (If not already set, change to Button Set 2 with the "Change
5) Log off operator and log on to the OS with authorized user account. ICSS
1) Start the SIMATIC Manager by either double-clicking the icon below on the ICSS
desktop.
2) Or by using the command: Start > SIMATIC > SIMATIC Manager (as shown ICSS
below)
Path
c. When the 'SIMANTIC Manager' screen comes up, click Cancel on the 'PCS 7 ICSS
Wizard...' screen that displayes.
d. Select and click on one of the icons - View (in the upper bar), then click Component ICSS
view and Online. (See below)
2) Select and right click each of the PLCs, one at a time. ICSS
3) In the drop down, click on PLC > Hardware Diagnostics (See below) ICSS
4) On the Hardware diagnostics window, select the CPU, click on Module ICSS
Information. Then choose Diagnostics Buffer.
6) Report any abnormality noticed. Use OEM documents to rectify any ICSS
abnormality when there is approved corrective work order.
1) Follow the steps on 6.2a-d, then choose PLC > Display Forced Values for ICSS
AS11/12/21/22, taking one at a time.
2) The 'Force Values' window opens to reveal any forced item(s) if it exist. ICSS
3) If any forced item exist, note the description and confirm there is an approval. ICSS
Take necessary action to have one in place if there is none or have the forced
point removed.
b. Record and report any problem or discrepancy and generate a work order as ICSS
necessary.
c. Exit from the SIMATIC Manager and ensure that the workstation is available for ICSS
process control:
1) Log of from the OS and click 'OK' when the 'ICSR...' screen appears to log on ICSS
Operator.
2) When the WinCC screen is ready, enter the appropriate password for normal ICSS
operation monitoring.
d. Follow the steps in the [Closeout] of this procedure to close PM. ICSS
End of Task
c. Observe the module OK status indicator on the 1756-EN2T Ethernet Bridge Module ICSS
for normal indication. The module OK status indicator should be "STEADY GREEN."
Any other status is abnormal.
d. Observe the module OK status indicator on the 1756-DHRIO Data Highway ICSS
+/RIO Port Scanner Module for normal indication. The module OK status
indicator should be "STEADY GREEN." Any other status is abnormal.
1) For ethernet communication (using RJ45 cable connection), confirm the IP ICSS
address displayed on the scrolling screen of the EtherNet/IP module
2) Configure IP address and domain of the laptop to communicate with the ICSS
controller
5) On the 'Configure Drivers' window, select EtherNet/IP Driver and click on Add ICSS
New...
7) Confirm the status of AB_ETHIP, Ethernet on the 'Configure Drivers' window ICSS
is Running
b. On the RSLinx page, confirm that the PLC shows up in RSWho. ICSS
d. Locate the previously backed up program of the controller. Click on File> open from ICSS
the Menu bar.
h. Select the controller and click on Go Online with the PLC. ICSS
i. If the controller goes online without showing “the open project has offline changes ICSS
that aren’t in the controller” message, the program is verified.
If the controller shows “the open project has offline changes that aren’t in the
controller” message, an upload must be performed.
Click on Upload (the uploaded program file may be named differently if the aim is
not to replace the previously backed up file) and wait to the uploading process to be
completed
k. Go to Major Faults and Minor Faults tabs respectively and note any faults logged. ICSS
l. Click on Clear Majors and Clear Minors on the respective Faults screens to ICSS
clear any fault log if any exist.
m. Check modules status. If faulted, make necessary correction using appropriate ICSS
corrective work order.
If any of the modules is faulted, a yellow caution sign appears beside it and a
description is shown on the lower bar of the controller organizer.
End of Task
8.0 6M Inspection & Diagnostics: Allen Bradley SLC 5/03 PLC System
SLC 5 CPU
c. Observe and record the condition of the Input / Output module and ICSS
channel status* indicator.
Note: The I/O indicator shows the status of the I/O modules in the controller.
*Some module do not have status indicator. For such, confirm the channel status
indicator.
N.B. The LED indication status in 8.1 (c) also applies here.
b. Launch RSLinx application - Start > All Program > Rockwell Software > RSLinx > ICSS
RSLinx. Confirm that the PLC shows up in RSWho.
It is hereby assumed that during installation, RSLinx application was properly setup
with the appropriate communication driver to establish communication with PLC. If
not, configure RSlink using PLC property. (Click communication, choose 'configure
driver'. Under configuration, choose PLC driver that matches the controller property)
d. On the RSLogix page, select and click - File > Open > C: > SLC500_Project > ... ICSS
(Select the project file of interest)
f. Select and click - Comm > Who active go online. Select the connected PLC on the ICSS
communication window that opens, then click Ok to go Online with the PLC.
Note: The FORCE indicator on the CPU (see 8.1b) shows whether the I/O forces
are active or enabled.
• Off indicates that no I/O points contain force values or I/O forces are inactive
(disabled).
• Steady amber indicates that forces are active (enabled).
• Flashing amber indicates that one or more I/O addresses have been forced but
the forces have not been enabled.
1) If force point(s) exist, identify the specific force point(s), match each with an ICSS
approved bypass certificate. Forced point is identified by '>ON', on the logic.
c. Close the PLC project and restore normal working condition. ICSS
End of Task
Complete the following steps to perform 6M ICS Complete Inspection & Diagnostics of the GE BN 3500
Vibration Monitoring System for active alarms and faults.
The module annunciates this via a green "Supply OK" light emitting diode on the
power supply’s front panel.
b. Verify that the low (120) voltage AC I/O module incoming power supply meets the ICSS
following requirements:
• 85 to 125 VAC
• 4.5 amps
• 47 to 63 Hz
c. Verify that the high (240) voltage AC I/O module incoming power supply meets the ICSS
following requirements:
d. Verify that the high voltage DC I/O module incoming power supply meets the ICSS
following requirements:
• 88 to 140 VDC
• 2.5 amps
e. Verify that the low voltage DC I/O module incoming power supply meets the following ICSS
requirements:
• 20 to 30 VDC
• 10 amps
1) Observe the condition of the BN3500 modules and record the status ICSS
indicators following the tables below;
c. Go to Start > All Programs > 3500 Software > Rack Configuration Software. ICSS
d. Connect the computer to the rack via interface module - Transient Data Interface ICSS
(TDI) either by using;
or
• Straight RJ45 ethernet cable between ethernet port of the computer and
ethernet port in the back of the Rack Interface Module.
e. Next click on the ‘Connect’ button near the top of the screen (the button with the blue ICSS
and orange horizontal arrows).
f. Set the communication parameters; baud rate at default 38400, appropriate comm. ICSS
port, IP address, as applicable. Click 'Browse'.
g. When the equipment of interest appears on the 'Available Racks' window, highlight ICSS
the equipment by clicking on it, then stop browsing, click 'Connect' to access the BN
3500 rack. See picture below -
h. Click 'OK' when 'Connection established' window appears as shown below. ICSS
i. After connection is established, click the ‘Upload From Rack’ button (shown ICSS
below). This will pull the configuration from the 3500 rack and display it within
the software screen so it can be viewed and/or changed.
k. Verify the uploaded rack configuration by comparing the physical modules with the ICSS
logical modules uploaded.
The uploaded rack should appear like the rack being checked - same number/types
of modules as well as module spaces not used. Example below is East Siemens BN
rack 1 with 15 slot.
Verify that computer date and time matches those for the rack. If there is a variance,
update the rack with correct time.
Go to Utilities>software switches
Use the dropdown button, select the slot and view module and channel switches for
each slot
o. Verify status of modules in each slot of BN3500 configuration rack to confirm NO ICSS
Alarm.
On the configuration rack above,Right click each of the slot and select verification to
confirm status of each slot
3. Observe the status of all the channels on each slot and record findings
1) Transient Data Interface - TDI [3500/22M] ICSS
p. Record and report any problem or discrepancy and generate a work order as ICSS
necessary.
d. If force point(s) exist, following the steps 1 to 3, match each with an approved ICSS
bypass certificate.
End of Task
10.0 6M ICS Complete Inspection & Diagnostics: GE Fanuc 90-30 PLC System
Complete the following steps to perform 6M ICS Complete Inspection & Diagnostics of the GE Fanuc 90-30
PLC to check the complete system for active alarms and faults.
10.1Hardware Diagnostics
a. Observe the Status indicators on the GE Fanuc controller for normal indications as ICSS
follows:
Check and confirm the status of battery. Replace if it shows sign of deterioration or
BATT LED is illuminated.
c. Observe the Status indicators on the GENIUS Analog Input block for normal ICSS
indications:
10.2Software Diagnostics
a. Connect the serial communication port on the CPU Module with the serial ICSS
communication (COM1) port of the Maintenance Laptop.
d. Press Status (F3) to view the PLC control and status. ICSS
g. Press F9 to clear the PLC fault table and avoid information overflows. ICSS
To clear the PLC fault table, the programmer must be in the Online mode.
l. Select Online, use the tab key cursor position, then press Enter. ICSS
m. To display the I/O fault table, from the PLC CONTROL AND STATUS screen Press ICSS
I/O Fault (F4).
n. Record the information that is displayed on the screen, and clear the fault table ICSS
to avoid information overflows.
Note: The Zoom (F10) enables you to obtain additional information pertaining
to each fault listed by placing the cursor on a particular fault and pressing
Zoom (F10).
o. To exit the Logicmaster 90-30 software. Press ESC and at the prompt, select ICSS
Y.
p. Check for forces on the I/Os by visually inspecting for blinking LED on the I/O ICSS
block.
End of Task
b. Confirm LED Indicators on the front of the controller. These provide indication of both ICSS
health condition.
c. The table below gives interpretation of the status of the controllerbased the indicator states. ICSS
e. Confirm LED Indicators on the front of the modules - Analogue Input modules ICSS
If any fault condition is observed, consult the appropriate OEM manual to clear fault and report
in a corrective work order.
f. Confirm LED Indicators on the front of the modules - Digital Input/Output modules ICSS
If any fault condition is observed, consult the appropriate OEM manual to clear fault
and report in a corrective work order.
If any fault condition is observed, consult the appropriate OEM manual to clear fault
and report in a corrective work order.
End of Task
12.1 Activity will be done when there is available competency and software access tools to the PLC.
13.0 6M Inspection & Diagnostics: Mitsubishi PLC System
13.1 Activity will be done when there is available competency and software access tools to the PLC.
14.0 12M ICSR Management Communication
14.1 Open annual management communication native file [word document] for the ICSS
previous year:
14.2 “Save as” annual ICSR management communication in the folder for the year in view ICSS
i.e. current year.
14.3 Review previous and current Industrial trends and ICSR Management communication to the ICSS
Work force.
14.4 Logon to ICSR share team site, review and get update on latest cybersecurity ICSS
happenings worthy of sharing.
Cybersecurity:
https://ishareteam1.na.xom.com/sites/EMPC0741/SitePages/CyberSecurity.aspx
Vulnerability Notifications:
https://ishareteam1.na.xom.com/sites/EMPC0741/Vulnerability%20Notifications/For
ms/AllItems.aspx
Announcements:
https://ishareteam1.na.xom.com/sites/EMPC0741/Lists/ICSR%20Announcements/All
Items.aspx
• PCS Supervisor ·
• Instrument and Controls Supt.
• In-Country ICSR Lead
14.6 Update the word document ICSR annual management communication one pager for ICSS
review by the following: ·
• PCS Supervisor ·
• Instrument and Controls Supt. ·
• In-Country ICSR Lead
• UN MICE Manager
14.8 Work with the Secretary to General Manager UN JV Operations and Publish as Inter ICSS
Office correspondence
14.9 Obtain meeting attendance register from location/work center Superintendents and ICSS
Offshore Installation Managers (OIMs) to cover at least two rotations of workers
where the ICSR annual management communication was discussed
End of Task
b. Blank form
c. Insert the tracking number for the network you require certification for and click ICSS
“search” on the top left-hand corner.
Note: Networks that had gone through EMIT Certification process and had been
certified are already in EMIT’s annual re-certification program and are triggered
automatically every year.
EMIT Network Certification team will send an email to JVO management (DOAG 7)
for approval of re-certification. When approval is obtained, network will be
re-certified.
b. Look out for a notification email from EMIT when network is re-certified.
c. Copy and save re-certification information from the portal in assigned folder in PCSG
shared LAN drive.
End of Task
16.1 Ensure the annual workorder has triggered in IPES for the task. ICSS
16.3 Change the review date on the top left-hand corner of the document to current date. ICSS
16.5 Confirm from the “Advanced System Security Evaluation Tool” (ASSET) web-based ICSS
application that there are/are no new risk assessments with initial risk level of
“medium”.
16.6 If new risk assessments with initial medium risks are available, add those risk ICSS
assessments to the list of critical systems
16.7 Look through the List of Critical Personnel documented by locations and verify that ICSS
there was no personnel movement changes since the last update period.
16.8 Look through the List of Critical Backup Personnel documented by locations and ICSS
verify that there was no personnel movement changes since the last update period.
16.9 Look through the List of Critical Vendors and verify that there was no 3rd Party ICSS
personnel changes since the last update period. The verifications include:
• Using phone calls with the documented phone numbers to contact personnel to
confirm continued support and availability.
• Emailing the vendor’s personnel using documented email addresses to verify
correctness.
• Adding any new vendors supporting any critical systems to the list, including
their contact information.
If there are changes in personnel and their contact information, update accordingly.
16.10 Look through the List of Critical Documentation to confirm that: ICSS
• For each system, necessary documentation are available for references and
systems’ support.
• Links to the storage directory are correct and valid
• All critical systems documentation are listed in the Critical Lists Documentation.
16.11 Save the document (in PDF) with the current date in shared LAN folder designated ICSS
for this purpose.
End of Task
17.0 24M ICS BCP/Disaster Recovery and Cybersecurity Emergency Response Plan
Test
b. Set up a team for the table-top exercise including PCSG personnel, EMIT (if required), field ICSS
operations, electrical and instrumentation/DCS techs., OIMs and Mtce Supervisors, and
other relevant personnel.
c. Obtain approval and inform participants of dates, location and timing for the exercise. ICSS
a. Title: ICSS
ICS Disaster Recovery and cyber Security Emergency Response Plan
Event Log
Randomly Accessed Trojan [RAT] infiltrated through the L4 network and attacked the Safety
Instrumented System [SIS] resulting in extended production outage.
g. Evaluation: ICSS
Attach equipment list for affected location(s). List the process control equipment that was
damaged or affected including an initial assessment of availability of replacement parts and
software backups (if applicable). Example below.
Example:
• Replacement Source
h. List the process control functions that are adversely affected or unavailable to ICSS
manufacturing, the equipment needed to restore the function and the approximate
date when manufacturing will be capable of using the function
Example:
1. Function
2. Equipment Needed
• Organization
• Date
• Notes
• Equipment
• Function
• Notes
k. Plan: ICSS
List the steps required to recover all necessary process control functions. Include equipment
and backup media which are needed, the source of the equipment, timing and man-power
requirements.
Example:
§ Steps
§ Responsibility
§ Completion Targets
l. Follow-up: ICSS
After recovery has been completed, list any follow-up items and describe any
learnings or process improvements.
m. Recovery Objective: ICSS
p. Approvals: ICSS
◦ Sign:
◦ Date:
◦ Sign:
◦ Date:
◦ Sign:
◦ Date:
◦ Sign:
◦ Date:
r. Document the test and reviews/approval in PCSG shared LAN folder named, “year” BCP_DRP ICSS
TEST DOCUMENTS.
End of Task
18.1Visual Inspection
a. Ensure that the ICS components are tagged with respective IPES tags, tags are ICSS
securely attached, legible, and correct.
h. Ensure that there are no unjustifiable jumper[s] / hardware override[s] installed. ICSS
b. Check for loss of redundancy, where redundant power supply is provided. ICSS
c. Verify the integrity of (Memory Back-up / Main) battery, where applicable. ICSS
18.3Inspect Wiring
a. Check for loose wire connections. ICSS
18.4Verify Grounding
a. Verify that ground (earth), bonding, and other connections are secure and corrosion ICSS
free.
Use the lowest ohms setting. Touch the multimeter's Black lead to a grounded metal
surface of the Panel and touch the Red lead to each wire of the circuit.
A meter reading of infinity, O.L. (Open Loop) indicates an open circuit with no path to
ground; that indicates a good ground.
c. Check the functionality of the ground fault detector where available. ICSS
• Ladder logic
• Flowcharts
• Control schematics
• Instrument Loop Drawing
• System Architecture Drawing
• Electrical Wiring Drawing
b. Ensure that the documents are the latest revision with all modifications captured. ICSS
c. Ensure that security procedures are sufficient to prevent unauthorized use. ICSS
End of Task
CAUTION: Do not use the power button to perform forced or hard shutdown of the
Workstation to prevent damage of the hardware or corrupt the software.
b. Inspect the exterior of the system for any signs of physical damage and ICSS
wipe the exterior of the enclosure with a soft cloth.
c. Clean Workstation System Unit, Keyboard, Mouse, Monitor, Laptop. ICSS
Use portable electronics vacuum cleaners or de-ionized air blowers, paint brush or
toothbrush to clean any dust buildup inside and outside the casing, especially on the
input/output connection areas, is recommended.
d. Inspect the keyboard to ensure that no keys are sticking. If keys are sticky, it ICSS
may be necessary to replace the keyboard.
b. Using a vacuum cleaner, dust all the internal components of your computer with ICSS
short bursts of air. Soft paint brush or toothbrush can also be used for the task.
Gently dust the surface of the motherboard, memory, processor, fans, expansion
cards, fan filters and all ports. If the fans are hard to reach or extremely dirty, feel
free to remove them from the case for easier cleaning. If using the vacuum cleaner
try to stay at least a few inches away from the components.
c. Ensure that computer internal hardware components (e.g., RAM, plugs, etc.) are ICSS
evenly and firmly seated in their slots. Pay attention to component orientation.
d. Close back the computer cover, restore inputs/outputs and power ICSS
connections.
b. Double-check that all power cables are properly connected to the system, the ICSS
monitor and peripherals, and their power sources.
If “system time invalid” error come up while booting up it means the onboard CMOS
battery needs to be changed.
Make replacement and power up the work and confirm normal operation is restored.
d. During Boot Up, press “F2” [for Dell Workstation] to go to the BIOS. ICSS
For workstation other than Dell, press the associated key on the keyboard to enter
BIOS e.g. “Delete” on Option Industrial Computer [Proplus 2000SB], etc.
e. Using the arrow keys scroll to EXIT on the menu and Navigate to DIAGNOSTIC ICSS
UTILITY.
f. Click enter on the Diagnostic Utility for it to open and run a PC-Diagnostic test on all ICSS
components of the computer.
g. Do not touch the computer for a few minutes till all the Icons are highlighted. The ICSS
green indicator signifies that the system component is in good condition while the red
signifies which system component is in bad condition.
End of Task
1) ICSS
Power on laptop/workstation and log on.
! IMPORTANT: There may be need to take “As Found” image and applications
backups before beginning software maintenance for restoration
purpose just in case necessary files are deleted by mistake.
3) Manually remove all unnecessary files and folders from the computer. ICSS
Click Search | All Files and Folders and type: *.jpeg, *.jpg, *.mpeg, *.mov,
*.exe, *.dat, *.bat, *.wmv, *.wma, *.mp3, *.mp4, *.png, *.bmp etc.
1) ICSS
Click on Start | Computer | Right Click on C Drive | Properties.
2) Click on General | Disk Cleanup and allow it to calculate amount of space to be free. ICSS
3) Select each of the check boxes in the “Files to delete” list in the Disk Cleanup dialog ICSS
box and click OK.
· If you have more than one hard disk drive, repeat this process for each hard
drive.
· Click Reboot later when prompted to reboot, till all disks are
completed then manually reboot.
4) Untick Automatically manage paging file size for all drives, Select the Drive letter, ICSS
Select Custom size, and input both Initial and Maximum value size to be the same as
Recommended.
Then Click Set, Then Reboot the computer when prompted.
1) Click Start | Right-Click Computer | Click Properties | Click Advance Tab | Click on ICSS
Settings under User profiles.
Delete any Account Unknown user profiles. Click OK all the way to exit.
2) Click Start | Settings | Control Panel | Administrative Tools | Event Viewer. ICSS
3) Select Application, then on the menu, click Action | Save Log File As. ICSS
4) In the “Save Application As” dialog box, name the file using the format ICSS
Sitename_Computer Name_Log File type and click Save.
Save as file types include - .evt. .txt, .csv. Optionally, Action - Export list can also
be used to save as .txt. In total, about three file types (.evt, .txt, .csv) should be
saved for each event viewer group item (Application, Security, etc).
5) Repeat this action for all items under Event Viewer. Items of importance are ICSS
System, Security and Application.
6) Review the event logs for warnings and possible failure and recurring ICSS
problems.
2) Select Drive C | Click on Defragment disk, wait for the process to be completed, then ICSS
Click Close, when Prompted.
4) Select both Check disk options and Click Start, then Click on Schedule disk check. ICSS
5) Reboot the Workstation/Laptop and wait for the CHECK DISK process to complete. ICSS
3) Manually remove all unnecessary files and folders from the computer. ICSS
· Click on the search bar and type (case sensitive): *.jpeg OR *.jpg OR *.mpeg
OR *.mov OR *.exe OR *.dat OR *.bat OR *.wmv, *.wma OR *.mp3 OR
*.mp4 OR *.png OR *.bmp etc.
2) Click on General | Disk Cleanup and allow it to calculate amount of space to be free. ICSS
3) Select each of the check boxes in the “Files to delete” list in the Disk Cleanup dialog ICSS
box and click OK.
· If you have more than one hard disk drive, repeat this process for each hard
drive.
· Click Reboot later when prompted to reboot, till all disks are
completed then manually reboot.
2) Click on Advance System Settings to open the System Properties dialogue box. ICSS
4) Select Advance Tab and Click Change under Virtual Memory . ICSS
5) Untick Automatically manage paging file size for all drives, Select the Drive letter, ICSS
Select Custom size, and input both Initial and Maximum value size to be the same as
Recommended.
1) Click Start | Right-Click Computer | Click Properties | Click Advance system settings | ICSS
Click Advance Tab | Click on Settings under User profiles.
2) Delete any Account Unknown user profiles. Click OK all the way to exit. ICSS
2) Click on Defragment disk if the fragmented percentage is greater than 0%. Wait for the ICSS
process to be completed, then Click Close.
1) Type compmgmt.msc on the search tab as shown below and Click on the ICSS
result program as shown.
2) Select Application, then on the menu, click Action | Save Log File As. ICSS
3) In the “Save Application As” dialog box, name the file using the format ICSS
Sitename_Computer Name_Log File type and click Save.
Optionally, Action - Export list can also be used to save as .txt. In total, about
three file types (.evt, .txt, .csv) should be saved for each event viewer group
item (Application, Security, etc).
4) Repeat this action for all items under Event Viewer. Items of importance are ICSS
System, Security and Application.
5) Review the event logs for warnings and possible failure and recurring ICSS
problems.
2) Select both Check disk options and Click Start, then Click on Schedule disk check. ICSS
3) Reboot the Workstation/Laptop and wait for the CHECK DISK process to complete. ICSS
End of Task
21.0 36M Workstations & Laptops Image Backups Using Acronis 11.7
Reference: All work must be conducted in accordance with the Production ICSS
Best Practice (PBP) Work Management System Manual, latest
revision.
! IMPORTANT: Only use Acronis to back up computers that cannot be backed up using
Apricorn.
21.1 Sign out On-site Backup Hard Disk from Maintenance Supervisor/or ICSS
designate's office.
IF... THEN...
Date and Time is not correct Set correct date and time ICSS
IF... THEN...
21.4 Connect the Site Hard Disk to an Available USB port on the Workstation/Laptop ICSS
21.5 Double click on the Acronis Backup 11.7 shortcut icon on the Desktop or Click on Start/All ICSS
Programs, Select Acronis Folder. Then Click on Acronis Backup 11.7 to launch the backup
application.
21.6 Click on Manage this machine icon to connect the console to Acronis Backup Agent ICSS
installed on the PC.
Acronis Back up now – will display the screen shown below. ICSS
21.8 Click on Items to back up… to launch the Data to backup dialogue. ICSS
21.9 Select Disks/Volumes, then Click on the Name of the computer ICSS
21.11 Select the Name tab, enter the name of the backup image, using the below naming ICSS
convention. Then Click Ok.
21.12 Set Backup type to Full and Parameters to Validate a backup as soon as it is ICSS
created. Then Click OK to begin the Backup process.
21.13 Confirm the Execution state shows Running with a percentage value as shown ICSS
below;
21.14 View the completion status dialogue box to ensure there is no error. Then Click on ICSS
Close.
21.15 Go to "Recent activities" to verify Validation of the image backed up as shown ICSS
below.
21.16 Delete the .xml file (from the location where the backup is saved). ICSS
21.17 Disconnect Site Backup Hard Disk Safely from the USB port on the ICSS
Workstation/Laptop
End of Task
22.0 36M Workstations & Laptops Image Backups Using Apricon EZ gig II
22.1 Sign out On-site Backup Hard Disk from Maintenance Supervisor/or ICSS
designate's office.
IF... THEN...
Date and Time is not correct Set correct date and time ICSS
IF... THEN...
22.4 Connect the Site Hard Disk to an Available USB port on the Workstation/Laptop ICSS
22.5 Run Apricorn backup software by clicking on the START >> All Programs >> ICSS
Apricorn >> Apricorn EZ Gig II. As shown below (Note steps 1, 2, 3 );
22.8 Tick the Disk 1 check box (to select all internal Hard disk partitions). ICSS
N/B: The naming of the partition will help to identify the correct disk number to select
22.9 Navigate to where you want to save the backup image file. (Note steps 1, 2, 3, 4) ICSS
22.10 Select the Naming tab, enter the name of the backup image, using the below naming ICSS
convention. Then Click Ok.
22.11 Click on Next ("Use default options" radio button checked). ICSS
22.13 View the summary of the list of operations to be carried out, then Click Proceed to ICSS
begin the backup process
22.14 View the completion status dialogue box to ensure there is no error. Then Click on ICSS
Ok.
22.15 Click "Explore and Validate Backup" Archives to validate backup image. ICSS
22.16 Click Validate Backup Archive on the Manage Backup Archives screen. ICSS
22.17 Navigate to the location of the image, then Select the just backed up image and click ICSS
Next.
22.19 View the completion status dialogue box to ensure there is validation no error. Then ICSS
Click on Ok.
22.20 Disconnect Site Backup Hard Disk Safely from the USB port on the ICSS
Workstation/Laptop
End of Task
23.0 36M Verification & Backup of Siemens Simatic S7-400 PLC System
c. Follow the path shown below to access the Simatic manager; ICSS
d. When the 'SIMATIC Manager' screen comes up, click Cancel on the 'PCS 7
Wizard...' screen that displayes.
e. In the SIMATIC Manager environment, select and click on the following menu ICSS
command:
f. On the "Archiving" dialog box that is displayed, switch to the 'Multiprojects' tab. ICSS
g. Select the project for archiving - the first option, QGFE ICSS
D:\Simantic\Projects\Qgfe_1\Qgfe, should be selected.
2) For File name, enter the name of the file where the data will be saved. ICSS
End of Task
24.0 36M Verification & Backup of Rockwell Automation ControlLogix PLC System
c. Launch RSLinx classic from start>All programs > Rockwell Software>RSLinx ICSS
Classic
f. Locate the previously backed up program of the controller with rungs comments. ICSS
Click on File> open from the Menu bar.
g. Select the appropriate RSLogix 5000 project for the controller and click on “Open” ICSS
button.
If the controller goes online without showing “the open project has offline changes
that aren’t in the controller” message, the program is verified.
If the controller shows “the open project has offline changes that aren’t in the
controller” message, an upload must be performed.
Click on Upload (name the file to be uploaded different from the offline file if you do
not want to replace the offline file) and wait to the uploading process to be completed
c. Name the file with the name of the original project name and save it in a folder that ICSS
can be name in this format
Sitename_PLCMaker_PLCservice_ASFound_dd/mm/yyyy. Copy this folder into the
Application folder (Application Backup\RAXXX\20xx\As_Found) of the site hard
drive.
For example:
TreatingPlant_AllenBradley_WaterTreatmentPLC_ASFound_dd/mm/yyyy
e. A “tag value may have change since last save” message pops up. Click on YES. ICSS
f. Take the Laptop offline by clicking on Communications>Go offline from the menu ICSS
bar.
h. Copy out the verified .ACD PLC project file and save in authorized external storage ICSS
media following the backup process.
End of Task
25.0 36M Verification & Backup of Allen Bradley SLC 5/03 PLC System
The offline project is verified as current if communication is established with PLC ICSS
without any display of mismatch message between the offline and the online project.
! IMPORTANT: Do not replace the backup file with upload file. Save file following file
naming convention to specify date.
c. On the 'Save in' bar, browse to the storage file location. Click on save ICSS
e. Name the file with the name of the original project name and save it in a folder that ICSS
can be named in this format
Sitename_PLCMaker_PLCservice_ASFound_dd/mm/yyyy.
f. Take the programmer offline by clicking on Comms > Go offline from the menu bar. ICSS
End of Task
b. To verify the program: From Logicmaster 90 Programmer Package, press Utility ICSS
(F9).
d. Scroll to ALL LOGIC BLOCKS and press tab to select Y, then press ICSS
Enter to start the verify function.
If the information being compared is the same, the screen prompts: "Verify
complete, no miscompares detected" and the program logic equality state
is set to EQUAL.
If the information being compared is not the same, the miscompares are
listed and the program logic equality state is set to NOT EQUAL.
e. Repeat the steps for verification of All Data Blocks and Configuration. ICSS
c. Press Backup (F4) to create a backup copy of the current selected ICSS
folder.
The backup folder is located in a subdirectory under the program folder. The
Backup Destination field allows you to specify the location for the backup
copy. A message of backup completion is shown.
d. Copy the backup and save following the UN ICS backups management framework. ICSS
End of Task
c. The following message appears asking if the rack configuration needs ICSS
to be downloaded again. Click ‘NO’ since the download has already
been done.
d. The following message allows one to select which of the 4 information files ICSS
should be saved. Leave all 4 checked for this exercise.
h. Each time the ‘Rack Info’ button is selected, the 4 information files are ICSS
written to this location for the rack that is connected. These files can
then be saved on a specific location on the Hard Disk Drives.
Navigate to the Application folder on the site hard drive, give the file an appropriate
name (Sitename_EQUIPMENTSERVICE_DD/MM/YYYY) and click on Save.
j. Terminate communication with the rack by clicking on the Disconnect command in ICSS
the File menu.
End of Task
28.1 Log out the operator and log on to the application software with authorized ICSS
password.
28.2 Exit the running iFIX software. In the Proficy iFIX Startup window. Use ALT+Tab till ICSS
the icon below appear. Select Options →Shutdown iFIX.
28.3 Log of operator from the operating system and log on with authorized password ICSS
28.4 Launch (double click) Windows XP icon on the HMI (Windows XP lunches on ICSS
VMware)
28.5 Authorization access window opens. Enter the appropriate username and password ICSS
to progress.
28.6 On the (VM ware) Windows XP screen, double click Workbench to launch it. ICSS
28.7 Click Connect on the selected option, on the pop-up window. ICSS
28.8 Select (on the top bar) Tools > Administrative Tools > Backup/Restore Project > ICSS
Backup Project
28.11 When the backup is complete, click Close on the Project Backup form. ICSS
Note: The Workbench checks for available disk space before performing backups
and restores. A warning message is displayed if there is a limited amount of space
available. You can choose to ignore this warning and continue with operation, if
desired.
• Attaches to the database and creates a backup of the project database. This file
is named xxx.bu (where xxx is the project name and the file is created in the
project's directory),
• The Workbench automatically compresses the project files into a single .zip file.
This .zip file is date and time stamped in the title. The naming convention for this
file is MPNU_<Projectname>_YYYY_MM_DD_HH_MM_SS.zip, indicating year
(YYYY), month (MM), day (DD), hour (HH), minute (MM), second (SS), refering
to the time and date the backup was done,
• As the backup procedure progresses, the status bar at the bottom of the form
shows the current step,
• Following a successful backup, a message indicating same is displayed in the
status bar and logged to the event viewer.
28.12 Move the backup to a safe location following UN Backup Process ICSS
(UN-ICS-PR-06-04). It is necessary to copy only the zip file -
MPNU_<Projectname>_YYYY_MM_DD_HH_MM_SS.zip
End of Task
29.1 Activity will be done when there is available competency and software access tools to the PLC.
30.0 36M Verification & Backup of HIMA PLC System
30.1 Activity will be done when there is available competency and software access tools to the PLC.
31.0 36M Verification & Backup of Siprotec PLC System
31.1 Sign off Siemens laptop from Maintenance Supervisor/or designate's office. ICSS
31.2 Log on to the laptop with authorized access name and password. ICSS
31.3 Create a folder in the general material folder, into which the configuration files will be ICSS
saved, using the approved naming convention. See sample below.
As shown in the second picture, the folders - QGFE_SIP\GT1\LHS, RHS (for left and ICSS
right hand side PLCs when facing the PLC cabinet), is created inside the folder
QGFE_SIPROTEC_BACKUP_ASFOUND_16NOV2019 in the path
D:\General_Materials\PROJECT_Backup\SIPROTEC
31.4 Connect laptop to PLC using RS232 male to female cable connector. ICSS
Navigate to the software from the start button as shown below and then click on it.
31.6 On the DIGSI Manager page that opens, Click File > New ICSS
31.7 On the window that pops up, populate the name (e.g GT1 for East SGT). For storage ICSS
location, browse to the appropriate folder created in step 31.3. Click Ok.
31.8 Select and click Device -> DIGSI (Plug & Play). ICSS
31.9 Select type - SIPROTEC 4 and click OK on the next screen. ICSS
31.10 Setup the parameters; Connection type – Direct, PC Interface – COM 1, Frame – 8 ICSS
E (ven)1 (as shown below) and click OK;
31.12 When connection is established, confirm 'Online' indication on the bottom right hand ICSS
side of the screen.
31.13 Select and click on File > Save to transfer parameters to PC. ICSS
31.15 When transfer of setting is completed, make soft disconnection (select and click ICSS
Device > Switch Off-line) then disconnect communication cable.
31.16 Confirm the parameters and setings are save to the PC. ICSS
31.17 Copy out to external hard drive and follow the ICS backup procedure to backup the ICSS
most current SIPROTEC PLC configuration parameters.
End of Task
32.1 Login to the programmer with an authorized username and password. ICSS
32.2 Connect the serial port COM 1 of the programmer to the serial port of the Moog ICSS
controller using the a crossed serial cable
32.3 Launch MOOG Windrive from Start>All programs > Moog WinDrive>WinDrive ICSS
32.4 Select the communication port number of your programmer (usually comm 1) Under ICSS
the "Port" section of the dialog box.
32.5 Select "RS-232" Under the “Rec. Standard” section of the dialog box and click Ok.
32.6 Verify active communication between the Moog controller and the programmer by ICSS
observing the “configure” and “online” message at the bottom status bar of the Moog
main window as shown above.
32.7 Observe the fault status of the Moog controller by looking at the fault message ICSS
located on the upper status bar of the Moog Windrive main window as shown below.
32.8 Upload the Moog controller configuration by clicking on File>Configuration Upload. ICSS
Most of the field values contained in this dialog will appear as comments in the log
file generated.
32.9 Type in a suitable but brief file name that reflects the location and service of the ICSS
Moog controller.
! IMPORTANT: • The file name must not be more than 8 characters long.
• The .Log extension must be attached to the filename and it does
not constitute part of the 8 characters.
32.10 Type in the company name (MPN) and click ok. All other fields are automatically ICSS
populated.
32.11 Wait for a while for the configuration parameters to appear on the left bottom pane of ICSS
the Moog main window.
32.12 Connect the site backup hard drive to the programmer and click on "File>save" from ICSS
File menu.
32.13 Type in a suitable but brief file name that reflects the location and service of the ICSS
Moog controller.
32.15 Repeat step 33.14 but replace the .mdl extension with .log extension. ICSS
End of Task
33.1Verification of project
a. Connect serial cable where applicable to connect to the Omni Flow computers to the ICSS
configuration laptop.
b. Power up the configuration laptop and log on using your logon credentials or the Fire ICSS
Call (only where individual logon cannot be used).
c. Launch Omnicom (Windows version) by clicking the icon located on the desktop. ICSS
d. Click File|Open, and then browse to where the Omni configuration files are saved on ICSS
the laptop.
Note: It is assumed that the site and Omni has already been set up as shown
below. If the site and Omni have not been set up, raise a notification for setup
f. Select the Omni that matches the one with the opened configuration in the step ICSS
above, and then click Connect.
The following screen displays, indicating that communication has been established
with the Omni
b. Under General Setup|System Date and System Time tabs, verify the Omni time ICSS
and date.
If not, enter the correct date and time, respectively. Verify the Omni Identification
information under the Setup tab
c. Click File|Save or click the diskette icon to save the configuration, overriding the ICSS
existing one on the laptop
! IMPORTANT: The laptop date and time MUST be correct prior to saving so that the
saved file will reflect the correct date and time stamp.
If the laptop date and time are incorrect, set them up correctly including
the correct time zone.
e. Repeat the above process to back up the configuration of the other Omni flow ICSS
computers
h. Copy the folder with the configuration files from the laptop to the site portable PCS ICSS
backups hard disk drive, saving it to the following location:
End of Task
34.1 Login to the programming tool with an authorized username and password. ICSS
34.2 Using corresponding access cable, make physical connection between the ICSS
programming tool (laptop, etc) and Jiskoot computer on the port shown -
Jiskoot path
34.6 Enter the connection description - name of file, choose telephone service (see ICSS
below). Click OK.
34.7 Enter further details for the connection. Choose the communication port as shown ICSS
below or any other available as applicable. Click OK.
34.8 Enter the "COM1 Properties" (or any other port choosen) as shown below. (Click ICSS
Restore Defaults for COM1)
34.9 After clicking "OK", the connection to the Jiskoot computer should be established. ICSS
Status is shown on the down left corner of the screen.
34.10 Confirm the screen accept character entry - type $, for e.g. ICSS
34.11 Commence Uploading Configuration file. Type BBSAVE and hit ENTER. ICSS
34.14 In the Receive File pop up window, browse the location the configuration is to be ICSS
received at and choose the protocol - Kermit. (See below)
34.15 When file transfer is completed, disconnect communication and restore normal ICSS
working condition.
34.16 Store backups using the process outlined in the UN ICSR backup process. ICSS
End of Task
35.1 Log off “Operator” account and log on with a user right that has Windows ICSS
desktop access
35.2 Create a folder in C: drive of the workstation. ICSS
35.4 ICSS
In the main window of InTouch, the name and path of the program would be
displayed as shown below, note it down.
35.5 Right click on the project and click on Windows Maker. This will open Intouch ICSS
Windows Maker.
35.6 Close the Intouch "Windows to Open…” dialog box. Ensure that all the ICSS
other opened windows are closed.
35.7 ICSS
Select File> Export Window…
An “Export to directory….” Dialog box pops up. Navigate to the folder that was
created in step b and click OK.
35.8 A “Windows to Export…” dialog box pops up. Select all the windows for backup ICSS
and click OK.
35.10 Navigate to the location of the folder were Wonderware windows were exported to. ICSS
Copy this folder into the Application Folder (Application
Backup\RAXXX\20XX\As_Found) in the site hard drive.
35.11 Also navigate to the path where the project is located and copy project folder into the ICSS
Application Folder (Application Backup/20XX/As_Found) in the site hard drive.
35.13 Store backups using the process outlined in the UN ICSR backup process. ICSS
35.14 Log off and log on as “Operator” for operations use. ICSS
End of Task
36.1 Activity is managed through Verification & Backup of Siemens Simatic PCS7-400 PLC System
procedure. The backup method used also backs up WinCC HMI application.
37.0 36M Backup of iFIX HMI Application
37.1 Log in to the operator workstation with an authorized username and password. ICSS
37.2 Confirm the date and time on the HMI to be correct ICSS
37.3 Stop the iFIX software, in the Proficy iFIX Startup window. Use ALT+Tab till the icon ICSS
below appear. Select Options →Shutdown iFIX.
37.4 From the Windows start button, follow the path; ICSS
All Programs > Proficy HMI SCADA - iFIX 5.5 > Tools > Backup & Restore
Wizard
Backup Path
37.5 When Backup & Restore Wizard is clicked, the following screen will open - ICSS
37.6 Click on FullBackup (1), then click on the Project Backup Wizard icon (2) ICSS
37.8 Browse to the desired backup path (file may be save to D: and then copied out to ICSS
external hard drive) and click Finish to complete procedure.
37.9 Follow the ICS backup procedure to save the HMI backup. ICSS
37.10 Confirm the date and time of the backed up file to be current and file extension to be ICSS
.fbk
37.11 Log out the authorized access credentials and log on operator and confirm normal ICSS
operation HMI is in place.
End of Task
BENTLY Nevada system 1 HMI is a vibration visualization workstation used for analysis, monitoring and
recording events related to axial and radial vibrations of equipment.
38.1 On the vibration monitoring workstation, select and click on Enterprise > Exit. (to ICSS
exit the running vibration monitoring program)
38.2 Login to the workstation with an authorized username and password. ICSS
38.3 Connect the On-site backup hard drive to the workstation. ICSS
38.5 Connect to the SQL Server that contains the database you want to backup ICSS
The “SQL Server dialog” box pops up. If the current workstation is an SQL Server, its
name will appear in the field.
38.6 Click the drop down menu, select the database of interest then click OK ICSS
You may also type in a SQL Server name that is accessible from this workstation.
38.7 Expand the Server hierarchy to view the databases - expand Enterprise then select ICSS
QGFE...
38.8 Select the configuration database (1) that needs to be backed up. Then, select and ICSS
click Database (2) ->backup (3) from the main menu bar.
38.9 Enter the Name and a brief Description for the backup in the Backup Name and ICSS
Backup Description fields respectively for the dialog box below.
38.10 Click on Next. The Destination page of the wizard will appear. ICSS
38.11 Enter the file path (Application folder in the site hard drive) for the *.dat backup file ICSS
you will create.
38.12 Click on Next. The Backup Options page of the wizard will appear. ICSS
a. Select "Overwrite Existing Media" if you don't care about any previous backups ICSS
and you want to reduce the file size of the *.dat backup file you are creating.
b. Select "Append to Existing Media" if you want to keep a copy of past backups ICSS
within the *.dat file so you can go back and restore any one of them in the
future.
38.13 Click on Next. The Summary page of the wizard will appear. ICSS
38.14 Verify that all the information you entered is correct. ICSS
38.17 Repeat steps 38.8 to 38.16 for the next database ICSS
38.18 After the backup activity, restore the HMI to its normal use for vibration monitoring. ICSS
End of Task
39.0 36M Backup of Rockwell Automation FactoryTalk (FT) View Site Edition (SE)
HMI Application
Perform the following steps to back up and archive FactoryTalk (FT) View Site Edition (SE) HMI Project.
39.1 To backup the HMI Project folder, click Start | All Programs | Rockwell Software | ICSS
FactoryTalk View | Tools | HMI Server Backup and Restore.
39.3 Under Source HMI Server, browse to the HMI project folder to backup ICSS
and open the project .sed file.
39.4 Under destination backup path, browse to where the project backup is to be saved ICSS
(e.g. external backup Hard Disk Drive), then click OK.
! IMPORTANT: Ensure that the destination folder does not have the project (with the
same name) already stored.
39.5 Click Start Backup and wait for the backup to complete. ICSS
39.6 Acknowledge the backup completion message and exit all opened ICSS
applications during the backup process.
39.7 To generate HMI project .apa archive file, click Start | All Programs | Rockwell ICSS
Software | FactoryTalk View | Tools | Application Manager.
39.10 Browse and select where to store the backup archive and click Finish. ICSS
39.11 To backup the .cli client runtime file for the HMI Project, copy it from the Client folder ICSS
(e.g. C:\Documents and Settings\All Users\Documents\RSView Enterprise\SE\Client)
to the backup storage location.
! IMPORTANT: Store the HMI Project backup folder, the .apa archive file and the .cli
client runtime file following the PCS backups management framework.
End of Task
40.1 Activity will be done when there is available competency and software access tools to the PLC.
41.0 36M Backup of Allen Bradley PanelView Plus Operator Interface Application
1. Use of USB flash drive to transfer the running .mer runtime file from PVP.
2. Use of FactoryTalk (FT) View Studio Machine Edition (ME) to compare and/or upload the .mer runtime
file in PVP.
Perform the following steps to backup PanelView Plus Operator Interface Terminal Runtime Project File.
41.1 Plug authorized USB flash drive to the USB port on the PanelView Plus (PVP). ICSS
41.5 Unplug the USB flash drive and return the PVP to service by running the application. ICSS
41.6 Using an authorized workstation, copy out the .mer PVP runtime project file from the ICSS
USB flash drive to authorized external storage media following the backup process.
End of Task
42.1 Activity is managed through PCS Backup of Intouch HMI Application procedure
43.0 36M Backup of OPC Applications
Follow the steps below to perform to perform OPC configuration backup on metering HMI.
43.1 Logic to the crude or condensate metering HMI with an authorized username and ICSS
password
43.3 Note the .opf file location on top bar of the screen ICSS
43.4 Browse to the project folder on C drive (C:\Program Files\Software Toolbox\TOP ICSS
Server\Projects\CRUDE_CONFIG.opf)
43.5 Copy the project file you just created into your external backup hard drive. ICSS
43.6 Close the TOP Server screen - File > Exit ICSS
43.7 Logoff from the metering HMI and logon operator ICSS
End of Task
44.2 Press the windows button on the keyboard and type "System Management Tools". ICSS
44.3 Right click on "System Management Tools" and Click Run as Administrator below ICSS
to elevate application permission.
44.4 Tick the check box on "QITSCADAII-HIST" under Collectives and Servers. ICSS
44.5 Click Operations > Archives under System Management Tools. ICSS
N/B: The Archive File that currently has "Primary" in the Status column and has
"Current Time" in the End Time column is the active archive.
44.6 Click the Force an archive shift button to start a new Archive. ICSS
After several seconds (of clicking the Force an archive shift button , you should see
results similar to the following: The original archive file is now identified as Status of
"Has Data" (So you know it is no longer active or "current" or primary)
N/B: Archive shifts are done automatically by Historian when a "current" archive is
almost full.
44.7 Select on the archive with "old" data (the one that is NOT PRIMARY) then click the ICSS
Unregister the selected archive button
44.9 Click Refresh button (This will remove the archive). ICSS
44.10 Goto E:\Historian_archives. Scroll down to the bottom and here you should see the ICSS
actual .arc file that you have unregistered, along with its "partner" file ending with an
.ann extension (This file would store any annotations related to the data in the arc
file).
44.11 Copy the files to the site external memory device. ICSS
44.12 Close the “System Management Tools” and restore normal operator HMI. ICSS
End of Task
45.1 Request for PCS Hard disk [transfer hard disk drive] from the PCSG Supervisor ICSS
45.2 Sign out the site Hard Disk and PCS Laptop from the Maintenance Supervisor Office ICSS
45.3 Whitelist the requested Hard Disk to Center Tools Drive Lock temporarily on the PCS ICSS
Laptop
45.4 Scan the requested Hard Disk to ensure it is free from Virus. ICSS
45.5 Connect the Site Hard disk to the PCS LAPTOP ICSS
45.6 Transfer all files back up done during ICSR Sustainment PM from the SITE Hard disk ICSS
to the Requested PCS Hard disk.
! IMPORTANT: Save files on the transfer hard disk following the same path on the site
storage hard disk drive.
45.7 Sign-in Site Hard Disk and PCS Laptop back to Supervisor's office ICSS
45.8 Send requested PCS Hard disk to PCSG Supervisor with a cargo manifest and ICSS
follow-up email to assign PCSG workshop personnel to transfer content to NAS
Server
45.9 Login to the QIT NAS SERVER STATION ( For PCSG perssonnel only) ICSS
45.10 Click on c(\\10.0.0.4) (Z:) to open the Nas server mapped Network drive. ICSS
45.11 Transfer backup files to the listed authorized locations as applicable under each site. ICSS
45.12 Arrange files by year in each system/risk assessment grouping. For each year, they ICSS
should be further arranged in “AS_FOUND” and “AS_LEFT” folders.
(\\UPSTREAMACCTS.XOM.COM\DFS).
The locations above has a folder with the site name containing sub-folders as
follows:
! IMPORTANT: The reason IMAGE BACKUP folder is present on I: for QIT only is due
to size limitation. QIT images are loaded on I: to safe as off-site
storage.
45.14 Arrange backup by year in each system/risk assessment grouping. For each year, ICSS
they should be further arranged in “As_Found” and “As_Left” folders.
End of Task
46.1 Locate the most recent PCS Hardware & Software Inventory excel workbook for the ICSS
facility of interest stored in I: MPN\ORG\AFSS&DCS\.ICSR. Copy out the workbook
and carry out hardware and software inventory update as described in the following
sections of this procedure. The workbook must have the following sheets: Installed
Hardware Inventory, Delivered Software Inventory and Installed Software Inventory.
See sample sheet tabs displayed below:
46.2 On the Installed Hardware Inventory worksheet, verify that the columns/rows are ICSS
populated in the manner shown below:
• S/N - Serial numbering of all items listed on the Installed Hardware Inventory
worksheet starting from 1
• Index/RA Ref – Risk assessment numbering and should be same for all items
under the same risk assessment
• Sub Index – Serial numbering of all items under a risk assessment starting from
1
• Process Area – Plant area housing the hardware.
• Control Panel – Identity tag of the panel housing the hardware e.g.
DCS-101A-738
• Function – Function of the hardware e.g. Basic Process Control, Alarm
Management.
• Packaged Unit – Package hardware is supporting e.g. Power Generation, etc.
• Equipment Category - Category of the hardware e.g. Controller/PLC, Network
Switch, HMI/Operator Station, etc.
• Item name/Machine identifier - This is the workstation name in the case of
workstations or specific name used to identify the hardware for items that are
not workstations.
• Item description - This is the description of the item as captured in IPES e.g.
WorkStation,DCS Engineering-1.
• Tag Number –This is the IPES tag number of the hardware e.g.
NG8A-WSTN-EWS1
• Quantity – This is the physical count of an item having an IPES tag.
• HW Vendor – This is the manufacturer of the hardware e.g. Dell, 3Com, etc.
• Model –This is the model of the hardware e.g. Optiplex 755, etc.
• Attended/Unattended - Is the equipment in an attended (manned) or
unattended (unmanned) location? Indicate “Attended” or “Unattended”
46.3 Verify that all in-scope hardware components are captured on the Installed Hardware ICSS
Inventory worksheet. Update the worksheet as necessary following site survey.
The Installed Hardware Inventory grouped according to risk assessment looks like
this:
46.4 On the Delivered Software Inventory worksheet, verify that columns/rows are ICSS
populated as shown below:
• S/N - Serial numbering of all items listed on the Delivered Software Inventory
worksheet starting from 1
• SUB S/N - Serial numbering of all software listed under a risk assessment
starting from 1
• OEM/VENDOR – Software Manufacturer
• SOFTWARE DESCRIPTION - This is a detailed description of the software
• MEDIA TYPE – Through which original/authentic media the software was
received e.g. CD, DVD, USB drive, email, file download, etc.
• PART# - The manufacturer’s part number of the software as stated on media or
packing.
• SERIAL# - Software serial number indicated on media or software
documentation.
• QTY - Software quantity; physical counting of original/authentic media.
• LOCATION – Location software is stored e.g. ICS Drawer in OIM's office.
• LICENSES COUNT – This states the software license coverage e.g. System
Wide, 2 Workstation, Unlimited, etc.
• LICENSE INFORMATION AS DELIVERED – Relevant information about
software license.
46.5 Confirm that all in-scope software on the facility received from project are captured ICSS
on the Delivered Software Inventory worksheet. Update the worksheet as necessary.
The Delivered Software Inventory worksheet once completed should look something
like this:
46.6 Run PCAudit on the ICS workstations and use the listing of “Software” to verify or ICSS
update the parameters on the Installed Software Inventory worksheet. Verify that the
columns/rows are populated as shown below:
The Installed Software Inventory worksheet once completed should look something
like this:
46.7 Save the updated Hardware and Software Inventory workbook in ICSS
I:\MPN\ORG\AFSS&DCS\.ICSR\ under the Current year PCS Security Documents
folder. Also safe the raw data [PCAudit] files named according to workstation and
arranged according to risk assessment.
End of Task
47.1 Locate the most recent VISIO PCS Network diagram for the facility of interest stored ICSS
in I:\MPN\ORG\AFSS & DCS\.I C S R
47.2 Copy out and open the VISIO PCS Network diagram. Check that all in-scope ICS ICSS
components at site are well represented and inter connected correctly.
47.3 Open the “Hardware Inventories” folder and select your facility of interest ICSS
47.4 Copy out, open and go through the hardware inventory file ICSS
Using the Installed Hardware Inventory worksheet, verify that ALL listed devices are
represented on the network diagram.
47.6 Save any modified and verified network diagram in the designated shared network ICSS
drive.
End of Task
Conduct software license compliance verification following guidelines from referenced procedure.
Reference: UN-ICS-PR-06-03, License Management
48.1 Open the current site ICS Hardwares_Softwares_License Inventory workbook from ICSS
the repository on the ICSR shared drive.
48.2 Update the “Delivered Softwares Inventory” sheet to match with the list of softwares ICSS
delivered to site or decommissioned at site.
For example
48.3 Update the “Installed Softwares Inventory” sheet to match with the list of softwares ICSS
installed on each ICS workstation including the respective Operating System [OS].
For Windows OS, use compatible PCAudit tool to ensure accuracy in the capture of
softwares and version numbers.
Example
• Accurately populate the list of softwares installed on all ICS workstations without
repetitions.
• Populate the “Installed Count” column using the cell “COUNTIF” formula already
existing
• Populate the “License Verified” column using the cell “IF” formula already
existing
for example
48.5 Report all “License Verified” response of “No” through the corrective work order ICSS
process.
48.6 Using the site ICS Laptop with wireless capability, SWITCH ON the wireless network ICSS
card.
48.7 Scan for wireless networks at site and prepare a list of those that are in scope for ICSS
ICSR stating their respective purpose
48.8 Check the network drive ICSR documentation repository for license documentation ICSS
to use the wireless network. CONTACT EMIT for the license documentation if not
found on repository. SAVE the documentation in the ICSR network drive repository
when received from EMIT.
48.9 For wireless networks on systems and components used for external connection, ICSS
VERIFY that existing EMIT external network certification clearly covers the wireless
networks.
48.10 Report all anomalies through the corrective work order process. ICSS
End of Task
This is about capturing the necessary information that would be used to fill up the
access review form per workstation. The information are automatically generated by
running an executable file.
Use the print utility of the HMI application software to print to a PDF file the list
of users, groups and assigned privileges for both users and groups. For
application software (such as older versions of WonderWare) that does not
have printing capabilities;
• Take screenshots of all users with their respective assigned groups and
privileges.
• Paste all captured screenshots into any word processing package (such as
Wordpad or MS word) in the workstation and use its printing utility to print
the captured information to a PDF file (see the figure below).
d. A window looking like the figure below pops up. Press any key on the keyboard ICSS
to continue. Do not interrupt the process. It requires some time to get
completed.
e. Once the process is completed, press any key to continue for the second time. ICSS
f. This folder in addition to the application access user PDF file should be copied ICSS
to the Site_Specific_Documentation folder of the onsite PCS Hard drive and
should be transferred to a GME computer with Microsoft Excel software.
g. To exit the OneClick_local.bat process, press any key on the keyboard for the ICSS
third time.
49.2 LOCATING AND PREPARING THE ACCESS REVIEW (AR) FORM TO BE ICSS
FILLED
a. The most recent copy of AR Forms for a facility is located in I:\MPN\ORG\AFSS ICSS
& DCS\.I C S R\20XX UN PCS SECURITY DOCUMENTS\20XX USER
ACCESS REVIEWS - (BY LOCATION)\ FACILITY_NAME.
FACILITY_NAME represents the name of the asset (e.g Usan, BRT, EAP, etc).
Select any AR form of interest, ensure you copy the selected form to another
location on your computer and make all changes to the copy.
b. The AR form is of the xlsm extension and can only be opened with MS Excel ICSS
software. To fill the AR form, double click on it to open in excel and clear all
existing content.
The Access review excel spreadsheet has macros and special scripts running at the
backend that is not visible to the user. The macros and special scripts are essential
to working with this document, thus, they should be enabled prior to populating the
spreadsheet. Always ensure you click on the Enable content button to activate
macros and special scripts.
c. Rename the worksheet tab with the computer name. Access Reviews are done ICSS
on a per workstation basis. So if you are preparing access review forms for 5#
workstation, then there will be 5# worksheet tabs with different computer
names.
! IMPORTANT: Do not delete the Groups tab. Hide it before sending for approval.
a. ICSS
b. Location: Fill this field with the name of the facility (see figures above). ICSS
c. STATIONS WHERE THIS ACCESS IS APPLICABLE: Fill this field with the ICSS
computer name and the IPES tag number of the work station. In some cases
where the computer name does not depict the service of the workstation, a
brief description of the computer function should be used in addition to the
computer name (see figure below: filled with a brief description of the
computer’s function).
a. Insert a new worksheet tab. This is a temporary work area that should be ICSS
deleted before sending the document out for approval.
c.
1) Paste the content into the temporary worksheet created (Sheet1 in the example ICSS
below)
2) Delete all row entries with “rc=120 RasAdminUserGetInfo” as its username. ICSS
d.
1) Re-arrange the columns to match the access review worksheet in the exact ICSS
order below.
2) Delete all other columns not mentioned. The result should look like below: ICSS
3) Copy only the relevant content of the populated cells. In the example above, ICSS
from cell A4 through cell D27 should be the only cells copied.
e.
1) Go over to the Main Access Review Worksheet and paste the copied cells. ICSS
Preferably, do a Value Paste so as not to change the border formatting of the
sheet.
2) After pasting, delete any excess rows at the bottom of the “LIST OF ICSS
IDENTIFIED USERS” module. If the rows are not sufficient, add in more rows
before pasting.
f.
1) Paste the content into the temporary worksheet created (Sheet1 in the figure ICSS
below). Ensure that the previous users’ information is cleared before pasting
the group information.
2) Re-arrange the columns to match the Group worksheet in the exact order ICSS
below.
3) Sort the table in an alphabetic order using the “GroupMember” column as the ICSS
sorting reference.
g.
2) Paste the content into the temporary worksheet created (Sheet1). ENSURE ICSS
that the previous users’ information is cleared before pasting the group
information.
3) Re-arrange the columns to match the Group worksheet in the exact order ICSS
(GroupMember; Group) below.
Sort the table in an alphabetic order using the “GroupMember” column as the
sorting reference.
4) Open the Group Worksheet and paste the copied cells. Preferably, do a Value ICSS
Paste so as not to change the border formatting of the sheet. ADD the name of
the workstation above the table of the user group.
Note down the cell id of the first User member and the last group in the table. In
contrast with the figure above, A3 and B36 should be noted down.
h.
1) Go over to the main AR worksheet (1. ANTIVIRUS). Click on the first cell ICSS
under the “Operating System Access Level” column, the following formula
will appear in the formula bar of excel.
=vlookmulti(C20,Groups!$A$X1:$B$Y1,2)
X1 and Y1 should be replaced with the two numbers that was noted down.
Referring to the figure above, X1 = 3 and Y1 = 36, thus, the formula to be
inputted into the formula bar will be: =vlookmulti(C20,Groups!$A$3:$B$36,2).
After inputting the formula, and pressing the enter key, all the groups that the
user in that row belongs to would be populated in the cell. Endeavor to expand
sufficiently the row to expose the names of all the groups.
2) Hover the mouse on the right bottom corner of the cell until you see the mouse ICSS
pointer change to a plus sign, then drag down to replicate this formula to other
cells below until the end of the “LIST OF IDENTIFIED USERS” module.
Note: At this level of the document completion, check the list of users for
errors. Below are some of the possible errors to watch out for:
If any error(s) are identified, the errors should be corrected in the concerned
workstation, the DUMPSEC information capture should be repeated to reflect
the correction and this part of the form should be refilled (that is section i of this
procedure should be repeated).
1) Select the cell below the application access level column. ICSS
3) Click on the “create from file” in the Object dialog box that pops up. ICSS
4) Browse to the application user access file saved while capturing the DUMPSEC ICSS
information
6) In the Caption text field, input a name that would be displayed as a part of the ICSS
embedded object. The choice of name should be reflective of the file purpose.
7) Click on OK twice to close all opened dialog boxes and the embedded file ICSS
should appear in the selected cell from step XX.
8) Click and drag on this file to position it in the middle of the cell. Below the ICSS
embedded file, you would add a descriptive comment about the attached file.
Fill this column with the list of all the groups in the operating system that users
are assigned to. Referring to example above, Administrators and IIS_WPG are
the only two groups that needs to be listed.
Fill this column should with a brief description of the each Group in its
associated row. The description of the Group can be found in the
ComputerName_groups.txt file generated during Dumpsec information capture
in the AR_ComputerName folder.
Fill this column with the list of all the groups in the Application Software that
users are assigned to. This column should be filled in line with one of the three
cases below:
CASE 1
If the groups and their privileges are listed in the embedded file under users
APPLICATION ACCESS LEVEL, then a comment can be added referring the
document viewer to the embedded attachment.
CASE 2
Case 3
Where the application has no user access management, this column should be
filled with Not Applicable (N/A).
d. Delete all temporary worksheet created at this stage and hide the group folder ICSS
before proceeding to declaration .
This section should be the last to be completed after completely filling other sections
of the access review form.
a. ICSS
Submit the completely filled AR form to the approved custodian (in most cases
the Maintenance Supervisor) for review. He/ She should append his/ her name
and signature after reviewing the document.
b. Submit the reviewed AP form to the Offshore Installation Manager (OIM) or the ICSS
Person in Charge (PIC) for endorsement. The OIM/ PIC should endorse the
document by appending his/ her name and signature after reviewing it for the
Area Operations Manager (Business Owner) approval.
c. The AOM is the final approval for the Access Review document. ICSR v400
has mandated that the AOM (business owner) cannot delegate this activity to
the OIM. His/ her signature and name must be appended to complete the AR
form.
d. The following mediums for appending names and signatures are all acceptable:
1. Hard copy printout of the access review form and embedded files are to
be wet inked by all the required levels of signatories.
2. Email review, endorsement and approval from all three levels of
signatories.
3. Docusign signatures from all three levels of signatories.
Note:
1. If option 1 (the hardcopy printout) is used, then the signed forms should
be scanned and sent for AOM’s approval either by email or Docusign.
2. If Docusign is used in securing approvals, then all the embedded files in
the form has to be attached separately as a part of the Docusign envelope
for review. This is because Docusign do not have the capability to open
an embedded file.
3. Since Access request form are to be filled on a per workstation basis, if a
group of forms are being prepared together, then options 2 and 3
becomes referred so as to obtain a single endorsement and approval to
cover for all prepared forms.
e. Save completed and approved copy of the AR form in I:\MPN\ORG\AFSS & ICSS
DCS\.I C S R\20XX UN PCS SECURITY DOCUMENTS\20XX USER ACCESS
REVIEWS - (BY LOCATION)\ FACILITY_NAME. XX represents the year of
approval
FACILITY_NAME represents the name of the asset (e.g Edop, Usan, BRT,
EAP, etc).
All approval emails and copied of documented approval from Docusign should
also be saved in this location as well.
End of Task
50.1 Logon to laptop/workstation with admin level username and password ICSS
The audit policy should be set to enable success and failure for all items except
Process Tracking. However, the recommended minimum Audit Log Policies for
process control Workstations and Servers are shown below.
This allows a user to log on to the computer from the computer's keyboard.
This user right should be used to restrict logon access to authorized users. The
default "Guests" and "Everyone" groups should be removed.
This allows a user to shut down a computer remotely over a network. This user
right should be enabled for Administrators only.
The following additional security option restriction should be set. They are set under
Local Policies->Security Options
The name of the last user to successfully log in is not displayed in the Log On
to Windows dialog box
a. Configure the security, application and system logs in Event Viewer as follows: ICSS
Click Start | Click Settings | Click Control Panel | Click Administrative
Tools | Click Event Viewer
2) Select event type (Application, Security, System) under Event Viewer> ICSS
Windows Log and review the logs checking for abnormal entries.
3) Select the event type (Application, Security, System), right click and ICSS
select Properties;
End - Of - Task
4) Configure the maximum log size possible to ensure it is adequate to capture ICSS
the events between periodic reviews; recommend a “Maximum log size
(KB)” of not less than 2048KB.
Overwrite Events as needed to ensure that there is no disruption when the logs
are full in the event types (Application, Security, System)
End of Task
a. Connect one end of the CISCO Console Cable to CISCO 2950 switch and the ICSS
other end to configuration laptop (i.e RJ45 end to console port of the switch and
DB9 female to laptop’s DB9 male port).
BROWSE to the directory to save the Log file and name following required
naming convention "SITE-NAME_SWITCH NAME_SWITCH
MODEL_DDMMMYYYY"
e.g. "USAN_CISCO_2950_6DEC2019":
SELECT the Ports (COM & LPT) to confirm the Communication ports.
e. Select serial on the session tab and use the default setting with baud rate 9600 ICSS
and the right COM port, then CLICK Open
f. Hit Enter key to go into the switch in this case USAN is the switch name. ICSS
g. Type "SHOW INTERFACE STATUS" and HIT ENTER on the Keyboard to ICSS
display the status of all ports in the switch.
h. Hit Enter key till you see the switch name appeared on the terminal interface as ICSS
shown
i. Riht click on the Title bar and click Close to disconnect from the switch and exit ICSS
the putty application
j. Press "CTRL+H" on the keyboard and copy the characters as shown in the ICSS
picture, paste in the "Find what" tab and leave the "Replace with" tab blank
Click Replace All
N/B: This special characters are created when pressing enter during the
capturing process
k. Go through the Log and SAVE the file by Clicking File | Save ICSS
If port 1 on the configuration shows “no shutdown”, it means the network port is
unblocked. If it shows “shutdown”, it means port is blocked.
Cable connected ports should indicate “no shutdown” while non-cable connected
ports should indicate “shutdown”. If they match, then review is completed.
! IMPORTANT: Scenerio: A network device connected to a switch port taken out for
repair, will leave that port with "not connected" status. Such ports can
be blocked immediately they are removed from the network.
! IMPORTANT: For non-cable connected ports which indicate “no shutdown”, ports
must be blocked immediately following the procedure below for
blocking (or unblocking).
Logon to the switch console: BY typing "en" in front of the switch name and
TYPE in the password as revealed in the Firecall envelope and press ENTER
key “Switch#” appears.
Result: Switch(config)#
o. Type Int f0/xx and press enter (where xx is the port number you want to ICSS
open)
Result: Switch(config-if)#
q. Type exit and press <enter>, type exit again and press <enter>, to exit to ICSS
Switch# mode.
(Note: this means “configure terminal” which can also be typed in full, and in
the BRT example the prompt will be NGBR-DVPRI-SW-1#)
Result:
t. Type the command enable secret xxxxxxxx and press <enter>. (where ICSS
xxxxxxxx is the new password)
x. Insert the new password for logon and press <enter>. ICSS
z. Create two new firecall envelopes (one for onsite fireproof safe and one for ICSS
PCSG offsite storage).
aa. Document the switch configurations in shared LAN drive under “year” ICSS
NETWORK SWITCHES CONFIGURATIONS in the respective location’s folder
51.2 Firewalls/Routers
a. Raise EMIT Get Assistance (REQ....) ticket asking for downloads of firewall ICSS
configurations for all firewalls in UN Business Unit (BU).
EMIT will create internal WO, send it to Global Network Security team to download
firewall configurations, and revert via email.
b. When download is available, open the previous firewall configuration in “ACL ICSS
RULES & IMPLEMENTATIONS (BY ASSET)” in shared LAN drive that were
signed off by respective asset managers.
c. Compare the last year’s configuration of each site (on shared LAN drive) with ICSS
the current downloaded configurations for each site.
d. Review the full access control list (ACL) as received from EMIT. ICSS
Note: For asset with two or three sites, the two or three OIMs will have to
endorse.
3) Document approval appropriately in shared LAN drive under “year” ACL ICSS
RULES & IMPLEMENTATIONS (BY ASSET) when approval is completed.
f. Option 2 – Configuration Does Not match With EMIT Submitted Log ICSS
1) Copy the full configuration received from EMIT into the ACL review document. ICSS
2) Identify any new IP address(es) on the new configuration from EMIT and follow ICSS
up with EMIT for prior owner's approval.
3) Document the change approval on shared drive and route the ACL ICSS
configuration review for DocuSign approval.
4) Once approval is provided, document appropriately in shared LAN drive under ICSS
“year” ACL RULES & IMPLEMENTATIONS (by asset).
5) If there was no approval for the changes, report the finding in a corrective work ICSS
order for investigation and proper closeout.
End of Task
52.1 Sign out the latest copy of the following from the OIM (Offshore Installation ICSS
Manager).
52.2 Confirm the Firecall Envelops checking that envelop number and physical count ICSS
matches with the number and count on the Firecall ID Inventory sheet. Ensure
Firecall IDs are present and accounted for.
52.3 Check for removal/proper documentation of any retired Firecall IDs. ICSS
52.4 Confirm no additional Firecall ID exist (that are not documented). ICSS
52.5 Reconcile the Firecall ID Inventory sheet against the Firecall IDs ensuring New ICSS
Firecall IDs are included.
52.6 Call the Security Contact at PCSG office to ensure the FireCall ID (offsite storage) ICSS
matches the one onsite.
N/B: Any unaccounted for or compromised Firecall ID(s) are to be noted and
investigated.
52.7 Check to make sure all Firecall Envelops are properly stapled/sealed and labeled. ICSS
52.8 Check the Firecall ID Check-in and Check-out process, to ensure that the ICSS
Information on the Firecall ID Usage Log is complete and timely.
52.9 Check the duration (ISSUE DATE – RETURN DATE) of usage of a Firecall ID to ICSS
ensure it is within the agreed upon time interval (maximum expected duration of
usage is 72 hours). If it’s more than, verify there is an approved extension.
52.10 Reconcile the Firecall ID Usage Log book against the Approved Firecall UserLists ICSS
(Located on AFSS & DCS folder I:\ drive) ensuring Firecall IDs are signed out by
approved users.
End of Task
53.3 Type goto/Asset on the Exxonmobil Home page Address bar ( as shown below and ICSS
hit the ENTER key on our keyboard
53.4 Click on the Assessment in the ASSET web page to drop down list, SELECT ICSS
“Search Assessment”.
53.5 Click on the drop down arrow as shown to the right of production unit name and ICSS
select “Upstream Nigeria” from the drop down list.
53.6 Type the location name e.g. BRT under the Risk Assessment Name. ICSS
Click the Search Button to display list of all Risk Assessment done for the BRT
location.
53.7 The Navigation bar to display other pages and the ScrollBar to scroll down. ICSS
Scroll Bar
Navigation Bar
53.8 Click on the pencil symbol beside the required risk assessment to open the ICSS
document, wait for it to finish loading.
53.9 Click on overview button on the top right side on the page to display the Overview of ICSS
the Document.
53.10 Click on the attachment button on the bottom of the overview page. ICSS
53.12 Click on View Detailed Report button on the bottom of the overview page. ICSS
53.13 Navigate using the Forward Arrow to the CONTROLS catalog page. ICSS
53.14 Open the downloaded Controls Document and check the status to make sure all ICSS
controls are in place.
53.15 If a Planned control is confirmed to be In Place: UPDATE the Controls Document of ICSS
the risk assessment in ASSET by changing the status of the control to “In Place”.
53.16 If a control status is still Planned to be implemented, implement the controls and ICSS
document in the risk assessment as 'In Place'.
53.17 Extract the applicable shall statements from the ICSR document based on the risk ICSS
assessment.
53.18 Verify that the applicable shall statements have been implemented, otherwise ICSS
IMPLEMENT.
End of Task
The selected ICSR Risk Assessment Team Leader/Facilitator will perform the following steps to conduct cross
functional team review of site ICSR risk assessments and deviations.
The ICSR Risk Assessment Team Leader/Facilitator is selected by the PCSG Supervisor.
! IMPORTANT: During the team review session, all ICSR risk assessments for the site
are to be reviewed [not only selected risk assessments]. The quality of
risk assessment review depends on the competency of facilitator and
cross functional team conducting the review. See mandatory [shall]
requirement below:
54.4 Check ICSR shared drive storage [e.g. I:\MPN\ORG\AFSS & DCS\.I C S R\2017 UN ICSS
PCS SECURITY DOCUMENTS\RISK ASSESSMENTS\USAN] for any approved and
active ICSR risk assessments for the site but not migrated to ASSET.
! IMPORTANT: Note that not all ICSR risk assessments for the site may have been
migrated to ASSET (Advanced Systems Security Evaluation Tool)
54.5 Compile the list of all approved and active ICSR risk assessments for the site ICSS
including respective review due date. It is required to compile the list of approved
and active risk assessments in ASSET and those not migrated to ASSET.
54.6 Note the earliest and latest review due dates from the list of approved and active ICSS
ICSR risk assessments compiled, check IPES for date of next 36M Verification of
ICSR & RA controls, and decide on planned review period to occur between the
earliest or latest review due date and the next 36M Verification of ICSR & RA
controls.
Example:
! IMPORTANT: Planned review period can fall before or after latest review due date
identified depending on activities and personnel involvement at site
including date of next verification PM. For instance, in the example
above, the stated planned review period will still remain if the latest
review due date falls in 2019 or 2020 because next verification PM is in
2Q2021.
54.8 Identify the cross functional team required to review the risk assessments. Typical ICSS
functions include:
• Operations Specialist
• Instrumentation & Controls Specialist
• Electrical Specialist
• ICE Engineer
• ICS Specialist
• OEM/Vendor ICS FSR ICSR Risk Assessment Facilitator – ICS Technical
Subject Matter Expert with the training or expertise to facilitate ICSR risk
assessment.
54.9 Identify the work location with the required resources to host the review of the risk ICSS
assessments.
54.10 Document the risk assessments review plan on email and obtain Business Owner’s ICSS
approval preferably before the earliest review due date is reached. The plan will
include the following:
• List of all approved and active risk assessments for the site with respective
review due date.
• Date period for the review of the risk assessments with reason(s) for selecting
the period.
• Cross functional team required.
• Location to host the review session.
• Continued operation of site ICSE with approved and active ICSR risk
assessments beyond reassessment period until reviewed and approved [if
earliest review due date precedes plan].
• For systems in operation, the Business Owner is the Area Operations Manager.
• For system in project phase, the Business Owner is the Project Manager.
54.11 Compile and study the latest verified inventory and network diagrams for the site ICSS
including documentation on the site ICS.
54.12 Gather the cross functional team for the risk assessment review session. ICSS
54.13 Decide on the grouping, naming and numbering of the risk assessments to follow the ICSS
format: BUSINESS UNIT_SITE_ICSR_RA_Serial Numbering_SYSTEM GROUPING
CODE or ACRONYMN
1. UN_USAN_ICSR_RA_1_ICSS
2. UN_USAN_ICSR_RA_2_SSCS
3. UN_USAN_ICSR_RA_3_TG-TC-LPC
4. UN_USAN_ICSR_RA_4_MMS
5. UN_USAN_ICSR_RA_5_COMS
6. UN_USAN_ICSR_RA_6_PDCS
7. UN_USAN_ICSR_RA_7_ESDG&EMDG
8. UN_USAN_ICSR_RA_8_OPS
! IMPORTANT: Decide on short risk assessment names/codes that clearly identify the
system(s) in scope. Serial numbering of risk assessments for a site
help in easy count and arrangement of ICSR documentation including
backups arrangement on approved storage media/locations.
Automatic/system generated naming without following serial numbering
should be avoided.
54.15 Create and complete as new/original risk assessment following the workflow, training ICSS
or expertise for risk assessments not migrated to ASSET or those in ASSET but
named not as required,
For system in project phase, the Custodian is the Project I&C Design Engineer
e. Complete the Exposures section through Risk Screening, Initial, Residual and ICSS
Threat Vector Assessments.
f. Go through the ICSR mandatory statements and compile list of deviations to ICSS
ICSR as applicable to the risk assessment. Read the global ICSR deviation
document and any available local deviation document for input on how to
compile the applicable deviations
g. Attach the verified inventory, network diagram, compiled deviation document, ICSS
one page summary of risk assessment conclusion, and controls document
extract [formatted with irrelevant content removed].
h. Update the comments section with summary of risk assessment outcome, ICSS
deviations to ICSR and list of attachments.
i. Print risk assessments in pdf with attachments and review with team members, ICSS
responsible parties to action items, custodian and business owner. Make valid
and fit-for-purpose updates as required by reviewers.
j. Submit risk assessment, follow up and obtain endorsement and approval. ICSS
k. Retire all previous risk assessments replaced by the reviewed ones. Add the ICSS
word “RETIRED” in file name of the risk assessment not in ASSET.
54.16 For risk assessments already in ASSET with name and template as required, clone ICSS
and complete the review following the workflow, training or expertise taking into
account any changes during the review period.
! IMPORTANT: If the cloning function is not available, conduct the review as a new risk ICSS
assessment.
• For systems in operation, the Custodian can be the Maintenance Supervisor. ICSS
-
• For system in project phase, the Custodian can be the Project I&C Design
Engineer.
• Complete the Exposures section through Risk Screening, Initial, Residual and
Threat Vector Assessments.
• Go through the ICSR mandatory statements and compile list of deviations to
ICSR as applicable to the risk assessment. Read the global ICSR deviation
document and any available local deviation document for input on how to
compile the applicable deviations.
• Attach the verified inventory, network diagram, compiled deviation document,
one page summary of risk assessment conclusion, and controls document
extract [formatted with irrelevant content removed].
• Update the comments section with summary of risk assessment outcome,
deviations to ICSR and list of attachments.
• Print risk assessments in pdf with attachments and review with team members,
responsible parties to action items, custodian and business owner. Make valid
and fit-for-purpose updates as required by reviewers.
• Submit risk assessment, follow up and obtain endorsement and approval.
• Confirm that the previous risk assessment is no more in ASSET, otherwise,
retire it.
54.18 Send official report of completion of the risk assessment review session using the ICSS
email trail of Business Owner’s approval to conduct the risk assessment review.
Save the report in dedicated shared drive e.g. I:\MPN\ORG\AFSS & DCS\.I C S
R\2017 UN PCS SECURITY DOCUMENTS\RISK ASSESSMENTS REVIEWS_MGT
APPROVALS\DWO - ERHA.
End of Task
55.1 Prior to closeout, remove all tools, extra parts, and loose materials from the work ICSS
area.
55.2 If the ICS was shut down and locked out, remove the locks and tags and then ICSS
restore power to the unit according to Lock out/Tag-out (LOTO) guidelines.
55.3 Notify the Control Room Operator that maintenance is complete and the ICS is ready ICSS
for service.
55.4 Verify that the ICS is in service and that all associated emergency shutdown initiators ICSS
and the inputs/outputs are according to the actual operating conditions.
55.5 Ensure backups for application and operating system are stored according to the ICSS
backups management framework.
55.6 Remove the Supplementary Control Certificate (SCC) from the safety system, as ICSS
applicable.
End of Task
Appendix
Checksheet
QIT ICSR Sustainment PM Workbook
Attachment 1
Siemens attachment 1.
Omni
OMNI FIXED DATA VERIFICATION TEMPLATE
Supporting Information
Associated Procedures
Reference Documents
Reference the following documents while preparing for and performing this procedure:
Vendor Documents
The following Rockwell Automation Documents are associated with their products in this procedure:
[Refer to the following vendor manuals for detailed instructions, diagrams, and specifications]
website:http:/literature.rockwellautomation.com
The following Vendor Documents are associated with Siemens S7-400 PLC installation in this procedure:
The following Vendor Documents are associated with GE Fanuc 90-30 PLC installation in this
procedure:
[Refer to the following vendor manuals for detailed instructions, diagrams, and specifications]
§ Series 90 -70 Programmable Controller, Installation Manual, GFK-0262G
§
Series 90 -70, Genius Bus Controller and Genius I/O System,
Troubleshooting Guide, GFZ-0087
The following OMNI Documents are associated with their products in this procedure:
The following FactoryTalk Documents are associated with their products in this procedure:
Classification Matrix
Procedure Classification Matrix
Probability Probability
A B C D E Category Probability
I IC IC IC IC IC/N* A Very likely (> 10 percent of occurrence; it occurs 1 in 10 times)
C
Immediate response and analysis required.
O
N II IC IC N N N B Somewhat likely (1 to 10 percent chance of occurring; it
S occurs 1 in 100 times) Prompt response and analysis
E required.
Q
U III IC N N WA WA C Unlikely (0.1 to 1 percent chance of occurring; it occurs 1 in
E 1,000 times) More than 10 minutes to respond, response is
N P1 P2 obvious.
C
IV N WA WA WA WA D Very unlikely (0.01 to 0.1 percent chance of occurring; it
E
occurs 1 in 10,000 times) Potential for human error causing
S
an incident.
IC - Integrity Critical Procedure E Practically impossible (< 0.01 percent chance of occurring; it
N - Normal Procedure may occur 1 in 100,000 times) Familiar, unlikely to be done
WA - Work Aid/Low Risk Procedure incorrectly.
*- Can be IC or normal based on local management decision
Considerations
1. Define the most severe credible consequence scenario assuming a procedure is not followed or not in place. Document the scenario
in the space provided below.
2. Determine the consequence and probability for the scenario assuming a procedure is not used. Plot this on the matrix and label it as
Point 1. If Point 1 falls in a box labeled:
▪ IC, the procedure is Integrity Critical (IC)
▪ N, then the procedure is Normal (N)
▪ WA, then the procedure is a Work Aid (WA)
3. Determine the consequence and probability for the scenario assuming a procedure is available and used. Plot this on the matrix and
label it as Point 2.
Note: Point 2 is the resulting residual risk with the procedure being used. If this point is in a box labeled IC or N, then additional actions (e.g.:
placing additional safety devices) must be taken.
Procedure Classification
Procedure Name: QIT ICSR SUSTAINMENT Date: DEC. 6, 2019
Step 1: Worst Case Scenario(s) used for During PM on Bentley Nevada GE 3500 machine monitoring system,
Classification:
configuration download was performed instead of upload resulting in severe
damage of the monitored equipment, significant financial loss, and
environmental impact.
Step 2: Plot 1 (P1) Classification (IC, N, Consequence: B
or WA): Probability: 3
Classification:
Step 3: Plot 2 (P2) Residual (should be Consequence: D
WA): Probability:3
Classification:
Team Lead: Iniobong Williams Team Lead Signature: