250 likes | 533 Views
IEEM 5352 E-Enterprise Integration. Enterprise Process Modeling Concept and Architecture of Integrated Information System. Dr. Amy Trappey. Architecture of Integrated Information Systems. Framework concept to describe enterprises and application system development
E N D
IEEM 5352E-Enterprise Integration Enterprise Process Modeling Concept and Architecture of Integrated Information System Dr. Amy Trappey IEEM, NTHU
Architecture of Integrated Information Systems • Framework concept to describe enterprises and application system development • Focused on business processes IEEM, NTHU
Enterprise Process Modeling Concept • The concept creates a guideline for developing, optimizing and implementing integrated application systems. Meantime, it shows business administration specialists how to view, analyze, document and implement information systems. IEEM, NTHU
Why an Enterprise need a Framework for Integrated Information Systems • Business software solutions comprise modules for accounting, purchasing, sales, finance, production planning, etc (with a high degree of complexity). Many corporate and external business partners are involved in the implementation of Information Systems. This becomes apparent in light of seamlessly integrated data processing, where data is shared by multiple applications. • For example -- CIM in manufacturing companies, IS-supported merchandise management systems for retailers, electronic banking in financial institutions, IS-oriented concepts implemented in enterprises. • 4M Modules – Money (Accounting, Finance, ..); Man (HR); Manufacturing (Procurement, Production, …); Marketing (Sales, Distribution, …) IEEM, NTHU
“Real World”: The actual situation of the company Problem Define the requirements: Analyze “as-is” and design “to-be” Business concept Design specification: “Translate” into data structures, hardware, ... IT Concept Technical implementation: Create physical hardware structure, ... Implementation Information technology “Enablers”: PC’s, networks, standards, databases, ... IEEM, NTHU
Business Administration Issue Information Technology Organization Effort vs. Software Effort 5:1 User’s target profile of concept Requirements Definition (Semantic Models) Reconciling target concept and system solution Design Specification Implementation Description Profile of traditional standard software solution IEEM, NTHU
Information Technology Reduce Organization Effort Business Administration Issue User’s target profile of concept Reducing time and effort by using reference models Requirements Definition (Semantic Models) Modeling documentation of standard software solution (SSS) for reconciling with target concept Tool-supported reconciling of target concept with system solution Design Specification Automatic customizing of standard solution Implementation Description Profile of model-based standard software solution IEEM, NTHU
Key Functionality • Offers a framework (architecture) to completely describe standard software solutions (SSS). • Integrates the most suitable methods for modeling information systems (IS) into the architecture, develops methods for describing business processes. • Provides reference models as tools for the administration of application know-how, for modeling and analyzing system requirements. IEEM, NTHU
Key Functionality (cont.) • Industry-specific reference model for specific business processes (order management process, procurement process, customer service process, etc) • For example, SAP (for electronic industry) procurement process reference model. • Leveraging SSS, the business engineering tool(s) provide architectures for managing business processes. Using workflow systems, it is loosely linked with software “building blocks” (business objects). modules IEEM, NTHU
Key Functionality (cont.) • You’re involved in procurement process. You will have a “procurement” workflow management system that you need to comply with. • For example, in your flow, you need to take care of 3 procurement approval tasks. • Provides the framework for describing the assembly of software components (resulting in business IS) which are ideal for configuring workflow systems, generating screens and determining parameters for applications. IEEM, NTHU
Basic Business Process ModelThe Initial Business Process Model • Responsible entities and their relationship: organization, interaction • Function flow: function, organization, function flow and organization flow • Output flow • Information flow: information services objects and other information objects • Consolidated business process model IEEM, NTHU
Example of Business Process: Order Confirmation訂單確認 Productivity Customer Order Receive order Order confirm Order tracking Prepare for order confirmation Production planning Department Staff Process/function User Organization Event Status Information source/DB IEEM, NTHU
ARIS House of Business Engineering (HOBE) IEEM, NTHU
HOBE - Linkages of Views Manage- ment Organization View Sales Materials manage- ment Disposition Sales Request received Sales processing Request Offer Request processing Offer processing Sales Request processing Request Credit- worthiness check Request processed Customer Determination of delivery date Offer processing Data View Control View Function View IEEM, NTHU
Organization View IEEM, NTHU
Chief Administration Administrator Medical Pharmacy Accounting Physical Medical Purchasing Services Plant Records Chief MR Manager Purchasing Chief Doctor Controller Manager Pharmacist Facility Registrar Manager Internal Medicine Surgery Surgical IM Doctor IM Nurse Surgeon Nurse Organization View Example IEEM, NTHU
Order Handling Order Preparation Order Entry Order Processing Shipping Reservation Order Confirmation Invoicing Inventory Reservation Production Schedule Reservation Hierarchical Diagram of Function View IEEM, NTHU
Function Flow Example administrator plan hospital order approval supplies payment supplies patient patient plan surgery evaluation registration perform patient surgery payment dispense medicine IEEM, NTHU
Entity Definition of Data View IEEM, NTHU
Control View - Process Chain Diagram IEEM, NTHU
eEPC Example IEEM, NTHU
Events initiate functions Functions generate events Order tracking Feedback received Customer Orderreceived Confirm customer order Order confirmation created Production plan created Production planning IEEM, NTHU
Data are processed in functions Production data Customer data Order tracking Feedback received Customer Orderreceived Confirm customer order Order confirmation created Resources Production plan created Production planning IEEM, NTHU
Employees are in charge of functions Production data Miller Production Customer data Order tracking Feedback received Customer Orderreceived Confirm customer order Order confirmation created Resources Smith Sales Production plan created Production planning Production scheduling Meyer IEEM, NTHU
Reducing the complexity of business processes by creating different views Data View Environment data . . . Event Function Event Function Function View Org. Unit Employee Organization View IEEM, NTHU