Systems,
Releases and Items
Management tool for modeling hierarchical
processes in production environments.
SRI is a single rooted hierarchy that
extends three levels deep. This is a simple yet surprisingly powerful
structure. A SRI database is composed of one or more stored SRI
hierarchies. SRI is intended to model processes that contain dependent
elements that ultimately make up a completed unit. SRI then allows the state of
any number of processes to be tracked and stored for trending analysis and
reporting.
Key Benefits
A multi-user, portable database schema supported by any Microsoft
ADO provider.
Database objects bound to a client view. As the SRI
hierarchy is modified in a client or the database, each is synchronized to
reflect the current state of the hierarchy.
The ability to access different SRI databases from the same
client.
Item aging through three ascending threshold magnitudes.
Each element in the hierarchy can be assigned an individual threshold
model. Each threshold can have different ranges assigned before breaching
adjacent thresholds.
Hierarchy security varying by Owner and Admin roles.
A user configurable, built-in reporting engine.
The ability to export the data to external formats such as
Microsoft Excel.
Run time instrumentation and monitoring. An Administrator
can use SRI to set up automatic monitoring of the SRI database and its
connected clients. Programmable monitor filters can trap unattended
alarms and events and initiate automatic actions.
Online System Administration providing the ability to configure
global parameters as well as maintain individual SRI clients on a running
system (much more planned for Release 2).
Highly generalized source code modules that lend themselves
towards rapid site customizations. Contact Morning Glory Technologies for
more details on leasing SRI sources.
SRI is intended to model processes that contain dependent
elements that ultimately make up a completed unit.
SRI GYR (Green/Yellow/Red) Reporting Engine.
Overview
SRI
is a single rooted hierarchy that extends three levels deep. This is a
simple yet surprisingly powerful structure. There can only be one
starting point for any SRI hierarchy. Each hierarchy branch terminates
after a maximum of two levels. The following figure illustrates the SRI
hierarchy:
Systems
Releases
.
.
Release
Items
Items
A
single System starts the hierarchy. It is composed of an arbitrary number
of Releases each of which is composed of an arbitrary number of Items. Typically,
this architecture is used to represent current time at the start of each
hierarchy (a System) that is made of preceding Releases and Items. This
does not always need to be the case however and the structure can be thought of
as not having any particular time direction at all.
A
SRI database is composed of one or more stored SRI hierarchies. SRI is
intended to model processes that contain dependent elements that ultimately
make up a completed unit. SRI then allows the state of any number of processes
to be tracked and stored for trending analysis and reporting.
Some possible SRI scenarios include:
Assembly and
manufacturing activities where complete units are made up of custom components
each needing different tracking requirements.
Aging applications that
report on pending operations such as Account Receivables or Billing
Systems. SRI could be used to create a pending Item and then arrange for
that item to transit through different thresholds with time.
Software development
organizations that build applications made of chronological releases. SRI
can measure and store each point in a given Codeset life cycle from
development, testing and production support.
A Field Service
Operations Center dispatching Field Engineers to remote sites. SRI will
keep a history of past problem resolutions as well as quantify the current
overall maintenance effort.
Etc