Currently viewing the tag: "Strategy"

Download (PDF, 663KB)

We’ve reviewed Chief of Naval Operations Adm. Jonathan Greenert testimony to the House Armed Services Committee.  Admiral Greenert has posted his Navigation Plan for Fiscal Years (FY) 2013-2017.  Key items in the Information Dominance Corps realm within his Sailing Directions are:

WARFIGHTING FIRST –

  • Fully exploit cyberspace and the electromagnetic spectrum as warfighting domains with upgrades to Ship’s Signal Exploitation Equipment and the SLQ-32 surface electronic warfare system, and continued development of the Next-Generation Jammer for airborne electronic warfare.
  • Defend our computer networks, sustain information assurance, develop network operations technology, as well as educate the next generation of cyber operators at the U.S. Naval Academy, Naval Postgraduate School, and Naval War College.

OPERATE FORWARD – While no individual bullet point sites a specific task for the Information Dominance Corps (IDC) the major move to push more ships & forces forward, increase their Operational Tempo, and rotate crews at the edge are major changes.  Thus the IDC importance is built within every bullet point listed.  These changes make the Network and Communication mission sets of the IDC more significant.  It also challenges network availability & integrity while stressing satellite and terrestrial communication pathways with higher traffic loads and most likely a more congested spectrum loading.

BE READY –

  • Improve the “wholeness” of the Aegis Weapons System through data link and software upgrades while adding the Shipboard Self Defense System to more non-Aegis ships, such as amphibious assault ships.
  • Sustain Fleet Synthetic Training to provide a wider range of complex and demanding simulations than possible in the field, while conserving operating expenses where appropriate.

[via Navy.mil]

Make sure to review the CNO’s 2012 update in his CNO’s Postion Report for 2012!

Incoming search terms:

cno sailing directions 2013, cno navigation plan, cno sailing directions 2012

Download (PDF, 1.09MB)

The new U.S. CIO, Steven VanRoekel, has updated the initial 25 point plan that was released in 2010 by the first U.S. CIO Vivek Kundra.

Some of the main challenges have been:

  • IT Reform #5 – Stand-up contract vehicles for Commodity IT services
  • IT Reform #17 – Work with Congress to create IT budget models that align with modular development
  • IT Reform #20 – Work with Congress to consolidate Commodity IT spending under Agency CIO
The items that will be focused on in the next 12-18 months (numbers are referenced from original plan for continuity):
  • 2. Create a government-wide marketplace for data center availability
  • 8. Scale IT program management career path
  • 12. Enable IT program manager mobility across government and industry
  • 16. Reduce barriers to entry for small innovative technology companies
  • 23. Rollout “TechStat” model at the bureau level

Pretty nice to have a 25 point plan to walk into the job with and review then work on the remainders while you formulate the next goals.

There is also discussion on the launch of FedRAMP.  The goals of which are to:

  • Accelerate the adoption of secure cloud solutions through reuse of assessments and authorizations
  • Increase confidence in security of cloud solutions
  • Achieve consistent security authorizations using a baseline set of agreed upon standards to be used for Cloud product approval in or outside of FedRAMP
  • Ensure consistent application of existing security practices
  • Increase confidence in security assessments
  • Increase automation and near real-time data for continuous monitoring

[via CIO.gov]

Incoming search terms:

chief tecumseh gedicht

GDE Error: Error retrieving file - if necessary turn off error checking (404:Not Found)

How do you mitigate the risk to your Information Technology supply chain?  At what level is it being addressed and assessed (CTO, CIO, COO, CBO, CEO)?  How are you assured that the keyboard, mouse, cables, PC, laptop, tablet, smartphone, and their sub-components and then their software are trustworthy?  It’s not simply fake Military parts from China or other countries it is a much larger problem then that.

You’d have no idea this was happening to you because we’re usually the one operating as the user.  And users often have some reason to balk at the time it takes to provide new equipment or allow a new piece of software.  Now the Security and Acquisition folks have plenty to apologize for but you may want to cut the a bit of slack.  It is a very difficult task, challenging environment, and is very rarely rewarded with anything but negative reviews and comments when things go alright or much worse if things go wrong.  

With all that said if you were in there shoes in this SH-60 case how would you handle it?  What would you do to prevent something like this in a global capitalist economy and supply chain?  And what would you do in the current environment where resources are very sparse?

[via The White House]

Update (22 MAY 2012) – Review the U.S. Senate Armed Service Committees’ report on the Inquiry into Counterfeit Electronic Parts in the Department of Defense Supply Chain (21MAY2012).

Set your Twitter account name in your settings to use the TwitterBar Section.