Domain 4: Manage the FinOps Practice
| Application | Visual One Intelligence (VisualOne / VSI) |
| Platform version referenced | v6.0.0.1 |
| FinOps Framework domain | Manage the FinOps Practice |
| Capabilities in this section | FinOps Practice Operations · Executive Strategy Alignment · FinOps Education & Enablement · Governance, Policy & Risk · Invoicing & Chargeback · FinOps Assessment · Intersecting Disciplines |
| Source basis | VisualOne reference documentation (FinOps for VisualOne Reference Guide; VSI Screen Reference Guide; VSI Virtualization Reporting User Guide; Visual One Storage Reference) |
4.1 FinOps Practice Operations
Capability: Enable a FinOps culture and empower the FinOps practice through implementation of FinOps strategy and processes.
How VisualOne enables this
Alongside the product surfaces, VisualOne ships an operating model, a four-phase implementation roadmap, named success factors, and eleven end-to-end use-case workflows across operational, financial, and governance domains, with the platform providing the surfaces each workflow step runs on.
Supporting features
| Element | Implementation |
|---|---|
| Phased implementation roadmap | Phase 1 Foundation (months 1-3): complete device inventory and registration, configure accurate operating costs, establish tagging standards, train users on data entry and validation. Phase 2 Analysis (months 4-6): generate baseline reports and metrics, identify cost patterns and drivers, validate cost allocations, establish budget baselines. Phase 3 Optimization (months 7-12): prioritize recommendations, implement quick wins, track savings realization, refine allocation models. Phase 4 Continuous Management (ongoing): monthly reporting and variance analysis, quarterly optimization reviews, annual budget planning, continuous process improvement |
| Named success factors | Complete and Accurate Data; Proper Configuration; Active Management; Stakeholder Engagement (executive sponsorship, department participation in chargeback, cross-functional collaboration, communication of insights); Continuous Improvement |
| Workflow library | Eleven use cases with objective, metrics used, step-by-step process, and stated outcome, four operational (capacity planning, performance management, asset lifecycle management, health monitoring), five financial (chargeback, budget variance, optimization prioritization, TCO analysis, financial forecasting), and four governance (tag governance, cost governance, optimization tracking, financial compliance reporting) |
| Recurring operating cadence | Daily health-indicator review; monthly chargeback and variance cycle; quarterly optimization review; annual budget planning |
| Multi-tenant / multi-team operation | Change Client selector in the global header and a dedicated Clients screen support running the practice across multiple organizations or business entities; Profile and Settings sections carry per-user configuration |
| Shared working artifacts | Saved views on every grid, saved chart zoom ranges, and named Cluster Modeling projects with notes fields, with the documented practice of recording assumptions so models can be reproduced by others |
| Workflow state in-product | Alert acknowledgement status, Orphaned VMDK acknowledgement, right-sizing Approve action, and the Open/Suggested/Applied recommendation lifecycle give the practice trackable work items rather than static reports |
| Communication mechanism | Custom Email / Generate Report in the global header for building and distributing reports; weekly efficiency reports delivered by email |
| Data discipline | The Collection Date model gives the whole practice a shared, unambiguous “as of” reference for any figure under discussion |
Personas served
FinOps Practitioner (owns the cadence), Leadership (sponsorship and review), Engineering and Finance (participants in the documented workflows).
4.2 Executive Strategy Alignment
Capability: Enable FinOps teams to partner with executive leaders on strategy alignment of technology spend, through clear decision support, shared accountability, and business-relevant measures.
How VisualOne enables this
VisualOne provides a dedicated Executive Reports section in the primary navigation, plus a set of single-number, executive-legible measures that roll the entire estate into a position a leadership audience can act on.
Supporting features
| Element | Implementation |
|---|---|
| Dedicated executive surface | Executive Reports is a top-level navigation section alongside Storage, FinOps, Hosts, Files, Virtual, Backup, Switches, Databases, Cloud, Security, and Kubernetes |
| Single-number position | Overall Efficiency gauge (0-100 with a status pill) gives leadership one portfolio-level measure of whether the estate is returning value for its cost |
| Total roll-up context | The Total context aggregates Storage + Compute + Cloud into a single consolidated view of all costs, the executive-level summary view |
| Financial position | Cost YTD Report presents year-to-date spend by context with month-over-month trend and run-rate-based year-end projection; Cost Per Sector presents budget vs. actual with variance by sector |
| Opportunity position | Optimization Recommendations supports executive reporting on cost optimization opportunities, with the Recommendations donut sized by savings value so the largest lever is immediately visible (example: Reserved Instance = 79% of a ~$77,000 opportunity) |
| Savings position | Savings Report Total context gives a one-screen estimated-savings figure by domain; Savings Realization % shows whether committed savings are landing |
| Investment decision support | TCO per TiB comparison for procurement, Payback Period, and ROI % translate technical proposals into the terms leadership decides in; Cluster Modeling’s cost tab supports budget justification |
| Shared accountability | Chargeback Report and Tag Summary devolve the consolidated number to named departments and cost centers, and the governance workflow includes reviewing variance directly with cost center managers and escalating out-of-policy spending |
| Enterprise health position | Enterprise Summary and Enterprise Health Report roll device inventory, capacity, performance, and health indicators to an estate-wide view |
| Distribution to executives | Report generation and email distribution, including weekly efficiency reports, deliver the position without requiring executives to log in |
Personas served
Leadership (primary), FinOps Practitioner (prepares and presents), Finance (budget and investment framing).
4.3 FinOps Education & Enablement
Capability: Provide FinOps training, skill development, and practical activities that enable teams to adopt and deliver FinOps best practices.
How VisualOne enables this
Enablement is delivered through structured user documentation, a published and transparent calculation methodology, a library of practical repeatable workflows, and contextual guidance at the point of use in the product.
Supporting features
| Element | Implementation |
|---|---|
| Formal user documentation | A versioned Virtualization Reporting User Guide (v1.0) structured for adoption: intended audience, platform overview, getting started, navigation and common page controls, core concepts and terminology, screen-by-screen guide, common workflows, reporting/exporting/integrations, security and retention, troubleshooting and FAQs, and appendices |
| Reference and terminology assets | A Glossary of Terms defining the vocabulary a new practitioner needs, Array, Capacity, Chargeback, Cost Center, Daily Operating Cost, Depreciation, Effective Capacity, Orphaned Resources, IOPS, Latency, Lifecycle, Normalization, Operating Cost, Optimization, Purchase Price, Savings, Tag, TCO, Utilization, Variance, YTD, plus a Metrics Quick Reference appendix and a URL map |
| Transparent methodology | Ten sections of documented formulas with worked examples (operating cost, normalization, depreciation, TCO, allocation, variance, forecasting, savings realization, payback, ROI). Publishing the calculations is itself an enablement asset: teams can understand and defend every number rather than treating it as a black box |
| Practical activity library | Eleven end-to-end use cases and four common workflows, each written as a repeatable procedure with a stated outcome, usable directly as training exercises |
| In-product guidance | Contextual helper text at the point of use: “Double click a row to edit then press enter to commit changes. Export CSV, edit values, then re-upload to bulk update.” · “Double click to see detailed tag reports” · “You can acknowledge (hide) alerts. Use Shift + Click on the grid below to select multiple alerts at once” · a filter-change warning on Tag Forecasting reminding users to save local changes first |
| Access to documentation from the product | Documentation and Installation Instructions buttons on the Collection Devices admin screen |
| Guided onboarding | Initial setup includes a data collection setup call, with typical setup completed in 1-2 hours |
| Q&A / FAQ assets | A common questions appendix covering report refresh cadence, allocation model customization, savings report interpretation, record-count discrepancies, blank performance fields, negative build capacity, and right-sizing validation |
| Standards literacy | FOCUS Export aligns the organization’s cost data to a recognized FinOps Foundation open standard, building transferable rather than tool-specific skills |
| Consistency as an enabler | Once a user has learned one VSI grid, the interaction model transfers directly to every other grid in the product, a deliberate reduction in the training burden |
| Training in the rollout plan | Phase 1 of the implementation roadmap explicitly includes training users on data entry and validation |
Personas served
All personas onboarding to the platform; FinOps Practitioner as the internal trainer.
4.4 Governance, Policy & Risk
Capability: Establish policies, controls, and governance mechanisms ensuring technology use aligns with business objectives, complies with regulatory requirements, and optimizes resources efficiently.
How VisualOne enables this
Governance operates on three levels: metadata governance (tag standards), financial governance (cost accountability and policy enforcement), and platform and security governance (access, audit, retention, certification).
Supporting features: metadata governance
| Element | Implementation |
|---|---|
| Tag standard enforcement | Tag Key Mapping establishes an authoritative internal vocabulary and reconciles source variants to it (Unified BU ← BU / BusinessUnit / Dept / Department / CostCenter), preventing the same dimension fragmenting across systems |
| Tag compliance audit | All Tags Report is the audit surface, every distinct tag key/value in the estate (73 records observed) in one catalog, supporting tag governance and compliance verification, identification of tag standardization opportunities, and discovery of tag pollution |
| Governance workflow | Review All Tags for standardization → verify all required tags are applied → check name consistency (BU vs. Business Unit) → validate mapping to external systems → correct non-compliant tags → document tagging standards. Stated outcome: standardized metadata, improved reporting accuracy |
| Unallocated visibility | An explicit Unknown BU value surfaces resources failing the tagging policy rather than hiding them |
Supporting features: financial governance
| Element | Implementation |
|---|---|
| Cost accountability policy | Assign accountability by cost center → establish cost targets and budgets → generate monthly chargeback reports → review variance with cost center managers → implement controls for cost compliance → escalate out-of-policy spending. Stated outcome: cost accountability, policy compliance |
| Variance policy threshold | Investigation of variances >10%, with month-over-month variance trend monitoring to catch drift early |
| Financial compliance reporting | Extract asset data from the Financial Administration Report → calculate depreciation for the accounting period → generate a fixed asset schedule → reconcile to the general ledger → provide to external auditors → archive for audit trail. Stated outcome: audit-ready financial data, compliant reporting |
| Controlled cost assumptions | Operating Cost is an admin-only Settings screen, the source-of-truth configuration behind the computed reports, separating who may change costing assumptions from who consumes the reports |
| Point-in-time auditability | Collection Date snapshots preserve the state of the estate on any past date, so a reported figure can be reproduced as of the period it was issued |
Supporting features: platform, security, and risk governance
| Element | Implementation |
|---|---|
| Certification | SOC 2 Type II compliant, with a SOC 2 Type II audit completed in 2024 |
| Authentication | Supports SSO and passwordless authentication; encrypted authentication and secure data handling |
| Encryption | Encryption in transit and at rest |
| Least privilege | Collector permissions guidance is least-privilege, with read-only often sufficient; SSH-key auth supported as an alternative to stored passwords; collection-device credentials carry a Password Removed state field |
| Data retention policy | Customer data retained while the account is active; where no contract terms apply, data deleted within 90 days of account closure (or sooner on request), with an option to archive prior to deletion |
| Privacy handling | Device and display name fields are shown PII-eliminated in the storage reporting |
| Risk detection and escalation | Health alert severity model with acknowledgement audit state and ServiceNow incident creation, moving risk items into the enterprise incident-management process; six per-device Green/Yellow/Red status indicators covering configuration, balance, mapping, errors, layout, and snapshot consistency |
| Operational risk controls | Pre-action controls, validate orphaned VMDKs against change records and retention policies before deletion; coordinate right-sizing with change management windows and application owners; validate post-change behaviour at the next collection |
| Administrative controls | Admin-scoped Settings screens (Operating Cost, Collection Devices, VM Right-Sizing) separated from the read-oriented report menu; destructive collector actions gated behind explicit selection (Update Selected / Delete Selected) |
Personas served
FinOps Practitioner (tag and cost governance), Finance (financial compliance and audit), Leadership (policy and escalation), Engineering (change-controlled remediation), Security and Compliance (platform certification, retention, access).
4.5 Invoicing & Chargeback
Capability: Enable invoice reconciliation workflows and chargeback models that align cost data and reporting to specific budgets and accounting requirements.
How VisualOne enables this
Chargeback is delivered through a purpose-built report, three configurable allocation models, resource-level bill backup, and a documented invoicing workflow, with an accounting-grade cost basis behind every charge.
Supporting features: chargeback
| Element | Implementation |
|---|---|
| Dedicated chargeback report | Grouping dimension selector (default Department) and cost metric selector (default Total Cost); horizontal stacked bar by cost center with per-resource segments and a colour legend; grid holding one record per department × resource × period, running to thousands of records |
| Three allocation models | Equal split (Total Cost ÷ Number of Units); Usage-based (Total Cost × Department Usage ÷ Total Usage, with a worked example reconciling exactly to the total); Tag-based (sum of all resource costs carrying the department tag, worked example totalling $26,700 for Finance across storage, virtual, and cloud). Allocation model is administrator-configurable |
| Multi-dimensional chargeback | A single device can carry multiple tags, so the same cost base can be charged out simultaneously by BU, Environment, Cost Center, Owner, Function, or Operational Category |
| Sub-resource chargeback | Compute cost split by Memory Cost % and CPU Cost % (typical 50/50) enables VM-level chargeback of a shared host on a per-vCPU and per-GiB-memory basis |
| Shared-cost allocation | FOCUS Export exposes Allocated Method ID, Allocated Resource ID, Allocated Method Details, Allocated Resource Name, and Allocated Tags, supporting distribution of shared cost across multiple consumers |
| Bill backup / line-item detail | Tag Summary provides the defensible detail behind each charge: per-resource daily cost with record counts, itemized as Host Name / LUN Name for storage, Resource Name / Service Type for cloud, and VM Name / Cluster for virtual, the detail needed to answer a disputed charge |
| Invoicing workflow | Ensure all devices properly tagged with Cost Center → run Chargeback Report grouped by Cost Center → validate cost calculations → generate invoices to departments → follow up on disputed charges. Stated outcome: accurate cost allocation, departmental accountability |
| Accounting-grade cost basis | Financial Administration Report supplies the auditable components behind each charge: Purchase Price, Total Acquisition Cost, Total Maintenance, Power/Floor Space/Personnel cost per day, Daily Operating Cost, Purchase Cost per Day, Cost of Asset per Day, Total Cost per GiB per Day, and Life of Asset |
| Depreciation alignment | Amortization Report provides the monthly asset depreciation value per device, aligning chargeback to the depreciation treatment used in the financial statements; formulas cover daily and annual straight-line depreciation |
| Budget alignment | Chargeback output reconciles to Cost Per Sector budget-vs-actual and to Cost YTD totals, so charges tie back to the budget they consume |
| Downstream billing integration | Foreign Tag Key mapping targets external billing systems, cloud provider tag schemas, and ITSM platforms; FOCUS Export (JSON) and grid CSV export deliver the charge dataset into an external billing or ERP process |
| Showback support | The Virtualization module supports showback/chargeback and cost tiers for FinOps and IT finance stakeholders, with per-VM cost distribution for informational showback where formal chargeback is not in place |
Supporting features: reconciliation
| Element | Implementation |
|---|---|
| Internal reconciliation | Cost calculations are validated before invoice issue; the usage-based allocation example is verified to sum back to the total; the sum of all chargeback records equals total infrastructure cost |
| GL reconciliation workflow | The financial compliance use case reconciles the extracted asset and depreciation schedule to the general ledger and archives for audit trail |
| Cloud billing identity | FOCUS Export carries Billing Account ID / Name / Type and Sub Account ID / Name / Type alongside Charge Period Start/End, Charge Category, and Effective Cost, the fields required to line data up against a provider invoice |
| Period alignment | Collection Date selection allows reports to be aligned to an accounting or audit period, and Charge Period Start/End fields carry the period boundary into exported data |
Personas served
Finance (invoice preparation, GL reconciliation, audit), FinOps Practitioner (allocation model design and dispute resolution), Leadership (departmental accountability), Engineering (understanding what their resources are charged).
4.6 FinOps Assessment
Capability: Conduct repeatable, measurable analysis of the maturity of a FinOps practice in the context of the FinOps Framework, for insight into strengths and areas for improvement.
How VisualOne enables this
VisualOne applies a consistent, repeatable scoring model on every collection, producing measurable results that are comparable over time, alongside effectiveness measures for the practice itself.
Supporting features
| Element | Implementation |
|---|---|
| Repeatable scored assessment | The Cost Efficiency Dashboard applies a consistent 0-100 scoring model to every asset on every collection: four tiers (Optimal >75, Efficient >50-75, Underutilized >25-50, Wasteful ≤25), live counts per tier, and an Overall Efficiency gauge for the portfolio (observed 14/100) |
| Strengths and weaknesses identification | Top Performers and Low Value panels name the five best and five worst assets by score; the Matrix view groups the whole estate into tier bands, making the shape of the problem legible at a glance |
| Longitudinal comparison | Scoring re-runs each collection and Collection Date snapshots are retained, so assessment results are comparable over time; the Delta Report quantifies change between any two periods |
| Capacity maturity indicators | Capacity Score (0-100 balance and utilization health), Weeks Left to Capacity, Build Capacity, and Limiting Factor give a second repeatable scored dimension |
| Practice-effectiveness measures | Savings Realization % (Actual ÷ Projected) measures whether the practice delivers what it identifies; Open / Suggested / Applied recommendation counts measure adoption rate; variance trend measures forecasting and budgeting accuracy, all three are recognized indicators of FinOps practice maturity |
| Data-maturity indicators | Tag coverage (56 tags under 28 keys, with an explicit Unknown bucket), All Tags standardization review, and collector registration completeness are measurable proxies for allocation maturity |
| Maturity progression model | The four-phase implementation roadmap (Foundation → Analysis → Optimization → Continuous Management) with named success factors provides a structured maturity path, and Phase 4’s quarterly optimization reviews establish a recurring assessment cadence |
| Standards alignment as a maturity signal | FOCUS Export demonstrates conformance to a FinOps Foundation open standard |
Personas served
FinOps Practitioner (self-assessment and improvement targeting), Leadership (portfolio position and trajectory).
4.7 Intersecting Disciplines
Capability: Coordinate activities between FinOps and interconnected disciplines and Allied Personas, ITAM, ITFM, Sustainability, Security, and others.
How VisualOne enables this
VisualOne is a hybrid-estate platform rather than a cloud-only cost tool, storage, virtualization, backup, networking, databases, Kubernetes, cloud, and security all sit in one navigation tree over one normalized dataset, so FinOps and its allied disciplines work from the same numbers.
Intersections
| Discipline | Intersection |
|---|---|
| ITAM (IT Asset Management) | Full asset lifecycle in-product: Purchase Date, Retired Date, Array Life, Life of Asset, device status (Active/Retired), Model, Serial Number, Vendor, Firmware version, Data Center, Classification, Tier. Documented use case: create asset record at purchase → track in Financial Administration Report → monitor approach to retirement → plan replacement before end-of-life → document asset retirement |
| ITFM (IT Financial Management) | Financial Administration Report and Amortization Report deliver capital cost, total acquisition cost, depreciation (daily and annual straight-line), maintenance, and operating cost, with the documented workflow producing a fixed asset schedule reconciled to the general ledger and archived for external audit |
| ITSM / Incident Management | ServiceNow integration, per-alert dropdown creating or linking incident tickets from Health Alerts (storage and virtual); ticket integration fields also present on the Orphaned VMDKs screen, enabling immediate ticket entry based on specific alerts identified in VSI |
| Change Management | Control points: validate orphaned VMDKs against change records and retention policies before deletion; coordinate right-sizing with change management windows and application owners; validate outcomes at the next collection via Delta Report and VM Summary |
| Security & Compliance | A top-level Security navigation section; SOC 2 Type II certification (2024 audit); SSO and passwordless authentication; encryption in transit and at rest; least-privilege read-only collector permissions; SSH-key auth; documented data retention and deletion policy; PII elimination in reporting |
| Capacity & Performance Management | IOPS, latency, throughput, SPM growth, dual-axis performance trending, SLA verification workflow, Pool and Device Capacity Plans with a dedicated Performance mode planning in IOPS and bandwidth |
| Data Protection / Backup | A top-level Backup section plus backup-platform collectors (Veeam, Commvault, Cohesity/Helios, Avamar, Data Domain, StoreOnce, Rubrik), bringing protection estate cost and capacity into the same FinOps dataset |
| Platform Engineering / Kubernetes | A top-level Kubernetes section; OPENSHIFT_DEVICE collector; a Kubernetes tag key in the tag catalog; and a Kubernetes-native optimization recommendation (Vertical Pod Autoscaler recommendation mode for right-sizing resource requests and limits) |
| Database and Network operations | Top-level Databases and Switches sections in the navigation, extending the shared dataset to those teams |
| Third-party FinOps tooling | CLOUDABILITY and RIGHT_SIZE collector types ingest data from adjacent FinOps tools; FOCUS Export provides standards-based outbound interchange so VisualOne data can flow into other tools in the ecosystem |
| External systems generally | Foreign Tag Key mapping is purpose-built for reconciliation with cloud provider tagging systems, external billing systems, IT service management platforms, and custom organizational systems |
| Sustainability | Power cost and floor-space cost (inclusive of cooling and power distribution) per device provide the physical-resource inputs a sustainability function draws on, alongside lifecycle, refresh, and consolidation data |
| Procurement | TCO per TiB comparison across competing products, payback period, and ROI, with the documented outcome of data-driven procurement and optimized equipment selection |
Personas served
FinOps Practitioner as the connective role, with Allied Personas across ITAM, ITFM, ITSM, Security, Capacity and Performance, Data Protection, Platform Engineering, Sustainability, and Procurement all working from the shared dataset.
Section summary
| Capability | Primary supporting surfaces |
|---|---|
| FinOps Practice Operations | Four-phase roadmap, named success factors, eleven documented workflows, multi-tenant Change Client, saved views and named models, email distribution, in-product work states |
| Executive Strategy Alignment | Executive Reports section, Overall Efficiency gauge, Total roll-up, Cost YTD and Cost Per Sector, savings-weighted opportunity view, TCO / ROI / payback, chargeback accountability |
| FinOps Education & Enablement | Versioned user guide, glossary and metrics reference, published formulas with worked examples, workflow library, in-product helper text, onboarding setup call, FAQ, FOCUS standards literacy |
| Governance, Policy & Risk | Tag governance (All Tags, Key Mapping, documented workflow), cost governance with >10% variance policy and escalation, GL-reconciled compliance reporting, SOC 2 Type II, SSO and passwordless auth, encryption, least privilege, retention policy, ServiceNow escalation |
| Invoicing & Chargeback | Chargeback Report with selectable dimensions, three allocation models, 50/50 compute split, FOCUS Allocated* fields, resource-level bill backup, invoicing workflow, GL reconciliation, FOCUS and CSV export |
| FinOps Assessment | Repeatable 0-100 asset scoring with four tiers and portfolio gauge, longitudinal comparison, Savings Realization %, adoption rate, variance accuracy, phased maturity roadmap |
| Intersecting Disciplines | Hybrid estate in one platform (Storage, Virtual, Backup, Switches, Databases, Cloud, Security, Kubernetes), ITAM/ITFM asset and depreciation ledger, ServiceNow ITSM integration, change-management controls, SOC 2 and SSO security posture, Cloudability and Right Size ingestion, FOCUS interchange, Foreign Tag mapping |