Validation of MODES,
Abstract
Central to any validation of MODES are the principal requirements under which it was designed and constructed: (1) MODES should support crisis action deployment planning; (2) MODES should aid in the very early part of the crisis action planning process; (3) MODES should provide useful information in two to four hours; and (4) MODES should address questions concerning gross transportation feasibility among alternative courses of action. A comprehension understanding of these design criteria is essential in developing a reasonable validation process. MODES is not a deliberate planning tool. It was not designed to accomodate the level of detail which is possible in a deliberate planning cycle. It was designed to aid in making rapid go/nogo decisions at the first level in a hierarchical planning system. At its first level of use, it should help establish attainable EADs, LADs, and RDDs as well as provide recommendations on channel size, on mode, and on general routing for movement requirements. It should also provides gross feasibility assessments with regard to closure. MODES was not designed to provide the detail scheduling informatiuon currently generated in the deliberate planning process. The output of MODES should be viewed as one on the inputs to the detailed scheduling process.
Document Details
- Document Type
- Technical Report
- Publication Date
- Jan 01, 1986
- Accession Number
- ADA168239
Entities
People
- H. D. Ratliff
- John J. Jarvis
Organizations
- Georgia Tech