Encl. (1) to COMDTINST 4100.7
Engineering Logistics
CONOP
I.
Introduction
________________________________________________________________________
A.
Purpose
The purpose of this Concept of Operations (CONOP) is to define the future Coast Guard
engineering logistics system and describe how it will work in supporting its customers. The
general intent is to ensure that all members of the engineering logistics community share a
common vision of the future and are working toward the same ends.
Two specific objectives are: (1) to provide a conceptual view of the optimal state for Coast
Guard engineering logistics, and (2) to provide a framework for the development of the
business practices and information management systems needed to support engineering
logistics for aircraft, shore facilities, and vessels, which are referred to generically as
platforms. Throughout the document the term platform is understood to be anything that
requires engineering logistics support.
B.
Background
The decision to develop a CONOP arose from the need to have a common vision of the
future state of Coast Guard engineering logistics which will bridge the gap between broad
strategic visions, as discussed in the Values, Vision, Mission and Doctrine, and specific
business plans.
This detailed, conceptual view of the optimal logistics system serves as the end state toward
which all logistics activities, and hence, all business plans, must lead.
The Vessel Logistics CONOP defined the optimal state for vessel logistics. This CONOP
expands the scope of that effort to include all elements of engineering logistics: aviation,
shore, vessel, and electronics.
C. Methodology
Representatives from the various Headquarters Offices and major field unit logistics
suppliers, as well as key customer representatives, have been meeting over a two year period
discussing logistics issues. On 5 May 1993 a Quality Action Team (QAT) was chartered by
the Engineering Logistics Steering Committee (ELSC), consisting of members from the
aviation, shore, and vessel communities. This team was asked to review the Vessel CONOP,
and develop a CONOP which includes the individual engineering disciplines. The QAT met
in a series of two day meetings over a period of five months. Through this effort they
developed the Engineering Logistics CONOP.
It is important to understand that the CONOP is not a plan-- that is the function of the
Logistics Master Plan and various other implementation plans. The CONOP document is a
high level description of the future and this description must be based on solid principles. To
be definitive and yet address how the future system will work, the CONOP must identify the
critical system characteristics and significant functional roles. Finally, these principles,
characteristics and role definitions must be easily understood and presented in a concise, easy
to read document.
1
Previous Page
