Circuit Breaker Maintenance

Using Mobile Agent Software

Ashwin Gopinath
ETAHEEE019
 Things we’ll go through
• Introduction
• Need for remote maintenance
• Maintenance Tasks
• Mobile Agent Software (brief intro)
• Various Application Scenarios
• Conclusion(s)
 Introduction
• A crucial component of power system
operations
• Indispensable in switching for routine n/w
operation + protection of other devices
• Hence, their maintenance is critical (periodical
as well as preventive)
 Need for remote maintenance

• CB condition monitoring at each operation

• Switch from TIME directed to CONDITION directed
repair/maintenance
• Significant reduction in size and cost of
maintenance crew
• Higher efficiency of maintenance as paper logging
and referential system is done away with
 CB maintenance tasks
• It is imperative that a CB stay in tip-top condition
• The task is made trickier given that a CB usually
remains idle for long periods of time
• They include periodic inspection, test and
replacement of worn or defective components
• Maintenance intervals are usually experience
derived
 Contd..
The maintenance practices are divided into 3
1. Corrective
2. Preventive
3. Predictive
 Mobile Agent Software(MAS)
An Agent is an autonomous component which is capable of making
reasonable and judicious decisions on behalf of the USER

• uses high level flexible abstractions to

represent systems
• they communicate with other agents by
passing messages or by synchronisation
• 3 types viz.
– Personal
– Mobile
– Collaborative
 MAS contd..

Qualities of a good MAS

• Should be intelligent and autonomous

• Adaptive
• Compatible with other agents
• Portability
• Transparency
Application Scenarios
 Info storage & retrieval

• Info is stored on heterogeneous systems

• The MAS can easily access any info needed
• Centralization of data means all users can
constantly update data keeping everyone up
to date
 Creating Failure Reports

• A failure is usually succeeded by a long list of

checks to determine cause and severity
• Needless to say, quite a tedious ordeal
• The MASs determine the failure at the exact
time of occurrence
• They synchronise their collective data and a
report is prepared at the main server
• The report consists of only the requisite
details thereby optimising space
 CB Monitoring

• User can select event of interest to monitor

• Once logged on, the events will be registered with
the agent running on the corresponding
concentrator
• The concentrator communicates with individual
sensors getting real-time info and notifies the user
when necessary
 Security Considerations
2 problems maybe encountered
• Proper authentication and authorisation
• Ensuring integrity of data
Remedial Measures
• Every agent be authenticated via secure
username/password pairs
• Tier system of security clearance for authenticated
agents
• Permissions to assigned on priority basis
• Encryption of data + protection while travelling
 Logging & Experience Sharing

• Recorded experience saved in a case based

reasoning system for future retrieval
• Difficult to search for requisite solution to
problems
• Agents record all the maintenance reports
 Conclusion

• MAS is quite a suitable choice for CB

maintenance/repair due to its support for
heterogeneous systems, enhanced security,
distributed events, low bandwidth usage and so on
• Due to its flexibility, any development in mobile
technology(say, 3G) can be easily integrated into it
QUESTIONS ???
• As