home about us solutions methodology contacts  
    Home  >  Methodology  
 

 

Methodology


figure 6

Vision
We stress the importance of vision before starting any enterprise scale initiative in any organization.

  1. the company's Risk Assessment scope
  2. the company's Risk Mitigation appetite and priorities
  3. the company’s preparedness to respond to disasters
  4. the company's preparedness to recover from disasters

Needs
Once these objectives are understood and agreed upon it is imperative that the organization's present needs are established in a strategic model, starting from common risk typical to an industry, then selecting relevant risk to the organization, with probability, impact, duration and costs. Next step will be documenting all the macro level functionally company is already doing. The model should then identify the goal of the enterprise for prevention and preparedness and clearly defined and understood in terms of human resources, assets, sites and respective plans.

  1. the project plan
  2. the responsibility matrix

Map
After identifying set of business process that need attention it is important to map them in to the enterprise overall tactical plan. This phase will involve lot of commitment from functional people. Compare your inventory of current risk mitigation to the top priorities based on the appropriate optimization scenarios. Deliverable of this phase are:

  1. business process study document
  2. as - is model
  3. to - be model

Pilot
Piloting phase involves a lot of detailing and usage of the system by functional people whom will be trained on the system. Deliverables of this phase are.

  1. requirements of document
  2. configuration design document
  3. delivery schedule


figure 7

Implementation
This phase will involve live solution activities implementation, which will be mix of local as well as off-shore synchronization fine tuning. By the end of this phase, Client will be in position to see the system in full function. Deliverables for this phase are.

  1. complete software system
  2. user technical documentation
  3. maintenance a configuration documentation
  4. Most of the content input and implementation
In the background at our end the software development cycle will follow the route of requirements - design - implementation - testing - iteratively to deliver the system.

Operations Readiness
The core of ERS operational readiness lies in its Methodology Engine. The Methodology Engine allows Incident Managers to think of different scenarios and prepare processes and procedures to tackle them. When an incident happens, ERS creates an optimum action plan based on the procedures, steps and action items deployed, location of the incident and the severity of the incident. The Optimum Plan created by the Methodology Engine, selects the right 1st Responder (or Agencies, EMU, etc…) and assets, which have to be deployed at the site. The Methodology Engine allows creation of the entire action plan as tasks in a collaborative manner, thus being able to draw from multiple experts and institutes best practices to address any incident scenario.

 
©GlobeCom21, all rights reserved