Building Situational Applications for Virtual Enterprises

Building Situational Applications for Virtual Enterprises

Lai Xu (Bournemouth University, UK) and Paul de Vrieze (Bournemouth University, UK)
DOI: 10.4018/978-1-4666-9787-4.ch050
OnDemand PDF Download:
$30.00
List Price: $37.50

Chapter Preview

Top

Introduction

Traditionally enterprise information systems have been used by big organisations to manage their customers and customer related activities. Most of them are centrally control systems, mission critical, and designed for the long term. Enterprise information systems have thus become critical for organisations. The ability to modify their behaviour by modifying existing processes or by adding new ones has been limited, often by design. It is a great challenge for these systems to adapt to today's business speed. Today business users demand many situational applications which can handle business needs within a short time and normally do not need to support so many users. Traditional enterprise information systems are not designed for such situational applications for virtual enterprises. In this chapter, we present a design methodology for building situational applications for virtual enterprises. We discuss how situational applications should be modelled so that existing resources can be identified and executed. A real world situational application in electrical power systems is discussed.

There is increased pressure to build enterprise applications quickly in order to respond to situational needs of the business (de Vrieze, Xu & Xie, 2010; Xu et al. 2011). Many of these applications never get delivered because they are too difficult to write, too costly to implement, too brittle to customize and maintain once deployed, or cannot be provided in a sufficiently timely fashion. As a result, many of the needs are addressed by business people who have some knowledge on IT techniques creating often inadequate solutions using tools like Excel, Access and Visual Basic for Applications.

Business process management is the technology of choice for handling long-lived dynamic software. Traditionally it has been hard to configure such systems, and many of the activities have been linked up in ad-hoc ways (Nguyen et al, 2009a, 2009b). Nowadays there is a large and growing provision of web services that could be very valuable in supporting business goals. Their use, procurement and provisioning is exceedingly simple. While the use of web services is relatively easy, they represent programming interfaces, and are not always straightforward from the perspective of end-users (even power users). Enterprise business process mashups aim to address these issues by both providing end-users the power to define custom processes, as well as to use web services, and information structured in various ways.

Enterprise business process mashups (Xu et al. 2011), are enabled through development and deployment services that use and allow for the execution of what can be seen as a domain specific language. These development and deployment services, combined with a “situational” mindset and methodology, can offer significant advantages. Unlike traditional enterprise applications, situational enterprise applications are relatively simple. They are not missioning critical for organisations. Many situational applications are developed at the point of need with short development cycle, not under central IT control with little or no recognized budget.

The situational applications under consideration will not replace core business applications, such as ERP (Enterprise Resource Planning), SCM (Supply Chain Management), CRM (Customer Relationship Management) etc (de Vrieze, Xu & Xie, 2010). They address different needs, and may be built for just a handful of users. Situational enterprise applications could be used for only a few weeks or months, or address a small piece of functionality. For example, within the perimeter ERP applications, departmental operation solutions, such as vacation scheduling, seminar and presentation management, purchase procedure management within a work unit, etc., normally are not included in an organisational ERP system. Such functionality, customized towards the department, can however be beneficial for individual departments. Much of the role of departmental staff on a daily basis involves such applications, and improved support for automation could significantly enhance productivity.

Key Terms in this Chapter

Enterprise Systems: Defined as the large complex computing systems which handle large volumes of data and enable organisations to integrate and coordinate their business processes. Such systems normally are a single system central to organisations and ensure that information can be shared across all functional levels and management hierarchies.

Enterprise Resource Planning (ERP) System: A software system which typically a suite of integrated applications that a company can use to collect, store, manage and interpret data from many business activities, including: product planning, cost, manufacturing or service delivery, marketing and sales, inventory management, shipping and payment, etc.

Incident Notification System: A software application which incident information flows among stakeholders and customers.

Enterprise Business Process Mashup: A software platform which allows both providing end-users the power to define customised processes, as well as to use web services, and information structured in various ways.

Customer Relationship Management (CRM) System: A software system which deals with existing and potential customers, and coordinates all customer interaction processes in sales, marketing, and service.

Situational Enterprise Applications: Enterprise applications which are relatively simple and not missioning critical for organizations. Lots of them can be developed at the point of need, with short development cycles, outside the direct central IT control, and with little or no recognized budget.

Supply Chain Management (SCM) System: A software system which automatically flow information between firm and suppliers to optimize production and delivery. It links activities involved in buying, making, moving a product.

Complete Chapter List

Search this Book:
Reset