Engage
Frame mission context, stakeholders, decision authority, and target impact level.
Functional Flow
The assessment engine is a decision pipeline.
The internal team should understand cMAP as a flow from evidence intake to client-facing recommendations, not as a spreadsheet of scores.
Discover
Register artifact intake, sensitivity, ownership, and evidence availability.
Assess
Score the 51 artifacts on a 0–4 evidence scale across People, Process, and Technology.
Verify
Confirm scores with SMEs and capture follow-ups before release language is used.
Synthesize
Apply rule sets, standards imprint, and 6R readiness logic to expose decisions.
Plan
Sequence transition and transformation actions across 0–48+ month horizons.
Deliver
Package the readout, reports, roadmap, traceability, and evidence caveats for sponsor-controlled release.
Decision Logic
What cMAP derives from the 51 artifacts.
The value is not the score alone. The value is the interpretation of what the score means for mission cloud operations.
Relationship Areas
How domains connect to standards imprint and OEM support.
These mock-ups show high-level relationship areas across the 10 cMAP domains without claiming compliance, authorization, or CSP service approval.
Migration Foundation Readiness
The 6R view is foundation readiness, not app disposition.
cMAP maps artifact gaps to minimum viable foundation services before a client selects migration treatments for specific applications.
Baseline landing zone, identity, network, logging, monitoring, wave planning, and environment controls needed before lift-and-shift is responsible.
Consumption, service catalog, FinOps, integration, data governance, acquisition, and IL alignment needed before managed cloud services become practical.
Automated toolchains, platform engineering, DevSecOps, CaC/IaC, telemetry, and cloud-native operating patterns needed before deeper modernization.
Legacy, latency-sensitive, RISC/Unix, coupled, or boundary-constrained systems may need isolation, surround controls, or delayed migration treatment.
People Capacity Reference
Use the operating-model reference when a staffing decision needs context.
This reference supports internal interpretation of team structure, platform skills, support tiers, hiring zones, and impact-level considerations. It does not alter evidence scores or create an engagement finding.
Roadmap Logic
Transition first. Transformation follows.
The time horizons explain why some work can begin immediately while other work needs architecture, acquisition, staffing, integration, or platform decisions.
Close no-regret blockers and evidence gaps the existing team can begin without waiting for major acquisition.
Stand up platform foundations, operating model depth, governance, integrations, and initial migration capability.
Move beyond baseline migration into managed services, automation, continuous monitoring, and repeatable delivery.
Scale cloud-native capability, automated evidence, portfolio rationalization, FinOps, and sustained mission operations.
Consultant Use
How to explain the tool internally.
This page is intentionally plain-language enough for pursuit teams and precise enough for technical delivery leads.
What cMAP helps a client see
Where readiness is real, where evidence is thin, which decisions are blocked, and what foundation services must exist before migration velocity is credible.
How recommendations are derived
Recommendations come from scored artifacts, domain readiness, standards/citation context, 6R foundation thresholds, and transition/transformation timing rules.
What cMAP does not claim
It does not replace RMF assessment, AO decisions, control inheritance validation, CSP authorization status, procurement authority, execution authority, or application-level migration disposition analysis. Phase 2 follow-on material can support WWT or approved partners only after sponsor release.
Release Roadmap
Plan feature releases without breaking the baseline.
Future production work is sequenced as minor feature releases, major feature releases, or deferred options while preserving the static/local default path.