should have the responsibility for producing the data model. Ideally, this would be within the TC184/WG3/T23 as most experience of the EXPRESS modelling and familiarity with the Ship Product Model are to be found there.
There are, however, overlaps with AP226 and a similar initiative from the Process Plant group of STEP.
A recent meeting between the NWI team and the AP226 (Ship Machinery) reached agreement on the overlap of scope be tween the two including;
■ Status parameters defined in AP226 or other existing application protocols shall be standardised within the existing application protocols. This means that parameters attributable to engines and equipment will be marked in the NWI informative annex with reference to AP226 and shall not be a part of the normafive part of the NWI..
■ Status parameters which are not standardised in other existing application protocols shall be standardised in the New Work Item.
The scope, proposed in the NWI Summary Sheet and elaborated on in a Working Draft document is currently under review. Please find a copy on the web site under：. http://www.oss.dk/emsa/pro-doc/pro-doc.htm. Copies have been distributed through national bodies who are collecting comments until June 3rd.
The NWI will be supported by a new Norwegian project (MARlTIM 1998-2002), and the US-lead Ship Life Cycle Support Infrastructure (SLCSI) project..
EMSA Training Proposals
During recent weeks another survey was initiated to discover what the training needs were among EMSA members. This follows on from the last TC meeting where the Co-ordinator suggested that such an initiative might help to stimulate greater activity among the group, particularly those who have recently joined. Once the surveys have been returned the assessment of the most popular and significant topics can be carried out, ahead of any actual courses later this year. All members are encouraged to participate in the survey even if not expecting to attend any courses as some may be able to provide material, examples or venues etc.. Feedback to members on the response to the survey will be presented during the next TC meeting in July.
Implementation Agreements
EMSA Technical Committee reviewed the latest recommendations proposed from SEASPRITE. These agreements are important decisions made by those validating the emerging models and allows the process of translator building and testing to be done in an incremental fashion.
The agreements themselves, can be categorised in the following way;
・Simple sub-setting (temporary)
・Redundant (not needed)
・Ambiguous (limit interpretation)
These were described in the last newsletter. Recent additions to the agreements include;
・Use of the IS version of Part 21 file format, with the technical corrigendum applied using conformance class 1.
The US MariSTEP project has a similar document which it is hoped will be made available at the next ISO meeting. The goal should be to produce one document reflecting all the views of the ISO Shipbuilding group.
Highlights from Orlando
The ISO TC184/SC4/WG3/T23 ship team committee met during February 1998. The major highlights were as follows;
・Overall Data Planning Model drafted
・AP218 team worked on Bevels, Seams, Features, Profiles and Corrugated bulkheads
・Provisional draft AP215 ARM presented - to be updated
・AP226 CDC drafted. Qualification proposed minor changes
・EMSA Implementation agreements reviewed
・Liaisons with PLIB, Implementers Forum & AP Modularisation
・Overview of Part 45- Materials
・AP212 (Electrical AP) walkthrough - group defers decision on use until report generated.
The Ship Team reported progress at the Implementers Forum along with an outline of typical problems encountered - which was well received.
The Building Block methodology was also described to the AP Modularisation group. There is an idea of carrying out a small experiment with part of the Ship Product Model to compare the approaches.
EMSA Web Site Registered
LR has registered a company-independent web site address which shall take over from the previous address at Odense Steel Shipyard. The new address shall provide the link between the administrative information (which stays at Odense site) and the html of the Building Blocks generated by the toolkit recently selected (see above). The new address is www.emsa-bbs.org and shall be going live shortly, so watch this space.
UoF Harmonisation
The role of the Ship Common Model can also be used to represent a group of "common" UoFs forming the Framework, Domain Models or Utilities etc., which are in turn used by the different APs in varying amounts. During the Orlando STEP meeting a draft data planning model of the SCM UoFs was put together. This has subsequently been reviewed during the last EMSA TC and the AP216 & AP218 teams which resulted in a number of modifications. These will need to be described at the next meeting in Bad Aibling (June 1998). The overwhelming need for each Ship AP to align itself to some common structure requires that the SCM should be used for this purpose. This should also provide a basis for orientating the user (and other Ship AP developers) when looking through the documentation. This may also result in a more consistent interpretation of the AP into AIM structures. Many of the concepts here will be refined for use within
