Www.oasis-open.org [email protected] Oasis-World Bank eGov Workshop 4-17-09 1 Standards-Based eGovernment Procurement Systems Opportunities

www.oasis-open.org

[email protected] Oasis-World Bank eGov Workshop 4-17-09 1

Standards-Based eGovernment Procurement

Systems

www.oasis-open.org

Opportunities and Priorities

Eduardo Talero

www.oasis-open.org


Agenda

• Electronic Government Procurement (eGP)

• Why standards?

• Standards and eGP

• Standards/FOSS and agile system development

• MDBs can help

• Closing thoughts

www.oasis-open.org


What is eGP?

www.oasis-open.org


SYNERGY

ECONOMY

EFFICIENCY

TRANSPA-RENCY

Governance

Leadership/Human

Resources

Institutional Change

Technology

Financing

Logframe of eGP

User Support Facilities

Transaction Facilities

Disclosure Facilities

Integration Facilities

eGP System

www.oasis-open.org


Why Standards for eGP?

www.oasis-open.org


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

www.oasis-open.org


Cloud computing lets Feds read your email

UK's Revenue and Customs losesUK's Revenue and Customs loses25 million customer records25 million customer records

Internet wiretappingBugging the cloud

Revealed: 8 million victims in the

world's biggest cyber heist

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)

Privacy fears are not completely unreasonable…

www.oasis-open.org


Standards Categories most relevant to eGPType of Standard Examples

Interoperability HTTP, WS-I Profiles, RNIF, IFX Registration UDDI, DUNS, ebXML Registry

Identification UN-SPSC, GTIN, LDAP, X500, ISO 7501

Web Services WS*, WSDL, JSR-168

Security HTTPS, ISO 17999, ISO 28000, WSS, X509 (PXIX)OSSTMM

Reliability HTTP-R, WS-R

Communication, Messaging IPS (TCP/IP), SOAP, ebMS, ISO 15489, SWIFT, ODF, PDF, ISO 20022

Interpretation ISO/IEC 7816, DSDL,UBL ebXML CC, RELAX-NG

Collaboration ebXML, WSCI, RN/PIPS

BPM, Workflow BPMN, BPEL,WS-C

Legal UNCITRAL Model laws, EU Directives

IT Service Management ISO/IEC 20000

www.oasis-open.org


DIFFERENT STANDARDS FOR DIFFERENT PHASES OF eGP SYSTEM DEVELOPMENT

SUPPLY CHAIN MANAGEMENT FACILITIES

TRANSACTION FACILITIES

DISCLOSURE FACILITIES

ePurchasing

eReverse Bidding eTendering

Communication

Identification

Registration

ePayments

Security

Reliability

Web Services

Workflow

Interoperability/Collaboration

www.oasis-open.org


Use of Open Standards/Open Source by 14 leading eGP governments*

*Argentina, Australia (State of New South Wales), Brazil, Chile, Finland, Hong Kong, India (Indian Railways), Italy, Mexico, Norway, Romania, Singapore, South Korea, The Philippines

• 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.

www.oasis-open.org


Standards / FOSS and agile system development

www.oasis-open.org


Short Timeline For E-governance System Development & deployment

Develop Detailed Project Proposal

10 months

Specify System and Hire Developers

10 months Develop system and deploy pilot

14 months

Rollout System

7 monthsOperate system with resident support

6 months

Y3



Develop system and deploy pilot

14 months


Operate system with resident support

6 months



14 months


Rollout System


6 months




Rollout System


6 months




Y1 Y2 Y4Y3

Rollout System


6 months




www.oasis-open.org


The Typical Resulting System Today…

CORE OF SYSTEM IS A BLACK BOX

Limited Configurability

Vendor lock-in Effective monopoly pricing for new licenses

Limited Interoperability with other vendor systems

www.oasis-open.org


LOGIC

DATA

INTERFACE

LOGICLOGIC LOGIC

DATA

INTERFACE

INTERFACEINTERFACE

INTERFACE

DATA

I1 I2 I4I3

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)

www.oasis-open.org


IMAGINE: industrial-strength eGovernance systems that are also easy to change, interoperable, social, knowledge-oriented, community-driven…

LOGIC

INTERFACE

DATA

INTERFACE

DATA

•Joined-up government

•Transaction wizards

•Discussion groups

•Community advice

•Personalized interface

•Workflow wizards

•Single sign-on

•Online support

•User profiles

•Customer content (wikis)

•Customer ratings

•Customer usage history

•Sponsored content

•Transaction history•Model documents

•Specification templates

•Secure all-electronic transactions

•S/P/R •Supply-chain automation

•Grievance management

•Workflow management•Business collaboration

•Business intelligence

•Business process automation

•Social networking/learning

www.oasis-open.org


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.

• Referencing good practice standards in guidelines, templates, model TOR, model specifications. Fex., ebXML, UMM, WSS, IMAP

• Recommending well 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“.

www.oasis-open.org


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.

www.oasis-open.org


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.

www.oasis-open.org


Thank you

Questions?

[email protected] or [email protected]

Documents

Www.oasis-open.org [email protected] Oasis-World Bank eGov Workshop 4-17-09 1 Standards-Based eGovernment Procurement Systems Opportunities