Productivity Improvements

Management Time Savings

Productivity improvements will be measured using a process cycle time analysis. Use the benchmarks to identify improvements in cycle time for each sub process in a general business process. Quantifiable savings will be measured using the number of

FTE

s saved.

Management time savings will be calculated based on the number of exceptions and approvals the management team must handle per year. The savings are unquantifiable in terms of dollars, but in minutes saved per year. Remember, 240 minutes of time saved is a round of golf.

-30%FIRM A FIRM B

cycle time afterimprovement

-15%just

ERP

-28%FIRM A FIRM B

order fulfillment afterimprovement

-22%just

ERP

-22%FIRM A FIRM B

inventory level afterimprovement

-19%just

ERP

53%FIRM A FIRM B

inventory turnover afterimprovement

46%just

ERP

Mobilize Your Workforce

by Mobilizing ERP

BYOD has already mobilized business processes, but you don’t know it.End users are bringing their own devices whether you sanction it or not.

97% of end users bring their own

devices to work regardless of a BYOD

policy.

Save over $45,000 when you complete the project using the Info-Tech project blueprint.

Productivity improvements

Process automation

There are 3 main areas where mobile ERP drives savings:

But organizations often stop optimizing their ERP systems once mobile implementation is complete.This is contrary to the fact that over 70% of organizations state that their main reason for implementing ERP is to optimize their business processes.

%0

80

Stream lining efficiencies (maximum efficiency)

Provide your company with a competitive advantage

Consolidate multiple resources (systems, people, processes)

Change in business model (delivery of new product or service)

High

Medium

Low

Primary drivers for ERP

investment

10%reduction in frequency of service or product delivery delays

10%reduction in error rates.

15%improvement in cycle times

A 2009 WASET*

survey indicates that

ERP

implementation and process optimization yields greater savings than just

ERP.

*World Academy of Science and Technology

Mobile ERP is a form of process optimization. Optimizing business processes leads to:

Determine if you should pursue mobile

ERPPart 1 of the Mobile

ERP Opportunity Assessment Tool

will determine whether you should pursue mobile ERP

based on your:Organization’s enterprise goals according to

COBIT5®

Business processesManagement team’s level of mobility

Step 1:

Relevance Primary Enterprise Goal

Secondary Enterprise Goal

Relevance Rating

Opportunity Increase in Productivity

Decision-Making Time

Process Automation

Mobility Current Use of Mobile Technology

Need for Persistent Data

Off-Site Workers

Satisfaction IT Department

Business Stakeholders

End Users

What business process is ideal for your “one killer

application”?

CRM

app 31%

Other 31%

Approvals 10%

What the indices consist of:

Step 2: Determine a course of action – build or buy

Part 2 of the Mobile ERP Opportunity Assessment Tool will

determine how you should pursue mobile ERP based on your

mobile development maturity level and your ERP’s current

capabilities. The Mobile

ERP

Opportunity Assessment tool will assess your mobile development’s people, processes, and technology in the areas of:

Requirements GatheringDevelopmentTesting Maintenance

Your

ERP

system’s people, processes, and technology will also be graded using an A-F grading scale.

Part 3 of the Mobile ERP Opportunity Assessment Tool will help you build the business

case for mobile ERP. The tool focuses on quantifying the benefits in the 3 key areas of:

Process Automation

Complete the use casesStep 4:

Use the Info-Tech Mobile ERP Use Case and Requirements Gathering Template to guide

you through the requirements gathering process. Remember to develop use cases for both knowledge and process workers.

Data Flow Requirements

Security Requirements

Enterprise Mobility

Management Requirements

Form Factor Requirements

Application Type Requirements

Development Platform

Requirements

User Interface Requirements

79%of users will abandon an app after two failed attempts

62% 47% 40% 37%

Crash or Error

Slow Load Times

Doesn’t Start

App is Confusing

Properly gathered requirements will ensure the application is successful. You can only fail twice before end users resist future use.

Build the business case and sell the project

Step 3:

We will also provide guidance on the typical costs of developing mobile applications in the areas of:

Design - $11,000 per business process

Development - $25,000 per business process

Testing - $11,000 per business process

Maintenance - $5,000 per business process

per year

+ Consumable Materials + Reduction in Labor

Reduction in Inventory+ Inventory Carrying Cost Savings+Reduction in Defects+ Reduction in Service Delays+

1

2

3

Development - $25,000 per business process

Build the project planStep 5: Building the project plan requires some understanding of the 4 options suggested in the Mobile

ERP Opportunity Assessment Tool.

The Mobile ERP project blueprint will also discuss best practices for key mobile

ERP

considerations. Such considerations include:Option 1: Develop your own mobile

ERP

applicationOption 2: Purchase a mobile

ERP

bolt-on from your vendorOption 3 & 4: Use third parties to

assist with mobile ERP

Interruption Testing

Connectivity Testing

Usability Testing

Future Maintenance

Understand the Correlations between Mobile

ERP

Usage and Process

KPI

sYou can then use the Info-Tech Project Request Template and Comprehensive Business Case Template to begin the project.

Step 6: Validate the implementation plan

Complete your project with some implementation best practices.1. Determine if you need to deploy an Enterprise Application Store

One App Many AppsFrequency of Updates

Require Constant User Updates

Highly Sensitive Information

Global Pressure

Strict User Interface Standards

2. Build a communication plan to ease end-user anxiety. Remember to communicate early and communicate often.

3. Train end users with

ERP

best practice training methods.

4. Document the how to execute the mobile business process using the Info-Tech Process Based Documentation Template.

Build or Buy

Intranet Status Updates

Make the case for Mobile

ERP Surveys, Emails and Meetings

Gather Requirements Workshops

Deploy andTrain

Training Sessions

Sandboxing using beta application

Classroom training

Screenshots of the application

Checklists Business Process Maps

Mobility isn’t about shiny new toys, it’s about empowering your workforceAs an

ERP Applications Manager you have wondered

how the proliferation of consumer mobile technology can be leveraged to optimize your

ERP system.

YYour mobile field force is burdened with manual, paper-based processes that impact your ability to optimize mobility in general. You are also wondering if mobile is right for you and, if it is, how lockmature does your mobile development capability need to be? You also need help building the business case and quantifying the savings from mobile ERP. Last, you must know that when the project is complete you have added strategy value to your organization.