This HTML guide consolidates the attached UMS Collection Process document with the earlier Collection → Mediation → EMS → Extraction explanation for interview and project documentation.
UMSCollectionMediationEMSMMPExtractionACEMetraTechIVR| Term | Purpose |
|---|---|
| UMS | Usage Management System that manages collection, mediation and extraction of usage. |
| ACE | Central InterCall database containing critical information for clients, products, reservations, company, account and owner. |
| Reference Database | Master/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. |
| MetraNet | Billing destination referenced by feature and extraction processing in the source document. |
The source document states that Collection inserts usage into three categories of tables.
| Table Type | Purpose | Example |
|---|---|---|
| Collected Tables | Store raw usage for each product. | ums_ivr_usage_part |
| Normalized Tables | Store normalized records used throughout mediation and extraction. | Session Control, Header, Participant, Feature |
| Optional Tables | Store event/error and collection audit information. | ems_case_rcd, ums_file_collection_log |
ums_ivr_usage_part.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.
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 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 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.
ems_case_rcdums_session_id.ums_file_collection_logEvery file-based collection job creates one log entry. The status identifies whether the job completed successfully, processed an empty file or encountered an error.
The operational pages in the attached document illustrate Local Fetch using the UMS environment, an SFTP client, CDR files and the UMS Web UI.
The source document defines date behavior specifically for Remote Fetch.
| Input | Behavior |
|---|---|
| Specified collection date | Fetch usage for that exact date. |
| No date supplied | Generally collect T-1 day usage. |
| Blank / Empty date | Read the last collected date from the database and fetch usage from that date onward. |
EMS is connected to event and error processing through the EMS Case Record.
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.
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.
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.
| Area | Remember |
|---|---|
| UMS | Usage Management System / Mediation Management System. |
| Collection | Fetch raw usage from bridges, databases and files. |
| Collected Tables | Store raw product usage. |
| Normalized Tables | Session Control, Header, Participant and Feature records. |
| Optional Tables | EMS Case and File Collection Log. |
| IVR | Separate bridge with Local Fetch and Remote Fetch. |
| Remote Fetch | Specified date, T-1 default or last collected date recovery. |
| Mediation | Process normalized usage for the billing lifecycle. |
| EMS | Auditable event and error processing. |
| Extraction | Prepare processed usage for MT / MetraTech billing. |