GB/T 16895.15-2002 建筑物电气装置 第5部分：电气设备的选择和安装 第523节：布线系统载流量
作者:标准资料网 时间:2024-05-15 04:53:52 浏览:9193
来源:标准资料网
基本信息
| 标准名称： | 建筑物电气装置 第5部分：电气设备的选择和安装 第523节：布线系统载流量 |
| 英文名称： | Electrical installations of buildings--Part 5:Seletion and erection of electrical equipment--Section 523:Current-carrying capacities in wiring systems |
| 中标分类： |
建材 >>
建筑构配件与设备 >>
建筑电器与防灾器材设备 |
| ICS分类： |
建筑材料和建筑物 >>
建筑物中的设施 >>
供电系统
|
| 发布部门： | 中华人民共和国国家质量监督检验检疫总局 |
| 发布日期： | 2002-02-28 |
| 实施日期： | 2003-03-01 |
| 首发日期： | 2002-02-28 |
| 作废日期： | 1900-01-01 |
| 主管部门： | 中国电器工业协会 |
| 提出单位： | 中国电器工业协会 |
| 归口单位： | 全国建筑物电气装置标准化技术委员会 |
| 起草单位： | 上海电缆研究所 |
| 出版社： | 中国标准出版社 |
| 出版日期： | 2003-03-01 |
| 页数： | 平装16开， 页数：44， 字数：83千字 |
适用范围
本标准的目的是在正常工作情况下，以电流持续期间产生的热效应为条件，为了导体和绝缘的合理寿命提供载流量。选择导体截面时未考虑电击防护（见GB 14821.1）、热效应保护（见GB 16895.2）、过电流保护（见GB 16895.5）、电压降（见GB 16895.6第525条）和导线相联设备端子上的温度限制（GB 16895.6第526条）。目前本标准仅适用于额定电压不超过交流1kV或直流1.5kV无铠装电缆和绝缘导体，不适用于铠装单芯电缆。
前言
没有内容
目录
没有内容
引用标准
没有内容
所属分类： 建材 建筑构配件与设备 建筑电器与防灾器材设备 建筑材料和建筑物 建筑物中的设施 供电系统
基本信息
| 标准名称： | 水产品中磺胺类药物残留量的测定 液相色谱法 |
| 发布部门： | 中华人民共和国农业部 |
| 发布日期： | 2007-12-18 |
| 实施日期： | 2008-03-01 |
| 首发日期： | |
| 作废日期： | |
| 出版日期： | 2008-03-01 |
适用范围
没有内容
前言
没有内容
目录
没有内容
引用标准
没有内容
所属分类： 农业 林业 畜牧 畜禽饲料与添加剂 农业 饲料
Product Code:SAE JA1002
Title:Software Reliability Program Standard
Issuing Committee:G-11 Rmsl Software Committee
Scope:In 1994, the SAE G-11 Reliability, Maintainability, Supportability and Logistics (RMSL) Divisionchartered a software committee, G-11SW, to create several software standards and guidance documents acrossthe RMSL spectrum, including a software reliability program standard. The committee was formed as a crosssection of international representatives from commercial industries and governments.The G-11SW committee has attempted to develop a standard that is consistent with a SAE G-11 system levelreliability program standard and augmented by necessary software-specific support information. The G-11SWcommittee believes this document reflects the best current commercial practices, and meets the objectives of theUnited States Department of Defense Acquisition Reform initiative. This document is performance based and isintended to be used by industries to address market demands for reliable software products that improve systemproductivity, time to market, and cost-effective implementation. As appropriate, governments may also referencethis document.Software has been recognized by SAE G-11 as an important system component that is not adequately addressedat the system level. Software requires interpretation and variations on RMSL methods used by hardware. Thisdocument relies on the simple concept of supplier-customer dialogue and partnership to define, meet, anddemonstrate assurance of software product reliability requirements. This document describes, within a Plan-Caseframework, what performance requirements are necessary. An accompanying implementation guide (SAEJA1003) sets forth current best practices for how to structure the Plan in terms of activities, tasks, and methods soas to achieve the requirements of this document and provide demonstration evidence of reliability achievement inthe form of a Case.Development of this document has required dedication by a few participants and extended review by a wideraudience of potential users. The professionalism of all these individuals and the support they received from theircompanies, governments, and other organizations is gratefully acknowledged.Abstract驴This SAE Standard defines a simple and flexible framework for the performance-based management ofa software reliability program. The principal mechanisms are termed the 驴Software Reliability Plan驴 and the驴Software Reliability Case.驴 The Plan and Case are general purpose management tools which are suitable for usein many fields of system engineering and will be observed throughout SAE RMSL program standards.The Plan and Case in combination provide a means of tracking progress, performance achievement, andsustainment of a reliability goal. The Plan and Case support the philosophy of early fault removal and continuedfault prevention throughout the software life-cycle. The Plan provides a forward view of intended reliabilityprocesses, activities, and performance requirements, while the Case provides evidence of software productreliability achievement as documented by quantitative and qualitative performance measures.
