CENTRIX Condition Monitoring

Transcription

1 k Product Information Standard (Off-the-shelf) Software without customisation hat are the standard features of the software? Analogue Data Replay (e.g. Points and Track Circuits) Alerts Logger Status & Configuration Interlocking & Level Crossing Graphical Replay Bookmarks Reporting & Data Export Triggered Capture Replay Central storage of capture traces sent from data loggers (MIMOSA XML) Graphical replay of traces, organised by asset Overlay of multiple traces for manual inspection and comparison Tagging of traces (normal, anomaly, baseline, fault) User commenting of traces Filtering of traces by direction and tag See appendix 1 Logger Status & Configuration Live status of all configured loggers Live log of messages received from loggers Mapping of logger inputs to channels within the system Analogue Channel (e.g. Track Circuit) Replay Graphical replay of analogue data Overlay multiple inputs on a graph to inspect correlations Save graph configurations for repeat use See appendix 2 Alerts Create alerts based on a given condition template Suppression period configuration to reduce repeat alert notifications Alert on capture trace values (area under curve, average current, peak current, trace time) Alert on analogue level thresholds Alert on interlocking/track-side digital events o Train travelling over speed o Signal passed at danger (SPAD) o Relay state change o Track flick o Points loss of detection during passage of train o Signal reversion Live status of all configured alerts, organised by location Audit/replay of triggered alert notifications (including suppressed) Disable notifications during known maintenance periods Interlocking & Level Crossing Replay User-editable, drag and drop track map designer Playback of event data represented as graphical track map Concise listing of all monitored relay events Logic analyser to confirm sequencing and timing of events Create bookmarks to quickly navigate back to an incident/fault See appendix 3 and 4 Bookmarks Create bookmarks of incidents to share with other users or to re-visit Add additional user comments / references to bookmarks Immediately navigate to the playback screen for the time of the incident

2 k here is Centrix currently used? Points Monitoring Centrix is being used by a Class I railroad in the United States. The customer is presently evaluating the benefits of Point Condition Monitoring at 12 sites, prior to a major roll-out. Centrix can interface with the customers EMC Smarts system using SNMP traps. During the trial phase, no maintainer intervention has been conducted on the monitored point ends. This has enabled MPEC to gather quality data from the point machines, and from the maintainer about point failures. Track Circuit Monitoring MPEC have strong working relations with Bombardier Transportation. Centrix has been used to monitor digital EbiTrack 200, 300 and 400 series receivers and transmitters for a number of years. This includes monitoring of EbiTrack 200 track circuits in Mackay, Queensland for three years. Centrix was used in the UK as a vital tool to aid with the network acceptance of the EbiTrack 400 system. Centrix has been used to perform verification and validation of EbiTrack operation at a number of diverse sites across the UK. Interlocking/LX Replay Centrix is used extensively in the UK for graphical replay of interlocking and level crossing data Free-wired and geographical relay interlocking s Panel Multiplexer Systems Solid State Interlocking s All varieties of Level Crossings hat tools are used to develop the software? Application development, build and debugging using IntelliJ IDEA 12/13 Build and dependency management provided by Apache Maven Continuous integration of development using Atlassian Bamboo Agile feature/bug backlog management, planning, work-in-progress and reporting using Atlassian JIRA hat is the underlying database? Percona Server (MySQL replacement) is used for the core database. Percona is an open-source MySQL alternative that provides the enterprisegrade stability and scalability of MySQL, with the additional performance tuning from Percona Hazelcast is used as an in-memory data store for caching objects and efficient processing of alert conditions How often is the software upgraded/new releases available? Development is carried out in 2-week iterations at which point a releasable product is available Production releases are usually deployed once a month, however may be as often as 2-weeks hat is the recommended hardware requirements to support the software? Client 512MB RAM (1GB Recommended) 128MB Graphics Memory Adobe Flash Player Mozilla Firefox 3+ (or) Microsoft Internet Explorer 8+ (or) Google Chrome Server Fully hosted option available and recommended, however installation on client infrastructure is possible. 8GB ECC RAM (16GB Recommended) Dual-Core server-grade CPU (Intel Xeon 2.4Ghz+ recommended) Enterprise-grade HDD array (RAID 10 recommended) 120GB HDD array storage Ubuntu Linux Server (x64) Supports hardware virtualisation (VMware ESXi tested) hat Hardware is Centrix compatible with? Full compatibility with any NRII (MIMOSA) compliant data loggers Compatibility with MPEC SA380 interlocking and LX data loggers (via dial-up) Compatibility with MPEC TDM/SSI data loggers (via closed API)

3 k Support hat post installation support services are available to your clients? Online user guide available 24/7 support for initial incident report Telephone and remote support available on incident follow-up All tickets logged and tracked internally using Atlassian JIRA hat training options are available? Online user guide available 24/7 for selftraining On-site or remote training of software available on request hat are the support hours? Current Standard support hours Mon-Fri 09:00-17:00 GMT/BST excl. UK Public Holidays Current Emergency support hours Mon-Sun 07:00-22:00 GMT/BST hat are the standard levels of support (SLA)? MPEC Hosting: 99% Availability of the Centrix System. 1.0% license rebate for each 0.5% reduction in availability. Support: 4hr response (during support hours) 24hr resolution on support queries How are software bugs dealt with? Uncaught system errors can be reported directly from the system with a supplementary user comment (full trace sent to development team) User detected bugs should be reported via support Bugs are logged in the product backlog in Atlassian JIRA Bugs are prioritised and assigned to the next development iteration where appropriate Critical bugs are dealt with immediately and may result in a patch-release of the software

4 T k Appendix 1. Points trace replay 2. Analogue channel replay (with digital event data & logic analyser)

5 T k 3. Interlocking replay 4. Level-crossing replay

6 k 5. System architecture diagram eb Browser Adobe Flash Player Centrix Client Application (Apache Flex SF) Data Loggers AMF/HTTPS HTTPS SOAP/HTTP Ubuntu Linux Server UF Firewall Remote Services Controllers Local Services Scheduled Tasks Repositories (DAO) Centrix eb Application (Spring Managed) Apache Tomcat (Java Application Server) Percona (MySQL) Database Hazelcast In-Memory Data Grid