ENCLOSURE (1) to COMDTINST 5230.59
DECEMBER 1999
U.S. Coast Guard Common Operating Environment (USCG COE)
2.
CG COE LAYERS DEFINED
What's not in?
The USCG COE is not a system unto itself; it is a framework for building an open information
system architecture and infrastructure. To understand the USCG COE concept better, the scope
and bounds need to be defined. By establishing what is NOT in the USCG COE first, the
remainder of the document can expand on the contents of the USCG COE.
Enterprise Applications (EAs) are outside the scope of the USCG COE. EAs are the
information systems that run on top of the USCG COE. EAs are documented in the Coast Guard's
Systems Plan. The USCG COE defines the information technology environment that EAs must
operate within to ensure EA peaceful coexistence. Any new or modified EAs must be certified by
TISCOM to successfully function without affecting other components within the USCG COE to be
deployed.
Data Standards are outside the scope of the USCG COE. COMDTINST 5230.42 (series), U.S.
Coast Guard Data Element Naming Standards, describes the Coast Guard Data Architecture and
establishes provisions by which data that is processed by USCG COE compliant systems shall
conform to. The objective is to design applications separate from the data that is processed to
promote principles such as data sharing, source data entry, and interoperability.
What's in?
The USCG COE is a "plug and play" open architecture. Components may be added or deleted
through a structured process, as required to maintain the living model. The following graphic
depicts the layers of the model and is intended to establish a common vocabulary for describing the
set of services and interfaces of the USCG COE. The definition for each layer follows.
2
Previous Page
