OSS · IM System Service Fulfillment – Inventory Management
Architecture

Architecture & Data Flow

How the IM system fits into the OSS stack and how data moves through it

OSS Component Overview

The Service Fulfillment solution is composed of three systems that work in sequence for every subscriber action:

CRM
Customer Portal / Self-Care
→
OM
Order Management
→
IM
Inventory Management
→
AM
Activation Management
→
Matrix / eMatrix
NMS (Network Mgmt System)

Full service fulfillment chain — CRM → OM → IM → AM → Network

CRM

Customer order intake. Customer changes go from Self-Care or call center into CRM.

OM

Receives orders from CRM, orchestrates fulfillment, sends work orders to IM via SOAP.

IM

Stores service and resource inventory. Registers subscriber services. Syncs resource data from Matrix/eMatrix.

Work Order Flow (OM → IM)

The primary data path into IM is a SOAP call from OM. Here is the step-by-step flow for a new subscriber installation:

  1. 1
    CRM receives customer order
    Customer orders a new ADSL/VDSL/FTTH connection via Self-Care or call center.
  2. 2
    OM creates a work order
    OM processes the CRM order and generates a work order (WO) with all service parameters.
  3. 3
    OM sends SOAP request to IM
    OM calls EgyptWorkSheetAll SOAP endpoint on IM with full order payload (flowId, popid, bussInfo block).
  4. 4
    IM validates and stores
    IM parses the XML payload, creates a task form record, and populates IM_HOME_CUSTOMER and IM_HOME_SERVICE tables.
  5. 5
    IM maps CFS → RFS
    IM automatically classifies all parameters into Customer Facing Service (CFS) and Resource Facing Service (RFS) categories.
  6. 6
    IM responds to OM
    IM returns an XML response with returnCode=0 (success) or an error code.
  7. 7
    Resource sync (background)
    IM periodically syncs physical resource data (DSLAMs, ONTs, ports) from Matrix/eMatrix.

External Integration Points

OM (Order Management)

Inbound
SOAP/XML over HTTP

OM is the only source of work orders for IM. IM does not accept WOs from any other system.

Matrix / eMatrix

Bidirectional
Proprietary sync

IM periodically synchronizes zone, sector, exchange, and CPE data from Matrix/eMatrix. This is a background process configured in IM ISD.

Active Directory (LDAP)

Inbound (auth)
LDAPs

IM supports two authentication modes: local DB or AD. AD authentication verifies passwords via LDAPs but users must still exist in IM's local DB.

Resource Synchronization

ℹ

Background sync from Matrix/eMatrix

IM pulls resource data (zones, sectors, exchanges, ONTs) from Matrix/eMatrix on a scheduled basis. This keeps the IM resource inventory up-to-date without manual data entry.
⚠

Resource import fallback

For historical Matrix/eMatrix data, IM provides XLSX import templates. This is a one-time manual process performed by the IT administrator during initial deployment.
📝

Retrial mechanism

IM supports a configurable retrial mechanism per integration point (number of retries and interval between retries). This is configured via background config files — one per interface.

Data Classification: CFS vs RFS

IM automatically classifies all order parameters into two categories when a work order arrives. This is a background operation — no configuration required:

CFS — Customer Facing Service

Customer-visible service attributes:

  • •CustomerName, CustomerCode
  • •AccountNumber
  • •UserName (PPPoE)
  • •ServiceType, ServiceName
  • •CustomerPhone, CustomerEmail
  • •CustomerSegment

RFS — Resource Facing Service

Network/resource technical parameters:

  • •ExchangeID, DSLAM, DslamIP
  • •FrameNumber, SlotNumber, PortNumber
  • •OLTName, VLAN, ONT SN
  • •WANIP, LANIP, SubnetMask
  • •Speed (e.g. 30720/15)
  • •CompoundId, CardNumber