Network Operations Center
What happens after the connection is delivered.
A business network is operated, not only installed. Monitoring, incident visibility, diagnosis and escalation are run by FajrFiber's Network Operations Center, with engineering support behind it.
From monitoring to a written commitment.
Visibility, technical ownership and agreed commitments belong together. This is the operating model behind the connection.
01
NOC
Monitored and diagnosed
Visibility
The network service is monitored by FajrFiber's Network Operations Center.
Owned by
NOC
Recognition
Incident visibility is part of how the Network Operations Center runs the service.
Owned by
NOC
Diagnosis
The Network Operations Center diagnoses issues affecting the network service.
Owned by
NOC
02
Engineering support
Owned by an engineer
Escalation
Escalation connects the problem to engineering support, with the environment and service scope in view.
Owned by
NOC → Engineering support
Ownership
An engineer owns the problem.
Owned by
Engineering support
Resolution
Troubleshooting and engineering support are core parts of the service, within the agreed service scope.
Owned by
Engineering support
03
SLA
Held to defined commitments
Accountability
Service commitments, support expectations and accountability are written down in the Service Level Agreement.
Owned by
Service agreement
What is operated depends on the service.
FajrFiber operates its network and the service delivered to your site. Your own environment (the LAN, systems and infrastructure inside the site) is operated where it is contracted, for example through Managed IT Infrastructure.
- 01
Your sites
- 02
Access
- 03
Network edge
- 04
Routing & security
- 05
Where you reach
The problem has an owner.
An engineer owns the problem. Escalation connects the problem to engineering support, with the environment and service scope in view.
Held to defined commitments.
Service commitments, support expectations and accountability are written down in the Service Level Agreement.
Request the applicable SLA as part of your service evaluation.
- Service scope and responsibilities
- Incident handling and escalation
- Support expectations