Osh summit talk_v1.5

@thebarkleynow

@ssayer

New Methods in Systems Engineering

Copyright © 2010, The MITRE Corporation. ALL RIGHTS RESERVED. Approved for unlimited distribution no. 10-3761.

ARx: Almost Ready To Anything

Systems Engineering

Systems Engineering (SE) – An interdisciplinary approach encompassing the entire technical effort to evolve and verify an integrated and total life cycle balanced set of system, people, and process solutions that satisfy customer needs.

ANSI/EIA-632-1999, 1999, “Processes for Engineering a System”ISO 15288, Nov. 2002, “A Guide for the Application of ISO/IEC 15288 System Life Cycle”IEEE 1220, 1998, “IEEE Standard for Application and Management of the Systems Engineering Process”IEEE 15288, 2004, “Systems and Software Engineering – System Life Cycle Processes”The International Council on Systems Engineering (INCOSE), 1990, http://www.incose.org

Systems Engineering Fundamentals, 2001, Defense Acquisition University

Systems Engineering Guidebook for ITS, v3.0 pp. 3.9.4, U.S. Department of Transportation

DoD Program System Engineering Management Plan (SEMP)

DOD Acquisition Lifecycle

Integrated Defense Acquisition, Technology, and Logistics Life Cycle Management System, Version 5.3.4, 15 June 2009. Defense Acquisition University, https://acc.dau.mil/ifc/

Almost Ready to Fly (ARf)

Almost Ready to Print (ARp)

Kit Systems

Almost ready to drive (ARd)(from macminter on flickr)

Power

Electrical

SoftwareHardware

Open Physical Components (e.g. brackets, mountings, enclosures)

Open Source Hardware (e.g. electrical components, sensors, microcontrollers)

Open Source Software

M A T U R I T Y

•Community

•Licensing

•Governance

•T

ools

•Capability

•…

Open Source Systems

Open Power Supply

New Methods

Agile Methods

Open Source Software

Open Hardware

• Agile Software Development, 1993

• SCRUM, 1995

• eXtreme Programming, 1996-1999

• Agile Systems Engineering

• Kit-style replication

The Power of OpenMethods, not products make open models successful

80% of innovations come from user communities because they’re innovating to benefit themselves, as opposed to companies who hope to innovate to sell products.

The [community benefiting themselves] is natural and emergent, the [company hoping to innovate] is a guessing game.

Democratizing Innovation, 2005. Eric Von Hippel, http://web.mit.edu/evhippel/www/books.htm

Community Innovation

Observations on Traditional v. Open S.E.

Open Eng. Traditional Eng.

Requirements Community is defining their own requirements,“good enough” requirements lead to faster delivery

Rigorous customer and stakeholder driven requirements process

Architecture High quality “artisan” development, refined over time

Carefully planned, designed, costed, implemented, T&Ed

Process Improvement Rapidly upgraded as technology improves

Upgraded only when forced

The Good

The BadOpen Eng. Traditional Eng.

Support Often community provided (wikis, forums, etc.)

Dedicated service personnel and systems

Supply Chain Management & Logistics

Sometimes chaotic configuration management

Dedicated personnel and systems (built-in from beginning)

Integration Partial design, often end user becomes integrator

ICDs, program office coordination

The UglyOpen Eng. Traditional Eng.

Safety “Hobbyist” notation used to sidestep regulation, burden of safety often shifted to end user

Subject to government safety regulations, designed with high safety factors

Quality Control Best effort Quality frameworks and large body of standards

Repeatability Relies on end user to perform complex assembly

Automated processes used to build product

jbarkley@mitre.org ssayer@mitre.orgwww.ohroadmap.org

• Over the next 9 months we will be researching for MITRE:

• Open hardware technology gaps and capabilities

• Evolution of open systems engineering

• We have decided to document this as a public wiki• All are invited to contribute at ohroadmap.org