Product development Engineering & Regulatory Raj Agrawal InnAccel.

Slides:



Advertisements
Similar presentations
Medical Device Software Development
Advertisements

Testing Medical Devices A Brief Overview © 2005 Max Cortner. Copying and distribution of this document is permitted in any medium, provided this notice.

Product Documentation Chapter 5. Title 21 of the Code of Federal Regulations  Volume 1: Parts 1-99 (FDA, General)  Volume 2: Parts (FDA, Food.
System Integration Verification and Validation
S Y S T E M S E N G I N E E R I N G.
Software Process Models
1 Chapter 2: Product Development Process and Organization Introduction Importance of human resources: Most companies have similar technology resources.
Combining Product Risk Management & Design Controls
Introduction to Requirements (Chapters 1-3 of the requirements text) CSSE 371, Software Requirements and Specification Don Bagert, Rose-Hulman Institute.
1 SYSTEM and MODULE DESIGN Elements and Definitions.
Security Engineering II. Problem Sources 1.Requirements definitions, omissions, and mistakes 2.System design flaws 3.Hardware implementation flaws, such.
APPLICATION DEVELOPMENT BY SYED ADNAN ALI.
CMPUT Software Process & QualityProcess Categories - slide# 1©P. Sorenson Engineering Process Category  Processes that specify, implement, or maintain.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
Slide 1 of 11 April 2014 Rob Packard, President Regulatory Pathways 101: Your 1 st Product Launch in Canada,
Effective Methods for Software and Systems Integration
Web Development Process Description
RUP Fundamentals - Instructor Notes
From Research Prototype to Production
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
 Project overview  Project-specific success criteria  Block diagram  Component selection rationale  Packaging design  Schematic and theory of operation.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Engineering Development New Products New Product Idea Funnel Trade Shows Visits to Customers Input from Rep’s Input from Sales Mgr. Existing Products.
Development and Regulation of Medical Products (MEDR-101)
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
Product Documentation Chapter 5. Required Medical Device Documentation  Business proposal  Product specification  Design specification  Software.
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
Refined ECSS Software Process Model Elements SD-TN-AI-0570, Issue 5 APPENDIX D.
Chapter SIX Implementation, Testing and Pragmatics Making it a reality.
Project Proposal Document Optimization 15 February 2007 Team members: Chris Catalano Chun-Yu Chang Chris Joson David Matthes.
Robotics & Engineering Design Projective Management Chin-Sung Lin Eleanor Roosevelt High School.
Request for Proposal (RFP)
Introduction to Software Project Estimation I (Condensed) Barry Schrag Software Engineering Consultant MCSD, MCAD, MCDBA Bellevue.
Prof. Moustafa M. Mohamed Vice dean Faculty of Allied Medical Science Pharos University in Alexandria Development and Regulation of Medical Products (MEDR-101)
DPE CSSW Process Model Annex A WP-400 ECSS Case Study.
R&D and Product Development Engineering Management & Design Process Hub van de Bergh - July Rev 1 | 17 July 2004 | Hub van de Bergh
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
Design Documentation Clint Kehres, Brian Krouse, Jenn Shafner.
The Engineering Design Process
Joel Gerber Zachary Reaver Kurt Schilling.  Provides physical proof of development  Maintains product design knowledge base  Meets government and corporate.
Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.
IDeaWorks- Good To Great – Program Hisham Al Zanoon July 5, 2012.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Surgical and Laboratory Instruments and Devices. Ward Engineering is a provider of quality medical device design, development, and manufacturing services.
Joe Selva Rohan Thakkar Jean Valderrama.  “Documentation” is what’s written on paper  Provides written details, events, and information about a particular.
Request for Proposal (RFP) In response to the RFP – the first step is to prepare a proposal 1. Review Customer Requirements and come up with candidate.
Plan-Driven Processes Emerson Murphy-Hill. The Planning Spectrum 2 Source: Barry Boehm “Get Ready For Agile Methods, With Care,” IEEE Computer, Jan 2002.
Engineering Quality Software Week02 J.N.Kotuba1 SYST Engineering Quality Software.
Medical Device Software Development
Raechel Huebner Ruthanne Sherer
FRIB PLC Testing & Verification Process
THE PROCESS OF EMBEDDED SYSTEM DEVELOPMENT
Software Requirements
Request for Proposal (RFP)
Rational Unified Process
Introduction to Software Testing
University of Idaho – Interdisciplinary Engineering Capstone Design
Software Development Process
EMIS 7307 Chapter 6.
Instrument PDR Summary of Objectives
Medical Device Design and Development
DOD’S PHASED SYSTEM DEVELOPMENT PROCESS
Engineering Quality Software
PSS verification and validation
University of Idaho – Interdisciplinary Engineering Capstone Design
Corey Beth Monarch Lindsey Novak Michael Seikel Whitney Young
Unit IV – Chapter 2 V-Test Model.
Presentation transcript:

Product development Engineering & Regulatory Raj Agrawal InnAccel

Why the process?

Product meets the user requirements Product is Safe & effective Regulatory compliance

D&D Process - Logic Requirements Design Testing Release

D&D Process – High level This model is translated to a more elaborated model as illustrated in the subsequent slides

D&D Process MRD Program Plan PRD Alpha proto D&D Plan Architecture Designs Prototypes V&V Plan User requirements Design output Clinical & regulatory Design inputs Design process Verification & internal validation M0 M0 A M0 B M1 Design Transfer & Pilot lot M2 M2 A Pilot field performance M3 Verification and validation reports Review Within each stage, the process is iterative Risk Mgt Milestones for go/ no go determination

Milestone-wise Deliverables User needs & program plan stage MRD Program Plan IP strategy M0 Design input stage Product reqts (PRD) Design & Development Plan Alpha proto Design review M0-A Engineering design & proto stage System Architecture, DRS, SRS, Integration Plan Prototype V&V Plan Strategy, Plan for external evaluation Preliminary Scope of external evaluation Entry Criteria for external Evaluation Design review M0-B V&V stage Verification reports Internal validation reports Readiness review for external Evaluation (based on the entry criteria) Final Scope of the external evaluation M1 Clinical & regulatory - Ready for pilot production External Evaluation outcome review Pilot customer list M2 Pilot build stage Pilot lot verification & validation results Ship first unit to customer M2-A Pilot units field performance Performance of the pilot units at customer locations Decide M4 schedule (post- market surveillance) M3

Proto Plan - Example

Proto - example Alpha proto of a secretion management device

High Level System Architecture- Example

Integrated System Architecture - Example

Design reviews Design Reviews are the systematic examination to – evaluate capability of the design to meet requirements evaluate adequacy of the requirements identify any problems

Design reviews

Regulatory documentation CE Product file Technical file Design output FDA Design History File (DHF) 510 (K) Device Master Record (DMR) Category DHF Elements Plan Marketing Requirement Document Product Requirement Document Design and Development Plan Verification & validation Plan Clinical Evaluation Plan Risk Management Plan System Clnical Workflow document Navigation diagram and alarm behaviour System Architecture document System Design Requirement Specification Risk management file( Risk Analysis, SHA) Residual Risk System verification protocol(SDRS) Software Software Development Plan Software Requirement Specification Software Design Specifications(SDD) Detailed Design Code Unit Test Protocols Integration test protocol Application Embedded Interface Configuration Management Review Records Mech Design Requirement Specifications -Mech Review Records Design Notes Drawings CAD Models Label Drawing Bill of Materials Hardware Design Requirement Specifications - EE Design Notes-Hardware ELECTRICAL SCHEMATIC SOP for Cable Assembly EMI EMC Changes Bill of Materials FQC(Comprises all the hardware tests ) FTR(Comprises all the hardware tests like ELECTRICAL safety Tests) Circuit Schematics PSP’s Intial Inspection Test Report Hardware Verification Test Plan Hardware Verification Test Records PCB Test Report Review Records Firmware Design Requirements Specifications - Firmware Design Notes Code Communication Protocols Unit Test Protocols Integration Test Protocols Configuration Management Review Records

Recap MRD Program Plan PRD Alpha proto D&D Plan Architecture Designs Prototypes V&V Plan User requirements Design output Clinical & regulatory Design inputs Design process Verification & internal validation M0 M0 A M0 B M1 Design Transfer & Pilot lot M2 M2 A Pilot field performance M3 Verification and validation reports Review Within each stage, the process is iterative Risk Mgt