All material on this web site is copyrighted by Honourcode, Inc. 1999-2017.

Configuration Management for In-Service Engineering Agents (ISEA)

Today’s systems do not stand alone; each system fits within an increasingly complex system-of-systems, a network of interconnection that virtually guarantees surprise behavior. In addition, systems are acquired using COTS and streamlined, performance-based acquisition methods that virtually guarantee configuration problems. Yet this network of operational systems demands as never before that the system configurations be properly managed.

The course is a comprehensive treatment of Configuration Management (CM) with multiple exercises to practice the learned methods using real-world, hands-on challenges. It is structured around the five essential CM processes of EIA-649B:

  • Configuration Management and Planning
  • Configuration Identification
  • Configuration Change Control (w/ Baseline Management)
  • Configuration Status Accounting
  • Configuration Verification and Audit

For each process, there is full discussion of how that process interacts with system development, integration, test, operations, and support throughout the system life cycle, with an emphasis on the viewpoint of in-service engineering. Aspects and consequences of software and COTS usage are also emphasized, particularly in the area of change control during in-service engineering.

Register here to receive more information on our courses.

Attend this course if you are:

  • Responsible for configuration management of an in-service system
  • Concerned about the systems’s technical success
  • Interested in how to better handle COTS and software
  • Looking for practical methods to use in your

The course is aimed at professionals in:

  • Configuration management
  • Logistics support
  • Program managers
  • Systems engineering
  • Test engineering
  • Maintenance
  • Others who participate in managing and supporting complex systems.

This course can be scheduled at your facility. Contact us at

Course Topics

Context of CM

• Why CM is crucial to the success of a lifecycle program
• CM in the context of the program lifecycle
• The relationship of CM to other disciplines
• CM issues with COTS; the control cycle from the viewpoint of the vendor
• How CM changes in moving from development to in-service
• Exercise #1: Examining CM Problems
• Software CM and its special considerations
• Commercial practices for software CM
• Agile development and its impacts
• Firmware CM strategies
• Sound practices for software and firmware; pitfalls

Planning a Well-Structured CM Program

• Tailoring the CM requirements
• The five core elements of CM
• Level of detail required for CM
• Special planning considerations for COTS
• The relationship of Navy CM to COTS vendors and their systems
• Special planning considerations for software and firmware
• Considerations for software COTS
• The relationship of CM to program management; the CM Plan; key program and CM milestones

Configuration Identification

• How CM fits into the development lifecycle
• What is product information and what form does it take?
• Selection of Configuration Items in a complex system
• Exercise #2: Identifying CIs (Swiss Army Bicycle)
• COTS configuration items; following the vendors while selecting for positive control
• Identifying effective software CIs during a changing development environment
• Firmware CIs in microcontrollers, ROMs, and FPGAs
• Requirements allocation and the CM definition of system components
• Nomenclature assignment; numbering of parts and documents
• Nomenclature differences for ordnance vs. electronics

Configuration Baseline Management

• Purpose of a baseline; types of CM baselines
• Contents of the different baselines, with lists of typical documents in each
• How to control the changes of a baseline while maintaining an effective baseline
• COTS baselines; how to maintain a baseline on a commercial item
• Software baselines and change control; software libraries; dynamic change
• Firmware baselines; forms of documentation
• Requirements traceability as used in CM

Configuration Change Control

• Baseline change during operations and support; controlling a configuration while it changes; examples of changes
• Engineering Change Proposals (ECPs) and the Form 1692 in depth; block by block directions on how to use the form and control ECPs
• Controlling COTS change issues; vendor configuration changes (documented and undocumented); re-selection of COTS for replacement; re-procurement for ongoing supply
• Software change in a dynamic environment; controlling the changes while allowing forward improvement of a system
• Documentation of firmware changes
• Configuration Control Boards; membership, roles, responsibilities
• Class 1 and Class 2 Engineering Change Proposals (ECPs) and their different handling
• The effect of ECPs and SCDs on the baselines
• Exercise #3: Change Control (Gladiator Missile Program)

Configuration Status Accounting

• Why keep track of CM status? – purpose and benefits
• Methods to track CM artifacts; flow of information
• Exercise #4: CSA Metrics (Gladiator Missile Program)
• COTS status accounting; tracking the vendor changes
• Software and firmware status accounting
• Principles for data integrity; types of data and best methods for each
• Business rules to allow changing of the data
• Version control in a complex system; proper application of the right version to the system

Configuration Verification and Audit

• Purpose and benefits of verification/audit
• Functional Configuration Audits
o Verification methods; source information; the Requirements Verification Matrix
o Performance verification; design verification
• Physical Configuration Audits
o Ensuring compatibility between the system and the documentation
• Verification and audit of COTS
• Verification and audit of software and firmware
• Certification against external standards
• Internal and formal audits

Policies and Issues in Acquisition that Influence CM Practice

• Variations in Acquisition Program Development Lifecycle and Development Models
o Waterfall
o Incremental Development
o Spiral Development
• Government Cost Austerity and the Reduction in Total Ownership Cost
• Systems of Systems

Special Topics in CM

• Special Issues in Differing Development Lifecycles
• Open Systems
• Online Configuration Control Boards
• Review of ONE BOOK processes as an example of CM tailoring

Continuing Education: This course qualifies for 1.4 CEUs or 14 PDUs

Qualified Instructors for this course

Dr. Eric Honour, CSEP, INCOSE Fellow, and former INCOSE President, has been in international leadership of the engineering of systems for over 20 years, part of a 40+ year career of complex systems development and operation. His energetic and informative presentation style actively involves class participants. He was the founding Chair of the INCOSE Technical Board in 1994, and served as Director of the Systems Engineering Center of Excellence (SECOE). He was selected in 2000 for Who’s Who in Science and Technology and in 2004 as an INCOSE Founder. He is on the editorial board for Systems Engineering. He has been a successful entrepreneur, systems engineer, engineering manager, and program manager at Harris Information Systems, E-Systems Melpar, and Singer Link, preceded by nine years as a US Naval Officer flying P-3 aircraft. He has led or contributed to the development of 17 major systems.. Dr. Honour has a BSSE (Systems Engineering) from the US Naval Academy, MSEE from the Naval Postgraduate School, and PhD from the University of South Australia based on his ground-breaking work to quantify the value of systems engineering. Dr. Scott Workinger has led innovative technology development efforts in complex, risk-laden environments for 30 years in the fields of manufacturing (automotive, glass, optical fiber), engineering and construction (nuclear, pulp & paper), and information technology (expert systems, operations analysis, CAD, collaboration technology). He currently teaches courses on program management and engineering and consults on strategic management and technology issues. Scott has a B.S in Engineering Physics from Lehigh University, an M.S. in Systems Engineering from the University of Arizona, and a Ph.D. in Civil and Environment Engineering from Stanford University.

Page last modified 5 Sep 17