5,679 research outputs found

    Inter-organizational fault management: Functional and organizational core aspects of management architectures

    Full text link
    Outsourcing -- successful, and sometimes painful -- has become one of the hottest topics in IT service management discussions over the past decade. IT services are outsourced to external service provider in order to reduce the effort required for and overhead of delivering these services within the own organization. More recently also IT services providers themselves started to either outsource service parts or to deliver those services in a non-hierarchical cooperation with other providers. Splitting a service into several service parts is a non-trivial task as they have to be implemented, operated, and maintained by different providers. One key aspect of such inter-organizational cooperation is fault management, because it is crucial to locate and solve problems, which reduce the quality of service, quickly and reliably. In this article we present the results of a thorough use case based requirements analysis for an architecture for inter-organizational fault management (ioFMA). Furthermore, a concept of the organizational respective functional model of the ioFMA is given.Comment: International Journal of Computer Networks & Communications (IJCNC

    The design co-ordination framework : key elements for effective product development

    Get PDF
    This paper proposes a Design Co-ordination Framework (DCF) i.e. a concept for an ideal DC system with the abilities to support co-ordination of various complex aspects of product development. A set of frames, modelling key elements of co-ordination, which reflect the states of design, plans, organisation, allocations, tasks etc. during the design process, has been identified. Each frame is explained and the co-ordination, i.e. the management of the links between these frames, is presented, based upon characteristic DC situations in industry. It is concluded that while the DCF provides a basis for our research efforts into enhancing the product development process there is still considerable work and development required before it can adequately reflect and support Design Co-ordination

    Deliverable JRA1.1: Evaluation of current network control and management planes for multi-domain network infrastructure

    Get PDF
    This deliverable includes a compilation and evaluation of available control and management architectures and protocols applicable to a multilayer infrastructure in a multi-domain Virtual Network environment.The scope of this deliverable is mainly focused on the virtualisation of the resources within a network and at processing nodes. The virtualization of the FEDERICA infrastructure allows the provisioning of its available resources to users by means of FEDERICA slices. A slice is seen by the user as a real physical network under his/her domain, however it maps to a logical partition (a virtual instance) of the physical FEDERICA resources. A slice is built to exhibit to the highest degree all the principles applicable to a physical network (isolation, reproducibility, manageability, ...). Currently, there are no standard definitions available for network virtualization or its associated architectures. Therefore, this deliverable proposes the Virtual Network layer architecture and evaluates a set of Management- and Control Planes that can be used for the partitioning and virtualization of the FEDERICA network resources. This evaluation has been performed taking into account an initial set of FEDERICA requirements; a possible extension of the selected tools will be evaluated in future deliverables. The studies described in this deliverable define the virtual architecture of the FEDERICA infrastructure. During this activity, the need has been recognised to establish a new set of basic definitions (taxonomy) for the building blocks that compose the so-called slice, i.e. the virtual network instantiation (which is virtual with regard to the abstracted view made of the building blocks of the FEDERICA infrastructure) and its architectural plane representation. These definitions will be established as a common nomenclature for the FEDERICA project. Other important aspects when defining a new architecture are the user requirements. It is crucial that the resulting architecture fits the demands that users may have. Since this deliverable has been produced at the same time as the contact process with users, made by the project activities related to the Use Case definitions, JRA1 has proposed a set of basic Use Cases to be considered as starting point for its internal studies. When researchers want to experiment with their developments, they need not only network resources on their slices, but also a slice of the processing resources. These processing slice resources are understood as virtual machine instances that users can use to make them behave as software routers or end nodes, on which to download the software protocols or applications they have produced and want to assess in a realistic environment. Hence, this deliverable also studies the APIs of several virtual machine management software products in order to identify which best suits FEDERICA’s needs.Postprint (published version

    Embedded intelligence for electrical network operation and control

    Get PDF
    Integrating multiple types of intelligent, mulitagent data analysis within a smart grid can pave the way for flexible, extensible, and robust solutions to power network management

    A Practical Example for Model-Driven Web Requirements

    Get PDF
    The number of approaches for Web environments has grown very fast in the last years: HDM, OOHDM, and WSDM were among the first, and now a large number can be found in the literature. With the definition of MDA (Model- Driven Architecture) and the acceptance of MDE (Model-Driven Engineering) techniques in this environment, some groups are working in the use of metamodels and transformations to make their approaches more powerful. UWE (UMLBased Web Engineering) or OOWS (Object-Oriented Web Solutions) are only some examples. However, there are few real experiences with Web Engineering in the enterprise environment, and very few real applications of metamodels and MDE techniques. In this chapter the practical experience of a Web Engineering approach, NDT, in a big project developed in Andalusia is presented. Besides, it shows the usability of metamodels in real environments

    Anthropocentric perspective of production before and within Industry 4.0

    Get PDF
    Abstract This paper presents a systematic literature review (SLR) of the anthropocentric perspective of production before and after (or, better, within) Industry 4.0. We identify central research clusters regarding traditional Anthropocentric Production Systems (APS) and Anthropocentric Cyber Physical Production Systems. By comparing the two perspectives, we are able to analyse new emerging paradigms in anthropocentric production caused by Industry 4.0. We further make prediction of the future role of the human operator, his needed knowledge and capabilities and how assistance systems support the Operator 4.0. Our paper gives a brief outlook of current and needed future research. It builds grounds for further scholarly discussion on the role of humans in the factory of the future

    EMBRACING DI[VERSHTY: A FRAMEWORK FOR RESOLVING CONFLICT BETWEEN MIS AND MANUFACTURING

    Get PDF
    Turf wars between corporate Management Information Systems (MIS) and corporate manufacturing threaten the success of computer integrated manufacturing (CIM). Cooperation between MIS and manufacturing is essential in the planning, design and implementation of cross-functional information systems, and it is information systems that are the biggest source of CIM failure. This paper takes the position that both MIS and manufacturing have been slow to recognize their contrasting corporate cultures and to deal with resolving the conflict between the two groups. In order to better understand the conflict between MIS and manufacturing, the authors identify the technical and organizational differences. From this, seven points of conflict are identified that are the focal point of the turf wars. A framework for resolving the MIS/manufacturing conflict, based on prior research in organizational diversity, is presented. An empirical research agenda is proposed that will test the framework for applicability, completeness and accuracy. In conclusion, the authors recommend collaborative research between the MIS and manufacturing communities to study the technical and organizational issues related to CIM
    corecore