codac, cis and css implementation plan may 2009

31
Implementation Plan – CODAC – May 2009 Page 1 CODAC, CIS and CSS CODAC, CIS and CSS Implementation Plan Implementation Plan May 2009 May 2009 Luigi Scibile On Behalf of the CODAC team (slides extracted and updated from the PMWG meeting 21-22 January 2009)

Upload: chi

Post on 13-Jan-2016

29 views

Category:

Documents


2 download

DESCRIPTION

CODAC, CIS and CSS Implementation Plan May 2009. Luigi Scibile On Behalf of the CODAC team (slides extracted and updated from the PMWG meeting 21-22 January 2009). Introduction. The implementation plan Some clarifications on terms and scope Integrated Product Team (IPT). Scope. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 1

CODAC, CIS and CSSCODAC, CIS and CSSImplementation PlanImplementation Plan

May 2009May 2009Luigi Scibile

On Behalf of the CODAC team(slides extracted and updated from the PMWG meeting 21-22 January 2009)

Page 2: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 2

• The implementation plan

• Some clarifications on terms and scope

• Integrated Product Team (IPT)

Introduction

Page 3: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 3

This plan covers• The design, implementation, installation, integration and

commissioning of the Central Instrumentation & Control System (CODAC, CIS and CSS)

• The definition, support, maintenance and enforcement of standards for and interfaces to Plant Systems Instrumentation & Control

This plan does NOT cover• The development, installation and commissioning of Plant

Systems Instrumentation & Control• Any activities after First Plasma (operation, upgrades,

decommissioning)

Scope

Page 4: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 4

Clarifications - Problem with the word CODAC

The word “CODAC” is heavily overloaded and means different things in different contexts and for different people.

Scope problem: whether CODAC means “central systems” or it includes plant systems and all ITER I&C in general.

Scope problem: whether CODAC includes Safety and Interlocks or not.

This leads to confusion in technical documents as well asin internal and external verbal communication.

We need clear definition of terms.

Page 5: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 5

Plant Systems I&C

Central I&C Systems

CODAC System

Central Safety System

Central Interlock System

ITER I&C System

ITER Instrumentation & Control System Includes all hardware and software required to operate the ITER machine. Comprises Plant System I&C and Central I&C Systems.

Central I&C SystemsInclude all hardware and software required to coordinate and orchestrate all Plant Systems I&C and provide the human machine interface. Comprise CODAC System, Central Interlock System and Central Safety System.

Plant Systems I&CIncludes all hardware and software required to control a Plant System stand-alone and autonomously.

Definition of terms

Page 6: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 6

Page 7: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 7

• We need a good description of required work and deliverables

• We need a schedule, up to first plasma, linked to milestones in the Integrated Project Schedule

• We need required staff profile in time and skills

• We need to identify required contracts and when they are needed taking into account tendering time

• We need an accurate cost estimate

Plan objectives

Page 8: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 8

• Divide the required Central I&C work in major tasks

• Identify deliverables (as defined in Product Breakdown Structure) for each major task

• Identify required deliverables to meet key milestones as defined in the Integrated Project Schedule

• Identify required resources, both capital costs (contracts) and IO staff

• Assign staff (existing and new) to tasks with clear objectives and responsibilities

Strategy

Page 9: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 9

IPS v2.2, May 16, 2008

01/2012: Start factory test07/2013: Start installation control infrastructure11/2013: Start commission cooling water heat

rejection system (first Plant System)06/2014: Control building ready10/2015: Completion of tokamak basic assembly06/2017: Start integrated commissioning01/2018: Final integrated tokamak commissioning07/2018: ITER First Plasma

Key Milestones and Major Tasks

Major Tasks

Task 1 – CODAC Core SystemsTask 2 – Interface Plant Systems I&CTask 3 – Network InfrastructureTask 4 – CODAC ServersTask 5 – Central Interlock SystemTask 6 – CODAC Application SystemsTask 7 – Central Safety SystemTask 8 – Control RoomTask 9 – Integration and VerificationTask 10 – Commissioning

Page 10: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 10

CODAC Core Systems comprise the hardware and software required to interface and test Plant System I&C.HW platforms: Plant System Host and Mini CODACSW: Communication middleware, PS self description schemas and tools, SCADA functionality; logging, alarming, error handling, reporting, configuration, database and HMI.Supply and delivery of Plant Systems Hosts and High Performance Networks interfaces

Deliverables45-03-SP – Slow control PSH 45-07-PS – Generic PS software45-03-FP – Fast control PSH 45-07-EL – Error and trace logging45-04-MC – Mini CODAC 45-07-AH – Alarm handling45-04-SM – Plant simulator 45-07-LD – Live database45-06-PS – PSH OS 45-07-VB – Visualization builder45-06-SS – Server OS 45-07-RG – Report generator45-07-CM – Communication. Middleware 45-10-SD – PS self description

ScheduleIPS constrain: Factory Acceptance Test to commence 01/2012Yearly releases to start 12/2009

ResourcesTo be disclosed after consolidation

Task 1: CODAC Core Systems

Page 11: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 11

Define, support and enforce Plant Systems I&C standards.Interface closely with and review PS I&C development.Regular releases of Plant Control Design Handbook and supporting documents.Active participation in SRD, S-ICD, DDD, PA and design reviews.Follow closely the design, manufacture and testing of Plant Systems I&C. Active participation in Factory Acceptance Tests and Site Acceptance Tests.

Deliverables45-10-SC – Catalogue of standard components 45-12-PS – Programming Standards45-12-NL – Naming and labeling 45-12-VA – S/W versioning and ArchivePlant Control Design HandbookPlant System Profile DatabaseReview Reports

ScheduleIPS constrain: Links to Detailed Procurement Arrangement schedule.Yearly releases of PCDH linked to Core Systems releases

ResourcesTo be disclosed after consolidation

Task 2: Interface Plant Systems I&C

Page 12: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 12

The Network Infrastructure comprises site cabling, hutches, switches and other equipments in network hutch cubicles. Networks to be designed including technology and transport media.Coordination with PO/CCS to reserve volume for hutches as well as cable trenches.Large procurement and installation contract. Installation requires close coordination with CCS and SSEPN (power cable installation)

Deliverables45-02-ON – Plant Operation Network (PON) 45-02-EN – Event Handling Network (EDH)45-02-TN – Time Communication Network (TCN) 45-02-AN – Audio Video Network (AVN)45-02-SN – Synchronous Databus Network (SDN) 45-05-BI – Technical building infrastructure

ScheduleIPS constrain: Start installation of control infrastructure 07/2013Internal milestones: Network design completed 01/2011, Network infrastructure completed (12/2014)

ResourcesTo be disclosed after consolidation

Task 3: Network Infrastructure

Page 13: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 13

CODAC Servers comprise all computers installed in the computer and control rooms in the control building.Definition and procurement.Due to the long timeline and fast technology evolution for this type of equipment it is foreseen that CODAC Servers will be updated before First Plasma.

Deliverables45-01-FS – File Servers 45-01-PS – PS Support Server45-01-DS – DB Servers & Storage 45-01-FC – Fast Feedback Controller45-01-AS – Application Servers 45-01-WS – Work Stations

ScheduleIPS constrain: Control building ready 06/2014Internal milestones: Start definition of servers (06/2012), MCR operational (06/2015), Start upgrading servers (06/2017)

ResourcesTo be disclosed after consolidation

Task 4: CODAC Servers

Page 14: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 14

The Central Interlock System comprises the hardware and software to implement inter Plant Systems interlocks. Provides, together with local Plant System Interlock System, the machine protection system.Definition, design, implementation, procurement, installation and commissioning of CIS.Aim is to have CIS installed at the time of first Plant System arrival.

Deliverables46-01-EA – Events & Action 46-02-MC – Operation Control Room46-01-MO – Monitoring 46-02-EX – Physics Control Room46-01-NW – Network 46-02-BC – Back-up Control Room46-02-BL – Building(PBS 46 is under re-consideration)

ScheduleIPS constrain: Start commission cooling water heat rejection system 11/2013.Central Interlock System to be released yearly starting 07/2013

ResourcesTo be disclosed after consolidation

Task 5: Central Interlock System

Page 15: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 15

CODAC Application Systems comprise all software running on the CODAC Servers.Functionality comprises everything required to integrate all Plant Systems and to operate ITER.Reuse middleware and frameworks delivered from CODAC Core Systems.

Deliverables45-08-OG – Operation Request Gateway 45-10-OC – Operation Configuration45-08-VA – Visualization Applications 45-10-CL – Configuration and Location DB45-08-PC – Plasma Feedback Control 45-10-BT – System Deployment Tool45-08-SS – Supervision System 45-11-DT – Diagnostic Tools45-08-SM – Schedule Management 45-11-MT – Maintenance Tools45-08-PS – PS Specific Applications 45-11-NT – Network Monitoring Tools45-09-DA – Data Archiving 45-11-RT – Regression Testing Tools45-09-DR – Data Retrieval 45-11-ST – Plant Simulator Tools45-10-CC – CODAC Configuration

ScheduleIPS constrain: Start commission cooling water heat rejection system 11/2013.Internal Milestones: CODAC and CIS Integration Phase 1 (07/2013), MCR Operational (01/2015)CODAC Application System to be released yearly starting 12/2012

ResourcesTo be disclosed after consolidation

Task 6: CODAC Application Systems

Page 16: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 16

The Central Safety System comprises the hardware and software to implement safety monitoring and functionsCentral safety monitoring available at the time of first Plant System arrival.Central safety functions will be added later.

Deliverables48-01-EA – Central Safety Events & Action 48-02-XX – Fire Safety System48-01-MO – Central Safety Monitoring 48-04-BL – Buildings48-01-NW – Central Safety Network 48-04-MC – Operation Control Room48-02-EA – Central Access Control Events & Actions 48-04-EX – Physics Control Room48-02-MO – Central Access Control Monitoring 48-04-BC – Back-up Control Room48-02-NW – Central Access Control Network(PBS 48 is under re-consideration)

ScheduleIPS constrain: Start integrated commissioning 07/2017.Internal Milestone: CODAC, CIS and CSS ready (01/2017)Central Interlock System to be released yearly starting 07/2014 (monitoring) and 12/2016 functions

ResourcesTo be disclosed after consolidation

Task 7: Central Safety System

Page 17: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 17

Control Room comprises MCR and ECR in the control building with equipments required to operate ITERDefinition and procurement of equipments in Main Control Room (MCR) and Experimental Control Room (ECR). Equipments comprise screens, input devices, large screens, cabling and furniture.Coordination with PO/CCS to define volume, false floors, penetrations, cooling etc.

Deliverables45-01-CI – Control Room Infrastructure

ScheduleIPS constrain: Control building ready 06/2014Internal milestones: MCR operational (01/2015)

ResourcesTo be disclosed after consolidation

Task 8: Control Room

Page 18: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 18

Final Integration and Verification of CODAC, CIS and CSS.Support ITER integration activities.It is important to separate development and integration. Integration has a different role and shall be carried out by a different team. Integration team received the system from development team and hand it over to commissioning team at completion.

DeliverablesPBS 45 – CODACPBS 46 – Central Interlock SystemPBS 48 – Central Safety System

ScheduleIPS constrain: Start integrated commissioning 06/2017, Final integrated tokamak commissioning 01/2018Internal milestones: CODAC, CIS and CSS ready (01/2017)

ResourcesTo be disclosed after consolidation

Task 9: Integration and Verification

Page 19: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 19

Commissioning of CODAC, CIS and CSS.Verification of all functional and non-functional requirements.It is important to separate integration and commissioning. Commissioning has a different role and shall be carried out by a different team. Commissioning team received the system from integration team and hand it over to operation team at completion.

DeliverablesPBS 45 – CODACPBS 46 – Central Interlock SystemPBS 48 – Central Safety System

ScheduleIPS constrain: Final integrated tokamak commissioning 01/2018, First Plasma 07/2018

ResourcesTo be disclosed after consolidation

Task 10: Commissioning

Page 20: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 20

Tentative Schedule

Page 21: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 21

Tentative Schedule

IPS: Start factory

test

Page 22: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 22

Tentative Schedule

Internal milestone:

Network design completed

Internal milestone: Network

infrastructure completed

IPS: start commissioni

ng

IPS: control building ready

Page 23: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 23

Tentative Cost – Not consolidated

Internal resources (IO staff)

Capital cost (contracts,

external staff)

Page 24: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 24

CODAC, CIS and CSS contracts and tasks – Jan 2009

Page 25: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 25

4. What is “I&C IPT”?

Page 26: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 26

• A tool to allow better management between the various participating partners (IO, DA and contractors).

• Instrumentation and Control (I&C) IPT is being setup, because:

– There is indispensable need for standardizing all I&C

– There is indispensable need for successful integration of Plant Systems I&C into Central I&C Systems

– There is indispensable need for an integrated design of Plant Systems I&C and Central I&C Systems

– A single I&C IPT must cover all aspects of I&C design in Central I&C Systems and Plant Systems I&C.

– There is indispensable need that this I&C IPT is centrally coordinated from IO to guarantee its compatibility with CODAC System, Central Interlock System and Central Safety Systems.

Integrated Product Teams

Page 27: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 27

Mission Statement

Ensure all ITER Plant Systems Instrumentation & Control are designed, implementedand integrated such that ITER can be operated as a fully integrated system.

Instrumentation & Control IPT

Strategy

• Create groups of Plant Systems and prioritize• Each group has multiple teams • Each team has 5-10 (not more!!!) members• Team leader is IO I&C staff• Team members provide links to

• Plant System process• Domestic Agencies I&C• Suppliers (industry / institutes)

Use standards (Plant Control Design Handbook, PCDH)

Page 28: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 28

Instrumentation & Control IPT

10 Plant Systems Group27 PBS

165 Plant System I&C

Staged implementation!

What is most urgent?

Page 29: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 29

Instrumentation & Control IPT

Page 30: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 30

Instrumentation & Control IPT

Coordination between Plant Systems I&C

Coo

rdin

atio

n be

twee

n P

lant

S

yste

m I

&C

and

Pro

cess

Coo

rdin

atio

n be

twee

n P

lant

Sys

tem

I&

C a

nd I

ndus

try

STANDARDS (PCDH)

• Development lifecycle with deliverables• Components (hardware and software)• Interfaces

Coo

rdin

atio

n be

twee

n D

A a

nd I

O I

&C

Page 31: CODAC, CIS and CSS Implementation Plan May 2009

Implementation Plan – CODAC – May 2009 Page 31

Conclusion

• We have started developing an implementation plan for CODAC, Central Interlock System and Central Safety System

• This plan is being consolidated and it will be distributed via the PMWG

• This plan will need to be re-aligned should there be any new releases of the Integrated Project Schedule

• The I&C IPT will allow a better integration of the different systems and people contributing to the implementation of the ITER Instrumentation and Control.