Operations of

BTS Key Management1

Introduction to Project CITADEL

This policy is established in order to maintain access to facilities while safeguarding the Base Transceiver Station (BTS)’s safety & security, protecting the most important property of the Grameenphone and avoiding potentially significant costs due to theft, vandalism, or excessive rekeying of locks.

The systematic control of locks and keys is one of the most important components of this security program. Without proper key control, locks provide little deterrence to illegal or unauthorized entry into a BTS facility.

Successful lock and key control requires the efforts of several departments of GP, including ;

Security & Risk Management : Process development, Implement, Smooth operation, Audit to maintains the integrity of the key management system.

Depts. of Networks : Comply with agreed process, Ensure accountability, Suggest for development of maintaining proper key assignment and being financially responsible for the cost of keys control.

Individual SCs & Vendors : Who safeguard assigned keys. Comply with process, Ensure strict accountability, Penalty clause.

2

3

Objectives of Project CITADEL

1. Increase the security access level of padlocks & keys.

2. Ensure proper security level of access into BTS sites.

3. Allow any person to use the lowest profile key for his need.

4. Efficient control over key purchase & usage.

5. Use numeric code in lieu of alphabetic letter to secure the accessibility & coding.

6. Develop a single point interface (SRM) for purchase & handover of Locks and Keys.

7. Keep records of all the transactions of locks & keys internally and externally.

8. Reduce the vulnerability of BTS sites due to key lost or unauthorized access to the premises.

4

Master Keying System

Regional Grand Master Key (RGMK)

Sub Center Master Key (SCMK)

D. Generator Room Key (DGK)

BTS Room Key (BTSK)

HO Key (HOK)

5

Condition before Implementing Project CITADEL

ABLOY CLASSIC PROFILE

GGMK

Regional GMK Security Level-1

Security Level-2

6

Condition after Implementing Project CITADEL

ABLOY PROTEC PROFILE

GGMK

Regional GMK

Sub Center MK

BTS Room

Security Level-4

Security Level-3

Security Level-2

Security Level-1

D/G Room ISS House Owner

BR Eng.

7

Proposed Profile Layers for Project CITADEL, P-3

ABLOY PROTEC PROFILE

GGMK

Regional GMK

Sub Center MK

Multiple Operator

Security Level-5

Security Level-4

Security Level-3

Security Level-1

House Owner

BR Eng.

ROBI BL WARID WIMAX Others

8

Activity Diagram for Profile Upgradation

9

Sl Tasks Time Line Responsibility1 Project Initiated May, 2007 Networks-ROM, SCM

2 Ownership Change June, 07 - Oct, 08 Admin-Security, Networks-ROM

3 Operational Website Nov, 2008 Admin-Security

4 Procedure Preparation Nov, 2008 Admin-Security

5 Workshop-1 Nov, 2008 Admin-Security

6 Workshop-2 March, 2009 Admin-Security

7 New Unit approval June, 2009 Admin-Security

8 Organogram Finalization June, 2009 Admin-Security, Networks-ROM

9 Pilot Project Kick-Off 12 August, 2009 Admin-Security, ROM_ROBs

10 Pilot phase implemented 03 September, 2009 Admin-Security, ROM_ROBs

12 Phase-2 Kick-Off 07 August, 2010 SRM, ROM_ROB

13 Phase-2 Completed 22 August SRM, ROM_ROB

14 Huawei Swap Project Aug, 10 – Dec, 11 SRM, Implementation

15 DCV & MW Swap Project Mar, 10 – Contd. SRM, ROM, Implementation

Important Milestones

10

Current Status of Project CITADEL

PADLOCKS’ PROFILE UPGRADATION

Networks Region Status Remarks

Barisal (ROBs) Completed in Sep,09 Pilot Phase

Bogra (ROB) Completed in July,10 Phase-2

Khulna (ROK) In Progress (PR)Phase-3

Mymensingh (ROMy) In Progress (PR)

Sylhet (ROS) In TargetPhase-4

Chittagong (ROC) In Target

Dhaka (ROD) N/A Phase-5

11

CLASSIC Key Status (Regional Master)

User Group DH KH SY CGROM_ROD 98 --- 1 ---

ROM_ROK --- 69 --- ---

ROM_ROS --- --- 67 ---

ROM_ROC --- --- --- 99

ROM SUPPORT 28 --- --- 1

ROM_ROMy 34 --- 29 ---

ROLL OUT 77 25 36 34

PDD 12 --- 13 5

IMPLEMEN_ISS 10 10 6 12

NMS 12 5 2

BPM & QA 3 2 2 2

PFCM 11 3 3 3

HUAWEI SWAP 27 105 157 40

MW SWAP 33 0 50 49

DCV 60 44 35 45

CITADEL 234 148 4 137

LOST REPORTED 7 7 6 10

12

Overall CLASSIC Key Status (Regional Master)

User Group DH KH SY CG

Purchased by GP 680 479 519 500

Assigned to Users 340 255 388 290

CITADEL Stock 234 148 4 137

Lost Reported 03 8 6 10

No Trace/Record 103 68 121 63

13

Current Status of Project CITADEL

PROTEC Key Status

Networks Region RGMK SCMK DGK ISK

Barisal

18 (8)

135 04 38

Faridpur 168 02 46

Patuakhali 117 02 14

Bogra

24 (9)

233 08 54

Rangpur 223 04 34

Rajshahi 156 04 35

Thakurgaon 136 04 32

14

PROTEC Key Distribution Status (BARISAL REGION)

User Group RGMK BS SCMK FP SCMK PTK SCMK BS DGK FP DGK PTK DGK

ROBs_Barisal 6 23 --- --- 4

ROBs_Faridpur 1 --- 20 --- 2

ROBs_Patuakhali 1 --- --- 14 2

ROM SUPPORT 2 2 2

ROLL OUT 3 15 12 6

IMPLEMEN_ISS 6 4 6

NMS 3 2 2

BPM & QA 1 1 1 1

PFCM 3 3 2

HUAWEI SWAP 60 80 22

MW SWAP 10 5 2

CWC 1 1 1

DCV 10 10 10

CWP 1 1 3 4

CITADEL 8 1 30 45 4

LOST REPORT 1

15

PROTEC Key Distribution Status (BOGRA REGION)

User Group RGMK BG SCMK

RP SCMK

RJ SCMK

TG SCMK BG DGK RP DGK RJ DGK TG DGK

ROB_Bogra 4 30 --- --- --- 9 --- --- ---

ROB_Rangpur 3 --- 17 --- --- --- 10 --- ---

ROB_Rajshahi 2 --- --- 20 --- --- --- 6 ---

ROB_Thakugaon 2 --- --- --- 12 --- --- --- 8

ROM SUPPORT 3 2 4 3 --- --- --- ---

ROLL OUT 2 15 13 13 12 --- --- --- ---

BRTS Ops 1 --- --- --- --- --- --- --- ---

IMPLEMEN_ISS 2 6 6 6 --- --- --- ---

NMS 1 2 2 2 --- --- --- ---

BPM & QA 1 --- --- --- --- --- --- --- ---

PFCM 2 3 3 3 --- --- --- ---

HUAWEI SWAP 80 150 80 80 --- --- --- ---

MW SWAP 3 2 --- --- --- ---

DCV 15 15 15 15 --- --- --- ---

CWP 2 2 2 1 --- --- --- ---

CITADEL 9 82 13 8 --- --- --- ---

LOST REPORT 1 1

16

PROCUREMENT PROCESS

OF ABLOY PADLOCKS &

KEYS

17

Procurement of ABLOY Padlocks

Generally Networks_Implementation purchases padlocks for the new BTS sites. Beside that Wholesale have purchased 500 padlocks for there infra share conversion support.

Need determination by user department

Consultation with CITADEL Team for profile distribution

Purchase requisition initiated by User group

Purchase Order issued to vendor by Sourcing

CITADEL & Vendor finalize the profile distribution

Vendor delivers the padlocks to CITADEL Team

CIATDEL Team notifies User & Warehouse on delivery

Warehouse transfers the padlocks to CITADEL sub-inventory

Vendor claims & receives the bill

STA

GE

-01

18

Procurement of ABLOY Padlocks (continued…)

CITADEL Team deposits padlocks at vendor office

User sends padlocks request against BTS sites

CITADEL determines the profile and informs vendor

Vendor completes the padlocks within SLA timeline

CITADEL team collects padlocks from Vendor

CITADEL Team handover the locks to User/Requester

CIATDEL Team updates the database of padlocks

User sends move orders in system for capitalization

CITADEL Team provide stock status to the user group

STA

GE

-02

19

Procurement of Keys

Previous Practices:

1. Any Network’s group can purchase any amount of keydirectly from Vendor.

2. No control over BTS Key purchase.

After initiating Project CITADEL:

1. Only CITADEL Team is authorized to deal with keys for theuser groups.

2. Vendor only communicates CITADEL Team for the deliveryagainst any new purchase request from Sourcing.

3. As per the SLA with vendor, they always handover the keysto CITADEL Team concern only.

20

Procurement of Keys (continued…..)

Need determination by user department

CITADEL Team receive key request

CITADEL Team checks the internal stocks

Purchase Requisition initiated by User (in case of shortage)

Purchase Order issued to vendor by Sourcing

CITADEL & Vendor finalize the profile distribution

Vendor delivers the keys to CITADEL Team

CIATDEL Team notifies User to collect the keys

CITADEL Team keep records of Handing/Taking over of Keys

STA

GE

-01

21

Project CITADEL – SWOT Analysis

Analysis Areas Key Components

StrengthDedicated Team, Secured Storage, IT Support, O & M Policy, Accountability Database, Set alignment with Stakeholders.

WeaknessIncomplete Software, Budgetary approval issues, Awareness of users, Huge CLASSIC keys are untraceable.

OpportunityDevelop integrated software database, Root level awareness on Operations of BKM, only ROM as Key issuer, Implement CITADEL in all Regions.

ThreatHigh dependency in budgetary approval for BTS Key Management, Rate of Theft increase in leftover CLASSIC regions.

22

Project CITADEL - Challenges

1. All Networks regions are not upgraded yet. Only 02 Regionshave completed and 05 rests are yet be done.

2. A good number of CLASSIC BTS Keys of DH, CG, KH & SYregions could not be traced during last 02 years.

3. After implementing Phase-3 in Khulna & Mymensinghregions, Dhaka & Sylhet regions will be affected as CLASSICkeys of these regions can be accessed by the keys ofMymensingh.

4. Root level control over keys and transactions from the usergroups (I,e; Sub Center, PDD, PFCM etc).

Achievements

GP recovered 1.2 Mn from vendors for 1st time upon lost of BTS keys. SRM initiated & communicated for the issue.

ROM, Technology could save huge (>20 Mn) amount BDT after implementing Project CITADEL.

Successfully implemented Project CITADEL, Phase-1 & 2 in Barisal & Bogra region respectively, which have brought a dramatic change in theft incident rate.

Extensive supports were provided to Wholesale Business on site sharing issue and almost 1700 BTS sites were configured for the access privileges for Seekers.

Achievements Glimpse

24

Comparison of the incident trends before & after

implementing Project CITADEL at Barisal region.

05

1015202530354045

Using BTS Key Breaking Locks Others

Jan, 09 - Aug, 09

Sept, 09 - 10 June, 10

0

20

40

60

80

100

Jan, 09 - Aug, 09 Sept, 09 - 10 June, 10

Total Theft Incidents

25

BTS Key Manager