FRUCT16,  Oulu,  Finland

Open  Budget  FormatOlga  Parkhimovich,  Vitaly  Vlasov

1

Outline• Reasons  • Budget  process  in  Russia  • Project  scope  • Approach  1.  Using  OpenSpending  • Approach  2.  Open  Budget  Format  • Future  work

2

Reasons

• High  interest  among  authorities  in  making  budget  more  transparent  and  reusable  

• Current  budget  process  is  inefficient    • Problems  of  using  current  format  • Citizens  need  to  know  how  their  taxes  are  spent  • Civil  society  should  engage  in  all  stage  in  the  budget  process

3

Budget  Process  in  Russia

Stage 1. Drawing up the draft budget

Stage 2. Review and approve the budget

Stage 3. Implementation of the budget

Stage 4. Preparation the budget execution report

~4 budget versions

+ >2 budget versions

Budget  Life  Cycle

>12 budget execution reports

Levels  of  Budget

National

Regional

Municipal

1 doc

>23 000 docs

>80 docs

Government  Contracts

4

Name Target costs Type of costs

Section, subsection Amount

1 Total 76 591 596,0

2 State Program «Public Health» 51 0 0000 13 388 576,1

3 Subprogram «Primary health care» 51 1 0000 601 242,0

4 Costs for the operation of state-owned public institutions 51 1 0016 169 453,3

5 Wage fund of state-owned institutions and contributions for compulsory social insurance 51 1 0016 111 135 922,3

6 Ambulatory care 51 1 0016 111 0902 135 922,3 budg

et it

em

Current  Structure  of  Budget  File

5

Code of the chief

administrator of budget

funds

Section code

Subsection code

Code of the target articleType of

costs code

Government Operations

codeProgram

code

Subprogram

code

Spending priorities code

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Budget  classification  code

Project  Scope

6

•Goal:  to  make  budget  data  simple  and  useful  for  developers  and  citizens  

•Tasks:  •analyse  existing  approaches  • implementation  of  international  methods  for  the  Russian  data    

•develop  initial  standard  and  specification  of  Open  Budget  Format  (OBF)  version  1.0

Approach  1.  Using  OpenSpending

7

• Popular  platform  for  publication  of  financial  information:  https://openspending.org/    

• Budget  items  are  presented  as  rows  with  values  of  different  «dimensions».  Dimensions  could  be  organized  in  groups  and  facets  for  better  visualization  

• Open  Refine  tool  has  been  used  to  prepare  data  for  OpenSpending.

https://openspending.org/russianbudgets/

DimensionsUsing  of  Open  Refine

Problems with OpenSpending:

• Current budget format could not be imported directly (without preparation)

• Specific requirements for Open Spending

Solution:

• Automation of preparing budget file with Open Refine tool.

Implementation

Pros:

• System is ready to use

• Good visualization tool

• Budget items are interlinked

Cons:

• This is proprietary format. Open Spending is just one of systems and like «Microsoft» in the world of financial data (like XLS vs. CVS).

• Government is not ready to put data into third-party services.

• This data format could not be used for interoperability for government needs.

We suggest another way:

• Our approach is not software but proposal of Data Format which could be applicable for different systems.

• Government can use this format as they want and integrate in their own systems.

• Easy to use for exchange information and building new services (official government services or citizen apps)

Budget item page

Program

Name

Code

SubProgram

Code

Name

……

See example of "budget item" page in Open Spending

Budget Code

beta  version  of  Leningrad’s  budget  for  citizens  website:  lenobl2014.ru

• Include best practices of the existing standards (e.g. SDDS

1 of IMF

2, Open

Contracting 3, Open Spending)

• Compatible with Data Packages4.

• Based on text formats (JSON, CSV, XML)

Approach  2.  Open  Budget  Format  

9

JSON CSV XML

Data package4

SDDS1

OCDS3

XLS5

Compatibility

Versioning

Versality

Scalable

Current budget formats

Text formats

Key characteristics

1 SDDS - Special Data Dissemination Standard

(http://dsbb.imf.org/Pages/SDDS/home.aspx) 2 IMF - International Monetary Fund

3 OCDS - Open contracting Data Standards by

Web Foundation (http://ocds.opencontracting.org/standard/r/0__3__2/.html) 4 http://dataprotocols.org/data-packages/

5 XLS - current Russian standard of budget

Versality Simple, general and universal, represent the budgets on different levels.

Good for automation Convenient for automatic processing and clear, if necessary for editing (converting) it by user.

Scalable Ability to use to represent any budgets in other countries too.

Versions support It is necessary to be able to specify different versions of the budget.

Integrated. Compatible with other budget formats

Easy for integrating with other existing formats such as Open Spending, Open Contracting Data Standard and Budget Data Package.

Friendly and intuitiveIn connection with trend of publishing «budgets for citizens» and «open budget» by governments it is necessary to have such version of OBF (readable both for machines and people).

Approach  2.  Open  Budget  Format.  Key  Characteristics

10

Name Avaliable types Mandatory Description

itemId string required Unique ID of item in current data set. May include numbers, etters, special symbols

version string required Version of budget doc, see details below. Could be «final» or Number

docVersion number required Last version of document

level enum required "national" (N), "regional" (R), "municipal" (M)

country string required Code of Country (RU, US, etc)subject string required Name of City, Region or Country, depends on level

dateCreation date-time required Date when current budgetItem has been createddateChanged date-time required Date when current budgetItem has been changed

tag enum required "expenditures", "income"

stage enum required"Proposal", «approval", "adjustment", «execution", "amendment". Any additional comments could be included in comments section.

lang string required Current language of documentcomment string optional For example reference to law

Implementation.  Meta  Data  Fields  in  OBF

11

Name Avaliable types Mandatory Description

budgetItemCode string required National budget classification or code system (in Russia Code of Budget Classification)

budgetItemName string required Name of budget item

adminName string required Name of organization that carries out operations with current budget item

adminCode string optional Code of organization

amount number required Amount of budget item

currency string required Currency of country or operation

Required  Data  Fields  in  OBF

12

Name Avaliable types Mandatory Description

programName string for Russia Name of programprogramCode string for Russia Code of program

subprogramName string for Russia Name of subprogramsubprogramCode string for Russia Code of subprogramsectionEcName string for Russia Section of economicssectionEcCode string for Russia Code of section of economics

subsectionEcName string for Russia Name of subsection of economicssubsectionEcCode string for Russia Code of subsection of economics

articleCode string for Russia Code of target articletypeOfCosts string for Russia Type of expenditure

typeOfCostsCode string for Russia Code of type of expendituregovOperName string for Russia Government operation namegovOperCode string for Russia Government operation code

uri string optional If available for current budget itemcofogCode string optional Code of Classification of the Functions of Government

(COFOG)cofogName string optional Name of COFOGimfName string optional Name of International Monetary bank (IMF) classification

codeimfCode string optional IMF Code

Specific  Data  Fields  in  OBF

13

Versioning

14

•Mechanism  of  updating  current  file  («U»,  update)  

•Each  version  has  own  file  («F»,  files)  

• Info  about  stages  of  budget  («S»,  stages)

U-­‐,  US-­‐,  F-­‐,  FS-­‐  versions

CSV  version  of  OBF  v1.0

15

•All  data  is  presented  as  rows  •First  rows  should  contain  names  of  field  •All  areas  of  fields  should  be  presented  for  each  row  

•U,  US,  F,  FS-­‐versions  could  be  implemented

{ “budgetItem” : { “itemId” : “121299”, “version” : “final”, “docVersion” : “1”, “level” : “R”, “country” : “RU”, “subject” : “Leningrad Region”, “dateCreation” : “16-09-2014 13:14:13”, “dateChanged” : null, “tag” : “income”, “stage” : “execution”, “lang” : “ru” } }

<metadata> !<level>R<level> <country>RU</country> <subject>Leningrad Region</subject> <lang>ru</lang> </metadata> <items> !<budgetItem> !<itemId>121299</itemId> <version>final</version> <docVersion>1</docVersion> <dateCreation>16-09-2014 13:14:13 </dateCreation> <tag>income</tag> <stage>execution<stage> </budgetItem> </items>

{ "type": "budgetItem", "properties": { "itemId": { "type": "string" }, "version": { "type": "string" }, "docVersion": { "type": "number" } "level": { "type": "string", "enum": ["N", "R", "M"] } ... },

JSON Schema

A piece of data

Example of XML data

JSON  view  &  XML  view

16

Conclusions  &  Future  Work

17

•We  can  convert  and  visualize  the  budget  for  less  than  three  hours,  and  explain  this  process  to  the  ordinary  citizen  or  official  

•We  have  the  first  version  of  Open  Budget  Format  •Future  work:  •ontologies  for  Russian  budget  process  and  mechanism  for  making  linked  budget  data  

•comparison  of  budgets  and  government  contracts  •more  useful  visualizations

Contacts  !

Olga  Parkhimovich,  olya.parkhimovich@gmail.com,  

@OpenDataRu  !

Vitaly  Vlasov,  inxaoc@gmail.com,   @inxaoc

FRUCT16,  Oulu,  Finland  18

KEEP  CALM  AND  TRY  TO  RESEARCH  BUDGET  DATA