5 overview of data conversion

8/8/2019 5 Overview of Data Conversion

1/24

By-

Preeta

An overview on

Data conversion and post

implementation support


2/24

Converting datay Data conversion is the hub around which the rest of the ERP implementation

turns.

y During initial planning, the budget is created taking into consideration the

extent of the data conversion.

y During the conference room pilot further discoveries are made. Again

adjustments are likely in both business processes and in the data conversion.

y Even in training a discovery could be made which requires a change in the

data conversion steps. Those being trained have a day-to-day familiarity with

the business processes. Their insight may bring up a consideration not

identified by the power user.y The benefits are: less one time fixes after cutover, and data which is more

useful for the enterprise.


3/24

Interface

y A user interface is the system by which people (users)interact with a machine. The user interface includeshardware (physical) and software (logical) components.

y Input: Allowing the users to manipulate a system, and

y Output: Allowing the system to indicate the effects of theusers' manipulation.


4/24

Determining format for interface

y Agenda : What is an ERP System? Why implement an ERP system?

How should ERP systems be implemented? Conclusion.

y What is an ERP System Definition ERP software is a multi-

module application software that integrates activities across functional

departments, from product planning, parts purchasing, inventorycontrol, product distribution, to order tracking in case of SCM.

y Key Characteristics:

Integration of all the information flowing through a company,

business process change adds considerably and risk of enterprisesystems implementation.


5/24

Creating an interface

Better Interface Design

y Quickly implement ideas

y Improved sketch-up

y Better communicationy Optimized usability

y Integration of clients

y Online interface design


6/24

Process:

step1. Definition and Analysis

step2. Design and prepare various functional reports.

Step3.Build Configure system as per set up document

specifications.

Step4.Test data compilation and testing of systems.

Conclusion: ERP systems provide a mechanism for implementing

systems where a high degree of integration between applications

is required. The Business Case or Value Proposition for

implementation must be outlined to successfully implement - a

proper mix of people, processes and technology should bemaintained.


7/24

Implementation issuesCompany's Point of View

Pacts

This issue largely influences the business prospects of a company that has

successfully implemented the process ofEnterprise Resource Planning.

Basically it all depends on the company's need and requirements and ifERP is their

short term or long term objective.

Personnel

It helps the people to experience change in the business scenario.

The relative success of an ERP process can be measured by the manner in which people adapt to

change.

The quicker the people adapt to ERP, the effect on business process will be greater.

Process

If the business process succumbs to change upon ERP implementation the chances of ERP success

are very high.

The company can aim at profits only if there is a significant change. If the company goes ahead with

the existing process or modifies it only to a negligible effect. The results of ERP won't be reflected

in the business and it will go waste. No business ERP software will help them to achieve the results.


8/24

Two Tier Implementation

y In a typical two-tier architecture, the server handles both application

and database duties.

y The users are responsible for presenting the data and passing user

input back to the server.

y There may be multiple servers and the users, distributed across several

types of local and wide area links.


9/24

Three Tier Implementation

y In three-tier architectures, the database and application functions areseparated.

y In this scenario, users requests requires two or more network

connections.

y Initially, the user establishes communications with the applicationserver. The application server then creates a second connection to the

database server.


10/24

Security

y For most enterprises, ERP security starts with user-basedcontrols where authorized users log in with a secureusername and password. Enterprises then limit a user'ssystem access based on their individual, customizedauthorization level.

y For example, an accounts payable clerk should not haveaccess to human resources or supply chain managementmodules within the ERP system.


11/24

Security

y The balance between making data available to the users thatneed it and denying it from those who should not haveaccess is not easy to achieve.

y Customers, vendors, partners and employees all need access

to the right ERP information at the right time. These userswork on many different systems and access data frommultiple locations.

y All have different passwords and authorizations.


12/24

Security

y Most security initiatives focus on preventing hackers fromattacking a system from the outside, the threat of securitybreaches from inside the company are potentially moredangerous and more likely to occur.

yThe costs of security are those incurred to achieve goodsecurity (i.e. protect the companys asset and comply withlegal, contractual and regulatory requirements) and thoseincurred when a security system fails.


13/24

Security components

y Network security

y Workstation security

y Database security

y

Operating system securityy Application security


14/24

Security failure

y Reasons for security breach: fraud, abuse, carelessness.

y Result of security failure: huge financial losses, distortion or

release of critical data (which may be difficult to detect), and a

slow-down of operations.


15/24

Testing

Testing is a very important part of development and delivering asolution.

y Firstly, you need to develop a test script so that a full end to end test

can be performed and ensure that the results you get are the results

you expect.y In order to do this you need to create a process flow to diagram

according to what the process is. This process is then subjected to

change during the development of the test script and unit testing.

y Once the process of flow diagram then development will be needed to

meet the business needs.


16/24


17/24

Types of testing

y Black box testing -Tests are based on requirements andfunctionality. Internal system design is not considered in this type of

testing.

yWhite box testing -This testing is based on knowledge of theinternal logic of an applications code. Also known as Glass box Testing.

Internal software and code working should be known for this type of

testing.


18/24

Types of testing

y Unit testing -Testing of individual software components or modules.Typically done by the programmer and not by testers, as it requires

detailed knowledge of the internal program design and code.

y Functional testing -This type of testing ignores the internal parts

and focuses on the output as per requirement.y Acceptance testing -Normally this type of testing is done to verify

if system meets the customer specified requirements or not. User or

customer do this testing to determine whether to accept application or

not.


19/24

Post implementation techniques

The following are the three steps to ERP benefits realization. Thefocus is to leverage the investment made in ERP technology to realize

a strong return on investment:

1. Baseline and post-go-live performance measures: Every ERP

project should have a solid business case well before the system isselected or implemented. However, the only way to understand the

level of ERP business benefits is to measure performance before and

after go-live This will help identify areas of under-performance and

opportunities for ongoing improvement.


20/24

Post implementation techniques

2. Identify ongoing training opportunities: Theres always adecrease in productivity after go-live. The key is to minimize this drop

and eventually be more productive than it was before ERP.

3.Identify opportunities to improve business: There are always

process inefficiencies and breakdowns that can be improved. Workingwith employees to identify process pain points helps to identify

opportunities to improve process and make them more efficient.


21/24

Back office and front office

Back Office

y The back office for any company requires many different layers of software.

y These systems go by names like customer relationship management (CRM)

and enterprise resource planning (ERP), but they're really just a carefully

crafted collection of database tables with a set of routine.

Front Office

y Front offices have paperwork not inventory. It is possible to implement lean

strategies in the front office.

y Order entry, quoting, scheduling are front-office functions that can providean opportunity to create improvement, eliminate waste and increase profits

in business.


22/24

Enterprise performance management

Enterprise Performance Management applications are a modular suiteof integrated applications that support a broad range of strategic and

financial performance management processes and enable management

excellence. This comprehensive, market-leading suite drives profitable

growth by delivering predictable results, improving transparency and

compliance and increasing business alignment.

y Balance scorecard

y Workflow analytics


23/24

y Balanced Scorecard

The balanced scorecard is a strategic planning and management system that is

used extensively in business and industry, government, and nonprofitorganizations worldwide to align business activities to the vision and strategy

of the organization, improve internal and external communications and

monitor organization performance against strategic goals.

Why Implement a Balanced Scorecard?

i. Increase focus on strategy and results.

ii. Focus on the drivers of future performance.

iii. Improve communication of the organizations Vision and Strategy

AnalyticsWorkflow

y Analytics workflow describes a series of steps that users work through tounderstand the fact, identify the problem area and to analyse the root cause

of problems.

y The design of an analytics workflow reflects the fact finding, problem

identification and decision making processes.


24/24

THANK YOU

5 overview of data conversion

Documents