BUSSINES ARCHITECTURE DESIGN IN CEMENT COMPANIES

WITH TOGAF ADM APPROACH

Afif Nugraha 1
1
Department Informatics, Information System Study Program, Faculty Of Industrial Engineering, National
Institute Of Technology
P.H.H Mustofa st. 23, Neglasari, Cibeunying Kaler, Bandung, West Java 40124
afifnugraha972@Gmail.com

Abstract. PT. X is one of the companies providing cement located in South Kalimantan, Tanjung. This
company was only established in mid-2016. The company already has an information system that is used to
assist its business activities, but the existing information system has not been used to the maximum and there
has been a place of fraud with customers.
In this study, the author is encouraged to plan the making of information systems that can support the overall
business process and that can make the company can compete with other companies. By planning an
Enterprise Architecture framework and using the TOGAF ADM method. PT. X will create a new system and
business process in the company.
Keywords: Bussiness Process, Planning, Information System, TOGAF.

1. Introduction
PT. X is a company providing cement products. This company has implemented technology in several business
processes, but has not run optimally. This is because there is no harmony between the technology used and business
needs. Therefore, it is necessary to define enterprise architecture to improve data integration capabilities between
parts of the organization. Enterprise architecture is a description of the stakeholder mission which includes
information, functionality / usability, organizational location and performance parameters.
In addition, enterprise architecture is also expected to be able to manage complex systems and can align the
business and information technology that will be invested. One of the frameworks that can be used to build and
manage and implement enterprise architecture is TOGAF (The Open Group Architecture Framework).

2. Literature Review
Enterprise architecture was introduced in the 1980s which started from problems that occurred in the system
architecture. Problems that occur recognize the scope of the design and the level of complexity in the
implementation of information systems that are increasing and widespread, so it takes a logic (architecture) that can
control and define interfaces by integrating all the components in the system.

Enterprise Architecture is a picture of the stakeholders' vision and mission, whether in the form of information,
functionality / usability, organizational location and performance measures aimed at developing a system or set of
systems. EA is a method used to design and realize structures, business processes, information systems and
organizational infrastructure.

The advantages of using EA for companies include:

a. More efficient business operations

 Low business operating costs
 Change management costs are lower
 Workforce is more flexible
 Increasing business is more productive

b. More efficient IT operations

 Low software development costs

 It's easy to upgrade and exchange system components
  And increasing application portability

3. Research Methods
TOGAF Architecture Development Method (ADM) First appeared in 1995 (v. 1) to the present (February 2,
2011 v. 9.1) Consisting of methods and components to assess, create, use and maintain a company's
architecture.

All of these activities are carried out in a repetitive and ongoing cycle, which enables organizations to
conduct controlled enterprise transformation in response to business goals and opportunities.

Figure 1: TOGAF ADM

The phase include:

a. The Preliminary phase describes the stages in the design process by making a framework in the form
of a vision architecture and also the principles of architecture in the form of business processes,
application data and technology.

b. Phase A: Architetcure Vision describes the initial phase of the architecture development cycle which
contains an overview of the boundaries of architectural design by explaining scope, boundaries of
architectural design, by defining the proposed architectural vision.

c. Phase B: Business Architecture explains the development of business architecture to support an

agreed architectural vision.

d. Phase C: Information System Architecture explains how the development of an information system
architecture, with more emphasis on the needs of an application that has been planned to support the
vision of architecture.

e. Phase D: Technology Architects, describes the technology to be built, on a project by first

determining technology candidates to support the agreed architectural vision.

f. Phase E: Opportunity & Solution, at this stage emphasizes more on initial implementation planning,
including business architecture, data, applications and technology described in the previous phase.

g. Phase F: Migration Planning, evaluates the migration plan and plans for implementation of an IS.
 h. Phase G: Implementation Governance, provides management of an architecture for implementation,
including management of organizationsinformation systems and architecture with the aim of
formulating recommendations from each project implemented.

i. Phase H: architeture Change Management, includes compiling and creating procedures to manage
changes to the new architecture, with the aim of establishing a change management process.

j. Requirement Management, defines the needs needed for the cycle / phase in TOGAF ADM.

4. Analysis
A. The preliminary phase

After conducting an analysis based on interviews with companies, it is found that the following are
important processes. the core is critical for the running of the company:

a. Marketing process.

b. Inbound & outbound logistics process.

c. Financial process.

d. Financial process.

e. Accounting process.

f. Human Resource process.

B. Phase A: Architetcure Vision

The architecture principle determines basic general rules and guidelines in designing an architecure
enterprise, this principle is a consensus between management requirements for designing enterprise
architecture and company business. The following are architectural principles which are divided into
4 parts in designing this architectural enterprise:

a. Business Principle

1. Increase consumer satisfaction to the highest stage.

2. Fast and responsive in all business events that occur.

3. Providing facilities to improve the quality of HR performance.

4. Maximizing the opportunities and advantages of the company.

5. Flexibility to the business market.

6. Providing the right business strategy to support every existing business unit

b. Data Principle.

1. Data is an important asset of the company.

2. Data can be used by anyone to be used in business interests.

3. Data security must be maintained.

4. Data accuracy must be trusted.

 c. Application Principle

1. The application must be easy to operate.

2. Applications must be flexible, can be run on various platform.

d. Technology Principle

1. Technology must be interoperability.

2. Technology must be reliable in its capabilities.

C. Phase B : Bussiness Architecture

This stage explains how IT (Information Technology) needs for the entire organization are carried
out by mapping the business architecture of the company. The purpose of this mapping is to get a
picture and consensus between IT and business needs at a later stage. The following are business
processes that are critical for the company today:
1. Order & Purchase orders from the process of ordering, approval, purchase orders and
shipping of goods.
2. Inbound & outbound logistics consist of the process of receipt of goods, quality check, and
delivery of goods.
3. Finance consists of collection of accounts receivable, and employee payments.
4. Accounting consists of the process of collecting documents and accounting reports.
5. Human Resource consists of recruitment, recording attendance lists, and payroll.

D. Phase C : Information System Architecture

This stage is used to define the IT needs or information technology (software and hardware) of the company
against the business and define information systems including the data architecture and application architecture
that will be designed and used later. Application architecture that will be designed in this enterprise
architecture. Consists of 5 systems:
1. Information system for inbound & outbound logistics.
2. Accounting information systems & reports.
3. Marketing information system.
4. Financial information systems.
5. Human Resourse information system.

E. Phase D : Technology Architecture

At this stage the design of the technological architecture is needed to support the previously designed system.

Figure 2: How To SMS Gateway Work

Information:
o SIG : Warehouse Information System.
o SIIOL : Inbound & Outbound logistics system.
o SIAL : Accounting & Report Information System.
o SIM : marketing information system.
o SIK : Financial information system.
o SHIR : Human Resourse information system.
o SIP : Production information system.

F. Phase E – Opportunities and Solution

At this stage, a comparison of the benefits of enterprise architecture is designed with the current conditions of
the company Figure 3, Figure 4, Figure 5).
From the results obtained the most striking comparison to the new system and this old system is that all
information systems in this new system will be integrated with each other, where this will facilitate data
transactions that occur in every business activity that occurs.

Figure 3: Gap information System Architecture

Figure 4: Gap Technology Architecture

Figure 5: Gap Business Architecture

G. Phase F : Migration Planning

Figure 6 outlines the planned technical stages of the migration of the old system to the new system.
When migration is carried out there may be risks that affect the company's business to use the new
system.
Figure 7 contains the formulation of possible risks and risk solutions when the old system migration
plan is carried out.
 Figure 6: System Mingration Plan

Figure 7: Impact Analysis

H. Phase G : Implementation Governance

The best recommendation given for organizational governance in the plan to implement this new system is to
recruit a team of experts in information technology who are experienced from outside the company to
implement this new system since there is no company information technology division in the company.
This recommendation is based on the reasons for effectiveness, where companies do not have to bother in
recruiting expert workers and then form IT divisions within the company.
Recommended technology governance is:

1. Each division is placed in a single PC and an information system is applied based on their respective
functions.
2. On the PC Director, can access all information system functions
3. Database server, router / modem is placed in the director's room, to maintain data security.

I. Phase H : Change Management

Change management from each process is carried out by testing and training if needed, which is intended for
the process of adaptation and looking for weaknesses / errors in the information system.
These stages of testing / training require the full support of each company organization that deals with
(marketing, accounting, human resources, production, directors, inbound & outbound logistics, finance,
warehousing).
The implementation of change management is clarified in the figure 8.
 Figure 7: Change Management

5. Conclusion
5.1 Conclusions from the results of the enterprise

architecture design found that :

1. Designing enterprise architecture using TOGAF provides the right tools in designing
enterprise enterprise architecture, because TOGAF provides a flexible framework and in
designing enterprise architecture.
2. The design results are in the form of marketing information systems, production information systems,
inbound & outbound logistics information systems, financial information systems, accounting
information systems, warehousing information systems, and human resource information systems.
This information system has been designed as well as possible with various features that can help
companies achieve their goals.