You are on page 1of 21

Appendix: Operation & maintenance transmission network guideline

Periodically Execu Co-


No Regulation Content Implementation Result Reference
/ Duration te ordinate

11 163
Deploying new
equipment
The plan is approved by the board of
- Analyze implementation requirements directors
As
Making plan - Check the input information Note: The plan must include an LLD DS BO
requirement
- Planning project implementation if the deployment project changes the
LLD
- Equipment/system is installed in
accordance with the Design.
- Check the infrastructure
Installing - Completion of the Equipment As plan DS BO
- Installation
Installation Acceptance Record
(BM1)
- Network node declared on NIMS
- The device is powered on
- Completed signing the minutes of
network node integration to NIMS
(BM04.03)
- Declare the network node on NIMS - Complete signing of power-on
As plan DS BO
- Power on the device minutes (BM02)
- Must ensure the power standard
condition for the axis station (if the
new device operation involves
converting the access station to the
main station)

- Backup source guaranteed by design


- Check for power backup - Equipment hardware is not faulty
As plan DS BO
- Check the hardware - Completion of signing of hardware
test and source backup (BM03)

Internal configuration of the device Internal configuration of the device As plan DS BO

Intergrating

triển khai
ai
g
Periodically Execu Co-
No Regulation Content Implementation Result Reference
/ Duration te ordinate

-Declare and configure information


safety for equipment/system in
accordance with the regulations and
Intergrating Check and declare security configuration information for instructions on information security
As plan DS BO
device/system for each type of equipment
- Signing of the record of acceptance
of the security configuration
(BM04.05)

- Declare equipment/systems to

1884/QyĐ-VTNet-CNTT: OLA/WLA quy trình quản lý phiên bản và triển khai


network management system that are
being used in the network operation

QT.VTNet.VHKT.13: Quy trình quản lý phiên bản và triển khai


1728/QĐ-CNVTQĐ-VTNet: Quy định VHKT mạng viễn thông
(supporting systems to operate
according to the O&M regulations,
for example: NIMS, GatePro, GNOC,
Intergrating to network management system As plan DS BO
NCMS, IPMS , TACACS, OSS,
Nocpro, LI, Billing ...) check the
operation status on the software,
mining support systems and sign
confirmation minutes with the lead
unit according to the form (BM04)
Equipment
management - Complete integration with remote
1
put into end systems
Configuration declaration, integration to systems As plan DS BO
operation - Sign a record of acceptance of all
contents in the form BM05
- Agree on the scenario of acceptance
Acceptancing - Build a test environment Complete the acceptance test process As plan DS BO
- Perform test acceptance
1884/QyĐ-VTNet-CNTT: OLA/WLA quy trình quản
QT.VTNet.VHKT.13: Quy trình quản lý phiê
1728/QĐ-CNVTQĐ-VTNet: Quy định VHK
Equipment
management
1
put into
operation
Periodically Execu Co-
No Regulation Content Implementation Result Reference
/ Duration te ordinate

BO receives
' - The BO received and exploited the
the
network node
- Prepare to hand over the account, the handover handover
- Perform loading test
documents, ensure that it has been integrated into the within 3
- The time to complete the hand-over
monitoring system working
is no more than 30 days after
- Perform the handover days from
completing the ATP test DS BO
Handover, loading test - Update resource information, device configuration to the date of
Note: In case the deployment group is
monitoring and management systems the
also the BO operating and exploiting,
- Sign test loading plan handover by
the acceptance and handover records
- Load test the
only need to sign the leader of the BO
deployment
unit.
unit

- Post-load evaluation, track KPI indicators and ensure


Official Loading system load according to KPI indicators Perform official loading As plan DS BO
- Perform official loading
Withdrawal old
equipment
Receive the plan, review documents related to the Number equipment and status of
Step 1 As plan DS,BO BO,VCC
cancellation network node connection

- Complete work contents in CR /


WO according to progress
- For converged network layer
devices or more in case there is no
Generate CR / WO for device cancellation including
Step 2 need to use and perform storage, As plan DS,BO BO,VCC
traffic transfer, disconnect, delete device configuration
delete the configuration, remove the
installation software, bring the device
back to the original configuration as
before deployment put into operation

The updated network node is no


longer on the network and deleted on
supporting systems of mining in
Step 3 Update databse accordance with regulations, for As plan DS,BO BO,VCC
example: NIMS, GatePro, GNOC,
NCMS, IPMS, TACACS, OSS,
Nocpro, LI, Billing ... …
Periodically Execu Co-
No Regulation Content Implementation Result Reference
/ Duration te ordinate

Power off
- The updated network node is no time is
longer on the network within 30
Step 4 Power off, remove and move device - The device is powered off, the days after DS,BO BO,VCC
hardware is disconnected and moved device has
out of the installation location finished
service
Report on the implementation result
Step 5 Completed and reported implementation results As plan DS,BO BO,VCC
is approved, closed
Monitoring alarm system

- Monitor all alarm, event generated on the network via


NMS software, Nocpro.
- Identify, categorize alarm & event, process and clear:
- All alarm generated on the network
+ Create a TT for: alarm arise and affect the quality of
are monitored, processed or put on Continuousl
Monitoring alarm system services, equipment: loss of network node monitoring, FO BO
track (in case need long time to y
control card failure, high ber error, loss of link, down
process)
equipment, high temperature, power card, microwave

2854/QyĐ-VTNet-CNTT: OLA/WLA quy trình quản lý sự kiện


1728/QĐ-CNVTQĐ-VTNet: Quy định VHKT mạng viễn thông
failure, low microwave, IUB congestion
+ Clear alarm for no effect

QT.VTNet.VHKT.15: Quy trình quản lý sự kiện


- Measurement error ber, channel, service. Determine the
level of service effect, make clear, handle the process.
For UAS, SES, ES operation immediately handle such as
incident
Ensuring the system/service works
Monitoring system/service - Measurement of link, compared with designed
stably, with the right quality as Daily FO FT
quality performance, handle with abnormal link. Handle, create
designed
a trouble ticket with abnormal link
Monitoring
2 - Monitor server activity status, DCN connection from
system
NMS to NE.
- Monitor the backup state of server, equipment
- Receive monitoring of requests from other units:
+ Require active supervision
+ Via email/phone
- All receiving tickets are monitored As
Monitoring other + Ticket from outside unit FO
and processed on time requirement
+ Change/maintenance information
- Assess the need for monitoring and feedback to the
requesting unit
QT.VTNet.VHKT.15: Quy
2854/QyĐ-VTNet-CNTT: OLA/W
Monitoring

1728/QĐ-CNVTQĐ-VTNet: Quy
2
system

Periodically Execu Co-


No Regulation Content Implementation Result Reference
/ Duration te ordinate

Duplicate alảms, events that do not


- Optimized repeated alarms, unsolved warnings
need to be handled immediately must
- Map alarms automatically according to the impact CR,
Optimizing alarms be optimized and filtered to only Weekly FO BO
according to the link/system to reduce the load of the
generate when action is needed, to
number of alarms to be monitored
avoid information disturbance.

'Alảm levels must be optimized with a frequency of 01 The alarm level corresponds to the
Reviewing alarm levels Monthly FO BO
month/time, ensuring the alarm level is correct with the severity of the problem
priority to be handled.
- Creates a TT on incident management software for
network problems, including:
- Create the TT on time, correct type
Creating TT + Problems arising from alarm monitoring, ber error, 10 minutes FO
of problem, correct object handle
performance, server / DCN, Database
+ Incident from another unit
- When the incident occurs, individuals and units - Assignment and operation of
involved in troubleshooting incident with the existing incident handling to the right subjects
As
Handling TT MOP. /units FO
regulation
- In the event of an incident affecting the service, the - Incidents are restored and
Contingency plan must be prioritized. fulfillment on target
- Check routing, service parameters are running

1728/QĐ-CNVTQĐ-VTNet: Quy định VHKT mạng viễn thông


Incident: services,

1616/QyĐ-VTNet-CNTT: OLA/WLA Quy trình quản lý sự cố


- Adjustment, routing services according to design - Fix the error and recover service the As
parameter declaration FO BO
- Check the service and continue to adjust, routing if not fastest regulation
wrong
up

QT.VTNet.VHKT.4: Quy trình quản lý sự cố


- Check network status, equipment.
- Make adjustments, routing the system to another
direction/network if there is a service impact (if
- Fix the error and recover service the As
Incident: equipment failure possible). FO BO, FT
fastest regulation
- Reset card/equipment: warm reset + cold reset
- Remove the card and reconnect it.
Handling - Replace the card / new device.
3
incident
- Check connection status and fiber status/redundant
wavelength channel. If there is a temporary emergency
- Fix the error and recover service the As
Incident: cable broken - Operating breakdown troubleshooting cable: test, FO FT
fastest regulation
determine broken, splice, quality fiber.
- Rollback back to the system after finishing the cable
1616/QyĐ-VTNet-CNTT: OLA/WLA Quy tr
QT.VTNet.VHKT.4: Quy trình quả
1728/QĐ-CNVTQĐ-VTNet: Quy định VHK
Handling
3
incident

Periodically Execu Co-


No Regulation Content Implementation Result Reference
/ Duration te ordinate

- Check fault localization, internal or partner fault


- Fix the error and recover service the As
Incident: relate partner detection FO
fastest regulation
- Contact/coordinate check processing with partners

- Checking the result of troubleshooting is done after the


troubleshooting is completed. Form of inspection:
+ Carry out tests according to guidelines already issued;
+ Monitor the performance, capacity of NE on the
Checking the result of
network;
troubleshooting and - The service is restored like before ≤ 45minutes FO
+ Perform traffic assessment and related KPIs / KQIs;
close the TT
+ Collect customer feedback through customer care.
- TT is closed on the software immediately after the
results of the service tests meet the requirements and
customers have used the service normally.

- In case you need to continue to find the root cause of


Creating PT for root - All issue, problem must be
the problem, need to create PT to find the root cause and 24h FO BO
cause problems generated PT
solution.
- Critical: ≤
7 days
- Major ≤

1728/QĐ-CNVTQĐ-VTNet: Quy định VHKT mạng viễn thông


- Find the root cause of the problem

324/QyĐ-VTNet-CNTT: OLA/WLA Quy trình quản lý vấn đề


Finding the root cause - Find the root cause of the problem 14 days
and provide solutions to thoroughly BO FO
and close the PT - Provide solutions to thoroughly overcome - Medium ≤
overcome

QT.VTNet.VHKT.18: Quy trình quản lý vấn đề


20 days
- Minor ≤
30 days

- Find the root cause of hardware failure: equipment self-


error, expiration life cycle, environmental conditions:
- Find the root cause of the problem
hot, dust, mining operation process: impact, move ... As
Hardware error and provide solutions to thoroughly BO FO/FT
- Replacement equipment/card error regulation
Problem overcome
4 - Review the remaining systems, evaluate and propose
management
solutions to prevent similar incidents (if any).

- Find the root cause of software error (version / license):


low, old, expired ... - Find the root cause of the problem
Sofware error (license, As
- Upgrade, patch version / license and provide solutions to thoroughly BO FO/FE
version) regulation
- Review remaining systems, upgrade / add software (if overcome
any)
1728/QĐ-CNVTQĐ-VTNet: Quy định VH

QT.VTNet.VHKT.18: Quy trình q


324/QyĐ-VTNet-CNTT: OLA/WLA Quy
Problem
4
management

Periodically Execu Co-


No Regulation Content Implementation Result Reference
/ Duration te ordinate

- Find the root cause of the parameter error: parameter is


wrong, no parameter - Find the root cause of the problem
As
Wrong parameter - Add, adjust, optimize parameters and provide solutions to thoroughly BO FO/FE
regulation
- Review the parameters of the remaining systems, overcome
synchronized standardized (if any).
- Find the root cause: by design, by the operator..
- Find the root cause of the problem
- Supplementing, adjusting, optimizing the declaration As
Wrong declaration and provide solutions to thoroughly BO FO/FE
- Review the remaining systems, adjust, optimize the regulation
overcome
declaration (if any).
Contingency plan
Building the MOP to - Build MOP troubleshooting for all incidents that -All incidents that have occurred
Quarterly BO FO
resolve incident have occurred on the network on the network must have MOP
- The Contingency plsn covers all
Making Contingency - Review and make the Contingency plan for all situations that arise on the network
Monthly BO FO
plan equipment with backup - Ensure feasibility and practical
application
Make contingency plan with backbone, inter-
province cable:
Cable broken - Make enough case of broken
- Broken cable to decrease protection from 1+2 to Monthly BO FO
contingency plan backbone cable
1+1,1+0
- Broken cable within spare or no spare cable
Make contingency plan cable attenuation without

1728/QĐ-CNVTQĐ-VTNet: Quy định VHKT mạng viễn thông


Cable attenuation switching - Make enough case of attenuation
Monthly BO FO
contingency plan - Guide to determine attenuation cable
- Guide to switch protection
Make contingency equipment failure:
Equipment failure - Error equipment - Make enough case of equipment
Monthly BO FO
contingency plan - Lost configuration equipment failure
- Lost sync equipment
Make contingency card failure:
Card failure
Contingency
- Error management card - Make enough case of card failure Monthly BO FO
5 contingency plan
plan - Error add/drop, service card
Make contingency server/DCN failure:
Server/DCN failure - Make enough case of
- Lost DCN, gateway Monthly BO FO
contingency plan server/DCN failure
- Error server
SNMP failure - Make enough case of SNMP
- Make contingency lost server-gatepro Monthly BO FO
contingency plan failure
1728/QĐ-CNVTQĐ-VTNet: Quy định VHKT
Contingency
5
plan

Periodically Execu Co-


No Regulation Content Implementation Result Reference
/ Duration te ordinate

Special case - Make contingency with special case of vendor:


- Make enough special case Monthly BO FO
contingency plan lost services, lost monitoring
Make contingency plan of synchronization:
Synchronization - Make enough case of
- PRC failure Monthly BO FO
contingency plan Synchronization failure
- SSU failure
Microwave/VSAT - Contingency of Microwave system - Make enough case of
Monthly BO FO
failure contingency plan '- Contingency of VSAT system Microwave/VSAT failure
Practise Contingency
plan
- Planning exercises for common situations on the
network. The plan must describe in detail the steps to do, - Simplify situations that may occur
Access network level of impact and the situations arising.
Quarterly FO BO
on the network
- Organizing and supervising
- Planning exercises for common situations on the
network. The plan must describe in detail the steps to do, - Simplify situations that may occur
Backbone network Quarterly FO BO
level of impact and the situations arising. on the network
- Organizing and supervising
-All changes that have been done on the network must be
had MOP:
- MOP requirements:
+ General information, network Node affected
+ Assurance conditions: Implementation tools, personnel
- MOP enough information and
Creating MOP implementation, materials/facilities Weekly BO FE
step/how to implement
+ Implementation steps, rollback: check the system
before the change, make changes and rollback, check the
system after the change
+ Procedures for testing change: service test scenario,
KPI

uản lý thay đổi


ạng viễn thông

thay đổi
Periodically Execu Co-
No Regulation Content Implementation Result Reference
/ Duration te ordinate

Create CR for all network changes:


- New development
- Network adjusment
- Network upgrade
All CR/ECR must have the following information:
- Contents of work to be done, services affected (What);
- CR enough/correct information,
- Causes of CR/ECR (Why);
Creating CR content/step of execution, scope of Daily BO FE
- The scope of the network is changed, the influence
affected
(Where);
- CR/ECR execution time, expected service impact time
(When);

638/QyĐ-VTNet-CNTT: WLA/OLA quy trình quản lý thay đổi


1728/QĐ-CNVTQĐ-VTNet: Quy định VHKT mạng viễn thông
- CR/ECR creator, Who will implement the change
(Who);

QT.VTNet.VHKT.10: Quy trình quản lý thay đổi


- How to do (How)

- CR and ECR need to be approved by the NOC / GNOC - CR approved in the right order, LĐP/B
Approving CR Daily FE
BoD before implementation decentralized GĐ
- CRs and ECRs must be verified by CAB (or ECAB)
before approval
- CR/ECR assessment results of CAB / ECAB must
Impacting indicate:
6
system + The feasibility of change;
CR is assessed properly / sufficient
Assessing CR + The extent and scope of affected; Daily BO FE
content as required
+ Possible risks;
+ Actions to promptly respond to problems, minimize
impacts on services;
+ Requirements to supplement, improve CR / ECR (if
any).
- CR is executed correctly/enough on
- CRs must be scheduled by date.
request BO/FO/
Executing CR - The implementation of CR must be strictly adhered to Daily FE
- The process of implementation must FT
the pre-scheduled calendar and the approved content
ensure network safety
- Checking the conditions for assurance of: tools; MOP,
Check the conditions DT; service tests; Network status ready for CR - Ensure conditions for CR As BO/FO/
FE
before the implementation implementation. implementation regulation FT
- If this condition is not met, CR is not allowed.
QT.VTNet
638/QyĐ-VTNet-
1728/QĐ-CNVT
Periodically Execu Co-
No Regulation Content Implementation Result Reference
/ Duration te ordinate

- Execute follow MOP, instructions in CR - CR is executed correctly/enough on


Executing follow MOP, - In the event of a incident during the execution of the request As BO/FO/
FE
instructions in CR CR, rollback the network back to the state immediately - The process of implementation must regulation FT
before executing the change. ensure network safety

- Check the result of change after the completion of the


CR or after the system rollback when the change of
execution fails.
+ Perform tests according to approved CR content
Checking the result of + Monitoring the operation of the network subject to - Network after change ensures As
FE FO
CR change; safety/quality regulation
Flow Assessment and KPI / KQI related;
Collection of customer feedback through customer care.
- If the test results are not successful, rollback the
network to the state immediately before the change.

- Execute/remove data/material after impact As


Closing CR - Closed CR as procedure FE BO
- Close CR after impact has been completed regulation
- Measure the power of DWDM

3127/QĐ-VTNet-VHKTTC: Quy định bảo dưỡng


4077/QyĐ-VTNet-CNTT: WLA/OLA Quy trình
1728/QĐ-CNVTQĐ-VTNet: Quy định VHKT
- Measure the power of DWDM system. system.
- Evaluate and handle the link with power difference in 2 - Evaluate and handle the link with
Transmission network
main/protect directions > 3 dB for systems with 2 or power difference in 2 main/protect
more cables. directions > 3 dB for systems with 2
or more cables.

mạng viễn thông


- The system is installed Security
software
Soft
Network management - Check capacity, virus software, system time, sync data - Correct time between NMS, NE,
maintenance Monthly BO FO
system - Perform handle (if any) Nocpro
- Data between active server/standby
is synchronized
NMS:
Measure the output performance of the SSU, measure monthly
Correctly measure frequency, number
Synchronization network the synchronous sequence with the largest number of Synchronous BO FO
and handle irregularities (if any)
nodes in the network. meter:
Yearly
DWDM Network
Powering on the backup - Power on the backup device Every 6
- The backup equipment works fine FO BO
equipment - Check equipment status months
Periodically Execu Co-
No Regulation Content Implementation Result Reference
/ Duration te ordinate

Checking the backup of - Switch each active/standby power card Every 6


- The backup card works fine FE BO
power card - Ensure the cards are stable months

Checking the backup of - Switch each active/standby SCC, cross-connect card Every 6
- The backup card works fine FE BO
SCC, cross-connect - Ensure the cards are stable months

Checking OLP/OMSP - Switch link 1+1 protection Every 6


- The backup link works fine FE BO
switching - Ensure that the switch service is not faulty months
SDH Network
Powering on the backup - Power on the backup device Every 6
- The backup equipment works fine FO BO
equipment - Check equipment status months
Checking the backup of - Switch each active/standby power card Every 6
- The backup card works fine FE BO
power card - Ensure the cards are stable months

Checking the backup of - Switch each active/standby SCC, cross-connect card Every 6
- The backup card works fine FE BO
SCC, cross-connect - Ensure the cards are stable months

Checking MSP-Linear - Switch link 1+1 protection


- The backup link works fine Yearly FE BO

1728/QĐ-CNVTQĐ-VTNet: Quy định VHKT mạng viễn thông


switching of STM1-BSC - Ensure that the switch service is not faulty

4077/QyĐ-VTNet-CNTT: WLA/OLA Quy trình bảo dưỡng


Checking MSP-Linear - Switch link 1+1 protection Every 6

3127/QĐ-VTNet-VHKTTC: Quy định bảo dưỡng


- The backup link works fine FE BO
switching - Ensure that the switch service is not faulty months

QT.VTNet.VHKT.02: Quy trình bảo dưỡng


SDH/Microwave
backbone link
Checking protection of - Switch protection of ring 1+1, 1+2, 1+3... - Shutdown all situations
Every 6
STM64/STM16/ - Ensure that services are declared fully protection - After the shutdown direction, the FE BO
months
Microwave backbone ring according to the design backup declaration works well
Checking Link the same cable
backup routes, ways
- Shutdown all situations
Turning off link the same - Turn off link the same cable routes, ways Every 6
- After the shutdown direction, the FE BO
cable routes, ways - Ensure services are not affected by the loss of links months
backup declaration works well
Synchronization
equipment
Powering on the backup - Power on the backup equipment
- The backup equipment works fine Yearly FO BO
equipment - Check equipment status
QT.VTNet.VHKT.02: Quy trì
4077/QyĐ-VTNet-CNTT: WLA/OLA
3127/QĐ-VTNet-VHKTTC: Qu
1728/QĐ-CNVTQĐ-VTNet: Quy định
Checking
backup

Periodically Execu Co-


No Regulation Content Implementation Result Reference
/ Duration te ordinate

Checking the backup of


main synchronous pulse - Switch each active/standby power card
- The backup card works fine Yearly FE BO
card, standard signal - Ensure the cards are stable
coding card, output card

Database, logfile system


- Change active to standby server and check the backup
Change active to standby Every 6
server state - The backup server works fine FE BO
server months
- Ensure backup server is working properly
Microwave, VSAT
backbone

- For the abis-2 routes:


Check the redundancy
* Option 1: Perform switching test on BSC. The service runs through solid
function of the solidified
* Method 2: Perform the test on the transmission head. microwave directions, the abis-2 Every 6
microwaves, abis-2, FE BO
- For solid lines, optical ring restoration: Perform optical returns normally when the main months
protection for optical
shutdown in main direction or manual switch to optical direction is faulty.
rings, SRT
microwave direction.

Checking the backup of


- Switch each active/standby power card Every 6
the ODU/RFU/RAU unit - The backup card works fine FE BO
- Ensure the cards are stable months
with 1+1 configuration

28/QĐ-CNVTQĐ-VTNet: Quy định VHKT mạng viễn thông


Backbone equipment

077/QyĐ-VTNet-CNTT: WLA/OLA Quy trình bảo dưỡng


Checking the power
- Clean and maintance hardware equipment

3127/QĐ-VTNet-VHKTTC: Quy định bảo dưỡng


source, dust filter, clean - Equipment is clean Monthly FT FO
- Ensure equipment operates in the best conditions

QT.VTNet.VHKT.02: Quy trình bảo dưỡng


dirty

Checking cable
connection, tighten screws, - Clean and maintance hardware equipment - The cable lay as standard
Quarterly FT FO
screws, recover unused - Ensure equipment operates in the best conditions - The connections are firmly fixed
redundant cables

Cleaning the inside of the - Clean and maintance hardware equipment Every 6
- Card is clean FT FO
equipment - Ensure equipment operates in the best conditions months
Access equipment
4077/QyĐ-VTNet-CNTT: WLA/OLA Quy trình bảo dư
1728/QĐ-CNVTQĐ-VTNet: Quy định VHKT mạng viễn
3127/QĐ-VTNet-VHKTTC: Quy định bảo dưỡng

QT.VTNet.VHKT.02: Quy trình bảo dưỡng


Periodically Execu Co-
No Regulation Content Implementation Result Reference
/ Duration te ordinate

- Clean and maintance hardware equipment


Cleaning equipment - Equipment is clean Monthly FT FO
- Ensure equipment operates in the best conditions

Cleaning the inside of the - The cable lay as standard


- Clean and maintance hardware equipment
equipment, change patch - The connections are firmly fixed Yearly FT FO
- Ensure equipment operates in the best conditions
cord, attenuation - Card is clean

- The equipment is firmly fixed to the


Maintenance outdoor unit - Clean and maintance hardware equipment
rack/tower Yearly FT FO
Microwave/VSAT - Ensure equipment operates in the best conditions
- The cable is firmly fixed to tower
Cable network
Patrolling cable
Repot the volume, the list of cable
- Aerial
link needs to be processed:
cable: 2
- List of unsafe locations on the
weeks;
Patrol along the cable route, risk of cable broken to be
- Check the patrol checklist Burried
route to assess the status of handled immediately and FT
- Proposals for dealing with problems cable: 1
optical cable immediately notify the relevant units.
month
- The list of unsafe locations on cable
- Before and
lines needs to be reinforced and
after storm
maintained

- The risk of unsafeness from external factors: road


construction, construction risk of cable broken, piling of
pole:
• Immediately notify the construction unit of the cable
route and ensure the safety of the cable line during
construction (co-ordinate directly)
• Hold a warning sign at unsafe locations. The cable is not broken during - Daily
Implementing the risk of
Hard • Assign the staff, fix cable in case of need. waiting repair. - Resolve ≤ FT
unsafe patrols
maintenance - Other risks: cables falling down the road, cable 24h

TQĐ-VTNet: Quy định VHKT mạng viễn thông


dropping pole, crushed cables causing cable attenuation,
electric wire touching the fire risk cable ....
• Take photos, record the scene, get feedback
immediately
• In case of risk of cable broken need to confirm with

ướng dẫn VHKT mạng cáp quang


NOC

Quality control of optical


fiber
Hard
maintenance

1728/QĐ-CNVTQĐ-VTNet: Quy định VHKT mạng viễn thông


Hướng dẫn VHKT mạng cáp quang
Periodically Execu Co-
No Regulation Content Implementation Result Reference
/ Duration te ordinate

- For existing fibers: perform periodic control through - NMS: 1


Testing and statistics monitoring by network management system (NMS, week
List cable attenuation FO,
attenuation of optical fiber Nocpro). - Spare
FT
are in use and spare - For spare fiber: periodic test with OTDR fiber: 3
months

3 Priority: - 1st priority


- 1st Priority: Cable error bit or affected service quality ≤ 3h
Classification of the cable FO,
- 2nd Priority: Attenuation of cable over the threshold - Handle the cable attenuated within - 2nd
list in three priority levels FT
(backbone cable reach the threshold) the target priority ≤ 7
- 3rd Priority: Remain attenuation link - The quality of the cable is days
guaranteed according to standard - 3rd
- Create WO with 1st, 2nd priority priority: ≤
Creating WO FO
- Handover to relate unit to resolve 3rd priority 15 days
Creating CR - Unit respond WO create CR to process FT

Reinforcement and
maintenance cable

Content of the maintenance:


- Reinforce,fix or replace of missing accessory points
(clamp, suspension/tension, non-fixed closure).
- Handle the position of the cable brush to the
pole/obstacle
Perform actions to
- Hanging position of the same cable hammock, not - Complete the required maintenance
overcome the risk of
guarantee the height on time
unsafe cable route was ≤ 3 months FT
- Handle the tree over the cable. - To ensure quality of cable to meet
detected during cable
- Reinforcing, replacing broken pole, block subsidence, the standards.
patrol or other
cracking, ... do not guarantee safety.
- Reinforcement, burial of cables exposed to road,
landslide (for buried route).
- Replacement of bad cables, multiple closures, cable tie.
- Replacing the cover of hole
Periodically Execu Co-
No Regulation Content Implementation Result Reference
/ Duration te ordinate

- Ensuring the correct evaluation


frequency as prescribed for a
particularly important system (3
months), very important (6 months),
Make plan evaluate the system Monthly BO QLVĐ
important (9 months), average (1
year)
Make plan evaluate the - Full evaluation of information /
system systems

Risk assessment report:


- Report weekly risk assessment progress to RM staff to
Weekly/Mon
check the results. Report the results of risk assessment BO QLVĐ
thly
- Risk results synthesis report is sent in the last week of
the deadline according to the registered evaluation plan.

1728/QĐ-CNVTQĐ-VTNet: Quy định VHKT mạng viễn thông


1639/QyĐ-VTNet-CNTT: WLA/OLA Quy trình quản lý rủi ro
All risks are classified at risk level Weekly/Mon
Creating risk Creating risk on GNOC BO QLVĐ
and updated on the GNOC thly
Weekly/Mon
Open risk Review the risks and propose RM to open risks Proposed open risk BO QLVĐ

QT.VTNet.CL.04: Quy trình quản lý rủi ro


thly
Risk adjustment: Exchange and clarify information
Adjusting risk Adjust risks (if necessary). Weekly QLVĐ BO
related to newly created risks, adjust risks (if necessary).

For newly created Low and Medium Risks: Exchange


and clarify information related to newly created risks, Open risk on time BO QLVĐ
Risk Risk analysis and risk and open risks to the receiving unit.
8
management contro For High and Very High Risks: assessed by the RAB
Open risk on time After 7 days BO QLVĐ
committee
Receiving and assigning a risk treatment focal point:
Taking risk receives and transfers the processor to the risk treatment Taking risk After 5 days BO QLVĐ
plan after the risk is recognized
Planning Develop a risk plan, consult RM / BO / FO (if necessary) Develop a risk plan BO QLVĐ

Approve the risk plan Evaluate the risk plan Evaluate the risk plan After 3 days BO QLVĐ

Assessing issues related to risks such as: Time of risk


treatment; Solution for risk treatment; Risk treatment
Change management Proposed information change BO QLVĐ
personnel; Level of risk… And suggest changes (if
necessary) for RM
Evaluation of proposed changes in
Change approval Evaluation of proposed changes in plan After 3 days BO QLVĐ
plan
1639/QyĐ-VTNet
QT.VT
1728/QĐ-CNVT
Periodically Execu Co-
No Regulation Content Implementation Result Reference
/ Duration te ordinate

Very High level of risk: Maximum time for planning


Complete risk treatment on time 15 days BO QLVĐ
execution, risk handling solutions
High level of risk: Maximum time for planning
Complete risk treatment on time 45 days BO QLVĐ
execution, risk handling solutions
Perform resolve risk
Medium level of risk: Maximum time for planning
Complete risk treatment on time 3 months BO QLVĐ
execution, risk handling solutions
Low level of risk: Maximum time for planning Every 6
Complete risk treatment on time BO QLVĐ
execution, risk handling solutions months
Closing risk Close risk on GNOC Close risk on time After 3 days QLVĐ BO
Legal review (*): Review legal issues from legal
documents to commitments, agreements, licenses,
laws, and regulations relating to design planning,
Review and evaluate differences Every 6
Auditing Legal (*) installation, operation and operation, optimization of BO
and legal violations (*) months
the system, asset management, construction /
deployment of system infrastructure, transmission
services (optical, microwave, VSAT ...)

Off-Site Audit Process

Review of detailed - Review of detailed design (LLD) and operation records


- Evaluate the correctness/adequacy
design documentation - Requires network nodes that have been put into Every 6
of the network diagram with the BO
(LLD) and exploitation operation to have an HLD design file. The detailed months
actual situation
operation records design must contain full the information.

- Check detail traffic routing according to LLD.


Review of DWDM - Evaluate declarations different with
- Test the quality of service Every 6
service declaration and designs, designs that need to be BO
- Check the alarm to detect abnormal issues (ex: months
routing optimized
loop, insert warning, ...)
- 'Review of basic parameters with the standard
Review of basic - Evaluate parameter different with Every 6
parameters BO
parameters designs months
- Detailed information on the file
- Check monitored nodes on NOCPro, NMS
Review of system
- Check the monitoring of internal switches, - Evaluate monitoring different with Every 6
monitoring and alarm BO
auxiliary server. designs months
on the system
- Check for early warning KPIs

iễn thông
lý rủi ro
Periodically Execu Co-
No Regulation Content Implementation Result Reference
/ Duration te ordinate

- Check the configuration and storage of backup


files
Review of backup
- Check the synchronization of data: - Evaluate backup different with Every 6
configuration, data BO
+ Between 2 nodes (Active/Active, designs months
synchronization
Active/Standby)
+ Between modules in the same node
- Check whether access to nodes is through FW,

1728/QĐ-CNVTQĐ-VTNet: Quy định VHKT mạng viễn thông


1639/QyĐ-VTNet-CNTT: WLA/OLA Quy trình quản lý rủi ro
GatePro or not.
Review of information - Evaluate systems that do not Every 6
- Review VPN connections to the system BO
security guarantee information security months
- Review security software, viruses

QT.VTNet.CL.04: Quy trình quản lý rủi ro


- Review the declaration, decentralize the user
- Check configuration details for each

157/ĐX-TD: Đề xuất audit hệ thống


Review of spare Card/Module/Port/Link card as designed. - Evaluate the equipment, the system Every 6
BO
information - Check the backup through the maintenance does not guarantee the rules months
process
- Check details of the Contingency plan
Review of contingency - Evaluate equipment, the system has Every 6
Auditing/optimi plans
- Check data, plans and procedures for BO
no contingency plan months
9 implementing Contingency
zation system
- Check all the equipments and links in the network
- Evaluate the capacity for current Every 6
Performance evaluation - Evaluation of equipment, cards are not used or BO
and future services months
used in accordance with planning
- Based on data to assess the failure rate of the Every 6
Evaluation of error rates - Evaluate of error rates BO
equipment meets the requirements or not months
- To review the risks of cable network
infrastructure: critical points, cable joints,
thoroughfares
Every 6
Risk management - Review of equipment risks - Evaluate all system risks BO
months
- Review the risks of hardware and software
versions of the system
- Risk assessment on service declaration
On-Site Audit Process
- Check the installation location of the equipment,
the external blocks at the station and the network
node profile
Profile and installation Evaluate positions that are different
- Check the installation distance of the shelf, Fiber Yearly BO FT
location from design
Tray, Mux / Demux
- Check that the network node profile has been
fully updated
Periodically Execu Co-
No Regulation Content Implementation Result Reference
/ Duration te ordinate

- Check the temperature, humidity of the machine Evaluate whether the machine
Check the operating
room and equipment room environment is standardized Yearly BO FT
environment
- Check room humidity or not
Clean the dust filter - Check and clean the dust filter of the appliance Check and clean the equipment Yearly BO FT
Check FAN - Check the status and operation of the FAN module Evaluate the status of the FAN Yearly BO FT
Fix rack, shelf - Check, re-rack, shelf of equipment to ensure safety Equipment is secure Yearly BO FT
- Clean patchcord, connectors are not guaranteed
Clean patchcord - Take all patchcord yarn at risk of unsafe as Room is clean Yearly BO FT
prescribed
- Measure the spectral power of the channel by
Measurement of channel OTDR. Check, compare the actual test
Yearly BO FT
power spectra - Test the accuracy of the spectrum measurement with the system
on the system.
Ensure 1 shelf is supplied from 2
Check the DC power Check the DC power connection at the site Yearly BO FT
different DC cabinets
Check the switch over
- Check for switch-over card activity when one card
the control card on the The control card works fine Yearly BO FT
is faulty
device
- Reviewing and checking cable entry routes,
Check the cable status critical points on cable lines and proposing The list unsafe optical cable Yearly BO FT
corrective measures

lý tần số viba, VSAT


KT: Quy định quản
2438QĐ-VTNet-
Quarterly,
Microwave/VSAT
Update microwave/VSAT frequency, fiber optic cable License correct/enough compared to or within 48
frequency, fiber optic FT,BO FT
license database reality hours of the
cable management license
change

Network resource
- Update new cable: update the cable database to NIMS
as guidelines.
Fully updated information
- Update after emergency
Cable information (infrastructure and cable connection) Monthly FT FO
- Update after re-route, move, relocation, maintenance
to NIMS
and repair of optical cable
- Update change information after patrol
Node database:
optical/microwave/vsat/bac - Update node database: type/configuration - Update all of network database Quarterly BO
kbone/access

hần mềm NIMS


ạng viễn thông
Periodically Execu Co-
No Regulation Content Implementation Result Reference
/ Duration te ordinate

QT.VTNet.TK.07: Quy trình sử dụng, khai thác phần mềm NIMS


Resourse database: - Update equipment, resource database: invested, using,

1728/QĐ-CNVTQĐ-VTNet: Quy định VHKT mạng viễn thông


- Update all of network database Quarterly BO
invest/exiting/spare/lost spare, lost
Network capacity: ring,
- Update capacity database: support/using - Update all of network database Quarterly BO
link
Protection database:
- Update protection database: 1+0, 1+1, 1+2…

Hướng dẫn VHKT cáp quang


- Update all of network database Quarterly BO
national, province

Hướng dẫn VHKT viba


- Update services declaration database, specially
Declaration database - Update all of network database Quarterly BO
important services: 2G, 3G, VIP customer…
- Update microwave database: long/lat, distance,
Microwave link database - Update all of network database Quarterly BO
frequency, capacity, antena...
- Update optical cable database: start/end point, distance,
Optical cable database - Update all of network database Quarterly BO
optical type, core
Chain link database - Update chain link database: > 3 BTS, 5 BTS - Update all of network database Quarterly BO
Deadpoint database - Update deadpoint database of transmission network - Update all of network database Quarterly BO
Link the same cable,
- Update link the same cable, route database - Update all of network database Quarterly BO
route
O&M database
- Update all event, incident, problem occured
Logfile TT, PT, KEDB - Update all of network database Monthly FO BO
- Save information for analysis, evaluation
- Update all CR history
Logfile CR - Update all of network database Monthly FE FO
- Save information for analysis, evaluation
- Update all KPI/KQI of network
KPI/KQI - Update all of network database Monthly FO BO
- Store information for analysis, evaluation
- Update all guideline, MOP, Contingency plan, lesson
Guideline, MOP,
Database learned
10 Contingency plan, lesson - Update all of network database Monthly BO
management - Store information for operation & maintenance,
learned
trainning, handover
Within 48
Lesson learned Update learned lessons to KEDB - Update learned lessons to KEDB hours of the FO BO
change
HLD diagram
- The overall design should ensure
that the overall structure of the
- Drawing/updating an overview of the transmission Every 6
System structure overview system is complied with, in BO
system, including network layers, services months
accordance with the content of
planning

n thông
ế
management

Periodically Execu Co-


No Regulation Content Implementation Result Reference
/ Duration te ordinate

-The design must describe the types


Description of equipment - Drawing/updating description of equipment types, Every 6
of equipment used on the system, BO
used on the system functions, configuration of DWDM, SDH months
based on documentation of the vendor

1728/QĐ-CNVTQĐ-VTNet: Quy định VHKT mạng viễn thông


LLD diagram
- Drawing/updating map of physical DWDM, SDH Description ofcable route deployed
Map diagram Quarterly BO

1610/QĐ-VTNet-KTTC: Quy định rà soát thiết kế


network of country/province/district/commune between sites
- Drawing/updating logical DWDM, SDH, Description of logical connection
Logical diagram Synchronization network of between site, the type of Quarterly BO
country/province/district/commune configuration of each site
Description of fiber information used
- Drawing/updating fiber core DWDM, SDH network of
Fiber core diagram to connect between sites according to Quarterly BO
country/province/district/commune
the logic diagram

Description of VC4 level service


- Drawing/updating declaration/routing DWDM, SDH,
Declaration/routing routing, wavelength routing,
Synchronization network of Quarterly BO
diagram synchronous signal routing according
country/province/district/commune
to logic connection diagram

Description of the connection


DCN diagram - Drawing/updating declaration/routing of NMS, DCN diagram to port level, IP design, ID Quarterly BO
for NE in the NMS
Description of the location of
Layout diagram - Drawing/updating layout of machine room Quarterly BO
equipment in the machine room
Description of the map showing the
- Drawing/updating card position in subrack of DWDM, location/function/ configuration/size
Subrack diagram Quarterly BO
SDH, Synchronization network of the card inserted to the subrack of
the device.
Detailed description of the
connection to each port on the
Internal connection - Drawing/updating internal fiber in subrack of DWDM,
equipment in accordance with the Quarterly BO
diagram SDH
icon used in the operation of the
transmission network.
- Full network diagram
Power diagram - Drawing/updating power of DWDM, SDH Quarterly BO
- Diagram is updated to the latest
KPI for Service quality

chất lượng mạng truyền dẫn


DWDM channel's port Evaluate DWDM channel's port ratio serious error Compare pass/fail compared to the
Monthly BO
ratio serious error (SESR) (SESR) target and make the optimal plan

u KPI mạng lưới


Periodically Execu Co-

TC.CNVTQĐ.VTNet.180: Bộ chỉ tiêu KPI chất lượng mạng truyền dẫn


No Regulation Content Implementation Result Reference
/ Duration te ordinate

497/TTr-VTNet-KT: Bộ chỉ tiêu KPI mạng lưới


The DWDM channel's port Compare pass/fail compared to the
Evaluate DWDM channel's port ratio degradation (BER Monthly BO
ratio degradation (BER target and make the optimal plan
before FEC)
before FEC)

SDH port ratio serious Compare pass/fail compared to the


Evaluate SDH port ratio serious error (SESR) Monthly BO
error (SESR) target and make the optimal plan

Control KPI of The ratio of the quality


11 Evaluate the ratio of the quality degradation of the Compare pass/fail compared to the
operation and degradation of the Monthly BO
microwave link (BER) target and make the optimal plan
maintenance microwave link (BER)

The number of Vsat


Evaluate the number of Vsat stations violated the signal- Compare pass/fail compared to the
stations violated the signal- Monthly BO
to-link noise ratio (Eb/No) target and make the optimal plan
to-link noise ratio (Eb/No)

KPI for O&M


Number of transmission Evaluate number of transmission incident, the ratio of Compare pass/fail compared to the
Monthly BO FT
incident the cause of the incident target and make the optimal plan
Compare pass/fail compared to the
Processing time of incident Evaluate processing time of incident Monthly BO FT
target and make the optimal plan
Evaluate Cell*h due to the transmission cause, the ratio Compare pass/fail compared to the
Cell*h Monthly BO FT
of the causes of transmission target and make the optimal plan

You might also like