A rack-mounted PLC splitter should be approved as a complete assembly, not as a split ratio plus a generic 19-inch label. The optical device, front-panel interface, chassis, internal fiber routing and ordered documents must all refer to the same model and revision. Use this guide to control fit, serviceability, port identity, acceptance evidence and quotation scope before release.
Start with the assembled product, not the label
“Rack mounted” describes an installation format, but it does not define the complete deliverable. A supplier may offer an integrated rack panel with the splitter and adapters inside one chassis, or a host chassis populated with removable splitter modules. Those options can serve similar network functions while using different drawings, service boundaries and order codes.
Before comparing offers, define the assembly boundary. State whether the quotation includes the splitter device, chassis, adapters, pigtails, splice protection, cable management, labels, mounting hardware and test documentation. If one offer includes only an optical module and another includes a finished rack assembly, their prices and lead times are not directly comparable.
Control five layers of the rack-mounted assembly
Review the product through five linked layers:
- Optical device: topology, split ratio, fiber type, operating wavelengths and model-level optical limits.
- Front-panel interface: adapter type, connector polish, port count, port identifiers and access direction.
- Rack chassis: rack format, height, depth, mounting-ear position, material and service access.
- Internal assembly: pigtail routing, splice protection, splitter retention, bend management and strain relief.
- Ordered deliverable: exact model, drawing revision, BOM, labeling, packing and document pack.
A release record should connect all five layers to one offered model. Do not infer an interface from a catalog photograph or approve the rack fit from a family-page description alone.
Integrated rack panel or modules in a host chassis?
An integrated panel puts the splitter, internal routing and front adapters inside one controlled chassis. A modular arrangement uses one or more splitter modules inside a named host. Neither architecture is automatically better; the decision depends on capacity, service strategy, spare policy, access and the approved rack layout.
For an integrated panel, confirm the complete chassis drawing and front-to-rear service boundary. For a modular design, identify both the module and the compatible host chassis. “LGX style” or a similar form-factor label is not a dimensional approval. The module drawing, retention method, orientation, connector access and host slot geometry must agree.
| Review item | Integrated rack panel | Modules in a host chassis |
|---|---|---|
| Primary controlled drawing | Complete panel assembly | Host chassis plus module drawing |
| Capacity statement | Ports and splitters in the finished panel | Slots, module quantity and port allocation |
| Service boundary | Usually the complete panel | Host and replaceable module boundaries |
| Spare strategy | Complete panel or internal service parts | Spare modules and compatible host capacity |
| Approval risk | Hidden internal BOM differences | Module-to-host compatibility assumptions |
Verify rack fit and serviceability
A nominal 19-inch format does not prove that the assembly fits the selected rack or can be serviced after installation. Check the exact drawing against the rack layout and adjacent equipment.
Record rack-unit height, chassis width and depth, mounting-ear position, front and rear projection, door clearance, cable-entry direction and access required for connectors or covers. Verify that patch-cord routing does not block neighboring equipment and that the minimum bend control used by the project can be maintained with the door closed.
The review should also identify whether installation or service requires rear access. A panel that physically fits may still be unsuitable if technicians cannot reach internal splices, labels or retention points in the selected cabinet.
Freeze the port map and interface schedule
The front-panel port map connects the optical topology to field labeling and acceptance records. Specify every input and output identifier, adapter type, connector polish and any reserved or unused position. The port map on the drawing, labels on the delivered unit and test-record channel names should use the same identifiers.
Do not treat color alone as proof of connector polish. Record APC or UPC explicitly in the interface schedule and verify that the mating components match. If the order includes pigtails or pre-terminated leads, include their fiber type, length reference and termination in the BOM.
For multi-splitter panels, define whether ports are grouped by splitter, service area or another controlled scheme. A technician should be able to trace each front port to the correct optical input without reconstructing the internal routing from photographs.
Separate component tests from installed-route acceptance
Model-level component evidence and installed-route testing answer different questions. A supplier test record can document the identified splitter assembly under the stated method, wavelengths and limits. Field acceptance evaluates the route after connectors, splices, patching and installation have been added.
Keep the two evidence sets traceable but separate. For the product record, require the exact model or unit identity, test method, wavelength, direction, port path, contractual limit and result. For the installed route, use the project-approved method and preserve the route, equipment, reference condition and acceptance decision.
An OTDR trace can support event location and comparative route analysis when the topology is known, but it does not replace the splitter port map or the agreed component measurement record. Establish the acceptance plan before shipment so that a failed result can be investigated against the correct scope.
Require a controlled five-document submittal
Before purchase release, request a document pack for the exact offered configuration:
- current product datasheet;
- dimensional drawing and front-panel port map;
- itemized BOM and interface schedule;
- inspection and test plan with a representative record format;
- labeling, packing and delivery controls.
Each document should identify the applicable model and revision. If a supplier proposes a deviation, record it against the same requirement baseline instead of accepting it through an informal email or an altered photograph.
Normalize quotations before comparing price
Build a comparison matrix using the same fields for every bidder. Confirm the assembly boundary, rack format, splitter topology, interfaces, fiber and lead details, optical evidence, documents, packing, quantity and destination. Classify each field as matched, approved variance or open.
Only compare price and delivery after the open technical fields are closed or clearly priced as options. This prevents a lower quotation from winning simply because it excludes the host chassis, adapters, test reports or project-specific labeling included by another supplier.
| Quotation field | Required response |
|---|---|
| Offered model and revision | Exact identifier |
| Assembly boundary | Included chassis, splitter, adapters, pigtails and accessories |
| Rack and access | Dimensions, mounting and service direction |
| Port and interface map | Controlled drawing reference |
| Optical evidence | Method, wavelengths, limits, sampling and report format |
| Commercial scope | Quantity, packing, destination, schedule and approved options |
Use approve, conditional approval, hold or reject
Release the submittal with a recorded decision:
- Approve when all order-critical fields and documents match the requirement.
- Approve with conditions when limited actions are assigned, dated and do not change the released configuration.
- Hold when evidence, fit, interface or assembly scope remains unresolved.
- Reject when a controlled requirement is not met and no approved deviation exists.
A hold is not a failure; it prevents purchasing from moving ahead with assumptions. Record the open item, owner, required evidence and closure date. Reopen the review when any controlled input changes, including the chassis, splitter ratio, connector interface, port map or document revision.
Rack-mounted PLC splitter RFQ checklist
Send the supplier enough information to quote one defined assembly:
- network topology and split ratio;
- required port count and front-panel map;
- fiber type, connector type and polish;
- rack format, available space and access constraints;
- pigtail, splice and cable-management scope;
- optical test basis and report requirements;
- labeling, packing, destination and quantity;
- required drawings, samples or first-article review;
- target schedule and permitted alternatives.
Ask the supplier to identify every exception in writing. The final purchase order should reference the approved model, drawing, BOM and document revisions rather than a generic rack-mounted splitter description.
Frequently asked questions
Is every rack-mounted PLC splitter compatible with a 19-inch rack?
No. Confirm the exact chassis dimensions, mounting-ear position, projection, door clearance, cable routing and service access against the selected rack.
Is an LGX-style splitter module interchangeable between host chassis?
Not automatically. Verify the module and host drawings, slot geometry, retention method, orientation, interfaces and service access for the named models.
What should appear on the port map?
Show each input and output identifier, splitter grouping, adapter type, connector polish and any reserved positions. The drawing, front labels and test-record channel names should agree.
Does a factory splitter test replace field acceptance?
No. Product evidence applies to the identified assembly under its recorded method. Installed-route acceptance includes the connectors, splices, patching and installation added in the field.
What should be sent for a quotation?
Send the topology, port map, interfaces, rack constraints, complete assembly boundary, optical evidence requirements, quantity, destination, documents and target schedule. Request a written exception list for anything the supplier cannot match.
Send a reviewable rack-splitter configuration
For a configuration review, send BWNFiber the rack layout, required split ratio, port map, interface schedule, assembly boundary and document requirements. A model-level response can then identify the proposed configuration, open items and evidence needed before quotation or sample approval.
