2. 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. 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. 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)
10. 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 Target
Phase-4
Chittagong (ROC) In Target
Dhaka (ROD) N/A Phase-5
17. 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
STAGE-01
18. 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
STAGE-02
19. 19
Procurement of Keys
Previous Practices:
1. Any Network’s group can purchase any amount of key
directly from Vendor.
2. No control over BTS Key purchase.
After initiating Project CITADEL:
1. Only CITADEL Team is authorized to deal with keys for the
user groups.
2. Vendor only communicates CITADEL Team for the delivery
against any new purchase request from Sourcing.
3. As per the SLA with vendor, they always handover the keys
to CITADEL Team concern only.
20. 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
STAGE-01
21. 21
Project CITADEL – SWOT Analysis
Analysis Areas Key Components
Strength
Dedicated Team, Secured Storage, IT Support, O &
M Policy, Accountability Database, Set alignment
with Stakeholders.
Weakness
Incomplete Software, Budgetary approval issues,
Awareness of users, Huge CLASSIC keys are
untraceable.
Opportunity
Develop integrated software database, Root level
awareness on Operations of BKM, only ROM as Key
issuer, Implement CITADEL in all Regions.
Threat
High dependency in budgetary approval for BTS
Key Management, Rate of Theft increase in
leftover CLASSIC regions.
22. 22
Project CITADEL - Challenges
1. All Networks regions are not upgraded yet. Only 02 Regions
have completed and 05 rests are yet be done.
2. A good number of CLASSIC BTS Keys of DH, CG, KH & SY
regions could not be traced during last 02 years.
3. After implementing Phase-3 in Khulna & Mymensingh
regions, Dhaka & Sylhet regions will be affected as CLASSIC
keys of these regions can be accessed by the keys of
Mymensingh.
4. Root level control over keys and transactions from the user
groups (I,e; Sub Center, PDD, PFCM etc).
23. 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.
24. Achievements Glimpse
24
Comparison of the incident trends before & after
implementing Project CITADEL at Barisal region.
0
5
10
15
20
25
30
35
40
45
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
