Potential value
Stronger continuity, more useful data and faster investigation. Agree which outcomes matter to this mission service.
FOUNDATIONS / PROJECT KICKOFF
Prepare the next decisions together.
Navy Gulf Support Activity (fictional, exercise only) · Start with the mission service. Compare potential value, shared responsibilities and the evidence needed to choose a practical way forward.
A facilitated opening. Confirm scope and participation with the sponsor.
1 What changes for the mission service?
Added work
Map dependencies, design recovery and instrument owned code. Coordinate platform, application, network and cyber-defense support.
Evidence to decide
Compare the legacy baseline with proposed changes. Verify coverage, restoration and service outcomes; retain human review and approval.
2 Who needs to be involved
The familiar local support contact may remain the same. In a shared-service model, that team may coordinate across platform, application, network and cyber-defense functions. Confirm the actual support path and retained decisions; a new provider name alone does not establish a new responsibility.
Sponsor & accountable owners
Confirm the purpose, scope, priorities and decision authorities.
Data steward & custodians
Coordinate existing material, identify its owner and explain its context. Collection does not set a reading.
Consultant & senior reviewer
Interpret, confirm or override proposals with a note; complete senior validation before issue. One consultant can perform both steps.
3 Two weeks of preparation + six weeks together
These eight weeks describe the advisory engagement. Advance data-call lead times and the 24–48-month implementation planning horizon are separate; confirm their dates and assumptions in Intake. Activities overlap. Agree checkpoints, access and participation; this overview is not a delivery or authorization guarantee.
4 How a reading becomes useful
Source → proposal
Existing material informs the engine’s proposed reading; unknowns remain visible.
Consultant judgment
Confirm the proposal or explain an override. Distinguish a requirement from a recommended practice.
Senior validation
Review every reading before issue. A readiness level is not certification or authorization.
5 One record, four connected reports
Leadership decision brief
Which decisions need attention?Priorities, alternatives, open risks and proposed owners.
Cloud foundation and readiness plan
What exists, and what must change?Current posture, future requirements, boundaries and unresolved questions.
Transition and transformation plan
What moves first, what waits and why?Workstreams, dependencies and a sequence to review with delivery owners.
Operating handover and evidence package
Who carries the work forward?Responsibilities, source references, follow-up actions and review cadence.
Jumpstarts support local adaptation. Foundations Plus is optional, separately scoped depth—not four additional mandatory stages. Packages & Plus →
6 What we ask you to bring
For the service under discussion, bring dependency paths, data freshness or lineage, a normal-performance baseline and recovery-test evidence where available. OpenTelemetry is a proposed instrumentation approach unless coverage is demonstrated. Resilience and human-reviewed AIOps depend on design, coverage and tests; no availability or repair-time gain is assumed.
Existing material
Use the data call. Identify the source, owner, date and relevant operating context; flag missing or restricted items.
People who know the service
Bring custodians to focused working sessions. Explain normal operations, exceptions and dependencies.
Decisions & corrections
Confirm future needs and responsible owners. Challenge misunderstandings before they become the plan.
7 How we work with your team
Approved handling
Use the agreed client environment and handling rules. This demonstration contains fictional material only.
Separate working and issued records
Browser changes are a working copy. Export and rebuild before revised reports are handed over.
Clear authority
Consultation and jumpstarts do not authorize implementation or accept risk. AI is optional and requires client-approved availability and use.
8 Start with the engagement context
For the consultant: daily working guide and filter → · Offline and enclave operating guidance