COMDTINST 5200.16
b. The SWIII Configuration Control Board (CCB) members are:
Commandant (G-SCC) (Chair), (G-SIA), (G-SCT), (G-SCE)
Commanding Officer TISCOM
MLCLANT (t)
MLCPAC (t).
Changes to the SWIII baseline will be documented in Engineering Change Proposals
(ECPs). Electronic mail will be the primary mode of dissemination of ECPs for SWIII
CCB review and approval. When the nature of the ECP warrants, the SWIII CCB may
meet or use a telephone conference. Generally, the SWIII CCB will have a minimum of
30 working days to provide a response and may task the SWIII Configuration
Evaluation Team and/or other CG application experts to provide a technical evaluation
of any request. In this case a response from the SWIII CCB may take longer than 30
days. The SWIII CCB will notify the originator if a response will take more than 30
working days. SWIII CCB processes will foster a rapid turnaround of the ECP and keep
the requester informed on the status.
c. Local Configuration Control Boards (LCCBs) may be established at MLCs, standalone
Headquarters units established as individual Windows NT domains, and Headquarters
Support Command (HSC). LCCBs must be chartered. Chartering organizations are
LANTAREA(t) and PACAREA(t) for the respective MLCs, the responsible
Headquarters program for standalone Headquarters units, and Commandant (G-CCS)
for HSC. MLCs may delegate LCCB authority to the ESUs. All LCCB decisions are
subject to oversight and may be overruled by their chartering organization. The LCCB
that approves an ECP is solely responsible for supporting the resulting changes to the
systems and for any present and/or future impact to their users or applications.
d. The Coast Guard's standard microcomputer infrastructure is divided into three
categories:
(1) Category A - SWIII operating system, e-mail and office automation software, Coast
Guard Data Network Plus (CGDN+), and the record message system. The SWIII
CCB is the only governing body that can approve ECPs in this category.
(2) Category B - Mission Essential, Department of Transportation (DOT) sponsored, or
other program sponsored CG-wide (enterprise) applications designed for
deployment for CG-wide access. The sponsoring program manager and
Commandant (G-SIA) will endorse ECPs for all enterprise systems in this category.
If the Category B request requires a change to the CG-wide SWIII baseline, then the
SWIII CCB must also approve the ECP. The program sponsor must submit the
application software to the Information Systems Division (isd) of TISCOM for
certification testing prior to deployment. The certification process takes place
subsequent to the approval of the ECP. If Category B applications require the use of
SWIII commercial off the shelf products (COTS) that are not part of the standard
image, the COTS software must undergo the certification process to determine
technical implementation procedures.
3