Change Management and Configuration
Management
April 24, 2013
James Morse
SE Manager 2 @ Newport News Shipbuilding
james.e.morse@hii-nns.com
Introduction
James (Jim) Morse
Education
AS Marine Engineering – Maine Maritime Academy
BS Industrial Engineering – University of Southern ME
BS Eng Mgt – The George Washington University
Pipefitter Apprentice – GD Marine Systems – Bath Iron Works
Career
Lobsterman / Commercial Fisherman – 1984 -1987
General Dynamics Marine Division - Bath Iron Works – 1987 - 2000
Manufacturing, Production, Engineering, Warrantee Engineering, Planning Yard, Program Office (LPD-17 Project)
Newport News Shipbuilding 2000 – 2007 / 2011 – Present
Systems Engineering
ECS-Federal (OAK Management, Inc) – 2007-2011
Engineering Technology Directorate / Software Development
Fun
Running/Racing, Home Projects, Family & Friends, Travel Talking point in red font
Agenda
Why Perspective Necessity
Configuration Management and Change Control Change Management
Light Bulb Moment INCOSE / PMI
My Problem / Your Problem Our Problem
More than just perspective
Why that question
Perspective
Particular evaluation of something
a particular evaluation of a situation or facts, especially from one person's point of view
Measured assessment of situation
a measured or objective assessment of a situation, giving all
Is change management necessary due to the
need to accurately manage the configuration of
an item?
Is configuration management necessary due to
the need to manage change imposed upon an
item?
ULTIMATELY YES
Then are there two plans for a project,
Configuration Management
A process that establishes and maintains consistency of
a product's attributes with its requirements and product configuration information throughout the product's life cycle. (EIA)…..or….
A discipline applying technical and administrative
direction and surveillance to (1) Identify and document the functional and physical characteristics of a
configuration item, (2) Control changes to those characteristics, and (3) Record and report change processing and implementation status……or…
Configuration Management is primarily a Version Control System for the Product of the Project
Fundamentals of Configuration Management
Configuration Identification Configuration Change Control Configuration Status Accounting Configuration Audits
Systems Engineering activities rely on product configurations being known and controlled
Configuration Management Plan
A Configuration Management plan documents how
configuration management will be performed. It defines those items that are configurable, those that require formal change control, and the process for controlling changes to such items.
Change Management
A generic procedure to manage all kinds of changes
on the project. You should have a Change
Management Plan to manage how changes will be handled – how will the changes be evaluated in terms of the impact on schedule, cost, scope, etc., how will change requests be created, who approves them, where will they be documented, and how will changes be managed through out the life cycle of the project. It goes beyond the product specifications.
Change Management Plan
A Change Management Plan documents how
changes will be monitored and controlled. The plan defines the process for managing change on the
Basically, a Change Management Plan is a
generic plan that guides the Project Manager in
terms of making any kind of change on the
project, specially the ones that can impact the
baselines (scope, schedule, cost baselines),
whereas, a Configuration Management Plan
guides Systems Engineers in making changes
which are specific to the Product
The Difference:
As an example, we are in the midst of undertaking
a project that is developing a product:
All the work that is done as part of this project is
considered the “process”, which is used to create the “product” of the project.
The change management plan oversees how any change to the “process” should be done.
The configuration management plan oversees how any change to the “product” should be done.
So where do we go from here……
What does it all mean…….
Learning Moment
INCOSE and PMI
Similar AND varying perspectives on a variety of
issues such as:
Leadership
Negotiation
Communications
Collaboration/teaming
Sustained focus on mission
Risk management
Change Management
PMI and INCOSE
Vested interest in Program successes
Similar principals and fundamentals in
their approach to program operations
Independent organizations developing
conceptual and implementable
management solutions to program controls (among other things)
Technical v. Cost/Schedule/
Scope
LPD 17 Program Example
Key word “Scope”
Changes to the “Scope” were
considered under the auspices of the Program Management Team
“My” Problem / “Your” Problem
Change Management Plan
Program Management Responsibility?
Systems Engineering Responsibility?
Configuration Management Plan
Program Management Responsibility?
Systems Engineering Responsibility?
I
initially
argue Change Management is PM
responsibility and Configuration
Management is SE responsibility.
Cost/Schedule/
Technical
“Technical” replaces Scope – (LPD17 (PM) vice CVN77 (SE))
Commonality within
process, practices and principals
Bridging the gap
between INCOSE and PMI (website) Change Management and Configuration Management is a microcosm of the bigger picture
Subset of “Bridging the Gap”
PM Processes SE Processes Change Management Plan Configuration Management Plan “Our” Problem
Stakeholder interest is addressed for any project through the application
of both INCOSE and PMI processes, practices, and principals (P3) Both believe we share these common themes:
Delivering value and benefit to customers and/or end users;
Integrating the required experience, knowledge and roles to successfully
achieve objectives and complete initiatives; and
Functioning effectively in a more complex environment where program
requirements and outcomes are not clearly defined or have numerous components to manage.
I conclude that Program Management (PMI) AND Systems
Engineering (INCOSE) need to work in concert in the Change Management and Configuration Management arena. Both have vested interest in the success of each.
Change Management is ultimately a Program Management responsible
“function” and Configuration Management is a Systems Engineering “function” with a sub-set of CM being change control of configuration items (and their associated configuration documentation).
Both PM AND SE principals need to be considered when developing
both the Change Management Plans and the Configuration Management Plans for a program.
OPEN FORUM
DISCUSSION
DESSERT?
Reference Material
ANSI/EAI –649 “National Consensus Standard for Configuration Management”
IAQG 9100 “Quality Management System”
ISO 10007 “Quality Management Guidelines for Configuration Management” MIL –HDBK-61A“Configuration Management Guidance”
MIL-STD-973 (obsolete/but available)“Configuration Management” PMBOK Guide – 5th Edition