Approach & Methodology Overview
Approach is divided into main project activities.
Design: Key activities during the design phase will be focused on improving the performance and stability of the applications:
Requirement Gathering: Compile a detailed assessment on current version. This will be used in the Fit / Gap analysis workshops to help identify enhancements. This phase we will phase out obsolete functionalities and reengineer code to function as is basis. Evaluate current stability of the application and document.
Analyze current solution design: Review with CLIENT’S stakeholders the major pain points of application components, current solution design and technical architecture to identify limitations. Prepare for the workshop discussions in terms of proposing alternatives, best practices and improvement options
Conduct application and technical architecture workshops:Organize and conduct workshops as needed to review the various aspects of the solution design opportunities. Document the outcome of the workshops, implementation approach and solution design. This will include a detailed inventory of the development work units to validate assumptions.
Development: Key activities of the project are listed here with additional details on execution and how objectives will be achieved:
Implement enhancements in DEV environment:Design the code and implement in DEV environment. Complete SIT testing to ensure utility functions appropriately. Update technical documentation which describes the enhancements process, including an check-list and the results of the tests.
Migrate applications to TEST, PROD: After the successful code design of the Hyperion components in the DEV environment migrate all the applications and artifacts from to (TEST and PROD). Perform the migration using the out of the box Hyperion Lifecycle Management process, since this will be a migration of applications between one server and the other, with the same Hyperion version.
Perform periodic application synchronization: Synchronize data, metadata, security and objects such as business rules, forms, and reports from the current environments to the new environments. Refresh cycles for DEV, TEST and PROD will be coordinated based on the beginning of each new test phase (system integration, UAT, performance). Code updates will be traced using a version control process. Perform automated approach for data, metadata and security synchronization depending on type of objects.
Perform final synchronization during freeze period: Identify freeze period with CLIENT and business stakeholders to reduce the risk of misalignment between environments. The freeze period will affect code changes and security changes, but not data or metadata (current automated processes will be run). The freeze period is a risk mitigation tool to reduce the number of moving parts during the deployment phase.
Testing: key activities for Testing:
Execute unit testing in DEV: Complete in the new DEV environment. This will identify the majority of the objects requiring remediation not previously identified. Coordinate unit testing activities. Correct changes needed in case of any defects / deviation. Sync up Test and production environment through standard migration process.
Collect unit, system & integration test templates: Collect the current documentation that CLIENT has in terms of system test and environment. The test templated will be adapted based on version and functionality changes. Validate with CLIENT & obtain official sign off on the test templates. Complete system integration test in TEST environment.
Obtain UAT test scripts: Obtain use cases from Essbase and Planning resources required as part of UAT. Obtain UAT test specifications and scripts. Obtain official sign off on user acceptance test run.
Project Methodology: this is a brief summary of the project methodology, high-level project schedule, and Bourntec delivery approach to meet the CLIENT’S requirement.
Schedule & Timelines: A timeline is devised based on our experience and expertise in similar complex engagements in Hyperion. The key features of the plan include:
High parallelism of activities
Confirmation of project scope, approach & cost. Key decision points will include agreement on the overall implementation and roll-out strategy.
Design and finalization of the validation templates and decision on the testing approach, data migration and training strategies
Go/No-Go Decision at the completion of UAT for each of the identified phases.
Our project methodology is based on our previous client experiences, but will be tailored to align with CLIENT’S methodology. There are specific phases during all projects:
Concept: In this phase the planning, the Fit/Gap Analysis is performed and the scope is established.
Definition: In this phase an assessment is performed to identify current technical and application architecture design gaps, and identify new requirements. During this phase the team will focus on three parallel activities and utilize a workshop approach to validate requirement and designs with stakeholders:
Application assessment and gap assessment
Technical architecture scoping for new hardware and procurement requirements if any.
Assessment of key design considerations and recommendations will need to be evaluated by CLIENT to determine priority, impact, and desired release strategy.
Construction: Key activities in this phase to establish an environment migration path for Production, and validate enhancement activities. The construction phase is also defined to create and/or modify objects required that are not automated by the utility (i.e., report modifications, interface modifications, business rule conversion, customization’s).
Testing: The test phase validates all environments, verifies integrated system test, user acceptance test, completes performance tuning, and obtains customer approval.
Objective of change management process is to ensure that changes are recorded, evaluated, authorized, prioritized, planned, tested, implemented and documented.
Change Management Services are activities that are to ensure that standardized methods and procedures are used for efficient and prompt handling of all changes, in order to minimize the impact of change upon Service quality and consequently to improve the day-to-day operations.
Typically, upon completion of change user acceptance testing, development team will submit change control form to CCB (Change control board).
CCB will evaluate business need, impact of these implementations of over existing application in production, complete documentation for change, implementation plan, outage schedule and also back out plan in case of failure in production or change of plans.
If change is approved, then implemented and validated in production. In case of back out form, team needs to initiate another change control form and mention the previous details along with it and repeat the process.
Change management process overview below:
Bourntec develops a measurement framework along with customer using our quality process addressing the customer needs. The measurement framework includes the metrics that are required from project level to relationship level to help CLIENT and Bourntec to monitor the health of the engagement. Bourntec has well thought out set of performance values to measure and enhance product quality with broad goals as:
- On Time Delivery
- Effort Variance
- Project Quality
Revolving around these measurement areas, Bourntec has coined a variety of metrics in-house, relevant to the type of activity to be measured and tracked. Apart from defining the measures of part of project initiation phase by CLIENT & Bourntec, target values are set for each metric and process improvements are made to achieve those targets.
Statistical Process Control techniques are used to enhance Consistency, Predictability and performance improvements. In addition to these, Control Charts are drawn to measure process stability.
Bourntec defines the project reporting needs during the project initiation phase. Bourntec standard process of project reporting is
- Through Weekly and Monthly meetings supported by respective reports
- Overall Project Status reports for all stake holders
- Project reporting will be provided through Softcopies prepared by PMO office
Our standard reviews and actions covered in meetings as below:
- Weekly report (Overall tasks status, Work in Progress, Pending issues, Escalations, Work planning for next week)
- Monthly Report (overall project status, Metrics, Critical/Risks)
- Future tasks in summary
BSI has delivered successful EPM solutions varying in size and scope including new implementation, upgrades, conversion of obsolete excel models to Hyperion Suite, configuration, architectural design and software integration with Oracle products or other company specific applications in which the solution is flexible and able to accommodate deployments throughout all our client’s necessary business needs.
In the end, we deliver results. Upon completion of a successful engagement our clients experience enhanced system functionality and tractable operating processes. Bourntec Solutions Inc. has a strong track record for delivering smarter, high-quality, end-to-end results to our clients worldwide. We enhance the performance of the technology to meet your requirements and goals.
Bourntec Solutions Inc. provides full support across the entire Oracle product portfolio, with proven & proprietary methodologies supported by stringent governance models. Our Solution Factory, Upgrade Lab, Tools, Accelerators and Enablers expedites implementations, migration and upgrades. Our deep knowledge about the requirements of enterprise systems, verticals and industries ensure your applications evolve along with your business.
- Bourntec EPM/Hyperion Services
- Does the system strengthen the organization’s competitive position?
- How does EPM affect the financial structure and culture?