1 / 9

The Path to IC Transformation

The Path to IC Transformation. Gathering the Necessary Disciplines. Standards – Doing it Well. Mitigating the standards gap in System Engineering Practice. The Standards Challenge. Stated Need: Develop IC community technical and management standards for existing and new capabilities.

sela
Download Presentation

The Path to IC Transformation

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. The Path to IC Transformation Gathering the Necessary Disciplines

  2. Standards – Doing it Well Mitigating the standards gap in System Engineering Practice

  3. The Standards Challenge • Stated Need: Develop IC community technical and management standards for existing and new capabilities. • Why is this a problem? • Why are existing resources inadequate? • Do we understand the scope and focus? • What is the answer?

  4. The Problem • IT systems don’t work, cost too much, and are riding a technology rocket. • Policy has committed us to design using ever increasing complexity to attain illusive goals of interoperability, information sharing, standardization, situational awareness, and, the ever present design to cost. • Standards are frequently cited as part of the solution. Generals Hayden, Meyerrose, et al.

  5. The Data • Standards viewed as a class can provide: • Standardization • Supercharged modules of very specific and detailed knowledge • Interoperability blueprints • Management methods and tools • A creation process for best solutions • Enforceable legal and contractual agreements • Large scale cost Reductions • The broad scope of the standards process suggests that it should be treated as an independent systems engineering activity at the same level as strategic planning, requirements, and architecture.

  6. The Questions • If standards define much of our technical designs- and they do- why are we not placing more resources in creating, understanding, learning from, and employing them in our systems? • If standards provide a primary mechanism for providing technological progress in the U.S., why are there so few U.S. Government resources and employees assigned to this area?

  7. The Status Quo • The Defense Standards Program –Primarily a logistics focus since the Perry decision to radically downsize the MIL SPECS system in 1994. • Defense Information Systems Registry (DISR) • A committee driven compendium of mandated IT standards. • US Government - Flushed standards responsibility from the NIST and assigned promotional activities to Commerce Department. • The Intelligence Community -Missing in action, part 1

  8. Progress • Three steps to recovery • EXECUTIVE AWARENESS - People have to know. • ESTABLISH A PROFESSIONAL STANDARDS CADRE - People have to be professional about this. • ELEVATE STANDARDS ACTIVITIES TO THE ORGANIZAIONAL/PRIORITY LEVEL OF OTHER SYSTEM ENGINEERING PROCESSES IN THE DoD/IC. - If its not considered important, it doesn’t get funded.

  9. Summary • Standards are being handled poorly throughout the Federal/DoD/IC hierarchy • This needs to change if we are to realize the badly needed and ambitious IC transformation goals. • INCOSE is in a position to help because it can explain and emphasize the important role of Standards in creating successful systems.

More Related