Diagnose a Data Center Power Failure

Diagnose a fictional data center power event with an evidence-based report.

Introduction

30 Second Summary

When critical equipment loses its normal power source, the device carrying the load may be the first thing to raise an alarm. A fast assumption can send attention to the wrong part of the system.

In this project, you will build a desktop diagnostic portfolio pack that turns a fictional data center power event into an evidence-based diagnosis. The pack combines a critical power path with alarm correlation in Google Docs and Google Sheets.

What You'll Build

You will point through a color-coded system map while a correlated timeline reveals the UPS supporting the critical IT load during a failed backup sequence.

By the end of this project, you'll have:

A power-path map you can trace from either source to the supported rack equipment.
An alarm workbook that reveals the failed backup sequence without turning an unresolved generator issue into a claimed root cause.
A portfolio-ready report that turns your diagnosis into a linked response chart plus a 60-second interview narrative.
Secret Mission: A branch-level PDU diagnosis that proves an energized PDU input does not guarantee support for every downstream rack.

Are there any prerequisites?

You need basic electrical fundamentals plus access to a Mac and Google Account. No recent data center experience is required because the project uses a focused refresher inside a fictional desktop exercise.

Before We Start

This first commitment keeps your work focused on evidence of refreshed power-path reasoning for a DCEO application. You are treating the project as a fictional desktop exercise with no live switching, maintenance, or equipment-control instructions or actions.

Set Up Your Diagnostic Workspace

Your safe desktop exercise now has a clear boundary. During an incident, evidence can become mixed with assumptions.

A consistent report in Google Docs will keep your analysis structured. A matching event log in Google Sheets will keep observations separate from decisions.

In this step, get ready to:

Create a private diagnostic report with its safety boundary and sections.
Create a private alarm workbook with two analysis tabs.
Confirm that both files have the required names and structure.

Create the report structure

Your report becomes the controlled record for the exercise. Google Drive stores it in your account while Google Docs saves your changes as you work.

Open Google Drive in your browser.
Complete the Google Account sign-in screen if it appears.

You should see your Google Drive files in the browser.

Click New in the left sidebar.
Point to Google Docs in the menu.

You should see the option to create a blank document.

Click Blank document.

A new Google Docs report opens in another browser tab.

Click Untitled document at the top of the page.
Enter Data Center Power-Path Failure Analysis.
Press Enter.

You should see Data Center Power-Path Failure Analysis as the report title.

Click at the top of the blank page.
Enter Fictional desktop exercise. No live switching, maintenance, or equipment-control instructions..

The safety note now makes the exercise boundary visible before any technical analysis.

Enter System Map, Decision Record, Limitations, and Interview Brief on separate lines below the note.
Select all four heading lines.
Apply a heading style with the text-style menu in the toolbar.

You should see the safety note followed by four clearly separated report sections.

Report not opening?

Confirm that your browser shows the Google Account you intend to use for this project.
Return to Google Drive if the document opened under a different account.
Reload Google Drive if the creation menu does not respond.

Help me create the Google Docs report for my diagnostic workspace.

Create the alarm workbook

The workbook gives time-based observations their own home. Its two tabs separate incident evidence from the response milestones you will record later.

Return to the Google Drive browser tab from earlier.
Click New in the left sidebar.

You should see the file-creation menu again.

Point to Google Sheets in the menu.

You should see the option to create a blank spreadsheet.

Click Blank spreadsheet.

A new Google Sheets workbook opens in another browser tab.

Click the workbook name at the top of the page.
Enter Power-Path Alarm Investigation.
Press Enter.

You should see Power-Path Alarm Investigation as the workbook title.

Double-click the text on the first sheet tab.
Enter Alarm Timeline.
Press Enter.

The first tab should now show Alarm Timeline.

Click Add sheet at the bottom of the workbook.

You should see a second sheet tab beside Alarm Timeline.

Double-click the text on the new sheet tab.
Enter Exercise Metrics.
Press Enter.

The workbook now has visible tabs named Alarm Timeline and Exercise Metrics.

Missing a workbook tab?

Click Add sheet again if only one tab appears.
Check both tab names for missing words or extra spaces.
Double-click a tab name again if it did not save.

Help me fix the tabs in my Google Sheets workbook.

Verify the private workspace

Files in Google Drive remain private unless you choose to share them. Confirming the access setting protects your unfinished analysis from accidental exposure.

Switch back to the Data Center Power-Path Failure Analysis report.
Click Share in the top right corner.
Confirm that General access shows Restricted.

This confirms that the report is private unless access is granted to specific people.

Select Restricted if another general-access setting is shown.
Click Done.
Switch back to the Power-Path Alarm Investigation workbook.
Click Share in the top right corner.
Confirm that General access shows Restricted.

This confirms that the workbook is private unless access is granted to specific people.

Select Restricted if another general-access setting is shown.
Click Done.

Unexpected access listed?

Use Remove access beside anyone you added accidentally.
Set General access to Restricted again.
Click Save if Google Drive asks you to confirm the change.

Help me make both project files private in Google Drive.

Before you make the final check, which file title and tab names do you expect to see?

Drag the workbook browser tab away from the tab bar to create a separate window.
Place the report window beside the workbook window.

You should now see both project files open on your Mac.

Scroll to the top of the report window.
Confirm that Data Center Power-Path Failure Analysis shows the safety note plus all four headings.
Confirm that Power-Path Alarm Investigation shows both required tab names.

The report should show System Map, Decision Record, Limitations, and Interview Brief. The workbook should show Alarm Timeline and Exercise Metrics.

✔️ Both files are ready

Both private files now match the diagnostic workspace for this project.

ⓧ I'd like to double check

Compare your workspace with this checklist:

The private report is named Data Center Power-Path Failure Analysis.
The report begins with Fictional desktop exercise. No live switching, maintenance, or equipment-control instructions..
The report contains headings named System Map, Decision Record, Limitations, and Interview Brief.
The private workbook is named Power-Path Alarm Investigation.
The workbook contains tabs named Alarm Timeline and Exercise Metrics.

Your investigation foundation is in place. Next up, you will map the normal and standby paths that feed the critical load.

Map the Normal and Backup Power Paths

Your diagnostic workspace is ready. The Google Docs report now gives your system map a dedicated home.

An alarm has little meaning until you can trace which source, transfer point, continuity device, and distribution stage support the load. You will use a drawing to make those dependencies visible before any incident evidence appears.

In this step, get ready to:

Draw the normal and standby power routes in one conceptual system map.
Label the function of every stage supporting the critical load.
Record the healthy utility and standby operating paths.

Draw the conceptual system

The normal route passes through a transformer before both sources converge through automatic transfer. A UPS protects continuity before a PDU distributes protected power to the supported load.

Return to the Data Center Power-Path Failure Analysis report from earlier.
Click the blank line directly below the System Map heading.
Click Insert in the top menu.
Select Drawing.
Select New.

You will see a blank drawing canvas with tools for shapes and lines.

Click Shape in the drawing toolbar.
Select a rectangular shape.
Create one box for each of these labels: Utility Grid, Transformer, Input Switchgear with Automatic Transfer, UPS, PDU, Critical IT Load, and Standby Generator.
Arrange the six normal-route boxes from left to right in the order listed above.
Place the Standby Generator box below the Input Switchgear with Automatic Transfer box.

Where do the paths meet?

The input switchgear receives one route from the utility path and another from the standby source. Both routes converge there before protected power continues toward the critical load.

This convergence point makes the source relationship visible without turning the map into an equipment-control procedure.

Click Select line in the drawing toolbar.
Select Arrow.
Connect the six normal-route boxes in their left-to-right order.
Draw one arrow from Standby Generator into Input Switchgear with Automatic Transfer.
Use the blue save control in the top-right corner to place the finished drawing in the report.

Good work. Your report now shows two sources converging before the continuity and distribution stages.

Diagram missing from the report?

Confirm that you created the drawing below the System Map heading.
Reopen the Drawing editor if the diagram did not appear.
Use the blue save control after confirming that every box and arrow is present.

Help me fix my missing or incomplete Google Docs drawing.

Label each component function

A useful system map explains the purpose of each stage. These labels give you the vocabulary to describe what an alarm means at different points in the path.

What does each stage do?

Utility Grid: normal source.
Transformer: conversion stage between the incoming supply and downstream distribution.
Input Switchgear with Automatic Transfer: source selection and protected distribution point.
Standby Generator: emergency source.
UPS: power-quality and continuity stage during a source disturbance or transition.
PDU: distributes protected power to downstream equipment.
Critical IT Load: the supported rack-level equipment.

Click the blank line beneath the inserted diagram.
Type the seven component-function lines from the callout into the System Map section.

You should now see a function key beneath the diagram that explains the role of every labeled box.

Record the healthy-state narrative

A healthy-state narrative records how the path is intended to work before you assess an alarm. It gives you a baseline for separating a source disturbance from a downstream loss.

Healthy-state text to record

During healthy normal operation, power follows this route: Utility Grid to Transformer to Input Switchgear with Automatic Transfer to UPS to PDU to Critical IT Load.
After the Standby Generator becomes available, power follows this route: Standby Generator to Input Switchgear with Automatic Transfer to UPS to PDU to Critical IT Load.
Conceptual learning model, not a construction or switching diagram.

Click the blank line beneath the component-function key.
Enter the three lines from the healthy-state callout exactly as shown.

Before you trace the finished map, where do you expect the normal and standby routes to converge?

Point from Utility Grid through each normal-route arrow while explaining the purpose of every stage.
Point from Standby Generator through each standby-route arrow while explaining the purpose of every stage.

You should find that both routes converge at Input Switchgear with Automatic Transfer before continuing through the UPS, PDU, and Critical IT Load.

✔️ My map passes the trace check

Your completed map shows how either source can support the shared downstream path.

ⓧ I'd like to double check the map

Confirm that the normal route runs from Utility Grid to Transformer to Input Switchgear with Automatic Transfer to UPS to PDU to Critical IT Load.
Confirm that the alternate route runs from Standby Generator to Input Switchgear with Automatic Transfer.
Confirm that the function key identifies the role of all seven components.
Confirm that one narrative traces normal utility operation.
Confirm that one narrative traces the standby path after the alternate source becomes available.
Confirm that the map includes Conceptual learning model, not a construction or switching diagram.

Your map now gives each future alarm a location in the power path. Next, you will test it against an ambiguous UPS observation without jumping to a root cause.

Triage the First Alarm

Your Google Sheets workbook is ready to capture the first fictional incident. The challenge now is deciding what the available evidence actually proves.

An on-battery observation from the UPS can tempt a fast diagnosis. You will test how much that single alarm proves about the wider power path before recording a conclusion.

In this step, get ready to:

Record the first-alarm snapshot in the Alarm Timeline tab.
Build an evidence gap from the unanswered questions.
Write an assessment that separates facts from hypotheses.

Enter the first alarm snapshot

The timeline keeps each type of incident information in its own column. The Evidence Class column distinguishes confirmed observations from missing information.

Switch back to the Power-Path Alarm Investigation workbook from earlier.
Select the Alarm Timeline tab at the bottom of the workbook.
Fill cells A1:E1 with Time, Observation, Status, Evidence Class, and Meaning.

You should see five headers spanning the top of the timeline.

Why Classify the Evidence?

A status describes the reported equipment state. An evidence class records whether that state was observed or remains missing.

This separation stops an unanswered question from quietly becoming a conclusion.

Fill cells A2:E2 with 10:00, UPS status, On battery, Observed, and UPS output is presently supporting the downstream path.
Fill cells A3:E3 with 10:00, PDU output, Energized, Observed, and Protected distribution is presently available.

Rows 2 and 3 should now show the continuity state and protected-distribution state.

Fill cells A4:E4 with 10:00, Critical IT load, Supported, Observed, and No load loss is currently observed.
Fill cells A5:E5 with 10:00, Utility source, Unknown, Missing, and The initiating source condition is not yet known.

Rows 4 and 5 should contrast a supported load with an unknown utility state.

Fill cells A6:E6 with 10:00, Generator source, Unknown, Missing, and The sustainable alternate source is not yet known.
Fill cells A7:E7 with 10:00, Automatic transfer status, Unknown, Missing, and No transfer conclusion can be made.

Rows 6 and 7 should show that the alternate source and transfer state remain unknown.

✔️ My snapshot matches

Good work. Your timeline now separates three observed downstream states from three missing upstream states.

ⓧ I need to compare the rows

Compare your six snapshot rows with these values:

Row 2 contains 10:00, UPS status, On battery, Observed, and UPS output is presently supporting the downstream path.
Row 3 contains 10:00, PDU output, Energized, Observed, and Protected distribution is presently available.
Row 4 contains 10:00, Critical IT load, Supported, Observed, and No load loss is currently observed.
Row 5 contains 10:00, Utility source, Unknown, Missing, and The initiating source condition is not yet known.
Row 6 contains 10:00, Generator source, Unknown, Missing, and The sustainable alternate source is not yet known.
Row 7 contains 10:00, Automatic transfer status, Unknown, Missing, and No transfer conclusion can be made.

Before you assess the snapshot, do you think these six rows are enough to identify a failed component?

Review rows 2 through 7 as one incident snapshot.

You can confirm present downstream support. You cannot identify the initiating cause or sustainable backup state from this snapshot.

Why the First Snapshot Falls Short

The on-battery state proves that the UPS is presently supporting its downstream path. It does not identify the disturbance that led to that state.

The unknown utility, generator, and transfer states leave several plausible explanations open. A component-failure claim would exceed the evidence.

Values in the Wrong Columns?

Check that every row starts in column A.
Place each row value in its matching column from A through E.

Ask for help if the row layout still looks wrong: Help me organize my first-alarm snapshot into the correct Google Sheets columns.

Build the evidence gap

Alarm correlation connects observations across the power path. Here it begins by turning every unknown condition into a specific request for evidence.

Fill cells A8:E8 with 10:00, Utility availability, Required evidence, Missing, and Is the utility source available?.
Fill cells A9:E9 with 10:00, UPS input status, Required evidence, Missing, and Is input power available to the UPS?.

Rows 8 and 9 should now request evidence about the normal source reaching the UPS.

Fill cells A10:E10 with 10:00, Generator availability, Required evidence, Missing, and Is the generator source available?.
Fill cells A11:E11 with 10:00, Automatic-transfer status, Required evidence, Missing, and Has transfer to the alternate source completed?.

Rows 10 and 11 should now request evidence about alternate-source availability and transfer status.

Fill cells A12:E12 with 10:00, Battery trend, Required evidence, Missing, and What trend does the UPS battery show?.
Fill cells A13:E13 with 10:00, Downstream load status, Required evidence, Missing, and Does the critical load remain supported?.

Rows 12 and 13 should now request evidence about continuity duration and present load impact.

Questions Are Not Conclusions

The Required evidence status identifies information that must be gathered. The Missing classification keeps those questions separate from observed facts.

Your evidence gap now guides the next investigation without pretending the answers are already known.

Scan cells C8:C13 to confirm that all six rows say Required evidence.

You should see six required-evidence rows covering the sources, transfer point, UPS input, battery trend, and downstream load.

Write the first assessment

Evidence versus inference is the discipline of separating what the snapshot confirms from explanations that remain possible. Your assessment needs a confirmed state, plausible hypotheses, and explicit unknowns.

Enter First Assessment in cell A15.
Fill cells A16:B16 with Confirmed state and UPS output is presently supporting the downstream path. PDU output is presently energized. Critical IT load is presently supported..

The confirmed-state row should contain only conditions supported by the snapshot.

Fill cells A17:B17 with Hypotheses and Upstream supply disturbance. Unresolved equipment alert..
Fill cells A18:B18 with Unknowns and Root cause and duration of protection cannot yet be determined..

The final two rows should preserve both hypotheses while keeping root cause and protection duration unresolved.

How the Assessment Stays Defensible

The confirmed state describes the present load-support condition. It does not assign a failed component.

The hypotheses give the investigation more than one direction. The unknowns show decision-makers where further evidence is still required.

✔️ My assessment stays within the evidence

Your assessment confirms present support without claiming an unverified root cause.

ⓧ I need to compare the assessment

Compare your assessment with these three fields:

The Confirmed state field says that the UPS output supports the downstream path. It also says that the PDU output is energized. It confirms that the critical IT load is supported.
The Hypotheses field lists an upstream supply disturbance and an unresolved equipment alert.
The Unknowns field says that root cause and duration of protection cannot yet be determined.

Before you read the assessment aloud, do you expect it to prove that the UPS has failed?

Read the three assessment fields aloud from top to bottom.

You should hear that the critical load remains supported. You should also hear that the initiating cause and sustainable backup state remain unresolved.

That is disciplined first-alarm triage. Your workbook now communicates current impact without turning a plausible explanation into a fact.

Assessment Sounding Too Certain?

Move any unverified cause from Confirmed state to Hypotheses.
Keep the root cause and protection duration in Unknowns.

Ask for help if the wording still overclaims the evidence: Help me separate confirmed observations, hypotheses, and unknowns in my first-alarm assessment.

Your first assessment preserves the uncertainty that matters. Next, you will add upstream evidence and test which hypothesis survives the full event sequence.

Correlate the Failure Chain

Your first assessment in Google Sheets kept one UPS alarm from becoming an unsupported component diagnosis. The initiating source remained unresolved.

Alarm correlation aligns observations by time so the power path can be read as a sequence. The added source evidence now shows why the UPS is supporting the load.

In this step, get ready to:

Add the observations from 10:00 to 10:05 to build a correlated event timeline.
Color the system map to show each stage's fictional state.
Write a three-field diagnosis that separates the sequence from the unresolved root cause.

Add the correlated timeline

A timeline turns separate alerts into one ordered story. Each added row answers one of the evidence questions you recorded earlier.

In the Alarm Timeline tab from earlier, select the first empty row beneath your existing content.
Fill the next row from left to right with 10:00 | Utility source | Unavailable | Observed | Normal source is unavailable.
Fill the next row from left to right with 10:01 | Generator start signal | Issued | Observed | Backup sequence was requested.
Fill the next row from left to right with 10:02 | Generator source | Not available | Observed | Alternate source is not ready.
Fill the next row from left to right with 10:03 | Transfer to alternate source | Not completed | Observed | The load has not moved to the alternate source.
Fill the next row from left to right with 10:04 | UPS output | Energized | Observed | The UPS continues to support the downstream path.
Fill the next row from left to right with 10:04 | UPS battery trend | Discharging | Observed | Stored energy is being consumed.
Fill the next row from left to right with 10:05 | Critical IT load | Supported | Observed | No load loss is yet observed.

You should now see seven new observed rows ordered from 10:00 through 10:05. The rows expose a failed source-transition sequence while the load remains supported.

What does the timeline prove?

The 10:00 row confirms that the normal source is unavailable.
The rows from 10:01 through 10:03 confirm that the backup sequence was requested without a completed transfer.
The rows from 10:04 through 10:05 confirm that stored energy is supporting the load.

Timeline values in the wrong columns?

Check that each observation occupies five cells under Time through Meaning.
Confirm that each new row uses Observed in the Evidence Class column.

Help me correct my correlated event rows.

Mark the fictional system state

Color adds affected-scope context to the conceptual map. It shows which stages are unavailable, bridging the disturbance, or presently supported.

In the Data Center Power-Path Failure Analysis report from earlier, double-click the system map in Google Docs to edit it.
Apply red to the Utility Grid box with the drawing toolbar's color control.
Apply red to the Standby Generator box with the drawing toolbar's color control.
Apply amber to the UPS box with the drawing toolbar's color control.
Apply green to the PDU box with the drawing toolbar's color control.
Apply green to the Critical IT Load box with the drawing toolbar's color control.
Add a text box beneath the map containing Colors describe the fictional snapshot, not equipment-control states.
Save the drawing changes.

You should see red on the unavailable Utility Grid and Standby Generator. You should see amber on the UPS continuity stage.

You should see green on the energized PDU and supported Critical IT Load. The original Conceptual learning model, not a construction or switching diagram label should still be visible.

Colors not matching the timeline?

Keep the fictional-state colors on the existing system map.
Confirm that every box retains its original component label.
Check that the Transformer and Input Switchgear boxes retain their existing appearance.

Help me check my fictional system-state colors.

Write the three-part diagnosis

A defensible diagnosis keeps the observed sequence separate from its operational meaning. It also names the question that the available evidence cannot answer.

In the Alarm Timeline tab from earlier, select the first empty row beneath the correlated event timeline.
Record this diagnosis field in the next empty row: Confirmed sequence: utility became unavailable, the generator start signal was issued, the generator source did not become available, transfer did not complete, and the UPS supported the load from stored energy.
Record this diagnosis field in the next empty row: Operational conclusion: the load is supported but has lost sustainable source redundancy and requires escalation.
Record this diagnosis field in the next empty row: Unresolved root cause: available evidence does not explain why the generator source failed to become available.

Before you read the diagnosis aloud, predict which field carries the escalation decision.

Read each of the three diagnosis fields aloud.
Compare each field with the event rows above it.
Confirm that each field answers one separate question about sequence, operational state, or root cause.

What should you hear?

Each field should make one distinct claim supported by the timeline.

The Confirmed sequence field names the observed progression from utility loss to UPS support.
The Operational conclusion field names the degraded resilience state plus the need to escalate.
The Unresolved root cause field preserves the unknown generator cause.

Strong work. Your diagnosis now explains the failure chain without overclaiming a generator root cause.

The failure chain is now defensible. Next, you will turn it into a decision record that communicates impact, risk, escalation, follow-up, and analytical limits.

Build the Decision Report

Your correlated timeline now shows how the source event developed from utility loss to UPS battery discharge. The next goal is to turn that analysis into a decision record that an authorized facility lead can act on.

Technical reasoning becomes useful when decision-makers can see the evidence plus the affected scope. Your Google Docs report will connect the critical power path to the current risk.

A linked chart will show your response milestones. A short interview brief will make your reasoning easy to explain.

In this step, get ready to:

Write an evidence-based decision record with impact, risk, escalation, follow-up, and safety boundaries.
Create response milestones in Google Sheets and link the resulting chart into your report.
Write a 60-second interview brief with explicit analytical limitations.

Write the decision record

A decision record separates the supported load from the degraded resilience state. It also assigns the next action without claiming an unverified generator root cause.

Switch back to the Data Center Power-Path Failure Analysis report.
Click beneath the Decision Record heading.

You should see the insertion point beneath the existing heading.

Type Current impact: Critical load remains supported in the fictional snapshot.
Type Resilience risk: No sustainable alternate source is confirmed while stored energy is being consumed.

Read both lines. They should keep the present load condition separate from the loss of sustainable source redundancy.

Type Decision: Escalate to the authorized facility lead and generator specialist, freeze unrelated changes, and continue monitoring under approved site procedures.
Type Required follow-up: Determine why the generator source was unavailable, validate restoration evidence, and record corrective and preventive actions.

Your report should now identify the authorized escalation path. It should also preserve the unresolved generator question for follow-up.

Type Safety boundary: No live switching or maintenance action is proposed by this desktop exercise.
Type Confirmed sequence: Utility became unavailable. The generator start signal was issued. The generator source did not become available. Transfer did not complete. The UPS supported the load from stored energy.

The safety boundary keeps the report within the fictional desktop exercise. The confirmed sequence records only what the timeline supports.

Type Operational conclusion: The load is supported. Sustainable source redundancy is lost. Escalation is required.
Type Unresolved root cause: Available evidence does not explain why the generator source failed to become available.

Read the completed diagnosis. You should see the confirmed sequence, operational conclusion, and unresolved root cause presented as three separate ideas.

Why this decision record works

The report states that the load remains supported while stored energy is being consumed. That combination makes the degraded resilience state visible without overstating the immediate impact.

The escalation decision assigns the next owners. The unresolved-root-cause field prevents a plausible generator explanation from becoming an unsupported conclusion.

Create and link the response chart

Response milestones show how quickly the fictional investigation moved from acknowledgement to escalation. These values measure the exercise workflow.

Use These Exercise Metrics

Use Milestone plus Elapsed minutes as the two column headers.

Acknowledgement: 1 minute.
Evidence gathered: 4 minutes.
Failure chain identified: 7 minutes.
Escalation decision: 8 minutes.

Switch back to the Exercise Metrics tab in the Power-Path Alarm Investigation workbook.
Enter the two-column milestone table using the headers plus the four row pairs shown above.

You should see four milestones with elapsed values increasing from 1 to 8 minutes.

Select the cells containing the completed milestone table.

The two headers plus all four milestone rows should appear highlighted.

Click Insert in the top menu.
Click Chart.

You should see a chart created from the selected milestones and elapsed values.

Choose a column chart in the chart editor.
Set the chart title to Exercise Response Milestones.

You should see one column for each milestone. The chart title should read Exercise Response Milestones.

Chart Missing a Milestone?

Confirm that the selected range includes both headers plus all four data rows.
Confirm that the elapsed values occupy one column as plain numbers.
Select the corrected table again before creating a replacement chart.

Help me fix my exercise milestones chart.

Switch back to the Data Center Power-Path Failure Analysis report.
Click below the evidence-based diagnosis in the Decision Record section.

You should see the insertion point where the response chart will sit.

Click Insert in the top menu.
Select Chart.

You should see the available chart source options.

Select From Sheets.
Choose the Power-Path Alarm Investigation workbook.

You should see the chart available for import from the workbook.

Select the Exercise Response Milestones chart.
Leave the link option enabled.

The selected chart should be ready to import with its connection to the workbook preserved.

Import the selected chart into the report.

You should see the chart beneath the diagnosis. Its title should read Exercise Response Milestones.

Chart Not Available for Import?

Return to the workbook from earlier to confirm that the source chart remains on Exercise Metrics.
Confirm that the chart title is Exercise Response Milestones.
Repeat the import after the chart is visible in the workbook.

Help me link my Google Sheets chart into my report.

Write the interview brief and limitations

The interview brief turns your report into a concise explanation of your reasoning. Its closing limitation keeps the portfolio claim accurate.

Click beneath the Interview Brief heading.
Write one or two sentences explaining how you mapped the utility, generator, transfer, UPS, PDU, and load dependencies.

Your opening should establish the full path you investigated before discussing the alarm.

Add one sentence explaining how you avoided misclassifying an on-battery UPS observation as a confirmed UPS failure.
Add one sentence connecting your project-management experience to evidence tracking.

The middle of the brief should show disciplined diagnosis. It should also connect your existing experience to incident coordination.

Add one sentence connecting your project-management experience to escalation ownership plus concise stakeholder communication.
Close with a sentence explaining that the exercise demonstrates refreshed reasoning without replacing hands-on critical-facilities experience.

Your finished brief should cover technical reasoning plus transferable incident-management skills.

Read the interview brief aloud at a natural pace.

Aim to finish in about 60 seconds while covering all four ideas.

Click beneath the Limitations heading.
Type This fictional desktop exercise demonstrates refreshed power-path reasoning and incident communication.

This line states the value of the artifact without expanding its scope.

Type It does not replace hands-on critical-facilities experience, authorized field training, or approved site procedures.

The limitations section now separates analytical evidence from hands-on operating experience.

Before you review the finished report, which section do you expect to make the escalation decision easiest to defend?

Return to the top of the Data Center Power-Path Failure Analysis report.
Confirm that System Map shows the normal path plus the standby path with the fictional-event colors.
Confirm that Decision Record contains the current impact, resilience risk, authorized escalation decision, required follow-up, and safety boundary.
Confirm that the diagnosis separates the confirmed sequence, operational conclusion, and unresolved generator root cause.
Confirm that the linked chart is titled Exercise Response Milestones.
Confirm that Limitations distinguishes refreshed reasoning from hands-on critical-facilities experience.
Confirm that Interview Brief covers power-path mapping, alarm classification, project-management skills, and analytical limits.

You should now see one portfolio-ready report that moves from the system map to a defensible decision. That is a strong finish because every claim stays tied to the fictional evidence.

You have turned an ambiguous alarm into a bounded technical diagnosis plus an escalation-ready report. Your workbook now supports the same story with a correlated timeline and measurable response milestones.

Secret mission

Isolate a Downstream Branch Fault

An energized PDU input can still hide a branch-level loss. Isolate the event to Branch B and Rack B while preserving the evidence needed before claiming a component root cause.

Clean Up Your Resources

Your finished report and workbook live in Google Drive with no ongoing project cost. Choose whether to keep them in use, pause with both files private, or move them to trash.

Resources you used:

A private Google Docs report named Data Center Power-Path Failure Analysis stored in Google Drive.
A private Google Sheets workbook named Power-Path Alarm Investigation stored in Google Drive.

Keep everything running

No action needed. Choose this if you want to keep using the report as an interview discussion artifact.

Keep Data Center Power-Path Failure Analysis private in Google Drive.
Keep Power-Path Alarm Investigation private in Google Drive.
Export the report as a PDF if you want an offline interview copy.

Pause - I'll come back to this later

Leave both files private in Google Drive so you can return later for another scenario or technical review.

Leave Data Center Power-Path Failure Analysis private in Google Drive.
Leave Power-Path Alarm Investigation private in Google Drive.
Return to the files when you are ready to revise the fictional analysis.

Delete - I don't want to use this again

Move both project files to Google Drive trash if you want to remove the fictional exercise.

This cleanup targets only the report and workbook from this project.

Return to the Google Drive file list from earlier.
Select Data Center Power-Path Failure Analysis.
Move the selected report to Google Drive trash.
Select Power-Path Alarm Investigation.
Move the selected workbook to Google Drive trash.
Open Google Drive trash to confirm both file names are listed.

You should see both file names in Google Drive trash. That closes the loop: both project artifacts have left your active file list.

Nice Work!

You did it! You built a diagnostic portfolio pack that traces a critical power path. It turns evidence from two fictional incidents into defensible decisions without claiming unverified root causes.

You've learned how to:

Mapped the normal utility route from its source to the critical IT load. Traced the standby generator route through the shared power path.
Used alarm correlation to show that UPS continuity was bridging an upstream source event. Preserved the unresolved generator root cause as an explicit unknown.
Created a decision record covering current impact plus resilience risk. Recorded escalation ownership. Defined required follow-up. Kept the analytical limitations visible. Presented the response milestones in a linked exercise-metrics chart. Connected your reasoning to DCEO work through a 60-second interview brief.
Completed the Secret Mission by isolating the second event to Branch B plus Rack B. Distinguished its branch-level scope from the first event's upstream resilience risk. Kept the component root cause open until branch-specific evidence becomes available.

Ready to quiz yourself?