ACQUISITION TRANSFORMATIONS

1
ACQUISITION TRANSFORMATIONS

• MN3309 Session 19
• Prof. Mark Nissen

2
Agenda

• Process Redesign Review
• DoD vs. Commercial S/W Acquisition
• Software Critical Best Practices
• C-SAWS Redesign Transformations
• Software Acquisition Research
• Summary

3
Process Redesign

• Central analytical process in BPR
• Parallels IS analysis design
• Analytical, upstream activities
• Match tech with requirements
• Key to implementation maintenance
• Two major approaches
• Greenfield (aka blank sheet of paper)
• Baseline transformation (as-is --gt to-be)

4
Aircraft System Design Model
Configuration Measurement
Wing Area
System
Thrust
Plastic
FBW
Performance - Speed - Altitude - Maneuverability
Weight
Environment
5
Process Redesign Model
Configuration
Performance
Environment
Transform
Strategy
6
Redesigning Reengineering
Select
Implement
Model
Measure
Rqmts/Test
ID select process
Diagnose
Generate
Match
Inner loop like medical exam outer loop like
product design?
7
Redesigning Reengineering
Select
Implement
Model
Measure
Test
ID select process
Diagnose
Generate
Match
8
Taxonomy of Process Pathologies

• 10 classes of common pathologies
• Problematic process structure (linear flows)
• Bureaucratic organization (job specialization)
• Fragmented process flows (process friction)
• IT infrastructure (manual, paper-based)
• Checking approach to quality (many reviews)
• Centralized authority (long decision chains)
• Under-utilized human potential (training v ed)
• Inhibitive leadership (directive supervision)
• Centralized information (central DB arch)
• Deficient core competencies (IT expertise)
• 2-tailed test

9
Pathologies Best Practices

• Hierarchy of learning
• Pathologies - experience problems
• Process flaws, faults, errors, inefficiencies
• Lessons learned
• College of hard knocks
• Must struggle before learning
• Virtual learning? SBA?
• Best practices - transformations
• Learn from successes failures
• Benchmark against best practices
• Innovation --gt better than the best

10
Taxonomy of Redesign Transformations

• 7 classes of common transformations
• Workflow reconfiguration (de-linearization)
• Information technology (shared DB system)
• Organizational design (case manager)
• Human resource (team-based compensation)
• Information availability (informate agents)
• Inter-org alliance (supplier-run inventory)
• Management culture (ESOP)
• Examples from readings?

11
DoD vs. Commercial Software Acquisition

• DoD industry have 3 S/W classes
• DoD can learn from industry
• Many com practices FAR-consistent
• Key com vs. DoD differences?
• Should not simply copy com practice?
• DoD pathologies transformations?

12
777 vs. C-17

• Planes fielded at same time
• Boeing 777 (4 years)
• Focus on cost, schedule performance
• Deferred use of advanced technology
• CATIA design - virtual pre-assembly
• McDonnell-Douglas C-17 (16 years)
• Focus on performance (C-X)
• Underestimated integration problems
• Paper design - mockups prototypes
• Pathologies transformations?

13
NTH Commercial Streamlining

• New Training Helicopter
• Streamlined using commercial methods
• Adapted commercial helicopter
• Backed-off from expensive requirements
• Used commercial standards
• Requested evaluations less testing
• Deleted inapplicable RFP clauses (listed)
• NTH represents baseline for further
  streamlining - non-combat aircraft

14
NTH Commercial Streamlining

• Still more cumbersome than com
• Required 7 years (vs. 3 months)
• 50 people in PMO (vs. 5-7)
• 7 volumes of proposal data (vs. 1-2 pp.)
• Non-value-added plans
• Key differences
• FAR and such (socio-economic, TINA)
• Specifying requirements as critical
• Proposal paperwork protest preparation
• Pathologies transformations?

15
Software Critical Best Practices

• SPMN examining best practices
• Cutting-edge companies dullards
• Focus on time to market
• Cost unimportant?
• Motorola Iridium
• Increased S/W complexity 3x
• Reduced defects 3x, CT 10x (OOM)
• Defense software
• Financial disincentives to productivity?
• Raytheon tripled productivity?

16
Software Critical Best Practices

• Innovation vs. best practices
• Floodlight vs. laser beam?
• Dramatic vs. incremental?
• How to explain OOM improvement?
• SPMN 16 point improvement plan
• Product integrity
• Product construction
• Project control
• Process improvement? (CMM L-5!)

17
Software Critical Best Practices

• Product integrity
• Inspect requirements design
• Manage testing as a continuous process
• Compile smoke-test frequently
• Project construction
• Life cycle CM
• Manage trace requirements
• System-based software design
• Data database interoperability?

18
Software Critical Best Practices

• Project construction (cont)
• Define control interfaces
• Design twice, code once
• Assess reuse risks costs
• Project control
• Adopt risk management process
• Empirical cost/schedule estimates?
• Manage through metrics

19
Software Critical Best Practices

• Project control (cont)
• Track earned value
• Timing of event horizons?
• Track defects vs. quality targets
• Treat people as 1 resource

20
Mil-Com Pilot Program

• Integrated mil-com industrial base
• Take advantage of com volume
• Flex mfg to insert mil production items
• TRW F-22 avionics equipment
• Some units by hand from TRW mil
• Some units on automated assembly line
• Save 40 cost meet F-22 rqmts
• Extend to other programs (clauses)
• Pathologies transformations?

21
JASSM Acquisition Planning

• Joint Air-Surface Standoff Missile
• Follows TSSAM termination (86-94)
• JSOW cousin
• 400-700k unit cost (FY95)
• Integrate with 6 aircraft, 2 services
• Acquisition reform com practices
• Cost rank equal to technical performance
• Partnership with industry, OTS technology
• Minimize mil specs, gov oversight
• Pathologies transformations?

22
Product-Line Development

• Product line
• Collection of individual products
• Engr similarities - common designs
• Mfg similarities - common tooling
• User similarities - common usage
• Each product is a refinement?
• Engineer only the deltas?
• Benefits limitations?
• Pathologies transformations?

23
C-SAWS Redesign Transformations

• Taxonomy of redesign transformations
• Workflow reconfiguration (de-linearization)
• Information technology (shared DB system)
• Organizational design (case manager)
• Human resource (team-based compensation)
• Information availability (informate agents)
• Inter-org alliance (supplier-run inventory)
• Management culture (ESOP)
• C-SAWS potential transformations?

24
21st Century S/W Engineering

• Lowry 1991
• Look at future S/W engineering
• KBSE S/W as art gt engr discipline
• Transformational programming
• Prototype, validate mod _at_ spec level
• Automatic program synthesis
• Benefits limitations?
• Pathologies transformations?

25
VISTA

• Virtual Software Acquisition
• USAF Blue Ribbon Panel
• Scacchi Boehm (1998)
• MS technology for S/W acquisition
• Feasibility Analysis Model (FAM)
• Feasibility analysis of requirements
• Check offerors architectures
• Iteratively hierarchically use throughout
  development process
• Pathologies transformations?

26
Intelligent Acquisition Agents

• Government S/W procurement
• Important domain
• Dynamic environment (tech, regs, needs)
• Problematic process
• Supply chain process redesign
• Integrate buyer-seller processes
• Virtually re-intermediate process
• Pathologies transformations?

27
Summary

• Process redesign
• Medical exam vs. product design
• Taxonomies heuristics
• Key com vs. DoD acq differences
• Many com practices FAR-consistent
• Still some fundamental differences
• SPMN best practices
• Laser beam vs. floodlight
• OOM improvements in software
• S/W acquisition is active research area