Deploying IT resources (MIS 533) MBS in Management Information Systems and Managerial Accounting Systems (2006 / 2007) Fergal Carton Business Information Systems

MBS (MIMAS) / MIS533 / Deploying IT Resources Last week Planning approaches (build to plan) Inventory consumption Difference between process and discrete manufacturing Lead times MusicMaestro : Context diagram discussion

MBS (MIMAS) / MIS533 / Deploying IT Resources Production planning Planning approaches (build to plan) –Top down quarterly plan drives both Production (units) and Sales (€) targets –Takes into account sales forecast, historical performance and market expectations –Production plan must then be broken down into units, configurations, geograpahies –Local production planners then turn this into: an MRP plan to drive purchasing and a Master production schedule to drive manufacturing

MBS (MIMAS) / MIS533 / Deploying IT Resources Keeping tabs on Work-in-Progress (WIP) Inventory consumption –Something must trigger inventory consumption as production proceeds (BO, WO, PO, SO, …) –Visibility of inventory in Work-in-Progress (WIP) is low –You can measure output / consumption at intermediate points but beware of disrupting process

MBS (MIMAS) / MIS533 / Deploying IT Resources Manufacturing modes and lead times Difference between process and discrete manufacturing –Process manufacturing consumes inventory at a steady rate, but yield of finished goods may vary –Discrete manufacturing consumes a predefined amount of inventory per article of finished goods Lead times: –key to replenishment policy: what’s my buffer stock? –Fiat Idea : re-uses previous model components to reduce cost & lead time

MBS (MIMAS) / MIS533 / Deploying IT Resources Practical assessment MusicMaestro : Context diagram discussion –Entities for Formats, Playlists, Songs, … –Think about depth of song attributes (artist, musicians, …) –Think about playlist sequencing –Compare to iTunes?

MBS (MIMAS) / MIS533 / Deploying IT Resources Practical assessment

MBS (MIMAS) / MIS533 / Deploying IT Resources This week Questions on DFD’s / ERD –Relationships (many to many, one to many, …) –Using different symbols (entities, relationships, …) –Transition from DFD to ERD –Practice makes perfect! Manufacturing data Data and normalisation Final system examples (Johanna, Kerrie, David, Michael) Associative entities (BOM, Sales orders, …) Despatch link to SO and AR

MBS (MIMAS) / MIS533 / Deploying IT Resources More system examples Quality control for Guinness –Test samples from franchised breweries –Test data stored (ph, alcohol, colour, …) –Tolerance ranges –Annual prize / discount for high achievers Interbank Accounts System for TSB –Transactional screen, query screen –Search limited to 3 chars (firstname, surname) SIFASoft for Electronic Point of Sale (EPOS) –Response time on price for products with long history Sage Accounting package –Entering transactions, coding of accounts –Issue knowing which account to use

MBS (MIMAS) / MIS533 / Deploying IT Resources Data storage Series of ad-hoc systems manual and computer- based (spreadsheet, filed forms…) Dedicated databases for manufacturing data (QC, shipping etc…) Process Control Systems (technical parameters) Other specialised proprietary systems (integration may not be easy). ERP system with its own data structure or fed by existing systems

MBS (MIMAS) / MIS533 / Deploying IT Resources Using Manufacturing data Operational data: –volumes - schedule / re-schedule runs –labour report - line up workers for next days –quality of output Tactical data: –defect rates –productivity –Quality of RM Strategic data: –product mix information –Market research –turnover of staff Some soft information is also required

MBS (MIMAS) / MIS533 / Deploying IT Resources Soft information Data collection - –Grapevine –factory tours (talking and observing) Data storage - –managers’ minds –special reports Data usage: –ad-hoc basis –decision making

MBS (MIMAS) / MIS533 / Deploying IT Resources Normalisation Process of simplifying the relationships amongst data items as much as possible (see example provided - handout) Through an iterative process, structure of data is refined to 1NF, 2NF, 3NF etc. Reasons for normalisation: –to simplify retrieval (speed of response) –to simplify maintenance (updates, deletion, insertions) –to reduce the need to restructure the data for each new application

MBS (MIMAS) / MIS533 / Deploying IT Resources First Normal Form design record structure so that each record looks the same (same length, no repeating groups) repetition within a record means one relation was missed = create new relation elements of repeating groups are stored as a separate entity, in a separate table normalised records have a fixed length and expanded primary key

MBS (MIMAS) / MIS533 / Deploying IT Resources Second Normal Form Record must be in first normal form first each item in the record must be fully dependent on the key for identification Functional dependency means a data item’s value is uniquely associated with another’s only on-to-one relationship between elements in the same file otherwise split into more tables

MBS (MIMAS) / MIS533 / Deploying IT Resources Third normal form to remove transitive dependencies when one item is dependent on an item which is dependent from the key in the file relationship is split to avoid data being lost inadvertently this will give greater flexibility for the design of the application + eliminate deletion problems in practice, 3 NF not used all the time - speed of retrieval can be affected

MBS (MIMAS) / MIS533 / Deploying IT Resources Realistic constraints Users cannot cope with too many tables Too much development required in hiding complex data structure Too much administration Optimisation is impossible with too many tables Actually: RDBs can be quite slow!

MBS (MIMAS) / MIS533 / Deploying IT Resources CUSTOMER TABLE PRODUCT TABLE ITEM TABLE SALES_ORDER TABLE PRICE TABLE Oracle Demo Set - Sales Order Processing