Attachment 1 to OMI Demonstration Transition Agreement
2 July 2014
Operational Contract Support Joint Concept (OCS JC)
OCS Mission Integrator (OMI) Demonstration with U.S. Pacific Command (USPACOM)
Concept of Operations
1.
Introduction
Operationalizing OCS is critical for integrating contracted support as an enabling capability
for Joint Force 2020 (JF 2020). Incorporating OCS into the JF 2020 vision requires the
ability to plan, manage, and integrate contractor support into military operations to gain
operational access and sustain forces to conduct globally integrated operations. In an OCS
context, this means the three OCS functions: contract support integration, contracting
support and contractor management must be highly developed and rapidly integrated across
the joint functions. This demonstration establishes an Operational Contract Support Mission
Integrator (OMI) at U.S. Pacific Command (USPACOM) to operationalize one of the main
ideas of the OCS Joint Concept (OCS JC) in an operational setting and to inform force
development processes to improve OCS.
2.
Purpose
This demonstration has three primary purposes. First, it establishes an OCS warfighting
enabling capability to address USPACOM’s current OCS capability gaps to plan and
integrate OCS into operations and training. This demonstration will assess the OMI’s
performance as envisioned in the OCS JC to accomplish its essential capabilities and tasks
under operational conditions to increase the responsiveness and accountability of contracted
support to the joint warfighter. Second, this demonstration contributes to the DOD’s
mandate to improve acquisition processes through training and continuous improvement in
the qualifications and experience of both the acquisition workforce and of non-acquisition
personnel. Lastly, the results of this demonstration will inform OCS Doctrine,
Organization, Training, Materiel, Leadership and education, Personnel, and Facilities and
Policy (DOTMLPF-P) force development and contribute to operationalizing OCS as an
interdependent capability of JF 2020.
This concept of operations (CONOPS) outlines in broad terms the phases, actions and
success measures for the demonstration. The origins and foundation blocks of this
CONOPS derive from the Joint Requirements Oversight Council (JROC) approved OCS JC
and its accompanying DRAFT Transition Implementation Guide (TIG) (v0.5.3). The OCS
JC broadly outlined the future OCS required essential capabilities to support JF 2020. The
TIG provides further details by describing transition products, recommendations and
outlining the force development processes to realize the capabilities. These documents
provide sufficient detail for the stakeholders to develop and coordinate their respective
plans, actions and tasks over the three-year demonstration period. This OMI demonstration
affords a unique opportunity to methodically assess and validate many of the force
development recommendations espoused in the concept in an “OCS operational laboratory.”
3. Background
JROC Memorandum 159-13, 07 October 2013, approved the OCS Joint Concept. This
concept envisions that contracted support for military operations will be an interdependent
1
Attachment 1 to OMI Demonstration Transition Agreement
2 July 2014
capability of JF 2020. This concept addresses how JF 2020 can operationalize OCS to
optimize contracted support capabilities of the Total Force partners to achieve operational
effects across the range of military operations within acceptable and manageable risk levels.
It builds upon ongoing efforts to institutionalize OCS in the present force and proposes a full
spectrum DOTMLPF-P capability solution framework to deliver more responsive and
accountable OCS.
The goal of joint concept development is to transition solutions to the joint warfighter and to
inform force development processes. USPACOM contributed to the concept development
by participating in the Limited Objective Experiment (LOE) to test solution elements of the
concept. The OMI, one of the major organizational solution elements in the OCS JC, will
provide combatant commanders, joint task forces or components a capability to integrate
OCS across the joint functions and into the contracting efforts to optimize Total Force
capabilities. The OMI will provide combatant commands (CCMD), joint task forces and
components unprecedented capability to plan, manage, and integrate contractor support
across the joint functions spanning the overlapping timeframes of current operations, future
operations, and future planning to gain operational access and to sustain joint forces. This
demonstration will validate the OMI in the operational setting as envisioned in the approved
OCS JC.
4.
Scope.
This warfighter enabling concept supports the Capstone Concept for Joint Operations
(CCJO) and describes in broad terms how future OCS DOTMLPF-P capabilities will better
facilitate the integration of Total Force partner capabilities into military operations. This
demonstration will addresses how USPACOM, joint task forces (JTFs), Service
components, and subordinate commands can better employ OCS capabilities to achieve
desired operational effects in the 2020-2030 timeframe. Since contracted support is
integrated into most joint functions to some extent and spans all operational levels, the OCS
JC and the OMI demonstration are applicable to commanders, their primary and specialty
staffs, and the subordinate components. The OCS JC is also consistent with the 2012
strategic guidance by proposing innovations in how the DOD plans for and oversees
contracted support to reduce the cost of doing business.
The required OCS capabilities outlined in the OCS JC and exercised in this demonstration
span the range of military operations from strategic to operational and tactical levels, and
through all phases of operations (0-V). Primarily focused on the operations of the Joint
Force and its components, the concept acknowledges that the Joint Force may be operating
in conjunction with other military, governmental, and/or nongovernmental partners. While
focused on OCS unity of effort within DOD, the OCS JC solution framework enables
interfacing with future interagency, multinational and nongovernmental organization
partners. A common OCS vision and the development of the technical details for
implementation within the department are necessary prerequisites before the OCS scope is
broadened to include all mission partners.
The demonstration is envisioned to span a three-year period to account for the complete
cycle time for plan development and joint exercise execution. Two years is the required
cycle time for planning, staffing with subordinate and supporting commands, and gaining
approval of major war plans. An additional year is planned for to complete OCS integration
2
Attachment 1 to OMI Demonstration Transition Agreement
2 July 2014
into USPACOM exercise scenarios and to integrate OCS across the joint functions and
within staff directorates.
5.
Operations Descriptions
5-1. Mission
JS J4 and USPACOM conduct a three-year demonstration for the purpose of exercising the
OMI at USPACOM in an operational setting as envisioned in the OCS JC to determine the
cell’s validity and utility for improving planning, managing, and integrating contracted
support into military operations. Additionally, observation and insights will inform ongoing
and future OCS DOTMLPF-P capability force development and contribute to
operationalizing OCS as an interdependent capability of JF 2020.
5-2. Stakeholders
Once concepts are approved, solutions must be transitioned to the warfighter and actions
initiated to ensure they become institutionalized across the DOTMLPF-P force development
spectrum. Succeeding in transitioning solutions requires transition partners agreeing to
sponsor and deliver sustainable joint capabilities to the joint warfighter. For the purpose of
this demonstration the JS J4 is the concept and demonstration sponsor and USPACOM is the
operational implementation sponsor (transition agent). A formal Transition Agreement (TA)
is required to outline the agreed upon roles, responsibilities and expectations of the
participating stakeholders and to provide continuity over the three-year period.
5-3. Assumptions and Constraints
5-3-1. Assumptions
A. The JS J4 requests and OUSD(AT&L) DP provides on an as available basis Defense
Acquisition Workforce Development Funds (DAWDF) to fund the demonstration as it
meets the intent of improving acquisition by increasing training and experience of the
acquisition workforce and non-acquisition personnel. While DP has indicated every
intention to continue funding through successful completion of the demonstration, it is
predicated on DAWDF funds availability.
B. Demonstration sponsors agree to a TA and adequate resources are available for a threeyear period. Funding will be on an annual basis based upon success in meeting
milestones and expectations.
C. Military and civilian personnel are not readily available to man all the OMI positions.
One (1) Government Service (GS) term employee to lead the OMI effort is budgeted for
and anticipated, and the remaining participants will be contracted. Limited qualified
contractor personnel may be available at the outset to fulfill the OMI duty positions as
described in the performance work statement.
D. Contracted personnel are subject to turnover. For planning purposes, estimate one each
contractor turnover in years two and three.
E. Extensive individual and collective training will have to be conducted in phase I to get all
OMI members sufficiently immersed into OCS knowledge and skills.
3
Attachment 1 to OMI Demonstration Transition Agreement
2 July 2014
F. The Joint OCS Planning and Execution Course (JOPEC) slated for 31 March in Hawaii
will be conducted as scheduled. Flexible arrangements for scheduling USPACOM OMI
personnel for JOPEC in fiscal year 2014 will be essential.
G. Contract start date is on or about 23 June 2014.1
5-3-2. Constraints
A. Funding will be incremental on an annual basis and competitive due to fiscal constraints.
B. Travel will be limited to essential training/orientation, joint exercise life cycle events,
operations, and mission essential coordination with the Joint Staff. Maximum use of
VTC/teleconference for coordination is required.
C. Qualified applicant pool availability in Hawaii may be a constraint in hiring all six
contractors by the desired start date and a phased hiring approach may have to be
implemented.
5-4. Operational Description
Planning and executing the OMI demonstration starts with an intensive shaping phase to
align resources with a plan, and then followed by a three phase demonstration. The high
level description of the CONOPS follows.
Phase 0, Part A
August 2013 – February 2014
Planning, requirements development, and resourcing.
This phase encompasses the critical activities to provide the foundation for the OMI
demonstration effort. During this phase the CONOPS will be finalized, performance work
statements (PWS) will be developed, a rough order of magnitude (ROM) cost will be
estimated to cover the three-year period, and a funding strategy will be determined. All
action officers are responsible for briefing their respective chains of command to gain their
support. Success will be achieved with an approved CONOPS, draft proposals highlighting
requirements, and approval from OUSD (AT&L) DP to provide Defense Acquisition
Workforce Development Funds (DAWDF) to resource the demonstration over a three-year
period.
JS J4. The JS J4 will act as the lead for this phase to staff the OMI demonstration CONOPS
and ROM development with OUSD (AT&L) DP and USPACOM. J4 along with
USPACOM will develop a rough order of magnitude (ROM) cost estimate for the
demonstration to include government and contractor labor and military, civilian and
contractor travel. This ROM includes the full time equivalents (FTE) requirement for the J4
contract to provide project management expertise and planning oversight as well as training
and integration support throughout the demonstration period. It is estimated 1.4 FTEs will be
required for years one and three, and 1.9 FTEs for year two due to the decoupling of the OCS
JX-16 exercise with the demonstration. The J4 will propose PWSs for the demonstration for
coordination. The ROM for both contracts (USPACOM and J4) will be furnished to OUSD
(AT&L) DP as justification for funding via DAWDF. During this phase the J4 will socialize
1
The OMI demo was originally planned to start in March 2014 to coincide with the JOPEC scheduled to start 31
March in USPACOM.
4
Attachment 1 to OMI Demonstration Transition Agreement
2 July 2014
the concept as well as the anticipated benefits of the OMI across the OCS community of
interest.
USPACOM. USPACOM will coordinate with the JS J4 to develop the CONOPS and the
ROM. USPACOM will estimate government and contractor labor (staffing) and travel
requirements by phase using published USPACOM labor and per-diem rates in their
calculations for its one GS position and 6.0 contracted FTEs to man the OMI for the threeyear period. USPACOM will coordinate with the JS J4 to determine the required skills and
qualifications necessary for the positions and to ensure skills include planning, acquisition,
program management and logistics expertise are considered. USPACOM will include this
information in the draft performance work statement (PWS) to staff with the J4. USPACOM
must develop the PWS in such a way that it provides clear measures of success as a result of
the demonstration program. Throughout this phase the USPACOM J46 will socialize the
concept and the OMI demonstration across the command and with its components.
Phase 0, Part B.
March 2014 - July 2014
Transition Agreement coordination and Acquisition.
This effort will focus on development of the Transition Agreement amongst the primary
stakeholders and completion of the overall acquisition strategy. The Transition Agreement
outlines the roles and responsibilities of each of the major participants: the Concept and
Demonstration Sponsor, JS J4 OCSSD and the operational implementation sponsor
(Transition Agent), USPACOM J46. The TA serves as a high level governance document to
provide continuity of the demonstration over its life cycle and is supplemented with details in
the OMI Demo CONOPS, the OCS JC and the accompanying TIG. The acquisition strategy
will determine the appropriate contract vehicle, contract offices, number and types of
contracts and the appropriate contract oversight to ensure each stakeholder is responsible and
empowered to execute its responsibilities. Success at the end of this phase will be a signed
Transition Agreement and contract(s) let in the May 2014 timeframe to coincide with a
planned ‘boots on ground’ of 23 June 2014.
JS J4. The JS J4 will lead the overall acquisition effort for the entire demonstration and
coordinate with OUSD (AT&L) DP and USPACOM throughout each phase of the
acquisition process. The J4 will include their detailed military, DOD civilian and contractor
travel estimates developed in phase 0, Part A. The J4 in coordination with USPACOM will
ensure the request for proposal (RFP) contains the required level of effort and skills
necessary to support the demonstration. JS J4 will determine an acquisition strategy that
culminates in the award of a contract in May 2014 for a 1 June start. As with USPACOM,
the J4 will ensure a contract oversight and management plan is accomplished and ready upon
award of the contract. Throughout this phase, J4 will continue to advise OUSD (AT&L) DP
of developments during the acquisition process and alert them of any potential funding
issues. J4 will also continue to socialize the concept and the progress of the demonstration
with the OCS community of interest.
USPACOM. USPACOM will support the acquisition effort for their specific OMI
requirements and coordinate on their progress with the J4 and OUSD (AT&L) DP.
USPACOM will develop the position description and required skills required for the one
Government Service (GS) representative and each of the six (6) FTE contractor positions to
5
Attachment 1 to OMI Demonstration Transition Agreement
2 July 2014
be incorporated into the PWS. USPACOM in coordination with the JS J4 will determine an
acquisition strategy that culminates in the award of the contract in May 2014. USPACOM
will ensure a contract oversight and management plan is developed and ready upon award of
the contract. Adherence to this timeline is essential to ensure the contractors selected can
locate and have personnel in place to begin work by June 2014.
Phase I
June 2014 – May 2015
Complete OCSJX-15 and Full Operational Capability OCSIC
This phase establishes an OCS Integration Cell (OCSIC), the precursor to the OMI,
capability at USPACOM as described in the soon to be published JP 4-10, Operational
Contract Support. Primary focus is for the new members of the OMI to complete individual
and collective training, develop internal SOPs, familiarization with USPACOM’s AOR, and
establish effective working relationships with the staff, components and other supporting
organizations, and to plan and execute OCSJX-15. Success is achieved at the conclusion of
OCSJX-15 when the forming OMI attains full operational capability (FOC)2 as an OCSIC
and successful completion of the JOPEC. Additionally, efforts to assess the feasibility and
utility of establishing an OCSIC or OCSIC ‘like’ capability in USPACOM Service
components should be initiated. Half way through the initial phase, JS J4 and USPACOM
J46 will develop the funding and supporting documentation request for continued DAWDF
for phase II.
USPACOM. As the transition implementation sponsor and the warfighter capability
recipient, J46 has the lead for providing workspaces and IT support, establishing and training
their new OCSIC, and to integrate the capability within the USPACOM staff. Initial
operating capability (IOC) success criteria for this phase include completing individual
training on OCS knowledge and practices, along with USPACOM specific procedures and
policies. Within 45 days of forming, the OMI will develop a detailed plan of actions and
milestones (POAM) and a work breakdown structure (WBS) of key tasks, deliverables, and
success criteria to guide progress and to provide actionable information for decision makers
to decide to continue resourcing with DAWDF. For planning purposes, it may take up to 90
- 120 days for the OMI members to complete JOPEC, become knowledgeable with their new
tasks, environs and responsibilities before progressing onto collective training and
networking. The latter part of this phase encompasses the OCSIC developing its internal
SOPs and becoming familiar with USPACOM’s numerous boards, bureaus, centers, cells and
working groups (B2C2WG) and establishing habitual relationships with contracting
organizations and requiring activities. It is anticipated that three (3) of the OMI contracted
planners will be focused on assisting components (USARPAC, PACAF, and PACFLT)
planning efforts, while still remaining integral OMI members responsive to J46.
Additionally, special emphasis must be directed towards exercise planning and coordination
as USPACOM is the host CCMD for OCSJX-15. Completion of Phase I is achieved when
the OCSIC is proclaimed FOC as an OCSIC and meets the evaluation criteria established by
USPACOM.
2
For the purpose of the demonstration, full operational capability (FOC) of the OCSIC equates to initial operational
capability (IOC) of the OMI.
6
Attachment 1 to OMI Demonstration Transition Agreement
2 July 2014
At or before the conclusion of OCS JX-15, senior leadership must evaluate the feasibility of
USPACOM leading or supporting OCSJX-16. While, efficiencies in training, costs and
informing force developmental efforts could be achieved by coupling the OMI demo with
future OCSJX series exercises, other considerations such as USPACOM operational needs
and involvement by other CCMDs must be assessed to make a more informed decision for
establishing a sustained OCS exercise strategy. USPACOM J46 has outlined an aggressive
campaign to integrate OCS into the upcoming Talisman Sabre and Ulchi Focus Guardian
combatant command exercises.
Joint Staff J4. As the OCS JC sponsor, the JS J4 is in a supportive role to transition the OMI
from a conceptual idea to a warfighting enabling capability. During this phase the J4
OCSSD will assist USPACOM by allocating spaces for the JOPEC and providing learning
materials, planning tools and sharing information accumulated over the last two years of
concept development. Some of these products include the Joint Metrics & Readiness Guide
(JMR), the DRAFT CJCSM 4300.01—Planning for OCS, and the JOPEC courseware. JS J4
will plan to conduct the JOPEC course (and additional desk-side training) with a mobile
training team (MTT) in Hawaii from 18 – 29 August. Additionally, JS J4 will coordinate for
an OCS Familiarization TDY to the D.C. and Virginia areas 6 – 12 September, and a
Contingency Acquisition Support Model (cASM) TDY to Layton Utah, 11 – 18 October. JS
J4 will provide technical support to the demonstration by making available subject matter
experts in concept, planning, training, OCS automation and project management. The JS J4
will lead efforts and conduct direct coordination with OUSD (AT&L) DP for annual
DAWDF. Close interaction with USPACOM will be critical for informing ongoing and
future OCS doctrine, organization, training, leadership and education, exercises and planning
lines of effort spanning the force development processes.
It is envisioned that most of the OCS JC TIG transition products and recommendations
spanning the DOTMLPF-P capability spectrum will be assessed to some extent throughout
this demonstration where practical. Determining OCS automation/tools and OCS manpower
requirements are designated as special emphasis areas as these capability areas are most
critical to operationalizing OCS. Also, determining materiel requirements to develop OCS
tools to share common data elements, to depict a common operating picture (COP), and to
inform the command’s knowledge management system is critical to achieving the operational
effectiveness of the OMI and delivering responsiveness and accountable contracted support
capabilities. Determining and validating the OMI’s OCS personnel requirements and
identifying the necessary skills and qualifications of its members, as well as determining the
organization structure will inform the DOD’s overall OCS manpower strategy to mature OCS
as a warfighter enabling capability.
JS J4 will synergize and integrate its leadership and planning responsibilities for OCSJX-15
with OCSIC/OMI development efforts. The JS J4 will leverage the demonstration to fulfill
CJCS US Code Title 10 responsibilities for providing joint doctrine, joint capability
validation (including materiel requirements), joint exercises, joint training, and joint
education support across the DOTMLPF-P force development processes. While not all
inclusive, these OCS efforts include: develop a joint OCS exercise strategy to create a standalone joint OCS exercise and to integrate OCS into existing GCC Title 10 exercises; establish
OCS operational and strategic readiness measures; inform authorities and doctrine and fill
documented OCS gaps; refine OCS JMETs, metrics and readiness measures (JMR Guide);
7
Attachment 1 to OMI Demonstration Transition Agreement
2 July 2014
train current doctrine and inform future doctrine; enhance acquisition and operational
community OCS Interaction; and increase senior leader awareness of OCS challenges and
capabilities.
Phase II
June 2015 – May 2016
OMI Full Operational Capability, Talisman Sabre, Ulchi Focus Guardian and OCSJX-16 (or
equivalent) participation, Annex Ws for CON/OPLANs
Phases II spans a complete year and signifies the transition from the OCSIC capability to the
more capable, robust OMI as described in the OCS JC and accompanying TIG. Building
upon the training and experience garnered over the previous phase, the OMI must
demonstrate proficiency in the essential capabilities and supporting tasks outlined in the
concept and be viewed as value added by the CCMD for integrating contracted support, as
part of the Total Force, into the CCMD’s operations and exercises. Successful completion of
phase II will have the OMI as an integral part of USPACOM’s B2C2WG structure,
documented OCS automation/tools and personnel requirements, participated in USPACOM
exercises such as Talisman Sabre, supported OCS JX-16, and made appreciable contributions
towards increasing OCS planning, contracting integration and contractor management into
USPACOMs planning, training and operations processes. Half way through the initial phase,
JS J4 and USPACOM J46 will develop the funding and supporting documentation request
for continued DAWDF for phase III.
USPACOM. J46 will oversee the evolution of the OCSIC to the OMI by achieving the
milestones established in their detailed POAM/WBS, assessing the proficiency of the OMI
and its members in conducting OCS planning, and serving as the “OCS operational
laboratory” to assess OCS TIG transition products, including the special emphasis areas of
automation/tool requirements and OCS manpower needs. The OCS JC essential capabilities
and tasks coupled with the transition products outlined in the OCS JC TIG will help guide
this phase. Some of these tasks include: lead OCS planning across the primary and special
staffs, develop OCS policies and procedures for requirements determination, serve as the
JRRB secretariat, and advise the commander and the staff on OCS benefits, risks and
mitigation strategies. Demonstrating proficiency of the tasks during planning, training and
exercises, or better yet conducting actual operations, are essential to validate the OMI’s
utility to the CCMD.
By leading OCSJX-15 and supporting OCSJX-16 (a leadership milestone decision to be
determined on or before completion of OCSJX-15), the OMI will have demonstrated
planning proficiency and interaction with contracting organizations and the CCMD’s staff in
demanding simulated environments/conditions. Continued training, education and
participation in B2C2WGs will increase the effectiveness of the OMI while increasing OCS
knowledge across the command. Expanding on the lessons of OCSJX-15 and participation in
other PACOM exercises, the OMI is the proponent to champion OCS themes and storylines
into joint and component exercises, as well as into theater security cooperation plans. For
OCSJX-16, integrating OCS within the other logistical functions such as distribution and
supply may become an exercise objective. Should USPACOM not lead OCSJX-16, it is
envisioned that a deployable two person element of the OMI will participate and share its
experiences with another CCMD that has been designated to lead the annual OCS exercise.
8
Attachment 1 to OMI Demonstration Transition Agreement
2 July 2014
The degree of OMI participation will have to be determined as soon as possible at the
conclusion of OCSJX-15.
Surveys or interviews of the primary and special staff, contracting organizations and units
could be conducted to gauge the utility and effectiveness of the OMI’s interaction and
support within the CCMD. Results of the surveys need to be incorporated into the POAM
where required and other innovations considered to improve or to refine the OMI.
Information will be shared with the JS J4 to inform OCS force development efforts as well
refine the OCS JC and future capability requirements. J46 will prepare an annual report to
gauge the demonstration, while OMI members will provide observations, insights and
lessons learned (OILs) into JLLIS to be shared with the OCS community of interest.
Based on the results of the demonstration to date J46 and USPACOM should assess,
document and validate their OCS personnel requirements for OCS-coded joint duty positions
on the Joint Duty Assignment List (JDAL) and enter them into the Joint Duty Assignment
Management Information System (JDAMIS). Subsequently USPACOM may initiate
personnel and Program Objective Memoranda (POM) actions to resource the OCS joint duty
positions for an enduring OMI capability beyond the demonstration period, starting in FY 17.
JS J4. Coordinating closely with USPACOM J46, OCSSD will monitor progress of the OMI
transition and review OILs to determine applicability and impact upon ongoing OCS
DOTMLPF-P force development efforts, such as the OCS Action Plan, OCS automation and
OCS manpower needs. J4 will regularly address the demonstration within appropriate
forums to socialize the concept. As USPACOM may or may not lead OCSJX-16 (as noted
above) JS J4 may split its DOTMLF-P force development efforts with a separate CCMD.
The JS J4 will continue to leverage the demonstration to fulfill CJCS US Code Title 10
responsibilities for championing joint doctrine, joint capability validation, joint exercise,
joint training, and joint education improvements across the DOTMLPF-P force development
processes. The JS J4 will lead efforts and conduct direct coordination with OUSD (AT&L)
DP for annual DAWDF.
Phase III
June 2016 – May 2017
OMI Validation and Transition to Enduring Capability
Phase III completes the demonstration and transitions the OMI into an enduring warfighter
enabling capability for USPACOM. Conceptually at the end of the demonstration, OCS is
fully operationalized within USPACOM. Position descriptions, joint duty assignment and
POM actions are completed and resourced to man the OMI at the end of the demonstration
period and a transition plan is executed to maintain continuity of operations. Validation will
include assessing the program over the three-year period with the measures of performance
and success criteria developed and reviewing observations, insights and lessons learned.
Ultimately the CCMD must determine whether the OMI was able to achieve greater
responsiveness and accountability of contracted support for the CCMD. USPACOM’s level
of participation in OCSJX-17, if any, will have to be determined at the conclusion of
OCSJX-16. All OMI demonstration related SOPs, planning products and assessments will be
shared with the JS J4 OCSSD to be used for OCS DOTMLPF-P capability development and
to serve as benchmarks for establishing OMIs, or OCSIC like capabilities, at other
commands or in JTFs.
9
Attachment 1 to OMI Demonstration Transition Agreement
2 July 2014
USPACOM. OCS is operationalized within the CCMD. Contractor support integration,
contracting support and contractor management will be sufficiently formalized and integrated
into USPACOM’s processes, and the command routinely recognizes contracted support, as
part of the Total Force, as a warfighting enabling capability and force multiplier. During this
phase, the OMI will review, validate, or revise, all the essential capabilities, effects and tasks
outlined in the OCS JC to validate or make revisions to the OCS JC and the OMI. Members
of the OMI will have successfully conducted at least one iteration of OCS training in support
of subordinate components. Available OCS automation and tools will be integrated where
applicable and validated JF 2020 materiel requirements will be provided to the JS J4 to be
entered into Joint Capability Integration and Development System (JCIDS) or commercial
business environment (CBE) processes. Annex W’s are completed for required plans and
successful completion of a full iteration of the OPLAN/CONPLAN development cycle. OMI
participation in multiple OCSJXs and other PACOM exercises, and potentially supported or
participated in actual operations, will have made significant contributions across the CCMD
such that leaders, staff elements, contracting organizations and units (as requirement
developers) appreciate the OMI’s capabilities to increase contracted support responsiveness
and accountability. During this final phase, the OMI successfully deploys a forward element
into a JOA to support a JTF in either an exercise or actual operation(s). J46 champions
personnel and POM actions leading to authorizing OCS civilian and military joint duty
assignment positions and develops a transition plan to fully institutionalize the OMI from a
demonstration to an enduring capability. All OMI demonstration related SOPs, planning
products and assessments will be shared with the JS J4 OCSSD to be used for OCS
DOTMLF-P capability development and to serve as benchmarks for establishing OMIs.
During the last quarter of the demonstration USPACOM will transition the OMI
demonstration staff element to permanent positions on the USPACOM staff by completing
the personnel and POM action if assessments are positive and authorizations and resources
are available. Manning levels may have to be flexible based on the prevailing authorization
and budget situation and competing priorities. At the time of this demonstration, the
stakeholders are aware of the DOD’s mandate to reduce senior staffs by 25% by 2017, and
realize the challenges this imposes to establish OCS as an emerging capability.
Additionally USPACOM will determine the manpower requirements and methodology to
transition the OMI from a “cell” to a larger “center” when mission requirements dictate. The
larger OMI Center would lead OCS operations during large, complex and enduring
contingency operations and permit the deployment of a forward element of the OMI to
deploy in support of a JTF or a component. This determination will outline courses of action
to source the additional manpower from either the Active Duty, Reserve Component
(AD/RC), government civilian workforce or additional contract labor.
JS J4. Coordinating closely with USPACOM J46, OCSSD will monitor progress of the OMI
attaining FOC and review OILs to determine applicability and impact upon ongoing OCS
DOTMLPF-P force development efforts, such as the OCS Action Plan, OCS
automation/tools and OCS manpower. The JS J4 will review OMI progress reports, OILs
and assessments provided over the entire period of the demonstration. The J4 will reevaluate
the OMI essential capabilities and tasks developed during the original concept development
effort and make changes accordingly to the OCS JC TIG to shape requirements development
for current and projected force development efforts across the DOTMLPF-P spectrum and/or
10
Attachment 1 to OMI Demonstration Transition Agreement
2 July 2014
submit change requests. JS J4 OCSSD will leverage assessments conducted by the OMI
demonstration as an OCS operational laboratory to validate OCS automation, information
technology and tools requirements and advocate for their development with the appropriate
stakeholders. In the event USPACOM submits OCS onto its integrated priority list (IPL), the
JS J4 and OUSD (AT&L) DP will advocate to the extent feasible for establishing personnel
and training resources as espoused in the OCS JC and validated by the CCMD.
J4 will regularly address the demonstration within appropriate forums and seek opportunities
to publish articles in defense journals to socialize the concept. Continue to identify OCS
requirements and to advocate DOTMLPF-P solutions to fully operationalize OCS for JF
2020, with emphasis on joint doctrine. Fortuitously, the timing of the OMI demo’s
conclusion will be useful for informing the next iteration for updating JP 4-10 which will
start the review/ update process in FY17. Informed by the demonstration, the J4 can use
actual testimonials to make factually based recommendations for advocating similar OMI
capabilities at other CCMDs and for operationalizing OCS to support JF 2020. Lessons from
previous OCSJX exercises will be incorporated into OCSJX-17 to increase complexity and
sophistication to challenge the participants in conducting globally integrated operations as
required by JF 2020.
Attachments
1. OCS JC Essential Capabilities, Effects and Tasks (separate Excel Spreadsheet )
11