RG Solutions® understands the needs for extensive information related to the IT services
processing. This information needs to take the form of two general types: Native and Common. The
native information is required by IT to perform the routine performance and provision requirements.
The common information is that information that links the IT services to the business.
|
|
Major Data Features |
|
Containers
|
A container is the lowest level of data storage within the program processing. It
can be thought of as a data record (like a database table row) that is uniquely
identified. It has several data fields that contain the values pertaining to the
container. The record is identified by a hierarchical name that allows for automatic
record summarization from child to parent levels.
|
Summary
|
Summary data is a data record (like a database table row) that is uniquely
identified and has several data fields that summarize the underlying associated
containers. There can be multiple summary records for a set of containers
depending on the processing requirements.
|
Processing
Entity
|
There are three types of processing entity: Repository, Service, and Business
Process. Each type of entry is associated with a level within the SOA architecture,
and they all have the same basic format of data storage. The Repository
information can be both a service and file server, but is generally just a file server
in the SOA framework. The processing supports a hierarchical structure that can
be used for grouping of related entities.
|
Servers
|
Servers are the main processing engine and are present in each level of the SOA
framework. The data associated with this type of processing is based on traditional
performance information and reflects the processing on the system. This
information will also include cost information.
|
Actions
|
Actions are the individual services that are provided by the IT operations. Actions
are available only for the Service and Business Process levels of the SOA
framework. The data associated with this type of processing is defined by the user
and reflects the processing (and costs) of the identified IT service.
|
Major Processing Capabilities
|
|
Collection
|
A collection is a group of related processing that forms the internal product data
from the collected performance data. The collection processing will form native
and common data containers and place them into the appropriate Data Type. The
collection also has functions and data to form other related information.
|
Data Types
|
A Data Type is a logical group of related data such as Memory, CPU, etc. It is
composed of one or more Data Sets along with all the corresponding containers.
Within the product processing, there are some “Common” Data Types that are the
same for each platform implementation and allows for comparative and merging
purposes.
|
Data Sets
|
A Data Set is a logical group of containers within a Data Type. The use of these
sets allows for the ability to have more than one group (i.e. Interval, Total, etc.) of
data within the Data Type. Generally speaking, the sum of values within one set is
equal to another set within the same Data Type.
|
Archive Data
|
At the lowest level, the processing entity is segmented to a single day. That is to
say, each file represents a single day for the entity. The program processing
allows for the archive of day information to week, month, or year values. This
provides for data consolidation and a more robust reporting environment.
|
Shared
|
The program processing fully supports the ability to share usage within the
processing. The sharing references are controlled by the user and the program
processing will use an ABC methodology to assign the shared workload. At the
Service and Business Process levels, it is possible to view the basic, shared, and
total processing for almost any entity or workload.
|