1. Nilesh Mandani Competencies include: Volume Licensing Enterprise Resource Planning Customer Relationship Management Business Intelligence Proposal for Architecting of Software Solution 25-Aug-2014

2. Proposal Presentation Process 1-2 Min AS IS Scenario 5 Min TO BE Scenario 5 - 10 Min Operational Challenges 10 Min Solution Recommendation 10 Min Anticipated Benefits / Project Implementation

3. Agenda AS – IS Scenario TO – BE Scenario Operational Challenges Solution Recommendation Anticipated Benefits Project Implementation

4. AS – IS Scenario Three Tier Architecture Client Tier – Access application from Web Browser Application Server – Apache Server - Application is built using Core Java Classes, Components, Servlets, JSP Database built on MySQL DB Application Server Client

5. TO – BE Scenario Three Tier Architecture + Web Services Client Tier – Access application from Web Browser Web Services + Application – Middle Layer for communication between Application and Database to perform transaction and roles & responsibility Application Server – Apache Server - Application is built using Core Java Classes, Components, Servlets, JSP Database built on MySQL DB Application Server Client Web Services Application

6. Operation Challenges Roles & Responsibility User wise Roles & Responsibility Assignments are difficult without security architecture (E.g. Surveyor log in to application should see his menu and reports) Forms / Pages Configurator Forms and Pages to be displayed according to user type and role assigned. In current practice there is no business logic reside between application and database. Reports Report Links / Report type, considering core java and jsp pages. Reports engine does not allow to print reports.

7. Solution Recommendation Change of Application Architecture Current architecture doesn’t support business logic to be access apart from application. Here it is required before getting in-to application, it required to build application layer and design templates based on users type. Design 6-7 Role Centers, where we would assign user type to role center. This role center would protect inside menus for displaying application function / reports. Change of Application Operation Core JAVA / JSP / Servlets has limitation to render page runtime from XML. Here using JSON techniques, we would build application fields to be showcase on each page. Build Configurator tool which decide configuration of each pages as instance and assign to individual menu. Introducing Web Services (SOAP) Convert page function in Web Services Calls Converting to web service call would help to attach web services call to Roles & Responsibility Architecture.

8. Migration & Implementation Approach Business Logic Current classes, code and files would be utilize towards building better business logic SDLC We would like to perform full SRS from existing application and develop design document for new application After application architecture & design approval enable to start development and building solution. Test based on business scenario and case studies Deployment & Training to End Users to put application in Operation Support (On-Site) / (Off-site)

9. Anticipated Benefit Re-Implementation Time consumption for designing application would be reduced as current business functional flow is clear. White - Label DCSPL would work by name of Emperial in front of customer NDA would be sign between Emperial and DCS to perform entire project.

10. Anticipated Benefit Project Estimation Man Months – 16 Months Fees – 12,00,000 INR /- (75,000/- PR) Team would be depute on-site for Requirement Gathering and Training Purpose (2 Months Approx) Payment Terms – 20% Advance, Rest would be paid based on agreed Milestones Boarding, Lauding, Food, Passport, Ticketing would be bare by customer. Support System would be entirely design by Emprieal

11. Next Steps Start Date Prospect resource requirements Go-Live Date (have to have a compelling reason to act NOW!) Ask for the Order!