using the business intelligence module based on the ocds...
TRANSCRIPT
Dmitry Palamarchuk
Using the Business Intelligence Module based on the OCDS for carrying out an analysis in public procurement
Everything starts with data….data structure
OCDS implementation, the goal
• Full coverage of the processes• Consistency• History of amendments• Data quality• Compliance with OCDS Objects, code lists, and extensions
What if we achieved the goal
• Complex data structure
• Tech oriented data format
• Complexity of process flow
interpretation
• No catalogs
• Access through API only
Transparency does not equal to Visibility!
Does transparency help in this case?
How to achieve Visibility?
“Business Intelligence is the delivery of accurate and valuable information, to key decision makers, "on demand." The purpose of which is not to answer the common questions, but instead to uncover new questions and find answers to questions you never thought you would ask.”
From Quora.com
Business Intelligence dashboards
Users are public procurement stakeholders
Operator of the e-procurement system
Public Procurement Agency
Review Body
Treasury
Controlling authorities
NGO
Ministries
SOE’s with branches
Regulators (market regulators)
High-level government officials
Value
• Powerful analytical engine is a MUST for an e-procurement system
• Common ground in KPI’s and numbers for all stakeholders
• Single point of analytical information
• Data discovery approach instead of report approach
• Different sources of information including analytical dimensions
from various catalogs can be utilized
• Dashboards customized for the stakeholder’s functions
• Best practices of KPI’s and dashboards
• Single point of data access in “readable” format (XLS, CSV)
• Any Ad-hoc report in few clicks
