An operation or group of operations of a particular type (grooming, rehoming, insert node, or remove node) that is managed as part of a project. You configure each activity individually using tools that are specific to its type.
A type of place entity that defines a location or site using textual information. You define specifications for Address entities to conform to business and national postal requirements. For example, in North America, an Address entity could include characteristics for street address, city, state or province, country, and postal code.
See also address range, location, site.
A type of entity that defines a group of addresses expressed as a range between values, such as a low street number and high street number. You can associate an address range to resources or services that serve multiple addresses.
A general term for something you can define in Design Studio, such as a specification, characteristic, or ruleset.
See facility.
A common business entity that represents an arrangement such as service fulfillment, a capital project, or other activity that you want to plan in advance. Business interactions make it possible for you to plan UIM actions and then execute those actions at a time of your choosing.
In UIM, capacity refers to the amount and type of something that entities require or provide. By default, bandwidth is the only capacity supported, but you can extend UIM to define various types of capacity and how they are measured.
A collection of entities and data defined in Design Studio and packaged in an archive file for deployment to a run-time server. In Design Studio, you build cartridges in cartridge projects. You can create your own custom cartridges to extend Oracle Communications applications. Additionally, you can obtain customized cartridges from Oracle that support integration with other common applications and support specific technology domains.
See also Design Studio.
A type of connectivity entity that represents channelized (multiplexed) connectivity. TDM and WDWM facilities are represented by Channelized Connectivity entities. Based on the rate code associated with the channelized connectivity, the UIM signal architecture determines how the connectivity can be multiplexed down to lower-rate channels. Channelized connectivity is one of three Connectivity entity types supported by UIM.
See also packet connectivity and service connectivity.
A data element that can be added to entity specifications to supplement default data elements. For example, a Physical Device specification may have a characteristic for the device serial number. In Design Studio, you define characteristics by defining new data elements and tagging those elements as characteristics. In UIM, characteristics are displayed as fields, such as text fields, lists, and check boxes.
A UIM entity that describes a business process or a relationship among entities. Unlike a resource, a common business entity does not represent an item in your inventory. Examples of common business entities include business interactions and inventory groups.
A hierarchically organized collection of facts about a parent entity. Configurations can versioned so that these facts can be managed as they evolve over time. Configurations are defined by specifications.
Service, Place, Network, Pipe, and Logical Device entities can have configurations. For example, a Service entity can have a configuration that stores facts, such as resource consumption, that describe how the service is realized.
See also configuration item.
An element of an entity configuration that specifies a particular fact, such as resource assignment or reference. Configuration items can also include characteristics that enable you to capture details. To organize configuration items and put them in context, you can arrange them in a hierarchy.
In a general sense, the ability to transfer information to and from devices and locations.
A UIM entity type that represents connectivity. Connectivity entities are similar to and derived from pipes, but have different data elements and behaviors.UIM supports three types of connectivity entities: channelized connectivity, packet connectivity, and service connectivity.
A designation that describes the purpose or role that a connectivity performs.
A segment in an end-to-end trail for which connectivity details are unknown.
A connectivity gap can be acceptable in cases where a third party provides transport, the details of which are unimportant, or when the trail passes through a network where ingress and egress are known, but transport details are unknown.An unacceptable connectivity gap is one that has no business validity, such as when the design of a trail is incomplete.
A type of entity relationship in which one entity is limited by another. For example, a constrains relationship results from associating a Network Node specification to a Logical Device specification. This relationship limits the types of entities that a network node can represent in UIM.
The UIM component that provides the architectural framework and common services, such as APIs and data storage. It also supplies functionality, such as search, that is used throughout the application. The core platform is required and is supplied with the purchase of any Functional Module.
A logical interconnection between two device interfaces that provides continuity in an end-to-end connectivity trail. Cross-connects can be interface-bound or trail-bound.
A UIM entity that defines a connection or dependency between other entities. You can assign roles to the entities participating in the custom involvement.
A network address is a name, label, or number that identifies a location in storage or a device in a network. UIM includes entity types for telephone numbers. logical device accounts, and IP addresses. You model other types of network addresses, such as Autonomous System Numbers (ASNs) or VPN IDs as custom network addresses.
A UIM entity that represents an inventory item that does not fall into any of the predefined entity types. Using custom objects enables you to model such items without having to modify the data model.
A logical collection of and data types in a Design Studio workspace that enables you to leverage common definitions across an entire Oracle Communications solution. The Data Dictionary enables you to share data defined for order templates, atomic actions, and service specifications between OSM, ASAP, and UIM.
A structured or simple type data definition created in Design Studio. When modeling data for a project, you create data elements that you can reuse throughout your model. There are two types of data elements: simple data elements and structured data elements. Data elements can be included in a specification.
See also characteristic.
The Oracle Communications service creation environment. Modelers and developers use Design Studio to define specifications, rulesets, and other artifacts that define how inventory is modeled in UIM. Design Studio is a separate application from UIM and is used by other Oracle Communications applications. See UIM Concepts and Design Studio Help for more information.
A UIM entity that represents where communications begins or ends on a logical device. You can map physical connectors to device interfaces to ensure that you have addressable network elements in your inventory of physical equipment. Device interfaces are UIM entities, but they cannot exist outside the context of a logical device.
A relationship between entities in which a resource such as a pipe realizes or supports a service or other resource. For example, a cable pair can enable the local loop for a POTS service. You can define pipe enablement manually or automatically by using path analysis.
A specialized kind of business interaction used to manage resource changes that involve channelized connectivity and logical devices.
A UIM database object that represents an item or relationship in your inventory. Entities can represent physical or logical resources, such as equipment and telephone numbers. They can also represent business processes or organizational tools such as business interactions or resource reservations. Most entities are based on specifications that are defined in Design Studio.
See also entity reference, specification.
A relationship that reflects a connection or interest between a configuration and an entity. An entity reference is similar to an assignment or allocation relationship except that the referenced entity is not consumed.
A group of entities based on technology or function. Entity types include Logical Device, Service, Network, Telephone Number, and so on. Entities of the same type share many features, such as search criteria and page layout.
Specifications are based on entity type. When you define a specification, you start with the entity type and then embellish it with additional data.
See also entity, specification.
A UIM entity that represents a physical unit such as a rack, shelf, circuit card, field-replaceable unit (FRU), or handheld phone. Equipment entities are one of several kinds of entities used to model hardware in UIM.
See also equipment holder, physical device, physical port, physical connector.
A UIM entity that represents a slot or mounting position that can contain cards or similar items. Unlike most other entities, equipment holders cannot exist independently. They are provided by Equipment entities and can contain Equipment entities. For example, a shelf is an Equipment entity that provides an equipment holder that in turn can contain a LAN card, another Equipment entity.
See also equipment, physical connector, physical port.
An artifact that you define in Design Studio that specifies a place where a ruleset is executed in UIM. A standard extension point is limited to a particular specification. You associate an extension point with a ruleset in a ruleset extension point.
See also global extension point.
A connectivity (pipe or channelized connectivity) that provides bandwidth capacity to other connectivities. Facilities are sometimes called bearers.
A UIM entity that represents identifiers such as VLAN IDs or Tags for Ethernet, VPIA and VCI for ATM, DLCI for Frame Relay, and VPLS IDs for MPLS. Used with flow interfaces to track traffic flow through networks.
A point in a network through which traffic flows. Flow interfaces are used with flow identifiers such as VLAN IDs to allow for stacking and translation.A flow interface always has a device interface parent.
A separately licensed UIM component that manages the end-to-end life cycle of entities in a specific area, such as connectivity, geographic addresses, and network modeling. You can purchase only the modules required for your business.
See also core platform.
An extension point that can be applied to any specification. In contrast, a standard extension point applies only to a particular specification.
The process of re-routing traffic or capacity from one route to another route between two end points. Grooming is usually done to optimize traffic or in response to network infrastructure changes. In UIM, you perform grooming as an activity in a project.
A resource form of network that is typically backbone in nature. Examples include Ethernet, MPLS, SDH, SONET, ATM, and Frame Relay.
A UIM common business entity that enables you to organize and correlate entities in your inventory. For example, you can use inventory groups to group telephone numbers based on the locations to which they are assigned. You can use rulesets to define behaviors associated with the entities in an inventory group.
Refers to an interconnection (physical jumper or cross-connect) whose existence is dependent on the lifecycle of a device interface to which it is assigned.
See also trail-bound.
A type of place entity that models a spot or area that can be defined by geographic coordinates. A location can be a specific place such as a residence or office. A location can also represent a geopolitical area such as a city, state, or country.
See also address, address range, site.
An entity that represents a collection of physical or logical resources that act together to perform a function in the network. Using Logical Device entities to model your inventory enables you create addressable network elements that can be managed with activation applications.You can associate physical devices to logical devices.
See also device interface, physical device.
An entity that represents accounts that are typically hosted or managed by a logical device. Examples include voice mail accounts, email accounts, and server logins. Logical device accounts are usually associated to logical devices, but can exist independently.
A group of related units of measure. For example, the bit rate measurement type includes units of measure such as bits per second (bps), kilobits per second (kbps), and so on.
A device interface that represents a physical interface or port that can host a physical connection. A device interface can be a media interface only when it is the root interface in its device interface hierarchy.
A UIM entity that represents a collection of other entities that have a common meaning or purpose. The entities in a network can be physical or logical resources, such as equipment or logical devices, or they can be non-resources, such as parties or places. A network can also include another network.
There are three network types: infrastructure network, service network, and virtual network.
See also network edge, network node.
A UIM entity that represents reachability or connectivity between nodes in a network. You can associate network edges with pipe entities to specify how that connectivity is realized.
See also network, network node.
A string that uniquely identifies a network entity (such as a logical device) within a network location. The network entity code is always displayed together with the network location code of its location. For example, the network entity code K01 is shown as PLANTXXA,K01 if it is owned by location PLANTXXA.
A property location that has been assigned a network location code.
An alphanumeric string that uniquely identifies a property location in a network. When you assign a network location code to a property location, it becomes a network location.
A UIM entity that represents a specific logical spot in a network. You can associate network nodes with other entities, such as logical devices, equipment, places, and parties.
See also network, network edge.
A type of role that identifies a logical device or party entity as a target for activation systems.
The Oracle application server for deploying enterprise Java EE applications. WebLogic Server hosts UIM.
A type of connectivity in which data is transmitted in packets. Packet technologies include Ethernet, Frame Relay, and ATM. Packet is one of the three types of Connectivity entity supported by UIM.
See also channelized connectivity and service connectivity.
A collection of the interfaces and connectivities that support a service based on packet technology. A packet virtual network can include , , , other packet virtual networks, packet connectivity, and . Multipoint EVCs are examples of packet virtual networks.
An area of the UIM user interface in which you perform tasks such as searching for entities. Pages can be divided into one or more sections.
A relationship in which an entity (the parent) is superior to one or more other entities (the children). Many entity types can participate in hierarchies in which they be a parent, a child, or both.
A UIM entity that represents a person or organization that interacts with your inventory.
See also role.
A UIM feature for automatic enablement of pipes based on criteria that you enter. Path analysis finds the most efficient routes or paths through connectivity in a network and provides enablement options.
See also enables relationship.
A UIM entity that represents an item that connects hardware units for signal or power transmission. Unlike most other entities, physical connectors cannot exist independently. They exist only in the context of a Physical Device or Equipment entity.
See also equipment, equipment holder, physical port, physical device.
A UIM entity that represents a group of physical hardware items; the physical equivalent of a logical device.
See also equipment.
A UIM entity that represents where communication begins or ends on a Physical Device or Equipment entity. Unlike most other entities, physical port cannot exist independently. They exist only in the context of a Physical Device or Equipment entity.
See also equipment, equipment holder, physical connector, physical device.
A UIM entity that represents a connections among devices, equipment, or places in your inventory. Pipes can represent physical connectivity (such as cables, cable pairs, and jumpers) and logical connectivity (such as service trails, DS1 facilities, and OC3 facilities).
See also connectivity.
An entity representing one of the two ends of a pipe. Every pipe has two termination points that represent its ends. Signals travel over pipes from one termination point to the other. Termination points are created automatically when you create a pipe in UIM.
Termination points can be associated to various kinds of entities, such as device interfaces, logical devices, equipment, and places.
A UIM entity that defines a geographic point, area, or concept, There are four different types of Place entities: address, address range, location, and site.
A UIM entity that defines how signals can be multiplexed in some signal technologies, such as SDH and SONET.
A conceptual model entity that represents something that your business sells. Because UIM is primarily used for service fulfillment rather than sales, products are often identifiers associated with information from other systems.
A UIM Product entity also exists, but is included only for backward compatibility with previous versions. The Product entity is not visible by default.
In UIM, an entity that you use to plan and organize , such as grooming and rehoming. Projects can include any number of activities, each of which defines operations of particular type. For example, you could create a project that includes all the activities related to a particular network infrastructure change or the activities during a specified time period. This UIM entity is also called a managed project.
In Design Studio, an entity that contains artifacts (entities, data, rules, code, and so on) that you use to model and deploy .
A physical area with defined legal boundaries that enables the identification of the location of assets, customers, and services. A property location must be defined as a network location, a service location, or both.
A relationship in which one entity's existence depends on another entity. For example, a physical port is provided by a physical device because the port could not be created or exist without the physical device.
An entity that defines a technology-specific transmission rate for a connectivity or device interface to which it is assigned.
For example, the DS-1 rate code identifies a T-Carrier signal that operates at a bit rate of 1.544 Mbps.
Changing a connectivity design at an end point, such as at a device interfaces or port. In UIM, you perform rehoming as an activity in a project.
A feature of the UIM consumption pattern that makes it possible to restrict a resource from being assigned to other entities or processes for a period of time. You redeem a reservation by allocating the reserved resource to service, logical device, network, or site configuration before the reservation expires.
A type of UIM entity that represents an item in your inventory. Resources entities can represent physical objects, such as network cards and fiber-optic cables, or logical resources, such as service trails and network addresses. Resources enable the delivery of services.
In UIM, you often assign resources to service configurations to specify how a service is realized in your network. For example, if you configure a VoiP service for a customer, you need to assign resources such as an IP phone, a telephone number, an IP address, a voice mail account, and a VoIP user account.
See also common business entity.
A UIM common business entity that identifies what part another entity plays in your inventory. For example, you can associate a Party entity with a role called Customer or Vendor.
See also role type.
Optional categories to which you can assign roles. There are three role types function, technology and topology.
Java code modules that execute at particular times in UIM. For example, when you validate a service configuration, a ruleset is used to perform the validation. Some rulesets are included by default, but custom rulesets can extend UIM. See UIM Concepts and UIM Developer's Guide for detailed information.
See also extension point, global extension point, ruleset extension point.
A Design Studio artifact that brings together a ruleset and an extension point. You associate the ruleset extension point with an entity specification to customize how UIM handles entities based on the specification.
See also global extension point.
A Design Studio artifact that you use in conjunction with Entity Identification specifications to customize the way that IDs are assigned to entities. The Sequence specification defines the minimum and maximum ID values and how the values are incremented.
A UIM entity that represents the way that a product is realized and delivered to a customer. For example, if you sell DSL Gold as a product, it is delivered as a DSL Gold service, enabled by appropriate resources.
A connectivity that represents the service consumption of infrastructure resources. When modeled with pipes, this type of connectivity is called a service trail. Service connectivity is one of the three types of Connectivity entity types supported in UIM.
See also channelized connectivity and packet connectivity.
A business process in which a customer order is accepted and a new service is provisioned to meet it. UIM plays a key role in service fulfillment by managing the services and resources used to design and realize the services.
A property location that defines a place where a service is delivered or located.
A type of virtual network that consolidates all , network access connectivity, and supporting virtual networks into a single unified view of the service. Although it is tailored for the more complicated multipoint service, it can also display simplified point-to-point service.
A type of pipe entity that describes the logical flow of data in a service. You can enable the service trail to specify the resources with which it is realized.
See also enables relationship, path analysis.
A set of related signal definitions that form the multiplexing hierarchy for a signal technology. Signal technologies supported in UIM include T-Carrier, E-Carrier, J-Carrier, SONET, and SDH. In the case of SONET and SDH, the signal definitions consist of signal termination point specifications and processing signal specifications that are related in a variety of ways.
The way that a TDM pipe's signal is channelized. For example, a T3 pipe may have 28 T1 channels. You use signal termination points to define the signals.
A UIM entity used to define capacity for pipes based on the TDM model. You use hierarchies of signal termination points to define signal structures that determine how a pipe's signal is channelized.
Shared Information Data Model (SID), a standard that provides the communications industry with a common vocabulary and set of definitions for next-generation operations support system (NGOSS) architectures.
A type of place entity that models a loosely defined place such as a campus. Unlike other Place entities, a site is not necessarily bound to specific geographic coordinates. Sites are only loosely defined, so they can be associated with configurations that record facts that change over time.
See also address, address range, location.
A blueprint that defines the composition of an entity, including the attributes and relationships between an entity and other objects. There are different types of specifications for different types of entities, such as telephone numbers, networks, customer facing services, and resources. Specifications are defined in Design Studio and deployed into run-time environments, where entities can be created based on them.
The section of the left side of the UIM user interface that contains links to entity pages and other features.
A UIM entity that represents a telephone number. You can have multiple specifications that corresponds to number formats for different regions.
A relationship between the end point of a pipe (a pipe termination point), and an entity that the pipe terminates on, such as a device interface.
The spatial relationships among inventory entities in UIM. Topology supports the graphical representation (visualization) of common business entities as well as advanced features such as path analysis.
See also topology node, topology edge.
An entity that represents a relationship between topology nodes. Two types of relationships are represented as edges: connectivity and containment.
An entity that represents an object into which information can be transported or from which information can be transported. A topology node can represent a specific resource, such as a router, or it can represent something more general or geographic, such as a VPN site or a city. Topology nodes can be connected by topology edges.
The logical, end-to-end path that describes how a signal travels from one point to another. A trail is enabled to describe the resources (pipe and connectivity entities) that realize the trail.
Refers to an interconnection (physical jumper or cross-connect) whose existence is dependent on the lifecycle of the trail in which it occurs.
See also interface-bound.
A quantity or increment that defines the units used to measure capacity in UIM. For example, kbps is a unit that measures a bit rate. Related units of measure are grouped into measurement types.
A non-backbone network that relies on the existence of an infrastructure network. A virtual network's nodes and edges can represent items in an infrastructure network or virtual items such as flow interfaces.