Managing Supply Chain Events to Build Sense-and-Respond Capability

As supply chains become more dynamic, there is a need for a sense-and-respond capability to react to events in a real-time manner. In this paper, we propose Petri nets extended with time and color (for case data) as a formalism for doing so. Hence, we describe seven basic patterns that are used to capture modeling concepts that arise commonly in supply chains. These basic patterns may be used by themselves and also be combined to create new patterns. Next, we show how to use the patterns as building blocks to model a complete supply chain and analyze it using dependency graphs and simulation. Dependency graphs can be used to analyze the various events and their causes. Simulation was, in addition, used to analyze various performance indicators (e.g. fill rates, replenishment times, and lead times) under different supply chain strategies. We performed sensitivity analysis to study the effect of changing parameter values on the performance indicators. In the experiments, by cutting resolution time for production delays in half (strategy 1), we were able to increase order fill rate from 89% to 95%. Similarly, upon raising the probability of successful alternative sourcing (strategy 2) from 0.5 to 0.7 the order fill rate again increased from 89% to 95%. We show that by modeling timing and causality issues accurately, it is possible to improve supply chain performance

Specification of requirements models

The main aim of this chapter is to present and discuss a set of modeling and specification techniques, in what concerns their ontology and support in the requirements representation of computer-based systems. A systematic classification of meta-models, also called models of computation, is presented. This topic is highly relevant since it supports the definition of sound specification methodologies in relation to the semantic definition of the modeling views to adopt for a given system. The usage and applicability of Unified Modeling Language (UML) diagrams is also related to their corresponding meta-models. A set of desirable characteristics for the specification methodologies is presented and justified to allow system designers and requirements engineers to more consciously define or choose a particular specification methodology. A heuristic-based approach to support the transformation of user into system requirements is suggested, with some graphical examples in UML notation.(undefined