Technical Architecture Evaluation

Following are the key architecture imperatives for a Execution-MiH tools:

• Multi-tier architecture: Should have at the minimum database, application server, and web-server layer and a zero client. Most of the tools come with both thin/zero and thick client versions. The thick client versions are reserved for more enhanced capabilities related to designers/power-users/administrators.
  
• Well encapsulated components: The entire tools should be in distinct set of encapsulated components. This enables a customer to pick and choose and this also makes maintenance, customization and integration much easier.
  
• Semantic layer: This layer separates the complex under layer of the tools and the front-end users/designers and administrators. It maps the technical meta-data with the logical meta-data. For Example ‘cust_id’ is mapped to ‘customer ID’.
  
• Common set of services:
  
  These are common services which can be available. These should be ideally centralized services which can be used by any component of a Execution-MiH (BUSINESS INTELLIGENCE AND PERFORMANCE MANAGEMENT) platform. For Example if a platform has an ETL, enterprise reporting and Analytics application, there should be common set of services catering to all the components. Some of these services are:

  - Security Services
  - Scheduling and alerting services
  - Publishing and distribution services
  - Repository storage and retrieval services.
  - Caching and fail-over services
  - Business rules and metrics services
  - Performance management services
  - Auditing services
  - Collaboration services