1 / 14

Chapter 3. Conceptual System Design (CSD)

Chapter 3. Conceptual System Design (CSD). CSD is the first step in system design and development Design criteria to be established which meets/satisfy customer’s need. Identification of Need.

deo
Download Presentation

Chapter 3. Conceptual System Design (CSD)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Chapter 3. Conceptual System Design (CSD) • CSD is the first step in system design and development • Design criteria to be established which meets/satisfy customer’s need

  2. Identification of Need • System engineering process being with the identification of need, want or desire with few/new/more/improved capabilities with the system • A system may not be adequate, supportive, rigid and costly to maintain

  3. Feasibility Analysis • Identify possible system level design approach that can be pursued to meet the need • Evaluate the most likely approach in terms of performance, effectiveness and economical • Recommend a preferred course of action • ROI, longevity etc.

  4. Advance System Planning • Communicate with user • Completion of feasibility analysis • Definition of the system maintenance/support • Identification and prioritization of technology and performance measure • Completion of top level analysis • Preparation of system specification • Conduct of a conceptual design review

  5. Definition of Operational Requirements • Operational distribution or deployment • Customer sites where the system will be used, geographical distribution, deployment schedule • Mission profile • Identification of the prime mission for the system and its alternative (routing etc.) • Performance and related parameter • Basic operational characteristic/function of the system parameter (range, accuracy, rate, throughput) • Utilization report • Anticipated usage of the system in accomplishing mission, % usage days/night/hrs etc.

  6. Definition of Operational Requirements • Effective requirements:cost/system effectiveness, operational availability, dependability, reliability, mean time between failure (MTBF), failure rate, maintenance downtime (MDT), personnel etc. • Operational life cycle: Anticipated time duration that he system will be operational • how long will the system be use by the consumer, total inventory for units of the system and its components,inventory location • Environment: The environment in which the system is expected to operate in a effective manner example, temp, shock, noise, humidity etc.

  7. Operational Requirement (geographical distribution)

  8. Maintenance and Support Requirements Level of Maintenance • Repair policies:( responsible, partial, repairable, unrepairable etc) • Organizational responsibility:(maintenance by the customer, produce, third party etc) • Logic support elements:(supply support, test support equipment, personnel, training, handling, self test etc. • Effective requirement: support capability, probability of available part, economics with parts • Environment: Shock, vibration, temp, noise etc.

  9. Functional Analysis & Allocation(FA) • FA is the process of translating system requirement into detailed design criteria along with the identification of specific resources requirement at subsystems. • A function refers to a specific or discrete action that is necessary to achieve a given objective • FA is the iterative process of breaking down or decomposing requirement from the system level to the sub system level and as for down the hierarchical structure as necessary

  10. Functional Flow Block Diagram(FFBD) • FFBD are developed for the primary purpose of structuring system requirements into functional terms • FFBD illustrate system organization and to identify major functional interfaces • all facets of system design and development, production, operation are considered • all elements of the system are fully recognized • a mean is provided for relating system packaging concepts and support requirement • the proper sequence of activity and design relationship are established

  11. System Requirements: Functional Breakdown System Top Level Functions 1 2 4 3 Function A Function B Function C Function D 5 6 Function E Function F Second Level Functions 5.1 5.5 5.3 5.4 5.2 Third Level Functions 5.5.5

  12. Functional AllocationAn open architecture approach is used when the functions are well definedSave time “what” converted into “how” System XYX System Operator Equipment Computer Resources (SW) Facility Unit A Unit B Unit C Assembly 1 Assembly 2 Assembly 3

  13. System Specification • The technical requirements for the system & its elements are documented through a series of specification System specification (type A): includes the technical, performance, operational & support characteristic for the system as an entity • information derived from feasibility analysis, operational requirement, maintenance concepts Development specification (type B):includes the technical requirement for any item below the system level where R&D are accomplished • this may cover equipment's, assembly, computer program etc.

  14. System Specification • Product specification (type C):this includes computer programs, a spare part, tool etc • Process specification (type D): covers service that is performed on any components of the system (welding, plating, heat treating etc.) • material specification ( type E) pertains to raw material (paints, chemical, cable, pipe etc.)

More Related