Transcription
Configuration ManagementBaseline WebinarPresented By: Lisa July for the Digital Enterprise SocietyDISTRIBUTION A. Approved for public release: distribution unlimited.Copyright: J2E Technology, LLC. All rights reserved.10/29/20191
Topic Agenda Instructor Introduction History of our program Learning Objectives Purpose of a Baseline Standard Baseline Types Baseline Procedure Introduction Baseline Procedure Map Baseline Procedure Activities (High-level) Sample Baseline Report Audience Questions10/29/20192
Presenter Introduction Prior Military, U.S. Navy (Data Systems Technician) Information Technology Background Commercial and Government experience Support Desk/SW Coding/ Implementation/Business AdvisorConfiguration Management Experience Lisa JulyVP of Data IntelligenceJ2E Technology, LLC Emphasis in Data Management proceduresFormally Trained Instructor Curriculum Developer ILT (In class and Remote)10/29/20193
History of This Baseline Procedure Problem: Our customer is unable to produce proper Baselines Requirement exists to have them Customer unsure how to proceedSolution: Guidebook Implementation A guidebook was written, tested and approved Using Industry and Government references Included Templates and other Job Aides CM Initiative was started Morphed into a command-wide Program (CM as a service)10/29/20194
Learning Objectives At the end of this webinar, the audience will be able to: Describe the purpose of a baseline Define standard baseline types Identify the activities in the baseline procedure10/29/20195
Purpose of a Baseline To define the configuration of a product at a specific point in time This “snapshot” identifies all data applicable for the specific baseline Configuration Items (CIs) Associated controlled informationOnce released, the baseline is published and should not be modified (data integrity)10/29/20196
Standard Baseline TypesAll baselines must be CCB approved before they can be releasedEstablished during the systemrequirements and design phase andvalidated during the FunctionalConfiguration Audit (FCA). Allocatedbaselines are built from theFunctional baseline and includesadditional derived requirementsand design constraints.Established during thedeployment/operations/sustainmentstages, this baseline is generated fora specific destination. It is built froman approved Product baseline andincludes additional configurationdetails such as the site identifier andactual serial numbers for the shippedproduct.Established in the production stage,this baseline represents the finalproduct configuration that will bedeployed to customers. This baselineis built from an approved InitialProduct baseline and has solidified allaspects of the product and itsdeployment (fully developed producttraced back to requirements,verification reports, operation/trainingdocumentation, etc.). This baseline isverified at the end of the PhysicalConfiguration Audit (PCA).As Installed (Updated)Established during thedevelopment/integrate/teststage, this baseline consists ofthe CIs and controlled itemsassociated with the in-workproduct solution. There can bemultiple Developmentalbaselines created during thisphase, and the first one is builtoff the Allocated baseline (orthe Functional baseline if theprogram or project does notgenerate an allocated d before product designbegins. Functional baselines shouldinclude the following requirements:- Functional- Interface/Interoperability- Verification- Configuration Item Identification- Design restraintsEstablished at the end of thedevelopment/integrate/test stage, thisbaseline consists of the “Build-to” and/or“Code-to” specs for hardware andsoftware, respectively. Productcomplexity can contribute to the numberof Initial Product Baselines generated, andthe first one is built from an approvedAllocated or Developmental baseline. Thisbaseline is verified at the end of theFunctional Configuration Audit (FCA).As Installed Initial ProductBaseline types are established following the Product Lifecycle TimelineAllocated Established during theoperations/sustainmentstages, this baseline isgenerated from the current AsInstalled baseline. Theupdated data could includeany differences documentedduring installation orsustainment (when parts arereplaced, or redlines recordedduring installation, etc.)710/29/2019
Baseline Procedure Introduction Establishing a baseline involves similar elements, regardless of the baseline type We have defined a Procedure Map (see the next slide) which shows: Entry and Exit Criteria Roles and Responsibilities Procedure ActivitiesWhen establishing a baseline, each activity includes: Inputs Instructions Outputs10/29/20198
Baseline Procedure Map10/29/20199
Baseline Procedure: Activity 1 Determine the Baseline to Establish with Appropriate Entry Criteria Inputs Instructions Project Schedule, CM Plan, Baseline Definition & Criteria, Previously ApprovedBaseline (if applicable)Using the input documentation, determine the next baseline to establishOutputs Notification to stakeholders of the To-Be baseline Begin applicable CM Activities Configuration Identification (which generates the Configuration Item (CI) List/hierarchy) Configuration Control (which generates released artifacts)10/29/201910
Baseline Procedure: Activity 2 Generate Preliminary Baseline Report Inputs Approved Configuration Item (CI) List, hierarchy, and released artifactsInstructions The CM Manager compiles this preliminary baseline to ensure all items that arepart of the baseline are created or revised, approved, and ready forimplementation If items are still being processed, the CM Manager works with the change owner(s)to ensure those items are completed in time for the next activityOutputs Preliminary Baseline Report, released CIs and controlled items in the CM System10/29/201911
Baseline Procedure: Activity 3 Conduct Baseline Verification Inputs Preliminary Baseline Report, released CIs and their controlled items, projectauthorized verification proceduresInstructions The Configuration Verification Team will review the released artifacts to confirmthey satisfy their documented requirements If establishing an Initial Product or Product Baseline, the verification team willperform its duties during a Functional or Physical Configuration Audit (FCA or PCA),respectively Any other baseline would be validated using the project’s verification procedureOutputs Verification Team results10/29/201912
Baseline Procedure: Activity 4 Adjudicate Discrepancies Inputs Verification Team resultsInstructions The CM Manager delivers the verification results to the product team, who willresolve any discrepancies found by the Verification Team This may include updating artifacts following the Configuration Control procedure. The CM Manager will monitor these activities, to ensure all discrepancies areresolved and any necessary actions are completed, and generate an updatedPreliminary Baseline ReportOutputs Updated Preliminary Baseline Report10/29/201913
Baseline Procedure: Activity 5 Review Baseline Inputs Preliminary Baseline Report, Verification Team results, CCB Agenda/ScheduleInstructions The CM Manager presents the inputs to the CCB for review. The CCB provides one of the following decisions: Approved, Deferred, Rework RequiredOutputs The CM Manger either publishes the final Baseline Report (if approved), assigns thenecessary actions to team members to complete the baseline (if rework isrequired), or ensures the changes to project data is marked appropriately (ifdeferred)10/29/201914
Baseline Procedure: Activity 6 Deliver the Approved Baseline Inputs Approved Baseline Report, Updated project data in the CM System, authorizedrecipientsInstructions The CM Manager facilitates the delivery of the Approved Baseline Report to theauthorized recipients, which could include the Installation Team (for As-Installedbaselines) All delivery requirements (classification markings, regulatory constraints, etc.)must be observedOutputs Documented receipt(s) of Approved Baseline Report in the CM System10/29/201915
Sample Baseline Report Sample Baseline Report derived from the Institute of Process Excellence (IPX)standard format10/29/201916
Audience QuestionsThis concludes the presentationThank-you for your attention.10/29/201917
10/29/2019 11 Generate Preliminary Baseline Report Inputs Approved Configuration Item (CI) List, hierarchy, and released artifacts Instructions The CM Manager compiles this preliminary baseline to ensure all items that are part of the baseline are created or revised, approved, and ready for implementation If items are still being processed, the CM Manager works with the change owner(s)
