CSUN Engineering Management Systems Engineering Management MSE607B Chapter 2, Part II The System Engineering Process.

CSUN EngineeringManagement

Systems EngineeringManagement

MSE607BChapter 2, Part II

The System Engineering Process

http://www.csun.edu/

Learning Objectives

Identify the applications for systems engineering Overview of the systems engineering process Introduce the basic activities of the process Evaluating systems in terms of their effectiveness Material provided is a necessary prerequisite to

the information presented later

Case Study:Elevator System

Apply Systems Engineering Concepts and Process to a ‘Simple’, Understood System.

Operational Concept

External Systems DiagramIDEFØ Model•Designed to model:

•Decisions•Actions•Activities

•Help organize the analysis of a system and promote good communication between the analyst and customer

Functional Architecture

Systems Engineering Approach

Establish Performance CriteriaEstablish Performance Criteria

Establish System Goals and ObjectivesEstablish System Goals and Objectives

Define the Define the ProblemProblem

Establish Institutional Establish Institutional FrameworkFramework

Build Build CoalitionsCoalitions

Define Functional RequirementsDefine Functional Requirements

Identify and Screen Identify and Screen TechnologyTechnology

Develop Develop Deployment PlanDeployment Plan

Deploy ProjectsDeploy Projects

EvaluateEvaluate

Define System ArchitectureDefine System Architecture

ShortShort MediumMedium LongLong

PhysicalPhysicalLogicalLogical











EvaluateEvaluate




Define the Problem

Vary in breadth from operational to institutional

Methods of identifying problems:• Traditional operational studies• Regional transportation and land-use studies• Air quality assessments

Coordination with other agencies input from local politicians

Inventory of System

PHYSICAL ORGANIZATIONAL

Roadway networkOperating agencies

Existing surveillance and control systems

Funding sources

Existing information dissemination systems

Political and agency jurisdictions











EvaluateEvaluate




Establish Institutional Framework

Critical step in process Needed at three levels

• Interagency• Intra-agency• Other stakeholders

Input identifying problems and developing goals

Interagency

MPOs Highway/public

works Transit Law enforcement Emergency

services

Turnpike/toll road authorities

Port authorities State and federal

emergency management agencies

Intra-agency

Planning Administrative Construction Design Operations Maintenance

Other Stakeholders

Major traffic generators Utility companies Politicians Media Private transportation providers











EvaluateEvaluate




Building Coalitions

Identify “champions”• “Top-down” or “bottom-up” support

Find individuals critical to success• Key individuals with knowledge and authority

• Present throughout entire process Use existing institutional frameworks











EvaluateEvaluate




Establish Goals and Objectives

Describe what system is to accomplish Directly related to specific problems Goals => long-range and broad Objectives => measurable and specific

Example of Goals and Objectives

IDENTIFIED PROBLEM Incidents => primary source of congestion

SYSTEM GOAL Reduce impacts of incidents

SYSTEM OBJECTIVES Detect all incidents within 2 minutes Reduce clearance time by 5 minutes











EvaluateEvaluate




Establish Performance Criteria

Judging performance of system System achieving design

objectives Measures of performance

• Qualitative• Quantitative

Example of Performance Criteria - Incident Management

Objective: Detect all incidents within 2 minutes• Average detection time• % of incidents detected in 2 minutes

Objective: Provide first response within 15 minutes• Average response time• % of incidents responded to in 15 minutes

Objective: Reduce clearance time by 5 minutes• Average clearance time before system implemented• Average clearance time after system implemented• % of incidents where clearance time reduced by 5

minutes











EvaluateEvaluate




Define Functional Requirements

Features needed by system to accomplish objectives

Independent of technology or architecture Describes what system does, not how!

Example of Functional Requirements

Incident Management

Identify incidents

Identify location of incident Identify impacts of incident Identify characteristics of incident

Formulate response actions

Identify necessary emergency vehicle response

Select incident information for dissemination to travelers

Identify traffic control strategies

Initiate and Monitor response

Provide response procedures to agencies

Monitors response











EvaluateEvaluate




Define System Architecture

Framework for achieving system objectives Example:

• Function: • Incident detection

• Architecture:Architecture:• Surveillance system• Detection algorithm• Communication system

Benefits from Planning System Architecture

Minimizes redundant systems Promotes efficient use of equipment, staff, and

resources Permits easy expansion and modernization Facilitates information sharing

System Architecture Levels

Functional Requirements => what system is supposed to do

Logical architecture => what information flows between components

Physical architecture => where function occurs and who is responsible for performing it

“Open” System Architecture

Designed with standard data interfaces• Not vender specific

Benefits:• Keeps system from being obsolete• More compatible with ITS technologies











EvaluateEvaluate




Identify and Screen Technology

Meets performance and reliability standard defined by architecture

Sources of information:• Evaluation studies and reports• Literature• Demonstration• Site visits

Evaluating Technologies

Interaction with system Impacts on physical configuration of system Expandability and flexibility Life-cycle costs:

• Procurement, installation, and construction• Operating and maintenance• Replacement and expansion costs

Operations and maintenance Iterative process











EvaluateEvaluate




Develop Deployment Plan

Outline how system is implemented Elements:

• Problems and opportunities to be addressed• Institutional arrangements• Goals and objectives• Functional requirements and architecture• Technology options

Include implementation plan

Elements of Implementation Plan

Goals and objectives Laws, ordinances, etc. Start-up procedures Adding functions Organizational and

reporting structure Agency responsibilities

Operating procedures Communications protocols

/ procedures Staffing requirements Hours of operation Training Maintenance Budget

Procurement Approaches

Sole-source• a contract is awarded to a named supplier without any

competition for the project Engineering / contractor

• A single contract is awarded to the lowest responsive bidder to a specific request by the highway agency

Two-step• A formal technical prequalification process is added to the

engineer/contractor approach System management

• A system manager is hired to perform the system design, software development, and system integration activities

Design / build• A single entity is responsible for all of the work associated with

deploying a system










EvaluateEvaluate





Evaluation

Ongoing process Occurs at all stages How well system is achieving design objectives Identify improvements Lessons learned

Summary

Applications for systems engineering Systems engineering process Basic activities of the process Evaluating systems in terms of their effectiveness Material provided is a necessary prerequisite to

the information presented later

Interactive Workshop

The purpose of feasibility analysis is:a) Identify functions the system must performb) Identify requirements the system must

performc) Determine the resources needed for the

system developmentd) Determine if the system design should be

successful

“Systems Maintenance” concept is the basis for:

a) Establishing supportability in system designb) Detailed maintenance planc) Detailed design of system componentsd) Both (a) and (c)e) Both (a) and (b)


Systems Operational requirements describe:a) The designer needs relative to utilization and

mission accomplishmentb) The consumer needs relative to utilization and

mission accomplishment c) Mission performance and test parametersd) The consumer needs relative to system

functional goals


One of the basic steps in system engineering process is NOT:

a) System retirement and material disposalb) Maintenance and support conceptc) System operational requirementsd) System marketing and research


System Functional requirements specify:a) The “How” not the “What”b) The “What” not the “How”c) What needs to be analyzedd) Baseline for system analysis


Homework Assignment

Textbook page 107 Answer questions 1, 8, 12, 18, 27

Use homework format provided in course website

Read Chapter 2

• Pages 46-107

Questions? Comments?

CSUN Engineering Management Systems Engineering Management MSE607B Chapter 2, Part II The System Engineering Process.

Documents

minutesaverage clearance

minutesreduce clearance

minutesaverage response

minutesaverage detection

systems engineeringoverview

processevaluating systems

specificexample of goals

entire process