3 resultados para Quality management – Reference model – Service ecosystem – Quality of service – Web service – Service level management – Requirements engineering
em Cambridge University Engineering Department Publications Database
Resumo:
With the rapid growth of information and communication technology (ICT) in Korea, there was a need to improve the quality of official ICT statistics. In order to do this, various factors had to be considered, such as the quality of surveying, processing, and output as well as the reputation of the statistical agency. We used PLS estimation to determine how these factors might influence customer satisfaction. Furthermore, through a comparison of associated satisfaction indices, we provided feedback to the responsible statistics agency. It appears that our model can be used as a tool for improving the quality of official ICT statistics. 2008 Elsevier B.V. All rights reserved.
Resumo:
This paper is concerned with the role of information in the servitization of manufacturing which has led to the innovation of an organisations capabilities and processes as equipment manufacturers seek to offer services around their products (Neely 2009, Baines et al 2009). This evolution has resulted in an information requirement (IR) shift as companies move from discrete provision of equipment and spare parts to long-term service contracts guaranteeing prescribed performance levels. Organisations providing such services depend on a very high level of availability and quality of information throughout the service life-cycle (Menor et al 2002). This work focuses on whether, for a proposed contract based around complex equipment, the Information System is capable of providing information at an acceptable quality and requires the IRs to be examined in a formal manner. We apply a service information framework (Cuthbert et al 2008, McFarlane & Cuthbert 2012) to methodically assess IRs for different contract types to understand the information gap between them. Results from case examples indicate that this gap includes information required for the different contract types and a set of contract-specific IRs. Furthermore, the control, ownership and use of information differs across contract types as the boundary of operation and responsibility changes.