Quick answer: Does armored fiber optic cable need to be grounded? A cable with metallic armor or another conductive member may require a project-specific grounding, bonding, or interruption decision. An all-dielectric armored cable does not create the same metallic pathway. Do not decide from the word "armored" alone. Verify the exact construction, route boundary, adopted requirements, AHJ record, and manufacturer's current instructions.
For an active cable review, put the exact part number, construction drawing, route sketch, and building-entry location beside this checklist. If one is missing, ask BWNFiber which product records are available for the offered part and which gap must remain open before quotation or release.
If a datasheet says a fiber cable is armored, the next question is not simply how much protection the armor adds. The approval question is whether the exact construction creates a conductive path, where that path begins and ends, and which project documents control its treatment.
A purchase order tied only to "armored fiber cable" does not identify the electrical construction that the submittal must address. Corning publishes both metallic and all-dielectric armored constructions. The word "armored" does not prove that a cable is conductive or tell the designer what to do at a splice closure, cabinet, building entrance, or termination.
This checklist is for design and submittal review. It is not an electrical design, a code interpretation, or a field installation procedure. Use the code edition adopted by the project jurisdiction, local amendments, the authority having jurisdiction (AHJ), the cable manufacturer's current instructions, and a qualified designer or installer.
Use it only when a project must trace a metallic cable member or confirm that a proposed all-dielectric construction removes that pathway. For ISP and FTTH work, that may be a feeder, building-entry, or interbuilding segment; this is not a drop-cable guide. For telecom EPC and campus or data-center teams, the checklist applies to route interfaces rather than indoor patching. A distributor can use it to collect a customer's submittal inputs, but not as a general armored-cable selection guide.
On this page
- Inventory every metallic component
- Check cable markings at pathway changes
- Draw the electrical continuity boundary
- Match the cable, enclosure, and hardware
- Follow each interface to termination
- Compare metallic and all-dielectric armor
- Build the buyer's minimum record
- Keep decision ownership clear
- Review buyer questions
- Send BWNFiber the project record
Start with the conductive-member question
The review record has one job:
Can the project team trace every conductive member through each interface and identify the document and authority that govern its treatment?
The answer cannot come from a family name alone. Corning's industrial cable specification distinguishes interlocking aluminum armor from corrugated steel-tape armor, while its all-dielectric specification documents a nonconductive armored construction. Those are different electrical and mechanical designs, even though all can be described as armored.
Start with the manufacturer, part number, revision, construction drawing, declared application, and jacket marking. If any one of those is missing, the technical release remains open.
Gate 1: Inventory every metallic component
The visible armor is only one component. A cable can contain other metallic elements, including strength members or moisture barriers. Armor does not settle the question because some armored constructions are all-dielectric.
Build the component list from approved documents, not from a product nickname or an unlabeled marketing image.
| Evidence item | What the reviewer needs to see | Clarify or hold when |
|---|---|---|
| Exact part number and revision | One orderable construction tied to the submittal | The document covers a family but not the offered part number |
| Controlled cross-section or construction drawing | Armor, strength members, barriers, ripcords, jackets, and cable core are labeled | A conductive component is shown but not identified, or the image is illustrative only |
| Material declaration | Each potentially conductive member is named as metallic or dielectric | The description only says "armored" or "FRP reinforced" without the full construction |
| Electrical continuity statement | The manufacturer states which members are continuous and where continuity ends | The statement is absent or conflicts with the drawing |
| Current accessory procedure | The cable construction is compatible with the proposed clamp, strap, enclosure, or isolation method | The procedure applies to another cable or enclosure |
Corning's PGS101 specification provides examples of interlocking aluminum armor and corrugated steel tape. Corning's PGS091 specification provides a contrasting all-dielectric armor example and states that its nonconductive armor does not require bonding or grounding during installation or splicing. These examples establish a review method, not a claim about an unverified BWNFiber model.
Gate 2: Read the jacket legend at each pathway change
A cable can pass the conductive-member review and still fail the route review. Its marking, environmental declaration, fire classification, and declared installation method must match each route segment.
UL's optical-fiber cable marking guidance distinguishes conductive and nonconductive optical cable designations. The guide is dated 2010 and warns that later code changes may not be reflected. Verify the current listing and locally adopted requirements instead of copying a designation from that guide.
For each candidate cable, record:
- the jacket legend exactly as supplied;
- the listing or classification and the source that verifies it;
- the manufacturer's declared indoor, outdoor, duct, aerial, or buried application;
- the installation, storage, and operating limits from the exact datasheet;
- any restriction on entry into a building or transition to an indoor pathway;
- the document revision and review date.
"Armored" is not an installation method. A cable may have armor and still be approved only for a specific indoor, aerial, or duct application. If the project is still choosing between metallic and all-dielectric constructions, compare the current BWNFiber armored and direct-burial cable families first. Then return to this checklist with the candidate part numbers; a category page cannot establish electrical continuity or pathway approval for a specific construction.
Gate 3: Draw the electrical continuity boundary
Building entry is a boundary, not a footnote. NFPA's official NEC development material addresses non-current-carrying metallic members of optical-fiber cables at building entry or outside termination. That development record does not establish the requirement for a live project; the locally adopted edition and the AHJ control the project decision.
Create a transition record before deciding how any conductive member will be treated.
| Route segment | Location and environment | Exact cable and marking | Conductive members | Proposed interface | Governing document | Reviewer / status |
|---|---|---|---|---|---|---|
| Outside plant | Project-specific | Part number and jacket legend | List every member | Closure, handhole, or entry facility | Route drawing and cable data | Open |
| Building entry | Exact penetration or outside termination point | Same cable or transition cable | State continuity at the boundary | Entry cabinet, enclosure, or transition splice | Adopted code, AHJ record, manufacturer procedure | Open |
| Indoor pathway | Room and pathway classification | Exact indoor or indoor/outdoor cable | State whether a conductive path continues | Cabinet, rack, tray, or raceway | Cable listing and project specification | Open |
| Final termination | Equipment location | Exact cable or assembly | State the final continuity boundary | Approved termination hardware | Manufacturer and project detail | Open |
The completed record should show where the outside cable ends, whether a transition cable is used, which conductive members continue through each interface, and who accepted the decision. If the pathway drawing and cable schedule describe different boundaries, stop the technical release until they agree.
Need the exact cable record checked before hardware selection? Send BWNFiber the candidate part number, current datasheet, route boundary, and proposed enclosure. Ask which product records are available, what evidence is missing, and which interface questions still need designer or AHJ decisions. Confirm the scope of this document support when you inquire; it is not project approval.
Gate 4: Match hardware to the enclosure and cable
This gate checks whether the cable, enclosure, accessory, and manufacturer procedure belong together. It does not prescribe a universal grounding method.
CommScope publishes a grounding procedure for armored cable in a named OFDC-C12 closure. Corning publishes armored-cable grounding kits and product-specific procedures. These first-party documents demonstrate that the enclosure, cable construction, clamp or strap, and preparation method must be reviewed as a system. A procedure for one closure is not automatic approval for another.
Include these items in the submittal:
- The manufacturer and part number of the proposed grounding, bonding, or isolation hardware.
- The installation procedure revision that covers the exact cable and interface.
- The cable outside-diameter and armor compatibility range for the hardware.
- The treatment of the visible armor and every metallic strength member or barrier.
- The connection point shown on the approved enclosure or cabinet detail.
- The designer's reference to the adopted code edition and project specification.
- The AHJ or owner decision when the design requires an interpretation.
- The inspection record that will confirm the installed condition.
A generic clamp detail cannot fill a gap in the manufacturer record. Universal conductor sizes, torque values, stripping dimensions, or termination steps also do not belong in a marketing article. Those values belong in the approved project and manufacturer documents.
Gate 5: Keep one interface record from entry to termination
A cable can pass through several physical interfaces before the fibers reach the equipment room. The submittal needs one continuity record that follows the route instead of treating each enclosure as an isolated purchase.
| Interface | Evidence to capture | Approval question |
|---|---|---|
| Splice point | Incoming and outgoing construction drawings, closure model, accessory procedure, and continuity treatment | Does the record show what happens to each conductive member on both sides? |
| Handhole or outside closure | Environmental rating, cable-entry range, armor hardware, corrosion/material compatibility evidence | Is the proposed hardware compatible with the cable and exposure? |
| Building-entry facility | Entry location, route transition, adopted code reference, AHJ or designer decision | Is the treatment documented at the correct project boundary? |
| Cabinet or rack | Approved connection detail and inspection point | Does the enclosure detail agree with the cable and grounding design? |
| Final termination | End-of-path treatment and as-built record | Is there an auditable final boundary for every conductive member? |
Use the same part number, route labels, interface names, and drawing revisions from the purchase record through the as-built package. A changed identifier can hide a break in the electrical continuity record.
When all-dielectric armor changes the design conversation
All-dielectric armor is not the same as unarmored cable. Corning documents armored constructions that use nonconductive materials and do not require armor bonding or grounding. These specifications treat mechanical protection and electrical conductivity as separate selection dimensions.
| Review point | Metallic armored candidate | All-dielectric armored candidate |
|---|---|---|
| Construction identity | The controlled drawing names the armor and every other metallic member | The controlled drawing confirms that the armor, strength members, and barriers are nonconductive |
| Conductive pathway | The route record traces each identified metallic member through every interface | Treat the construction as having no conductive cable pathway only after the exact construction has been verified |
| Grounding or bonding record | The responsible designer documents the approved treatment at each boundary | No metallic armor treatment is needed for a verified nonconductive construction, but route, listing, entry, and enclosure reviews still apply |
| Evidence before purchase | Part number, construction drawing, continuity statement, marking, route boundary, enclosure, accessory, and decision record | Part number, material declaration, marking, route approval, mechanical limits, enclosure compatibility, and decision record |
| Selection question | Can the project approve and inspect every metallic interface? | Does the verified nonconductive construction meet the same route and mechanical requirements? |
Put an all-dielectric candidate into the comparison when the design team wants to avoid a metallic pathway, reduce grounding-interface complexity, or resolve a route-specific electrical concern. It still needs the same review:
- exact part number and construction;
- declared route application;
- required mechanical performance and test methods;
- water-blocking and jacket details;
- cable marking and listing;
- pulling, bend, temperature, and termination limits;
- compatible closures, glands, and accessories;
- project acceptance by the designer and AHJ where applicable.
Avoid the phrase "lightning-safe." An all-dielectric construction removes specified conductive cable members; it does not replace the project's lightning, power-corridor, civil, or safety design.
Build the minimum metallic-pathway record
One review package is easier to approve than a chain of screenshots and sales messages. At minimum, include:
| Buyer record | Evidence to include | Hold the release when |
|---|---|---|
| Cable schedule | Exact manufacturer part number and revision | A family name replaces the orderable construction |
| Product documents | Controlled datasheet and labeled construction drawing | The drawing is illustrative, undated, or tied to another model |
| Marking and application | Jacket marking, listing, and declared application evidence | The route segment is not covered by the supplied declaration |
| Route drawing | Outdoor, entry, indoor, splice, cabinet, and termination points | The cable schedule and pathway drawing show different boundaries |
| Conductive-member register | Armor, strength members, barriers, or messenger components | Any potentially conductive member is unnamed |
| Interface design | Proposed grounding, bonding, or isolation detail from the responsible designer | A sales document or field preference is being treated as design approval |
| Manufacturer procedures | Instructions for the exact cable, enclosure, and accessory hardware | The procedure does not cover the proposed combination |
| Project basis | Adopted code edition, local amendments, project specification, and known AHJ decision | The project relies on an undated article or an unadopted requirement |
| Inspection plan | Acceptance checklist with named owners | No one owns the interface or final inspection record |
| Handover control | As-built, deviation, and revision-control requirements | A field change is not reflected in the accepted record |
Keep unresolved items in a closure register rather than reducing them to a generic score:
| Open item | Close only with | Decision owner | Closure record |
|---|---|---|---|
| Conductivity is unknown | Revised construction drawing or manufacturer declaration | Cable supplier | Document number and revision |
| Jacket marking or application is unclear at a pathway change | Current listing/application record and updated cable schedule | Designer and supplier | Schedule revision |
| Continuity boundary is missing | Approved interface detail | Responsible designer | Drawing or RFI response |
| Cable, enclosure, and accessory compatibility is unproven | Matching manufacturer procedure and part-number range | Supplier and installer | Procedure revision and method statement |
| Code or AHJ interpretation remains open | Written project decision from the responsible authority | Designer or AHJ | Decision reference and date |
Keep supplier, designer, installer, and AHJ decisions separate
| Role | Typical evidence responsibility | What this role should not be assumed to approve |
|---|---|---|
| Cable supplier | Exact part number, controlled datasheet, construction, declared application, available manufacturer procedures, quotation scope | Local code interpretation or the final building grounding design |
| Network or electrical designer | Route boundaries, conductive-member treatment, interface details, project specifications | Unverified manufacturer performance or inventory |
| Installer | Method statement, hardware compatibility check, installation and inspection records | A design change that has not been approved |
| AHJ or project authority | Required interpretation or acceptance within its authority | Manufacturer product truth outside the reviewed submittal |
| Procurement and quality team | Revision control, deviation log, document completeness, release status, as-built handoff | Technical approval based only on a family name or sales description |
Keeping these approvals separate prevents a supplier quotation from being treated as electrical design approval. It also prevents a field method from changing the accepted cable construction without review.
Questions buyers and reviewers ask
Does the word "armored" prove that a cable has a conductive member?
No. Metallic and all-dielectric armored constructions both exist. Review the exact construction drawing and material declaration, including strength members and barriers.
What is the difference between bonding and grounding for armored fiber cable?
Bonding establishes electrical continuity between specified conductive parts. Grounding connects the approved conductive path to the applicable grounding system. The project's adopted requirements, design, AHJ decision, and manufacturer instructions determine how those concepts apply at each interface.
Do metallic strength members count, or only the visible armor?
Review every potentially conductive component. Metallic strength members, moisture barriers, messenger components, or other elements can matter even when the visible armor has already been identified.
Which document should identify every conductive component?
Use the controlled construction drawing or cross-section tied to the exact part number, supported by the current datasheet and manufacturer declaration. A generic family brochure is not enough for final approval.
Can one grounding kit be specified for every armored fiber cable?
No universal compatibility should be assumed. Match the cable construction and diameter, enclosure, accessory part number, and current manufacturer procedure.
Can an armored outside-plant cable enter a building?
The word "armored" does not answer that question. Verify the exact jacket marking and listing, declared application, route and entry point, conductive members, transition method, adopted requirements, manufacturer documents, and the responsible project approval.
How far can outside-plant armored fiber run inside a building?
Do not use a universal distance from an undated article or an older code summary. The answer depends on the locally adopted edition, cable listing, point-of-entry design, pathway, enclosure or transition, and the AHJ's project-specific determination.
Where should a metallic pathway be bonded, grounded, or interrupted?
That location belongs on an approved route and interface detail. The article cannot choose a connection or interruption point without the exact cable, exposure, boundary, enclosure, adopted requirements, and responsible designer's decision.
What should be recorded at a splice closure?
Record the incoming and outgoing cable constructions, the treatment of each conductive member, the closure and accessory part numbers, the approved detail, and the inspection result.
When should the team compare an all-dielectric armored cable?
Compare it when the route needs mechanical protection but the design team wants to avoid a specified metallic cable pathway. The exact model must still pass mechanical, environmental, marking, route, and interface review.
Who confirms the applicable building-entry requirement?
The responsible designer and the AHJ or project authority, using the adopted code edition, local amendments, project specification, route, and manufacturer documentation. A supplier article cannot make that decision for a project.
What documents should procurement request before releasing the purchase order?
Request the exact part number and revision, controlled datasheet and construction drawing, jacket marking and listing evidence, route and interface drawing, conductive-member register, compatible enclosure and accessory procedure, decision record, inspection plan, and deviation-control requirements.
Ask BWNFiber for a conductive-member document check
Ask BWNFiber to tie the inquiry to one offered construction and state which product records can be supplied for that part. Project design decisions remain with the responsible designer and AHJ. Confirm that this document-check scope is available for the offered part; it is not an AHJ approval or a substitute for the responsible designer.
Include these items in the inquiry:
- project location and route drawing;
- exact cable part number or candidate datasheet;
- outdoor, building-entry, and indoor segments;
- known conductive members and open questions;
- enclosure, cabinet, and termination models;
- required listing, standard, or code edition if known;
- quantity, run length, termination format, destination, required documents, and the required submittal or bid date.
Before sending a route drawing that contains sensitive site information, confirm the approved submission channel and whether a sanitized boundary sketch is sufficient.
State the route's network role and every interface point instead of sending only a generic cable request.
Before accepting the supplier response, check that it identifies:
- the exact offered part number and the controlled specification or construction drawing currently available for it;
- a list of missing construction, marking, route, enclosure, accessory, or approval evidence;
- customization or deviation requests that still require written confirmation for the offered construction;
- sample options and the test-document or inspection scope available for the offered part, if requested;
- a quotation scope that states quantity, destination, documentation, and delivery assumptions.
For a sample review, add the evaluation purpose, required length or termination, acceptance method, and destination. Sample availability, customization, test-document scope, price, and delivery timing must be confirmed in the quotation for the exact offered part number.
Send the part number and route record to BWNFiber for a document check. If a sample or quotation is also needed, include the evaluation purpose and quantity in the same inquiry.
Primary sources
- Corning PGS101, Gel-Free Loose Tube Optical Fiber Cables for Industrial LSZH Applications, accessed August 19, 2026.
- Corning PGS091, All Dielectric Armored Riser and Plenum Fiber Optic Cables, accessed August 19, 2026.
- Corning AEN140, Indoor Fiber Optic Bonding and Grounding, accessed August 19, 2026.
- CommScope OFDC-C12 product support page, including the armored-cable grounding instruction, accessed August 19, 2026.
- Corning, Armored Cable Grounding Kits, accessed August 19, 2026.
- UL Solutions, Optical Fiber Cable Markings, accessed August 19, 2026. The document carries an older-edition warning; verify current requirements.
- NFPA, NEC Panel 16 First Draft Public Input Responses for the 2025 development cycle, accessed August 19, 2026. This development record is not a substitute for the locally adopted code.
- TIA, ANSI/TIA-607-E publication announcement, accessed August 19, 2026. The announcement confirms the current standard's scope; it is not the full standard or a project interpretation.
