Extreme weather events and business continuity planning

There is now a broad scientific consensus that the global climate is changing in ways that are likely to have a profound impact on human society and the natural environment over the coming decades. The challenge for Facilities Mangers is to ensure that business continuity plans acknowledge the potential for such events and have contingencies in place to ensure that their organisation can recover from an extreme weather event in a timely fashion. This paper will review current literature/theories pertinent to extreme weather events and business continuity planning; will consider issues of risk; identify the key drivers that need to be considered by Facilities Managers in preparing contingency/disaster recover plans; and identify gaps in knowledge (understanding and toolkits) that need to be addressed. The paper will also briefly outline a 3 year research project underway in the UK to address the issues

A design pattern for integration of business process management systems

A cross-domain workflow application may be constructed using a standard reference model such as the one by the Workflow Management Coalition (WfMC) [7] but the requirements for this type of application are inherently different from one organization to another. The existing models and systems built around them meet some but not all the requirements from all the organizations involved in a collaborative process. Furthermore the requirements change over time. This makes the applications difficult to develop and distribute. Service Oriented Architecture (SOA) based approaches such as the BPET (Business Process Execution Language) intend to provide a solution but fail to address the problems sufficiently, especially in the situations where the expectations and level of skills of the users (e.g. the participants of the processes) in different organisations are likely to be different. In this paper, we discuss a design pattern that provides a novel approach towards a solution. In the solution, business users can design the applications at a high level of abstraction: the use cases and user interactions; the designs are documented and used, together with the data and events captured later that represents the user interactions with the systems, to feed an intermediate component local to the users -the IFM (InterFace Mapper) -which bridges the gaps between the users and the systems. We discuss the main issues faced in the design and prototyping. The approach alleviates the need for re-programming with the APIs to any back-end service thus easing the development and distribution of the applications