{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/fiber-tier-1-tier-2-acceptance-testing/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/fiber-tier-1-tier-2-acceptance-testing/",
        "slug": "fiber-tier-1-tier-2-acceptance-testing",
        "url": "https://update.dsesecurity.com/updates/fiber-tier-1-tier-2-acceptance-testing/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/fiber-tier-1-tier-2-acceptance-testing.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/fiber-tier-1-tier-2-acceptance-testing/"
        },
        "title": "Accept new fiber with both Tier 1 loss evidence and Tier 2 event evidence",
        "summary": "Tier 1 OLTS testing proves total insertion loss, length, and polarity against the selected limit. Tier 2 OTDR testing adds event location, loss, and reflectance. Specify both where needed, test correctly, and receive native traces—not just a pass/fail PDF.",
        "format": {
            "slug": "checklist",
            "name": "Checklist"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "network-infrastructure",
            "label": "Networks & infrastructure",
            "alt": "Resilient network core with engineered blue and gold data paths.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "business-continuity",
                "name": "Business Continuity",
                "url": "https://update.dsesecurity.com/topic/business-continuity/"
            },
            {
                "slug": "networks-infrastructure",
                "name": "Networks & Infrastructure",
                "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-08-11T09:07:00+00:00",
        "modified_at": "2026-08-11T14:12:11+00:00",
        "reviewed_on": "2026-08-11",
        "reading_minutes": 4,
        "word_count": 685,
        "potentially_affected": "New and renovated multimode and single-mode fiber links; campus backbones, data centers, telecommunications rooms, outside-plant runs, splices, connectors, patch panels, optical loss test sets, OTDRs, and project closeout records.",
        "dse_recommendation": "Define the standard, link model, fiber type, wavelengths, reference method, loss budget, Tier 2 scope, bidirectional requirements, native result format, naming convention, tester calibration, and remediation rules before field testing starts.",
        "primary_source": {
            "name": "Fluke Networks: OTDR—Your Ultimate Troubleshooter",
            "url": "https://www.flukenetworks.com/blog/cabling-chronicles/otdr-your-ultimate-troubleshooter",
            "published_on": "2025-08-11",
            "authority": "Fluke Networks"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<h2>Source facts: Tier 1 and Tier 2 are complementary measurements</h2>\n<p>Fluke Networks’ <a href=\"https://www.flukenetworks.com/blog/cabling-chronicles/otdr-your-ultimate-troubleshooter\" target=\"_blank\" rel=\"noopener noreferrer\">OTDR guidance</a> distinguishes the two common acceptance layers. Tier 1 testing uses an optical loss test set (OLTS) to measure end-to-end insertion loss and commonly length and polarity at the specified wavelengths. The result is compared with the selected standard, application, or project limit. An OLTS provides the most accurate total insertion-loss measurement for acceptance.</p>\n<p>Tier 2 adds an optical time-domain reflectometer (OTDR). An OTDR launches light pulses and analyzes reflection and backscatter over distance, producing a trace and event table for connectors, splices, bends, breaks, and the end of the link. It can show where loss or reflectance occurs and identify a marginal component hidden inside an otherwise acceptable total-loss result.</p>\n<p>Tier 2 does not replace Tier 1. Fluke notes that OTDR-derived total loss is not as accurate or repeatable as the controlled OLTS insertion-loss measurement, particularly for multimode links with defined launch conditions. A complete Tier 2 acceptance therefore retains the Tier 1 OLTS result and adds OTDR characterization.</p>\n<p>Direction matters to OTDR event loss. Differences in fiber backscatter can make a splice appear to gain power in one direction or exaggerate its loss in the other. Bidirectional results are averaged to estimate the event correctly. Launch and tail fibers are needed to characterize the first and last connectors, which otherwise sit inside the instrument’s dead zones. The tested wavelengths must match the fiber, standard, application, and contract. Separately, ANSI/TIA-568.3-E is the current TIA optical-fiber cabling and component standard announced by the Telecommunications Industry Association in September 2022; the exact project edition and limits should be stated rather than implied.</p>\n\n<h2>DSE recommendation: write the acceptance specification before the pull</h2>\n<p>Put the test requirement in the design and contract before installation. For every link class, define:</p>\n<ul>\n<li>link identifier, endpoints, pathway, fiber type, strand count, connector and polish, splice plan, and link model;</li>\n<li>governing standard and edition, application limits where relevant, project loss budget, wavelengths, and pass/fail method;</li>\n<li>Tier 1 OLTS configuration, reference method, test-reference cords, polarity and length requirements;</li>\n<li>Tier 2 OTDR scope, both-direction requirement, launch and tail cords, event-loss and reflectance limits, and trace settings;</li>\n<li>tester model, software version, calibration status, technician qualification, native result format, PDF report, and file naming;</li>\n<li>inspection and cleaning procedure, failed-link remediation, retest, witness sampling, and final acceptance authority.</li>\n</ul>\n<p>At the start of testing, verify tester time, project limits, fiber and wavelength selection, reference method, cords, launch conditions, and calibration. Inspect and clean connector end faces before reference and measurement; a contaminated test cord can create bad results across an entire project. Preserve the reference result and tester configuration with the job record.</p>\n<ol>\n<li><strong>Run Tier 1 on every required strand.</strong> Capture insertion loss, length, and polarity at all specified wavelengths. Investigate marginal results rather than accepting a pass that leaves no allowance for aging, moves, or additional connections.</li>\n<li><strong>Run Tier 2 where specified.</strong> Test from both directions with appropriate launch and tail fibers. Review the trace and event table, not only the instrument’s overall badge. Reconcile the number and position of events with drawings and splice records.</li>\n<li><strong>Remediate the cause.</strong> Clean, reterminate, resplice, relieve a bend, repair damage, or correct polarity through an approved method, then rerun the complete required test. Do not edit a report or delete the failing direction.</li>\n<li><strong>Normalize the closeout package.</strong> Require one identifier across label, drawing, OLTS record, OTDR traces, splice record, panel schedule, and asset system. Receive native tester files so future engineers can reopen traces, plus durable human-readable reports.</li>\n<li><strong>Sample the evidence.</strong> Independently review all failures and marginal passes and witness a representative cross-section of distances, pathways, crews, panels, and fiber types before final acceptance.</li>\n</ol>\n<p>Keep baseline traces for future moves and troubleshooting. When a later outage occurs, comparison with the accepted event map can distinguish a new bend, splice, connector, or break from an original condition. The project is complete when the owner receives traceable proof of total link performance and component-level workmanship—not when light merely appears at the far end.</p>\n\n<h2>Official references</h2>\n<ul>\n<li>Fluke Networks, <a href=\"https://www.flukenetworks.com/blog/cabling-chronicles/otdr-your-ultimate-troubleshooter\" target=\"_blank\" rel=\"noopener noreferrer\"><em>OTDR: Your Ultimate Troubleshooter</em></a>, August 11, 2025.</li>\n<li>Telecommunications Industry Association, <a href=\"https://tiaonline.org/standardannouncement/tia-issues-updated-optical-fiber-cabling-component-standard-ansi-tia-568-3-e/\" target=\"_blank\" rel=\"noopener noreferrer\"><em>TIA Issues Updated Optical Fiber Cabling Component Standard, ANSI/TIA-568.3-E</em></a>, September 29, 2022.</li>\n</ul>",
        "content_text": "Source facts: Tier 1 and Tier 2 are complementary measurements\nFluke Networks’ OTDR guidance distinguishes the two common acceptance layers. Tier 1 testing uses an optical loss test set (OLTS) to measure end-to-end insertion loss and commonly length and polarity at the specified wavelengths. The result is compared with the selected standard, application, or project limit. An OLTS provides the most accurate total insertion-loss measurement for acceptance.\nTier 2 adds an optical time-domain reflectometer (OTDR). An OTDR launches light pulses and analyzes reflection and backscatter over distance, producing a trace and event table for connectors, splices, bends, breaks, and the end of the link. It can show where loss or reflectance occurs and identify a marginal component hidden inside an otherwise acceptable total-loss result.\nTier 2 does not replace Tier 1. Fluke notes that OTDR-derived total loss is not as accurate or repeatable as the controlled OLTS insertion-loss measurement, particularly for multimode links with defined launch conditions. A complete Tier 2 acceptance therefore retains the Tier 1 OLTS result and adds OTDR characterization.\nDirection matters to OTDR event loss. Differences in fiber backscatter can make a splice appear to gain power in one direction or exaggerate its loss in the other. Bidirectional results are averaged to estimate the event correctly. Launch and tail fibers are needed to characterize the first and last connectors, which otherwise sit inside the instrument’s dead zones. The tested wavelengths must match the fiber, standard, application, and contract. Separately, ANSI/TIA-568.3-E is the current TIA optical-fiber cabling and component standard announced by the Telecommunications Industry Association in September 2022; the exact project edition and limits should be stated rather than implied.\n\nDSE recommendation: write the acceptance specification before the pull\nPut the test requirement in the design and contract before installation. For every link class, define:\n\nlink identifier, endpoints, pathway, fiber type, strand count, connector and polish, splice plan, and link model;\ngoverning standard and edition, application limits where relevant, project loss budget, wavelengths, and pass/fail method;\nTier 1 OLTS configuration, reference method, test-reference cords, polarity and length requirements;\nTier 2 OTDR scope, both-direction requirement, launch and tail cords, event-loss and reflectance limits, and trace settings;\ntester model, software version, calibration status, technician qualification, native result format, PDF report, and file naming;\ninspection and cleaning procedure, failed-link remediation, retest, witness sampling, and final acceptance authority.\n\nAt the start of testing, verify tester time, project limits, fiber and wavelength selection, reference method, cords, launch conditions, and calibration. Inspect and clean connector end faces before reference and measurement; a contaminated test cord can create bad results across an entire project. Preserve the reference result and tester configuration with the job record.\n\nRun Tier 1 on every required strand. Capture insertion loss, length, and polarity at all specified wavelengths. Investigate marginal results rather than accepting a pass that leaves no allowance for aging, moves, or additional connections.\nRun Tier 2 where specified. Test from both directions with appropriate launch and tail fibers. Review the trace and event table, not only the instrument’s overall badge. Reconcile the number and position of events with drawings and splice records.\nRemediate the cause. Clean, reterminate, resplice, relieve a bend, repair damage, or correct polarity through an approved method, then rerun the complete required test. Do not edit a report or delete the failing direction.\nNormalize the closeout package. Require one identifier across label, drawing, OLTS record, OTDR traces, splice record, panel schedule, and asset system. Receive native tester files so future engineers can reopen traces, plus durable human-readable reports.\nSample the evidence. Independently review all failures and marginal passes and witness a representative cross-section of distances, pathways, crews, panels, and fiber types before final acceptance.\n\nKeep baseline traces for future moves and troubleshooting. When a later outage occurs, comparison with the accepted event map can distinguish a new bend, splice, connector, or break from an original condition. The project is complete when the owner receives traceable proof of total link performance and component-level workmanship—not when light merely appears at the far end.\n\nOfficial references\n\nFluke Networks, OTDR: Your Ultimate Troubleshooter, August 11, 2025.\nTelecommunications Industry Association, TIA Issues Updated Optical Fiber Cabling Component Standard, ANSI/TIA-568.3-E, September 29, 2022.",
        "content_markdown": "## Source facts: Tier 1 and Tier 2 are complementary measurements\n\nFluke Networks’ [OTDR guidance](https://www.flukenetworks.com/blog/cabling-chronicles/otdr-your-ultimate-troubleshooter) distinguishes the two common acceptance layers. Tier 1 testing uses an optical loss test set (OLTS) to measure end-to-end insertion loss and commonly length and polarity at the specified wavelengths. The result is compared with the selected standard, application, or project limit. An OLTS provides the most accurate total insertion-loss measurement for acceptance.\n\nTier 2 adds an optical time-domain reflectometer (OTDR). An OTDR launches light pulses and analyzes reflection and backscatter over distance, producing a trace and event table for connectors, splices, bends, breaks, and the end of the link. It can show where loss or reflectance occurs and identify a marginal component hidden inside an otherwise acceptable total-loss result.\n\nTier 2 does not replace Tier 1. Fluke notes that OTDR-derived total loss is not as accurate or repeatable as the controlled OLTS insertion-loss measurement, particularly for multimode links with defined launch conditions. A complete Tier 2 acceptance therefore retains the Tier 1 OLTS result and adds OTDR characterization.\n\nDirection matters to OTDR event loss. Differences in fiber backscatter can make a splice appear to gain power in one direction or exaggerate its loss in the other. Bidirectional results are averaged to estimate the event correctly. Launch and tail fibers are needed to characterize the first and last connectors, which otherwise sit inside the instrument’s dead zones. The tested wavelengths must match the fiber, standard, application, and contract. Separately, ANSI/TIA-568.3-E is the current TIA optical-fiber cabling and component standard announced by the Telecommunications Industry Association in September 2022; the exact project edition and limits should be stated rather than implied.\n\n## DSE recommendation: write the acceptance specification before the pull\n\nPut the test requirement in the design and contract before installation. For every link class, define:\n\n- link identifier, endpoints, pathway, fiber type, strand count, connector and polish, splice plan, and link model;\n\n- governing standard and edition, application limits where relevant, project loss budget, wavelengths, and pass/fail method;\n\n- Tier 1 OLTS configuration, reference method, test-reference cords, polarity and length requirements;\n\n- Tier 2 OTDR scope, both-direction requirement, launch and tail cords, event-loss and reflectance limits, and trace settings;\n\n- tester model, software version, calibration status, technician qualification, native result format, PDF report, and file naming;\n\n- inspection and cleaning procedure, failed-link remediation, retest, witness sampling, and final acceptance authority.\n\nAt the start of testing, verify tester time, project limits, fiber and wavelength selection, reference method, cords, launch conditions, and calibration. Inspect and clean connector end faces before reference and measurement; a contaminated test cord can create bad results across an entire project. Preserve the reference result and tester configuration with the job record.\n\n- Run Tier 1 on every required strand. Capture insertion loss, length, and polarity at all specified wavelengths. Investigate marginal results rather than accepting a pass that leaves no allowance for aging, moves, or additional connections.\n\n- Run Tier 2 where specified. Test from both directions with appropriate launch and tail fibers. Review the trace and event table, not only the instrument’s overall badge. Reconcile the number and position of events with drawings and splice records.\n\n- Remediate the cause. Clean, reterminate, resplice, relieve a bend, repair damage, or correct polarity through an approved method, then rerun the complete required test. Do not edit a report or delete the failing direction.\n\n- Normalize the closeout package. Require one identifier across label, drawing, OLTS record, OTDR traces, splice record, panel schedule, and asset system. Receive native tester files so future engineers can reopen traces, plus durable human-readable reports.\n\n- Sample the evidence. Independently review all failures and marginal passes and witness a representative cross-section of distances, pathways, crews, panels, and fiber types before final acceptance.\n\nKeep baseline traces for future moves and troubleshooting. When a later outage occurs, comparison with the accepted event map can distinguish a new bend, splice, connector, or break from an original condition. The project is complete when the owner receives traceable proof of total link performance and component-level workmanship—not when light merely appears at the far end.\n\n## Official references\n\n- Fluke Networks, [OTDR: Your Ultimate Troubleshooter](https://www.flukenetworks.com/blog/cabling-chronicles/otdr-your-ultimate-troubleshooter), August 11, 2025.\n\n- Telecommunications Industry Association, [TIA Issues Updated Optical Fiber Cabling Component Standard, ANSI/TIA-568.3-E](https://tiaonline.org/standardannouncement/tia-issues-updated-optical-fiber-cabling-component-standard-ansi-tia-568-3-e/), September 29, 2022."
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/fiber-tier-1-tier-2-acceptance-testing/",
                "url": "https://update.dsesecurity.com/updates/fiber-tier-1-tier-2-acceptance-testing/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-11"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/fiber-tier-1-tier-2-acceptance-testing/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Accept new fiber with both Tier 1 loss evidence and Tier 2 event evidence",
                        "item": "https://update.dsesecurity.com/updates/fiber-tier-1-tier-2-acceptance-testing/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/fiber-tier-1-tier-2-acceptance-testing/#article",
                "identifier": "https://update.dsesecurity.com/updates/fiber-tier-1-tier-2-acceptance-testing/",
                "url": "https://update.dsesecurity.com/updates/fiber-tier-1-tier-2-acceptance-testing/",
                "headline": "Accept new fiber with both Tier 1 loss evidence and Tier 2 event evidence",
                "description": "Tier 1 OLTS testing proves total insertion loss, length, and polarity against the selected limit. Tier 2 OTDR testing adds event location, loss, and…",
                "abstract": "Tier 1 OLTS testing proves total insertion loss, length, and polarity against the selected limit. Tier 2 OTDR testing adds event location, loss, and reflectance. Specify both where needed, test correctly, and receive native traces—not just a pass/fail PDF.",
                "articleBody": "Source facts: Tier 1 and Tier 2 are complementary measurements\nFluke Networks’ OTDR guidance distinguishes the two common acceptance layers. Tier 1 testing uses an optical loss test set (OLTS) to measure end-to-end insertion loss and commonly length and polarity at the specified wavelengths. The result is compared with the selected standard, application, or project limit. An OLTS provides the most accurate total insertion-loss measurement for acceptance.\nTier 2 adds an optical time-domain reflectometer (OTDR). An OTDR launches light pulses and analyzes reflection and backscatter over distance, producing a trace and event table for connectors, splices, bends, breaks, and the end of the link. It can show where loss or reflectance occurs and identify a marginal component hidden inside an otherwise acceptable total-loss result.\nTier 2 does not replace Tier 1. Fluke notes that OTDR-derived total loss is not as accurate or repeatable as the controlled OLTS insertion-loss measurement, particularly for multimode links with defined launch conditions. A complete Tier 2 acceptance therefore retains the Tier 1 OLTS result and adds OTDR characterization.\nDirection matters to OTDR event loss. Differences in fiber backscatter can make a splice appear to gain power in one direction or exaggerate its loss in the other. Bidirectional results are averaged to estimate the event correctly. Launch and tail fibers are needed to characterize the first and last connectors, which otherwise sit inside the instrument’s dead zones. The tested wavelengths must match the fiber, standard, application, and contract. Separately, ANSI/TIA-568.3-E is the current TIA optical-fiber cabling and component standard announced by the Telecommunications Industry Association in September 2022; the exact project edition and limits should be stated rather than implied.\n\nDSE recommendation: write the acceptance specification before the pull\nPut the test requirement in the design and contract before installation. For every link class, define:\n\nlink identifier, endpoints, pathway, fiber type, strand count, connector and polish, splice plan, and link model;\ngoverning standard and edition, application limits where relevant, project loss budget, wavelengths, and pass/fail method;\nTier 1 OLTS configuration, reference method, test-reference cords, polarity and length requirements;\nTier 2 OTDR scope, both-direction requirement, launch and tail cords, event-loss and reflectance limits, and trace settings;\ntester model, software version, calibration status, technician qualification, native result format, PDF report, and file naming;\ninspection and cleaning procedure, failed-link remediation, retest, witness sampling, and final acceptance authority.\n\nAt the start of testing, verify tester time, project limits, fiber and wavelength selection, reference method, cords, launch conditions, and calibration. Inspect and clean connector end faces before reference and measurement; a contaminated test cord can create bad results across an entire project. Preserve the reference result and tester configuration with the job record.\n\nRun Tier 1 on every required strand. Capture insertion loss, length, and polarity at all specified wavelengths. Investigate marginal results rather than accepting a pass that leaves no allowance for aging, moves, or additional connections.\nRun Tier 2 where specified. Test from both directions with appropriate launch and tail fibers. Review the trace and event table, not only the instrument’s overall badge. Reconcile the number and position of events with drawings and splice records.\nRemediate the cause. Clean, reterminate, resplice, relieve a bend, repair damage, or correct polarity through an approved method, then rerun the complete required test. Do not edit a report or delete the failing direction.\nNormalize the closeout package. Require one identifier across label, drawing, OLTS record, OTDR traces, splice record, panel schedule, and asset system. Receive native tester files so future engineers can reopen traces, plus durable human-readable reports.\nSample the evidence. Independently review all failures and marginal passes and witness a representative cross-section of distances, pathways, crews, panels, and fiber types before final acceptance.\n\nKeep baseline traces for future moves and troubleshooting. When a later outage occurs, comparison with the accepted event map can distinguish a new bend, splice, connector, or break from an original condition. The project is complete when the owner receives traceable proof of total link performance and component-level workmanship—not when light merely appears at the far end.\n\nOfficial references\n\nFluke Networks, OTDR: Your Ultimate Troubleshooter, August 11, 2025.\nTelecommunications Industry Association, TIA Issues Updated Optical Fiber Cabling Component Standard, ANSI/TIA-568.3-E, September 29, 2022.",
                "datePublished": "2026-08-11T09:07:00+00:00",
                "dateModified": "2026-08-11T14:12:11+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/fiber-tier-1-tier-2-acceptance-testing/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/fiber-tier-1-tier-2-acceptance-testing/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Accept new fiber with both Tier 1 loss evidence and Tier 2 event evidence"
                },
                "articleSection": [
                    "Business Continuity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Business Continuity",
                    "Networks & Infrastructure",
                    "Checklist",
                    "Advisory priority"
                ],
                "genre": "Checklist",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Business Continuity",
                        "url": "https://update.dsesecurity.com/topic/business-continuity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 685,
                "timeRequired": "PT4M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "Fluke Networks: OTDR—Your Ultimate Troubleshooter",
                    "url": "https://www.flukenetworks.com/blog/cabling-chronicles/otdr-your-ultimate-troubleshooter",
                    "datePublished": "2025-08-11"
                }
            }
        ]
    }
}