03.07.2013 Views

View/Open - Naval Postgraduate School

View/Open - Naval Postgraduate School

View/Open - Naval Postgraduate School

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

A recent initiative to accommodate joint urgent operational needs is codified in<br />

CJCSI 3470.01 (July 15, 2005). It establishes policy and procedures to facilitate<br />

procurement of urgent, execution-year combatant commander needs outside of the DoD<br />

5000 series process, specifically for programs of ACAT II level or below. Generally, these<br />

are considered to be life- or combat mission-threatening needs, which were previously<br />

unforeseen and that are now required to be fulfilled within months versus years.<br />

While this new process is not intended to replace the JCIDS process of formal<br />

requirements development, it is meant to accelerate the fielding of readily available systems<br />

for wartime use. Each of the services has a similar initiative for rapid response or<br />

accelerated deployment capability using COTS or Nondevelopmental Items (NDI). One<br />

such example is the Army’s Warfighter Rapid Acquisition Program (WRAP). It is a fund of<br />

approximately $100 million per year that the Army uses to rapidly procure relatively low-cost<br />

but high-leverage systems that performed well in experimentation. The WRAP effort has<br />

reportedly reduced acquisition cycle-time for systems procured by an average of 12 months.<br />

The Marine Corps and the Air Force∗ have established similar rapid acquisition programs in<br />

FY 2001 and FY 2002, respectively (ADR, 2000).<br />

In keeping with the aspect of timeliness as it relates to transaction procedures and<br />

governance, we have also noted above that commercial availability can serve as an<br />

important factor. Likewise, within the realm of system development, technology maturity (or<br />

“readiness”) levels dictate the appropriate RDT&E funding categories to be employed, and<br />

determine whether progression into advanced development or production is warranted.<br />

Technology Readiness Levels (see Table 4 below) are measures used to assess the<br />

maturity of evolving technologies prior their incorporation into a system. This characteristic<br />

can be viewed as addressing both timeliness and customer quality-of-use or degree of<br />

technical performance. Usually, when new technologies emerge, they are not suitable for<br />

immediate application. Both hardware and software typically go through a process of<br />

experimentation, refinement, and increasingly rigorous testing until they are considered<br />

mature enough to be applied by end-users in military applications. The scale below is now<br />

used by the DoD to assess maturity before the Department commits to further investments<br />

in technology. This paradigm correlates well to a scale of increasing certainty or declining<br />

uncertainty. For example, depending on a trade-off between urgency of the requirement and<br />

cost, it may be desirous for technology to be at a 6 or 7 rating on the scale before<br />

commencing an advanced development (system-level development and demonstration)<br />

program.<br />

∗ Air Force Instruction 10-602 defines their Quick Reaction Capability (QRC) procedures for “any system or<br />

equipment that will or must be deployed (dictated by mission requirements) in a period of time that does not<br />

allow for routine planning, budgeting, and procurement. Deployment may occur with less than a complete<br />

support package. However, special provisions shall be made to effect lifecycle support.”<br />

=<br />

==================^Åèìáëáíáçå=oÉëÉ~êÅÜW=`ob^qfkd=pvkbodv=clo=fkclojba=`e^kdb====- 256 -<br />

=<br />

=

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!