SCM MAPPING：
● the generic SCM constructs map only to a few or exactly one destinations in the AIM：
● modelling framework, domain models
● use of mapping templates
● the SCM utilities are shared by the APs.
● Configuration management, external referencing, general characteristics, base geometry, materials, location concepts, units
● reuse of existing mappings
Fig.1 SCM mapping/backbone of mapping
Issues arising from the workshop：
● QC issue： how to deal efficiently with the redeclared ARM attributes in the mapping tables?
● AIM subtypes：
● consistent creation
● interoperability issue
● consistent mapping of type names： could go into name attributes, description attributes or be done as X_assignments
● consistent creation of global rules
● provide AP218/SCM requirements to the PDM schema work done by PDES, Inc and ProSTEP
● forward the SCM requirements to the AP modularization/interoperability and the new SC4 architecture activities
● address overlaps between AP218, AP230 (building structural components) and AP227 (plant components)
Post workshop activities：
● resolve harmonisation issues
● get the remaining UoFs mapped
● review and harmonize the mapping
● second workshop：
● final review
● address SCM mappings (add to SCM document?)
● could be part of a SEASPRITE meeting
● produce AIM shortform (to be discussed in Bad Aibling)
● Is it reasonable to get AP218 out for CD by October?
● 2 groups of people (working independently) were able to create 1/3 of the AIM during 1.5 weeks = 3 man weeks)
● approximately 6 (10) man weeks to do the next
● split among 6 people (the main BB owners)
● If yes, needs to be done by the end of August.
A PDM schema meeting is scheduled in the end of August.
