Project implementation of Industrial & Financial

Systems (IFS7.5)

A PROJECT REPORT

Submitted in partial fulfilment of the Requirement for the award of the degree
Of
BACHELOR OF TECHNOLOGY (B.Tech)

Submitted by

Syed Junaid Javed

159102141

8th Semester, B-Tech, Information Technology

Information Technology

MANIPAL UNIVERSITY JAIPUR

JAIPUR-303007
RAJASTHAN, INDIA

May, 2019

1
 DEPARTMENT OF INFORMATION TECHNOLOGY, SCHOOL OF
COMPUTING AND IT
MANIPAL UNIVERSITY JAIPUR

Date: 20th May, 2019

CERTIFICATE

This is to certify that the project titled PROJECT TITLE is a record of the bonafide Work
done by SYED JUNAID JAVED (159102141) submitted in partial fulfilment of the
Requirements for the award of the Degree of Bachelor of Technology (B.Tech) in
(Discipline) of Manipal University Jaipur, during the academic year 2018-19.

Mr. ANKIT MUNDRA

Project Guide, Dept of (Information Technology)
Manipal University Jaipur

Dr. PANKAJ VYAS

HOD, Dept of (Information Technology)
Manipal University Jaipur

2
ACKNOWLEDGMENTS

In preparation of my assignment, I had to take the help and guidance of some respected persons, who
deserve my deepest gratitude. As the completion of this assignment gave me much pleasure, I would like
to show my gratitude Mr. Ankit Mundra my Mentor, on Manipal University Jaipur for giving me a good
guidelines for assignment throughout numerous consultations. I would also like to expand my gratitude to
all those who have directly and indirectly guided me in writing this assignment.

In addition, a thank Mr. Basava who introduced me to the Methodology of work, and whose passion for the
project and the workings of it. With guidance and mentoring me through the project throughout my
internship.

I would like to thank Aquagreen Engineering Management Private Ltd. For giving me this opportunity to
learn and grow and putting faith in me and my true potential.

I am thankful to the HR team for guiding me from the first day of my internship and introducing me to this
opportunity.

3
ABSTRACT
IFS develops and delivers enterprise software for customers around the world who manufacture and
distribute goods, maintain assets, and manage service-focused operations. And IFS Applications is capable
of delivering more than just ERP. It has native functionality for enterprise project management
(EPM), enterprise asset management (EAM) and service management. The application can be
configured for a variety of settings including but not limited to discrete manufacturing, process
manufacturing, multi-mode manufacturing, construction and engineering, and esoteric and
demanding settings like multi-mode manufacturing, aerospace and defense, engineer, procure
construct (EPC) and offshore oil and gas drilling. It is in these demanding settings that combine
elements of manufacturing, project management and asset management that IFS Applications is
without peer as an ERP solution.

The Implementation methodology is divided into five phases. Initial Phase, Confirm Prototype Phase,
Establish Solution Phase, Implement Solution Phase, Go-Live Phase. Further, a critical factor in the success
of any project is a clear delineation of the roles and responsibilities of the participants. The implementation
of an ERP system touches virtually all aspects of a business. Throughout the implementation, many critical
decisions will be made based on the needs of the enterprise. To support the implementation process, a
clearly defined team of resources from the customer and IFS will be assigned to the project to lead different
aspects of the project.

There are various functions and features to the software. The software connects all the departments of the
organization. Rather than keeping separate excel sheets, this software interlinks all the information within
the respective departments and the work flow of the information including the initial phase when the data
is in raw form to shaping it to a usable information. IFS manages the flow of data within the organization.
The features allow the data to be shaped in various visualizations like Ms Word and Excel sheets by directly
converting the raw data into information.

The software runs on and supports BO Crystal Reports XI, 2008, 2011, Oracle Sql developer, Tableau
Desktop & Server, OBIEE11g Steven Software (CRD SEVEN).
The Crystal reports and tableau desktop make this software unique as these features make the visualization
of data more readable and understandable. As from the point of view of business analytics, it lets the
management perceive a strong representation of the order of work and helps the management take more
firm decisions.

4
 LIST OF FIGURES
Fig no. Content Page No
1.1 IFS Technology and architecture 2
2.1 ERP modules 8
2.2 Recovery Catalog and Maintenance overview 9
2.2.1 IFS Foundation1 contains the definition and technology of IFS 11
Service-Oriented Component Architecture, tools to support the full
lifecycle, and common application components.
2.2.2 Service oriented architecture and implementation 12
2.2.3 IFS Service-Oriented Component Architecture is divided in to three 13
main tiers, with the business logic available through access providers
to IFS user interfaces and custom interfaces.
2.2.4 User communicate through Http(s) to the web and application 14
servers, which in turn access the database instance through JDBC.
2.2.5 Web integration 15
2.2.6 Integrating processes and data flows (web services) 16
3.1 The overall network between Client and Data Base 17
3.1.1 IFS implementation Methodology Phase depiction 18
3.1.2 Initial Phase 19
3.1.3 Confirmation Prototype Phase 20
3.1.4 PHASE 3: Establish Solution Phase 22
3.1.5 PHASE 4: Implement Solution Phase 25
3.1.6 PHASE 5: Go-Live Phase 27
3.2.1 IFS user and JDBC 28
4.1 Quick Reports explore nodes in the Navigator 29
4.2 Quick Reports Context Menu 30
4.3 Example Quick Report Query dialog 30
4.4 4.4 Example Quick Report Results page with Context Menu 31
4.5 Obtaining Crystal Report 31
4.6 Crystal Report in making 32
5.2.1 Cloud sharing 35
5.2.2 Data sharing from the Web Portal 36

5
 Contents
Page No
Acknowledgement 3
Abstract 4
List Of Figures 5
Chapter 1 INTRODUCTION 1
1.1 Introduction to work done/ Motivation (Overview, Applications & Advantages) 3
1.2 Project Statement / Objectives of the Project 5
1.3 Organization of Report 6
Chapter 2 BACKGROUND MATERIAL 7
2.1 Conceptual Overview (Concepts/ Theory used) 8
2.2 Technologies Involved 10
Chapter 3 METHODOLOGY 17
3.1 Detailed methodology that will be adopted 18
Circuit Layouts / block diagrams 28
3.2

Chapter 4 IMPLEMENTATION 29
Chapter 5 RESULTS AND ANALYSIS 33
Last
CONCLUSIONS & FUTURE SCOPE
Chapter
5.1 Conclusions 34
5.2 Future Scope of Work 36

6
1. Introduction

IFS Applications 10 is a complete solution that helps your business connect to what’s next for your industry,
business and people. Unlike competitive offerings that are too often generic, IFS Applications 10 provides
industry-specific functionality that enables you to create a competitive advantage

IFS Applications is a different kind of enterprise resource planning software (ERP). It is not complex and
rigid like some other ERP suites. Rather, it is designed to rapidly adjust to changes in technology and
business, maximizing enterprise agility.
And IFS Applications is capable of delivering more than just ERP. It has native functionality for enterprise
project management (EPM), enterprise asset management (EAM) and service management. The application
can be configured for a variety of settings including but not limited to discrete manufacturing, process
manufacturing, multi-mode manufacturing, construction and engineering, and esoteric and demanding
settings like multi-mode manufacturing, aerospace and defence, engineer, procure construct (EPC) and
offshore oil and gas drilling. It is in these demanding settings that combine elements of manufacturing,
project management and asset management that IFS Applications is without peer as an ERP solution.

ERP SOFTWARE WITH BEST-IN-CLASS FUNCTIONALITY FOR NUMEROUS AREAS OF THE

BUSINESS

IFS Applications includes all of the functionality you would expect from a tier one ERP software suite, plus
powerful embedded functionality that extends the application into other crucial areas of your business. Here
are a few horizontal offerings that lend best-in-class functionality regardless of their vertical industry or
specific configuration of IFS Applications.
The combined features from data distribution to data analyzation makes the software best in class.

The application not only distributes the data internally but also circulates it in the directed flow from
particular department to department. The local connectivity of the software enables easy and fast access for
Preparation of ‘Quick Reports’.

1
IFS Applications™
MULTI-SITE
COMPLEX MRO
PLANNING

CONSTRAINT- VEHICLE
BASED INFORMATION
SCHEDULING MANAGEMENT
SALES PROCESS
MAKE TO
eINVOICE CONTRACT AUTOMATION
PROJECT
MANAGEMENT INTEGRATION
SERVICE SCHEDULING &
BUDGET ENGINEER TO DEMAND
SELF-SERVICE CONTRACT RESOURCE
MANAGEMENT ORDER PLANNING
MANAGEMENT ALLOCATIONS
MAKE | CONFIGURE
CASH FIELD PREVENTIVE
RECRUITMENT ASSEMBLE INVOICING
FLOW SERVICE MAINTENANCE
TO ORDER
EMPLOYEE
ACCOUNTS CALL BATCH CUSTOMER WORK COLLABORATIVE
DEVELOPMENT &
PAYABLE CENTER PROCESS SCHEDULES ORDER SOLUTIONS
CERTIFICATIONS

ACCOUNTS TRAINING CUSTOMER PROJECT REPETITIVE CUSTOMER OVERALL PERSONAL

EQUIPMENT
RECEIVABLE MANAGEMENT QUOTATION DELIVERY PRODUCTION ORDERS PORTAL
EFFECTIVENESS
ENGINEERING MOBILE &
FIXED EXPENSE SALES SHOP SUPPLIER EQUIPMENT
CHANGE WIRELESS
ASSETS MANAGEMENT CONFIGURATOR ORDER SCHEDULES METERING
MANAGEMENT SERVICES

CONSOLIDATED TIME & ASSET DATA EQUIPMENT EVENT

WEB STORE COSTING PURCHASING
ACCOUNTS ATTENDANCE MANAGEMENT MONITORING MANAGEMENT

SYSTEM
GENERAL PAYROLL SALES & PDM SHOP FLOOR
INVENTORY EQUIPMENT INTEGRATION &
LEDGER ADMINISTRATION MARKETING CONFIGURATION REPORTING
WEB SERVICES

IFS IFS IFS

IFS IFS IFS IFS IFS
HUMAN SALES & BUSINESS
FINANCIALS ENGINEERING MANUFACTURING DISTRIBUTION MAINTENANCE
RESOURCES SERVICE ENABLERS

BUSINESS ACCOUNTING BUSINESS PROJECT PROJECT DOCUMENT QUALITY CASE BUSINESS

PERFORMANCE RULES REPORTING MANAGEMENT REPORTING MANAGEMENT MANAGEMENT MANAGEMENT MODELER

IFS Foundation1—Technology and Architecture

- Fig 1.1 IFS Technology and architecture

2
 1.1. Motivation

The whole purpose of an ERP system is to be able to plan and capture business transactions. The results are
used for forecasting, accounting and reporting. The ERP does this by mirroring the processes of your
company. It is extremely important to check that the out-of-the-box processes included in your future ERP
are well aligned with your business. Maybe not perfectly with your current as-is state, but rather with your
future state.

To do this evaluation on a detailed level can be very demanding and difficult to accomplish as part of a
selection process. One way to work around this is to look closer at a few specific and critical scenarios. This
gives potential vendors a chance to prove their solution where it matters most.

The second step for evaluating functional fit is to speak with companies similar to your own that are
currently using this ERP. Not only will this confirm whether their software is a good fit for your company
– but will also show whether the ERP vendor is knowledgeable about your business and industry.

The advantages associated to the product-

 One Product

IFS Applications is a single, integrated product supporting the management of 4 core processes; Service
and Asset, Manufacturing, Project, and Supply Chain. Combined with our deep industry knowledge and
horizontal solutions such as financials, HR, CRM etc., it is a complete ERP solution for all your business
needs.

 User Productivity

IFS Applications provides an attractive, intuitive and efficient user interface, helping you easily find what
you need to do your job. So you can spend less time managing your software and more time managing your
task at hand.

 Component-Based SOA

IFS Applications is built using the same principles as successful manufacturers—the production and
assembly of components .Service-oriented component architecture you can choose only the business
components you need. And add new ones as you go along

 Built For change

With IFS Applications you stay agile, ready for change and evolution without disrupting the implemented
solution. A strong strategy of building for change includes a number of best practices, including a
commitment to standard technologies and well-known products.

3
The applications for Industrial Financial System (IFS)-

IFS Applications 10 provides one complete solution for global businesses that manufacture and distribute
goods, maintain assets and manage service-focused operations. It is a leading enterprise software solution
that, with its compelling user experience, enables you to define and deliver on your next chapter, whatever
that may be.
Unlike competitive offerings that are too often generic, IFS Applications 10 provides industry-specific
functionality that enables you to create a competitive advantage.
Connect to the future with IFS software that offers:
 Deep industry functionality within a broad suite that also includes financials, human capital
management and customer relationship management.

 A more engaging and enjoyable work experience through IFS Applications 10 provides one
complete solution for global businesses that manufacture and distribute goods, maintain assets and
manage service-focused operations. It is a leading enterprise software solution that, with its
compelling user experience, enables you to define and deliver on your next chapter, whatever that
may be.

 Unlike competitive offerings that are too often generic, IFS Applications 10 provides industry-
specific functionality that enables you to create a competitive advantage.

 Connect to the future with IFS software that offers:

 Deep industry functionality within a broad suite that also includes financials, human capital
management and customer relationship management.

 A more engaging and enjoyable work experience through IFS Aurena, its intuitive user interface
accessible from any device.

 Choice of cloud service models, Software-as-a-Service (SaaS) or IFS Managed Cloud, or running
on-premise.

 Support for global operations and greater transparency in business processes, bringing all parts of
the company closer together.

 IoT technology and real-time data capture for predictive maintenance and service.

 Low cost of ownership, proactive quality management and continuous innovation through a regular
update cadence plus a Layered Application Architecture (LAA)
4
 1.2. Objective of the Project

With large data pouring in everyday from various sources with no end to end connections to study and
optimize the data for beneficial use, this software discretely develops a strong local connection within the
organization connecting all the necessary ends to regulate the data into desired flow while managing and
developing the data into useful information which can be further used for Business Analytics.

With handling the data as the priority followed by making the data suitable for studying by converting them
into appropriate versions of it and other managerial efforts required to put on the information obtained.

The main purpose of my project was to learn the apt features of IFS (7.5) and to learn about the architecture
and data flow. On how is the data maintained and processed for further evaluation for the benefit of the
firm.

The features include Crystal reports and Quick reports which converts data into processed data into excel
sheets and word files.

5
1.3. Organization of Report

 Chapter 1 contains the introduction and motivation to the project developed followed by the
objective of the project.

 Chapter 2 gives brief background concepts that were helpful and used in developing this project.

 Chapter 3 describes the methodology applied while developing this project with flow chart
describing the workflow. It also tells about the general steps and dataset used while development of
the project.

 Chapter 4 tells about the practical work that can be performed by the software with its features. The
phases are explained in lengths.

 Chapter 5 describes the results obtained by the implementation of the software by its various uses
of tools and features

6
2. Background Material

Built using a modern, component-based, Service Oriented Architecture (SOA), IFS Applications is made
up of discrete software objects that can be selected and configured based on your specific business needs.
This frees you from buying software components you don’t need, and allows you to implement software
for immediate needs first. You can add new components step by step as your requirements change and new
technologies emerge. The result is a flexible system that delivers rapid payback and lower overall risk.

Background theory

A 'financial system' is a system that allows the exchange of funds between lenders, investors, and borrowers.
Financial systems operate at national and global levels. They consist of complex, closely related services,
markets, and institutions intended to provide an efficient and regular linkage between investors and
depositors.

Money, credit, and finance are used as medium of exchange in financial systems. They serve as a medium
of known value for which goods and services can be exchanged as an alternative to bartering. A modern
financial system may include banks (public sector or private sector), financial markets, financial
instruments, and financial services. Financial systems allow funds to be allocated, invested, or moved
between economic sectors. They enable individuals and companies to share the associated risks.

Before the Enterprise resource planning the data collected by the firm was individually stored in excel
sheets or MS word files. This type of data collection was highly distorting and confusing. The data being
separate and segregated from each other resulted in time consumption and inaccurate decisions. Thus
introduction of connected information via various platforms was introduced system integrates varied
organizational systems and facilitates error-free transactions and production, thereby enhancing the
organization's efficiency

7
 2.1. Conceptual overview

IFS Service-Oriented Component Architecture is a layered, multi-tier architecture. Each tier has its own job
to do and does it in a standard way with a clear separation from, and interface to, other tiers. Each tier has
its own software objects. These are all derived from a common design model but are implemented using
different technologies to suit their purpose.

- Fig 2.1 ERP modules

With the introduction of ERP modules all the departments of the organization with respect to their data
could be well connected and the information could be processed more efficiently with less and less of errors.
IFS tapped this opportunity and made a single platform where organizations collective information could
be collected and be furnished and be sent to other associating departments for further use and informative
purposes

IFS’ strategy of building for change applies also to standards. As new standards appear, IFS updates its
architecture accordingly. XML, J2EE™, .Net, and web services were little known five years ago. Today
they are all industry standards and integral parts of IFS Applications.

Maintenance overview
8
The recovery catalog is an optional repository containing information on:
 Backup Repository Information (Backup Metadata)
 The physical structure of the target database
 Persistent RMAN configuration settings
 Stored job scripts

This is an overview of recovery catalog creation and maintenance.

The main database is linked with RMAN (recovery manager) which is in addition linked with the main
user. All the work that is saved by the user is saved into the targeted data base. Further the RMAN is linked
to an additional catalog. Thus the new catalog which is newly created.

- Fig 2.2 Recovery Catalog and Maintenance overview

9
 2.2. Technologies involved

IFS Foundation1

IFS Foundation1 is IFS’ strategic packaged architecture platform for component based business
applications. Based on open standards such as XML, UML, BPEL, J2EE and .NET, it includes the
technology and tools to design, develop, deploy, configure, integrate, and administer IFS Applications. IFS
Foundation1 is also the product family name for all things related to IFS technology and architecture. IFS
Foundation1 includes:

• The definition and documentation of IFS Service-Oriented Component Architecture.

• Runtime containers, frameworks required to run and manage an IFS Applications installation. This
includes runtimes for business logic, portals, web, Windows, and mobile clients.

• User interface environment enabling access to IFS Applications from web browsers, PCs, PDAs and
more.

• Tools and routines to manage the full lifecycle of the applications. From solution development,
through installation and configuration, to administration and use of IFS Applications.

• Options that extend the configuration possibilities of the platform. For example, IFS Connect and
IFS Report Designer.

• Common application components and services such as ISO codes, security services, change logging,
event notifications and user collaboration. Everything in IFS Foundation1—from the choice of core
technologies to the functionality in the tools—is optimized for the development of large, scalable,
high-quality business applications.

10
 - Fig 2.2.1 IFS Foundation1 contains the definition and technology of IFS Service-Oriented Component
Architecture, tools to support the full lifecycle, and common application components.

IFS Service-Oriented Component Architecture Components for agility and reliability

IFS uses a combination of process modeling and Unified Modeling Language (UML) object modeling to
design IFS Applications. The process model describes what the application does; the object model describes
the components that make up the application and how they relate to one another.

IFS Service-Oriented Component Architecture combines the proven benefits of components and object
orientation with the agility and ease of use of service oriented architectures (SOA).

Process-oriented enterprise computing relies on SOA to address many of the issues in adapting software to
change in real-life business processes. SOA applications map well to models and language used to describe
real-life processes. In practice, such models as the Business Process Modeling Language (BPML) require
the application to expose service interfaces or to be wrapped behind them. Where SOA promotes software
functionality to be organized around the business service it provides, rather than which object it operates
on, it also becomes easier to add and change process-related business rules in an SOA application.

Although SOA addresses many challenges related to developing agile business software, it suffers from
some of the drawbacks that were solved by object orientation. For example, SOA applications generally
have more redundant implementations, resulting in quality risks and more difficult maintenance. The many
layers of indirection and relatively low level of maturity of development tools mean that performance can
suffer—both when using the systems and during development. IFS has chosen to combine the strengths of
both object orientation and SOA in IFS Service-Oriented Component Architecture. An object-oriented core
provides the performance, reliability, and quality required in business applications. Combined with a service
layer and hundreds of ready-to-use SOA services this makes it easy to integrate IFS Applications with other
business systems, customers, and partners.

11
 -Fig 2.2.2 Service oriented architecture and implementation

Multitier architecture

IFS Service-Oriented Component Architecture is a layered, multitier architecture. Each tier has its own job
to do and does it in a standard way with a clear separation from, and interface to, other tiers. Each tier has
its own software objects. These are all derived from a common design model and implemented with
technologies to suit their purpose.

12
 -Fig 2.2.3 IFS Service-Oriented Component Architecture is divided in to three main tiers, with
the business logic available through access providers to IFS user interfaces and custom
interfaces.

The fully normalized data storage tier is based on the relational database model. This is the prevalent storage
technology for today and the foreseeable future. The database server is configured so that no data can be
accessed or modified except through the business logic. This guarantees data integrity and prevents “back-
door” modification.

The business logic tier is the heart of the application. It implements business knowledge, functionality, and
processes. This tier is divided into two sub-tiers. The application core sub-tier is a high-performance, object-
oriented implementation of business-object level and activity-level business logic. The composite services
layer is a service-oriented interface and API used for integrations, client access, and process-level logic.

The presentation tier provides interaction with human users and client-side applications and devices. The
same business logic can serve many different types of interfaces, such as web browsers, PDAs, and PCs.
Interfaces in the presentation tier access the functionality of the business logic tier through access providers.

Integration through access providers and IFS Connect

IFS Service-Oriented Component Architecture is an open architecture, allowing other applications to access
information and invoke functionality in IFS Applications. Both the services layer and application core are
exposed to other applications and environments through IFS’ access providers for .Net, COM, Java™, and

13
SOAP. Message-based business process integration is provided through IFS Web Services and the IFS
Connect integration broker.

Deployment view of the architecture

IFS Applications is built using standard tools and technologies. This gives low total cost of ownership
(TCO) and a high degree of freedom in deployment options. IFS supports most platforms, including
Microsoft Windows, major UNIX variants, and Linux. Because each physical tier in the architecture is
separated through standard protocols, it is possible to “mix and match” platforms in a deployment. IFS
Applications can be deployed on anything from a single laptop running all components to multi-server
installations with both database and application servers running in cluster configurations—supporting tens
of thousands of users. The two principal deployment components are the database and the J2EE application
server. The open architecture makes full use of J2EE but avoids proprietary extensions, allowing companies
to deploy on application servers from IBM and Oracle—or go open source with JBoss, Apache, and Linux.
This openness protects against vendor lock-in

-Fig 2.2.4 User communicate through Http(s) to the web and

application servers, which in turn access the database instance
through JDBC.

The database runs both the storage tier and the application core business logic objects. The J2EE application
server runs the services layer business logic objects, the web/portal presentation tier, and integration
services. Both the database and the application server can be run in clustered configurations for extreme
reliability and scalability. IFS Web Client and portals can be deployed in the main application server or in
a separate web application server. A front-end web server such as Microsoft IIS or Apache can also be used
14
as a complement to the application server. Clients access the business logic predominantly by using Http
(or Https using SSL) protocol. This allows easy passage through firewalls, proxies, and other network
infrastructure. Port numbers can be configured. Integrations and customer interfaces access the business
logic through the same access providers as used by IFS Applications clients, and thus use the same
protocols.

Integration, web services

Technology continues to drive a wave of integration. New industry standards enable applications to
communicate and work together. Internal systems are linked to each other, to extranets, and to the Internet.
Business processes are expanding to include multiple organizations in a networked business community.
For applications, integration is about making independently designed software systems work together. IFS
distinguishes between two main categories of integration, driven by different needs. The first category gives
users access to IFS Applications functionality using other presentation tier applications than those supplied
by IFS. A user might want to build an Excel macro that integrates with the financials solution or an Intranet
web page that retrieves certain customer information. The second category is what is usually assumed when
talking about integration in the context of business applications. This refers to sending business documents
and transactions between systems, to and from customers and suppliers. EDI and EAI fall into this category.
IFS supports the first category of integration with IFS Access Providers—allowing integration of IFS
Applications business logic with other clients regardless of the technology with which they are built. The
second category is supported through IFS Web Services and IFS Connect.

- Fig 2.2.5 Web integration

15
Integrating processes and data flows (EDI, web services)

IFS Applications includes a number of services that send or receive information. Some are generic, such as
the reporting framework or replication functionality. Other services, such as order confirmations and
invoices, belong to specific business components. With IFS Applications, all services sending or receiving
information do so using XML natively. This means that IFS Applications is ideally suited to be integrated
with other applications that also use XML and web services technology.

Despite the popularity of web services in newer applications, many systems in use still require other ways
of integration. These are also supported. Other formats (e.g. another XML format or a delimited file) and
different protocols are provided using an integration broker. IFS Applications comes with its own
lightweight integration broker, IFS Connect. Because of the open architecture, IFS Connect can easily be
combined with 3rd party integration brokers, EAI and EDI software. Or the 3rd party broker can be used
on its own, accessing IFS Applications web services directly through SOAP.

-Fig 2.2.6 Integrating processes and data flows (web services)

16
3. Methodology

The methodology is managed within the PMI PMBOK framework, which includes risk management and
progress tracking to ensure the project runs according to plan. Key milestones are adhered to and stake-
holders are kept informed throughout the project.

The use IFS Scope tool to create a visual representation of how your requirements fit into the IFS standard
application. Establishing a firm scope allows us to accelerate the project by ensuring a common
understanding is reached at an early stage. The scope is then confirmed by both parties through prototyping.
Methodology allows organizations to quickly and confidently tackle new challenges and emerging
opportunities, putting them in control of what's next for their business.

The use of Features like Quick reports, Crystal or Adhoc reports and Scheduled reports play a vital role in
the documentation and representation of vast data collected through various commitments and roles by the
firm. IFS play a significant role in the display of data as relevant information.

Network
Oracle
Database

Export
Files

391

- Fig 3.1 The overall network between Client and Data Base

17
 3.1. Detailed methodology

IFS Implementation Methodology is based on many years of experience successfully implementing IFS
software for a wide range of IFS users from single-site operations to multi-site, multi-country companies
with many divisions. Having our IFS employees globally utilize the same IFS Implementation Methodology
has been key to deploying the defined customer solution around the world.

IFS Implementation Methodology is supported by five main phases. These include the following:

• Initiate Project Phase

• Confirm Prototype Phase

• Establish Solution Phase

• Implement Solution Phase

• Go Live Phase

-Fig 3.1.1 IFS implementation Methodology Phase depiction

18
PHASE 1: INITIATE PROJECT PHASE

The Initiate Project Phase aims to achieve a seamless transfer from the sales process and to create a sound
foundation for a successful project. In most cases, the foundation for the project will be built around the
customer specific solution generated from IFS Scope Tool.

-Fig 3.1.2 Initial Phase

During this phase the project management plan is updated and relevant subsidiary plans are established.
Additionally, the technical infrastructure is established and the solution installed. Documentation from the
Initiate Project Phase becomes the baseline against which actual progress can be measured and reported.

19
PHASE 2: CONFIRM PROTOTYPE PHASE

The Confirm Prototype Phase confirms the scope and key business processes of the solution. During the
Confirm Prototype Phase a first prototype of the solution is built and presented. Based on the prototype, the
project confirms that the solution scope and specifications meet the agreed requirements and that the
prototype solution will be the basis for the full IFS solution delivered in Establish Solution Project Phase.

- Fig 3.1.3 Confirmation Prototype Phase

Confirm Prototype key activities

Key activities during the Confirm Prototype Phase include:

 Start up and training: Conduct project kick off and, if agreed, an optional initial training session in
the standard solution.

 Create book of rules: The work starts with a set of workshops defining generic prerequisites for the
solution (customer business, financial and operational steering model, legal and operational
structure) and defining answers to specifically prepared questions within each solution area. The
results and answers are documented in a book of rules that defines the complete set of prerequisites
for the solution.
20
 Specify prototype: The prototype is defined and specified, including end-to-end business processes
and other relevant process scenarios. The customer-unique sample data for the prototype is defined
here.

 Build prototype: IFS builds the first prototype of the solution based on prototype specifications, the
defined solution scope and prerequisites as defined in the book of rules.

 Confirm scope and prototype: IFS runs the IFS solution for specified end-to-end business scenarios
and process scenarios. The customer confirms that the prototype, the refined solution scope and
functional specifications meet the agreed requirements and that the prototype solution will be the
basis for the full solution delivered in the Establish Solution Project Phase. Afterwards, the refined
solution scope is approved and the prototype solution is locked and kept for tracking purposes during
the project.

 Specify functions for development: Objects for development (interfaces, modifications and, if
applicable, configurations and reports) are specified at functional level.

 Define data scope: In this stage, the data scope and objects for migration are defined and the need
for data cleansing and harmonization is analyzed and defined.

21
PHASE 3: ESTABLISH SOLUTION PHASE

The purpose of the Establish Solution Phase is to build and verify the customer-specific solution.
Implementation and rollout of the solution are packaged and prepared.

-Fig 3.1.4 PHASE 3: Establish Solution Phase

Establish Solution Phase key activities-

22
Key activities during the Confirm Prototype Phase include:

APPLICATION SOLUTION, which includes:

 Specify development: Development objects (configurations, reports, interfaces and modifications)

are defined and specified at a technical level.

 Build and test development: Configurations, reports, interfaces and modifications are developed and
functionally tested. Business roles, security and profiles are developed and functionally tested.

 Specify tests: Test scopes for Verify Solution and Solution Acceptance Test are refined. Test
specifications are delivered and test data defined. Test cycles are planned.

 Train teams: Customer solution teams are trained in the solution concept and functions. IFS trains
customer experts in relevant IFS tools.

 Test cycles to verify application solution: The prototype solution is used as a basis for the solution
and copied into the IFS solution test environment. The parameters and test data are set up for the
complete software solution.
 The customer runs sub-process scenarios and verifies that the delivered software solution fulfills
agreed requirements. The software solution is verified in the test environment based on sample data.
Testers are logged on as users with full access to data and functions.

 Verify solution with end-users and migrated data: The customer runs processes and verifies that
business roles, security and profiles are set up correctly and that the processes can be run with
migrated data. The test is verified in the test environment based on migrated data. Testers are logged
on as end-users with restricted access to data and functions and with configured profiles.

MIGRATED DATA SOLUTION, which includes:

 Specify migration: Exporting and cleansing of data from legacy systems is specified. The cut-over
approach is defined.

 Build and test migration: Tools for data export, cleansing and migration to IFS solution are
developed. Data is exported, cleansed and migrated into the IFS solution migration test environment.

 Build production data: Approved basic data is established in the production master environment.

SOLUTION ACCEPTANCE TEST, which includes:

 Specify test: Test is defined and specified.

23
  Set up and migrate data: Data is migrated from the legacy systems into the IFS solution environment
for the Solution Acceptance Test.

 Solution Acceptance Test: The customer verifies that the complete Established solution, on business
process level, fulfills agreed requirements. The solution is verified during workshops where the
customer runs end-to-end business scenarios with migrated data, established business roles, security
and profiles.

CHANGE MANAGEMENT, TRAINING, ROLLOUT, and GOVERNANCE, which includes:

 Specify change and training. Build training material: Change impact analysis is performed and
creates the basis for a change management plan and training plan. Training material is produced and
work instructions are developed.

 Plan and prepare cut-over and governance: Detailed cut-over for go-live and a solution governance
model are defined. For projects with an extensive number of rollouts, the rollout strategy is reviewed
and template project .Management plans and operational plans are created for rollout projects.

24
PHASE 4: IMPLEMENT SOLUTION PHASE

The purpose of the Implement Solution Phase is to rehearse cut-over/go-live and to prepare and train
organization for go-live.

- Fig 3.1.5 PHASE 4: Implement Solution Phase

Implement Solution Phase key activities include:

 Local infrastructure: Local technical infrastructure is established.

 Local cut-over and go-live rehearsal

 Train local super users: Local super users are trained in the solution based on developed training
material. The sessions are used to verify super-users have achieved necessary skills.

 Test local cut-over: Local test cut-over is performed according to cut-over plan.
25
 Operational Readiness Test: The local cut-over is verified during work shops where the customer
super-users run end-to-end business scenarios.

 Change management and training: Planned change management is performed and end-users are
trained in the solution based on developed training material and classroom training sessions
followed by handover to support.

 Go Live Decision: Any remaining open issues are agreed and planned; solution and organizational
readiness are assigned; a go-live decision is taken.

26
PHASE 5: GO-LIVE PHASE

The purpose of the Go-Live Phase is to make the cut-over to the new system as smooth as possible. As the
defined go-live criteria are met, a handover to the support organization takes place. Once all sites are up
and running, project closing procedures commence.

- Fig 3.1.6 PHASE 5: Go-Live Phase

Go Live Phase key activities include:

The Go-Live Phase is the final phase in IFS Implementation Methodology, which the customer cuts over
using the approved solution.

 Go-live: Cut-over is performed according to the cut-over plan and the go-live is performed with end-
user supported.

 Evaluate and close project, hand over solution: Solution is handed over to the governance organization
and the project is evaluated and closed.

IMPLEMENTATION TEAM ROLES & RESPONSIBILITIES

A critical factor in the success of any project is a clear delineation of the roles and responsibilities of the
participants. The implementation of an ERP system touches virtually all aspects of a business. Throughout
the implementation, many critical decisions will be made based on the needs of the enterprise. To support
the implementation process, a clearly defined team of resources from the customer and IFS will be assigned
to the project to lead different aspects of the project.

27
 3.2. Block diagrams

Deployment and platforms

IFS Applications is built using standard tools and technologies. IFS supports most platforms, including Microsoft
Windows, major UNIX variants, and Linux. Because each physical tier in the architecture is separated
through standard protocols, it is possible to "mix and match" platforms in a deployment. IFS Applications
can be deployed on anything from a single laptop running all components for demo purposes, to multi-
server production installations with both database and application servers running in cluster configurations
- supporting tens of thousands of concurrent users.

The two principal deployment components are the database and the J2EE application server.

- Fig 3.2.1 IFS user and JDBC

28
4. Implementation

Quick Report

Quick Reports can be used to print out any information from IFS Applications based on SQL
statements, Crystal Reports etc. When running a Quick Report the result is presented in a
table/overview page. From this page you have the option to export/transfer the information via
an Output Channel or to view it via Quick Chart.

Quick Reports are usually defined by the System Administrator, read about how to create Quick
Reports in the Administration Guide in the Technical Documentation.

- Fig 4.1 Quick Reports explore nodes in the Navigator

29
 -Fig 4.2 Quick Reports Context Menu

-Fig 4.3 Example Quick Report Query dialog

30
 -Fig 4.4 Example Quick Report Results page with Context Menu

Crystal Reports

Crystal Reports is a business intelligence application used to create custom reports from a variety of data
sources. The package includes the major features needed for a business to create a
database reporting environment, such as data access, report design/formatting, report viewing, and
application integration.

- Fig 4.5 Obtaining Crystal Report

31
-Fig 4.6 Crystal Report in making

32
5. Results and Analysis

The Industrial Financial System (IFS) has a great versatility in terms of handling users with different
approaches to their business.

IFS implementation helps in visualizing the data accurately and clearly with the help of its tools and
features. It enhances the power of a data Analyst to give more output with certain raw data by converting it
into important information shaped by the raw data that was entered into the software.

Not only the data visualization but also the inter connectivity of the whole organization can be approached
with this single software and the data can flow easily through the organization as desired with the data being
shaped into usable information.

33
 5.1. Conclusion

At conclusion, we can surely say that the whole concept of one single entity handling all the data with
controlling the direction flow of the data has optimized the industrial analyzation and has brought more
significant points into light by its descriptive tools. Business analytics and been given a prime mount in all
this which furthermore has helped the management take more precise and better decisions.

The software not only is efficient but is also evolving. There is much room for betterment and additional
tools to be implemented to ease the work and gain more output with minimal of work hours.

34
 5.2. Future Scope

At present stage the IFS Managed Cloud is a fully managed service. The software is run in the cloud, in a
highly secure single-tenant (private, not shared) environment that’s fully maintained, updated and
monitored by IFS. The operating system, database, middleware, and the IFS product. Due to the single-
tenant model it is possible to have your unique configuration of the IFS product, including customizations.

Industrial & Financial Systems is adopting a Cloud service approach. The main enterprise to the cloud
feature are-

FOCUS ON INCREASED AND OPTIMIZED SECURITY

Concerns over data breaches, malware threats and regulatory pressures are mandating a more secure, fully
compliant IT system. Cloud software applications are typically better managed and run in the most secure
data centers – and so are less vulnerable.

REAL-TIME ACCESS TO A SINGLE CUSTOMER VIEW

Enterprises delivering services need to meet demanding SLAs. The cloud readily supports field working
and service operations that depend on access to a detailed, real-time view of each customer relationship.

- Fig 5.2.1 Cloud sharing

35
The introduction of Cloud service in the predecessor versions of IFS has made the sensitive information
of the client more easily accessible and safe though out the world.

As relying on IFS, IFS can also be run by another partner or hosting provider working with other cloud or
hosting partners of your choice. For example, combine an IFS subscription license with another provider’s
service to configure the solution you need.

Today, the many participants in the lifecycle of such an asset, from manufacturer to transporter to maintainer
to operator, each have their own disparate systems. Consequently, single picture of the truth when looking
at that asset’s entire lifecycle. Often, these records can be incomplete or still on paper, and communication
between the different participants is often done on paper or even verbally. Lack of standardization leads to
limited traceability and the cost of compliance, if even possible, can be very high.

-Fig 5.2.2 Data sharing from the Web Portal

36