Richard Farnsworth –Controls and IT Manager Australian synchrotron OUTSOURCING, INSOURCING, AND INTEGRATION OF CONTROL SYSTEMS IN THE AUSTRALIAN SYNCHROTRON.

Slides:



Advertisements
Similar presentations
Control and IT Systems status and strategy ALBA, Piotr Goryl on behalf of Michał Ostoja-Gajewski, Krzysztof Wawrzyniak, Łukasz Żytniak, Tadeusz.
Advertisements

Australian Synchrotron Richard Farnsworth With Steven Banks and Mark Clift.
System Integration Verification and Validation
F. Fernandez 28/10/ Ferran Fernandez WAO2014 Operators training experience at the ALBA synchrotron light source.
CSCU 411 Software Engineering Chapter 2 Introduction to Software Engineering Management.
Wayne Lewis Australian Synchrotron Beamline Controls Design and Implementation.
W5HH Principle As applied to Software Projects
A framework for describing IT Project Management Processes and Tool Set Features Enterprise Project Management Framework.
SYSTEMS DEVELOPMENT Phases, Tools, and Techniques
Elder Matias CLS Control System Recent Upgrades. Major Changes Synchrotron Upgrade New Isotope Production Linac EPICS Software –Python EDM –Aquaman –ScienceStudio.
Introduction to Software Testing
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
EPICS Qt Update Paul Martin 1. Australian Synchrotron 3GeV, 216m circumference synchrotron 8 Beamlines 12 Software Engineers IMBL – Worlds Widest Beam.
Effective Methods for Software and Systems Integration
1 The SpaceWire Internet Tunnel and the Advantages It Provides For Spacecraft Integration Stuart Mills, Steve Parkes Space Technology Centre University.
Elder Matias Canadian Light Source University of Saskatchewan CLS – Control System Overview.
S/W Project Management
System Implementation. System Implementation and Seven major activities Coding Testing Installation Documentation Training Support Purpose To convert.
Global Design Effort 1 Conventional Facilities and Siting Overview A. Enomoto, J-L. Baldy, V. Kuchler GDE.
SYSTEMS DEVELOPMENT Phases, Tools, and Techniques
Project Management Development & developers
The Rational Unified Process
EPICS Developments at the Australian Synchrotron Contributors: Richard Farnsworth, Andrew C Starritt (Controls Team) Chris Myers & Mike DeSilva (Versi)
WAO, Trieste, 24th - 28th September 2007 An Overview of the Reliability and the Fault Trends of the SRS Cheryl Hodgkinson Daresbury Laboratory Synchrotron.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
From Research Prototype to Production
Testing Challenges in an Agile Environment Biraj Nakarja Sogeti UK 28 th October 2009.
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Quality Control Project Management Unit Credit Value : 4 Essential
SENG521 (Fall SENG 521 Software Reliability & Testing Software Product & process Improvement using ISO (Part 3d) Department.
ETICS2 All Hands Meeting VEGA GmbH INFSOM-RI Uwe Mueller-Wilm Palermo, Oct ETICS Service Management Framework Business Objectives and “Best.
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem Darwish.
E.Matias Canadian Light Source. Where is Saskatoon?
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
1 Kenneth Osborne, 9/14/07 Inter Group communications at the Advanced Light Source. Overview of the different methods of communication between different.
CLS Control System Progress Report Elder Matias Canadian Light Source University of Saskatchewan Saskatoon Saskatchewan.
Dr. Jana Jagodick Polytechnic of Namibia, 2012 Project Management Chapter 2 Project Management Cycle.
Operations, Test facilities, CF&S Tom Himel SLAC.
Service Level Agreements Service Level Statements NO YES The process of negotiating and defining the levels of user service (service levels) required.
ANKITHA CHOWDARY GARAPATI
Software Development A Proposed Process and Methodology.
MIS 7003 MBA Core Course in MIS Professor Akhilesh Bajaj The University of Tulsa Introduction to S/W Engineering © All slides in this presentation Akhilesh.
Oktalia Juwita, S.Kom., M.MT. SYSTEMS DEVELOPMENT Dasar-dasar Sistem Informasi – IKU1102.
Managed by UT-Battelle for the Department of Energy SCL Vacuum Control System Upgrade Derrick Williams
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
Neutron Chopper Technologies Work Package
An Overview of Support of Small Embedded Systems with Some Recommendations Controls Working Group April 14, 2004 T. Meyer, D. Peterson.
Chapter 6 SYSTEMS DEVELOPMENT Phases, Tools, and Techniques.
From the customer’s perspective the SRS is: How smart people are going to solve the problem that was stated in the System Spec. A “contract”, more or less.
SOFTWARE PROJECT MANAGEMENT
Electrical Engineering for NSS - Status and Planning- Thomas Gahl Electrical Engineering Group Leader February 26, 2014.
Conventional Facilities integration: Approach and Issues Daniel Piso Fernández WP Leader (WP13 Conventional Facilities Integration Support) November 5,
What is a WBS? A Work Breakdown Structure is not a list of tasks, a schedule or an organization chart. Rather it provides the basis on which a task.
Prof. Shrikant M. Harle.  The Project Life Cycle refers to a logical sequence of activities to accomplish the project’s goals or objectives.  Regardless.
Breakdown Work Structure Applying Management Tools to a Project.
Montse Pont ARW 2013 Operation and Reliability at ALBA Montse Pont.
Report Technical Director Storage-Ring-Installation Completed
Operations Machine Simulator.
Lecture 3 Prescriptive Process Models
PLC-based control systems at SOLEIL - ICALEPCS 2017
Accelerator Reliability and Software
DLS Standard PLC System
The Systems Engineering Context
BE/RF-IS Contribution to LIU C. Rossi and M. Paoluzzi
IEEE Std 1074: Standard for Software Lifecycle
What Do I Want from an RDB?
EPICS: Experimental Physics and Industrial Control System
Managing Project Risks and Opportunities
System Analysis and Design:
Update on the JLEIC pCDR
Presentation transcript:

Richard Farnsworth –Controls and IT Manager Australian synchrotron OUTSOURCING, INSOURCING, AND INTEGRATION OF CONTROL SYSTEMS IN THE AUSTRALIAN SYNCHROTRON Richard Farnsworth Bryce Karnaghan, Wayne Lewis, Andrew Starritt and Mark Clift

The Australian Synchrotron was built in less than four years and under budget with many subsystems outsourced. The reasons for outsourcing The approach taken Technical issues involved The importance of a solid engineering approach, systems design and in-house Some suggestions for future projects

MANAGEMENT APPROACH – STRUCTURE AND TEAMMinimise staff;Maximise contracting and outsourcing;Meet tight deadlines;Defined acceptance criteria;Form small “Project/product teams; andMinimise and outsource risks. We gotA total team of less than 50;The major subsystems outsourced;A lot of contractual support work;A need to integrate separate subsystemsLow risk solutions – leading edge, not bleeding edgeDefined but not prescriptive standards

Outsourcing mechanical works building the injection systems, Linac, Booster and RF systems were outsourced as “turn-key contracts”. controls were included in the scope of supply. risk for ensuring that it is actually fit for purpose

Work and system breakdown structures Work breakdown structure was derived for all major subsystems. For the accelerator, this included storage ring RF, DC magnets, diagnostics, power supplies, vacuum equipment, and injection kickers. controls work breakdown was then aligned with these systems system breakdown structure was derived. Controls Focus Controls was recognized in having a special focus on integration. Controls team for a while was the largest team on the project reaching eleven members !

Instant Friends EPICS was chosen for the control system, collaborative nature, entrance to the existing community provided instant friends! The Australian Synchrotron is the major EPICS user in the country, although we did discover two other smaller users Sharing training with the turnkey contractors. Picking your contractors wisely

GUIs The visible part of the control system. Standard tools were spec’d for the contractors We are slowly replacing them. Using a commercial MS Windows based integrated development environment (IDE) Runs in a Linux environment using WINE. This works well response is fast, Functionality identical across the MS Windows and Linux. Gratuitous screen shots follow

Hardware selections EPICS for Linux was A proper port of EPICS to a commercial real time Linux Modbus EPICS driver for equipment and safety PLCs PCI to VME bridge technologies PC104 + solid state disks

Operating system selection The use of specialist real-time operating systems can be important; The real time work was provided by “Redhawk” propriety real time system Later non realtime IOC’s on PC104 hardware and standard PC hardware was used. Australian Synchrotron uses Linux operating systems for all critical data collection purposes and all user machines. Could have avoided real time operating systems entirely.

Timing systems commercial off the shelf timing systems have become available. The master oscillator & RF distribution amplifiers. Conventional Facilities Building controls, compressed air, HVAC systems, cooling water effort required to pass data to the EPICS accelerator systems has been substantial. External Peer Reviews There were several external peer reviews assure management that the controls successful. provide minor corrections and good direction,

Engineering Approach A standard systems engineering approach, identifying the functional requirements, sorting our the interfaces, producing design documents, creating the code sourcing the hardware, testing against the requirements An incremental delivery approach block interface diagrams, sequence diagrams, collaboration diagrams, use cases and flow charts.

Formal internal peer reviews formal peer reviews for the design of each system. “Pack” of information distributed amongst reviewers The build system and source control “Build” for the accelerator. control very tightly exactly what software is deployed. all EPICS code base, but also extends to PLC code. useful when delivering incrementally, deployed over 125 builds to the accelerator

LONG TERM OPERATIONS operation for over twelve months beamlines for over six months. machine has achieved over 95% uptime over the last six months. Insourcing e importance of having all source code in our configuration repositories Bringing the various outsourced systems into a common environment common components will decrease the spares count increase the ability of staff Source and configuration controls Perforce a commercial but free for Open source developers Bugzilla as the source control and bug/enhancement tracking tools respectively.

SUGGESTIONS FOR FUTURE PROJECTS The following suggestions are made for future projects Get controls in early as you can, Get conventional facilities as part of the systems Standardise before any contracts Copy instead of reinventing where possible Don’t take too many risks, and manage those you do. Set realistic, milestones and goals See what works elsewhere Get good people and let them free..

Farnsworth Law of control systems Finally, a statement of some experience on the way: “Controls gets squeezed most as time runs out.”

Australian Synchrotron site from the air, June 2006 Building

From a tiger moth

Storage ring circumference: 216m Electron energy: 3 GeV Commencing operation: 2007 Initial suite of 9 beamlines Capacity for at least 30 beamlines in the long term Aerial view of the Australian Synchrotron with Melbourne CBD skyline

Community Open Day 20 March 2005 and again in August 2006