Developing manufacturing control software: A survey and critique

The complexity and diversity of manufacturing software and the need to adapt this software to the frequent changes in the production requirements necessitate the use of a systematic approach to developing this software. The software life-cycle model (Royce, 1970) that consists of specifying the requirements of a software system, designing, implementing, testing, and evolving this software can be followed when developing large portions of manufacturing software. However, the presence of hardware devices in these systems and the high costs of acquiring and operating hardware devices further complicate the manufacturing software development process and require that the functionality of this software be extended to incorporate simulation and prototyping.Peer Reviewedhttp://deepblue.lib.umich.edu/bitstream/2027.42/45542/1/10696_2005_Article_BF01328739.pd

Developing control and integration software for flexible manufacturing systems

The slow growth of computer-integrated manufacturing is attributed to the complexity of designing and implementing their control and integration software. This article expands on a methodology for designing and implementing this software that was introduced in [16]. The goal of this methodology is to build flexible and resuable control and integration software for computer-integrated manufacturing systems. It hinges upon the concepts of software/hardware components, their assemblages, a distributed common language environment, formal models, and generic controllers. Major sources of flexibility are obtained by decoupling process plan models from the model of the factory floor and by using a generic controller. Reusability is achieved by building selfcontained software/hardware components with general, possibly parametrized, interfaces. The interplay between simulated and actual hardware internals of software/hardware components is used as the basis of a testing strategy that performs off-line simulation followed by on-line testing.Peer Reviewedhttp://deepblue.lib.umich.edu/bitstream/2027.42/43095/1/10952_2005_Article_BF02265064.pd

Executable system architecting using systems modeling language in conjunction with Colored Petri Nets - a demonstration using the GEOSS network centric system

Models and simulation furnish abstractions to manage complexities allowing engineers to visualize the proposed system and to analyze and validate system behavior before constructing it. Unified Modeling Language (UML) and its systems engineering extension, Systems Modeling Language (SysML), provide a rich set of diagrams for systems specification. However, the lack of executable semantics of such notations limits the capability of analyzing and verifying defined specifications. This research has developed an executable system architecting framework based on SysML-CPN transformation, which introduces dynamic model analysis into SysML modeling by mapping SysML notations to Colored Petri Net (CPN), a graphical language for system design, specification, simulation, and verification. A graphic user interface was also integrated into the CPN model to enhance the model-based simulation. A set of methodologies has been developed to achieve this framework. The aim is to investigate system wide properties of the proposed system, which in turn provides a basis for system reconfiguration --Abstract, page iii

Prototyping real-time systems

The traditional software development paradigm, the waterfall life cycle model, is defective when used for developing real-time systems. This thesis puts forward an executable prototyping approach for the development of real-time systems. A prototyping system is proposed which uses ESML (Extended Systems Modelling Language) as a prototype specification language. The prototyping system advocates the translation of non-executable ESML specifications into executable LOOPN (Language of Object Oriented Petn Net) specifications so that ESML can be used as a graphical executable specification language for the prototyping of real-time systems. If the translation process is automatic then the user need not be aware of LOOPN. The ESML/LOOPN prototyping system defines an execution semantics for the ESML language in terms of LOOPN nets, a set of translation templates are supplied for the translation of ESML language specifications into LOOPN language specifications. The execution semantics are based on a set of execution rules (guidelines) which have been defined for ESML to allow prediction of the behaviour of ESML specifications over time. A C language program which can be run by the user as a prototype of the modelled system is generated automatically from the LOOPN specification. The ESML/LOOPN prototyping system has been applied to build an exploratory prototype of a typical real-time system, 1e the Fuel Subsystem of the Auxiliary Power Unit (APU), an avionic system used on the Boeing-737 airplane series

User Interface Management Systems: A Survey and a Proposed Design

The growth of interactive computing has resulted in increasingly more complex styles of interaction between user and computer. To facilitate the creation of highly interactive systems, the concept of the User Interface Management System (UIMS) has been developed. Following the definition of the term 'UIMS' and a consideration of the putative advantages of the UIMS approach, a number of User Interface Management Systems are examined. This examination focuses in turn on the run-time execution system, the specification notation and the design environment, with a view to establishing the features which an "ideal" UIMS should possess. On the basis of this examination, a proposal for the design of a new UIMS is presented, and progress reported towards the implementation of a prototype based on this design

A new approach to the development and maintenance of industrial sequence logic

This thesis is concerned with sequence logic as found in industrial control systems, with the focus being on process and manufacturing control systems. At its core is the assertion that there is a need for a better approach to the development of industrial sequence logic to satisfy the life-cycle requirements, and that many of the ingredients required to deliver such an approach are now available. The needs are discussed by considering the business case for automation and deficiencies with traditional approaches. A set of requirements is then derived for an integrated development environment to address the business needs throughout the control system life-cycle. The strengths and weaknesses of relevant control system technology and standards are reviewed and their bias towards implementation described. Mathematical models, graphical methods and software tools are then assessed with respect to the requirements for an integrated development environment. A solution to the requirements, called Synect is then introduced. Synect combines a methodology using familiar graphical notations with Petri net modelling supported by a set of software tools. Its key features are justified with reference to the requirements. A set of case studies forms the basis of an evaluation against business needs by comparing the Synect methodology with current approaches. The industrial relevance and exploitation are then briefly described. The thesis ends with a review of the key conclusions along with contributions to knowledge and suggestions for further research

Petri net modelling of a communications protocol

The Petri net is a formal modelling tool applicable to distributed systems and communication protocols. Two methods of analysis are applied to formal models of the "Alternating Bit Protocol". (i) A timed Petri net model is simulated to measure protocol performance. (ii) A modular numeric Petri net model is validated by reachability analysis. The simulation and validation tools are programmed in (i) "C" language and (ii) Prolog. A specification language "Needle" is developed. It describes the model system as a hierarchy of modular state transition networks. The model is searched for all possible event sequences, and the result displayed as a reachability tree. The specification language is capable of describing models which execute backwards in simulation time. The modular numeric Petri net is the basis of a powerful computer architecture, capable of parsing its own specification language to build complex models. Attention is drawn to the similarities between Petri net theory and quantum mechanics