Find the standard you are looking for at Engineering360. Documents are available for purchase from the IHS Standards Store.

1 - 12 of 12 results

ASTM E1578 - STANDARD GUIDE FOR LABORATORY INFORMATION MANAGEMENT SYSTEMS (LIMS) Organization: ASTM
Date: 2013-08-01
Description: It explains the evolution of laboratory informatics tools used in today's laboratories such as Laboratory Information Management Systems (LIMS), Electronic Laboratory Notebooks (ELN), Scientific Data Management Systems (SDMS), and Chromatography Data Systems (CDS).
ASTM E2066 - STANDARD GUIDE FOR VALIDATION OF LABORATORY INFORMATION MANAGEMENT SYSTEMS Organization: ASTM
Date: 2000-01-10
Description: This guide describes an approach to the validation process for a Laboratory Information Management System (LIMS). This guide is for validation of a commercial LIMS purchased from a vendor.
ASTM E1381 - STANDARD SPECIFICATION FOR LOW-LEVEL PROTOCOL TO TRANSFER MESSAGES BETWEEN CLINICAL LABORATORY INSTRUMENTS AND COMPUTER SYSTEMS Organization: ASTM
Date: 2002-08-10
Description: This instrument output may include patient results, quality control results, and other related information. Typically, the computer system will be a Clinical Laboratory Information Management System (CLIMS).
ASTM - STP1209 - QUALITY AND STATISTICS: TOTAL QUALITY MANAGEMENT Organization: ASTM
Date: 1994-01-01
Description: 14 peer-reviewed papers cover: • Statistical measurement control for the evaluation of laboratory test results of automotive parts • How ISO 9000 registration relates to accreditation bodies worldwide • Formal design review, failure mode effects analysis, and fault tree analysis procedures • An explanation of the Energy Program Research Institute guide for sampling procured items for the nuclear industry • Application of E691, ASTM Guide for Interlaboratory Studies, and its computer software capabilities • Advantages of continuous process flow analyzers in the Canadian oil industry.
CLSI AUTO11 - INFORMATION TECHNOLOGY SECURITY OF IN VITRO DIAGNOSTIC INSTRUMENTS AND SOFTWARE SYSTEMS; APPROVED STANDARD - SECOND EDITION; VOL 34; NO 17 Organization: CLSI
Date: 2014-10-01
Description: The intended users for this standard are vendors (IVD system manufacturers), users (eg, laboratory personnel), and IT management of HCOs. This standard is not intended for use as the final written policy for the HCO.
ASTM D3856 - STANDARD GUIDE FOR MANAGEMENT SYSTEMS IN LABORATORIES ENGAGED IN ANALYSIS OF WATER Organization: ASTM
Date: 2011-11-15
Description: This guide provides information on consensus good laboratory practices for laboratories that provide services in the sampling and analysis of water.
ISO - ISO/IEC 25024 - SYSTEMS AND SOFTWARE ENGINEERING - SYSTEMS AND SOFTWARE QUALITY REQUIREMENTS AND EVALUATION (SQUARE) - MEASUREMENT OF DATA QUALITY - FIRST EDITION Organization: ISO
Date: 2015-10-15
Description: It can be applied in many types of information systems, for example, such as follows: — legacy information system; — data warehouse; — distributed information system; — cooperative information system; — world wide web.
DS/ISO/IEC 25051 - SOFTWARE ENGINEERING - SYSTEMS AND SOFTWARE QUALITY REQUIREMENTS AND EVALUATION (SQUARE) - REQUIREMENTS FOR QUALITY OF READY TO USE SOFTWARE PRODUCT (RUSP) AND INSTRUCTIONS FOR TESTING Organization: DS
Date: 2014-02-14
Description: The intended users of this International Standard include: a) suppliers when: 1) specifying requirements for a COTS software product; 2) assessing their own software products against the claimed performance; 3) issuing declarations of conformity (ISO/IEC 17050); 4) applying for certificates or marks of conformity (ISO/IEC Guide 23); b) certification bodies that may wish to establish a third-party certification scheme (international, regional or national) (ISO/IEC Guide 28); c) testing laboratories which will have to follow the instructions for testing when testing for a certificate or a mark of conformity (ISO/IEC 17025); d) accreditation bodies for accrediting registration or certification bodies and testing laboratories; e) potential acquirers who may: 1) compare the requirements for the intended work task with the information in product descriptions of existing software products; 2) look for certified COTS software product; 3) check if the requirements are otherwise met; f) end users who may profit from better software products; g) organizations: 1) establishing management and engineering environments based on the quality requirements and methods of this international standard; and 2) managing and improving their quality processes and personnel. h) regulatory authorities who may require or recommend the requirements of this International Standard for COTS software products used in safety or business-critical applications.
CLSI POCT01 - POINT-OF-CARE CONNECTIVITY; APPROVED STANDARD - SECOND EDITION; VOL 26; NO 28 Organization: CLSI
Date: 2006-07-01
Description: CLSI document POCT1 provides the framework for engineers to design devices, workstations, and interfaces that allow multiple types and brands of point-of-care devices to communicate bidirectionally with access points, data concentrators, and laboratory information systems from a variety of vendors. As an interface standard, this document specifies the common communication interfaces and protocols between systems and devices.
DSF/ISO/IEC DIS 25051 - SOFTWARE ENGINEERING - SOFTWARE PRODUCT QUALITY REQUIREMENTS AND EVALUATION (SQUARE) - REQUIREMENTS FOR QUALITY OF COMMERCIAL OFF-THE-SHELF (COTS) SOFTWARE PRODUCT AND INSTRUCTIONS FOR TESTING Organization: DS
Description: The intended users of this International Standard include: a) suppliers when: 1) specifying requirements for a COTS software product; 2) assessing their own software products against the claimed performance; 3) issuing declarations of conformity (ISO/IEC 17050); 4) applying for certificates or marks of conformity (ISO/IEC Guide 23); b) certification bodies that may wish to establish a third-party certification scheme (international, regional or national) (ISO/IEC Guide 28); c) testing laboratories which will have to follow the instructions for testing when testing for a certificate or a mark of conformity (ISO/IEC 17025); ISO/IEC 25051: REVISION (E) © ISO/IEC 20** - All rights reserved 2 d) accreditation bodies for accrediting registration or certification bodies and testing laboratories; e) potential acquirers who may: 1) compare the requirements for the intended work task with the information in product descriptions of existing software products; 2) look for certified COTS software product; 3) check if the requirements are otherwise met; f) end users who may profit from better software products; g) organizations: 1) establishing management and engineering environments based on the quality requirements and methods of this international standard; and 2) managing and improving their quality processes and personnel. h) regulatory authorities who may require or recommend the requirements of this International Standard for COTS software products used in safety or business-critical applications.
ASTM MNL20 - CORROSION TESTS AND STANDARDS: APPLICATION AND INTERPRETATION - 2ND EDITION Organization: ASTM
Date: 2005-01-01
Description: Since gtandards are universally recognized as an important tool in effective corrosion control management, this Manual not only provides information required to find and use proper standards in specific applications, it also includes a CD with almost 200 of the most widely used ASTM and NACE corrosion standards.
SAE AS6171 - TEST METHODS STANDARD; GENERAL REQUIREMENTS, SUSPECT/COUNTERFEIT, ELECTRICAL, ELECTRONIC, AND ELECTROMECHANICAL PARTS Organization: SAE
Date: 2016-10-01
Description: The requirements of this document supplement the requirements of a higher level quality standard (e.g., AS9100, AS9003, AS9120, ISO 9001) and other quality management system documents. They are not intended to stand alone, supersede, or cancel requirements found in other quality management system documents, or requirements imposed by contracting authorities This standard should be implemented when other risk mitigation methods for avoiding the use of SC EEE parts (e.g., acquiring all parts from Authorized Sources, redesigning the system, having obsolete parts emulated, etc.) are either unavailable or inadequate.

1 - 12 of 12 results