Experimental Physics and Industrial Control System
|
Dear EPICS community,
I'm currently doing an evaluation of technologies to use (or customise) for our Fault Report System. The current astronomical observatories ATCA, Parkes and Mopra use an in-house developed Fault Report and Tracking System being maintained by only one person,
it is not easily extensible or flexible and has some issues around searching and reporting. Putting some effort on updating it is not cheap considering that they might be other alternatives available.
Our main requirements/use cases are:
- Easy creation of faults that affects observations by all kind of users, including observers (which do not have a CSIRO account). The users should not need to login, and an email should suffice or entering via a web page
- Fault tracking and customised workflows (assign tickets to individuals or groups)
- Ability to support multiple projects, telescopes, systems (hierarchical configuration)
- Email notifications, and possible updating the fault log via email
- Web client (and mobile clients would be a plus)
- Ability to do easy search for past faults, recurrent faults (link faults)
- Customised search and API for advanced data mining
We have experience with a project tracking tool call Redmine that we are using for the ASKAP project but I'm also interested in other popular software development tracking tool call JIRA that can be customised for this type of workflows. I'm going to trial
JIRA in the upcoming weeks.
I was wondering what is being used at other facilities as a Fault Report and Tracking System? Do you have a commercial generic workflow framework? Do you have a complete in-house product catered for your needs?
Any input/comments/thoughts are very welcome.
Kind regards,
JC.
Juan Carlos Guzman
ATNF Software and Computing Group Leader
Astronomy and Space Science
CSIRO
E [email protected] T +61
2 9372 4457 M +61 432 699 791
PO Box 76, Epping, NSW, 1710 | Vimiera & Pembroke Rd, Marsfield, NSW, 2122 Australia
www.csiro.au | www.csiro.au/CASS
PLEASE NOTE
The information contained in this email may be confidential or privileged. Any unauthorised use or disclosure is prohibited. If you have received this email in error, please delete it immediately and notify the sender by return email. Thank you. To the extent
permitted by law, CSIRO does not represent, warrant and/or guarantee that the integrity of this communication has been maintained or that the communication is free of errors, virus, interception or interference.
Please consider the environment before printing this email.
|
- Replies:
- Re: Fault Report and Tracking System enquiry? Benjamin Franksen
- Re: Fault Report and Tracking System enquiry? J. Lewis Muir
- Navigate by Date:
- Prev:
CSS/BOY rule question [SEC=UNOFFICIAL] LYNCH, Damien
- Next:
Re: Fault Report and Tracking System enquiry? Benjamin Franksen
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
CSS/BOY rule question [SEC=UNOFFICIAL] LYNCH, Damien
- Next:
Re: Fault Report and Tracking System enquiry? Benjamin Franksen
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|
ANJ, 20 Apr 2015 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|