Upload
frans-thamura
View
1.084
Download
4
Tags:
Embed Size (px)
Citation preview
Final Report Standards-based Web
Servicesfor Interoperability
Presented to: Kusmayanto Kadiman, Minister for Research and Technology+
Project Steering Committee
March 15, 2006
15/03/2006 Standards-base Web Services for Interoperability 2
Agenda• Welcome + Introduction – Minister of Ristek
• TOR + Background - RH
• Technical Architecture - GZ
• Proofs of Concept - GZ
• Capacity Building + Implementation - RH
• Conclusion – RH
• Closing Comments – Minister of Ristek
15/03/2006 Standards-base Web Services for Interoperability 3
Terms of Reference1. Develop an IT solution architecture to provide a
common web services API for disparate systems. 2. Solution must provide:
– A standards-based architecture that enables interoperability within governments;
– A repeatable process for exposing common web services for existing/legacy systems; and
– An application runtime environment, development environment and tools to develop and deploy web services applications.
15/03/2006 Standards-base Web Services for Interoperability 4
Terms of Reference cont
3. OSS (Open Source Software) should be used where possible.
2. The architecture should applied to three distinct cases encompassing national and regional/local government applications.
3. The proofs of concept must be tested and demonstrated to the technical advisers of Ristek, Kominfo, Menpan and Transportasi.
4. Capacity building and technology transfer should be done.
15/03/2006 Standards-base Web Services for Interoperability 5
Background• Three years ago three senior officers (from Ristek,
Kominfo and Menpan) developed a shared vision of what could be done to improve the use of IT both in government and throughout the country.
• Their goals:
– to facilitate and support the drive for ‘Good Governance’ via modern IT; and
– to help modernize the national IT sector and thereby improve the rate of national economic and social development.
15/03/2006 Standards-base Web Services for Interoperability 6
StrategyThe strategy to achieve this consisted of an initial three
simple, high level and potentially very high impact elements.
2. Open IT standards – adopt as mandatory for all future government systems.
3. Interoperability – adopt as mandatory for all future government systems, and facilitate use in high priority legacy (existing) systems.
4. OSS – use where possible.
15/03/2006 Standards-base Web Services for Interoperability 7
Action To launch this strategy three initiatives were identified and planned.
2. Endorse OSS and launch a new government program; IGOS was launched.
3. Identify and conduct a single high impact project to address an endemic problem of government, ‘Islands of Information’. Solution: Interoperability for legacy systems This project – Interoperability (SP 202) was
launched.3. A White Paper on Open IT Standards and OSS was
planned and drafted.
15/03/2006 Standards-base Web Services for Interoperability 8
‘Islands of Information’ – Occur where data in a computer system
cannot be electronically accessed from or shared with any external system.• Typically the only person/s with effective
access to such data are those who collect and/or maintain it;
– Exist in literally thousands of situations throughout government; and
– Constitute a huge (and to date largely impenetrable) barrier to improving public administration and governance Indonesia.
15/03/2006 Standards-base Web Services for Interoperability 9
Governance• Governance relies on information and data.• To be useful, data should be:
– Accessible• to all with a need, or a right, to know;
– Able to be shared (exchanged)• with related data bases and applications;
– Timely• Most data is only useful if it is timely; and
– Accurate• Not subject to errors from repeated manual re-
entry (or manipulation).• Good governance needs good access to good data.
15/03/2006 Standards-base Web Services for Interoperability 10
Access to Data in Government• Throughout most governments in Indonesia:
– Data is often directly accessible only to those who collect/maintain it;
– In vast numbers of cases government data and information is NOT accessible other than via paper reports (or sneaker net);
– Direct result much data loses its potential to be useful. (Too little, too late!)
15/03/2006 Standards-base Web Services for Interoperability 11
Project Team • Technical Assistance Team (provided by CIDA/GRS II and
Belleclaire Consulting Inc of Halifax, Nova Scotia)
– Richard Higgins, Team Leader – Geoff Zeiss, Senior IT Architect – Frans Thamura, Local IT developer
• Counterpart Team– Ristek: Haryanto Sahar + support– Kominfo: Ibu Lolly Abudullah + support– Transportasi: Cahyano Partawijaya + support– Menpan: Hendrumal Panjaitan
15/03/2006 Standards-base Web Services for Interoperability 12
Technical Architecture
15/03/2006 Standards-base Web Services for Interoperability 13
Technical Objectives• Propose an architecture for interoperability
– Follows GoI guidelines– Enables GoI to address interoperability
• Legacy IT systems• New IT solutions
• Apply recommended architecture– Implement three proofs of concept
• All development performed by local software development resources.
15/03/2006 Standards-base Web Services for Interoperability 14
Problem: ‘Islands of Information’
Portable computer
ServerApplication 1
ServerApplication 2
ServerApplication 3
PC
Application 1Client
Application 2Client
Application 3Client
PC
Application 1 Datastore
Application 1 Datastore
Application 1 Datastore
15/03/2006 Standards-base Web Services for Interoperability 15
Traditional Solution• Traditional solutions for interoperability
– Require rewriting application– Not feasible when source code is ‘lost’– Require very scarce high level IT skills and
experience– Result is a non-repeatable, proprietary
solution– Expensive
15/03/2006 Standards-base Web Services for Interoperability 16
Technical Objective• GoI and regional systems must interoperate.• New systems:
– Interoperability architecture standard for new systems.
• Legacy systems: – Systems should interoperate without
massive rewrite.• Should adhere to international open
standards
15/03/2006 Standards-base Web Services for Interoperability 17
Steering Committee Guidelines
• Must conform to GOI specified guidelines:
– Open Standards
• Additional requirements:
– Use OSS where feasible
– Able to be implemented by local software development resources
– Inexpensive
15/03/2006 Standards-base Web Services for Interoperability 18
Project Development TasksProject Name: PASIR(Program Arsitektur Sistem Informasi dan InteRoperabilitas)
3. Define interoperability architecture4. Identify and select OSS components5. Select three proofs of concepts6. Implement data drivers
Examples: MySQL, Foxpro, Excel, and Sybase
7. Implement web services API8. Test9. Demonstrate
15/03/2006 Standards-base Web Services for Interoperability 19
1. Interoperability Architecture• World Wide Web Consortium (W3C)
standards– Basic internet protocols
• HTTP, XML– Internet web services
• SOAP, WSDL• Platform neutral
– Linux, Windows, Unix, Mac OS,…• Supported by both .Net and J2EE
– Supports J2EE and .Net interoperability
15/03/2006 Standards-base Web Services for Interoperability 20
W3C Standards
• Transport
• Data representation
• Messaging
• WS Description
• Interoperability
• HTTP
• XML
• SOAP
• WSDL
• WS-I Basic Profile
15/03/2006 Standards-base Web Services for Interoperability 21
2. PASIR OSS Web Services• Web Server
• Servlet Engine
• SOAP/WSDL
• Development
• Data Access
• Web framework
• Apache
• Tomcat
• AXIS
• Eclipse
• Apache POI, JDBC, ODBC
• Webworks
15/03/2006 Standards-base Web Services for Interoperability 22
PASIR - OSS User Interaction
• User role and model manager: Cimande*
– Bahasa Indonesia
– OSS
*Cimande is an Indonesian OSS product
– developed and maintained by Frans Thamura.
15/03/2006 Standards-base Web Services for Interoperability 23
PASIR OSS Libraries for Data Providers
• Excel files– Apache POI
• FoxPro (.DBF)– ODBC
• SQL (Sybase, MySQL)– JDBC, ODBC
15/03/2006 Standards-base Web Services for Interoperability 24
PASIR Architecture
DataDestination
Web Server: ApacheApp Server: Tomcat
PA
SIR
Web S
ervicesA
PI*
SOAPHTTPServlet Libraries
SOAP/WSDL: Axis Data Provider: ODBCPASIR User/Model: Cimande *
Data Source
Server Client
PASIRWSDL*
Web Browser
Web Server: ApacheApp Server: Tomcat
Servlet LibrariesSOAP/WSDL: Axis Data Provider: ODBCPASIR User/Model: Cimande*
PASIR Data Provider * PASIR Data Provider*
Industry standard*PASIR specific
15/03/2006 Standards-base Web Services for Interoperability 25
PASIR - Published on CD“PASIR: The IGOS Web Services Toolkit for Interoperability”
Contents of CD• Apache 2.0• Tomcat 1.5• Axis 1.21• Eclipse 3.1• Webwork• Cimande• Apache POI• ODBC libraries• JDBC libraries• PASIR Example Data Providers for MySQL, Foxpro, Excel, and Sybase• Documentation:
– Installation, – How to use,– How to customize– IGOS contacts for technical support and general information
Developed by: RISTEK + DEPKOMINFO+ MENPAN With assistance from the Canadian International Development Agency (CIDA)May 2006
15/03/2006 Standards-base Web Services for Interoperability 26
15/03/2006 Standards-base Web Services for Interoperability 28
3. Proofs of Concept (POC)
15/03/2006 Standards-base Web Services for Interoperability 29
Three Proofs of Concept
A. Local government Payroll and
Accounting systems interoperability
B. Pare Pare Personal ID and Permitting
systems interoperability
C. Marine Shipping Reporting System
Ports Pelindo Transportasi HQ
15/03/2006 Standards-base Web Services for Interoperability 30
Guidelines for POC• Addresses and resolves a real business
problem.– If implemented, would deliver significant
business benefits• Requires no or minimal modifications to
existing systems.• Developed by local IT professionals.• Repeatable solution not possible without
PASIR.
15/03/2006 Standards-base Web Services for Interoperability 31
A. Payroll and Accounting• Business problem
– Most local governments transfer all payroll data manually to accounting departments.
– Redundant data entry is a large waste of time and staff, and introduces errors
– New national regulations will require interoperability.
• Solution– Project proponent: GRSII – CIDA– Use web services to automatically communicate
payroll data to accounting department
15/03/2006 Standards-base Web Services for Interoperability 32
Accounting and PayrollCurrent Information Flow
Payroll Group
Accounting Group
SIMGAJIPayroll
Application
SIMAKDAAccountingApplication
Working Unit 11. Prepares monthly
update3. Pays employees
Working Unit 21. Prepares monthly
update3. Pays employees
3. Cheques
1. MonthlyUpdate
3. Cheques
2. Payroll Data
1. MonthlyUpdate
15/03/2006 Standards-base Web Services for Interoperability 33
Accounting and PayrollWeb Services POC
SOAPHTTP
SIMAKDA(Accounting)
Web Server
WE
B S
ER
VIC
ES
Data Provider
SIMGAJI(Payroll)
Cimande
Foxpro
`
Foxpro
`
Web Server
Data Provider
Cimande
15/03/2006 Standards-base Web Services for Interoperability 34
Payroll and AccountingTechnical Summary
• Demonstrates interoperability between
remote Microsoft applications.
• Interoperability required no modifications to
existing MSM SIMGAJI and SIMAKDA
systems.
15/03/2006 Standards-base Web Services for Interoperability 35
Ibu Uci Fajar Nasution, DirectorMSM Consultants
15/03/2006 Standards-base Web Services for Interoperability 36
B. Pare ParePersonal ID and Permitting
• Business case– Pare Pare has excellent (ISO 9000), but separate Personal ID
Admin and Permitting systems. – Checking of personal ID of permit applicants is manual and
unreliable.
• Solution– Project proponent: MENPAN– Enabled Permitting access to personal ID data– Reduces errors in permit applications– Helps identify fraudulent applications– In principle can be used to verify personal ID against other
local and national government records.
15/03/2006 Standards-base Web Services for Interoperability 37
Pare PareCurrent Information Flow
Personal ID
Permitting
Personal IDApplication
(Foxpro)
PermittingApplication(Sybase)
Manual Validation of Identity
Personal IDs
PermitApplication
15/03/2006 Standards-base Web Services for Interoperability 38
Pare PareWeb Services POC
SOAPHTTP
PermittingSystem
Web Server
WEB SER
VICE
S
Data Provider
Personal IDSystem
Cimande
Foxpro
`
Sybase
`
Web Server
Data Provider
Cimande
Validate Personal ID
15/03/2006 Standards-base Web Services for Interoperability 39
Pare PareTechnical Summary
• Demonstrates how interoperability enables an essential security benefit for the Pare Pare Permitting System.
• Demonstrates interoperability between applications developed using different technologies. – Personal ID system uses Foxpro
– Permitting is based on Sybase.
15/03/2006 Standards-base Web Services for Interoperability 40
Mulianto Halim, DirectorPt. Turangga Pranadita
15/03/2006 Standards-base Web Services for Interoperability 41
C. Marine Shipping Reporting• Business problem
– Data is captured using electronic tools, but the data flow between ports, Pelindos and Transportasi is paper.
– Redundant data entry is large waste of time and staff and Introduces errors.
– Process is time consuming. Data loses value with time.
– Current information system precludes decentralization of port authority to regional/local government.
15/03/2006 Standards-base Web Services for Interoperability 42
C. Marine Shipping Reporting• Solution
– Proponent: Secretary General, Transportasi
– Developed system to automate flow of marine shipping data from ports, to Pelindos, to Transportasi HQ.
15/03/2006 Standards-base Web Services for Interoperability 43
Commercial Ports Current Information Flow
Foxpro
TransportasiPelindo Office
Pelindo Transportasi HQ Jakarta
Foxpro MySQL
Secretary General
and Minister
Dat
a E
ntry
Paper Report
Dat
a E
ntry
Paper Report
Dat
a E
ntry
Paper ReportData
ConsolidationAnd Reporting
CollectRaw
ShippingData
Data Consolidation
And Reporting
SImoppelMonthlyShippingReport
Foxpro
Ports(ADPEL)
Dat
a E
ntry
Paper ReportCollectRaw
ShippingData
15/03/2006 Standards-base Web Services for Interoperability 44
Non-commercial PortsCurrent Information Flow
Foxpro
HQ JakartaTransportasi
MySQL
Secretary General and
Minister
Dat
a E
ntry
Paper Report
Dat
a En
try
Paper ReportData
ConsolidationAnd Reporting
Collect Raw Shipping
Data
SImoppelMonthlyShippingReport
Ports(ADPEL)
15/03/2006 Standards-base Web Services for Interoperability 45
Marine Shipping ReportingWeb Services POC
SOAPHTTP
Ports(ADPEL) Pelindo Transportasi
HQ Jakarta
SOAPHTTP
Secretary General and
MinisterTransportasiPelindo
Data EditApplication
Web Server
WEB
SE
RVIC
ES
Data Driver
PortData CaptureApplication
Cimande
HQAggregation
and ReportingApplication
Foxpro MySQLExcel
SIMOPPELMonthlyReport
100 90 80 70 60
Web Server
WEB
SE
RVIC
ES
Data Driver
Cimande
` `
Web Server
Data Driver
Cimande
15/03/2006 Standards-base Web Services for Interoperability 46
Marine Shipping ReportingTechnical Summary
• Demonstrates the ability to use the internet and web services to automate the collection, aggregation, and reporting of shipping information.
• Demonstrates that interoperability requires no modifications to existing shipping electronic data capture and report generating systems.
15/03/2006 Standards-base Web Services for Interoperability 47
Cahyono PartawijayaAssistant Deputy Minister
Data and Information
15/03/2006 Standards-base Web Services for Interoperability 48
Capacity Building
+
Implementation
15/03/2006 Standards-base Web Services for Interoperability 49
Capacity BuildingFour principles adopted.• Use and train local developers with
experienced guidance and supervision. • Use IT staff (of organizations selected for
proofs of concept) to implement and demonstrate the architecture.
• Work with management to ensure capacity building is practical and follow through commitments would be made.
• Transfer all technology.
15/03/2006 Standards-base Web Services for Interoperability 50
Capacity Building - Results• Two local developers trained and guided to
successfully develop the web services, architecture and proofs of concept.
• Eight IT staff for the three proofs of concept trained now capable of demonstrating and continuing development activities.
• Two local IT professionals now capable of training for web services + PASIR architecture + toolkit, and providing related technical advice.
• Excellent follow through commitments received from key ministries, and private sector participants.
• All IT technology transferred.
15/03/2006 Standards-base Web Services for Interoperability 51
15/03/2006 Standards-base Web Services for Interoperability 52
Implementation Commitments• Four ministries have made specific
implementation commitments to ensure future use and continuing development of the interoperability architecture developed and proven under this project.– Ristek– Menpan– Kominfo– Transportasi
15/03/2006 Standards-base Web Services for Interoperability 53
RISTEK Commitments• Presented by: Engkos Koswara, ADM• Joint Ministerial Decree (with Kominfo and
Menpan) improving access to data as a critical aspect of facilitating ‘good governance’;– recommend all ministries and regional/local
governments use or consider using PASIR (architecture and toolkit) for establishing interoperability among critical legacy systems.
• Information Infrastructure for Ristek/BPPT– PASIR foundation for information infrastructure
within and among RISTEK and LPND.
15/03/2006 Standards-base Web Services for Interoperability 54
• Leadership + Communications– Lead program to socialize interoperability
benefits– Sponsor (+ Kominfo + Menpan)
government wide conference on interoperability
– Sponsor (+ Kominfo + others) interoperability conference for IT industry
– Sponsor (+ others) series of regional conferences and workshops on interoperability for government
RISTEK Commitments
15/03/2006 Standards-base Web Services for Interoperability 55
Menpan CommitmentsPresented by: Hendrumal Panjaitan, Menpan• “Best Practice” for all government
administration and management (both national and regional/local) will now include requirements and guidelines for data access and exchange based on: – Open IT standards– Interoperability, and– PASIR architecture and toolkit (maintained
and supported by Kominfo).
15/03/2006 Standards-base Web Services for Interoperability 56
CommitmentsPresented by: Ibu Lolly Amalia AbdullahDirector for Information Systems, Software and
ContentMinistry of Communication and Information
Technology (Kominfo)• Responsibility:
– Kominfo accepts responsibility for PASIR architecture and technology maintain, extend and support; and
– One sub-directorate within Info Systems, S/W and Content is now dedicated to interoperability of information systems and PASIR
Department of Communication and Information TechnologyDepartment of Communication and Information Technology
15/03/2006 Standards-base Web Services for Interoperability 57
CommitmentsDepartment of Communication and Information TechnologyDepartment of Communication and Information Technology
• Advisory role:– Advise and assist other ministries to implement
interoperability for legacy systems based on PASIR.
• S/W development projects:– PASIR will now be used as web services and
interoperability foundation for;• e-Government (now in development)• e-Business, particularly for SMEs (about to be
developed)• e-Health (planned for development)
15/03/2006 Standards-base Web Services for Interoperability 58
CommitmentsDepartment of Communication and Information TechnologyDepartment of Communication and Information Technology
• PASIR to provide web services and interoperability foundation other key projects, including:
– SIN, Single Identity Number; where PASIR will now be used as a foundation for the reference number system to link all public services databases;
– SISKAB, the Cabinet Information System; where it will be used to gather the important information needed by the President and his Cabinet; and
15/03/2006 Standards-base Web Services for Interoperability 59
CommitmentsDepartment of Communication and Information TechnologyDepartment of Communication and Information Technology
– Coordinating Ministry for Politics, Laws and Security; the Committee’s new Executive Information System (EIS) will use PASIR as the interoperability architecture and basis for data access and exchange across the six ministries to provide a more timely, effective and efficient Cabinet level EIS.
15/03/2006 Standards-base Web Services for Interoperability 60
Transportasi CommitmentsPresented by: Wendy AritenangSecretary General, Ministry of Transportation 3. Commercial Ports - Executive Information
System (EIS)– Create a new EIS for the Ministry to
improve dramatically the timeliness and reliability of shipping and related port data for (the 130) commercial ports and Pelindos. EIS will be based on PASIR and will use the ‘proof of concept’ as starting point;
– This opportunity will be used to streamline (reengineer) the business process for shipping and port operations data flows.
15/03/2006 Standards-base Web Services for Interoperability 61
Transportasi Commitments2.Non-commercial Ports - Information
System– Develop a modern information
system for the 300+ non-commercial ports reporting to Transportasi dramatic improvements in all aspects of shipping, safety and operations data for these ports;
– New system to be based on PASIR architecture and web services toolkit.
15/03/2006 Standards-base Web Services for Interoperability 62
Transportasi Commitments3.Decentralization of Authority - Non-
commercial Ports– Based on the new system (with built-
in process for accountability), Transportasi will be able to transfer authority for the operations of 300+ marine ports to local governments. This will be a major new step in the government’s decentralization program.
15/03/2006 Standards-base Web Services for Interoperability 63
Transportasi Commitments
4.National Transport Management System
• Develop: a permanent integrated information system and ‘management centre’, based on PASIR and on experience from the transport crisis management centre established annually during Idul Fitri to manage people movement nationwide.
15/03/2006 Standards-base Web Services for Interoperability 64
Transportasi Commitments5. Access to Information on Transportation
Relevant information would be directly accessible, with appropriate security and protection for confidential and strategic information, • Minister, Secretary General and
management of Transportasi• Office of the President and Cabinet (via
SISKAB)• Other ministries and public agencies• Local governments, and• General public.
15/03/2006 Standards-base Web Services for Interoperability 65
Project SummaryWork plan: approved by RISTEK + Kominfo + Menpan + Transportasi
– Architecture for using web services for interoperability among legacy/existing systems was:
• Recommended, approved and named ‘PASIR’; and • Developed and tested.
– Three case projects were:• Recommended and approved;• Developed and tested for proof of concept; and• Demonstrated.
– Local staff were trained and used throughout to:• Develop all systems and case project applications;• Demonstrate all systems and proof of concept; and• Play key roles in delivering workshops and training.
15/03/2006 Standards-base Web Services for Interoperability 66
Success FactorsSteering Committee requested independent comment on why this project successful where others failed.
• Project start with clear vision shared by 3 ministries:– Ambitious, but achievable objectives (including
definite deadline to finish)– Prepared to try new approaches– Multi-ministry participation + team– Create opportunities for private sector participation
• Outstanding support + commitment throughout:– four ministries (RISTEK, Kominfo, Menpan,
Transportasi)– private sector, and– Minister of RISTEK
15/03/2006 Standards-base Web Services for Interoperability 67
Success Factors cont
• e-LeadershipCombination of ‘open IT standards + OSS + interoperability’ captured the attention (and subsequently enthusiasm) of IT management and staff:– practical way to significantly improve the use of
legacy systems, and avoid throwing away applications;
– avoids costly battles resulting from vendor bias; • it is neither anti-Microsoft nor pro any other
vendor or system; provided a system is based on open IT standards it can be interoperated with any other standards-based system.
15/03/2006 Standards-base Web Services for Interoperability 68
Special AcknowledgementsFor cooperation and commitment:
• Payroll Accounting proof of concept
– Farhan Royani, Direktur, MSM Consultants
• Pare Pare ID Admin Permitting proof of concept
– Mohammad Zain Katoe, Walikota Pare Pare
– Haryanto, Coordinator, ‘The Pare Pare City One Stop Service’ (SINTAP)
– Mulyanto Halim, private consultant, developer Pare Pare ID Administration System.
15/03/2006 Standards-base Web Services for Interoperability 69
• For extraordinary intellectual (and physical) effort and achievements, acknowledgement and thanks to:
– Frans Thamura
– Alex Sander
Finally …
15/03/2006 Standards-base Web Services for Interoperability 71
end of presentation