|
|
 |
 |
|
| |
|
|
| |
Organization Modeling
and Management™ Architecture |
| |
The OMM™ design meets
the challenges of next stage Enterprise eBusiness (EeB) by providing
an architectural platform that enables the development of integrated
and extensible application suite functionality. OMM™ consists of the
following technology components to meet the stated challenges: |
| |
|
| |
| The four primary components
of OMM™ |
| |
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
| |
|
| |
Resource Modeling:
The OMM™ model is an advanced object-oriented approach designed
specifically to represent different resource types within and across
enterprises. Applying the OMM™ methodology, system designers
are able to represent to the desired level of complexity various business
objects such as products, services, companies, employees, partners,
contracts, invoices, auctions, negotiations and others.
Virtual Link™:
Provides dynamic relationship management. Objects are linked based
on business rules. This unique approach, using our patented Virtual
Link™ model, abstracts business relationships and policies into
computable rules, whereby thousands of relationships that exist can
be represented by a handful of business rules. When the underlying
information of the business objects change, these virtual links automatically
adjust themselves to represent the new relationships between the business
entities. |
| |
|
| |
OMM™ Model |
| |
 |
| |
Illustration depicts how
OMM™ and Virtual Link™ work together. |
| |
|
| |
EGI WorkFlow™:
An object-based workflow system is developed on top of the OMM™ model.
The workflow system allows system designers to define flexible business
processes to represent the numerous interactions and collaboration.
Many eBusiness application functions also rely on the workflow engine
to enhance their flexibility for modeling relationships between various
users. However, with the object approach, the EGI WorkFlow™ system
can be easily integrated with external workflow systems developed
by other vendors.
Event-based Messaging and Notification:
System administrators can define system events and business modelers
can define business events. All of the defined events are associated
to specified plug-in executable programs (methods). When a certain
event is raised, the system will automatically trigger the corresponding
program to run. This mechanism enables users to receive notifications
(via email, cell phones or other wireless communication means) upon
event occurrence. |
| |
|
| |
Predefined Explicit
Object Classes:
Through research and customer input, EGI has developed an extensive
set of predefined, explicit object classes used to deliver eBusiness
functionality. These object classes allow us to quickly customize
our application suites to meet customer specific business needs. These
object classes were built using industry standards, which include
Java, Java Beans, EJB, J2EE, JDBC, Java Server Pages, LDAP and XML.
We have developed over 70 Java object classes with over 300 Java Application
Programming Interfaces (API).
Library of JSP / WEB Pages:
The EGI Library of JSP / WEB pages is developed on top of these
Java Object Classes and provide over 80% of the required eBusiness
functionality on the WEB. These predefined pages can be easily customized
to support unique image, brand and business requirements.
Backend Integration:
All objects within EGI PerfectSuite™ can be imported from
and exported to XML format. This makes the integration of our data
objects with backend systems easy and straightforward. EGI also
provides integration solutions via our partner relationships. |
| |
|
| |
|
| |
|
| |
|
| |
Home
| Company | Press
Room | Solutions | Career
Opportunities | Education | Download |
|
