Table of Contents

  • i Engineering Design
  • 2 Terminology
    • 2.1 Constraint
    • 2.2 Interoperability
    • 2.3 Standards
    • 2.4 Codes
    • 2.v Technical Regulation
  • 3 Organizations that Define Standards, Codes, and Regulations
  • 4 References/Resources
  • 5 Program Constraints
    • v.i Allocated Requirements / System Resource Reports
      • v.1.1 Ability Shared Resources Report / Resource allotment
      • 5.1.2 Mass Shared Resources Written report / Allocation
      • five.one.three Other Shared Resource Written report(s) / Allocation
    • 5.two Cost
    • 5.3 Schedule
    • 5.four Interface Definition
  • six Verification & Validation Exam Plan
  • 7 Engineering Standards, Codes, and Regulations
  • eight Program Standards, Codes, and Regulations
      • 8.0.i Applicable Technology Standards, Codes, and Regulations
      • 8.0.2 Ecology, Wellness, and Safety (EH&S) Standards, Codes, and Regulations
        • viii.0.2.1 Disposal of Hazardous Waste including Electronic and Solar Cells
        • 8.0.two.2 Electrical Condom
        • viii.0.2.3 Safe Method for Testing, Storage, and Disposal of LiIon batteries
  • nine Real World Constraints Exercise

Engineering Design

Engineering design is a process of devising a system, component, or process to meet desired needs and specifications within constraints. It is an iterative, creative, controlling procedure in which the bones sciences, mathematics, and engineering sciences are applied to convert resources into solutions. Engineering science blueprint involves identifying opportunities, developing requirements, performing assay and synthesis, generating multiple solutions, evaluating solutions against requirements, because risks, and making trade- offs, for the purpose of obtaining a high-quality solution nether the given circumstances. For illustrative purposes only, examples of possible constraints include accessibility, aesthetics, codes, constructability, price, ergonomics, extensibility, functionality, interoperability, legal considerations, maintainability, manufacturability, marketability, policy, regulations, schedule, standards, sustainability, or usability.

– Abet Glossary F'18

Terminology

Constraint

A constraint is a status that must be met. Sometimes a constraint is dictated by external factors such as orbital mechanics (schedule) or the state of technology; sometimes constraints are the result of the overall upkeep surround. Information technology is of import to document the constraints and assumptions along with the mission objectives. [i]

In this definition we run into a clear delineation between constraints (cost and schedule) and performance (mission objectives). [iii]

Constraints may also take the form of compliance with standards, codes, and technical regulations. These evolve from the concept of interoperability.

Interoperability

Interoperability is a characteristic of a product or system, whose interfaces are completely understood, to piece of work with other products or systems, nowadays or hereafter, in either implementation or access, without whatever restrictions. [4]

Within the context of the class we volition limit the scope of interoperability to its original definition; in other words, information technology and systems engineering applications. A broader definition takes into account social, political, and organizational factors that impact system to arrangement performance.

In the Figure 1 nosotros come across the term "interoperability" within the context of "compatibility" and "de facto standard. Historically, interoperability is the codification of a de facto standard by a recognized professional organisation, like the IEEE .

Figure 1. Interoperability

With respect to the Open Systems Interconnection model (OSI model) [5], interoperability may be nowadays at each layer.   Examples at higher layers include XML and SQL. At lower layers we accept ASCII and Unicode. At the hardware (concrete) layer we have series communication protocols like the I2C serial peripheral interface (SPI), universal asynchronous receiver-transmitter (UART); all supported by the 3DoT board.

Standards

Standards provide a proven footing for establishing common technical requirements across a program or project to avoid incompatibilities [two] and may in some instances actually lower implementation cost.

This most mutual example of standards is in weights, measures, and monetary.

Codes

Laws that specify minimum standards to protect public safety and health such as codes for structure of buildings. Initially voluntary and consensus standards, later incorporated into codes. Codes which apply to product development and workmanship are included in the production specifications.

Technical Regulation

A technical regulation is a Regime document that defines product characteristics or their related processes and production methods, including the applicable authoritative provisions, with which compliance is mandatory. [7]

The difference between standards, codes, and technical regulations lies in compliance. While compliance with standards is voluntary, codes and technical regulations are past nature mandatory.

Organizations that Ascertain Standards, Codes, and Regulations

Standards Organizations

Following is a pocket-size representative sample of organizations that establish standards.

  • ASTM (American Society for Testing and Materials)
  • IEEE (Institute of Electrical and Electronics Engineers)
  • ASME (The American Society of Mechanical Engineers)
  • ANSI (American National Standards Institute)
  • NASA Standards
  • ISO (International Organization for Standardization)

Codes and Regulatory Organizations

Hither are two examples of organizations that establish codes and regulations.

  • United States Section of Justice Civil Rights Division, Americans with Inability Deed (ADA)
  • In Canada, national construction codes are published by the National Research Council of Canada.

References/Resources

ii) ibid, Department 4.two.2.five Technical Standards

3) ibid, Department 7.3.4 Design Standards

half dozen) Institute of Electrical and Electronics Engineers. IEEE Standard Computer Dictionary: A Compilation of IEEE Standard Computer Glossaries. New York, NY: 1990.

Program Constraints

From Constraints to Programmatic Requirements

A critical role of the blueprint process is an early on understanding of the overall real-world constraints placed on the plan. These constraints may come up from the customer "programmatic" or the implementing organization "institutional." The specific constraints applied to the programme are a subset of the constraints, standards, codes, and regulations nether which the customer or implementing organization operate. These constraints are typically not able to be changed based on trade off analyses. Once this subset is defined, they go programmatic requirements. Oncethese constraints are defined requirements tin can be further defined by establishing performance criteria. The performance is expressed as the quantitative part of the requirement to indicate how well each product function is expected to be accomplished. The rationale should exist kept up to date. Often the reason for the requirement is not obvious, and information technology may be lost if non recorded as the requirement is being documented. The reason may point to a constraint or concept.
This flow-downwardly of client and institutional constraints into requirements is illustrated in Figure 2.

Effigy 2. The catamenia-down of constraints into requirements

Equally part of your concluding report you will need to review and prove compliance with constraints on the project imposed past The Robot Visitor (i.e., CSULB) and Projection Stakeholders.

Project/Economic

Subcategories: Cost, Extensibility, Interoperability, Maintainability, Quality, Marketability, and Schedule

All 3DoT robots shall be constrained to a a Cost not to exceed $250.

All project Schedules shall be constrained to a completion date of Tuesday Dec 18, 2018. Project completion includes documentation and materials purchased past or loaned to the projection.

One of the Economic Factors affecting our robots are return rates. To demonstrate the durability and child friendliness of our robot a unproblematic drop test from ane.4 meter shall exist performed. The height is defined past the average height of an average 11 year sometime girl.

Extensibility is designed into the 3DoT lath by way of i 8-pivot 100 mil connector located on the front of the board and 2 viii-pivot 100 mil connectors located on the pinnacle of the board. By plugging shields into these connectors, the 3DoT board can support a diverse set of robots. All robots shall contain ane or more custom designed 3DoT shields. The 3DoT shield(southward) incorporating interface electronics betwixt the 3DoT board and sensors and/or actuators unique to the robot. Surface Mount Technology (SMT) will be employed unless a waiver for through-hole parts is granted.

Maintainability : Detach and Reassemble of the robot shall be constrained to less than 20 minutes (ten + 10 minutes). Disassembly: The 3Dot board is articulate of all other electronic and mechanical subassemblies. All electronic and mechanical subassemblies and associated connectors, sensors, and actuators including motors are asunder. A functional test of the robot is conducted subsequently reassembly to confirm its functionality. All project may reference a cable tree as well every bit an assembly diagram equally necessary. This requirement is demonstrated/verified on the last day of the schedule. Projects may request a waiver with justification.

Social and Ethical

Subcategories: Accessibility, Aesthetics, and Usability

Accessibility by the blind and Marketability of the robots shall exist implemented/enhanced by a speaker. The speaker shall generate sound effect consequent with the type of the robot. For example, the Goliath tank would make "track" sounds, the AT-ST sound effects would mimic their Star Wars ancestor.

To enhance Aesthetics, the robot shall be designed in such a way that there are no dangling or exposed wires. Compliance with this requirement, includes the use of keyed and conspicuously labeled connectors between all electronic and electromechanical components. Practise not utilise jumper wires; ribbon cables are preferred only not required. Loose wires should be independent using spaghetti tubing (not shrink tubing). For 3DoT projects consider using final blocks, 100 mil contact pins and headers, 2.0mm PH serial JST connectors , and barrel connectors. Handling Precaution for Terminal and Connector volition be in compliance with JST documentation.

To enhance Aesthetics , the class gene of a robot modeled on a real or fictitious robot shall be constrained past the original. For example, Goliath should be a scale model of the real Goliath 302 tank. Projects may request a waiver with justification.

Usability of the robots shall be enhanced by adding autonomous functions and/or past use of the Arxterra phone and control console application equally dictated past the assigned mission.

Manufacturability

Subcategories: Constructability, Size, Weight, and Power (Swap)

Constructability of 3DoT robots shall exist documented at the CDR and approved by the president of the TRC robot visitor. Constraints imposed by this requirement include the use of bushing or bearings in all moving and rotating parts. Interlocking Hinges with latching mechanism. No gaps greater than 1 millimeter, and immediate access to all external connectors (USB, switches).

Manufacturability of 3D printed robots shall be demonstrated by compliance with the 3/3/3 rule. Specifically, full print of a robot is constrained to nine hours, with no single print taking longer than 3 hours. Projects may asking a waiver with justification. This requirement is waived for 3D prints provided by the library's Innovation Space. In its place, all 3D prints provided by the library'due south Innovation Space should minimize the number of files to be printed. Justification should exist provided if more than one (1) file is required.

The Size of the electronics enclosure, shall exist constrained to be no greater than the 3DoT board, 3DoT shield(south), and associated mounting hardware.

Ability to all 3D robots shall be provided by the three.7V RCR123A battery included with the 3DoT board or use of the external battery 2.0mm PH series JST connector located on the 3DoT board. The RCR123A is a Lithium Polymer LiPo bombardment. All Safety regulations equally defined in Department 4.3 Hazards and Failure Assay of this document shall apply to the shipping, handling, storage, and disposal of LiPo batteries.

Power to all 3DoT robots shall exist provided by the three.7V 750 mA two.775Wh Li-Ion battery included with the 3DoT board or use of the external bombardment 2.0mm PH series JST connector located on the 3DoT lath. Compliance will exist provided in Section 3.5 Ability in the Final Blog Postal service. Measured electric current shall take a margin of five%. Contingency shall be based on measured current, plus margins associated with each line item, minus 750 mA with an assumed depth of belch of 80% grams (i.e., 600 mA).

Back of the envelope calculations and experiments shall be conducted to ready the bore of Power carrying wires. Follow the American Wire Gauge (AWG) standard when defining the diameter of power-carrying wires. This work to be completed and documented past the CDR.

Environmental Health and Prophylactic (EH&South) Standards

Subcategories: Ecology Standards, Sustainability, Toxic waste (Solar panels), Health and Safety, Ergonomics

All standards, codes, and regulations as divers in the "Engineering Standards and Constraints" Section of this document shall apply.

All Lithium (Li-ion, Li-polymer) batteries shall be purchased with and stored, when not in apply, in a fire and explosion proof bombardment pocketbook.

Robot Interoperabilty

All 3DoT robots shall comprise the 3DoT v9.05 or subsequently series of boards.

Software shall exist written in the Arduino De facto Standard scripting linguistic communication and/or using the GCC C++ programming language, which is implements the ISO C++ standard ( ISO/IEC 14882:1998 ) published in 1998, and the 2011 and 2014 revisions. Required exceptions to this standard can be found hither .

All 3DoT robots shall be in compliance with the 3DoT Command and Telemetry Packet specification.

All 3DoT robots shall be controlled via Bluetooth 4.0 in compliance with the Bluetooth Special Involvement Group (SIG) Standard (supersedes IEEE 802.15.ane).

Allocated Requirements / System Resource Reports

Allocated requirements, likewise known every bit resource reports, are written and tracked by the Arrangement Engineer. The types of resource reports are based on the project. For case, ability allocation/approximate for each subsystem module of a spacecraft would be of import, while a more than loose tracking for a toaster would be in club. Each resources should take a margin fastened to it based on the doubt in the guess. Information technology should also show contingency, where contingency is defined every bit the project allotment minus the approximate plus total margin. Project allocations shall be based on a model (dorsum-of-the-envelope, simulation, paradigm, etc.) or other rationality (e.g., similarity to a related product).

Power Shared Resources Report / Allocation

Section shows updated useable chapters of the power source selected for the project. Typically represented in a tabulated format, it should include an expected current drawn, measured current drawn, pct dubiousness, and margin for each resource consuming power. Lastly, information technology should comprise total expected current, total margins, project allocation, and contingency clearly showing the ability source selected will support the projection.

Mass Shared Resource Report / Allocation

This section is comparable to the previous power allocation section notwithstanding, defended to the updated mass of the project. Also in a tabulated format, it should incorporate the expected weight, measured weight, per centum uncertainty, and margin for each respective resource being used in the project. Lastly, it should contain total expected weight, total margins, projection allocation, and contingency.

Other Shared Resource Report(s) / Allocation

Any other resource tracked by the system engineer. For case, 3DoT projects using a 3D printer have an nine 60 minutes. (3/3/3) resource requirement that must exist tracked.

Cost

This section should contain an updated table listing all of items purchased for the project including prototype price, parts and implementation, PCB manufacturing price etc. Like all allocated resources (see Mass and Power), this chart should comprise the expected toll, actual cost, pct uncertainty, and margin for each item listed in the table. Lastly, it should evidence the full expected/final price, total margins, project allocation, and contingency.

Schedule

This section should contain an updated schedule, generated through programs like ProjectLibre or Microsoft Projection, showing the organization and subsystem tasks that accept been completed or are withal in progress. It is important to include the projection's critical path (visually representing the critical path in the schedule diagram is recommended).

Interface Definition

This section is an updated version of the Interface Matrix presented at the PDR and CDR. An additional section should discuss the Cablevision Tree (i.e. wire harness, wiring diagram, etc.) adult in concert with the Eastward&C and MFG showing how the wires, cables, and connectors were integrated into the final product.

If your project has includes and Interface Control Document (ICD), it would get here: meridian level explanation of MST advice, E&C connections, MFG mating and fastening → to be covered in detail afterward in the presentation during respective sections.

Verification & Validation Test Plan

Once an acceptable design solution has been selected from amidst the various alternative designs and documented in a technical data package, the design solution must adjacent be verified against the organization requirements and constraints.

The verification must show that the design solution definition:

  • Is realizable inside the constraints imposed on the technical effort;
  • Has specified requirements that are stated in acceptable statements and accept bidirectional traceability with the derived technical requirements, technical requirements, and stakeholder expectations; and
  • Has decisions and assumptions made in forming the solution consistent with its set of derived technical requirements, separately allocated technical requirements, and identified system product and service constraints.

Boosted Reading and Resource:

  1. Arxterra / Getting Started / Systems Engineering / Missions, Systems and Exam Timeline
  2. Week #7 – Product Verification & Firmware Setup
  3. Week #eight – Product Validation & Cablevision Tree/Cablevision Routing Diagram
  4. Sample Verification and Validation Plans

In your concluding report begin by presenting your strategy for verifying that your blueprint meets design requirements and how y'all will validate (i.e., the mission plan) that you lot congenital the right product for the mission. The next section should present your project'due south verification test programme as an overview/summary level.  The Verification and Validation Test Plan should exist uploaded to BeachBoard and provided in printed course at the day of the mission.

Engineering Standards, Codes, and Regulations

Standards provide a proven footing for establishing mutual technical requirements across a program or project to avoid incompatibilities and ensure that at least minimum requirements are met. [2]

The most common example of standards is in weights, measures, and budgetary.

Standards provide a proven basis for establishing common technical requirements across a program or project to avoid incompatibilities and ensure that at least minimum requirements are met.

Standards in common employ, such every bit weights and measures, tin upshot in lower implementation cost too as costs for inspection, common supplies, etc. Typically, standards (and specifications) are used throughout the production life cycle to establish design requirements and margins, materials and procedure specifications, test methods, and interface specifications.

Standards are used as requirements (and guidelines) for design, fabrication, verification, validation, acceptance, operations, and maintenance.

Standards are generated from many sources, leading to confusion, contradiction, and a demand for prioritization. Here is one manner standards may be prioritized.

  1. Standards mandated by law (eastward.g., ecology standards)
  2. National or international voluntary consensus standards recognized by manufacture,
  3. Government standards
  4. Customer and Institutional policy directives, and technical standards.

Depending on the specific domain or discipline, there may be industry and Middle-specific standards that must be followed, particularly when designing hardware. This can exist evident in the design of a mechanical part, where a mechanical computer-aided pattern packet selected to model the parts must accept the capability to meet specific standards, such as model accuracy, dimensioning and tolerancing, the power to create dissimilar geometries, and the adequacy to produce annotations describing how to build and inspect the part. However, these same issues must exist considered regardless of the product. [three]

To larn more about standards read NASA System Engineering Handbook, Sections 4.2.two.5 Technical Standards and vii.3.iv Design Standards, of which the to a higher place is an abridged version.

Program Standards, Codes, and Regulations

As part of your final report you volition demand to review and prove compliance with standards, codes, and regulations adopted past The Robot Company (i.e., CSULB) and Project Stakeholders. Specifically include Academy and applicable environmental, wellness, and safety standards and those safety standards specifically associated with the product (eastward.one thousand., Children's Toys).

Applicable Engineering Standards, Codes, and Regulations

  1. IEEE 29148-2018 – ISO/IEC/IEEE Approved Draft International Standard – Systems and Software Engineering — Life Cycle Processes –Requirements Engineering.
  2. NASA/SP-2007-6105 Rev1 – Systems Engineering Handbook
  3. Bluetooth Special Interest Group (SIG) Standard (supersedes IEEE 802.15.1)
  4. C++ standard (ISO/IEC 14882:1998)
  5. Federal Communications Commission (FCC) Relevant standards for a product implementing a 2.4GHz radio, FCC Intentional Radiators (Radio) Role 15C, and Unintentional Radiators FCC Office 15B for CPU, memories etc.
  6. NXP Semiconductor, UM10204, I2C-autobus specification and user manual.
  7. ATmega16U4/ATmega32U4, eight-bit Microcontroller with xvi/32K bytes of Isp Flash and USB Controller datasheet department datasheet, Department 18, USART.
  8. USB 2.0 Specification released on April 27, 2000, usb_20_20180904.zip
  9. Motorola's SPI Block Guide V03.06

Environmental, Health, and Safety (EH&S) Standards, Codes, and Regulations

CSULB College of Engineering (COE) Rubber Resource.  Start your search for applicable CSULB COE Safety Standards and Procedures here . Delight review and acknowledge if any safety issues equally defined by the COE applicable to your project.For example, the closest safety constraint for a linear actuator is for apply of the Hydraulic Press located in the Engineering science Technology (ET) Building Lab. Here is a link to the Hydraulic Press Safety document.

CSULB Environmental Wellness & Prophylactic (EH&S)

IEEE National Electrical Safety Lawmaking (NESC)

NCEES Central Handbook (Iron) Reference Handbook

ASTM F963-17 , The Standard Consumer Safety Specification for Toy Prophylactic, is a comprehensive standard addressing numerous hazards that have been identified with toys. In 2008, the Consumer Product Safety Improvement Deed of 2008 (CPSIA) mandated that the voluntary toy safety standard in effect at that time become a nationwide mandatory children's product safe dominion.

Disposal of Hazardous Waste matter including Electronic and Solar Cells

CSULB Physical Planning & Facilities Management (PPFM) Ecology Compliance Electronic Waste Handling and Disposal Procedures. These procedures shall be followed for the disposal of all batteries.

Electrical Safety

The National Institute for Occupational Safety and Health (NIOSH) Electrical Safety [1998][page 8] Worker Deaths by Electrocution; A Summary of NIOSH Surveillance and Investigative Findings. Ohio: U.S. Health and Human Services.

Current Level (Milliamperes) Probable Effect on Homo Body
1 mA Perception level. Slight tingling sensation. All the same dangerous under certain weather condition.
5 mA Slight daze felt; not painful but agonizing. Average private can allow go. However, strong involuntary reactions to shocks in this range may lead to injuries.
half dozen mA−sixteen mA Painful stupor, begin to lose muscular control. Commonly referred to as the freezing current or "let-become" range.
17 mA−99 mA Extreme pain, respiratory arrest, severe muscular contractions. Private cannot let go. Death is possible.
100 mA−2,000 mA Ventricular fibrillation (uneven, uncoordinated pumping of the heart.) Muscular contraction and nervus impairment begins to occur. Death is probable.
> ii,000 mA Cardiac arrest, internal organ damage, and severe burns. Decease is probable.

Safe Method for Testing, Storage, and Disposal of LiIon batteries

Personal email communication dated May ix, 2018, to Gary Loma, Adjunct Professor, COE Department of Electrical Engineering, from Michael R. Kitahara, CSP, ARM-P, CHMM, Ecology Health & Safety, California State University, Long Embankment

  1. Condom Method for Testing  – Most industry maintenance guidelines estimate the typical life of a LiIon battery to be 2-3 years, even if they are unused during this period.   Given that you lot have a drove that are age-uncertain, in addition to the potential for explosion and/or fires that may upshot from recharging old, depleted or malfunctioning batteries, we cannot advocate a "safe" method of testing to come across if the batteries can still be charged.  Our recommendation would be to start from scratch and physically date each bombardment with a Sharpie pen.  We do this when opening peroxide containers (ane year storage limit as crystals that form on the edge of the container combined with the friction of opening the cap tin can cause an explosion).
  2. Safe storage – Once you marking the age on the batteries, they should be stored in a mode where the terminals do not make contact.  You can physically isolate the terminals (e.g.  by placing record or other bulwark on them) or isolate the batteries themselves through a storage container (eastward.chiliad. a inexpensive, plastic angling lure or jewelry storage box such as the 1 below would suffice).
  3. Battery disposal – This 1 is the easiest to answer.  Tape the terminals of the batteries to be discarded with duct or electrical record.  If you take a few, they can be dropped off in the recycling container in ECS-662.  If you have many, call or e-mail me and nosotros can pick it them at your location.

Other conditions for storing LiIon batteries:

  1. Barrier protection – a dissever, isolated storage room would be best, or if this is not practical, a cabinet or closet.  In that location should be appropriate signage, e.g. "Lithium Battery Storage – Explosion Chance" or similar warning.
  2. Periodic Maintenance Checks – Storage containers should exist checked regularly (at least once a semester) for battery condition.
  3. Class "D" Fire Extinguisher – Obtaining one is a corking idea.  This would be purchased through your department.

EH&Due south recommends post-obit industry guidelines by disposing LiIon batteries after their useful life, typically 2-iii years.  Storing LiIon batteries on campus later on this catamenia would crave approval of the campus Chance Director, Felicia Waynick, cc:ed here

Real World Constraints Do

Discuss how constraints, standards, and regulations may take prevented or contributed to the following technology mistakes.

The Dumbest Mistakes In Space Exploration

10. Russian Polues spacecraft

9. Apollo TV photographic camera – unlike standards

8. Ariane 5

7. ESA Schiaparelli Lander

6. Russian Venera Spacecraft

5. NASA/JPL Mars Climate Orbiter – unlike standards

iv. NASA Hubble Space Telescope

three. Robert Goddard Pendulum Rocket

2. Russian Proton Rocket

1. Infinite Shuttle Programme – over constrained