{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/tie-powered-industrial-truck-authorization-to-training-and-equipment-condition/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/tie-powered-industrial-truck-authorization-to-training-and-equipment-condition/",
        "slug": "tie-powered-industrial-truck-authorization-to-training-and-equipment-condition",
        "url": "https://update.dsesecurity.com/updates/tie-powered-industrial-truck-authorization-to-training-and-equipment-condition/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/tie-powered-industrial-truck-authorization-to-training-and-equipment-condition.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/tie-powered-industrial-truck-authorization-to-training-and-equipment-condition/"
        },
        "title": "Tie powered-industrial-truck authorization to training and equipment condition",
        "summary": "Use 29 CFR 1910.178 - Powered industrial trucks to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "playbook",
            "name": "Playbook"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "physical-security",
            "label": "Physical security",
            "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "access-control",
                "name": "Access Control",
                "url": "https://update.dsesecurity.com/topic/access-control/"
            },
            {
                "slug": "business-continuity",
                "name": "Business Continuity",
                "url": "https://update.dsesecurity.com/topic/business-continuity/"
            },
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            }
        ],
        "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-27T12:12:16+00:00",
        "modified_at": "2026-08-27T13:04:10+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 593,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 29 CFR 1910.178 - Powered industrial trucks",
        "dse_recommendation": "Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards.",
        "primary_source": {
            "name": "29 CFR 1910.178 - Powered industrial trucks",
            "url": "https://www.ecfr.gov/current/title-29/section-1910.178",
            "published_on": null,
            "authority": "www.ecfr.gov"
        },
        "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": "<p>Keep this document to one review outcome: Tie powered-industrial-truck authorization to training and equipment condition. Only the official source and traced locations below supply facts. Confirm applicability before acting.</p>\n<h2>Source fact:</h2>\n<p>The official <a href=\"https://www.ecfr.gov/current/title-29/section-1910.178\" target=\"_blank\" rel=\"noopener noreferrer\">29 CFR 1910.178 &#8211; Powered industrial trucks</a> from Occupational Safety and Health Administration via eCFR supports the following bounded statements:</p>\n<ul>\n<li>Under 29 CFR 1910, the rule requires that all operator training and evaluation be conducted by persons who have the knowledge, training, and experience to train powered industrial truck operators and evaluate their competence. The research record locates this support at <strong>29 CFR 1910.178(l)(2)(iii) (eCFR anchor p-1910.178(l)(2)(iii))</strong>.</li>\n<li>Under 29 CFR 1910, the rule requires that the employer ensure that each powered industrial truck operator is competent to operate a powered industrial truck safely, as demonstrated by the successful completion of the training and evaluation specified in this paragraph (l). The research record locates this support at <strong>29 CFR 1910.178(l)(1)(i) (eCFR anchor p-1910.178(l)(1)(i))</strong>.</li>\n</ul>\n<p>Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths and the conditions the source actually describes.</p>\n<h2>What the source does not establish</h2>\n<p>Federal workplace rule; truck type, environment, attachments, hazardous locations, traffic plan, and state-plan requirements affect the controls. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders and the environment&#8217;s recorded constraints.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>29 CFR 1910.178(l)(2)(iii) (eCFR anchor p-1910.178(l)(2)(iii))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>29 CFR 1910.178(l)(1)(i) (eCFR anchor p-1910.178(l)(1)(i))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Which deployed instance of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths will be compared with the source, and why that instance?</li>\n<li>How will the review distinguish a source mismatch from a failure in identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders?</li>\n<li>Who approves the conclusion, exception, test window, and rollback threshold?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>DSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, observed and expected states, owner, and reason for deviation.</p>\n<p>Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders, while excluding secrets and sensitive personal or topology data from ordinary tickets.</p>\n<h2>Verification and evidence</h2>\n<p>Build a reproducible chain from <strong>29 CFR 1910.178(l)(2)(iii) (eCFR anchor p-1910.178(l)(2)(iii))</strong>; <strong>29 CFR 1910.178(l)(1)(i) (eCFR anchor p-1910.178(l)(1)(i))</strong> to the observed environment. Useful domain evidence includes facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions; label every item with scope, timestamp, collector, and stable identifier.</p>\n<p>Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today&#8217;s observation is not a continuing guarantee.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://www.ecfr.gov/current/title-29/section-1910.178\" target=\"_blank\" rel=\"noopener noreferrer\">29 CFR 1910.178 &#8211; Powered industrial trucks</a> — Occupational Safety and Health Administration via eCFR</li>\n</ul>",
        "content_text": "Keep this document to one review outcome: Tie powered-industrial-truck authorization to training and equipment condition. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 29 CFR 1910.178 – Powered industrial trucks from Occupational Safety and Health Administration via eCFR supports the following bounded statements:\n\nUnder 29 CFR 1910, the rule requires that all operator training and evaluation be conducted by persons who have the knowledge, training, and experience to train powered industrial truck operators and evaluate their competence. The research record locates this support at 29 CFR 1910.178(l)(2)(iii) (eCFR anchor p-1910.178(l)(2)(iii)).\nUnder 29 CFR 1910, the rule requires that the employer ensure that each powered industrial truck operator is competent to operate a powered industrial truck safely, as demonstrated by the successful completion of the training and evaluation specified in this paragraph (l). The research record locates this support at 29 CFR 1910.178(l)(1)(i) (eCFR anchor p-1910.178(l)(1)(i)).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths and the conditions the source actually describes.\nWhat the source does not establish\nFederal workplace rule; truck type, environment, attachments, hazardous locations, traffic plan, and state-plan requirements affect the controls. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders and the environment’s recorded constraints.\nApplicability questions\n\nFor source statement 1 at 29 CFR 1910.178(l)(2)(iii) (eCFR anchor p-1910.178(l)(2)(iii)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 29 CFR 1910.178(l)(1)(i) (eCFR anchor p-1910.178(l)(1)(i)), which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders?\nWho approves the conclusion, exception, test window, and rollback threshold?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, observed and expected states, owner, and reason for deviation.\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders, while excluding secrets and sensitive personal or topology data from ordinary tickets.\nVerification and evidence\nBuild a reproducible chain from 29 CFR 1910.178(l)(2)(iii) (eCFR anchor p-1910.178(l)(2)(iii)); 29 CFR 1910.178(l)(1)(i) (eCFR anchor p-1910.178(l)(1)(i)) to the observed environment. Useful domain evidence includes facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions; label every item with scope, timestamp, collector, and stable identifier.\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\nOfficial references\n\n29 CFR 1910.178 – Powered industrial trucks — Occupational Safety and Health Administration via eCFR",
        "content_markdown": "Keep this document to one review outcome: Tie powered-industrial-truck authorization to training and equipment condition. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [29 CFR 1910.178 – Powered industrial trucks](https://www.ecfr.gov/current/title-29/section-1910.178) from Occupational Safety and Health Administration via eCFR supports the following bounded statements:\n\n- Under 29 CFR 1910, the rule requires that all operator training and evaluation be conducted by persons who have the knowledge, training, and experience to train powered industrial truck operators and evaluate their competence. The research record locates this support at 29 CFR 1910.178(l)(2)(iii) (eCFR anchor p-1910.178(l)(2)(iii)).\n\n- Under 29 CFR 1910, the rule requires that the employer ensure that each powered industrial truck operator is competent to operate a powered industrial truck safely, as demonstrated by the successful completion of the training and evaluation specified in this paragraph (l). The research record locates this support at 29 CFR 1910.178(l)(1)(i) (eCFR anchor p-1910.178(l)(1)(i)).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths and the conditions the source actually describes.\n\n## What the source does not establish\n\nFederal workplace rule; truck type, environment, attachments, hazardous locations, traffic plan, and state-plan requirements affect the controls. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders and the environment’s recorded constraints.\n\n## Applicability questions\n\n- For source statement 1 at 29 CFR 1910.178(l)(2)(iii) (eCFR anchor p-1910.178(l)(2)(iii)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 29 CFR 1910.178(l)(1)(i) (eCFR anchor p-1910.178(l)(1)(i)), which observable configuration, record, or test can confirm applicability here?\n\n- Which deployed instance of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths will be compared with the source, and why that instance?\n\n- How will the review distinguish a source mismatch from a failure in identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders?\n\n- Who approves the conclusion, exception, test window, and rollback threshold?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, observed and expected states, owner, and reason for deviation.\n\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders, while excluding secrets and sensitive personal or topology data from ordinary tickets.\n\n## Verification and evidence\n\nBuild a reproducible chain from 29 CFR 1910.178(l)(2)(iii) (eCFR anchor p-1910.178(l)(2)(iii)); 29 CFR 1910.178(l)(1)(i) (eCFR anchor p-1910.178(l)(1)(i)) to the observed environment. Useful domain evidence includes facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions; label every item with scope, timestamp, collector, and stable identifier.\n\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\n\n## Official references\n\n- [29 CFR 1910.178 – Powered industrial trucks](https://www.ecfr.gov/current/title-29/section-1910.178) — Occupational Safety and Health Administration via eCFR"
    },
    "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/tie-powered-industrial-truck-authorization-to-training-and-equipment-condition/",
                "url": "https://update.dsesecurity.com/updates/tie-powered-industrial-truck-authorization-to-training-and-equipment-condition/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/tie-powered-industrial-truck-authorization-to-training-and-equipment-condition/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Tie powered-industrial-truck authorization to training and equipment condition",
                        "item": "https://update.dsesecurity.com/updates/tie-powered-industrial-truck-authorization-to-training-and-equipment-condition/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/tie-powered-industrial-truck-authorization-to-training-and-equipment-condition/#article",
                "identifier": "https://update.dsesecurity.com/updates/tie-powered-industrial-truck-authorization-to-training-and-equipment-condition/",
                "url": "https://update.dsesecurity.com/updates/tie-powered-industrial-truck-authorization-to-training-and-equipment-condition/",
                "headline": "Tie powered-industrial-truck authorization to training and equipment condition",
                "description": "Use 29 CFR 1910.178 - Powered industrial trucks to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use 29 CFR 1910.178 - Powered industrial trucks to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Keep this document to one review outcome: Tie powered-industrial-truck authorization to training and equipment condition. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 29 CFR 1910.178 – Powered industrial trucks from Occupational Safety and Health Administration via eCFR supports the following bounded statements:\n\nUnder 29 CFR 1910, the rule requires that all operator training and evaluation be conducted by persons who have the knowledge, training, and experience to train powered industrial truck operators and evaluate their competence. The research record locates this support at 29 CFR 1910.178(l)(2)(iii) (eCFR anchor p-1910.178(l)(2)(iii)).\nUnder 29 CFR 1910, the rule requires that the employer ensure that each powered industrial truck operator is competent to operate a powered industrial truck safely, as demonstrated by the successful completion of the training and evaluation specified in this paragraph (l). The research record locates this support at 29 CFR 1910.178(l)(1)(i) (eCFR anchor p-1910.178(l)(1)(i)).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths and the conditions the source actually describes.\nWhat the source does not establish\nFederal workplace rule; truck type, environment, attachments, hazardous locations, traffic plan, and state-plan requirements affect the controls. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders and the environment’s recorded constraints.\nApplicability questions\n\nFor source statement 1 at 29 CFR 1910.178(l)(2)(iii) (eCFR anchor p-1910.178(l)(2)(iii)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 29 CFR 1910.178(l)(1)(i) (eCFR anchor p-1910.178(l)(1)(i)), which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders?\nWho approves the conclusion, exception, test window, and rollback threshold?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of critical rooms, power, cooling, water, fire protection, alternate sites, physical barriers, and documented recovery paths, observed and expected states, owner, and reason for deviation.\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include identity and access control, Windows DNS where networked services use it, time, communications, utilities, life-safety systems, vendors, and authorized responders, while excluding secrets and sensitive personal or topology data from ordinary tickets.\nVerification and evidence\nBuild a reproducible chain from 29 CFR 1910.178(l)(2)(iii) (eCFR anchor p-1910.178(l)(2)(iii)); 29 CFR 1910.178(l)(1)(i) (eCFR anchor p-1910.178(l)(1)(i)) to the observed environment. Useful domain evidence includes facility inventories, inspection records, alarm and shutdown tests, maintenance history, recovery exercises, and corrective actions; label every item with scope, timestamp, collector, and stable identifier.\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\nOfficial references\n\n29 CFR 1910.178 – Powered industrial trucks — Occupational Safety and Health Administration via eCFR",
                "datePublished": "2026-08-27T12:12:16+00:00",
                "dateModified": "2026-08-27T13:04:10+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/tie-powered-industrial-truck-authorization-to-training-and-equipment-condition/"
                },
                "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/tie-powered-industrial-truck-authorization-to-training-and-equipment-condition/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Tie powered-industrial-truck authorization to training and equipment condition"
                },
                "articleSection": [
                    "Access Control",
                    "Business Continuity",
                    "Cybersecurity"
                ],
                "keywords": [
                    "Access Control",
                    "Business Continuity",
                    "Cybersecurity",
                    "Playbook",
                    "Advisory priority"
                ],
                "genre": "Playbook",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Access Control",
                        "url": "https://update.dsesecurity.com/topic/access-control/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Business Continuity",
                        "url": "https://update.dsesecurity.com/topic/business-continuity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    }
                ],
                "wordCount": 593,
                "timeRequired": "PT3M",
                "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": "29 CFR 1910.178 - Powered industrial trucks",
                    "url": "https://www.ecfr.gov/current/title-29/section-1910.178"
                }
            }
        ]
    }
}