1 / 21

Example of Multilevel representation of ammunition

Example of Multilevel representation of ammunition. D Mott v2. Some types of multilevel representation. Adding constraints need a flight -> need a helicopter -> need a helicopter with a capacity of X -> need helicopter 26 A Type is Instantiated

cate
Download Presentation

Example of Multilevel representation of ammunition

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. Example of Multilevel representation of ammunition D Mott v2

  2. Some types of multilevel representation • Adding constraints • need a flight -> need a helicopter -> need a helicopter with a capacity of X -> need helicopter 26 • A Type is Instantiated • We need a Helicopter of type T, we will allocate H123 • Aggregation • a request is bundled up into larger requests, eg logistics • More complex mappings • High level wants a hammer, low level only has a brick, needs a functional mapping • …

  3. Logistics Organisations • HQ Log • responsible for logistics for all BNs in the Division • BN1 Log • responsible for logistics for all tasks undertaken by BN1 • BN2 Log • responsible for logistics for all tasks undertaken by BN2

  4. Basic Concepts • Tasks (eg SECURE Enemy Bank) require field artillery • different types for different tasks • may be geographically dispersed • Field Artillery fires “rounds” of ammunition • different types for different FAs • number required depends on the task? • Ammunition comes in a “crate”: • contains a fixed number of rounds of a certain type • has a weight and a 3D dimension • Crates may be aggregated into “containers” • has a maximum weight capacity • has spatial dimensions • Logistics organisations deliver ammunition • as crates • as containers

  5. Visualisation

  6. Aggregation Logic … … … set of mixed crates according to: up to maximum weight (easy) OR spatial packing constraints (complex) N rounds per crate, where N is fixed per type of round & crate.

  7. BN Log planning • Aggregate all requests from BN and send to HQ Log • Unpack container from HQ Log into crates for Tasks • Take to BNx DropOff Task 1 … To HQ Log Task 2 … Follow packing constraints (max wt, round up to complete crate) Consolidated Request Use packing heuristics to minimise no of crates

  8. HQ Log Planning • Aggregate all BN requests into container(s) • Get from Suppliers • Deliver to Division DropOff Follow packing constraints (max wt, or spatial dimensions) Consolidated Request from BN1 Use packing heuristics to minimise no of containers, distance travelled etc Consolidated Request from BN2

  9. Locations BN1 Log BN1 Tasks HQ Log BN2 Tasks BN2 Log

  10. Views of the ammunition • Task is supported by Field Artillery • needs N rounds • VIEW as rounds • BN Log must supply all of its tasks • needs N crates of type X, … M crates of type Y • VIEW as consolidated sets of crates • HQ Log must supply all of the battalions • needs N containers, each containing a mixed set of crates • VIEW ascontainers

  11. Levels of aggregation of an entity container [HQ Log] • This reflects the containment of resource requests inside each other: • request for round is satisfied by request for crate • request for create is satisfied by consolidated request • consolidated request is satisfied by container request consolidated request [BNx Log] crate [BNx Log] round [Task]

  12. Rationale • We must retain the containment links between the resource requests at various levels • The rationale for the containment must also be recorded: • resource request X is present because: • resource request Y… • packing constraints • packing heuristics

  13. Some logical constraints • the crate must hold things of the correct type • call this the “content type” of the crate • there must be no more than a maximum number of items in the crate • call this the “maximum content” of the crate

  14. Correct type - logic version 1 • pick any thing from the crate and it will be of the correct “content type” if ( the crate C holds the thing S ) and ( the crate C has the value A as content type ) then ( the thing S has the value A as type ) .

  15. Visualisation IF Existing Structure THEN ADD New Structure

  16. Correct type - logic version 2 • it cannot be that there is something in the crate of the wrong type if ( the crate C holds the thing S ) and ( the thing S has the value ST as type ) and ( the crate C has the value A as content type ) and ( the value ST # the value A ) then ( there is an inconsistency ) .

  17. Visualisation

  18. Maximum number in a crate - 1 • if you count the number of items in a crate then that count will be less than the maximum content if ( the thing C is a crate ) and ( the set S includes every thing T where ( the crate C holds the thing T ) ) and ( the set S has N members ) and ( the crate C has the value Max as maximum content ) then ( the value N <= the value Max ) . Sets not yet available in CE

  19. Visualisation

  20. Maximum number in a crate - 2 • it cannot be that there are more than the maximum number of items in a crate if ( the thing C is a crate ) and ( the set S includes every thing T where ( the crate C holds the thing T ) ) and ( the set S has N members ) and ( the crate C has the value Max as maximum content ) and ( the value N > the value Max ) then ( there is an inconsistency ) .

  21. Visualisation

More Related