微软成功收购家庭自动化公司R2 Studios
批量许可服务中心用户指南
分配订阅 ............................................................................................................................................................................. 47 分配多个订阅 ................................................................................................................................................................... 49 删除订阅者 ........................................................................................................................................................................ 51 使用发货情况搜索 .......................................................................................................................................................... 52 查看订阅摘要 ................................................................................................................................................................... 53
FactoryTalk View Site Edition 安装指南说明书
注意：标识可能导致人员伤亡、财物损害或经济损失的做法或环境的相关信息。注意事可帮助您识别危险，避开 危险，以及意识到后果。
重要 标识对成功应用和了解产品至关重要的信息。 还会在设备上或内部使用标签来提供具体预防措施。
章节 2 系统要求
我可以在一台服务器上安装和运行什么？ ................................................................................................15 查看硬件要求 ..................................................................................................................................................15 查看操作系统要求 .......................................................................................................................................... 16
章节 3 预安装配置
禁用 Windows 自动更新..............................................................................................................................19 配置 NIC 和交换机端口...............................................................................................................................19 禁用或卸载第三方防火墙 ............................................................................................................................20 移除增强的安全配置 ....................................................................................................................................20
Avaya IP Office快速安装说明V2.2
AVAYA IP OFFICE快速安装说明V2.2适用IP Office 3.0、3.1版本修改日期备注V2.2 2005-12-31 朱炜添加实现Delta Server的IP计费应用2005-12-31 王毅修改安装TAPI和Devlink2006-1-4 王毅添加安装License软件许可2006-1-17 王毅修改H323 VOIP中继中Local Tones选项2006-2-8 王毅删减 IPOffice数据安装章节2006-3-10 朱炜修改System系统数据修改2006-3-10 王毅增加 IP Office最新版本提示2006-3-14 王毅修改串口初始化系统或清除Bin修改IP Office的端口软件版本发布日期备注Admin CD 3.1.56 2006-3-10IP Office 2月份维护版本Voicemail Pro 3.1.18 2006-3-10IP Office 2月份维护版本User 3.1.17Conference Center 3.1.11CCCV5 5.0.25注：IPOffice 3.1下一个维护版本将在2006年5月底发布。
IPOffice 3.2将在2006年7月底发布。
注：1.Avaya IP Office 在本文中简称：IPO，对于IP Office Small Office Edition 在本文中简称SOE；2.在本文中尤其要注意“注：……”的蓝色字体内容。
3.本文中大量引注了《IP Office 3.1 Document CD》（在文中简称《Document CD》）中的内容，这个文档库软件请务必装在你的电脑中，可以到网站中下载。
4.推荐网站链接 IP Office的管理和应用软件，免费下载 IP Office的论坛 IP Office的国外论坛目录1IPO 硬件概述 (6)1.1IPO的视图和连接 (6)1.2IPO的加电 (6)1.3IPO的接地 (6)2系统软件介绍 (7)2.1IPO C ORE SOFTWARE (7)2.2IPO A DMIN光盘 (8)2.2.1IP Office Manager (9)2.2.2IP Office Wizard (10)2.2.3CallStatus (11)2.2.4Monitor (11)2.2.5Delter Server (13)2.3IPO U SER光盘 (14)2.4IPO V OICEMAIL P RO 光盘 (15)2.5IPO CCC光盘 (15)2.6IPO C ONFERENCE C ENTER (15)2.7IPO D OCUMENT CD工程师工具光盘 (15)3IPO 主机的参数设置 (15)3.1IPO的初始化数据 (15)3.2登陆系统 (16)3.3S YSTEM系统数据修改 (17)3.4安装L ICENSE软件许可 (18)3.4.1关于License Key的说明 (18)3.4.2并口或USB License Key的安装 (19)3.4.3Manager的设置和License 的导入 (20)3.4.4有关License的故障 (20)3.5中继线设置 (21)3.5.1模拟中继线 (22)3.5.2ISDN-PRI中继 (22)3.5.3China R2 中国1号信令中继 (23)3.5.4H.323 VOIP中继 (23)3.6分机设置 (25)3.6.1Extension设置 (25)3.6.2User设置 (25)3.7S HORT C ODE (27)3.7.1分机电话功能ShortCode (27)3.7.2呼叫路由ShortCode (27)3.7.3阻塞式呼出和直播/重叠式呼出的比较 (29)3.7.4LCR最优路由的使用 (30)3.7.5用Shortcode进行呼叫路由的几个技巧 (30)3.7.6在Shortcode中用到的字符说明 (31)3.8I NCOMING C ALL R OUTE (32)3.9L INE A PPEARANCE/B RIDGE A PPEARANCE/C OVERAGE A PPEARANCE (33)3.9.1LineAppearance (33)3.9.2BridgeAppearance (33)3.9.3CoverageAppearance (33)3.10IPO设置案例 (34)3.10.1IPOffice 组网路由设置 (34)3.10.2手动控制切换夜服流程 (34)4IP OFFICE PHONEMANAGER的安装 (34)4.1IP S OFTPHONE的安装 (34)4.2P HONE M ANAGER的日志抓取 (35)5IP OFFICE DELTER SERVER (36)5.1实现D ELTA S ERVER IP计费的应用 (38)6VMPRO 软件安装使用说明 (39)6.1VMP RO S ERVER 的安装 (39)6.2编辑自己的VMP RO 语音流程 (42)6.2.1打开Voicemail Pro来编辑一个新的流程 (42)6.2.2IPOffice的配置 (44)6.2.3VMPro语音流程的导入导出 (44)6.3VMP RO 语音邮箱I NTUITY模式 (45)6.3.1Intunity Mode 操作图 (47)6.3.2Intuity模式下直接访问语音邮箱 (47)6.4VMP RO设置语音留言的E MAIL转发 (48)6.4.1使用MAPI进行留言的Email转发 (49)6.4.2使用SMTP进行留言的Email转发 (49)6.5数据库访问 (51)6.6V OICE M AIL P RO中的参数 (51)6.6.1$SAV的应用 (51)6.7VMP RO与A UDIX的组网连接 (54)7IP OFFICE CALL CENTER的安装 (54)7.1IP O FFICE 的TAPI接口介绍 (54)7.1.1CTI Lite和CTI Pro接口 (55)7.1.2DevLink事件消息 (57)7.2IP O FFICE ACD软件介绍 (57)7.2.1IP Office的技能组 (57)7.2.2IP Office 技能组的ACD算法 (57)7.2.3技能组的语音留言 (58)7.2.4技能组的后备组 (58)7.2.5技能组的排队 (58)7.2.6技能组的录音 (59)7.3IP O FFICE的座席介绍 (60)7.3.1座席的登陆退出 (61)7.3.2座席的置忙 (61)7.3.3座席的录音设置 (62)7.3.4PhoneManager Pro软件 (63)7.4IPO呼叫中心的安装 (65)7.4.1配置IPOffice (65)7.4.2配置VMPro (66)7.4.3安装配置TAPI和DevLink (66)7.4.4Wave User的安装 (67)7.4.5呼叫中心排队保持音乐 (72)7.5CCC软件说明 (72)7.5.1关于CCC报表中有关时间的说明 (72)7.5.2关于报表数据字段的问答 (73)8IP OFFICE CONFERENCE CENTER的安装说明 (74)8.1安装之前的环境确认 (74)8.2IPO FFICE中相关设置 (75)8.3VMP RO 中相关设置 (76)8.4C ONFERENCE C ENTER软件安装 (76)8.5测试 (76)9IP OFFICE/话机功能使用说明 (79)9.1数字/IP话机查看呼叫记录 (79)9.1.1缩位拨号，Using Speed Dials (80)9.1.2Personal speed dials (81)9.1.3Short Code Speed Dials (82)9.1.4System AD List 和Directory (82)9.2IP O FFICE会议操作 (83)9.2.1IP Office Meet-Me（拨入式）会议的设置 (83)9.2.2IP Office ConferenceAdd会议（按需会议）的操作 (83)9.3热线电话 (83)10IPO的日常维护及常见故障排除 (84)10.1IPO FFICE主机的维护 (84)10.1.1日常维护的对象 (84)10.1.2日常需要备份的文件清单 (84)10.1.3故障提交Avaya 工程师处理所需提供的材料 (84)10.2升级 (85)10.3串口初始化系统或者清除B IN (85)10.4通过M ANAGER恢复IPO主机 (87)10.5扩展模块的灾难恢复 (88)10.6内置保持音乐M USIC O N H OLD (88)10.7分机的登陆/退出，座席的登陆/退出 (91)10.8DDI被叫号码显示的应用 (91)10.8.1被叫号码显示的需求 (91)10.8.2前台识别被叫号码方案 (91)10.8.3Unified FAX 应用 (92)10.9关于L ICENSE K EY的说明 (93)10.9.1IPOffice的软件许可常变为不可用（Invalid） (93)10.9.2时间的不同步导致License 识别故障 (93)10.10常见故障排除 (94)10.10.1模拟中继呼出掉线的问题1 (94)10.10.2模拟中继呼出掉线或长途经常拨叫不成功2 (95)10.10.3内置保持音乐经常丢失 (95)10.10.4IP Office IP地址找不到 (95)10.10.5IPOffice 与S8700的VOIP连接故障 (96)11IPO 的技术参数 (97)11.1IPO的CPU (97)11.2D IRECTORY（电话薄）的容量 (97)11.3IPO FFICE 的端口 (98)11.4内置语音邮箱的自动话务台语音提示长度 (98)1 IPO 硬件概述1.1 IPO 的视图和连接注1：SOE 是支持4端口ISDN BRI ，即通过扩展，SOE 能够支持8个通道的数字中继。
IDC - China IT Services 20082012 Forecast and Analysis
Filing Information: July 2008, IDC #CN221105Q, Volume: 1, Tab: MarketsM A R K E T A N A L Y S I S C h i n a I T S e r v i c e s 2008–2012 F o r e c a s t a n d A n a l y s i s Grace Han Ting Yang Vivian Yu Gloria Li I D C O P I N I O N China's IT services market is facing both domestic demand and offshore opportunity. With global sourcing becoming a strategic decision of companies to lower costs and enhance core competencies, the country boundary among services is blurring. To better capture this global sourcing opportunity, IDC strongly suggests leveraging China's comparative advantages and using the economies of scope by developing both domestic and offshore IT services industries collaboratively. ! 2007 was still a bull year for IT services players in China, especially the leading services providers. With the market gradually consolidating, the top 10 services providers' gained share from 17.0% in 2006 to 19.7% in 2007. ! The market size also grew very fast, from US$6239.8 million in 2006 to US$7699.1 million in 2007, with a 23.4% year-on-year growth. This is 1.1% higher than IDC's previous forecast. Looking forward, China's IT services market will still be in the double-digit growth stage for the next five years, with a 2007–2012 compound annual growth rate (CAGR) of 16.2%, although the growth rate will be slightly lower than that in the past two years. ! For IT services, as observed, a large amount of competition comes from the clients' internal IT departments. Because of this, it is very important to understand users' adoption rates of third-party services providers, reasons for insourcing, and vendor evaluation criteria. ! For outsourcing services, the dilemma in China is that labor costs are low, so the cost effectiveness of outsourcing, especially by global vendors, is not apparent. Clients' IT environments are currently very complicated and non-transparent; it is hard to realize vendors' technical and management expertise in such situation. Consulting services should be provided to help improve the IT operation level first, and then try selective outsourcing to build up trust before continuing to outsource more. Managed services are also a very smart way to solve the control preference of clients in China. ! In the long run, utility services will be well received by users due to their significant cost effectiveness and high expertise, which is difficult to maintain in an internal IT department.R o o m 611,Bei j i n g T ime sSqu a re88 W e stC h a n g 'a n A ven u e B ei j i n g 100031 P eo p l e 'sR e p u b l i co f C h i n a P .86.10.8391.3610T A B L E O F C O N T E N T SPIn This Stud y 1 Methodology (1)Situat ion Overview 1Global Sourcing Impact (1)User Demand and Buying Behavior (2)IT Services Overview (6)IT Services by Submarket (8)IT Services by Industry (14)IT Services by Region (15)Competitive Landscape (16)Future Ou tlook17Forecast and Assumptions (17)Future Trends (26)China IT Services Road Map (26)Market Context (29)Essential Gu idance30Advice to Technical Product Services Providers (30)Advice to Consulting Firms and Systems Integrators (31)Advice to Outsourcing Players (32)Learn Mo re32Related Research (32)Definitions (32)IT Services Foundation Market Definitions (32)Regional Markets (35)IDC #CN221105Q ©2008L I S T O F T A B L E SP1 Top 10 China IT Services Providers, 2007 (17)2 China IT Services Spending by Foundation Market, 2007–2012 (US$M) (18)3 Key Forecast Assumptions for the China IT Service Market, 2008–2012 (19)4 China IT Services Spending, 2005–2012: Comparison of July 2008 and September 2007Forecasts (US$M) (29)5 China Regional Market Definitions, 2007 (35)©2008 IDC #CN221105QL I S T O F F I G U R E SP1 Economic Analysis of Global Sourcing (2)2 Competition Models of Products and Services (3)3 Use of a Third Party or an Outside Vendor for Managed Services (4)4 Reasons for Maintaining In-House IT Services Management (5)5 Selection Criteria for IT Services Providers (6)6 China IT Services Life Cycle (7)7 China and United States Different Outsourcing Stages (8)8 China IT Services Spending and Year-on-Year Growth Rate by Foundation Market,2007–2012 (9)9 China Consulting and Systems Integration Growth Rate and Share, 2007 (10)10 China Outsourcing Growth Rate and Share, 2007 (12)11 China Technology Product Services Growth Rate and Share, 2007 (13)12 China IT Services Market Spending by Industry, 2007 (15)13 China IT Services Market Spending by Geography, 2007 (16)14 China IT Services Road Map (27)15 China IT Services Spending, 2005–2012: Comparison of July 2008 and September 2007Forecasts (30)IDC #CN221105Q ©2008I N T H I S S T U D YThis IDC study provides an overview of the status of the China IT services marketand a forecast for the next five years. The study also includes a demand-sideanalysis, a competitive landscape with top vendors' rankings, as well as a segmentanalysis. IDC also provides recommendations for services providers in each ITservices segment.M e t h o d o l o g yThis study is part of the continuous effort by IDC to research the China IT servicesmarket. IDC China services analysts get secondary information from, but are notlimited to, the following: the Internet, trade publications, previous IDC research, andIDC's proprietary database. Both primary and secondary research approaches areused in conjunction with each other to validate and cross-check information, asfollows:! Interviews with IT services providers. IDC China Services analysts interview all significant participants in the IT services market to determine the marketrevenue and other relevant information. Most interviews were conducted inperson, although other data-collection methods, such as telephone or faxinterviews, were applied when needed.! Provider briefings, press releases, and other publicly available information.IDC services analysts meet with a large number of service providers (SPs)semiannually. These briefings provide an opportunity to review current and futureservice offering strategies, revenue, customer bases, target markets, and otherkey market information.Ultimately, the data presented herein represents IDC's best estimates based on theabove data sources, reported and observed activity by providers, and furthermodeling of data that we believe to be true to fill in any information gaps.Note: All numbers in this study may not be exact due to rounding.S I T U A T I O N O V E R V I E WG l o b a l S o u r c i n g I m p a c tChina's IT services market is facing both domestic demand and offshore opportunity.With global sourcing becoming a strategic decision of companies to lower costsand enhance core competencies, the country boundary among services is blurring.Figure 1 illustrates the economic analysis and the impacts of global sourcing.For sourcing countries (e.g. the United States), clients there can enjoy lower pricesdue to the increase of supply from offshore vendors. The equilibrium point will movefrom point E to point E', where clients will have a greater surplus, while U.S. domesticvendors' surplus in the sourcing country will decrease. Thus, United States–basedglobal vendors like IBM and HP keep on building global delivery centers to solve thechallenge.©2008 IDC #CN221105Q 1O u t sou r cin g M a rke tAs many organizations are completing the first round of IT infrastructure implementation, they are shifting their focus on how to improve business efficiency and realize reliable business continuity (BC). After years of market cultivation and informing clients about the benefits of IT outsourcing services, organizations are more welcoming of professional services from outsourcing vendors and of buying into a model of business value improvement rather than just pure cost reduction through outsourcing.The China outsourcing market reached US$1,098.2 million in 2007, with a year-on-year growth of 36.2%. As for the current outsourcing market, we forecast it will evolve both in service expansion and project complexity. Organizations that have adopted outsourcing models are usually taking leading positions among the competition and are pioneering technology innovation. They are ready to entrust more projects with professional service vendors if they truly benefit from this model. The incremental market for outsourcing services will continue to boom on the similar track of the current existing market, and will generate more business from the China SME market. Requirements for outsourcing in the SME market will take more time to improve to maturity, but the huge customer base provides large business potential for this market. Local channels that have a wide social network and deep understanding of local potential customers will stand more chances to gain business from the local SME market. These traits are considered an important alliance necessary to leading IT outsourcing service vendors wanting deep market penetration.Big organizations that have a clear outsourcing strategy and streamlined business processes are capable of purchasing IS outsourcing (ISO) services to realize economies of scale and to transfer more management responsibility to vendors. Most organizations in the SME market are inclined to start outsourcing business from noncore or low-level transactional projects with vendors that match them in size and price. In the outsourcing market, we have observed that both global and local IT outsourcing vendors are struggling to find the right place that suits their scale and capability. Leading vendors target organizations demanding strategic and highly integrated services, while other small vendors improve themselves by collaborating with local small businesses. Interestingly, in taking advantage of China's rapid economic growth, many small businesses in China are experiencing their own dramatic growth and are willing to extend cooperation to existing vendors rather than launch new vendor selection campaigns, given the vendors fulfill their business requirement. This customer preference helps local outsourcing vendors expand their service coverage, deepen their industry knowledge, and therefore improve their competitive edge in the outsourcing field.Many services providers have launched series of services, such as IBM, Bluex, and Lenovo-Sunny services. These service offerings make it easier for customers to choose what they should buy when they encounter problems.With an increased reliance on software and hardware for mission-critical operational environments, enterprises prefer to contact support providers whenever a problem occurs — regardless of when or where it happens. Therefore, many support providers continue to launch advanced support services to better fulfill their customers' requirements.Increasingly, enterprises are looking for a single point of contact for their enterprise software and hardware support services. To meet the customers' needs, more and more SPs are carrying on multivendor support services to enrich their multibrand maintenance technical ability.To ensure peak performance and reliability of the entire IT system, an enterprise must implement a comprehensive strategy to support its IT environment. The product manufacturers are continuing innovation on the form of support services. Along with the fierce market competition, they have gradually been breaking away from being a single product support provider, and are tending to change into professional and personal value-added service (VAS) providers.In addition, product manufacturers try to penetrate tier 4 or 5 cities and expand their footprints. They are scrambling for service channels and entrusting them with more product-related services to penetrate local industry-centric markets and fulfill customers' needs.Beyond traditional customer training, vendors are making more efforts in channel education as channels gain value and become more important to vendors.IT Services by IndustryThe industry segmentation of the 2007 China IT services market was similar to that in 2006; the top 4 industries contributed 80% to the total market revenue. The top 4 industries include finance, communications and media, manufacturing, and government.In most of the industries, the growth engine came from the SME sector. The SME segment is unique because of its approach to purchasing IT solutions, particularly in terms of the emphasis on price. As such, vendors need to increase the number of channel partners and provide solutions/services to help drive growth in this market. There are strong growth opportunities in the SME market, including smaller cities. However, the uniqueness of the SME market coming from price sensitivity, limited IT demand, and flexible IT requirements still poses challenges for IT services providers.Figure 12 shows various industry shares in overall IT services spending in 2007.Accenture maintained its high and healthy growth in 2007. Continuing the strategy ofproviding business consulting services for resources, power, and telecom industriessharpened its business focus and made its market position clear. Accenture alsoprovides IT outsourcing services after implementing SI services for industry clients.AsiaInfo is a newcomer to the top 10 list. AsiaInfo mainly provides CRM, networkmanagement solutions, CAD, consulting, and SI services to the telecom industry.It enjoyed growth of 27.6% in 2007 over 2006. China's telecom industry marketis inclined to change from being demand driven to being layout driven; thisreorganization and realignment of the telecom industry along with the emergence of3G will bring more opportunities.Table 1 shows the revenue and market share of the top 10 IT SPs in China in 2007.T A B L E1T o p10C h i n a I T S e r v i c e s P r o v i d e r s,2007Ranking Vendor Revenue (US$M) Market Share (%)Services 533.1 6.1 Global1 IBM2 HP 314.9 3.6China 221.9 2.63 Digital4 Huawei 179.0 2.15 Accenture 105.0 1.2Technology 82.9 1.0 Dongli6 CE7 Neusoft 78.2 0.98 Dell 67.9 0.89 CS&S 66.3 0.810 AsiaInfo 60.9 0.7 Others 6,970.9 80.3 Total 8,681.0 100.0Note: The total market size in this table includes both primary and secondary markets. Therefore, the total market size islarger than the 2007 services market size. The primary market represents the IT services spending from the client and thesecondary market represents the IT services revenue from the vendor's subcontracting.Source: IDC, 2008F U T U R E O U T L O O KF o r e c a s t a n d A s s u m p t i o n sTable 2 shows the expected expenditures in the various foundations within the overallIT services market in China from 2007 to 2012.T A B L E 2C h i n a I T S e r v i c e s S p e n d i n g b y F o u n d a t i o n M a r k e t , 2007–2012 (U S $M )2007 2008 2009 2010 2011 2012 2007–2012CAGR (%)C&SICAD 1,110.3 1,307.4 1,491.8 1,690.6 1,913.4 2,178.1 14.4 IT consulting 311.7 373.6 440.3 535.5 650.9 795.8 20.6 SI 1,814.9 2,146.6 2,498.4 2,948.9 3,457.0 4,054.6 17.4 C&SI total 3,236.9 3,827.6 4,430.5 5,174.9 6,021.3 7,028.5 16.8 C&SI growth 25.9% 18.2% 15.8% 16.8% 16.4% 16.7% Outsourcing Application management 140.0 193.3 262.1 346.0 431.9 541.8 31.1 Desktop management 285.6 371.4 482.0 612.0 762.3 940.4 26.9 Hosted application management 100.1 128.9 157.1 199.0 249.4 307.1 25.1 Hosted infrastructure services 119.0 150.7 185.4 220.7 262.7 309.9 21.1 IS outsourcing 214.0 261.7 319.3 385.5 454.0 522.4 19.5 Network management 239.5 319.6 412.1 525.4 666.4 806.6 27.5 Outsourcing total1,098.2 1,425.7 1,818.0 2,288.6 2,826.6 3,428.2 25.6 Outsourcing growth (%) 36.2 29.8 27.5 25.9 23.5 21.3 TPSHardware deployment & support 1,390.0 1,556.5 1,713.8 1,900.7 2,123.7 2,350.9 11.1IT education & training 481.8 529.6 587.0 652.0 723.0 788.8 10.4 NCIS 842.9 930.2 1,007.5 1,084.8 1,192.0 1,298.3 9.0 Software deployment & support 649.4 784.6 922.9 1,071.4 1,240.6 1,443.417.3TPS total 3,364.0 3,800.8 4,231.2 4,708.8 5,279.3 5,881.3 11.8 TPS growth (%) 17.5 13.0 11.3 11.3 12.1 11.4 Grand total 7,699.1 9,054.1 10,479.812,172.414,127.216,338.016.2Grand total growth rate (%)23.417.615.716.216.115.6Note: See table 3 for key forecast assumptions.Source: IDC, 2008Table 3 is a look at the key assumptions for the China IT services market.K e y F o r e c a s t A s s u m p t i o n s f o r t h e C h i n a I T S e r v i c e M a r k e t,2008–2012Market Force IDC Assumption Impact Accelerator/Inhibitor/NeutralCertainty ofAssumptionMacroeconomicsGross domestic product (GDP) growth China maintained high GDPgrowth of 11.4% in 2007. Thisgrowth is expected to slowdown slightly in 2008,decreasing to 9.6%. Althoughgrowth in 2008 was adjustedto lower than the previousestimates due to theslowdown in the globaleconomy, it will be backed bystrong domestic demand.Domestic consumption willremain firm, with acceleratinggovernment spending anddemand in rural areas playingsignificant roles.Moderate. IDC assumes thatmore effective measures takenby the government will helpreduce the risk of economicoverheating and thus have nomajor impact on most ITmarkets. A strong and healthyeconomy will translate intoincreased overall IT spendingaccompanied by improvedbusiness sentiments andconfidence as well asexpanded domestic market.↔###$$U.S. recession The global economic outlookis increasingly grim as effectsof the housing meltdowncontinue to spread and creditconditions remain difficult.Contrary to previous IDC'sassumptions that the UnitedStates might be able to pullitself back from falling into arecession, the possibility of arecession is increasinglypossible. As the U.S.economy continues tocontract, it is likely that it willslide into a mild recession,and will stagnate throughmuch in 2009. Low. While some export-intensive countries mayexperience a squeeze, there isenough domestic demandacross most countries in theregion to sustain IDC's ongoingIT spending forecasts. Anynegative effects from the UnitedStates might even be a goodthing in helping to ease somepotentially overheatingcountries in the region.↓###$$Interest rates Up until December 25, 2007,China's central bank hadincreased the deposit rate by5.5% after 10 adjustmentsand increased the interest rateby 1.62%, intervening sixtimes in total. Thesemeasures were taken to keepconsumer prices from risingtoo fast and to turn around thesituation of negative interestrates. In 2008, the interestrate will keep rising under thepressure of inflation. Moderate. The continualincreasing interest rates willmake bank loans moreexpensive and thus makecompanies cautious inexpanding IT investments.↓##$$$K e y F o r e c a s t A s s u m p t i o n s f o r t h e C h i n a I T S e r v i c e M a r k e t,2008–2012Market Force IDC Assumption Impact Accelerator/Inhibitor/NeutralCertainty ofAssumptionInflation The pork crisis largely droveup China's consumer priceindex (CPI) in 2007 and wasconsidered a signal of generalinflation. The CPI recorded itshighest levels in 11 years,reaching 6.9%, bringing theaverage annual CPI to 4.8%.The China government hasmade the task of avoidingoverall inflation a high priorityin 2008. Low. Expectations of highinflation are becoming moreentrenched among the public,and demand-driven inflationarypressures will remain relativelystrong in 2008. Nonetheless,the average inflation isexpected to fall slightly after thewidely celebrated Lunar NewYear, as demand for porkeases. Inflation will not impactIT spending patterns to a largeextent.↓###$$China's yuan revaluation Revaluations of the yuan mayoccur again in the future,although they would mostlikely occur very gradually, ifat all.Low. Even if anotherrevaluation occurs, there will beno major disruptions to theeconomy as a result (both forChina itself as well as othercountries in the region thattrade heavily with China).↓###$$Urbanization The government has devoteditself to facilitatingurbanization in the next fiveyears. Three initiatives includeincreasing the urbanproportion in the totalpopulation, increasing thenumber of cities, and reducingthe gap between urban andrural areas by improving theeconomy, culture, and livingenvironment in thecountryside. High. The standard of living inthe countryside will beimproved, and the consumptionof and investment in IT willincrease, especially in SouthChina and East China. Closingthe gap between the urban andrural areas together will alsohelp reinforce social stability.↑####$Foreign direct investment (FDI) The increasing FDI in China isstrongly fueling economicgrowth. This trend is expectedto continue for the next 2–3years.High. Increasing FDI isbolstering stable andsustainable infrastructureinvestments as well as rapidgrowth in spending in the ITservice market. Joint venturesand foreign-owned enterprises(FOEs) are more inclined toadopt IT services comparedwith state-owned enterprises(SOEs) and privately ownedenterprises (POEs).↑###$$K e y F o r e c a s t A s s u m p t i o n s f o r t h e C h i n a I T S e r v i c e M a r k e t,2008–2012Market Force IDC Assumption Impact Accelerator/Inhibitor/NeutralCertainty ofAssumptionMarket ecosystemMinistry of Information Industry (MII) 11th Five-Year Plan The MII has set its 2006–2010five year IT plan. The strategyof "information technologygives an impetus toindustrialization andindustrialization promotesinformation technology " putsthe IT industry as a toppriority, and technology will beencouraged to be used widelyin all economic and socialfields to promote economicstructure adjustment andindustrial development.Low. This plan has littlesurprises but imposes anoptimistic atmosphere for the ITservices market.↑####$IT for SMEs The SME segment is uniquebecause of its approach topurchasing IT solutions,particularly in terms of theemphasis on price. As such,vendors need to increase thenumber of channel partnersand provide solutions/servicesto help drive growth in thissegment. Moderate. There are stronggrowth opportunities in theSME market, including smallcities. However, the uniquenessof the SME market in pricesensitivity, limited IT demand,and flexible IT requirements stillpose challenges for IT serviceproviders.↑####$2008 Summer Olympics The 2008 Summer Olympicswill be held in China in August2008. This will not only serveas a healthy economicstimulus but will also requireservice providers to preparefor hosting and relevant SIprojects.Moderate. The games will fuelservice industries such astourism, hotel and restaurant,B2C, and online trading.As such, service enterpriseswill invest more in ecommerceor SaaS to enable moreefficient and effective accessfor consumers.↑###$$Technology/Service developmentsGlobal sourcing Both domestic and pure-playoffshore providers areincreasing their globalsourcing sophistication inChina, allowing forhigher-quality levels at lowerblended rates. Additionally,these benefits andexperiences are being passedonto local services markets asthey increase. Moderate. The maturation ofoffshore offerings will increasethe overall market opportunityby allowing existing customersto expand the scope of theircontracts and by allowing newcustomers to utilize servicesthat were previously tooexpensive; the price pressureswill negate much (but not all) ofthat effect on the overallservices markets.↔###$$K e y F o r e c a s t A s s u m p t i o n s f o r t h e C h i n a I T S e r v i c e M a r k e t,2008–2012Market Force IDC Assumption Impact Accelerator/Inhibitor/NeutralCertainty ofAssumptionNevertheless, the net impact of increased market opportunity will somewhat outweigh decreased prices.On-demand/Utility computing Technologies such asvirtualization and gridcomputing will enable thedelivery of real "pay by thedrink" computing by bothtraditional outsourcers andnew entrants. Thisdevelopment will begin toaffect the traditionaloutsourcing market as well asother infrastructure-intensiveservices markets.Moderate. The impact will below for the near term (twoyears) as adoption takes hold.These technologies will affectprofitability as opposed torevenue in the near term.Competition and lower costswill stimulate demand andaccelerate migration frominternal to external spending.This service model will bepopular among SMEs since ithelps them realizeinformatization with limited ITbudgets.↑###$$Industry restructuring One of current revolutionaryfocus areas for organizationsis optimizing industry structure— weakening high resource-costing, labor-intensive, andlow added-value industrieswhile encouraging efficient,high-tech, and highadded-value industries.Moderate. The transformationfrom external to internaleconomic growth will giveconfidence to high-techindustries, led by theinformation industry, to reachstrategic heights as the driverof structural change andgrowth.↑###$$Security and BC services Security is in demand bysectors such as ebusiness,government, and legal inChina. Both local andmultinational vendors are thusaddressing security and BC.Moderate. This shouldstimulate both hardware andtotal solution demand.Purchases of consulting andimplementation andoutsourcing with high security,BC, and disaster recovery (DR)will increase, including interestfrom the egovernment, army,and police sectors.↑###$$K e y F o r e c a s t A s s u m p t i o n s f o r t h e C h i n a I T S e r v i c e M a r k e t,2008–2012Market Force IDC Assumption Impact Accelerator/Inhibitor/NeutralCertainty ofAssumptionDynamic IT IDC has identified the nextstyle of computing — dynamicIT for dynamic enterprises —as one that dramaticallyincreases the effectiveness ofIT. Dynamic IT will supportboth business strategy and IToperational efficiency through12 key technologies. Withindynamic IT are a number ofimportant subtrends —virtualization in thedatacenter, data federation,and composite and rule-basedapplication. Transition todynamic IT will be slow andlabored but will proceednonetheless. High. Dynamic IT, by addingcoherence to the enterpriseusage of IT, will spur the ITservices market. However,confusing choices forenterprises and funding hurdlesfor a new infrastructure willbalance this impetus to marketgrowth. ↑###$$Software The software market will keepdouble-digit growth in the nextfive years, and many hotsolutions like SOA and ITservice management (ITSM)will increase the convergencebetween software andservices. Moderate. Software-relatedservices, such as softwaredeployment and support,software implementation, andconsulting services, willincrease.↑###$$SOA To implement services-oriented, architecture-typeprojects and increasebusiness agility, clients need afair amount of consulting andimplementation services tobuild an architecture based onits business process and tointegrate it with legacysystems. High. SOA movement will driveservices market growth rapidly.↑###$$Market environment The increased adoption of thehosting application model andthe number of enterprisedatacenters, as well as thecontinual drop in internetcosts, are providing a positiveenvironment for outsourcingservice providers to developtheir business. High. A favorable marketenvironment will accelerategrowth in IT services market.↑####$。
ANSYS收购LSTC带来的技术优势_20190916(2)(1)(2)
文章来源：安世亚太官方订阅号（搜索：peraglobal）1、ANSYS收购LSTC公司9月11日，ANSYS公司（纳斯达克：ANSS）宣布：已经签订最终协议，收购了美国LSTC公司（Livermore Software Technology Corporation）。
英文版通告原文：PITTSBURGH, Sept. 11, 2019 /PRNewswire/ —ANSYS(ANSS), the global leader and innovator of engineering simulation software, announced today that it has entered into a definitive agreement to acquire Livermore Software Technology Corporation (LSTC), the premier provider of explicit dynamics and other advanced finite element analysis technology. Once closed, the acquisition will empower ANSYS customers to solve a new class of engineering challenges, including developing safer automobiles, aircraft and trains while reducing or even eliminating the need for costly physical testing. The purchase price for the transaction is $775 million, of which 60% of the consideration will be paid in cash and 40% will be paid through the issuance of ANSYS common stock to the current owners of LSTC. In conjunction with the transaction, ANSYS anticipates obtaining new debt financing to fund all or a significant portion of the cash component of the purchase price.此次ANSYS收购LSTC公司是继2005年收购显式算法为核心的CDI公司（旗下有AUTODYN、ASAS、AQWA、AutoReaGas等软件工具）后的又一世界顶级CAE产品的收购。
OSHA现场作业手册说明书
DIRECTIVE NUMBER: CPL 02-00-150 EFFECTIVE DATE: April 22, 2011 SUBJECT: Field Operations Manual (FOM)ABSTRACTPurpose: This instruction cancels and replaces OSHA Instruction CPL 02-00-148,Field Operations Manual (FOM), issued November 9, 2009, whichreplaced the September 26, 1994 Instruction that implemented the FieldInspection Reference Manual (FIRM). The FOM is a revision of OSHA’senforcement policies and procedures manual that provides the field officesa reference document for identifying the responsibilities associated withthe majority of their inspection duties. This Instruction also cancels OSHAInstruction FAP 01-00-003 Federal Agency Safety and Health Programs,May 17, 1996 and Chapter 13 of OSHA Instruction CPL 02-00-045,Revised Field Operations Manual, June 15, 1989.Scope: OSHA-wide.References: Title 29 Code of Federal Regulations §1903.6, Advance Notice ofInspections; 29 Code of Federal Regulations §1903.14, Policy RegardingEmployee Rescue Activities; 29 Code of Federal Regulations §1903.19,Abatement Verification; 29 Code of Federal Regulations §1904.39,Reporting Fatalities and Multiple Hospitalizations to OSHA; and Housingfor Agricultural Workers: Final Rule, Federal Register, March 4, 1980 (45FR 14180).Cancellations: OSHA Instruction CPL 02-00-148, Field Operations Manual, November9, 2009.OSHA Instruction FAP 01-00-003, Federal Agency Safety and HealthPrograms, May 17, 1996.Chapter 13 of OSHA Instruction CPL 02-00-045, Revised FieldOperations Manual, June 15, 1989.State Impact: Notice of Intent and Adoption required. See paragraph VI.Action Offices: National, Regional, and Area OfficesOriginating Office: Directorate of Enforcement Programs Contact: Directorate of Enforcement ProgramsOffice of General Industry Enforcement200 Constitution Avenue, NW, N3 119Washington, DC 20210202-693-1850By and Under the Authority ofDavid Michaels, PhD, MPHAssistant SecretaryExecutive SummaryThis instruction cancels and replaces OSHA Instruction CPL 02-00-148, Field Operations Manual (FOM), issued November 9, 2009. The one remaining part of the prior Field Operations Manual, the chapter on Disclosure, will be added at a later date. This Instruction also cancels OSHA Instruction FAP 01-00-003 Federal Agency Safety and Health Programs, May 17, 1996 and Chapter 13 of OSHA Instruction CPL 02-00-045, Revised Field Operations Manual, June 15, 1989. This Instruction constitutes OSHA’s general enforcement policies and procedures manual for use by the field offices in conducting inspections, issuing citations and proposing penalties.Significant Changes∙A new Table of Contents for the entire FOM is added.∙ A new References section for the entire FOM is added∙ A new Cancellations section for the entire FOM is added.∙Adds a Maritime Industry Sector to Section III of Chapter 10, Industry Sectors.∙Revises sections referring to the Enhanced Enforcement Program (EEP) replacing the information with the Severe Violator Enforcement Program (SVEP).∙Adds Chapter 13, Federal Agency Field Activities.∙Cancels OSHA Instruction FAP 01-00-003, Federal Agency Safety and Health Programs, May 17, 1996.DisclaimerThis manual is intended to provide instruction regarding some of the internal operations of the Occupational Safety and Health Administration (OSHA), and is solely for the benefit of the Government. No duties, rights, or benefits, substantive or procedural, are created or implied by this manual. The contents of this manual are not enforceable by any person or entity against the Department of Labor or the United States. Statements which reflect current Occupational Safety and Health Review Commission or court precedents do not necessarily indicate acquiescence with those precedents.Table of ContentsCHAPTER 1INTRODUCTIONI.PURPOSE. ........................................................................................................... 1-1 II.SCOPE. ................................................................................................................ 1-1 III.REFERENCES .................................................................................................... 1-1 IV.CANCELLATIONS............................................................................................. 1-8 V. ACTION INFORMATION ................................................................................. 1-8A.R ESPONSIBLE O FFICE.......................................................................................................................................... 1-8B.A CTION O FFICES. .................................................................................................................... 1-8C. I NFORMATION O FFICES............................................................................................................ 1-8 VI. STATE IMPACT. ................................................................................................ 1-8 VII.SIGNIFICANT CHANGES. ............................................................................... 1-9 VIII.BACKGROUND. ................................................................................................. 1-9 IX. DEFINITIONS AND TERMINOLOGY. ........................................................ 1-10A.T HE A CT................................................................................................................................................................. 1-10B. C OMPLIANCE S AFETY AND H EALTH O FFICER (CSHO). ...........................................................1-10B.H E/S HE AND H IS/H ERS ..................................................................................................................................... 1-10C.P ROFESSIONAL J UDGMENT............................................................................................................................... 1-10E. W ORKPLACE AND W ORKSITE ......................................................................................................................... 1-10CHAPTER 2PROGRAM PLANNINGI.INTRODUCTION ............................................................................................... 2-1 II.AREA OFFICE RESPONSIBILITIES. .............................................................. 2-1A.P ROVIDING A SSISTANCE TO S MALL E MPLOYERS. ...................................................................................... 2-1B.A REA O FFICE O UTREACH P ROGRAM. ............................................................................................................. 2-1C. R ESPONDING TO R EQUESTS FOR A SSISTANCE. ............................................................................................ 2-2 III. OSHA COOPERATIVE PROGRAMS OVERVIEW. ...................................... 2-2A.V OLUNTARY P ROTECTION P ROGRAM (VPP). ........................................................................... 2-2B.O NSITE C ONSULTATION P ROGRAM. ................................................................................................................ 2-2C.S TRATEGIC P ARTNERSHIPS................................................................................................................................. 2-3D.A LLIANCE P ROGRAM ........................................................................................................................................... 2-3 IV. ENFORCEMENT PROGRAM SCHEDULING. ................................................ 2-4A.G ENERAL ................................................................................................................................................................. 2-4B.I NSPECTION P RIORITY C RITERIA. ..................................................................................................................... 2-4C.E FFECT OF C ONTEST ............................................................................................................................................ 2-5D.E NFORCEMENT E XEMPTIONS AND L IMITATIONS. ....................................................................................... 2-6E.P REEMPTION BY A NOTHER F EDERAL A GENCY ........................................................................................... 2-6F.U NITED S TATES P OSTAL S ERVICE. .................................................................................................................. 2-7G.H OME-B ASED W ORKSITES. ................................................................................................................................ 2-8H.I NSPECTION/I NVESTIGATION T YPES. ............................................................................................................... 2-8 V.UNPROGRAMMED ACTIVITY – HAZARD EVALUATION AND INSPECTION SCHEDULING ............................................................................ 2-9 VI.PROGRAMMED INSPECTIONS. ................................................................... 2-10A.S ITE-S PECIFIC T ARGETING (SST) P ROGRAM. ............................................................................................. 2-10B.S CHEDULING FOR C ONSTRUCTION I NSPECTIONS. ..................................................................................... 2-10C.S CHEDULING FOR M ARITIME I NSPECTIONS. ............................................................................. 2-11D.S PECIAL E MPHASIS P ROGRAMS (SEP S). ................................................................................... 2-12E.N ATIONAL E MPHASIS P ROGRAMS (NEP S) ............................................................................... 2-13F.L OCAL E MPHASIS P ROGRAMS (LEP S) AND R EGIONAL E MPHASIS P ROGRAMS (REP S) ............ 2-13G.O THER S PECIAL P ROGRAMS. ............................................................................................................................ 2-13H.I NSPECTION S CHEDULING AND I NTERFACE WITH C OOPERATIVE P ROGRAM P ARTICIPANTS ....... 2-13CHAPTER 3INSPECTION PROCEDURESI.INSPECTION PREPARATION. .......................................................................... 3-1 II.INSPECTION PLANNING. .................................................................................. 3-1A.R EVIEW OF I NSPECTION H ISTORY .................................................................................................................... 3-1B.R EVIEW OF C OOPERATIVE P ROGRAM P ARTICIPATION .............................................................................. 3-1C.OSHA D ATA I NITIATIVE (ODI) D ATA R EVIEW .......................................................................................... 3-2D.S AFETY AND H EALTH I SSUES R ELATING TO CSHO S.................................................................. 3-2E.A DVANCE N OTICE. ................................................................................................................................................ 3-3F.P RE-I NSPECTION C OMPULSORY P ROCESS ...................................................................................................... 3-5G.P ERSONAL S ECURITY C LEARANCE. ................................................................................................................. 3-5H.E XPERT A SSISTANCE. ........................................................................................................................................... 3-5 III. INSPECTION SCOPE. ......................................................................................... 3-6A.C OMPREHENSIVE ................................................................................................................................................... 3-6B.P ARTIAL. ................................................................................................................................................................... 3-6 IV. CONDUCT OF INSPECTION .............................................................................. 3-6A.T IME OF I NSPECTION............................................................................................................................................. 3-6B.P RESENTING C REDENTIALS. ............................................................................................................................... 3-6C.R EFUSAL TO P ERMIT I NSPECTION AND I NTERFERENCE ............................................................................. 3-7D.E MPLOYEE P ARTICIPATION. ............................................................................................................................... 3-9E.R ELEASE FOR E NTRY ............................................................................................................................................ 3-9F.B ANKRUPT OR O UT OF B USINESS. .................................................................................................................... 3-9G.E MPLOYEE R ESPONSIBILITIES. ................................................................................................. 3-10H.S TRIKE OR L ABOR D ISPUTE ............................................................................................................................. 3-10I. V ARIANCES. .......................................................................................................................................................... 3-11 V. OPENING CONFERENCE. ................................................................................ 3-11A.G ENERAL ................................................................................................................................................................ 3-11B.R EVIEW OF A PPROPRIATION A CT E XEMPTIONS AND L IMITATION. ..................................................... 3-13C.R EVIEW S CREENING FOR P ROCESS S AFETY M ANAGEMENT (PSM) C OVERAGE............................. 3-13D.R EVIEW OF V OLUNTARY C OMPLIANCE P ROGRAMS. ................................................................................ 3-14E.D ISRUPTIVE C ONDUCT. ...................................................................................................................................... 3-15F.C LASSIFIED A REAS ............................................................................................................................................. 3-16VI. REVIEW OF RECORDS. ................................................................................... 3-16A.I NJURY AND I LLNESS R ECORDS...................................................................................................................... 3-16B.R ECORDING C RITERIA. ...................................................................................................................................... 3-18C. R ECORDKEEPING D EFICIENCIES. .................................................................................................................. 3-18 VII. WALKAROUND INSPECTION. ....................................................................... 3-19A.W ALKAROUND R EPRESENTATIVES ............................................................................................................... 3-19B.E VALUATION OF S AFETY AND H EALTH M ANAGEMENT S YSTEM. ....................................................... 3-20C.R ECORD A LL F ACTS P ERTINENT TO A V IOLATION. ................................................................................. 3-20D.T ESTIFYING IN H EARINGS ................................................................................................................................ 3-21E.T RADE S ECRETS. ................................................................................................................................................. 3-21F.C OLLECTING S AMPLES. ..................................................................................................................................... 3-22G.P HOTOGRAPHS AND V IDEOTAPES.................................................................................................................. 3-22H.V IOLATIONS OF O THER L AWS. ....................................................................................................................... 3-23I.I NTERVIEWS OF N ON-M ANAGERIAL E MPLOYEES .................................................................................... 3-23J.M ULTI-E MPLOYER W ORKSITES ..................................................................................................................... 3-27 K.A DMINISTRATIVE S UBPOENA.......................................................................................................................... 3-27 L.E MPLOYER A BATEMENT A SSISTANCE. ........................................................................................................ 3-27 VIII. CLOSING CONFERENCE. .............................................................................. 3-28A.P ARTICIPANTS. ..................................................................................................................................................... 3-28B.D ISCUSSION I TEMS. ............................................................................................................................................ 3-28C.A DVICE TO A TTENDEES .................................................................................................................................... 3-29D.P ENALTIES............................................................................................................................................................. 3-30E.F EASIBLE A DMINISTRATIVE, W ORK P RACTICE AND E NGINEERING C ONTROLS. ............................ 3-30F.R EDUCING E MPLOYEE E XPOSURE. ................................................................................................................ 3-32G.A BATEMENT V ERIFICATION. ........................................................................................................................... 3-32H.E MPLOYEE D ISCRIMINATION .......................................................................................................................... 3-33 IX. SPECIAL INSPECTION PROCEDURES. ...................................................... 3-33A.F OLLOW-UP AND M ONITORING I NSPECTIONS............................................................................................ 3-33B.C ONSTRUCTION I NSPECTIONS ......................................................................................................................... 3-34C. F EDERAL A GENCY I NSPECTIONS. ................................................................................................................. 3-35CHAPTER 4VIOLATIONSI. BASIS OF VIOLATIONS ..................................................................................... 4-1A.S TANDARDS AND R EGULATIONS. .................................................................................................................... 4-1B.E MPLOYEE E XPOSURE. ........................................................................................................................................ 4-3C.R EGULATORY R EQUIREMENTS. ........................................................................................................................ 4-6D.H AZARD C OMMUNICATION. .............................................................................................................................. 4-6E. E MPLOYER/E MPLOYEE R ESPONSIBILITIES ................................................................................................... 4-6 II. SERIOUS VIOLATIONS. .................................................................................... 4-8A.S ECTION 17(K). ......................................................................................................................... 4-8B.E STABLISHING S ERIOUS V IOLATIONS ............................................................................................................ 4-8C. F OUR S TEPS TO BE D OCUMENTED. ................................................................................................................... 4-8 III. GENERAL DUTY REQUIREMENTS ............................................................. 4-14A.E VALUATION OF G ENERAL D UTY R EQUIREMENTS ................................................................................. 4-14B.E LEMENTS OF A G ENERAL D UTY R EQUIREMENT V IOLATION.............................................................. 4-14C. U SE OF THE G ENERAL D UTY C LAUSE ........................................................................................................ 4-23D.L IMITATIONS OF U SE OF THE G ENERAL D UTY C LAUSE. ..............................................................E.C LASSIFICATION OF V IOLATIONS C ITED U NDER THE G ENERAL D UTY C LAUSE. ..................F. P ROCEDURES FOR I MPLEMENTATION OF S ECTION 5(A)(1) E NFORCEMENT ............................ 4-25 4-27 4-27IV.OTHER-THAN-SERIOUS VIOLATIONS ............................................... 4-28 V.WILLFUL VIOLATIONS. ......................................................................... 4-28A.I NTENTIONAL D ISREGARD V IOLATIONS. ..........................................................................................4-28B.P LAIN I NDIFFERENCE V IOLATIONS. ...................................................................................................4-29 VI. CRIMINAL/WILLFUL VIOLATIONS. ................................................... 4-30A.A REA D IRECTOR C OORDINATION ....................................................................................................... 4-31B.C RITERIA FOR I NVESTIGATING P OSSIBLE C RIMINAL/W ILLFUL V IOLATIONS ........................ 4-31C. W ILLFUL V IOLATIONS R ELATED TO A F ATALITY .......................................................................... 4-32 VII. REPEATED VIOLATIONS. ...................................................................... 4-32A.F EDERAL AND S TATE P LAN V IOLATIONS. ........................................................................................4-32B.I DENTICAL S TANDARDS. .......................................................................................................................4-32C.D IFFERENT S TANDARDS. .......................................................................................................................4-33D.O BTAINING I NSPECTION H ISTORY. .....................................................................................................4-33E.T IME L IMITATIONS..................................................................................................................................4-34F.R EPEATED V. F AILURE TO A BATE....................................................................................................... 4-34G. A REA D IRECTOR R ESPONSIBILITIES. .............................................................................. 4-35 VIII. DE MINIMIS CONDITIONS. ................................................................... 4-36A.C RITERIA ................................................................................................................................................... 4-36B.P ROFESSIONAL J UDGMENT. ..................................................................................................................4-37C. A REA D IRECTOR R ESPONSIBILITIES. .............................................................................. 4-37 IX. CITING IN THE ALTERNATIVE ............................................................ 4-37 X. COMBINING AND GROUPING VIOLATIONS. ................................... 4-37A.C OMBINING. ..............................................................................................................................................4-37B.G ROUPING. ................................................................................................................................................4-38C. W HEN N OT TO G ROUP OR C OMBINE. ................................................................................................4-38 XI. HEALTH STANDARD VIOLATIONS ....................................................... 4-39A.C ITATION OF V ENTILATION S TANDARDS ......................................................................................... 4-39B.V IOLATIONS OF THE N OISE S TANDARD. ...........................................................................................4-40 XII. VIOLATIONS OF THE RESPIRATORY PROTECTION STANDARD(§1910.134). ....................................................................................................... XIII. VIOLATIONS OF AIR CONTAMINANT STANDARDS (§1910.1000) ... 4-43 4-43A.R EQUIREMENTS UNDER THE STANDARD: .................................................................................................. 4-43B.C LASSIFICATION OF V IOLATIONS OF A IR C ONTAMINANT S TANDARDS. ......................................... 4-43 XIV. CITING IMPROPER PERSONAL HYGIENE PRACTICES. ................... 4-45A.I NGESTION H AZARDS. .................................................................................................................................... 4-45B.A BSORPTION H AZARDS. ................................................................................................................................ 4-46C.W IPE S AMPLING. ............................................................................................................................................. 4-46D.C ITATION P OLICY ............................................................................................................................................ 4-46 XV. BIOLOGICAL MONITORING. ...................................................................... 4-47CHAPTER 5CASE FILE PREPARATION AND DOCUMENTATIONI.INTRODUCTION ............................................................................................... 5-1 II.INSPECTION CONDUCTED, CITATIONS BEING ISSUED. .................... 5-1A.OSHA-1 ................................................................................................................................... 5-1B.OSHA-1A. ............................................................................................................................... 5-1C. OSHA-1B. ................................................................................................................................ 5-2 III.INSPECTION CONDUCTED BUT NO CITATIONS ISSUED .................... 5-5 IV.NO INSPECTION ............................................................................................... 5-5 V. HEALTH INSPECTIONS. ................................................................................. 5-6A.D OCUMENT P OTENTIAL E XPOSURE. ............................................................................................................... 5-6B.E MPLOYER’S O CCUPATIONAL S AFETY AND H EALTH S YSTEM. ............................................................. 5-6 VI. AFFIRMATIVE DEFENSES............................................................................. 5-8A.B URDEN OF P ROOF. .............................................................................................................................................. 5-8B.E XPLANATIONS. ..................................................................................................................................................... 5-8 VII. INTERVIEW STATEMENTS. ........................................................................ 5-10A.G ENERALLY. ......................................................................................................................................................... 5-10B.CSHO S SHALL OBTAIN WRITTEN STATEMENTS WHEN: .......................................................................... 5-10C.L ANGUAGE AND W ORDING OF S TATEMENT. ............................................................................................. 5-11D.R EFUSAL TO S IGN S TATEMENT ...................................................................................................................... 5-11E.V IDEO AND A UDIOTAPED S TATEMENTS. ..................................................................................................... 5-11F.A DMINISTRATIVE D EPOSITIONS. .............................................................................................5-11 VIII. PAPERWORK AND WRITTEN PROGRAM REQUIREMENTS. .......... 5-12 IX.GUIDELINES FOR CASE FILE DOCUMENTATION FOR USE WITH VIDEOTAPES AND AUDIOTAPES .............................................................. 5-12 X.CASE FILE ACTIVITY DIARY SHEET. ..................................................... 5-12 XI. CITATIONS. ..................................................................................................... 5-12A.S TATUTE OF L IMITATIONS. .............................................................................................................................. 5-13B.I SSUING C ITATIONS. ........................................................................................................................................... 5-13C.A MENDING/W ITHDRAWING C ITATIONS AND N OTIFICATION OF P ENALTIES. .................................. 5-13D.P ROCEDURES FOR A MENDING OR W ITHDRAWING C ITATIONS ............................................................ 5-14 XII. INSPECTION RECORDS. ............................................................................... 5-15A.G ENERALLY. ......................................................................................................................................................... 5-15B.R ELEASE OF I NSPECTION I NFORMATION ..................................................................................................... 5-15C. C LASSIFIED AND T RADE S ECRET I NFORMATION ...................................................................................... 5-16。
ISO 26262-4
Reference numberISO 26262-4:2011(E)© ISO 2011INTERNATIONALSTANDARD ISO 26262-4First edition2011-11-15Road vehicles — Functional safety —Part 4: Product development at the system levelVéhicules routiers — Sécurité fonctionnelle —Partie 4: Développement du produit au niveau du systèmeISO 26262-4:2011(E)COPYRIGHT PROTECTED DOCUMENT © ISO 2011All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical,including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body in the country of the requester.ISO copyright office Case postale 56CH-1211 Geneva 20 Tel. + 41 22 749 01 11Fax + 41 22 749 09 47E-mail copyright@Web Published in Switzerlandii © ISO 2011 – All rights reservedISO 26262-4:2011(E)Contents PageForeword (v)Introduction ........................................................................................................................................................ v i 1Scope (1)2Normative references (2)3Terms, definitions and abbreviated terms (2)4Requirements for compliance (2)4.1General requirements (2)4.2Interpretations of tables (3)4.3ASIL-dependent requirements and recommendations (3)5Initiation of product development at the system level (3)5.1Objectives (3)5.2General (4)5.3Inputs to this clause (6)5.4Requirements and recommendations (6)5.5Work products (6)6Specification of the technical safety requirements (7)6.1Objectives (7)6.2General (7)6.3Inputs to this clause (7)6.4Requirements and recommendations (7)6.5Work products (10)7System design (10)7.1Objectives (10)7.2General (11)7.3Inputs to this clause (11)7.4Requirements and recommendation (11)7.5Work products (16)8Item integration and testing (16)8.1Objectives (16)8.2General (16)8.3Inputs to this clause (16)8.4Requirements and recommendation (17)8.5Work products (25)9Safety validation (25)9.1Objectives (25)9.2General (25)9.3Inputs to this clause (26)9.4Requirements and recommendation (26)9.5Work products (27)10Functional safety assessment (28)10.1Objectives (28)10.2General (28)10.3Inputs to this clause (28)10.4Requirements and recommendation (28)10.5Work products (28)11Release for production (28)© ISO 2011 – All rights reserved iiiISO 26262-4:2011(E)11.1Objectives (28)11.2General (29)11.3Inputs to this clause (29)11.4Requirements and recommendations (29)11.5Work products (30)Annex A (informative) Overview and document flow of product development at the system level (31)Annex B (informative) Example contents of hardware-software interface (33)Bibliography (36)iv © ISO 2011 – All rights reservedISO 26262-4:2011(E)ForewordISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.The main task of technical committees is to prepare International Standards. Draft International Standards adopted by the technical committees are circulated to the member bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote.Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights.ISO 26262-4 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 3, Electrical and electronic equipment.ISO 26262 consists of the following parts, under the general title Road vehicles — Functional safety: Part 1: VocabularyPart 2: Management of functional safetyPart 3: Concept phasePart 4: Product development at the system levelPart 5: Product development at the hardware levelPart 6: Product development at the software levelPart 7: Production and operationPart 8: Supporting processesPart 9: Automotive Safety Integrity Level (ASIL)-oriented and safety-oriented analysesPart 10: Guideline on ISO 26262© ISO 2011 – All rights reserved vISO 26262-4:2011(E)IntroductionISO 26262 is the adaptation of IEC 61508 to comply with needs specific to the application sector of electrical and/or electronic (E/E) systems within road vehicles.This adaptation applies to all activities during the safety lifecycle of safety-related systems comprised of electrical, electronic and software components.Safety is one of the key issues of future automobile development. New functionalities not only in areas such as driver assistance, propulsion, in vehicle dynamics control and active and passive safety systems increasingly touch the domain of system safety engineering. Development and integration of these functionalities will strengthen the need for safe system development processes and the need to provide evidence that all reasonable system safety objectives are satisfied.With the trend of increasing technological complexity, software content and mechatronic implementation, there are increasing risks from systematic failures and random hardware failures. ISO 26262 includes guidance to avoid these risks by providing appropriate requirements and processes.System safety is achieved through a number of safety measures, which are implemented in a variety of technologies (e.g. mechanical, hydraulic, pneumatic, electrical, electronic, programmable electronic) and applied at the various levels of the development process. Although ISO 26262 is concerned with functional safety of E/E systems, it provides a framework within which safety-related systems based on other technologies can be considered. ISO 26262:a) provides an automotive safety lifecycle (management, development, production, operation, service,decommissioning) and supports tailoring the necessary activities during these lifecycle phases;b) provides an automotive-specific risk-based approach to determine integrity levels [Automotive SafetyIntegrity Levels (ASIL)];c) uses ASILs to specify applicable requirements of ISO 26262 so as to avoid unreasonable residual risk;d) provides requirements for validation and confirmation measures to ensure a sufficient and acceptablelevel of safety being achieved;e) provides requirements for relations with suppliers.Functional safety is influenced by the development process (including such activities as requirements specification, design, implementation, integration, verification, validation and configuration), the production and service processes and by the management processes.Safety issues are intertwined with common function-oriented and quality-oriented development activities and work products. ISO 26262 addresses the safety-related aspects of development activities and work products.Figure 1 shows the overall structure of this edition of ISO 26262. ISO 26262 is based upon a V-model as a reference process model for the different phases of product development. Within the figure:the shaded “V”s represent the interconnection between ISO 26262-3, ISO 26262-4, ISO 26262-5, ISO 26262-6 and ISO 26262-7;the specific clauses are indicated in the following manner: “m-n”, where “m” represents the number of the particular part and “n” indicates the number of the clause within that part.EXAMPLE “2-6” represents Clause 6 of ISO 26262-2.vi © ISO 2011 – All rights reservedISO 26262-4:2011(E)Figure 1 — Overview of ISO 26262© ISO 2011 – All rights reserved viiINTERNATIONAL STANDARD ISO 26262-4:2011(E)© ISO 2011 – All rights reserved1Road vehicles — Functional safety —Part 4: Product development at the system level1 ScopeISO 26262 isintended to be applied to safety-related systems that include one or more electrical and/or electronic (E/E)systems and that are installed in series production passenger cars with a maximum gross vehicle mass up to 3 500 kg. ISO 26262 does not addressunique E/E systems in special purpose vehicles such as vehicles designed for drivers with disabilities.Systems andtheir components released for production, or systems and their components already under developmentprior to the publication date of ISO 26262, are exempted from the scope. For further developmentor alterations based on systems and their components released for production prior to the publication of ISO 26262, only the modifications will be developed in accordance with ISO 26262.ISO 26262 addressespossible hazards caused by malfunctioning behaviour of E/E safety-related systems, including interaction of these systems. It does not address hazards related to electric shock, fire, smoke, heat, radiation, toxicity,flammability, reactivity, corrosion, release of energy and similar hazards, unless directly caused by malfunctioning behaviour of E/E safety-related systems.ISO 26262 doesnot address the nominal performance of E/E systems, even if dedicated functional performancestandards exist for these systems (e.g. active and passive safety systems, brake systems, Adaptive Cruise Control).This part of ISO 26262 specifies the requirements for product development at the system level for automotive applications, including the following:requirements for the initiation of product development at the system level,specification of the technical safety requirements,the technical safety concept,system design,item integration and testing,safety validation,functional safety assessment, andproduct release.ISO 26262-4:2011(E)2 Normative referencesThe following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.ISO 26262-1:2011, Road vehicles — Functional safety — Part 1: VocabularyISO 26262-2:2011, Road vehicles — Functional safety — Part 2: Management of functional safetyISO 26262-3:2011, Road vehicles — Functional safety — Part 3: Concept phaseISO 26262-5:2011, Road vehicles — Functional safety — Part 5: Product development at the hardware levelISO 26262-6:2011, Road vehicles — Functional safety — Part 6: Product development at the software levelISO 26262-7:2011, Road vehicles — Functional safety — Part 7: Production and operationISO 26262-8:2011, Road vehicles — Functional safety — Part 8: Supporting processesISO 26262-9:2011, Road vehicles — Functional safety — Part 9: Automotive Safety Integrity Level (ASIL)-oriented and safety-oriented analyses3 Terms, definitions and abbreviated termsFor the purposes of this document, the terms, definitions and abbreviated terms given in ISO 26262-1:2011 apply.4 Requirements for compliance4.1 General requirementsWhen claiming compliance with ISO 26262, each requirement shall be complied with, unless one of the following applies:a) tailoring of the safety activities in accordance with ISO 26262-2 has been planned and shows that therequirement does not apply, orb) a rationale is available that the non-compliance is acceptable and the rationale has been assessed inaccordance with ISO 26262-2.Information marked as a “NOTE” or “EXAMPLE” is only for guidance in understanding, or for clarification of the associated requirement, and shall not be interpreted as a requirement itself or as complete or exhaustive.The results of safety activities are given as work products. “Prerequisites” are information which shall be available as work products of a previous phase. Given that certain requirements of a clause are ASIL-dependent or may be tailored, certain work products may not be needed as prerequisites.“Further supporting information” is information that can be considered, but which in some cases is not required by ISO 26262 as a work product of a previous phase and which may be made available by external sources that are different from the persons or organizations responsible for the functional safety activities.2 © ISO 2011 – All rights reserved4.2 Interpretations of tablesTables are normative or informative depending on their context. The different methods listed in a table contribute to the level of confidence in achieving compliance with the corresponding requirement. Each method in a table is eithera) a consecutive entry (marked by a sequence number in the leftmost column, e.g. 1, 2, 3), orb) an alternative entry (marked by a number followed by a letter in the leftmost column, e.g. 2a, 2b, 2c).For consecutive entries, all methods shall be applied as recommended in accordance with the ASIL. If methods other than those listed are to be applied, a rationale shall be given that these fulfil the corresponding requirement.For alternative entries, an appropriate combination of methods shall be applied in accordance with the ASIL indicated, independent of whether they are listed in the table or not. If methods are listed with different degrees of recommendation for an ASIL, the methods with the higher recommendation should be preferred. A rationale shall be given that the selected combination of methods complies with the corresponding requirement.NOTE A rationale based on the methods listed in the table is sufficient. However, this does not imply a bias for or against methods not listed in the table.For each method, the degree of recommendation to use the corresponding method depends on the ASIL and is categorized as follows:“++” indicates that the method is highly recommended for the identified ASIL;“+” indicates that the method is recommended for the identified ASIL;“o” indicates that the method has no recommendation for or against its usage for the identified ASIL.4.3 ASIL-dependent requirements and recommendationsThe requirements or recommendations of each subclause shall be complied with for ASIL A, B, C and D, if not stated otherwise. These requirements and recommendations refer to the ASIL of the safety goal. If ASIL decomposition has been performed at an earlier stage of development, in accordance with ISO 26262-9:2011, Clause 5, the ASIL resulting from the decomposition shall be complied with.If an ASIL is given in parentheses in ISO 26262, the corresponding subclause shall be considered as a recommendation rather than a requirement for this ASIL. T his has no link with the parenthesis notation related to ASIL decomposition.5 Initiation of product development at the system level5.1 ObjectivesThe objective of the initiation of the product development at the system level is to determine and plan the functional safety activities during the individual subphases of system development. This also includes the necessary supporting processes described in ISO 26262-8.This planning of system-level safety activities will be included in the safety plan.© ISO 2011 – All rights reserved34 © ISO 2011 – All rights reserved5.2 GeneralThe necessary activities during the development of a system are given in Figure 2. After the initiation of product development and the specification of the technical safety requirements, the system design is performed. During system design the system architecture is established, the technical safety requirements are allocated to hardware and software, and, if applicable, on other technologies. In addition, the technical safety requirements are refined and requirements arising from the system architecture are added, including the hardware-software interface (HSI). Depending on the complexity of the architecture, the requirements for subsystems can be derived iteratively. After their development, the hardware and software elements are integrated and tested to form an item that is then integrated into a vehicle. Once integrated at the vehicle level, safety validation is performed to provide evidence of functional safety with respect to the safety goals.ISO 26262-5 and ISO 26262-6 describe the development requirements for hardware and software. This part of ISO 26262 applies to both the development of systems and subsystems. Figure 3 is an example of a system with multiple levels of integration, illustrating the application of this part of ISO 26262, ISO 26262-5 and ISO 26262-6.NOTE 1 Table A.1 provides an overview of objectives, prerequisites and work products of the particular subphases of product development at the system level.ײ·¬·¿¬·±² ±º °®±¼«½¬ ¼»ª»´±°³»²¬ ¿¬ ¬¸» -§-¬»³ ´»ª»´ìóëÍ°»½·º·½¿¬·±² ±º ¬¸» ¬»½¸²·½¿´ -¿º»¬§®»¯«·®»³»²¬-ìóê׬»³ ·²¬»¹®¿¬·±² ¿²¼ ¬»-¬·²¹ìóèÍ¿º»¬§ ª¿´·¼¿¬·±²ìóçÚ«²½¬·±²¿´ -¿º»¬§ ¿--»--³»²¬ìóïðλ´»¿-» º±® °®±¼«½¬·±²ìóïïͧ-¬»³ ¼»-·¹²ìóéﮬ ìæ Ю±¼«½¬ ¼»ª»´±°³»²¬æ -§-¬»³ ´»ª»´NOTE 2 Within the figure, the specific clauses of each part of ISO 26262 are indicated in the following manner: “m-n”, where “m” represents the number of the part and “n” indicates the number of the clause, e.g. “4-5” represents Clause 5 of ISO 26262-4.Figure 2 — Reference phase model for the development of a safety-related item© ISO 2011 – All rights reserved5NOTE Within the figure, the specific clauses of each part of ISO 26262 are indicated in the following manner: “m-n”, where “m” represents the number of the part and “n” indicates the number of the clause, e.g. “4-5” represents Clause 5 of ISO 26262-4.Figure 3 — Example of a product development at the system level5.3 Inputs to this clause5.3.1 PrerequisitesThe following information shall be available:project plan (refined) in accordance with ISO 26262-2:2011, 6.5.2;safety plan in accordance with ISO 26262-3:2011, 6.5.2;functional safety assessment plan in accordance with ISO 26262-2:2011, 6.5.4; andfunctional safety concept in accordance with ISO 26262-3:2011, 8.5.1.5.3.2 Further supporting informationThe following information can be considered:preliminary architectural assumptions (from external source); anditem definition (see ISO 26262-3:2011, 5.5).5.4 Requirements and recommendations5.4.1 The safety activities for the product development at the system level shall be planned including determination of appropriate methods and measures during design and integration.NOTE The results of planning of the verification activities during design in accordance with 6.4.6 (Verification and validation) and 7.4.8 (Verification of system design) are part of the safety plan while the planning of item integration and testing in accordance with 8.4.2 (hardware/software), 8.4.3 (element integration) and 8.4.4 (item integration) is represented in a separate item integration and testing plan in accordance with requirement 8.4.1.3.5.4.2 The validation activities shall be planned.5.4.3 The functional safety assessment activities for the product development at the system level shall be planned (see also ISO 26262-2).NOTE An example of a functional safety assessment agenda is provided in ISO 26262-2:2011, Annex E.5.4.4 The tailoring of the lifecycle for product development at system level shall be performed in accordance with ISO 26262-2, and based on the reference phase model given in Figure 2.NOTE The project plan can be used to provide the relationship between the individual subphases of product development at the system level and the hardware and software development phases. This can include the integration steps at each level.5.5 Work products5.5.1 Project plan (refined) resulting from requirement 5.4.4.5.5.2 Safety plan (refined) resulting from requirement 5.4.1 to 5.4.4.5.5.3 Item integration and testing plan resulting from requirement 5.4.1.5.5.4 Validation plan resulting from requirement 5.4.2.5.5.5 Functional safety assessment plan (refined) resulting from requirement 5.4.3.6 © ISO 2011 – All rights reserved6 Specification of the technical safety requirements6.1 ObjectivesThe first objective of this subphase is to specify the technical safety requirements. The technical safety requirements specification refines the functional safety concept, considering both the functional concept and the preliminary architectural assumptions (see ISO 26262-3).The second objective is to verify through analysis that the technical safety requirements comply with the functional safety requirements.6.2 GeneralWithin the overall development lifecycle, the technical safety requirements are the technical requirements necessary to implement the functional safety concept, with the intention being to detail the item-level functional safety requirements into the system-level technical safety requirements.NOTE Regarding the avoidance of latent faults, requirements elicitation can be performed after a first iteration of the system design subphase.6.3 Inputs to this clause6.3.1 PrerequisitesThe following information shall be available:functional safety concept in accordance with ISO 26262-3:2011, 8.5.1; andvalidation plan in accordance with 5.5.4.6.3.2 Further supporting informationThe following information can be considered:safety goals (see ISO 26262-3:2011, 7.5.2);functional concept (from external source, see ISO 26262-3:2011, 5.4.1); andpreliminary architectural assumptions (from external source, see ISO 26262-3:2011, 8.3.2).6.4 Requirements and recommendations6.4.1 Specification of the technical safety requirements6.4.1.1 The technical safety requirements shall be specified in accordance with the functional safety concept, the preliminary architectural assumptions of the item and the following system properties:a) the external interfaces, such as communication and user interfaces, if applicable;b) the constraints, e.g. environmental conditions or functional constraints; andc) the system configuration requirements.NOTE The ability to reconfigure a system for alternative applications is a strategy to reuse existing systems. EXAMPLE Calibration data (see ISO 26262-6:2011, Annex C) is frequently used to customise electronic engine control units for alternate vehicles.© ISO 2011 – All rights reserved76.4.1.2 The consistency of the preliminary architectural assumptions in ISO 26262-3:2011, 8.3.2 and the preliminary architecture assumptions in this subphase shall be ensured.6.4.1.3 If other functions or requirements are implemented by the system or its elements, in addition to those functions for which technical safety requirements are specified in accordance with 6.4.1 (Specification of the technical safety requirements), then these functions or requirements shall be specified or references made to their specification.EXAMPLE Other requirements are coming from Economic Commission for Europe (ECE) rules, Federal Motor Vehicle Safety Standard (FMVSS) or company platform strategies.6.4.1.4 The technical safety requirements shall specify safety-related dependencies between systems or item elements and between the item and other systems.6.4.2 Safety mechanisms6.4.2.1 The technical safety requirements shall specify the response of the system or elements to stimuli that affect the achievement of safety goals. This includes failures and relevant combinations of stimuli in combination with each relevant operating mode and defined system state.EXAMPLE The Adaptive Cruise Control (ACC) ECU disables the ACC functionality if informed by the brake system ECU that the Vehicle Stability Control functionality is unavailable.6.4.2.2 The technical safety requirements shall specify the necessary safety mechanisms (see ISO 26262-8:2011, Clause 6) including:a) the measures relating to the detection, indication and control of faults in the system itself;NOTE 1 This includes the self-monitoring of the system or elements to detect random hardware faults and, if appropriate, to detect systematic failures.NOTE 2 This includes measures for the detection and control of failure modes of the communication channels (e.g.data interfaces, communication buses, wireless radio link).b) the measures relating to the detection, indication and control of faults in external devices that interact withthe system;EXAMPLE External devices include other electronic control units, power supply or communication devices.c) the measures that enable the system to achieve or maintain a safe state;NOTE 3 This includes prioritization and arbitration logic in the case of conflicting safety mechanisms.d) the measures to detail and implement the warning and degradation concept; ande) the measures which prevent faults from being latent [see 6.4.4 (Avoidance of latent faults)].NOTE 4 These measures are usually related to tests that take place during power up (pre-drive checks), as in the case of measures a) to d), during operation, during power-down (post-drive checks), and as part of maintenance.6.4.2.3 For each safety mechanism that enables an item to achieve or maintain a safe state the following shall be specified:a) the transition to the safe state;NOTE 1 This includes the requirements to control the actuators.b) the fault tolerant time interval;NOTE 2 In-vehicle testing and experimentation can be used to determine the fault tolerant time interval.8 © ISO 2011 – All rights reservedc) the emergency operation interval, if the safe state cannot be reached immediately; andNOTE 3 In-vehicle testing and experimentation can be used to determine the emergency operation interval.EXAMPLE 1 Switching off can be an emergency operation.d) the measures to maintain the safe state.EXAMPLE 2 A safety mechanism for a brake-by-wire application, which depends on the power supply, can include the specification of a secondary power supply or storage device (capacity, time to activate and operate, etc.).6.4.3 ASIL Decomposition6.4.3.1 If ASIL decomposition is applied during the specification of the technical safety requirements it shall be applied in accordance with ISO 26262-9:2011, Clause 5 (Requirements decomposition with respect to ASIL tailoring).6.4.4 Avoidance of latent faults6.4.4.1 This requirement applies to ASILs (A), (B), C, and D, in accordance with 4.3: if applicable, safety mechanisms shall be specified to prevent faults from being latent.NOTE 1 Concerning random faults, only multiple-point faults have the potential to include latent faults.EXAMPLE On-board tests are safety mechanisms which verify the status of components during the different operation modes such as power-up, power-down, at runtime or in an additional test mode to detect latent faults. Valve, relay or lamp function tests that take place during power up routines are examples of such on-board tests.NOTE 2 Evaluation criteria that identify the need for safety measures preventing faults from being latent are derived in accordance with good engineering practice. The latent fault metric, given in ISO 26262-5:2011, Clause 8, provides evaluation criteria.6.4.4.2 This requirement applies to ASILs (A), (B), C, and D, in accordance with 4.3: to avoid multiple-point failures, the multiple-point fault detection interval shall be specified for each safety mechanism implemented in accordance with 6.4.4 (Avoidance of latent faults).6.4.4.3 This requirement applies to ASILs (A), (B), C, and D, in accordance with 4.3: to determine the multiple-point fault detection interval, the following parameters should be considered:a) the reliability of the hardware component with consideration given to its role in the architecture;b) the probability of exposure of the corresponding hazardous event(s);c) the specified quantitative target values for the maximum probability of violation of each safety goal due tohardware random failures (see requirement 7.4.4.3); andd) the assigned ASIL of the related safety goal.NOTE The use of the following measures depends on the time constraints:periodic testing of the system or elements during operation;on board tests of elements during power-up or power-down; andtesting the system or elements during maintenance.© ISO 2011 – All rights reserved9。
IBM SPSS Modeler 18.2.2 用户指南说明书
517操作说明书
05pmii选择复印纸23预设缩小放大24缩放24分页25更改份数26用单面纸复印身份证两面用户工具用户工具菜单系统设置29用户工具菜单复印机设置31访问用户工具32更改默认设置32退出用户工具33可以通过用户工具更改的设置34系统设置34复印机功能37用户代码39注册新的用户代码39更改用户代码40删除用户代码40显示每个用户代码的计数器41打印每个用户代码的计数器41清除计数器故障排除如果本机不能正常工作43复印件不清晰44无法正常复印45内存空间用尽时45b装入纸张46装入纸张46方向固定的纸张或双面纸张47d添加碳粉48处理碳粉48碳粉存放48用过的碳粉48取出碳粉49加碳粉50kirc3azhopebookpageiiwednesdaymarch20103
PandaC4cpyZH_Cover1.fm Page 1 Sunday, April 25, 2010 8:43 AM
soaring团队微软收购诺基亚(终极版)
案例分析——微软收购诺基亚MADE BY——Soaring目录1.微软收购诺基亚背景 (4)1.1微软简介 (4)1.2诺基亚简介 (4)1.3微软收购诺基亚事件 (5)2.微软收购诺基亚的原因分析 (5)2.1微软收购原因 (5)2.2诺基亚被收购原因 (5)3.微软收购诺基亚的环境分析 (6)3.1宏观环境（PEST) (6)3.2微观分析(SWTO) (7)4.微软收购诺基亚的影响 (9)4.1对微软影响 (9)5.微软收购诺基亚的未来趋势 (10)6.我们给微软的建议 (10)1.微软收购诺基亚背景1.1微软简介微软（Microsoft Corporation)是一家基于美国的跨国电脑科技公司。
创建于1975年，是世界个人和商用计算机软件行业的领袖。
微软公司为用户提供范围广泛的产品和服务，并通过优秀的软件予人们在任何时间、任何地点、通过任何设备进行沟通的能力。
以研发、制造、授权和提供广泛的电脑软件服务业务为主。
总部位于美国华盛顿州的雷德蒙德，最为著名和畅销的产品为Microsoft Windows操作系统和Microsoft Office系列软件。
Windows Phone是微软发布的一款手机操作系统，它将微软旗下的Xbox LIVE 游戏、Zune音乐与独特的视频体验整合至手机中。
2010年10月11日晚上9点30分，微软公司正式发布了智能手机操作系统Windows Phone。
微软的巨大潜力已经渗透到了软件界的方方面面，简直是无孔不入，而且是所向披靡。
公司目前在60多个国家设有分公司，全世界雇员人数近91,000人。
1.2诺基亚简介诺基亚公司（Nokia Corporation）是一家总部位于芬兰埃斯波主要从事生产移动通信产品的跨国公司，诺基亚公司（Nokia Corporation）是一家世界著名的移动通信产品制造商，创始于1865年，1871年组建为诺基亚公司，总部位于芬兰的Espoo。
系统开发计划表
项目编号：01<正大软件项目管理系统>项目开发计划version：项目承担部门：软件一系.net项目组撰写人（签名）：郑孝宗完成日期：2007年7月23日本文档使用部门：□主管领导□项目组□客户（市场）□维护人员□用户评审负责人（签名）：评审日期：普耀科技公司,2007 修订历史记录copyright ? 重庆正大普耀科技有限公司, all right reserved 目录1. 引言.............................................................................. ........................................................ 1 1.1编写目的 ............................................................................. ................................................ 1 1.2项目简介 ............................................................................. ................................................ 1 1.2.1项目名称 ............................................................................. ............................................. 1 1.2.2产品标识 ............................................................................. ............................................. 1 1.2.3项目背景 ............................................................................. ............................................. 1 1.3定义 ............................................................................. ....................................................... 1 1.4参考资料 ............................................................................. ................................................ 1 2 项目概述.............................................................................. ................................................. 1 2.1 2.2 2.3 2.4 工作内容.............................................................................. .......................................... 2 项目进度和资源 ............................................................................. ................................ 2 交付项和非交付项.............................................................................. ............................ 2 其他需求与约束 ............................................................................. .. (2)3. 项目组织和资....................................... 2 3.1 项目组织.............................................................................. .......................................... 2 3.2 项目资源.............................................................................. ............ 错误！未定义书签。
ATA8-AST Draft Rev.3__T13
Working Draft ProjectAmerican National T13/1697-D StandardRevision 3February 25,2010 Information technology -AT Attachment 8 - ATA/ATAPI Serial Transport(ATA8-AST)This is a draft proposed American National Standard of Accredited Standards Committee INCITS. As such this is not a completed standard. The T10 Technical Committee may modify this document as a result of comments received during public review and its approval as a standard. Use of the information contained here in is at your own risk.Permission is granted to members of INCITS, its technical committees, and their associated task groups to reproduce this document for the purposes of INCITS standardization activities without further permission, provided this notice is included. All other rights are reserved. Any commercial or for-profit replication or republication is prohibited.T13 Technical Editor: John GeldmanLexar Media, Inc. (A subsidiary of Micron Technology, Inc.)47300 Bayside ParkwayFremont, CA 94538USATelephone:510-580-8715Email: jgeldman@Reference numberISO/IEC xxxx-xxx:200xANSI INCITS ***-200xT13/1697-D Revision 3February 25,2010 Points of ContactT13 Chair T13 Vice chairDan Colgrove Jim HatfieldHitachi Global Storage Technologies Seagate Technology2903 Carmelo Dr389 Disc DriveHenderson, NV 89502Longmont CO 80503Tel:702-614-6119Tel:720-684-2120Fax:702-614-7955Fax:720-684-2722INCITS SecretariatNCITS Secretariat Tel: 202-737-88881101 K Street NW, Suite 610Fax: 202-638-4922Washington, DC 20005Email: INCITS@T13 ReflectorSee the T13 Web Site at for reflector information.T13 Web SiteDocument DistributionINCITS Online Store /incits.htmlmanaged by Techstreet Telephone: 1-734-780-80003916 Ranchero Dr. or 1-800-699-9277Ann Arbor, MI 48108 Facsimile: 1-734-780-2046orGlobal Engineering /H15 Inverness Way East Telephone: 1-303-792-2181Englewood, CO 80112-5704 or 1-800-854-7179Facsimile: 1-303-792-2192American National Standardfor Information Technologyii Working Draft AT Attachment 8 - ATA/ATAPI Serial Transport (ATA8-AST)February 25,2010 T13/1697-D Revision 3DraftSecretariatInformation Technology Industry CouncilApproved mm.dd.yyAmerican National Standards Institute, Inc.ABSTRACTThis standard specifies the AT Attachment command set between host systems and storage devices. It provides a common command set for systems manufacturers, system integrators, software suppliers, and suppliers of intelligent storage devices. It includes the PACKET feature set implemented by devices commonly known as ATAPI devices. This standard maintains a high degree of compatibility with the AT Attachment Interface with Packet Interface - 7 (ATA/ATAPI-7) volume 1, INCITS 397-2004, and while providing additional functions, is not intended to require changes to devices or software that comply with previous T13 standards.DraftWorking Draft AT Attachment 8 - ATA/ATAPI Serial Transport (ATA8-AST)iiiT13/1697-D Revision 3February 25,2010iv Working Draft AT Attachment 8 - ATA/ATAPI Serial Transport (ATA8-AST)Published byAmerican National Standards Institute11 W. 42nd Street, New York, New York 10036Copyright © 2009 by Information Technology Industry Council (ITI).All rights reserved.No part of this publication may by reproduced in anyform, in an electronic retrieval system or otherwise,without prior written permission of ITI, 1250 Eye Street NW, Suite 200,Washington, DC 20005.Printed in the United States of AmericaAmerican National Standard Approval of an American National Standard requires verification by ANSI that therequirements for due process, consensus, and other criteria for approval have been met by the standards developer. Consensus is established when, in the judgment of the ANSI Boardof Standards Review, substantial agreement has been reached by directly and materially affected interests. Substantial agreement means much more than a simple majority, but notnecessarily unanimity. Consensus requires that all views and objections be considered, and that effort be made towards their resolution.The use of American National Standards is completely voluntary; their existence does not inany respect preclude anyone, whether he has approved the standards or not, frommanufacturing, marketing, purchasing, or using products, processes, or procedures notconforming to the standards.The American National Standards Institute does not develop standards and will in nocircumstances give interpretation on any American National Standard. Moreover, no personshall have the right or authority to issue an interpretation of an American National Standardin the name of the American National Standards Institute. Requests for interpretationsshould be addressed to the secretariat or sponsor whose name appears on the title page ofthis standard.CAUTION NOTICE: This American National Standard may be revised or withdrawn at anytime. The procedures of the American National Standards Institute require that action betaken periodically to reaffirm, revise, or withdraw this standard. Purchasers of AmericanNational Standards may receive current information on all standards by calling or writing theAmerican National Standards Institute.The patent statement goes here.If no patents have been disclosed place the statement in 5.5.2 shall be used.If any patents have been disclosed place the statement in 5.5.3 shall be used.February 25, 2010 T13/1697-D Revision 3Document StatusDocument f10107 is the issues list for this draft. f10107 contains a list of the issues associated with the document, an issue number that remains assigned to the issue for the life of document development, a resolution to the issue, an owner for the issue, and a disposition for the issue. All major changes associated with this draft starting with Rev 1 are first documented in f10107 and given a number. This includes proposals which are targeted for inclusion into this draft.Revision HistoryRev Date Description1August 16, 20071)Used ATA8-ACSr4b as a template to port ATA8-ASTr0 + Changes to thisversion. This version should be taken as the initial proposal...2October 21, 20092)New Editor starting cleanup. There are no proposals integrated in thisversion. This version supersedes the previous initial proposals as thenew initial proposal.3February 25, 20103)Updated Issues document reference, added Acronym Section (3.2),replaced clause 4 with material accepted in T13 plenary meetings(2010-02)New Capabilities added to ATA8-ASTIntegrated Proposal List#Doc Description1234567891011121314151617181920Working Draft AT Attachment 8 - ATA/ATAPI Serial Transport (ATA8-AST)vT13/1697-D Revision 3February 25, 2010 vi Working Draft AT Attachment 8 - ATA/ATAPI Serial Transport (ATA8-AST)February 25, 2010 T13/1697-D Revision 3 ContentsPage Points of Contact (ii)Document Status (v)New Capabilities added to ATA8-AST (v)Contents (xiii)Tables (xv)Figures (xvii)Foreword (xix)Introduction (xix)1 Scope (1)2 Normative references (3)2.1 Approved references (3)2.2 References under development (3)2.3 Other references (3)3 Definitions, abbreviations, and conventions (4)3.1 Definitions and abbreviations (4)3.2 Symbols and abbreviations (9)3.3 Conventions (9)3.3.1 Overview (9)3.3.2 Precedence (9)3.3.3 Lists (9)3.3.4 Keywords (9)3.3.5 Numbering (10)3.3.6 Bit conventions (10)3.3.7 State diagram conventions (11)3.3.8 Byte, word, DWord, and QWord Relationships (12)3.3.9 ATA string convention (13)4 Mapping AAM and ACS-2 to AST (15)4.1 Mapping Overview (15)4.2 Mapping ACS-2 and SATA-2.6 fields (15)4.2.1 Mapping ACS-2 command fields into SATA-2.6 RHD FIS fields (15)4.2.2 Mapping ACS-2 Normal Outputs and Error Outputs into a RDH FIS (16)4.2.3 Mapping ACS-2 Normal Outputs and Error Outputs into a SDB FIS (17)4.3 AST specific ACS-2 Transport Dependent responses (17)4.4 Mapping of Identify Device and Identify Packet Device (18)4.5 AAM Protocols (23)4.5.1 Native Command Queuing (23)Annex A (Normative) Place Holder Annex (25)A.1 Overview (25)Working Draft AT Attachment 8 - ATA/ATAPI Serial Transport (ATA8-AST)xiiiT13/1697-D Revision 3February 25, 2010 xiv Working Draft AT Attachment 8 - ATA/ATAPI Serial Transport (ATA8-AST)February 25, 2010 T13/1697-D Revision 3 TablesPage Table 1 - Approved ANSI References (3)Table 2 - References Under Development (3)Table 3 - ATA string byte swapping (13)Table 4 - ATA firmware revision example (14)Table 5 - 28-Bit Command Mapping (15)Table 7 - 28-Bit Normal/Error Mapping (16)Table 6 - 48-Bit Command Mapping (16)Table 9 - 48-Bit Queue Aborted Mapping (17)Table 8 - 48-Bit Normal/Error Mapping (17)Table A.1 - Sample Table (25)Working Draft AT Attachment 8 - ATA/ATAPI Serial Transport (ATA8-AST)xvT13/1697-D Revision 3February 25, 2010 xvi Working Draft AT Attachment 8 - ATA/ATAPI Serial Transport (ATA8-AST)February 25, 2010 T13/1697-D Revision 3 FiguresPage Figure 1 - ATA document relationships (2)Figure 2 - State diagram convention (11)Figure 3 - Byte, word, Word and QWord relationships (12)T13/1697-D Revision 3February 25, 2010February 25, 2010 T13/1697-D Revision 3Foreword(This foreword is not part of this standard.)Requests for interpretation, suggestions for improvement and addenda, or defect reports are welcome. They should be sent to the INCITS Secretariat, ITI, 1101 K Street NW, Suite 610, Washington, DC 20005.This standard was processed and approved for submittal to ANSI by InterNational Committee for Information Technology Standards (INCITS). Committee approval of this standard does not necessarily imply that all committee members voted for approval. At the time it approved this standard, INCITS had the following members:Karen Higginbottom, ChairDavid Michael, Vice-chairMonica Vago, SecretaryTechnical Committee T13 on ATA Interfaces, that reviewed this standard, had the following members and additional participants:Dan Colegrove, ChairmanJim Hatfield, Vice-ChairmanMark Overby, SecretaryEditor’s Note 1: [Editors Note: Insert T13 Membership List Here]IntroductionThis standard encompasses the following:Clause 1 describes the scope.Clause 2 provides normative references for the entire standard.Clause 3 provides definitions, abbreviations, and conventions used within the entire standard.Clause 4 describes the mapping of ATA8-AAM and ATA8-ACS structures and resets into the Serial ATA transportT13/1697-D Revision 3February 25, 2010AMERICAN NATIONAL STANDARD BSR INCITS ***-200xAmerican National Standardfor Information Technology –AT Attachment 8 - ATA/ATAPI Serial Transport (ATA8-AST)1 ScopeThe set of AT Attachment standards consists of this standard and the ATA implementation standards described in AT Attachment - 8 ATA/ATAPI Architecture Model (ATA8-AAM). The scope of this standard is strictly limited the description of the mapping of ATA command structures, ATA command status (see ref. ATA8-ACS), ATA architecture model (see ref. ATA8-AAM), and ATA protocol model (see ref. ATA8-AAM) into the paradigm of the Serial ATA transport (see ref. Serial ATA Revision 2.6). The actual description of the Serial ATA transport, including, but not limited to, the description of:a)the physical interconnection between Serial ATA host and Serial ATA storage device(s), includingconnectors and cables;b)b) the electrical characteristics of the interconnecting signals;c)c) the logical characteristics of the interconnecting signals; ord)d) the protocols for transporting ATA commands, data, and status information using Serial ATA transportis not within the scope of this standard.This document defines the ATA Serial ATA transport by:a)referencing the Serial ATA documents published by the SATA-IO organization; andb)documenting the transport dependent components found in ATA8 family of documents.The following specifications are found in the SATA-2.6 and SATA-3.0 references:a)the mapping of ACS-2 command blocks to SATA-3.0 FIS fields;b)the physical interconnection between Serial ATA host and Serial ATA storage device(s), includingconnectors and cables;c)the electrical characteristics of the interconnecting signals; andd)the logical characteristics of the interconnecting signals.This document specifies some of the relationship between this document and multiple versions of SATA. This document specifies:a)the mapping of ACS-2 command blocks to SATA-2.6 FIS fields;b)transport dependant command parameters (see ACS-2); andc)transport dependant ATA transport dependent model components (see ATA8-AAM).T13/1697-D Revision 3February 25, 2010 Figure 1 shows the relationship of this standard to the other standards and related projects in the ATA and SCSI families of standards and specifications. Note that the SATA-2.6 and SATA-3.0 documents exist outside of thisEditor’s Note 2: <Editor’s Note: Update drawing for link between “related host...” and “otherrelated...”>Figure 1 — ATA document relationshipsFebruary 25, 2010 T13/1697-D Revision 32 Normative referencesThe following standards contain provisions that, through reference in the text, constitute provisions of this standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent editions of the standards listed below.Copies of the following documents may be obtained from ANSI: Approved ANSI standards, approved and draft international and regional standards (ISO, IEC, CEN/CENELEC, ITUT), and approved and draft foreign standards (including BSI, JIS, and DIN). For further information, contact ANSI Customer Service Department at 212-642-4900 (phone), 212-302-1286 (fax), or via the World Wide Web at .Additional availability contact information is provided below as needed.2.1 Approved referencesTable 1 lists approved ANSI standards, approved international and regional standards (ISO, IEC,CEN/CENELEC, ITUT), may be obtained from the international and regional organizations who control them. To obtain copies of these documents, contact Global Engineering or INCITS. Additional information may be available at and Table 1 — Approved ANSI ReferencesName ReferenceAT Attachment-8 – ATA Command Set (ATA8-ACS)ANSI INCITS 452:2008 SCSI Primary Commands - 3 (SPC-3)ANSI INCITS 408:2005ISO/IEC 14776-453AT Attachment-8 – ATA/ATAPI Architecture Model (ATA8-AAM)ANSI INCITS 451:2008ISO/IEC 14776-8612.2 References under developmentAt the time of publication, the following referenced standards were still under development. For information on the current status of the document, or regarding availability, contact the relevant standards body or other organization as indicated.Table 2 — References Under DevelopmentName Project Number AT Attachment-8 - Parallel Transport (ATA8-APT)INCITS 1698DISO/IEC 14776-881 AT Attachment-8 – ATA/ATAPI Architecture Model (ATA8-AAM)INCITS 1700DISO/IEC 14776-861 AT Attachment-8 – ATA Command Set 2 (ACS-2) INCITS 2015DSCSI Primary Commands - 4 (SPC-4)INCITS 1731DFor more information on the current status of the T10 documents, contact INCITS. To obtain copies of T10 or SFF documents, contact Global Engineering.2.3 Other referencesThe following specifications are also referenced.Serial ATA revision 2.6 (SATA-2.6)Copies of the SATA 2.6 specification published by SATA-IO can be obtained at Serial ATA revision 3.0 (SATA-3.0)Copies of the SATA 3.0 specification published by SATA-IO can be obtained at T13/1697-D Revision 3February 25, 2010 3 Definitions, abbreviations, and conventions3.1 Definitions and abbreviationsEditor’s Note 3: Review the use of each retained definition3.1.1 28-bit command: A command which uses Features (7:0), Count (7:0), LBA (27:0), Device (15:8) andCommand (7:0) to specify its arguments. (see 4.1)3.1.2 48-bit command: A command which uses Features (15:0), Count (15:0), LBA (47:0), Device (15:8) andCommand (7:0) to specify its arguments. (see 4.1)3.1.3 ASCII: American Standard Code for Information Interchange.3.1.4 ASCII Character: A byte containing a 7-bit ASCII pattern in bits 6:0 with bit 7 cleared to zero.3.1.5 ATA device: A device implementing the ACS-2 General feature set.3.1.6 ATA8-AST device: A device that complies with this standard.3.1.7 ATAPI (AT Attachment Packet Interface) device:ATAPI (AT Attachment Packet Interface) device: Adevice implementing the PACKET feature set.3.1.8 BIOS (Basic Input/Output System): An initial application client run by a computer when power isapplied. The primary function of BIOS is initialize various components of the system, including storage devices.3.1.9 byte: A sequence of eight contiguous bits considered as a unit. (See 3.3.8)3.1.10 cache: A data storage area outside the area accessible by application clients that may contain a subsetof the data stored in the non-volatile data storage area.3.1.11 command aborted: Command completion with ERR set to one in the Status field and ABRT set to onein the Error field.3.1.12 command acceptance: P ositive acknowledgement of a command being received by a device. See theappropriate transport standard for a definition of positive acknowledgement.3.1.13 command acceptance: Positive acknowledgement of a command being received by a device. See theappropriate transport standard for a definition of positive acknowledgement.Editor’s Note 4: We need to define “positive acknowledgement” in the SATA domain3.1.14 Command Block: In a parallel implementation this is the set of interface registers used for deliveringcommands to the device or posting status from the device. In a serial implementation, the commandblock fields are FIS payload fields.3.1.15 command completion: The completion by the device of the action requested by the command or thetermination of the command with an error, the setting of the appropriate bits in the Error field, and the set-ting of the appropriate bits in the Status field.February 25, 2010 T13/1697-D Revision 3 3.1.16 command packet: A data structure transmitted to the device during the execution of a PACKET com-mand that includes the command and command parameters.3.1.17 command released: When a device supports the TCQ feature set, a command is considered releasedwhen a release occurs before command completion.3.1.18 device: A storage-related peripheral. Traditionally, a device on the interface has been a hard disk drive,but any form of storage device may be placed on the interface provided the device adheres to this stan-dard.3.1.19 DMA (direct memory access) data transfer: A means of data transfer between device and host mem-ory without host processor intervention.A method of data transfer between a host port and the device port which does not involve application client intervention.3.1.20 DRQ data block: A unit of data words associated with available status when using either the PIO data-incommand protocol or the PIO data-out command protocol.3.1.21 Word: A sequence of four contiguous bytes considered as a unit. (See 3.3.8)3.1.22 FIS: The Frame Information Structure for the serial interface. See SATA-2.6 and SATA-3.0.3.1.23 hardware reset: the routine performed by a device after a hardware reset event as defined inATA8-AAM. The hardware reset routine performed by the device includes the actions performed by the device for a software reset, and the actions defined in ATA8-AAM, this standard, and the applicabletransport standards. The routine performed by a device after a hardware reset event as defined inATA8-AAM or a COMRESET (see SATA 3.0). The hardware reset routine performed by the deviceincludes the actions performed by the device for a software reset, and the actions defined in ATA8-AAM, this standard, and the appropriate SATA-IO specification (see SATA 3.0).3.1.24 host: The computer system executing the application client (e.g., BIOS, operating system, or devicedriver) controlling the device and the adapter hardware for the ATA interface to the device.3.1.25 host adapter: The implementation of the host transport, link, and physical layers.3.1.26 LBA (logical block address): The value used to reference a logical sector or a field used to carry a log-ical block address value.3.1.27 logical sector: A set of logical words accessed and referenced as a unit (see IDENTIFY DEVICE datawords 118:117). These units are referenced by LBA (see ).3.1.28 log: A collection of data accessed using log commands.3.1.29 log address: A numeric value that a log command uses to identify a specific log.3.1.30 log command: A SMART READ LOG command, SMART WRITE LOG command, or GPL feature setcommand.3.1.31 log page: A unit of measure for determining the size of a log. Each log page is a 512-byte block of data.A log consists of one or more pages.T13/1697-D Revision 3February 25, 2010 3.1.32 LSB (least significant bit): In a binary code, the bit or bit position with the smallest numerical weighting in a group of bits that, when taken as a whole, represent a numerical value (e.g., in the number 0001b, the bit that is set to one).3.1.33 Master Password Capability: The Master Password Capability indicates whether or not the Master password may be used to unlock the device. This was formerly know as “Security Level”.3.1.34 Media: The material on which data is stored.3.1.35 Media Access Command: Any command which causes the device to access non-volatile media.3.1.36 MSB (most significant bit): In a binary code, the bit or bit position with the largest numerical weighting in a group of bits that, when taken as a whole, represent a numerical value (e.g., in the number 1000b, the bit that is set to one).3.1.37 native max address: The highest LBA that a device accepts in the factory default condition, that is, the highest LBA that is accepted by the SET MAX ADDRESS or, if the native max is greater than 28 bits then SET MAX ADDRESS EXT.3.1.38 Non-Volatile cache: Cache that retains data through all power and reset events. Non-volatile cache shall be a subset of the non-volatile media.3.1.39 Nexus Loss Event: TBDEditor’s Note 5: AAM: 3.1.23 nexus loss event: a transport specific event where the host port is nolonger in communication with a device port (e.g., a device was removed from a computer system).This needs further work to correlate to unrecovered loss of PHYRDY.3.1.40 Non-Volatile Media: Physical storage media that retains data written to it for subsequent read opera-tions through all power and reset events (e.g., magnetic media, optical media, flash media).3.1.41 NV Cache Pinned Set: The set of logical blocks that have been made un-removable from the NV Cacheby the host. Writes to logical blocks represented in the NV Cache Pinned Set always results in valid data in the NV Cache Set.3.1.42 NV Cache Set: The set of logical blocks currently represented in the device's entire NV Cache.3.1.43 NV Cache Set Data: A data structure representing the standard format of transmitting logical blocks inthe form of a list of LBA Range Entries.3.1.44 NV Cache Unpinned Set: The set of logical blocks that are represented in the NV Cache Set but notrepresented in the NV Cache Pinned Set. The NV Cache Pinned Set and the NV Cache Unpinned Set are mutually exclusive. NV Cache Unpinned Set is completely managed by the device and logical blocks represented in the NV Cache Unpinned Set may be added or removed from the NV Cache Set at any time.3.1.45 Password Attempt Counter Exceeded: There were too many attempts to unlock the device with anincorrect password. This is a name associated with IDENTIFY DEVICE, word 128, bit 4.3.1.46 PATA: A device implementing the parallel transport, see ATA8-APT3.1.47 physical sector: One or more contiguous logical sectors that are read from or written to the devicemedia in a single operation.3.1.48 PIO (programmed input/output) data transfer: PIO data transfers are performed using PIO com-mands and protocol.3.1.49 power cycle: the period from when power is removed from a host or device until the subsequentpower-on event (see ATA8-AAM).3.1.50 power-on reset: the host specific routine performed by the host or the routine performed by a deviceafter detecting a power-on event. The power-on reset routine performed by a device includes the actions performed by the device for a hardware reset and a software reset, and the actions defined inATA8-AAM, this standard, and the applicable transport standards.3.1.51 queued: Command queuing allows the host to issue concurrent commands to the same device. Onlycommands included in the Tagged Command Queuing (TCQ) feature set may be queued. In this stan-dard, the queue contains all commands for which command acceptance has occurred but commandcompletion has not occurred.3.1.52 Queued Command: A NCQ command that has reported command acceptance but not command com-pletion.3.1.53 Word: A sequence of eight contiguous bytes considered as a unit. See 3.3.8.3.1.54 RDH FIS: Register - Device to Host FIS. See SATA-2.6 and SATA-3.03.1.55 RHD FIS: Register - Host to Device FIS. See SATA-2.6 and SATA-3.03.1.56 read command: A command that causes the device to transfer data from the device to the host. The fol-lowing commands are read commands: READ DMA, READ DMA EXT, READ DMA QUEUED, READ DMA QUEUED EXT, READ FPDMA QUEUED, READ MULTIPLE, READ MULTIPLE EXT, READ SEC-TOR(S), READ SECTOR(S) EXT, READ STREAM DMA, READ STREAM DMA EXT, READ VERIFY SECTOR(S), or READ VERIFY SECTOR(S) EXT.3.1.57 release: The action by a device implementing the TCQ feature set that allows a host to select an alter-nate device or deliver another queued command.3.1.58 SATA: A device implementing the serial transport, see ATA8-AST3.1.59 sector: See logical sector.3.1.60 Security Is Disabled: The Security feature set is supported, but there is no valid User password. Thereis a Master password. Access to user data is not restricted by the Security feature set. The terms 'Secu-rity Is Locked' and 'Security Is Unlocked' are not applicable. (e.g., Security states SEC0, SEC1, SEC2).3.1.61 Security Is Enabled: The Security feature set is supported, and a valid User password has been set.(e.g., Security states SEC3, SEC4, SEC5, SEC6).3.1.62 Security Is Frozen: Security may be either enabled or disabled. Changes to Security states are notallowed until after the next power-on or hardware reset. (e.g., Security states SEC2, SEC6).3.1.63 Security Is Locked: Security is enabled. In addition, access to the device is restricted. (e.g., Securitystate SEC4).3.1.64 Security Is Not Frozen: Security may be either enabled or disabled. Changes to Security states areallowed (e.g., Security states SEC1, SEC4, SEC5).3.1.65 Security Is Unlocked: Security is enabled. A SECURITY UNLOCK command was successful, allow-ing access to the device. (e.g., Security state SEC5, SEC6).3.1.66 Security Level: See Master Password Capability.。
IFS系统介绍
IFS 应用系统介绍................................................................................................................................................9
ifs系统介绍ifs系统win8系统功能介绍微信广告系统介绍系统介绍ppt系统介绍系统介绍ppt模板图书管理系统介绍linux系统介绍小米v6系统介绍
IFS 应用系统
功能方案
广州万迅电脑软件有限公司
广州万迅电脑软件有限公司 Tel:020-83283115 Fax:020-83283054
IFS 应用系统功能概要......................................................................................................................................10 IFS 应用系统 ......................................................................................................................................................10
SIMATIC Energy Manager PRO V7.2 - Operation Operat
2 Energy Manager PRO Client................................................................................................................. 19
2.1 2.1.1 2.1.2 2.1.3 2.1.4 2.1.5 2.1.5.1 2.1.5.2 2.1.6
Basics ................................................................................................................................ 19 Start Energy Manager ........................................................................................................ 19 Client as navigation tool..................................................................................................... 23 Basic configuration ............................................................................................................ 25 Search for object................................................................................................................ 31 Quicklinks.......................................................................................................................... 33 Create Quicklinks ............................................................................................................... 33 Editing Quicklinks .............................................................................................................. 35 Help .................................................................................................................................. 38
CRM竞品分析报告
CRM竞品分析报告目录1背景 (4)1.1行业概况 (4)1.1.1行业分类 (4)1.1.1行业现状及发展 (4)1.2竞品选择 (5)1.2.1产品直接竞争者 (5)1.2.2产品间接竞争者 (6)1.2.3资本雄厚概念炒作者 (6)1.2.4竞品选择 (6)2竞品分析 (7)2.1定位和功能 (7)2.1.1产品定位 (7)2.1.2目标用户 (7)2.1.3市场数据 (7)2.1.3.1访问量分析 (7)2.1.3.2用户画像 (8)2.1.4产品功能 (9)2.1.5交互和体验 (11)2.1.5.1客户 (11)2.1.5.2销售漏斗 (12)2.1.5.3协同办公 (16)2.1.5.4流程管理 (18)2.1.6产品框架 (21)2.2运营和商业化 (23)2.2.1盈利模式 (23)2.2.2市场覆盖 (23)2.3策略 (24)2.4优缺点总结和借鉴 (24)3总结 (25)4索引 (26)1背景1.1行业概况1.1.1行业分类随着移动互联网、云计算、大数据技术的高速发展，CRM厂商迎来了新一轮的“春天”，并已形成细分领域竞争格局：SCRM、销售自动化、客户服务类、外勤管理类。
据权威机构移动信息化研究中心2017年7月份研究数据显示，在原有细分格局领域基础上，社交因素为“常规武器”，以客户为中心的跨界融合逐步加深。
图表 1 行业分类1.1.1行业现状及发展经历2016年底资本寒冬之后，CRM资本层面回归理性，不再是“广撒网”式投资，对明星级厂商进行“集中”式投资的趋势更明显。
图表 2 资本市场同时，CRM在基于社交能力渗透基础上，PaaS平台“初露峥嵘”，定制化需求较高的企业用户逐渐转向应用移动CRM的PaaS平台，基于企业实际需求，通过公司的开发团队和移动CRM厂商的技术支持，自主开发CRM产品。
图表 3 发展现状1.2竞品选择1.2.1产品直接竞争者纷享销客、销售易、爱客CRM 等。
云智控 3.0 使用手册说明书
云智控3.0使用手册快速上手——PC端目录一、登录 (6)1.1 注册系统 (6)1.2 登录系统 (7)二、使用流程 (9)2.1 首页（MoguV） (9)2.1.1 首页概述 (9)2.1.2 MoguV编辑器 (11)2.1.2.1 页面 (11)2.1.2.2 组件 (11)2.2 设备组 (35)2.2.1 设备组列表 (35)2.2.1.1 添加设备组 (35)2.2.1.2 快速配置 (36)2.2.1.3 移动设备组位置 (39)2.2.1.4 删除设备组 (40)2.2.2 基本信息 (40)2.2.3 下属设备 (41)2.2.3.1 编辑下属设备 (41)2.2.3.2 查看设备详情 (42)2.2.4 设备组属性 (42)2.2.4.1 新增设备组属性 (42)2.2.4.2 编辑设备组属性 (43)2.2.4.3 新增自定义属性 (44)2.2.5 实时监测 (44)2.2.5.1 2D实时监测 (44)2.2.5.2 3D实时监测 (46)2.2.5.3 视频监测 (46)2.2.6 边缘智控 (47)2.2.6.1 智控算法 (47)2.2.6.2 智控参数 (54)2.2.6.3 水智控 (57)2.2.7 云端智控 (57)2.2.7.1 智控算法 (57)2.2.7.2 智控参数 (60)2.3 设备 (61)2.3.1 添加设备 (61)2.3.2 删除设备 (62)2.3.3 设备列表 (63)2.3.3.1 设备列表设置 (63)2.3.3.2 导入导出 (63)2.3.4 查看设备详情 (64)2.3.5 远程控制 (68)2.4 统计分析 (68)2.4.1 能源统计 (68)2.4.2 空压站分析 (69)2.4.2.1 效益分析 (69)2.4.2.2 气电分析 (70)2.4.2.3 能效分析 (70)2.4.2.4 浪费分析 (71)2.4.2.5 智控分析 (72)2.4.2.6 智能报告 (72)2.4.3 故障分析 (73)2.4.4 数据查询 (74)2.5 系统管理 (76)2.5.1 用户管理 (76)2.5.1.1 用户账号 (76)2.5.1.2 角色与权限 (77)2.5.1.3 登录日志 (78)2.5.1.4 操作日志 (79)2.5.2 智控管理 (79)2.5.2.1 配置文件同步 (79)2.5.2.2 边缘端控制 (80)2.5.2.3 第三方上位机协议配置 (81)2.5.2.4 智控参数日志 (83)2.5.2.5 边缘智控日志 (83)2.5.2.6 云端智控日志 (84)2.5.3 系统设置 (85)2.5.3.1 能耗单价设置 (85)2.5.3.2 通知设置 (85)2.5.3.3 第三方系统授权 (86)2.5.3.4 费用充值及账单 (87)2.5.3.5 名称与Logo (91)2.6 消息提醒 (92)2.6.1 设备提醒 (92)2.6.2 信息公告 (93)2.7 个人信息 (93)2.8 意见反馈及售后电话 (94)2.9 退出登录 (95)一、登录1.1 注册系统点击【免费注册】，输入手机号码获取验证码，无法收到验证码，点击【查看帮助】获取帮助；点击阅读【云智控使用条约】并勾选同意接受，点击【注册】进入云智控注册页面。
丹佛斯签署协议拟并购美国涡旋技术公司
离给 世界一 流的压 缩机 制造商 ，是值 得肯定 的事 件。这
与 我 们 将 压 缩 机 的 需 求 外 包 给 包 括 丹 佛 斯 在 内 的 全 球 专
字作为无含义 的 自造词汇 ，具有一定的显著性 ，故北京正 泰亚明照明科技有限公司使用 “ 正泰亚明”标识 ，易使相 关公众对该 商品的来源产生误认或认为该商品与正泰集团 股份有 限公司涉案 “ 正泰”注册商标 的相关商品有特定的 联 系。因此 ，北京正泰亚明照明科 技有 限公 司的上述涉案 行为侵 犯了涉案第 ９ ０ ４ 号 “ ５９７ 正泰”注册商 标专用权 ，应
注册商标在相关公众 中获得了一定的知名度 ，北京正泰亚
明照 明科技有 限公司 的涉 案行为 具有 利用他人商 誉的故
意 ，足以使相 关消费者对涉案产品的来源以及不同经营者 之问具有关联关系产生混淆误认 ，违反了诚实信用的基 本 原则 ，构成不正 当竞争 。
下属 开利和 江森控 制 集团的 子公 司布 里斯 托尔压 缩机 等 两 家美 国公 司合 资运营 的 。 丹佛斯 将 并购涡 旋技术 公 司 ｌ ０ ％的股 权 ，并将 继 ０ 续在现 有工厂 生产 。本次并 购的完 成还有 赖于是 否满 足 包括取 得政府 部 门的批准 等最终 条件 。本次交 易预计 将
措 ，是一次具 有历 史意义 的并 购。我 们确 信在商用 建筑
空 调 领 域 里 的 压 缩 机 市 场 上 ， 丹 佛 斯 已经 确 保 占据 非 常
有 吸引力 的地 位。 同时 ，我们 还将进 一步拓 展我 们的产 品范 围 ，提 升我 们 包括 在 民用住 宅市 场上 的市 场地 位 。
北京 正泰亚 明照 明科 技有 限公司辩称 ，被告使 用的 “ 正泰亚明”商标注册 申请 已经过初步审定并公告 ， 现该商 标处于异议审查程序 中；北京正泰亚明照明科技有 限公 司 的企业名称经合法注册 ，其 中 “ 正泰亚明”的企业字号 是
试用R&S公司EMFP解调电视发射机37MHZ中频信号
广 播 电视 国 际标 准规 定 。电视发 射 机 中频 频率 为 ３ ８ ＭＨ ， ｚ而我国 目前太多数 电视发 射机的 中颤仍 然是 ３ ｚ ７ＭＨ 。 南通 电视 台曾于 ２ ０世纪 ９ ０年代 中期 购置了该型 电视解调 器。 当初订 货时要求厂家将仪器 中频 输入通 道改为 ３ ｚ ７ＭＨ ， 未果 ． 因此 ． 该型解调器 的中颤输入通道一直 闲置未用 。 而在 调试 电视发射机技术指 标时 ， 往往需要了解已调 中频信号 中 视频信号及伴音信号的失真情况 ， 这时就不得不用到解调器
解 调 ３ ＭＨ ７ ｚ
３ 试 验结果分析
将 北广 产 １ Ｗ ＨＦ电视发 射 机 的中频 调制处 理部分 Ｕ ｋ 电视发射机中频调制器输出的中频信 号是双边带的 ， 在 频谱上 ３ ＭＨ ７ ｚ已谓 图像载频处 于右端 ． ３ ． 而 ０５ＭＨ ｚ已调伴 音 中频处于左端。经过对通带 、 阻带和过渡带都有一定要求
噪声 中：
发射机伴音通道及图像通 道的整机技术指标 。 Ｍ Ｐ Ｒ Ｓ Ｅ Ｆ 是 ＆
公司２ ０世 纪 ９ ０年 代 中 期 的产 品 ，具 体 型 号 名称 为 “ Ｖ Ｔ
Ｔ Ｓ Ｅ ＥＶ Ｒ Ｅ Ｆ ” 其解调频率范 围涵盖我 国全部电 Ｅ ＴＲ Ｃ ＩＥ ．Ｍ Ｐ 。
视频道及某些调频 频道 ， 适用 电视制式 为标 准 Ｐ ＬＤ Ｋ， Ａ － ／ 且 有两个输 入通 道 。 个是射频输 入通 道 ， 一 另一个是 中频 输人
（ ） Ｅ Ｐ的射频输 人通道来解调发 射机 ３ － ２ 用 ＭＦ ７ＭＩ ｌ ｚ中 频 信号 。即将 ３ ｚ中频信 号送入 Ｅ Ｐ的射频输 入通 ７ＭＨ ＭＦ
２ 试 验
测试平 台搭建如图 ｌ 所示 。
VMWARE RENEWAL业务介绍
潜在的预定
现状下获得的预定
议程
• • • • VMware Renewal业务的战略目标 全球支持服务 (GSS) 运营动态 Renewal中心概况和动态 Partner Central Renewal部分
概述 与 ServiceSource 合作进行维护Renewal业务
• 新的Renewal销售和渠道能力提升专家团队 • 分析和优化Renewal运营的世界级能力 • 为管理数据并为 VMware 及我们的合作伙伴提供可见性指标而 专门构建的技术基础架构
VMware Renewal业务介绍 Christopher Goo 区域支持经理，VMware, Inc.
VMware Renewal业务介绍
就绪、启动、成长！
议程
• • • • VMware Renewal业务的战略目标 全球支持服务 (GSS) 运营动态 Renewal中心概况和动态 Partner Central Renewal部分
提高了门户速度。经过数周的调整后，我们已设法在不影响Renewal中心 逻辑和质量的情况下优化了查询。您从 4 月 1 日起会注意到这一点。 共享信息。合作伙伴销售经理可以在节假日期间轻松替班，并且还可以确保 他们不会发出重复的请求。 技术支持按钮。通过超链接使合作伙伴更方便获得技术支持，该超链接将 打开新的“编写邮件”页面，其中已经为您填写好了正确的电子邮件地址。 隐藏/取消隐藏列。如果合作伙伴不想看到某些列，他们可以选择隐藏 这些列并将注意力集中于对他们重要的信息。 快速搜索。“Quarter List”（季度列表）视图中的“Quick search” （快速搜索）框使合作伙伴可以方便快捷地查找他们正在寻找的销售机会。 刷新功能。通过在所有选项卡（而不只是“Quarter List”（季度列表））中单 击“Reload”（重新加载），合作伙伴将能利用续购中心的实时数据更新。 活动报价筛选器。合作伙伴现在可以轻松识别仍然处于活动状态的报价， 同时仍然可以选择查看已经关闭的报价。