Reference
Our words, defined.
Where the category uses a term loosely, Riopex uses it narrowly. These are the definitions the product is built to.
- TEM
- Telecom expense management. The discipline of knowing what a group's connectivity costs, whether it was delivered, and whether it should still be paid for. Riopex is a TEM platform for groups holding several legal entities.
- HoldCo
- The group. It consolidates, compares entities against each other and holds group vendor leverage. It reports in a presentation currency and sees every operating company beneath it through one audited path.See also: OpCo · Presentation currency
- OpCo
- An operating company: a legal entity, which may trade in several countries. It is the tenancy boundary, and the only one. Everything below it is data, not isolation.See also: HoldCo · Tenant isolation · Functional currency
- Site
- A premises. It carries a cost centre, a timezone and an address, and it is a data level rather than a permission level.
- Service
- The billed and delivered thing: an MPLS port, a dedicated internet access circuit, a mobile plan, a number range. Services are the spine of the inventory; only some of them have a circuit.See also: Circuit role · Service identifier
- Service identifier
- An opaque reference for a service, stored exactly as printed alongside a case-folded, separator-stripped twin used for matching. Meaning is never parsed out of it, because identifier formats share no grammar across regions.See also: Alias
- Alias
- One of several identifiers naming the same service. The CMDB, the contract and the invoice frequently disagree about what a circuit is called, and all three names are kept.
- Circuit role
- What a circuit is for: primary, backup, DR failover, burst overflow, seasonal, test, out-of-band management, one half of a diverse pair. It defaults to unknown, and unknown blocks a waste finding exactly as firmly as backup does.See also: Waste · Gate
- Service status
- The operational axis: whether the service is actually delivering. Deliberately separate from billing status, because keeping them apart is what makes a ghost circuit representable at all.See also: Billing status · Ghost circuit
- Billing status
- The commercial axis: whether the service is still being charged for. Separate from service status, always.See also: Service status
- Ghost circuit
- A service disconnected at the site that is still on the invoice. It is one of the two things we call waste, evidenced by a disconnect acknowledgement and a recurring charge that outlived it.See also: Waste · Cease verification
- Waste
- Confirmed billing errors and cleared ghost circuits, and those two things alone. A low utilisation figure sits outside the word, because backup, DR, contractual minimums, burst headroom and seasonal capacity are all legitimately billed.See also: Circuit role · Coverage
- Coverage
- The fraction of a period that actually had data. Zero coverage means missing, never zero bits per second; a twenty-minute hour is a one-third-coverage hour. Coverage travels with every published number, and nothing is interpolated.See also: Cost per megabit delivered · Gate
- NMS
- The network monitoring system a customer already runs, such as PRTG, SolarWinds or Zabbix. Riopex reads its hourly and daily aggregates over a read-level key and leaves the system to the team that owns it.See also: Read-level key · Interface binding
- Read-level key
- The one credential Riopex asks for on a monitoring system. It is held as an opaque reference into a secrets manager and resolved at job time, so the secret itself stays in the vault.
- IF-MIB
- The standard interface counters a monitoring platform polls to produce traffic figures. Riopex reads the aggregates your platform has already computed from them, which is why one read-level key is the whole ask.
- Interface binding
- The link between a monitored interface and a service in the inventory. Automatic only on an exact identifier match; everything else opens a review item with ranked candidates. Bindings are dated, so a rebind never rewrites history.See also: Work item
- p95 hourly
- The delivered-bandwidth denominator: a percentile taken over hourly buckets, bidirectional, named for its bucket. It is explicitly not a carrier's five-minute burstable percentile, because an unqualified percentile gets disputed the first time it is quoted.See also: Cost per megabit delivered
- CIR
- Committed information rate: the capacity the contract obliges the carrier to deliver. It is the denominator of the fallback metric, the one that needs no monitoring integration at all.
- Cost per megabit delivered
- Recurring charges net of discounts, normalised to a month and converted at policy rate, divided by delivered bandwidth. The headline metric wherever coverage supports it, always published with that coverage beside it.See also: Coverage · CIR · p95 hourly
- Cost per megabit subscribed
- The same recurring charges divided by the contracted bandwidth rather than the delivered one. It works from bills and contracts alone, so it is the figure a group has before its monitoring system is connected, and it always says which of the two it is.See also: Cost per megabit delivered · CIR
- Carrier confirmation
- Sending a carrier what the group holds for it, as CSV or XLSX by email, and keeping its answers as evidence field by field. An answer sits beside the record and never overwrites it, and each carrier shows the share of its services it has confirmed.See also: Record claim · Finding
- Bundle
- A managed package a carrier prices as one charge. Riopex splits the charge to the member services, so each carries its share of the cost and none is counted twice.See also: Allocation rule · MRC
- MRC
- Monthly recurring charge. Only recurring charges and discounts enter a run rate or the numerator of a cost-per-megabit figure; usage, installation fees and taxes do not.See also: Charge class
- Charge class
- What an invoice line is: recurring, usage, one-off, discount, tax, or unclassified. Unclassified is a legal value that routes to review, because dropping an unrecognised line silently under-reports spend.
- Period direction
- Whether a line bills in advance or in arrears. Recurring charges bill forward and usage bills back, so one invoice spans two windows and each line carries its own service period.
- Arithmetic gate
- The check that an invoice's lines sum to its total in minor units, and that its tax lines sum to its declared tax. A mismatch opens a review item rather than passing quietly downstream.
- Minor units
- How money is stored: an integer count of the currency's smallest unit plus an ISO-4217 code, with the exponent read from a currency table. Never a float. Several currencies we handle have three decimals, not two.See also: FX rate id
- Transaction currency
- The currency the carrier actually billed in. Immutable once recorded, because it is the statutory fact.See also: Functional currency · Presentation currency
- Functional currency
- The currency an operating company keeps its books in, under IAS 21. A property of the entity, not a display preference on a report.See also: OpCo
- Presentation currency
- The currency the group consolidates and reports in. The third of three layers held on every money figure.See also: HoldCo
- FX rate id
- The identity of the exact rate row used for a conversion, recorded on the converted figure. A converted amount that cannot name its rate is not allowed to exist.See also: Restatement
- Restatement
- A corrected exchange rate. Rates are append-only, so a restatement arrives as a new row rather than an edit. The presentation rate for a group, a month and a currency pair is frozen onto the roll-up, so a board pack already presented cannot move.
- Allocation rule
- How a charge that lands at account or section level is split across services or entities. Shares sum exactly and the remainder goes to the largest share, so amounts conserve to the minor unit. An allocation never edits the invoice line it came from.See also: Intercompany allocation
- Intercompany allocation
- A recharge between two entities in the same group. It is evidence in two ledgers, so it is readable by the sending and the receiving entity, and it stays distinguishable from a carrier charge in the same roll-up.
- Source artifact
- The immutable raw bytes of anything ingested: an invoice PDF, a portal export, a contract. Deduplicated by content hash per entity, never mutated, never deleted. Portals retain months; we retain indefinitely.
- Import batch
- One run of one file through one mapping, with a dry-run mode, per-row errors and an undo. A bad mapping found in week six is rolled back to the pre-batch state, not hand-cleaned.See also: Header fingerprint
- Header fingerprint
- The hash of a normalised header row, used together with the carrier and the entity to key a saved mapping. It is what stops two different layouts from the same carrier overwriting each other, and what makes month two of onboarding cheaper than month one.
- Record claim
- One asserted value for one field, with its source, its confidence and a pointer into the artifact it came from. Provenance is a row rather than a column, so a conflict stays visible and a correction supersedes rather than overwrites.
- Work item
- An entry in the one queue that holds every unresolved thing: an unmatched identifier, an extraction below the confidence floor, an unbound interface, a field conflict, a data gap, an approval. One inbox, because an implementation team cannot live in five.See also: Review queue
- Review queue
- Human review as a first-class surface rather than error handling. Every uncertain field is shown, with the source page and the exact location of the claim beside it.
- Data completeness
- Which facts a service still needs: role, contract, bandwidth, site, carrier account, identifier, monitoring binding and at least one invoice. It also records which analytics each gap blocks, so partial data renders a number behind a badge rather than an empty state.
- Finding
- A defensible claim about a specific service in a specific month: a ghost circuit, an over-provisioned service, a billing error, an SLA breach, a contract mismatch. It carries a snapshot of role, contract and coverage as they stood when it was reached.See also: Gate · Suppression
- Gate
- One of six conditions a finding must clear: billing history, coverage, window length, a known and eligible circuit role, contract exposure, and join confidence. Gates run in the domain layer, never in a dashboard query.
- Suppression
- A finding that failed a gate, kept with its reason rather than deleted. An unknown role or insufficient coverage becomes a data-quality task that improves onboarding instead of a false positive that costs credibility.
- MACD
- Moves, adds, changes and disconnects. In Riopex the workflow is internal and ends at the carrier boundary: request, group IT review, budget check, approval, procurement, handoff, install tracking. The handoff reference and the carrier acknowledgement are kept as evidence.See also: Budget check · Cease verification
- Budget check
- The step that reprices a proposed change against a budget line in transaction, functional and presentation currency, each naming its rate id. A budget check repriced at today's rate is not a budget check.
- ETF
- Early termination fee: what ending a contract early costs. A disconnect cannot pass the budget check without one, because a cease that costs more than it saves is not a saving.
- Cease verification
- The clock armed by a completed disconnect. If the recurring charge is still on the invoice two months later, that raises its own finding with the carrier handoff reference attached.See also: Ghost circuit
- Dispute
- A challenge to a specific charge, with its own ageing clock. Billing complaints and SLA credit claims route here rather than through the change workflow.See also: Credit
- Credit
- Money returned by a carrier. It exists independently of the dispute that earned it, because a credit typically lands on a future invoice and may arrive unmatched.
- Tenant isolation
- The rule that a query can only see the operating companies its user is a member of. Enforced in the route, in the server action and again as a database row policy. Group roll-up goes through one audited function; there is no unrestricted client.See also: OpCo
- Out of term
- A service past its contract expiry, drifting to month-to-month list pricing. Always derived from the contract dates rather than stored as a flag, because a stale flag hides one of the most common overcharges.
That is the vocabulary the product is built to. Where a definition here reads narrower than the category’s, the difference is deliberate, and the pages behind each term explain why.
