Encl (1) to COMDTINST 5231.2
15 MAY 1988
FORMAT FOR AIS NOTIFICATION OR (PRELIMINARY) AIS PROPOSAL
(1) NAME. Provide AIS name and acronym (if applicable).
(2) PURCHASE COST. Estimate cost for system purchase. The term "purchase" means the total
expected value of a contract(s) or purchase(s) required to implement the system. For multi-
year contracts the full potential value of the contract must be used.
(3) OBJECTIVE. A definition of the objective of the AIS application, including a description of
the problem to be solved.
(4) CONCEPT OF OPERATION. A description of how the AIS will accomplish its objective.
That is, what functions will be performed, including a concept of operation along with any
communication requirements. Specify the date when system is expected to be operational.
(5) BENEFIT/COSTS. A summary of expected life-cycle costs and benefits, including the
effectiveness and/or efficiency improvements expected from the new AIS. The system life
will be assumed to be five years unless a shorter or longer life-cycle can be justified.
(6) SYSTEM RESOURCE REQUIREMENTS. A description of the minimum user hardware,
software and data communications requirements (e.g., hard disk storage requirements,
memory requirements, software licenses needed, planned means of connecting to
communications systems, etc.). Determine whether or not the application will fit on target
hardware and any upgrades required. This step requires coordination with field managers and
IRM staffs to verify existing systems can support additional requirements. The mere
presence of Standard Terminal equipment does not ensure such capacity. Commandant (G-
TIS) will normally assist with this determination if requested.
Previous Page
