Seimens have a prototype. Japanese have also done something similar but showed PLIB referencing. Next week a workshop with 212 team is planned at Siemens, Germany. 8-9 examples to be walkthroughed - should get feedback in or before Beijing.
Usage guide has 4-5 examples for shipbuilding. The guide was distributed at meeting in electronic form.
Qaualification meeting： QCV is coinsidering parallel development of ATS with APs. This will result in a better AP.
Implementor's Forum： Tim Turner
Shipbuilding Implementations：
SCM example was described to them as for the application of IRs. 216 do not yet used that whereas 217 has used it.
MariSTEP presentation - Burt Gischner - Presented the successful exchange of data based upon AP216 between partners of the MariSTEP project. A small number of technical changes had been required as follows. Tolerencing issue - needed a new entity to record each systems accuracy used.
Using GUID. Associative geometry - spacing position needs to be able an External Instance Reference (EIR), and also to be able to treat one instance as a boundary. i.e. a GUID is required for something that is to be externally referenced like frame number. Should use BB "s.p.with.station.reference" perhaps? EIR candidates must have a GUID. AP209 composite structural analysis translator was able to read 216 file with a schema name change. This enabled access to PATRAN and ProEngineer, and development of FE meshes.
SEASPRITE - additional note by Tim Turner - EU based exchange of 218 shown in the Orlando STEP meeting. Exchange of 216 also successful - see EMSA Newsletter. Both projects will look at schema harmonisation and possible transatlantic exchange.
Process plant - AP221 David Adams presented; EPISTLE (European Process Plant Initiative STEP Liaison Executive...) Is becoming an equivalent Nat. body in terms of being able to distribute work efforts (previously all voluntary). Setting up industry user group (no vendors). See www.stepcom.ncl.ac.uk. Vendors have own group - apprehension without users being present.
｡?TAP - failure of systems from simple errors catastrophic result - not graceful degradation. (using 221)
● Pippin - own data model - populated very quickly.
● More jobs for Shell Sheerwater based upon 221/POSC Caesar etc.
● Class library management being harmonised across a number of projects for Reference data libraries.
Larry MacKee： Big issues
New modules - new resources hence new part 50s slot proposed.
Accuracy Problem - exchange of solids over 90% successful, but not for other stuff like geometry bounded wireframe. However, just by doing solids doesn't mean that lower rep will be more successful since translators might not be that rigorous. Heeling tool, helpful but cause problems if not done right. Removes holes and gaps etc. and works in isolated instances. Perhaps the best advice
