VST: dome THE LIFE CYCLE OF MODERN TECHNOLOGICAL PROJECTS Ing. Davide Fierro THE LIFE CYCLE OF...

VST: dome

THE LIFE CYCLE OF MODERN THE LIFE CYCLE OF MODERN TECHNOLOGICAL PROJECTSTECHNOLOGICAL PROJECTS

Ing. Davide FierroIng. Davide Fierro

THE LIFE CYCLE OF MODERN TECHNOLOGICAL PROJECTSTHE LIFE CYCLE OF MODERN TECHNOLOGICAL PROJECTS

Typical Project Life Cicle

D. Fierro

WBS

0

nRequirements

DefinitionProduction &Verification


Phase 0 (MDR)

Project scope/needs identification

• Identificate the project scope, final user needs, expected performance, and project constraints

• Develop the preliminary requirements • Identify possible concepts• Perform preliminary assessment of programmatic

aspects (market and economic studies) • Define the risk policy and perform preliminary

risk assessment

D. FierroTHE LIFE CYCLE OF MODERN TECHNOLOGICAL PROJECTSTHE LIFE CYCLE OF MODERN TECHNOLOGICAL PROJECTS

MDR Mission (Project) Definition Review

Identification of user requirements and initial concepts

The primary objective of this review is• to release the project statement• to assess the preliminary technical requirements and programmatic aspects.

THE LIFE CYCLE OF MODERN TECHNOLOGICAL PROJECTSTHE LIFE CYCLE OF MODERN TECHNOLOGICAL PROJECTS D. Fierro

• Elaborate possible system, operations concepts and system architectures and compare these against the identified needs, to determine levels of uncertainty and risks.

• Develop the preliminary management plan, system engineering plan and product assurance plan for the project.

• Assess the technical and programmatic feasibility of the possible concepts by identifying the project constraints.

• Identify critical elements and propose pre development activities.

• Elaborate the risk assessment • Propose possible adjustment solutions, including model

philosophy and verification approach.

Phase A (PRR) Feasibility


PRRPreliminary Requirement Review

User requirements converted into overall system requirements, project feasibility and validation of system architecture

The primary objectives of this review are:• Validation of System Architecture• Release of the overall system requirements.• Release of project sub-system func. requirem• Selection of system and operations concept(s) and

technical solutions, including verification approach. • Confirmation of the technical and programmatic

feasibility of the system concept(s).


Phase B (SRR, PDR) Preliminary Definition

• Finalize the project management, engineering and product assurance plans.

• Establish the baseline master schedule.• Elaborate the cost baseline.• Conduct “trade off” studies and select the preferred system

concept, together with the preferred technical solution(s).• Establish a preliminary design definition for the selected

system concept and retained technical solution(s).• Determine the verification program including model

philosophy.


Phase B (SRR, PDR) Preliminary Definition

• Identify and define external interfaces.• Prepare the next level specification and related business

agreement documents.• Initiate pre development work on critical technologies or

system design areas when it is necessary to reduce the development risks.

• Initiate any long lead item procurement required to meet project schedule needs.

• Conduct reliability and safety assessment.• Finalize the product tree, the work breakdown structure

and the specification tree.• Update the risk assessment.


SRRSystem Requirements Review

System technical specification established

The primary objectives of this review are:• Release of system requirements specifications

including ext interfaces• Assessment of the preliminary design vs system

functional requirements.• Release of preliminary management, engineering

and product assurance plans.• Assessment of the preliminary verification

program.• Release of the controlled configuration procedure


PDRPreliminary Design Review

Preliminary design established

The primary objectives of this review are:• Verification of the compatibilty between design and

technical solutions against project requirements. Design Analisysis, TRL

• Release of technical requirements on each subsystem• Release of final management, engineering and product

assurance plans.• Release of product tree, work breakdown structure and

specification tree.• Release of the verification plan (including model

philosophy).• Development of ICD• Long-lead material procurement plans


Organization Plan


Roles and Responsibilities • The PI, Project Investigator, has overall responsibility for the

direction, execution, and completion of the project. He leads the Project ensuring that the scientific goals are achieved.

• The PM, Project Manager, have day to day responsibility for managing the project to achieve the goals within the approved schedule and budget. He develops the Project Program and supervices the Tender definition.

• The PE, Project Engineer, is responsible for overall engineering, logistics, production, integration and test tasks coordination and performance. The PE has the responsibility to establish the tech. spec, controls the common interfaces, defines the overall design and establishes procedures and plans


• The Project Controller monitor the progress of work and will provide the PM with the status of the activities. They makes periodic updates of the scheduling baseline and propose corrective actions, if necessary, to prevent and reduce any slippage that could occur during the project life.

• The Project Scientist, define the scientific requirements and has the responsibility of ensuring that the scientific objectives, specifications and programmes are adequately met.

• The AIV manager is the responsible of the final Instrument integration and logistic activities and supervises the execution of the final tests.

• The Documentation Manager has the responsibility of the codification, archiving and distribution of the Documentation. The DM can be in charge of the Configuration Control with the objective to establish and maintain a systematic change management process. (CIDL) Critical Item Data List

Roles and Responsibilities


Product Tree

D. Fierro

M1 CELL

MECHANICSELECTRONICS

& SWAUXILIARY

UNITSOPTICS

SUPPORT EQUIPMENT

CELL STRUCTURE

AXIAL ACTUATORS

LATERAL SUPPORTS

FIXED POINTS(AX. & LAT.)

SAFETY SYSTEMS

AXIAL ACTUATORSCONTROL BOARDS

AX. ACT. POWER DISTRIBUT. BOARDS

HARNESS

CONTROL SW

ADC

ROTATOR

CO-ROTATOR

ADAPTER

PROBE

TECHNICAL CCDs

PRIMARY MIRROR

ADC OPTICS

PROBE OPTICS

M1 HANDLING DEVICE

M1 COATING INTERFACE TOOL

TCS WORKSTATION

M1 ELECTRONICSCABINET

DUMMY OPTICS


WBS – Main level

D. Fierro

M1 CELL ACTIVITIES

MANAGEMENT10.000 - CAPACCIOLI

ENGINEERING20.000 - SCHIPANI

SUBSYSTEMS MAIT30.000

FIERRO/MOLFESE

VSTCen MANAGEM.11.000 - CAPACCIOLI

INDUSTRIALCONTRACTS MANAG.

12.000 - DE PARIS

SYSTEM INTEGRAT. & TEST50.000 - SCHIPANI

ESO I/F MANAGEMENT

13.000 - CAPACCIOLI

PROJECT CONTROL14.000 - DE PARIS

INDUSTRIAL TECH. MANAG.

15.000 - SCHIPANI

REQUIREMENTS SPECIFICATIONS21.000 - SCHIPANI

I/F DEFINIT. & CONTROL

22.000 - SCHIPANI

AXIAL ACTUATORSREFURBISHMENT31.000 TOMELLERI

ANALYSIS23.000 PERROTTA

S/S DESIGN24.000 - TOMELLERI

SAFETY SYSTEMSMAIT

33.000 TOMELLERI

LATERAL SUPPORTSMAIT

32.000 TOMELLERI

ASSEMBLY51.000 - TOMELLERI

ELECTRICAL INTEGRATION

52.000 - TOMELLERI

AUXILIARY UNITS MAINTAN. & VERIFIC.

40.000 - CAPUTI

TESTING53.000 - TOMELLERI

ADC MAINTAN. & VERIFIC.

41.000 - CAPUTI

ROTATOR MAINTAN. & VERIFIC.

42.000 - CAPUTI

HARNESSMAIT

34.000 TOMELLERI

CONFIGURATION MANAGEMENT

16.000 - SANTORO

CO-ROTATORMAINTAN. & VERIFIC.

43.000 - CAPUTI

ADAPTERMAINTAN. & VERIFIC.

44.000 - CAPUTI

PROBEMAINTAN. & VERIFIC.

45.000 - CAPUTI

COLOUR LEGENDA

INDUSTRIAL ACTIVITIES

VST TEAM ACTIVITIESSUPPORT EQUIPM.

DESIGN25.000 - FERRAGINA

SUPPORT EQUIPM.MAIT

35.000 - FERRAGINA


Phase C (CDR) Detailed definition

• Completion of the detailed design of the system at all levels in the customer supplier chain.

• Production, development testing and prequalification of selected critical elements and components.

• Production and development testing of engineering models, as required by the model philosophy and verification approach.

• Completion of assembly, integration and test planning for the system and its constituent parts.

• Detailed definition of internal and external interfaces.• Issue of preliminary user procedures.• Update of the risk assessment.• Made or buy definition• Justification file


CDRCritical Design Review

Detailed design established Development testing completed.

D. Fierro

The primary objectives of this review are:• Assessment of the qualification and validation status

of the critical processes.• Design justification files• Confirmation of compatibility with external interf.• Release the final design.• Release of hardware/software manufacturing

procedures. • Release assembly, integration and test planning.• Release of user manual.


• Complete qualification testing and associated verification activities.

• Complete manufacturing, assembly and testing of hardware/software components/prototypes.

• Prepare acceptance data package

• Complete the operational procedures

Phase D (QR, AR, ORR) Qualification & production


QRQualification Review

Integrate and test the qualification models or prototypes. Qualification of the design

The primary objectives of this review are:• To confirm that the verification process has

demonstrated that the design, including margins, meets the applicable requirements.

• To verify that the verification data package is complete at all lower levels in the customer‐supplier chain.

• To verify the acceptability of all waivers and deviations.


Qualification and test Tables


Verification Matrix


ARAcceptance Review

Integrate and test the full system

The primary objectives of this review are:• To confirm that the verification process has demonstrated

that the product is free of workmanship errors and is ready for operational use.

• To verify that the acceptance data package is complete at lower levels in the customer‐supplier chain.

• To verify that all deliverable products are available.• To verify the “as‐built” product components against the

required “as designed” product.• To verify the acceptability of all waivers and deviations.• To authorize delivery of the product.• To release the certificate of acceptance.


ORROperational Readiness Review

Operational readiness established

The primary objectives of this review are:

• To verify readiness of the operational procedures and their compatibility with the operational environment.

• To verify readiness of the operations teams.

• To accept all system for operations

• Declaration of operational readiness


Risk Areas• Requirement phase. Programmatic risks are first reduced by

assessing the system requirements. Excessive requirements are avoided.

• Development/production processes. Margin in performance may be included in the specification of subsystems. Where the performance of a subsystem can deviate from an ideal value a budget error will be calculated.

• Operational risks demand the following types of responses: avoidance of hazardous conditions (processes, materials, operational procedures), reduce the consequences of failure (e.g. by redundancy), management of degradation (by monitoring of condition).

A Risk Register will be maintained following the PDR.

Each risk source will have an “owner”, whose task it is to manage the risk


The primary objectives of this review are:• Perform all activities in order to allow the

starting of operation.• Perform the commissioning activities.• Perform all the operations in order to achieve

the project objectives.• Perform all maintenance activities to support

the operations.• Finalize the disposal plan.

Phase E (CRR, ELR) Operation/Utilization


CRRCommissioning Results Review

Performance fine tuning

The primary objectives of this review are:• Verification of the system readiness for final

routine operations/utilization. • Verify that all elements of the system are

performing within the specified performance parameters.

• Approve the formal handover of the system to the project initiator or to the system operator.


Maintenance Table


ELREnd of Life Review

End of useful time of operation or service

The primary objectives of this review are:

• To verify that the system has completed its useful operation or service.

• To ensure that all elements are configured to allow safe disposal.


D. Fierro

Implement the disposal plan & procedures

Phase F (MCR) Disposal


MCRMission Closure Review

The primary objectives of this review is:

• To ensure that all mission disposal activities are adequately completed


VST: dome THE LIFE CYCLE OF MODERN TECHNOLOGICAL PROJECTS Ing. Davide Fierro THE LIFE CYCLE OF...

Documents

Transcript of VST: dome THE LIFE CYCLE OF MODERN TECHNOLOGICAL PROJECTS Ing. Davide Fierro THE LIFE CYCLE OF...