DOCSLIB.ORG

Engineering Design Process in the Mechanical Engineering Program at Cal Maritime: an Integrated Approach

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Engineering Design Process in the Mechanical Engineering Program at Cal Maritime: an Integrated Approach Engineering Design Process in the Mechanical Engineering Program at Cal Maritime: An Integrated Approach Teaching and Learning in the Maritime Environment Conference The California Maritime Academy Vallejo, CA 94590 Mansur Rastani Cal Maritime Academy Mechanical Engineering Department Vallejo, CA 94590 Nader Bagheri Cal Maritime Academy Mechanical Engineering Department Vallejo, CA 94590 Garett Ogata Cal Maritime Academy Mechanical Engineering Department Vallejo, CA 94590 1 AbstractU The capstone design project has become an integral part of the mechanical engineering (ME) program at Cal Maritime. Students in the program take three courses in sequence starting in the spring semester of their junior year. The first course, Engineering Design Process, introduces the students to the ten tasks involved in the design process. These tasks are introduced and taught in five stages as follows: 1) Problem Definition, 2) Conceptual Design, 3) Preliminary Design, 4) Detailed Design and prototyping, and 5) Communication Design. The details of each task are introduced and discussed. Students implement the first three stages in their second course, Project Design I, and the last two stages in their third course, Project Design II. Successful completion and understanding of these courses are the key to completing the ME program requirements as well as on-time graduation at Cal Maritime. IntroductionU Definition: Engineering design is an iteration process of devising a system to meet a set of desired needs. The design process begins with an identified need, which can be initiated based on any of the following sources: Observable deficiency (i.e., A car bumper that gets easily damaged in low speed collisions) Product improvement (i.e., A system for improving traction on ice without studs or chains) New products (i.e., A more effective alarm clock for reluctant students) Change in law (i.e., An average automobile gas mileage of 25 miles per gallon of gasoline) When a new design problem is begun, very little is known about the solution, especially if the problem is a new one for the designer. As work on the project progresses, the designer’s knowledge about the technologies involved and the alternative solutions increase. Thus, the goal during the design process is to learn as much about the evolving product as early as possible in the design process because during the early phases changes are least expensive. The systematic methodology of the evolutional engineering design process consists of five stages as follows: 1) Problem Definition In this stage the objectives, constraints, and the functional requirements of the designed objects are clarified through qualified terms by the customers, which in turn are converted into measurable engineering parameters. 2) Conceptual Design In this stage using brainstorming method and morphological tool, from information compiled in prior phase, concepts are created, evaluated, and design alternatives are selected. 3) Preliminary Design In this stage the product architecture (form and shape) is performed, materials are selected, and engineering analysis is carried out. 4) Detailed Design & Prototyping In this stage the preliminary design is refined through design for manufacturing, design for assembly, and design for safety & reliability. Detailed drawings, bill of materials and final design review are executed. 5) Communication Design This is the last stage of the design process that includes the final written report and oral presentation. Each stage has been itemized into instructional tasks as set of languages that we can use to describe how those designed objects came to be. 2 ProblemU Definition Stage This stage involves tasks 1A, 1B, 2, and 3. Each task is described below: TaskU 1A: Identifying User Requirements / Clarifying Design Objectives This task presents a method for comprehensively identifying a set of customer needs. The goals of the method are to: 1 • Ensure that the product is focused on customerTPF F PT needs • Identify implicit needs as well as explicit needs • Provide a fact base for justifying the product specifications • Ensure that no critical customer need is missed or forgotten • Develop a common understanding of customer needs among members of the development team. A team should be able to identify customer needs without knowing how it will eventually address those needs. Also note that we choose to use the word need to label any attribute of a potential product that is desired by the customer. Other terms used in industrial practice to refer to customerU needs U include customerU requirements, design attributes, and design objectives.U The latter is the terminology used in this course. Objectives are usually expressions of the desired attributes and behavior that the potential users would find attractive. They are normally expressed as "being" statements that say what the design will be, 2 as opposed to what the design must doTPF F.PT Identifying customer needs is itself a process, for which we present a three-step method as follow: 1. Gather data on customer needs. 2. Organize the needs into a hierarchy of primary, secondary, and if necessary, tertiary needs (Objective Tree). 3. Establish the relative importance of the needs (Weighted Objective Tree). StepU 1. Gathering data on customer needs Means for gathering data includes: 1. Literature Review on Similar Products 2. Market Research 3. Bench Marking 4. Interviews & Focus Groups 5. User Survey 6. Consulting Expertise 7. Questioning and Brainstorming 8. Reverse Engineering on Competitive products (Dissection) 9. Watching Customers Use an Existing Product 10. Web Sites for Similar Products StepU 2. Organize the needs into a hierarchy of primary, secondary, ……. needs (Objective Tree). The results of step 1 may end up to a large number of need statements. Working with such a long list of detailed needs is difficult. The goal of this step is to organize these needs into a hierarchical list. Group the need statements according to the similarity of the needs they express. The list will typically consist of a set of primary needs, each one of which will be further characterized by a set of secondary needs. In some cases, the secondary needs may be broken down into tertiary needs as well. The primary needs are the most general needs, while the secondary and tertiary needs express needs in more detail. The groups of need statements are clustered according to the similarity of the needs they express, and then organized in hierarchical order by assigning a head-objective to a group of sub-objectives. 1 TP PT Word “customers” refers to: manufacturers, marketing staff, distributors, retailers, and the end users. 2 TP PT Functions are the things a design supposed to do, the actions that it must perform. Functions are usually expressed as "doing" terms. We will discuss functions in greater details later in task 2. 3 ObjectiveU Tree:U The above hierarchical list can then be put in an objective tree form, which is a graphical depiction of the objectives for the artifact. The top-level goal in an objective tree, which we represent as a node at the peak of the tree, is decomposed or broken down into sub-goals that are at different levels of importance or that include progressively more detail, so the tree reflects a hierarchical structure as it expands downward. An objective tree also shows that related sub-goals or similar ideas can be clustered together, which gives the tree some organizational strength and utility. StepU 3. Establish the relative importance of the needs (Weighted Objective Tree). So far we have assumed that all of the design objectives are equal, whereas it is almost certain that some objectives will be worth more than others. We use a fairly simple technique, pair-wise comparison, which can be used to rank a cluster of objectives that are at the same level in the objective tree. It is important to keep in mind that the pair-wise comparison method should be applied in a "top-down" fashion, so that the higher-level objectives are compared and ranked before those at lower levels. Each design objective is listed and is compared to every other objective, two at a time. In making the comparison the objective that is considered the more important of the two is given a 1 and the less important objective is given a 0. A rating of 1/2 is given for objectives that are equally valued. The total number of possible comparisons is N= n(n-1)/2, where n is the number of objectives under consideration. The ratings are added and the total score for each one of the objectives are listed. In the resulting scores, if the smallest score for an objective is a zero, it is changed to one, which in turn moves up the scale for the other scores by one. The reason for doing this is simply due to the fact that an objective cannot have a zero value. TaskU 1B: Identifying Constraints Constraints are restrictions or limitations on a behavior or a value or some other aspect of a designed object's performance. Constraints are important to the designer because they limit the size of design space by forcing the exclusion of unacceptable alternatives. For example for a ladder design project, any design that fails to meet OSHA standards will be rejected. Objectives and constraints sometimes seem to be interchangeable, but they are not. On the other hand, objectives and constraints are closely related. Constraints limit the size of the design space, while objectives permit the exploration of the remainder of the design space (i.e. expand the design space). Constraints are usually expressed in measurable, quantitative terms, such as dollars, pounds, cubic feet, Psi, etc, whenever possible. Tools for identifying constraints, are listed below: 1. Identify sponsor-imposed constraints 2. Identify any compatibility constraints (with existing equipment, or mating parts) 3.
Load more

Recommended publications
  • Open JW Masters Final Thesis.Pdf
    The Pennsylvania State University The Graduate School Engineering Design, Technology, and Professional Programs PART DESIGN AND TOPOLOGY OPTIMIZATION FOR RAPID SAND AND INVESTMENT CASTING A Thesis in Engineering Design by Jiayi Wang 2017 Jiayi Wang Submitted in Partial Fulfillment of the Requirements for the Degree of Master of Science December 2017 The thesis of Jiayi Wang was reviewed and approved* by the following: Guha P. Manogharan Assistant Professor of Mechanical and Nuclear Engineering Thesis Co-Advisor Timothy W. Simpson Paul Morrow Professor of Engineering Design and Manufacturing Thesis Co-Advisor Sven G. Bilén Professor of Engineering Design, Electrical Engineering, and Aerospace Engineering Head of School of Engineering Design, Technology, and Professional Programs *Signatures are on file in the Graduate School iii ABSTRACT The integration of additive manufacturing into traditional metal casting provides a wide range of rapid casting solutions. One important motive for rapid casting is additive manufacturing’s ability to create highly complex objects without any fixture or tooling requirements. Such advantages provide great design freedom for the geometry of cast metal parts. The objective in this thesis is to explore the part design opportunistic and restrictions of two rapid casting processes: (1) sand casting with 3D Sand Printing-fabricated molds and (2) investment casting using material extrusion–fabricated wax-like patterns. Knowledge-based design guidelines are developed for both of these rapid casting processes through novel integration of topology optimization with design for casting and design for AM principles. For each process, a case study is conducted in which a mechanical metal benchmark is topologically optimized and redesigned following the proposed design rules.
    [Show full text]
  • Network Optimization and High Availability Configuration Guide for Vedge Routers, Cisco SD-WAN Releases 19.1, 19.2, and 19.3
    Network Optimization and High Availability Configuration Guide for vEdge Routers, Cisco SD-WAN Releases 19.1, 19.2, and 19.3 First Published: 2019-07-02 Last Modified: 2019-12-22 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 © 2019 Cisco Systems, Inc. All rights reserved. CONTENTS CHAPTER 1 What's New for Cisco SD-WAN 1 What's New for Cisco SD-WAN Release 19.2.x 1 CHAPTER 2 Network Optimization Overview 3 Cloud OnRamp for IaaS 3 Provision vManage for Cloud OnRamp for IaaS 4 Configure Cloud OnRamp for IaaS for AWS 8 Configure Cloud OnRamp for IaaS for Azure 14 Troubleshoot Cloud OnRamp for IaaS 19 Cloud OnRamp for SaaS 22 Enable Cloud OnRamp for SaaS 23 Configure Cloud OnRamp for SaaS 24 Monitor Performance of Cloud OnRamp for SaaS 26 Cloud OnRamp for Colocation Solution Overview 27 Manage Clusters 28 Provision and Configure Cluster 29 Create and Activate Clusters 30 Cluster Settings 33 View Cluster 35 Edit Cluster 35 Remove Cluster 36 Reactivate Cluster 37 Create Service Chain in a Service Group 37 Create Custom Service Chain 42 Custom Service Chain with Shared PNF Devices 43 Configure PNF and Catalyst 9500 46 Network Optimization and High Availability Configuration Guide for vEdge Routers, Cisco SD-WAN Releases 19.1, 19.2, and 19.3 iii Contents Custom Service Chain with Shared VNF Devices 46 Shared VNF Use Cases 48 View Service Groups 54 Edit Service Group 54 Attach and Detach Service Group with Cluster 55 View Information
    [Show full text]
  • Configuration Management in Nuclear Power Plants
    IAEA-TECDOC-1335 Configuration management in nuclear power plants January 2003 The originating Section of this publication in the IAEA was: Nuclear Power Engineering Section International Atomic Energy Agency Wagramer Strasse 5 P.O. Box 100 A-1400 Vienna, Austria CONFIGURATION MANAGEMENT IN NUCLEAR POWER PLANTS IAEA, VIENNA, 2003 IAEA-TECDOC-1335 ISBN 92–0–100503–2 ISSN 1011–4289 © IAEA, 2003 Printed by the IAEA in Austria January 2003 FOREWORD Configuration management (CM) is the process of identifying and documenting the characteristics of a facility’s structures, systems and components of a facility, and of ensuring that changes to these characteristics are properly developed, assessed, approved, issued, implemented, verified, recorded and incorporated into the facility documentation. The need for a CM system is a result of the long term operation of any nuclear power plant. The main challenges are caused particularly by ageing plant technology, plant modifications, the application of new safety and operational requirements, and in general by human factors arising from migration of plant personnel and possible human failures. The IAEA Incident Reporting System (IRS) shows that on average 25% of recorded events could be caused by configuration errors or deficiencies. CM processes correctly applied ensure that the construction, operation, maintenance and testing of a physical facility are in accordance with design requirements as expressed in the design documentation. An important objective of a configuration management program is to ensure that accurate information consistent with the physical and operational characteristics of the power plant is available in a timely manner for making safe, knowledgeable, and cost effective decisions with confidence.
    [Show full text]
  • 19 International Configuration Workshop
    19th International Configuration Workshop Proceedings of the 19th International Configuration Workshop Edited by Linda L. ZHANG and Albert HAAG September 14 – 15, 2017 La Defense, France Organized by ISBN: 978-2-9516606-2-5 IESEG School of Management Socle de la Grande Arche 1 Parvis de La Défense 92044 Paris La Défense cedex France Linda L. ZHANG and Albert HAAG, Editors Proceedings of the 19th International Configuration Workshop September 14 – 15, 2017, La Défense, France Chairs Linda L ZHANG, IESEG School of Management, Lille-Paris, France Albert HAAG, Albert Haag – Product Management R&D, Germany Program Committee Michel ALDANONDO, Mines Albi, France Tomas AXLING, Tacton Systems AB, Sweden Andres BARCO, Universidad de San Buenaventura-Cali, Colombia Andreas FALKNER, Siemens AG, Austria Alexander FELFERNIG, Graz University of Technology, Austria Cipriano FORZA, Universita di Padova, Italy Gerhard FRIEDRICH, Alpen-Adria-Universitaet Klagenfurt, Austria Albert HAAG, Albert Haag – Product Management R&D, Germany Alois HASELBOECK, Siemens AG, Austria Petri HELO, University of Vassa, Finland Lothar HOTZ, HITeC e.V. / University of Hamburg, Germany Lars HVAM, Technical University of Denmark, Denmark Dietmar JANNACH, TU Dortmund, Germany Thorsten KREBS, Encoway GmbH, Germany Katrin KRISTJANSDOTTIR, Technical University of Denmark, Denmark Yiliu LIU, Norwegian University of Science and Technology, Norway Anna MYRODIA, Technical University of Denmark, Denmark Brian RODRIGUES, Singapore Management University, Singapore Sara SHAFIEE, Technical University of Denmark, Denmark Alfred TAUDES, Vienna University of Economics & Business, Austria Élise VAREILLES, Mines Albi, France Yue WANG, Hang Seng Management College, Hong Kong Linda ZHANG, IÉSEG School of Management, France Organizational Support Céline LE SUÜN, IÉSEG School of Management, France Julie MEILOX, IÉSEG School of Management, France Preface As a special design activity, product configuration greatly helps the specification of customized products.
    [Show full text]
  • Modelling of Product Configuration Design and Management by Using Product Structure Knowledge
    8 Modelling of Product Configuration Design and Management by Using Product Structure Knowledge Bei Yu and Ken J. MacCallum University of Strathclyde CAD Centre, University of Strathclyde, 75 Montrose Street, Glasgow GJ 1XJ, UK, Tel: +44 41 552 4400 Ext. 2374, Fax: 01223-439585. email: [email protected], [email protected] Abstract For whole life cycle of product development, configuration can be considered from two aspects: configuration design which is the activity of creating configuration solutions, and configuration management which is the process of maintaining a consistent configuration under change. Both configuration design and configuration management are complex pro­ cesses for many products, particularly when the product structure is complex in terms of a large number of elements with different relationships, the configuration problem will be significant. This paper presents an AI-based system to support configuration design and manage­ ment. The contribution is of a system which models product configuration knowledge, and uses a Reason Maintenance System as an inference engine to assist the designer to create a product structure in terms of configuration solution. At the same time, the configuration consistency is maintained by the inference engine. Keywords configuration design and management, product structures, reason maintenance mecha­ nism, logic-based truth maintenance system, constraint-based reasoning. 1 INTRODUCTION In engineering design, any product or machine can be viewed as a technical system which consists of elements and their relationships. Configuration thus can be regarded as a pro­ cess: from a given set of elements, to create an arrangement by defining the relationships between selected elements that satisfies the requirements and constraints.
    [Show full text]
  • Audiovisual Best Practices
    AUDIOVISUAL AUDIOVISUAL BEST PRACTICES The Design and Integration Process for the AV and Construction Industries AUDIOVISUAL With pride, thoughtfulness and attention to detail, Audiovisual Best Practices was created for everyone responsible for ensuring the success of an AV project. And in today’s environment of exploding growth in sophisticated information communications technology within every aspect of public life, this book arrives in the nick of time. BEST It is a guide designed to bring all the players in AV systems integration to a point of mutual understanding and collaboration. Developed in an easy-to-read, logical format, BEST Audiovisual Best Practices offers the recommendations of highly successful experts with years of experience in systems integration and design, consultancy, project management and information technology. PRACTICES The following audiences will find this book invaluable: I Architects I Facility owners PRACTICES I Building and construction personnel I Project managers I Consultants I AV industry newcomers I Contractors I AV professionals I Developers I Sales representatives I Engineers I Rental and sales Read what others in the field have to say about this book: “An essential read - this is an invaluable guidebook that defines the course of action for everyone involved in building and integrating installed AV systems. As an end-user technology manager, I have needed a resource like this to communicate better, and THE DESIGN AND now we have it!” — John Pfleiderer, MA, CTS-D, Video Infrastructure Coordinator, INTEGRATION PROCESS Cornell University Ithaca, NY FOR THE AV “AV Best Practices is a great primer for owners, architects, design consultants and AV AND CONSTRUCTION professionals on the processes required to create great technology-intensive projects, achieve timely collaboration, speed decision/procurement processes and reduce INDUSTRIES overall risk.
    [Show full text]
  • The Relative Contribution of Individual Team Member Proficiency In
    Only as Strong as the Strongest Link: The Relative Contribution of Individual Team Member Proficiency in Configuration Ethan Brownell Department of Mechanical Engineering, Design Carnegie Mellon University, Pittsburgh, PA 15213 Prior research has demonstrated how the average characteristics of a team impact team e-mail: [email protected] performance. The relative contribution of team members has been largely ignored, espe- cially in the context of engineering design. In this work, a behavioral study was conducted Jonathan Cagan with 78 participants to uncover whether the most or least proficient member of a configu- Department of Mechanical Engineering, ration design team had a larger impact on overall performance. Proficiency is an individ- Carnegie Mellon University, ual’s ability to deal with a specific range of problem. It was found that a configuration Pittsburgh, PA 15213 design team is most dependent on the proficiency of its most proficient member. The most e-mail: [email protected] proficient member had a significant positive effect on how quickly the team reached perfor- mance thresholds and the other members of the team were not found to have the same pos- Kenneth Kotovsky itive impact throughout the design study. Behavioral heuristics were found using hidden Department of Psychology, Markov modeling to capture the differences in behavior and design strategy between differ- Carnegie Mellon University, ent proficiency members. Results show that high proficiency and low proficiency team Pittsburgh, PA 15213 members exhibit different behavior, with the most proficient member’s behavior leading e-mail: [email protected] to topologically simpler designs and other members adopting their designs, leading to the most proficient member driving the team design and thus the team performance.
    [Show full text]
  • Engineering Design Synthesis Springer-Verlag London Ltd
    Engineering Design Synthesis Springer-Verlag London Ltd. http://www.springer.de/phys/ Amaresh Chakrabarti (Ed) Engineering Design Synthesis Understanding, Approaches and Yools Springer Amaresh Chakrabarti Associate Professor Centre for Product Design and Manufacturing (CPDM) Indian Institute of Science Bangalore 560012 Karnataka, India British Ubrary Cataloguing in Publication Data Engineering design synthesis: understanding, approaches and tools 1. Engineering design 2. Engineering design - Data processing 3. Engineering design - Computer pro grams 1. Chakrabarti, Amaresh 620'.0042 ISBN 978-1-84996-876-8 ISBN 978-1-4471-3717-7 (eBook) DOI 10.1007/978-1-4471-3717-7 Library of Congress Cataloging-in-Publication Data Engineering design synthesis: understanding, approaches and tools I Amaresh Chakrabarti (ed). p. cm. Includes bibliographieal references and index. 1. Engineering design. 1. Chakrabarti, Amaresh. TA174.E5452001 620' .0042 - dc21 2001038410 Apart from any fair dealing for the purposes of research or private study, or criticism or review, as permitted under the Copyright, Designs and Patents Act 1988, this publication may only be reproduced, stored or transmitted, in any form or by any means, with the prior permission in writing of the publishers, or in the case of reprographie reproduction in accordance with the terms of licences issued by the Copyright Ucensing Agency. Enquiries concerning reproduction outside those terms should be sent to the publishers. © Springer-Verlag London 2002 Originally published by Springer-Verlag London Limited in 2002. Softcover reprint of the hardcover 1st edition 2002 The use of registered names, trademarks, etc. in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant laws and regulations and therefore free for general use.
    [Show full text]
  • Canavangard, Udo Kasemets's Trigon, and Marshall
    Twentieth-Century Music 14/2, 209–243 © Cambridge University Press, 2017 doi: 10.1017/S1478572217000214 Canavangard, Udo Kasemets’s Trigon, and Marshall McLuhan: Graphic Notation in the Electronic Age JEREMY STRACHAN Abstract Composer Udo Kasemets (1919–2014) emigrated to Canada in 1951 from Estonia following the Second World War, and during the 1960s undertook a number of initiatives to mobilize experimental music in Toronto. This article investigates Canavangard, Kasemets’s publication series of graphic scores which appeared between 1967 and 1970. Influenced by Marshall McLuhan’s spatial theory of media, Kasemets saw the transformative potential of non-standard notational practices to recalibrate the relationships between composer, performer, and listener. Kasemets’s 1963 composition Trigon,whichwasfrequentlyperformedbyhisensembleduringthedecade, illuminates the connections between McLuhan and experimental music. In my analysis of the work, I argue that Trigon manifestly puts into performance many of the rhetorical strategies used by McLuhan to describe the immersive, intersensory environments of post-typographic media ecologies. Kasemets believed that abandoning standard notation would have extraordinary ramifications for musical practice going forward in the twentieth century, similar to how McLuhan saw the messianic power of electronic media to destabilize the typographic universe. Canavangard, as much more than a short-lived publication series of graphic scores, maps the convergences of music, culture, and technology in post-war Canada. Introduction Anewgenerationwhichhasgrownupwithafreshsenseofinvolvement will make radical alterations in the overall character of the music scene. The symphony hall and the opera house will be treated for what they are: museums for keeping the treasures of the past. The real musical life will be governed again by music of its own time.1 On 3 October 1965, a troupe of performers making their debut as the Isaacs Gallery Mixed Media Ensemble performed Udo Kasemets’s Trigon at the University of Toronto’s Faculty of Music.
    [Show full text]
  • Download MSFC-STD-3394-A.Pdf
    MSFC-STD-3394 National Aeronautics and REVISION A Space Administration January 31, 2005 George C. Marshall Space Flight Center Marshall Space Flight Center, AL 35812 ED03 STANDARD FOR CONTRACTOR CONFIGURATION MANAGEMENT FOR MSFC PROGRAMS/PROJECTS Approved for Public Release; Distribution is Unlimited CHECK THE MASTERLIST VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE Multiprogram/Project Common-Use Document ED03 Title: Standard for Contractor CM Document No.: MSFC-STD-3394 Revision: A Requirements, MSFC Programs/Projects Effective Date: January 31, 2005 Page 2 of 70 DOCUMENT HISTORY LOG Status Document Effective (Baseline/ Revision Date Description Revision/ Canceled) Baseline 09/30/2003 Initial Release Revision A 01/31/2005 General: updated language utilizing “shall” for requirements (avoiding use of must or will) per Rules Review; 2.0 Changes reflecting new Marshall Program Requirements; 6.1 change acknowledging variance in selection CIs for technology studies; 6.4 change providing greater detail on engineering drawing requirements and content; 6.4.2 Added section for CAD models; 7.1 Add text specifying location of engineering release system; 8.7 New paragraph defining post-deployment software/firmware change process; 8.7 Added information relative to MSFC form 460 in the deviation/waiver process; 9.3.5 Add paragraph describing software status accounting; 10.2 Added requirement for specific planning issued to be addressed during planning; 10.3 Made allowances for Government overview of FCA/PCA, added requirement for Contractor to
    [Show full text]
  • Design Standard Control System
    JERG-2-500A DESIGN STANDARD CONTROL SYSTEM Mar 17,2014 Japan Aerospace Exploration Agency JERG-2-500A This is an English translation of JERG-2-500A. Whenever there is anything ambiguous in this document, the original document (the Japanese version) shall be used to clarify the intent of the requirement. Disclaimer The information contained herein is for general informational purposes only. JAXA makes no warranty, express or implied, including as to the accuracy, usefulness or timeliness of any information herein. JAXA will not be liable for any losses relating to the use of the information. Published by Japan Aerospace Exploration Agency Safety and Mission Assurance Department 2-1-1 Sengen Tsukuba-shi,Ibaraki 305-8505, Japan i JERG-2-500A Contents 1. General Provisions ............................................................................................................................. 1 1.1 Purpose .............................................................................................................................................. 1 1.2 Scope.................................................................................................................................................. 1 1.3 Related documents ............................................................................................................................. 1 1.3.1 Document system ............................................................................................................................... 1 1.3.2 Applicable documents .......................................................................................................................
    [Show full text]
  • 9. Configuration, Design Security, and Remote System Upgrades in Arria II July 2012 AIIGX51009-4.3 Devices
    9. Configuration, Design Security, and Remote System Upgrades in Arria II July 2012 AIIGX51009-4.3 Devices AIIGX51009-4.3 This chapter describes the supported configuration schemes for Arria® II devices, instructions for executing the required configuration schemes, and the necessary option pin settings. This chapter also reviews the different ways you can configure your device and explains the design security and remote system upgrade features for Arria II devices. Arria II devices use SRAM cells to store configuration data. Because SRAM memory is volatile, you must download configuration data to the Arria II device each time the device powers up. All configuration schemes use either an external controller (for example, a MAX® II device or microprocessor), a configuration device, or a download cable. This chapter includes the following sections: ■ “Configuration Features” ■ “Power-On Reset Circuit and Configuration Pins Power Supply” on page 9–4 ■ “Configuration Process” on page 9–7 ■ “Configuration Schemes” on page 9–9 ■ “Fast Passive Parallel Configuration” on page 9–11 ■ “AS and Fast AS Configuration (Serial Configuration Devices)” on page 9–19 ■ “PS Configuration” on page 9–26 ■ “JTAG Configuration” on page 9–33 ■ “Device Configuration Pins” on page 9–39 ■ “Configuration Data Decompression” on page 9–46 ■ “Remote System Upgrades” on page 9–48 ■ “Remote System Upgrade Mode” on page 9–52 ■ “Dedicated Remote System Upgrade Circuitry” on page 9–55 ■ “Quartus II Software Support” on page 9–60 ■ “Design Security” on page 9–61 © 2012 Altera Corporation. All rights reserved. ALTERA, ARRIA, CYCLONE, HARDCOPY, MAX, MEGACORE, NIOS, QUARTUS and STRATIX are Reg. U.S.
    [Show full text]