zerO’clock is ISO certified also for Software Development, System Integration, Information Security Management and Project Management.

 

International Standards bring technological, economic and societal benefits. They help to harmonize technical specifications of products and services making industry more efficient and breaking down barriers to international trade. Conformity to International Standards helps reassure consumers that products are safe, efficient and good for the environment.

 

For business, International Standards are strategic tools and guidelines to help companies tackle some of the most demanding challenges of modern business. They ensure that business operations are as efficient as possible, increase productivity and help companies access new markets.

 

Benefits include:

  • Cost savings – International Standards help optimize operations and therefore improve the bottom line.
  • Enhanced customer satisfaction – International Standards help improve quality, enhance customer satisfaction and increase sales.
  • Access to new markets – International Standards help prevent trade barriers and open up global markets.
  • Increased market share – International Standards help increase productivity and competitive advantage.
  • Environmental benefits – International Standards help reduce negative impacts on the environment.

 

Below the details of zerO'clock certifications.

 

ISO 9001:2008 – Quality Management Systems
ISO 9001:2008 sets out the criteria for a quality management system. We can use regardless all of our field of activity. The standard is based on a number of quality management principles including a strong customer focus, the motivation and implication of top management, the process approach and continual improvement. These principles ensure that customers get consistent, good quality products and services, which in turn brings many business benefits.
ISO/IEC 27001:2013 – Information Security Management Systems
The ISO 27000 family of standards helps organizations keep information assets secure. ISO/IEC 27001:2013 specifies the requirements for establishing, implementing, maintaining and continually improving an information security management system within the context of the organization. It also includes requirements for the assessment and treatment of information security risks tailored to the needs of the organization. ISO/IEC 27001 is the best known standard in the family providing requirements for an information security management system (ISMS). We use and apply this standards to manage the security of assets such as financial information, intellectual property, employee details or information entrusted by third parties.
ISO/IEC 12207:2008 – Systems and software engineering / Software life cycle processes
ISO/IEC 12207:2008 establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware. ISO/IEC 12207:2008 applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included. ISO/IEC 12207:2008 also provides a process that can be employed for defining, controlling, and improving software life cycle processes.

ISO/IEC 25010:2011 – Systems and software engineering — Systems and software
Quality Requirements and Evaluation (SQuaRE) — System and software quality models ISO/IEC 25010:2011 defines:

  • A quality in use model composed of five characteristics (some of which are further subdivided into subcharacteristics) that relate to the outcome of interaction when a product is used in a particular context of use. This system model is applicable to the complete human-computer system, including both computer systems in use and software products in use.
  • A product quality model composed of eight characteristics (which are further subdivided into subcharacteristics) that relate to static properties of software and dynamic properties of the computer system. The model is applicable to both computer systems and software products.
  • The characteristics defined by both models are relevant to all software products and computer systems. The characteristics and subcharacteristics provide consistent terminology for specifying, measuring and evaluating system and software product quality. They also provide a set of quality characteristics against which stated quality requirements can be compared for completeness.

Although the scope of the product quality model is intended to be software and computer systems, many of the characteristics are also relevant to wider systems and services. ISO/IEC 25012 contains a model for data quality that is complementary to this model. The scope of the models excludes purely functional properties, but it does include functional suitability.
The scope of application of the quality models includes supporting specification and evaluation of software and software-intensive computer systems from different perspectives by those associated with their acquisition, requirements, development, use, evaluation, support, maintenance, quality assurance and control, and audit. The models can, for example, be used by developers, acquirers, quality assurance and control staff and independent evaluators, particularly those responsible for specifying and evaluating software product quality. Activities during product development that can benefit from the use of the quality models include:

  • identifying software and system requirements;
  • validating the comprehensiveness of a requirements definition;
  • identifying software and system design objectives;
  • identifying software and system testing objectives;
  • identifying quality control criteria as part of quality assurance;
  • identifying acceptance criteria for a software product and/or software-intensive computer system;
  • establishing measures of quality characteristics in support of these activities.
ISO 21500:2012 – Guidance on Project Management
ISO 21500:2012 provides guidance for project management and can be used by any type of organization, including public, private or community organizations, and for any type of project, irrespective of complexity, size or duration. ISO 21500:2012 provides high-level description of concepts and processes that are considered to form good practice in project management. Projects are placed in the context of programmes and project portfolios, however, ISO 21500:2012 does not provide detailed guidance on the management of programmes and project portfolios.
ISO 12967-2:2009 Health informatics
ISO 12967-2:2009 specifies the fundamental characteristics of the information model to be implemented by a specific architectural layer (i.e. the middleware) of the information system to provide a comprehensive and integrated storage of the common enterprise data and to support the fundamental business processes of the healthcare organization, as defined in ISO 12967-1. 
The information model is specified without any explicit or implicit assumption on the physical technologies, tools or solutions to be adopted for its physical implementation in the various target scenarios. The specification is nevertheless formal, complete and non-ambiguous enough to allow implementers to derive an efficient design of the system in the specific technological environment that will be selected for the physical implementation. This specification does not aim at representing a fixed, complete, specification of all possible data that can be necessary for any requirement of any healthcare enterprise. It specifies only a set of characteristics, in terms of overall organization and individual information objects, identified as fundamental and common to all healthcare organizations, and that is satisfied by the information model implemented by the middleware.