{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/practice-facility-power-restoration-restart-sequence/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/practice-facility-power-restoration-restart-sequence/",
        "slug": "practice-facility-power-restoration-restart-sequence",
        "url": "https://update.dsesecurity.com/updates/practice-facility-power-restoration-restart-sequence/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/practice-facility-power-restoration-restart-sequence.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/practice-facility-power-restoration-restart-sequence/"
        },
        "title": "Practice the restart sequence after facility power returns",
        "summary": "Utility power returning does not mean every dependent service is ready. Build and rehearse an authorized restart sequence that validates power quality, facility systems, network, identity, storage, applications, security, and monitoring.",
        "format": {
            "slug": "playbook",
            "name": "Playbook"
        },
        "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": "it",
                "name": "IT",
                "url": "https://update.dsesecurity.com/topic/it/"
            },
            {
                "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-17T12:47:00+00:00",
        "modified_at": "2026-08-17T19:22:10+00:00",
        "reviewed_on": "2026-08-17",
        "reading_minutes": 3,
        "word_count": 636,
        "potentially_affected": "Facility electrical and cooling systems; generators and UPS; network, storage, virtualization and identity; physical-security systems; business applications; monitoring; vendors; communications; and post-outage change control.",
        "dse_recommendation": "Map service dependencies and startup authority, define safe prerequisites and sequencing, create observable checkpoints and abort criteria, rehearse representative restoration, validate business workflows, and feed findings back into continuity plans.",
        "primary_source": {
            "name": "Ready Business Power Outage Toolkit",
            "url": "https://www.ready.gov/sites/default/files/2020-04/ready_business_power-outage-toolkit.pdf",
            "published_on": null,
            "authority": "Ready.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": "<h2>Source facts: restoration requires planning beyond power availability</h2>\n<p>The <a href=\"https://www.ready.gov/sites/default/files/2020-04/ready_business_power-outage-toolkit.pdf\" target=\"_blank\" rel=\"noopener noreferrer\">Ready Business Power Outage Toolkit</a> asks organizations to evaluate outage impacts, create a plan, protect systems and data, identify backup-power needs, communicate, train, and exercise. The toolkit treats power loss as a business interruption whose consequences and recovery tasks extend beyond the utility feed.</p>\n<p>FEMA <a href=\"https://www.fema.gov/sites/default/files/2020-07/fema_p-1019_final_02-06-2015.pdf\" target=\"_blank\" rel=\"noopener noreferrer\">P-1019</a> explains that emergency power performance depends on generation, fuel, transfer, distribution, controls, maintenance, testing, and connected loads. Returning from backup to normal supply is part of that system behavior, and downstream services may have their own safe operating prerequisites.</p>\n<p>The sources support planning and testing but do not provide a universal IT restart order. Actual sequence depends on electrical and life-safety conditions, cooling, network design, identity, storage consistency, application architecture, vendor requirements, and the cause of the outage. Restoring damaged or wet equipment can be dangerous.</p>\n\n<h2>DSE recommendation: promote services through observable recovery stages</h2>\n<p>Create one coordinated runbook with facility, safety, IT, security, operations, application, communications, and vendor owners. No technical convenience should override qualified confirmation that power and the environment are safe.</p>\n<ol>\n<li><strong>Map dependency layers.</strong> Connect each critical business service to power, UPS, cooling, carrier links, switching, routing, firewalls, DNS, time, identity, storage, virtualization, databases, middleware, integrations, physical-security systems, and required staff. Identify circular dependencies and manual credentials needed during an identity outage.</li>\n<li><strong>Assign command and authority.</strong> Name who confirms facility safety, authorizes energization, controls generator or transfer actions, starts each technology layer, communicates status, approves vendor access, and declares service restored. Provide alternates and an offline copy of contacts and procedures.</li>\n<li><strong>Define entry conditions.</strong> Require qualified checks for damage, water, smoke, temperature, grounding, voltage, frequency, phase, transfer state, fuel, UPS alarms, and cooling before equipment starts. Set abort criteria for unstable power, overheating, unusual noise or odor, repeated trips, and uncertain equipment condition.</li>\n<li><strong>Sequence by dependency and load.</strong> Restore facility services and approved infrastructure, then foundational network, name and time services, identity, storage and compute, databases, applications, integrations, monitoring, and user access as the architecture requires. Stage inrush and demand according to engineering limits.</li>\n<li><strong>Use checkpoints rather than assumptions.</strong> At each stage, validate redundancy, configuration, replication, data consistency, certificate and clock state, routing, authentication, queues, backups, alarms, logging, and downstream reachability. Record the observer, time, evidence, deviation, and decision to proceed.</li>\n<li><strong>Test end-to-end business workflows.</strong> A green server console is not proof of service. Validate representative customer communication, ticketing, access events, video, remote access, transactions, printing, alerting, escalation, backup, and reporting with business owners.</li>\n<li><strong>Stabilize after return.</strong> Monitor delayed failures, exhausted batteries, thermal change, storage rebuilds, expired sessions, missed jobs, duplicate processing, carrier instability, and security-control gaps. Replenish fuel, back up changed state, open corrective actions, and conduct a structured review.</li>\n</ol>\n<p>Keep recovery credentials and runbooks available through a protected offline or independently reachable path. Test that designated personnel can retrieve them when normal identity, password vault, file sharing, telephony, and internet services are unavailable. Use controlled check-out, tamper evidence, rotation after use, and dual authorization for powerful emergency credentials.</p>\n<p>Define a stop point for every layer. If power quality, temperature, storage consistency, identity replication, routing, security telemetry, or application data integrity is outside its accepted range, hold the next layer, preserve evidence, and invoke the named recovery owner. Continuing can transform a contained fault into wider corruption or unsafe load.</p>\n<p><strong>Factual boundary:</strong> The correct restart sequence is site-, architecture-, and vendor-specific. This article never authorizes energizing damaged, wet, overheated, contaminated, or otherwise unsafe equipment. Qualified electrical, facility, safety, engineering, manufacturer, utility, and authority-having-jurisdiction direction takes precedence.</p>\n<p>Measure time to qualified release, checkpoint success, undocumented dependencies, manual interventions, failed service tests, repeat incidents, and corrective-action closure. Declare recovery only when priority business services work safely and monitoring can detect their next failure.</p>\n\n<h2>Official references</h2>\n<ul>\n<li>Ready.gov, <a href=\"https://www.ready.gov/sites/default/files/2020-04/ready_business_power-outage-toolkit.pdf\" target=\"_blank\" rel=\"noopener noreferrer\"><em>Ready Business Power Outage Toolkit</em></a>.</li>\n<li>FEMA, <a href=\"https://www.fema.gov/sites/default/files/2020-07/fema_p-1019_final_02-06-2015.pdf\" target=\"_blank\" rel=\"noopener noreferrer\"><em>P-1019: Emergency Power Systems for Critical Facilities</em></a>.</li>\n</ul>",
        "content_text": "Source facts: restoration requires planning beyond power availability\nThe Ready Business Power Outage Toolkit asks organizations to evaluate outage impacts, create a plan, protect systems and data, identify backup-power needs, communicate, train, and exercise. The toolkit treats power loss as a business interruption whose consequences and recovery tasks extend beyond the utility feed.\nFEMA P-1019 explains that emergency power performance depends on generation, fuel, transfer, distribution, controls, maintenance, testing, and connected loads. Returning from backup to normal supply is part of that system behavior, and downstream services may have their own safe operating prerequisites.\nThe sources support planning and testing but do not provide a universal IT restart order. Actual sequence depends on electrical and life-safety conditions, cooling, network design, identity, storage consistency, application architecture, vendor requirements, and the cause of the outage. Restoring damaged or wet equipment can be dangerous.\n\nDSE recommendation: promote services through observable recovery stages\nCreate one coordinated runbook with facility, safety, IT, security, operations, application, communications, and vendor owners. No technical convenience should override qualified confirmation that power and the environment are safe.\n\nMap dependency layers. Connect each critical business service to power, UPS, cooling, carrier links, switching, routing, firewalls, DNS, time, identity, storage, virtualization, databases, middleware, integrations, physical-security systems, and required staff. Identify circular dependencies and manual credentials needed during an identity outage.\nAssign command and authority. Name who confirms facility safety, authorizes energization, controls generator or transfer actions, starts each technology layer, communicates status, approves vendor access, and declares service restored. Provide alternates and an offline copy of contacts and procedures.\nDefine entry conditions. Require qualified checks for damage, water, smoke, temperature, grounding, voltage, frequency, phase, transfer state, fuel, UPS alarms, and cooling before equipment starts. Set abort criteria for unstable power, overheating, unusual noise or odor, repeated trips, and uncertain equipment condition.\nSequence by dependency and load. Restore facility services and approved infrastructure, then foundational network, name and time services, identity, storage and compute, databases, applications, integrations, monitoring, and user access as the architecture requires. Stage inrush and demand according to engineering limits.\nUse checkpoints rather than assumptions. At each stage, validate redundancy, configuration, replication, data consistency, certificate and clock state, routing, authentication, queues, backups, alarms, logging, and downstream reachability. Record the observer, time, evidence, deviation, and decision to proceed.\nTest end-to-end business workflows. A green server console is not proof of service. Validate representative customer communication, ticketing, access events, video, remote access, transactions, printing, alerting, escalation, backup, and reporting with business owners.\nStabilize after return. Monitor delayed failures, exhausted batteries, thermal change, storage rebuilds, expired sessions, missed jobs, duplicate processing, carrier instability, and security-control gaps. Replenish fuel, back up changed state, open corrective actions, and conduct a structured review.\n\nKeep recovery credentials and runbooks available through a protected offline or independently reachable path. Test that designated personnel can retrieve them when normal identity, password vault, file sharing, telephony, and internet services are unavailable. Use controlled check-out, tamper evidence, rotation after use, and dual authorization for powerful emergency credentials.\nDefine a stop point for every layer. If power quality, temperature, storage consistency, identity replication, routing, security telemetry, or application data integrity is outside its accepted range, hold the next layer, preserve evidence, and invoke the named recovery owner. Continuing can transform a contained fault into wider corruption or unsafe load.\nFactual boundary: The correct restart sequence is site-, architecture-, and vendor-specific. This article never authorizes energizing damaged, wet, overheated, contaminated, or otherwise unsafe equipment. Qualified electrical, facility, safety, engineering, manufacturer, utility, and authority-having-jurisdiction direction takes precedence.\nMeasure time to qualified release, checkpoint success, undocumented dependencies, manual interventions, failed service tests, repeat incidents, and corrective-action closure. Declare recovery only when priority business services work safely and monitoring can detect their next failure.\n\nOfficial references\n\nReady.gov, Ready Business Power Outage Toolkit.\nFEMA, P-1019: Emergency Power Systems for Critical Facilities.",
        "content_markdown": "## Source facts: restoration requires planning beyond power availability\n\nThe [Ready Business Power Outage Toolkit](https://www.ready.gov/sites/default/files/2020-04/ready_business_power-outage-toolkit.pdf) asks organizations to evaluate outage impacts, create a plan, protect systems and data, identify backup-power needs, communicate, train, and exercise. The toolkit treats power loss as a business interruption whose consequences and recovery tasks extend beyond the utility feed.\n\nFEMA [P-1019](https://www.fema.gov/sites/default/files/2020-07/fema_p-1019_final_02-06-2015.pdf) explains that emergency power performance depends on generation, fuel, transfer, distribution, controls, maintenance, testing, and connected loads. Returning from backup to normal supply is part of that system behavior, and downstream services may have their own safe operating prerequisites.\n\nThe sources support planning and testing but do not provide a universal IT restart order. Actual sequence depends on electrical and life-safety conditions, cooling, network design, identity, storage consistency, application architecture, vendor requirements, and the cause of the outage. Restoring damaged or wet equipment can be dangerous.\n\n## DSE recommendation: promote services through observable recovery stages\n\nCreate one coordinated runbook with facility, safety, IT, security, operations, application, communications, and vendor owners. No technical convenience should override qualified confirmation that power and the environment are safe.\n\n- Map dependency layers. Connect each critical business service to power, UPS, cooling, carrier links, switching, routing, firewalls, DNS, time, identity, storage, virtualization, databases, middleware, integrations, physical-security systems, and required staff. Identify circular dependencies and manual credentials needed during an identity outage.\n\n- Assign command and authority. Name who confirms facility safety, authorizes energization, controls generator or transfer actions, starts each technology layer, communicates status, approves vendor access, and declares service restored. Provide alternates and an offline copy of contacts and procedures.\n\n- Define entry conditions. Require qualified checks for damage, water, smoke, temperature, grounding, voltage, frequency, phase, transfer state, fuel, UPS alarms, and cooling before equipment starts. Set abort criteria for unstable power, overheating, unusual noise or odor, repeated trips, and uncertain equipment condition.\n\n- Sequence by dependency and load. Restore facility services and approved infrastructure, then foundational network, name and time services, identity, storage and compute, databases, applications, integrations, monitoring, and user access as the architecture requires. Stage inrush and demand according to engineering limits.\n\n- Use checkpoints rather than assumptions. At each stage, validate redundancy, configuration, replication, data consistency, certificate and clock state, routing, authentication, queues, backups, alarms, logging, and downstream reachability. Record the observer, time, evidence, deviation, and decision to proceed.\n\n- Test end-to-end business workflows. A green server console is not proof of service. Validate representative customer communication, ticketing, access events, video, remote access, transactions, printing, alerting, escalation, backup, and reporting with business owners.\n\n- Stabilize after return. Monitor delayed failures, exhausted batteries, thermal change, storage rebuilds, expired sessions, missed jobs, duplicate processing, carrier instability, and security-control gaps. Replenish fuel, back up changed state, open corrective actions, and conduct a structured review.\n\nKeep recovery credentials and runbooks available through a protected offline or independently reachable path. Test that designated personnel can retrieve them when normal identity, password vault, file sharing, telephony, and internet services are unavailable. Use controlled check-out, tamper evidence, rotation after use, and dual authorization for powerful emergency credentials.\n\nDefine a stop point for every layer. If power quality, temperature, storage consistency, identity replication, routing, security telemetry, or application data integrity is outside its accepted range, hold the next layer, preserve evidence, and invoke the named recovery owner. Continuing can transform a contained fault into wider corruption or unsafe load.\n\nFactual boundary: The correct restart sequence is site-, architecture-, and vendor-specific. This article never authorizes energizing damaged, wet, overheated, contaminated, or otherwise unsafe equipment. Qualified electrical, facility, safety, engineering, manufacturer, utility, and authority-having-jurisdiction direction takes precedence.\n\nMeasure time to qualified release, checkpoint success, undocumented dependencies, manual interventions, failed service tests, repeat incidents, and corrective-action closure. Declare recovery only when priority business services work safely and monitoring can detect their next failure.\n\n## Official references\n\n- Ready.gov, [Ready Business Power Outage Toolkit](https://www.ready.gov/sites/default/files/2020-04/ready_business_power-outage-toolkit.pdf).\n\n- FEMA, [P-1019: Emergency Power Systems for Critical Facilities](https://www.fema.gov/sites/default/files/2020-07/fema_p-1019_final_02-06-2015.pdf)."
    },
    "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/practice-facility-power-restoration-restart-sequence/",
                "url": "https://update.dsesecurity.com/updates/practice-facility-power-restoration-restart-sequence/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-17"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/practice-facility-power-restoration-restart-sequence/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Practice the restart sequence after facility power returns",
                        "item": "https://update.dsesecurity.com/updates/practice-facility-power-restoration-restart-sequence/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/practice-facility-power-restoration-restart-sequence/#article",
                "identifier": "https://update.dsesecurity.com/updates/practice-facility-power-restoration-restart-sequence/",
                "url": "https://update.dsesecurity.com/updates/practice-facility-power-restoration-restart-sequence/",
                "headline": "Practice the restart sequence after facility power returns",
                "description": "Utility power returning does not mean every dependent service is ready. Build and rehearse an authorized restart sequence that validates power quality…",
                "abstract": "Utility power returning does not mean every dependent service is ready. Build and rehearse an authorized restart sequence that validates power quality, facility systems, network, identity, storage, applications, security, and monitoring.",
                "articleBody": "Source facts: restoration requires planning beyond power availability\nThe Ready Business Power Outage Toolkit asks organizations to evaluate outage impacts, create a plan, protect systems and data, identify backup-power needs, communicate, train, and exercise. The toolkit treats power loss as a business interruption whose consequences and recovery tasks extend beyond the utility feed.\nFEMA P-1019 explains that emergency power performance depends on generation, fuel, transfer, distribution, controls, maintenance, testing, and connected loads. Returning from backup to normal supply is part of that system behavior, and downstream services may have their own safe operating prerequisites.\nThe sources support planning and testing but do not provide a universal IT restart order. Actual sequence depends on electrical and life-safety conditions, cooling, network design, identity, storage consistency, application architecture, vendor requirements, and the cause of the outage. Restoring damaged or wet equipment can be dangerous.\n\nDSE recommendation: promote services through observable recovery stages\nCreate one coordinated runbook with facility, safety, IT, security, operations, application, communications, and vendor owners. No technical convenience should override qualified confirmation that power and the environment are safe.\n\nMap dependency layers. Connect each critical business service to power, UPS, cooling, carrier links, switching, routing, firewalls, DNS, time, identity, storage, virtualization, databases, middleware, integrations, physical-security systems, and required staff. Identify circular dependencies and manual credentials needed during an identity outage.\nAssign command and authority. Name who confirms facility safety, authorizes energization, controls generator or transfer actions, starts each technology layer, communicates status, approves vendor access, and declares service restored. Provide alternates and an offline copy of contacts and procedures.\nDefine entry conditions. Require qualified checks for damage, water, smoke, temperature, grounding, voltage, frequency, phase, transfer state, fuel, UPS alarms, and cooling before equipment starts. Set abort criteria for unstable power, overheating, unusual noise or odor, repeated trips, and uncertain equipment condition.\nSequence by dependency and load. Restore facility services and approved infrastructure, then foundational network, name and time services, identity, storage and compute, databases, applications, integrations, monitoring, and user access as the architecture requires. Stage inrush and demand according to engineering limits.\nUse checkpoints rather than assumptions. At each stage, validate redundancy, configuration, replication, data consistency, certificate and clock state, routing, authentication, queues, backups, alarms, logging, and downstream reachability. Record the observer, time, evidence, deviation, and decision to proceed.\nTest end-to-end business workflows. A green server console is not proof of service. Validate representative customer communication, ticketing, access events, video, remote access, transactions, printing, alerting, escalation, backup, and reporting with business owners.\nStabilize after return. Monitor delayed failures, exhausted batteries, thermal change, storage rebuilds, expired sessions, missed jobs, duplicate processing, carrier instability, and security-control gaps. Replenish fuel, back up changed state, open corrective actions, and conduct a structured review.\n\nKeep recovery credentials and runbooks available through a protected offline or independently reachable path. Test that designated personnel can retrieve them when normal identity, password vault, file sharing, telephony, and internet services are unavailable. Use controlled check-out, tamper evidence, rotation after use, and dual authorization for powerful emergency credentials.\nDefine a stop point for every layer. If power quality, temperature, storage consistency, identity replication, routing, security telemetry, or application data integrity is outside its accepted range, hold the next layer, preserve evidence, and invoke the named recovery owner. Continuing can transform a contained fault into wider corruption or unsafe load.\nFactual boundary: The correct restart sequence is site-, architecture-, and vendor-specific. This article never authorizes energizing damaged, wet, overheated, contaminated, or otherwise unsafe equipment. Qualified electrical, facility, safety, engineering, manufacturer, utility, and authority-having-jurisdiction direction takes precedence.\nMeasure time to qualified release, checkpoint success, undocumented dependencies, manual interventions, failed service tests, repeat incidents, and corrective-action closure. Declare recovery only when priority business services work safely and monitoring can detect their next failure.\n\nOfficial references\n\nReady.gov, Ready Business Power Outage Toolkit.\nFEMA, P-1019: Emergency Power Systems for Critical Facilities.",
                "datePublished": "2026-08-17T12:47:00+00:00",
                "dateModified": "2026-08-17T19:22:10+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/practice-facility-power-restoration-restart-sequence/"
                },
                "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/practice-facility-power-restoration-restart-sequence/#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": "Practice the restart sequence after facility power returns"
                },
                "articleSection": [
                    "Business Continuity",
                    "IT",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Business Continuity",
                    "IT",
                    "Networks & Infrastructure",
                    "Playbook",
                    "Advisory priority"
                ],
                "genre": "Playbook",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Business Continuity",
                        "url": "https://update.dsesecurity.com/topic/business-continuity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 636,
                "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": "Ready Business Power Outage Toolkit",
                    "url": "https://www.ready.gov/sites/default/files/2020-04/ready_business_power-outage-toolkit.pdf"
                }
            }
        ]
    }
}