A Multi-Scan Labeled Random Finite Set Model for Multi-object State Estimation

State space models in which the system state is a finite set--called the multi-object state--have generated considerable interest in recent years. Smoothing for state space models provides better estimation performance than filtering by using the full posterior rather than the filtering density. In multi-object state estimation, the Bayes multi-object filtering recursion admits an analytic solution known as the Generalized Labeled Multi-Bernoulli (GLMB) filter. In this work, we extend the analytic GLMB recursion to propagate the multi-object posterior. We also propose an implementation of this so-called multi-scan GLMB posterior recursion using a similar approach to the GLMB filter implementation

CRM packaged software: a study of organisational experiences

Customer Relationship Management (CRM) packaged software has become a key contributor to attempts at aligning business and IT strategies in recent years. Throughout the 1990s there was, in many organisations strategies, a shift from the need to manage transactions and toward relationship management. Where Enterprise Resource Planning packages dominated the management of transactions era, CRM packages lead in regard to relationships. At present, balanced views of CRM packages are scantly presented instead relying on vendor rhetoric. This paper uses case study research to analyse some of the issues associated with CRM packages. These issues include the limitations of CRM packages, the need for a relationship orientation and the problems of a dominant management perspective of CRM. It is suggested that these issues could be more readily accommodated by organisational detachment from beliefs in IT as utopia, consideration of prior IS theory and practice and a more informed approach to CRM package selection

Risky business: when a CRM vendor masqueraded as an ERP specialist

Taking a social shaping perspective we unpack the development trajectory of a packaged software product to show, that contrary to mainstream accounts, design is not completely specified a-priori and that the process continues throughout implementation, and use. We show how developers, in this case third party vendors, can continue to engage in shaping packages during implementation and also how users contribute to the development effort. In particular, we illustrate how a customer relationship management package application targeted at a particular organisational function was configured to make an enterprise wide system and the key role of the vendor in this effort. To do this we refer to a 3- year qualitative field study of an expanding United Kingdom based consultancy company undergoing extreme ICT related change. This empirical research is used to explore an often ignored phenomenon, that of the role of vendors in appropriating ICTs and the potential risks they bring. Through this, we highlight the plight and responsibilities of low-level organisational actors in this process in cognisance of the fact they usually have a minor role in ICT selection but become a major player in dealing with vendors at the implementation stage when the devil is truly in the detail. The risks we identify relate to: vendor sales pitches of products as specifically related to their capabilities and the products they put forward; the calling upon of organisational resources by vendors; vendor knowledge of the application are and the actual ‘social’, ‘technical’ and ‘organisational’ capabilities of vendors to deliver a working product. We also point to the risks managers in vendor and consumer organisations create by placing their staff in difficult conditions within appropriation processes. The implications of our work centre on the need for further research related to: vendor/developer risks of packaged software, custom and open source projects; notions of professionalism and ethics in the software industry and project working conditions