COMDTINST 5200.16
Once Category B software is certified for CG-wide use, additional certification by
LCCBs will not be required. Development and implementation of DOT-wide
systems is accomplished with the input of CG and other modal agencies. The CG
sponsor or POC for any DOT-wide system will work within the SWIII CCB process
to accommodate the requirements of the DOT system within the CG infrastructure.
(3) Category C - Applications and devices procured and /or developed and supported by
local IRM staffs. The LCCB will approve these requests and conduct the necessary
testing to ensure capability with the Standard Image. The LCCB that approves a
Category C request is solely responsible for supporting the resulting changes to the
systems and for any present and/or future impact on their users or applications. As
this ultimately becomes a local resource issue, the Commanding Officer should be
aware of such decisions. The LCCB must refer any ECP whose life cycle cost
exceeds K, or which requires a change to the standard image, to the SWIII CCB.
Enclosure (1) provides a detailed explanation of SWIII configuration control board
processes.
e. An LCCB or its chartering organization shall deny any user request if it determines
there is no valid business requirement for it. If the need is valid, LCCB approval will be
contingent on the requesting organization's funding any increase in recurring support. If
the requestor does not agree to funding, then the LCCB will not implement the request.
f. ECPs will be documented on the worksheet forms designed and maintained by the
SWIII CCB/LCCB. These documents provide the requestor an opportunity to state the
business case for the proposed change, provide data for establishing the impact on SW
infrastructure resources such as main memory, and document the need for funds for
recurring maintenance. While LCCBs are not required to use the ECP form for
Category C requests of K or less, use of this form, or minor variants, is strongly
encouraged so that common data will be available for loading into the Knowledge Base
maintained by TISCOM. Category C requests that are over K in lifecycle costs must
be submitted to the SWIII CCB using the ECP form.
g. The CGDN+ is a critical component of the communications infrastructure that supports
SWIII and SWIII-compatible systems. The use of CGDN+ for any application other
than those authorized by TISCOM is prohibited. The sensitivity of the data in an
application that is a candidate for deployment must be evaluated. Accreditation may be
required in accordance with reference (e).
h. Modifications to the approved/installed configurations of the CGDN+ or the record
messaging system (SSAMPS) by any organization other than TISCOM are not
authorized. All modifications to the CGDN+ or the record messaging system are subject
to approval by Commandant (G-SC).
4
Previous Page
