The transportation system capability model (TRANSCAP) : a mixed language development approach for an army deployment simulation. Page: 4 of 8
This article is part of the collection entitled: Office of Scientific & Technical Information Technical Reports and was provided to Digital Library by the UNT Libraries Government Documents Department.
The following text was automatically extracted from the image on this page using optical character recognition software:
TRANSCAP comprises four categories of
component modules: pre-processing, simulation,
post-processing, and inter-process communica-
" The pre-processing module includes the
Installation, Force & Scenario Manager and
the Scenario Report Manager. These pre-
processing modules manage data input, se-
lect the installation, specify pieces for de-
ployment, identify the method of deploy-
ment (e.g., convoy), and specify deployment
characteristics (e.g., the method used to
form the convoy groups).
" The simulation module contains the heart of
TRANSCAP - the discrete-event simula-
The two post-processing modules include the
Results Display Manager, which manages the
reporting and presentation of simulation results,
and the Export Manager, which exports results to
other simulation models.
* The Inter-process Communication Manager
enables interaction between the pre- and
post-processing modules and the simulation
The goal of TRANSCAP's discrete-event
simulation is detailed analysis. Because ELIST
can perform a high-level, aggregate analysis of
the operations at a fort, TRANSCAP was written
at the lowest possible level of data and process.
It was also written in an object-oriented pro-
gramming language to foster the greatest amount
of modularity and potential for reuse in future
The following are descriptions of the three
types of low-level data that TRANSCAP uses:
transportation and cargo, infrastructure, and re-
source. Transportation and cargo data are Level
6, which means that details are available for each
individual piece of cargo and transport, rather
than an aggregated data description based on
tonnage or category. Infrastructure data are the
most detailed type of data about quantity and
exact measurements of existing infrastructure.
For example, rather than using an aggregate ca-
pacity for all marshaling areas or rail yards, spe-
cific data for each are used. Resource data in-
clude information about such existing facility
resources as the quantity and location of each
truck loading ramp, rail end ramp, inspector,
mechanic, or tie-down crew.
There are three types of processes in de-
ployment simulations. TRANSCAP processes
are implemented in an object-oriented program-
ming language. These processes are at a low
level because of how transportation and cargo,
infrastructure, and resources are modeled. Trans-
portation and cargo are modeled at a low level
because there is a different class for each type of
cargo, transport, and locomotive. Also, each in-
dividual piece of cargo, transport, and locomo-
tive is instantiated as its own object - aggrega-
tion is not used. Processes simulating infra-
structure use are modeled at a low level because
the process times of the movements of trans-
ports, cargo, and locomotives are based on the
actual distances in the infrastructure that is trav-
ersed, rather than on stochastic (or random) dis-
tributions. Resources, like transportation and
cargo, are modeled at a low level because there
is a different class for each type of resource, and
each individual resource is instantiated as an
object. Also, each resource is assigned a specific
responsibility and a specific service time; multi-
ple processes are never represented by a general
Installation, Force & Scenario Manager
The first pre-processing module, called the
Installation, Force & Scenario Manager, encap-
sulates most of TRANSCAP's graphical user
interface (GUI). It manages the installations
available for simulation, the forces resident at the
installations, and the deployment scenarios. This
module allows the user to specify and generate
the scenarios needed for the simulation module.
For TRANSCAP's purposes, an installation
(e.g., Fort Stewart) consists of a resident force; a
modeled infrastructure consists of landmarks and
routes. A scenario is a description of a deploy-
ment, which includes the installation from which
the items are deployed, the items to be deployed,
and other deployment characteristics. A resident
force must exist to create an installation, and an
installation must exist to create a scenario.
If a desired installation does not exist in
TRANSCAP's database, it can be created in the
Installation, Force & Scenario Manager module.
Here’s what’s next.
This article can be searched. Note: Results may vary based on the legibility of text within the document.
Tools / Downloads
Get a copy of this page or view the extracted text.
Citing and Sharing
Basic information for referencing this web page. We also provide extended guidance on usage rights, references, copying or embedding.
Reference the current page of this Article.
Love, R. J.; Burke, J. F., Jr.; Macal, C. M.; Howard, D. L. & Jackson, J. The transportation system capability model (TRANSCAP) : a mixed language development approach for an army deployment simulation., article, June 2, 2000; Illinois. (digital.library.unt.edu/ark:/67531/metadc711362/m1/4/: accessed December 18, 2018), University of North Texas Libraries, Digital Library, digital.library.unt.edu; crediting UNT Libraries Government Documents Department.