Business Continuity Management Plan Version 1.0

8/15/2019 Business Continuity Management Plan Version 1.0.

1/64

Business Continuity Management Plan

PROCEDURE NUMBER:

EFFECTIVE DATE:

Page 0 of 64

Business ContinuityManagement Plan

June 2015


2/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

Page 1 of 64


3/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

Contents1. Executive Summ!".............................................................................................................................. ##. BCM Po$ic" Sttement.......................................................................................................................... #%. O&'ectives.............................................................................................................................................. %(. Sco)e..................................................................................................................................................... %*. Assum)tions......................................................................................................................................... %+. BCM P$n St!uctu!e..............................................................................................................................(,. P!evention - Ris Mn/ement P$n..................................................................................................+0. P!e)!eness 2 Business Im)ct Assessment...................................................................................03. Res)onse - Incient Res)onse P$n................................................................................................14

9.1 Emergency Requiring Evacuation...................................................................................................9.2 Emergency Response not Requiring Evacuation............................................................................9.3 Immediate Response Checklist.......................................................................................................

14. Business Continuit" Ro$es n Res)onsi&i$ities..........................................................................1%10.1 ! E"ecutive Committee #EC$..................................................................................................10.2 %usiness Continuity &anagement Committee #%C&C$...............................................................10.3 %usiness Recovery 'eams ( %R's..............................................................................................10.) *ey Contact +um,ers.................................................................................................................10.- Important 'elephone +um,ers....................................................................................................10. /ist o ! %ranches..................................................................................................................10. Customers...................................................................................................................................10. ervice roviders45endors..........................................................................................................10.9 Employee Call 'ree /ist..............................................................................................................

11. Recove!" - Recove!" P$n..............................................................................................................1013.1 6isaster Recovery ite #6R$.....................................................................................................13.2 7eneral Recovery rocedure8.....................................................................................................

13.3 Recovery Requirements..............................................................................................................11.3.1 ta Resources...............................................................................................................................11.3.2 ork tations : +et;orked Cs +eeded.......................................................................................11.3.3 rinters< hotocopiers : =a" &achine............................................................................................11.3.) ot;are needs...............................................................................................................................11.3.- 5ital Records needed......................................................................................................................

13.) 7> ?C*...................................................................................................................................13.- %usiness @nit Recovery ?ctivities...............................................................................................

11.-.1 Construction upervision................................................................................................................11.-.2 6esign.............................................................................................................................................11.-.3 Commercial %usiness @nit..............................................................................................................11.-.) &4=&4%6 %usiness @nit................................................................................................................11.-.- Integrated &anagement ystem.....................................................................................................11.-. =inance...........................................................................................................................................11.-. Inormation 'echnology...................................................................................................................11.-. !uman Resources..........................................................................................................................11.-.9 &arketing........................................................................................................................................

1#. Re5e!se6 Mintin n Revie7.....................................................................................................*01%. Annexu!es........................................................................................................................................*3

13.1 ! Computer ystems.............................................................................................................13.2 %usiness Recovery Checklists....................................................................................................13.3 Event /og....................................................................................................................................

Page 2 of 64


4/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

1. Executive Summ!"

'he !As &anagement deems it important to have a %usiness Continuity lan #%C$ so asto ensure the continuity o the !As >perations at all times< especially during an emergencyor disaster ;hen at least the minimum ,asic customer services should ,e made availa,le.'his is an imperative to ensure ,usiness survival< ,usiness continuity< including ulillment o responsi,ility to;ards customers< government< partners and employees.

'his %C incorporates the revention< reparedness< Response and Recovery #RR$rame;ork. Each o these key elements is represented ,y a part in the %usiness Continuitylanning rocess.

#. BCM Po$ic" Sttement

! aims to develop< implement and resource a %C& lan that ;ill ena,le us to respond

to and manage any disruptions that occur. !As %C& lan is concerned ;ith improving

the resilience o the !. 'his means developing its a,ility to detect< prevent< minimiBe

and ;here necessary deal ;ith the impact o disruptive events. In the atermath o an

incident< it ;ill ena,le the urgent or priority activities o ! to continue in the longer term

it ;ill help ! to recover and return to D,usiness as usualD as soon as possi,le.

'he %usiness Continuity &anagement lan has the ollo;ing key o,ectives are to8

• Raise the proile o %C& ;ithin !. 'his ;ill include arrangements to make sta

a;are o plans< their roles in them and are trained appropriately

• Identiy urgent or priority #time critical$ activities across ! and develop suita,le

,usiness continuity arrangements or them

• Esta,lish deined structures to plan or and respond to incidents

• !ave ongoing %C& arrangements that are su,ect to regular revie;s< audits and

e"ercises

• &eet applica,le legal requirements and revie; the lan or continuous improvement<

;ith reerence to ,est practice< such as I> 223018201- #%usiness continuitymanagement systems requirements$ and

• Em,ed %usiness Continuity into the culture o ! so it ,ecomes an integral part o

decision making.

Page 3 of 64


5/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

%. O&'ectives

• 'he development o a ;ell(structured and coherent plan ;hich ;ill ena,le ! to

recover as quickly and eectively as possi,le rom an unoreseen disaster or emergency ;hich interrupts normal ,usiness operations ,y rendering the technicalinrastructure inopera,le or a period e"ceeding one day.

• Esta,lish cohesive emergency response and crisis management plan.

• 6evelop a communications plan to notiy teams< activate the plan< assess damages<

and declare a disaster.

• 6eine mission critical processes using a %usiness Impact ?nalysis.

• 6eine manual processes that can ,e implemented until the technical inrastructure is

restored.

• 6evelop a plan to recover and restore !As technical inrastructure.

• Esta,lish criteria or making the decision to recover at a 6R or repair the aected site.

• 6escri,e an organiBational structure or implementing the plan.

• rovide inormation concerning the types o personnel ;ho ;ill ,e required to

implement the plan and deine the skills and kno;ledge required.

• Identiy the equipment< procedures< and other items necessary or the technical

recovery.

(. Sco)e

'he scope o the %usiness Continuity &anagement lan ;ill operate across ! ( *u;ait<covering all its departments. 'he I' %usiness @nit ;ill remain responsi,le or speciic6isaster Recovery arrangements relating to the recovery o I' servers4applications that !operate.

'he %C& lan is ocused on protecting and recovering the critical activities o ! and linksto the vision o ! o Frovide regional leadership in delivering high standards o qualityand value to our customersG.

'he %C& lan aims to ensure that ro,ust ,usiness continuity management arrangements

are developed and applied to all key services that are proportionate to their signiicance andthe risks o disruption that may impact them.

*. Assum)tions

• !ealth< lie and saety issues are addressed ,y the ! Emergency Response lan

maintained ,y the I& @nit.

Page 4 of 64


6/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

• Restoration o acilities is addressed in the =acilities &anagement lan maintained ,ythe =& 'eam #6ocument +um,er HE01/?011v1.0C6$.

• 6etailed actions to restore the I' system are addressed in the I' 6R maintained ,y

the I' @nit. !o;ever the list o critical ,ackup computer reports that ;ill ,e madeavaila,le during a disaster and the distri,ution lists o these reports are covered in thisdocument.

• 'his plan covers catastrophic events. lanned and unplanned do;ntime o less than

one days are not addressed.

• 'he %usiness Impact ?nalysis developed ,y dierent ! @nites ;ill drive Restoration

and Recovery trategies detailed in this plan.

• revention is the most important aspect o continuity planning.

• 'he Recovery oint >,ective #R>$ deines the amount o data that can potentially ,e

lost in the event o a disaster.

• 'he Recovery 'ime >,ective #R'>$ is the time rame in ;hich the technical

inrastructure is to ,e restored. In some cases< the R'> is not quantiied due to the lacko a redundant data center and the unkno;n varia,les o ho; long it ;ill take toprepare a 6R in the event that one o ! ites is damaged ,eyond use.

+. BCM P$n St!uctu!e

'he main sections o this %C& lan< as sho;n in the ollo;ing igure< are as ollo;s8

revention ( Risk &anagement planning8 Incorporates the Prevention

element that identiies and manages the likelihood and4or eects o riskassociated ;ith an incident.

reparedness ( %usiness Impact ?nalysis8 Incorporates the Preparedness

element that identiies and prioritiBes the key activities o a ,usiness thatmay ,e adversely aected ,y any disruptions.

Response J Incident Response planning8 Incorporates the Response

element and outlines immediate actions taken to respond to an incident interms o containment< control and minimiBing impacts.

Recovery ( Recovery planning8 Incorporates the Recovery element that

outlines actions taken to recover rom an incident in order to minimisedisruption and recovery times.

In addition this %C includes a Rehearse< &aintain and Revie; section

;hich includes details activities necessary to test< regularly revie; and

Page 5 of 64


7/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

update the %usiness Continuity lan in order to ensure that ! sta areamiliar ;ith it< and that it relects changing ,usiness needs.

Page 6 of 64


8/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

,. P!evention - Ris Mn/ement P$n

• ? Risk is an event that causes a disruption in the normal ! operating environment o

more than t;o days. ! recogniBes the ollo;ing types o threats8

Environmental Risk #e.g. ire< lightning strike< earthquake< lood$

Equipment =ailure Risk #e.g. hard;are< internet and communication< !5?C<

ire$ @tility =ailure Risk #e.g. electricity< ;ater$.

!uman Risk #e.g. sa,otage< terrorism< virus< ,om, threats< ro,,ery4thets


9/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

Ris Desc!i)tion:

8 i . e $ i 5 o o 1

I m ) c t

R t i n /

P!eventtive Action

• @ are availa,le at u,han site.

• =or more details reer to the =acilities

&anagement lan maintained ,y the =& 'eam.

!uman Risk #e.g. sa,otage<terrorism< virus< ,om,

threats< ro,,ery4thets<hackers$

1 - / • ensure adequate insurance cover in place

including ,usiness interruption and general property

• ?ll systems should have security products

installed to protect against unauthoriBed entry. ?llsystems should ,e protected ,y pass;ords< especiallythose permitting updates to data. ?ll users should ,erequired to change their pass;ords on a regular ,asis.

?ll security systems should log invalid attempts toaccess data< and security administrators should revie;these logs on a regular ,asis.

• ?ll systems should have the latest virus protection

sot;are.

• ?ll systems should have the latest patches applied

to operating systems. Computers ;ithout the latest

patches are more vulnera,le to attack and can have adevastating impact on the campus net;ork.

• ?ll systems should ,e ,acked up on a periodic

,asis. 'hose ,ackups should ,e stored in an areaseparate rom the original data. hysical security o thedata storage area or ,ackups must ,e implemented.tandards should ,e esta,lished on the num,er o,ackup cycles to retain and the length o theirretention.

• =or more details reer to the I' 6R maintained

;ith the I' @nit.

=oreign ?ggression 1 - / • ensure adequate insurance cover in place

including ,usiness interruption and general property

Page 8 of 64


10/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

0. P!e)!eness 2 Business Im)ct Assessment

• 'he %usiness Impact ?nalysis #%I?$ is designed to help %usiness 6ivisions4 @nits

;ithin ! determine the impact on its unctions i they ;ere to suer a disruption o ,usiness operations.

• &ission critical processes and systems are identiied on the ollo;ing %usiness Impact

?nalysis matri". 'his matri" ;as developed considering the eed,ack received rom all%usiness @nits and is ,ased on the impact to ! >perations. hile the impact mayvary depending on the timing o an event< the matri" assumes ! is in normal

operating mode ;hen the event occurs.• 'he criteria used to determine the ,usiness impact consist o the ollo;ing elements8

=inancial /osses

/egal /ia,ility

Competitive osition

Reputation

Business Unit Business Activit"

C!itic$it"

RTO

1 " 1 7ee mont5

Construction upervision %idding & & & 1 day

Recruitment 4 R& / / & 1 day

&:C 4 Reporting 4 Contract&anagement 4 Invoicing 4 Close out

/ / / 1 day

6esign 6esign rocess / & ! 1 day

Reprographics / / & 1 day

%idding and roposals / & & 1 day

upport ervices / & ! 1 day

I& H? / / & 1 ;eek

!E & & ! 1 day

Corporate ?airs / / / 1 month

tatutory ?uthority / & & 1 day

roect Controls / & & 1 dayCommercial %usiness ?dvisory & ! ! 1 day

Company ecretarial & & ! 1 day

Revie; R=Ks and Contractual6ocuments

& & ! 1 day

&< =& : %6 & / & ! 1 day

=& / & & 1 day

%6 / & & 1 day

=inance ?ccounts aya,le / / & 1 day

Revenue< %illing and Collections / / / 1 day

Page 9 of 64


11/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

Business Unit Business Activit"

C!itic$it"

RTO

1 " 1 7ee mont5

%udgeting +? +? +? 1 day

Reporting / / & 1 day

I' I' Inrastructure lanning+? +? +? +?

Inormation ecurity +? +? +? +?

ot;are ?pplication 6evelopment: 'rou,leshooting

+? +? +? +?

&aintain 6ata centerAs to !ostE"change : &ass torage 6evises

+? +? +? +?

!elpdesk @ser End upport :'raining

+? +? +? +?

!R Employee ervices +? +? +? 1 day

6ata &anagement and 'raining +? +? +? 3 days

Recruitment : resourcemo,iliBation

+? +? +? 3 days

&arketing :Communications

Internal and e"ternalcommunication

+? +? +? 1 day

Page 10 of 64


12/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

3. Res)onse - Incient Res)onse P$n

• 'he purpose o this section is to prepare ! or a timely response to critical incidents

and reduce the impact o those incidents on ! ,usiness operations as identiied inthe risk assessment. It also prepares key personnel to provide and coordinate aneective response to ensure minimal disruption to ,usiness operations in the event o emergency.

• Emergency response addresses the ollo;ing types o emergencies8

Emergency requiring evacuation o the premises and Emergency response that does not require evacuation o premises

3.1 Eme!/enc" Re9ui!in/ Evcution

• In respect o emergency response requiring evacuation< a detailed evacuation plan is

prepared or each oice ,y the hysical ecurity 'eam. ? copy o the evacuation planrelevant to the team is attached as an appendi" to this document.

• 'he assem,ly point or emergency response requiring evacuation or ,usinesses

located in ?l !amra oice is deined in the =acilities lan.

• 'he %R' or his deputy should assume or assign responsi,ility or evacuation

coordination ;ithin in his ,usiness area.

• =ollo;ing the evacuation i the ,usiness is una,le to resume operations rom their

oice due to the non(availa,ility 4 inaccessi,ility o the premises< the %C&C ;ill declarean emergency and issue orders to invoke the %usiness Recovery lan. 'his ;ill requirethe department to relocate their critical ,usiness operations to !As disaster recoveryacility.

• 'hese are the irst stage activities undertaken to control or contain urther damage to

! in the event o a maor incident and include preparation or resumption o critical,usiness operations. Emergency response activities are maintained under separatecover ,y the relevant Emergency Response teams< as ollo;s8

P5"sic$ Secu!it" J evacuation plan and corresponding procedures #Reer8

HE01/?011$ Ino!mtion Tec5no$o/" J I' disaster recovery plans and procedures

#Reer8 ! 6R 'est lan$ ;umn Resou!ces J eople management plan #Reer8 HE01R003$

Page 11 of 64


13/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

CEO


14/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

INCIDENT RESPONSE ACTIONS TA=EN

• ,rieed team mem,ers on incidentL

• conirmed speciic roles and responsi,ilitiesL

• identiied any damageL

• identiied critical ,usiness activities that have

,een disruptedL

• kept sta inormedL

• contacted key stakeholdersL

• understood and complied ;ith any

regulatory4compliance requirementsL

• initiated media4pu,lic relations responseL

Page 13 of 64


15/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

14. Business Continuit" Ro$es n Res)onsi&i$ities

14.1 SS; Executive Committee >EC?

• E"ecutive Committee #EC$ is the core management team responsi,le to oversee %usiness

Recovery during emergency or crisis.

• In the a,sence or ina,ility to meet or contact all individuals< any three individuals can take

required decisions.

• ?ny t;o individuals listed in the EC can ointly sign to collect the ,ackup tapes rom

u,han site and 4 or ?l !amra site.

EC Mem&e!s Contct Num&e!s A$te!ntive Num&e!

Ro,ert !ope #!ead o EC$ M9- 90 02 02 M9-2221203

&att quires M 9) ) )99 M 9) )03 -0 -1

teve &ullholland M 9- 93 0 -9 M9-2221209

ean 6e;hurst M 9- -0 9 )) M9-222120

/ee kinner M 9- 90 02 01 M 9- 222 12 0

%assam Nahreddine M 9- -01 - 1 M 9- 222 12 0-

!ala 'ayli M 9- 0 - --M 9- 222 12 099 e"t01-

EC 2 Min !es)onsi&i$ities

• 'he main responsi,ilities o EC are to8

'ake e"ecutive decisions ,ased on the scenarios and prevalent situation Coordinate ;ith the CE>< 7overnment ?uthorities and the media

?uthoriBe emergency actions< approvals and purchases

Call or meetings o ;orking groups as and ;hen necessary and

?uthoriBe collection o ,ack(up tapes rom u,han site and 4 or ?l !amra

ite in case o a country(;ide disaster.

Page 14 of 64


16/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

14.# Business Continuit" Mn/ement Committee >BCMC?

• %C&C reports to the !ead o EC as per the duties and responsi,ilities assigned to

them. 'he %C&C communicates ECAs decisions to the relevant ! %R's.

BCMC Mem&e!s Nmes Contct Num&e!s A$te!ntive Num&e!

!ead o %C&C +ick =or,ess M 9- -09 - ))1 M 9- 222 12 02

?lternative %C&CCoordinator

te;art Cripps M 9- 99 3 3- M 9- 222 12 099

Resident 6irector 7eorge ?,i

!annaM9- 3)111 M9- 222120-

!ead o I' ean 6e;hurst M 9- -0 9 )) M 9- 222 12 0

Risk &anagement<Commercial :Compliance

/ee kinner M 9- 90 02 01 M 9- 222 12 0

&anager< &arketing: Communications

!ala 'yali M9- 0---M9- 22212099 e"t.01-

BCMC - Main responsibilities

• 'he main responsi,ilities o the %C&C are to8

Identiy locations #including sites$ to ,e operated and4or closed rovide alternate oice space or sta< ;hen required

Ensure adequate staing or all locations and security access

?rrange adequate liquidity

rovide transport or 6isaster Recovery ite #6R$ equipment and supplies

rovide or sae movement o valua,le documents

?dvise and o,tain approval o emergency purchases and repairs

Coordinate ;ith government and 4 or emergency services

Ensure providing agreed customer services or customers depending on the

emergency situation

Ensure the smooth running o computer systems and management o the

relevant teams

Coordinate ;ith other %usiness Recovery 'eams #%R's$ and update the EC

?nalyBe and assess damage claims or insurance and

Conduct periodic adhoc simulation o disaster tests.

Page 15 of 64


17/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

14.% Business Recove!" Tems 2 BRTs

• %C&C reports to the !ead o %C&C as per the duties and responsi,ilities assigned to

them. 'he %R' teams communicates %C&CAs decisions to their respective @nits.

BU BRT Mem&e!s Contct Num&e!s A$te!ntive Num&e!

Constructionupervision

heri ona,aty M9- 0 - M9- 2220 0-

6esign&ark ilson

antosh onnan M 9- 90 1 -- M 9- 222 - 3

Commercialheikh ?si &ahmood M 9- 90 29 99 M 9- 222 12 091

/ouise !unt M 9- - 9) -0- M9- 222 12 03

I&Ooseph Oo, M 9- ) )9 )- M 9- 222 12 099

/ucy,el 6enaque M 9- 90 1 )3 M 9- 222 12 099

=acilities&ostaa 6aha, M9- 0 3) 331 M9- 222 - 0)

?tikur Rahamn M9- 99- 0- )9 M9- 222 - 09

=inance%assam Nahreddine M9- -01-1 M9- 222120-

ivakumar 5 M9- 3---1 M9- 222120

!R Radha Ramasamy M 9- 9 1 1 M 9- 222 12 099&ohammad ?li M9- 90029 M9- 222--

I'7ordon right M 9- 23 ))1 M 9- 222 12 099

Russell =ernandes M9- M 9- 9) 9 M9- M 9- 222 - 2

BRT - Main responsibilities

• 'he main responsi,ilities o the %C&C are to8

@ndertake ,usiness recovery activities in line ;ith ,usiness recovery in

coordination ;ith %C&C

Escalate issues promptly and in accordance ;ith the %C& incident

escalation process and

&anage ,usiness resumption under the direction o the %C&C

Page 16 of 64


18/64


19/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

14., Custome!s

• /ist to include customers< ;ho are the maor customers that ! ;ould need to contact to

keep them updated in case o ,usiness interruption. 'he list is maintained ,y %C&C !eadand kept up to date.

14.0 Se!vice P!ovie!s@Veno!s

• /ist to include ervice roviders 4 5endors that ! ;ould need to contact to keep them

updated in case o ,usiness interruption. 'he list is maintained ,y %C&C !ead and keptup to date.

14.3 Em)$o"ee C$$ T!ee 8ist

• 'he call tree list is a key communication tool or ,usiness continuity operations. 'his list is

important or the &anager and their alternate to have stored in their mo,ile phone< and tokeep a hard copy list at home in a secure location at all times. 'he list is maintained ,y%C&C !ead and kept up to date.

Page 18 of 64


20/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

11. Recove!" - Recove!" P$n

Recovery is the return to ! pre(emergency condition. erorming critical activities assoon as possi,le ater a critical incident is ! primary ocus.

1%.1 Disste! Recove!" Site >DRS?

6R ?ddress #insert address o the 6R$6R /ocation #Insert the location map of the DRS)

Page 19 of 64


21/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

1%.# ene!$ Recove!" P!oceu!e:

Disste! Scen!io Recove!" P$ns

Environmental Risk #e.g.lightning strike<earthquake< lood$

>r

=oreign ?ggression

• hile the threat o a country(;ide disaster is very lo;< ,ut should not ,e

ignored.

• In this scenario< EC declares a disaster and instructs %C&C to prepare a

list o ! key sta ;ho ;ill ,e evacuated outside the country.

• *ey ! sta< determined ,y %C&C< are to ,e evacuated to operate

rom the nearest ! oice #%ahrain 4 @?E$ or other location determined ,ymanagement.

• %C&C< in coordination ;ith the !R @nit< and according to the situation

;ill advise key sta on the assem,ly points and means o transportation.

• Remaining sta are to ,e evacuated to the nearest country or to their

home countries. ?rrangements or their logistics shall ,e handled ,y the !R@nit #or more details please reer to the eople &anagement lan$.

• >site ,ackup tapes shall ,e sent ;eekly to a sae location in %ahrain 4

@?E that contains a copy o company(;ide systems and data.

Equipment =ailure Risk#e.g. hard;are< internetand communication<

!5?C< ire$

>r

!uman Risk #e.g.sa,otage< terrorism< ,om,threats$

hen a disaster happens in ?l !amra >ices< all systems at this site< ;ill,ecome completely non(unctional or more than hours. 'he ollo;ing sequenceo steps must ,e ollo;ed to;ards recovery8

• In this scenario< EC declares a disaster and instructs %C&C to prepare a

list o ! sta ;ho operates rom dierent ! site.

• I the !ead >ice ,uilding or computer room is completed destroyed<

%C&C must declare a disaster in order to implement the plan to recover andoperate rom the 6R in u,han

• 'he u,han site is suiciently equipped to ,e a semi(;arm site. In

addition< Huorto,a site has suicient oices to accommodate part o ?l!amra support sta.

• Entire ,ackup o ?l !amra >ices replicate through the u,han site

through the E&C data domain

• %C&C decides on the list o sta to operate rom the u,han and

Huorto,a• 6esign team ;ill continue to operate rom u,han oices<

• ta ;ho largely depends on ! computer systems #I'(?6 ervices<

Citri"< /ync ervices< =ile ervices< +e;orma< 6eltek< !R+E'$ ;ill ,emoved to u,han site

• >ther support ! sta may operate rom Huorto,a or rom home as

decided ,y the %C&C

• %C&C< in coordination ;ith the !R @nit and %R's< shall arrange means

Page 20 of 64


22/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

Disste! Scen!io Recove!" P$ns

o transportation ;hen needed

• Restoring data at u,han site can then commence. /atest ,ack(ups o

data and systems ;ill ,e restored

• I' recovery team ;ill ,ring ,ack the most ;anted services irst< so that

the ,usiness ;ill ,e online and can recover the other services one ,y one

• 'he recovery time depends on the siBe o data. Entire system restore ;ill

take a minimum o t;o hours or each system and

• ?ll remaining systems equipment ;ill have to ,e ordered and thereore

their recovery times ;ill ,e varia,le #up to one months$.• .. same recovery plan applies in case the disaster occurs at u,han

ite ;ith the only dierence< that sta depending on the net;ork ,asedsystems ;ill ,e moved to operate rom ?l !amra oice.

@tility =ailure Risk #e.g.electricity< ;ater$

• ince u,han site ,uildings already have an electric generator< thereore

all systems ;ill ,e unctional rom this site. =or more details reer to the %@s,usiness recovery plans.

!uman Risk #e.g. virus<hackers$

• ! has &aintenance Contracts and ervice /evels ?greements ;ith

escalation procedures or all vendors o >perating< ?pplication< +et;ork and6ata,ase systems. ?ll pro,lems ;ill ,e attended to initially ,y the !As orin(house I' sta. /ocal vendor support ;ill ,e sought as required. I thepro,lem cannot ,e resolved< then out(o(country support in the regional

centres or at !ead >ice in the home country o the vendors must ,e sought.Initially< remote access to the !As systems ;ill ,e provided or and i thepro,lem cannot ,e resolved< then a relevant e"pert may ,e lo;n to *u;ait.

• In the meantime< transactions have to ,e kept pending or done on an o(

host mode. 'his ;ill synchroniBed ;ith the server ;hen systems resumes.

• ame as the contingency plans o the environmental threat.

+otes8

• Relevant data must ,e loaded onto the system rom the latest ,ack(ups ater the

disaster happens.

• 6ata in the semi(;arm 6R can ,e up to 2) hours old #depending on the disaster

time$.

Page 21 of 64


23/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

1%.% Recove!" Re9ui!ements

11.%.1 St Resou!ces

BusinessUnit

8eve$Num&e! o St Neee.

Tem Positions Neee05!s

#(5!s

#2%"s

*"s

#2%7ee

1mnt5


ta #managerial$ ) ) ) ) ) )

ta #other$ 2 2 2 2 2 2

6esign

ta #managerial$ ) ) ) ) ) )

ta #other$ 12 12

Commercialta #managerial$ 2 2 2 2 2 2

ta #other$ 1 1 1 1 1 1

&< =& : %6ta #managerial$ 9 10 1- 1-

ta #other$ ) - -

I&ta #managerial$ 2 2 2 2 ) -

ta #other$ 2 2 2 2 ) -

=inanceta #managerial$ 0 0 0 1 1 1

ta #other$ 0 0 2 3 3 )

I'

ta #managerial$ 0 0 0 3 3 -

ta #other$ ) - 10 11

!Rta #managerial$ 1 2 2 2 3 3

ta #other$ 1 )

&arketing:Communications

ta #managerial$ 1 1 1 1 1 1

ta #other$ 1 1 1 1 1 )

'otal 43 50 57 66 85 94

11.%.# o! Sttions Net7o!e PCs Neee

BusinessUnit

o!sttions Net7o!e PCs Access to Net7o! P!inte!s05!s

#(5ss

#2%"s

*"s

#2%7ee

s

1mont

5

05!s

#(5ss

#2%"s

*"s

#2%7ee

s

1mont

5

05!s

#(5ss

#2%"s

*"s

#2%7ee

s

05!s

Constructionupervision ) 10 11 13 13 - 10 11 13 13 0 3 3 3 3 0

6esign 11 11 11 12 1 1 11 11 11 12 1 1 1 1 1 1 1 1

Commercial 3 3 3 3 3 3 3 3 3 3 3 3 0 1 1 1 1 0

&< =& : %6 ) ) ) 9 - 9 1- 1- 1- 1 1 1 2 2 1

I& ) ) ) ) 10 ) ) ) ) 10 ) ) ) ) 10

Page 22 of 64


24/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

=inance 0 0 2 2 2 2 0 0 2 ) ) - 0 0 1 1 1 0

I' 0 0 0 3 1) ) - 10 1) 0 0 0 0 0 0

!R 2 ) - 2 3 3 ) - 1 1 1 1 1 1

&arketing andCommunication

0 0 0 0 0 0 0 0 0 0 0 0 ) ) ) ) )

'otal 2

833

39

48

64

73

34

41

49

60

74

82

11

15

16

17

21

19

11.%.% P!inte!s6 P5otoco)ie!s Fx Mc5ine

BusinessUnit

P5otoco)ie!s Fx Mc5ines Te$e)5ones0

5!s

#(

5ss

#2%

"s

*

"s

#2%

7ees

1

mont5

0

5!s

#(

5ss

#2%

"s

*

"s

#2%

7ees

1

mont5

0

5!s

#(

5ss

#2%

"s

*

"s

#2%

7ees

1

mont5


0 1 1 3 3 3 0 0 0 1 2 2 1 1 1 2 3 3

6esign 1 1 1 1 1 1 0 0 0 0 0 0 30 30 30 30 100 100

Commercial 0 1 1 1 1 1 0 0 0 0 0 0 3 3 3 3 3 3

&< =& : %6 1 1 1 1 1 1 1 1 1 1 1 1 -

I& 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 3 -

=inance 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1 1 1 2

I' 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 3 -

!R 0 0 0 1 1 1 0 0 0 1 1 1 2 ) -

&arketing and

Communication 0 0 0 0 0 0 1 1 1 1 1 1 0 0 0 0 0 0'otal

3 5 5 8 8 8 2 2 2 4 5 6 4

041

43

45

121

126

11.%.( Sot7!e nees

Business Unit Business P!ocesses A))$iction Nme@ Mou$e Nme RTO


%idding 6eltek< & >ice< >utlook1 day

Recruitment 4 R& 6eltek< & >ice< >utlook 3 days

&:C 4 Reporting 4 Contract

&anagement 4 Invoicing 4 Close out

6eltek< rimavera & >ice<

>utlook

1 day

6esign

6esign rocess 6eltek< & >ice< >utlook 1 day

Reprographics 6eltek< & >ice< >utlook 1 day

%idding and roposals 6eltek< & >ice< >utlook 1 day

upport ervices 6eltek< & >ice< >utlook 1 day

Commercial %usiness ?dvisory 6eltek< & >ice< >utlook 1 day

Company ecretarial 6eltek< & >ice< >utlook 1 day

Page 23 of 64


25/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

Revie; R=Ks 4 Contractual 6ocs 6eltek< & >ice< >utlook 1 day

&< =& : %6

maintenance<6eltek< +e;orma< & >ice<>utlook

2 days

procurement6eltek< +e;orma< & >ice<>utlook

1 day

security services & >ice< >utlook 2 days

I&

H?6eltek< rimavera< & roect<kype< +e;orma or harepoint

1 day

!E ame as a,ove 1 day

Corporate ?airs ame as a,ove 1 day

tatutory ?uthority ame as a,ove 1 day

roect Controls ame as a,ove 1 day

=inance ?ccounting 6eltek< & >ice< >utlook +?

%udgeting : Reporting & >ice< >utlook +?

I'

I' Inrastructure lanning +? +?

Inormation ecurity +? +?

ot;are ?pplication 6evelopment :'rou,leshooting

+? +?

&aintain 6atacentreAs to !ostE"change : &ass torage 6evises

+? +?

!elpdesk @ser End upport : 'raining +? +?

!R ?ll !R.+et< 6eltek< & >ice< >utlook +?

&arketing andCommunication

Internal and e"ternal communication & >ice< >utlook +?

11.%.* Vit$ Reco!s neee

Business Unit Vit$ Reco!s RTO Mei T")e A$te!ntive Sou!ce

Construction

upervision

Contract 6ocuments 3 days erver !ard copy at proectsite

%id 6ocs4R=4'>R 3 days erver !ard copy

Correspondences 1 day erver !ard copy at proect

siteta C5s 2 days erver !ard copy

'imesheets 2 days 6eltek server +one

Contract 6ocuments 3 days erver !ard copy at proectsite

6esign 6ra;ings +? +? +?

peciications +? +? +?

%ills > Huantities +? +? +?

%idding +? +? +?

!istorical 6ata +? +? +?

Page 24 of 64


26/64


27/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

1%.( O PAC=

• I there is damage to the ,uilding or i it must ,e evacuated and operations need to ,e

moved to an alternative location< the F7> ackG emergency kit can ,e picked(up andquickly and easily carried o(site or alternatively stored saely and securely o(site.F7> ackG emergency kit shall include the ollo;ing8

'his %usiness Continuity lan

/ist o employees ;ith contact details J include home and mo,ile num,ers<

and even e(mail addresses. ! may also ;ish to include ne"t(o(kincontact details.

/ists o customer and supplier details. %uilding site plan #this could help in a salvage eort$< including location o

electricity and ;ater shut o points. Evacuation plan.

Insurance company details.

=inancial and ,anking inormation.

!eaded stationery and company seals and documents.

6epartment speciic vital records #contracts< registration license etc.$.

• +otes8

&ake sure this pack is stored saely and securely on(site or o(site #in

another location$. Ensure items in the pack are checked regularly< are kept up(to(date< and are

;orking. It is the responsi,ility o the %R's to determine and maintain any additional

documents necessary or the recovery o their respective %usiness @nits.

Page 26 of 64


28/64


29/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

C!itic$ &usiness )!ocess Biin/

Page 28 of 64


30/64


31/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

1. ?ccess to primary I' systems J ervers 4 Email 4 hared drives 4 6eltek 4 'elephone.

2. ite sta access or timesheet ,ooking #6eltek$.

3. Esta,lish communication ;ith other departments.

). ?ccess to contract documents.

-. Esta,lish communication ;ith proect site sta.

. rinter availa,ility.

Page 30 of 64


32/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

1%.*.# Desi/n

Business Recove!" Tem

Page 31 of 64


33/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

C!itic$ &usiness )!ocess Desi/n P!ocess 2 P!e)!tion Conce)t Desi/n

rocess o;ner ?rchitecture tudio

erson#s$ responsi,le orrecovery activities

imon 6ennison and ?min OaBeyeri

?lternate person#s$ Rio Qandri

Recovery time o,ective ithin hours

Recove!" Activities

1. 'erms o Reerence and Client %rie

2. cope o ork

3. resentation made previously to the client.

). chematic 6esign and Concept Reports

C!itic$ &usiness )!ocess Desi/n Deve$o)ment

rocess o;ner ?rchitecture roduction


?drian atson and ?ndrBe %ohdano;icB #%oris$

?lternate person#s$ ?,ir El Chami and iotr Ro,ert *acorByk


Recove!" Activities

1. Client ?pproved Concept /ayouts

2. 6esign 6evelopment 6ra;ings #all 6isciplines$

3. Coordination 6ra;ings< +otes< ketches< etc.

). 6esign Calculations

-. erspectives

C!itic$ &usiness )!ocess Deti$e Desi/n.




Page 32 of 64


34/64


PROCEDURE NUMBER:

EFFECTIVE DATE:



Recove!" Activities

1. 6etailed 6esign 6ra;ings #all 6isciplines$

2. =inal Coordination 6ra;ings< +otes< ketches< etc.

3. 6etailed 6esign input rom pecialists

). peciications and %ill o Huantities

-. erspectives

. =inal 6esign Report

C!itic$ &usiness )!ocess Tene! Documenttion.






Recove!" Activities

1. 'ender 6ra;ings #all 6isciplines$2. peciications and %ill o Huantities

3. 6esign Calculations

). 6esign Close >ut Reports

C!itic$ &usiness )!ocess Issue o! Const!uction @ Cont!ct






Recove!" Activities

1. Issued or Construction4Contract 6ra;ings #all 6isciplines$

2. peciications and %ill o Huantities

3. 6esign Calculations

). 6esign Close >ut Reports

Page 33 of 64


35/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

1%.*.% Comme!ci$ Business Unit


Page 34 of 64


36/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

C!itic$ &usiness )!ocess Business Aviso!"

rocess o;ner /ee kinner


/ee kinner

?lternate person#s$ heikh ?si &ahmood


Recove!" Activities

1. >,tain the inormation rom 6eltek or rom Individuals

2. @se the inormation and present a solution or strategic decision on the ;ay to proceed

3. peak to the CE>4%oard &em,ers4R6As and present the inormation required

C!itic$ &usiness )!ocess Com)n" Sec!et!i$

rocess o;ner /ee kinner


/ee kinner

?lternate person#s$ heikh ?si &ahmood


Recove!" Activities

1. Recover emails and access to company data

2. @se this inormation to administer the company.

3. peak to the CE>4%oard &em,ers4R6As and present the inormation required.

C!itic$ &usiness )!ocess Cont!cts Mn/ement

rocess o;ner heikh ?si &ahmood


heikh ?si &ahmood

?lternate person#s$ /ee kinner


Page 35 of 64


37/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

Recove!" Activities

. Receive Contracts and 6ocuments rom personal seeks assistance

. roduce a report or give guidance into the contractual commitments4issues presented.

9. /iaise ;ith various departments to ensure issues are resolved.

Page 36 of 64


38/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

1%.*.( PM@FM@BD Business Unit


C!itic$ &usiness )!ocess P!o'ect Mn/ement

rocess o;ner Qasmeen ?l hatti


Qasmeen ?l hatti

?lternate person#s$


Recove!" Activities

1. 6etermine the roect &anagement lan

• Identiy proect ,rie

• /ist cope o ervices

• /ist proect tages4hases

•

Identiy roect 6elivera,les• ?pprove the %udget ,ase line

• Esta,lish roect rogram

• Esta,lish proect >rganiBation and Responsi,ility &atri"

• Esta,lish ?uthorities rocess =lo; Chart

• Identiy Communication matri"

2. ?rrange proect *ick J o meeting

Page 37 of 64


39/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

3. Identiy proect team #internal4e"ternal$). Ensure commercial arrangement are in place #Client4! and or !4u,(consultants$

-. Conduct proect coordination meetings

. /ogistics ,eing coordinated or proect delivera,les

. rovide monthly proect revie;s or management4client

. Huality management

9. Recourse management

10. Risk management

11. Client &anagement 4atisaction

12. =inancial management # timely ,illing and cash collection< ,onds< insurances$

13. rovide proect close(out report

C!itic$ &usiness )!ocess Fci$ities Mn/ement

rocess o;ner &ostaa 6aha,


&ostaa 6aha,

?lternate person#s$ ?tikur Rahamn


Recove!" Activities

=or access cards and other maintenance8

1. In case o any equipment4 security card ailure( contact the concerned vendor 2. >nce the vendor is at the location< ensure that the maintenance is done3. ign o on the o, card). 7et the payment approved ,y one o the 6irectors-. ?rrange ;ith =inance to pay the vendor

=or purchase81. Receive the request rom concerned department2. Check that the request is approved as per authority matri"3. Contact vendor or purchase). I purchase can ,e carried in car< go to vendor to carry ,ack the purchase in car -. I not< send company driver to pick up purchase. rovide ,ill to =inance or payment

C!itic$ &usiness )!ocess Business Deve$o)ment

rocess o;ner ?,,as &ayahi

Page 38 of 64


40/64


41/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

1%.*.* Inte/!te Mn/ement S"stem


Page 40 of 64


42/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

C!itic$ &usiness )!ocess Gu$it" Assu!nce

rocess o;ner %arry =autley


%arry =autley

?lternate person#s$ !e,a 6emerdash


Recove!" Activities

H? 'raining

1. Contact Radha to esta,lish training session time2. Revie; training material ,eore session3. Conduct session). >,tain =eed,ack =orms-. ?nalyse eed,ack and revision training material accordingly. @pdating and re(upload revised training material on the Intranet

teps or auditing

. Revie; audit programme. Check ;hat audit needs to ,e completed.9. 6iscuss ;ith !E &anager or enior H?4!E >icer regarding audit requirements10. Revie; checklist requirements11. Inorm proect and relevant personnel o audit and date. #?udit notiication orm$12. ?ttend audit E"plain to ?uditee the audit requirements13. E"plain audit indings to ?uditee once audit completed1). Return to oice and complete audit report and send report to the relevant persons.1-. =ile audit report and any reerence documents into the ' drive under HE then audits.1. ?ttendance to meetings1. I asked to attend meetings revie; the last meeting minutes.

1. ?ttend meeting e"plaining ;hy you are attending.19. 'ake notes during meeting and any questions you have the ans;er or please do.20. rite a ,rie notes regarding the meeting to pass onto the relevant person

C!itic$ &usiness )!ocess ;e$t5 Set" Envi!onment >;SE?

rocess o;ner te;art Cripps


te;art Cripps

Page 41 of 64


43/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

?lternate person#s$ !e,a 6emerdash


Recove!" Activities

!E ?uditing1. Revie; audit programme2. Issue ?udit num,er as per audit programme.3. Check ;hat audit needs to ,e completed.). 6iscuss ;ith %arry regarding audit requirements-. Revie; checklist requirements. Inorm proect and relevant personnel o audit and date. #?udit notiication orm$. ?ttend audit E"plain to ?uditee the audit requirements. Conduct ite inspection and revie; Contractor !E documentation9. E"plain audit indings to ?uditee once audit completed10. Return to oice and complete audit report and send report and photographs taken during !E 'our to

the relevant persons.11. =ile audit report and any reerence documents 4 photographs into the ' drive under HE then audits.

!E 'raining1. Contact C6 and Resident Engineer to esta,lish training session time2. Revie; training material ,eore session3. 'raining &odules stored in I&). Ensure ?ttendance sheet is completed and signed ,y the Instructor.-. Ensure eed,ack =orms are completed ,y attendees.. ?nalyse eed,ack and revision training material accordingly

. @pdating and re(upload revised training material on the Intranet. =or;ard attendance sheet and eed,ack orms to Radha or inclusion in personnel documents.

!E tatistics

1. C6 to ensure all !E tatistics are returned ,y the Resident Engineers ,y the 3rd o each &onth2. eekly !E Checklists to ,e su,mitted ,y every unday rom the Resident engineer.3. tatistics to ,e logged on e"cel sheet in HE =older named tatistics.). 6etails or !E section o !E &anagement report to ,e su,mitted to /ucy,ell

C!itic$ &usiness )!ocess Co!)o!te Ai!s

rocess o;ner i,y 7eorge


i,y 7eorge

?lternate person#s$ &aura Rodrigues

Recovery time o,ective ithin ) hours

Recove!" Activities

Page 42 of 64


44/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

Co!)o!te Soci$ Res)onsi&i$it"1. CR program4initiatives are documented under I&4CR =older #electronically$ and also in the CR

=ile #as hard(copy$.2. Reer to the CR lan 201-(201 and particularly the schedule or the year.3. Revie; the eriodic @pdate Report to kno; the current status.). Coordinate ;ith the proect leads4sponsors mentioned in the proect charters or the planned initiatives.-. =acilitate the ne"t CR initiative as per the schedule4plan.. Coordinate the event and post(event activities in coordination ;ith the proect sponsor< proect lead<

I& 6irector< &arketing : Internal Communication teams and any e"ternal parties associated.. repare ummary Report o the concluded CR initiative ( as per the DsampleD attached #LL$< along

;ith the relevant attachments #supported ,y the proect team$.. @pdate the eriodic @pdate Report and send it to I& 6irector.9. @pdate the CR progress report or the &onthly &anagement Reporting or I&< and or the I&

teering Committee meeting.10. =acilitate CR related actions and4or comments rom the &onthly &anagement Report and I&

teering Committee.11. >n a quarterly ,asis< revie; and update the CR ,udget ;ith the I& 6irector.12. %eore H3< propose the ne"t yearKs CR ,udget in line ;ith the CR lan #201-(201$ in the I&

teering Committee &eeting or CE>Ks revie; and su,sequent approval.13. %y >cto,er(+ovem,er< ollo;(up and ensure CR ,udget or the su,sequent year is signed(o.1). Coordinate ahead o time #2(3 months$ ;ith everyone on the CR proect team or the ne"t initiative.1-. rovide a ummary CR Report or the CE> to present in the artnerKs ?nnual %oard &eeting

regarding the achievements o the year and initiatives planned or the ne"t year.

Business Im)!ovement1. %I program4initiatives are documented under I&4%I =older #electronically$ and also in the %I =ile #as

hard(copy$.2. Reer to the %I lan4>pportunity 'racker 201- and the proect charters.3. Revie; the eriodic @pdate Report #discussed during &onthly Change %oard$ to kno; the current

status.). chedule the &onthly Change %oard meeting at least 2 ;eeks in advance< and circulate the agenda at

least 1 ;eek in advance.-. Communicate ;ith the proect leads4sponsors mentioned in the proect charters to get a periodic

update regarding the planned initiatives #or discussion during the Change %oard &eeting$.. I& may ,e required to acilitate the proect sponsors in creating drat proect charters.. ?s agreed during the Change %oard &eeting< I& may oer to acilitate supporting some %I proects<

till the intended proect lead takes(over.. I I& is involved in managing %I proects< the designated personnel to coordinate the %I activities in

close coordination ;ith the proect sponsor< proect steering committee< proect team and keep I&6irector posted at all times.

9. repare minutes o the Change %oard meeting and circulate to all attendees or necessary action.10. @pdate the %I lan4>pportunity 'racker on a monthly ,asis #or earlier< as inormation ,ecomes

availa,le$.11. @pdate the %I Report or the &onthly &anagement Reporting or I&< and or the I&

teering Committee meeting.12. =acilitate %I related actions and4or comments rom the &onthly &anagement Report and I& teering

Committee.13. >n a quarterly ,asis< revie; and update the %I ,udget ;ith the I& 6irector.1). %eore H3< propose the ne"t yearKs %I ,udget ,ased on the %I lan #or the su,sequent year$

during the I& teering Committee &eeting or CE>Ks revie; and su,sequent approval.

Page 43 of 64


45/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

1-. %y >cto,er(+ovem,er< ollo;(up and ensure %I ,udget or the su,sequent year is signed(o.

1. rovide a ummary %I Report or the CE> to present in the artnerKs ?nnual %oard &eeting regardingthe achievements o the year and initiatives planned or the ne"t year.

C!itic$ &usiness )!ocess Sttuto!" Aut5o!it"

rocess o;ner 6e"ter 6avid


6e"ter 6avid

?lternate person#s$ /ucy,el 6enaque


Recove!" Activities

• 01 &onth. Contact all Regional tatutory ?uthority &anagers #?&$ and discuss previous months

permits

• 6iscuss any roects at RiskA or /ate ermitsA and steps or corrective action

• ?& to update the regional permit sheets in 8S/iveS?001Sermit Reports older

• @pdate ! ermit tatus +otes a,out regions at '8SI&S1.&CS? 6ocsSermit Reports

• Conirm ;ith team that ? report is updated

• 0-(0 &onth. Report any issues to I& 6irector.

• Revie; and discuss ;ith ?& any ermit procedures or change request.

• 1-(20 &onth. Carry out random audits on permit documentation in proect olders

C!itic$ &usiness )!ocess P!o'ect Cont!o$s

rocess o;ner ?na >liveira< Ooseph Oo,


?na >liveira< Ooseph Oo,

?lternate person#s$ /ucy,el 6enaque


Recove!" Activities

&onthly roect Controls 6elay Report1. 7enerate reports ;ith a list o live proects rom 6eltek or each territory #Ino Center4roects4click on

the older icon #right side$$2. /ist all ! live proects and separate them ,y region #e"cel sheet$3. Identiy the roect &anager responsi,le or each proect

). Identiy the sector o each proect #%ulding 6esign< Inra or C6$-. Check and identiy i the roect Revie;4ite Revie; has ,een completed on 6eltek or each proect

Page 44 of 64


46/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

. Check and identiy i the &4& has ,een produced or each proect. Check and identiy i the roect Closeout Report has ,een produced or each proect. Check and identiy i each proect has a signed and ,aselined cost plan9. Check and identiy i each proect has a signed< ,aselined and updated programme10. Check and identiy i the 6esign Revie;s have ,een conducted as per programme

&onthly roect Controls Report1. 7enerate reports ;ith a list o live proects rom 6eltek or each territory #Ino Center4roects4click on

the older icon #right side$$2. Create a report in ord document or each ! live proect.3. In ection 1 J Cont!ct Deti$s8 Include Contract 6etails or the proect #original contract< 5> ees<

and total amount$). In ection 2 J P!o'ect Sc5eu$e8 Include ,aseline start and inish dates< and insert ,aselined and

updated programme produced or the proect. I the programme is not in accordance ;ith rocedureor chedule Controls< make comments to identiy4descri,e the pro,lems.

-. In ection 3 J P!o'ect Revie78 Check each roect Revie; ta, on 6eltek and include on the report

screenshots o pro,lems ound. ?dd mark(ups and make comments to identiy4descri,e the pro,lems.. In ection ) J P!o'ect P$nnin/8 Check roect lanning ta,s on 6eltek #/a,our< E"penses and

Consultant$ and include on the report screenshots o pro,lems ound. ?dd mark(ups and make

comments to identiy4descri,e the pro,lems.

*Is ( I& &onthly &anagement Report1. 7enerate reports ;ith a list o live proects rom 6eltek or each territory #Ino Center4roects ( click on

the older icon #right side$$2. /ist all ! live proects and separate them ,y region #e"cel sheet$3. Check and identiy the status o each proect on the system #?ctive or Inactive$. >nly the ?ctive

proects should ,e checked to generate this *I report.

4. PMP C5ec ( Identiy the proects that should ,e producing4revising or should have inaliBed a &during the present month. =rom this list< consider QE or those that have issued a version o the &

on time and +> or those that have not issued a version o the & on time. 'he time to issue the irst

revie; o the & is ;eeks ater the commencement date o the proect< and the time to issue ne"t

revie;s is 2 ;eeks ater the & receives a commented version rom I& team.

5. SMP C5ec ( Identiy the proects that should ,e producing4revising or should have inaliBed a &during the present month. =rom this list< consider QE or those that have issued a version o the &

on time and +> or those that have not issued a version o the & on time. 'he time to issue the irst

revie; o the & is ;eeks ater the commencement date o the proect< and the time to issue ne"t

revie;s is 2 ;eeks ater the & receives a commented version rom I& team.

6. Mont5$" P!o'ect Revie7s Conucte C5ec J >n the Ino Center section in 6eltek< go to roectRevie; ta,4/ist 5ie;4elect =ields J select R+o< roect and Revie; 6ate only J click >*. >nce the

list o roect Revie;s conducted is opened< check i each proect conducted a roect Revie; on thepresent month.

7. Mont5$" Site Revie7s Conucte C5ec J >n the Ino Center section in 6eltek< go to ite Revie;ta,4/ist 5ie;4elect =ields J select R+o< roect and ite Revie; 6ate only J click >*. >nce the list

o ite Revie;s conducted is opened< check i each proect conducted a ite Revie; on the present

month.

8. Mont5$" En o St/e Revie7s Conucte C5ec J >n the &aster chedule #,aseline programme$<check ;hich proects should ,e conducting an End o tage Revie; on the present month. =rom this

list< consider QE or those that have conducted the End o tage Revie; ,eore su,mitting the

Page 45 of 64


47/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

delivera,les package to the client. Consider +> or those that have not conducted the End o tageRevie; ,eore su,mitting the delivera,les package to the client. I the proect is delayed and still did

not su,mit the package it ;as supposed to su,mit on that month< ;ait until the package is su,mitted to

include the proect on the report.

9. Desi/n C$oseout Re)o!t Conucte C5ec ( >n the &aster chedule #,aseline programme$< check;hich proects should ,e producing a 6esign Closeout Report on the present month. =rom this list<

consider QE or those that issued the roect Closeout Report until 21 days ater the completion o

the proect #end date$. Consider +> or those that have not issued the roect Closeout Report until

21 days ater the completion o the proect.

Page 46 of 64


48/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

1%.*.+ Finnce


Page 47 of 64


49/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

C!itic$ &usiness )!ocess Accountin/

rocess o;ner ivakumar 5


6e,it 6utta ( ?noop * ( =ahad irkhot

?lternate person#s$ hen,agavalli


Recove!" Activities

1. ersonal aety

2. ?ccess permit to the >ice

3. ?ccess to the /?+

). /ogin to the C and 6eltek ot;are

-. Run a 'rial %alance at Consolidated : Regional level save it in e"ternal hard drive.

. Run ?R ?geing Report and copy it in e"ternal hard drive.

. Run ? ?geing Report and save it in e"ternal hard drive.

. Run Consolidated and Regional 7/ or at least current year and save it e"ternal harddrive.

9. aeguard %ank Reconciliation =iles

C!itic$ &usiness )!ocess Bu/etin/ n Re)o!tin/

rocess o;ner hen,agavalli


Chetan ( *arthikeyan rinivasan

?lternate person#s$ ivakumar 5


Recove!" Activities

1. ersonal aety2. ?ccess permit to the >ice

3. ?ccess to the /?+

). /ogin to the C : 6eltek ot;are

-. Run a Consolidated and Regional 'rial %alances and save it in a sae location.

. aeguard the previous monthly reports #consolidated< divisional< regional anddepartmental reports$

Page 48 of 64


50/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

1%.*., Ino!mtion Tec5no$o/"


Page 49 of 64


51/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

Critical ,usiness process Inrastructure

rocess o;ner !akim %hungra;ala


!akim %hungra;ala

?lternate person#s$ >sama Rashidi


Recove!" Activities

1. =acilities to ensure ,asics such as Electricity : ?ir(conditioning are availa,le

2. Recovery data rom e"ternal site storage

3. ?ll &icrosot ervices to ,e reconigured

). ?ll ile share servers to running

-. ?pplication erver to ,e accessi,le

. Coniguration : Implementation

. 'esting o a,ove services

C!itic$ &usiness )!ocess Se!vice Des

rocess o;ner Russell =ernandes


!akim %hungra;ala : &ostaa 6aha,

?lternate person#s$ 7eorgee &alayil


Recove!" Activities

1. =acilities to ensure ,asics such as Electricity : ?ir(conditioning are availa,le

#. Inrastructure to conirm server : net;ork accessi,le

%. ?ctivation o &anageEngine

(. Receive customer request or I' intervention

*. CategoriBe request /og the request on &anageEngine

+. Issue incident ticket num,er

,. &onitor incident action and closure on &anageEngine

0. @pdate log ;ith action 4 resolution

3. Close incident once actioned

Page 50 of 64


52/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

C!itic$ &usiness )!ocess A))$iction

rocess o;ner 'homas 7race


!akim %hungra;ala

?lternate person#s$ Raymund 5asques


Recove!" Activities

1. Inrastructure to conirm server : net;ork accessi,le

2. Recovery o ,ackup data rom E&C storage to 6eltek servers at data center

3. 'est accessi,ility

Page 51 of 64


53/64


54/64


55/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

C!itic$ &usiness )!ocess Em)$o"ee Se!vices

rocess o;ner &ohammed 7house ?li


&ohammed 7house ?li

?lternate person#s$ heik iraudin 4 &atheen ?hmed


Recove!" Activities >&ain steps to ,e ollo;ed to deliver service$

1. 7athering all important contacts o employees required in emergency

#. Ena,ling ;ork rom home or oice environment or our responsi,le sta to ,ook tickets< toactivate mo,ile lines< to arrange accommodation and to arrange Insurances as required.

%. Immediate ;ork should ,e started on arranging the %usiness4 ersonal4 &o,iliBation 5isaAs inemergency as required ,y ,usiness.

(. 'ransportation activities needs to ,e take care or important sta

*. !r.+et and 6eltek systems should ,e ena,led to ;ork on ayroll activities.

C!itic$ &usiness )!ocess Em)$o"ee Dt Mn/ement T!inin/

rocess o;ner Radha Ramasamy


Radha Ramasamy

?lternate person#s$ riya 7onsalves #!R ?dministrator$< Contact ( --1323<priya.gonsalvesPsshic.com4 priyagonBPgmail.com

Recovery time o,ective ithin 2(3 days

Recove!" Activities >&ain steps to ,e ollo;ed to deliver service$

1. Retrieve hard copy iles

2. ystem entry details pertaining to hr.net can ,e shared ;ith ayroll team

3. &anual timesheets validation or payroll

). revious month payroll ile the list o ne; oiners can ,e provided.

C!itic$ &usiness )!ocess Rec!uitment n Resou!ce Mo&i$iHtion

rocess o;ner 7ary Checketts


7ary Checketts

?lternate person#s$ unny /ascuna

Page 54 of 64


56/64


57/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

1%.*.3 M!etin/


Page 56 of 64


58/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

C!itic$ &usiness )!ocess P!ess Re$ese

rocess o;ner Richard /ira


!ala 'ayli

?lternate person#s$ a,a a,u hana,


Recove!" Activities

1. In case o an incident that has a direct impact on one o more o our clients< an e"ternalcommunication might need to ,e addressed directly to the client rom the R6 or the proect director inquestion.

2. Incident that has a general impact on our reputation and possi,le uture relationships ;ith utureclients< needs to ,e communicated to the press and media platorms through an oicial press releasestating and descri,ing ;hat happened and ho; the company is planning to react4manage damage.

C!itic$ &usiness )!ocess Int!net

rocess o;ner uBan aadi


!ala 'ayli

?lternate person#s$ CE>As >ice4I&4!R


Recove!" Activities

1. Issue sta communication on intranet should the server still ,e unctioning

2. @pdate sta ;ith latest developments< progress< measures taken at a certain incident.

C!itic$ &usiness )!ocess St communictions

rocess o;ner !ala 'ayli


!ala 'ayli

?lternate person#s$ uBan aadi


Recove!" Activities

Page 57 of 64


59/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

1. Emergency Contact /ist

Create an Emergency contact list that includes8

• !ome hone

• ?lternate &o,ile

• ersonal E‐mail

• =amily4Emergency Contact Inormation

2. etup an ?lert +otiication rogram #the Employee ?pp on cell phones$

• E"plain urpose

• 'est Regularly

• @pdate regularly ;ith any changes to the organiBation

• 'rain +e; !ires

Page 58 of 64


60/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

1#. Re5e!se6 Mintin n Revie7

• It is critical that ! rehearse this %C& plan to ensure that it remains relevant and useul.

'his may ,e done as part o a training e"ercise and is a key actor in the successul

implementation o the plan during an emergency.

• %C&C must also ensure that they regularly revie; and update this plan to maintain

accuracy and relect any changes inside or outside the ,usiness.

• 'he ollo;ing points may help8

? training schedule must ,e prepared or all people ;ho may ,e involved in

an emergency at the site. ay attention to sta changes.

It is ,est to use sta titles rather than names.

I you change your organiBational structure or suppliers4contractors this

must ,e amended in your plan. ?ter an event it is important to revie; the perormance o the plan<

highlighting ;hat ;as handled ;ell and ;hat could ,e improved upon ne"ttime.

Page 59 of 64


61/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

1%. Annexu!es

1%.1 SS; Com)ute! S"stems

• AD Se!vices: ?6 is used or centraliBed access control. Currently in premise< ho;ever

6C ;ill initially ,e put in the cloud.

• Cit!ix: Citri" is used mainly or remote user access to the ! intranet.

• 8"nc Se!vices: @sed or colla,oration ,et;een users and or conerence meetings.

• Ne7o!m: roect Inormation Control.

• De$te: ER and time management.

• ;RNET: !RI or control o Employee Records.

1%.# Business Recove!" C5ec$ists

• In addition to overseeing the recovery o ,usiness critical activities< the ,usiness unit

recovery team leader should perorm the tasks set out in the checklists provided ,elo;.

BRT 8ee!:

Initi$ Actions

Ensure all appropriate Eme!/enc" Res)onse tasks have ,een completed ;here necessary

Receive notiication o incident4crisis rom BCMC n @ o! BCMC coo!into!.

Conirm invocation o the Business Recove!" Tem and the recovery location or your department;ith the BCMC.

Receive status ,rieing rom BCMC o! BCMC coo!into!.

@pdate the BCMC ;ith any additional status inormation. Conirm the saety o your people i possi,le

%egin an Event 8o/ and keep it updated regularly

Conirm the timerame or the ne"t BCMC ,rieing

Page 60 of 64


62/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

BRT 8ee!:

Initi$ Actions

Communicate ;ith your Business Recove!" Tem. 7ive them immediate instructions to clariy theollo;ing8

– aety o sta

– ho ;ill go to the %C& recovery location J consider transport requirements and

personal circumstances o sta

– ork in progress at the time o the incident J use the ork in rogress Checklist inthe 'ools section

– /ost or inaccessi,le vital records #hard copy iles< etc$ team mem,ers.

%rie c!itic$ )!ocess o7ne!s as soon as possi,le. Ensure the ollo;ing is contained in the ,rieingas a minimum8

– ? update on the incident4crisis to date

– aety o sta update

– Immediate actions or people to complete

– 'iming and method o the ne"t update.

/iaise ;ith the %C&C to conirm arrangements or the relocation o critical sta to the %C& site.Conirm the ollo;ing8

– +ames o those relocating to the %C& site

– hen the alternative site ;ill ,e availa,le

– /ogistics #transport etc$

– ersonal implications #childcare< commuting time etc$

&anage any !R issues as they arise< seeking support rom the BCMC as required.

Continue to communicate ;ith all sta< including those not directly involved in the recovery eort

On/oin/ Actions

Continue to liaise on a regular ,asis ;ith the BCMC.

Conirm the relocation o critical sta to the %C& site. Escalate any relocation issues to the BCMC asnecessary.

Continue to update the BCMC on a regular ,asis as requested< e.g. every ) hours. Ensure all

Page 61 of 64


63/64


PROCEDURE NUMBER:

EFFECTIVE DATE:

BRT 8ee!:

Initi$ Actions

communication is cascaded to the ;hole department via Business Recove!" Tem mem,ers.

Briefings should take place with all staff on a daily basis as a minimum

Briefings should include those not directly involved in the recovery effort

&onitor the recovery o critical processes4unctions ensuring this is accomplished in a timely andprioritiBed manner

Use the Summary !ecove!" plan information and the work in progress checklists to assist youwith the process.

&anage any !R issues as they arise< seeking support rom !R.

6iscuss the recovery o non(critical processes perormed ,y your %usiness @nit ;ith the BCMC.'hese non(critical processes should ,e recovered ater 1 month unless the %C&C advise other;ise.

Page 62 of 64


64/64

Documents

Business Continuity Management Plan Version 1.0