An overview on

Data conversion and post

implementation support

By-
Preeta
Converting data
 Data conversion is the hub around which the rest of the ERP
implementation turns.
 During initial planning, the budget is created taking into
consideration the extent of the data conversion.
 During the conference room pilot further discoveries are made.
Again adjustments are likely in both business processes and in the
data conversion.
 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.
 The benefits are: less one time fixes after cutover, and data which is
more useful for the enterprise. 
Interface
A user interface is the system by which people (users)
interact with a machine. The user interface includes
hardware (physical) and software (logical)
components.
Input: Allowing the users to manipulate a system, and
Output: Allowing the system to indicate the effects of
the users' manipulation.
Determining format for interface
 Agenda : What is an ERP System? Why implement an ERP
system? How should ERP systems be implemented?
Conclusion.
 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, inventory control, product distribution, to order
tracking in case of SCM.
 Key Characteristics:
Integration of all the information flowing through a company,
business process change adds considerably and risk of
enterprise systems implementation.
Creating an interface
Better Interface Design
 Quickly implement ideas
 Improved sketch-up
 Better communication
 Optimized usability
 Integration of clients
Online interface design
• 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 be
maintained.
 Implementation issues
Company's Point of View
Pacts
• This issue largely influences the business prospects of a company that has successfully
implemented the process of Enterprise Resource Planning.
• Basically it all depends on the company's need and requirements and if ERP 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.
Two Tier Implementation
 In a typical two-tier architecture, the server handles both
application and database duties.
 The users are responsible for presenting the data and passing
user input back to the server.
 There may be multiple servers and the users, distributed across
several types of local and wide area links.
Three Tier Implementation
 In three-tier architectures, the database and application
functions are separated.
 In this scenario, users requests requires two or more network
connections.
 Initially, the user establishes communications with the
application server. The application server then creates a second
connection to the database server.
Security
For most enterprises, ERP security starts with user-
based controls where authorized users log in with a
secure username and password. Enterprises then limit
a user's system access based on their individual,
customized authorization level.
For example, an accounts payable clerk should not
have access to human resources or supply chain
management modules within the ERP system.
Security
The balance between making data available to the
users that need it and denying it from those who
should not have access is not easy to achieve.
Customers, vendors, partners and employees all need
access to the right ERP information at the right time.
These users work on many different systems and
access data from multiple locations.
All have different passwords and authorizations.
Security
Most security initiatives focus on preventing hackers
from attacking a system from the outside, the threat of
security breaches from inside the company are
potentially more dangerous and more likely to occur.
The costs of security are those incurred to achieve
good security (i.e. protect the company’s asset and
comply with legal, contractual and regulatory
requirements) and those incurred when a security
system fails.
Security components
Network security
Workstation security
Database security
Operating system security
Application security
Security failure
Reasons for security breach: fraud, abuse, carelessness.
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.
Testing
Testing is a very important part of development and delivering
a solution.
 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.
 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.
 Once the process of flow diagram then development will be
needed to meet the business needs.
Testing
Once development is completed, the true unit testing
occurs. You must do integrated testing on all possible
scenarios that may come out of the business process
(different variations of the same process).
Once unit testing is approved, then the solution is
ready for use.
 Types of testing
 Black box testing - Tests are based on requirements and
functionality. Internal system design is not considered in this
type of testing.

 White box testing - This testing is based on knowledge of the

internal logic of an application’s code. Also known as Glass
box Testing. Internal software and code working should be
known for this type of testing.
Types of testing
 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.
 Functional testing - This type of testing ignores the internal
parts and focuses on the output as per requirement.
 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.
Post implementation techniques
The following are the three steps to ERP benefits realization.
The focus 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 is selected 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.
Post implementation techniques
2. Identify ongoing training opportunities: There’s always a
decrease 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.
Working with employees to identify process pain points helps
to identify opportunities to improve process and make them
more efficient.
Back office and front office
Back Office
 The back office for any company requires many different layers of
software.
 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
 Front offices have paperwork not inventory. It is possible to
implement lean strategies in the front office.
 Order entry, quoting, scheduling are front-office functions that can
provide an opportunity to create improvement, eliminate waste and
increase profits in business.
Enterprise performance management
Enterprise Performance Management applications are a
modular suite of 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.

 Balance scorecard
 Workflow analytics
 Balanced Scorecard
The balanced scorecard is a strategic planning and management
system that is used extensively in business and industry, government,
and nonprofit organizations 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 organization’s Vision and Strategy
Analytics Workflow
 Analytics workflow describes a series of steps that users work
through to understand the fact, identify the problem area and to
analyse the root cause of problems.
 The design of an analytics workflow reflects the fact finding,
problem identification and decision making processes.
THANK YOU