Splice Matrix Builder^beta

It lays out a single fiber splice point the way it's actually spliced: any number of cables in and out, each cable's count stack, and every fiber-to-fiber connection. Collapse a big cable to its tubes to see the whole splice at a glance, then expand the one group you're working to the individual fiber.

A count is a named circuit set — for example ABCD001, 1-288. That name and number identify a circuit that persists across the whole network, so you splice through by matching the same name and number on both sides. Each cable carries one or more counts that partition its fibers. Use XD or dead for spare/dead fibers; anything you don't assign is filled with XD automatically.

Yes. Click Scan Splice, upload a photo or PDF, frame the splice point you want, and the builder reads each cable's stack and builds the matrix. You can also scan one cable at a time from the cable editor. New here? Click Sample Splice to drop in a ready-made splice and poke around.

Yes. Import Files takes a PDF or CSV — a count sheet, or an OSP cable schedule from a print set. Drop in one or both end sheets, then pick which cables to build from the list it finds. Reading happens in your browser, so a well-formed sheet never leaves your device.

Cable schedules are usually rotated tables: each attribute is a row running across the page and each pigtail is a column. The reader works that out, tells the pre-terminated end from the fusion-spliced end, and flags the usual print problems — a letter O in a cable id, a mistyped path — instead of quietly accepting them.

A sheet often carries dozens of cables, so you pick which to build from a list. Schedules give strand ranges but never the ribbon structure, so you also set fibers per ribbon and ribbons per group at that point. Build several and a Run selector appears above the matrix to move between them.

No. One sheet is a complete splice point — the pigtails, the fusion splice, and the OSP cable they land on — which is all you need to work that end. The far end shows as an open stub, and importing the other sheet later fills it in and splices the run through.

An OSP backbone is spliced at both ends: a pre-terminated pigtail lands on a cassette or FAP in each building, and each one is fusion-spliced to the OSP cable running between them. Import both sheets and you get the whole run; import one and you get that end's splice point.

It's drawn to scale. A 192F pigtail is a quarter the height of its 864F OSP cable and sits beside the exact quarter it serves, so the picture itself shows which strands go where. Ribbon lines carry through, and strands the cable doesn't use (a 385-432 gap, say) are marked rather than hidden.

If the builder can't read a file on its own — a scan with no text in it, or an unfamiliar layout — it asks you a question rather than guessing, because a wrong guess makes a diagram that looks right and isn't. You get a plain question with a few options, plus a box to describe the sheet in your own words. Only files it couldn't read are sent for help; the rest stay on your device.

Drop a file on the box when you open the tool — a photo of a work print, a PDF, or a CSV. It works out what it is: a schedule goes to the importer, a photo goes to the scanner. There is also Start from scratch if you would rather add cables by hand, and Load a sample splice to look around first.

Once something is loaded the controls appear above the matrix, grouped as Build, Controls, Splice details and Export. On a phone those four sit behind tabs — tap one to bring that card forward.

Yes. Each cable has a ⠿ grip in its header. Drag it to reorder cables within a column, to slide one further down so it lines up opposite its counterpart, or straight across to move it between cables in and cables out. Drag near the edge and the view scrolls with you.

A cable cannot splice to its own side, so moving one across removes its splices — it tells you how many first. Auto-arrange re-stacks everything to cross as few lines as possible, which also clears any gaps you placed by hand.

Print is what you see on screen, straight to your printer. PDF, PNG and SVG are emailed to you while the builder is in beta — you are already signed in, so there is nothing extra to fill in and the file goes to that address. Save keeps the splice on your account so you can reopen it later from My splices.

The file is still built in your browser from exactly what is on screen; it is sent only so it can be attached, and nothing is kept on our side.

TIA-598-D, IEC 60304, and VDE 0888 — including loose-tube and ribbon-stack cables, with fiber color cycling per ribbon exactly like the color chart builder.

The builder is free while in beta and your matrix stays in your browser. You sign in once with your email, and exports are emailed to that address rather than downloaded.

A well-formed schedule is read entirely on your device and never leaves it. Only a sheet the reader cannot handle on its own, or an image you scan, gets sent out to be read — and the file is not stored either way.