COMDTINST 5200.38
(e) Data Management
(f) Elevating requests for release through the FAM to the M&S Advisory Council for
adjudication by the Executive Secretariat.
(g) Representation
(h) Security
(i) Reuse
(2) Update the Coast Guard M&S Repository with appropriate information about the M&S under
their management.
(3) When in doubt about the application of this policy, bring exceptions or questions through the
appropriate FAM for adjudication or clarification by the M&S Advisory Council.
(4) Use sound professional judgment when accomplishing the activities in paragraphs 8.f.(1).
These activities are generally accepted as being critical success factors for a M&S project to
meet its objectives. However, it is clear that the extent of the requirements of paragraph
8.f.(1) will vary for different M&S. Procedures may be tailored as appropriate to satisfy the
intentions of the policy consistent with common sense, sound business management and
accepted industry practices and the time-sensitive nature of the requirements themselves. In
addition, tailoring may be applied differently to the various phases of the M&S development
process. Some examples:
(a) The depth of analysis involved with the V&V of an established legacy or commercial off-
the-shelf (COTS) M&S would be different from the development of a new M&S. In the
case of the legacy or COTS M&S, the M&S PM could leverage the existing V&V
information or commercial acceptance.
(b) The extent of a life-cycle management plan for a new development M&S that will be
supporting a multi-year major acquisition from concept development through deployment
will be greater than the informal planning done for a simple spreadsheet M&S used to set
performance goals.
(c) The formality and requirements of configuration management for an M&S, which is
centrally managed and distributed to multiple users is much greater than the informal CM
processes for a M&S developed in a commercial off-the-shelf product and used by only a
few users.
8
Previous Page
