Neil Bonel

1
Neil Bonel
2
(No Transcript)
3
WorleyParsons Historical Data

• TIGA JV select Intergraph's AIM System for Bayu
  Undan Project. 1999.
• WorleyParsons select SmartPlant Foundation as
  part of corporate toolkit. 2004
• Intergraph recommend SmartPlant Foundation BO
  model for fast track startup. Jun 05
• Australia develop Document Control Model in BO
  model. Jul 05 on
• All document control installations to date
  configured on BO model
• London develop Data Handover solution in SO
  model. Sept 05 on
• Houston commence TEF interface testing in SO
  model. Feb 06 on
• SP Data Loader introduced by Intergraph. Jun 06
• Workshops and development to implement SPF 2008
  commenced Dec 07
• Development on SPF 2008 model commenced April 08

4
Total token usage to July 08 127,950Average
12000 tokens per month globally
5
SPF Regional ProfileAug 08
6
Network Structure
7
Network Overview

• The SmartPlant Foundation global solution within
  WorleyParsons is based around a centralised
  application and Oracle database server.
• These servers are currently located in Perth
  Australia.
• The corporate investment in network and Internet
  cloud technology enables direct access to the SPF
  application from any office within the
  WorleyParsons domain.
• To further increase performance it is typical to
  install an additional file server in each
  location enabling search via Perth with results
  displayed locally. This performance enhancement
  is realised through change replication constantly
  monitoring alignment between Perth and the
  project location.
• Development of an https configuration enables
  external parties to gain entry to SPF within a
  secured environment.
• Integration of FTP or Microsoft's SharePoint is
  also widely utilised for delivery and receipt of
  Supplier data.
• Where infrastructure is poor not only in terms of
  network but also services etc. a standalone
  installation would be considered and an example
  of this would be Lagos in Nigeria.

8

• Key Developments

9

• Tag Extractor
• WorleyParsons/Intergraph developed tag extractor
• Extracts tags from non-intelligent 2D
  deliverables
• MicroStation or AutoCAD format
• Generates tag extraction file for import into SPF
• Generates relationships between 2D deliverable
  and document number for import into SPF
• Utilised in WorleyParsons London office for
  client data delivery

10
(No Transcript)
11
Supplier Data Functionality

• The Supplier/Vendor module has undergone
  considerable development recently.
• We now have separate business objects for PO, PO
  line Item, Requisition, Requisition Line Item and
  Enquiry business objects to allow full
  flexibility and traceability within SPF
• Supplier Revision forms now updated to include
  extra fields for the tracking of Supplier
  documents through their lifecycle.
• Development of vendor template with direct
  loading into SPF from completed return.
• Reporting interface to SPM to propagate document
  section.
• Current development on workflow automation
  including expediting.

12
Reporting
13
Reporting
14
Reporting
15
SPF User Manager (SUM)
16
Transmittal Export
17
Multi-Update
Development to allow the document controllers the
ability to batch update the Document Status of
Document Revisions. Other work is underway to
extend this functionality to a generic form to
allow the update of multiple properties against
multiple revisions.
18
Snippets

• New Functionality
• Email drag and drop
• Configuration and roll-out of secure internet SPF
  access via https
• DFS replication across multiple offices
• Vast improvements in bulk document loading
• Transmittal Automation
• Automatic updating of document revision
  attributes based on transmittal status and type
• Bulk extraction of documents for project handover
• Oracle tag and log of deleted files
• Restart workflow step for failed transmittals
• Set local file server
• Reset user windows

19
Lessons Learnt (Pre 2008)

• Not originally architected as a multi instance
  environment
• Poor reporting and performance OOTB
• No vendor data control or workflows
• Inferior web interface
• High expertise level required at administration
  level
• Data integration overwhelming and only realised
  at the tag level
• Hot fixes consistently introduced or reintroduced
  issues
• Multitude of data loaders developed at Intergraph
  regional level
• Token costing model complex for external parties
• Lack of token reporting mechanism at project
  level from global server

20

• SPF 2008

21
The Approach

• Delta training of existing WorleyParsons
  technical resources
• Establishment of regional SPF expertise through
  recruitment and training
• Distribution of development across regional hubs
• Re-architecture of existing BO development to SO
  model 6 month program
• Full user acceptance testing and documentation
  prior to project delivery
• Report Creation utilising ASP and Microsoft
  reporting engine
• Ongoing support of 2007 BO model for existing
  projects with selective migration plans
• Utilisation of automated vendor document control
  workflows
• Phased approach to full SPE integrationPhase 1
  SPPID and SPIPhase 2 Linelist and
  DatasheetsPhase 3 SP3DPhase 4 SPEL (Cable
  Schedule Management)Phase 5 SPI and SPELPhase
  6 SP3D and SPMatPhase 7 PDS and PDMS (Model
  Publisher)Phase 8 Zyqad
• Utilisation of multi domain environment
• Evaluation of SPF 2008 progressing

22
Key SPE Milestones

• Alignment on SmartPlant 2007 toolset versioning
• Completion of development on SPF 2008
• Creation of master PBS and publish from SPF
• Tool mapping exercise
• Architecture of SPE infrastructure
• Discipline workshops and workflow development
• Datasheet philosophy
• Publish and Retrieve cycle
• Supporting Documentation
• Training

23
Global SPE Network
24
Lessons Learnt (2008 to date)

• Powerful but more complex architecture enforcing
  more standardisation
• Re-training and new documentation required for
  existing users
• Ongoing transmittal issues
• Reporting OOTB still lacking
• Token issues still prevalent
• Realise requirement of SP3D for major benefits

25
Future Plans

• Smartforms development to produce content rich
  interface
• Binders development for medium level data
  handover
• Barcoding integration
• PDF extraction
• XML reporting interface
• MS Office integration
• Progressing
• Interfacing to WorleyParsons corporate toolset
  including PIMS and AutoPLANT

26

• Questions