CCR-006 Project Relay — Operational Continuity Dependency Mapping Lab

CCR // PROJECT RELAY

CCR-006OPERATIONAL CONTINUITYCONCEPT ENVIRONMENT

STATUSACTIVEMODEEXPERIMENTALPRODUCTIONNOVISIBILITYINTERNAL

THE QUESTION

WHAT DOES THIS BUSINESS DEPEND ON?

AND THEN: WHO OR WHAT DOES EACH OF THOSE THINGS DEPEND ON?

Project Relay explores how a small or midsize organization could identify and visualize the people, systems, vendors, accounts, devices, and processes that its operations actually depend on.

Someone knows the password.

Someone owns the vendor relationship.

Someone remembers why the software exists.

Someone knows which credit card pays for it.

Someone knows where the contract is.

Someone knows what happens when it breaks.

Until that person leaves.

Or is unavailable.

Or simply forgets.

DEPENDENCY MAPPING CONSOLE

SELECT A FUNCTION TO TRACE ITS DEPENDENCY CHAIN

BUSINESS OPERATIONS

DEPENDENCY CHAIN

DOMAIN

DNS

HOSTING

ADMINISTRATIVE ACCESS

BILLING METHOD

RESPONSIBLE PERSON

DEPENDENCY RECORD

DEPENDENCYDOMAIN REGISTRATION

PURPOSEPrimary business domain

PRIMARY ADMINOperations Manager

BACKUP ADMINNONE IDENTIFIED

BILLING OWNEROperations Manager

DOCUMENTATIONNOT FOUND

LAST VERIFIED214 DAYS AGO

DEPENDENCY STATUS

ACTIVE

CONTINUITY FLAGS

SINGLE PERSON DEPENDENCY

NO BACKUP ADMINISTRATOR

RECOVERY PROCEDURE NOT DOCUMENTED

THE ABSENCE TEST

WHAT HAPPENS IF THIS PERSON IS UNAVAILABLE TOMORROW?

DEPENDENCIES ASSOCIATED WITH OPERATIONS MANAGER

DOMAIN ADMINISTRATIONREVIEW REQUIRED

PHONE ACCOUNTREVIEW REQUIRED

WEBSITE HOSTINGREVIEW REQUIRED

FACILITY ALARMREVIEW REQUIRED

PRIMARY VENDOR CONTACTBACKUP OWNER

SOFTWARE BILLINGBACKUP OWNER

MFA DEVICEREVIEW REQUIRED

SUMMARY

DEPENDENCIES IDENTIFIED

HAVE BACKUP OWNERS

REQUIRE REVIEW

The dependency structure is what is being evaluated — not the individual.

FAILOVER VIEW

IF THIS DISAPPEARS, WHAT BREAKS?

IF INTERNET SERVICE DISAPPEARS →

PAYMENT TERMINALSTOPS WORKING

CLOUD APPLICATIONSSTOPS WORKING

VOIP PHONESTOPS WORKING

CUSTOMER WIFIDEGRADED

REMOTE ACCESSDEGRADED

CONTINUITY READINESS

OPERATIONAL CONDITIONS

Transparent counts. No proprietary score.

DEPENDENCIES DOCUMENTED

18/ 24

BACKUP OWNER IDENTIFIED

15/ 24

RECOVERY PROCEDURE DOCUMENTED

11/ 24

VERIFIED WITHIN REVIEW PERIOD

17/ 24

A MAP IS ONLY USEFUL IF IT STAYS TRUE.

Businesses change.

Employees leave.

Vendors change.

Accounts move.

Devices are replaced.

Contracts renew.

New software appears.

Old software gets forgotten.

Operational continuity is not just documenting dependencies once.

It is periodically verifying that the map still reflects reality.

IDENTIFY

DOCUMENT

ASSIGN

VERIFY

REVIEW

UPDATE

CONCEPTUAL FUTURE STATE

WHAT A MATURE VERSION COULD SUPPORT

These features do not currently exist. This is a concept environment.

DEPENDENCY REGISTER

OWNERSHIP ASSIGNMENT

BACKUP OWNERS

REVIEW DATES

VENDOR RECORDS

CONTRACT REFERENCES

RECOVERY INSTRUCTIONS

DEPENDENCY RELATIONSHIPS

PERIODIC VERIFICATION

CHANGE HISTORY

PROJECT DECISION

WHAT ARE WE TRYING TO LEARN?

Could a lightweight dependency-management system help smaller organizations maintain operational continuity without requiring a large enterprise business-continuity platform?

WHAT WOULD WE TEST NEXT?

Is the dependency model understandable?

Can a business complete the initial inventory without excessive effort?

Which dependencies actually deserve ongoing review?

Which information becomes stale fastest?

What should trigger a review?

Could periodic verification become a practical managed service?

EXIT

PROMOTE

EXTEND