配置管理

CM WorkshopSAP, Palo AltoFebruary 1999 Norman ScobieIBU A&D/E&C, SAP AGThe definitive CM functions Configuration ManagementConfiguration Management -CMConfigurationStatus AccountingRecordand reportinformationConfigurationAuditAudit to verifyconformanceConfiguration ControlControl changes toconfigurationitemsConfiguration IdentificationIdentifythe functional andphysical characteristicsof configuration itemsWhat is it?●Configuration management is defined asa process for establishing and maintainingconsistency of a product’s performance, functionaland physical attributes with its requirements, designand operational information throughout its life.●Effective CM answers the questions⏹What should it be?⏹What is it?⏹Are they consistent?⏹...for life!Change ManagementChangeIdentificationEvaluation & CoordinationNeed for changeDocumented Change RequestApproved ChangeCurrent BaselineNew current design baselineImplementation & VerificationUpdated Product Baseline DataApprovalCost Control●What will it cost and what did it cost?●Cost visibility and control at various levels is part of anintegrated CM process in an ERP system●Estimated costs to assess change impact arenecessary as well as continuing control of those costs for major change (actual costs).●SAP has a development project calledClaim Management to deal with this area.Configuring for LifeConfiguration identification and relationships inthe product lifecycleMain Lifecycle Phases ConfigurationManagement has to beperformed in all 3 mainlifecycle phases.The Configuration datahas to be managed acrossthese phases as well aswithin to provideconsistencySub phases in the lifecycleEach main phase, will be definedby a progression of configurationsused for specific purposesas designed as plannedas builtConfiguration Identification -Baselines●Central aspect of CM●Specific status of a configuration item ●Life-cycle Control●Baseline Attributes⏹Known and defined point of reference⏹Agreed reference configuration at a milestone or a specific time ⏹Frozen set of referenced objects and relationships (logical bracket)⏹Data formally protected from changeas designedas plannedas maintainedas builtSupport of a product life cycle means covering status and functionality across different areas...as shippedas soldas designedas engineered as plannedas builtas maintainedApprovalRelease strategyConsistency checkChange managementEngineeringProduction / ProcurementMaintenanceSales / Shipping... across different processesEngineeringProduction / ProcurementMaintenanceSales / ShippingMaintenance and ServiceTCS / MRODesignDTOManufacturingMTO / ETO Sales & MarketingOrder EntryOrder ProcessingDelivery, Handover &WarrantyDesign, Concept &Specification Quotation & Contract Costing OrderEntry Prototyping & OptimizationHandover & Contract PreparationSales & MarketingService Planning &PreparationService ProcessingHandover & WarrantyProduction Process ChangesDesign ChangesPerfective Adaptive CorrectiveAs designedChange 01Change04Config Item.d1initialChange09Change10Config Item.b1baselinedConfig Item.b1in work As maintainedConfig Item.m1initialChange07Config Item.d2initial Config Item.d2baselined Config Item.d1baselinedAs plannedChange08Config Item.p2initialAs builtConfig Item.b1initial Config Item.p1initial Config Item.p1baselined---and with different relationships...1:1 1:11:n 1:nDerived relationshipSuccessor -Predecessorrelationship 1:n1:m1:1ManufacturingMTO / ETOCustomers have different profilesEngineeringProduction / ProcurementMaintenanceSales / ShippingServiceTCS / MRODesignDTODesign ConsultancyMaintenance OrganisationManufacturing SubcontractorDesign, Manufacture and MaintenanceOrganisationConfiguration Management where are you today?Configuration Management in R/3R/3 today -Objects relevant for CM ●Documents●Material Master●Bill of Material●Routings●PRT●Orders●Projects●Equipment●Functional Location●Maintenance Plan●Maintenance StrategyEngineeringProduction / ProcurementMaintenanceSales / ShippingServiceTCS / MRODesign DTOManufacturing MTO / ETOR/3 today -Life just gets worse with age….Documents Material MasterBill of Material Routings PRT Orders Projects EquipmentFunctional Location Maintenance Plan Maintenance StratDocuments Material MasterBill of Material (Equipment)(Functional Location)Documents Material MasterBill of Material Routings PRT Orders Projects (Equipment)(Functional Location)R/3 today -Some of the objects have sub-typesBill of MaterialsMaterialEquipment Functional locationStandardSales order WBS (Project) Document BoMRoutings / Task Lists Reference operation setInspection plan Gen. maintenance task list Equipment task listMaster recipeRate routingReference rate routing Functional location task listR/3 today -Configuration Identification●Structured Object Configuration⏹BOM⏹Routing♦Effectivity♦Variant configuration●Object Links⏹Document Management System●Product Structure BrowserR/3 today -Structured Object ConfigurationEffectivity and variant configuration define a flexible basis for product configuration for BOMs and RoutingsMaster DataPRODUCTSTANDARD_1STANDARD_2SPECIAL ASPECIAL B SPECIAL CValuationExplosion ResultPRODUCTSTANDARD_1SPECIAL AOne set of Master Data defines many individual products!R/3 today -Object Links DocumentsTEXT TEXT TEXT TEXT TEXT TEXT TEXTTEXT TEXT TEXT TEXT TEXT TEXT TEXT TEXTTEXT TEXT T TEXT TEXT TEXT TEXT TEXT TEXT EXT MaterialsEquipments Functional Locations Equipments Functional Locations Functional LocationsMaterialsMaterialsEquipmentsR/3 today -Object LinksR/3 tomorrow-CM Development areas●ability to freeze a structured configuration(collectionof objects) of various R/3 object types independent of object links●requires enhanced object functions for CM especiallybaselining at object level● a single tool behaving⏹consistently across the life-cycle⏹flexible to match the requirements of a particular phase⏹able to support analysis and transfer of information acrossphasesMaterial Master Versions● A related CM project in SAP●Historical R/3 issue is that Material Master RevisionLevels provide no true material versioning.R/3 4.5 -Configuration Control-Engineering Change Management●Control Process⏹Object Management Records⏹ECR / ECO⏹Workflow⏹Digital Signature●Release Control●ECM Structure⏹Change Hierarchy●EffectivityECM Control Process●Object Management Records (OMR)⏹available for BOM, Material, Routings⏹captures change texts for that object⏹centre of workflow for the objectECMRef:Object_1OMR Object_1Ref:Object_2OMR Object_2ECM Control Process ObjectManagementRecordsECM -Release Control●Release Key (optional)⏹value set in ECM header data⏹controls validity of an ECM for♦Simulation♦Costing♦Planning♦Production●Until ‘released’ the ECM remains invalid for anapplicationECM -Change Hierarchy Structuring Change MastersChange LeaderChange PackageChangePackage ChangePackageObjects Objects ObjectsObjectsObjectsObjectsEffectivityRelease KeyWorkflowChange Hierarchy -ReportingR/3 4.5 -Configuration Control Workflow in ECMR/3 ECM is strongly supported by WorkflowfunctionalityR/3 4.5 -Configuration Control EffectivityMutually exclusive -only one to beselectedPRODUCTSTANDARD_1STANDARD_2SPECIAL A SPECIAL B SPECIAL C Effective for all versions of PRODUCTPlant EffectivityPlant 0001 from 01.02.98 Plant 0002 from 01.06.98Customer Effectivity Customer BA, Serial #5Model/Unit Effectivity Model UH-1, Serial 50The MRO Process-Development issuesFull Part TraceabilityFull Part TraceabilitySpecific as-planned ConfigurationAn example of an MRO Process KLM CFM56 Engine ShopAcceptance, Breakdown and InspectionRepair, Rebuild and DeliveryEngine Delivery PartsInspectionIncoming InspectionDisassembly CleaningParts Repair Assembly PreparationAssembly DeliveryGeneral Target ConfigurationEngineManufacturer Documentation IPC, SB’s, AD’s As-shipped ConfigurationAs-received ConfigurationCertified Task ListsAs-builtConfigurationInterchange-abilityFeatures of the process●Characterised by the use of configurations as afundamental element of the business process●Full traceability⏹what is it?⏹how was it done?⏹who did it?CM Issues at KLM●Engine Configurationrequired for variousreasons⏹Target configuration⏹as-received configuration⏹Part exchanges⏹as-shipped configuration●Document Control⏹Illustrated Parts catalogue⏹Service Bulletins⏹Airworthiness Directives●Part Interchangeability⏹defined at location level in IPC ●Part Configuration Control⏹full traceability of each part for♦which part♦location♦work performed♦who performed work●Task List (Routing)Configuration Control⏹task list configuration controlin PM Order⏹task list certification⏹authorisation of operatorALL INFORMATION TO BE KEPT FOR LIFE OF ENGINE AND INDIVIDUAL PARTS !Configurations at KLMECM in R/3:31H -time based effectivityEquipment BOMMaterial 4711-005 : Casing strengthenerAs shipped configurationMaterial 4711-113 :Gasket Material 87723005 : New bracket 123A Material exchangesMaterial exchangesAs received configuration Material 4711-005 : Gasket Material 159889 : Flange Material 872636 : Bracket 123Material 47AK11-005 : CasingAs received configurationAs received configuration As received configurationECMs raised for specific points in shop visitMaterial exchanges As shipped configurationAs received configuration They each represent a point in time in theshop visitBOM configuration at a specific point in time i.e. shop visit, can then be identified in the BOM via the ECM numberANZES Solution -SB/AD implementationService Bulletin /Airworthiness DirectiveDocument MasterEngineering Change MasterNotification Drivesanalysis of effectivityIf fleet is affectedClassification of ECM Effectivity : Equi's and FL's definedas characterisitcsNotification for each object definedin ECM classn.Change Management -EIA 649Need for changeDocumented Change RequestApproved Change Current BaselineNew current baselineImplementation & VerificationUpdated Baseline DataEvaluation & •Planning•Implementation •Co-ordination / Consistency •Verification•Items affected -internal•Identify external areas affected •Reason for change -Reference to initiation •Before / After state•Commenting of Change Requests / Red-lining tools?•Change Request versions?ChangeIdentification•Initial impact statement•Identification as Major or Minor •Impact on processing and reporting?CoordinationPlant Maintenance StructureInstalled BaseImplementating ECM and PM integration●Customers currently link ECM to the applications viaworkflow, add configuration data using classification and add their own code extensions for statusaccouting.●Limitations today in R/3 are⏹workflow can link functions but can’t provide a natural historyof the process⏹adding own code is difficult and time consuming●The CM Motivation⏹add value to the business process by♦improving process automisation/integration♦improving implementation timesECM integration to PM●Changes to actual equipment occurs in service andthese are represented by PM Technical Objects in R/3 (Functional Locations and Equipments)●Changes in industry often flow down from design tothe operating engineering objects described by FL’s and Equi’s in R/3.●The requirement is to link Notifications, PM Orders,Functional Locations and Equipments to ECM toprotocol the following⏹initiation of the a change process by notification⏹confirmation/reporting when changing technical objects.●Also to be considered, Maintenance Plans andStrategiesSB/AD or design change implementationEng. Change MasterNotificationPM/QM OrderEquipmentService BulletinAirworthiness DirectiveProcess example detailedFault ReportEng. Change MasterDesign/Production Object ListMaterialsDocumentsBOMs Routingsetc.Maintenance ObjectsPlans Strategies ItemsTechnical ObjectsFL’s Equi’sNotificationItemsMaterialsAnalysisDesign ChangePM/QM OrdersPM/QM Orders PM/QM OrdersFL’s Equipments FL’s Equipments FL’sEquipmentsAuto Order generation •when initiated e.g.at time of maintenance or •generated immediately?Auto Task list generation?1. A fault causes a design change.2. Analysis of Notification shows design change required3. ECM generated to define design/production change4. The change of Docs, Materials, etc. is controlled via ECM.5. The change has to be implemented in exisiting technical objects (FL’s, Equi’s).6. Status History is required in ECM to answer -when/which objects have been changed?7. History is required in FL’s/Equipments to answer -when/which changes have been implemented?SB / ADDocument Master created in DMSMaintenance objects control via ECM functionality?Change existing plans/strategies Create new plans/strategiesEffectivity on ECM:For FL’s and Equi’s, ECM Master logs implementation when the PM order is confirmed.Reporting required?ECM Implementation status What is the change status of an equipmentGenerate changemaster for Notification or DMSEffectivityService ProviderOperatorFfgdfgsdghd dghghfghfghf rhrhrhhfghfdghSB/ADUpdate to as-planned configurations for shop visitsOrders to be generated at time of shop visitCheck fleet for effectivity,If affected issue Notifications for work to be performedConfiguration Service?If company provides a config. Service, check effectivity and advise operatorsConfiguration ItemConfiguration Item -SAP Concept for R/3●Design Goals●The configuration object●CM functions●Configuration Life cycle●Design●Claim ManagementMaterial BOMRoutings Variant configurationPVS DocumentProductdefinitionProductionShipmentMaintenanceMRP planningPurchase orderPlant structureFunctional location EquipmentsProduction PP-Order PI-Order Foreign procurementDesignCost dataConfig ItemProject systemStore resultUse configurationUse configurationStore resultStore configurationUse configUse configurationModify ConfigurationCreate Configuration●Baseline of product structure●Enhanced structure navigation and handling ●History of product definition throughcomplete life cycle●Automatic generation of configuration data ●Cost control of changes。