Modelling and Implementation issues：
Comments were received from 7 organisations including JMSA. These comments were incorporated in the CDC.
Usage of version_id：
● The usage is to be refined.
● Since each definition entity is versioned, there are numerous version_ids which is confusing.
function and functionality attributes of Item Functionality：
● this attribute belongs to Functional_definition entity.
● function of an item is to be defined but functionality is not appropriate to be defined at each functional_definition's sub-entity level. AP226 has included this attribute in mechanical_product_general_characteristics.
Engineering Units：
● local_units atribute is currently introduced at definition level and units attribute at ship level.
Unit_component attribute is introduced at measure_with_unit attribute. Such a requirement is not clear and is confusing.
● To alleviate this, unit is declared at measure_with_unit level in AP226.
Electrical connections：
● Electrical connection model in 226 needs to be enhanced to facilitate definiton of some basic geometry and technical data for mechanical products.
● Results of issues FL-36 and OR-02 to be reflected in AP226.
Redundant defined types：
● At each item level entity, there is a defined type attribute which defines the type of that item. This has resulted in redundant attributes (e.g. the_type and the_function attributes specific to AP226 at lower level; the_type → say, slow speed, medium speed, and high speed engines.) This is to be corrected.
Reference to Part 40：
● Reference to Part 40 differs in method between AP226 and AP218. This is to be rectified.
● The cookbook defines the reference method which has been used in AP226.
Harmonisation：
● Definition of terms to be made consistent by the CD version.
● AP226 needs harmonisation with ISO/DIS14224 and IEC50(191).
● RAM-SHIPNET proposed some issues regarding harmonisation. (RAM： Reliability, Availability and Maintainability.)
● DNV NWI Ship Operational Logs, Records and Messages：
