Skip to content
English
  • There are no suggestions because the search field is empty.

Battleground Command Centre: what it shows and how to read it

The Command Centre reads the records your team already keeps: analyses (BIAs), risks, controls, incidents, exercises, plans, providers and obligations. It works out what those records mean when they are read together. It holds no data of its own, so everything on every screen is computed from your registers each time you open it. You'll find it in the left-hand menu under Command Centre.

The screens

  • Overview - Your resilience score across six measures, the resources your critical work depends on with no workaround, and what to look at first.
  • Mapping - Dependency Map (what an analysis stands on), Critical Operations Map, Process Map, End-to-End Chains and Portfolio Breakdown.
  • Connections - Insights and Findings, Chains, Network, Linkage Matrix, Coverage and Gaps, and Concentration and SPOF.
  • Scenario Lab - What-If Lab (remove a site, provider or application and see what stops), Reverse Stress Test, Batch Simulations, Test Log and Exercise Builder.
  • Exercise Insights - Programme, Deep Dive, Coverage and Audit, Learnings and Themes.
  • Regulation and Assurance - Frameworks, Assurance Calendar, Evidence and Definitions.
  • SOCI and CPS 230 Reporting - Completeness and position against those regimes, with registers and notification tracking.
  • Board Reporting - The same figures, written for a board pack.

Not every organisation sees every screen. What appears depends on the modules you hold and your own permissions.

Reading what it tells you

The Command Centre separates five states. Most of the questions we get come from reading one as another.

State What it means Who resolves it
Evidenced Your records support it Nobody, it is done
Not evidenced Your records say the duty is not being met You
Not recorded The field exists, you hold the module, nothing has been entered You
Not held The platform has no field where that answer could live Us, once you tell us
Not licensed The field exists; the module has not been purchased A commercial conversation

The important one is Not recorded. A blank area is never shown as a clean one. If nothing has been entered, the screen says so and says what that means. It will tell you key-person risk has not been assessed, rather than showing a reassuring zero.

 

Common questions

A panel says nothing has been recorded to assess. What do I do?

Nothing is broken. It means that area of your analyses holds no records at all, so nothing on that screen could have found anything in it. The panel names the area and what it costs you, and the fix is data entry rather than a support ticket.

Why is our single point of failure count so high?

A resource is counted as a single point of failure when two things are both true: your most critical work depends on it, and no workaround is recorded against it anywhere it appears.

A high count usually means workarounds exist in practice but have not been written down. Add the manual workaround on the dependency, application or workplace in the analysis and the count falls on the next load.

A site shows "no alternate site" but we do have one

The Command Centre reads two fields on the workplace inside the analysis:

  1. "For this location, can staff be relocated to an alternative workplace / location?", set to Yes
  2. Alternative Workplace Locations, naming the location itself

Setting the first is enough for the site to count as having an arrangement. Naming the location as well is what lets the map show where staff would go. If the map still says no alternate, check the workplace record inside the BIA rather than the location register.

Why are People shown as not recorded?

People reach the Command Centre through the response team attached to an analysis. Holding response teams with members in them is not enough on its own. The team has to be linked to the analysis. Until it is, key-person risk cannot be assessed and the screen says so.

I updated a record. Why hasn't the Command Centre changed?

Feeds are cached briefly per user so the screens stay quick when you move between them. Reload the page to pull fresh data. If a figure still looks wrong after a reload, tell us.

A finding I fixed has come back

Findings are recomputed from your records every time the screen loads. They are not a list that gets ticked off. If one has returned, the records it reads have moved back into the state that raises it. Each finding shows the chain of records it came from, so open it and follow the chain to see which record is now triggering it.

The wording doesn't match ours

It should. The Command Centre uses your configured terminology: Critical Operation or Important Business Service, Service Provider or Third Party, your criticality tiers and consequence categories. If a screen is using wording you don't recognise, that is worth reporting.

A screen is missing from my menu

Either your organisation does not hold that module, or your user does not have permission for it. Your Battleground administrator can confirm which.

 

Telling us something is wrong

There is a Feedback button at the top of every screen. It sends us the screen you were on along with your message, which is usually enough for us to reproduce the problem without a back-and-forth. Use it for anything that looks wrong, including figures you think are wrong. Those are the most useful reports we get.