LGD Impact on PRIASoft

Transcription

1 LGD Impact on PRIASoft Scenario 1: Create new village Sub Scenarios: 1.1 New village is created from new land (when river changes its direction, new island popped-up) 1.2 New village created by taking part of a village 1.3 New village created by taking whole area of existing villages 1.4 New village created by taking area from Urban body Newly created census villages will get automatically updated in work module of PRIASoft. No impact on voucher entries. Add/Modify WorksCase Record 1

2 Scenario 2: Change Village Sub Scenarios: Name of the Village is Changed Changed Village Name will get automatically updated in work module of PRIASoft. No impact on voucher entries. Add/Modify WorksCase Record Scenario 3: Invalidate Village Village is submerged. Sub merged village will automatically get updated in work module of PRIASoft. No impact on voucher entries. Add/Modify WorksCase Record 2

3 Scenario 4: Create PRI Local Government Body 4.1 New PRI Local Body is created from Unmapped/Partially Mapped Land Regions (newly formed village) Username for newly created PRI local body needs to be added in PRIASoft. Create User Newly created PRI Local Body will automatically get reflected in Accounting Entity dropdown in all the modules of PRIASoft. Scenario 4: Create PRI Local Government Body (Contd ) 4.2 New PRI Local Body is created with contribution from existing Local Bodies New username needs to be created for newly created PRI local body. Create User Newly created PRI Local Body will automatically get reflected in Accounting Entity dropdown in all the modules of PRIASoft. 3

4 Scenario 5: Create Traditional Local Government Body 5.1 New Traditional Local Body is created from Unmapped/Partially Mapped Land Regions (newly formed village) Newly Created Traditional Local Body will automatically get updated in PRIASoft. Username needs to be created for newly created Traditional Local Body. Create User Newly created Traditional Local Body will automatically get reflected in Accounting Entity dropdown in all the modules of PRIASoft. Scenario 5: Create Traditional Local Government Body (Contd..) 5.2 New Traditional Local Body is created with contribution from existing Local Bodies New username needs to be added for newly created Traditional local body. Create User Newly created Traditional Local Body will automatically get reflected in Accounting Entity dropdown in all the modules of PRIASoft. 4

5 Scenario 6: Create Urban Local Government Body 6.1 New Urban Local Body is created from Unmapped/Partially Mapped Land Regions (newly formed village) 6.2 New Urban Local Body is created with contribution from existing Local Bodies No Impact since PRIASoftdoes not deal with Urban Local Bodies. No Impact Scenario 7: Change Name of Local Government Body (PRI) 7.1 Name of the PRI Local Body is changed Username needs to be updated in PRIASoft. Changed Name of the PRI Local Body will automatically get reflected in Accounting Entity dropdown in all the modules of PRIASoft. 5

6 Scenario 8: Change Name of Local Government Body (Urban) 8.1 Name of the Urban Local Body is changed No Impact since PRIASoftdoes not deal with Urban Local Body. No Impact Scenario 9: Change Name of Local Government Body (Traditional) 9.1 Name of the Traditional Local Body is changed Username needs to be updated in PRIASoft. Changed Name of the Traditional Local Body will automatically get reflected in Accounting Entity dropdown in all the modules of PRIASoft. 6

7 Scenario 10: Convert Rural Local Body to Urban Local Body 10.1 Rural Local Body converted into new Urban Local Body i.e. selected Village Panchayat(s) declared as new Town Panchayat 10.2 Rural Local Body merged into existing Urban Local Body Data related to Rural Local Body needs to be archived Existing usernames for Rural Local Body needs to be blocked The converted Rural Local Body will not shown in Accounting Entity dropdown in any of the module of PRIASoft. Scenario 11: Convert Traditional Local Body to Urban Local Body 11.1 Traditional Local Body converted into new Urban Local Body 11.2 Traditional Local Body merged into existing Urban Local Body Data related to Traditional Local Body needs to be archived Existing usernames for Traditional Local Body needs to be blocked The converted/merged Traditional Local Body will not shown in Accounting Entity dropdown in any of the modules of PRIASoft. 7

8 Scenario 12: Change Covered Land Region (PRI) 12.1 Some areas are added from Unmapped / Partially Mapped land regions 12.2 Some areas(villages) are added from existing Local Bodies 12.3 Certain areas(villages) are removed from the existing covered area Newly added/deleted villages will automatically get reflected in work module of PRIASoft. No impact on transactions since PRIASoft does not deal with Land Region. Add/Modify WorksCaseRecord -The added/deleted villages will automatically get reflected in add/modify workscase record of PRIASoft. Scenario 13: Change Covered Land Region (Urban) 13.1 Some areas are added from Unmapped / Partially Mapped land regions (Urban) 13.2 Some areas(villages) are added from existing Urban Local Bodies 13.3 Certain areas(villages) are removed from the existing covered area (Urban) No Impact since PRIASoftdoes not deal with Urban Local Bodies. No Impact since PRIASoftdoes not deal with Urban Local Body. 8

9 Scenario 14: Change Covered Land Region (Traditional) 14.1 Some areas are added from Unmapped / Partially Mapped land regions (Traditional) 14.2 Some areas(villages) are added from existing Traditional Local Bodies 14.3 Certain areas(villages) are removed from the existing covered area (Traditional) Newly added/deleted villages (Village Council) will automatically get reflected in work module of PRIASoft. No impact on transactions since PRIASoft does not deal with Land Region. Add/Modify WorksCaseRecord -The added/deleted villages will automatically get reflected in add/modify workscase record of PRIASoft. Scenario 15: Change Parent of Local Body (PRI) 15.1 A Village Panchayat is shifted from one Block Panchayat to another If parent panchayat has multiple privilege for shifted Village Panchayat, the same panchayat has to be removed from the existing parent and added to the new parent. If username has been created for shifted village panchayat, parent code for the same needs to be changed. Select Role The shifted village panchayat will get reflected under its new parent block panchayat. The shifted village panchayat will get reflected in Accounting Entity dropdown in all the modules of the PRIASoft. 9

10 Scenario 16: Change Parent of Local Body (Traditional) 16.1 A Village Council is shifted from one District Council to another If parent has multiple privilege for shifted Village Council, the same has to be removed from the existing parent and added to the new parent. If username has been created for shifted village council, parent code for the same needs to be changed. Select Role - The shifted village council will get reflected under its new parent BAC (Block Advisory Council) The shifted village council will get reflected in Accounting Entity dropdown in all the modules of PRIASoft. Scenario 17: Change Local Government Type (Urban) 17.1 Modify Type (only for Urban Local Bodies) -Change Type of Urban Local Body from Town Area to Municipality, Municipality to Corporation) No Impact since PRIASoftdoes not deal with Urban Local Body. No Impact since PRIASoftdoes not deal with Urban Local Body. 10

11 Scenario 18: Invalidate PRI Local body 18.1 Village Panchayat is invalidated and the Villages under the Village Panchayats merge with one or more other Village Panchayats Data pertaining to invalidated village panchayat needs to be archived Username for invalidated village panchayat needs to be blocked Select Role The deleted village panchayat will not shown in Accounting Entity dropdown. The invalidated village panchayat will not shown in Accounting Entity dropdown in all the modules of PRIASoft. Scenario 18: Invalidate PRI Local body (Contd ) 18.2 District Panchayat is invalidated and the local bodies (like Block Panchayats) under that District Panchayat shifts to other District Panchayats Data pertaining to invalidated district panchayat needs to be archived Username for invalidated district panchayat needs to be blocked If parent (district panchayat under which block panchayat is merged) has multiple privilege for block panchayat, same has to be added to the new parent. If username has been created for block panchayat, parent code for the same needs to be changed. Select Role The invalidated district panchayat will not shown and the child panchayats will shown under its newly assigned parent panchayat in Select Role page. The invalidated district panchayat will not shown and the child panchayats will shown under its newly assigned parent panchayat in Accounting Entity dropdown in all the modules of PRIASoft. 11

12 Scenario 18: Invalidate PRI Local body (Contd ) 18.3 District Panchayat / Block Panchayat / Village Panchayat is invalidated, local bodies under that are also invalidated Data pertaining to invalidated panchayats needs to be archived. Usernames related to invalidated panchayats need to be blocked Select Role The invalidated panchayat will not shown in Select Role page. The invalidated panchayat will not shown in Accounting Entity dropdown in all the modules of PRIASoft. Scenario 19: Invalidate Urban Local body Urban Local Body is submerged No Impact since PRIASoftdoes not deal with Urban Local Body. No Impact since PRIASoftdoes not deal with Urban Local Body 12

13 Scenario 20: Invalidate Traditional Local body 20.1 Village Council is invalidated and the Villages under the Village Council merge with one or more other Village Council Data pertaining to invalidated village council needs to be archived Username for invalidated village council needs to be blocked Select Role The invalidated village council will not shown in Select Role page. The invalidated village council will not shown and the merged village council will shown in its newly assigned parent traditional local body in Accounting Entity dropdown in all the modules of PRIASoft. Scenario 20: Invalidate Traditional Local body (Contd ) 20.2 District Council is invalidated and the local bodies (like Block Council) under that District Council shifts to other District Council Data pertaining to invalidated district council needs to be archived Username for invalidated district council needs to be blocked If parent (district council under which block council is merged) has multiple privilege for block council, same has to be added to the new parent. If username has been created for block council, parent code for the same needs to be changed. Select Role The invalidated district council will not shown and the child traditional local body will shown under its newly assigned parent traditional local body in Select Role page. The invalidated district council will not shown and the child traditional local body will shown under its newly assigned parent traditional local body in Accounting Entity dropdown in all the modules of PRIASoft. 13

14 Scenario 20: Invalidate Traditional Local body (Contd ) 20.3 District Council/ Block Council/ Village Council is invalidated, local bodies under that are also invalidated Data pertaining to invalidated councils needs to be archived. Usernames related to invalidated councils need to be blocked Select Role The invalidated councils will not shown in Select Role page. The invalidated councils will not shown in Accounting Entity dropdown in all the modules of PRIASoft. Scenario 21: Create new Sub-district Sub-districts can be created by the contribution from 1 or more Sub-districts by taking full or part contributions from other Sub-district of the same District No Impact since PRIASoft does not deal with Sub-district No Impact since PRIASoft does not deal with Sub-district. 14

15 Scenario 22: Modify Sub-district Change the name of the Sub-district No Impact since PRIASoft does not deal with Sub-district No Impact since PRIASoft does not deal with Sub-district. Scenario 23: Shift Village between Sub-districts Village shifted from one Sub-district to another Sub-district No Impact since PRIASoft does not deal with Sub-district No Impact since PRIASoft does not deal with Sub-district. 15

16 Scenario 24: Shift Sub-district Shift a Sub-district (to another District) within same State No Impact since PRIASoft does not deal with Sub-district No Impact since PRIASoft does not deal with Sub-district. Scenario 25: Invalidate Sub-District 25.1 The existing villages of the Sub-district can be merged with another Sub-district (only one) of the same District 25.2 Villages can be merged with different Sub-districts of the same District No Impact since PRIASoft does not deal with Sub-district No Impact since PRIASoft does not deal with Sub-district. 16

17 Scenario 26: Create new District The New District is created by taking full or part contributions of one or more Districts, contributing Districts retain their name if contributing partly Username needs to be created for newly added District Admin. Select Role The newly created district administrator will show in Select Role Page. The newly created district will show in Accounting Entity dropdown in all the modules of PRIASoft. Scenario 27: Change District Change name of the District Username needs to be updated for changed District Admin. Select Role The updated district will show in Select Role page. The updated district will show in Accounting Entity dropdown in all the modules of PRIASoft. 17

18 Scenario 28: Shift District Shift District from one State to another State Data pertaining to shifted district needs to be archived Existing username of shifted district needs to be blocked All ZP, BP, VP etcfalling under shifted district needs to be mapped with newly assigned state. Select Role The shifted district will show in its newly assigned state in Select Role page. The shifted district and its child panchayats will display in newly assigned state login. Scenario 29: Invalidate District 29.1 The existing District's Sub-districts are merged with another District (only one) of the same State 29.2 Sub-districts of the invalidated District are merged with more than one District No Impact since PRIASoft does not deal with Sub-district No Impact since PRIASoft does not deal with Sub-district. 18

19 Scenario 30: Create New State / Union Territory New State / Union Territory created from part of one or more existing State(s) / Union Territory(s) Data pertaining to existing state (ZP/BP/VP) needs to be archived Existing username (ZP/BP/VP) of the merged state needs to be blocked New username needs to be added for all ZP, BP, VP etcfalling under state (which is created from part of one or more existing state/union territory) The newly created state admin will be allowed to login in PRIASoft The existing ZP/BP/VP of existing state will show in newly created state and will be allowed to record transactions as fresh entity. Scenario 31: Change State / Union Territory Name of the State / Union Territory is changed Username of the changed state needs to be updated. Select Role The changed username of state admin will be reflected in PRIASoft The changed username of state admin will be shown in PRIASoft. 19

20 Scenario 32: Upgrade UT to State Status of an existing Union Territory is changed to State No impact since both State and Union Territory are considered at same level in PRIASoft. No Impact since no state has been created or deleted/no name has been changed. Scenario 33: Merge ULBs One or more existing Urban Local Bodies is merged into another Urban Local Body No impact since PRIASoftdoes not deal with ULBs No Impact since PRIASoftdoes not deal with ULBs. 20