What are some of the key points to consider prior to implementing JOYN FSM?

General Implementation Considerations

This page helps you understand how to plan for an FSM implementation including

• Integration Efforts

• Manual upload Efforts

• Considerations and assumptions around access to data and understanding of technology among your staff

• Availability of internal resources

• Timeline Estimations

• Training

• Goal Setting/Risk Minimization

• Upload Templates

NOTE: This is not a complete detailed list and there are always unknowns in any project given your goals for the project. The intent of the document is to help you plan to minimize project risks as much as possible given what we believe is typical for a basic implementation to get going.

Integration Unknowns

Integration unknowns are usually the biggest cost factor in an implementation. However, the less the unknowns, the faster the implementation goes and in turn can lower the overall cost of implementation.

Note: It is difficult for W Energy to know the level of expertise to which your staff knows its own internal systems or understands basic integration technologies such as APIs. Therefore, the assumptions for estimates we have made in this document are as follows:

1. Customer has access and understands how to access or grant access to all relevant source systems required for integration

2. Customer knows how to query all relevant internal source systems for integration

3. W Energy staff would help with S2T mapping for integrations assuming all customer source system data identification is clearly defined. I.e. No Business Analysis is required by W Energy on internal source systems to understand structures, perform queries, etc to support S2T mapping

4. Customer has basic knowledge of API technology and is be able to work with JOYN APIs with as needed services support from W Energy.

5. Customer has a general understanding of the entity definitions in this document (JOYN FAQ web page links are provided for more info in entity tables below)

Integration vs Manual Upload

While integrations are great and keep everything live and in sync between different systems, it can sometimes be a costly endeavor if you don’t have the right SMEs to setup proper integrations and this can lead to expensive delays and rework. Therefore – depending on the level of expertise available within your staff – sometimes it may be a quicker path to value to perform manual uploads of such data.

This page provides both Integration and Manual upload estimates for entities that have both options.

Estimates for Entities that can be integrated or manually uploaded

Upload Templates

Below are the templates that can be used to upload assets

Estimates for Entities/Setup that have done via integration

Estimates for Entities that must be manually uploaded/setup

Project Timeline

A typical timeline for a ready to implement JOYN FSM project can be as little as 2 to 4 weeks or as long as 4+ months. However, the actual timeline is defined by your readiness as a client in terms of:

• Clarity and focus of goal

• Clearly defined and focused set of use cases supporting the overall goal

• Clearly defined criteria/setup/needed attributes/logic/workflow for the use cases

• Clearly defined user personas and identified users for testing and feedback input for use cases

• Clearly defined and well understood source systems and APIs for potential integrations to support use cases

• Ability to attain relevant data required for the project (e.g. manual uploads, etc) for general setup and use cases

Editable Excel Timeline Templates based on below Timelines

Excel Estimation Template.xlsx

Sample 2 Month Timeline without Integrations

Sample 2.5 Month Timeline with Integrations

NOTE: Integration timelines are estimates and may change subject to customer’s SME knowledge for internal systems.

Training

Training can be conducted remotely or in person. It is up to the customer what training model to use. However, this is what we recommend:

• Basic Web Administrator Training: One 4 hours session or 2 x 2 hour sessions

• Basic Mobile user Training: One 2 hours session

• If your field users cannot be accommodated in a single training session, it may be better to train one set of users and then internally train the trainer.

• Additional Training can be requested as needed.

Goal Setting & Risk Minimization

It may be tempting to move hundreds of field activities to JOYN all at once in a big bang approach. However, historical indicators all but ensure this is a recipe for failure.

The change management involved across hundreds of field activities may be too much for the organization to handle.

Instead – the natural, faster and more effective path to success is to spend time up front getting 4 or 5 activities setup in JOYN and rolled out across a small user base. This leads to immediate success due to:

• Focused planning and execution

• Less change management

• Controlling the blast radius of risk for a smaller set of use cases and personnel

• Allows for fine tuning the small kinks

• Once the first 4-5 activities succeed, the next 400-500 usually spread like wildfire!

Summary of Recommended Effort Estimate from Above

*Note: It is difficult for W Energy to know the level of expertise to which your staff knows its own internal systems or understands basic integration technologies such as APIs. Therefore, the assumptions for estimates we have made in this document are as follows:

1. Customer has access and understands how to access or grant access to all relevant source systems required for integration

2. Customer knows how to query all relevant internal source systems for integration

3. W Energy staff would help with S2T mapping for integrations assuming all customer source system data identification is clearly defined. I.e. No Business Analysis is required by W Energy on customer’s internal source systems to understand structures, perform queries, etc to support S2T mapping

4. Customer has basic knowledge of API technology and is able to work with JOYN APIs with as needed services support from W Energy.

5. Customer has a general understanding of the entity definitions in this document (JOYN FAQ web page links are provided for more info)

6. Effort estimates and Training are per recommendations in this document.