전사적시스템엔지니어링 (Enterprise Systems Engineering) 과PLM 융합 PLM 지식연구소조형식대표 hyongsikcho@korea.com
목차 시스템과시스템엔지니어링정의 시스템엔지니어링의조건 전사적시스템엔지니어링의트렌드 시스템엔지니어링과 PLM 의비교 시스템엔지니어링과 PLM 의융합 결론 2
시스템엔지니어링정의 시스템 (System) 공통목적을달성하기위해서함께일하는연관된부분들의사람과제품과프로세스의결합체 A system is a composite of people, products, and processes interact with one another and their environment to achieve a stated need and objective. 3
시스템엔지니어링정의 시스템엔지니어링 (Systems Engineering ) 성공적인시스템을개발하기위한다분야의종합적인접근방법과수단. System Engineering is a multidisciplinary, iterative process for defining technical products(paper studies, hardware, software) in which customer needs and expectations are met through 4
시스템특성 시스템은자원들의복잡한결합체로구성된다. 인간, 재료, 장비, 소프트웨어, 설비, 데이터, 자금등시스템은계층구조의어떤형태내에존재한다. 시스템은복잡도와수행되는기능에따라하부시스템과관련구성품으로분해된다. 시스템은목적을지녀야한다. 5
시스템엔지니어링역사 1969 New Era ANSI/ Mil - Std - 499 1994 1974 EIA/IS 632 Mil - Std - 499A 1998 ANSI/ EIA 632 2000 + EIA 632 (Updates) 1990-1994 Mil - Sd Std - 499B (Not Released) 1994 IEEE 1220 (Trial Use) Commercial Processes 1998 IEEE 1220 (Full STD) 2000 + ISO 15288 Best Practices 6
시스템엔지니어링조건 1. 적절한통합활동계획을가지고있는가? 2. 요구사항 (Requirement) 을문서화하였는가? 3. 위험관리 (Risk Management) 을하는가? 4. 형상관리 (C M) 을통해서베이스라인관리 (Baseline Control) 를하는가? 5. 대안시스템의구조와설계개발절차가있는가? 6. 단계별상태에대한검토회의를하는가? 7. 시스템구조와설계를검증된절차로선택하는가? 8. 제품에대한확인절차를하는가? 7
1. Appropriate integrated activity planning Customer Needs/ Objectives/Expectation - Missions - Measures of Effectiveness - Environments/ Constraints INPUT Plan Technical Effort Task & Integrated Planning Guidance & Redirection Management Plan System Engineering Management Plan (SEMP) Integrated Master Plan (IMP) Integrated Master Schedule ( IMS) Risk Management Plan Design Verification Plan Configuration Management Plan System Engineering Plan 8 Etc.
2. Documented requirements(given and derived) Analyze Requirements Perform Mission/Operations Analysis Define IPT req. & technical req. Define Performance & Design Constraints System Requirements & Operational Concepts Hierarchy & Specification Trees Functional Flows Data & Control Flows State & Mode Tyransition Diagrams Timeliness Interface Charts Performance & Error Budgets Interaction Diagrams Etc. 9
10 3. Risk management
3. Risk management 11
3. Risk management Plan Technical Effort System Baseline Control Technical Baseline Status Control Direction Re-Direction Planning EIA 632 Process for Engineering a system Control On Track Alert Assess & Evaluate Technical Efforts Management Plan Control Manage Risk Risk Management Plan 12
4. Baseline Control - 형상관리 13
5. Candidate architecture/design development Define Candidate Architectures Define/Refine/integrate Functional & Physical Architecture Decompose Lower-Level Level Functions Candidate System Designs/Architecture Mission Environment Life Cycle Cost System Effectiveness Risk Producibility Testability Operability Supportability 14 Etc.
6. Status t reviews
7. Architecture/design selection and 임무요구판단개념선정사업진행생산및배치 개념정립데모및확인개발생산및배치 체계요구사항분석 요구사항분석 상세설계개략설계 체계체계통합운용시험 SRR SDR SSR PDR CDR TRR 생산및배치개념및시험및평가 제작 시험 FCA PCA FQR SRR :System Reqt. Review SDR : System Design Review SSR : Software Spec. Review Type A 체계규격서 Type B 개발규격서 Type C/D/E 제품 / 공정 / 자재규격서 PDR : Pre. Design Review CDR : Critical Design Review TRR : Test Readiness Review FCA : Functional Config. Audit 16 기능 Baseline 할당 Baseline 생산 Baseline PCA : Physical Config. Audit FQR : Formal Quality Review
Require ement Verif fication 17 8. Product verification Analyze Requirements Requirement System Requirements Loop & Operational Concepts Define Candidate Architectures Candidate System Designs/Architecture Comp liance Optimize & Evaluate Alternatives System Analysis(Perf. Pred.), Verification Trade Studies, Design/Architecture, Loop & Assessment Results Verify System Define/Refine Verification Method Perform Verification Analyze Results Select Architecture/Design System Requirements Compliance & Veryfiction Methods Verification Plan Test Plans Test Cases Scenarios Analysis Simulations Audits Performance Demos Producibility Demos Algorthm Test Beds HWIL Test Beds Development Tests Qual Tests Acceptance Tests Integrated System Tests Operational Tests Etc.
Enterprise Systems Engineering 엔터프라이즈 (Enterprise) 의의미는단일구성으로관리되는기술지원, 프로세스, 인력의네트워크를의미한다. 대기업의경우에는전사적인패러다임이라고생각할수있다. 전사적체계공학또는엔터프라이즈시스템엔지니어링 (Enterprise Systems Engineering) 은기업이당면한불확실성 (Uncertainty) 와상호의존성 (Interdependence) 을해결하기위해집중하는시스템공학의영역이라고할수있다. 18
Enterprise Systems Engineering 전사적체계공학 (ESE) 의장점은기존의체계공학이급변하는기업의비즈니스환경에적합하지않다. 전통적인기존의체계공학 (TSE) 은고객의비교적정적이고예측이가능한요구사항중심의사업이라면새로운전사적체계공학은단순히성능이나기능의기술뿐아니라복잡한사회적요소나규제, 환경, 지속가능성같은부분과통합적으로구현하는경우에필요하다. 19
Enterprise Systems Engineering 전사적시스템공학의다음같은근본적인기조는다음과같다. 1. 통합적인시스템적인사고를한다. (Systems thinking) 2. 정치적, 운용적, 경제적, 기술적영향과제한의상황의인식을가진다. (Context awareness) 3. 창조적인문제해결과불확실성을수용한다. (Accepting uncertainty) 4. 복합적이고복잡한시스템진화과정을가진다. (Complex systems evolution) 5. 문제에대한적절한시기적실행을한다. (Matching practice to the problem) 20
Enterprise Systems Engineering 전사적체계공학은기업이전사적으로체계공학을적용하는것이다 21
22 Enterprise Systems Engineering
시스템 주기 vs 제품 수명주기 시 제작 설계검증 공정설계 양산 상세설계 판매유통 소싱 사업관리 서비스지원 제품수명주기 Product Lifecycle 개념설계 운용 유지보수 상품전략 요구분석 상품기획 폐기 재활용
시스템엔지니어링과 PLM PLM 을도와주는자 (Enabler) 라고한다면시스템엔지니어링은상황 (Context) 을파악해서해결해주는자라고할수있다. 시스템엔지니어링 PLM 성격 Solver Enabler 목적 시스템개발관리 제품데이터 / 프로세스관리 비전 균형적인시스템개발 RTM, TTM 환경 복잡다양한전문성 단일제품개발 사용 다양한지식소통 다양한자료통합 비고 소셜, 요구사항, 위험관리 엔지니어링정보 24
25 시스템개발수명주기
시스템엔지니어링 Effort Systems Engineering Systems Engineering creates the Vision Project Management creates the Product Project Management Project Managemnt of the Systems Enginering proess Time 26 Requirements Development Concept Exploration Full-Scale Dedign & Development Manufacturing & Deployment System Integration & Test Operation, Maintenance & Modification Retirement, Disposal & Replacement
27 시스템환경 (Context)
28 System Requirements Compliance System Verification Methods Veryfy System System Analysis (Perf Predictions and Allocations) System Trade-Off Studies System Architecture e System Assessment Resuslt System Qualification Analyze Requirements Direction Re-Direction Agreement EIA 632 Process for Engineering a system System Design On Track Alert Optimize & Evaluate Alternatives System Design System Requirements System Operational Concepts Define Candidate Architecture Candidate System Architectures
29 전사적시스템엔지니어링과 PLM 통합
CAX PLM PMS ERP
전사적시스템엔지니어링융합 현재의기업의정황 (Context) 를인식 시스템요구사항이나문제해결사항을작성 시스템엔지니어링절차를도입 전사적시스템엔지니어링과개발전산시스템과 End-to-End 프로세스시나리오작성 전사적시스템엔지니어링과 PLM 융합 31
시스템환경 (Context)
전사적시스템엔지니어링효과
전사적시스템엔지니어링효과
전사적시스템엔지니어링효과
Enterprise Systems Engineering 전사적시스템엔지니어링패러다임 5S Smart Speed System thinking Safety and Security Social 38
결론 전사적시스템엔지니어링의도입으로기업은다음같은 5S을가질수있다. 기업의더스마트 (Smart) 지고, 신속해지고 (Speed), 체계적으로사고를하고 (System thinking), 안전과보안 (Safety and Security) 과소셜 (Social) 에대해서통합적인인식을가질수있다. 39