Understanding and Creating Metadata Models

Metadata & data models

Understanding metadata and data models

• 'Data Models' are a good source for extracting business, technical metadata models that
  can be then used for creating metadata structures that contain data.
• Sometimes an organization will have a source for extracting metadata and sometimes we
  will need to create data models from scratch together with our customers

Technical Metadata

E-Line Service Offering

Business Metadata

Ethernet Business Service
A service entity that is defined by business ethernet services SLA's and technical implementation requirements under a contractual SLA agreement with a CUSTOMER that is a of TYPE Business Customer.

• Technical Metadata may descibe the structure, format, technical aspects, etc.
• Business Metadata describes the business context, service associations, context, etc
• The Data represents actual value for the metadata.

The Context

• Who are the ultimate users ?
• What are the needs?
• Who are the personas?
• What will the metadata be used for?
• Which dashboards and filtering are needed?
• System be usage ? proactive or reactive?

Work together with the customer to suggest, guide and go beyond the ask. Help them understand what metadata they may need as opposed to 'ask the customer to give it to you'.

• Region metrics may be needed - Hence which regions
• In regions there may be sub areas such as MTX sites or cities
• Technical staff may want to see equipment types and technologies 2G, 3G, 4G, and 5G
• There may be different access technologies - microwave, fixed, broadbandm leased, ect.
• How about subtended links. Cell to cell microwave from the core.
• Data rate ect.

Workflow Breakdown

Ethernet Services Example

Point to Point Example

Hops are metadata. In terms just hop3 may be a link between service providers. We can have a different calue for hop3 to indicate its a provider or create a new Metadata that defines the LINK_TYPE as a METADATA tag. PM flows are always end to end.

Point to Multi-Point

A PM flow per A-Z and per CoS
This is a very common architecture for residential and business broadband/mobile backhaul services PM sessions can be grouped in Analytics to immediately understand Core vs edge impact.

Deliverable

Creating Templates

Data about Data
The Data is qualifying information and data is metric/KPI/flow/PM session ect. The model helps to identify how the data about the data fits into a particular 'context'. This is in fact turning data into information for insight/action/management/enlightenment! A TAG can be any arbitrary 'TAG name' that helps define the data set. We create tags that are meaningful to the topology, srvice, or business model.