Definition: Where possible, public administrations should seek to streamline and simplify their administrative processes by improving them or eliminating any that do not provide public value. Administrative simplification means, where possible, streamlining and simplifying administrative processes by improving them or eliminating anything that does not provide public value. Administrative simplification can help businesses and citizens to reduce the administrative burden of complying with EU legislation or national obligations.Digitisation of public services should take place in accordance with the following concepts:• digital-by-default, whenever appropriate, so that there is at least one digital channel available for accessing and using a given European public service;• digital-first which means that priority is given to using public services via digital channels while applying the multi-channel delivery concept and the no-wrong-door policy, i.e. physical and digital channels co-exist. Simplify processes and use digital channels whenever appropriate for thedelivery of European public services, to respond promptly and with highquality to users’ requests and reduce the administrative burden on publicadministrations, businesses and citizens.""
Source: Administrative Simplification Underlying Principle (10) of the European Interoperability Framework (EIF)
Source reference: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/glossary/term/administrative-simplification
Last modification: 2024-01-17
Identifier: http://data.europa.eu/2sa/elap/administrative-simplification
LOST view: TVA-Functional Architecture Principles
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: elap:administrative-simplification
Title: Administrative Simplification
EIF Layer: N/A
ABB Specialised: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
|
|
dct:type | elap:ServiceOrientationPrinciple |
dct:title | Service Orientation |
eira:PURI | http://data.europa.eu/2sa/elap/service-orientation |
dct:modified | 2024-01-17 |
eira:definitionSource | Open Group |
eira:definitionSourceReference | https://web.archive.org/web/20160819141303/http://opengroup.org/soa/source-book/soa/soa.htm |
eira:eifLayer | N/A |
eira:concept | eira:ArchitectureBuildingBlock |
skos:definition | Service orientation is a way of thinking in terms of services and service-based development and the outcomes of services. Being user-centred or remaining \"user-led,\" is possible with a service-oriented strategy. It entails offering services that employ the best technological solutions to provide better results. By making this change, the organization will put user demands and goals at the centre of its vision, culture, and operations. After then, make sure that everyone supports it and owns it so that decisions and technology are driven by user demands.A service-oriented strategy entails developing an IT platform made up of numerous systems, each one tailored to carry out particular tasks. You can change one aspect of a systems functionality with a tech stack made up of separate components without changing the operation of the entire system. Certain components can be digitalized more quickly because of this function fragmentation, which also offers a distribution strategy that allows for independently distributed functions. Communication with external programs is also made possible by separate systems where each software tool is designed to carry out a specific task using a well-defined interface.There are a variety of technologies that can be applied to this service orientation approach such as SOAP, REST API and GraphQL. At the organisational level, public administrations need to establish the proper agreements that allow collaboration and common mechanisms to provide relevant information through the desired Service Oriented Architecture. At the technical level, the organisations in charge of implementing and delivery of digital public services will need to determine which is the best approach to fit their needs. There are different approaches such as SAP, RESTApi or GraphQL, taking into account the relevant aspects of the services, the organisation responsible for the service should select the more sustainable and efficient way of implementing the SOA approach. "" |
skos:broader | eira:EuropeanLibraryofArchitecturePrinciplesPrinciple |