Model-driven Enterprise Systems Configuration

Enterprise Systems potentially lead to significant efficiency gains but require a well-conducted configuration process. A promising idea to manage and simplify the configuration process is based on the premise of using reference models for this task. Our paper continues along this idea and delivers a two-fold contribution: first, we present a generic process for the task of model-driven Enterprise Systems configuration including the steps of (a) Specification of configurable reference models, (b) Configuration of configurable reference models, (c) Transformation of configured reference models to regular build time models, (d) Deployment of the generated build time models, (e) Controlling of implementation models to provide input to the configuration, and (f) Consolidation of implementation models to provide input to reference model specification. We discuss inputs and outputs as well as the involvement of different roles and validation mechanisms. Second, we present an instantiation case of this generic process for Enterprise Systems configuration based on Configurable EPCs

The suitability of MSP for engineering infrastructure

This paper arose from empirical investigations of practitioner views of both governance and program definitions together with investigations of practitioner reference documents. These investigations indicated that some confusion had arisen in infrastructure project management as a result of approaches used in IT. This paper contributes to the literature evaluating project standards and methodologies by conducting an examination of the suitability of one such source (MSP) for use in engineering infrastructure program management. A deductive definitional approach is taken to identify features that could cause difficulty. Eight features were examined, and six were found to have difficulty in application to engineering infrastructure. The remaining two were found to be terminology differences that are unlikely to cause too much difficulty. The features causing difficulty include an inappropriate definition of a program, use of a non-generic process flow unsuitable for rolling programs, confusion of transformation projects with programs, the presumption of a board governance model, and confusion of large projects with programs. The paper concludes that MSP is quite poorly suited to managing rolling programs, whether they are in engineering infrastructure or IT. Various changes to MSP and PMI publications are recommended

Mobile support in CSCW applications and groupware development frameworks

Computer Supported Cooperative Work (CSCW) is an established subset of the field of Human Computer Interaction that deals with the how people use computing technology to enhance group interaction and collaboration. Mobile CSCW has emerged as a result of the progression from personal desktop computing to the mobile device platforms that are ubiquitous today. CSCW aims to not only connect people and facilitate communication through using computers; it aims to provide conceptual models coupled with technology to manage, mediate, and assist collaborative processes. Mobile CSCW research looks to fulfil these aims through the adoption of mobile technology and consideration for the mobile user. Facilitating collaboration using mobile devices brings new challenges. Some of these challenges are inherent to the nature of the device hardware, while others focus on the understanding of how to engineer software to maximize effectiveness for the end-users. This paper reviews seminal and state-of-the-art cooperative software applications and development frameworks, and their support for mobile devices

Preliminary Report on Patent Literature, Search Methodology and Patent Status of Medicines on the WHO EML 2009

Over the past several decades the World Health Organization (WHO) has produced the Essential Medicines List (EML) to assist countries in deciding what medicines should be essential and available in National Essential Medicine Lists.1 WHO, through the work of regional offices, supports nations using the EML to ensure the quality, availability, and affordability of pharmaceuticals required to promote and advance public health in nations across the globe. However in some cases, access to EML pharmaceuticals might be complicated by existing patents, i.e., where issued, patent rights might pose obstacles to access and inclusion in national EMLs. Indeed, in developed and emerging economy national jurisdictions patent protection may be in effect for a not insignificant number of the WHO EML pharmaceuticals (Figure 2A). However, in developing countries, it is uncertain whether these patents have been filed or issued. Without patent data predicated on an established, reproducible protocol for accessing and assembling patent information on the EML pharmaceuticals, discussions, debates and strategic approaches to understanding and managing patents with regard to access and delivery to developing countries remain in the dark. Indeed, it is absurd to make policy and formulate strategy without solid patent information: the critical foundation for rational debate. To analyze the degree and scope of patenting of EML pharmaceuticals, WIPO (with WHO) approached the Franklin Pierce Center for Intellectual Property at the University of New Hampshire School of Law, specifically the International Technology Transfer Institute (ITTI) to generate a preliminary overview of patents appurtenant to recently added pharmaceutical updates to the EML.2 As part of this work, with inputs from WHO and WIPO, ITTI developed novel methodology and a detailed protocol for identifying EML pharmaceutical patents in national jurisdictions, with an easily reproducible yet cost effective template. Herein is described the development of such a protocol and a preliminary pool of patent information that illustrates its utility. The protocol yields data in a layered approach thereby allowing a user to quickly and effectively obtain both broad and detailed patent information for medications on the WHO EML. In addition, the protocol can be used as an initial path for targeted strategic analysis of potentially relevant patent information in national jurisdictions. In sum, the objectives for this project were: To develop a robust methodology to assess the patent status of medicines on the WHO Model List of Essential Medicines; To place in the public domain a detailed report on the present (2010) patent status of medicines that were on patent in 2003 and those medicines added to the Model List since 2003 by country and level of development; and To analyze the patent status of these Essential Medicines by the development status of countries. The report describes the development of the protocol and presents a preliminary list of EML and corresponding patents in certain jurisdictions to illustrate the utility of the approach. Results will be discussed both in terms of global access and patents, and in the context of establishing standard, systematic, protocols for periodic patent searches related to EML content. 1 WORLD HEALTH ORGANIZATION, CONTINUITY AND CHANGE IMPLEMENTING THE THIRD WHO MEDICINES STRATEGY 2008--‐2013 20 (WHO Press, 3rd ed. 2009). 2 This report covers the EML up to and including updates until 2009

Opening up Magpie via semantic services

Magpie is a suite of tools supporting a ‘zero-cost’ approach to semantic web browsing: it avoids the need for manual annotation by automatically associating an ontology-based semantic layer to web resources. An important aspect of Magpie, which differentiates it from superficially similar hypermedia systems, is that the association between items on a web page and semantic concepts is not merely a mechanism for dynamic linking, but it is the enabling condition for locating services and making them available to a user. These services can be manually activated by a user (pull services), or opportunistically triggered when the appropriate web entities are encountered during a browsing session (push services). In this paper we analyze Magpie from the perspective of building semantic web applications and we note that earlier implementations did not fulfill the criterion of “open as to services”, which is a key aspect of the emerging semantic web. For this reason, in the past twelve months we have carried out a radical redesign of Magpie, resulting in a novel architecture, which is open both with respect to ontologies and semantic web services. This new architecture goes beyond the idea of merely providing support for semantic web browsing and can be seen as a software framework for designing and implementing semantic web applications