1 / 8

Term Project D1 Reviews L3: 130228 Class

High Concept: drag-and-drop plug-and-play modular options to deal with an ever surprising situational environment . Mental Preparation (Operational Story): you live in the operational environment, you see a variety of surprises, you configure an appropriate response for each.

howe
Download Presentation

Term Project D1 Reviews L3: 130228 Class

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. High Concept:drag-and-drop plug-and-play modular options to deal with an ever surprising situational environment . Mental Preparation (Operational Story):you live in the operational environment, you see a variety of surprises, you configure an appropriate response for each. Term Project D1 ReviewsL3: 130228 Class Agile systems have effective situational response under: Unpredictability: unknowable situations Uncertainty: randomness with unknowable probabilities Risk: randomness with knowable probabilities Variation: knowable variables and variance range

  2. FIRST Student Robotics Club – WikiSpeed InspiredDouglas Gault • What does it do? Uses college & high school students in scrum-like process to produce a competitive competition-specific robot in 1.5 months, each year, with: • uncertain student availability during a project • uncertain mentor availability during a project • unpredictable mix of new and experienced students • unpredictable competition requirements until 30 days (?) before project start • risk that competition requirements need other expertise How does it do that? Example: Team WikiSpeed Creates: modular architecture for independent design/build subsystem iterations? Creates: tasks, tests, sprints, novice/experienced team pairs? Improves: overall process effectiveness across multiple project-years? Migration: of this team process to something suitable for other project teams? Modifies: tests, available mentors, subject matter expertise? Corrects: test-failing build iterations, design and requirements understanding? Variation: in time, commitment, and ability of students? Expansion/contraction: in number of students for a yearly project? Reconfigures: team pairs on tasks, full-build prototypes?

  3. Drone Net Package DeliveryTim Adams • What does it do? Delivers small packages reliably in hub and spoke route system, with • uncertain package carriers (impaired at hub, impaired in flight) • uncertain hub availability (overloaded, power outage) • uncertain spoke viability (temporarily unusable rout) • unpredictable entry and exit of end-points (subscribers, one-timers) • risk: (drone disappearances on routs, dead hubs) How does it do that? (Examples: Internet, UPS, Fed-X, John Robb’s Dronet) Creates: what? Improves: what? Migration: (infrastructure evolves to) what? Modifies: (modules evolve to) what capability? Corrects : what? Variation: in what? Expansion: in what? Reconfigures: what?

  4. Agile Drone Net Infrastructure • John Robb talks about the standards required for building the DRONENET: • Simple rules for drone weight, dimensions, service ceiling, and speed. • Simple rules for battery swap and recharging (from battery type, dimension, etc.). • Simple rules for package containers. • Simple rules for the dimensions and capabilities of landing pads. • Decentralized database and transaction system for coordinating the network. • Rules for announcing a landing pad (information from GPS location and services provided) to the network. • Rules for announcing a drone to the network (from altitude to speed to direction to destination). • Cargo announcement to the network, weight, and routing (think: DNS routing). • A simple system for allocating costs and benefits (a commercial overlay). This commercial system should handle everything from the costs of recharging a drone and/or swapping a battery to drone use.

  5. Agile Configuration of Dual Mission SystemsBen Brown • What does it do? Configures payloads for Strategic Missions and Targets of Opportunity missions, with • uncertain rapidity of delivery time or TOO response time? • uncertain Strategic Mission needs or TOO capability needs? • unpredictable capabilities and timing on TOO response? • what else/instead? How does it do that? Do what: configure in-depot or in-flight? Creates: dual capability in one aircraft, dual data transmission capability? Improves: range of TOO missions possible per strategic mission package? Migration: (infrastructure evolves to) in-flight TOO mission configuration? Modifies: (modules evolve to) what capability? Corrects: what? Variation: in range of required geographies? Expansion: in mission package aircraft-space required? Reconfigures: Processors for Strategic and TOO mission capability?

  6. Agile HDL MaintenanceRandy Hosier • What does it do? Reduces time & increases quality by using specialty-focused teams across multiple aircraft, and order-stacking for each area before closeout. • uncertainty of stress/corrosion/structure condition until torn down & inspected • uncertainty of when an aircraft area will be ready for order-stacked work • uncertainty of specialty-team scheduling rate and conflicts • unpredictability of refurb increase due to older aircraft life extension • risk of competition under same pressure developing more competitive process How does it do that? Creates: task ordered stacks Improves: specialty-team efficiency? Migrates: to other aircraft platforms? Modifies: expertise on specialty teams? Corrects: mis-ordered task stacks? Variation: stress/corrosion/structural work? Expands: team size and number? Reconfigures: task ordered stacks?

  7. RRS Principles for: HDL Maintenance System • Self-Contained Units (Encapsulated Modules) • Teardown & inspection team • Electrician team • Test team • Supervisor team • Mechanical team • Installer team • Close out team • Supply team • Order-stacked tasks • Evolving Standards (Infrastructure/Framework) • Order stacking procedure • Team handoff rules • DOD / FAA standards • Union rules • Unit Redundancy & Diversity • Multiple specialty teams • ? • Plug Compatibility (Facilitated Interfacing) • Ordered-stack facilitates team handoff • ? Scalable Reusable • Facilitated Reuse • Teams move aircraft to aircraft on specialty tasks • ? • Elastic Capacity (Scalable) • Team members added /removed as needed • Teams in each specialty modulated as needed • ? Reconfigurable • Distributed Control & Information (Decentralization) • ? • Flat Interaction (Peer-Peer, Non-Hierarchical) • Daily meeting with all teams involved facilitates communication and schedule adjustment • ? • Deferred Commitment • Don’t close up until area is finished • ? • Self Organization • ?

  8. Understand the Dynamics of the Environment

More Related