Functional Assignment: Some (more) Thoughts on the Evolving Subject

  • strict warning: Non-static method flag_flag::factory_by_row() should not be called statically in /home/accountindia/webapps/demo/modules/flag/flag.module on line 1357.
  • strict warning: Non-static method flag_flag::factory_by_row() should not be called statically in /home/accountindia/webapps/demo/modules/flag/flag.module on line 1357.
  • strict warning: Non-static method flag_flag::factory_by_array() should not be called statically in /home/accountindia/webapps/demo/modules/flag/flag.module on line 1433.
  • strict warning: Non-static method flag_flag::factory_by_array() should not be called statically in /home/accountindia/webapps/demo/modules/flag/flag.module on line 1433.
  • strict warning: Non-static method flag_flag::factory_by_array() should not be called statically in /home/accountindia/webapps/demo/modules/flag/flag.module on line 1433.
  • strict warning: Non-static method view::load() should not be called statically in /home/accountindia/webapps/demo/modules/views/views.module on line 906.
  • strict warning: Declaration of views_handler_filter::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in /home/accountindia/webapps/demo/modules/views/handlers/views_handler_filter.inc on line 607.
  • strict warning: Declaration of views_handler_filter::options_submit() should be compatible with views_handler::options_submit($form, &$form_state) in /home/accountindia/webapps/demo/modules/views/handlers/views_handler_filter.inc on line 607.
  • strict warning: Declaration of views_handler_filter_term_node_tid::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /home/accountindia/webapps/demo/modules/views/modules/taxonomy/views_handler_filter_term_node_tid.inc on line 302.
  • strict warning: Declaration of views_plugin_style_default::options() should be compatible with views_object::options() in /home/accountindia/webapps/demo/modules/views/plugins/views_plugin_style_default.inc on line 24.
  • strict warning: Declaration of views_plugin_row::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/accountindia/webapps/demo/modules/views/plugins/views_plugin_row.inc on line 134.
  • strict warning: Declaration of views_plugin_row::options_submit() should be compatible with views_plugin::options_submit(&$form, &$form_state) in /home/accountindia/webapps/demo/modules/views/plugins/views_plugin_row.inc on line 134.
  • strict warning: Non-static method view::load() should not be called statically in /home/accountindia/webapps/demo/modules/views/views.module on line 906.
  • strict warning: Non-static method view::load() should not be called statically in /home/accountindia/webapps/demo/modules/views/views.module on line 906.
  • strict warning: Non-static method view::load() should not be called statically in /home/accountindia/webapps/demo/modules/views/views.module on line 906.
  • strict warning: Declaration of calendar_plugin_display_page::options_submit() should be compatible with views_plugin_display_page::options_submit(&$form, &$form_state) in /home/accountindia/webapps/demo/modules/calendar/includes/calendar_plugin_display_page.inc on line 297.
  • strict warning: Declaration of calendar_plugin_display_page::options() should be compatible with views_object::options() in /home/accountindia/webapps/demo/modules/calendar/includes/calendar_plugin_display_page.inc on line 297.
  • strict warning: Declaration of calendar_plugin_display_block::options() should be compatible with views_object::options() in /home/accountindia/webapps/demo/modules/calendar/includes/calendar_plugin_display_block.inc on line 78.
  • strict warning: Declaration of calendar_plugin_display_attachment::options_submit() should be compatible with views_plugin_display_attachment::options_submit(&$form, &$form_state) in /home/accountindia/webapps/demo/modules/calendar/includes/calendar_plugin_display_attachment.inc on line 242.
  • strict warning: Declaration of calendar_plugin_display_attachment::options() should be compatible with views_object::options() in /home/accountindia/webapps/demo/modules/calendar/includes/calendar_plugin_display_attachment.inc on line 242.
  • strict warning: Declaration of calendar_plugin_display_ical::options_submit() should be compatible with views_plugin_display_page::options_submit(&$form, &$form_state) in /home/accountindia/webapps/demo/modules/calendar/calendar_ical/calendar_plugin_display_ical.inc on line 217.
  • strict warning: Declaration of date_handler_field_multiple::pre_render() should be compatible with content_handler_field_multiple::pre_render($values) in /home/accountindia/webapps/demo/modules/date/date/date_handler_field_multiple.inc on line 185.
  • strict warning: Declaration of views_handler_filter_boolean_operator::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /home/accountindia/webapps/demo/modules/views/handlers/views_handler_filter_boolean_operator.inc on line 159.
  • strict warning: Non-static method view::load() should not be called statically in /home/accountindia/webapps/demo/modules/views/views.module on line 906.
  • warning: implode(): Invalid arguments passed in /home/accountindia/webapps/demo/modules/views_customfield/includes/views_customfield_handler_field_phpcode.inc(118) : eval()'d code on line 18.
  • user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') GROUP BY nr.nid ORDER BY nr.nid DESC LIMIT 5' at line 4 query: SELECT DISTINCT(n.title) ,tn.nid as tnid FROM term_node tn LEFT JOIN node_revisions nr ON tn.nid = nr.nid LEFT JOIN node n ON n.nid = nr.nid WHERE (n.type='blog' OR n.type='raghubytes') AND tn.nid != 2887 AND tn.tid IN() GROUP BY nr.nid ORDER BY nr.nid DESC LIMIT 5 in /home/accountindia/webapps/demo/modules/views_customfield/includes/views_customfield_handler_field_phpcode.inc(118) : eval()'d code on line 24.
  • strict warning: Non-static method view::load() should not be called statically in /home/accountindia/webapps/demo/modules/views/views.module on line 906.
  • strict warning: Declaration of views_handler_argument::init() should be compatible with views_handler::init(&$view, $options) in /home/accountindia/webapps/demo/modules/views/handlers/views_handler_argument.inc on line 744.
  • warning: implode(): Invalid arguments passed in /home/accountindia/webapps/demo/modules/views_customfield/includes/views_customfield_handler_field_phpcode.inc(118) : eval()'d code on line 18.
  • user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') ) AND tn.nid IN (779,780,781,782,783,784,785,786,787,788,789,791,792,1450,1468' at line 3 query: SELECT n.nid AS nid, n.title FROM node n LEFT JOIN term_node tn ON n.vid = tn.vid WHERE (tn.tid IN() ) AND tn.nid IN (779,780,781,782,783,784,785,786,787,788,789,791,792,1450,1468,1855,1988,2261,2298,2299,2300,2302,2320,2378,2396,2399,2404,2516,2523,2524,2572,2663,2702,2734,2735,2738,2789,2790,2800,2832,2863,2865,2866,2884,2890) GROUP BY n.nid ORDER BY n.nid DESC in /home/accountindia/webapps/demo/modules/views_customfield/includes/views_customfield_handler_field_phpcode.inc(118) : eval()'d code on line 54.
Posted on:20-10-15

Vincy Davis

(This is part 2 of 2 entries on Functional Assignment by the same author.)

In my previous blog post I initiated a discussion on some of the lessons I learnt from the workshop organised by LOGIN on Functional Assignment. In this post, I will be sharing more of my takeaways from the workshop:

Unbundling” the modalities of decentralisation in light of FA – Conversations centred on the choice of the most appropriate mode of decentralisation were particularly interesting to me as we were made to question the fundamental choices that shape our respective countries. In the Indian context, ‘devolution’ is clearly idealised. Debates are generally carried out on the method/process through which devolution is to be carried out and rarely on whether or not devolution itself is the way to go.

In the 90’s, Local Self-Governments (LSGs) gained national recognition in India through Constitutional amendments. The task of actually devolving functions to the LSGs, however, was left to the states. Since then, functional devolution has been patchy and leaves much to be desired. Moreover, in practice, the Indian administration primarily functions on the principle of deconcentration, preferring to provide the bulk of public services through line departments and parallel agencies. In case of subnational governments, the administration prefers to engage them through delegation of duties in the area of programme implementation.

Undertaking FA in India will force the relevant stakeholders to assess the modes of decentralisation appropriate for different levels of government. It will also be important to address the possibility that multiple modes of decentralisation may be appropriate for different levels. There isn’t much on this topic in the current literature on FA and thus might be worth exploring further.

Lost in translation – One only has to go through the 2014-15 Devolution Report to appreciate the research team’s struggle to rank states on the Devolution Index, owing to the adoption of different definitions of fundamental concepts (such as the 3 Fs themselves) by different states! This lack of consensus on key terms needs to be resolved before a country undertakes FA, unless one wishes to witness turf wars resulting from different definitions. In fact, the term “Functional Assignment” itself can cause confusion since FA doesn’t merely involve assignment of functions, but also of functionaries and funds. Perhaps a more encompassing term could be devised to bind the entire process.

Matching functionaries and funds with the functions “map” – What remains unclear is how functionaries can be meaningfully assigned to functions allocated to the appropriate tiers. This is a question of matching capacity with the task at hand and not just assigning the job to the person with the most qualifications. What are the criteria that should be applied in this context? Whose capacities are we assessing in the first place? Only the officials at the frontline or even the policy makers or members of the steering committee that would guide the FA process? What sort of preparation must these individuals undergo before launching into a dialogue on FA? Similarly, how does one match funds with functions? These are some of the “dilemmas” which were discussed in the workshop but left largely as questions to probe further.

Listening to the discussions on FA concepts and the experiences of other countries in this area, I realized that India has a long way to go before it can truly practice what it preaches. Administrative decentralisation has barely kept pace with the movement on political decentralisation in the country. Moreover, what we peddle in the name of decentralisation itself is quite muddled. When we talk of FA implementation in India, we are talking about a process that could take years to unfold. It could mean undertaking multiple rounds of discussions with stakeholders, pilots to see what works and what does not, and “change management” to contain the effects of structural shifts at an unprecedented scale. Coming to a basic consensus on the abovementioned issues will be essential if we are to even begin having a meaningful conversation on the subject.



Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
Image CAPTCHA
Enter the characters shown in the image.