3E’s Approach to Business Process Management Solutions

1. 3E’s Approachto Business Process ManagementSolutions 3E SOFTWARESOLUTIONS 24, CMH Road, Indira Nagar IIStage +91 9916 832878 Bangalore, Karnataka – 560038,India hello@3esofttech.com

2. 1 RequirementsGathering

3. 1.1 High-Level BusinessRequirements  1.1.1 Current process/ITEnvironment  1.1.2 Planned Process/ITEnvironment  1.1.3 Metrics andObjectives  1.1.4 Functional GapAnalysis  1.1.5 ComplianceRequirements

4. 1.2 Elaborated TechnicalRequirements  1.2.1 IntegrationRequirements  1.2.2 LegacySystems  1.2.3 Human and Systeminterfaces  1.2.4 ExistingErrors  1.2.8 Internal and Externalconsumers  1.2.9 Consumerization andBYOD requirements  1.2.10 Social MediaIntegration  1.2.11 Business ActivityMonitoring  1.2.12 Business RulesManagement  1.2.13Technical GapAnalysis  1.2.14 ToolsEvaluation  1.2.5 Data Compatibility andData Conversion  1.2.6 DeploymentRequirements  1.2.7Interoperability

5. 2 Design and Proof ofConcept

6. WORKFLOW/PROCESS MANAGEMENTSystem 2.1 Process Diagram for thenew The step is about coming upwith:  -High-level business process diagram that outlines the business process flow with thePlanned WORKFLOW/PROCESS MANAGEMENTSystem.  -High-level technical design for the Planned WORKFLOW/PROCESS MANAGEMENTSystem.

7. 2.2 PrototypeDevelopment  If the Business Process is complex enough, development of a quick Prototype, with necessary Simulations, is carried out that helps in fine-grained analysis of the requirements and helpidentify any technical gaps that were not identified during requirementsgathering.  If multiple tools (WORKFLOW/PROCESS MANAGEMENT/SOA) are used for the implementation, the integration of these tools is also tested during this Prototyping and Proof of Concept phase to analyze the end-to-end process.

8. 3Implementation

9. 3.1 Prioritization  Prioritize the implementation tasks as per the Business and Technical significance andchallenges. For example, integrating a legacy database System could be technically challenging and implementing this first in the WORKFLOW/PROCESS MANAGEMENT System could benefit a lot compared to keeping this to theend.  Replacing the tasks that are currently done by Spreadsheets may fetch in a lot of value and fills alot of gap with the SMART objectives that are desired to beachieved.

10. 3.2 FunctionalImplementation  Implement the Functionality and develop a new WORKFLOW/PROCESS MANAGEMENT System that works end-to-end, with all Human and System actionssupported.  This is done as per the priorities defined as above, and elaborating the requirements to-the-details for eachoutcome.

11. 3.3 Implementing SMARTObjectives Once the Functional Implementation is in place, it is now about looking at the SMART objectives tosee where we are and what else needs to bedone. Is the Database access speed enough to meet the desired level of Business Process efficiency? Is any fine-tuning needs to be done? Do we need to increase the size of the Databasepool? Are the service components on the Application Server scalable to the Business Requirements? What are the typical Load scenarios and how do we fine-tune? If the Automatic notifications are now being sent to the Business user, is the notification frequency good enough? Do we need to increasethis notification frequency to fit exactly into business objectives? What’s the optimalfrequency?

12. 4 Testing andDeployment

13. 4.1 DevelopmentTesting  End-to-End testing is carried out in the Testenvironment.  GOAL: Verifying and Validating theFunctionality.  This is followed by a typical feedback and bug-fixcycle.

14. 4.2 System Integration Testing(SIT)  Ensure End-to-End testing is done with all the business systemsintegrated.  GOAL: Identify any integration and interoperabilitygaps.  Issues, if any, will be fixed and will be validated after a quick ‘DevelopmentTesting’.  Works with Business IT on any organization procedures to be followed forSIT.

15. 4.3 Deployment & User Acceptance Testing(UAT)  Production components will be replaced in steps to reduce the risk. It again goes with the levelof change beingimplemented.  GOAL: Identify any production deploymentissues.  Works with Business IT on any organization procedures to be followed forSIT.  Identified Business Users/Analysts will perform theUAT.

16. 5 Transition –Documentation, Training,Support

17. 5.1Documentation  5.1.1 TechnicalDocumentation  Modelling and ArchitecturalDiagrams  Technical ImplementationDetails  Information on handling modifications andextensions  5.1.2 UserDocumentation  End-Usermaterial.  5.1.3Installation  Information onDeployment  Information onConfiguration

18. 5.2 Training  5.2.1 General User & Power UserTraining  To enable the Business team of the organization handle the business operations using theWORKFLOW/PROCESS MANAGEMENT solutiondeployed.  5.2.2 DeveloperTraining  To enable the IT team of the organization handle the WORKFLOW/PROCESS MANAGEMENT modificationsand enhancements post Supportphase.  5.2.3 TrainerTraining  Typically required for the big or multi-siteorganizations.  May take care of only User Training or Developer Training orboth.

19. 5.3Support  Enables smooth transition of the WORKFLOW/PROCESS MANAGEMENT solution postdeployment.  3E team handles Technical Administration & Operationalmodifications/enhancements.  On-Site and Off-Shore support is identified as needed and SLAs are defined whereverapplicable.

20. ThankYou 3E SOFTWARESOLUTIONS 24, CMH Road, Indira Nagar IIStage +91 9916 832878 Bangalore, Karnataka – 560038,India hello@3esofttech.com