Tobey Strauch
Navarro Systems
 Traditional software systems have
requirements definitions and planning with a
system life cycle implementation.
 So should industrial controls.
 6 stages
◦ Planning
◦ Analysis
◦ Design
◦ Construction
◦ Test
◦ Rollout
(Morris, 2013).
Resource: (Ponce, 2013)
 Due Diligence with Requirements
◦ System purpose
◦ System life cycle
◦ System fault criteria
◦ System interface criteria
◦ Hardware criteria
◦ Deliverables
◦ Time frame
◦ Training
 Everyone should learn from the chemical and
pharmaceutical industry
◦ Don’t accept equipment that does not meet
prescribed requirements
◦ Make sure your requirements are in place before
allowing design functions to start
◦ Decrease maintenance and poor start ups
◦ Make fault predictions early on
 Harikesh, Bahadur Yadav, (2014), “A Multistage Model for
Defect Prediction of Software Development Life Cycle
Using Fuzzy Logic.” Third International Conference on Soft
Computing for Problem Solving Advances in Intelligent
Systems and Computing, Volume 259, 2014, pp. 551-671.
Retrieved from
http://www.ijcaonline.org/volume11/number6/pxc38721
24.pdf
 Meadowcroft, Ben (2013), “Why Systems Fail”, retrieved
from
http://www.benmeadowcroft.com/reports/systemfailure/
 Morris, K, (2013), “Steps in the System Development Life
Cycle”, Houston Chronical, retrieved 4/29/2014 from
http://smallbusiness.chron.com/steps-system-
development-life-cycle-43241.html

Requirements and analysis needed in implementing control systems

  • 1.
  • 2.
     Traditional softwaresystems have requirements definitions and planning with a system life cycle implementation.  So should industrial controls.
  • 3.
     6 stages ◦Planning ◦ Analysis ◦ Design ◦ Construction ◦ Test ◦ Rollout (Morris, 2013).
  • 4.
  • 5.
     Due Diligencewith Requirements ◦ System purpose ◦ System life cycle ◦ System fault criteria ◦ System interface criteria ◦ Hardware criteria ◦ Deliverables ◦ Time frame ◦ Training
  • 6.
     Everyone shouldlearn from the chemical and pharmaceutical industry ◦ Don’t accept equipment that does not meet prescribed requirements ◦ Make sure your requirements are in place before allowing design functions to start ◦ Decrease maintenance and poor start ups ◦ Make fault predictions early on
  • 7.
     Harikesh, BahadurYadav, (2014), “A Multistage Model for Defect Prediction of Software Development Life Cycle Using Fuzzy Logic.” Third International Conference on Soft Computing for Problem Solving Advances in Intelligent Systems and Computing, Volume 259, 2014, pp. 551-671. Retrieved from http://www.ijcaonline.org/volume11/number6/pxc38721 24.pdf  Meadowcroft, Ben (2013), “Why Systems Fail”, retrieved from http://www.benmeadowcroft.com/reports/systemfailure/  Morris, K, (2013), “Steps in the System Development Life Cycle”, Houston Chronical, retrieved 4/29/2014 from http://smallbusiness.chron.com/steps-system- development-life-cycle-43241.html