- Subscription
MightyCare VCF Adoption Portal
MightyCare's VCF Adoption Portal turns a Broadcom VCF adoption from a slide deck into a tracked, evidenced process.
Every customer journey follows the five-phase Broadcom model, from Consult and Vision through Workload Migration and Optimization, with the AD checkpoint at each gate. The portal shows what is due, who owns it, whether partner, customer or Broadcom, and what is overdue, so nothing waits in an unread mailbox.
A PCMMA maturity assessment establishes the starting point. From there the adoption plan is versioned: each snapshot records what was agreed and what was
delivered, giving partner and customer the same picture at every review.
Journeys can be shared with the customer and with Broadcom by explicit opt-in. Master data, licenses, activities, commitments and risks live on the customer record, with a full audit trail.
Built by MightyCare Solutions GmbH and used daily on our own VCF engagements.
Features
Adoption is where a VCF deal is won or lost after the signature, and it usually lives in slides and inboxes. This portal gives the process a place to happen: five Broadcom phases, an AD checkpoint at every gate, and one clear answer to the question that actually moves a project — whose turn is it now? Partner, customer and Broadcom each look at the same record through their own gated view, so nobody works from a stale export.
- • Five Broadcom phases with an AD checkpoint each
- • Whose turn: partner, customer or Broadcom
- • PCMMA maturity assessment across 35 questions
- • Adoption plan versioned as frozen snapshots
- • Customer portal plus login-free share link
- • Vendor view for Broadcom, opt-in per journey
- • Evidence on file for deal registration
- • Renewal readiness score with open blockers
- • Every change logged on the customer record
- • English and German, switched in one click
Specifications
Deployment: Runs in MightyCare's own environment as a managed service. Containerised services on Linux, PostgreSQL as the data store. No agent and no appliance is installed in the customer's VCF estate.
Access and identity: Single sign-on against Keycloak (OIDC), JWT bearer tokens carrying a tenant claim. Roles govern what each account may see and change.
Tenant isolation: Every tenant-bound table is protected by fail-closed row-level security in PostgreSQL. Without a bound context a query returns nothing rather than everything. The customer view and the vendor view are separate perspectives at the database level, each limited to the journeys explicitly opted in — not an application filter that a missing WHERE clause could bypass.
Data brought in: File imports for Broadcom Support Portal entitlements, the VCF licence calculator, VCF Operations utility exports, vCollector, vScout, the Broadcom questionnaire, and RVTools exports for usage evidence. Collector and entitlement files are handled as confidential and are not shared through the customer or vendor views.
Data given out: Adoption plan as a document, adoption status as a spreadsheet, readiness and AI reports as PDF, and a Broadcom-shaped export for reporting. Every download of an adoption plan is recorded in the audit log.
Process model: Five-phase Broadcom journey with an AD checkpoint closing each phase. Journey templates for greenfield build, consolidation, and the full holistic path; a renewal template for the day-2 cycle. PCMMA assessment covering 35 questions across four audience levels.
Language: Interface and generated documents in English and German, switched per user.
Use of AI: Every model call is routed through an in-house language model with an explicit data classification, is logged with prompt, response and purpose, and is confined to the tenant it was made for. Customer data does not leave the environment for a cloud model. Model output is marked as such in the interface, as required by Article 50 of the EU AI Act.
Audit: Append-only audit log covering security-relevant actions and every change to a customer record, with actor, timestamp and the values before and after.