Proposal for CSPA

Zum Ende der Metadaten springen

Ready for Testing

Reviewed Proposal for CSPA

Proposers: Elaine, Juan

Reviewers: Guillaume, Christina, Essi

Self-assessment criteria for CSPA

Levels Dimensions	Initial	Pre-implementation	Early implementation	Corporate implementation	Mature implementation
Business	Each area designs and develops its own solutions. Budget and staff is located at each area.	Although each area continues designing its own solution they try to make them modular and share the code. The ICT budget and staff are still located at each area but central coordination creating some general guidelines exists.	There is analysis of the business processes. GAMSO and GSBPM are applied as a basis to identify each statistical service and business function. Some of the roles defined by CSPA start being recognized and informally adopted by the ICT areas.	A unique services environment running on a common ICT platform to attend all organizational needs are part of the organization’s long term plans. All services are defined following an agreed granularity level. ICT resources (people, budget, skills, etc.) are mainly oriented to build and maintain the common platform. CSPA roles and responsibilities are clearly defined and mapped to areas in the organization.	Statisticians are able to make specific orchestrations of services to cover their projects and new user’s requests. A specialized ICT cross-organization group is in charge of the maintenance and expansion of the services platform. There is a planned evolution of the ICT services based in long term institutional goals, historic performance indicators and external changes.
Methods	Methods are not standardized.	There are some attempts to use some common methodologies, mainly related to codification standards and APIs definition but under the interpretation of each area.	CSPA and other standards starts to be implemented as a concern of the whole organization, but the implementation is partial obeying to internal needs. First attempts to develop SOA/CSPA based services.	CSPA has been implemented, and all ICT staff in the organization follows it. Reuse and sharing of services developed by other NSOs is a common practice. Service virtualization is a “must” characteristic in order to make the instantiation of the services easier in different environments.	A basic set of skills shared by all NSOs is defined making it easier to find trained people able to participate on interinstitutional collaboration efforts.
Information	Information is duplicated and each application uses its own structure.	Separated information structures in separated systems are common. Some applications share information but in the form of views or other similar mechanisms. Separation of development and production databases starts to being made.	Integrated databases covering several domains exist and services use these shared information sources. Early attempts to apply GSIM and CSPA LIM are carried out. There are separated instances of the databases for development, testing and production, each one following specific rules. Production and dissemination databases are clearly separated.	The common services platform accesses an integrated information environment. The information environment follows the CSPA LIM so shared services can be configured by each organization to cover its own needs.	Information databases can incorporate new sources of information without affecting the services environment applying an internationally agreed set of models and standards. Information is independent of the environment, so internal, public and hybrid facilities can be used in a transparent way.
Applications	Applications run as separated instances. It’s very difficult to make them interoperable, manual work is inevitably required.	Some common component libraries start to appear. The components are difficult to integrate in practice and therefore often rejected. Some commercial components start to be integrated.	Some early service oriented systems making use of services attending certain common activities starts to appear. Services orchestration is still an issue that is mainly carried out for each system.	All applications are developed as an orchestration of services following the CSPA guidelines. Services are developed to be independent of specific ICT configurations. An international service catalog is used to complement the organization's own one.	Some (or all) services are shared by several statistical organizations. There is a shared catalog that is used by the institutions as a first level place to find existent services. Local catalogs are still being used for very specific services.
Technology	Technology implementations are carried out by demand satisfying individual, isolated, requirements and generating heterogeneity of hardware, software, languages, protocols, etc. Management and support of technology goes from absent to very basic.	There is a definition of a set of core technologies supported by the organization which is mostly used as a guideline, but each area still deciding how to fulfill the needs of each project so the integration, reuse and support of technologies is very limited.	There is a standardized ICT platform which is supported by the organization. Interaction of ICT solutions is a common practice because all areas share the same set of technologies. Reutilization of solutions on diferent projects is the common rule. Resources are dynamically managed to optimize its distribution.	ICT platform fully supports the SLAs of the services platform, and includes all the needed components to virtualize the services. ICT solutions are customized for the needs of the projects. Hardware and software are optimized dynamically to attend changes in requirements and demands of the statistical business processes.	There is a consolidated corporate ICT platform and parts of it are used by several subscribed organizations sharing costs, responsibilities and management supporting commonly agreed SLAs.

Seitenhierarchie

2 Kommentare

Juan Muñoz sagt:

Juan Muñoz sagt: