Staying aware of.

Uploaded on:
Open Frameworks Designing Staying aware of the evolving scene... … by planning and building weapon frameworks utilizing the open framework approach. Open Frameworks Joint Team Novel, Shut Weapons Frameworks Plans Cost A lot to Create Cost A lot to Bolster Cost A lot to Adjust
Slide 1

Open Systems Engineering Keeping up with the evolving scene... …by outlining and building weapon frameworks utilizing the open framework approach. Open Systems Joint Task Force

Slide 2

Unique, Closed Weapons Systems Designs Cost Too Much to Develop Cost Too Much to Support Cost Too Much to Modify Can Not Readily Employ New Technologies Inter-operation Is Less Than Desirable Longer Weapon System Life Reduced DOD Budget Increased Dominance of Commercial Market Shortened Technology Cycle Time The New Acquisition Environment

Slide 3

Life Cycle Cost Operation and Support System Acquisition Production System Research, Development, Test and 60% Evaluation 30% 10% 0 | || ||| Years Milestones DSMC Systems Engineering Management Guide Life Cycle Costs

Slide 4

What Is an Open System Approach? The open frameworks methodology is a coordinated business and specialized procedure to: pick economically upheld determinations and measures for chose framework interfaces (outer, inner, useful, and physical), items, practices, and instruments, and fabricate frameworks taking into account secluded equipment and programming outline.

Slide 5

Business and Technical Approach It is a business way to deal with influence utilization of business items that guides assets to a more escalated preparatory outline push to result in a lifecycle cost lessening. As a business approach it underpins the DOD arrangement activities of CAIV, expanded rivalry, and utilization of business items. It is a specialized methodology that accentuates frameworks building, interface control, measured outline, and configuration for update. As a specialized methodology it bolsters the building objectives of outline adaptability, hazard decrease, setup control, long haul supportability, and improved utility. The Open Systems Approach Makes Sense Whether You are a Manager, Engineer, Logistician, Comptroller, or Contracting Officer.

Slide 6

Easier Technology Insertion Improved Support Increased Competition Reduced Life Cycle Costs Open Systems Benefits Open Systems Benefits Systems Fielded Improved Intra-& Interoperability Faster State-of-the-Art Improved Systems Operational Capability Better Performance

Slide 7

Relationship to Acquisition Reform Relationship to Acquisition Reform Objectives: Objectives: Cost as a Performance SPECs Cost as a Performance SPECs Reduced Cycle Times Reduced Cycle Times Independent Variable State prerequisites in wording Independent Variable State necessities as far as requirements, not plans Lower Costs Lower Costs Trade Performance and of necessities, not outlines Trade Performance and Schedule for Lower Costs Schedule for Lower Costs Clear Accountability Non-Developmental Clear Accountability Non-Developmental in Design and Commercial Items in Design and Commercial Items Acquisition Government Controls Use Existing Technology Government Controls Use Existing Technology Performance - Contractor and Products, If Applicable Performance - Contractor and Products, If Applicable Reform Designs the Solutions. Outlines the Solutions. Level Modernization Horizontal Modernization Technology Insertion Through Spares Technology Insertion Through Spares Evolutionary Acquisition

Slide 8

SUMMARY - Open System Approach Emphasizes -Flexible Interfaces, -Maximum Interoperability, -Use of Commercial Competitive Products, -Enhanced Capacity for Future Upgrade. - Business and Technical Approach -Business Establishes the Need and Availability -Technical Supplies the Means - Associated with Clear Lifecycle Performance, Cost, and Schedule Benefits - Acquisition Reform Enabler

Slide 9


Slide 11

Systems Engineering Management Development Phasing Configuration Baselines Lifecycle Planning Systems Engineering Management Systems Engineering Process Lifecycle Integration Integrated Teams

Slide 12

DEVELOPMENT PHASING Concept Studies DESIGN DEFINITION System Definition (Functional Baseline) DESIGN DEFINITION Preliminary Design (Allocated Baseline) DESIGN D EFINITION Detail Design (Product Baseline)

Slide 13


Slide 14

Systems Engineering Process Inputs Customer Needs/Objectives/Requirements OP Concept, Missions, and Measures of Effectiveness Environments and Interoperability Constraints (e.g. Expense, Schedule) Technology Base and Engineering Processes. Lifecycle Issues: Producibility, Maintainability, Testability, and Similar Output Requirements From Prior Application of SEP. Program Decision Requirements.

Slide 15

P R O C System Analysis E and Control S (Balance) S Requirements Analysis I N Requirements P Loop Functional Analysis/U Allocation T Design Verification Loop Synthesis PROCESS OUTPUT Requirements Analysis Develop System Functional & Performance Requirements n Define: – What System Must Do » How Well It Must Do It » Utilization Environment » Design Constraints » Performance Requirements Define: n Quantity - what number – Quality - How Good – Coverage - How Far – Time Lines - When – Availability - How Often » Design Constraints Define: n Environmental Conditions or Limits – Defense Against Internal or External Threats – Contract, Customer or Regulatory Standards –

Slide 16

REQUIREMENTS ANALYSIS OUTPUTS THREE VIEWS Operational Focuses on how the framework will be worked by clients, including interoperability needs. Sets up HOW WELL and UNDER WHAT CONDITION the framework must perform. Utilitarian Focuses on WHAT framework must do to create obliged operational conduct. Shows obliged inputs, yields, states and change rules. Physical Focuses on HOW the framework is built. Key to building up the physical interfaces and innovation necessities.

Slide 17

Functional Analysis and Allocation Allocate Functions – Decompose Higher Functions P R O C System Analysis Allocate Performance E and Control S (Balance) S Requirements Analysis I – From Higher to Lower Functions N Requirements P Loop Functional Analysis/U Allocation T Functional Descriptions Design Verification Loop Synthesis – Functional Flow Block Diagrams – Time Line Analysis PROCESS OUTPUT – Functional Architecture

Slide 18

Typical Functional Analysis and Allocation Tools Time Line Analysis Functional Flow Block Diagram IDEF and Similar Functional Interface Tools Requirements Allocation Sheet

Slide 19

Design Synthesis Outputs: Physical Architecture (Product Elements & Software Code). Details and Baselines. Choice Database. Inputs: To Be Transformed: Functional Architecture. Empowering agents: IPTs; Decision Database; Tools: CASE, CAD, CASETS. Controls: Constraints, Technical Architectures, GFE, COTS, System Concept & Subsystem Choices; Organizational Procedures.

Slide 20

Design Synthesis Activities: Allocate Functions & Constraints to System Elements. Orchestrate System Element Alternatives. Evaluate Technology Alternatives. Characterize Interfaces. Characterize System Product WBS. Create Life Cycle Techniques & Procedures. Coordinate System Elements. Select Preferred Concept/plan.

Slide 21

Typical Design Synthesis Tools WBS Schematic Block Diagram Concept Description Sheet Requirements Allocation Sheet

Slide 22

Verification Each Requirement Must Be Verifiable Specification Section 4 Relates Directly to Section 3 Confirms That Solution Meets Requirements Types of Verification: Inspection Demonstrations Simulations/Analysis Test

Slide 23

SYSTEMS ANALYSIS AND CONTROL ANALYSIS : Trade Studies Effectiveness Analysis QFD CONTROL: Work Breakdown Structure CONFIGURATION AND INTERFACE MANAGEMENT Data Management Event Schedules and Tech Reviews Metrics Risk Management Modeling and Simulation AND OTHERS!

Slide 24

Configuration Management Process for Establishing and Maintaining Consistency of a Product’s Performance, Functional, and Physical Attributes With Its Requirements, Design, and Operational Information Throughout Its Life. Distinguishing proof, Control, Status Accounting, Audits Interface Management Process for Identifying and Controlling Interfaces and the Requirements Associated With Them. ICWGs, ICD

Slide 25

Technical Reviews Concept Studies Alternative Systems Review DESIGN DEFINITION System Definition (Functional Baseline) System Functional Review DESIGN DEFINITION Preliminary Design (Allocated Baseline) System Requirements Review Preliminary Design Review DESIGN DEFINITION Detail Design (Product Baseline) Critical Design Review

Slide 26

Acquisition Milestones Concept Studies ASR System Definition (Functional Baseline) DESIGN DEFINITION SFR SRR Preliminary Design (Allocated Baseline) DESIGN DEFINITION PDR DESIGN DEFINITION Detail Design (Product Baseline) CDR MS1 MS2 Findings of the ASR support MS1 Findings of the SFR support MS2 MS3

Slide 27

SE PROCESS OUTPUTS Level of Development Dependent Decision Data Base System/Configuration Item Architectures Specifications & Baselines P R O C System Analysis E and Control S (Balance) S Requirements Analysis I N Requirements P Loop Functional Analysis/U Allocation T Design Verification Loop Synthesis PROCESS OUTPUT

Slide 28

Architectures of a System Functional necessities Performance prerequisites Physical (equipment and programming) System Products and procedures for improvement, fabricating, organization, operations, bolster, transfer, preparing, and confirmation.

Slide 29


View more...