WHAT

N ERP?
ENTERPRISE RESOURCE PLANNING (ERP)
ERP is a process by which a company manages and integrates the important parts of its
business. ERP integrates/consolidates departments such as Engineering, Procurement,
Inventory, Finance and Human Resources. Combines all databases across departments
in to a single database that can be accessed by all employees. ERP automates the
tasks in performing a business process.

Few benefit of ERP

 ERP eliminates repetitive processes
 Automatic and coherent workflow from one department/function to another, to
ensure a smooth transition and quicker completion of processes.
 All information is now located in a single location. Data is also kept consistent and
up-to-date.
 Makes reporting easier and more customizable.
 Very Transparent
 Security: ERP systems are more secure as centralized security policies can be
applied to them. All the transactions happening via the ERP systems can be
transparent

Evaluation and Selection of ERP

FHSK carefully evaluated three ERP Solutions (SAP-All in One, Sidat Hyder- Suite of
Application Software-ERP (Oracle Based) & Microsoft Dynamics AX) and on the basis
of following reasons/features, FHSK concluded that Microsoft Dynamics AX could be a
better choice for Fazaia Housing Scheme Karachi.

 User Friendly/Ease of use because it's Graphic User Interface is same like other
Microsoft Software/Technology.
 Shorter Implementation time than other competitors.
 Built in Client Access License
 Total Cost of Ownership: All Microsoft Dynamics AX functionality is included in
one License.
 Dynamics AX has low cost of implementation as that of SAP (which has the
highest). Just implementation cost of SAP is more than the total cost involves in
the implementation of Dynamics AX (including Software License Cost +
Hardware Cost/Configuration Services + Implementation Cost)
 It has a shorter implementation due to the familiar nature of Microsoft products.
The system also allows users to make changes more rapidly
Client contacts the vendor and gives them an idea of what they are looking for. What
industry are they in? Are they looking for a heavily customized project or for one
following best practices? What modules are they looking for and what do they seek to
benefit out of it?

Service Agreement Signing Cermony

Signing Ceremony was held on August 02, 2016. FHSK’s Managing Director and CEO
of Systems Limited signed the Service Agreement of Microsoft Dynamics AX along with
Work Order and Non-Disclosure Agreement

Implementation of ERP

Pre Analysis Phase

After getting a basic understanding of the requirements, the implementation

partner selects the SME (subject-matter expert) with the best techno-functional
knowledge for the job.
In this phase Consultants gathered the requirements by conducting the separate
sessions for Human Resources, Engineering, Finance and Supply Chain.
Each session lasted for three hours.

Analysis Phase
This consultant then will go to the client’s business and conduct an analysis, an analysis
to determine the current state of the business & its processes vs. what its optimal
situation would be with the proper ERP software in place. This will be a very detailed
report outlining the structure of the company, how many employees they have, what
their departments are, who will be users on the system, who sees what information, and
so on. Customization points will also be identified. The end result of this will be a
Functional Requirements Document (FRD).

Functional Conference
Project Kick Fit Gap
Room Pilot
Off Meeting Document Analysis
(CRP)
Analysis Phase
Functional Requirement Gathering
Start Data/Doc Collection, Share Engagement Plan
Requirements Workshop

Functional Require Document (FRD)

The Functional Requirements Document (FRD) is a formal statement of an application’s
functional requirements. It serves the same purpose as a contract. Here, the developers
agree to provide the capabilities specified. The client agrees to find the product
satisfactory if it provides the capabilities specified in the FRD.

CRP (Conference Room Pilots)

Conference Room Pilots (CRPs) are a great way to give end users hands-on time with
a system or new software before it is fully developed. A Conference Room Pilot comes
near the very end of the create phase of the project CR when you are wrapping up
requirements and custom development. In CRP we would run separate CRP for each
process category that’s in scope during the implementation. CRPs are often used to
gives users an idea of how the new software will work.
The next immediate step is to review the design feedback and schedule any re-
configuration or new development work right away. Once that is all complete we move
to the deployment phase of the project.

Design Phase
With the FRD prepared, the subject-matter expert will form a team of developers to work
on the project. Now the software customization phase begins. The development team
will configure solution and design customization needed to meet our requirement. They
also will customize it, adding new features to the application. Finally, they’ll integrate it
with other software.

Solution Solution FHSK

Gap Design Design
Solution Design Document (SDD) /Fit Gap Analysis
A Solution Design Document (SDD) includes information about the working
elements of the overall solution, including Dynamics AX standard features (Fits),
Gaps, and integrations. It is important to get the entire solution depicted in a pictorial
representation. The business process modeler in LCS is a great tool with which to put
together the solution design document.

In general cosmetic errors are the spelling mistakes, tab sequence,UI

Anamolies like Font related variance, Background color of specific fields
etc.

Data migration:

In the next ERP implementation phase, the client will begin the process of data
migration, taking their data from existing systems and putting it on their new software.
Access rights, passwords, etc. will start to be put in place here. Integrity checks will also
be done to make sure that the data has been successfully transferred and that there are
no errors.

User acceptance testing:

Now, user acceptance testing (UAT) begins. UAT is the closest thing to real-world tests
before the software is fully deployed. Here, specific users in the company will run tests
with the new software in parallel with their old software, making sure that they achieve
matching results. Once this is done, it will signify that the ERP system or at least certain
parts of it are ready for deployment.

User training:

After the software is ready, user training will begin. In this phase, the full set of
employees that will be using the new ERP system get trained with it. This will involve
the use of manuals/training videos as well as additional training from the vendor.
Training will be done according to specific functions, e.g. for sales, marketing,
accounting, etc. This can occur on-site or offline, depending on the request.

Go live:

Finally, when all is said and done, the project goes live. The new software continues to
run in parallel with the old software for the near future. This gives the business owner
peace of mind and helps confirm that there are no issues.