Giobatta Lanfranco, Evangelia Vaena

ESTABLISHING THE BACK-OFFICE FOR ACCSYS PLANT INTEGRATION

www.europeanspallationsource.se July 3, 2014

GOALS

2

Easy exchange data internally, externally (IKC, suppliers)

safely

easily

Interact with a well integrated virtual 3D model of the accelerator

Stay up-to-date and not use obsolete data / configurations (revision control)

Reduce time spent on communication for data exchange

HOW TO REACH OUR GOALS

3

We need tools made for integration that handle integration

Such tools are built on a PDM architecture

PDM = Product data management

OUTLINE

4

This presentation

PDM requirements

Data flow: now and proposed one

Tools: the AIG* way

Live demo on proposed solution for AIG

* Accelerator Integration Group

HIGH LEVEL REQUIREMENTS FOR ACCSYS PDM

5

Requirements focus on PDM tools for successful and timely plant integration

Requirements evaluation was presented in February to Design Office and evaluation was completed by wk10, 2014

Many (see next slides) months were estimated necessary to satisfy just some of the highest level requirements without an interim solution

6

ACCSYS PDM HIGH LEVEL REQS (1/3)

ID Requirement Headings and Text [months]

REQ_59The CAD software shall be capable of generating simplified defeatured part configurations such as space envelopes.

12

REQ_85The CAD software shall be capable to handle fully parametric large assemblies. 12

REQ_89The CAD software shall be capable to visualise the full ACCSYS assembly in light model fluidly. 12

REQ_8 The CAD software shall provide 3D spatial interface management and clash detection.

6

7

ACCSYS PDM HIGH LEVEL REQS (2/3)

ID Requirement Headings and Text [months]

REQ_33The PDM software shall provide 3D instances tagging according to the ESS naming convention. 6

REQ_37 All data shall be subjected to configuration control. 6

REQ_38 All data shall be subjected to revision control. 6

REQ_95 The PDM software shall be capable of enforcing the ACCSYS PBS structure onto the CAD assembly tree.

6

8

ACCSYS PDM HIGH LEVEL REQS (3/3)

ID Requirement Headings and Text [months]

REQ_55The CAD software shall allow accurate* placement of beam lattice critical components in the 3D environment according to their location (set by the skeleton).

4

REQ_87 The CAD software shall provide light model* visualization of assemblies with more than 500'000 parts. 4

REQ_93Data structure organization and data structure modification shall be capable of following the ACCSYS PBS and WBS structure.

4

REQ_12 User groups shall have access to the repository from outside ESS.

0 ?

9

CURRENT ESS-INTERNAL DATA EXCHANGE

☹ Takes a long time ☹ ‘Double-handling’ ☹ Data is lost in conversion ☹ CF configuration has a machine configuration 3 weeks old, and vice versa

CHESS%

CF# Accelerator##

‘DO%Back%Office’%%

converted#CAD#building#model##into%Ca4a%V6%

NavisWork#source#building#model%

source#CAD#machine#model##in%Ca4a%V6%

converted#CAD#machine#model##into%STEP%

Takes%up%to%3%weeks%!%

…%and%another%3%weeks%

DATA#LOSS#

PROPOSED DATA ARCHITECTURE, FLOW AND PDM TOOLS - STEADY POINTS

10

CHESS remains the ESS ultimate data repository where data exchange and sharing among all ESS project occurs

ACCSYS database must be developed, handled and owned by Accelerator to manage data used by each Accelerator partner, IKC and supplier.

Single point of truth for any data

Included ACCSYS master assembly

Incidentally, model for ACCSYS data exchange back office follows CF’s!

11

Manual

Automatic

NAVISWORK

11

Manual

Automatic

NAVISWORK

11

Manual

Automatic

NAVISWORK

11

Manual

Automatic

NAVISWORK

NAVISWORK

12

NAVISWORK

12

Virtually CAD-platform independent allows robust clash detection

V5

NAVISWORK

12

Virtually CAD-platform independent allows robust clash detection

Handle most of native CAD formats (but V6…) included Sketchup (up to V8) and civil engineering software (such as Revit)!

V5

NAVISWORK

12

Virtually CAD-platform independent allows robust clash detection

Handle most of native CAD formats (but V6…) included Sketchup (up to V8) and civil engineering software (such as Revit)!

Manage large assemblies, fast!

V5

NAVISWORK

13

Allows installation sequencing, detection of installation interferences and helps simulate construction schedules and logistics.

Connect model to MS Project and Primavera P6 activities!

It is a worldwide standard, today

It’s easy!

VAULT

14

A collaboration environment (a PDM!) that enhances NavisWork capabilities

Single source for data

Efficient data searching

Automatically track evolution and important milestones

Track design and project history

Lifecycle with mail notifications

Vault Office: the thin client version

BUZZSAW, THE MISSING LINK

15

No need to install additional software (true also for Vault Office)

It’s for the “outside world”

Secure access anywhere and managed cloud storage

Seamless mirroring with Vault

Mail notification when new files become available

Possibility to create and administrate several Buzzsaw sites

Users can be added and removed on the fly also by non-administrator

WAKE-UP! TIME FOR A QUICK DEMO!

DEMO

17

NavisWork

Visualise

Measure

Clash detection

Vault

Data structure

Manage data (checkin/-out, review/revise)

Vault Office / BuzzSaw

Upload / download