1 / 17

Modeling Kanban Scheduling in Systems of Systems

Modeling Kanban Scheduling in Systems of Systems. Alexey Tregubov, Jo Ann Lane. Outline. Modeling Kanban scheduling in System of Systems: Why do we need to model? Overview of KSS Network Key aspects of Kanban scheduling technique Simulation model Example of KSS Network

ishana
Download Presentation

Modeling Kanban Scheduling in Systems of Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Modeling KanbanScheduling in Systems of Systems Alexey Tregubov, Jo Ann Lane

  2. Outline Modeling Kanban scheduling in System of Systems: • Why do we need to model? • Overview of KSS Network • Key aspects of Kanban scheduling technique • Simulation model • Example of KSS Network • Results & future work

  3. Why do we need to model? Applications of modeling in System of System environments: • Hypothesis testing • Process improvement • Business decision support • Cost and effort estimation

  4. Health care example of KSS Network

  5. Key aspects of Kanban scheduling Kanban principles embedded in prioritization algorithm: • Eliminate waste • Minimize context switching • Limit work in progress • Make process more visible and transparent • Kanban boards • Increased value delivered earlier • Value-based work prioritization • Reduce governance overhead

  6. Key aspects of Kanbanscheduling (continued) Work prioritization algorithm based on the following: • All work items (WI) prioritized according to their business value • Every WI has a class of service: Standard, Important, Date Certain, Critical Expedite • Limiting work in progress: work in progress is never interrupted unless new work has a Critical class of service

  7. Simulation model Discrete event simulation: • Inputs: • Event scenario: a sequence of events that describes how network evolves over course of their execution • Team configuration: structure of teams, resource/specialties allocation • Simulation configuration: stop condition • Outputs: • Sequence of network states • Analysis: various indicators of effectiveness

  8. Simulation model: definitions Discrete event simulation – network state & transition algorithm Network state objects: • Kanban board – demand log, work items in progress • Team – group of resources (e.g. software development team) • Work item – task that requires effort to completed • Aggregation Nodes – logical group of work items, such as requirements, capabilities • Kanban network – teams, Kanban board, and their work items Transition algorithm: • Trigger events according to the scenario • Apply work prioritization algorithm

  9. Health care example

  10. Example: capabilities to requirements to products

  11. Example: network structure & scenario

  12. Example: outputs

  13. Example: workflow

  14. Example: result analysis Value:

  15. Conclusion: results • Simulation model • Simulator implementation: KSS Simulator • Two prioritization algorithms implemented • Several scenarios analyzed

  16. Conclusion: future work • Pilot the Kanban scheduling with several organizations • Fine-tune the simulator using empirical data and organizations feed back • Scale up the cases we run through the simulator • Refine and calibrate cost models

  17. Questions & answers

More Related