I’ve got this feedback from Anatoly on my first iteration of System-of-interest definition here https://blog.system-school.ru/2022/09/23/my-understanding-of-why-system-thinking-is-useful-first-round-of-target-system-reveal/
Not target system, system-of-interest. External project roles -- stakeholders. Not system reveal, but better system discovering (rare), even more better will be system definition (standard name for it).Department is organizational unit (constructive object, not functional object, not orgrole), you need something functional for system definition. Data are descriptions, not systems. We will explore this case at a group meeting.Искать нужно а) системы, с ними работающие/их интерпретирующие и б) что именно описывают эти данные, что мы собираемся менять (изменение этих данных нам нужно для изменения чего? вот ключевой вопрос).
So let's do the second iteration for System-of-interest definition.
My interest Function - is governing the Master Data (limiting Master data usage, managing it's life cycle principles - when and how to create to be to balance different functional interest to maximize value for whole Enterprise). As a functional unit I can think of Role Master Data Governance Lead (I have two in my team: one for Vendors and one for Materials)
If we leave System-of-Interest as defined in 1st iteration as End Customer enjoys Payed Product, then chain of enabling systems up to the my Engineered System will be:
| Number | System Name | System Type | Grounding example | Data used | Applications used | Roles involved |
|---|---|---|---|---|---|---|
| 1 | End Customer enjoys Payed Product | System-of-Interest | Mr J.Smith has bought in a shop a Chocolate bar and paid $1 | Transaction: Sales; Master data: Product, | Customer Relationship Management System (CRM) | Customer, Shop assistant |
| 2 | Sales | Enabling system | Sales Representative took an order from a shop for 30 Chocolate bars | Transaction: Order; Master data: Product, Customer | Enterprise Resource Planning System (ERP) | Sales Representatives, Shop owner |
| 3 | Distribution | Enabling system | Order was processed and transportation organized from Warehouse to the Shop, Truck has delivered 30 Chocolate bars to the Shop | Transaction: Order; Invoice Master data: Product, Customer | ERP, Transport management system (TMS) | Warehouse oterator, Truck driver |
| 4 | Manufacturing | Enabling system | Plant has produces 1000 Chocolate bars and sent to the Warehouse | Transaction: Process Order; Master data: Product, Material | ERP, Manufacturing Execution system (MES) | Chocolate line operator |
| 5 | Purchasing | Enabling system | Buyer has ordered 1 ton of Cocoa for the Plant, Vendor has supplied it the the Ware house | Transaction: Purchase Order; Master data: Vendor, Material | ERP | Buyer, Vendor, Warehouse operator |
| 6 | Finance | Enabling system | Finace controller has check and authorized the purchasing | Transaction: Purchase Order; Master data: Vendor, Material | ERP | Finance controller |
| 7 | IT | Enabling system | IT has supported the access of all Roles to the ERP system | Roles, Employees, Access | all | Security specialist |
| 8 | Internal Control | Enabling system | Legal has checked the access is comliant to the Law | Roles, Employees, Access | all | Internal Control specialist |
| 9 | R&D | Enabling system | R&D specialist creates new specification and asks for new sku code for a new product | Transaction: New Specification creation Master Data: Materials, Product | Product Lifecycle management system (PLM) | R&Q specialist |
| 10 | Master Data | Enabling system | Master data operator has created the sku code for Chocolate bar as this is a new product after a check it’s Name, weight and receipt | Transaction: Product creation Master data: Product | Master data management system (MDM), ERP | Master Data operaor |
| 11 | Master Data Governance | System-in-hands/Engineered System | Master Data Governance Lead has set up a rule which restrict creating of new skus in ERP if Name and weight is the same with existing sku | Process: Rule of Product creation Master data: Product | MDM | Master Data Governance Lead |