IEEE RS Standards Status and Descriptions

Slides:



Advertisements
Similar presentations
ENTITIES FOR A UN SYSTEM EVALUATION FRAMEWORK 17th MEETING OF SENIOR FELLOWSHIP OFFICERS OF THE UNITED NATIONS SYSTEM AND HOST COUNTRY AGENCIES BY DAVIDE.
Advertisements

P1801 PAR Extension Motivation Address deferred issues Consider further UPF/CPF convergence SAIF integration and extension Continue to raise the abstraction.
 Capacity Development; National Systems / Global Fund Summary of the implementation capacities for National Programs and Global Fund Grants For HIV /TB.
1 The Role of the Revised IEEE Standard Dictionary of Measures of the Software Aspects of Dependability in Software Acquisition Dr. Norman F. Schneidewind.
Dr. Julian Lo Consulting Director ITIL v3 Expert
Software Engineering General Project Management Software Requirements
Jeju, 13 – 16 May 2013Standards for Shared ICT HIS – Smart Grid Karen Bartleson, President, IEEE Standards Association Document No: GSC17-PLEN-72 Source:
Oversight CHAPTER SIXTEEN Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
Introduction to ISO New and modified requirements.
Cybersecurity: Engineering a Secure Information Technology Organization, 1st Edition Chapter 7 Software Supporting Processes and Software Reuse.
NIST Special Publication Revision 1
ETICS2 All Hands Meeting VEGA GmbH INFSOM-RI Uwe Mueller-Wilm Palermo, Oct ETICS Service Management Framework Business Objectives and “Best.
08 October 2015 M. Ammar Mehdi Introduction to Human Resource Management & SSG-16 Actions 4 th Steering Committee on Competence of Human.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
The European Qualifications Framework for Lifelong Learning – Update on Recent Developments ReferNet Meeting 22 January 2009.
Over View of CENELC Standards for Signalling Applications
Lead Agency Viability Assessment Consistent with OPPAGA Report 04-65, DCF contracted with FMHI to assist in the design and implementation of a centralized.
Software Quality Assurance. Software Quality Software quality is defined as the quality that ensures customer satisfaction by offering all the customer.
Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.
by: Er. Manu Bansal Deptt of IT Software Quality Assurance.
Software Engineering Process - II 7.1 Unit 7: Quality Management Software Engineering Process - II.
Project: EaP countries cooperation for promoting quality assurance in higher education Maria Stratan European Institute for Political Studies of Moldova.
Software Engineering — Software Life Cycle Processes — Maintenance
Steve Griffith February 28th, 2017
Compliance with Technical Standards
Where We Are Now. Where We Are Now Project Oversight Project Oversight Oversight’s Purposes: A set of principles and processes to guide and improve.
DoD Template for Application of TLCSM and PBL
Physical Security Governance Model
Chapter 1 The Systems Development Environment
Software Project Configuration Management
The Components of Information Systems
Chapter 1 The Systems Development Environment
2012 Spring Simulation Interoperability Workshop
Herman Smith United Nations Statistics Division
Orientation for New Site Visitors
Software and Systems Integration
Chapter 1 The Systems Development Environment
ISO/IEC Software Testing
Path Operator Implementation Task Force
The International Plant Protection Convention
For Computer Society Internal Use Only
TechStambha PMP Certification Training
IEEE Std 1074: Standard for Software Lifecycle
UNIT V QUALITY SYSTEMS.
EOB Methodology Overview
Chapter 1 The Systems Development Environment
Need for ISO 9000 & other Q Systems Swamynathan.S.M AP/ECE/SNSCT
The Open Group Architecture Framework (TOGAF)
Chapter 1 The Systems Development Environment
BU IS GIG Chemical, Oil & Gas
© 2016, 2017 Change Healthcare Solutions, LLC. All Rights Reserved.
The Components of Information Systems
Cyber-security and IEC International Standards
Engineering Processes
Where We Are Now. Where We Are Now Project Oversight Project Oversight Oversight’s Purposes: A set of principles and processes to guide and improve.
Karen Bartleson, President, IEEE Standards Association
Focus Group Committee Chairs
Communication and Consultation with Interested Parties by the RB
CLINICAL INFORMATION SYSTEM
Relationship between MRLs and AS6500
Evaluation in the GEF and Training Module on Terminal Evaluations
Smart Grids activities in ETSI
NPA 450/579 (Area Code) Relief in Quebec
Project Lifecycle and IT Product Life Cycle
PSS verification and validation
Information System Building Blocks
Chapter 1 The Systems Development Environment
September, 2016 IEEE/HL7 Baltimore, USA
Technology Maintenance
Presentation transcript:

IEEE RS Standards Status and Descriptions Lou Gullo June 17, 2012

IEEE RS Status 5 Standards in Sustainment: IEEE 1624-2008 (Standard for Organizational Reliability Capability) IEEE 1633-2008 (Recommended Practice on Software Reliability) IEEE 1413-2010 (Standard for Reliability Predictions) IEEE P1332-1998 (Standard Reliability Program For The Development And Production Of Electronic Systems And Equipment ) IEEE P1413.1-2002 (IEEE Guide for Selection and Using Reliability Predictions Based on IEEE 1413TM ) 2 Standards in Development: IEEE/IEC P61014 (Standard for Reliability Growth Programs) IEEE P1856 (Standard Framework for Prognostics and Health Management of Electronic Systems)

IEEE 1624 Title: Standard for Organizational Reliability Capability Purpose: for assessing the reliability capability of an organization is to facilitate improvement of the product reliability. Scope: A standard which defines the reliability capability of organizations and identifies the criteria for assessing the reliability capability of an organization. This Standard can be used for self-assessment by organizations or for supplier/customer relationship development between members of supply chain. A method to identify the shortcomings in reliability programs which can be rectified by subsequent improvement actions

IEEE1633 Title: Recommended Practice on Software Reliability Purpose: promotes a systems approach to Software Reliability (SR) predictions and assessments Scope: This Recommended Practice revision reflects those advances in SR since 1992, including modeling and prediction for distributed and network systems. The methodologies and tools included in this Recommended Practice are extended over the software life cycle (SLC). Jointly development with AIAA Leverages CMU SEI CMM/CMMI

IEEE 1413 Title: Standard Framework for Reliability Prediction of Hardware Purpose: To identify the required elements for an understandable and useful reliability prediction. Scope: This standard provides the framework for performing and reporting reliability predictions. It applies to hardware products including electronic, electrical and mechanical devices and assemblies. A reliability prediction made according to this standard shall have sufficient information concerning inputs, assumptions, and uncertainty so the risk associated with using the prediction results can be understood.

Planning to complete by 2012 IEEE 1332 Title: Reliability Program for the Development and Production of Electronic Products Purpose: The purpose of this document is to establish a standard set of objectives which provide an effective structure for the life-cycle activities needed to design, manufacture and utilize reliable electronic products and systems across the supply chain. Scope: This document provides a standard set of reliability program objectives for use between customers and producers, or within product development teams, to express reliability program requirements early in the development phase of electronic Replacement for MIL-STD-785; similar to GEIA 0009 and SAE JA2000 New project (PAR) authorized in March 2008 Planning to complete by 2012

Planning to complete by 2012 IEEE 1413.1 Title: Guide for Developing and Assessing Reliability Predictions Based on IEEE Standard 1413 Purpose: The purpose of this guide is to assist in the selection, performance, and comparison of the various reliability prediction processes and methodologies, and prediction results and outputs complying with IEEE 1413 standard. Scope: The scope of this guide is to provide processes and methodologies for conducting and assessing reliability predictions for electronic systems or products. This Guide will facilitate the understanding of reliability prediction processes and methodologies, and help users to determine how to use the different processes and methodologies during the life cycle of systems and products. References MIL-HDBK-217 and other handbooks and methods PAR approved by NesCom on 26 March, 2008 Planning to complete by 2012

Planned for completion in 2014 IEEE/IEC 61014 Title: Standard for Reliability Growth Programs Recent emphasis by the DoD community placed on reliability growth The international community already has an existing standard that could be leveraged for IEEE use and suppliers to the DoD, without creating a new and redundant standard. Collaboration on a new joint IEEE/IEC standard for Reliability Growth based on existing International IEC standard 61014: IEC 61014: “Programmes for reliability growth”. A PAR (modified from IEEE P1467) was written for this new project, and approved by NesCom in 2010. Planned for completion in 2014

Planned for completion in 2016 PHM Standard (P1856) Title: Standard Framework for Prognostics and Health Management of Electronic Systems Purpose: to classify and define the concepts involved in prognostics and health management of electronic systems to provide a standard framework that assists practitioners in the development of business cases, and the selection of approaches, methodologies, algorithms, condition monitoring equipment, and strategies for implementing prognostics for electronic systems. Scope: Describes a normative framework for classifying PHM capability and for planning the development of PHM for a system or product. PAR approved by NesCom in 2012 Planned for completion in 2016 April 1, 2008

More than 360,000 members in ~150 countries IEEE Basics The IEEE creates consensus standards through an open process IEEE standards process has evolved over the past century. IEEE standards are dynamic documents designed to ensure products and services fit their purpose and perform as intended. IEEE standards clear the way to commercialize a technology, allowing for interoperability, rapid design, easy installation and testing, and protection for users and the environment. 41 societies, associations, councils and committees IEEE Standards Association is the IEEE standards development body More than 360,000 members in ~150 countries

IEEE-SA Develops More Standards Than Anyone Else Summary of IEEE-SA IEEE Standards Association (IEEE-SA) is the global standards generating organization composed of IEEE employees and IEEE/non-IEEE volunteers. Active portfolio of over 900 completed standards, recommended practices, and guides (all are called "standards"). More than 400 standards in development Consider joining IEEE, IEEE-RS and IEEE-SA to develop and sustain reliability standards IEEE-SA Develops More Standards Than Anyone Else

Questions