Wirtschaftsinformatik (Subject) / Business Software (Lesson)

BS bei Prof. Schubert

This lesson was created by Irec42.

Learn lesson

back  |  next 1 / 2

• Business Process Modelling Tools (Create Process Models) - Modelling Frameworks - (Process Models) - Attributes - Interdependencies - Modelling Languages
• Business Process Modelling Tools (Administer Process Models) - Persist (database, client-server, multi-user, access rights) - Navigate (model-spanning browse) - Communicate (discussion, evaluation) - Version (track and remember changes) - Basic Analysis
• Business Process Model Analysis - Extract, condens and reuse information contained in a model not visible at first sight - (e.g.: How often is an employee working at order management involved in a process?)
• Business Process Analysis Tools (Search Models) - key figures (e.g. frequencies of occuring objects, cost average, time, ...) - patterns (e.g. model sections that indicate problems / best practices) - behavior (e.g. execution semantic, e.g. "tast A and B always have been executed concurrently")
• Business Process Evaluation Tools - Models specify reality - prescriptive model is to be implemented in reality - descriptive model is supposed to show how reality really looks like
• ERP Modules - Accounting and Finance - HR Management - Marketing and Sales - CRM - SRM - Procurement - Warehouse management/logistics - Material planning/disposition - Production palnning - Project Management - Service - Management Information System (MIS) - Web Shop
• ERP "Checklist" (general) - Characteristics - Products - Technology - Further Criteria - Miscellaneous
• ERP "Checklist" (Characteristics) - System Operation - In-house - Hosting of an independent system by a provider - ASP (shared server and software) - Distribution model of the ERP provider - direct marketing - Distribution partners - Industry Sectors - Trade - Service - Manufacturing
• ERP "Checklist" (Products) - Number of products in the product catalogue/service catalogue - Structure of the products (e.g. bills of material) - Special requirements (e.g. supplements dangerous goods) - Sales type - make-to-stock production - make-to-order production - Production type - Individual production (typical for make-to-order) - series manufacturing (typical for make-to-stock) - Process manufacturing - Lot production - Organization - Single/several production site - Intercompany deliveries - Distributed warehouse locations
• ERP "Checklist" (Further Criteria) - Company Characteristics - Number of users - Size of enterprise (Number of employees) - Number of production sites - Licensing Model - Available budget - Leasing model - One-time purchase of license - Maintenance costs - ASP/SaaS - Open Source
• ERP "Checklist" (Technology) - Architecture - OS - Supported Databases - Programming Languages - Client (Fat/Thin Client) - Possibilities for additional programming - Integration potential - Already implemented business interfaces
• ERP "Checklist" (Miscellaneous) - Scalability - Role concept - Customization - Possibilities for customization - Upgradability - Multi-client capability
• Data in ERP Systems - Three types of data: - Organizational data - Master Data - Transaction Data
• Organizational Data - Defines the organizational structure of the enterprise - Includes Definitions of - Companies (subsidiaries, etc.) - Divisions based on product or geographical hierarchy - sales organization - purchasing organizations - physical facilities - HR organization - Data that rarely changes - Data created as part of the ES configuration process
• Master Data - Define key entities in an organization, for example: - Customers (debitors)/ Suppliers (creditors): - Basic information: name, address, contact info - Financial information: payment terms, methods - Products: - Basic data: description, weight, color, ... - Purchasing data - Sales data - Manufacturing data - Employees - basic demographic data - Personal data - Payroll data - Tax data - Entitlements - Data from different sources can be integrated in a customer order - Data sources: - Master data of receivables - Master data of material - Master data of terms - settings for communications - Control tables (default values)
• Transaction Data - Data that is the outcome of day-to-day business transactions - who, what, when, where, how, how much - Sales orders - Customer, products, quantities, dates and times, location, sales person - Purchase order - Vendor, products, quantities, dates and times, location, sales person, requester - Production schedule - Materials, quantities, facilities, resources, dates and times, locations
• Bill of Materials (BOM) - identifies components needed to make one unit of a product - Multiple levels of BOM - A component may have its own components
• Oder and Procurement Process (Sales Process (Order Processing)) Customer Order -> Sales, Service -> Planning and Disposition -> Procurement -> Purchase Order
• Oder and Procurement Process (Production Process) External Inbound Logistics -> Warehouse Logistics, Raw Materials -> Manufacturing -> Warehouse Logistics, Final Product -> External Outbound Logistics
• Invoice Verification: 3-Way Match Enterprise System checks if purchase order, goods receipts and invoice match
• Bookkeeping - Chart of accounts - general ledger - Income statement - Balance sheet
• 5 Phase Model Animation Phase -> Information Phase -> Agreement Phase -> Fulfillment Phase -> Loyalty Phase
• Customization - Selection of program modules (configuration) - individual adoption of the ERP software that do not compromise the ability for releases (parameterisation) - system settings such as country, currency, menus, ... - possibly additional programming in accordance with the software framework - light 2001 article: customization affects maintenance
• Potential Maintenance Effort Lowest - New Report - Amend existing reports/displays - Process automation - Add functionality - Change functionality Highest
• Release Compatibility - ability for customization to continue to work in future releases - ERP vendor should provide guidelines for the customization possibilities -> RC is dependent on the architecture of the ERP system
• Success Factors for Projects - Strong support inside the company - Dedicated executives - fast decisions - Project team with power user and decision makers - rapid return of investment - manageable project scope - Release compatibility
• Requirements Gathering Process User Consultant/Implementation Partner Business Req. Doc. --Automation possible--> System Req. Doc. -> Software program -> User
• Techniques for Requirements Gathering - Interviews - Requirements Workshop - Documents (plain text) - Prototyping - Rich Pictures - Brainstorming - Scenarios - Use Cases - Process charts - Data Flow Diagrams - Observations - Focus Groups - Business Process Modelling - UML - Survey - Videos - EPC
• Vendor Evaluation - Business functions or modules supported by their software - Features and integration capabilities - Financial viability of the vendor, as well as length of time in business - Licensing and upgrade policies - Customer service and help desk support - Total cost of ownership (TCO) - IT infrastructure requirements - Third-party software integration - Legacy systems support - Consulting and training service - Future goals and plans for the short and long term
• Partner Roles - Independent Software Vendor (ISV) - Create industry solutions (standard package) - Take original ERP software and add functionality - Implementing and non-implementing ISVs - Value-added Reseller (VAR) - Implementation consultants - Add features or services to existing product, then resell it as an integrated product or complete "turn-key" solution - added value can be in form of services like integration, customizing, consulting, training and implementation
• ERP Implementation Methodology Requirements gathering/Gap Analysis -> General System Design -> Build & Test -> Implementation -> Stabilization and Production Support
• ERP Standard Software Evaluation Process Phase 1: Pre Selection Phase 2: Requirements identification Phase 3: Detailed evaluation Phase 4: Implementation Phase 5: Operation
• ERP Implementation Approach - Comprehensive - Implementation of the full functionality as well as industry specific modules and third-party applications - May require considerable change to the build in process to tailor the application to the very specific processes of the organization - Vanilla - Utillises core functionality of the ERP modules and exploits best practice business processes built into the software - Minimal tailoring of the software - Change business practices to fit the system
• Reasosn for Vanilla ERP Implementation Approach - Straight forward business practices that are not unique - no experience at building or changing systems - financial component is critical - all branches are running the same system in a single instance
• Best Breed Solution - Tailored to the needs of one department/one functional area - Typically isolated to one process or one part of a process - leads to combination of different software products (heterogeneous technology) - Higher maintenance costs - More specific knowledge of IT supporters - Cost of integration with other applications
• Total Cost of Ownership (TCO) - Cost depends on - number of divisions it will serve - number of modules installed - amount of integration that will be required with existing systems - The readiness of the company to change - Ambition of project - Operating costs
• Enterprise Collaboration Systems (ECS) - de facto digital workspace of the platform - Large-scale integrated platforms that provide tools for collaboration and communication - Support document, knowledge and information sharing
• Commonalities: Architecture Presentation Level: Proprietary Client (Fat Client), Web Browser (Thin/Rich Client), Mobile Client, Third Party Web Services Application Leve: Products of the Software Vendor, Standard Components, Third-Party Products Database Level: Database, Documents
• Use Case - High level business activity with focus on interaction between user and system - Achieve business goal - High level of abstraction and technology agnostic
• Collaboration Scenario - composition of activities that are carried out by one or more people (actors) to achive a common goal (collaboratively) - describe specific steps of interactions among actors/social documents - generic components that can occur in different use cases - include reference to concrete software features
• Social Collaboration Analytics (SCA) (Key Themes) - System Usage - Identification of types of users - Community analysis - Identification of expertise - Identification of usage patterns - Network analysis - Organizational impacts - System usage
• Social Collaboration Analytics (SCA) (Data Sources) - Organizational Data - User accounts - Organizational structure - Content Data - User generated content - Transactional Data - Event Log - User interactions with timestamp - User relations - Webserver Log - URL query string with timestamp - Device and OS - Session duration
• Dimensions of Social Collaboration Analytics - Level of Analysis - Content Type - Content Component - Action Type - Time - Further Filter
• Dimensions of Social Collaboration Analytics (Level of Analysis) - Platform - Community - Members - Where?
• Dimensions of Social Collaboration Analytics (Content Type) - Activities - Blogs - Forums - Profiles - Wiki - Which type of content?
• Dimensions of Social Collaboration Analytics (Content Component) - Entry - Post - Comment - Like - Tag - Which content component?
• Dimensions of Social Collaboration Analytics (Action Type) - Add - Comment - Copy - Read - Update - Which type of action?
• Dimensions of Social Collaboration Analytics (Time) - Timestamp - When?
• Dimensions of Social Collaboration Analytics (Further Filter) - Business Unit - Region - Time constraints - Custom - Which filters?
• ESC Integrated Software Suite - Developed by one software vendor - One UI, one account, seamless - Single sing on - Ubiquitous user presence awareness

back  |  next 1 / 2