A software architecture for autonomous maintenance scheduling: Scenarios for UK and European Rail

A new era of automation in rail has begun offering developments in the operation and maintenance of industry standard systems. This article documents the development of an architecture and range of scenarios for an autonomous system for rail maintenance planning and scheduling. The Unified Modelling Language (UML) has been utilized to visualize and validate the design of the prototype. A model for information exchange between prototype components and related maintenance planning systems is proposed in this article. Putting forward an architecture and set of usage mode scenarios for the proposed system, this article outlines and validates a viable platform for autonomous planning and scheduling in rail

Model the System from Adversary Viewpoint: Threats Identification and Modeling

Security attacks are hard to understand, often expressed with unfriendly and limited details, making it difficult for security experts and for security analysts to create intelligible security specifications. For instance, to explain Why (attack objective), What (i.e., system assets, goals, etc.), and How (attack method), adversary achieved his attack goals. We introduce in this paper a security attack meta-model for our SysML-Sec framework, developed to improve the threat identification and modeling through the explicit representation of security concerns with knowledge representation techniques. Our proposed meta-model enables the specification of these concerns through ontological concepts which define the semantics of the security artifacts and introduced using SysML-Sec diagrams. This meta-model also enables representing the relationships that tie several such concepts together. This representation is then used for reasoning about the knowledge introduced by system designers as well as security experts through the graphical environment of the SysML-Sec framework.Comment: In Proceedings AIDP 2014, arXiv:1410.322

Support for collaborative component-based software engineering

Collaborative system composition during design has been poorly supported by traditional CASE tools (which have usually concentrated on supporting individual projects) and almost exclusively focused on static composition. Little support for maintaining large distributed collections of heterogeneous software components across a number of projects has been developed. The CoDEEDS project addresses the collaborative determination, elaboration, and evolution of design spaces that describe both static and dynamic compositions of software components from sources such as component libraries, software service directories, and reuse repositories. The GENESIS project has focussed, in the development of OSCAR, on the creation and maintenance of large software artefact repositories. The most recent extensions are explicitly addressing the provision of cross-project global views of large software collections and historical views of individual artefacts within a collection. The long-term benefits of such support can only be realised if OSCAR and CoDEEDS are widely adopted and steps to facilitate this are described. This book continues to provide a forum, which a recent book, Software Evolution with UML and XML, started, where expert insights are presented on the subject. In that book, initial efforts were made to link together three current phenomena: software evolution, UML, and XML. In this book, focus will be on the practical side of linking them, that is, how UML and XML and their related methods/tools can assist software evolution in practice. Considering that nowadays software starts evolving before it is delivered, an apparent feature for software evolution is that it happens over all stages and over all aspects. Therefore, all possible techniques should be explored. This book explores techniques based on UML/XML and a combination of them with other techniques (i.e., over all techniques from theory to tools). Software evolution happens at all stages. Chapters in this book describe that software evolution issues present at stages of software architecturing, modeling/specifying, assessing, coding, validating, design recovering, program understanding, and reusing. Software evolution happens in all aspects. Chapters in this book illustrate that software evolution issues are involved in Web application, embedded system, software repository, component-based development, object model, development environment, software metrics, UML use case diagram, system model, Legacy system, safety critical system, user interface, software reuse, evolution management, and variability modeling. Software evolution needs to be facilitated with all possible techniques. Chapters in this book demonstrate techniques, such as formal methods, program transformation, empirical study, tool development, standardisation, visualisation, to control system changes to meet organisational and business objectives in a cost-effective way. On the journey of the grand challenge posed by software evolution, the journey that we have to make, the contributory authors of this book have already made further advances

WESTT (Workload, Error, Situational Awareness, Time and Teamwork): An analytical prototyping system for command and control

Modern developments in the use of information technology within command and control allow unprecedented scope for flexibility in the way teams deal with tasks. These developments, together with the increased recognition of the importance of knowledge management within teams present difficulties for the analyst in terms of evaluating the impacts of changes to task composition or team membership. In this paper an approach to this problem is presented that represents team behaviour in terms of three linked networks (representing task, social network structure and knowledge) within the integrative WESTT software tool. In addition, by automating analyses of workload and error based on the same data that generate the networks, WESTT allows the user to engage in the process of rapid and iterative “analytical prototyping”. For purposes of illustration an example of the use of this technique with regard to a simple tactical vignette is presented

Managing healthcare workflows in a multi-agent system environment

Whilst Multi-Agent System (MAS) architectures appear to offer a more flexible model for designers and developers of complex, collaborative information systems, implementing real-world business processes that can be delegated to autonomous agents is still a relatively difficult task. Although a range of agent tools and toolkits exist, there still remains the need to move the creation of models nearer to code generation, in order that the development path be more rigorous and repeatable. In particular, it is essential that complex organisational process workflows are captured and expressed in a way that MAS can successfully interpret. Using a complex social care system as an exemplar, we describe a technique whereby a business process is captured, expressed, verified and specified in a suitable format for a healthcare MAS.</p

A Semantic-based framework for discovering business process patterns

Patterns currently play an important role in modern information systems (IS) development and their use has mainly been restricted to the design and implementation phases of the development lifecycle. Given the increasing significance of business modeling in IS development, patterns have the potential of providing a viable solution for promoting reusability of recurrent generalized models in the very early stages of development. This paper focuses on business process patterns and proposes an initial framework for the discovery and reuse of business process patterns within the IS development lifecycle. The framework synthesizes the idea from the domain engineering literature and proposes the use of semantics to drive both the discovery of patterns as well as their reuse

Study on thermal model for calculating transformer hot Spot temperature

A power transformer is a static piece of apparatus with two or more windings which, by electromagnetic induction, transforms a system of alternating voltage and current into another system of voltage and current usually of different values and at same frequency for the purpose of transmitting electrical power. The hot spot temperature depends on instantaneous load and ambient temperature, winding design and also cooling model. There are two possible methods for hotspot temperature determination. The first method is to measure the hot spot temperature using a fiber optic, and other is to calculation the hotspot temperature using transformer thermal models. It was noticed that the hot spot temperature rise over top oil temperature due to load changes is a function depending on time as well as the transformer loading (overshoot time dependent function). It has also been noticed that the top oil temperature time constant is shorter than the time constant suggested by the present IEC loading guide, especially in cases where the oil is guided through the windings in a zigzag pattern for the ONAN and ONAF cooling modes. This results in winding hottest spot temperatures higher than those predicted by the loading guides during transient states after the load current increases, before the corresponding steady states have been reached. This thesis presents more accurate temperature calculation methods taking into account the findings mentioned above. The models are based on heat transfer theory, application of the lumped capacitance method, the thermal-electrical analogy and definition of nonlinear thermal resistances at different locations within a power transformer. The methods presented in this thesis take into account all oil physical parameters change and loss variation with temperature. In addition, the proposed equations are used to estimate the equivalent thermal capacitances of the transformer oil for different transformer designs and winding-oil circulations. The models are validated using experimental results, which have been obtained from the normal heat run test performed by the transformer manufacturer at varying load current on a 250-MVA-ONAFcooled unit, a 400-MVA-ONAF-cooled unit and a 2500-KVA-ONAN-cooled unit. The results are also compared with the IEC 60076-7:2005 loading guide method. Keywords: power transformers, hot spot temperature, top oil temperature, non-linear therma

A framework for effective management of condition based maintenance programs in the context of industrial development of E-Maintenance strategies

CBM (Condition Based Maintenance) solutions are increasingly present in industrial systems due to two main circumstances: rapid evolution, without precedents, in the capture and analysis of data and significant cost reduction of supporting technologies. CBM programs in industrial systems can become extremely complex, especially when considering the effective introduction of new capabilities provided by PHM (Prognostics and Health Management) and E-maintenance disciplines. In this scenario, any CBM solution involves the management of numerous technical aspects, that the maintenance manager needs to understand, in order to be implemented properly and effectively, according to the company’s strategy. This paper provides a comprehensive representation of the key components of a generic CBM solution, this is presented using a framework or supporting structure for an effective management of the CBM programs. The concept “symptom of failure”, its corresponding analysis techniques (introduced by ISO 13379-1 and linked with RCM/FMEA analysis), and other international standard for CBM open-software application development (for instance, ISO 13374 and OSA-CBM), are used in the paper for the development of the framework. An original template has been developed, adopting the formal structure of RCM analysis templates, to integrate the information of the PHM techniques used to capture the failure mode behaviour and to manage maintenance. Finally, a case study describes the framework using the referred template.Gobierno de Andalucía P11-TEP-7303 M