| Tue, 11 Mar 1997 21:51:12 -0000 |
| < rjb3@student.open.ac.uk (Bob Bryne)> |
Hi, First a quick intro; I work on an offshore gas platform looking after a Ferranti Argus computer system and all the Telecoms kit, (LOS radio, PABX, etc,). I was 12 years in the merchant Navy as a Radio Officer before moving into computers. The Ferranti in this gas field is the only real time system I've worked on, prior to this all my computer experience was with Banking systems and EPOS. I have always worked in a maintenance role. For the past few years I've been studying with the Open University, and am now in my final year of an honours degree for which I have to write a thesis. Now down to business; For my thesis I've chosen to investigate the changing out of our aging Ferranti system. I'm mainly concentrating on the hardware side of things. Obviously I need to do some kind of user requirements analysis, I have plenty of my own ideas, and I've already had the odd chat with one or two users. However, I really need to put together some kind of questionnaire to pass round all users and department heads, the trouble is I haven't got a clue what to put in it. Are there any experts out there willing to offer advice or point me in the right direction to some literature on the subject. Regards Bob Bryne
| Wed, 12 Mar 1997 11:13:59 +0000 |
| < "Nuno J. Nunes" dnnunes@dragoeiro.uma.pt> |
Hello I'm doing a similar process for my thesis, on the software side. The people on the company didn't cooperate very much with the process of requirement analysis so I very interested in that questionnaire, if you come up with it! Regards Nuno Ferranti Argus computer system
------------------------------------------------------------------- | Da Madeira em Directo... Live From Madeira... | ------------------------------------------------------------------- | Nuno Jardim Nunes - Computer Science Unit | | University of Madeira - Portugal | ------------------------------------------------------------------- | Address: Largo do Municipio, 9000 - Funchal - Portugal | | Contact: Voice:351-(0)91-222417 ext. 213, Fax:351-(0)91-225111 | | e-mail : dnnunes@dragoeiro.uma.pt | | URL : http://www.uma.pt/dnnunes/nuno.html | -------------------------------------------------------------------
| 12 Mar 97 17:25:11 EST |
| < Mike Jennings 100567.3703@CompuServe.COM> |
Bob I need to think about how best to help you. My colleagues and I have been associated with specifying and procuring new generation SCADA over the past few yeaars - some which have been Ferranti Argus based systems. What are your timescales? We have some generic specs that may help although most of my recent experience is in the electricity supply industry. Why only concentrate on the hardware, is the software functionality what is wanted. I suspect that pressures on the offshore business have changed in the ten years or so the system has been in and that there is some justification in looking at wider applications than just a like for like replacement. What is the justification/business case for replacing the system? I have a theory that I've been banging on about that SCADA is a back office application responsible for controlling and monitoring equipment for presentation to a user along with information from a suite of systems tackling different problems - modelling, knowledged based fault diagnosis, event filtering, plant condition monitoring, fire detection, process control, other SCADA - the list can go on and on. Is there a need to share data between systems? I guess these are all questions you can ask users and their management. Hope this hasn't confused you too much.
Mike Jennings 100567.3703@compuserve.com
| Thu, 13 Mar 1997 08:16:49 -0000 |
| < rjb3@student.open.ac.uk (Bob Bryne)> |
In end user, as you say, the software functionality. The justification for replacement is based on the current reliability of the Ferranti kit, the cost of maintaining it, cost of module repairs, and the fact our module repairer can no longer provide replacement parts and only guarantee to carry on repairing the modules for a limited period. Many thanks for your help. Regards Bob Bryne rjb3@student.open.ac.uk
| Thu, 13 Mar 1997 11:43:00 +1000 |
| < Ian Anderson IAnderson@skm.com.au> |
Bob, As Australia's largest SCADA/Telemetry/Automation consultant, we have a number of standard questionnaires covering all facets of SCADA/DMS/EMS and Industrial Automation, and are able to help with custom questionnaires. In addition we have standard "Boilerplate" specifications, should your thesis follow on to a change-out project. We also have staff who have worked with a Ferranti Argus system previously. Please contact me directly if you want some help.
------------------------------------------------------- | Ian Anderson _--_|\ | | / \ | | Sinclair Knight Merz ---- \*_.-._/ | | 7th Floor Durack Centre v | | 263 Adelaide Tce Phone: +61 9 268 4577 | | PO Box H615 Perth Fax : +61 9 268 4444 | | Western Australia 6001 EMail: ianderson@skm.com.au | -------------------------------------------------------
| 13 Mar 97 07:30:05 EST |
| < Mike Jennings 100567.3703@CompuServe.COM> |
Bob Given that you are concentrating on the user requirements I suggest you not be too concerned with any hardware or software solution yet. this should come out of responses to any Invitiation you attach to a Specification. To define the requirements I recommend that, rather than send out questionnaires, you run a number of half day workshops - three is a good number; for users, system maintainers and managers, plan to have six or seven attendees covering different aspects of their job. All three groups influence the buying decision and need to have their needs reflected in the specification. The workshops should be structured and not a general discussion; i.e. lead the workshop through a number of topics - what the current system can't do, what more is needed (not wanted), size of system, acceptable performance, timescales, constraints, future requirements, business case or benefits - appropriate to the attendees. For the structure and contents of the specification itself we have used the STARTS Purchasers' Handbook (available from NCC) as a sound guide, their Level 1 Requirements Specification contains sufficient detail to accompany an Invitation to Tender. Other sections in the handbook provide guidelines on a procurement process as well. Have fun
Mike Jennings 100567.3703@compuserve.com
| Mon, 17 Mar 1997 14:49:50 +0200 |
| < Johan du Raan johandr@africon.co.za> |
I am looking for info on SCADA hardware and software. I need to compile a specification indicating the minimum standards these systems must adhere to. The systems will typically be used in water distribution systems. Can somebody put me on the right track to find these information. Thanks Johan.
| Mon, 17 Mar 1997 09:36:58 -0500 |
| < Andrew Armstrong aarmstro@intranet.ca> |
Johan, My name is Andrew Armstrong and I work with a company called Control Microsystems. We are a leading North American Manufacturer of RTUs and PLCs created specifically for the SCADA market in water/wastewater. We have a wide range of products that could suit your needs and an excellent team of technical specialists to help you determine the rights specifications for the job. If you would like to learn more about our products, please e-mail me directly and I will put you in touch with our Sales Manager for your region. (Please advise as to where you are located)
| Tue, 18 Mar 97 09:57:56 PST |
| < Tim.Kannegieter@reedbusiness.com.au> |
Johan, Re SCADA specifications. My magazine (Process and Control Engineering) published a survey of SCADA systems available in Australia (over 20). I designed 36 questions which just about covers the main range of specifications. I also published an article discussing what to watch out for in each of the categories. I can send this to you but unfortunately you have to subscribe to the magazine (A$96/a or US$159 outside Australia). Email me direct on tim.kannegieter@reedbusiness.com.au if you are interested in this. Tim Kannegieter Editor, PACE
| Tue, 18 Mar 1997 11:30:20 +0800 |
| < John Bailey jbailey@cygnus.uwa.edu.au> |
Johan du Raan wrote: You might find IEEE standard C37.1-1994, "IEEE Standard Definition, Specification, and Analysis of Systems Used for Supervisory Control, Data Acquisition, and Automatic Control", useful. It was developed for the electricity industry, but is a good starting point.
John Bailey Supervising Engineer SCADA Water Corporation Western Australia
| Mon, 17 Mar 1997 17:26:37 -0000 |
| < Trond Thorman trond@radius.co.uk> |
Dear Johan, We are not manufacturer of SCADA system, neither outstations (RTU's) for the water industry. However as radio telemetry supplier we have excellent corporation with Alfa-Laval Automation (former Sattcontrol) which operate as a hardware software supplier for the water utility segment. We have completed several successful joint water projects with them and are pleased so far. I can only recommend them for your further research. Re their RTU's and SCADA system please contact: Mr Keith Davies at Alfa-Laval Automation in the UK for further information. Tel: +44 1606 49935 Fax: +44 1606 49939 I haven't got their parent company address in Sweden handy, so please use this as a starter.
Regards Trond Thorman, Radius UK VHF/UHF Radio Telemetry Systems Manufacturer
| Wed, 19 Mar 1997 01:42:42 -0200 (GMT) |
| < hhwill hhwill@lin01.global.co.za> |
Hi end SCADA) or Mike Whitwam of Wise Technologies (home page on the web) for Intouch info. Or myself for background on all SCADA types, I/O systems, telemetry, etc. The specification would have to be driven by your application requirements.
Hansell Williams Automation Consultant Information Engineering Services JHB 011-882-2083 083-274-3527