Download 4 EQUIPMENT LIFECYCLE IN DATASTREAM 7i

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Investment management wikipedia , lookup

Transcript
EUROPEAN ORGANIZATION FOR NUCLEAR RESEARCH
ORGANISATION EUROPÉENNE POUR LA RECHERCHE NUCLÉAIRE
CERN - TS Department
EDMS Nr: 590570
Group reference: TS-CSE
TS-Note-2005-036
25 May 2005
MIGRATION OF MP5 TO D7I
P. Martel, B. Vercoutter
Abstract
In this document are presented some of the new functionalities available in the new release of
Datastream 7i. The features now available can substantially improve the performance of the
system as well as reduce the overall administrative load to manage work orders. A brief
overview of how the lifecycle of an equipment is handled in the Datastream 7i is given as well
as a comment on the state of the known systems performance issues.
Presented at the 2nd TS Workshop
Archamps, France, May 24 – May 26, 2005
1
INTRODUCTION
In this document we present a few functionalities and techniques that are expected to help the
maintenance managers in their daily activities as well as improving the system’s performance. It is
important to notice that this document is not exhaustive and is mainly focused on the currently used
modules.
We also discuss briefly the Datastream 7i concept of equipment’s lifecycle from its
conception to manufacturing, operation (maintenance) and finally dismantling
Finally, we discuss a few issues concerning system performance and their current status.
2
NEW FUNCTIONALITIES AND POSSIBILITIES
2.1
Key Performance Indicators – KPIs
Datastream 7i supports the definition of maintenance management Key Performance Indices,
KPI, indices which are calculated each time the user accesses the system’s start centre (home page).
The data used in the KPI’s are defined by the respective TS department service managers and
implemented by the support team. The KPI’s offer the responsible service manager a rapid overview
of how his different services perform and what can be expected in terms of appreciation by the user
communities.
Figure 1 – Key Performance Indicators
As the KPI’s are recalculated every time the manager logs into the system they offer both a
global perspective of the service’s maintenance performance and a rapid identification of any
potentially serious problems.
Additionally a careful use of KPIs will reduce the burden of running manually report
generations to review the performance of a given maintenance contractor or system installation.
2.2
Workload Inbox
The Workload Inbox display actions or activities that are in a pending state; offering a rapid
overall view of situations requiring more detailed attention along with the KPIs.
The Workload Inbox is also displayed every time the system home page is accessed by the user.
2
Figure 2 – Workload Inbox
All the system functions required to complete actions or activities associated with an Inbox
entry may now be called directly from the Workload Inbox.
By configuring the Inbox queries to show open work orders by trade and by person, the Inbox
may be used as an efficient tool to schedule work lots; clicking on an entry, will open the job
scheduling function for easy assignment of a work order to an agent.
2.3
Exporting Data from Datastream 7i
In this release of the system the results of a query can be easily exported to a tabular (e.g.
Excel) format from D7i, allowing the generation of simple lists directly by the user, without the need
to first run a report generator.
This system functionality should lead to a reduction of the demands for the creation of new
specific user reports to the system support team as virtually any report requiring access to a singletable now can be directly generated by the user instead. As many other information management
systems, D7i supports the saving and retrieval of query criteria permitting the reuse of queries without
the need for reentering data.
2.4
Request acknowledgement message
Datastream 7i can be configured to send an acknowledgement message (e.g. a “ticket”) to the
user that originates a work request to ensure proper follow-up of requests. This feature helps the
support team to organize and efficiently work with support cases. Incoming problems and requests are
gathered and organized in D7i, and distributed among the TS support managers with ease. Support
cases are referenced via tickets, which can be assigned and re-assigned to support experts, while
tracked and supervised by support managers. User information, problem description, progress,
solutions, time spent and more information are all referenced via the ticket. This also permits the user
to follow the progress of his request.
3
3
NEW TECHNIQUES
3.1
Datastream 7i as the data source for analysis
Datastream 7i can be used as the data source of a maintenance dashboard. If the
decomposition of the Mean Time To Repair (MTTR) [1] value is desired, then Datastream 7i can be
customised in order to collect more data and thus allow a better precision for the break down sub
values.
Datastream 7i can also be used to calculate (totally or partially) the Facilities Condition Index
(FCI), which is a comparative indicator of the relative condition of facilities. The FCI is expressed as
a ratio of the cost of remedying maintenance deficiencies relative to the current replacement value.
3.2
Portable devices
Portable devices allow an effortless automated work order creation in situ, which eliminates
the need to create manually paper notes in the field and later input them into the system. The support
of portable devices has been considerably simplified due to a much more flexible system architecture.
3.3
Service Requests originated directly by the user
Some Datastream customers having big facilities and large user communities (e.g. a
university campus) have been taking advantage of a new mechanism that permits services order to be
created in external application programs and subsequently to be submitted to D7i. By integrating the
management and creation of D7i work orders into an organisational-wide application program
framework these customers have managed to reduce the associated administrative overhead.
4
EQUIPMENT LIFECYCLE IN DATASTREAM 7I
The planned merge of the Datastream 7i account where the manufacturing data for the LHC
and the LHC experiments are managed with the account used for maintenance management of
CERN’s infrastructure will support the integration of the equipment’s different lifecycle phases into a
single system. This integration will simplify a number of work processes. The processes that are
typically concerned by this are:
 The creation in D7i of equipment installed and operated that later will have to be
maintained.
 The browsing of all stored events that are related to the manufacturing and installation
phases of equipment that are in operation.
5
SYSTEM PERFORMANCE AND STATUS
Datastream 7i has been in production for more than 2 months. Even though the system
performance is not at the level expected by the user community, it is important to recall that no major
problem has occurred and that all ‘denial-of-service’ situations had to do with underlying system
software (namely, SunOS and Oracle).
It is still not clear in what proportion existing performance problems are related to the
database server, the application server or the network. Analysis of the situation and comparisons are
being done, and possible alternatives studied.
An important issue concerns the deployment of Datastream 7i by our contractors, which
greatly extends the use of the system permitting the Organisation a better control of said contractors.
The extended deployment also however creates new problems related to system performance, security
issues and remote print stations.
With the introduction of Datastream 7i, CERN user and system support is being streamlined,
offering a single entry point ([email protected]), and a unique web site for all matters
concerning maintenance management and its support (http://cmms.web.cern.ch/cmms/home.htm).
4
REFERENCES
[1] T. Pettersson, LHC Maintenance Policy and Requirements, Chamonix XIV, EDMS 536848
5