Container
Container
An isolated application environment that shares the host operating-system kernel rather than emulating a full computer.
In everyday business: Applications can be packaged consistently without needing a full VM for each one.
FIBRE SPLICING
Fusion Splicing and Fibre Termination Playbook
Strip, clean, cleave, align, fuse, protect, tray and test fibre splices with a repeatable field process.
Book 2 | Chapter 7
Chapter opening
Chapter 7 moves from the course overview into fusion splicing and fibre termination. The aim is not to memorise product menus or commands. The reader should understand what problem the technology solves, how it fits into the wider cabling, fibre, racks and power textbook, what normal operation looks like, and how to prove the result in the field.
The previous chapter introduced fibre optic cable installation playbook. This chapter continues the sequence by focusing on fusion splicing and fibre termination playbook, so the reader can connect the architecture to a more specific operational problem.
Learning objectives
- Explain the main purpose of Fusion Splicing and Fibre Termination in plain language.
- Distinguish installation quality, optical loss, polarity and transceiver compatibility.
- Use evidence to separate a design problem from a configuration or physical fault.
- Describe the business impact of a failure and the evidence required for handover.
Why this matters in a real company
Fibre carries high-speed links between racks, buildings and network equipment. Correct installation and testing avoids intermittent outages that can be expensive to locate after ceilings, ducts or trenches are closed.
PLAIN ENGLISH
Technical terms used in this chapter
You do not need to memorise the jargon first. Understand what each term does and why somebody running a company would care about it.
Image
Container Image
A read-only package containing an application and its required files used to create containers.
In everyday business: IT can deploy the same known application build repeatedly.
OLTS
Optical Loss Test Set
A fibre test method for measuring end-to-end insertion loss.
In everyday business: It proves how much optical power the installed fibre path loses.
OTDR
Optical Time Domain Reflectometer
A fibre tester that sends pulses and measures reflections/backscatter to locate events along a link.
In everyday business: It can show where a splice, connector, bend or break is located.
NAT
Network Address Translation
A router or firewall function that changes IP addressing as traffic crosses a boundary.
In everyday business: Many private office devices can share one public Internet address.
PAT
Port Address Translation
A form of NAT that lets many internal connections share one public address by tracking transport ports.
In everyday business: Hundreds of users can browse the Internet through one public IPv4 address.
BUSINESS TRANSLATION
What this means outside the server room
This topic affects the physical foundation of the network. Good installation costs less to support because faults are measurable, documented and less likely to return.
Firewall
What it means: A firewall controls which network connections are allowed between users, systems and external networks.
In normal business language: It is a security checkpoint between parts of the company network. It should allow legitimate work while blocking unwanted access.
Why the decision matters: Firewall rules should describe real business flows such as 'staff may reach accounting on HTTPS', not unexplained broad permits.
NAT
What it means: NAT changes IP addresses as traffic crosses a network boundary.
In normal business language: It is similar to a company switchboard: many internal extensions can share one public number.
Why the decision matters: NAT helps with address use and publishing services, but it is not a substitute for firewall security.
Container
What it means: A container packages an application and its dependencies while sharing the host operating-system kernel.
In normal business language: Think of standardised shipping containers: the application is packaged the same way even when moved between compatible systems.
Why the decision matters: Containers improve deployment consistency, but persistent data, networking, security and backup still need deliberate design.
OTDR
What it means: An OTDR locates events such as splices, connectors, bends and breaks along a fibre by analysing reflected light.
In normal business language: It is like a fault locator that tells the technician roughly where along a long fibre route the problem is.
Why the decision matters: Use OTDR for event location and diagnosis, not as a replacement for every end-to-end loss test.
OLTS
What it means: An OLTS measures end-to-end optical loss across a fibre link.
In normal business language: It tells you how much signal is lost from one end of the fibre to the other.
Why the decision matters: Use OLTS when the project needs proof that total installed loss is within the allowed budget.
Chapter contents
7.1 The splice is decided before the arc
Fusion splicing joins two fibres by aligning and fusing the glass. FOA describes the basic preparation sequence as strip, clean and cleave. A good splicer cannot rescue dirty fibre, damaged glass or a poor cleave consistently.
Prepare the work area
- Use a stable, clean work surface.
- Control wind and dust.
- Keep stripping and cleaving tools clean.
- Prepare a safe glass-shard container.
- Confirm the splicer program matches the fibre type.
- Fit the splice-protection sleeve before making the splice.
Step 1: strip
Remove the required coating length with a stripper designed for the fibre coating. Do not nick the glass. Worn or damaged stripping blades can weaken the fibre and cause later breaks.
Step 2: clean
Clean exposed glass with the splicer/tool manufacturer's recommended method and lint-free materials. Contamination on the bare glass affects cleaving and the fusion process.
Step 3: cleave
The cleaver creates the end faces the splicer must align. A bad cleave angle, chip or contaminated end should be rejected and recleaved. FOA calls cleave quality one of the key factors in consistent low-loss splices.
Step 4: align and fuse
Load both fibres into the splicer without touching the prepared ends. Select the appropriate splice program. Automatic machines inspect the fibres, align them and run the fusion arc sequence. The splicer's estimated loss is useful process feedback but is not the same as an independent field measurement.
Step 5: protect the splice
Move the heat-shrink sleeve over the splice without bending the bare joint, then use the correct heater cycle. Corning documents heat-shrink sleeves as a common way to protect individual fusion splices.
Step 6: dress the tray
Place the protected splice in its holder and route fibre slack at the tray's intended bend radius. Do not cross fibres unnecessarily or force them under clips. Leave identification visible for future re-entry.
Pigtail splicing
Many installations terminate field cable by fusion-splicing factory-connectorised pigtails in a patch panel or closure. This keeps the field splice inside a protected tray while presenting standard connectors at the front of the panel.
Splice-on connectors
Splice-on connectors use a factory-made connector stub that is fusion-spliced onto the field fibre. They can reduce polishing work in the field but still depend on correct stripping, cleaning, cleaving, splicer compatibility and connector-specific handling.
How to judge the result
- Splicer image/estimated loss is a process check.
- OTDR can locate and characterise splice events.
- End-to-end insertion-loss testing proves the total link loss where required.
- Bidirectional OTDR averaging may be required because backscatter differences can make splice loss appear different from opposite directions.
Common failure causes
| Symptom | Likely area |
|---|---|
| Splicer rejects fibre | Bad cleave, dirt, fibre not seated correctly. |
| High estimated loss | Cleaves, contamination, wrong splice program, fibre mismatch. |
| Splice breaks after heating | Weak/nicked fibre, handling stress, sleeve process. |
| OTDR shows unexpected event loss | Actual splice quality, bend near tray, direction/backscatter effect. |
Client benefit
A disciplined splicing process produces low-loss, protected and traceable joints that can be re-entered and tested later instead of becoming hidden weak points in the fibre route.
WORKED BUSINESS SCENARIO
Scenario: a new fibre link passes traffic but has very little margin
A new inter-building link comes up and carries traffic. The installer sees higher loss than expected and one connector event on the OTDR trace.
What the chapter teaches us: A working link is not the same as a well-commissioned link. The design budget, measured loss, cleanliness, polarity and event location must be understood before handover.
Think it through
- What does OLTS prove that OTDR does not?
- What does OTDR reveal that total loss alone cannot?
- Why should the original test results be saved?
PRACTICAL WORK
Hands-on lab
Build or use a lab fibre link with known connectors or splices. Record calculated loss budget, measured OLTS loss and OTDR event locations.
Troubleshooting exercise
A fibre link is down. Verify optic compatibility, clean and inspect, check DOM levels, test continuity or polarity and then use OLTS or OTDR as appropriate.
Chapter field checklist
- I can explain the subject without relying only on acronyms.
- I can draw or describe the main traffic, storage, power or service path.
- I know what normal operation should look like.
- I know which logs, counters or test results prove the result.
- I can explain the business impact if this component fails.
- I would document the final configuration and evidence at handover.
Chapter summary
Fusion Splicing and Fibre Termination Playbook should now be understood as a business service with a technical implementation, not simply a collection of commands or product names. The important habit is to know the purpose, understand the dependencies, measure the result and document what was proven.
END OF CHAPTER
Review questions
- Explain the subject in plain language to a business owner.
- List the main dependencies that must be healthy before this service can work.
- Describe one realistic failure and the first three pieces of evidence you would collect.
- Explain what should be documented at handover.
- When would you use OLTS and when would you use OTDR?
- Why must connectors be inspected and cleaned before optical testing?
A good answer should explain the reason, not only repeat a product name or command.
Technical references
Use the current project specification and exact manufacturer documentation for the installed products. These references support the technical principles explained here.