Figure CM.02 - Basic Capacity Entities

Header Image
Project:
Figure CM.02 - Basic Capacity Entities : Class diagram
Created: 3/28/2022 3:51:09 PM
Modified: 5/25/2023 1:06:38 PM
Project:
Advanced:
A generalized capacity and capacity demand model is shown in the following Figure.<br/>The need to satisfy the capacity requirement during the first week in June is expressed using the fromToDateTime attribute, which is a composite of from and to dates/times, and the rangeInterval attribute of ApplicableTimePeriod.    Refinements to the schedule can include days of the week as shown by the daysOfWeek attribute in the ApplicableTimePeriod entity.  The rangeInterval attribute is used to handle some combination of #gt;, #lt;, #gt;=, #lt;=.  It is assumed this is a planned Capacity, which would be indicated using the plannedOrActutalCapacity attribute.  The CapacityRelationship entity enables a planned Capacity to be associated with an actual Capacity or for Capacities to be aggregated.<br/>The requirement for this capacity to be available in the Northeast geographic area is expressed using the relationship to GeographicPlace.  Other entities that further define/refine capacity requirements could be added as needed by extending the SID.<br/>The ability to deliver 10000 units of Product described in the previous example is expressed via the CapacityAmount, whose datatype is Quantity.  Quantity is a composite of an amount attribute and a units (unit of measure) attribute. For this instance of Capacity, the capacityAmount attribute contains the amount “10000”, and the unit of measure “units”.  Other examples of units of measure could be transaction volumes, storage requirements, traffic volumes, port availabilities, and so forth.  The capacityAmountFrom, capacityAmountTo, and rangeInterval enable ranges of capacity to be specified.<br/>Demands are placed on the capacity as defined by the CapacityDemand entity.  The related ApplicableTimePeriod is used to here to express the timeframe over which the demand exists.  It may or may not be the same instance of the ApplicableTimePeriod associated with the Capacity.  Therefore, it may be a demand placed on more than one CapacityAmount.  Similarly, the CapacityAmount may have many demands placed against it.<br/>The attributes are similar to those in CapacityAmount with the addition of a priority attribute that defines the relative importance of this demand.<br/>The AppliedCapacityDemand entity represents the amount of the CapacityDemand that has been applied against a CapacityAmount.<br/>