Resource Components represent a set of SOA services which can be consumed by any system via a standardized interface like SOAP or JMS. Resource components internally communicate with Granite Inventory but also can communicate with other systems in order to provide feasibility study and service instance assignment capabilities.In general, functions of Resource Components range from identifying available resources all the way to constructing end user circuits and services. Since Resource Components provide their functionality in an access technology and service agnostic way, they add a high degree of flexibility and agility to the design of automated fulfillment solutions.

Resource Components are of following types: 

  • Feasibility study components,
  • Allocation and manipulation of Network Inventory objects,
  • Communication with external systems like GIS, customer services etc.

Feasibility study Resource Components identify appropriate specific available physical and logical resources in Network Inventory which are necessary for end customer service assignment. Resource Components are atomic provisioning adapter interface to Granite Inventory and they execute order decomposition done by GDi GEOSS Dynamic Service Catalog  Engine. They map Network Inventory objects to provide allocation and manipulation of resources and services. They also provide manipulation of Granite Inventory resources and services for GDi GEOSS Order Management.

The methods that all resource components implement:

  • Create
  • Change status
  • Delete
  • Modify
  • Load
  • Get

Some examples of available Resource Components are:

  • RoutingEngine Component – The RoutingEngine (RE) is used to find a route from the A-side to the Z-side
  • FindFreePort Component – The FindFreePort resource component is responsible for searching for free ports on equipment (on active equipment in most cases) in accordance with defined parameters.
  • FindFreeChannel Component – The FindFreeChannel resource component is responsible for searching for free channels on equipment in accordance with defined parameters.
  • Equipment Component – In the context here, equipment represents mainly customer equipment that has to be created at provisioning time.
  • Customer Component – This component is responsible for managing customer objects in the inventory.
  • Site Component – This component is responsible for managing site objects in the inventory.
  • Path Component – This component is used for managing the inventory Path object. A new path is created from a path template and the associated path elements result from the execution of other resource components like RoutingEngine, FindFreePort, Equipment etc.
  • Network Component – This component is used for managing the inventory Network. A new network is created from a network template and the associated network elements result from the execution of other resource components like RoutingEngine, FindFreePort, Equipment etc.

Although PE/RC are built around Network Inventory for provisioning purposes it is also possible to extend them for resource manipulation in other OSS relevant systems.