UMS Collection Process – Updated Technical Guide

This HTML guide consolidates the attached UMS Collection Process document with the earlier Collection → Mediation → EMS → Extraction explanation for interview and project documentation.

UMSCollectionMediationEMSMMPExtractionACEMetraTechIVR

Contents

  1. UMS Overview
  2. UMS Architecture
  3. Collection Phase
  4. Collection Sources
  5. Collected, Normalized & Optional Tables
  6. Normalized Records
  7. Optional Tables
  8. IVR Collection
  9. Local Fetch
  10. Remote Fetch
  11. Mediation
  12. EMS
  13. Extraction & Billing
  14. Operational Validation
  15. Interview Explanation

1. UMS Overview & Terminology

UMS = Usage Management System, also called Mediation Management System. According to the attached document, UMS collects raw usage from bridges, databases and files, processes that usage and sends it to billing through MT / MetraTech.
TermPurpose
UMSUsage Management System that manages collection, mediation and extraction of usage.
ACECentral InterCall database containing critical information for clients, products, reservations, company, account and owner.
Reference DatabaseMaster/reference database for clients, products, reservations, company, account and owner data.
MetraTech (MT)Billing platform through which usage is billed and billing reports are generated.
MetraNetBilling destination referenced by feature and extraction processing in the source document.

2. Overall UMS Architecture

Collection
→
Mediation
→
EMS
→
MMP
→
Extraction
Web UI
+
Post Processing
The attached document shows Collection, Mediation, EMS, MMP, Extraction, Web UI and Post Processing as the broader UMS ecosystem.

3. Collection Phase

Definition: Collection is the mechanism or process to fetch raw usage from bridges, databases or files. It is the entry point into the UMS processing pipeline.

Main Responsibilities

Bridges
Databases
Files
↓
Collection Process
→
Collected Tables
→
Normalized Tables
→
Mediation
Optional EMS Case
Optional File Collection Log

4. Collection Sources

File CollectionUsage is collected from source files. Every file collection job is audited through the file collection log.
Database CollectionUsage is fetched directly from source databases and inserted into the UMS collection flow.
Bridge CollectionConference bridge usage is collected as raw usage. The attached document illustrates IVR as a bridge source.
Project IntegrationsThe earlier project explanation included Adobe and Webex web services plus CCASP REST APIs as project-specific collection adapters. Keep these as integrations you actually worked with.

5. Collected, Normalized & Optional Tables

The source document states that Collection inserts usage into three categories of tables.

Table TypePurposeExample
Collected TablesStore raw usage for each product.ums_ivr_usage_part
Normalized TablesStore normalized records used throughout mediation and extraction.Session Control, Header, Participant, Feature
Optional TablesStore event/error and collection audit information.ems_case_rcd, ums_file_collection_log
For every product, raw usage is saved into an associated product collected table. The document specifically gives IVR usage stored in ums_ivr_usage_part.

6. Normalized Records

Session Control Record

The Session Control Record controls the mediation process for a conference or standalone feature from collection through extraction for billing. The source highlights Status Flag, Conference Event Type, Conference Event Code and Supersede Flag as the fields that indicate processing state.

Conference Header Record

The Conference Header contains information common to all participant legs and conference features within a conference. It is created when a collected event contains multiple participant records. If required, the source describes creating a header using ACE reservation information.

Participant Record

Participant Records represent individual user usage within a conference or event. Usage duration based on start and end time is important for billing. Since several service types use this format, not every field is populated for every record.

Feature Record

Feature Records represent non-recurring charges that flow through mediation before billing. The source distinguishes conference feature records associated with reserved conferences and owner feature records associated with an owner number. Both use the common ums_feature structure and are identified by record_type.

7. Optional Tables

EMS Case Record – ems_case_rcd

File Collection Log – ums_file_collection_log

Every file-based collection job creates one log entry. The status identifies whether the job completed successfully, processed an empty file or encountered an error.

8. IVR Collection

IVR = Interactive Voice Response History. The document describes IVR as a separate bridge (bridge type ID 4) used for Operator Assisted and Automated calls involving Spectel and Compunetix bridges.
IVR
→
Collection
→
Collected + Normalized
Transformation
→
Validation
→
Mediation
→
EMS
Usage Ready for Billing?
Yes →
Extraction
→
MetraNet Tables

9. Local Fetch

The operational pages in the attached document illustrate Local Fetch using the UMS environment, an SFTP client, CDR files and the UMS Web UI.

Configured Trigger
→
Connect to SFTP
→
Browse CDR Files
→
Launch IVR Collection Job
↓
Collection Completed
→
Launch IVR Mediation Job
→
Verify Session Control Counts
Operational interview explanation: “For IVR Local Fetch, we connected to the configured SFTP location, collected the CDR files, launched the IVR Collection Job through the UMS Web UI, launched the Mediation Job and finally validated the resulting Session Control status and event counts using database queries.”

10. Remote Fetch

The source document defines date behavior specifically for Remote Fetch.

InputBehavior
Specified collection dateFetch usage for that exact date.
No date suppliedGenerally collect T-1 day usage.
Blank / Empty dateRead the last collected date from the database and fetch usage from that date onward.
Important: This date-selection logic applies only to Remote Fetch according to the attached document.

11. Mediation

The source establishes that normalized records are used by mediation to control the conference lifecycle from collection through extraction for billing.

12. EMS – Event Management System

EMS is connected to event and error processing through the EMS Case Record.

13. Extraction & Billing

Normalized Usage
→
Mediation
→
Extraction
→
MT / Billing Tables

Extraction prepares processed usage for billing. The source references billing through MT / MetraTech and also describes feature records being extracted into appropriate MetraNet billing tables.

14. Operational Validation & Controlled Cleanup

Validation

The document demonstrates validating processed data by grouping Session Control records using fields such as status_flag, conf_event_code, conf_event_type, source and partition date. This helps verify the processing distribution after Collection and Mediation.

Cleanup

The last page contains operational DELETE statements for IVR-related usage, feature/session records, EMS cases and file collection logs before controlled reprocessing. In documentation and interviews, present this as a controlled test/support cleanup procedure rather than a general production operation.

15. Updated 2–3 Minute Interview Explanation

Project Explanation

I worked on a Usage Management System called UMS, also known as Mediation Management System. Its purpose was to collect raw conference usage from different sources such as bridges, databases and files, process that usage through mediation, manage event and error cases through EMS and finally send the processed usage to the billing platform.

The Collection phase was the entry point. It collected raw usage from file-based sources, database sources and conferencing bridges. In my project, external integrations also included Adobe and Webex web services and CCASP REST services. The collected raw usage was stored in product-specific collected tables, and normalized records were created for downstream processing.

The normalized layer contained Session Control, Conference Header, Participant and Feature records. Session Control controlled the lifecycle from collection through extraction, Conference Header represented common conference information, Participant represented individual usage legs and Feature records handled non-recurring charges.

For file collection, every job was tracked in the file collection log. If a processing event or error occurred, EMS created an EMS Case Record and preserved the complete audit history by allowing multiple cases for the same UMS session.

The IVR flow supported Local Fetch and Remote Fetch. Local Fetch operationally connected to the configured SFTP location, collected CDR files and launched Collection and Mediation jobs through the UMS Web UI. Remote Fetch supported explicit dates, default T-1 collection and blank-date recovery using the last collected date stored in the database.

Finally, Extraction prepared processed usage for billing through MT / MetraTech. In simple terms: Collection acquires raw usage, Mediation processes normalized usage, EMS manages event/error cases and Extraction delivers billing-ready usage.

16. Quick Revision Sheet

AreaRemember
UMSUsage Management System / Mediation Management System.
CollectionFetch raw usage from bridges, databases and files.
Collected TablesStore raw product usage.
Normalized TablesSession Control, Header, Participant and Feature records.
Optional TablesEMS Case and File Collection Log.
IVRSeparate bridge with Local Fetch and Remote Fetch.
Remote FetchSpecified date, T-1 default or last collected date recovery.
MediationProcess normalized usage for the billing lifecycle.
EMSAuditable event and error processing.
ExtractionPrepare processed usage for MT / MetraTech billing.