» Dan Sacchitella – ChE, Project manager » Amanda Doucett- Che, Lead Engineer » Jay Moseley- EE, Controls Engineer » Marc Farfaglia- Che, Controls Liason.

Slides:



Advertisements
Similar presentations
Modelling and Simulation 7. September 2014 / Dr. –Ing Naveed Ramzan 1 Instrumentation and control Department of Chemical Engineering, U.E.T. Lahore Pakistan.
Advertisements

John Consiglio The Cooper Union February 24, 2009 Using Hardware-in-the-Loop Simulations to Improve EPA Emissions Testing.
Root Cause Analysis for Effective Incident Investigation Christy Wolter, CIH Principal Consultant Environmental and Occupational Risk Management (EORM.
Composite Filament Winding Machine: P09226 Shijo George Christofer Brayton Alex Sandy Tiago Santos Daniel Weimann Project Manager Electrical Engineer Chief.
Alternate Software Development Methodologies
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 6/e (McGraw-Hill 2005). Slides copyright 2005 by Roger Pressman.1.
MSD 1 P12453 Detailed Design Review Markus Holzenkamp Robin Leili Cody Anderson 5/17/2015 Detailed Design Review 1.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
Compressor ReVamp and Fabrication PO9452. Update Revised Concept Generation Selected some concepts Scheduled Conference call with Dresser Rand Schedules.
Team Members: Bryan McCormick (ME) Andy Freedman (ME) John Kreuder (ME) Ken McLoud (ME) Jon Holdsworth (EE) Gabriela Santa Cruz (IE) Thermoelectric Module.
Chapter 2 Succeeding as a Systems Analyst
Team 10 Air Conditioning Experiment Members –Sean Gallagher –Pamela McDowell –Brian Davison –Prathana Vanarath Sponsors –Dr. Wexler –Dr. Advani Advisor.
SE 555 Software Requirements & Specification 1 SE 555 Software Requirements & Specification Prototyping.
Wireless Data Acquisition for SAE Car Project by: J.P. Haberkorn & Jon Trainor Advised by: Mr. Steven Gutschlag.
FINAL PRESENTATION P The Team Austin Frazer Role: Lead Engineer - Analysis Major: Mechanical Engineering Eileen Kobal Role: Lead Engineer – Mixtures.
CSC230 Software Design (Engineering)
LSU 10/09/2007System Design1 Project Management Unit #2.
PIC Evaluation & Development Board Project Team Chad Berg – CprE Luke Bishop – CprE Tyson Stichka – EE Nick Veys - CprE Financial Budget Abstract/Background.
“HEAR IT AND FORGET IT, SEE IT AND REMEMBER IT, DO IT AND UNDERSTAND IT” R12310: ME and ChemE Lab and Demo Hardware Development DPM – Spring 2012.
P13621: Conductive Heat Transfer Lab Equipment MSD II: Final Project Review 10 May, 2013 RIT KGCOE.
SYSTEM ANALYSIS AND DESIGN
P13363 Touch Sensitive Piano Keys Justine Converse (ISE) James Cover (CE) Alexander Eschbach (EE) Jason Hang (ME) Ashley Trode (EE)
Project Process Control Flow Cart: Heat Exchange Temperature Control Loop Amanda Doucett, Dan Sacchitella, Jay Moseley, Micah Bitz, Marc Farfaglia,
» Dan Sacchitella – ChemE, Project manager » Amanda Doucett- ChemE, Lead Engineer » Jay Moseley- EE, Controls Engineer » Marc Farfaglia- ChemE, Controls.
Chapter 8: Systems analysis and design
Jon KleinISEProject Manager Nguyen VuMETechnical Lead Kyle MengesMETechnical Lead Christine LowryMEDesign Engineer Chris SteinMEDesign Engineer Priya NarasimhanEEElectrical.
Team: James Mazza, Andre Berwin, Peter Dunning, Nathan Fulcher, Andrew Watson, Travis Bardsley, Anthony Parker April 5, 2013.
Week 5: Business Processes and Process Modeling MIS 2101: Management Information Systems.
Evaluation and Recommendation of a Flow Computer For Replacing Chart Recorders ETM 5121 Project Proposal Submitted By Toby O’Brien.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Gravity Fed System Team Members: James Brinkerhoff, Christopher Kulbago, Patrick O’Connell, Lauren Pahls, Ted Rakiewicz, Sarah Salmon Group Number: P13631.
ERP. What is ERP?  ERP stands for: Enterprise Resource Planning systems  This is what it does: attempts to integrate all data and processes of an organization.
Software Engineering Management Lecture 1 The Software Process.
1 Chapter 5 Project management. 2 Project management : Is Organizing, planning and scheduling software projects.
Ankle Linear Force Comparison A (reference)BCD Current Passive-Dorsi-flex AFO Dorsi-flex assist AFOPlantar-flex assist AFOPlantar/Dorsi assist AFO Segment.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
AP-1 5. Project Management. AP-2 Software Failure Software fails at a significant rate What is failure? Not delivering it on time is an estimation failure.
Introduction to Software Development. Systems Life Cycle Analysis  Collect and examine data  Analyze current system and data flow Design  Plan your.
Gravity Fed System Team Members: Chris Kulbago, Lauren Pahls, Ted Rakiewicz, Patrick O’Connell, Sarah Salmon, James Brinkerhoff Group Number: P
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Gravity Fed System Team Members: Chris Kulbago, Lauren Pahls, Ted Rakiewicz, Patrick O’Connell, Sarah Salmon, James Brinkerhoff Group Number:
through Introduction  Particle Imaging Velocimetry (PIV) uses a sheet laser beam to illuminate particles that cross the sheet.  The particles.
Systems Development Life Cycle
Air Conditioning Experiment Department of Mechanical Engineering University of Delaware.
THROUGH NERANJAN DHARMADASA JAMES BROWN P09451: Thermo-Electric Module for Large Scale Systems.
Nanofluidic Characterization David Sharp David West Justin Davis.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
P13631: Gravity Fed Flow Process Control Teaching Aid An RIT education couples theory in lecture with practical application in lab. In the past, carts.
ELVIS Educational Laboratory Virtual Instrumentation Suite: Phase II Abstract Problem Statement The goal of this project is to convert the EE 201 labs.
MSD-II P ROJECT R EVIEW Modular Motion Tracking Sensors 1.
Fish Tank Project Introduction ME 121Portland State University Mechanical and Materials Engineering.
Ashima Wadhwa.  Probably the most time-consuming project management activity.  Continuous activity from initial concept through to system delivery.
بسم الله الرحمن الرحيم وبه نستعين
P10203 LV1 MOTOR CONTROLLER FINAL REVIEW MAY 14, 2010 Electrical: Kory Williams, Adam Gillon, Oladipo Tokunboh Mechanical: Louis Shogry, Andrew Krall.
Author: Nurul Azyyati Sabri
Software Engineering Management
Microcontroller Enhancement Design Project
Turbomachinery Flow Visualization P08453
P07203 Dynamometry Laboratory Infrastructure
CS 5150 Software Engineering
How SCADA Systems Work?.
Project Members: M.Premraj ( ) G.Rakesh ( ) J.Rameshwaran ( )
Software Life Cycle Models
MOOG EMA Installation MSD1 - P12251
Root Cause Analysis for Effective Incident Investigation
Project Readiness Review P10029 – Air Muscle Artificial Limb
SDLC (Software Development Life Cycle)
Project Management Unit #2
Presentation transcript:

» Dan Sacchitella – ChE, Project manager » Amanda Doucett- Che, Lead Engineer » Jay Moseley- EE, Controls Engineer » Marc Farfaglia- Che, Controls Liason » Rebecca Davidson- Che, Technical Engineer » Micah Bitz- ChE, Technical Engineer Systems Design Review MSD14/5/2013

» Project Background » Functional Analysis » Concept Development » Systems Architecture » Risk Assessment » Schedule Systems Design Review MSD14/5/2013

» Develop a process that will produce varied control results » Design the process using the skill sets of every individual in the group » Assemble process onto portable carts » Test and evaluate » Provide a recommended lab protocol for teaching Systems Design Review MSD14/5/2013

» Analysis for process and control interactions » Detailed design » Heat transfer model » Assembled cart for use in Chemical Engineering Lab » Evaluation results-system capability » Experimental protocol for teaching Systems Design Review MSD14/5/2013

» Designs requested: ˃PFD ˃P&ID ˃Fabrication ˃Equipment list ˃Control loop drawings ˃Electrical drawings ˃Operation manuals ˃Recommendation for spare parts and maintenance Systems Design Review MSD14/5/2013

» Design must be modular and adaptable » Durability » Minimal maintenance » Interface with Labview » Realistic to be utilized by students in the lab » Operated by 3 students » Control temperature by regulating flow or temperature Systems Design Review MSD14/5/2013

» Must fit on the cart currently in use by the Chem E department » Utilize donated equipment to reduce cost Systems Design Review MSD14/5/2013

Systems Design Review MSD14/5/2013

Systems Design Review MSD14/5/2013

Systems Design Review MSD14/5/2013

Systems Design Review MSD14/5/2013

» The cart is approximately 3’ by 2’ by 2’6” high » Uses two of the heating and cooling water recirculation baths that were used previously in the unit operations lab » Uses the air lines that will be available in the lab » Air operated valve dimensions are based on the one currently used on the existing flow carts » Uses a shell and tube heat exchanger with countercurrent flow » All cart components are supported by columns that attach to the upper level of the cart » Large components (such as the valve, controller, water baths and LCD output) are supported by a central structure that attaches to the lower level of the cart » The four temperature transmitters will be a combination of two RTD’s and two thermocouples Systems Design Review MSD14/5/2013

Systems Design Review MSD14/5/2013

Systems Design Review MSD14/5/2013

Systems Design Review MSD14/5/2013

 Organization of following slides is as follows:  Labview interface and control through national instrument equipment  Advantages and disadvantages  Labview interface using msp430 microcontroller to sample and collect data from rtd's and thermocouples, while using Honeywell controller to drive flow. Advantages and disadvantages  Complete Labview interface and control using msp430 to collect data from rtd/thermocouples, simulate customizable control through Labview, return data through msp430 to control flow.  Advantages and disadvantages  Risk assessment and analysis of all methods Goal: Present multiple possibilities for data acquisition and Labview interface while assessing the advantages and disadvantages of each in order to determine the best course of action in continuing with the design. Systems Design Review MSD14/5/2013

The national instruments data acquisition chassis with associated modules for thermocouple and rtd inputs can be used to collect temperature data and control the flow of the system through Labview. Systems Design Review MSD14/5/2013

Advantages Simple implement and interface with Labview Accurate data Has interchangeable parts for multiple types of inputs No external components will be needed to implement Used in real world applications Disadvantages Expensive chassis Expensive modules to go along with chassis each serving only one purpose Overpaying for what it is going to be used for Systems Design Review MSD14/5/2013

The Honeywell controller would be used to drive the flow control of the system. The microcontroller would be used to collect data from the rtd's and thermocouples and send it to the computer the systems data could be plotted and observed in Labview. Systems Design Review MSD14/5/2013

Advantages Shows students how to use and calibrate physical controller Microcontroller transferring data to computer can also be used to drive LCD displays with data Microcontrollers are extremely cheap and easily replaced and reprogrammed Can be designed so that the national instruments equipment can be easily swapped in Disadvantages External circuitry will be necessary Potential for more errors in temperature measurement (can be tested for) May potentially need EE to debug if problems in the future External power will need to be supplied (3.3v) Systems Design Review MSD14/5/2013

The thermocouple and rtd outputs will be tied directly to microcontroller which will interface with Labview. Data received in Labview will then go through a modeled controller in Labview to create a new set of data which will actively be output to another pin on the microcontroller. Data will then be processed and sent to control the flow rate of the system. Systems Design Review MSD1

Advantages Very adaptable, many different systems with can be modeled and tested through Labview. For example part of the lab could involve varying set pole locations and seeing their diminishing effect as their magnitude increases Cheap to implement Can be designed where the National Instruments equipment can be easily swapped in No real maintenance would be necessary Students would get a better feel for labview by creating the controller with the software instead of just using it to show data Disadvantages Difficult to implement and as a result more difficult to debug if something goes wrong in the future Although systems can be modified quickly in Labview, it will still be necessary to wait on the fluids to return to they're initial state temperature to run multiple experiments. External circuitry will be necessary Potential for more errors in temperature measurement (can be tested for) External power will need to be supplied (3.3v) Systems Design Review MSD14/5/2013

» PID equation » Valve characteristics ˃Inherent vs installed » Noise introduction and filtering » Manual Control ˃Manual pressure regulator on AOV » Find heat flow through the heat exchanger » Fit sensor data to the ideal equation of operation » RTD vs Thermocouple performance Systems Design Review MSD14/5/2013

Systems Design Review MSD14/5/2013

IDRisk ItemEffectCause Likelihood Severity Importance Action to Minimize RiskOwner Describe the risk briefly What is the effect on any or all of the project deliverables if the cause actually happens? What are the possible cause(s) of this risk? L*S What action(s) will you take (and by when) to prevent, reduce the impact of, or transfer the risk of this occurring? Who is responsible for following through on mitigation? 1 Customer Priority ChangesDelay of project progression Poor communication/ Uncertainty 224 Have weekly meetings with guide and keep both sides updated on project Project Manager 2Unreliable Suppliers Disrupt our project budget plan, and delay design process. Parts are not available through Kodak122 Take initiative and request parts from Guide, and compile a list of what we have and what needs to be orderedGroup 3Skill Set Alters design slightly, and will change list of parts that we need to order Only one EE to develop controls, and rest of team members have little experience in that field122 Group EE seeks feedback from EE department to make sure concepts are feasibleEE 4Team Dysfunction Poor team chemistry will demotivate group and may cause delays in deliverables. Differences in opinions/ concepts111 Reach consensus on ideas/concepts to make sure everybody is on boardGroup 5UnavailabilityMay delay deliverables Poor communications/ Illness212 Let group know if/ why you can’t attend meetings. Plan ahead.Individual 6Poor Communication People may not know current tasks Lack of motivation/communi cation with group members111 Keep everyone updated on current goals/ ideas. Ask for progress ahead of the date when the deliverable are expected. Project Manger Systems Design Review MSD14/5/2013

National Instruments risk : Cost of equipment, expensive to replace Honeywell controller risk : not easily replaceable since it was donated and a new controller would have to be bought if anything happens to it. microcontroller risk: difficult to develop and ensure accurate results Not much to lose with complete microcontroller interface and control with Labview and the advantages that it will provide More teaching flexibility Can replace with national instruments equipment if problems little cost, so hardly any loss if anything breaks Systems Design Review MSD14/5/2013

This project incorporates many expensive components, similar to those used in industry, to facilitate learning Many parts are being generously donated by Kodak A few components, such as the cart on which the system will be built, have to be bought The proposed budget will cover the cost of these parts We propose a budget of $1500 dollars to complete this project Systems Design Review MSD14/5/2013

Systems Design Review MSD14/5/2013

Systems Design Review MSD14/5/2013