MECOMS Sure Step
MECOMS™ Sure Step extends the proven Microsoft Dynamics Sure Step implementation methodology to reduce the risks and implementation cost and accelerate the implementation time of a MECOMS™ project.
Ferranti and its partners use the MECOMS™ Sure Step methodology to implement MECOMS™ at utilities.
A formula for successful MECOMS™ Implementations
MECOMS™ Sure Step is designed to help customers reduce their total cost of ownership. The Sure Step Methodology can be used for large, medium, and small projects. The methodology provides different project types to suit the implementation engagement, as well as optional offerings to assist during diagnostics and optimizations.
The MECOMS™ Implementation Methodology is based on Microsoft Sure Step Methodology and expands it to perfectly align with the challenges of the energy and utilities sector. It does this by providing proven processes, template documents, blueprints and more.
Flowchart diagrams within the Sure Step Methodology point you to tools and templates that can be used at different phases, while the content provides detailed guidance on roles required to perform activities and proven best practices. The content tools, templates and best practices of the methodology can help you increase the consistency, timeframes, quality and success of your implementations.
Cross Phases Process Phases
Program Management - Project Management Library
Project Management disciplines include: risk, scope, issue, time and cost, resource, communication, quality, procurement, and sales management. The process view for Project Management differentiates between initiation and planning, execution and monitoring and closing of projects.
The Training Strategy and Plan identifies the objectives, vision, approach, and delivery mechanisms for the training over the course of the project. This is a critical aspect of Organization Change Management (OCM) to align and mobilize the organization’s users.
Business Process Analysis
Business Process Analysis begins with workshops designed to explore the current stateprocesses, improve efficiencies, suggest automations/workarounds and design the future state processes.
Requirements and configuration
During the Analysis phase, gathering and documenting the customer’s business requirements is the most important set of activities that must be undertaken when implementing MECOMS™.
Code development standards are extremely important to be documented at the start of the project. These standards are agreed upon between the development team and the customer and result in consistent and documented code that is easily read and understood.
Quality and Testing
The value of comprehensive, well-executed testing cannot be over emphasized. Even when there are minimal customizations, it is important for the customer to execute their typical business processes in the new environment in order to ensure that user workflow procedures and application configuration settings are appropriate for optimal productivity.
The Infrastructure cross phase process contains activities to define, recommend and deploy the architecture required to support the MECOMS™ solution. The needs of the business must be balanced against the infrastructure, operational, and security requirements defined in the Analysis phase.
The need for integrations and interfaces to external systems should be identified during the analysis of business processes.
It is very important to define the master data elements and gain consensus on their meaning and usage with the customer. The Data Entity and related Taxonomy includes the master data elements, their definitions, and how they will be used in the new solution.