Implementation Model (Material Master Building Block)
The following diagram shows the relationships between the main Thing Shapes, Thing Templates, and Things in the material master building block, and their relationships with entities in other building blocks.
In the diagram, arrows with hollow heads and solid lines (
) indicate that an entity extends from the entity to which the arrow points, arrows with hollow heads and dashed lines (
) indicate that an entity implements the entity to which the arrow points, and arrows with open heads and dashed lines (
) indicate that an entity has a dependency upon services on the entity to which the arrow points.
) indicate that an entity extends from the entity to which the arrow points, arrows with hollow heads and dashed lines () indicate that an entity implements the entity to which the arrow points, and arrows with open heads and dashed lines () indicate that an entity has a dependency upon services on the entity to which the arrow points.The significant entities in the material master building block include the following:
• PTC.MaterialMaster—Project entity for the material master abstract building block. Used to package and contain all building block entities.
In the PTC.MaterialMaster project:
◦ PTC.MaterialMaster.EntryPoint—Entry point Thing for the material master building block. Used to call services defined on the PTC.MaterialMaster.EntryPoint_TT Thing Template.
◦ PTC.MaterialMaster.EntryPoint_TT—Thing Template for the material master entry point. Used to contain building block metadata, including the display name, version, description, and so on. Also contains services to allow the building block to be deployed and configured.
◦ PTC.MaterialMaster.Manager_TT—Thing Template for the material master building block manager. Contains implementation code for services defined in the PTC.MaterialMaster_Management_TS Thing Shape. Note: This building block does not have a manager Thing, as it is an abstract building block that is paired with an implementation building block.
◦ PTC.MaterialMaster_Management_TS—Management Thing Shape for the material master building block. Used to define the services for the material master building block functionality.
◦ PTC.MaterialMaster.ModelLogic_TS—Model logic Thing Shape for the material master building block. Used to give individual models access to model-specific services for this building block.
◦ PTC.MaterialMaster.UomConvsWithNames—Data Shape defining the structure for unit of measure conversions. These unit of measure conversions refer to the units of measure defined by the PTC.Materials.UnitOfMeasure Data Shape. This structure is useful to manipulate the transformation between different units of measure.
• PTC.MaterialMasterImpl—Project entity for the material master implementation building block. Used to package and contain all building block entities.
In the PTC.MaterialMasterImpl project:
◦ PTC.MaterialMasterImpl.EntryPoint—Entry point Thing for the material master implementation building block. Used to call the services defined on the PTC.MaterialMasterImpl.EntryPoint_TT Thing Template.
◦ PTC.MaterialMasterImpl.Manager—Manager Thing for the material master implementation building block.
◦ PTC.MaterialMasterImpl.EntryPoint_TT—Thing Template for the material master implementation building block entry point. Used to contain the building block metadata, including the display name, version, description, and so on. Also contains services to allow the building block to be deployed and configured.
◦ PTC.MaterialMasterImpl.Manager_TT—Thing Template for the material master implementation building block manager. Contains implementation code for the service defined in the PTC.MaterialMaster_Management_TS Thing Shape.
The complete list of entities in the building block can be found by viewing the PTC.MaterialMaster and PTC.MaterialMasterImpl projects in ThingWorx Composer.