Dette er en utdatert side

Du er nå kommet til en gammel utdatert side. Du kan besøke våre nye sider her.

This is an outdated page

You have reached an old outdated page. Please visit our new pages here.

Organizational change distributed on ministries and affiliations

Ministries:


Affiliations:

 

Inclusion of groups:

Group of bodies subordinated ministry
Body part of group subordinated ministry

Group of bodies subordinated integrated civil service organization
Body part of group subordinated integrated civil service organization

Organizational change:

"New-" changes:

Explanation for organizational change-code '101 Regular foundings'

This code is used when the unit is born without any connections to other units.

Some units given this code will most probably have a history or background, which indicates that other codes should have been used. If knowledge to this information is not known at the time of coding, this code has been used.

Explanation for organizational change-code '102 Foundings by secession'
Code 102 "Founding by secession" is used when a unit is given an independent standing / status through a secession from an existing unit. In this process, the remaining unit is given the code 202; "Maintenance by secession". Information about the relation between the units involved in this process is given in a separate field ("Relation").
Explanation for organizational change-code '104 Foundings by splitting'
When a unit cease to exist through a splitting into two or more new units, the code 104 "Founding by splitting" is used for the new unit. In this process, the dismantled unit is given the code 304; "Ending by splitting". Information about the relation between the units involved in this process is given in a separate field ("Relation").
Explanation for organizational change-code '106 Foundings by merger'
This code is used when two or more units are merged into one new unit which is given an independent standing / status. In this process, the dismantled units are given the code 306 "Ending by merger". Information about the relation between the units involved in this process is given in a separate field ("Relation").
Explanation for organizational change-code '111 Foundings by complex reorganization'
Sometimes it is difficult to use specific codes for organizational change; for instance when major changes occur at the same time with several units. It can be difficult to trace exactly what happens to the units involved in the change. In such complex events the code 111 "Founding by complex reorganization" is used for new units. The codes 211 "Maintenance by reorganization" and 311 "Ending by complex reorganization" may also be used for any possible existing and terminated units.
Explanation for organizational change-code '112 Entered; new relevant entity'
Creation by inscription (technical code when a unit is entered in the database and we don't know the time of birth or history behind birth).

"Maintenance-" changes:

Explanation for organizational change-code '202 Maintenance by secession '
Code 202 "Maintenance by secession" is used for the remaining unit when a new unit is given an independent standing / status through a secession from an existing unit. In this process, the new unit is given the code 102; "Founding by secession". Information about the relation between the units involved in this process is given in a separate field ("Relation").
Explanation for organizational change-code '203 Maintenance by absorption '
Code 203 "Maintenance by absorption" is used when an existing unit absorbs another existing unit. In this process the dismantled unit is given the code 303; "Ending by absorption". Information about the relation between the units involved in this process is given in a separate field ("Relation").
Explanation for organizational change-code '207 Changes of name '

This code is used when a unit change its name without changing any other obvious aspects (cosmetic change). Can also be used in combination with other specific codes for organizational change to ensure the correct name of a unit.

Obviously, other change concerning functions and structure of the unit in question may be behind this type of change.

Explanation for organizational change-code '209 Changes of location '
Code 209 "Change of location" is used when a unit is moved from one location to another.
Explanation for organizational change-code '211 Maintenance by reorganization'
Sometimes it is difficult to use specific codes for organizational change; for instance when major changes occur at the same time with several units. It can be difficult to trace exactly what happens to the units involved in the change. The code 211 "Maintenance by reorganization" is used for units that "survive" the upheaval.
Explanation for organizational change-code '213 New line of reporting'
Code 213 "New line of reporting" is used in cases where a new unit is established between two existing units. In such cases, the unit lowest in the hierarchy will report to a new superior unit. For example, if a new section is established between an existing office and an existing department within a ministry, the existing office will have a new line of reporting.
Explanation for organizational change-code '221 New superior organization (horizontal movement) '
This code is used when a unit reports to a new superior organization without changing its own form of affiliation or administrative level (horizontal movement). For units within a ministry, this type of change may occur both inside and between ministries. For units outside ministries, this type of change involves movement between ministries.
Explanation for organizational change-code '222 New form of affiliation/administrative level '
This code is used when a unit is reorganized and changes its form of affiliation/administrative level. Vertical reorganization (transformation from one form of affiliation to another) is mainly used for units outside ministries. The unit reports to the same ministry after the change. But the code is also used for units within a ministry to capture change of administrative level.
Explanation for organizational change-code '223 New superior organization and level'
This code is used when a unit reports to a new superior organization and at the same time changes its form of affiliation/administrative level. This code is a combination of 221 "New superior organization (horizontal movement)" and 222 "New form of affiliation/administrative level". This code is always used when a unit is transferred to counties or municipalities, or privatized (transferred to non-profit sector or market).
Explanation for organizational change-code '291 No change to units, but change of superior'
This code is used when a unit reports to a new superior organization at the same time as its previous superior organization is terminated. No change in form of affiliation / administrative level. The code is widely used to transfer all units subordinated one ministry to a new ministry when the first ministry is terminated. This code is of a technical character as no specific change happens to all subordinated units; the change is on a higher lever (the ministry). The code is necessary to place all subordinated units under its new superior ministry, i.e. there is no change to unit itself, but change of superior.
Explanation for organizational change-code '292 Units moving into integrated organizations '
This code is used when a unit moves into an integrated organization or a group organization; the unit in question becomes part of a larger service / group of organizations.

"Terminate-" changes:

Explanation for organizational change-code '303 Endings by absorption'
Code 303 "Ending by absorption" is used when an existing unit is absorbed by another unit. The unit, which lives on, is given the code 203 "Maintenance by absorption". Information about the relation between the units involved in this process is given in a separate field ("Relation").
Explanation for organizational change-code '304 Endings by splitting'
When a unit cease to exist through a splitting into two or more new units, the code 304 "Ending by splitting" is used for the terminated unit. In this process, the new units are given the code 104; "Founding by splitting". Information about the relation between the units involved in this process is given in a separate field ("Relation").
Explanation for organizational change-code '306 Endings by merger'
This code is used when two or more units are merged into one new unit which is given an independent standing / status. In this process, the dismantled units are given the code 306 "Ending by merger". Information about the relation between the units involved in this process is given in a separate field ("Relation")
Explanation for organizational change-code '310 Pure disbandings'
When a unit is permanently disbanded, code 310 "Pure disbanding" is used. In the database, this code probably is used too often due to lack of information about possible continuation of tasks and functions.
Explanation for organizational change-code '311 Endings by complex reorganization'
Processes where the formal structure of one or several organization are completely wiped out and replaced with one or several new organizations characterize these changes. This implies that it is very hard to identify the units going into a reorganization process after the process is completed although tasks and functions handled by the new organization(s) are much the same as before the reform. Tasks, functions, resources and staff carry on, but are mixed in a new formal structure, usually with new names. Old units are permanently disbanded and no longer visible after the change.
Explanation for organizational change-code '312 Discharged; no longer relevant entity'
When an organizational event implies that a unit no longer is subordinated a ministry (privatized or transferred to local government for instance); the unit is no longer a relevant entity in the database. The unit is then given the code 312 "Discharged; no longer relevant entity".

Period:

 

Source: NSD´s State Administration Database | Condition for Use of Data | Access to Data