Installation and Commisioning SE view point Romuald Duperrier ESS SE manager.

Slides:



Advertisements
Similar presentations
System Integration Verification and Validation
Advertisements

Software Quality Assurance Plan
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
SAE AS9100 Quality Systems - Aerospace Model for Quality Assurance
TECH 101 Product Design and Manufacturing. TECH 1012 System Life-Cycle Engineering 2 Major phases in almost all products and in many cases services –Acquisition.
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
CSE Senior Design II Test Planning Mike O’Dell Based on an earlier presentation by Mike O’Dell, UTA.
Introduction to Software Testing
Software Testing & Strategies
IV&V Facility Model-based Design Verification IVV Annual Workshop September, 2009 Tom Hempler.
Development plan and quality plan for your Project
BAE SYSTEMS Overview of Systems Engineering at BAE SYSTEMS & ALENIA MARCONI SYSTEMS 8/10/2015/MS By Leigh Watton Friday 27th July 2001.
Engineering Systems of.
LSU 01/18/2005Project Life Cycle1 The Project Life Cycle Project Management Unit, Lecture 2.
N A managed approach to planning and controlling the implementation of complex application software. n A flexible tool kit, designed to support the Project.
Effective Methods for Software and Systems Integration
Chapter 2: Overview of Essentials ISE 443 / ETM 543 Fall 2013.
Web Development Process Description
Introduction to Software Quality Assurance (SQA)
Chapter 6 Software Implementation Process Group
Software Testing Lifecycle Practice
Software Inspection A basic tool for defect removal A basic tool for defect removal Urgent need for QA and removal can be supported by inspection Urgent.
FCS - AAO - DM COMPE/SE/ISE 492 Senior Project 2 System/Software Test Documentation (STD) System/Software Test Documentation (STD)
SENG521 (Fall SENG 521 Software Reliability & Testing Software Product & process Improvement using ISO (Part 3d) Department.
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
Main Requirements on Different Stages of the Licensing Process for New Nuclear Facilities Module 4.1 Steps in the Licensing Process Geoff Vaughan University.
© Mahindra Satyam 2009 Configuration Management QMS Training.
University of Southern California Center for Systems and Software Engineering Barry Boehm, USC CS 510 Software Planning Guidelines.
Pre-Project Components
1 15 quality goals for requirements  Justified  Correct  Complete  Consistent  Unambiguous  Feasible  Abstract  Traceable  Delimited  Interfaced.
NCSX Systems Engineering Management Plan Peer Review Bob Simmons May 15, 2003.
Configuration Management Romuald Duperrier Head of Systems Engineering Division April 22, 2015.
Software Requirements Specification Document (SRS)
SRR and PDR Charter & Review Team Linda Pacini (GSFC) Review Chair.
1 Lecture 2.4a: SEF SE Planning and the SEP (SEF Ch 16) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Software Test Plan Why do you need a test plan? –Provides a road map –Provides a feasibility check of: Resources/Cost Schedule Goal What is a test plan?
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
Collaborating for Quality Quality Assurance (QA) & Quality Control (QC) in the Accelerator Project (ACCSYS) Matthew Conlon ACCSYS QA/QC
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
CS646: Software Design and Architectures Introduction and Overview †  Definitions.  The general design process.  A context for design: the waterfall.
Testing throughout Lifecycle Ljudmilla Karu. Verification and validation (V&V) Verification is defined as the process of evaluating a system or component.
1 Interfaces, Engineering and Standards. 2 Interfaces LoKI Interface document description for deliverables Elements: PBS number, Deliverable description,
Collaborating for Quality through the Project Quality Plan Matthew Conlon ESS ACCSYS QA/QC Quality Learning & Planning.
Supportability Design Considerations
Software and Systems Integration
IEEE Std 1074: Standard for Software Lifecycle
FC facilitation of Installations
Session 5b Dr. Dan C. Surber, ESEP
Software Requirements
Manfred Huber Based on an earlier presentation by Mike O’Dell, UTA
Level - 3 Process Areas (CMMI-DEV)
Enabling System Elements
Engineering Processes
Introduction to Software Testing
Test Planning Mike O’Dell (some edits by Vassilis Athitsos)
CLINICAL INFORMATION SYSTEM
EMIS 7307 Chapter 6.
Click to add title Planning for LSST Verification George Angeli LSST All Hands Meeting Tucson August 15, 2016.
System Modeling Assessment & Roadmap Joint OMG/INCOSE Working Group
Engineering Processes
PSS verification and validation
Software Testing Lifecycle Practice
Technical Documentation Coordinator
Machine Protection PLC Based System Verification and Validation Plan
Atefeh Sadeghzadeh Control engineer – Target safety and control
ESHAC #8 Safety Readiness Review Thomas Hansson, ESH
Software Reviews.
KEC Dhapakhel Lalitpur
Presentation transcript:

Installation and Commisioning SE view point Romuald Duperrier ESS SE manager

Terms and definitions [ISO/IEC/IEEE 15288/15289] Installation > Integration: Assemble the implemented system elements. Interface are indentified and activated to enable interoperations. Enabling systems to facilitate interoperations are included. Commissioning > Verification : Activity to provide objective evidence that the system fulfils its specified requirements. Identify anomalies and necessary information to resolve them. 2

Funding profile and facility lifecycle 3 Design phase Procurement and Installation phase Procurement and Installation phase Commissioning phase Decommissioning phase Operation phase PDR TRR ORRSAR Construction Steady state Operations Decommissioning First Beam on target Handover to Operations Start of user programme 2065 Initial Ops 2011 Integration and Verification phase Validation phase Pre construction 2019

SEMP: Integration planning The equipment and/or software products to be integrated referred by their PBS Id. Integration strategy, each step. Supporting human resources (quantity and nature). The location of the activities, Any support equipment (special software, test hardware, and drivers to simulate yet-to-be-integrated software components, external systems e.g. tooling) needed for this integration step. Consumables. A description of the verification activities that occur after integration step (not in detail but traceability to the Verification Plan content must be unambiguous). The responsible parties for each activity in the integration step. The schedule for each activity Template is ESS

SEMP: Verification planning The Verification Plan identifies the specific verification cases to be performed. A complete list of the requirements to be verified called in by their Id and traced to the corresponding verification case. Any data to be recorded or noted during the verification, such as expected results of a verification step. A statement of the pass/fail criteria. This may be just a statement that the system operates per the requirements, A description of the verification configuration. That is a list of the hardware and software items needed for the test and how they should be connected/calibrated. Consumables. A list of any other important assumptions and constraints necessary for conduct of the verification case. A schedule of the activity. 5

Verification plan template [ESS ] 6

Verification report template [ESS ] 7

Recommendations (1/2) A large effort has been undertaken to developing requirements. This is the best way to prepare installation and commissioning. It is important to define further the corresponding verification activities (inspection, test, analysis, demonstration) and related integration activities. Verification is performed bottom-up at different levels of the PBS, escalation is supported by the integration activities. Let’s do the best use of our ESS breakdown structure for supporting the definition of the intermediate assemblies. 8

Recommendations (2/2) From the plans: – Identify risks (including safety) – Identify new requirements to facilate the performance of the plans. – Identify needs for training (cost and delays) – Identify needs for work permits (interface and delays) – Identify interfaces to other parties for anticipating concurrent activities (e.g. crane usage). Do consider enabling systems as a resource in the plan to detect double booking (room, tools). 9