4.8.1-General Requirements
《金属面夹芯板安装及验收规程》(征求意见稿)
CECS CECS XXX:20XX 中国工程建设协会标准建筑用金属面绝热夹芯板安装及验收规程Specification for installation and acceptance of double skin metal faced insulating panels for building(征求意见稿)中国XX出版社前言本规程是根据中国工程建设标准化协会（2000）建标协字第15号“关于印发《中国工程建设标准化协会2000年第一批推荐性标准制、修订计划》的通知要求，由国家住宅与居住环境工程技术研究中心和中国绝热节能材料协会会同有关单位共同编制的。
本规程包括总则、术语、材料、安装施工、施工安全与成品保护、工程验收等内容。
本规程由中国工程建设标准化协会建材分会归口管理，国家住宅与居住环境工程技术研究中心负责具体技术内容的解释。
请各使用单位在执行过程中认真总结经验，如发现需要修改和补充之处，请将意见和有关资料寄送国家住宅与居住环境工程技术研究中心（地址：北京市西城区车公庄大街19号，邮政编码：100044），以便今后修订时参考。
主编单位：国家住宅与居住环境工程技术研究中心中国绝热节能材料协会参编单位：主要起草人：主要审查人：目次1 总则 (1)2 术语 (2)3 材料 (3)3.1 夹芯板材料及质量要求 (3)3.2 紧固件辅件及密封材料质量要求 (3)４安装施工 (4)4.1 一般规定 (4)4.2 运输与存放 (4)4.3 施工准备 (4)4.4 墙体工程 (5)4.5 屋面工程 (5)4.6 采光工程 (6)4.7 雨蓬，挑蓬工程 (6)4.8 设备工程 (6)4.9 避雷针、避雷带工程 (7)5 施工安全与成品保护 (8)5.1 施工安全 (8)5.2 成品保护 (8)6工程验收 (9)6.1 一般规定 (9)6.2 工程验收 (10)本规范用词说明 (12)引用标准名录 (13)附：条文说明 (14)Contents1 General (1)2 Terms (2)3 Material (3)3.1 Sandwich panel Quality and Applications (3)3.2 Fasteners、accessories and sealing materials quality requirements (3)4 Installation (4)4.1 General requirements (4)4.2 Transport and storage (4)4.3 Construction preparation (4)4.4 Walling project (5)4.5 Roofing project (5)4.6 Lighting project (6)4.7 Awning, canopy project (6)4.8 Equipment project (6)4.9 Lightning rod, lightning protection zone project (7)5 Construction safety and product protection (8)5.1 Construction safety (8)5.2 Product protection (8)6 Project acceptance (9)6.1 General requirements (9)6.2 Project acceptance (10)Explanation of wording in this code (12)List of quoted standards (13)Addition: Explanation of provisions (14)1 总则1.0.1为了提高建筑用金属面绝热夹芯板（以下简称夹芯板）施工技术水平和统一验收依据，确保工程施工质量，做到技术先进，经济合理，安全适用。
Requirements_Definition
Requirements Definition How we should (attempt to) specify exactly what is needed before we start designing12Requirements DefinitionRequirements describe the necessary functions and features of the system we are to conceive, design,implement and operate.PerformanceScheduleCost Other Characteristics (e.g. lifecycle properties)Requirements are often organized hierarchically At a high level requirements focus on what should be achieved, not how to achieve itRequirements are specified at every level, from the overall system to each hardware and software component.Critically important to establish properly4Importance of TechnicalRequirements Development (2/2)Provides a baseline for verificationOrganizations can develop their validation and verification plans much more productively from a good requirements document.The requirements document provides a baseline against which compliance can be measured.The requirements are also used to provide the stakeholders with a basis for acceptance of thesystem.Facilitates transfer of the product tonew users or new machines. Serve as a basis for later enhancement or alteration of the finished product.MOE, MOP, TPMRelationship8Technical Requirements Definition Best Practice Process Flow DiagramActivitiesInputOutput910Requirements AllocationDecompose system requirements into lower levels of design.Define all the lower level functions which must be performed to satisfy the requirement Create architecture of sub-components to provide thosefunctionsAllocate a level of performance to each lower level functionSpecify interface requirements to other sub-systems Closure -Ensure that satisfaction of the set of requirements at the lower level will guarantee satisfaction of the higher level requirement .Requirements Analysis. The requirementsanalysis is this: First we determine thefunctions that must be accomplished for thesubsystem to meet its requirement. Then wecreate an architecture for the subsystem madeup of sub-components and define therequirements for each sub-component. Willthis set of requirements ensure satisfaction ofthe requirements at the higher level? Is the setboth necessary and sufficient? Then we iteratethe allocation of requirements to optimize thedesign. As we proceed down into therequirement/architecture tree, we may learnthat we need to revise an upper level of thearchitecture, using different subsystems orrequirement allocation to optimize the overalldesign.11Requirement Allocation Process.Requirements are always developed fromthe top down. We begin with the top-levelfunctional requirements and decompose itinto what is necessary to achieve itsfunctional capability. Then we specify whateach sub-component will have to do, howwell it will have to function to provide thatcapability. This process often includesnegotiation and balancing betweensubsystems to minimize the overall effort.13Sometimes it is necessary to push back onrequirements when the cost to achieve thestated capability is too great. We also prioritizerequirements when not all requirements can beachieved. The set of subsystems, togetherwith the requirements necessary and sufficientto guarantee the performance of the systemabove, is called an architecture. It is only onearchitecture of potentially many and may notbe optimum. We continue to iterate the designand apportionment of requirements to optimizethe design, maximizing some performancefactor or minimizing cost or schedule.1415VerificationEvery requirement must be verified to ensure that the proposed design actually satisfies the requirement byExamination, Test,Demonstration, orAnalysisRequirement documentation specifies the development phase and method of verification。
1.General_Requirements通用准则
AWS D1.1/D1.1M:2002Structural Welding Code — SteelAWS D1.1/D1.1M:2002 An American National StandardStructural Welding Code — SteelCOPYRIGHT 2003; American Welding Society, Inc. 00:02:09 MDT Questions or comments about this message: please call the DocumentDocument provided by IHS Licensee=Aramco HQ/9980755100, User=, 04/24/20031Policy Management Group at 1-800-451-1584.AWS D1.1/D1.1M:2002Structural Welding Code — SteelAWS D1.1/D1.1M:2002 An American National Standard Approved by American National Standards Institute August 31, 2001Structural Welding Code — Steel18th Edition Supersedes AWS D1.1:2002Prepared by AWS D1 Committee on Structural WeldingUnder the Direction of AWS Technical Activities CommitteeApproved by AWS Board of DirectorsAbstractThis code covers the welding requirements for any type of welded structure made from the commonly used carbon and low-alloy constructional steels. Sections 1 through 8 constitute a body of rules for the regulation of welding in steel construction. There are twelve mandatory and fifteen nonmandatory annexes in this code. A Commentary of the code is included with the document.550 N.W. LeJeune Road, Miami, Florida 33126COPYRIGHT 2003; American Welding Society, Inc. 00:02:09 MDT Questions or comments about this message: please call the DocumentDocument provided by IHS Licensee=Aramco HQ/9980755100, User=, 04/24/20032Policy Management Group at 1-800-451-1584.AWS D1.1/D1.1M:2002Structural Welding Code — Steel1 General Requirements 通用原则1.1 Scope 适用范围This code contains the requirements for fabricating and erecting welded steel structures. When this code is stipulated in contract documents, conformance with all provisions of the code shall be required, except for those provisions that the Engineer (see 1.4.1) or contract documents specifically modifies or exempts. 本规范包括制作和安装焊接钢结构的要求。
需求管理英文单词
需求管理英文单词
需求管理是一项重要的工作，需要掌握一定的英文单词和术语。
以下是一些常用的需求管理相关单词：
1. Requirement：需求
2. Specification：规格
3. Functional Requirement：功能需求
4. Non-Functional Requirement：非功能需求
5. User Story：用户故事
6. Use Case：用例
7. Acceptance Criteria：验收标准
8. Stakeholder：利益相关者
9. Business Analyst：业务分析师
10. Product Owner：产品负责人
11. Scope：范围
12. Change Request：变更请求
13. Traceability Matrix：追踪矩阵
14. Prioritization：优先级排序
15. Validation：验证
16. Verification：确认
17. Agile：敏捷的
18. Waterfall：瀑布的
19. Sprints：迭代周期
20. Backlog：待办事项列表
以上单词仅为需求管理中的部分词汇，请根据实际需求和场景学习和运用。
ISO9000英文版质量管理体系要求
NOTE In this International Standard,the term “product”applies only to the product intended for,or required by,a customer.
Quality management system - Requirement
4 Quality management system
4.1 General requirements The organization shall establish,document,implement and maintain a quality
management system and continually improve its effectiveness in accordance with the requirements of this International Standard.
Quality management system - Requirement
4.2 Documentation requirements
4.2.1 General The quality management system documentation shall include a) Documented statements of a quality policy and quality objectives, b) A quality manual, c) Documented procedures required by this International Standard, d) Documents needed by the organization to ensure the effective planning,and e) Records required by this International Standard(see 4.2.4)
ERTMS-ETCS需求规范 SUBSET-026-4 v330
4.1 Modification History4.2 Table of Contents4.1Modification History (2)4.2Table of Contents (5)4.3Introduction (7)4.3.1Presentation of the document (7)4.3.2Identification of the possible modes (7)4.4Definition of the modes (9)4.4.1Introduction (9)4.4.2General Requirements (9)4.4.3ISOLATION (10)4.4.4NO POWER (11)4.4.5SYSTEM FAILURE (12)4.4.6SLEEPING (13)4.4.7STAND BY (15)4.4.8SHUNTING (16)4.4.9FULL SUPERVISION (18)4.4.10UNFITTED (19)4.4.11STAFF RESPONSIBLE (20)4.4.12ON SIGHT (23)4.4.13TRIP (24)4.4.14POST TRIP (25)4.4.15NON LEADING (27)4.4.16Intentionally deleted (29)4.4.17National System (SN) mode (30)4.4.18REVERSING (31)4.4.19LIMITED SUPERVISION (33)4.4.20PASSIVE SHUNTING (34)4.5Modes and on-board functions (36)4.5.1Introduction (36)4.5.2Active Functions Table (36)4.6Transitions between modes (41)4.6.1Symbols (41)4.6.2Transitions Table (42)4.6.3Transitions Conditions Table (43)4.7DMI depending on modes (47)4.7.1Introduction (47)4.7.2DMI versus Mode Table (47)4.8Acceptance of received information (51)4.8.1Introduction (51)4.8.2Assumptions (53)4.8.3Accepted information depending on the level and transmission media (53)4.8.4Accepted Information depending on the modes (59)4.8.5Handling of transition buffer in case of level transition announcement or RBC/RBC handover (62)4.9What happens to accepted and stored information when entering a given level (65)4.9.1Introduction (65)4.10What happens to accepted and stored information when entering a given mode (66)4.10.1Introduction (66)4.11What happens to stored information when exiting NP mode (70)4.3 Introduction4.3.1 Presentation of the document4.3.1.1 This document defines the modes of the ERTMS/ETCS on-board equipment (seechapter 4.4 “Definition of the modes” and chapter 4.5 “Modes and on-board functions”.4.3.1.2 This document gives all transitions between modes (see chapter 4.6 “Transitionsbetween modes”).4.3.1.3 This document describes the possible exchanged information between the driver andthe ERTMS/ETCS on-board equipment, respect to the mode (see chapter 4.7 “DMIdepending on modes”).4.3.1.4 This document describes how the received information is filtered, respect to severalcriteria such as the level, the mode, etc.. (see chapter 4.8 “Acceptance of receivedinformation”).4.3.1.5 This document describes how the stored information is handled, respect to severalcriteria such as the level, the mode, etc. (see chapter 4.9 “What h appens to acceptedand stored information when entering a given level”, and chapter 4.10 “What happensto accepted and stored information when entering a given mode”).4.3.1.6 All the tables that are included in this document shall be considered as mandatoryrequirements.4.3.1.7 Some notes appear in this document. These notes are here to help the reader tounderstand the specifications, or to explain the reason(s) of a requirement.4.3.2 Identification of the possible modes4.3.2.1 List of the modes:Full Supervision (FS)Limited Supervision (LS)On Sight (OS)Staff Responsible (SR)Shunting (SH)Unfitted (UN)Passive Shunting (PS)Sleeping (SL)Stand By (SB)Trip (TR)Post Trip (PT) System Failure (SF) Isolation (IS) No Power (NP) Non Leading (NL) National System (SN) Reversing (RV)4.4 Definition of the modes4.4.1 Introduction4.4.1.1 For each mode the following information is given:a) The context of utilisation of the mode and the functions that characterise the mode(chapter “Description”).b) The ERTMS/ETCS levels in which the mode can be used (chapter “Used inlevels”).c) The related responsibility of the ERTMS/ETCS on-board equipment and of thedriver, once the equipment is in this mode (chapter “Responsibilities”).4.4.1.2 A complete list of transitions to and from each mode is given in the section 4.6.2“Transitions Table” ).4.4.2 General Requirements4.4.2.1 When the desk is open, a clear indication of the ERTMS/ETCS mode shall be shownto the driver.4.4.2.2 Intentionally deleted.4.4.3 ISOLATION4.4.3.1 Description4.4.3.1.1 In Isolation mode, the ERTMS/ETCS on-board equipment shall be physically isolatedfrom the brakes and can be isolated from other on-board equipments/systemsdepending on the specific on-board implementation.4.4.3.1.2 There shall be a clear indication to the driver that the ERTMS/ETCS on-boardequipment is isolated.4.4.3.1.3 To leave Isolation mode, a special operating procedure is needed (no transition fromIsolation is specified). This procedure shall ensure that the on-board equipment is onlyput back into service when it has been proven that this is safe for operation.4.4.3.1.4 Note: for the list of main functions related to this mode, refer to chapter 4.5 “Modesand on-board functions”.4.4.3.2 Used in levels4.4.3.2.1 Used in all levels: Level 0, level 1, level 2, level 3 and level NTC.4.4.3.3 Responsibilities4.4.3.3.1 Isolation of the ERTMS/ETCS on-board equipment is performed by the driver under hiscomplete responsibility.4.4.3.3.2 Once the ERTMS/ETCS on-board equipment is isolated, the ERTMS/ETCS on-boardequipment has no more responsibility.4.4.4 NO POWER4.4.4.1 Description4.4.4.1.1 When the ERTMS/ETCS on-board equipment is not powered, the equipment shall bein the No Power mode.4.4.4.1.1.1 Note: in order to ensure cold movement detection function, some parts of theERTMS/ETCS on-board equipment may be fed by an auxiliary power supply.4.4.4.1.2 The ERTMS/ETCS on-board equipment shall permanently command the emergencybrake.4.4.4.1.3 Note: for the list of main functions related to this mode, refer to chapter 4.5 “Modesand on-board functions”.4.4.4.2 Used in levels4.4.4.2.1 Used in all levels: Level 0, level 1, level 2, level 3 and level NTC.4.4.4.3 Responsibilities4.4.4.3.1 The ERTMS/ETCS on-board equipment has no responsibility in this mode, exceptcommanding the emergency brake and (optionally) monitoring cold movements.4.4.4.3.2 The notion of responsibility of the driver is not relevant for the No Power mode.4.4.4.3.3 If it is required to move a loco in NP mode as a wagon, ETCS brake command mustbe overridden by external means.4.4.5 SYSTEM FAILURE4.4.5.1 Description4.4.5.1.1 The ERTMS/ETCS on-board equipment shall switch to the System Failure mode incase of a fault, which affects safety.4.4.5.1.2 The ERTMS/ETCS on-board equipment shall permanently command the EmergencyBrakes.4.4.5.1.3 Note: for the list of main functions related to this mode, refer to chapter 4.5 “Modesand on-board functions”.4.4.5.2 Used in levels4.4.5.2.1 Used in all levels: Level 0, level 1, level 2, level 3 and level NTC.4.4.5.3 Responsibilities4.4.5.3.1 The ERTMS/ETCS on-board equipment is responsible for commanding theEmergency Brakes.4.4.5.3.2 No responsibility of the driver.4.4.6 SLEEPING4.4.6.1 Description4.4.6.1.1 The Sleeping mode is defined to manage the ERTMS/ETCS on-board equipment of aslave engine that is remote controlled.4.4.6.1.2 The desk(s) of a sleeping engine must be closed (since there is no driver, noinformation shall be shown).4.4.6.1.3 As the engine is remote controlled by the leading engine, its ERTMS/ETCS on-boardequipment shall not perform any train movement supervision.4.4.6.1.4 The ERTMS/ETCS on-board equipment shall perform the Train Position function; inparticular, the front/rear end of the engine (i.e., not the train) shall be used to refer totrain front/rear end.4.4.6.1.5 Sleeping mode shall be automatically detected on-board via the train interface.4.4.6.1.6 If possible, the train must not be stopped due to a safety critical fault in a sleepingengine. The ERTMS/ETCS on-board equipment shall therefore try to memorise theoccurrence of such fault(s), which shall be handled when the engine leaves theSleeping mode. The ERTMS/ETCS on-board equipment shall also try to send an errorinformation to the RBC.4.4.6.1.7 If a desk of the sleeping engine is opened while the train is running (this is anabnormal operation), the ERTMS/ETCS on-board equipment shall switch to Stand-Bymode.4.4.6.1.8 If the “sleeping input signal” is lost (no more detection of the remote control), theswitch to Stand-By mode shall be made only if the train is at standstill.4.4.6.1.9 Intentionally deleted.4.4.6.1.10 The ERTMS/ETCS on-board equipment shall open a communication session with theRBC when at least one of the following events occurs:a) in all levels, on receipt of the order to contact the RBC.b) In level 2/3, when entering or exiting Sleeping mode (to report the change of modeto the RBC).c) In level 2/3, when a safety critical fault of the ERTMS/ETCS on-board equipmentoccurs (to report the fault to the RBC).4.4.6.1.11 Note: for the list of main functions related to this mode, refer to chapter 4.5 “Mod esand on-board functions”.4.4.6.1.12 In case of balise group message consistency error (refer to 3.16.2.4.4 and 3.16.2.5.1),the ERTMS/ETCS onboard equipment shall not command the service brake.4.4.6.1.13 When in levels 2 or 3, if no compatible version has been established between the on-board equipment in Sleeping mode and the RBC, the ERTMS/ETCS onboardequipment shall react as specified in 3.5.3.8 b) but no driver‟s indication shall be given.4.4.6.2 Used in levels4.4.6.2.1 Used in all levels: Level 0, level 1, level 2, level 3 and level NTC.4.4.6.3 Responsibilities4.4.6.3.1 The ERTMS/ETCS on-board equipment of an engine in Sleeping mode has noresponsibility for the train protection.4.4.6.3.2 The notion of responsibility of the driver is not relevant for the Sleeping mode.4.4.6.3.2.1 Note:The leading engine is responsible for the movement of the train. It is then theERTMS/ETCS on-board equipment of the leading engine that is fully/partially/notresponsible for the train protection, with respect to its mode.4.4.7 STAND BY4.4.7.1 Description4.4.7.1.1 The Stand-By mode is a default mode and cannot be selected by the driver.4.4.7.1.2 It is in the Stand-By mode that the ERTMS/ETCS on-board equipment awakes.4.4.7.1.3 Data for mission shall be collected in Stand-By (see SRS-chapter 5: “Start of Mission”procedure).4.4.7.1.4 In Stand-By mode, the desk of the engine can be open or closed. No interaction withthe driver shall be possible as long as the desk is closed, except isolation of theERTMS/ETCS on-board equipment.4.4.7.1.5 The ERTMS/ETCS on-board equipment shall perform the Standstill Supervision.4.4.7.1.6 Note: for the list of main functions related to this mode, refer to chapter 4.5 “Modesand on-board functions”.4.4.7.2 Used in levels4.4.7.2.1 Used in all levels: Level 0, level 1, level 2, level 3 and level NTC.4.4.7.3 Responsibilities4.4.7.3.1 The ERTMS/ETCS on-board equipment is responsible for maintaining the train atstandstill.4.4.7.3.2 The driver has no responsibility for train movements.4.4.8 SHUNTING4.4.8.1 Description4.4.8.1.1 The purpose of the Shunting mode is to enable shunting movements. In Shuntingmode, The ERTMS/ETCS on-board equipment supervises the train movementsagainst:a) a ceiling speed: the shunting mode speed limitb) a list of expected balise groups (if such list was sent by the trackside equipment).The train shall be tripped if a balise group, not contained in the list, is passed(When an empty list is sent, no balise group can be passed. When no list is sent,all balise groups can be passed)c) “stop if in shunting mode” information. The train is tripped if such information isreceived from balise groupsd) Intentionally deleted4.4.8.1.2 The Shunting mode shall not require Train Data.4.4.8.1.3 The ERTMS/ETCS on-board equipment shall perform the Train Position function4.4.8.1.4 Intentionally deleted.4.4.8.1.5 When in Shunting mode, the ERTMS/ETCS on-board shall not manage leveltransitions. However, an immediate level transition order or a conditional leveltransition order shall be stored and evaluated only when another mode than Shuntingor Passive Shunting has been entered (i.e. when the Shunting movement isterminated).4.4.8.1.5.1 When receiving a communication session establishment order, the ERTMS/ETCS on-board in Shunting mode shall not establish the communication session, but shall storethe RBC ID/phone number.4.4.8.1.5.2 When in Shunting mode, the ERTMS/ETCS on-board shall not manage RBC-RBChand-over, except for storing the RBC ID/phone number given at the RBC/RBC border.4.4.8.1.6 Shunting mode can be selected by the driver, only accepted when the train is atstandstill, or ordered by the trackside.4.4.8.1.7 In case of selection of Shunting mode by the driver:∙in level 1 operations, the switch to shunting is always accepted by the on-board equipment∙in level 2 and 3 areas, the on-board shall ask the trackside for an authorisation. The switch to shunting is possible only after receiving such authorisation. The tracksidecan send a list of balises, that the train is allowed to pass while in SH, together withthe authorisation4.4.8.1.8 In case of order to switch to Shunting mode from trackside, the order:∙in level 1 is given by a balise group. A list of balises, that the train is allowed to pass after the entry in Shunting, can be sent together with the order∙in level 2 and 3 is sent via radio. A list of balises, that the train is allowed to pass after the entry in Shunting, can be sent together with the order4.4.8.1.9 When the switch to shunting is ordered by trackside, a driver acknowledgement isrequested.4.4.8.1.9.1 Note: in Shunting mode the train is only partially supervised, therefore it is necessarythat the driver takes the responsibility.4.4.8.1.10 The ERTMS/ETCS on-board equipment shall display the train speed and, only ondriver request, the permitted speed. The display of the permitted speed shall also bestopped on driver request.4.4.8.1.11 Intentionally deleted.4.4.8.1.12 Note: for the list of main functions related to this mode, refer to chapter 4.5 “Modesand on-board functions”.4.4.8.2 Used in levels4.4.8.2.1 Used in level 0, NTC, 1, 2 and 3.4.4.8.3 Responsibilities4.4.8.3.1 The ERTMS/ETCS on-board equipment is responsible for the supervision of theshunting mode speed limit, and that the engine with the active antenna is tripped whenpassing the defined border of the shunting area (only if there is a defined border:balise group not in the list given by trackside, or balise group giving the information“stop if in shunting”).4.4.8.3.2 The driver is responsible for:a) Remaining inside the shunting area defined by a procedure or an external systemoutside ERTMS/ETCS (also when the shunting area is protected by balises)b) Train/engine movements and shunting operations4.4.9 FULL SUPERVISION4.4.9.1 Description4.4.9.1.1 The ERTMS/ETCS on-board equipment shall be in the Full Supervision mode when alltrain and track data, which is required for a complete supervision of the train, isavailable on board.4.4.9.1.2 Full supervision cannot be selected by the driver, but shall be entered automaticallywhen all necessary conditions are fulfilled.4.4.9.1.3 To be in Full Supervision mode, SSP and gradient are not required for the wholelength of the train, but shall be at least available from the FRONT END of the train.4.4.9.1.4 Once in Full Supervision mode, if SSP and gradient are not known for the whole lengthof the train, an indication “ENTRY IN FULL SUPERVISION” shall be clearly displayedto the driver until SSP and gradient are known for the whole length of the train.4.4.9.1.4.1 Note: this indication may also be displayed in case the train length has been increased,see 3.18.3.8.4.4.9.1.5 The ERTMS/ETCS on-board equipment shall supervise train movements against adynamic speed profile.4.4.9.1.6 The ERTMS/ETCS on-board equipment shall display the train speed, the permittedspeed, the target distance and the target speed to the driver (this list is not exhaustive– refer to chapter 4.7 “DMI depending on modes”).4.4.9.1.7 Note: for the list of main functions related to this mode, refer to chapter 4.5 “Modesand on-board functions”.4.4.9.2 Used in levels4.4.9.2.1 Used in level 1, 2 and 3.4.4.9.3 Responsibilities4.4.9.3.1 The ERTMS/ETCS on-board equipment is fully responsible for the train protection(except for the 2 situations described below).4.4.9.3.2 The driver is responsible for respecting the EOA when approaching an EOA with arelease speed.4.4.9.3.3 When “ENTRY IN FULL SUPERVISION” is displayed to the driver, the driver isresponsible for respecting speed restrictions that apply for the part of the train that isnot covered by SSP and gradient data.4.4.10 UNFITTED4.4.10.1 Description4.4.10.1.1 The Unfitted mode is used to allow train movements in either:a) Areas that are equipped neither with ERTMS/ETCS track-side equipment nor withnational train control systemb) Intentionally deletedc) Areas that are equipped with ERTMS/ETCS trackside equipment and/or nationaltrain control system(s), but operation under their supervision is currently notpossible4.4.10.1.2 The ERTMS/ETCS on-board equipment shall supervise train movements against aceiling speed: the lowest of the maximum train speed and the Unfitted mode speedlimit for unfitted area (national value).4.4.10.1.2.1 Intentionally deleted.4.4.10.1.3 The ERTMS/ETCS on-board equipment shall also supervise temporary speedrestrictions.4.4.10.1.4 The ERTMS/ETCS on-board equipment shall display the train speed to the driver.4.4.10.1.5 Note: for the list of main functions related to this mode, refer to chapter 4.5 “Modesand on-board functions”.4.4.10.2 Used in levels4.4.10.2.1 Used in level 0.4.4.10.3 Responsibilities4.4.10.3.1 The ERTMS/ETCS on-board equipment supervises a ceiling speed and (if available)temporary speed restrictions.4.4.10.3.2 The driver must respect the existing line-side signals and is fully responsible for trainmovements.4.4.11 STAFF RESPONSIBLE4.4.11.1 Description4.4.11.1.1 The Staff Responsible mode allows the driver to move the train under his ownresponsibility in an ERTMS/ETCS equipped area.4.4.11.1.2 This mode is used when the system does not know the route. For example:a) After the ERTMS/ETCS on-board equipment starts-up (awakening of the train).b) To pass a signal at danger / override an EOA.c) After a trackside failure (for example: loss of radio contact).4.4.11.1.3 The ERTMS/ETCS on-board equipment shall supervise train movements against:a) a ceiling speed: the staff responsible mode speed limitb) a given distance (regarding its origin location see 4.4.11.1.3.1). The ERTMS/ETCSon-board equipment shall supervise braking curves with a target speed of zero tothe end of this distance. If the train overpasses this distance (see next note) theERTMS/ETCS on-board equipment shall trip the trainc) a list of expected balise groups, if this list has been sent by the RBC. The trainshall be tripped if over-passing a balise group that is not in the list. (When anempty list is sent, no balise group can be passed. When no list is sent, all balisegroups can be passed)d) balise groups giving the order …stop if in SR‟. This order shall immediately trip thetrain, unless the over-passed balise group is included in a list of expected balisesas defined in item c)e) running in the direction opposite to the train orientation (reverse movementprotection)4.4.11.1.3.1 The ERTMS/ETCS on-board shall determine the start location of the SR distanceas follows:a) If the National/Default value determines the max permitted distance to run in SRmode, the starting point of this distance shall refer to the estimated position of thetrain front when SR mode was entered, or, already in Staff Responsible mode,when Override was activated.b) If the max permitted distance to run in SR mode is determined by the valuetransmitted by the RBC, or entered by the driver, the start location of the distanceshall refer to the estimated position of the train front when the distance informationis received or entered.c) If the max permitted distance to run in SR mode is determined by the valuetransmitted by EUROLOOP, the distance information transmitted by EUROLOOPshall be referred to one or more reference balise groups. On-board shall evaluatethe distance to run in SR mode by matching the reference balise groups given withthe LRBG.In case the LRBG is, due to a change of orientation, in front of the train when thedistance to run in SR mode is to be determined from the EUROLOOP information,the complete distance to run in SR mode shall be determined as the distancegiven by EUROLOOP plus the distance between the estimated train front end andthe LRBG.4.4.11.1.4 Note: Since the gradient is unknown, the supervision of the braking curves in StaffResponsible mode does not ensure that the train will not pass the given distance.4.4.11.1.5 The ERTMS/ETCS on-board equipment shall give the possibility to the driver to modifythe value of the SR mode speed limit and of the given distance. This shall be possibleonly at standstill.4.4.11.1.5.1 If a train movement is detected while the driver is entering the SR speed/distancelimits, the ERTMS/ETCS on-board equipment shall trigger the brake command.4.4.11.1.6 In level 2/3, the driver shall have the possibility to request a new distance to run inStaff Responsible, by selecting "Start". This triggers an MA request.4.4.11.1.6.1 Note: Once the SR distance is covered, the driver may have to go further.4.4.11.1.6.2 When entering SR mode, the value applicable for SR mode speed limit and thevalue applicable for SR distance shall be the corresponding National/Default values.Exception for SR distance: SR mode is authorised by RBC giving an SR distance.4.4.11.1.6.3 While in SR mode, the value applicable for the SR mode speed limit shall be, ifavailable, the last value entered by the driver.4.4.11.1.6.4 While in SR mode, the value applicable for the SR distance shall be, if available,the last value received by the ERTMS/ETCS on-board equipment amongst:a) the distance to run in SR entered by the driver;b) the distance to run in SR given by trackside.4.4.11.1.6.5 When "Override" is selected, the SR mode speed limit value and the SR distancevalue previously entered by driver or given by trackside, if any, shall be deleted. Thecorresponding National/Default values shall enter in force.4.4.11.1.6.6 If the train is in SR and receives a new distance to run in SR mode from theRBC, the stored list of expected balise groups, if any, shall be deleted or shall bereplaced by the list of expected balise groups sent together with the distance to run inSR.4.4.11.1.6.7 If an ERTMS/ETCS on-board equipment in SR mode, after having received fromEUROLOOP max permitted distance to run in SR mode information, detects the mainsignal balise group being part of this information then it shall ignore any new maxpermitted distance to run in SR mode information from that loop.4.4.11.1.7 The ERTMS/ETCS on-board equipment shall display the train speed and the (whenactive) override (permission to pass a signal at danger, trip inhibited). The permittedspeed, target distance and the target speed shall be displayed only on driver request,until the driver requests to stop their display.4.4.11.1.8 Intentionally deleted.4.4.11.1.9 If receiving a "track ahead free" request from the RBC, the ERTMS/ETCS on-boardequipment requests the driver to enter the "track ahead free" information.4.4.11.1.10 Note: for the list of main functions related to this mode, refer to chapter 4.5 “Mo desand on-board functions”.4.4.11.1.11 Intentionally deleted.4.4.11.2 Used in levels4.4.11.2.1 Level 1, 2 and 3.4.4.11.3 Responsibilities4.4.11.3.1 The ERTMS/ETCS on-board equipment supervises a ceiling speed and a SR distanceif finite (and if level 2/3, might also supervise a list of balises).4.4.11.3.2 The driver must check if the track is free, if points are correctly positioned, and mustrespect the existing line-side information (signals, speed boards etc.).4.4.11.3.3 When using the possibility to modify the value of the SR mode speed limit and of thegiven distance, the driver is responsible for entering reasonable values.4.4.12 ON SIGHT4.4.12.1 Description4.4.12.1.1 The On Sight mode enables the train to enter into a track section that could be alreadyoccupied by another train, or obstructed by any kind of obstacle.4.4.12.1.2 On Sight mode cannot be selected by the driver, but shall be entered automaticallywhen commanded by trackside and all necessary conditions are fulfilled.4.4.12.1.3 The ERTMS/ETCS on-board equipment shall supervise train movements against adynamic speed profile.4.4.12.1.4 The ERTMS/ETCS on-board equipment shall display the train speed to the driver (thislist is not exhaustive). The permitted speed, target distance,target speed and releasespeed (if any) shall be displayed only on driver request, until the driver requests to stoptheir display.4.4.12.1.5 If receiving a "track ahead free" request from the RBC, the ERTMS/ETCS on-boardequipment requests the driver to enter the "track ahead free" information.4.4.12.1.6 To be in On Sight mode, SSP and gradient are not required for the whole length of thetrain, but shall be at least available from the FRONT END of the train.4.4.12.1.7 Once in On Sight mode, if SSP and gradient are not known for the whole length of thetrain, an indication “ENTRY IN ON SIGHT” shall be clearly displayed to the driver untilSSP and gradient are known for the whole length of the train.4.4.12.1.7.1 Note: this indication may also be displayed in case the train length has beenincreased, see 3.18.3.8.4.4.12.1.8 Deleted4.4.12.1.9 Note: for the list of main functions related to this mode, refer to chapter 4.5 “Modesand on-board functio ns”.4.4.12.2 Used in levels4.4.12.2.1 Used in level 1, 2 and 3.4.4.12.3 Responsibilities4.4.12.3.1 The ERTMS/ETCS on-board equipment is responsible for the supervision of the trainmovements.4.4.12.3.2 The driver is responsible for checking the track occupancy when moving the train,because the track may be occupied.4.4.13 TRIP4.4.13.1 Description4.4.13.1.1 Deleted4.4.13.1.1.1 Note: Application of emergency brakes and train trip are two different things. Forexample, exceeding the permitted speed leads to application of the emergency brakes,but as long as the train does not pass the EOA, it is not a train trip.4.4.13.1.2 The ERTMS/ETCS on-board equipment shall command the emergency brakes (nobrake release is possible in Trip mode).4.4.13.1.3 The ERTMS/ETCS on-board equipment shall indicate to the driver the reason of thetrain trip.4.4.13.1.4 The ERTMS/ETCS on-board equipment shall request an acknowledgement from thedriver once train is at standstill (to allow the driver to acknowledge the train trip).4.4.13.1.4.1 Note: This acknowledgement is mandatory to exit from Trip mode.4.4.13.1.5 Note: for the list of main functions related to this mode, refer to chapter 4.5 “Modesand on-board functions”.4.4.13.1.6 Closing the desk while being in Trip mode will not cause a mode change but nointeraction with the driver shall be possible as long as the desk is closed, exceptisolation of the ERTMS/ETCS on-board equipment4.4.13.2 Used in levels4.4.13.2.1 Used in level 0, NTC, 1, 2 and 3.4.4.13.3 Responsibilities4.4.13.3.1 The ERTMS/ETCS on-board equipment is responsible for stopping the train and formaintaining the train at standstill.4.4.13.3.2 The driver has no responsibility for train movements.。
EN71-1(
12
4. 一般要求
4.10.4 弹簧
下列弹簧必须不可触及: - 螺旋状弹簧旳两个螺线之间旳空隙不小于3mm时 - 拉伸弹簧在40N拉力作用下，两相邻弹簧间距离不小于3mm - 压力弹簧处于静止时，相邻两弹簧之间距离不小于3mm，且
玩具使用时能承受不小于40N
进行如下测试时，不能倒塌，分开成几部分或锁定装置失效。 － 主副锁定装置均作用时，100kg负载向下作用于方向杆5分钟 － 仅副锁定装置作用时，50kg负载向下作用于方向杆5分钟 － 滑板车倒放于支撑架上，主副锁定装置均作用时，悬挂50kg 负载于方向杆上5分钟
25
4. 一般要求
4.15.5.4 可调整高度及可折叠旳操纵杆：
2) 软性投射物为 0.5J
弓和箭 (必须符合要求)
- 出售旳带有箭旳弓在本原则中作为玩具看待。其潜在危险性应按照
7.7旳要求加以阐明
Warning! Do not aim at eyes or face.
30
4. 一般要求
4.18 水上玩具
- 气塞应与玩具阀相连。 - 终止阀必须能被推动玩具，使其距玩具表面不超出 5mm。 - 扭力拉力试验后，终止阀应不能完全溶入小部件筒内。 - 应提醒使用者注意使用水上玩具旳潜在危险。
3
4. 一般要求
4.1 材料 4.2 装配
所用原材料需要清洁卫生。
供组装旳玩具必须附有详细旳组装阐明。 供成年人组装旳玩具必须有明确旳阐明。
4
4. 一般要求
4.3 柔韧旳塑料薄膜
面积不小于100mm x 100mm旳薄膜，须 A) 平均厚度不能少于0.038mm B) 若少于0.038mm，则须在任意30mm x 30mm面积内 至少有1%面积旳孔以作呼吸。 C) 对于塑料气球， 在不充气或不破坏气球旳情况下,双层塑料薄膜
质量管理系统Requirements手册
Quality Excellence for Suppliers ofTelecommunications Forum(QuEST Forum)TL 9000Quality Management System Requirements HandbookRelease 3.0CopyrightCopyright _ __ _ 2001 Quality Excellence for Suppliers of Telecommunications ForumFor further information,see the QuEST Forum web site at:TL 9000 is a registered trademarkof theQuality for Excellence for Suppliers of Telecommunications Forum.Sections of this document contain copyrighted material from a variety of sources; these sources areidentified in the Bibliography of this handbook.The text highlighted in the boxes throughout this document is a verbatim reproduction of ISO 9001:2000.This text is copyrighted by the International Organization for Standardization. Not for resale. No part ofthis standard may be copied or reproduced in any form, including an electronic retrieval system, withoutthe prior written permission of the American National Standards Institute, Inc., 11 West 42 nd Street, NewYork, NY 10036, which holds reproduction rights in the United States.Approved and Adoptedby theQuEST ForumEffectiveMarch 31, 2001TL 9000 Quality Management System Requirements Handbook 3.0IiForeword ForewordThe TL 9000 Quality Management System Requirements Handbook wasprepared in a cooperative effort by the members of the Quality Excellence forSuppliers of Telecommunications (QuEST) Forum. From the outset the QuESTForum’s goal has been to develop and maintain a consistent set of qualitysystem requirements and measurements that, when implemented, will helpprovide telecommunications customers with faster, better and more cost-effectiveservices.This book complements the TL 9000 Quality Management SystemMeasurements Handbook with requirements that support Telecommunicationsindustry service providers and their suppliers’ commitment to meeting theexpectations of their customers.The QuEST Forum is pleased to present this book in a common spirit ofdelighting our customers.George C. Via, Verizon Olga Striltschuk, MotorolaQuEST Forum – Chairman QuEST Forum – Vice ChairSteven Welch, SBC Barry D’Amour, Nortel NetworksDon Pickens, Bell South Jerry Cates, CorningWilliam Wessman, Boston Karl-Heinz Augenstein, AlcatelCommunications GroupMarty Lustig, SPRINT Masahide Sekiguchi, FujitsuSignature on FileIsabelle Courville, Bell Canada Monica Garcia, ComplasTL 9000 Quality Management System Requirements Handbook 3.0iiiPreface PrefaceThe Quality Excellence for Suppliers of Telecommunications Forum (QuESTForum) was founded to foster continued improvements to the quality andreliability of telecommunications service. The founders took the critical initial stepof establishing a common set of quality management system requirements andmeasurements by creating the TL 9000 Quality Management SystemRequirements Handbook and the TL 9000 Quality Management SystemMeasurements Handboo k. These handbooks are the result of a cooperativeeffort among members of the telecommunications industry.The work of the QuEST Forum yields benefits to customers, their subscribers,and their suppliers. Membership is composed of telecommunication ServiceProviders, Suppliers, and Liaisons. Members fund and participate in the QuESTForum, have defined voting rights and are expected to contribute to the work ofthe QuEST Forum. Members vote on adoption of the TL 9000 structure, content,administration, and other questions coming before the QuEST Forum.The QuEST Forum establishes and maintains a common set of qualitymanagement system requirements and measurements built on currently usedindustry standards, including ISO 9001:2000. The requirements andmeasurements promote consistency and efficiency, reduce redundancy andimprove customer satisfaction. They also enable suppliers to improve qualityand reliability, reduce costs, and increase competitiveness.TL 9000 Quality Management System Requirements Handbook 3.0IvAcknowledgementsAcknowledgementsThe strength of the QuEST Forum is the outstanding capabilities andcommitment of the members who represent their respective organizations at theQuEST Forum and Work Group Meetings. This exceptional talent produced thefirst TL 9000 Quality Management System Requirements Handbook in recordtime and now has completed this major update in less than eighteen months.Individuals whose companies were customers, suppliers, and competitorsaccomplished the update of the Requirements handbook through extraordinaryteamwork.This outstanding accomplishment was facilitated in partnership with the AmericanSociety of Quality (ASQ) and The University of Texas at Dallas (UTD). Specialthanks for their constant support and encouragement during the last three yearsof our development to Dr. Bill Osborne, Dean and Dr. Douglas E. Harris,Associate Dean, Erik Jonsson School of Engineering and Computer Science andto Paul Borawski, ASQ Executive Director and Brian LeHouillier, ASQ Director,Programs & Operations.Personally, and for the entire QuEST Forum, I would like to thank the followingQuEST Forum individuals and companies of the Requirements and Oversightwork groups for their direct contributions to this update of the TL 9000 QualityManagement System Requirements Handboo k.Jack PompeoQuEST Forum Project DirectorRequirements Work GroupLeaders: Chair Brendan Pelan VerizonVice-Chair(2000) Debbie Hearn TelcordiaVice-Chair(1999) Matt Lindsay Tellabs Operations, Inc.Secretary Tama McBride MotorolaTime Keeper Jeffrey Rose Sumitomo Electric LightwaveSME(2000) Richard Morrow The University of Texas at DallasSME(1999) Bob Brigham TelcordiaContributors:3M Telecom Systems Advanced Fibre AlcatelThierno Diallo Communications Chandan BanerjeeADTRAN Mark Hodges Ian MackieCharles O'Donnell Rhonda Sator Mark MooreMike RippeTom YoheTL 9000 Quality Management System Requirements Handbook 3.0v AcknowledgementsRob LindnerBob LichkayBill TaylorAstec Advanced PowerSystemsAndre LapointeAT&TKathy ParkerMichael ServerBell CanadaJean-Normand DrouinJean-Pierre QuoibionBellSouthTelecommunicationsTex PraterJoel SullivanBritish TelecommunicationsSteve DickensCharles IndustriesAngelo DiMonteVictor PotentChatsworth ProductsEdward GaickiCommWorksLaura CoplonJim OatesDavid StahlComverse Network SystemsBruce RozettElizabeth TracyCorningSteve CooperLen YoungEntelaRalph StoweEricssonVictor SandovalExcel PartnershipSteve ObolewiczDave SanicolaTL 9000 Quality Management System Requirements Handbook 3.0vi AcknowledgementsAcknowledgementsOversight Work GroupLeaders: Chair Joe Taylor Tellabs OperationsVice-Chair Ron Basque ComplasSecretary Kim Hauswirth American Society for QualityContributors:ADC TelecommunicationsRandy PezonADTRANRandal WhortonAlcatelDave Aiken Ron LuttrullAmerican Society for QualityKim HauswirthBritish Standards Institution (BSI)Ky WhiteComplasRon BasqueThe QuEST Forum benefits from the continued and dedicated service of many individuals working towards the goals of the QuEST Forum. Without these individuals and their company’s support, the QuEST Forum would not besuccessful in ensuring that the quality of telecommunication services to the end-userkeep pace with changing technological opportunities in the twenty-first century.A Board of Directors guides the QuEST Forum activities through a strategic plan, which is implemented by work groups. The Requirements and Oversight work groups are credited for producing this document and they would like to recognize the individuals and companies that participated in the other work groups for providing invaluable service in support of the overall QuEST Forum Mission.Business Excellence Acceleration Model (BEAM) Work GroupLeaders: Chair Gene Hutchison SBCVice-Chair Mary Hattrick Marconi Vice-Chair Don Brown AlcatelSecretary/SME Tom Withey The University of Texas at DallasContributors: Agilent Technologies John Murray Alcatel Don Brown Ian MackieTL 9000 Quality Management System Requirements Handbook 3.0viiAcknowledgementsAcknowledgementsCorningSteve Cooper Len YoungExcel Partnership David MiddletonFlextronicsJohnny Hancock FujitsuAshok DandekarGlenayre Technologies Deborah BrighamGovernance Work GroupLeaders: Co-Chair Jim McDonnell SBCCo-Chair Len Young CorningContributors:AlcatelRon LuttrullCorningLen YoungECI TelecomMisha PtakMarketing and Communications (Marcom) Work GroupLeaders: Chair Jack Pompeo TeleCentric Vice-Chair Ashok Dandekar FujitsuContributors: ADC Telecommunications Jerry Lefever Randy Pezon ADTRAN Randal Whorton Alcatel Dave Aitken Ron LuttrullTL 9000 Quality Management System Requirements Handbook 3.0viiiAcknowledgementsMeasurements Work GroupLeaders: Chair Rick Werth SBCVice-Chair Matt Lindsay Tellabs Operations Secretary ohn Walz Lucent TechnologiesTime Keeper Jeffery Rose Sumitomo Electric LightwaveContributors:ADTRANCharles O’DonnellAdvanced FibreCommunicationsMark FischerMark HodgesRhonda SatorAlcatelBob CicelskiJim KoPeter LoewJune MillerSteven QuigleyTab RabalaoTom YoheAntecBob LichkayRob LindnerAstec Advanced PowerSystemsRoger DaunaisAndre LapointeAT&TKathy ParkerMichael ServerBell CanadaJean-Normand DrouinBellSouthTelecommunicationsEd BallingtonMort BurnettTex PraterBoston CommunicationsGroupTareq RahmanBritish TelecommunicationsSteve DickensCelestica CorporationPaul PettingerCharles IndustriesAngelo DiMonteVictor PotentCommWorksJames OatesComverse Network SystemsBruce RozettElizabeth TracyTL 9000 Quality Management System Requirements Handbook 3.0ix AcknowledgementsSupply Chain Work GroupLeaders: Chair David Briggs KARLEEVice-Chair Greg Lilly Nortel NetworksContributors: Array ArrayActernaAndrzej KozakADCJerry Lefever Soundar RajanAgilent Technologies Brent Wahl Alcatel Phil DudleyArtesyn Technologies Scott Ireland Michael Sullivan AT&TMike ServerAtlanta Cable Sales Bryan Glutting BellSouthTelecommunications Joel SullivanBookham Technology Nick Whiteley Celestica Paul Pettinger Complas Fred Denny Corning Joel Reece Leonard Young ECI Telecom Misha PtakTraining Work GroupLeaders: Chair Rosemarie Moskow SBCVice-Chair Jeff Harpe Nortel NetworksContributors: CTDI Jim McCormick Excel Partnership Joe DeCarlo Steve Obolewicz Donna LockeTL 9000 Quality Management System Requirements Handbook 3.0XTable of Contents 目录表Table of Contents 目录表SECTION 1 INTRODUCTION 1-1 第一部分 简介SECTION 2 STRUCTURE 2-1 第二部分 结构SECTION 3 TL 9000 ADMINISTRATION 3-1 第三部分 TL 9000管理SECTION 4 QUALITY MANAGEMENT SYSTEM 4-1第四部分 质量管理体系4.1 GENERAL REQUIREMENTS 4-1一般要求4.2 DOCUMENTATION REQUIREMENTS 4-24.2 文件要求SECTION 5 MANAGEMENT RESPONSIBILITY 5-1第五部分管理责任5.1 MANAGEMENT COMMITMENT 5-1管理义务5.2 CUSTOMER FOCUS 5-1客户中心5.3 QUALITY POLICY 5-2质量方针5.4 PLANNING 5-2计划5.5 RESPONSIBILIT Y, AUTHORITY AND COMMUNICATION 5-3责任，权力和联系5.6 MANAGEMENT REVIEW 5-4管理评论SECTION 6 RESOURCE MANAGEMENT 6-1第六部分资源管理6.1 PROVISION OF RESOURCES 6-1资源供应6.2 HUMAN RESOURCE 6-1人力资源6.3 INFRASTRUCTURE 6-2基础组织6.4 WORK ENVIRONMENT 6-2工作环境SECTION 7 PRODUCT REALIZATION 7-1第七部分产品实现7.1 PLANNING OF PRODUCT REALIZATION 7-1产品实现的计划7.2 CUSTOME R-RELATED PROCESSES 7-3相关客户程序7.3 DESIGN AND DEVELOPMENT 7-5设计和开发7.4 PURCHASING 7-10采购7.5 PRODUCTION AND SERVICE PROVISION 7-12生产和服务供应7.6 CONTROL OF MONITORING AND MEASURING DEVICES 7-16监测设备的控制SECTION 8 MEASUREMENT, ANALYSIS AND IMPROVEMENT 8-1第八部分测量，分析和改进8.1 GENERAL 8-1总述8.2 MONITORING AND MEASUREMENT 8-1监测8.3 CONTROL OF NONCONFORMING PRODUCT 8-4不合格品控制8.4 ANALYSIS OF DATA 8-5数据分析8.5 IMPROVEMENT 8-5改进TL 9000 Quality Management System Requirements Handbook 3.0TL 9000质量管理体系要求手册3.0xiTable of Contents目录表APPENDIX A TL 9000 ACCREDITATION BODY IMPLEMENTATION REQUIREMENTS A-1附录A TL 9000合格部分实施要求APPENDIX B CODE OF PRACTICE FOR TL 9000 REGISTRARS B-1附录B TL 9000注册代码APPENDIX C REGISTRATION GUIDANCE C-1附录C 注册指南APPENDIX D MIGRATION PATH, AUDIT DAYS, AND REQUIREMENTS ORIGIN D-1附录D 转移路线，审核日期和要求来源APPENDIX E ALTERNATIVE METHOD FOR MAINTAINING附录E 维修选择方法TL 9000 CERTIFICATION/REGISTRATION E-1TL 9000 证明/注册 E-1APPENDIX F GUIDANCE FOR COMMUNICATION WITH CUSTOMERS F-1附录F 与客户联系指南 F-1APPENDIX G QUALIFICATIONS AND EXPERIENCE REQUIREMENTSFOR TL 9000 REGISTRAR AUDITORS G-1附录G TL 9000注册审核员的资格和经验要求 G-1GLOSSARY 1术语表 1BIBLIOGRAPHY AND ENDNOTE REFERENCE 1参考书目和尾注参考1List of Figures图目录FIGURE 2.1-1 THE TL 9000 MODEL...............................................................2-1图2.1－1 TL 9000模型FIGURE 3.4-1 THE TL 9000 LOGO.................................................................3-2图3.4－1 TL 9000标识语FIGURE E-1 ALTERNATIVE ACCREDITATION PROCESS ...................... E-1图E－1 选择性的鉴定过程FIGURE E-2 INTERNAL AUDITS................................................................... E-2图E－2 内审List of Tables表目录TABLE 3.2-1 REGISTRATION REQUIREMENTS表3.2－1 注册要求BY SPECIALITY AREA............................................................3-2专业领域TL 9000 Quality Management System Requirements Handbook 3.0TL 9000质量管理体系要求手册3.0xii Section 1 – Introduction第一部分－简介Section 1 Introduction第一部分简介The TL 9000 handbooks (TL 9000 Quality Management System Requirements Handbook and TL9000 Quality Management System Measurements Handboo k) are designed specifically for thetelecommunications industry to document industry quality management system requirements andmeasurements.The TL 9000 Quality Management System Requirements Handbook establishes a common set ofquality management system requirements for suppliers of telecommunications products:hardware, software, and services. The requirements are built on existing industry standards,including ISO 9001. The TL 9000 Quality Management System Measurements Handbook definesa minimum set of performance measurements. The measurements are selected to measureprogress and evaluate results of quality management system implementation.TL 9000手册（TL9000质量管理体系要求手册和TL 9000质量管理衡量手册）是专为通讯工业设计的，使其工业质量管理体系要求和衡量文件化。
EN62366
EN62366EN 62366:2008 C hecklist/检查表Medical devicesApplication of usability engineering to medical devices可用性工程于医疗器械的应用Report Reference No/编号. ............ :版本号：验证人：Date of issue/发布日期:Test item description/项目............. :Model/Type reference/型号 .............. :Abbreviations used in the report/缩写：- Usability Engineering/可用性工程: UE - Risk analysis/风险分析: RA - User interface/用户界面: UI - Risk management/风险管理: RM - Primary operating function/主要操作功能: POFGeneral product information/产品描述:版本修改记录：日期版本说明验证人审批人IEC 62366 checklistClause 条款Requirement要求Remark解释Verdict判定4 GENERAL REQUIREMENTS/总要求4.1 General Requirements/总要求4.1.1 U SABILITY E NGINEERING P ROCESS/可用性工程过程Has the MANUFACTURER established, documentedand maintained a USABILITY ENGINEERING PROCESS to provide S AFETY for the PATIENT, USER and others related to USABILITY for the product?制造商是否建立、记录并维持了一个可用性工程过程，以确保患者、用户和其它涉及产品适用性的人的安全?Does the P ROCESS address USER INTERA ctions with the MEDICAL DEVICE according to the ACCOMPANYING DOCUMENT including, but not limited to transport, storage, installation, operation, maintenance, repair and disposal?该过程是否用于解决用户按随机文件与医疗器械的交互，如运输、存储、安装、操作、维护、维修和废弃？4.1.2Are R ESIDUAL R ISKS associated with U SABILITY of the MEDICAL D EVICE presumed to be acceptable, unless there is OBJECTIVE EVIDENCE to the contrary and documented?关系医疗器械可用性的剩余风险是否推定可接受？4.1.3 MANUFACTURER SHALL subject the information for safety used as a RISK CONTROL to the USABILITY ENGINEERING PROCESS (e.g., warnings or limitationof use in the ACCOMPANYING DOCUMENTS, marking, etc.).对于做为风险控制措施的安全信息，制造商应把它纳入可用性工程过程的控制Disregarding such information for SAFETY is considered beyond any further reasonable means of RISK CONTROL忽视安全信息的行为应被认为是超出风险控制措施的（即非正常使用）4.2The results of the USABILITY ENGINEERING PROCESSare recorded in the USABILITY ENGINEERING FILE可用性工程过程的结果记录于可用性工程文档。
欧盟GMP附录1计算机系统中英文对照
.EUROPEAN COMMISSION欧盟委员会HEALTH AND CONSUMERS DIRECTORATE-GENERAL卫生与消费者协会Public Health and Risk Assessment公共卫生与风险评估Pharmaceuticals药品Brussels,SANCO/C8/AM/sl/ares(2010)1064599EudraLexThe Rules Governing Medicinal Products in the European Union 欧盟药品生产规范Volume 4卷4Good Manufacturing PracticeMedicinal Products for Human and Veterinary Use人用与兽用药品良好生产管理规范Annex 11: Computerised Systems附件11：计算机系统Legal basis for publishing the detailed guidelines: Article 47 of Directive2001/83/EC on the Community code relating to medicinal products for human use and Article 51 of Directive 2001/82/EC on the Community code relating to veterinary medicinal products. This document provides guidance for the interpretation of the principles and guidelines of good manufacturing practice (GMP) for medicinal products as laid down in Directive 2003/94/EC for medicinal products for human use and Directive 91/412/EEC for veterinary use.依法发布的具体指导方针：2001/83/EC第47条人用药品规范和2001/82/EC第51条兽用药品规范。
DL 5009.1-2014 电力建设安全工作规程 第1部分： 火力发电 (1)
DL 5009.1 — 2014前言本规程根据《国家能源局关于下达2011 年第二批能源领域行业标准制（修）订计划的通知》（国能科技〔2011〕252 号）的要求，由电力行业火电建设标准化技术委员会负责，会同有关单位在DL 5009.1—2002《电力建设安全工作规程第1 部分：火力发电厂》基础上修订的。
DL 5009《电力建设安全工作规程》共3 个部分：— DL 5009.1第1 部分：火力发电— DL 5009.2第2 部分：电力线路— DL 5009.3第3 部分：变电站本部分是DL 5009 的第 1 部分：火力发电。
本部分共分7 章和6 个附录，主要内容是：1 总则、2 术语、3 基本规定、4 综合管理、5 土建、6 安装、7 调整试验及试运行。
本部分除1总则、2术语、3基本规定、4.1 基础管理和附录等条文为推荐性外，其余均为强制性。
本部分修订的主要内容：1.对整体章节结构重新进行了编排，新增“1 总则”、“2 术语”、“3 基本规定”、“4 综合管理”、“7 调整试验及试运行”章节，“4 综合管理”中“4.1 基础管理”、“4.2 安全防护设施和劳动防护用品”、“4.4 环境影响与节能减排”、“4.6 特种设备”“4.8.11 承重平台”、“4.10.3 受限空间作业”、“4.10.4 邻近带电体作业”、“4.14.2 防腐”等内容。
将原规程“3 施工现场”和“5 文明施工”的内容合并到“4.3 文明施工”，原规程“8 高处作业及交叉作业”并入“4.10 高风险作业”，原规程“19 砖石砌体及装饰工程”拆分为“5.8 砖石砌体”和“5.9 装饰装修”，IDL 5009.1 — 2014原规程“18.1 预应力混凝土工程”并入“5.6 混凝土结构”中，原规程“27 电气设备安装”、“28 母线安装”、“29 电缆”、“30 热控设备安装”合并到“6.3 电气和热控安装”。
其他内容均在原规程基础上作了修订。
DL 5009.1- 电力建设安全工作规程 第1部分： 火力发电 (1)之欧阳德创编
2021.03.07前言本规程根据《国家能源局关于下达 2011 年第二批能源领域行业标准制（修）订计划的通知》（国能科技〔2011〕252 号）的要求，由电力行业火电建设标准化技术委员会负责，会同有关单位在 DL 5009.1—2002《电力建欧阳德创编2021.03.072021.03.07设安全工作规程第 1 部分：火力发电厂》基础上修订的。
DL 5009《电力建设安全工作规程》共3个部分：— DL 5009.1 第 1 部分：火力发电— DL 5009.2 第 2 部分：电力线路— DL 5009.3 第 3 部分：变电站本部分是 DL 5009 的第 1 部分：火力发电。
欧阳德创编2021.03.072021.03.07本部分共分7 章和6个附录，主要内容是：1 总则、2 术语、3 基本规定、4 综合管理、5 土建、6 安装、7 调整试验及试运行。
本部分除1总则、2术语、3基本规定、4.1 基础管理和附录等条文为推荐性外，其余均为强制性。
本部分修订的主要内容：欧阳德创编2021.03.072021.03.071.对整体章节结构重新进行了编排，新增“1 总则”、“2 术语”、“3 基本规定”、“4 综合管理”、“7 调整试验及试运行”章节，“4 综合管理”中“4.1 基础管理”、“4.2 安全防护设施和劳动防护用品”、“4.4 环境影响与节能减排”、“4.6 特种设备”“4.8.11 承重平台”、“4.10.3 受限空间作业”、“4.10.4 邻近带电体作业”、欧阳德创编2021.03.072021.03.07“4.14.2 防腐”等内容。
将原规程“3 施工现场”和“5 文明施工”的内容合并到“4.3 文明施工”，原规程“8 高处作业及交叉作业”并入“4.10 高风险作业”，原规程“19 砖石砌体及装饰工程”拆分为“5.8 砖石砌体”和“5.9 装饰装修”，原规程“18.1 预应力混凝土工程”并入“5.6 混凝土结构”中，原规程“27 电气设备安装”、“28母线安欧阳德创编2021.03.072021.03.07 装”、“29 电缆”、“30 热控设备安装”合并到“6.3 电气和热控安装”。
F16飞行员培训手册1
BY ORDER OF THE SECRETARY OF THE AIR FORCE AIR FORCE INSTRUCTION 11-2F-16,VOLUME 119 JANUARY 2007Flying OperationsF-16--PILOT TRAININGCOMPLIANCE WITH THIS PUBLICATION IS MANDATORY ACCESSIBILITY:Publications and forms are available on the e-Publishing website at for downloading or ordering. RELEASABILITY: There are no releasability restrictions on this publication.OPR:HQ ACC/A3TO Certified by:HQ USAF/A3O(Maj Gen David E. Clary) Supersedes AFI11-2F-16V1, 8 August 2002 Pages:85 This volume implements AFPD 11-2, Aircraft Rules and Procedures; AFPD 11-4, Aviation Service; and AFI 11-202V1, Aircrew Training. It establishes the minimum Air Force standards for training and quali-fying personnel performing duties in the F-16 A/B/C/D. This publication applies to the Air National Guard and US Air Force Reserve. Selected paragraphs of this publication do not apply to all Air Force units. When an exception exists to the requirements of a paragraph, the exception is indicated in a paren-thetical within the paragraph, or by using subparagraphs directed at specific units. MAJCOMs/DRUs/ FOAs are to forward proposed MAJCOM/DRU/FOA-level supplements to this volume to HQ USAF/ A3OT, through HQ ACC/A3TO, for approval prior to publication IAW AFPD 11-2, paragraph 4.2. Cop-ies of MAJCOM/DRU/FOA-level supplements, after approved and published, will be provided by the issuing MAJCOM/DRU/FOA to HQ USAF/A3OT, HQ ACC/A3TO, and the user MAJCOM/DRU/FOA and NGB offices of primary responsibility. Field units below MAJCOM/DRU/FOA level will forward copies of their supplements to this publication to their parent MAJCOM/DRU/FOA office of primary responsibility for post publication review. NOTE: The terms Direct Reporting Unit (DRU) and Field Operating Agency (FOA) as used in this paragraph refer only to those DRUs/FOAs that report directly to HQ USAF. Keep supplements current by complying with AFI 33-360V1, paragraph 3.66 (periodic review). See paragraph 1.3. for guidance on submitting comments and suggesting improvements to this publication.This instruction requires the collection or maintenance of information protected by the Privacy Act of 1974. The authority to collect and maintain the records prescribed in this instruction are 37 USC 301a, Incentive Pay; Public Law 92-204 (Appropriations Act for 1973), Section 715; Public Law 93-570 (Appropriations Act for 1974); Public Law 93-294 (Aviation Career Incentive Act of 1974); DOD Instruction 7730.57, Aviation Career Incentive Act and Required Annual Report; AFI 11-401, Aviation Management; and E.O. 9397. System of records notice F011 AF XO A, Aviation Resource Management (ARMS), applies. Ensure that all records created as a result of processes prescribed in this publication are maintained in accordance with AFMAN 37-123, Management of Records (will convert to AFMAN33-363), and disposed of in accordance with the Air Force Records Disposition Schedule (RDS), located at https:///.NOTE:This instruction contains references to the following field (subordinate level) publications and forms which, until converted to departmental level publications and forms, may be obtained from the respective MAJCOM publication distribution office:Publications: AFTTP 3-1, ACCI 11-464, (MAJCOM) 11-301NOTE:MAJCOM-specific guidance is embedded within the text and prefaced with the MAJCOM acronym.SUMMARY OF CHANGESThis publication contains significant changes. Of note, this revision aligns RAP training with AEF cycle; Table 4.1. Ground Training Cycle Requirements and Table 4.2. Basic Skills (formerly NON-RAP) Cycle Training Requirements are removed and replaced with tables in the RAP Tasking memorandum; numer-ous changes to the currency table; redefines strafe minimums; removes Maverick upgrade and several other excessive Chp 6 upgrade programs; removes most paragraphs with specific MAJCOM instructions; makes guidance more directive where required; and updates office symbols with the A-staff designation. Chapter 1— GENERAL GUIDANCE 51.1.Abbreviations, Acronyms, and Terms (5)1.2.Responsibilities: (5)1.3.Processing Changes: (7)1.4.Training (7)1.5.Training Concepts and Policies: (9)1.6.Ready Aircrew Program Policy and Management: (10)1.7.Training Sortie Program Development: (11)Table 1.1.F-16 RAP Lookback Requirements. (11)1.8.Training Records and Reports (12)1.9.Pilot Utilization Policy: (12)1.10.Sortie Allocation Guidance: (13)1.11.Waiver Authority: (13)Chapter 2— INITIAL QUALIFICATION TRAINING 142.1.General (14)2.2.Approval/Waiver for IQT (14)2.3.Prerequisites (14)2.5.Flying Training: (14)2.6.IQT for Senior Officers: (15)Chapter 3— MISSION QUALIFICATION TRAINING 163.1.General (16)3.2.Ground Training: (16)3.3.Simulator Training: (16)3.4.Flying Training (17)3.5.Initial Aircrew Chemical Defense Training (ACDT) (18)3.6.Flight Surgeon (FS) and Ground Liaison Officer (GLO) Training: (19)Chapter 4— CONTINUATION TRAINING 204.1.General (20)4.2.Ground Training (20)4.3.Flying Training (22)4.4.Special Categories: (23)4.5.Multiple Qualification/Currency: (24)4.6.Currencies/Recurrencies/Requalifications: (25)Table 4.1.F-16 Pilot Currencies. (26)4.7.Regression: (29)4.8.End of Cycle Requirements (30)4.9.Proration of End-of-Cycle Requirements (30)Table 4.2.Proration Allowance. (31)4.10.Regaining CMR/BMC Status: (33)4.11.Example of the Lookback, Regression, Proration, and Requalification Process: (33)Figure 4.1.Regression Flow Chart. (34)4.12.Instrument Training (34)4.13.G-Awareness Continuation Training (35)Chapter 5— WEAPONS EMPLOYMENT QUALIFICATION 365.1.General (36)5.2.Initial qualification (36)5.3.CT qualification (36)5.5.Weapons Employment Parameters (37)5.6.Full Scale Inert/Live Ordnance (39)Chapter 6— SPECIALIZED TRAINING 406.1.Specialized Training Programs (40)6.2.Flight Lead (FL) Upgrade (40)6.3.Instructor Pilot (IP) Upgrade (43)6.4.Mission Commander (MC) Upgrade (45)6.5.Simulator Instructor (SI) (46)6.6.Targeting Pod (TGP): (47)6.7.Night Vision Goggle (NVG) Qualification Program: (48)6.8.Forward Air Controller (Airborne) (FAC(A)) Upgrade (50)6.9.Suppression of Enemy Air Defenses (SEAD) Upgrade (55)6.10.Joint Helmet Mounted Cueing System (JHMCS) Qualification Training (56)6.11.Alert Camera (57)6.12.Low Altitude Step-Down Training (LASDT) (57)Table 6.1.LOWAT Categories. (58)6.13.Armed Tactical Reconnaissance (60)6.14.F-16 Block Differences Training (60)6.15.Contingency/Exercise Spin-Up Training (61)6.16.Forms adopted or prescribed (62)Attachment 1— GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION 63 Attachment 2— GLOSSARY OF MISSION/SORTIE AND EVENT DEFINITIONS 79Chapter 1GENERAL GUIDANCE1.1. Abbreviations, Acronyms, and Terms. See Attachment 1.1.2. Responsibilities:1.2.1. HQ ACC/A3 is designated as the responsible agency for this volume IAW AFPD 11-2, AircraftRules and Procedures. HQ ACC/A3 will:1.2.1.1. Chair semiannual ACC Realistic Training Review Boards (RTRBs) to review ground andflying training requirements/programs for CAF units. RTRB participants will include applicable ACC active and reserve component representatives. MAJCOM/A3s with major weapons systems for which ACC is lead command will be invited to send representatives and/or inputs.1.2.1.2. Process all change requests.1.2.2. All user Major Commands (MAJCOMs) will:1.2.2.1. Determine training requirements to meet expected unit tasking.1.2.2.2. Submit MAJCOM supplements to HQ USAF/A3OT, through HQ ACC/A3TO, forapproval before publication. Provide HQ USAF/A3OT, HQ ACC/A3TO, and all applicable MAJ-COM/A3s a copy of their supplements after publication.1.2.2.3. Review subordinate unit supplemental instructions and supplemental training programsannually.1.2.3. Direct Reporting Units (DRUs) will:1.2.3.1. Provide standard instructional texts to support operational weapons/tactics training. For-ward copies to each MAJCOM, NAF/A3, and to each CAF wing/group.1.2.3.2. Review, update, and distribute changes to instructional texts annually.1.2.3.3. Review subordinate unit training programs annually.1.2.4. Wings/Groups will:1.2.4.1. Develop programs to ensure training objectives are met. Assist subordinate units in man-agement of training programs, ensure programs meet unit needs, and provide necessary staff sup-port. ACC wings/groups will also assist ANG and AFRC unit training programs as required/ requested IAW the AFRC unit advisory support program.1.2.4.2. Attach API-6/8 flyers to a flying squadron.1.2.4.3. Except when otherwise mandated, designate the training level to which each API – 6(ARC: all flyers) will train. Upon request provide MAJCOM/A3T (ANG: ACC/A3G, AFRC: ACC/A3U) with a list of Basic Mission Capable (BMC) and Combat Mission Ready (CMR) man-ning positions. Review programs and manning position designations annually.1.2.4.4. Forward supplements of this volume and Wing syllabi to MAJCOM/A3T for review eachtraining cycle, or upon significant changes (ANG: to ACC/A3G, AFRC: to ACC/A3U upon request). Review supplements each training cycle.1.2.5. Squadron supervisor (ARC: Appropriate operations supervisor) will:1.2.5.1. Ensure adequate continuity and supervision of individual training needs, experience, andproficiencies of assigned/attached pilots.1.2.5.2. Review training and evaluation records of newly-assigned pilots and those completingformal training to determine the training required for them to achieve BMC or CMR and to ensure provisions of this instruction have been met.1.2.5.3. Orient Ready Aircrew Program (RAP) missions to develop combat skills or practice tac-tical employment relevant to expected unit tasking. Provide guidance to ensure only effective RAP missions are logged. See Attachment 2 for RAP mission definitions.1.2.5.4. Review qualifications and training requirements of FS/GLO and determine appropriateflight restrictions.1.2.5.5. Determine missions/events in which individual BMC pilots will maintain qualificationversus familiarization.1.2.5.6. Determine utilization of BMC pilots.1.2.5.7. Determine how many and which BMC and CMR pilots will carry special capabilities/qualifications.1.2.5.8. Identify the levels of supervision required to accomplish the required training, unless spe-cifically directed.1.2.5.9. Assist the wing/group in developing the unit training programs.1.2.5.10. Monitor individual assigned/attached pilot currencies and requirements.1.2.5.11. Ensure pilots only participate in missions, events, and tasks for which they are ade-quately prepared, trained, and current.1.2.5.12. Squadrons will submit a training report to MAJCOM/A3T (ANG: ACC/A3G) every 4thmonth during the training cycle (always at the end of Jan, May, Sep for all). Squadrons may sub-mit an out of cycle report at anytime if Higher Headquarters (HHQ) assistance is required to pre-pare for Designed Operational Capability (DOC) or AEF tasking. Reports will consist of: 1) an email memo summarizing results or unresolved issues since the last report, current training plan summary, and significant shortfalls/Limiting Factors (LIMFACS) affecting training. 2) A filled out squadron training health slide (attachment to email memo) summarizing critical training issues. Both items IAW the guidance and examples at the web site https:///A3t/ A3TO/Fighter/FighterTeam.asp . Reports will reflect on different phases of training unique to each AEF pair. Key reports are the Post-AEF (end of the 1st month after AEF Vulnerability (Vul) period) and the Pre-AEF 4 months prior to AEF Vul period, others are snapshots of a squadron’s training health. Report only significant shortfalls/LIMFACS of events/missions that affect 15% or greater of the squadron’s pilot force. Include possible solutions or specific assistance required if able. HQ ACC will attempt to rectify or minimize noted shortfalls/LIMFACS while the training cycle is under way. Other MAJCOMs submit training reports IAW RAP Tasking Memo.1.2.5.12.1. Shortfalls occur when required mission training tasks are not accomplished due toshortages of equipment, munitions, etc. Example: unable to accomplish actual weapons release due to a shortage of training weapons.1.2.5.12.2. LIMFACS are factors, constraints, restrictions, etc. that degrade training effective-ness. Example: squadron's ability to accomplish actual weapons release is limited due to thelack of ranges that allow aircraft to drop munitions. This may include support hardware andsoftware.1.2.5.12.3. All deviations from these training requirements, after proration, will be summa-rized and reported to ACC/A3T (ANG: ACC/A3G) with the Post-AEF training report (end ofthe 1st month after AEF Vul period) IAW paragraph 1.2.5.12. above. This includes require-ments waived by OG/CC. Email training reports to ACC/A3TO RAP program manager ataccdoto.rapreporting@ , DSN 574-8323 (ANG: Email training reports toaccdog.rapreporting@ ). Contact ACC/A3TO F-16 Functional Area Manager(FAM) DSN 574-4099. Other MAJCOMs submit training reports IAW RAP Tasking Memo.1.2.6. Individual pilots will:1.2.6.1. Hand carry all available training records, gradebook, and Flight Evaluation Folders toassist the gaining unit in assessing qualifications and training requirements.1.2.6.2. Complete training requirements and currencies within the guidelines of this instruction.1.2.6.3. Participate only in ground and flying activities for which they are qualified, current, andprepared.1.3. Processing Changes:1.3.1. Forward recommendations for change to this volume to MAJCOM/A3 on AF IMT 847, Rec-ommendation for Change of Publication.1.3.2. MAJCOMs will forward approved recommendations to HQ ACC/A3.1.3.3. HQ ACC/A3 will:1.3.3.1. Coordinate all changes to the basic instruction with all MAJCOM/A3s.1.3.3.2. Process recommendation for change after approval by HQ USAF/A3/5.1.3.3.3. Address time sensitive changes by immediate action message.1.3.3.4. MAJCOM/A3 (ANG: ACC/A3G) will determine training requirements for subordinateunits. AFI changes will be issued via revision, Interim Change (IC), or Administrative Change (AC) to this publication. Due to dynamic requirements of Combatant Commanders, training requirements and currencies may be altered regularly. These training requirement and currency adjustments may be made via RAP Tasking Memorandum. HQ ACC/A3 will include MAJCOM supplemental guidance in the next publication of the AFI.1.4. Training.Training programs are designed to progress pilots from Initial Qualification Training (IQT) (B-Course or Transition/Requalification Training [TX]), then to Mission Qualification Training (MQT), and finally to Continuation Training (CT).1.4.1. IQT provides the training necessary to initially qualify pilots in a basic position and flyingduties without regard to a unit's mission. Upon completion of IQT, the pilots attain Basic Aircraft Qualification (BAQ) status. BAQ is a prerequisite for MQT. Except for General Officers above winglevel, BAQ is not a long term qualification status. Waiver authority for pilots, other than general offic-ers above the wing level, to remain BAQ is MAJCOM/A3 (ANG: ACC/A3G).1.4.2. MQT provides the training necessary to initially qualify or requalify pilots in a specific position and flying duties to perform the missions assigned to a specific unit. Pilots maintain BAQ status until they complete MQT. Completion of MQT or FTU instructor course is a prerequisite for BMC and CMR.1.4.3. CT. There are two aspects of CT. The first consists of pilot training in the basic flying skills contained in the RAP Tasking Memo (RTM). These skills ensure safe operation of the aircraft. The second consists of specific mission-related training required to accomplish the unit's assigned mis-sions.1.4.4. Ready Aircrew Program (RAP). The CT program is designed to focus training on capabili-ties needed to accomplish a unit's core tasked missions. Following completion of IQT and MQT, pilots will have received training in all the basic missions of a specific unit unless excepted in Chapter 3. Pilots will then be assigned to either a CMR or BMC position.1.4.4.1. Combat Mission Ready (CMR). The minimum training required for pilots to be quali-fied and proficient in all of the primary missions tasked to their assigned unit and weapons system.1.4.4.2. All CC-coded unit active duty API-1 positions, flying SQ/CC and DO positions are des-ignated CMR positions. OG/CCs may designate other API-6 positions not assigned to the flying squadron as CMR. (Exception: If a unit is over-manned, the SQ/CC may elect to train the front line of their Unit Manning Document (UMD) API-1s to CMR and designate the overage BMC. In this case, priority should be given to inexperienced pilots with at least 50 percent, if available, des-ignated CMR). (ARC/TFI: Any pilot may be designated CMR at OG/CC discretion). CMR pilots maintain proficiency and qualification in all core missions of the flying unit to which they are assigned or attached. CMR pilots maintain currencies which affect CMR status, accomplish all core designated flight training (missions and events), and all mission ground training. Failure to complete this training or maintain these currencies results in regression to non-CMR (N-CMR) status unless waived by appropriate authority.1.4.4.3. Basic Mission Capable (BMC). Pilot accomplishes training required to remain familiar-ized in all, and may be qualified and proficient in some, of the primary missions of their weapon system and unit. (ARC: Any pilot may be designated BMC at OG/CC discretion).1.4.4.4. All non-CMR active duty wing pilot positions are designated BMC positions. BMC des-ignations are assigned to pilots who have a primary job performing wing supervision or staff func-tions that directly support the flying operation, or are FTU instructors, Weapons School instructors, pilots assigned to active flying billets in units without assigned aircraft (i.e. 549 CTS [Air Warrior I], etc.), or operational test pilots. For those missions in which they maintain famil-iarization only, BMC pilots must be able to attain proficiency and qualification in 30 days or less.BMC pilots accomplish all mission related ground training designated by their attached SQ/CC.BMC pilots may deploy and may participate in any mission for which they are proficient and qual-ified, without additional training, as determined by the SQ/CC. Failure to complete BMC required training results in regression to non-BMC (N-BMC) status. AFRC and AFRC TFI BMC training events will be directed by RAP Tasking Memo.1.4.4.5. BMC pilots assigned to units without assigned aircraft (i.e. 549 CTS [Air Warrior I], etc.)will fly a RAP mix as determined by the unit commander consistent with their unit’s tasking. RAP events and weapon requirements are determined by the unit commander.1.4.4.6. N-CMR/N-BMC. Pilots that regress to N-CMR/N-BMC status will accomplish therequirements in accordance with paragraph 4.10. While N-CMR/N-BMC, pilots may perform missions (including exercise and contingencies) in which they are current, qualified, and either familiar or proficient.1.4.4.7. Specialized Training. Specialized training is training in any special skills necessary tocarry out the unit's assigned missions that is not required by every pilot. Specialized training con-sists of upgrade training such as FLUG, IPUG, FAC(A), etc., including CT to maintain proficiency and qualification in unit tasked special capabilities and missions. Specialized training is normally accomplished after a pilot is assigned CMR/BMC status, and is normally in addition to CMR/ BMC requirements. Unless otherwise specified, pilots in CMR or BMC positions may hold spe-cial capabilities/qualifications as long as any additional training requirements are accomplished.1.5. Training Concepts and Policies:1.5.1. Units will design training programs to achieve the highest degree of combat readiness consis-tent with flight safety and resource availability. Training must balance the need for realism against the expected threat, pilot capabilities, and safety. This instruction provides training guidelines and poli-cies for use with operational procedures specified in applicable flying/operations publications.1.5.2. ACC Training Support Squadron (ACC TRSS) will assist OG/CCs in development of trainingprograms when/where tasked by the HQ ACC/A3. Other MAJCOMs may submit requests for training program support to the HQ ACC/A3. If validated, these requests will be prioritized and tasked to ACC TRSS. Designated test units (CB-coded) may develop syllabi to upgrade operational test pilots in sup-port of specific test plans. These syllabi will be approved by the OG/CC and submitted to ACC TRSS.1.5.3. Design training missions to achieve combat capability in squadron tasked roles, maintain pro-ficiency, and enhance mission accomplishment and safety. RAP training missions should emphasize either basic combat skills or scenarios that reflect procedures and operations based on employment plans, location, current intelligence, and opposition capabilities. Tactical training will include use of inert and live ordnance, threat simulators, countermeasures, and dissimilar aircraft as much as possi-ble.1.5.4. In-flight Supervision:1.5.4.1. Unless specifically directed, the SQ/CC determines the level of supervision necessary toaccomplish the required training. If the mission objectives include introduction to tasks or instruc-tion to correct previous discrepancies, then an instructor pilot (IP) may be required.1.5.4.2. IPs and FL-qualified SQ supervisors may allow any pilot to lead portions of a mission ifappropriately briefed. This provision will only be used to allow the pilot to practice events in which he is already qualified or to help determine if the pilot is ready for FLUG.1.5.4.3. Flight leads may give their wingman the tactical lead for specific tasks. As a tactical lead,the wingman makes tactical decisions for the flight, but the flight lead retains overall authority and responsibility.1.5.5. Experienced Pilot (EXP)1.5.5.1. An experienced pilot has one of the following:1.5.5.1.1. 500 hours PAI.1.5.5.1.2. 300 hours PAI with 1,000 hours (FP/IP/MP).1.5.5.1.3. 100 hours PAI and previously fighter EXPERIENCED.1.5.5.2. For pilots, fighter time is defined as FP/IP/MP hours logged in aircraft while assigned anAFSC of 11FX. OA-10 and AT-38 are considered fighter time. WSOs must achieve fighter EXPE-RIENCED while assigned an AFSC of 12F3X or 12F4X.1.5.5.3. Hours logged in the MTC accomplishing RAP Tasking Memo-approved missions will becounted as “hours” when determining experience level. RAP MTC Mission hours will not exceed 20% of the total required to meet the experienced threshold (ex: 100 RAP MTC Mission hours out of 500 hours PAI). See the current RAP Tasking Memo for guidance on approved RAP MTC Mis-sions and logging procedures. AFRC: N/A.1.6. Ready Aircrew Program Policy and Management:1.6.1. The RAP training cycle is equal in length to the AEF cycle. RAP tasking is aligned with asquadron’s specific AEF pair and executed IAW RAP Tasking Memorandum. If not assigned to an AEF pair or assigned to multiple AEF pairs, RAP tasking is aligned to the AEF cycle itself. AETC training cycle is 12 months and aligned with the calendar year.1.6.2. Each RAP training level (CMR, BMC & BAQ) is defined by a total number of RAP missions,broken down into simulators, missions, specific weapons qualifications, and associated events as determined by the MAJCOM and unit commander.1.6.3. The breakout of mission and event types is provided as a guideline to be followed as closely aspossible but minor variances (other than increased Red Air allocations for CMR; AFRC: N/A) are authorized. However, SQ/CCs may still use variations in missions or events as a basis for regression.1.6.4. An effective RAP training mission requires accomplishing a tactical or building block profile.Each mission requires successfully completing a significant portion of the relevant events as deter-mined by the SQ/CC, RTM, and Attachment 2.1.6.4.1. Only one RAP training mission may be logged per sortie (day or night) unless separatedby AAR. Each mission on either side of the AAR must stand alone as an effective RAP training mission. A maximum of two RAP missions per sortie may be logged under these rules.1.6.5. The SQ/CC's first priority should be to train all designated pilots to CMR status. CMR statusrequires:1.6.5.1. A 1-month lookback at the CMR sortie rate.1.6.5.2. Qualification in all core missions and weapons events required at CMR.1.6.5.3. Confirmation that CMR pilots can complete the prorated number of sortie/event require-ments remaining by the end of the training cycle.1.6.5.4. Completion of mission-related ground training, to include a current verification or certi-fication.1.6.6. Progression from BMC to CMR requires:1.6.6.1. A 1-month lookback at the CMR rate.1.6.6.2. Qualification in all core missions and weapons events required at CMR. 1.6.6.3. Completion of mission-related ground training, to include a current verification or certi-fication.1.6.6.4. Squadron CC certification.1.6.7. SQ/CCs will determine and assign pilots that will train for and maintain special capabilities or qualifications. Special capability/qualification mission and event requirements are normally accom-plished in addition to baseline CMR/BMC requirements except for mission commander and flight lead training.1.6.8. End of Cycle training requirements are based on the pilot's experience level on the last day of the current training cycle.1.6.9. Units converting to another MDS may fly pilots in CMR positions at the BMC rate if CMR sor-tie rates cannot be supported. One month prior to the operationally ready date, CMR pilots should be flown at a CMR rate. Active duty wings converting to new MDS are authorized one SQ equivalent (7/6 for 24/18 or less PAI) of additional API-6s during the conversion period. However, total wing staff flying the new aircraft shall not exceed new authorized total.1.7. Training Sortie Program Development:1.7.1. RAP mission and event requirements (see Attachment 2) apply to CMR and BMC pilots including those carrying special capabilities or qualifications. They are IAW the RAP tasking memo which specifies the total RAP training cycle mission requirements. The RAP Lookback requirements at Table 1.1. establish the minimum number of missions required for BMC and CMR levels. The RAP tasking memo takes precedence over this instruction and may contain updated requirements and events not yet incorporated in Attachment2.Table 1.1. F-16 RAP Lookback Requirements.1.7.2. Navigation sorties should be programmed for API-1 pilots. These sorties ensure that pilots maintain their skills necessary to operate safely in the civil airspace environment.1.7.3. Experiencing/Collateral sortie requirements must be considered when developing unit flying hour programs.1.7.3.1. Experiencing sorties are additional training sorties necessary to achieve desired profi-ciency in optimum time. RAP missions may not provide sufficient hours to experience pilots to achieve overall unit experience levels. Component Cycle BMC Inexp BMC Exp CMR Inexp CMR ExpActive Duty 3-Month Lookback 18 15 30 271-Month Lookback 6 5 10 9ARC 3-Month Lookback 18 15 24 181-Month Lookback 6 5 8 6。
防腐中英文对照
1.1.SupplementedStandards补充标准.....................................................................................2REFERENCE引用...................................................................................................................2.1.××××HSERIESSTANDARDSANDMODIFICATIONS............................................................××××H系列标准和修改.............................................................................................2.2.IndustryCodesandStandards工业码和标准......................................................................3.CONTRACTORSRESPONSIBILITY承包商责任.......................................................................3.1.ExtentofSupply供应的范围............................................................................................4.QUALITYREQUIREMENTS质量要求...................................................................................4.1.GeneralRequirements通用要求....................................................................................5.SURFACESTOBECOATED防腐前的表面处理.......................................................................5.1.General通用......................................................................................................................6.SURFACESNOTTOBECOATED无需防腐的表面............................................................6.1.General通用.......................................................................................................................7.PROTECTIONOFSURFACES保护的面...................................................................................7.1.TemporaryCoverings临时的覆盖........................................................................................8.COATINGSYSTEMSANDMATERIALS防腐系统和材料.......................................................8.1.General通用.........................................................................................................................9.COATINGSCHEDULE防腐计划表............................................................................................10.COLOR颜色........................................................................................................................... 10.1.ColorCode颜色代码..........................................................................................................10.2.PipingIdentificationColorCode管道识别颜色编码.........................................................11.SURFACEPREPARATION表面准备......................................................................................11.1.AbrasiveMaterials研磨用的材料......................................................................................... 11.2.Pre-BlastCheck预吹扫检查.............................................................................................. 11.3.Cleaning清扫....................................................................................................................11.4.Equipment设备...................................................................................................................12.COATINGAPPLICATION防腐程序步骤..................................................................................13.INSPECTION检查....................................................................................................................14.FIELD-ERECTEDEQUIPMENT现场立式设备..........................................................................16.GALVANIZING电镀..............................................................................................................17.REPAIROFGALVANIZEDSURFACES修复的镀锌面........................................................ AppendixA:CoatingSystem附录一:防腐系统.....................................................................1.SCOPE范围1.1.SupplementedStandards补充标准ThisProjectSpecificationsupplementsthecoatingrequirementsof××××××××公司EngineeringStandards×××××××001,CoatingSelection&ApplicationRequirementsforIndustrialPlants &Equipmentand××××××××××,Internal&ExternalCoatingsforSteelPipelines&Piping.沙特××××××公司为本工程补充了防腐详细说明，×××××××001工业厂房和设备的防腐选择及步骤要求，××××××××××管线和管道的内防腐和外防腐2.REFERENCE引用Thefollowingreferencesarepartofthisspecification.下列参考文献是这份详细说明的一部分.2.1.××××HSERIESSTANDARDSANDMODIFICATIONS×××××××001CoatingsSelection&ApplicationReq uirementsforIndustrialPlants&Equipment-21February2010.为工业厂房和设备进行防腐选择及程序要求××××H系列标准和改版的×××××××001，2010年2月21.××××××××××Approved××××××××公司DataSheets-19April2009.××××××××××××××××××公司审批单，2009年4月19日××××××××××InternalandExternalCoatingsforSteelPipelinesandSteelPipelinesandPiping-1June2010. ××××××××××钢制管线和钢制管道的内防腐和外防腐，2010年6月1日.××××××××××VApproved××××××××公司DataSheets-30May2009.××××××××××V××××××××公司审批单，2009年5月30日.××××××××××ProtectiveCoatingSelection&ApplicationRequirementsforOffshoreStructureandFaciliti es.××××××××××离岸结构和设施的防腐蚀防护选择及程序步骤要求.××××××××××SafetyIdentificationandSafetyColors-17February2010.××××××××××安全识别和安全颜色，2010年二月17日.×××××××006FireproofingforPlants×××××××006工厂消防2.2.IndustryCodesandStandards工业识别码和标准PIPCTSE1000Applicationofexternalcoating-February2005.PIPCTSE1000外防腐的程序步骤，2005年2月.×××××SteelStructuresPaintingCouncil-Thirdedition.×××××第三版的钢结构油漆评议SIS05-5900PictorialSurfacePreparationStandardforPaintingSteelSurfaces-1988.SIS05-5900防腐前钢表面预处理图片1988.ISO8501-1PreparationofSteelSubstratebeforeApplicationofPaintsandRelatedProducts-VisualAsses smentofSurfaceCleanliness-Edition3.ISO8501-1进行油漆及相关产品前的钢材表面预处理——表面清洁度的视觉评估版本3 ASTMAmericanSocietyforTestingandMaterials.ASTM美国测试和材料协会.ASTMA123StandardSpecificationforZinc(Hot-DipGalvanized)CoatingsonIronandSteelProducts. ASTMA123在钢铁和钢构件上进行锌粉(热电镀-镀锌)防腐的标准说明NACERP0198-2×××TheControlofCorrosionUnderThermalInsulationandFireproofingMaterials-ASys temsApproachNACERP0198-2×××在有热保温和耐火材料时的防腐蚀：一系列步骤3.CONTRACTORSRESPONSIBILITY承包商责任3.1.ExtentofSupply供应的范围AllitemsthatarespecifiedtobecoatedorgalvanizedshallbecompletelycoatedorgalvanizedbytheCONT pletecoatingshallmeanallsurfacepreparationhasbeenperformedandallcoatsofpainth avebeenproperlyappliedasspecifiedin×××××××001or××××××××××,fortheapplicablecoatingsystem,a ndtheapplicable09-×××××seriesspecifications.Galvanizingshouldbecompletelygalvanizedinaccorda ncewithASTMA123StandardSpecificationforZinc(Hot-DipGalvanized)CoatingonIronandSteelProdu cts.所有被描述为需要防腐和镀锌的项目将被承包商完全防腐或电镀.完整的防腐将意味执行完所有的表面预处理，及所有油漆防腐是按照×××××××001或××××××××××的指定油漆系统说明恰当的实施，并适用于09-×××××的系列详细说明。
Windows Phone 风格指南说明书
WINDOWS PHONES TYLE GUIDE FOR S IMPLIFIED C HINESE Contents1.Goals of This Guide (3)2.The Windows Phone Voice (3)nguage-Specific Guidelines (4)3.1.General Tone & Voice—Share the Message (4)3.2.Style—Help Deliver the Voice (5)age—Sound Natural (6)3.4.Terminology—Be Consistent (6)3.4.1.Naming Guidelines and Trademark Requirements (8)3.5.Handling Fictitious Content (8)3.6.Measurements (9)4.Windows Phone UI Localization Guidelines (10)4.1.How to Translate UI Elements (10)4.1.1.App Bar Icon (10)4.1.2.App List Item (10)4.1.3.Buttons (12)4.1.4.Check Box Label (14)4.1.5.Edit Box Label (14)4.1.6.Group Label (15)4.1.7.Hub Title (16)4.1.8.List Item in Settings (16)4.1.9.Menu Items (17)4.1.10.Message Box (18)4.1.11.Notification Toast (19)4.1.12.Page Title (20)4.1.13.Pane Section Title (20)4.1.14.Phone Control Label (21)4.1.15.Pivot Item (21)4.1.16.Progress Indicator Text (21)4.1.17.Text Box (22)4.1.18.Tile Label (23)4.1.19.Toggle Switch (24)4.2.How to Translate References to UI Elements (25)4.4.Capitalization—Mind the Case (26)4.5.Words—Show as well as Tell (27)4.6.Punctuation—Divide and Conquer (28)4.7.Editing/Screen Review—Fine-Tune the Translation (29)4.8.Handling Input from External Stakeholders (31) (31)5.1.General (31)5.2.Terminology (32)5.3.Elements Specific to (33)5.3.1.Image Captions (33)5.3.2.Topic Titles (33)5.3.3.References to UI Elements (34)5.3.4.Mix of Western and Asian Characters (35)5.4.Sample Translations of Texts (35)5.4.1.Marketing Text (35)5.4.2.How-to Text (35)5.5.Fine-Tuning during Editing/Screen Review (37)1.Goals of This GuideThis document describes the tone, style and some specific translation instructions which should be used as reference during the Simplified Chinese localization of Windows Phone and its documentation. Windows Phone is a unique project as regards tone, style and terminology usage. The main goal of this guide is to help the translator understand and learn how to deal with all its linguistic and stylistic nuances during localization.There are 4 main focus areas in this guide:1.Windows Phone Voicenguage-specific guidelines on tone, style and terminology3.UI-specific Localization Guidelines—e.g. capitalization, text overflow,punctuation4.UA-specific stylePlease note this style guide is intended to be the main stylistic reference for Windows Phone projects. It is also a live document—it may be updated at certain stages to make sure the examples reflect all the latest information and guidelines.2.The Windows Phone VoiceThe language related to Windows Phone should make consumers (users) feel that they are empowered and supported. Windows Phone should be perceived as genuine, spirited, balanced, and supportive:Genuine•Speak with confidence.•Be an experienced guide.•Be friendly, focusing on the customer’s needs.Spirited•Genuinely express your own enthusiasm.•Express the achievable and talk about the difference it makes.•Reveal the unexpected, the sparkle, the delight.•Express a pleasant, engaging rhythm.Balanced•Be an experienced concierge: personal, friendly, enthusiastic, attentive.•Know when to keep things light, when to get down to facts.•Keep the moment, the audience, and the message in mind.•Don’t overpromise—be quick, clear, concise.Supportive•Lend help where it's needed, when it's needed.•Convey your knowledge like a trusted friend.•Strive to put others at ease.•Frame things positively, with a friendly demeanor.nguage-Specific Guidelines3.1.General Tone & Voice—Share the MessageThe Windows Phone device targets a group of modern, career-oriented people who expect their mobile phone to meet their needs in both their professional and private lives.In order to appeal to this audience, use contemporary, up-to-date style and terminology, close to what people actually say in everyday settings rather than theformal, technical language that is often used for technical and commercial content. Avoid using overly colloquial language, and keep a professional tone instead.3.2. Style—Help Deliver the VoiceThe style is direct and e straightforward translations and keep the user always in mind. The language used should sound natural.For Simplified Chinese, the formal second person is to be used with the following considerations:a)Use "您" instead of "你" to express respect to the user.b)Follow the rules of conciseness and clarity. Use "您" only if it is necessary.Minimize the occurrence of "您" in UI and documentation.If the source contains a structure in the first person plural, the decision whether to keep the sentence in the first person plural or use an impersonal structure will depend on the context. Generally, an impersonal structure should be used for error messages.Examples:The characters "&", "+" appear frequently in the source as connectors. The ampersand char acter should be localized using the Chinese preposition “and” (和). The plus symbol (“+”) is part of the design language of the phone and saves space, so it should be preserved in the translation based on the decision of Microsoft. The plus symbol should be surrounded by spaces.Examples:age—Sound NaturalIn order to transmit a positive and friendly tone, direct speech should be used instead of indirect. This will also help avoid redundancy and improve the fluency of the text. Keep the following general points in mind:∙Be straightforward and concise. Avoid redundancy.∙Be accurate but not over-exhaustive, as it might harm legibility.∙Avoid slang and be careful with colloquialisms.∙Make sure explanations are pleasant to read.∙Make the complicated uncomplicated without oversimplifying: focus on essentials.Examples:3.4.Terminology—Be ConsistentUse terminological options which are easy to understand, up to date and in line with the terminology used by competitors. The focus should not be on following Microsoftstandard terminology, but rather on researching and identifying those terms most widely used within the mobile industry of your target country.Always refer to the Windows Phone terminology as priority no. 1. Please note that approved translations for Windows Phone key terms are to be found in the Windows Phone MultiTerm database.When translating Windows Phone for Office applications such as presentations, e-mails, spreadsheets etc., aim for consistency with current Office applications in order to give the user a consistent experience. Please pay special attention to Excel formulas and functions—verify their translation in the latest localized version of Excel and/or in TRES.Microsoft standard terminology should be used in conjunction with other Microsoft products (Xbox, Internet Explorer, etc.) as secondary source of reference. As part of your terminology research, always check what is used in other products in TRES and TermStudio.If needed, please provide feedback on Windows Phone terminology you feel is incorrect (but please do not attempt to change approved terminology before receiving confirmation from the project team).Also contact the project team if you come across a new app, product or feature name that is not included as part of the Windows Phone terminology. Product names are normally not translated (e.g. Windows Phone). Feature names can usually be translated (e.g. Data Sense, voicemail). In any case, it is extremely important to always confirm localizability of any such items with the project team.Examples:3.4.1.Naming Guidelines and Trademark RequirementsPlease follow Windows Phone Naming Guideline and Trademark Requirements provided separately.3.5.Handling Fictitious ContentFictitious content is legally sensitive material and as such cannot be handled as a pure localization issue. When dealing with fictitious company and people names in Windows Phone, please use the list of legally approved names provided by the Microsoft Legal department (LCA). The Windows Phone product team representative will be able to provide you with the list of legally approved names managed by LCA.*******************The domain name should be left unlocalized, as it is a globally recognized domain created by the IANA (Internet Corporation for Assigned Names and Numbers) for sample purposes. “Someone” should stay as-is for SimplifiedChinese, so the fictitious address will be the same as in EN-US(*******************).3.6.MeasurementsThe EN US source contains measurements in strings such as:Please add a blank space between the value and the unit of measurement in the translation if the unit of measurement needs to be translated as Simplified Chinese. If the unit of measurement should be kept in English, don’t add a blank space between the value and the unit of measurement if there is no space between the value and the unit of measurement in source. The following is the sample translation of the above strings:The unit “KB” (kilobyte) should be translated as “KB”, keeping the letter “K” in uppercase.4.Windows Phone UI Localization Guidelines 4.1.How to Translate UI Elements4.1.1.App Bar Icon4.1.2.App List Item4.1.3.Buttons4.1.3.1.Dialog Button4.1.3.2.Push Button4.1.3.3.Radio Button4.1.4.Check Box Label4.1.5.Edit Box Label4.1.6.Group Label4.1.7.Hub Title4.1.8.List Item in Settings4.1.9.Menu Items4.1.9.1. Application Menu Item4.1.9.2.Context Menu Item4.1.10.Message Box4.1.10.1. Message Box Body4.1.10.2. Message Box Header4.1.11.Notification Toast4.1.12.Page Title4.1.13.Pane Section Title4.1.14.Phone Control Label4.1.15.Pivot Item4.1.16.Progress Indicator Text4.1.17.Text Box4.1.18.Tile Label4.1.19.Toggle Switch4.1.19.1. Toggle Switch Label4.1.19.2.Toggle Switch Title4.2.How to Translate References to UI ElementsReferences to UI elements within the UI can be found in error messages, task messages, etc. It is important to have a consistent approach towards the localization of such references. References to UI elements can appear in examples such as the below.Example:SourceMake sure your email address and password are correct, and then tap Sign In.DescriptionThe string above makes a reference to the “sign in“ push button. In the EN US source, push buttons are in all lowercase when appearing on their own as standalone UI options; however, when there is a direct reference to these elements in UI messages, English does not use lowercase, but title casing instead, i.e. the 1st letter of each word is capitalized. This is why in the source example above “Sign In“ appears in title casing.Translation StrategyFor Simplified Chinese, references to UI elements within UI strings should be translated using the Chinese double quotation marks enclosing the UI element. As a result, the translation of the source string in the example above would be as follows.Translation请确保您的电子邮件地址和密码正确，然后点击“登录”。
平流层飞艇通用技术要求 第1部分：环境控制系统-最新国标
平流层飞艇通用技术要求第1部分：环境控制系统1范围本文件规定了平流层飞艇环境控制系统的组成和功能、通用技术要求以及相应的试验验证要求。
本文件适用于平流层飞艇环境控制系统的设计，低空飞艇，高空气球等相关类型浮空器环境控制系统的设计也可参考。
2规范性引用文件下列文件中的内容通过文中的规范性引用而构成本文件必不可少的条款。
其中，注日期的引用文件，仅该日期对应的版本适用于本文件；不注日期的引用文件，其最新版本（包括所有的修改单）适用于本文件。
GB/T2423电工电子产品环境试验GB8624建筑材料及制品燃烧性能分级GB/T10294绝热材料稳态热阻及有关特性的测定防护热板法GB/T14812热管传热性能试验方法GB/T15428电子设备用冷板设计导则20213277-T-469浮空器术语ISO16691Space systems-Thermal control coatings for spacecraft-General requirements3术语和定义20213277-T-469规定的术语和下列属于适用于本文件。
3.1环境控制系统environmental control system环控系统用于控制飞艇吊舱内和舱外各设备的工作环境（主要指温度），使环境条件处于规定范围内的系统。
3.2保温设备Insulation equipment用于吊舱或设备外表面，起到被动保温作用的设备，一般指保温棉、保温板。
3.3加热设备heating equipment用于吊舱壁面或设备外表面，起到主动加热作用的设备，一般指加热膜、加热器等。
3.4散热风机cooling fan安装于飞艇吊舱上，用于舱体内部空气与外界环境进行热交换，对舱体进行降温的风机。
3.5热管heat pipe用于发热设备的外表面，将其热量迅速传递至外界或者其他发热量低的设备。
3.6液冷板Liquid cooled plate用于发热设备的外表面，通过将水或其他液体引入到散热器中，利用流体对设备进行冷却来降低温度。
DL 5190.8-2012 电力建设施工技术规范 第8部分：加工配制
2.3 拼接与矫正.........……….........................................…...…...…....5
2.4 焊接.........…....……………………………………………………………7 … 2.5 除锈及涂装底漆.........................…….....9....…...
Байду номын сангаасIV
DL5190.8 一-2012
Contents
Forewo 时……………………………………………………………………………..
1
1 General provisions' …................................….............................…1
∞ 5 Steam ， water pipelines and c omponents' ……..…...…….川…...……..…….川…….川…….川.….2….0川……..…….川……..…….川
5.1 General requirement .…...…...…...…....….川..….川..…...….川..…...…...…....…...…......2.…0...…...…...….川..…
2.3 Splicing and correction ……..........................… .............................5
2.4 Welding ………………………………………………………………………
..7
2.5 Derusting and primer painting …................................….........…… .9
中英对照文件控制程序
Document Control Procedure 文件管理程序1.0 Purpose目的Define the requirements and responsibilities for Document control.定义出文件控制的要求和权责。
2.0 Scope范围This procedure applies to all QMS documentation, including: quality manual, procedure, WI,external document and form.适用于与质量管理体系有关的所有文件。
包括:手册、程序文件、操作指导书、外来文件及表单。
3.0 Definitions定义3.1 Quality Manual: According to the requirements of International and national standard (suchas ISO9001), describe quality management system documentation in Co-active.3.1质量手册：根据相关国际或国家标准(如ISO9001)要求，阐述本公司质量管理体系的文件。
3.2 Procedure: Define the function of QMS requirement allocation by department. Such asdocument control, management review, internal audit procedure.3.2程序文件：描述为实施质量管理体系要求所涉及的各职能部门的活动的文件。
如文件控制程序、管理评审控制程序、内部审核控制程序。
3.3 Working Instruction: Operation procedures, inspection standards, design drawing and etc.3.3操作指导书：操作规程、检验标准、加工图纸等。
民用建筑外窗工程技术规范DB37 5016-2014
DB37/ 5016-2014
民用建筑外窗工程技术规范
Technical code for external windows of civil building
山东省住房和城乡建设厅 联合发布
山东省质量技术监督局
1
山东省工程建设标准
民用建筑外窗工程技术规范
Technical code for external windows of civil building
4
6.4 外窗装配................................................................................... 21 6.5 建筑外窗标志、包装和运输....................................................... 22 7 安装施工........................................................................................ 23 7.1 一般规定.................................................................................. 23 7.2 施工准备.................................................................................. 23 7.3 建筑外窗安装........................................................................... 23 7.4 防雷施工.................................................................................. 25 7.5 清理及成品保护........................................................................ 26 7.6 安全技术措施........................................................................... 26 8 工程验收........................................................................................ 28 8.1 一般规定.................................................................................. 28 8.2 验收主控项目........................................................................... 29 8.3 验收一般项目........................................................................... 30 9 保养与维护.................................................................................... 31 9.1 一般规定.................................................................................. 31 9.2 检查、维护及维修.................................................................... 31 附录 A 地震载荷及强度计算原则................................................... 32 附录 B 常用材料的力学及其它物理性能....................................... 34 本规范用词说明................................................................................ 36 引用标准目录.................................................................................... 37 条文说明............................................................................................ 40
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
PART 4.8 ERECTION AND COMMISSIONING4.8.1 GENERAL REQUIREMENTS4.8.1.1 Scope of WorkThe Bidder shall erect and commission all the equipment furnished by himas required by the Contract in accordance with the requirements specifiedherein.The Works shall conform to the applicable requirements of governingcodes and all Indonesian codes or regulations having jurisdiction.The Bidder shall arrange the schedule of his work in every respect to meetthe Contract Schedule.The Bidder shall provide erection and commissioning procedures for allequipment furnished by him. These shall be submitted after ContractAward.The Bidder shall furnish all erection tools, machinery, testing devices,expendable supplies, labor and labor supervision required and as necessaryto properly erect and commission the equipment.All workmanship shall be the best of its kind. All labour shall be performedby men skilled in their particular line of work and to the full satisfaction ofthe Owner. All of the Works shall be erected complete, ready forcommercial operation and to the full satisfaction of the Owner.4.8.1.2 GeneralWORK AND SUPERVISIONThe erection and commissioning of all equipment shall be done under theguidance of the manufacturer's representative (as applicable) or inaccordance with manufacturer's recommendations. The equipment shallbe erected, set, leveled, aligned and completed in conformance with hisdirection and to his complete satisfaction before equipment is put intoservice. The manufacturer's representative shall also guide and direct theplacing of the unit in successful operation by Owner's personnel.The Bidder shall provide all Works and materials required for erection,assembly mounting, wiring, checking, testing and commissioning for allequipment, components, controls, instruments, accessories andappurtenances furnished by the Bidder; and all other equipment supplied by sub Bidders and erected by the Bidder items of which are included in the Contract.Certain accessories and appurtenances may be located remotely from the main equipment as shown on the drawings. It shall be part of Bidder's Works to set and erect such accessories and appurtenances and install interconnecting piping and/or wiring furnished by the manufacturer as an integral part of the whole unit.The Bidder shall perform all Work which is normally considered part of the Work whether or not such Work is fully listed in detail in the Bid Document or Contract. The words "erect", "install", "installation", "checking", "testing", "correction", and "adjustment" will be frequently used concerning the Work of Erection and Commissioning.WORK, SCHEDULES AND COORDINATIONIt shall be the responsibility of Bidder to engage the proper trades for carrying on all phases of the Works harmoniously. Bidder may sublet any portion of the Works, as may be required. However, the sub Bidder shall be subject to the written approval of the Owner, prior to performance of any work by sub Bidder.It shall be the responsibility of the Bidder to co-ordinate his installation activities with the material delivery schedule of his sub Bidder and the construction program so that a smooth and harmonious schedule may be maintained. It shall also be the responsibility of the Bidder to co-ordinate his installation activities with his sub Bidders.INTERFACINGThe Bidder shall provide all necessary interfacing information and cooperate fully with sub Bidders to check for interferences to ensure that interfacing information furnished will be as required to erect and commission all the equipment to the full satisfaction of the Owner. ACCEPTABLE AND UNACCEPTABLE WORKAll poor, defective or condemned work shall be remedied at the expense of Bidder and he shall not be reimbursed for any expense in connection with such repairs. The Bidder shall be responsible for the care, safety and maintenance of all the materials and all equipment included in this contract until acceptance of the installed materials by the Owner. The Owner will not pay for the removal or replacement of damaged or faulty material after it has been installed or if damaged prior to installation. The Owner shall make the final decision as to whether Work is acceptable or not.Bidder shall be responsible for the correct setting, mounting andalignment of all equipment erected by him and shall maintain and submitto Owner's representative written records of alignment readings. TheOwner's representative will inspect the completion of each of theshimming, grouting, alignment and dowelling work. Bidder shall notproceed with the subsequent work and operation of the equipment untileach inspection is completed.PRESERVATIVESThe Bidder shall be responsible during the installation process for thecomplete removal of all preservatives applied to power plant equipmentcomponents which are incompatible with the system path and auxiliarysystems to which they are applied.The Bidder shall provide any and all equipment, mineral or solventsrequired to completely remove all preservatives from the equipment parts.The Bidder shall install components immediately after removal ofpreservatives. If this cannot be done Bidder shall apply a light dutypreservative to the components which is compatible with the equipment.Light duty preservatives to be used shall be in strict accordance with themanufacturers recommendations.4.8.1.3Supervision and Manufacturer’s RepresentativesGENERALThe Bidder shall supply all technical guidance and supervision required forthe Work.MANUFACTURER'S REPRESENTATIVESThe Bidder shall furnish guidance from manufacturer's technicalrepresentative for erection and commissioning of the equipment under thisBid Document. A manufacturer's representative shall be included for eachitem of major equipment.If the services of any additional manufacturer's representatives arerequired by the Bidder, the total cost of such services shall be at theexpense of the Bidder. All equipment covered by this Specification shallbe unloaded, stored, protected, erected, set, and aligned in completeaccordance with the manufacturer's instruction books or directives. Allrework or additional work required due to noncompliance withmanufacturer's instructions shall be at the expense of the Bidder and noclaims shall be made by Bidder for lack of understanding of the completeScope of Work.The Bidder shall identify his Site personnel including Erection Supervisors,Start-up Supervisors and Performance Test Supervisors. Such personnelshall be subject to approval by the Owner.RECORDS AND REPORTSThe Bidder shall maintain a Site inspection record of QualityAssurance/Quality Control.Bidder's representative at Site shall maintain a daily log-book consisting of:Owner's instructionsOwner's complaintsSchedule of important events of the dayRecord of disagreementsOWNER'S INSPECTORThe Owner will have his inspection personnel at Site, to inspect the workdone by Bidder.4.8.1.4ErectionEQUIPMENT AND ACCESSORIESThe Work shall be in accordance with the Specification and all work shallbe done in orderly and work- manlike manner, shall present a neatappearance when completed and shall conform to the best modernengineering practice for the class of work, not with standing any omissionin the Drawings and Specifications.Each piece of equipment shall be located as shown on the drawings andshall be erected complete in all respects unless exceptions are specificallynoted herein.The Work shall include the assembly and alignment of components whereequipment is shipped unassembled or knocked down, or where thecomponents are shipped separately.The Works shall include the erection of all piping, wiring, instruments,controls, drivers and other components and accessories furnished with theequipment, unless otherwise indicated in the Specification or on thedrawings.The erection of equipment shall be in accordance with therecommendations of the equipment manufacturers.CONSTRUCTION EQUIPMENT AND SAFETYBidder shall furnish and install temporary ladders and scaffolding as hemay require. All temporary stairways, ladders or platforms which may berequired by Bidder shall be furnished and installed by Bidder at hisexpense and shall be removed by him after they have served their purposeat his expense.Bidder shall furnish all hoisting, rigging cables, slings and otherconstruction equipment (regardless of size and type) and supplies requiredfor unloading, assembly and erection of equipment to be erected byBidder. Attachments to building steel for hoisting and rigging shall bereviewed by the Owner.Bidder shall erect all temporary barricades to isolate the block underconstruction and commission that may be required as approved by theOwner. All such barricades shall be arranged so as to ensure the safety ofthe workmen and passersby. Bidder shall remove such protection at thecompletion of the Works.The Bidder shall keep the construction Site as clean as possible in order tofacilitate construction work and to avoid damaging the equipment andinjuring workers. Piping flushing oil, chemicals, etc. used for equipmentcleaning shall be properly disposed of by Bidder.The Bidder shall keep the construction Site as clean as possible in order tofacilitate construction work and to avoid damaging the equipment andinjuring workers. Piping flushing oil, chemicals, etc. Used for equipmentcleaning shall be properly disposed off by Bidder.4.8.1.5 Adjustment and Correction WorkAt the completion of erection of each system, Bidder shall perform all thenecessary tests, including hydrostatic tests and performance tests.The Works shall be subject to inspection and acceptance by the Owner.Bidder shall make such adjustments and do such other work as may berequired by the Owner to place each piece of equipment erected byBidder in proper operating condition ready for service. This adjustmentand correction work shall be done by Bidder without additional cost to theOwner.Any correctional work required to be done by Bidder in order to install theequipment properly and which is due to the manufacturers' faulty shopwork or design shall be reported by Bidder to the Owner and shall bedone byBidder only after review by the Owner of the correctional procedures.This in no way shall affect the warranty on the equipment.4.8.1.6 Start up and CommissioningPREPARATION AND SPECIALTIESPrior to start up, the Bidder shall provide cleaning and flushing as requiredby each equipment.Temporary pumps, piping, hose, valves, jumpers etc. not furnished withthe equipment but required for start-up and commissioning shall befurnished by Bidder and removed after cleaning operations are completed,prior to performance testing.SCHEDULESUpon the completion of erection the Bidder shall carry out the start upand commissioning of each equipment in accordance with the start-up andcommissioning procedures as reviewed by the Owner.The startup and commissioning activities shall in general follow thesequence of events shown in Exhibit 1.During the availability test no accumulation period between unsatisfactoryconditions shall be accepted, except if the sources of trouble clearlycomes from the PT PLN (Persero) network system.OPERATION AND SUPERVISIONFrom initial start up until take over by the Owner, the Bidder shall beresponsible for the running, operation and maintenance of the Works.The start up shall be supervised by the Bidder using the Owner's operators.The Owner's operators shall be trained by the Bidder to his satisfaction toensure safe and orderly plant start up and operation. Under the Bidder'ssupervision the Owner's operators shall exclusively operate all controls ofthe plant.4.8.1.7 Checking and TestingSCOPE OF WORKThe Bidder shall perform all specified testing required for the equipmenterected or furnished by him.All testing shall be in accordance with the specified Codes and Standardsand instructions & recommendations of manufacturers as specified atPerformance Testing, Guarantees and First Inspection and individualTechnical Specifications.In addition to the tests listed above, the Bidder shall demonstrate thefunction and capability of all equipment and systems supplied under theContract, to perform in accordance with the Specification requirementsand applicable standards.All tests to be performed at Site shall be agreed with the Owner prior tocommencement of the work. The Bidder shall prepare the details of theITP (Inspection & Test Plans), Schedules, test procedures and submit thesedocuments to the Owner for approval. The Owner will mark in theappropriate spaces his intention to attend or waive the invited tests orinspections.A minimum of twenty one days notice of the readiness of plant for test orinspection shall be provided to the Owner by the Bidder.The Bidder shall furnish the Owner all test reports including test datataken for tests performed by the Bidder's representative. The test dataforms used for tabulating the information required shall be furnished bythe Bidder as soon as possible after tests have been made, for theapproval of the Owner.The Bidder shall prepare detail of ITP (Inspection and Test Plant)PERFORMANCE TESTINGPerformance Test shall be conducted under the direction of theManufacturer's representative as applicable to ensure that the testing isconducted in accordance with the Manufacturer's recommendations and isconsistent with the procedures in the operating manuals.The testing shall be performed under the direction and supervision asexplained above using the Owner's operators. At least one year prior tothe scheduled commercial operating date the Bidder shall advise theOwner of the training requirements for the Owner's start up and testingcrew.TEST COORDINATION AND RESULTThe Owner will co-ordinate the performance of all tests with the Bidderand with the sub Bidders.If, in the opinion of the, test results show improper adjustment, operationor performance of any equipment and such deficiencies are due tonegligence or unsatisfactory installation by the Bidder, the Bidder shallfurnish all labour, equipment and materials required to remedy thesituation to the satisfaction of the Owner and at no increase in cost to theOwner.4.8.1.8 Quality Assurance/Quality Control (QA/QC)THE QUALITY CONTROL PROCEDURES SHALL INCLUDE, BUT NOT BE LIMITEDTO, THE FOLLOWING:Welding Procedure and Welding Procedure QualificationsRadiographyMagnetic ParticleLiquid PenetrantUltrasonic TestingHydrostatic Testing and/or Pneumatic TestingLeak TestingPW Heat TreatmentMajor Weld RepairsControl of Welding MaterialsSub Bidder Qualification and SurveillanceNon conformance and Deviation ControlNDE Personnel QualificationsWiring Insulation TestingControl and Functional TestingTHE QUALITY CONTROL DOCUMENTATION SHALL INCLUDE, BUT NOT BELIMITED TO, THE FOLLOWING:All documentation specified in the Specifications.All other documentation required by the applicable codes andstandards.All other documentation required by the equipment manufacturer'sfield erection procedures.Material test reports.Material certification reports.Inspection reports.BOOK IIIPART 4.8 Erection and Commissioning4.8.1 General RequirementsRevision 0 Part 4.8 - 10 PT PLN (Persero) – Jatim Selatan CFSPPEXHIBIT ISEQUENCE OF EVENTS FOR START UPAND COMMISSIONINGSTART UP OF MISC. EQUIPMENTINDIVIDUAL TESTS*2LOADING TEST*3LOAD REJECTION TESTSHUT DOWN30 DAYS *1 RELIABILITYRUNGUARANTEE PERFORMANCETESTSSYSTEM TEST PERIODADJUSTMENT TO SYSTEM, OVERSPEEDTEST(INITIAL OPERATION)SUB SYSTEM TEST PERIODPRELIMINARY INSPECTION & CHECKOUTAND INDIVIDUAL TEST PERIODUNIT SYSTEM TEST PERIODCOMMISSIONINGNOTES : *1 RELIABILITY RUN TO INCLUDE 96 HRS FULL CONTINUOUS LOAD THEN LOAD VARIES SUBJECT TO SYSTEM DEMAND *2 LOADING TEST TO INCLUDE 10% OVERSPEED *3 TO INCLUDE FULL LOAD REJECTION TEST*4 NOT TO SCALEERECTIONESSENTIALLY COMPLETEERECTIONESSENTIALLY COMPLETEERECTIONESSENTIALLY COMPLETE ERECTIONESSENTIALLY COMPLETE ERECTIONESSENTIALLY COMPLETECONSTRUCTIONCONSTRUCTIONOPERATION。