Real Estate Transaction Standard: Development and Governance

1. Real Estate Transaction Standard: Development and Governance

2. Agenda • SOA Software: Company Background • SOA Software: Participation in Standards Development • Basic Tenets of Standards Development • RETS Standards & Governance: • Fact-finding Results • Recommendations • Next Steps

3. SOA Software: Company Background • Headquartered in Los Angeles, California • The largest platform-independent Service Oriented Architecture (SOA) infrastructure vendor: • SOA WorkbenchTM provides: • Registry, Repository, Contract Management, Workflows, Re-use Management • SOA Service ManagerTM provides: • Policy Management, Security, SLA and Exception Management • SOLATM provides: • Mainframe Web Services for CICS • Investors: • Redpoint Ventures, Draper Fisher, Mellon Ventures, Paladin Capital, Palisades ventures

4. SOA Software: Representative Customers and Awards 2005 Cool Vendor 2005 WSM Leader

5. SOA Software: Standards Development SOA Software participates in the development of industry-wide standards: Sponsor member since 2002. Active on committees: UDDI (Universal Description, Discovery and Integration), WSS (Security Services), WSDM (Distributed Management), WSRM (Reliable Messaging), WSSX (Secure Exchange), WSTX (Transaction). Member since 2003. Observer status and participate to remain compliant and stay ahead of standards. Perform compliance testing in our product.

6. Standards Development: Basic Tenets There are certain key aspects that successful standards bodies have in common: • Clearly defined / adhered to organizational structure, processes and procedures • Open and accessible to industry professionals • Participation levels define voice • Technical agendas are set via consensus • Transparency into processes and procedures • Completed work is ratified by participating members • Leadership is chosen by democratic election and serve terms

7. Fact-finding Results: RETS as a Standard Conflict amongst members with regard to RETS 1.x vs. 2.x: • Does 1.x work the way it was intended? • Hold off on 2.x or keep going? Key findings: • 1.x, while well on the way to becoming a standard, is not yet ready: • Needs to more efficiently transfer MLS data • Needs to be easier and less resource-intensive to implement • Limited industry adoption • Majority want efforts to be focused on getting 1.x to a true standard status

8. Fact-finding Results: RETS Governance Highlights of the feedback on governance: • Can we reassess the current governance structure? • What is the best mix from the industry for committees and work groups? • How can we have more involvement in requirements and design? Key findings: • More structured governance: • Transparency and accessibility • Reviews of work • Approvals of work • Membership involvement: • Participation in business and technical requirements • Be “heard” when present ideas

9. Recommendations: RETS as a Standard Concentrate on 1.x and deliver a “true” standard: • Revive mission and business requirements: • A common language that enables easy access to systems and data • Transfer MLS data efficiently • Standards that require no or minimal customizations • Review current standards: • Completeness • Ease of implementation • Quality of code / performance metrics • Form work groups to develop revisions: • Prioritize deliverables • Set reasonable timelines

10. Recommendations: RETS Governance Restructure current governance: • Increase RETS membership to encompass professionals from all segments • Committees and work groups should be representative of all segments • Leadership committee defines structure, processes and procedures: • Committees and work groups – how many, participants, accountability • Development planning, monitoring and reviews • Transparency to membership • Membership ratification before general release

11. Next Steps Governance: • Elect Leadership • Define Mission • Define structure and processes 1.x Standards: • Review business requirements • Perform a technical review • Develop and release