Overview of Mission Continuity

What to expect

CardinalShield Mission Continuity (MC) is similar to using tax preparation software, like TurboTax, which many people are already familiar with. The following are some similarities:

First, you need to gather the necessary information to enter into the software; see the section Prework Before Updating MC for the questions you should consider and data you should gather in advance.
Second, MC is workflow driven, so you must enter data step by step, as the data builds on each other, but you can go back to an earlier section and make updates before you submit for approval.
Third, there are descriptions and help text within MC, so you are guided how to answer questions and enter data.
Fourth, while the software application will be unfamiliar to you the first time you use it and while it may seem like you’re initially entering a lot of data, in the following update cycles, the software application will be more familiar and you’ll just be reviewing and making incremental updates.
Fifth, once your updates are complete, your MC plan will be forwarded for two levels of review and approval.
Lastly, once your MC plan is approved, you’ll be able to print it and/or save it as a PDF outside of the CardinalShield application.

Overview of MC

The chart below provides a summary of the steps in the MC workflow and the data being gathered in each.

WORKFLOW STEPS	SUMMARY OF DATA BEING GATHERED
Group/Team/Division Profile	Group/Team/Division Name, Category, Description, Scope, Staff Listing
Essential Contacts	Other Stanford Contacts Info, Non-Stanford Contacts Info
Leadership & Succession/Delegation	Continuity Responsibilities, Activation Authority, Order of Succession, Delegation of Authority
Essential Functions	Function Name, Description, Manager, Participants, How to Continue with Reduced Staff, Can It Be Performed Elsewhere, Peak Period, Primary Role, Recovery Priority, Stanford Impact, Duration of Interruption when Operational/Financial Impacts Will Occur, Severity of Impacts
Technology Requirements	Applications - Name, Function, Workaround IT Service - Type, Function, Workaround External Website/Service - Website Name, URL, Function, Workaround
Essential Resources	Equipment - Name, Function, Location, Model, Vendor, Monitoring Status, Backup Plan Supply - Name, Function, Location, Vendor, Sensitivity, Backup Plan, Special Requirements Vendors - Name, Contact Info, Alternative Vendors Interdependencies - Upstream, Downstream Vital Records - Name, Function, Backup, Off-site Access
Facility & Alternate Facility Requirements	Primary - Function, Stanford Property or Non-Stanford Property, Location, Space Type, Requirements, Loss of Utilities Alternative - Stanford Property or Non-Stanford Property, Location, Equipment, Requirements
Activation & Demobilization	Step Name, Details/Description, Positions
Group/Team/Division Review & Approval	Approvals, Changes