Keyword: factory
Paper Title Other Keywords Page
MOPPC039 Hardware Interface Independent Serial Communication (IISC) interface, software, hardware, controls 169
 
  • P. Kankiya, L.T. Hoff, J.P. Jamilkowski
    BNL, Upton, Long Island, New York, USA
 
  Funding: Work supported by Brookhaven Science Associates, LLC under Contract No. DE-AC02-98CH10886 with the U.S. Department of Energy.
The communication framework for the in-house controls system in the Collider-Accelerator Department at BNL depends on a variety of hardware interfaces and protocols including RS232, GPIB, USB and Ethernet to name a few. IISC is a client software library, which can be used to initiate, communicate and terminate data exchange sessions with devices over the network. It acts as a layer of abstraction allowing developers to establish communication with these devices without having to be concerned about the particulars of the interfaces and protocols involved. Details of implementation and a performance analysis will be presented.
 
poster icon Poster MOPPC039 [1.247 MB]  
 
MOPPC040 A Hazard Driven Approach to Accelerator Safety System Design - How CLS Successfully Applied ALARP in the Design of Safety Systems controls, PLC, operation, radiation 172
 
  • E. D. Matias, M. Benmerrouche, G. Cubbon, A. Hodges, H. Zhang
    CLS, Saskatoon, Saskatchewan, Canada
 
  All large scale particle accelerator facilities end up utilising computerised safety systems for the accelerator access control and interlock system including search lockup sequences and other safety functions. Increasingly there has been a strong move toward IEC 61508 based standards in the design of these systems. CLS designed and deployed its first IEC 61508 based system nearly 10 years ago. The challenge has increasingly been to manage the complexity of requirements and ensure that features being added into such systems were truly requirements to achieve safety. Over the past few years CLS has moved to a more structured Hazard Analysis technique that is tightly coupled and traceable through the design and verification of its engineered safety systems. This paper presents the CLS approach and lessons learned.  
 
TUPPC101 Scaling of EPICS edm Display Pages at ISAC ISAC, controls, EPICS, TRIUMF 816
 
  • R. Keitel
    TRIUMF, Canada's National Laboratory for Particle and Nuclear Physics, Vancouver, Canada
 
  The EPICS-based control system of the ISAC facility at TRIUMF uses the edm display editor / display manager to create and render the Operator interface displays. edm displays are expressed in pixel coordinates and edm does not scale the display page when a window is re-sized. A simple scheme was implemented to allow operators to switch page magnifications using a set of pre-selected scaling factors. Possible extensions of the scheme and its limitations will be discussed.  
poster icon Poster TUPPC101 [1.067 MB]  
 
TUPPC117 Unifying Data Diversity and Conversion to Common Engineering Analysis Tools software, superconducting-magnet, status, data-analysis 852
 
  • H. Reymond, O.O. Andreassen, C. Charrondière, M.F. Gomez De La Cruz, A. Rijllart
    CERN, Geneva, Switzerland
 
  The large variety of systems for the measurements of insulation, conductivity, RRR, quench performance, etc. installed at CERN’s superconducting magnet test facility generates a diversity of data formats. This mixture causes problems when the measurements need to be correlated. Each measurement application has a dedicated data analysis tool used to validate its results, but there are no generic bridge between the applications that facilitates cross analysis of mixed data and data types. Since the LHC start-up, the superconducting magnet test facility hosts new R&D measurements on a multitude of superconducting components. These results are analysed by international collaborators, which triggered a greater need to access the raw data from many typical engineering and analysis tools, such as MATLAB®, Mathcad®, DIAdem™, Excel™… This paper describes the technical solutions developed for the data formats unification and reviews the present status.  
poster icon Poster TUPPC117 [11.140 MB]  
 
THCOAAB06 Achieving a Successful Alarm Management Deployment – The CLS Experience controls, operation, software, monitoring 1062
 
  • E. D. Matias, L. Baribeau, T. Batten, J.W. Li, W.A. Wurtz
    CLS, Saskatoon, Saskatchewan, Canada
 
  Alarm management systems promise to improve situational awareness, aid operational staff in correcting responding to accelerator problems and reduce downtime. Many facilities, including the Canadian Light Source (CLS), have been challenged in achieving this goal. At CLS past attempts focusing on software features and capabilities. Our third attempt switched gears and instead focused on human factors engineering techniques and the associated response processes to the alarm. Aspects of ISA 18,2, EEMUA 191 and NREG-700 standards were used. CLS adopted the CSS BEAST alarm handler software. Work was also undertaken to identify bad actors and analyzing alarm system performance and to avoid alarm flooding. The BEAST deployment was augmented with a locally developed voice annunciation system for a small number of critical high impact alarms and auto diallers for shutdown periods when the control room is not staffed. This paper summaries our approach and lessons learned.  
slides icon Slides THCOAAB06 [0.397 MB]  
 
THPPC080 Testing and Verification of PLC Code for Process Control PLC, controls, framework, software 1258
 
  • E.B. Blanco Vinuela, B. Fernández Adiego, A. Merezhin
    CERN, Geneva, Switzerland
 
  Functional testing of PLC programs has been historically a challenging task for control systems engineers. This paper presents the analysis of different mechanisms for testing PLCs programs developed within the UNICOS (Unified Industrial COntrol System) framework. The framework holds a library of objects, which are represented as Function Blocks in the PLC application. When a new object is added to the library or a correction of an existing one is needed, exhaustive validation of the PLC code is needed. Testing and formal verification are two distinct approaches selected for eliminating failures of UNICOS objects. Testing is usually done manually or automatically by developing scripts at the supervision layer using the real control infrastructure. Formal verification proofs the correctness of the system by checking weather a formal model of the system satisfies some properties or requirements. The NuSMV model checker has been chosen to perform this task. The advantages and limitations of both approaches are presented and illustrated with a case study, validating a specific UNICOS object.  
poster icon Poster THPPC080 [3.659 MB]