Transition Plan

Context

As the contract between AP-CDMA and eGov is going to conclude on 30th September, this requires transition of ERP modules to the internal team of AP-CDMA in order to take up support and enhancements activities in future for smooth functioning of the ERP modules. Planned duration of the transition process is 2 months in taking over the ownership of ERP.

Scope

The document defines the areas to be covered under the transition process, the stakeholders involved at each phase and the supporting documents required under each phase.

This includes detailing application architecture, application setup, application design, functionality of each module, code base walkthrough, database, ElasticSearch, third party integrations, REST APIs, dashboards, portals, known issues, recurring issues.

Domain KT has to be conducted by the CDMA before initiation of transition process by eGov.

Stakeholders

Management team, technical team and functional team of eGov and incumbent vendor. This includes Project Manager, Architect, Business Analyst and the development team of eGov and inhouse team of AP-CDMA.

Pre-requisites

SPOC to be appointed by the department for the transition process.
- SPOC is required to co-ordinate the overall KT process, clear all blocks on the way and ensure that transition happens smoothly.
- SPOC should also ensure that all the required resources are put in place well before starting the KT process.
Municipal Domain KT has to be conducted by the department before introducing the team to eGov for technical KT. Municipal Domain KT includes :
- Structure & Functioning of ULBs
- Grades of ULBs
- Role of Council in the ULBs
- Departments in the ULBs
- Understanding Municipal Processes & Terminologies
- Services under various Modules
- Requirements for submission of a Service & Levels of Workflows
- Types of Notices, Proceedings, etc., generated under various services
Department must provide a repository wherein eGov can share the technical and functional documents that are to be shared with the incumbent team. Recommended git repository.
Development team must have prerequisites installed on their machine that includes the latest JDK, IDE (Eclipse or IntelliJ), Postgres, ElasticSearch, IReport IDE. Recommended latest Ubuntu OS installed on machine with minimum 16GB RAM.
Proper internet connection and power backup must be in place to ensure interrupted transition processes as most of it would be conducted through virtual sessions.

Resource Requirements

Sl. No.	Role [Required No.]	Key Responsibilities
01.	Project Manager [01]	Create Project Plans Monitors production and quality to customer/stakeholder standards. Identify, log and help resolve issues and risks. Reports on project progress, offers viable solutions and opportunities as they arise. Implement change practices. Manage resources to ensure the schedule is on track. Conduct meetings and set expectations for the project team.
02.	Architect [01]	Lead the technology & architecture of ERP. Responsible for technology choices and decisions; Design & Code frameworks. Ensure projects are designed within approved enterprise architectural standards. Enforce coding standards & adherence to enterprise architecture in product development Provide technical leadership in all aspects of SDLC, including system analysis, design, development, testing, and deployment.
03.	Technical/Module Leads [04]	Hands on development skills. Thorough understanding of the system. Analysis, design, development, design review, code review. Upskilling and reskilling of team members. Task allocation to team members. Planning and estimation.
04.	Business Analysts [04]	Communicate with internal colleagues to understand the needs of departments and the organization as a whole. Work with external stakeholders to understand and investigate feedback into the service,function or product provided. Use data modelling practices to analyse your findings and create suggestions for strategic and operational improvements and changes. Consider opportunities and potential risks attached to suggestions you make identify the processes and information technology required to introduce your recommendations. Gain agreement, usually from senior management, of the best method of introducing your recommendations to the business. Communicate the benefits of your recommendations across departments and help to address any uncertainty and concern. Produce written documentation to support your work, report on your findings and to present to stakeholders when necessary. Support staff and teams in making your recommended changes, including helping to resolve any issues. Ensure plans are made and processes are created to evaluate the impact of the changes made, including taking responsibility for overseeing and reporting on this evaluation. Raise Jira tickets for any enhancement/ change request with complete details, acceptance criteria, out of scope parameters
05.	Senior Software Engineer for Portals [01]	Portal maintenance and incorporate enhancements in CDMA and ULB Portal Implement regular Drupal, MySQL, PHP and associated upgrades. Implement best practices.
06.	Senior Software Engineer for ERP [04]	Complete ownership of the modules assigned Design, Code, Writing junit Test cases & release Ensure projects are designed within approved architectural standards. Lead Code reviews and implement best coding standards. Lead engagements with Clients. Review and discuss enhancement/change requests with the team. Provide inputs to Jira tickets.
07.	Software Engineer [04]	Complete ownership of the task assigned. Ensure end to end completion, including test cases, manual testing of the task assigned. Ensure coding standards are strictly followed. Provide inputs during design discussions. Must ensure the feature is tested as per the acceptance criteria provided in the ticket.
08.	DevOps Engineer [01]	Support the continuous integration and release process for both Microservices modules and Monolith modules. Design, build and maintain the CI/CD infrastructure and tools. Ensure landscape availability, performance and stability. Investigate and evaluate new tools and DevOps technologies. Work closely with development teams to ensure that solutions are designed with customer user experience, scale/performance and operability in mind. Proactively escalate visible upcoming issues. Open to work in off business hours.
09.	QA Engineer [04]	Creation and Execution of Scenario and use-case testing. Creation of functional, and automation tests. Good verbal and written communication skills Exhibits good judgment establishing priorities and escalating issues Flexible, adaptable and independent work style End-to-end data verification. Collaborate with team members to verify system performance and scalability.
11.	DBA	Responsible for upgrading, configuring, integrating, and maintaining staging and production PostgreSQL database. Responsible for all backup, recovery, and upgrading the PostgreSQL databases. Responsible for monitoring databases to optimize database performance and diagnosing any issues. Responsible to develop, implement, maintain policies and procedures and document database architecture to ensure the security and integrity of the databases. Responsible for implementing data access, table maintenance and changes together with the development team.