01 — The Software

Engineering software for cable network construction

Splicer addresses cable network documentation: the records that describe how conductor pairs are joined between cables in the field. It is built around two engines, one for each cable type. Access is restricted to authorised accounts; the platform does not accept public registration.

Available

Copper Splicing Engine

CSE

Produces copper splice tables — the documents that map conductor pairs in a feeder cable onto conductor pairs in one or more field cables at a splice point.

An operator records cable designations and count assignments for a splice location. The engine produces the corresponding splice table, tracks completion as work proceeds, and issues the field documentation the crew carries out.

Work is organised by project, plan, and splice location, so a route is documented as a whole rather than as a pile of isolated splices. The interface is available in English and French.

Feeder-to-field pair mapping across multiple field cables
Binder group segmentation and colour coding
Completion tracked at pair-level granularity
Documents sized for tabloid field prints

Planned

Fiber Splicing Engine

FSE

The companion engine for fiber optic splice documentation is planned. It is not currently available on this platform.

Fiber splice documentation follows a different structure from copper. Strands are organised into buffer tubes rather than binder groups, and colour identification follows the twelve-position fiber standard rather than the twenty-five pair colour code described in Part II.

Strand-to-strand mapping between distribution and drop cables
Buffer tube segmentation and twelve-position colour coding
Splice closure and tray assignment records

02 — Capabilities

What the software can account for

Cable networks are rarely tidy. Pairs are dead, reserved, reversed, or belong to another office; a rearrangement has to be documented in both its old and new state; and what the crew finds on site does not always match what the record says. The full set below.

Available today

Every capability listed here is in the shipping copper engine. The Fiber Splicing Engine named in section 01 is the only planned item anywhere on this page.

01

Multi-cable mapping

Feeder pairs mapped onto one or more field cables at a single splice point, with each field cable presented on its own side of the table.

02

Binder group segmentation

Counts divided into binder groups according to insulation class and conductor gauge, for both paper- and plastic-insulated cable.

03

Binder colour coding

Every group carries its tip and ring colours through to the finished document, including sub-lettering for cables large enough to repeat the sequence.

04

Group size set by hand

Where a cable's construction is unknown or non-standard, group size is stated explicitly for that cable instead of being inferred, so an unusual cable does not have to be forced into a standard one.

05

Super-group lettering

Cables large enough to exhaust the twenty-five colour sequence are handled as lettered sub-groups, each carrying its own identifying colour alongside the group number.

06

Full range of count types

Live assignments alongside dead pairs, fictitious ranges, single reserved positions, reversed counts, and assignments belonging to another central office.

07

Count modifiers combine

A single assignment can be reversed and belong to another central office at the same time. Modifiers stack rather than being mutually exclusive.

08

Before-and-after documentation

Rearrangement work produces both states, so a change can be verified against what was there before once the crew is finished.

09

Validation at entry

Counts that disagree with a cable's declared capacity, ranges that overlap one another, and gauge mismatches between joined cables are raised for the operator rather than silently accepted.

10

Lead sheath detection

Lead sheath construction is recognised from the cable record itself and flagged on documentation, so handling and disposal obligations surface before crews are dispatched.

11

Pair-level completion

Rows are marked as spliced while work proceeds and progress is counted in pairs rather than splices closed, so a job half finished reports as half finished.

12

Route diagram

Access points and the cable runs between them are drawn as a diagram, so a splice is seen in the context of the route it belongs to rather than on its own.

13

Access point records

Poles, access wells, chambers, and central offices are recorded as locations, and each splice is associated with the point at which the work happens.

14

Cable runs identified

A cable run carries its own reference alongside its name and designation, so the same cable stays recognisable across every access point it passes through.

15

Project and plan structure

Work is organised by project, plan, and splice location, so a route is documented as a whole rather than as a pile of unrelated splices.

16

Shared records

A project is visible to its owner and to accounts explicitly granted access, so a planner and a crew work from one record.

17

Bilingual throughout

English and French, selected per user and persisted across sessions, carried through to the exported documents themselves.

18

Field documents that fit the page

Tables export to spreadsheet and print-ready formats, fitted to tabloid rather than shrunk to it, with spliced rows highlighted and a total of pairs spliced.

19

Records corrected from the field

Where the network as built differs from the record, the crew corrects the record on site. The office copy is right before anyone leaves, rather than after somebody remembers to update it.

20

Runs on the device in hand

Installable on phone, tablet, or desktop as one responsive application, with records already retrieved readable when there is no signal to be had.

03 — On the Job Site

What it changes for the crew

The document is read in a handhole, in the weather, with the splice half made. Most of what follows exists because of where the work actually happens.

01

Works with no signal

Records already retrieved stay readable without a network connection. A vault, a rural route, or a bad corner of a service area does not cost the crew their assignments.

02

Printed at a usable size

Documents are laid out for tabloid prints rather than shrunk onto letter paper, so a group and pair range can be read at arm's length in poor light.

03

Lead sheath flagged early

Lead sheath construction is identified from the cable record and flagged on documentation before crews are dispatched, so handling obligations are known before anyone leaves.

04

Groups found by colour

Binder colours are carried onto the document itself, so a group is located by matching a ribbon rather than by counting groups into a bundle.

05

The record gets fixed on the spot

When the network in front of the crew does not match what was documented, the correction goes in from the field — not on a scrap of paper to be transcribed by somebody else, later, if it survives the truck.

06

One record, not three

The planner and the crew work from the same project rather than from a document, a marked-up copy of it, and somebody's memory of what changed.

04 — What It Produces

The document the crew receives

Each row states one continuous range of feeder pairs and the field cable pairs it joins to. The feeder side is presented in green and each field cable in blue, so a technician finds their side of the splice at a glance.

Export

Finished tables export to spreadsheet and print-ready page formats, sized for tabloid field prints, in the language the operator is working in.

Illustrative extract from a copper splice table
Feeder — F1		Field — D22		Field — D41
Grp	Pairs	Grp	Pairs	Grp	Pairs
1	1 – 25	1	1 – 25
2	26 – 50	2	26 – 50
3	51 – 75			1	1 – 25
4	76 – 100			2	26 – 50
5	101 – 125	—	reserved
6	126 – 150	—	not spliced

Active feeder range Active field range Reserved, no live assignment Dead, not spliced

Illustrative extract. Cable names, group numbers, and pair values are examples chosen to show the structure; they do not describe any real cable network. Paired dots reproduce the binder colours described in section 08.

05 — How Work Flows

How a job moves between office and site

A job is planned in the office and carried out on site, and the two do not always agree. The stages below describe how a job travels between them — including what happens when the network turns out to be built differently from its record.

Validation runs while records are entered: counts that disagree with a cable's declared capacity, gauge mismatches between joined cables, and overlapping ranges are raised rather than silently accepted. What no validation can catch is a network that was built differently from its record — which is what the two stages on site are for. Records are corrected while connected; previously retrieved records stay readable when there is no signal.

06 — Delivery Standards

How the software is delivered

Splicer is delivered as a web application built on open standards, with no installer and no separate mobile build. The table below describes delivery characteristics as implemented.

No third-party loading

Every font, stylesheet, script, and image is served from this domain. No content delivery networks and no external resource loading.

Platform delivery specification
Characteristic	Implementation
Transport	All traffic served over TLS. Requests arriving without encryption are redirected to the secure endpoint before any content is returned.
Protocol	HTTP/2 with multiplexed connections and header compression.
Transport policy	HTTP Strict Transport Security declared, instructing browsers to refuse unencrypted connections to this domain.
Client architecture	Progressive web application conforming to the W3C Web App Manifest and Service Worker specifications. Installable on desktop and mobile devices.
Offline behaviour	Previously retrieved records remain readable without a network connection. Calculation and modification require connectivity.
Responsive delivery	Single responsive layout from handheld through widescreen. No separate mobile host.
Accessibility	Semantic document landmarks, keyboard navigation, visible focus indication, and honoured reduced-motion preferences.
Localisation	Bilingual interface, English and French, selectable per user and persisted across sessions.
Asset delivery	All fonts, stylesheets, scripts, and images are served from this domain. No content delivery networks and no third-party resource loading.
Document export	Generated tables export to spreadsheet and print-ready page formats, sized for tabloid field prints.

TLS 1.3 HTTP/2 HSTS Progressive Web App Self-hosted assets No tracking

07 — Security Posture

Controls enforced on this domain

Cable network records describe a network's physical layout, which is why access to them is restricted and the controls below are enforced across the platform.

Scope of this section

Described as posture. No configuration values, thresholds, or product details are published.

Encrypted transport

All content is served exclusively over TLS. Plaintext requests are redirected before any content is returned.

Strict transport security

Browsers are instructed to connect to this domain over HTTPS only, for a long declared duration.

Content Security Policy

A Content Security Policy restricts which sources may contribute executable content and assets to a page.

Framing protection

Embedding this domain's pages within third-party frames is denied, preventing clickjacking.

MIME type enforcement

Content type sniffing is disabled. Browsers must honour the declared type of every response.

Referrer control

Referrer information sent to external destinations is restricted to origin only.

Cross-origin isolation

Browsing contexts are isolated from cross-origin openers, limiting cross-window interference.

Session cookies

Session cookies are marked secure and are not readable by client-side script.

Authentication controls

One active session per account. Sessions terminate automatically after a period of inactivity. Repeated failed authentication is rate limited.

Input handling

Operator-supplied values are escaped before rendering and validated before processing.

Access control

Application endpoints require authentication. Records are visible only to their owner and to accounts explicitly granted access.

No third-party tracking

No analytics, advertising, behavioural tracking, or third-party scripts are served from this domain.

About this page specifically

This page is static. It executes no JavaScript, sets no cookies, uses no local storage, and makes no requests to any external host. Every asset it loads — fonts, styles, and graphics — is served from this domain. These properties are verifiable from the page source and from the network activity of any browser.

08 — Binder Colour Code

The twenty-five pair colour sequence

Pairs are identified by a two-colour scheme: a tip colour drawn from a five-colour sequence and a ring colour drawn from another. Five by five gives twenty-five unique combinations, and that number is fixed. The same sequence marks the binder ribbons inside a cable, which is why a technician can find group 14 without counting to it.

Twenty-five is not the group size

Twenty-five is how many colour combinations exist — not how many pairs a binder ribbon bundles. Group size is a separate property of the cable, and it is not always twenty-five.

Twenty-five pair colour code matrix, tip colour by ring colour
Tip \ Ring	Blue	Orange	Green	Brown	Slate
White	1	2	3	4	5
Red	6	7	8	9	10
Black	11	12	13	14	15
Yellow	16	17	18	19	20
Violet	21	22	23	24	25

Binder group size

How many pairs a binder ribbon actually bundles is set by the cable's insulation class and conductor gauge — not by the colour code above. A hundred-pair group carries the same twenty-five colour sequence as a twenty-five pair group; there are simply more pairs under the ribbon.

25pairs

Plastic-insulated cable. The same group size at every conductor gauge.

50pairs

Paper-insulated cable in the heavier gauges — 19 and 22 AWG.

100pairs

Paper-insulated cable in the lighter gauges — 24 and 26 AWG.

Cables large enough to exhaust the twenty-five sequence repeat it under a second identifying band, so groups are lettered as well as numbered. Where a cable's construction is not known, group size is recorded explicitly rather than assumed, so the uncertainty stays visible.

09 — Glossary

Copper cable splice terminology

Reference definitions for the terms used throughout this document.

Cable designation: The coded identifier carried by every cable, stating how it was built and what it contains: construction and sheath, total pair count, and conductor gauge.
Insulation class: Distinguishes paper-insulated conductors, using pulp and paper tape, from plastic-insulated conductors. The class determines how a cable's pairs divide into binder groups.
Binder group: A bundle of conductor pairs identified by a coloured binder ribbon wrapped around it. Plastic-insulated cable groups in twenty-fives; paper-insulated cable groups in fifties at 19 and 22 AWG and in hundreds at 24 and 26 AWG. Group size is independent of the twenty-five colour sequence, which every group uses whatever its size.
Tip and ring: The two conductors of a pair. Each carries a distinct colour, and the combination identifies the pair within its group.
Pair count: The total number of conductor pairs in a cable. Two insulated conductors twisted together form one pair, carrying one circuit.
Conductor gauge: Conductor diameter expressed in American Wire Gauge. Distribution cable commonly uses 19, 22, 24, and 26 AWG. A larger number denotes a thinner conductor.
Central office: The building housing a network's switching and transmission equipment. Feeder cable originates here and carries circuits outward toward the areas it serves.
Cable network: The physical cable, enclosures, and access points that carry a network beyond the central office, together with the records describing how they are connected. Also called outside plant.
Sheath: The outer covering protecting a cable's conductors from moisture and mechanical damage. Its construction is stated in the cable record and governs how the cable is handled.
Feeder cable: A high pair-count cable carrying circuits from a central office toward a distribution area. At a splice point its pairs are divided among field cables.
Field cable: A distribution cable receiving pairs from a feeder cable at a splice point and carrying them toward service locations.
Splice: The physical joining of conductor pairs between two or more cables, housed in an enclosure at a pole, pedestal, handhole, or vault.
Dead pair: A pair present in the cable but not connected at a given splice point. Dead pairs are recorded so the count remains continuous and unused capacity stays documented.
Fictitious range: A documented range carrying no live assignment, used to hold position in a count where pairs are absent, reserved, or pending rearrangement.
Count change: A rearrangement of existing assignments. Both the previous and the new state are recorded so the change can be verified once the work is complete.
Splice table: The document produced for field use, listing each binder group and pair range on the feeder side alongside the corresponding group and range on each field cable.
Access point: A physical location where cables can be reached and spliced — a pole, handhole, vault, or central office. Splice records are associated with the access point at which the work occurs.
Lead sheath: An older outer sheath construction, identified from the cable record. Its presence carries handling and disposal obligations and is flagged on documentation before crews are dispatched.

surle.cloud