17
Arcology Systems Engineering Considerations Rowin Andruscavage ENPM642 Spring 2003 Prof. John Baras

Arcology Systems Engineering Considerations Rowin Andruscavage ENPM642 Spring 2003 Prof. John Baras

Embed Size (px)

Citation preview

Page 1: Arcology Systems Engineering Considerations Rowin Andruscavage ENPM642 Spring 2003 Prof. John Baras

Arcology Systems Engineering

ConsiderationsRowin Andruscavage

ENPM642 Spring 2003

Prof. John Baras

Page 2: Arcology Systems Engineering Considerations Rowin Andruscavage ENPM642 Spring 2003 Prof. John Baras

Problem

• Much SE work done to improve transportation networks – congestion due to auto traffic, rail traffic, air traffic, port traffic, etc.

• Symptoms of underlying problems with fundamental city design

• Solution : apply SE methods to urban design & planning

Throw in some aesthetics…

ARCOLOGY

Page 3: Arcology Systems Engineering Considerations Rowin Andruscavage ENPM642 Spring 2003 Prof. John Baras

Systems Engineering Approach

• Goals & Use Cases

• Structural Model

• Behavioral Model

• System Requirements Allocation

• Specifications

• Tradeoff Analysis

• Optimization Criteria

• Problem Formulation

• Pareto Optimal Curves

Page 4: Arcology Systems Engineering Considerations Rowin Andruscavage ENPM642 Spring 2003 Prof. John Baras

Goals & Use Cases – The Sims Example

Page 5: Arcology Systems Engineering Considerations Rowin Andruscavage ENPM642 Spring 2003 Prof. John Baras

Goals & Use Cases

Cargo

Living Quarters

Feed

Work

Sleep

Maintenance

Travel

Entertain

Individual

Industry

Page 6: Arcology Systems Engineering Considerations Rowin Andruscavage ENPM642 Spring 2003 Prof. John Baras

System StructureReactionEngine

LeafCell

ResourceEngine

TransportationInfrastructure

Cell

Resources::Resource

Environment

Manages

1

1

Contains

1

*

1 *

Check Inputs

*

Request Resources

*

1

1

1

1

Composedof

1

*

Page 7: Arcology Systems Engineering Considerations Rowin Andruscavage ENPM642 Spring 2003 Prof. John Baras

System StructureExample

Household

GeneralHabitat::LeafCellCity

Industry

World

Individual

Region

GeneralHabitat::Cell

Nation

Community

1

*

1

*

0,1 *

1

*

1

*

1

*

1

*

1

*

Page 8: Arcology Systems Engineering Considerations Rowin Andruscavage ENPM642 Spring 2003 Prof. John Baras

System BehaviorLive

Sleep

Feed

Entertain

Maintenance

Travel

Work

/evWakeup();

/evFeed();/evFeed();

/evSleep();

OutputResourcesInputResources

Combustion

GeneralHabitat::Resources::AirPollution

GeneralHabitat::Resources::Heat

GeneralHabitat::Resources::Petroleu

GeneralHabitat::Resources::Air11

1

1

1

1

1

1

Page 9: Arcology Systems Engineering Considerations Rowin Andruscavage ENPM642 Spring 2003 Prof. John Baras

System RequirementsArcology Primitive Requirements1.      Attend to basic occupant needs defined in the Individual use

cases described in Live.1.1.   Provisions (Feed)1.1.1.      Food1.1.2.      Water1.1.3.      Other consumables (vitamins, nutrients, etc.)1.2.   Indirect assets & qualities1.2.1.      Shelter, security (Sleep)1.2.2.      Health, hygiene maintenance not covered by 1.1.3

(Maintenance)1.2.2.1.            Waste removal2.      Self-sufficiency & sustainability (Work)2.1.   Extract required resources from environment2.2.   Extract labor from occupants3.      Improve quality of life for occupants (Entertain)3.1.   Education3.2.   Entertainment3.3.   Social interaction

Arcology Derived Requirements1.      Transformations of resources1.1.   Fuel to Waste - byproducts of Arcology Requirements 11.2.   Construction / deconstruction mechanism - resulting from

2.22.      Accounting & transportation mechanism for resources2.1.   Solid - Arcology Requirements 1.12.2.   Liquid - Arcology Requirements 1.12.3.   Gaseous - Arcology Requirements 1.12.4.   Information - Arcology Requirements 3.1,3.22.5.   Monetary credits - intermediary between exchanges and

transformations.3.      Transportation mechanism for resources & occupants in

order to satisfy all of the above (Travel)

Page 10: Arcology Systems Engineering Considerations Rowin Andruscavage ENPM642 Spring 2003 Prof. John Baras

System SpecificationsFor Arcology Primitive Requirements1.      Attend to basic occupant needs defined in the Individual use

cases described in Live.1.1.   Provisions1.1.1.      Food : > 1.77 kg per diem1.1.2.      Water : > 2.3 kg per diem1.1.3.      Other consumables (vitamins, nutrients, etc.)1.2.   Indirect assets & qualities1.2.1.      Shelter, security : distribution of 5 - 10 hours of sleep,

personal living quarters with > 37 m2 of personal living space.1.2.2.      Health, hygiene maintenance not covered by 1.1.3 – timely

delivery of emergency supplies & services.1.2.2.1.            Waste removal – roughly equivalent to total of

Provisions.2.      Self-sufficiency & sustainability 2.1.   Extract required resources from environment – varies, should

balance with environmental production rates, if known.2.2.   Extract labor from occupants – a distribution of around 1/3 of

the daily cycle. Provide > 19 m2 of work space.3.      Improve quality of life for occupants : continually increase

amount of leftover time dedicated to the following:3.1.   Education3.2.   Entertainment3.3.   Social interaction

For Arcology Derived Requirements1.      Transformations of resources1.1.   Fuel to Waste – roughly 1 to 1 conversion factor by

weight.1.2.   Construction / deconstruction mechanism – 2.      Accounting & transportation mechanism for resources

– Conversion, creation, consumption of each class of resource.

3.      Transportation mechanism for resources & occupants –

3.1.   Quantify measures of effectiveness – cost, latency, throughput, efficiency

Page 11: Arcology Systems Engineering Considerations Rowin Andruscavage ENPM642 Spring 2003 Prof. John Baras

Tradeoff Analysis

• Transportation network design for resource distribution via mass transit

• Each node has unique resources that must be distributed to other nodes

• Hub nodes are proportionally larger both in resource pools and capacity

• Multi-Criteria optimization:– max Profit (revenues – operating

costs)– max coverage (min unserved

units)– min change to current fleet size

Hubnode

node node

Page 12: Arcology Systems Engineering Considerations Rowin Andruscavage ENPM642 Spring 2003 Prof. John Baras

LP Formulation

Constructed as an inventory management problem:

• 4 main sets of variables:

• P[tijk] : people from node i going to node j at time t with final destination k

• F[tsij] : flights of type s from node i going to node j at time t

• PP[tik] : pool of people at node i at time t whose destination is node k

• AP[tsi] : pool of aircraft of type s at node i at time t

AP

AP

APNode 1

Node 2

Node 3p12 p21

p23

p32

p13

p31

Page 13: Arcology Systems Engineering Considerations Rowin Andruscavage ENPM642 Spring 2003 Prof. John Baras

Pareto Optimal Curves- Unserved units vs. Deviation from fleet size

Page 14: Arcology Systems Engineering Considerations Rowin Andruscavage ENPM642 Spring 2003 Prof. John Baras

Pareto Optimal Curves- Profit vs. Deviations from fleet size

Page 15: Arcology Systems Engineering Considerations Rowin Andruscavage ENPM642 Spring 2003 Prof. John Baras

Pareto Optimal Curves- Profit vs. Unserved units

Page 16: Arcology Systems Engineering Considerations Rowin Andruscavage ENPM642 Spring 2003 Prof. John Baras

Analysis & Conclusions

• Tradeoff curves are a bit too linear to be interesting: need to tweak inputs to find more complex regions

• Need to really tweak inputs in order to get non-trivial results: optimization criteria not strongly opposed to each other

• Useful for finding slope of coverage line, allowing tradeoff between cost and maximum coverage, stable fleet size.

Page 17: Arcology Systems Engineering Considerations Rowin Andruscavage ENPM642 Spring 2003 Prof. John Baras

Future Work,Questions & Discussion

• Design of Experiments parametric analysis of model inputs for preliminary design.

• Verification, Validation