John Scott: Mil-OSS


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Open source optionsOpen source software implementations creates options for the government:Don’t have to be locked into single technology vendor with forced license requirements (per seat, CPU, etc. )Open source can be a powerful negotiating point with vendors to decrease costs
  • John Scott: Mil-OSS

    1. 1. WHY  THE  GOVERNMENT  IS  EVOLVING  TO  ‘OPEN’  2013  Conference     March  5,  2013   John  Scott     @johnmscott  
    2. 2. 1.  Why  is  the  gov  opening?  §  People  §  Technology  §  Process  
    3. 3. Trends:  People  Employees  &  Citizens:  §  Impatient  (generational)  §  Raised  on  open  and  free  development  tools/ sites/portals  Developers:  §  Good  ones  are  lazy  §  Good  ones  don’t  want  to  resolve  completed   problems  
    4. 4. Trends:  Technology  §  Need  for  Speed   ú  Software  development  &  change  §  Tooling   ú  Best  software  development  tools  mainly  OSS   ú  OSS  easiest  available    §  Commoditization  /  maturity  of  OSS  
    5. 5. OODA  Loop­‐content/uploads/2011/01/New-­‐Picture-­‐1.png  
    6. 6. OSS  inside  the  Closed  Tech   OODA  Loop   Cycle  moves  faster  for   open  technologies  
    7. 7. What’s  Special  becomes   Commodity    Commercial     Software   ISR   Software  /   Hardware   C4   Software  
    8. 8. Good  Tech  Becomes  Commodity    
    9. 9. Gartner  predicts  that  within  2010  25%  of  the  overall  software  market  will  be  Free  Software-­‐based,  with  roughly  12%  of  it  “internal”  to  companies  and  administrations  that  adopt  Free  Software.  The  remaining  market,  still  substantial,  is  based  on  several  different  business  models,  that  monetize  the  software  using  different  strategies.  Gartner  Group,  “Open  source  going  mainstream,”  2006  
    10. 10. Example  Savings  10 Source:  OSDL,  Stuart  Cohen,  GOSCON  2007  
    11. 11. 11
    12. 12. 2.  Where  is  the  Gov?  §  3  stages:  Use,  modify  &  create  §  Open  data:  shock  troops  of  openness  §  OSS  the  logistics/supply  train    
    13. 13. Open  Continuum     Gov  Data     DATA   about  here   Full  Access     ACCESS   INTERACT   COMBINE   &  Open  Closed   USE   MODIFY   CREATE     TO     RELEASE   Gov  Tech     about  here   TECHNOLOGY  
    14. 14. People  &  Tech  Gov  Employees  §  Workforce  aging/retiring  and  not  being   replaced  at  same  rate  due  to  costs  Technology  §  Lots  of  Legacy  systems  and  code  
    15. 15. Process  (the  bigger  problem)  §  Policy,  Regulations,  Law  §  Hardware  vs.  Software  &  Acquisitions   ú  WW2  &  software  development  and  tools    
    16. 16. Key  Issues  in  Technology  Acquisitions  Key  Point  #  1:  Measure  Twice,  Cut  Once  Acquisitions  Processes  based  on  one  premise  -­‐  Measure  Twice,  Cut  Once  -­‐   Industrial  vs.  Digital      /      Steel  vs.  Bits      /      Land  Warfare  vs.  Cyber      Key  Point  #2:  Knowledge  Monopolies  Hardware:  Enabling  industry  to  have  commercial  rights  to   hardware  technologies  (which  requires  factories,  etc.)  works    Software:  enabling  a  knowledge  monopoly  limits  the   dissemination  of  knowledge  about  defense  systems     Gov  Intellectual  Property  Regime  based  in   20th  (19th?)  Century  
    17. 17. 4  x  6  foot  wall  chart  
    18. 18. Government  Software  IP  Knot   Tactical  IP:   Good  at  tactical  management  of   intellectual  property  on  a  programs   basis     Strategic  IP:   Bad:  No  DoD  strategic  policy  on  how   the  software  ecosystem  should   function  for  us:  i.e.,  how  (as  an   enterprise)    should  software  IP  rights   be  exercised  in  DoD  
    19. 19. * USER CANNOT CLEAN, FIX, MODIFY, OR UPGRADE *Non-starter for the military, but we allow in software?
    20. 20. LAW  §  House:  Issa  IT  Reform  Bill  §  Senate  2012  Bill   ú  Supported  use  of  OSS  
    21. 21. POLICY    §  DOD  CIO,  OMB,  NASA,  CFPB…  §  New  @  NIH  !   ú  NCIP’s  Open-­‐Development  Strategy  Enables   Community-­‐Driven  Cancer  Informatics  Software   Development   ú­‐open-­‐development-­‐ strategy-­‐enables-­‐community-­‐driven-­‐cancer-­‐informatics-­‐ software-­‐development/  
    22. 22. DoD:  OSS  OK  to  use,  it  won’t  hurt   22  
    23. 23. Open Source Software! =! "software for which the human-readable source code is available for use, study, re-use,modification, enhancement, and re-distribution by the users of that software"*! *Reference: 16 October 2009 memorandum from the DoD CIO, "Clarifying Guidance Regarding Open Source Software (OSS)"
    24. 24. Open  Open  Gov  DoD:  Clarifying  Guidance  Regarding  Open  Source  Software16  October  2009  
    25. 25. Other  .gov/.mil  efforts  §  Dept  of  State:  Tech@State  on  Open  Source  §  NASA  Open  Source  Software  Day   ú­‐open-­‐source-­‐proceedings    §  SPAWAR/Atlantic:  Open  Source  Day  §  Veterans  Affairs  Vista  
    26. 26. 29  
    27. 27. OSFA  Reportcard  
    28. 28. 3.  Where  the  gov  will  end  up?  3  things  not  to  do  in  public:  1.  Sex  2.  Math  3.  Experimentation     ú  Modern  software  built  this  way   ú  Open  data  requires  maturity  and  public   education    
    29. 29. People  §  Aging  workforce  §  Younger  gov’s/contractors  coming  in  with     turnover    
    30. 30. Tech  §  Churn  continues    §  Opening  continues    §  Enterprise  Automation   ú  Simplify  systems  deployment  §  Abstraction    
    31. 31. Process  Prediction    §  More  outsourcing  to  save  money   ú  Agencies  to  focus  mission  vice  IT  §  Capability  will  be  the  Service  
    32. 32. Off-­‐the-­‐Shelf  Software  Maintenance  Strategies     36  
    33. 33. How  to  help?  Strategy  §  CIOs:  Focus  on   ú  Increasing  enterprise    options   ú  Enterprise  automation    §  Educating  COTRs  §  Require  review  of  OSS  solutions   ú  Already  a  req,  but  ignored     ú  At  least  use  to  negotiate  
    34. 34. Wrap-­‐up  
    35. 35. Key  Points  §  Open  Source  is  not  FREE  §  Must  (somehow)  fund  and  sponsor  development   to  keep  the  technology  fresh,  evolving  and  up-­‐to-­‐ date  §  Either  through  subscriptions  or  services    
    36. 36. Software  is  a  Renewable  Civilian/Military  Resource    (and  we  paid  for  it)     §  Software  has  become  central  to  how  the   government  conducts  missions       §  For  reliance  on  software  to  be  a  strength,  the   government  must  pursue  an  active  strategy   to  manage  its  software  portfolio  and  foster   an  internal  culture  of  open  interfaces,   modularity  and  reuse   40  
    37. 37. How  to  Build  a  Capability  Running Open Technology DevelopmentProjectsStep 1: Determine reuse optionsStep 2: Identify the Projects to be EstablishedStep 3: Choose and Apply a Common LicenseStep 4: Establish GovernanceStep 5: Establish CollaborationStep 6: Create Project Technical DirectionStep 7: AnnouncingContinuously Review Steps 1-7 Rules of the Road: 1.  Don’t Fork OSS Solely for Government Use 2.  Open Standards 3.  Continuous Delivery 4.  Simplify Intellectual Rights Management
    38. 38. OSS  Winning…   Its  just  not  evenly   distributed     (across  government)  
    39. 39. Thanks!  OSS  Maturity:  Certified  to  DoD  5015.02  standard  for  records  management  
    40. 40. MILITARY OPEN SOURCE SOFTWARE(MIL-OSS)HTTP://MIL-OSS.ORGJohn Scott, RadiantBlue Tech., 240.401.6574