SearchUser loginPopular contentAll time:
Valuation Firm GuideClient Guide
|
Valuation Firm GuideNew Property TypesAs of roughly September 2011, we will be supporting the following Property Types under List of property types grouped by security categoryIn addition to the 3 security categories (Rural, Commercial, Residential) dictating the available property types, the National Australia Bank also have their own custom property types. In total there are 6 groups of property types:
In the future, we are considering a JSON Web Service that will allow easier integration. Just pass in a job ID from your UI, and use the property types in a drop-down box. Please note that the property types below must be provided with the exact same formatting and are case sensitive! NAB RESIDENTIAL SECURITY PROPERTY TYPES: NAB COMMERCIAL SECURITY PROPERTY TYPES: NAB RURAL SECURITY PROPERTY TYPES: STANDARD SHORT FORM PROPERTY TYPES: STANDARD COMMERCIAL PROPERTY TYPES: STANDARD RURAL PROPERTY TYPES: ANZ SPECIFIC PROPERTY TYPES: Standard LIXI Residential Property TypesSee also: Existing Standard LIXI Residential Property Type Mappings for All Property TypesPlease note, the listed property types are every property type in our database, not all of these will be accepted for every job.
Multiple Improvements (or Dwellings)If the property has 2 dwellings, then the Valuer should report the main dwelling on the front page of the report and also under the main building section and the second dwelling in the ancillary improvements (including description of areas etc). The additional comments should explain clearly that there are two dwellings and the basis of valuation (i.e., in one line etc). We will not propose to make any changes to the output report in ValEx until the new version of Property Pro is released and then align our output report with the API Property Pro report. Regards, National Compliance Manager New ZealandWe currently have the following sites set up for NZ:
New Zealand AddressesLIXI is an Australian standard; with concepts of 'state' and 'suburb' built in at a fundamental level. In Australia, the geographical/political divisions are:
with each entity contained within the borders of its next level up. Only Suburb, Postcode, State & Country are commonly used in addresses. New Zealand is a more complicated entity, consisting of:
with some combined concepts of "Unitary Authority" (both a region and a territorial authority). Typically only Suburb, Postcode, Territorial Authority/Unitary Authority & Country are used in addresses. To support this, ValEx renders the below structure:
<Location PropertyIdentification="NZ-1554515">
<Address>
<StreetNo>1</StreetNo>
<Street Type="Place">Test</Street>
<!-- Suburb -->
<City>Unsworth Heights</City>
<!-- Territorial Authority -->
<State Name="Other" OtherDescription="North Shore City" />
<!-- Auckland Region is implied -->
<Postcode>632</Postcode>
<Country>NZ</Country>
</Address>
</Location>
For Unitary Authorities, ValEx models a Territorial Authority linked to a Region, each having the same name. There are Gisborne District, Nelson City, Tasman District, Marlborough District, and Auckland Council. Chatham Islands Council is not modelled at this stage. Regions are modelled along geographic features such as major drainage divides, and Territorial Authorities are based on populations. As such, a Territorial Authority can exist in more than one Region - Taupo District for instance exists in 4 regions. Country
Territorial Authority
Suburb/Postcode
Regions in New ZealandSee wikipedia for a full list. Public holidays in New ZealandAt this stage, public holidays are not modelled for individual regions of new zealand - only national holidays are recorded. Area specific public holidays are associated with provinces or other geographical constraints which are distinct from Suburb/Territorial Authority/Region. Service Types / ProductsAs of January 2012, only Long Form reports and EVR are generally supported. This is because Short Form are based on the Australian Property Institute's PropertyPro format, which obviously is not suitable for New Zealand. Replacement Value (@InsuranceAssessment)We parse Replacement Value from The Replacement Value field is strictly a numeric value except for unit report types, where you may use non-numeric text to describe the strata insurance arrangement.
vx:DelayWe have created a ValEx namespace to escape LIXI limitations. The first feature of this namespace enables valuation firms to specify a delay reason ID that relates directly to how delay reasons are modeled within ValEx. If the An example follows:
<?xml version="1.0" encoding="utf-8"?>
<ValuationTransaction
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="https://vx.valex.com.au/lixi/schema/1.4.1/ValuationTransaction.xsd"
xmlns:vx="https://vx.valex.com.au/lixi/schema/vx/0.1/#"
ProductionData="No">
<-- LIXI Standard Content here -->
<vx:Job>
<vx:Status>
<vx:Delay ReasonID="4">
<vx:Comment>Unit test delay comment</vx:Comment>
</vx:Delay>
</vx:Status>
</vx:Job>
</ValuationTransaction>
Delay reasons are: ID Reason 4 Next visit to Location 9 Request is Outside of Lender policy 13 Inspection Contacting Issues 14 Access Issues 15 Property Identification 16 Insufficient Documentation (Client/Lender/Broker to Provide) 17 Other 18 Cancellation Request 19 Request to Change Service Type 20 Fee Approval 22 Request to Change Service Type and Higher Fee Approval Testing Tools - Ordering Test JobsOrder test jobs using our testing tool. Escalation ReasonsWe document our escalation reasons at: http://vxtest.valex.com.au/tests/evr/escalation-reasons.php If this is not up to date, please advise us. See also: Escalation of Service Type LIXI Queue LogWithin ValEx, we have a LIXI Queue Log. This can be useful for debugging LIXI issues.
This is an explanation of some of the less obvious information:
You can download the following files:
Receiving a Copy of the Final Valuation Response After Submitting to the Client (for Valuation Firms)Note: This is not for Clients! This is for Valuation Firms! We support sending a copy of the final valuation response that is sent to the client to the valuation firm. The implementation is a simple as adding a The LIXI message will be similar (but not the same) as you send back to us. Basically, the response will be an interpretation of your response, which is a standard LIXI message (not a workflow). All ValEx identifiers will be in their usual locations. If you want an example of the LIXI message that is sent, log into ValEx and check the Queue Log for any completed LIXI job. You should look for a response sent to the valfirm (we queue the LIXI message even if we do not support actually sending it). Due to the queue system, the response may be delayed by up to 10 minutes on average. Extending the LIXI standardsOne problem we have encountered a number of times is the requirement to go beyond the LIXI valuation standards. This is because the LIXI standards really do represent the most common uses; but the ValEx platform and its partners are seeking to innovate - the two goals of innovation and standards often conflict. Consequently for the 1.4.1 version of the ValEx XSD, we are introducing a minimal change to allow much greater extensibility. We are introducing an <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded" processContents="skip"/> node. What this allows is for lixi partners to define information in a non-lixi namespace; without breaking schema validation. For instance:
<ValuationTransaction xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:foo="http://foo.com"
ProductionData="No">
<-- Appearing after the RelatedPartySegment or AttachmentSegment -->
<foo:Foo>Hello! I'm a custom string, but could be any valid custom XML structure</foo:Foo>
</ValuationTransaction>
We are strongly advocating this amongst the LIXI valuation and CAL standards group as a way to move forward with custom or proprietry requirements; whilst still remaining LIXI standard compatible. You can preview and update to the 1.4.1 schema; which is not yet in use by the ValEx application. 
|
Related LinksNavigation |
To access the Queue Log, simply log into ValEx, open a job record, and click on the Queue Log icon in the upper right-hand corner.
Recent comments
7 years 46 weeks ago
8 years 38 weeks ago
8 years 40 weeks ago
8 years 40 weeks ago
8 years 45 weeks ago
9 years 16 weeks ago
9 years 21 weeks ago
9 years 26 weeks ago
9 years 26 weeks ago
9 years 27 weeks ago