www.oasis-open.org Standards-Based eGovernment Procurement Systems Opportunities and Priorities Eduardo Talero
Agenda • Electronic Government Procurement (eGP) • Why standards? • Standards and eGP • Standards/FOSS and agile system development • MDBs can help • Closing thoughts
eGP System Leadership/ Human Resources Disclosure Facilities TRANSPA-RENCY Governance UserSupportFacilities EFFICIENCY Institutional Change TransactionFacilities ECONOMY Technology IntegrationFacilities SYNERGY Financing Logframe of eGP
How Standards can help eGP • Enhance B2G/G2G connectivity and interoperability • Generate trust in electronic experience • Enhance competition and inclusion • Enhance efficiency and flexibility of public procurement function • Enhance cooperation and transparency • Facilitate evolution and innovation • Increase return, reliability of investments • Avoid vendor lock-in
Revealed: 8 million victims in the world's biggest cyber heist Cloud computing lets Feds read your email UK's Revenue and Customs loses 25 million customer records Internet wiretapping Bugging the cloud Privacy fears are not completely unreasonable… Personal information records compromised by security breaches in the U.S. since January 2005 exceeds 255 million(www.privacyrights.org/ar/ChronDataBreaches.htm, accessed March 9, 2009. Hacker clones a valid CA certificate from and MD5-based SSL certificate using a Playstation 3. ( Technology Review, March/April 2009, pg. 86)
ePurchasing eTendering eReverse Bidding DIFFERENT STANDARDS FOR DIFFERENT PHASES OF eGP SYSTEM DEVELOPMENT Interoperability/Collaboration Workflow SUPPLY CHAIN MANAGEMENT FACILITIES Web Services Reliability TRANSACTION FACILITIES Security ePayments Registration Identification DISCLOSURE FACILITIES Communication
Use of Open Standards/Open Source by 14 leading eGP governments* • 7 use proprietary development platforms. Other 7 (6 in Asia) use J2EE • Only 4 use Linux, 2 of them in EU • Only 4 use Apache, the rest use proprietary web servers • 7 use MySQL, most others Oracle. • No one says to allow ODF documents. • Only 6 use UNSPSC. • Only 4 use XML, and only one uses ebXML for interoperable electronic business • Only 4 use SOAP, 3 use UDDI, only 1 uses WSDL and none use BPEL, WS-Security, WSCI (so much for SOAs). • Most use digital certificates and asymmetrical encription for authentication. *Argentina, Australia (State of New South Wales), Brazil, Chile, Finland, Hong Kong, India (Indian Railways), Italy, Mexico, Norway, Romania, Singapore, South Korea, The Philippines
Operate system with resident support Operate system with resident support Operate system with resident support 6 months 6 months 6 months Y4 Y1 Y2 Y3 Short Timeline For E-governance System Development & deployment Develop Detailed Project Proposal Develop Detailed Project Proposal Develop Detailed Project Proposal Develop Detailed Project Proposal Develop Detailed Project Proposal Develop Detailed Project Proposal Develop Detailed Project Proposal 10 months Specify System and Hire Developers Specify System and Hire Developers Specify System and Hire Developers Specify System and Hire Developers Specify System and Hire Developers Specify System and Hire Developers 10 months Develop system and deploy pilot Develop system and deploy pilot Develop system and deploy pilot Develop system and deploy pilot Develop system and deploy pilot Develop system and deploy pilot 14 months 14 months 14 months Rollout System Rollout System Rollout System Rollout System 7 months Operate system with resident support Operate system with resident support 6 months 6 months Y3
The Typical Resulting System Today… Limited Configurability Limited Interoperability with other vendor systems CORE OF SYSTEM IS A BLACK BOX Effective monopoly pricing for new licenses Vendor lock-in
INTERFACE INTERFACE INTERFACE INTERFACE INTERFACE DATA DATA DATA LOGIC LOGIC LOGIC LOGIC An agile system development strategy based on open standards and open source* * Proposed in essence by ICT Agency of Sri Lanka (http://www.icta.lk) I1 I2 I3 I4
INTERFACE • Discussion groups • Personalized interface • Joined-up government • Single sign-on INTERFACE • Online support • Transaction wizards • Workflow wizards • Community advice DATA • Customer ratings • Sponsored content • User profiles • Model documents • Transaction history DATA • Specification templates • Customer content (wikis) • Customer usage history LOGIC • Workflow management • Business collaboration • S/P/R • Supply-chain automation • Secure all-electronic transactions • Business process automation • Grievancemanagement • Socialnetworking/learning • Business intelligence IMAGINE: industrial-strength eGovernance systems that are also easy to change, interoperable, social, knowledge-oriented, community-driven…
MDBs can Help by: • Developing lending instruments and procurement procedures/documents for agile system development • Leveling procurement playing field for Open source products. For example, of proprietary office suites with functionally equivalent open systems alternatives. • Referencinggood practice standards in guidelines, templates, model TOR, model specifications. Fex., ebXML, UMM, WSS, IMAP • Recommendingwell established standards that are widely recognized and tested. Fex: SOA, Uncitral model laws, ODF, UNSPSC, BPEL4WS • Requiring standards only very selectively, when economy/efficiency of investments, products or services would otherwise be compromised. Fex: XML, ISO 9000, ISO 14000 “or equivalent QA standards“.
In Closing… • Standards enhance economy, efficiency, competition, transparency and evolution of eGP • Free and Open source SW (FOSS) facilitates and accelerates use of open standards • Open standards/FOSS facilitate fast, iterative development of eGovernance applications which now take too long and are very risk-prone. • Governments cannot afford to build the organic, social applications of the future only with proprietary standards/technology.
In (really) Closing… • MDBs can be far more proactive in referencing, recommending and sometimes even requiring Standards. • MDB’s need to create level playing field for procurement of FOSS and for contracting of agile application development.
Thank youQuestions? firstname.lastname@example.org or email@example.com