Kristanti, Tanti (2009) Integrasi Enterprise (Studi Kasus: Yayasan Pendidikan “X"). Jurnal Sistem Informasi, 4 (1). pp. 17-32.
![[img]](http://repository.maranatha.edu/style/images/fileicons/text.png) |
Text
Integrasi Enterprise.pdf - Published Version Download (266Kb) |
Abstract
Ownership of information system at one particular company is expected to support their totally business process, which is not limited to just certain business function but can give benefit to a number of functional areas. This tendency claims to the requirements to integrate the function oriented system in order to make them in line with business process. Yayasan Pendidikan “X” as educational institution has also a number of business function supported by information system. But in its growth, management of the system is conducted independently by a number of organizational unit regardless of business requirement so that emerging “islands” of information system as impact from the system that having stovepipe character and unable to communicate one with another. Enterprise integration is the answer for the problems resulted from the system that has differ platform which cannot give optimal benefit to company. To be able to obtain holistic benefit for business, hence integration project will preceded by analysis activities to capture enterprise present condition. Analysis is aimed to understand “X” current condition (as-is), started with business modeling, defines what is in place today for application system and supporting technology that result information resource catalog. Business modeling by using Porter Chain Value as well as Four Stage Life Cycle Business System Planning is expected to understand functional areas owned by “X” so that yielded architecture that is not impressionable by internal and external changing environment. Information resource catalog analysis constitute integration project that can be manage in an optimal fashion without depending on certain technology. Pursuant to result of analysis from current condition, hence major kinds of data, technology and application for future needs can be determined (to-be). As-is analysis and to-be definition will result some gaps that constituting policies for integration project. Integration is also triggered by business drivers and requirements. The business drivers and requirements which are triggering the needing of integration project in “X” are the needs to increase business efficiency and competitiveness and to improve customer satisfaction for both internal and external customer of “X”. Integration architecture development covers technical, service, information and business process integration. The results from this architecture then are used as basis for integration implementation strategy.
| Item Type: | Article |
|---|---|
| Uncontrolled Keywords: | enterprise integration, enterprise architecture planning. |
| Subjects: | T Technology > T Technology (General) |
| Depositing User: | Perpustakaan Maranatha |
| Date Deposited: | 21 Feb 2012 05:21 |
| Last Modified: | 21 Feb 2012 05:21 |
| URI: | http://repository.maranatha.edu/id/eprint/426 |
Actions (login required)
 |
View Item |
