 |
EBT Process (Process Milestone Implementation Methodology) |
|
|
|
| A phased customization approach supplemented by its time tested and proven methodology and clearly defined milestones to achieve a timely, cost effective and quality solution. Each phase of the project will have well defined entry and exit criteria. Pre-defined deliverables for each phase will enable us to easily track and control the progress of the project. |
|
| The methodology supports efficient project implementation management, resource planning and various types of accounting, results analysis, etc. This method allows the company to begin ERP implementation process on its own or share all the responsibility with the partner. This implies that it would be a shared platform where the files / knowledge is with the partner, as they will be a part of ERP implementation. This method of ERP implementation has grown widely popular. |
|
| The merit of this methodology is that it avoids immediate restructuring of the company. The approach is completely hands off to the business structure, after considering all options regarding the technique / business processes. |
|
| System Requirement Document-SRS
|
• Establish Customer / EBT project management process and team
• Collate all background information and documentation
• Confirm the business objectives for the project
• Develop macro and micro plan for implementing the solution
• Develop plan for supporting technology infrastructure and deployment
• Provide first level education to user and technical team members
• Confirm Customer Business Unit representatives participation and involvement
• Team designs, develops and refines new business processes where required |
| |
| Functional Requirement Document-FRD
|
•
Customization requirements are identified for development
•
Decisions and conversion definitions for data mapping are provided
• Business flows and desktop procedures prepared, validated and documented for use in later project phases
• Business processes documented during the SRS phase are mapped with the product
•
Take a signoff for the FRD document
• Provide first level education to user and technical team members
• Confirm Customer Business Unit representatives participation and involvement
• Team designs, develops and refines new business processes where required |
| |
| Customization & Development
|
•
Customization requirements: special forms, custom reports, interfaces and customization are developed
•
Design and write specifications for customizations
•
Make changes to programs following customer change control procedures
• Execute unit tests and QA scripts and correct as necessary
|
| |
| Conference room pilot demo- CRP
|
•
Test, demonstrate and validate the solution
•
Test, verify all setups, data migrations, processes and customizations
•
Prove the solution meets the business requirements
• Resolve all issues, make necessary corrections before continuing
•
Repeat the conference room pilot, if warranted, to prove the changes and the total solution
• Final Customer Executive decision for go-live phases
|
| |
| Training of Users (TOT)
|
•
Select and train an extended user team to conduct the final testing
•
Validate that the solution fits the business requirements and can be used to run the business
|
| |
| User Acceptance Testing(UAT)
|
•
Conduct an integration test as a "dress rehearsal" for go-live
•
Validate all solution deliverables
•
Submit test cases to the users
• Assure all elements required to execute the conversion and loads system are in place and available
•
Make any required last minute, minor changes
• Confirm the go-live date
|
| |
| System Integration Testing(SIT)
|
•
Acquire necessary hardware & network required
•
Test and QA user response time and network loading
•
Establish support model
• Project team and the business prepare for the go-live
•
Final conversion and startup schedules are refined
• Changes in user procedures and documents for training are completed
• Deliver training to the extended user community
• Dates and schedule for cutover and implementation are communicated throughout the organization |
| |
| Migration of Data
|
•
Map legacy system(s) data to the data schema
•
Use the application Data Direct / BizTalk Server and application adaptors to load programs or prepare custom programs
•
Prepare one-time programs to extract and format legacy data for the solution to load the programs
• Prepare one time data load and field initialization programs, including all required parameters
• Description: http://www.ebtech.biz/images/blt1.gif
Identify old, inaccurate, obsolete legacy data to be improved or eliminated before conversion
• Assign teams to cleanse data
|
| |
| Go Live
|
•
A production environment for new system is initialized
•
All data is converted and loaded into the solution
•
The team executes the detail conversion schedule with all validation steps to assure complete and correct data is loaded
• Customer does final month-end close on legacy system
•
Final conversion and startup schedules are refined
• When conversion is complete the new system is ready for production use
• Legacy system(s) is restricted to inquiry only
• Dates and schedule for cutover and implementation are communicated throughout the organization |
| |
| Support
|
•
User, IT and EBT support teams provides round-the-clock on-site support for the new system
•
Any issues are logged and resolved as reported
•
For the first week, the user, IT and EBT team support the startup
• Help desk receives calls, resolves as many as they can; reminder is given to project team members to resolve on a priority basis
•
Support continues through the next 'x' months end close cycles-where 'x' is to be mutually agreed
|
| |
| Post Implementation Audit
|
•
Evaluate the progress and effectiveness of the solution
•
Review the operational effectiveness of the system as implemented
•
Identify problems, performance or process issues
• Identify what is working well
•
Review opportunities to further improve effectiveness with the users
• Eliminate short-term problems and obstacles
• Present a plan of longer term corrective actions and improvements — if required
|
