Aperture Cloud: Fourteen Revenue Metrics and No Single Net Revenue
Aperture Cloud has 14 Revenue metrics and 9 Active Customer definitions in one shared MicroStrategy project. Finance defines Net Revenue as gross bookings minus credits, refunds, and FX impact. Sales uses ARR, which annualizes contracted recurring revenue and excludes services. Customer Success uses recognized revenue under GAAP. The board deck shows Net Revenue of 4.2 million; Finance's own close shows 3.9 million, a 7.7% gap. Of 42 dashboards, 11 still use metrics marked deprecated. Three metrics carry a certified badge, but one is 'Net Revenue (Finance)' and another is 'Net Revenue - Legacy'. No metric has a named owner beyond the Finance team, and Active Customer is defined variously as a 90-day purchase, a 30-day login, or a 12-month contract. Analysts want one number without losing legitimate regional reporting.
1. Write the specification for the governed Net Revenue metric. What must be explicit so that two analysts cannot legitimately produce different numbers?
Read the worked answer
The specification must state the business definition, formula, grain, filters, time basis, exclusions, source, owner, version, and certification status. For Net Revenue: gross bookings minus credits, refunds, and FX impact; measured at invoice line or service period as Finance specifies; excluding intercompany, tax, and contra-revenue items that belong elsewhere; sourced from the certified revenue fact; owned by a named Finance role, not a team; versioned with an effective date.
The formula must name each component metric and its sign. The time basis must say whether revenue is recognized at booking, service, or close, and how partial periods are handled. The filters must be inside the metric, not left to report authors, so a dashboard cannot silently include a different customer segment. The grain must match the fact table and state how credits and refunds are allocated to lines.
Separate Net Revenue from ARR and recognized revenue in the data dictionary, with plain-language descriptions and synonyms. State that ARR is a contracted run-rate, not a GAAP measure, and that recognized revenue follows accounting rules. That avoids forcing one metric to serve three business questions. Certification should mean the definition has passed Finance review and has a named owner, not merely that a badge was applied.
2. How would you implement and migrate the governed metric in MicroStrategy without breaking 42 dashboards?
Read the worked answer
Build the governed metric as a certified metric object in the shared project, using compound metrics and metric-level filters rather than free-form SQL or report-level filters. Set the format, description, synonyms, owner, and certification metadata. Create a mapping table that lists every existing Revenue metric, its formula, its dashboards, and its disposition: replace, map to a variant, or retire.
Use metadata search and metric lineage to find dependencies before changing anything. Prioritize the 11 dashboards on deprecated metrics, then the remaining dashboards by business criticality. For each, compare the old and new result at a controlled grain, document the variance, and obtain owner sign-off. Where a dashboard needs a different business question, map it to the correct governed metric rather than cloning Net Revenue.
Retire duplicates in stages: mark them deprecated, remove them from the palette, redirect synonyms, and eventually archive them. Keep a compatibility view for one close cycle if needed. Publish a data dictionary and a change log, and require impact analysis for new Revenue metrics. The goal is one certified Net Revenue with explicit variants, not a badge on 14 similar objects.
3. Regional controllers need statutory revenue under local GAAP. How do you allow that without reopening metric sprawl?
Read the worked answer
Treat statutory revenue as a governed variant, not an exception hidden in a dashboard. Create a parent definition that states the shared components and the permitted local differences, then create variants with a clear naming convention such as 'Net Revenue - Statutory DE' and 'Net Revenue - Statutory BR'. Each variant gets the same required specification fields, a named regional owner, a Finance approver, an effective date, and a mapping to the parent metric.
Certify variants only for their intended scope and label them in the dossier. Do not let a variant inherit the global certified badge without qualification. Require the dashboard to show the variant name and the scope, and block use of a statutory variant in global board reporting. Maintain a crosswalk that reconciles each variant to the parent and explains the difference.
Set an exception process: a new variant needs a business question, a legal or accounting basis, an owner, and a sunset review. That prevents analysts from creating a fourteenth Revenue metric because a local report is inconvenient. Review the variant list each quarter and retire any that no longer have a statutory requirement.