SİSTEM MÜHENDİSLİĞİ SİSTEM MÜHENDİSLİĞİ YÖNETİMİ ÖMER ERTEKİN, PSCONSULTECH 1
SİSTEMLERİN ÖMÜR DEVRİ Sistemin ömür devri, bir fikir ile başlar, paydaş ihtiyaçlarının sistem mühendisleri tarafından tanımlanması ile sürer, tasarım, entegrasyon ve kalifikasyon ile devam eder, üretim, kullanım ve iyileştirme aşamalarından geçer. Sonunda sistemin emekliye ayrılması ve imhası ile tamamlanır. 2
TİPİK BİR ORGANİZASYON Program Manager Program Controls Systems Engineering Engineering 3
SİSTEM MÜHENDİSLİĞİYÖNETİMİ Systems Engineering Management Work Breakdown Structure Development Selection of Engineering Design Method Systems Engineering Program Planning Cost & Schedule Control Design Review and Evaluation Technical Control Managing the Organization Supplier Evaluation, Selection, & Control Systems Engineering Conceptual Design Preliminary System Design Detail System Design & Development Production and/or Construction Operational Use & System Support 4
SİSTEM MÜHENDİSLİĞİYÖNETİMİ Systems Engineering Program Planning Cost & Schedule Control Technical Control Supplier Evaluation, Selection, & Control Managing the Organization Conceptual Design Preliminary System Design Detail System Design & Development Production and/or Construction Operational Use & System Support 5
SİSTEM MÜHENDİSLİĞİYÖNETİMİ Systems Engineering Program Planning What is my management approach? Cost & Schedule Control Technical Control Supplier Evaluation, Selection, & Control Managing the Organization Conceptual Design Preliminary System Design Detail System Design & Development Production and/or Construction Operational Use & System Support What steps of the SE process will I execute? What resources do I require? 6
Systems Engineering Management Plan A Systems Engineering Management Plan (SEMP) is used to establish the technical content of the engineering work. The SEMP is written early in the formulation phase for each project and updated throughout the project life cycle. The SEMP provides the communication bridge between the project management team and the technical implementation teams. The SEMP provides the specifics of the technical effort : what technical processes will be used how the processes will be applied using appropriate activities how the project will be organized to accomplish the activities what appropriate work products will be produced the cost and schedule associated with accomplishing the activities. 7
SEMP Kapsamı Proje Kapsamı Proje Mühendislik Yönetimi ve Program Yönetimi ile İlişkisi Sistem Mühendisliği Yönetimi Sistem Mühendisliği Analiz ve Tasarım Süreçleri Alan Uzmanlığı Entegrasyonu Özel Mühendislik Alanları Sistem Mühendisliği Riskleri 8
İŞ TANIM DOKÜMANI (SOW) The SOW is: The highest level capture of the activities to be performed Narrative description of the work required for a given project Developed from the overall project SOW in the PMP Read by engineers as well as accountants, contract managers, schedulers, lawyers, etc. (must be no ambiguity) Basis for definition and costing of detailed tasks Basis for subcontractor and supplier requirements 9
İŞ TANIM DOKÜMANI (SOW) The SOW includes: Summary statement of tasks to be accomplished Identification of input requirements from other tasks References to applicable specifications, standards, etc. Description of specific results to be achieved and deliverables 10
İŞ TANIM DOKÜMANI (SOW) General guidelines for preparing a SOW Short, to the point, 2-3 pages, clear and precise Avoid ambiguity and possibility of misinterpretation Describe requirements in sufficient detail to ensure clarity Must consider practical applications and possible legal interpretations Do not underspecify or overspecify Avoid unnecessary repetition and extraneous material and requirements Do not repeat details already in applicable referenced documentation 11
WBS Follows SOW generation Product-oriented family tree that leads to identification of activities, functions, tasks, subtasks, work packages, etc., that must be performed for the completion of a given program Is not an organization chart for personnel Project activities Functions Tasks Subtasks 12
WBS Is a representation of organization of work packages The purpose of the WBS is to be a framework for: Considering the products, services, and information need to fulfill objectives and scope of the project (MM) Project planning and control Program planning, budgeting, contracting, and reporting Project activities Functions Tasks Subtasks 13
WBS List task breakdown in successively finer levels of detail Continue until all meaningful tasks or work packages identified and each task can be individually planned, budgeted, scheduled, monitored, and controlled Test for completeness: If you are detailing the process for doing or producing something in the WBS, you have gone one step too far Branches need not be the same length, number of levels driven by complexity of that portion of project 14
WBS Total system easily described through logical breakout of its elements into nicely definable work packages Increases probability that every program activity will be accounted for Links program objectives and activities with available resources Facilitates the initial allocation of budgets and the subsequent collection and reporting of costs Provides excellent matrix for assignment of tasks and work packages to various organizational components, responsibility for assignments can be readily identified Vehicle for reporting of system technical performance measures (TPMs) against schedule and cost 15
IMP/IMS The Even Planning Process: A hierarchical planning framework Steps Level 1: Make a list of major activities in general order of occurrence (about 2 to 20 activities) Level 2: Breakdown each Level 1 activity into 2 to 20 tasks Level 3: Breakdown each Level 2 task into 2 to 20 subtasks Continue until tasks at each level are manageable Fundamental: Be sure all tasks at a specific level are at the same level of detail (or level of generality) Project manager usually performs Level 1 and delegates lower levels to those who will do work Objectives are from project master plan 16