Equipment Design Integrated Component Selection tool (EDICS) Jim Benfante Ray Seeger December 9, 2003.

Slides:



Advertisements
Similar presentations
Integration of MBSE and Virtual Engineering for Detailed Design
Advertisements

Defining Decision Support System
Chapter 11 user support. Issues –different types of support at different times –implementation and presentation both important –all need careful design.
NML/436/L1-1 Nazareth Northwestern Mutual Life Participants in IS Development l A team of people comprising: l Project Manager l Systems Analysts l Specialists.
Lab7: Introduction to Arduino
ATLAS Utility Management Software BobComm 2004 January
Lesson 1 Computers and Computer Systems
Key-word Driven Automation Framework Shiva Kumar Soumya Dalvi May 25, 2007.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Basic guidelines for the creation of a DW Create corporate sponsors and plan thoroughly Determine a scalable architectural framework for the DW Identify.
Pg. 1 Systems Development Life Cycle (SDLC) Systems Analyst – change agent Systems Analyst – change agent  coordination, communication, planning, design.
Chapter 3: System design. System design Creating system components Three primary components – designing data structure and content – create software –
1 Chapter 9 Rules and Expert Systems. 2 Chapter 9 Contents (1) l Rules for Knowledge Representation l Rule Based Production Systems l Forward Chaining.
Organizational Information Systems
Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall Chapter Chapter 7: Expert Systems and Artificial Intelligence Decision Support.
Fundamental System Concepts Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Updated: September 2014.
Chapter 2: Understanding and conceptualizing interaction
Managing Data & Information with the SECN Decision Support System GWS Meeting New Orleans, LA March 14-18, 2011.
Review 4 Chapters 8, 9, 10.
EXPERT SYSTEMS Part I.
Chapter 2: IS Building Blocks Objectives
Lead Black Slide. © 2001 Business & Information Systems 2/e2 Chapter 11 Management Decision Making.
Chapter 1 Program Design
Library Automation: Planning and Implementation
What is Business Analysis Planning & Monitoring?
Špindlerův Mlýn, Czech Republic, SOFSEM Semantically-aided Data-aware Service Workflow Composition Ondrej Habala, Marek Paralič,
Bina Nusantara 2 C H A P T E R INFORMATION SYSTEM BUILDING BLOCKS.
Katanosh Morovat.   This concept is a formal approach for identifying the rules that encapsulate the structure, constraint, and control of the operation.
Chapter 10 PLC Processors.
Using Mathematica for modeling, simulation and property checking of hardware systems Ghiath AL SAMMANE VDS group : Verification & Modeling of Digital systems.
Information System and Management
Programming. What is a Program ? Sets of instructions that get the computer to do something Instructions are translated, eventually, to machine language.
Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition Irwin/McGraw-Hill.
2131 Structured System Analysis and Design By Germaine Cheung Hong Kong Computer Institute Lecture 2 (Chapter 2) Information System Building Blocks.
Programming Project (Last updated: August 31 st /2010) Updates: - All details of project given - Deadline: Part I: September 29 TH 2010 (in class) Part.
RELATIONAL FAULT TOLERANT INTERFACE TO HETEROGENEOUS DISTRIBUTED DATABASES Prof. Osama Abulnaja Afraa Khalifah
Košice, 10 February Experience Management based on Text Notes The EMBET System Michal Laclavik.
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition Irwin/McGraw-Hill.
Property of Jack Wilson, Cerritos College1 CIS Computer Programming Logic Programming Concepts Overview prepared by Jack Wilson Cerritos College.
Copyright © 2002 Delmar Thomson Learning Chapter 10 PLC Processors.
Framework for MDO Studies Amitay Isaacs Center for Aerospace System Design and Engineering IIT Bombay.
15 August, 2005IEEE IRI Web Based Expert System for Class Schedule Planning using JESS Ken Ho Hewlett Packard Company Meiliu Lu Department of Computer.
Soft Computing Lecture 19 Part 2 Hybrid Intelligent Systems.
Why Do We Use Computers For Communication?. Read the words and make up the word combinations fax phone electronic to receive to send printed to use computer.
Internal and Confidential Cognos CoE COGNOS 8 – Event Studio.
CEN/ISSS eBIF GTIB Project Meeting, Brussels Mar , 2009 CEN/ISSS eBIF GTIB Project Meeting, Brussels 1 CEN/ISSS eBIF Global eBusiness Interoperability.
Inria Rhône-AlpesEMGnet meeting - December 98 1 A Platform for EMG Studies Danielle Ziébelin, Martine Maume and Philippe Genoud INRIA Rhône-Alpes Projet.
Dialog Design I Basic Concepts of Dialog Design. Dialog Outline Evaluate User Problem Representations, Operations, Memory Aids Generate Dialog Diagram.
Equipment Design Integrated Component Selection tool (EDICS) Jim Benfante Ray Seeger October 28, 2003.
Learning Objectives Understand the concepts of Information systems.
Enabling Grids for E-sciencE EGEE-III INFSO-RI Workflow management tool for Earth science applications Ladislav Hluchy, Viet Tran Institute of Informatics.
Model Based Systems Engineering Visualization Steven Corns Missouri University of Science & Technology.
VOCAB REVIEW. A field that can be computed from other fields Calculated field Click for the answer Next Question.
Advanced Higher Computing Science The Project. Introduction Worth 60% of the total marks for the course Must include: An appropriate interface using input.
SUBJECT : DIGITAL ELECTRONICS CLASS : SEM 3(B) TOPIC : INTRODUCTION OF VHDL.
Databases (CS507) CHAPTER 2.
The Components of Information Systems
Intelligent Systems Development
Information Systems Sarika Agarwal.
System Design, Implementation and Review
HARDWARE The hardware is the part you can see the computer, ie all components of their physical structure. The screen, keyboard, and mouse tower of the.
Developing Information Systems
Architecture Components
For Monday Read WebCT quiz 18.
The Components of Information Systems
Database System Architecture
Chapter 11 user support.
Design Review 2/21/2001.
DSS Concepts, Methodologies and Technologies
Presentation transcript:

Equipment Design Integrated Component Selection tool (EDICS) Jim Benfante Ray Seeger December 9, 2003

12/9/2003 Problem: Design of complex piece electronic equipment Proposal design – Base-Of-Estimate (BOE) Actual design – Bill-Of-Material (BOM) Cost estimating – Rough-Order-of-Magnitude (ROM) Conceptual design Short time frame Number of components Electronic module descriptions

12/9/2003 Solution: Provide automated design tool using AI applications and methodologies Provides quick matching of user requirements to available components to satisfy the design requirements. Outputs an electronic file capable of being inserted in existing report formats.

12/9/2003 Design Criteria: Component descriptions Module Monitor Cabling Fixture Chassis Cabinet Power Computer-PC

12/9/2003 Semantic Representation

12/9/2003 Semantic Representation (Digital)

12/9/2003 Agent Architecture: User Interface Inference Engine Data Base Output Selection Preliminary Clarification & Determination Administrator

12/9/2003 Knowledge Base Development Sources of knowledge Designer Expert Current designs

12/9/2003 Data Base Development Sources of data Vender information  Data sheet  Catalogs  Lead time  Cost Information standards  Approved Vendor List (AVL)

12/9/2003 Rules (Input Description Rules) (rule (value {if {linesInDigital > 0} {then {set Ports1 += linesInDigital / 8}}} {if {linesOutDigital > 0} {then {set Ports1 += linesOutDigital / 8}}} {if {linesBusDigitalIO > 0} {then {set Ports1 += linesBusDigitalIO / 8}}} {if {linesIsolatedDigital > 0} {then {set isolatedIO1 = linesIsolatedDigital}}})) * )

12/9/2003 Working User Input Screen ( Input Description rules )

12/9/2003 Rules ( Digital Module Rules – Comparing User input to Inventory ) (rule (value {if { {usersInput_1 parameter handshaking} = {this parameter handshaking} {and {this parameter possibility} not{"false"} } } {then {set {this parameter possibility} "true"}} {else {set {this parameter possibility} "false"}} } } {if { {usersInput_1 parameter messaging} = {this parameter messaging} {and {this parameter possibility} not{"false"} } } {then {set {this parameter possibility} "true"}} {else {set {this parameter possibility} "false"}} } } * )

12/9/2003 Working User Input Screen ( Digital Module rules )

12/9/2003 Working User Input Screen

12/9/2003 Working User Input Screen (D1001)

12/9/2003 Working User Input Screen ( User Input )

12/9/2003 Working User Input Screen ( User Input after rules )

12/9/2003 Working User Input Screen ( D1001 after rules )

12/9/2003 Final Rule (Making Module Selection) A) Using MATHRULE1 compare (req for Ports) to (inv avail ports) using PORTS1 - ISO1 (where PORTS1 = DigitalIN + DigitalOUT + DigitalIO) (where ISO1 = users linesIsolatedDigital) users req PORTS1, compared to the inventory parameter - portsIO. users req ISO1, compared to the inventory parameter - linesIsolatedDigital. *************************************************************************************** From NARL send the above parameters to a JAVA proc PORTS1 / portsIO = p1 #.### Possable answer a1: a1 = p1(round up to nearest integer) a1 is the number of boards of this type needed for solution. (The inv board with the Min a1 would be the selection.) (p1 exp. 9/4 = 2.25, 9/8 = 1.125, 9/16 = ) (a1 exp. 9/4 = 3, 9/8 = 2, 9/16 = 1 <-) #3? #2? #1 choice? (The selection will be made by COST or LEADTIME )

12/9/2003 Final Rule (Making Module Selection) Possable answer a2: PORTS1 / portsIO = p1 #.### a2 = p1(do NOT round up to nearest integer. Use Modulus function) a1 is the number of boards of this type needed for solution, plus (The inv board with the Min a1 would be the selection.) (p1 exp. 20/4 = 5, 20/8 = 2.5, 20/16 = 1.25) (a2 exp. 20/4 = 5, 20/8 = 2, 20/16 = 1 <--) (From the remainer, nL2 exp. 20/4 = 0, 20/8 = 4, 20/16 = 4) | (with a remainder of 0 no added boards are needed))

12/9/2003 Final Rule (Making Module Selection) Calculate to satisfy the remainder: a2r exp. 4/4 = 1 <--, 4/8 = 0.5, 4/16 = 0.25) Solutions: 1) Q1 from (a2 = 20/16) and Q1 from (a2r = 4/4) <-- #2? choice 2) Q1 from (a2 = 20/16) and Q1 from (a2r = 4/8) <--- #3? choice (4/8 will have unused Ports) The COST and LEADTIME decision may make this choice) Execute MATHRULE2 Execute MATHRULE3 Execute Select Best Comparison (User Input to Inventory)

12/9/2003 Estimate Rules for System Modules (~175 Rules) Digital Module 25 Analog Module25 Clock Module25 DAQ Module25 Com Module25 Switch Module25 Source Module 25 Cabling (~100 Rules) Computer (~150 Rules) Chassis (~75 Rules) Cabinet H/W (~250 Rules) Test Fixture (~75 Rules) Monitor (~75 Rules) Power (~125 Rules) Total Rule Estimate ~1025 Rule

12/9/2003 Proposed Design Solution

12/9/2003 Issues Use a database or individual text files Focus will be on Digital Module Selection JAVA/NARL Interaction Data parsing routines

12/9/2003 Status Conceptual design completed Adding to the existing rule base Selected JAVA and NARL Data file format