...
- Deliverfully customized web-based client applications over http/https
- Provides XML configuration and analysis data to the web-based client
- Executes unlimited, configured "analysis models" according to set schedules e.g. daily, every 5 minutes or runs analysis on user request.
- The analysis engine:
- Reads data from other JDBC compliant databases using template SQL configured within the models.
- Reads data from files according to structures configured within the models
- Reads data from websites or web services over HTTP according to logic configured within the models.
- Transforms the data according to rules configured within the models e.g. merges data from different sources, enriches the data using "Excel-like" expressions, performs referential lookups, filters data, aggregates data etc.
- Creates alarms based on data specific rules
- Initiates workflows based on alarms / data specific rules
- Updates external databases using template SQL or "stored procedure" calls configured within the model
- Exports structured data files e.g. CSV or Excel documents according to structure definitions defined in the model.
- Invokes web services over HTTP based on model parameters
- Emails files and spreadsheets to users
- Creates graphical reports and automatically emails them to configured users according to defined schedules
- Archives data according to defined, data specific schedules
- Provides user group role based security and secure access to applications, data, charting and reports
- Maintains a full and detailed audit trail
- Maintains a full and detailed log trail of all analysis
...
The following server configuration should be considered a typical minimum environment for PhixFlow deployment. A server with this specification will enable PhixFlow to process typical analysis models for medium sized organisations. For organisations with large analysis requirements e.g. rerating 30+ million events in a single analysis step, then PhixFlow consultants should be engaged to carry out a detailed machine sizing exercise based on the complexity and number of the models that need to be configured and the volume of data that will be processed.
CPU | 2 x Quad-core 2.6 GHz |
Memory | 16 GB (Expandable to 64 GB) |
Disk | 8 x 146 GB in RAID5 configuration |
Operating System | 64 bit Red Hat Linux Enterprise Edition |
Network Connection | 1 Gbit Rj45 Ethernet |
Table 1 Minimum PhixFlow Server
A typical server with this sizing is the HP ProLiant DL380.
...
- Definition of control frameworks i.e. areas of system monitoring or task automation
- Prioritisation support for control design and deployment
- Creation of unlimited analysis models through the drag and drop design screens
- Creation of unlimited workflow models through the drag and drop design screens
- Chart and report definitionAlarm lists and alarm maintenance
- User task lists and task maintenance
- Drag and drop definition of user defined dashboards
- Guided drill down into analysis results to determine root cause analysis
- Evaluation of the effectiveness of the control framework
- User administration
- Scheduled task definition
- Log viewers and drill down for Active and Completed tasks
- Audit trail summaries and detailed drill down
- Archive log viewing and archive restore
- Model import and export via XML
- Base system configuration e.g. status codes, external queues
...