How do Delays work in Valex?

Who Can Add Delays?

Delays in Valuation Exchange are entered by administrative valuation firm users or
valuers; typically through the interface. We give users a number of preset
reasons for the delay, and also ask for an expected end, as well as
any other comments pertaining to the delay.

The default expected end of a delay is typically 2 business days
from the point of adding a delay; but can be easily overridden by users.

When Can Delays Be Added?

We allow delays to be applied at any point during the life cycle of a job, not
just prior to an inspection - though this is typically when a delay is used.

What Happens When A Delay Is Added?

As soon as a delay is added to the job, valex check for any notification requirements of the client or related parties to the job. For LIXI client organisations a workflow packet is prepared and queued for sending; though other options exist such as email or fax.

What's In The Delay Workflow Packet?

A delay workflow packet is effectively the same as a regular valuation request or
response packet. The key differences are in where we input our information.

We also model a delay reason.

<Message>
    <Identifier UniqueID="Dummy_Value" Type="VPMAssigned"/>
    <MessageRelatesTo>
        <Identifier UniqueID="VXJ-000000012345" Type="VPMAssigned"/>
        <Identifier UniqueID="REF-001" Type="LenderAssigned"/>
    </MessageRelatesTo>
    <MessageBody Type="Information">
        <Status Name="Delayed">
            <Date>2006-10-18</Date>
        </Status>
    </MessageBody>
    <ValuationType>
        <Identifier UniqueID="Dummy_Value" Type="VPMAssigned"/>
        <WorkFlow Type="Status" DelayReason="TenantDeniedAccess" FromStatus="Accepted">
            <ExpectedValuationDate>
                <Date>2007-11-25</Date>
            </ExpectedValuationDate>
            <Comment>Owner unvailable until specified date</Comment>
        </WorkFlow>
    </ValuationType>
</Message>

The key bits of information here are

The status of the job
Message/MessageBody/Status
When the delay was added
Message/MessageBody/Status/Date
The user's delay reason
Message/ValuationType/WorkFlow/@DelayReason
The estimated end of the delay
Message\ValuationType\WorkFlow\ExpectedValuationDate\Date
The user's comments
Message\ValuationType\WorkFlow\Comment

Valex Specific Notes

  1. Our system requires comments for all delays being added, even though this is not required by the XSD.
  2. Any date you submit, our system will assume is YYYY-MM-DD 0:00:00. When possible, submit a Time as well for greater clarity.
  3. Our system does not allow delays to be set in the past.

Delays, Workflow and Service Level Agreements

When we receive a workflow packet, we add a delay as soon as we process it. If there are any errors, a delay is not added to the job.

Due to conditions affecting our servers, your workflow packets may be queued for a short period of time (a few minutes, typically); which may slightly affect your service level agreements.

Timezones

We assume that all dates and times given are in the timezone of the job being processed Australia/Adelaide timezone. A better solution would be to assume the timezone of the job, or to send ISO 8601 dates - however we do not have specifc plans to implement either solution anytime soon.

Delay end date

When an expected valuation date is provided, ValEx assumes the close of business on that particular day (rather than what is specified in the /Time node). That is in sync with the user interface behaviour of ValEx - we may look at changing this if there is enough interest.