GB/T 3711-2008 酚类产品中性油及吡啶碱含量测定方法

作者:标准资料网 时间:2024-05-17 00:15:51   浏览:9035   来源:标准资料网
下载地址: 点击此处下载
基本信息
标准名称:酚类产品中性油及吡啶碱含量测定方法
英文名称:Method of determination for neutral oils and pyridine bases contents of phenol products
中标分类: 化工 >> 有机化工原料 >> 一般有机化工原料
ICS分类: 化工技术 >> 有机化学 >> 酚
替代情况:替代GB/T 3711-1983
发布部门:中华人民共和国国家质量监督检验检疫总局 中国国家标准化管理委员会
发布日期:1983-05-24
实施日期:2009-10-01
首发日期:1983-05-24
作废日期:
主管部门: 中国钢铁工业协会
提出单位:中国钢铁工业协会
归口单位: 全国钢标准化技术委员会
起草单位:鞍钢股份有限公司化工总厂、冶金工业信息标准研究院
起草人:关永毅、张明明、孙伟、于梅春、陆云
出版社:中国标准出版社
出版日期:2009-10-01
页数:12页
计划单号:20061208-T-605
适用范围

本标准规定了酚类产品中性油及吡啶碱含量的测定原理、仪器、采样、分析步骤、结果计算及精
密度。
本标准适用于煤焦油分馏所得的酚类产品中性油及吡啶碱含量的测定

前言

没有内容

目录

没有内容

引用标准

GB/T1999 焦化油类产品取样方法

所属分类: 化工 有机化工原料 一般有机化工原料 化工技术 有机化学 酚
下载地址: 点击此处下载
【英文标准名称】:Suctionrubberhosesforexcrementcars
【原文标准名称】:环境卫生车用抽吸橡胶软管
【标准号】:JISK6340-1982
【标准状态】:作废
【国别】:日本
【发布日期】:
【实施或试行日期】:
【发布单位】:日本工业标准调查会(JISC)
【起草单位】:Abolishment
【标准类型】:()
【标准水平】:()
【中文主题词】:吸入软管;柔性管;卫生设施
【英文主题词】:suctionhoses;;flexiblepipes
【摘要】:
【中国标准分类号】:G42
【国际标准分类号】:
【页数】:3P;A4
【正文语种】:日语


Product Code:SAE JA1002
Title:Software Reliability Program Standard
Issuing Committee:G-11 Rmsl Software Committee
Scope:Context-This SAE Standard provides a framework for the management of software reliability within system reliability requirements. It is based around the Software Reliability Plan and Software Reliability Case and emphasizes the importance of evaluating progress towards meeting software reliability requirements throughout the project life-cycle.Range of Application-This document can be applied to all projects that incorporate software. This includes the integration of Off the Shelf (OTS) software products and custom software. OTS software sources include commercial vendors, government, and industry (e.g., reused library software). Custom software is generally newly developed software or a significant rework/upgrade of existing software that is for use with a specific application.Rolesa. The Software Reliability Plan and the Software Reliability Case are intended to serve the needs of industry organizations in meeting software product reliability objectives.b. The Software Reliability Plan and the Software Reliability Case can be employed as deliverables contacted between a customer and a supplier. Additionally, the Software Reliability Plan and the Software Reliability Case can contribute to any proposal for development or production and should be requested in a Request for Proposal (RFP). c. A Software Reliability Case can be created or maintained to serve the needs of a support organization in sustaining reliability objectives. d. A Software Reliability Case can be used to supply the data needed by independent, regulatory, and/or third party certification bodies.Relationship to Management Plans-The Software Reliability Plan and the Software Reliability Case extend existing practices and may be integrated within other project management mechanisms provided that reliability progress is identifiable and traceable. Technical Guidance-This document does not describe or recommend software development practices. However, ty Case can be used to supply the data needed by independent, regulatory, and/or third party certification bodies.