952 resultados para enterprise systems engineering
Resumo:
The maturation of the cruise industry has led to increased competition which demands more efficient operations. Systems engineering, a discipline that studies complex organizations of material, people, and information, is traditionally only applied in the manufacturing sector; however, it can make significant contributions to service industries such as the cruise industry. The author describes this type of engineering, explores how it can be applied to the cruise industry, and presents two case studies demonstrating applications to the cruise industry luggage delivery process and the information technology help desk process. The results show that this approach can make the processes more productive and enhance profitability for the cruise lines.
Resumo:
Part 7: Cyber-Physical Systems
Resumo:
An essential challenge for organizations wishing to overcome informational silos is to implement mechanisms that facilitate, encourage and sustain interactions between otherwise disconnected groups. Using three case examples, this paper explores how Enterprise 2.0 technologies achieve such goals, allowing for the transfer of knowledge by tapping into the tacit and explicit knowledge of disparate groups in complex engineering organizations. The paper is intended to be a timely introduction to the benefits and issues associated with the use of Enterprise 2.0 technologies with the aim of achieving the positive outcomes associated with knowledge management
Resumo:
Business practices vary from one company to another and business practices often need to be changed due to changes of business environments. To satisfy different business practices, enterprise systems need to be customized. To keep up with ongoing business practice changes, enterprise systems need to be adapted. Because of rigidity and complexity, the customization and adaption of enterprise systems often takes excessive time with potential failures and budget shortfall. Moreover, enterprise systems often drag business behind because they cannot be rapidly adapted to support business practice changes. Extensive literature has addressed this issue by identifying success or failure factors, implementation approaches, and project management strategies. Those efforts were aimed at learning lessons from post implementation experiences to help future projects. This research looks into this issue from a different angle. It attempts to address this issue by delivering a systematic method for developing flexible enterprise systems which can be easily tailored for different business practices or rapidly adapted when business practices change. First, this research examines the role of system models in the context of enterprise system development; and the relationship of system models with software programs in the contexts of computer aided software engineering (CASE), model driven architecture (MDA) and workflow management system (WfMS). Then, by applying the analogical reasoning method, this research initiates a concept of model driven enterprise systems. The novelty of model driven enterprise systems is that it extracts system models from software programs and makes system models able to stay independent of software programs. In the paradigm of model driven enterprise systems, system models act as instructors to guide and control the behavior of software programs. Software programs function by interpreting instructions in system models. This mechanism exposes the opportunity to tailor such a system by changing system models. To make this true, system models should be represented in a language which can be easily understood by human beings and can also be effectively interpreted by computers. In this research, various semantic representations are investigated to support model driven enterprise systems. The significance of this research is 1) the transplantation of the successful structure for flexibility in modern machines and WfMS to enterprise systems; and 2) the advancement of MDA by extending the role of system models from guiding system development to controlling system behaviors. This research contributes to the area relevant to enterprise systems from three perspectives: 1) a new paradigm of enterprise systems, in which enterprise systems consist of two essential elements: system models and software programs. These two elements are loosely coupled and can exist independently; 2) semantic representations, which can effectively represent business entities, entity relationships, business logic and information processing logic in a semantic manner. Semantic representations are the key enabling techniques of model driven enterprise systems; and 3) a brand new role of system models; traditionally the role of system models is to guide developers to write system source code. This research promotes the role of system models to control the behaviors of enterprise.
Resumo:
To meet new challenges of Enterprise Systems that essentially go beyond the initial implementation, contemporary organizations seek employees with business process experts with software skills. Despite a healthy demand from the industry for such expertise, recent studies reveal that most Information Systems (IS) graduates are ill-equipped to meet the challenges of modern organizations. This paper shares insights and experiences from a course that is designed to provide a business process centric view of a market leading Enterprise System. The course, designed for both undergraduate and graduate students, uses two common business processes in a case study that employs both sequential and explorative exercises. Student feedback gained through two longitudinal surveys across two phases of the course demonstrates promising signs of the teaching approach.
Resumo:
The linguistic turn within philosophy has recently gained increased attention within social sciences. It can be seen as an attempt to investigate traditional philosophical problems by analysing the linguistic expressions used for these investigations. More generally, the phenomenon of language itself must be considered because of its (constitutional) impact on the investigation of phenomena in social sciences. In order to understand the consequences of the linguistic turn, its origins in philosophy are important and will be discussed. Within social sciences the linguistic turn already had significant impact. As an example, we will therefore discuss what directions the linguistic turn enabled for organizational analysis. Information Systems as a discipline must face the consequences of the linguistic turn as well. We will discuss how the linguistic framework introduced impacts the development of knowledge management and that of managerial and organizational support systems. This example shows what different perspectives the linguistic turn can provide for investigations within Information Systems. In addition, we will briefly outline the impact of the linguistic turn with respect to methodologies in Information Systems research.
Resumo:
The development of user expertise is a strategic imperative for organizations in hyper-competitive markets. This paper conceptualizes opreationalises and validates user expertise in contemporary Information Systems (IS) as a formative, multidimensional index. Such a validated and widely accepted index would facilitate progression of past research on user competence and efficacy of IS to complex contemporary IS, while at the same time providing a benchmark for organizations to track their user expertise. The validation involved three separate studies, including exploratory and confirmatory phases, using data from 244 respondents.
Resumo:
Enterprise Systems purport to bring innovation to organizations. Yet, no past studies, neither from innovation nor from ES disciplines have merged their knowledge to understand how ES could facilitate lifecycle-wide innovation. Therefore, this study forms conceptual bridge between the two disciplines. In this research, we seek to understand how ES could facilitate innovation across its lifecycle phases. We associate classifications of innovation such as radical vs. incremental, administrative vs. technical innovation with the three phases of ES lifecycle. We introduce Continuous Restrained Innovation (CRI) as a new type of innovation specific to ES, considering restraints of technology, business processes and organization. Our empirical data collection at the implementation phase, using data from both the client and implementation partner, shows preliminary evidence of CRI. In addition, we state that both parties consider the implementation of ES as a radical innovation yet, are less interest in seeking further innovations through the system.
Resumo:
Abstract - Enterprise Resource Planning (ERP) software has become the dominant strategic platform for supporting enterprise-wide business processes. However, single vendor ERP software systems have been criticised for not meeting specific organisation and industry requirements. An alternative approach ‘Best of Breed (BoB)’, integrates components of software from multiple standard package vendors, and in some cases custom components. The objective is to develop enterprise systems that are more closely aligned with the requirements of an organisation. Although this approach may not be common at present it is likely to grow in importance due to business needs and technology advances such as the componentisation of ERP software. A case study analysis of a BoB implementation at a global entertainment's company is used as a platform for the discussion of the issues associated with this strategy and a comparison is made with the single vendor ERP alternative. The analysis centres on the complexity of implementation, the differences in the levels of functionality and business fit and the maintenance requirements.
Resumo:
Despite a wealth of studies focusing on innovation, types of innovations and their outcomes, the process of innovation has largely been under studied. In 2010, Swanson calls for researchers to address the ‘innovation process black box’, to better understand how IT innovation potential can be exploited upon. This study derives and instantiates three unique and mutually exclusive innovation execution mechanisms: Continual, Progressive and Plug and Play. The innovation execution mechanisms of this study are developed with reference to Swanson (1994) Information Systems innovation types.
Resumo:
The first User-Focused Service Engineering, Consumption and Aggregation workshop (USECA) in 2011 was held in conjunction with the WISE 2011 conference in Sydney, Australia. Web services and related technology are a widely accepted standard architectural paradigm for application development. The idea of reusing existing software components to build new applications has been well documented and supported for the world of enterprise computing and professional developers. However, this powerful idea has not been transferred to end-users who have limited or no computing knowledge. The current methodologies, models, languages and tools developed for Web service composition are suited to IT professionals and people with years of training in computing technologies. It is still hard to imagine any of these technologies being used by business professionals, as opposed to computing professionals. © 2013 Springer-Verlag.
Resumo:
Despite the substantial organisational benefits of integrated IT, the implementation of such systems – and particularly Enterprise Resource Planning (ERP) systems – has tended to be problematic, stimulating an extensive body of research into ERP implementation. This research has remained largely separate from the main IT implementation literature. At the same time, studies of IT implementation have generally adopted either a factor or process approach; both have major limitations. To address these imitations, factor and process perspectives are combined here in a unique model of IT implementation. We argue that • the organisational factors which determine successful implementation differ for integrated and traditional, discrete IT • failure to manage these differences is a major source of integrated IT failure. The factor/process model is used as a framework for proposing differences between discrete and integrated IT.