ISO TC 184/SC 4/WG 3/T 23 (SHIP TEAM) AGENDA
Poiriers 2003
Theme: Ship APs, AP
239 PLCS, AP233 Systems Engineering, PDM Schema Modularisation
October 2003, Poitiers, France
See updated action list (Annex A)
See presentation (Annex B)
Ho-Jin Hwang gave a presentation of the status KS-STEP. New project has just begun 7.2003 – 7.2006
involving just KRISO – ship yards may review data.
The objective is to develop test cases for production processes such as
steel cutting, edge preparation and welding (to be used in STEP-NC). AIM/XML data will be generated using AP218.
The first year will do AP215:2004, 216:2003, 218:2004 and the second
year AP227 ed2.
They will construct a STEP database for bulk carrier, tanker and
container ships.
Ron Wood gave an update on the projects in the US (See Annex C).
All fall under the NSRP programme.
Industry wide effort to develop of an Integrated Shipbuilding
Environment
The project has 21 members including
Electric boat, Newport News, Niip, ABS, Bath Iron works, NASSCO,
Atlantec-es, STEP Tools, ERIM, SENER and The University of Michigan
The Final demo was held on 10 April 2003 and included data exchange between LEAPS, Intelliship, Flagship,
Foran, Safehull, TRIBON, CATIA and AutoCAD.
It was based around 4 scenarios:
The project will continue till 2004 to develop documentation and usage
guides.
This is a continuation project to do HVAC and common parts
catalogs. The participants include EB, NG, NIIIP, Intergraph, Atlantec and
Simsmart.
Participants are EB, Northrop-Grumman Ship Systems, Bath Iron Works,
(Northrop-Grumman –Newport News, NASSCO)
The objectives are:
The project will run from Sept 2003-sept 2004
Harvest ran from Oct 2001 to March 2003, the objective was to complete
the ship AP215:2004, 216:2003, 218:2004.
It has succeeded in that AP216:2003 was published August 1, and AP215
and AP218 are awaiting the incorporation of WG3 convenors comments. Should be published by about March next
year.
Integrated steel processing environment
Phase 0 ran from May 31 2002 – April 2003, and was requirements
collection for manufacturing rule base, work packages, CAM interfaces and
manufacturability. However phases 1-2 have not been awarded.
The STEP meeting for July 2004 is being hosted by EMSA in Bath, a world
heritage site due to its Toman and Georgian (18th Century)
architecture. The meeting will be held
at the University and accommodation rooms will be held in the Hilton
Hotel. EMSA are looking for sponsors
for the Sunday evening welcome reception.
The Tuesday evening event will be a tour of the Roman Baths in Bath
followed by a dinner in either the pump rooms or the Guildhall.
Burt gave an overview of the AP227 progress. (See Annex D for details)
A joint effort between process plant and shipbuilders. The DIS ballot concluded in June 2003 which
was unanimously approved. It should be
sent to Geneva in about Jan 2004.
Edition 2 scope included cableways, HVAC design and installation,
configuration change management, ship unique information, mechanical systems.
Translators have been developed by Dassault, CADDS, CATIA... for edition
1. Edition 2: Intelliship, TRIBON, CATIA, FORAN. A demonstration happened in April 10 2003.
Year 3 demo, Ship Constructor, SimSmart piping functional design sent to
product portal.
GD-EB are using AP227 internally to do pipe stresses.
A new project for HVAC will run from Oct 2003 to Sept 2004 consisting of
CATIA, FORAM, Intelliship, SIMSMART, TRIBON.
An AP227 usage guide meeting will be held at December 3-4 at NIST.
Philippe gave an overview of the thickness measurement project (See
Annex E).
The project is designed to produce a standard of the exchange of
thickness measurements. They start from
the 3D Product data model to which the thickness measurements are
attached. However the 3D model is not a
complete model but a ‘shoe box’ model i.e. bottom, weather deck and
bulkheads. This is supported by a
hierarchical and topological model, there is no detailed geometry. This amounts to about 1 days effort for each
ship, which is necessary as they have thousands of ships.
Original thickness, measured thickness, cracks, coating condition and
comments.
The system they are envisaging will use 2 operators one entering data
who will position the TM on a graphical interface on the PC and one operator
(or robot) doing the measurements.
Philippe gave a run through of his STEP implementation white paper (See
Annex F).
His vision is that functionality will be integrated in-house within the
shipyards as a single system, which will communicate through web based
portals. STEP is therefore needed to
communicate between these clusters. The
main application area will be machinery exchange.
Rob Bodington gave a presentation on the Product Lifecycle Support
Standard (AP239) (See Annex G)
PLCS is a joint industry and government initiative to produce a standard
which will ensure that support information for a product is aligned to the
evolving definition over the entire lifecycle.
Rob gave an overview of the scope and potential uses for the standard,
and also an overview of the modular structure of the AP. See also the plcs web site http://www.plcs.org.
A module is somewhat simlar to a T23 building block, but is more
detailed as it is constructed like a mini AP with scope, ARM and MIM (module
Integrated Model).
A-Liaisons may make SC4 standards available to their members free of
charge.
This means that EMSA as an A-liaison may make all STEP standards
available to its members free of charge on its web site. The EMSA coordinator will be putting those
that are currently available in the members area of the EMSA web site.
JK to apply to the SC4 secretariat to get the electronic version of
those standards which are available.
Nils Sandsmark gave an overview of the Data Exchange Sets (DEXS) concept
which is used by PLCS for defining the information requirements for exchange
within certain business scenarios (See Annex H). There were originally 35 DEXs, but there are now nine which are
being developed:
1. Product breakdown for support
2. Fault states
3. Task set
4. Workpackage definition
5. Maintenance plan
6. Support drivers
7. Operational feedback
8. Product as individual
9. Workpackage reporting
These 9 are approximately 50% complete.
The data for the DEXs are collected in spreadsheets; much of it is
reused Reference Data libraries developed by ISO 15926 (A sister stand to STEP
for lifecycle data in the Oil and Gas industries).
This is being tested in a Frigate project for the Norwegian Navy (See
Annex I). The frigate is being built by
IZAR. Their data is being mapped into
PLCS and loaded into a PLCS database (an EPM tool). The data will then be transferred into SAP v4.6 which is being
used by Norwegian Defence in the future, the transfer will be done according to
the 9 DEXs.
DNV and Norwegian Defence will go for ISO 15926 for the Reference Data.
Jim U’Ren Nasa JPL chair of AP233 group gave a presentation on the
systems engineering data representation AP233.
Systems engineering is managing, structuring and allocating requirements
including the design product breakdowns – physical, functional and system. This includes Rules, Scheduling, Risk
analysis, behaviour models.
AP233 builds on work done in the EU funded SEDRES project, but has been
produced as a modular AP and now conforms to the requirements of INCOSE, the
International Council on Systems Engineering.
They also collaborate with work going on in OMG.
A large consortium including Northrop Grumman, BAE Systems, UK MoD and
NAVSEA.
The modules for AP233 are still in development and there are still some
areas which need sponsors for development including risk analysis.
They have a demonstrator which has import/export interfaces with Word,
Excel, RequisitePro, Doors, Vitech CORE and STEP PDM Schema.
GL stated that they may have interest in Risk analysis in the
future. NG-SS also do systems
engineering and requirements analysis.
It was noted that AP233 could cover the exchange of classification
society rules, as these are essentially requirements.
-
Benefits
-
Technical issues
-
Funding
PR: We need to make the most of
practical implementations of the existing basic APs before we spend time on
enhancing their capability with PLCS etc.
JM: The need for PLCS is clear,
AP233 less clear, but we need to use the ship APs first.
RW: System engineering is coming back strong and is being specified by
clients. But not specifying AP233. Additionally there are Oasis, W3c competing
efforts.
Japan: small committee, difficult to discuss PLCS, AP233. But can discuss AP227 based on AP226
JK: It would be desirable to have a usage guide for getting Ship APs
working with PLCS/SE
RW: Demonstrating usage is important.
They are using 203 which is a huge improvement over IGES/DXF, but they
haven’t got round to using 218 which would add more functionality.
Korea: do comment on 227. PDM Schema in PLCS is useful for BOM and
other properties of ship structures.
AP233
In summary, there was some support for looking into PLCS further,
particularly how they it could work with the ship APs, the need for AP233 was
less clear. Ideally a study should be
done to examine the business needs for the 2 APs within the marine community.
The next meeting is scheduled for Fort Lauderdale. It was felt that there would not be a need
for a only T23 meeting. T23 members are
interested in liaison with manufacturing, plant spatial configuration, and
other APs identified in the T 23 plan (Annex K) so the chair will distribute to
the T23 community a list of relevant activities (e.g. AP227, PLCS, AP233) which
will be happening there and individual T23 members can liaison with those
projects to represent the ship building community and report on their
activities at the Bath England meeting.
|
43rd |
2004-07-04/09 |
Bath, England |
|
44th |
2004-10-03/08 |
Seattle WA, USA |
|
45th |
2005-02-27/03-04 |
Lillehammer, Norway |
|
46th |
2005 (Summer) |
Valencia, Spain |
|
47th |
2005 (Fall) |
China |