M & D Platform-Conceptual Architecture: GE Internal
M & D Platform-Conceptual Architecture: GE Internal
1. Data Infrastructure Layer:This is the database layer which contains Historian Database, Rule Engine Manager, Summary Engine, Data Warehouse, Proficy Alarm & Event Database, and OSM Fleet. Historian database is the main database for GE which stores all the data/ information related to Turbines. Rule Engine Manager is just like calc engine which has various set of rules viz. Matlab, CCAP etc. to implement on the raw data in order to process it & convert it into readable, understandable form. It has got some input & output ports. 2. Data Access Layer:The Data Access Layer is used to access/consume the data present in the database so as to get the functionality done in different applications as per requirement given by the client/customer. It consists of Proficy SOA workflow which runs timely & RMD Data Layer. Proficy SOA has SOA DB which is nothing but Service Oriented Architecture Database. 3. Data Presentation Layer:Data Presentation Layer is like UI (User Interface). In this, many applications are running such as M & D Health Portal, Tibco Spotfire & RMD Portal. RMD stand for Remote Monitoring & Diagnostics. It also contains SME Analysis tools, internal web server & Info content server. M & D Health Portal basically monitors & diagnoses the
GE Internal
health (functionality/Quality of working) for: -> Database servers (Oracle, SQL, and Historian); GE Internal
GE Internal
->Applications such as Tibco Spotfire, RMD Portal, OSM (OnSite Monitoring) Fleet, Missed Alarms module; -> Calc Engine Rules Health; -> Turbines Health By checking tags. Each & Every Turbine is connected or linked to an OSM. OSM takes the raw data from one or multiple turbines & stores it into Historian database in the form of tags. It has got some temporary data storage capability.
GE Internal