Information Management

- attribute related to primary key of another relation (Foreign key)

Relationship:

- relation can contain any number of secondary keys

- primary and secondary key must have same data type (but not same name)

- if no input required for secondary key attribute, it may also be empty (Null values)

- Secondary Keys belonging to primary key may never be empty

- Two tables with 1:1 relation: either take the primary key of first table and add it as secondary key in second table or vice versa

- Primary Key in first table gets placed as secondary key in second table (secondary key is always placed in table with the n!)

- the primary keys of both tables (entity types) become secondary keys and form a new relation together.

e.g. Branches (n) sell Items (m) --> new relation: Sales (Branch No, Item No)

--> In new Relation the secondary keys can become combined primary key

Referential Integrity: prevents database changes from causing secondary key values to reference non-existing records (primary key values)

Is a Relationship type between same entity type --> entities of same type are related (same rules apply as for different entity types)

e.g.

1:1: persons is married to Persons --> Persons (PNo, Name, Firstname, PartnerNo)

1:n: Employee (1) leads Employees (n) --> Employees (ENo, Name, Firstname, SuperiorNo)

n:m: Products/Parts (n) contains Products/Parts (m) --> New Relation: Components (SuperiorNo, SubNo)

Designing a database where redundancies can be avoided

Use:

- detect and eliminate redundancies

- transform existing data into relational model

- create stable and flexiblie data structure that needs to be changed as little as possible

- transforms complex relations n:m into hierarchal relations 1:n

Normalization takes place step-by-step from one normal form to the next

the higher the normal form (1NF, 2NF etc.), the higher the degree of normalization --> meaning less redundancies

To determine the degree of normalization:

relation must be examined: value of each attribute, dependencies between attributes of each relation

Functional Dependency: attribute of A is related to exactly one attribute of B e.g. Persons (PNo, Name, Firstname)

Full Dependency: Attributte B is functionally dependent on all Atrributes in A e.g. Sales (CNo, ANo, Salesdate)

Transitive Dependency: Non-key attribute B is dependent on A and attribute C is functionally dependent on B, But A not functionally dependent on C e.g. Persons (PNo, Name, DepNo, Department)

1NF: if in each table only one value is contained and all atrributes are atomic (indivisble)

2NF: if the relation is in first normal form and every non key attribute is fully functionally dependent on the primary key

3NF: if the relation is in the second normal form and there are no transitive dependencies

Modifications turn the Descriptive model (ERP): business model (current state)

 into..

The Prescriptive model: IT model (traget state)

EM: models digital transformation of an enterprise (Data Model)

-->generates value, promotes business efficiency, agility, durability etc.

Organization view (WHO) : Org. Structure, HR, Hierarchy,

Data view (WHAT): Entity and Data Models (e.g. ER Model)

Control view (HOW): Connects other views to a time-logical schedule (e.g. Process flow diagrams)

Function view (WHERE): Activities within/across business functions (e.g. hierarchy trees)

Product and Service View (WHAT FOR): P&S portfolio (e.g. Product Models)

1. Requirements specification (standards)

2. Data Processing concept

3. Implementation: technical realization

Process: logical sequence of activities (start and termination event)

Business Process: chain of tasks than contribute value for company--> derieved from corporate strategy

- Order-to-Cash (e.g. amazon order): customer submits order, product delivered

- Quote-to-Order: Supplier receives request for purchase quote (purchase order)

- Procure-to-Pay: need for p&s in company--> p&s delivered and payed

- Application-to-Approval (building permit etc): Application for benefit: benefit approved or denied

- Issue-to-Resolution (IT service): customer raises problem/issue --> issue resolved

Activities

- Oversight of Organization Performance --> Manages entire chain of events, activities, decisions

- Improvements (reducing costs, execustion time, error rates

- Tools to design, analyze, execute, monitor business processes

Benefits

- Business-IT alignment: Process Models can be understood by both business and IT people

- Process Improvements: High quality management (cost, time, quality, flexibility), Process automation (workflow, control, efficiency), Business information system integration

1. Initial Ad-Hoc: Enterpreneurial management ( Process known but not documentet)

2. Managed Documentation: Base management (documented process, not modelled)

3. Defined Modelled Process: Process definition (standard processes)

4. Quantitatively Managed: Process measurement (measures with key-figures)

5. Optimizing: Process management, change management (quality feedback and insights from experts)--> very expensive

higher levels: Quality, Productivity

lower levels: risk not meeting customer needs

Purpose:

- Basis for decision making (communicating, analysis)

- Documentation of facts (knowledge, design, automation)

Methods (in control view of ARIS)

- EPC Event-driven Process Chain

- BPMN Business Process Model and Notation

Event driven Process: Mapes start and end state as well as activity, direct graph of function or tasks

1. Events (e.g. order received): does not consume time or money, passive (hexagones)

2. Task function (e.g. check stock): verb plus object, (rectangles with rounded corners)

3. Operators: connector, identify logical links (circle with < and, > and/or, x or)

4. Control flow: temporal, logical dependencies of events and functions

- at least one start and end event --> events followed by event or connector

- functions and events have exactly one incoming and outgoing edge (except start or end event)

- connectors have either several incoming and one outgoing event, or one incoming and several outgoing event

BPMN: for business and IT, simple process notation, Representation by Business Process Diagram

1. Flow Objects: events (circles), activities (rectangles), Gateways/operators  (diamonds)

2. Connecting objects

3. Participants (pool, swimlanes)

Differences to EPC:

- BPD shows how to convert charts into machine readable process descriptions

- has help of workflow engine

Robotics

- Improvement of hardware components, regulation, control technology

- interdisciplinary scientific disipline

- Human-Robot Interaction and Collaboration

Augmented Reality: projecting digital things in our field of vision

Virtual Reality: allows complete immersion into a virtual worl

Digitization: Transformation from Analog to Digital

Digitalization: Process of moving into digital business:

- Big Data/Digital Information

- Connectivity/Mobility

- Cloud Computing/Networks

- Internet of Things/Automation

Digital Transformation: broader understanding coming together -->greater impact on business and society (AR/VR, Block chain technologies, AI, Disruptive Developments, Internet of Things)

1. What do I offer? (Digitalization can take place at product/service level)

2. How is my offer created? (Internal Process become more efficient through digital Transformation)

3. How do I earn money? (Via alternative models in the future: Subscription, Freemium, Licensing etc.)

Data, Information, Knowledge, Wisdom

- Relevance

- Accuracy

- Timeliness

- Usability

- Completeness

- a group of components inside a boundary that work together to accomplish a purpose

- Software, Procedures, Hardware, People, Data

 1. Entering

2. Processing

3. Storage

4. Sending

5. Using

- Organisations create/use data in:

business processes, application softwares, exchange with other organizations

- Data have to be:

stored reliably, retrieved and access easily

- Insufficients data organisation leads to:

Redundancies (duplicated, triplicated)

inconsistencies (contradictory, missing due to redundant data)

Miscalculations (data captured incorrectly)

Extra work (time consuming troubleshooting)

--> costs, wrong assumptions, faulty external representation

Senior Management (Strategic level): C-Level

Middle Management (Control level): Heads of primary, secondary areas

Employees (Operative level): Value chain (production, marketing etc.)

Rarely edited:

- Modification Data (Modification of Addresses, adjustment of products etc.)

- Master Data (Article nr., customer data, product data, parts list etc)

Periodically edited:

- Stock Data (Stock volume etc.)

- Transaction Data (Bookings, Orders, Payments etc)

- Organising data in files: usage mainly by application software, stored individually in seperate files via file system

- Organising data in database systems: usage mainly by ERP systems, stored in logical structures by database management systems

Disadvantages files:

- Application Dependency: files only editable with specific applications (excel, word etc)

- High preparation effort for analysis: merging and evaluating very time consuming

- Redundancy leads to inconsistencies and high maintenance effort

Advantages Database:

- Data independence: processable with any application

- Flexible data anylsis: through logical data model

- No redundancies

Consists of one or more Databases...:

- several linked files

- collection of content-related data

...and a database management system DBMS:

- software for building, checking, changing, retrieving

- interface for use of data by application software

- User groups have access rights to different data: Multi-user access, Data Protection, Data Integrity (consistency)

- Data can be analysed and linkes acc. to characteristics: Data Independence, Multi-user access, Usability, Flexibility, Efficiency, non-redundancy

- Queries on database provide answers quickly: Usability, Efficiency

- Data available at any time without errors: Data security, Data Integrity, Non-redundancy