Information Technology Reference
In-Depth Information
process description
generates an Air Task order. This is an application
with numbered missions and each new mission
is entered on a new line. The line number is the
mission number, by which the new mission is
referenced in the Air Force.
Upon receiving the Air Task the operational
unit performs the mission and reports it on the mis-
sion report format and sends it to the Operational
Command that after due analysis, sends it back
to the Chief of Air Force Chief of Staff Cabinet.
Next, the mission administrator calculates the
mission fee that the requester has to pay. Based on
existing Memorandum of Agreement or aircraft
hour of flight cost, he finds the amount due. Then,
he writes down the amount in the mission report
and sends it the finance directorate.
Upon receiving mission report, the finance
directorate issues a mission card on which are
mentioned the mission number, the commence-
ment date, the organization name, the mission date,
the departure and arrival locations, and the postal
address and prepares an invoice to the requester
for payment. Payments have to be performed by
bank transfer.
As soon as the payment is received the receipt is
sent to the mission requester by postal mail or fax.
Every organization can issue a mission request for
the Air Force. The mission request should be sent,
by letter, fax or postal mail to the Chief Of Staff
Cabinet. In that letter the requesting organization
has to mention its name, telephone number, postal
address, fiscal number (street, house number and
zip code), the type of mission, estimated time of
departure, estimated time of arrival, departure
location, arrival location, number of passenger
and/or cargo (number of packages, size and weight
and information about the passengers (birth date
and sex).
Upon receiving the request, one person
inside the Chief of Staff Cabinet, the one that
administrates mission requests, checks whether
the information provided is complete. If not, he
makes a telephone call to the sender in order to
complete the data.
If the information is complete, the person adds
an incoming mail number and the date, records
the letter in the IT system, and archives a copy. He
then checks for the existence of a memorandum
of understanding (MOU) between the Air Force
and the requesting that foresees the realization
of such missions. If the MOU does not exist he
checks the potential interest for the Air Force on
accomplishing the mission. In both cases, exist-
ing MOU and Air Force interest, he checks with
the Operational Command for availability of the
type of aircraft and crew for the requested date
and time.
Upon verification completeness, he prepares
a Memo and proposes to the Chief of Air Staff
whether this mission is to be performed.
If a mission request is denied (e.g., because lack
of aircraft availability or because the maximum
number of requested passengers or cargo exceeds
the aircraft capacity), the mission administrator
will send a letter in which he explains why the
applicant cannot receive the requested mission.
If the decision is affirmative, the mission de-
tails are sent to the Operational Command that
transaction and ontological
Models Application
The Mission Request Process is more complex
than the Volley. Under the perspective of the
Transaction Pattern the Volley has two main stages:
membership request and acceptance (which then
culminates with paying the first membership). The
in processing of the request is depending only in
one actor and all the actions are performed within
the same office. Therefore, a “request” is followed
by a “promise” (of processing the request) and
then a “state” that is “accepted” by the person
which wants to becoming a member and paying
the first membership fee.
The Mission Request is rather more complex.
The requestor issues the “Request” which, as
Search WWH ::
Custom Search