ControlDraw
This web was generated automatically from a sample ControlDraw model.
Move the mouse over the diagram area - you can click on the objects that have numbers by them to go to the detailed diagram for the object. It is a bit like using ControlDraw (but that is much more powerful!)
More Sample models    Go to ControlDraw.co.uk


List of Diagrams
[First] [Previous]][Next][Last]
001 - index
002 - About Process Control
003 - Your Business
004 - For Manufacturers
005 - For EPC Companies
006 - For Systems Integrators
007 - For DCS/PLC suppliers
008 - Education
009 - Process Operation
010 - Process Control Systems
011 - Automation Software Design
012 - Functional Design
013 - S88 Links
014 - Process Design
015 - Design Documents
016 - FRS
017 - P&ID
018 - Process Descriptions
019 - SDS
020 - URS
021 - PCS Graphic
022 - Engineers
023 - For DCS/PLC Programmers
024 - For Automation Engineers
025 - For Process Engineers
026 - Process Eng Diagram Flow
027 - For Project Managers
028 - Project Management ControlDraw
029 - For Instrument Engineers
030 - Automation Design
031 - REQUIREMENTS ANALYSIS PROCESS
032 - Instrument Engineering
033 - Diagrams
034 - Logic Diagrams
035 - Control Loops
036 - PFC
037 - Process Flow Diagram
038 - Sequential Function Charts
039 - State Transition Diagrams
040 - Polymorphic
041 - Controldraw Software
042 - Automation Models
043 - Hierarchical Objects
044 - Database
045 - IO List
046 - Data lists
047 - S88 Models
048 - S88 Recipes
049 - S88 Physical Model
050 - Process Cells
051 - Units
052 - Equipment Modules
053 - Control Modules
054 - S88 Procedures
055 - Recipe Procedure
056 - Unit Procedure
057 - Operation
058 - Phase
059 - State Matrices
060 - State Based Control
061 - Control Design Reviews
062 - ControlDraw Reviewer
063 - Overview
064 - Why Controldraw
065 - FAQ
066 - Controldraw Compared
067 - Main Screen
068 - Matrix Screen
069 - Life Cycle
070 - Life Cycle and Models
071 - Specifications
072 - Functional Requirements Spec
073 - Functional Design Specification
074 - User Requirements
075 - Support
076 - Download
077 - Standards
078 - Services
079 - About Web Site
080 - ControlDraw Prices
081 - History
082 - History of Control
083 - History of ControlDraw
084 - History of S88
085 - History of Diagrams
086 - Documentation for the Life Cycle
087 - Large distributed projects
088 - System Development Structure
089 - The RTF Editor
090 - ControlDraw with CAD
091 - Web Layout
092 - Prototyping Partnership
093 - All pages
094 - IEC1131
095 - OnePageOverview

31 - Requirements Analysis Process (Web Page)

The diagram shows the main activities for developing the detailed functional requirements. It is oriented around the physical and procedural models.
S88.01 defines these models generically - that is to say that the models are universal and apply to any plant. The analysis process must take these generic models and then apply them to the particular plant. For example the physical model in S88 shows Control Modules. The requirements analysis should identify what are the actual modules required by the particular plant.
The diagram above shows that there are pre-requisites before the detailed analysis is done.
These starting points include:

Piping & Instrument Diagrams:
These contain the details of the equipment in the plant
Usually available before the analysis is done
If not available, the requirements analysis has the opportunity to document or even influence the basic design process

Control & Operability Philosophy:
This should contain the general principles that the end user will want to apply to the project. It should define the level of automation that is required, the information handing needs and the operational requirements.
Typical issues are:

  • What level of flexibility is required? The plant may be dedicated to a single product and always use the same recipe. Or the plant may be intended to make a large range of products. These issues can influence the requirements' analysis considerably.
  • How far up the procedural model should the automation extend? For example, some operators want phases automated but operations and procedures to be manual.
  • What level of batch reporting and management information will be required?
  • Who operates the plant?
  • Where do the operators work?
  • What skill levels they will have?
  • ·
    Process Description
    This is typically written by a process engineer, often without reference to S88
    Useful starting point for the analysis
    May be superseded by the document that is generated as a result of the requirements analysis
    Should provides a basis for Process Recipes

    Equipment Protection Requirements
    This is typically p
    rovided by mechanical equipment suppliers needs.

    Describe the Physical Model
    This involves finding and describing the entities in the physical model, specifically the Units, Common Resources, Equipment modules and control modules

    Describe the Procedural Model
    This involves finding and describing the entities in the Procedural model, specifically the Recipe, Operations, and Phases


    S88 Physical Model S88 Procedures P&ID Process Descriptions


    Page Review Status: None Version 346