XOG Resource Allocation Hard and Soft Booking
Article ID: 92762
Updated On:
Products
CLARITY PPM FOR ITG
CLARITY PPM FEDERAL
Clarity PPM SaaS
Clarity PPM On Premise
Issue/Introduction
How can I use XOG to load hard booking, and soft booking allocation entries for resources on a specific project?
For a given project, you may want to use XOG to load in allocations for the resources on the project team. At times, you may want to give a certain resource a "hard booking" allocation entry on that project.
For a given project, you may want to use XOG to load in allocations for the resources on the project team. At times, you may want to give a certain resource a "hard booking" allocation entry on that project.
Environment
CA PPM - On Premise or On Demand - All Versions
Resolution
This can be done, however, each entry in the input xml file needs to have the proper booking status, and allocation tags used in order for the system to recognize that resource as being hard booked or soft booked for that project.
For example, lets use a resource named Resource1. First, add a "hard allocation" to a project for Resource1 through the GUI. Then XOG out that project's allocations using the xml file "prj_projects_alloc_act_etc_read.xml" - in tthat file, specify the project ID, and then run XOG to output the data to a separate file.
Open that file and search for the word "Resource1", and located the section with the hard booking allocation entry that was created for Resource1 on that project within the GUI, and then locate an entry for another resource, "Resource2", who had a soft booking allocation entry. Note the differences between the hard booking allocation and soft booking allocation entries.
The hard booking allocation resource entry for Resource1 has the allocation tag as "HardAllocCurve", and that the entry for Resource1 had a "booking status" of "15"
The soft booking allocation resource entry for Resource2 has a "booking status" of "5", and the allocation tag was just "AllocCurve" (note it didn't have SoftAllocCurve, but rather just AllocCurve).
Here are XML examples for the hard booking and soft booking allocations:
Hard Booking Allocation XML Resource Entry for Resource1:
<Resource availFrom="2018-04-01T08:00:00" availTo="2018-07-16T17:00:00" bookingStatus="15" capitalPercentage="0" defaultAllocation="1"
isProjectManager="false" lastUpdatedBy="csk.admin" lastUpdatedDate="2018-04-16T00:00:05" openForTimeEntry="true"
projectRoleID="csk.businessAnalyst" resourceID="Resource1">
<HardAllocCurve>
<segment finish="2018-04-25T00:00:00" rate="0.2000" start="2018-04-23T00:00:00"/>
</HardAllocCurve>
<CustomInformation>
<ColumnValue name="partition_code">NIKU.ROOT</ColumnValue>
</CustomInformation>
<SkillAssocs/>
</Resource>
Soft Booking Allocation XML Resource Entry for Resource2:
<Resource availFrom="2018-04-01T08:00:00" availTo="2018-07-16T17:00:00" bookingStatus="5" capitalPercentage="0" defaultAllocation="1"
isProjectManager="false" lastUpdatedBy="csk.admin" lastUpdatedDate="2018-04-16T00:00:05" openForTimeEntry="true" projectRoleID="csk.architect" resourceID="Resource2">
<AllocCurve>
<Segment finish="2018-04-08T00:00:00" start="2018-04-01T00:00:00" sum="0.0000"/>
<Segment finish="2018-05-08T00:00:00" start="2018-04-08T00:00:00" sum="1.0000"/>
<Segment finish="2018-07-17T00:00:00" start="2018-05-08T00:00:00" sum="0.0000"/>
</AllocCurve>
<CustomInformation>
<ColumnValue name="partition_code">NIKU.ROOT</ColumnValue>
</CustomInformation>
<SkillAssocs/>
</Resource>
Note the highlighted values above as those are the differentiating factors between the Hard Book Allocation and Soft Book Allocation entries for resources.
The key to this is that you can only have one resource entry per resource, per XOG run, and that entry needs to have the proper booking status on it, as well as the proper allocation tags. Note that you cannot have multiple allocation types used in the same load file, for the same resource. If you need to have both hard and soft booking allocation entries for the same resource, this would need to be done using separate XOG runs with the separate input files containing the proper tags and values for those entries.
For example, lets use a resource named Resource1. First, add a "hard allocation" to a project for Resource1 through the GUI. Then XOG out that project's allocations using the xml file "prj_projects_alloc_act_etc_read.xml" - in tthat file, specify the project ID, and then run XOG to output the data to a separate file.
Open that file and search for the word "Resource1", and located the section with the hard booking allocation entry that was created for Resource1 on that project within the GUI, and then locate an entry for another resource, "Resource2", who had a soft booking allocation entry. Note the differences between the hard booking allocation and soft booking allocation entries.
The hard booking allocation resource entry for Resource1 has the allocation tag as "HardAllocCurve", and that the entry for Resource1 had a "booking status" of "15"
The soft booking allocation resource entry for Resource2 has a "booking status" of "5", and the allocation tag was just "AllocCurve" (note it didn't have SoftAllocCurve, but rather just AllocCurve).
Here are XML examples for the hard booking and soft booking allocations:
Hard Booking Allocation XML Resource Entry for Resource1:
<Resource availFrom="2018-04-01T08:00:00" availTo="2018-07-16T17:00:00" bookingStatus="15" capitalPercentage="0" defaultAllocation="1"
isProjectManager="false" lastUpdatedBy="csk.admin" lastUpdatedDate="2018-04-16T00:00:05" openForTimeEntry="true"
projectRoleID="csk.businessAnalyst" resourceID="Resource1">
<HardAllocCurve>
<segment finish="2018-04-25T00:00:00" rate="0.2000" start="2018-04-23T00:00:00"/>
</HardAllocCurve>
<CustomInformation>
<ColumnValue name="partition_code">NIKU.ROOT</ColumnValue>
</CustomInformation>
<SkillAssocs/>
</Resource>
Soft Booking Allocation XML Resource Entry for Resource2:
<Resource availFrom="2018-04-01T08:00:00" availTo="2018-07-16T17:00:00" bookingStatus="5" capitalPercentage="0" defaultAllocation="1"
isProjectManager="false" lastUpdatedBy="csk.admin" lastUpdatedDate="2018-04-16T00:00:05" openForTimeEntry="true" projectRoleID="csk.architect" resourceID="Resource2">
<AllocCurve>
<Segment finish="2018-04-08T00:00:00" start="2018-04-01T00:00:00" sum="0.0000"/>
<Segment finish="2018-05-08T00:00:00" start="2018-04-08T00:00:00" sum="1.0000"/>
<Segment finish="2018-07-17T00:00:00" start="2018-05-08T00:00:00" sum="0.0000"/>
</AllocCurve>
<CustomInformation>
<ColumnValue name="partition_code">NIKU.ROOT</ColumnValue>
</CustomInformation>
<SkillAssocs/>
</Resource>
Note the highlighted values above as those are the differentiating factors between the Hard Book Allocation and Soft Book Allocation entries for resources.
The key to this is that you can only have one resource entry per resource, per XOG run, and that entry needs to have the proper booking status on it, as well as the proper allocation tags. Note that you cannot have multiple allocation types used in the same load file, for the same resource. If you need to have both hard and soft booking allocation entries for the same resource, this would need to be done using separate XOG runs with the separate input files containing the proper tags and values for those entries.
Additional Information
For more information about using XOG, please see the XOG documentation here: https://docops.ca.com
Feedback
Yes
No
Powered by
