control-ES has an enterprise architecture which is capable of scaling from the smallest department to the largest multi-national organization.  Below is a summary of the technical architecture which is described in more detail in the paper “control-ES Release 6.0 Technical Architecture”

Environment; The data is managed in 3 databases for process, documents and metrics.  The process repository holds process diagrams and all process related info (resources, metadata, access rights).  The document repository holds all files related to processes (forms, templates, application links, policy documents).  The business intelligence repository tracks trend data for the key metrics to produce graphs and launch alerts.

Enterprise Web Server; This presents all information to any browser enabled device. It has been designed with scalability, ease of use and minimal IT admin overhead in mind.

It has been tuned for large-scale usage through the use of a memory and disk image cache. The server allows interaction using only HTML and JavaScript and does not rely on any ActiveX controls. The Enterprise Server runs on top of Internet Information Server (IIS).

Enterprise Client; This is used to capture, analyze, reports and extract content.  The Workshop Client can run in standalone mode where the Process Repository is hosted on the local machine for live mapping workshops, and can then be synchronized to the central server. The Enterprise Client operates across the network using shared drives, UNC paths or via Citrix for a global deployment over the internet.

 Action Server; control-ES integrates with the corporate IT infrastructure, with LDAP for single sign-on, with email and SMS to be able to send alerts, reminders and subscriptions, and with integration with MSOffice.

Samples of screenshots and more information

• Up
• control-ES Concept & Initatives
• control-ES Benefits and Clients
• control-ES Architecture
• control-ES Screen Shots