Sole Source Form with Mtelligence Mtell for Predictive Analysis Software Professional ServicesDate: 10-13-2014
Item or Service: Mtell Predictive Analysis / CBM Software and Professional Services
❑ Sole Source: Item is available from only one vendor. Item is one -of -a kind
item and is not sold through distributors. Manufacturer is a
sole distributor.
Refer to instructions on 2nd page for completion.
JUSTIFICATION: (Attach additional pages if needed)
The City's Supervisory Control and Data Acquisition (SCADA) System was recently re -designed under the
direction of our 2013 SCADA Master Plan. This master plan was developed to increase capability and capacity
of our current SCADA System making it more valuable and efficient as a data collection management tool.
Part of this improvement is the incorporation of Condition Based Monitoring (CBM) software and related
programing needed to combine data captured by SCADA and merging it into the City's Infor Asset Management
System. This software is vendor specific and is the only one authorized by infor Systems and capable of
meeting the monitoring and functionality requirements of the City's SCADA and Asset Management Systems,
Mtell CBM Software is patented and as such is only distributed by the manufacture Mtelligence Corporation
(DBA Mtell). .
*Please see attached the attached Sole Source Letter resolution designating of Mtelligence Corporation for Mtell
Software.
CERTIFICATION:
I am aware of the requirements set forth in the City's Purchasing Policy & Procedures Manual for competitive bidding and the
established criteria for justification for sole source/sole brand purchasing. I have gathered technical information and have made
a concerted effort to review comparable/equal equipment. I hereby certify as to the validity of the information and feel confident
that this justification for sole source/sole brand meets the City's criteria and is accurate.
Dennis Teller
Requestor (Print Name ) or
Department Manager
Council Approval
Date: 101Q
Purchasing
Approval:
Purchasing Manager
F3
Mtell Sole Source Justification
To: City of Meridian Idaho — Water Division
From: Mtelligence Corporation (DBA Mtell)
Date: 1 October, 2014
Re: Sole Source Justification for Mtell Predictive Analytics / CBM Software & Professional Services
This letter is intended to serve as a Sole Source justification for the Mtell Predictive Analytics / CBM
Software & Professional Services at the City of Meridian ID as of the date indicated above for the
following reasons:
1. Product includes proprietary intellectual property which is covered under US Patent # 8,380,842
B2, issued Feb 19, 2013 — "System and Methods for the Universal Integration of Plant Floor
Assets and a Computerized Management System" (See document Mtell_Patent-08380842.pdf)
a. This intellectual property will be used for connecting data contained in the City of
Meridian Idaho — Water Division's SCADA (supervisory control and data acquisition)
System with the Infor computerized maintenance management system (IPS 8.3).
2. Mtell Advanced is a condition monitoring solution using machine learning that stops machines
breaking down, makes them last longer, reduces maintenance costs and results in net increases
in production output on any processes where it is installed.
a. The Mtell Product contains unique features (including Machine Learning via Artificial
Intelligence algorithms) which support a predictive analytic business model with the
intent to reduce costs / expenses / unplanned downtime events.
3. Difference of other Condition Monitoring Techniques:
a. Ideal equipment protection must recognize precise failure modes, time -to -failure, and
automatically learn and adapt with little intervention as operating conditions change.
Most other condition monitoring products only execute anomaly detection; using
modeled estimates against actual measured performance to determine if variances are
apparent. They do not do precise pattern recognition to learn normal and exact failures
and they provide much later stage warnings; often occurring only after damage has
already occurred.
b. Whereas, the Mtell product executes very precise pattern recognition of changes in
stream signals produced from sensors on and around the equipment being monitored.
As a result, the technology detects extremely early onset of degradation through multi-
variate differences across all the streaming signals and also temporal distinctions; tiny
changes in those signals offset by time.
1550 Hotel Circle North, Suite 120, San Diego, CA 92108 PH: 619-295-0022 URL: www.mtell.com
F3
4. Professional Services Subject Matter Expertise for the installation/ configuration/ support of
the Mtell Advanced product is possessed by Mtell only.
5. Mtell is the only authorized provider for product training, support, maintenance and upgrades
of the referenced product.
Submitted by:
Paul Rahilly
CEO
Mtelligence Corporation (DBA Mtell)
1550 Hotel Circle North, Suite 120, San Diego, CA 92108 PH: 619-295-0022 URL: www.mtell.com
(12) United States Patent
Bates et al.
(54) SYSTEM AND METHODS FOR THE
UNIVERSAL INTEGRATION OF PLANT
FLOOR ASSETS AND A COMPUTERIZED
MANAGEMENT SYSTEM
(75) Inventors: Alex Bates, San Diego, CA (US); Paul
Rahilly, San Diego, CA (US); Scott
MacNab, Wilsenville, OR (US); Gordon
Brooks, San Diego, CA (US)
(73) Assignee: Mtelligence Corporation, San Diego,
CA (US)
O Notice: Subject to any disclaimer, the term of this
patent is extended or adjusted under 35
U.S.C. 154(b) by 1638 days.
(21) Appl. No.: 11/740,404
(22) Filed: Apr. 26, 2007
(65) Prior Publication Data
US 2008/0271057 Al Oct. 30, 2008
(51) Int. Cl.
G06F 15/16 (2006.01)
G06F 151173 (2006.01)
G08B 21100 (2006.01)
(52) U.S. Cl. ......... 709/224; 709/217; 340/501; 340/679
(58) Field of Classification Search .................. 709/246,
709/217, 224; 340/501, 679
See application file for complete search history.
(56) References Cited
U.S. PATENT DOCUMENTS
5,764,155 A 6/1998 Kertesz et al.
6,192,325 Bl 2/2001 Piety et al.
6,266,713 Bl 7/2001 Karanarn et al.
6,411,963 Bl 6/2002 Seese et al.
6,421,571 B1 7/2002 Spriggs et al.
6,466,934 B2 10/2002 Seese et al.
6,513,044 132 1/2003 Seese et al.
6,587,900 BI 7/2003 Wiscbinski
mom
can
uuAuuduuwiiumnuiuiuii�uui�u�iuAuiuii
(1o) Patent No.: US 893809842 B2
(45) Date of Patent: Feb. 19, 2013
6,600,964 132 7/2003 Hess et al.
6,687,761 B 1 2/2004 Collins et al.
6,775,576 132 8/2004 Spriggs et al.
6,813,587 B2 11/2004 McIntyre et al.
6,889,096 B2 5/2005 Spriggs et al.
6,901,432 B2 5/2005 Peterson et al.
6,993,576 Bl 1/2006 Labedz et al.
7,085,841 B2 8/2006 Edwards et al.
7,117,119 B2 10/2006 Van Dyk et al.
7,120,558 132 10/2006 McIntyre et al.
7,133,727 B2 11/2006 Van Dyk et al,
7,146,230 B2 12/2006 Glanzer et al.
(Continued)
OTHER PUBLICATIONS
Mathew et al., A review of the MIMOSA OSA-EAI database for
condition monitoring systems., Jul. 2006 http://epiints,qut.edti.ati/
8290/.*
(Continued)
Primary Examiner — Joseph Avellino
Assistant Examiner — James Conaway
(74) Attorney, Agent, or Firm — Cooley LLP
(57) ABSTRACT
A server platform and a method to integrate a plurality of
diverse plant floor equipment with at least one computerized
management system in a manufacturing operational or main-
tenance system, The server platform includes a plurality of
plant floor drivers adapted to communicatively interface with
a plurality of diverse plant floor data sources. The server
platform further includes at least one computerized manage-
ment system driver adapted to communicatively interface
with the at least one computerized management system. The
server platform also includes a message translator adapted to
broker communication between the plant floor data sources
and the at least one computerized management system using
an open standard. The server platform, using the open stan-
dard, enables a universal enterprise type taxonomy across the
plant floor data sources and the at least one computerized
management system.
57 Claims, 10 Drawing Sheets
US 8,380,842 B2
Page 2
U.S. PATENT DOCUMENTS
2006/0058987 Al* 3/2006 Kumar et al . ..................... 703/2
2006/0074498 Al 4/2006 Kalan et at.
7,151,966 Bl
12/2006
al.
Baier et al
2006/0133412 Al 6/2006 Callaghan
7,181,493 B2
2/2007
English al.
2006/0164296 Al 7/2006 LaMothe et al.
7,512,906 Bl*
3/2009
Baier et al .....................
715/866
2006/0224361 Al 10/2006 McIntyre l.
7,548,970 B2
6/2009
Labedz et al.
t 1.
2006/0235951 Al 10/2006 Edwards et
7,606,919 B2
10/2009
Labedz et al.
2006/0259603 Al 11/2006 et al.
1,
8,200,620 B2 *
6/2012
Aki ama et al ...............
707/609
KeeverShrade
2007/0143162 Al * 6/2007 Keever et 705/7
2001/0001851 Al
5/2001
Piety et al.
t al ....................
2007/0226317 Al * Rydberg et 709/218
2001/0032202 Al
10/2001
Seese et al.
4/2007 Hall ..................
2008/0079560 Al * 4/2008 Hall et al . ..................... 340/506
2001/0032206 Al
10/2001
Seese et al.
2010/0082130 Al* 4/2010 et al ..................... 700/83
2002/0103828 Al
8/2002
Kupiec et al.
2012/0078403 Al* 3/2012 Cahill Cahill et al. ................. 700/95
2002/0116486 Al
8/2002
Toure et al.
a l
2012/0173671 A t * 7/2012 Callaghan et al ............. 709/217
2002/0161674 Al*
10/2002
Scheer ............................
705/28
2002/0198990 Al
12/2002
Bradfield et al.
OTHER PUBLICATIONS
2003/0004598 Al
1/2003
Morris
2003/0004987 Al
1/2003
Glanzer et al.
MIMOSA, MIMOSA's Open System Architecture for Enterprise
2003/0023518 Al*
1/2003
Spriggs et al ...................
705/28
Application Integration (OSA-E.AI) Technical Architecture Smn-
2003/0028269 Al
2/2003
Spriggs et al.
mary, Dec. 2006.*
2003/0126222 Al
7/2003
Peterson et al.
OpenO&M, Collaborative Operations & Maintenance Using MIMO-
2003/0200060 Al
10/2003
Eryurek et al.
SA's OSA-EAI and ISA-95/B2MML, Oct. 2006
2003/0200130 Al
2004/0024572 Al
10/2003
2/2004
Kali et al.
Pagnano et al.
MIMOSA; MIMOSA's Open System Architecture for Enterprise
2004/0143628 Al
7/2004
Bradford et al.
Application Integration (OSA-EAI) Technical Architecture Sum -
2004/0153594 Al
8/2004
Rotvold et al.
mary; May 2006.
2005/0010931 Al
1/2005
Langkafel et al.
MIMOSA; MIMOSA OSA-EAI, Common Conceptual Object
2005/0027379 Al
2/2005
Dyk et al.
Mode, Version 3.0; Updated: May 2, 2006.
2005/0044532 Al
222005
Pfarder et al.
Machinery Information Management Open Systems Alliance; Tech -
2005/0060408 Al
3/2005
McIntyre et al.
XML -Services Client & Server, Version 3.0; Jim. 16, 2006.
2005/0177533 Al
8/2005
Herzog
2005/0267882 Al*
12/2005
Aupperlee et al .................
707/4
" cited by examiner
U.R. Patent
/
k
)
§
�
/
Fe .19 2013 Sheet 1 of 10 US 8,380,842 G2
U.R. Patent Fe ,}9 20!] Sheet 2 0 !O
/
c /
%
�
\
US 89380,842 G2
\)
c
2
{
e
}
§
�
�
\
•{ �
/ (
v !
c /
%
�
\
US 89380,842 G2
\)
c
2
{
U.S. Patent
Feb. 19, 2013 Sheet 3 of 10 US 8,380,842 B2
U.S. Patent
c�3
Feb. 19, 2013 Sheet 4 of 10 US 8,380,842 B2
U.R. Patent
/
�
/
Fe ,!9 2n}]
0
tn
Sheet 5 of !O
CA
US 8 380 842 B2
5
\
7
U.S. Patent
Feb. 19, 2013 Sheet 6 of 10 US 89380,842 B2
ago 0 0 0
sm
M
C
�G
0 0 0
,I- vl 110
N
ago 0 0 0
sm
M
C
�G
0 0 0
,I- vl 110
U.S. Patent Feb. 19, 2013 Sheet 7 of 10
US 89380,842 B2
G
N
a�g
v
O N
U O
15 N
-au
O
N
_
N N
O �.,
v, P• v
ei
Q-
•cJ
rq �+� � "�S'
� Vl y
N N fd
R (N
Id
O
�
p •N
<�C
O
O
O
US 89380,842 B2
G
N
U.S. Patent
Feb.19, 2013
M
Sheet 8 of 10
9
KAI
u
Q
N
3,
A]
m
US 8,380,842 B2
7
a� v Q w w
V
00Q
U.S. Patent
/
�
Fe ,!9 20!] Sheet 9 0 !O US 893809842 G2
� . �« \
j ƒ \ & §
e § • }
y § g
> � c
� » /
_
\
A
\
§
&
q
.0
j ( d
§)a
o
•
�
g
r
� . �« \
j ƒ \ & §
e § • }
y § g
> � c
� » /
_
\
A
\
§
&
V.S. Patent Feb. 19, 2013 Sheet 10 of 10 US 8,380,842 B2
booker
0
0
US 8,380,842 B2
1
2
SYSTEM AND METHODS FOR THE
external vendor system is speaking the MIMOSA language,
UNIVE RSAL INTEGRATION OF PLANT
whichis notthe case today and is notlikelyto becomethe case
FLOOR ASSETS AND A COMPUTERIZED
any time soon.
MANAGEMENT SYSTEM
Manufacturers are drowning in a flood of real-time and
5 non -real time data and are losing revenues at the same time.
TECHNICAL FIELD
Therefore, there is a growing call for a manufacturing intel-
ligence solution that contextualizes the disparate data in a
Certain embodiments of the present invention relate to
balanced manner.
manufacturing operational and maintenance systems and
Further limitations and disadvantages of conventional, tra-
methods. More particularly, certain embodiments of the
10 ditional, and proposed approaches will become apparent to
present invention relate to a server platform and method for
one of skill in the art, through comparison of such systems
integrating a plurality of diverse plant floor equipment to at
and methods with the present invention as set forth in the
least one computerized management (CM) system by
enabling a universal enterprise type taxonomy across the
remainder of the present application with reference to the
plant floor data sources and the CM system using an open
r5 drawings,
standard.
BRIEF SUMMARY
BACKGROUND
An embodiment of the present invention comprises a
Large manufacturers today face extreme margin pressures
20 server platform for integrating a plurality of diverse plant
from low-cost producers, rising energy costs, and regulatory
floor equipment with at least one computerized management
and environmental restrictions. The need to improve asset
(CM) system. The serverplatform includes a plurality of plant
performance is very great. One barrier to improvement has
floor drivers adapted to operationally interface with a plural -
been the absence of a performance management solution
ity of diverse plant floor data sources to at least receive infor-
encompassing the various divisions of operations, mainte-
25 mation from the plant floor data sources. The server platform
nance, and finance, for example. With each division using its
also includes at least one CM system driver adapted to opera -
own performance metrics, it is difficult for optimal decisions
tionally interface with the at least one CM systern to at least
to be made, such as balancing reliability goals against asset
receive information from the at least one CM system. The
utilization goals,
server platform further includes a message translator adapted
Many people have been chasing the "holy grail" of self-
30 to broker conmiun icationbetweenthe plant floor data sources
diagnostics. Furthermore, there are many balanced score-
and the at least one CM system using an open standard.
cards and key performance indicator solutions being offered
Another embodiment of the present invention comprises a
in today's market. Many seem to be making similar claims
method of integrating a plurality of diverse plant floor equip -
including that their product will make a manufacturing pro-
ment with at least one computerized management (CM) sys-
cess ran better, faster, more efficiently, and with greater
35 tem. The method includes establishing first communication
returns. However, one of the greatest challenges for effec-
links between a server platform and a plurality of diverse
tively improving plant asset performance is that the necessary
plant floor data sources via a plurality of plant floor adapters
information is scattered across disconnected silos of data in
of the server platform to at least receive information from the
each department. Furthermore, it is difficult to integrate these
plant floor data sources. The method further includes estab-
silos due to several fundamental differences. For example,
40 lishing a second communication link between the server plat -
control system data is real-time data measured in terms of
form and at least one computerized management (CM) sys-
seconds, whereas maintenance cycle data is generally mea-
tem via at least one CM system adapter of the server platform
sured in temis of calendar based maintenance (e.g., days,
to at least receive information from the CM system. The
weeks, months, quarters, semi-annual, annual), and financial
method also includes discovering defined device objects and
cycle data is measured internis of fiscal periods. Furthermore,
45 types of the plurality of plant floor data sources via the first
different vendors of various equipment and enterprise sys-
communication links and importing the discovered device
tems tend to have their own set of codes (e.g., status codes)
objects andtypes into the server platform. The methodfurther
and are non compliant with any universal standard.
includes discovering defined management objects and types
An open standard is a standard that is publicly available
of the at least one CM system via the second communication
and has various rights to use associated with the standard. The
50 link and importing the discovered management objects and
term "open" is sometimes restricted to royalty -free technolo-
types into the server platform. The method also includes
gies while the term "standard" is sometimes restricted to
mapping the discovered objects and types to universal iden-
technologies approved by formalized committees that are
tifiers within the server platform, wherein the universal iden-
open to participation by interested parties and which operate
tifiers are defined in ani open standard.
on a consensus basis. As used herein, the term "open" refers
55 A further embodiment of the present invention comprises a
to a standard that is publicly available and that may be used
system for maintenance and asset management. The system
across vendors and customers.
includes a plurality of plant floor data sources adapted to
MIMOSA (Machinery Information Management Open
collect data from a plurality of plant floor equipment. The
Systems Alliance) is am operations and maintenance informa-
system also includes at least one computerized management
tion open systems alliance organized as a non-profit trade
60 (CM) system and a server platform adapted to integrate the
association which includes vendors, integrators and service
plurality of plant floor data sources with the at least one CM
providers, and end users. MIMOSA collaboratively develops
system based on a universal enterprise type taxonomy using
and promotes open standards for operations and maintenance
an open standard.
for fleets, plants, and facilities. MIMOSA produces vendor-
These and other advantages and novel features of the
neutral open information exchange standards. The MIMOSA 65 present invention, as well as details of illustrated embodi-
open standard provides a common language for vendors to
ments thereof, will be more fully understood from the follow -
use. However, the MIMOSA standard assumes that every
ing description and drawings.
US 8,380,842 B2
3
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a schematic block diagram of an embodiment of
a server platform for integrating a plurality of diverse plant
floor equipment with at least one computerized management
(CM) system;
FIG. 2 is a schematic block diagram of an embodiment of
a system for maintenance and asset management using the
server platform of FIG. 1;
FIG. 3 is an exemplary diagram graphically illustrating a
discrete mapping of device objects to CM objects.
FIG. 4 illustrates a flowchart of an embodiment of a method
of integrating a plurality of diverse plant floor equipment with
at least one computerized management (CM) system using
the server platform of FIG. 1;
FIG. 5 illustrates a flowchart of a first embodiment of a
method of semantically contextualizing vendor types to uni-
versal type identifiers;
FIG. 6 is an exemplary diagram graphically illustrating the
method of FIG. 5;
FIG. 7 illustrates a flowchart of a second embodiment of a
method of semantically contextualizing vendor types to uni-
versal type identifiers;
FIG. 8 is an exemplary diagram graphically illustrating the
method of FIG. 7;
FIG. 9 is an exemplary diagram graphically illustrating a
process for setting up (i.e., configuring) the server platform of
FIG. 1 within the system of FIG. 2; and
FIG. 10 is a diagram graphically illustrating a process for
actively running the system of FIG. 2 using the server plat-
form of FIG. 1.
DETAILED DESCRIPTION
FIG. 1 is a schematic block diagram of an embodiment of
a server platform 100 for integrating a plurality of diverse
plant floor equipment with at least one computerized man-
agement (CM) system for the purpose of maintenance and
asset management in an enterprise. The server platform 100
interfaces between plant floor data sources 210 of the plant
floor equipment 220 and a computerized management (CM)
system 230 (see FIG. 2), enabling a universal enterprise type
taxonomy across the plant floor data sources 210 and the CM
system 230 in a manufacturing operational or maintenance
environment, for example.
FIG. 2 is a schernatic block diagram of an embodiment of
a system 200 for maintenance and asset management using
the server platform of FIG. 1. The server platform 100 pro-
vides an open standard interface between the plant floor and
the CM system. In accordance with an embodiment of the
present invention, the server platform provides a common
MIMOSA -based interface between the plant floor and the
CM system, allowing interoperability between the plant floor
and the CM system. The server platform 100 provides the
tools and applications to contextualize information and bro-
ker com municationusing the MIMOSA standard vocabulary.
Information utilized by the MIMOSA message protocol is
organized and communicatedusingXML, in accordance with
an embodiment of the present invention.
The CM system 230 may comprise an enterprise asset
management (EAM) system or a computerized maintenance
management system (CMMS), for example. Other CM sys-
tems are possible as well. The CM system 230 typically acts
as a maintenance system but may also encompass other areas
such as costs and financials in which executives may have an
interest. In accordance with an embodiment of the present
4
invention, more than one CM system may be interfaced to the
server platform 100, even if the CM systems are of differing
kinds.
The plant floor equipment 220 may include, for example,
5 motors, compressors, engines, boilers, manufacturing
machines, or any other type of equipment that may be found
in a plant or factory environment. The plant floor data sources
210 include devices that provide access to operational or
measurement data of the plant floor equipment 220. For
io example, the plant floor data sources 210 may include on-line
condition monitoring devices, process control devices, asset
health devices, plant historian devices, transient measure-
ment devices, off-line sampling measurement devices,
15 hnnan-machine interface devices (e.g., for inspection -based
expert recommendations), or any other type of devices that
collect and output electronic data or information related to the
plant floor equipment 220.
The plant floor equipment 220 and the associated plant
20 floor data sources 210 tend to be of very diverse and disparate
types. Also, the CM systems tend to be quite unique in their
design and data structures. The server platform 100 provides
the integration that allows information collected from such
disparate types to be related and effectively used to trigger
25 work flows and generate work orders in the context of the
manufacturing operational or maintenance environment.
Typically, the serverplatform 100 is deployed atfacilityhead-
quarters and connects down to the plant floor systems from
there. However, if there is a large volume of equipment at a
30 plant and/or a large geographical distance between the plant
and headquarters over a wide area network, then a logical
gateway may be installed at the plant acting as a buffer to be
able to send data to the server platform 100 at facility head-
quarters.
35 Referring again to FIG. 1, the server platform 100 includes
a plurality of plant floor drivers or adapters 110 which allow
interfacing of the server platform 100 to the plant floor data
sources 210 to transmit and receive information between the
server platform 100 and the plant floor data sources 210. The
40 plant floor drivers/adapters 110 comprise software and/or
firmware type drivers/adapters, in accordance with certain
embodiments of the present invention. The plant floor drivers
110 may support various open communication protocols and
various proprietary communication protocols to allow access
45 to various types of real-time data and non -real-time data
associated with the plant floor equipment 220. Examples of
some of the plant floor side coriummication protocols include
OPC (an open connectivity protocol), modbus, and XML web
services. Other communication protocols are possible as
50 well.
In accordance with an embodiment of the present inven-
tion, the serverplatfonn 100 may be connected to a plant floor
data source 210 by entering security credentials and then
entering a network identifier and IP address of the data source
55 to which to connect. After connection, the various informa-
tion (objects and types) from the data source may be pulled
into the server platform 100.
The server platform 100 also includes at least one CM
system driver or adapter 120 which allows interfacing of the
so server platform 100 to at least one CM system 230 to transmit
and receive information between the server platform 100 and
the CM system 230. Again, the CM driver/adapter 120 com-
prises a software and/or firmware type driver/adapter, in
accordance with certain embodiments of the present inven-
i5 tion. The CM driver/adapter 120 supports a web services
protocol, in accordance with certain embodiments of the
present invention. For example, in accordance with an
US 8,380,842 B2
5
6
embodiment of the present invention, the CM driver/adapter
fiers, and mappings between management objects and univer-
120 supports the MIMOSA OSA-EAI Tech -XML -services
sal type identifiers. When avendortypeorobjectismappedto
web services protocol.
a universal type ID having a pre -defined semantic meaning,
At the heart of the server platform 100 is a message trans-
then the mapped vendor type or object has been contextual-
lator 130. The message translator 130 acts as a commnun ica-
5 ized.
tion broker between the CM system 230 and the plant floor
Non -semantic mappings may include, for example, map -
data sources 210 based on a universal type taxonomy. The
pings between device objects and universal object identifiers,
message translator 130 allows contextual ization of received
and mappings between management objects and universal
information with metadata and allows mapping of specific
object identifiers. At run time, the message translator 130 is
vendor types to universal type identifiers. The message trans-
to capable of accessing the mappings to facilitate brokered com-
lator 130 also allows discrete mapping of specific vendor
munication between the plant floor side and the CM system
objects to universal object identifiers. As a result, information
side. Once all of the mappings are complete, then all vendor
and data from both the plant floor side and the CM system side
objects and types that have been mapped are in the same
may be associated and related to each other in a meaningful
context which is defined by the universal standard (e.g., the
manner such that appropriate work flows may be triggered
15 MIMOSA standard). The MIMOSA open standard is exten-
and such that appropriate work orders may be generated
siblesuch that new rows may beadded tothe MIMOSA tables
and/or updated to facilitate maintenance and asset manage-
to support new vendor objects and types that may not conve-
nient of the enterprise. As used herein, the term vendor refers
niently map to a currently defined universal ID.
to the plant floor side and/or the CM system side of the
hn accordance with various embodiments of the present
enterprise. At run time, the message translator 130 translates
20 invention, the defined objects may include, for example,
back and forth between the plant floor side and the CM side
assets, segments, agents, measurement points, enterprise, and
from an object identifier standpoint and also from a semantic
site. An asset is a piece of physical equipment having a serial
type standpoint.
munber. A segment is a logical view of the physical equip -
The message translator 130 includes an open object meta-
ment, typically indicating a location of the physical equip -
data registry 131 which is a semantic database model. The
25 went within an enterprise, an agent is a human agent or a
open object metadata registry 131 includes pre -defined open
software agent that makes an observation, typically providing
standard universal identifiers and type taxonomies to which
human intelligence or artificial intelligence capability. Mea -
plant floor objects andtypes and CM system objects andtypes
surement points are outputs of sensors that measure various
are associated upon set up or configuration of the server
kinds of equipment parameters such as, for example, tem -
platform 100. The open object metadata registry 131 also
30 perature and pressure. An enterprise refers to the corporate
includes various tables which are updated at run time to keep
level of an organization. A site refers to a manufacturing
track of conditions such as, for example, status and priority. In
plant, facility, or potentially a fleet object such as a truck
accordance with an embodiment of the present invention, the
which has its own set of segments and assets which may be
open object metadata registry 131 is based on the MIMOSA
tracked for maintenance purposes.
standard and, therefore, uses MIMOSA -defined universal
35 In accordance with various embodiments of the present
object and type identifiers.
invention, the defined types may include, for example, asset
The message translator 130 also includes a mapper data-
types, work types, priority types, asset priority types, alarni
base 132 which stores the various mappings that occur
severity types, healthtypes, work priority types, and problem
between plant floor objects and types and universal objects
code types. An asset type is a nominal scale type which is a
and types, as well as mappings that occur between CM system
4o hierarchical categorization of assets based on functional
objects and types and universal objects and types. Again, the
properties, for example "pnmip" or "seawater pump". A work
universal objects and types are defined by an open standard
type is a nominal scale type which is a categorization of
(e.g., the MIMOSA open standard) and are stored in the open
maintenance activities, for example "preventive mainte-
object metadata registry 131. Types take on a semantic value.
nance" or "corrective maintenance". An asset priority type is
Asusedherein,the.termsvendor objects and types refer to
45 anordinal scale type forrankingthe relative importance ofthe
the various information and data that may be collected by the
asset. An alarm severity type is an ordinal scale type for
server platform 100 from the plant floor data sources 210 (i,e.,
ranking the relative importance of the severity of the alarm. A
device objects and device types) and the CM system 230 (i.e.,
health type is a nominal scale type for indicating the type of
management objects and management types). The terms open
health advisory, for example "vibration analysis" or "inst u -
standard objects and types refer to the various universal object
so mentation alert". A work priority type is an ordinal scale type
and type identifiers or codes defined by the open standard
for ranking relative importance of work, for example "high"
(e,g., MIMOSA object identifiers and MIMOSA type identi-
or "low". A problem code type is a nominal scale type which
fiers). By relating the various device objects and types and the
is a categorization of problems that can impact the health of
various management objects and types to the universal object
assets, for example "mechanical failure" or "electrical fail -
and type identifiers, a universal enterprise taxonomy may be
55 ure".
established across theplant floor data sources 210 andthe CM
Referring againto FIG. 1, the serverplatforni 100 includes
system 230, By establishing such a universal enterprise tax-
various software applications that reside in and run on the
onomy using such an open standard, a manufacturing intelli-
server platform 100 to provide various types of functionality.
gene solution that contextualizes the disparate data in a
The various software applications shown in FIG. 1 may be
balanced manner is provided.
6o discrete applications or may be combined in certain ways, in
The mappings stored in the mapper database 132 may
accordance with various embodiments of the present inven-
include semantic mappings and non -semantic mappings. For
tion. In the discovery phase of set up, the server platform 100
example, semantic mappings may include mappings between
detects plant floor monitoring systems and picks up device
device types and universal type identifiers, and mappings
definitions within the plant floor monitoring systems. Simi -
between management types and universal type identifiers,
65 larly, the server platform 100 detects CM systems and picks
Furthermore, for example, semantic mappings may include
up asset definitions within the CM systems. The server plat -
mappings between device objects and universal type identi-
form 100 includes a discovery application 140 adapted to
US 8,380,842 B2
7
automatically discover and import defined device objects and
types from the plant floor data sources 210 via the plant floor
driver/adapters 110, and adapted to automatically discover
and import defined management objects and types from the
CM system 230 via the CM system driver/adapter 120. The 5
discovery application 140 is used during set up for configur-
ing of the server platform 100 with particular plant floor data
sources 210 and a particular CM system 230.
The server platform 100 also includes a semantic mapping
R
or contextualizing application 150 adapted to semantically
map the discovered management types to pre -defined open
standard universal type identifiers, and adapted to semanti-
cally map certain device types to the pre -defined open staun-
dard universal type identifiers. When a device type gets n,
mapped to a universal type ID, and a CM system type gets
mapped to the same universal type ID, then the device type
and the CM system type become related via the common
universal type ID. Furthermore, certain device objects may
get mapped to certain management types. When a device 2c
object gets mapped to a management type, the device type
"inherits" all of the type information ofthe management type.
Examples of such semantic mappings are described below
herein with respect to FIGS. 5-8.
The server platform 100 further includes an assigning 25
application 160 adapted to assign first universal object iden-
tifiers to the device objects and second universal object iden-
tifiers to the management objects. The server platform 100
also includes a non-sennantic mapping application 170
adapted to non -semantically map the first universal object 3c
identifiers to the second universal object identifiers, thereby
relating the device objects to the management objects.
The MIMOSA open standard defines the format of the
universal IDs that are used for non -semantic assigmnents, 35
Such non -semantic assigimients may be used simply for
trackability and traceability purposes.
The server platform 100 further includes a manual map-
ping application tool 175 allowing for a user to manually
accomplish semantic and/or non -semantic mappings. Such 40
manual mappings maybe performed to refine automatic map-
pings performed by the server platform 100, or to accomplish
mappings that are not automatically handled by the server
platform 100.
In accordance with an embodiment of the present inven- 45
tion, the system 200 includes a graphic user interface 240
operationally interfacing to the server platform 100 and
adapted to allow a user to manage, for example, MIMOSA -
based mappings between defined device objects and types
imported from the plant floor data sources 210 andthe defined 50
management objects and types imported from the CM system
230 using the manual mapping application tool 175. The
graphic user interface 240 may be used for other purposes as
well such as, for example, allowing a human operator to
manually input information into the system 200. 55
For example, referring to FIG. 3, a CMMS system may
provide a CMMS defined object 310 being a motor definition
having a string, a serial number, and an object identifier in a
proprietary format for the CMMS vendor. The CMMS object
310 may be assigned to a single universal object identifier 320 60
by the assigning application 160 of the server platform 100.
Similarly, there may be five sensors on the plant side corre-
sponding to five different device objects 330 each measuring
a different parameter of the same actual motor on the plant
floor. Each of the five device objects 330 may correspond to a 65
different sensor measurement or reading for the motor. Each
of the five device objects 330 may have a string and a tag
8
identifier and get assigned to five different universal object
identifiers 340 by the assigning application 160 of the server
platform 100.
The non -semantic mapping application 170 may then auto-
matically map the five universal object identifiers 340 corre-
sponding to the five device objects 330 to the single universal
object identifier 320 corresponding to the CMMS object 310,
thereby relating the five sensors of the plain floor motor to the
CMMS motor object and storing this mapping in the mapper
database 132. Therefore, at nm time (i.e., during operation of
the system 200), rile -based work flows may be triggered and
work orders may be generated for the motor in response to
any of the five sensor measurements. As an alternative, the
manual mapping application tool 175 may be used by all
operator, via the graphic user interface 240, to manually per-
form the mapping. As a result there are five children UIDs
mapped to one parent UID to establish the relationship
between the CMMS motor definition and the five plant floor
sensor outputs.
Non -semantic mappings may be many -to -one, as in the
above example, or one-to-one. For example, for a compressor
definition in the CM system, there could be a number of
condition monitoring sensors which are fed into a plant his-
torian. When the mappings are created, connections are
defined between the plant floor tags (each of which corre-
spond to a sensor in this example) and the asset definitions in
the CM system. The server platform 100 may automatically
discover and enumerate the entities from the plant floor sys-
tems, however, the mapping/association to the CM system via
the universal open standard may require manual input.
The server platform 100 may further may include a condi-
tion -based maintenance application 180 adapted to generate
maintenance work orders in response to information col-
lected from the plant floor data sources 210 and the CM
system230. Certainkinds ofmaintenance work order include
predictive maintenance work orders, preventive maintenance
work orders, corrective maintenance work orders, and emer-
gency maintenance work orders. For example, the condition -
based maintenance application 180 may monitor a lower level
condition point of a plant floor valve providing temperature
and vibrationinfornation. Ifthe temperature exceeds 100° C.
and the vibration level exceeds a threshold value TVI. and the
valve status is "open", then a work order may be generated to,
for example, shut down the valve and/or have the valve
inspected.
As an option, the server platform 100 may also include a
perfornance measurement application 190 adapted to track
key performance indicators in response to information col-
lected from the plant floor data sources 210 and the CM
system 230. The performance measurement application 190
tracks key performance indicators in the forn of score cards,
in accordance with an embodiment of the present invention.
Such applications 180 and 190 process and analyze data put
information in a human intelligible form.
For example, a key performance indicator (KPI) may be the
overall facility maintenance cost as a percentage of the overall
facility equipment replacement cost. If the cost to maintain
the facility equipment is greater than the cost to replace the
facility equipment, then it is likely that too much maintenance
is being performed at the facility. Such a key performance
indicator is determined by the performance measurement
application 190 after extracting and relating the relevant
information from the CM system side and the plant floor side.
A lower level KPI may be pulled up into a higher level KPI,
for example, such that the higher level KPI may be used by an
executive at headquarters.
US 8,380,842 B2
9
10
As an option, the server platform 100 may include a soft-
the plant floor data sources 210 and the CM system 230 using
ware development kit (SDK) 195 which is an API program-
the stored mapped universal identifiers. The server platform
mingtoolkitthatallowsvendors toconununicatemessages to
100 may poll certain measurement points every so often and
call an appropriate method and direct the SDK 195 to perform
pull the data into the server platform via the drivers/adapters.
an appropriate mapping. Such an SDK 195 allows a vendor to
5 Also, there may be one or more dedicated real-time connec-
have more direct control over the mapping outcomes.
tions to the server platform 100 such that the server platform
FIG. 4 illustrates a flowchart of an embodiment of a method
100 is continuously pulling in real-time data. Furthermore, an
400 of integrating a plurality of diverse plant floor equipment
asset health vendor may use the SDK 195 to push messages
220 with at least one computerized management (CM) sys-
into the server platform 100 by writing code against the API
tem 230 using the server platform 100 of FIG. 1. In step 410,
io of the SDK.
establish first conununication links 215 between the server
One or more work flows may be triggered inresponse to the
platform 100 and a plurality of diverse plant floor data sources
brokered communication during run time of the system 200.
210 via a plurality of plant floor adapters 110 of the server
In general, a particular work flow is triggered when a certain
platform 100 to at least receive information from the plant
set of conditions occur. For example, the various kinds of
floor data sources 210. In step 420, establish a second com-
15 work flows that may be triggered include an audit work status
munication link 235 between the server platform 100 and at
work flow, an escalate priority work flow, a synchronize asset
least one computerized management (CM) system 230 via at
data work flow, a production asset capability forecast work
least one CM system adapter 120 of the serverplatform 100 to
flow, and a measure performance work flow (score carding).
at least receive information form the CM system 230. In step
A work flow is similar to a state machine operation and
430, discover defined device objects and types of the plurality
20 includes a set of steps that occur over time and often involve
of plant floor data sources 210 via the first communication
human interaction. At run time, a work flow routes messages
links 215 and import the discovered device objects and types
to the appropriate system end points.
into the server platform 100. In step 440, discover defined
For example, an alert or alarm may be detected for a piece
management objects and types of the at least one CM system
of equipment on the plant floor that has a problem and
230 via the second communication link 235 and import the
25 requires attention. hi response to the detected alert, a work
discovered management objects and types into the server
flow is triggered and a work order is generated, having a first
platform 100. In step 450, map the discovered objects and
priority, in the CM system to go and inspect that piece of
types to universal identifiers within the server platform 100,
equipment (i.e., that asset). If two weeks pass, and there is no
wherein the universal identifiers are defined in an open star-
record in the CM system that the inspection has occurred,
dard. In accordance with an embodiment of the present inven-
30 then the priority may be escalated by opening the work order
tion, the open standard is the MIMOSA open standard. The
and increasing the priority of the work order and triggering a
method 400 is accomplished during a set up time or a con-
work flow in the CM system which will flag the situation to
figuration time for the server platform 100.
the maintenance committee to make sure action is taken
The mapping of step 450 may include semantically con-
immediately. Similarly, if a more critical alert occurs, the
textualizing the device types and the management types to
35 priority of the work order may be escalated. However, to
pre -defined open standard universal type identifiers within
escalate priority, the system 200 must understand the seman-
the server platform 100. Also, the mapping of step 450 may
tic meaning within the CM system for the corresponding
include assigning the device objects and the management
priority code. The semantic mappings provide this meaning
objects to globally unique identifiers (universal object iden-
and allows rules for escalating priority and for checking work
tifiers) within the server platform 100. Furthermore, the map-
40 order status to be processed.
ping of step 450 may include semantically associating the
As another example of a work flow, with respect to syn -
management objects to universal type identifiers within the
chronization of data, a valve may be installed on the plant
server platform 100. The mapped universal identifiers are
floor and the valve is detected by one of the lower level plant
stored within the mapper database 132 of the server platform
device monitoring systems (i.e., a plant floor data source)
100.
45 such as a device manager. When the server platform 100
Again, the CM system 230 may include an enterprise asset
determines that the valve has been installed on the plant floor,
management (FAM) system, a computerized maintenance
the server platform 100 may check within the CM system to
management system (CMMS), or some other type of com-
determine if such a valve has already been defined. If not, the
puterized management system. The first communication
corresponding valve definition can be automatically gener-
links 215 are adapted to use at least one of open communica-
5o ated and mapped (semantically and/or non-senmantically),
tion protocols and proprietary commnunicationprotocols such
As a further example, an asset health system (a particular
as an open connectivity protocol, a modbus protocol, anXML
kind of plant floor data source) may detect a degradation in
web services protocol, or some particular proprietary proto-
the health of a certain piece of plant floor equipment. The
col, for example. The second conununication link 235 is
asset health system may push a message "create work order"
adapted to use a web services protocol such as, for example,
55 to the serverplatform 100. As a result, a work flow is triggered
the MIMOSA OSA-EAI Tech -XML -services web services
within the server platform 100 in response to the message.
protocol.
The server platform 100 checks if there is already a work
In accordance with an embodiment of the present inven-
order open and, if so, if the status of the work order is
tion, the device types may include at least one of alarm sever-
"opened" or "closed". If the status of the work order is
ity types, asset criticality types, health types, problem types,
60 "closed", another work order may be generated. If the status
failure types, and remedy types. Similarly, the management
of the work orderis "open", thepriority of the work ordermay
types may include at least one of asset types, work priority
be escalated.
types, asset criticality types, health types, problem types,
FIG. 5 illustrates a flowchart of a first embodiment of a
failure types, and remedy types.
method 500 of semantically contextualizing vendor types to
Once the server platform 100 is configured using the 65 universal type identifiers. In step 510, automatically sort the
method 400 of FIG. 4, the entire system 200 may be run such
device types and/or the management types, having a first
that the server platform 100 brokers communication between
ordinal scale, by ordinality. In step 520, automatically sortthe
US 8,380,842 B2
11
12
universal type identifiers, having a second ordinal scale, by
type F being mapped to MIMOSA universal type A (preven-
ordinality. In step 530, automatically assign the sorted device
tive-high). Therefore, four of the six work types on the CM
types and/or management types to the sorted universal type
side have been successfully mapped (in a semantically con -
identifiers by applying an inference algorithm.
textualized manner) to the four work types defined by the
FIG. 6 is an exemplary diagram 600 graphically illustrating
5 MIMOSA open standard. Two of the CM types C and E
the method 500 of FIG. 5. The diagram 600 illustrates how
apparently do not semantically fit into any of the four
CM types 610, being priority types and having an ordinal
MIMOSA universal types A to D and, therefore, have not
scale of I to 6, have been sorted by ordinal number from
been mapped. Such CM work types C and E may not be used
lowest priority 1 to highest priority 6. The CM types 610 may
by the server platform 100 in the system 200, or may be
correspond to the priority of a corrective maintenance work
10 handled in a separate manner by the server platform 100.
order, for example. The diagram 600 also illustrates how
Again, in accordance with an embodiment of the present
MIMOSA universal types 620, also being priority types and
having a different ordinal scale of 1 to 4 (low, medium, high,
invention, the sorting and mapping is performed by the
very high), have been sorted by ordinal number from lowest
semantic mapping application 150 of the server platform 100.
priority 1 to highest priority 4. An automated inference algo-
15 FIG. 9 is an exemplary diagram 900 graphically illustrating
rithm is used to perform the semantic contextualization map-
the process for setting up (i.e., configuring) the server plat -
ping from the CM types 610 to the MIMOSA universal types
form 100 of FIG.1 within the system 200 of FIG. 2. Discov-
620 as shown by the arrows.
ery 910 of objects and types is performed both on the CM side
In this example, the automated inference algorithnn applies
and the plant floor side. Assigning 920 of universal identifiers
a histogram technique that allows mapping from one ordinal
20 is performed, both on the CM side and the plant floor side, to
scale to another. The histogram technique results in CM types
objects and types. Non -semantic association 930 of CM
1 and 2 being mapped to MIMOSA universal type 1 (low
objects and device objects is perforied. Contextualized
priority), CM type 3 being mapped to MIMOSA universal
semantic type association 940 of CM types and device types
type 2 (medium priority), CM type 4 being mapped to
is performed, The semantic type associations may be per -
MIMOSA universal type 3 (high priority), and CM types 5
25 formed usingan ordinal type automated inference model 941,
and 6 being mapped to MIMOSA universal type 4 (very high
a nominal type automated inference model 942, or some other
priority). Therefore, the six priority types on the CM side have
interference model (not shown). Furthermore, contextualized
been successfully mapped (in a semantically contextualized
semantic type association 950 of objects and types is per -
manner) to the four priority types defined by the MIMOSA
formed.
open standard. In accordance with an embodiment of the
3o FIG. 10 is a diagram 1000 graphically illustrating the pro -
present invention, the sorting and mapping is performed by
cess for actively nursing the system 200 of FIG. 2 using the
the semantic mapping application 150 of the server platform
server platform 100 of FIG. 1. As data and information are
100.
received by the server platforn 100 from both the plant floor
FIG. 7 illustrates a flowchart of a second embodiment of a
side and the CM side, the server platform 100 performs uni-
mnethod 700 of semantically contextualizing vendor types to
35 versal identifier (UID) translations 1010 based on the map -
universal type identifiers. In step 710, automatically sort the
pings that were generated during set up and stored in the
device types and/or the management types, having a first
mapper database 132. Events are detected 1020 witlmin the
nominal scale, by frequency of occurrence. In step 720, auto-
server platform 100 in response to the translated data and
matically sort the universal type identifiers, having a second
information, andwork flows 1030 are triggered inresponse to
nominal scale, based on a pre -defined rate of occurrence. In
40 the detected events 1020. Also, the server platform 100 bro-
step 730, automatically assign the sorted device types and/or
kers commnunications 1040 betweenthe CMside andtheplant
management types to the sorted universal type identifiers by
floor side to accomplish work flows and to generate work
applying an inference algorithm.
orders.
FIG. 8isanexenmplary diagram 800graphically illustrating
In accordance with an embodiment of the present inven-
the method 700 of FIG. 7. The diagram 800 illustrates how
45 tion, the server platform 100 may extract information from
CM types 810, being work types and having a nominal scale
the CM system 230 and send the extracted information to the
of A to F, have been sorted by frequency of occurrence from
plant floor side to be rendered or displayed via a portal on the
highest (A) to lowest (F). The CM types 810 may correspond
plant floor side. For example, work history status or priority
to the different maintenance work types, for example. The
information may be extracted and rendered in this manner. In
diagram 800 also illustrates how MIMOSA universal types
5o general, the CM system 230 may transmit back events that
820, also being work types and having a different nominal
occur totheplant floor for non -control purposes. Suchevents
scale of A to D (preventive -high, corrective -medium, ewer-
include change events such as, for example, a change in a
gency-low, and safety), have been sorted based on a pre-
work status. For example, a planned overhaul message may
defined rate of occurrence. The pre -defined rate of occurrence
be sent from the CM system to an asset health system on the
may be determined from an actual work orderhistory that has
55 plant floor. As a result, the asset health system will know not
been accumulated and stored in the server platform 100 or in
to send out a plurality of predictive work orders, for example,
the CM system 230. An automated inference algorithm is
because the associated plant floor equipment will be getting
used to perform the semantic contextualization mapping from
shut down toperfommithe planned overhaul.
the CM types 810 to the MIMOSA universal types 820 as
In summary, a server platform and a method to integrate a
shown by the arrows.
60 plurality of diverse plant floor equipment with at least one
In this example, the automated inference algorithm applies
computerized management system in a manufacturing opera -
a heuristic probability technique that allows mapping from
tional or maintenance system are disclosed. The server plat -
one nominal scale to another. The heuristic probability tech-
form, using an open standard, enables a universal enterprise
nique results in CM type A being mapped to MIMOSA uni-
type taxonomy across the plant floor data sources and the at
versal type D (safety), CM type B beingmappedto MIMOSA
65 least one computerized management system, providing a
universal type C (emergency -low), CM type D being mapped
manufacturing intelligence solution that contextualizes the
to MIMOSA universal type B (corrective -medium), and CM
disparate data in a balanced manner.
US 8,380,842 B2
13
While the invention has been described with reference to
certain embodiments, it will be understood by those skilled in
the artthatvarious changes may bemade and equivalents may
be substituted without departing from the scope of the inven-
tion. In addition, many modifications may be made to adapt a s
particular situation or material to the teachings of the inven-
tion without departing fromits scope. Therefore, it is intended
that the invention not be limited to the particular embodiment
disclosed, but that the invention will include all embodiments
failing within the scope of the appended claims. to
What is claimed is:
1. A server platform for integrating a plurality of diverse
plant floor equipment with at least one computerized man-
agement (CM) system, said server platform comprising: 1
a processor;
a memory;
a plurality of plant floor drivers adapted to interface with a
plurality of diverse plant floor data sources to at least
receive first information from said plant floor data 2(
sources, at least one of the plurality of diverse plant floor
data sources providing a measurement associated with a
first plant equipment;
at least one CM system driver adaptedto interface with said
at least one CM system to at least receive second infor- 2`
mation from said at least one CM system;
a discovery application adapted to:
automatically discover and import defined device objects
and types from said plurality of diverse plant floor data
sources via said plant floor drivers, said defined device R
objects including a first device object representing said
first plant equipment and a second device object repre-
senting at least one of the plurality of diverse plant floor
data sources, and
automatically discover and import defined management 35
objects and types from said at least one CM system via
said CM system driver;
one or more mapping applications configured to map said
defined device objects and types and said defined man-
agement objects and types to universal identifiers to 40
generate mappings, the one or more mapping applica-
tions being configured to map said first device object,
said second device object and a first management object
of said defined management objects to a first universal
identifier, thereby relating the first plant equipment and 45
the at least one of the plurality of diverse plant floor data
sources to the first management object; and
a message translator adapted to, based on said mappings,
associate portions ofthe first information from saidplant
floor data sources with portions of the second informa- so
tion from said at least one CM system.
2. The server platform of claim 1 wherein said message
translator includes a semantic model forming an open object
metadata registry capable of enabling a universal enterprise
type taxonomy across said plant floor data sources and said at ss
least one CM system.
3. The server platform of claim 1 further comprising a
mapper database adapted to store semantic mappings and
non -semantic mappings behveen said plant floor data sources
and said CM system such that said message translator is 60
capable of accessing said mappings to facilitate said message
translator to associate said portions of first and second infor-
mation.
4. The server platform of claim 1 wherein said CM system
comprises one of a computerized maintenance managerrnent 65
system (CMMS) and an enterprise asset management (EAM)
system.
14
5. The server platform of claim 1 wherein said plant floor
data sources includes at least one of an asset health system,
condition monitoring sensors, and a plant historian system.
6. The server platform of claim 1 wherein said universal
identifiers are defined in an open standard and said open
standard comprises the MIMOSA open standard.
7. The server platform of claim 1 further comprising a
contextualizing application adapted to semantically map said
management types to pre -defined open standard universal
type identifiers and adapted to semantically map said device
types to said pre -defined open standard universal type iden-
tifiers.
8. The server platform of claim 1 further comprising an
assigning application adapted to assign first universal object
identifiers to said device objects and second universal object
identifiers to said management objects.
9. The server platform of claim 8 wherein a first mapping
application of the one or more mapping applications is
adapted to non -semantically map said first universal object
identifiers to said second universal object identifiers, thereby
relating said device objects to said management objects.
10. The server platform of claim 1 wherein said defined
objects comprise at least one of assets, segments, agents,
measurement points, enterprise, and site.
11. The server platform of claim 1 wherein said defined
types comprise at least one of asset types, worktypes, priority
types, asset priority types, alarm severity types, ordinal health
types, work priority types, and problem code types.
12. The server platform of claim 1 further comprising a
condition based maintenance application adapted to generate
maintenance work orders in response to said first information
collected from said plant floor data sources and said second
information collected from said at least one CM system.
13. The server platform of claim 1 further comprising a
performance measurement application adapted to track key
performance indicators in response to said first information
collected from said plant floor data sources and said second
information collected from said at least one CM system.
14. The serverplatform of claim 1 wherein communication
with said plurality of plant floor data sources is accomplished
via at least one of open communication protocols and propri-
etary communication protocols.
15. The server platform of claim 1 wherein communication
with said at least one CM system is accomplished via a web
services protocol,
16. A method of integrating a plurality of diverse plant floor
equipment with at least one computerized management (CM)
system, said method comprising:
establishing first communication links between a server
platform and a plurality of diverse plant floor data
sources via a plurality of plant floor adapters of said
server platform to at least receive first information from
said plant floor data sources, at least one of the plurality
of diverse plant floor data sources providing a measure-
ment associated with a first slant equipment;
establishing a second corium mication link between said
server platform and at least one computerized manage-
ment (CM) systemvia at least one CM system adapter of
said server platform to at least receive second inforna-
tion from said CM system;
discovering defined device objects and types of said plu-
rality of plant floor data sources via said first communi-
cation links and importing said defined device objects
and types into said server platform, said defined device
objects including a first device object representing said
US 8,380,842 B2
15
16
first plant equipment and a second device object repre-
32. The method of claim 30 further comprising automati-
senting said at least one of the plurality of diverse plant
cally triggering at least one work flow in response to said
floor data sources;
associated portions.
discovering defined management objects and types of said
33. The method of claim 32 wherein said work flow com-
at least one CM system via said second commiumication 5
prises at least one of an audit work status work flow, an
link and importing said defined management objects and
escalate priority work flow, a synchronize asset data work
types into said server platform; and
flow, a production asset capability forecast work flow, and a
mapping said defined device objects and types and said
measure performance work flow.
defined management objects and types to universal idea-
34. The method of claim 30 fiirther comprising automati-
tifiers to generate mappings within said server platform, n0
cally generating at least one work order in response to said
wherein said first device object, said second device
associated portions.
object and a first management object of said defined
35. The method of claim 34 wherein said work order com-
management objects are mappedto a firstuniversal iden-
prises an automated condition -based maintenance work
tifier, thereby relating the firstplant equipment and the at 15
order.
least one data source to the first management object.
36. The method of claim 35 wherein said automated con -
17. The method of claim 16 wherein said mapping includes
dition-based maintenance work order comprises at least one
semantically contextualizing said device types and said man-
of a predictive maintenance work order, a corrective mainte-
agement types to pre -defined open standard universal type
nance work order, a preventive maintenance work order, and
identifiers within said server platform. 20
an emergency maintenance work order.
18. The method of claim 16 wherein said mapping includes
37. The method of claim 30 further comprising automati-
assigning said device objects and said management objects to
cally tracking at least one key performance indicator in
globally unique identifiers within said server platform.
response to said associated portions.
19. The method of claim 16 wherein said mapping includes
38. The method of claim 17 wherein said semantic contex-
semantically associating said management objects to univer- 25
tializing includes:
sal type identifiers within said server platform.
automatically sorting said device types and/or said man -
20. The method of claim 16 wherein said CM system
agement types, having a firstordinal scale, by ordinality;
comprises one of a computerized maintenance management
automatically sorting said universal type identifiers, hav-
system (CMMS) and an enterprise asset management (EAM)
ung a second ordinal scale, by ordinality; and
system. 30
automatically assigning said sorted device types and/or
21. The method of claim 16 wherein said first conununi-
management types to said sorted universal type identi-
cation links are adapted to use at least one of open cornmu-
fiers by applying an inference algorithm,
nication protocols and proprietary communication protocols.
39. The method of claim 38 wherein said inference algo-
22. The method of claim 21 wherein saidprotocols include
rithm includes a histogram technique.
at least one of an open connectivity protocol, a modbus pro- 35
40. The method of claim 17 wherein said semantic contex-
tocol, an XML web services protocol, and a proprietary pro-
tializing includes:
tocol,
automatically sorting said device types and/or said man -
23. The method of claim 16 wherein said second comm u-
agement types, having a first nominal scale, by fre-
nication link is adapted to use a web services protocol.
quency of occurrence;
24. The method of claim 23 wherein said web services 40
automatically sorting said universal type identifiers, hav-
protocol includes a MTM:OSA OSA-EAI Tech -XML -ser-
hug a second nominal scale, based on a pre -defined rate
vices web services protocol,
of occurrence; and
25. The method of claim 16 wherein said defined objects
automatically assigning said sorted device types and/or
include at least one of assets, segments, agents, measurement
management types to said sorted universal type identi-
points, enterprise, site. 45
fiers by applying an inference algorithm.
26. The method of claim 16 wherein said defined types
41. The method of claim 40 wherein said inference algo-
include at least one of asset types, work types, priority types,
rithm includes a heuristic technique.
asset priority types, alarm severity types, ordinal health types,
42. The method of claim 40 wherein said frequency of
work priority types, and problem code types.
occurrence is determined from a work history stored within
27. The method of claim 16 wherein said device types 50
said server platform.
include at least one of alarm severity types, asset criticality
43. A system for maintenance and asset management, said
types, health types, problem types, failure types, and remedy
system comprising:
types.
a plurality of plant floor data sources adapted to collect first
28. The method of claim 16 wherein said management
data from a plurality of plant floor equipment, at least
types includes at least one of asset types, work priority types, 55
one of the plurality ofplant floor data sources providing
asset criticality types, health types, problem types, failure
a measurement associated with a first plant floor equip -
types, and remedy types.
ment;
29. The method of claim 16 fiirther comprising storing said
at least one computerized management (CM) system
mapped universal identifiers within said server platform.
adapted to provide second data; and
30. The method of claim 29 fiurther comprising associating 60
a serverplatform adapted to integrate said plurality ofplant
portions of the first information from said plant floor data
floor data sources with said at least one CM system
sources with portions of the second information from said at
based on a universal enterprise type taxonomy, said
least one CM system using said stored mapped universal
server platform comprising:
identifiers.
a processor;
31. The method of claim 16 wherein said universal identi- 65
a memory;
fiers are defined in an open standard and said open standard
a plurality ofplant floor drivers adapted to receive at least
comprises the MIMOSA open standard.
a portion of the first data,
US 8,380,842 B2
17
at least one CM system driver adapted to receive at least a
portion of the second data,
a discovery application adapted to:
automatically discover and import defined device objects
and types from said plant floor data sources via said plant
floor drivers, said defined device objects including a first
device object representing said first plant equipment and
a second device object representing said at least one of
the plurality of plant floor data sources, and
automatically discover and import defined management
objects and types from said at least one CM system via
said CM System driver; and
one or more mapping applications configured to map said
defined device objects and types and said defined man-
agement objects and types to universal identifiers of the
universal enterprise taxonomy to generate mappings, the
one or more mapping applications being configured to
map said first device object, said second device object
and a first management object of said defined manage-
ment objects to a first universal identifier, thereby relat-
ing the first plant equipment and the at least one data
source with the first management object.
44. The system of claim 43 wherein said universal enter-
prise type taxonomy is defined in ail open standard and the
open standard comprises the MIMOSA open standard.
45. The system of claim 43 wherein said computerized
management (CM) system comprises one of a computerized
maintenance management system (CMMS) and an enterprise
asset management (EAM) system.
46. The system of claim 43 wherein said server platform
further comprises:
a message translator adapted to, based on said mappings,
associate portions of the first data from said plant floor
data sources with portions of said second data from said
at least one CM system.
47. The system of claim 46 wherein said message translator
includes a semantic model forming an open object metadata
registry capable of enabling said universal enterprise type
taxonomy across saidplant floor data sources and said at least
one CM system.
48. The system of claire 43 further comprising a contextu-
alizing application residing in said server platform and
adapted to semantically map said management types to pre-
defined open standard universal type identifiers and adapted
18
to semantically map said device types to said pre -defined
open standard universal type identifiers.
49. The system of claim 43 further comprising an assigning
application residing in said server platform and adapted to
5 assign first universal object identifiers to said device objects
and second universal object identifiers to said management
objects.
50. The system of claim 49 wherein a first mapping appli-
cation of the one or more mapping applications is adapted to
10 non -semantically map said first universal object identifiers to
said second universal object identifiers, thereby relating said
device objects to said management objects.
51. The system of claim 43 wherein said defined objects
comprise at least one of assets, segments, agents, measure -
15 ment points, enterprise, and site.
52. The system of claim 43 wherein said defined types
include at least one of asset types, work types, priority types,
asset priority types, alarm severhy types, ordinal health types,
work priority types, and problem code types.
53. The system of claim 43 further comprising a condition
20 based maintenance application residing in said server plat-
form and adapted to generate maintenance work orders in
response to information collected from said plant floor data
sources and said at least one CM system.
25 54. The system of claim 43 further comprising a perfor-
mance measurement application residing in said server plat-
form and adapted to track key performance indicators in
response to information collected from said plant floor data
sources and said at least one CM system.
55. The system of claim 43 wherein conmmunication
so between said plurality of plant floor data sources and said
server platform is accomplished via at least one of open
communication protocols and proprietary communication
protocols.
56. The system of claim 43 wherein communication
35 between said at least one CM system and said server platform
is accomplished via a web services protocol.
57. The system of claim 43 further comprising a graphic
user interface operationally interfacing to said server plat-
form and adapted to allow a user to at least manage
ao MIMOSA -based mappings between defined device objects
and types imported from said plant floor data sources and said
defined management objects and types imported from said at
least one CM system.