1 / 8

Operational Contract Support (OCS) Joint Capabilities and Integration Development Systems (JCIDS)

Operational Contract Support (OCS) Joint Capabilities and Integration Development Systems (JCIDS). 24 March 2009. History. New inputs Legislation Guidance Audits . Evolving Concepts Program Management Institutional Mission Whole of Government Multinational/Coalition

nonnie
Download Presentation

Operational Contract Support (OCS) Joint Capabilities and Integration Development Systems (JCIDS)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Operational Contract Support (OCS)Joint Capabilities and Integration Development Systems (JCIDS) 24 March 2009

  2. History • New inputs • Legislation • Guidance • Audits • Evolving Concepts • Program Management • Institutional Mission • Whole of Government • Multinational/Coalition • Value Proposition • Expanded Audience • Changing inputs • Doctrine • Lessons Learned • Solutions

  3. Objective • Conduct analysis of OCS and staff through JROC to improve synchronization, coordination, and integration of OCS programs and activities across the DoD components and with DoD mission partners to include whole of government (DoS, USAID), NGOs, PVOs, and multinational partners: • Define a comprehensive OCS strategy to promote convergence/coherence of OCS between/among DoD, WoG, and coalition partners. • Broaden community of interest and promote stakeholder awareness/commitment • Identify OCS requirements/overlap/gaps, mitigate risk/shortfalls • Standardize on OCS concepts, policy, doctrine, processes, tools, training, organizations…to improve effectiveness and efficiency. • Define and resource long term OCS capabilities • Institutionalize OCS in DoD (DCR, S&T, PPBE, Acq, CD&E, etc)

  4. Scope of CONOPS • Conduct analysis of OCS: • Time horizon: near- (2009) to mid-term (2016) • Integrate OCS beyond Logistics to synchronize, coordinate and integrate with other JCA capability areas and functionals • Address full lifecycle OCS, integrating Program Management • Echelons: strategic to tactical application of OCS from institutional capacity to tactical capability • Operations: across all phases (0-V) for world-wide contingencies across the ROMO • Relations: Address whole of gov’t (WoG), Joint, Interagency, Intergovernment, Multinational, NGOs and PVOs

  5. Research • Be informed, but not constrained by: • Public Law (NDAAs, Federal Acquisition Regulations) • Strategic Guidance (NDS, NMS, CCJOv3) • Policy (DoDI 3020.41) • Doctrine (JP 4-10, TTPs) • Reports (Gansler, GAO) • Lessons learned (current operations, exercises) • Tools (SPOT, BISA, FPDS-NG, JOPES) • More interested parties and products emerging • New oversight bodies in place (Commission on Wartime Contracting) • Active GAO reports in work

  6. Core Team: Sponsor: OADUSD(PS) Research/Analysis: LMI Community of Interest: JS (J4) OSD(P, DPAP, DLA, DCMA, JCASO) Services (ASAALT, HQDA G-4, SAF/AQ, ASN/RDA, HQMC) CCDRs (JOCSPs, NORTHCOM J4) …expanding OGA (DoS, USAID,…) Coalition (NATO, …) FCBs JCBs JROC CCDRs OGA (DoS, USAID) Coalition (MN, NATO) Partners

  7. OCS JCIDS Schedule

More Related