R 111418Z DEC 17
MARADMIN 670/17
MSGID/GENADMIN/CMC WASHINGTON DC CDI//
SUBJ/DEFENSE INNOVATION UNIT EXPERIMENTAL PROJECT MANAGEMENT//
REF/A/DOC/SECRETARY OF DEFENSE/5JUL16//
REF/B/DOC/MCO/3960.6 – MARINE CORPS SCIENCE AND TECHNOLOGY (S AND T)//
REF/C/DOC/MCO/5311.6 – ADVOCATES AND PROPONENTS//
REF/D/DOC/COMMANDANT OF THE MARINE CORPS/SEP16//
NARR/REF (A) IS DOD DIRECTIVE 5105.85 DATED 6 JUL 2016, DEFENSE INNOVATION UNIT EXPERIMENTAL. REF (B) IS MARINE CORPS ORDER ON SCIENCE AND TECHNOLOGY POLICY. REF (C) IS MARINE CORPS ORDER ON ADVOCACY AND PROPONENCY. REF (D) IS THE MARINE CORPS OPERATING CONCEPT.//
GENTEXT/REMARKS/1.  Purpose.  Background.  Par. 3.2 of ref (a) directs the Vice Chiefs of the Services to communicate their Services priority needs and requirements to DIUx.  The Assistant Commandant of the Marine Corps has delegated this task and authority to the Deputy Commandant for Combat Development and Integration (DC, CD and I).  This MARADMIN establishes a process for Marine Corps involvement in projects at the Defense Innovation Unit Experimental (DIUx).
2.  Background.  The Commandant of the Marine Corps provided the future vision for the Marine Corps based on strategic guidance as currently defined in reference (D).  As the EA, MCS AND T, CG, MCWL expands on the CMCs vision by developing Marine Corps warfighting concepts and capabilities that enable the Marine Corps to field combat-ready and relevant forces.
3.  In order to ensure a coordinated and synchronized execution of DIUx efforts for the Marine Corps, DC, CD AND I is assigning the responsibility and the necessary authority to the CG, MCWL as the EA, MCS AND T, to coordinate and prioritize prototyping efforts at DIUx.  This will not limit access to DIUx, but will ensure a collaborative and coordinated effort in this important combat development area.
4.  Policy and procedures
  a.  In order to ensure visibility and to improve coordination of development, prototyping, and related efforts in which a Marine Corps element is expected to be the lead customer, primary proponent, primary stakeholder, or primary investor, proposed projects will be submitted to CG, MCWL (S AND T) for formal proposal within DIUx.  Marine Corps elements submitting projects may be required to sign a Memorandum Of Agreement (MOA) with DIUx.
  b.  For projects in which a Marine Corps element desires to be a secondary customer, stakeholder, or investor, projects will be submitted to CG, MCWL for formal incorporation into a DIUx project.
  c.  Marine Corps elements which are customers, stakeholders, investors, or participants in DIUx project or are supporting a DIUx project will submit weekly SITREPs to the senior DIUx Marine Corps Representative.
  d.  For projects in which a Marine Corps element is not customer or a stakeholder, but is a participant or is providing support (for example, participation in testing) Marine Corps elements are only required to advise the Senior DIUx Marine Corps representative of their participation prior to commencing participation.
  e.  Prioritization.  In instances when DIUx resources are insufficient to support all proposed Marine Corps projects, prioritization will be given to projects which address a validated Urgent Universal Needs Statements (UUNS) requirement, a Warfighting Capabilities Gap, or a Critical Task as defined in ref (d).
  f.  Funding.  Funding for DIUx projects in which the Marine Corps is an investor will normally be provided or coordinated by the Marine Corps element submitting the project.
5.  Applicability.  This MARADMIN is applicable to the Marine Corps Total Force.
6.  Release authorized by Lieutenant General Robert S. Walsh, Deputy Commandant, Combat Development and Integration.//