Know who consumes your storage, what it costs and where usage is heading.
NASLORD Chargeback & Showback Manager attaches every gibibyte and every API call in your Dell PowerScale and ObjectScale environments to a tenant, a budget and a forecast — then alerts the owners before the overrun, not after.
From the monthly spreadsheet to continuous accountability
Every terabyte has an owner
Consumption is attached to the tenants, departments or services you define. No more “orphaned” storage that nobody claims and IT silently absorbs.
Overruns are visible before, not after
Monthly and annual forecasts project each budget’s trend. Thresholds trigger alerts while there is still time to act.
Reports deliver themselves
Financial and consumption reports are scheduled and sent automatically to IT, finance and internal clients — in each recipient’s format and cadence.
PowerScale and ObjectScale, in the same financial view
File and object rarely converge in reporting — each platform has its own units, counters and tools. NASLORD reconciles them into a single cost model.
-
Dell PowerScale Chargeback per cluster, access zone and directory: capacity, file counts and quotas, with per-component chargeback profiles.
-
Dell ObjectScale Chargeback per virtual data centre (VDC), namespace and bucket: capacity, object counts and API consumption.
-
Consolidated views Dashboards and reports across the whole estate, whatever the number of clusters and VDCs — a single tenant can span both platforms.
| Component | Platform | Quantity | Rate | Cost |
|---|---|---|---|---|
| /ifs/imaging (capacity) | PowerScale | 338 TiB | $28/TiB | $9,464 |
| pacs-archive (capacity) | ObjectScale | 92 TiB | $19/TiB | $1,748 |
| pacs-archive (API requests) | ObjectScale | 14.2 M | $0.04/10k | $57 |
| pacs-archive (egress) | ObjectScale | 28.4 TiB | $2/TiB | $57 |
| Snapshots (capacity) | PowerScale | 41 TiB | $14/TiB | $574 |
| Month total | $11,900 | |||
The budget cycle, from definition to alert
Define
Global or per-component budget, per tenant, department or service — monthly or annual.
Track
Actual consumption accrues daily against the budget, with complete history.
Forecast
The trend projects month-end and year-end: actual + forecast on the same chart.
Alert
Configured thresholds notify the owners by email before the overrun.
Flexible chargeback profiles
Each tenant, access zone, namespace or bucket can carry its own chargeback profile. Different rates per component, per platform or per client — as useful for an internal IT service as for a managed service provider.
- Rates by capacity, file or object counts and API consumption
- Association by cluster, access zone, VDC, namespace or bucket
- Configurable currency and units (GiB, TiB, PiB)
Exports for finance and operations
Data flows cleanly into your existing processes: accounting reconciliation, internal rebilling, capacity reviews or integration with an analytics tool.
- PDF, XML and JSON exports of every view and every report
- Scheduled email delivery to each tenant’s recipients
- History retained for trend analysis and audits
The metering dimensions, in detail
The full mechanics, folded away so they don’t dominate the page — expand what concerns you.
Capacity billed in GiB-days
Capacity is measured daily and aggregated into gibibyte-days (GiB-days): a tenant that consumes 100 GiB for 15 days pays half as much as one that consumes it all month. Billing reflects actual usage over time, not an arbitrary month-end snapshot.
Write and delete requests (PUT, POST, DELETE)
On ObjectScale, write operations — object creation, replacement and deletion — are counted separately from reads. They can be priced per block (for example, per 10,000 requests) in the chargeback profile.
Ingress and egress traffic
Ingress (data written to the platform) and egress (data read from the platform) are measured per namespace and per bucket, and priced independently — the familiar cloud-provider model, applied to your private storage.
File and object counts
File counts (PowerScale) and object counts (ObjectScale) are tracked per directory, namespace and bucket. Useful for spotting millions-of-small-files workloads whose operational cost exceeds their raw capacity.
Collection frequency and retention
Collection runs on a configurable schedule (typically daily) via the built-in scheduler. History is retained in the appliance’s local database for trend analysis, budget snapshots and audits.
See NASLORD using your own Dell environment.
Deployed in your environment in about two hours. Measured with your data, your tenants and your budgets — for 90 days, at no cost.