HCS All Hands 2.21.14
Festo CPX-AP-I-8DI-M8-3P商品说明书
DIN 46211:1965-03 DIN 46225:1976-12 DIN 46234:1980-03
–
2 Safety
2.1 Safety instructions
T.1 1.2 1.3 1.4 2 2.1 2.2 2.3 3 4 5 5.1 5.2 5.2.1 5.2.2 5.2.3 6 7 8 9 10 10.1 10.2 11 12
About this document................................................................................................... 4 Applicable documents.................................................................................................. 4 Product version............................................................................................................ 4 Product labelling.......................................................................................................... 4 Specified standards...................................................................................................... 5 Safety........................................................................................................................... 5 Safety instructions........................................................................................................ 5 Intended use................................................................................................................ 5 Training of qualified personnel..................................................................................... 5 Additional information................................................................................................ 5 Service.......................................................................................................................... 5 Product overview......................................................................................................... 6 Function....................................................................................................................... 6 Configuration................................................................................................................ 7
LabWindows_CVI多线程技术在多功能显示器测试软件中的应用
LabWindows/CVI多线程技术在多功能显示器测试软件中的应用发布时间：2023-03-07T02:22:58.947Z 来源：《科学与技术》2022年21期作者：杨柳暄陈涛沈晓雪[导读] 多功能显示器测试软件模拟任务管理计算机与显示器进行422通讯，实时接收显示器发送的按键杨柳暄陈涛沈晓雪(苏州长风航空电子有限公司江苏苏州215151)[摘要]多功能显示器测试软件模拟任务管理计算机与显示器进行422通讯，实时接收显示器发送的按键信息，并且向显示器发送画面信息完成画面显示。
本文针对LabWindows／CVI的多线程机制进行了详细的介绍，并给出了其在多功能显示器测试中的应用。
测试结果表明，利用多线程技术能够更好地开发并行任务，加快系统的响应速度，提高执行效率。
关键词：多线程；多功能显示器测试；LabWindows／CVI；Application of LabWindows/CVI multi-threadtechnology in multi-function display test softwareYang Liuxuan Chen Tao Shen Xiaoxue(Suzhou Changfeng Avionics co.,LTD., Suzhou Jiangsu 215151,China)Abstract: The multi-function display test software simulates the task management computer to perform 422 communication with the display, receives the key information sent by the display in real time, and sends the screen information to the display to complete the screen display. This paper introduces the multi-thread mechanism of LabWindows/CVI in detail, and gives its application in the multi-function display test. The test results show that using multi-threading technology can better develop parallel tasks, speed up the response speed of the system, and improve execution efficiency.Key words: Multithread；Multifunction Display Test；LabWindows／CVI；1.引言在多功能显示器测试过程中，需要设计相应的测试软件。
神州数码DCRS-5650交换机配置手册_端口操作
第 5 章 LLDP功能操作配置 ........................................................ 5-1
5.1 LLDP功能简介 ..................................................................................5-1 5.2 LLDP功能配置任务序列....................................................................5-1 5.3 LLDP功能典型案例 ...........................................................................5-4 5.4 LLDP功能排错帮助 ...........................................................................5-4
第 7 章 MTU配置 ....................................................................... 7-1
7.1 MTU介绍 ...........................................................................................7-1 7.2 MTU配置任务序列 ...................Байду номын сангаас........................................................7-1
9.2 bpdu-tunnel配置任务序列 ...............................................................9-1 9.3 bpdu-tunnel举例 ..............................................................................9-2 9.4 bpdu-tunnel排错帮助 .......................................................................9-3
Solaris 10操作系统商品说明书
Introducing Predictive Self-HealingThe Solaris™ 10 Operating System (OS) introduces a new architecture for building anddeploying systems and services capable of Predictive Self-Healing. This technology enables Sun™ systems to accurately predict component failures and mitigate many serious problems —before they actually occur. Solaris Fault Manager and Solaris Service Manager are the two main components of Predictive Self-Healing. Solaris Fault Manager receives data relating to hardware and software errors and automatically diagnoses the underlying problem. Once diagnosed, Solaris Fault Manager automatically responds by offlining faulty components. Solaris Service Manager makes services, rather than processes, into first-class citizens, permitting automatic self-healing. Base Solaris services have service descriptions which include full dependency information for start, stop, and restart; applications can easily be converted to run under Solaris Service Manager.Maximizing availabilityPredictive Self-Healing is designed to maximize the availability of the system and application services by automatically diagnosing, isolating, and recovering from faults. This helps to not only reduce hardware failures but also to reduce the impact of application failures,leading to increased system and application availability. •Reducing Hardware Failures—A self-healing system automatically diagnoses problems, and the results can be used to trigger auto-mated reactions such as dynamically taking a CPU,regions of memory, and I/O devices off line before these components can cause system failures. Solaris Fault Manager isolates and disables faulty components, and helps ensure continuous service even before admin-istrators know there is a problem. In addition, remote service agents can retrieve informa-tion from Sun that is vital to diagnosing the underlying root cause of the failure. •Reducing the Impact of Service Failures—If an application service should fail, the built-in service restart mechanism in the Solaris 10 OS automatically restarts the application or service. This mechanism also extends into Sun Cluster software failover environments for even higher availability.Automatic diagnosis and recoveryfrom failuresWith Solaris Fault Manager, the system auto-matically diagnoses faulty components, a function that in some cases can reduce analysis time from days to seconds. Once diagnosed, the system can quickly take corrective action and automatically restore application services. This powerful technology ensures that business-critical applications and essential system services can continue uninterrupted in the event of software failures, major hardware component failures, and even software misconfiguration problems.<Highlights•Maximized system and serviceavailability through predictivediagnosis and isolation of faultycomponents•Automatic diagnosis of failedcomponents and automaticrestart of failed services inmilliseconds•Simplified administration modelfor managing services, reducingcost of ownership•Fast and easy repair of problemswith links to knowledge articles•Scalable architecture can berapidly upgraded and adapted tonew problems — without requiringdowntimeCustomers can now deliver higher levels of availability and application services while minimizing downtime and associated adminis-trative costs. Reduced downtime can potentially save companies $10,000 to $6 million per hour for mission-critical environments.Simplified administrationSolaris Service Manager reduces complexity by abstracting problem diagnosis and services in a manner that is transparent to users and applications. It simplifies common administrative tasks, speeds system boot, and significantly reduces human errors associated with system failures that can lead to service downtime and inefficient management of the system.Admin-istrative tasks such as enabling and disabling services and changing properties are simplified and secure, with an undo capability to revert changes. In addition, service information is stored in a central repository,making the systems easier to manage and maintain. Self-healing technology can also help improve the productivity of support staff. They can now spend much less time investigating and resolving issues,resulting in a higher ratio of supported systems per individual. Plus, a self-healing system can lead to reduced administration costs — systems that perform many complex tasks without user intervention require staff with less expertise, experience, and salary.Fast and easy repairSolaris Fault Manager issues easy-to-understand diagnosis messages that link to knowledge articles at /msg. By providing system administrators with unique event IDs, they can access detailed information in knowledge articles, which describe what failure occurred and what the system did to fix it. These knowl-edge articles guide system administrators through any tasks that require human interven-tion, including repairs, and explain predicted or detected problems using clear language and links to repair procedures and documentation —all of which greatly reduces the complexity of repairing the system.Scalable and flexible architectureThe scalable architecture of Sun’s Predictive Self-Healing technology can be rapidly evolved to new problems and updated as new diagnosis and availability technologies are added to the system. Most future updates can be dynamically loaded and unloaded from the system while it is running and can be upgraded on the fly without requiring downtime or losing previous diagnosis data.ConclusionWith businesses operating around the clock and demanding uninterrupted service, service availability is of paramount importance. Predictive Self-Healing delivers the next generation of availability technology today, including features that keep systems and services running and simple for administrators. Over time, a rapidly evolving ecosystem of self-healing components can help provide consistent, easy-to-use, and always-available Sun systems.©2005 Sun Microsystems, Inc. All rights reserved. Sun, Sun Microsystems, the Sun logo, Solaris, the Solaris logo, and The Network is the Computer are trademarks or registered trademarks of Sun Microsystems, Inc. in theUnited States and other countries. Information subject to change without notice.11/05Sun Microsystems, Inc.4150 Network Circle, Santa Clara, CA 95054 USA Phone 1-650-960-1300 or 1-800-555-9SUN Web 2。
FTDI Chipi-X Cable 数据手册说明书
Chipi-X Cable DatasheetVersion 1.0Document Reference No.: FT_000634 Clearance No.: FTDI# 288Future TechnologyDevices InternationalLtdDatasheet Chipi-X CableChipi-X is a USB to full-handshake RS232 cable with a male DB9 connector. This cable isavailable with or without an enclosure.1IntroductionThe Chipi-X cable is a USB to RS232 level full-handshake UART cable. Chipi-X utilises FTDI’s FT231XS USB to full-handshake UART IC and FT3243S RS232 transceiver IC. A male DB9 (aka DE9) connector provides the connectivity for RS232 communications and a USB-A plug tethered by a 10cm cable to the PCB provides connectivity for USB communications. All components used are Pb-free (RoHS compliant).1.1 FeaturesEntire USB protocol handled on the FT232XS chipFTDI’s royalty -free VCP and D2XX drivers eliminate the requirement for USB driver development in most casesUART interface support for 7 or 8 data bits, 1 or 2 stop bits and odd / even / mark / space / no parity.Fully assisted hardware or X-On / X-Off software handshaking.Data transfer rates from 300 baud to 250 kilo-baud at RS232 voltage levels.512 byte receive buffer and 512 byte transmit buffer utilising buffer smoothing technology to allow for high data throughputAdjustable receive buffer timeout.ESD protection on RS232 I/Os exceeding ±15kV IEC1000-4-2 Air Gap Discharge, ±15kV for Human Body Mode (HBM) and ±8kV IEC1000-4-2 Contact Discharge.ESD protection on USB lines exceeding ±2kV for Human Body Mode (HBM), ±200V for Machine Mode (MM) and ±500V for Charged Device Mode (CDM).Integrated MTP-ROM for storing USB VID, PID, serial number and product description strings.Low operating and USB suspend current. Low USB bandwidth consumption. USB 2.0 Full Speed compatible. -40°C to 85°C extended operating temperature range.Latch-up FreeTable of Contents1Introduction (1)1.1Features (1)2Driver Support (3)3Ordering Information (3)4Functional Description (4)4.1Block Diagram (4)4.2Electrical Details (4)5Chipi-X Signals and Pin Out (5)5.1RS232 Signals (5)5.2USB Signals (5)6Module Dimensions (6)7Chipi-X Circuit Schematic (7)8Internal MTP ROM Configuration (8)9Contact Information (9)Appendix A – List of Tables and Figures (10)Appendix B – Revision History (11)2Driver SupportRoyalty-Free VIRTUAL COM PORT (VCP) DRIVERS for:Windows 7 32,64-bitWindows VistaWindows XP 32,64-bitWindows XP EmbeddedWindows 4.2 , 5.0 and 6.0MAC OS OS-XLinux 2.6.32 or later Android Royalty-Free D2XX Direct Drivers (USB Drivers + DLL S/W Interface):Windows 7 32,64-bitWindows VistaWindows XP 32,64-bitWindows XP EmbeddedWindows 4.2, 5.0 and 6.0MAC OS OS-XLinux 2.6.32 or later AndroidThe drivers listed above are all available to download for free from . Various 3rd Party Drivers are also available for various other operating systems - visit for details.For driver installation instructions please see:/Support/Documents/InstallGuides.htm.3Ordering Information4 Functional Description 4.1Block DiagramFigure 4.1 – Chipi-X Block Diagram4.2Electrical Details5Chipi-X Signals and Pin Out 5.1RS232 SignalsFigure 5.1 – Chipi-X DB9 Pin Out5.2 USB Signals6Module DimensionsFigure 6.1 – Chipi-X DimensionsFigure 6.2 – Enclosure DimensionsAll dimensions are given in millimetres.Chipi-X cables only use lead free components, and are fully compliant with European Union directive 2002/95/EC.7Chipi-X Circuit SchematicFigure 7.1 – Chipi-X Circuit Schematic8Internal MTP ROM ConfigurationFollowing a power-on reset or a USB reset the FT231X will scan its internal MTP ROM and read the USB configuration descriptors stored there. The default values programmed into the internal MTP ROM in theThe internal MTP ROM in the FT231X can be programmed over USB using the utility program FT_PROG. FT_PROG can be downloaded from . Users who do not have their own USB vendor ID but who would like to use a unique Product ID in their design can apply to FTDI for a free block of unique PIDs. Contact FTDI Support(*********************)forthisservice,alsosee TN_100 and TN_101.9Contact InformationHead Office – Glasgow, UKFuture Technology Devices International LimitedUnit 1, 2 Seaward Place, Centurion Business Park Glasgow G41 1HHUnited KingdomTel: +44 (0) 141 429 2777Fax: +44 (0) 141 429 2758E-mail (Sales) *******************E-mail (Support) *********************E-mail (General Enquiries) ******************* Branch Office – Taipei, TaiwanFuture Technology Devices International Limited (Taiwan) 2F, No. 516, Sec. 1, NeiHu RoadTaipei 114Taiwan , R.O.C.Tel: +886 (0) 2 8791 3570Fax: +886 (0) 2 8791 3576E-mail (Sales) **********************E-mail (Support) ************************E-mail (General Enquiries) **********************Branch Office – Hillsboro, Oregon, USA Future Technology Devices International Limited (USA) 7235 NW Evergreen Parkway, Suite 600Hillsboro, OR 97123-5803USATel: +1 (503) 547 0988Fax: +1 (503) 547 0987E-Mail (Sales) *********************E-Mail (Support) ***********************E-Mail (General Enquiries) ********************* Branch Office – Shanghai, ChinaFuture Technology Devices International Limited (China) Room 408, 317 Xianxia Road,Shanghai, 200051ChinaTel: +86 21 62351596Fax: +86 21 62351595E-mail (Sales) *********************E-mail (Support) ***********************E-mail (General Enquiries) *********************Web SiteDistributor and Sales RepresentativesPlease visit the Sales Network page of the FTDI Web site for the contact details of our distributor(s) and sales representative(s) in your country.System and equipment manufacturers and designers are responsible to ensure that their systems, and any Future Technology Devices International Ltd (FTDI) devices incorporated in their systems, meet all applicable safety, regulatory and system-level performance requirements. All application-related information in this document (including application descriptions, suggested FTDI devices and other materials) is provided for reference only. While FTDI has taken care to assure it is accurate, this information is subject to customer confirmation, and FTDI disclaims all liability for system designs and for any applications assistance provided by FTDI. Use of FTDI devices in life support and/or safety applications is entirely at the u ser’s risk, and the user agrees to defend, indemnify and hold harmless FTDI from any and all damages, claims, suits or expense resulting from such use. This document is subject to change without notice. No freedom to use patents or other intellectual property rights is implied by the publication of this document. Neither the whole nor any part of the information contained in, or the product described in this document, may be adapted or reproduced in any material or electronic form without the prior written consent of the copyright holder. Future Technology Devices International Ltd, Unit 1, 2 Seaward Place, Centurion Business Park, Glasgow G41 1HH, United Kingdom. Scotland Registered Company Number: SC136640Chipi-X Cable DatasheetVersion 1.0Document Reference No.: FT_000634 Clearance No.: FTDI# 288 Appendix A – List of Tables and FiguresList of FiguresFigure 4.1 – Chipi-X Block Diagram (4)Figure 5.1 – Chipi-X DB9 Pin Out (5)Figure 6.1 – Chipi-X Dimensions (6)Figure 6.2 – Enclosure Dimensions (6)Figure 7.1 – Chipi-X Circuit Schematic (7)List of TablesTable 3.1 – Chipi-X Ordering Information (3)Table 4.1 – Chipi-X I/O Characteristics (4)Table 4.2 – Chipi-X ESD Tolerance (4)Table 5.1 – Chipi-X RS232 Signals (5)Table 5.2 – Chipi-X USB Lines (5)Table 8.1 – Default Internal MTP ROM Configuration (8)Chipi-X Cable DatasheetVersion 1.0Document Reference No.: FT_000634 Clearance No.: FTDI# 288 Appendix B – Revision HistoryDocument Title: DS_CHIPI-XDocument Reference No.: FT_000634Clearance No.: FTDI# 288Product Page: /FT-X.htmDocument Feedback: Send FeedbackVersion 1.0 Initial Datasheet Released 14/03/12Copyright © 2012 Future Technology Devices International Limited 11。
BSHIS2.21用户手册.门诊医生站
目录第一章系统概述 (4)1.1软件功能概述 (4)1.2新增功能 (4)1.3技术特征 (5)1.4应用环境 (5)第二章系统安装 (7)2.1安装前准备 (7)2.2系统安装 (7)2.3系统卸载 (13)第三章系统登录 (15)第四章数据维护及初始化 (17)4.1初始化 (17)4.2系统选项 (17)4.3设置用户及用户权限 (19)4.4医生科室权限维护 (19)4.5发药药房维护 (20)4.6治疗方案维护 (21)4.7药品禁用维护 (23)4.8鉴别诊断维护 (25)4.9诊断代码维护 (26)4.10体征代码维护 (27)4.11病程记录维护 (29)第五章基本业务 (32)5.1新病人 (32)5.3结束就诊 (35)5.4就诊 (37)5.4.1病程列表 (37)5.4.2诊断结果 (38)5.4.3检查治疗 (41)5.4.4门诊手术 (43)5.4.5中西药方 (44)5.4.6病程记录 (49)第六章查询 (51)6.1药典查询 (51)6.2结果报告 (52)6.3手术查询 (53)6.4费用总计 (54)6.5门诊日志查询 (55)6.6门诊工作量查询 (56)第七章住院 (58)7.1住院预约 (58)7.2住院情况 (59)第八章系统 (60)8.1院内邮件 (60)8.2密码修改 (63)8.3计算器 (64)8.4工具栏 (65)8.5注销（操作员） (65)8.6退出系统 (65)第九章帮助 (67)9.1帮助 (67)第一章系统概述1.1软件功能概述门诊医生站采用下拉式汉化菜单，界面友好，实用性强，设有与门诊挂号收费系统、医技科室信息系统、住院结算信息系统的软件接口，主要功能有：就诊：对就诊病人进行诊断处理、检查治疗、处方录入及病程记录。
查询：查询就诊病人的费用总计、检查报告、门诊手术等情况，并提供药典、门诊日志、门诊工作量等查询功能。
住院：对门诊病人进行住院预约以及查询住院部的床位使用情况。
NFC论坛Tag Type 技术标准： NFCForum_TS_Type_5_Tag_1.0
Type 5 Tag Operation Technical SpecificationVersion 1.02015-07-07[T5TOP]NFC Forum TMRESTRICTIONS ON USEThis specification is copyright © 2015 by the NFC Forum, and was made available pursuant to a license agreement entered into between the recipient (Licensee) and NFC Forum, Inc. (Licensor) and may be used only by Licensee, and in compliance with the terms of that license agreement (License). If you are not the Licensee, you may read this Specification, but are not authorized to implement or make any other use of this specification. However, you may obtain a copy of this Specification and implementation rights at the following page of Licensor's website: /our-work/specifications-and-application-documents/specification-application-license/ after entering into and agreeing to such license terms as Licensor is then requiring. On the date that this specification was downloaded by Licensee, the non-implementation terms of that license were as follows:1.LICENSE GRANT.Licensor hereby grants Licensee the right, without charge, to copy (for internal purposes only, except with respect to the elements listed on Exhibit A) and share this Specification with Licensee's members, employees and (to the extent related to Licensees’ use of this Specification) consultants. This license grant does not include the right to sublicense, modify or create derivative works based upon any portion of the Specification, except for the elements listed in Exhibit A.2.NO WARRANTIES.THE SPECIFICATION IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, ACCURACY, COMPLETENESS AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL LICENSOR, ITS MEMBERS OR ITS CONTRIBUTORS BE LIABLE FOR ANY CLAIM, OR ANY DIRECT, SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THE SPECIFICATION.3.THIRD PARTY RIGHTS.Without limiting the generality of Section 2 above, LICENSOR ASSUMES NO RESPONSIBILITY TO COMPILE, CONFIRM, UPDATE OR MAKE PUBLIC ANY THIRD PARTY ASSERTIONS OF PATENT OR OTHER INTELLECTUAL PROPERTY RIGHTS THAT MIGHT NOW OR IN THE FUTURE BE INFRINGED BY AN IMPLEMENTATION OF THE SPECIFICATION IN ITS CURRENT, OR IN ANY FUTURE FORM. IF ANY SUCH RIGHTS ARE DESCRIBED ON THE SPECIFICATION, LICENSOR TAKES NO POSITION AS TO THE VALIDITY OR INVALIDITY OF SUCH ASSERTIONS, OR THAT ALL SUCH ASSERTIONS THAT HAVE OR MAY BE MADE ARE SO LISTED.4.TERMINATION OF LICENSE.In the event of a breach of this Agreement by Licensee or any of its employees or members, Licensor shall give Licensee written notice and an opportunity to cure. If the breach is not cured within thirty (30) days after written notice, or if the breach is of a nature that cannot be cured, then Licensor may immediately or thereafter terminate the licenses granted in this Agreement.5.MISCELLANEOUS.All notices required under this Agreement shall be in writing, and shall be deemed effective five days from deposit in the mails. Notices and correspondence to the NFC Forum address as it appears below. This Agreement shall be construed and interpreted under the internal laws of the United States and the Commonwealth of Massachusetts, without giving effect to its principles of conflict of law.NFC Forum, Inc.401 Edgewater Place, Suite 600Wakefield, MA, USA 01880ContentsContents1Introduction (1)1.1Objectives (1)1.2Applicable Documents or References (1)1.3Administration (1)1.4Name and Logo Usage (2)1.5Intellectual Property (2)1.6Special Word Usage (2)1.7Convention and Notations (2)1.7.1Representation of Numbers (2)1.8Abbreviations (3)1.9Glossary (3)2Memory Structure and Management (5)2.1Memory Structure (5)2.1.1Capability Container (6)2.1.2Data Area (6)2.2TLV blocks (6)2.2.1NDEF Message TLV (8)2.2.2Proprietary TLV (8)2.2.3Terminator TLV (9)3RF Interface (10)4Framing / Transmission Handling (11)5Command Set (12)5.1State Diagram (Informative) (12)5.2Generic Command Response Structure (13)5.2.1Generic Command structure (13)5.2.2Generic response structure (14)5.3READ_SINGLE_BLOCK (16)5.4WRITE_SINGLE_BLOCK (16)5.5LOCK_SINGLE_BLOCK (17)5.6READ_MULTIPLE_BLOCK (17)5.7EXTENDED_READ_SINGLE_BLOCK (18)5.8EXTENDED_WRITE_SINGLE_BLOCK (19)5.9EXTENDED_LOCK_SINGLE_BLOCK (20)5.10EXTENDED_READ_MULTIPLE_BLOCK (21)5.11SELECT (22)6NDEF Detection and Access (23)6.1NDEF Management (23)6.1.1Version Treating (25)6.2NDEF Storage (26)6.3Life Cycle (26)6.3.1INITIALISED State (27)6.3.2READ/WRITE State (27)6.3.3READ-ONLY State (27)6.4Command Sequence Description (28)6.4.1NDEF Detection Procedure (28)6.4.2NDEF Read Procedure (30)Figures6.4.3NDEF Write Procedure (31)6.4.4State Changes (32)A.Exhibit A (34)B.Empty NDEF Message (35)C.Revision History (36)FiguresTable 2: Generic memory structure with (n+1) blocks of BLEN bytes (5)Figure 1: Length Field Formats (7)Figure 2: Type 5 Tag State Diagram (13)Figure 3: NDEF detection procedure (30)Figure 4: Life Cycle with State Changes (transitions) (32)TablesTable 1: Abbreviations (3)Table 3: Example of an 8 bytes Capability Container (6)Table 4: Defined TLV blocks (8)Table 5: Command Set (12)Table 6: Generic Command structure (13)Table 7: REQ_FLAG (14)Table 8: Generic response structure (15)Table 9: Format of RES_FLAG (15)Table 10: Error codes (15)Table 11: READ_SINGLE_BLOCK (16)Table 12: WRITE_SINGLE_BLOCK (17)Table 13: LOCK_SINGLE_BLOCK (17)Table 14: READ_MULTIPLE_BLOCK (18)Table 15: EXTENDED_READ_SINGLE_BLOCK (19)Table 16: EXTENDED_WRITE_SINGLE_BLOCK (20)Table 17: EXTENDED_LOCK_SINGLE_BLOCK (20)Table 18: EXTENDED_READ_MULTIPLE_BLOCK (21)Table 19: SELECT (22)Table 20: Byte 1 of Capability Container (23)Table 21: Byte 3 of Capability Container (24)TablesTable 22: Example of 4 bytes coding of CC (24)Table 23: Example of 8 bytes coding of CC (25)Table 24: Example of 8 bytes coding of CC (25)Table 25: Handling of the mapping document version numbers (26)Table 25: Revision History (36)1 IntroductionThis specification is part of the NFC Forum documentation about tag types that an NFC Forum device needs to support in reader/writer mode.This specification documents how an NFC Forum Device SHALL operate an NFC Forum Type 5 Tag platform. This is not a specification of the NFC Forum Type 5 Tag platform itself.1.1 ObjectivesThe purpose of this specification is to document the requirements and to specify, with a set of rules and guidelines, the NFC Forum Device operation and management of the Type 5 Tag platform.This specification assumes that the Collision Detection and Device Activation activities have been performed as documented in [DIGITAL], [ACTIVITY], and [ANALOG].This specification also defines data mapping and how the NFC Forum Device detects, reads, and writes NDEF data into the Type 5 Tag platform in order to achieve and maintain interchangeability and interoperability.The Type 5 Tag Operation specifies how to read and write one NDEF Message TLV only.1.2 Applicable Documents or References[ACTIVITY] NFC Activity Specification,NFC Forum[ANALOG] NFC Analog,NFC Forum[DIGITAL] NFC Digital Protocol,NFC Forum;[NDEF] NFC Data Exchange,NFC Forum[RFC2119] Key words for use in RFCs to Indicate Requirement Levels, RFC2119, S. Bradner,March 1997,Internet Engineering Task Force1.3 AdministrationThe Type 5 Tag Operation is a technical specification supported by the Near Field Communication Forum, Inc., located at:401 Edgewater Place, Suite 600Wakefield, MA, 01880Tel.: +1 781-876-8955Fax: +1 781-610-9864/The NFC Forum, Inc. maintains this specification. Comments, errors, and other feedback can be submitted at /our-work/specifications-and-application-documents/feedback-on-technical-specifications/.1.4 Name and Logo UsageThe Near Field Communication Forum’s policy regarding the use of the trademarks NFC Forum and the NFC Forum logo is as follows:•Any company MAY claim compatibility with NFC Forum specifications, whether a member of the NFC Forum or not.•Permission to use the NFC Forum logos is automatically granted to designated members only as stipulated on the most recent Membership Privileges document, during the period of time for which their membership dues are paid.•Member’s distributors and sales representatives MAY use the NFC Forum logo in promoting member’s products sold under the name of the member.•The logo SHALL be printed in black or in color as illustrated on the Logo Page that is available from the NFC Forum at the address above. The aspect ratio of the logo SHALL be maintained, but the size MAY be varied. Nothing MAY be added to or deleted from thelogos.•Since the NFC Forum name is a trademark of the Near Field Communication Forum, the following statement SHALL be included in all published literature and advertising material in which the name or logo appears:NFC Forum and the NFC Forum logo are trademarks of the Near Field Communication Forum.1.5 Intellectual PropertyThe Type 5 Tag Operation Specification conforms to the Intellectual Property guidelines specified in the NFC Forum's Intellectual Property Rights Policy (/wp-content/uploads/2013/11/NFC-Forum-IPR-Policy.pdf), as outlined in the NFC Forum Rules of Procedure (/wp-content/uploads/2013/11/NFC-Forum-Rules-of-Procedure.pdf).1.6 Special Word UsageThe key words “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT” and “MAY” in this document with the exception of the RESTRICTION ON USE section are to be interpreted as described in [RFC2119].1.7 Convention and Notations1.7.1 Representation of NumbersThe following conventions and notations apply in this document unless otherwise stated. •Binary numbers are represented by strings of digits 0 and 1 shown with the most significant bit (msb) left and the least significant bit (lsb) right, “b” is added at the end.Example: 11110101b•Hexadecimal numbers are represented using the numbers 0 - 9 and the characters A – F, an “h” is added at the end. The most significant byte (MSB) is shown on the left, the leastsignificant byte (LSB) on the right.Example: F5h•Decimal numbers are represented as is (without any trailing character).Example: 2451.8 AbbreviationsThe abbreviations as used in this document are defined in Table 1.Table 1: Abbreviations1.9 GlossaryMandatory NDEF Message TLV, First NDEF Message TLVNDEF Message TLV detected by the NDEF detection procedure.NFC Forum Compliant DeviceIn this document, the NFC Forum device always uses the Reader/Writer modus operandi (for more information, see [DIGITAL]).NFC Forum DeviceA device that supports the following modus operandi: Initiator, Target andReader/Writer. It may also support Card Emulator.Read Alike CommandSet of commands not changing the persistent state of the Type 5 Tag Platform (for more information, see [DIGITAL]).Type 5 Tag PlatformA legacy platform supporting a subset of a Technology (also called Technology Subset).Type 5 Tag platform uses a particular subset of NFC – Type 5 technology including anti-collision (for more information, see [DIGITAL]).Write Alike CommandSet of commands changing the persistent state of the Type 5 Tag Platform (for moreinformation, see [DIGITAL]).Memory Structure and Management2 Memory Structure and ManagementType 5 Tag platform is based on a memory chip with a various memory size and space for data. The following sections describe the details of this type of memory chip, and in particular, its memory structure and management.Whatever the memory size, the generic memory structure used by Type 5 Tag platform is organized by blocks of fixed size.Each block contains either 4, 8, 16, or 32 bytes. The memory is one continuous area that is addressed by the block number and the byte number within a block as shown inTable 2.Table 2: Generic memory structure with (n+1) blocks of BLEN bytesRegular memory offers up to 256 blocks (n ≤255) addressed by one byte.Extended memory offers up to 65536 blocks (n ≤ 65535) addressed by two bytes.Memory area starts with byte 0 of block 0. The last byte of this memory area is the last byte of the last block n*BLEN+(BLEN-1).In this document, the bit and byte order when defining packets and messages follows the Big Endian byte order.[RQ_T5T_MEM_001] The NFC Forum device SHALL support block sizes of 4, 8, 16, and 32bytes.[RQ_T5T_MEM_002] The NFC Forum device SHALL support one and two byte blockaddress commands.NOTE No DSFID value is reserved for NDEF format. It is recommended to use a DSFID equal to 00h for Type 5 Tag.2.1 Memory StructureThe memory area is composed of two fields:•The Capability Container (CC)•The Data area.The CC begins at the first byte of the memory area and contains 4 or 8 bytes.The CC is stored on contiguous bytes.The Data area (i.e., memory containing the NDEF message ) starts with the first byte following the last byte of CC. The size of the Data area is defined by the content of CC.2.1.1 Capability ContainerThe Capability Container (CC) manages the information of the NFC Forum Type 5 Tag Platform. The four bytes CC limits the maximum Data area size at 2040 bytes (block number is coded on one byte). When extended to 8 bytes, the CC allows a larger Data area (block number is coded on two bytes).See Section 6.1 for details.Table 3: Example of an 8 bytes Capability ContainerNOTE* field present when Byte 2 equal 00hExh = E1h when the complete Data area can be read by 1-byte block address commandsExh = E2h when the last part of the Data area can be only read by 2-bytes block address commands. The first 256 blocks can be read by 1-byte block address commands2.1.2 Data AreaData area follows directly the CC within the memory of the Type 5 Tag Platform.[RQ_T5T_MEM_003] The NFC Forum device SHALL write the Data area starting from thefirst byte following the CC up to the end of the data area specified bythe data area length stored within the CC. (see Section 6.2).[RQ_T5T_MEM_004] The NFC Forum device SHALL retrieve the Block Length BLENfrom the response of the Read Single Block of the CC.NOTE BLEN is equal to the number of bytes in the Payload_Data excluding flag, CRC_V and optional Block Security Status fields.2.2 TLV blocksA TLV block consists of one to three fields:[RQ_T5T_MEM_002] T (tag field or T field) identifies the type of the TLV block (see Table4), and SHALL consist of a single byte defined in Table 4.[RQ_T5T_MEM_003] L (length field or L field) provides the size in bytes of the value field.It has two different formats composed of one or three bytes. The NFCForum device SHALL understand both length field formats. Figure 1shows the two different length field structures. However, depending onthe tag field value, the length field MAY not be present.• One-byte format: The NFC Forum device SHALL use the one-byte format to code the lengthof the value field between 00h and FEh bytes. The NFC Forum device SHALL interpret this byte as a cardinal if the value is between 00h and FEh. If it contains FFh, the NFC Forum device SHALL interpret the value as flag that specifies that the length field is composed of more than one byte. • Three consecutive bytes format: The NFC Forum device SHALL use this format to code thelength of the value field between 00FFh and FFFEh bytes. The first byte is assumed to be a flag equal to FFh, indicating that two more bytes are present. The NFC Forum device SHALL interpret the two remaining bytes as a word. The NFC Forum device SHALL interpret this word as a cardinal if the value is between 00FFh and FFFEh. The value FFFFh is reserved forfuture use (RFU).1 byte format 3 bytes formatFigure 1: Length Field Formats[RQ_T5T_MEM_004] V (value field, or V field) If the length field is equal to 00h or there is no length field, the value field is not present (i.e., the TLV block is empty). If there is the length field and it indicates a length N bigger than zero (N>0), the value field consists of N consecutive bytes.Table 4 lists the TLV blocks specified by this document that are described in the following sections.Table 4: Defined TLV blocksTLV block name Tag field Value Short DescriptionNDEF Message TLV 03h It contains the NDEF message (see [NDEF])Proprietary TLV FDh TLV for proprietary informationTerminator TLV FEh Last TLV block in the data areaAll other Tag Field Values are RFU.[RQ_T5T_MEM_005] The NFC Forum device SHALL write the Terminator TLV as the lastTLV block on Type 5 Tag Platform if unused data area is present. Terminator TLV is the only TLV block that is 1 byte long (i.e., composed of only the Tag field, see Section 2.2.3).[RQ_T5T_MEM_006] NFC Forum devices SHALL ignore and jump over TLV blocks usingunknown tag field values. To jump over a TLV block with unknowntag field values, the NFC Forum device SHALL read the length fieldto understand the length of the value field.NOTE Future definitions of TLV blocks composed of only the tag field are not backward compatible with this NFC Forum specification.2.2.1 NDEF Message TLVThe NDEF Message TLV is always present inside the Type 5 Tag Platform. It stores the NDEF message inside the Value field (see [NDEF]).[RQ_T5T_MEM_007] The NFC Forum device SHALL be able to read and process the NDEFmessage (see Section 6.4.1); The always present mandatory NDEFMessage TLV provides the starting point when writing the NDEFMessage into the Type 5 Tag.[RQ_T5T_MEM_008] The encoding of the three TLV fields of NDEF Message TLV is:•T is equal to 03h (see Table 4).•L is equal to the size in bytes of the stored NDEF message.•V stores the NDEF message (see [NDEF]).An empty NDEF Message TLV is defined as an NDEF Message TLV with L field equal to 00h and no V field (i.e., no NDEF message is present in the V field; see [NDEF]).A non-empty NDEF Message TLV can contain either empty or non-empty NDEF messages. The definition of an empty NDEF message is given in Appendix A.2.2.2 Proprietary TLVThe Proprietary TLV contains proprietary information. A Type 5 Tag Platform contains zero, one, or more Proprietary TLV. The NFC Forum device MAY ignore the data contained in this TLV block. The encoding of the thee TLV fields of Proprietary TLV are::•T is equal to FDh (see Table 4).•L is equal to the size in bytes of the proprietary data in the Valuefield.•V contains any proprietary data.2.2.3 Terminator TLV[RQ_T5T_MEM_009] The Terminator TLV can be present inside the Type 5 Tag Platform,and an NFC Forum device SHALL be able to read and process it. TheTerminator TLV is the last TLV block in the data area. TerminatorTLV is composed of 1 byte tag field. Below the encoding of the tagfields of the Terminator TLV are shown:•T is equal to FEh (see Table 4).•L is not present.•V is not present.RF Interface3 RF InterfaceThe NFC Type 5 Tag complies with the RF interface defined in [ANALOG].[RQ_T5T_RFI_001] The NFC Forum device SHALL comply with the RF interface relatedto the Type 5 Tag Platform as defined in [ANALOG].Framing / Transmission Handling4 Framing / Transmission HandlingThis chapter describes the framing (also called packet structures) and the transmission handling of the NFC Forum device.[RQ_T5T_FTH_001] The NFC Forum Device SHALL comply with the sequence format,the bit level coding, the frame format, the data and payload format,and the command set related to the Type 5 Tag Platform as defined in[DIGITAL], including the activation sequence of the Type 5 TagPlatform as defined in [ACTIVITY].[RQ_T5T_FTH_002] If the Special_Frame flag within the CC is set to 0b, the NFC ForumDevice SHALL use the standard frame format for all commands andresponses and the bit 7 of REQ_FLAG (OF) of commands changingpersistent memory (Table 5) SHALL be set to 0b.[RQ_T5T_FTH_003] If the Special_Frame flag within the CC is set to 1b, the NFC ForumDevice SHALL use the Special Frame format for all commandschanging the persistent memory and defining the OPTION_FLAG forthe usage of Special Frames(Table 5). For these commands, the bit 7of REQ_FLAG (OF) SHALL be set to 1b. The NFC Forum Deviceshall use the standard frame format for all other commands and for allresponses.[RQ_T5T_FTH_004] For all supported commands and responses, the NFC Forum DeviceSHALL comply with the requirements defined in Section 5.5 Command SetTable 4 lists the Commands that are available for communication with an NFC Forum Type 5 Tag Platform. For each Command, the corresponding response from the NFC Forum Type 5 Tag is indicated.Table 5: Command SetPoll Mode (Command) Listen Mode (Response) SpecialFramesupport ReadAlikeWriteAlikeREAD_SINGLE_BLOCK _REQ READ_SINGLE_BLOCK_RES, X WRITE_SINGLE_BLOCK_REQ WRITE_SINGLE_BLOCK_RES X X LOCK_SINGLE_BLOCK_REQ LOCK_SINGLE_BLOCK_RES, X X READ_MULTIPLE_BLOCK _REQ READ_MULTIPLE_BLOCK_RES,XEXTENDED_READ_SINGLE_REQ EXTENDED_READ_SINGLE_BLOCK_RES, XEXTENDED_WRITE_SINGLE_BLOC K _REQ EXTENDED_WRITE_SINGLE_BLOCK_RESXXEXTENDED_LOCK_SINGLE_BLOC K _REQ EXTENDED_LOCK_SINGLE_BLOCK_RESXXEXTENDED_READ_MULTIPLE_BL OCK _REQ EXTENDED_READ_MULTIPLE_BLOCK_RESXSELECT_REQ SELECT_RES X5.1 State Diagram (Informative)This informative section shows the state diagram of a Type 5 Tag and the commands used byNFC Forum Device to manage state transitions.• A Type 5 Tag operate in three states called “Ready”, “Quiet”, and “Selected”. • In Ready state, all commands where the SMS is not set are processed.• In Quiet state, the Type 5 Tag does not process the INVENTORY command. Any othercommands where the AMS is set are processed. • In Selected state, every command where SMS is set are processed. There can be at most onePower OffReady QuietSelectedPower OffPower OnPower OffPower OffSELECTSELECTSLPV_REQSLPV_REQSELECT with /=UIDFigure 2: Type 5 Tag State Diagram5.2 Generic Command Response Structure5.2.1 Generic Command structureTable 6 specifies the generic command structure for all commands described in this section.Table 6: Generic Command structureUID is coded on 8 bytes.If present, Parameter and Data fields are defined in each command.The REQ_FLAG is coded as specified in Table 7:Table 7: REQ_FLAGb8 b7 b6 b5 b4 b3 b2 b1 Meaning0 RFUx OPTION_FLAG (OF): The meaning of this flag iscommand specificx Address mode Selector (AMS)x Select mode Selector (SMS)0 0b: No protocol format extension0 0b: No Inventory command1 1b : High Data Rate0 0b : Single SubcarrierCommand can be sent in Select mode. REQ_FLAG bit b5 “SMS” is the Select mode selector. When b5 is equal to 1b, the command is executed only by the Type 5 Tag in Selected state.When b5 is equal to 0b, the command execution depends on the AMS bit and the UID field. Command can be sent in Addressed or Non Addressed mode. REQ_FLAG bit b6 “AMS” is the Address mode selector.When b6 is equal to 1b. the command is sent in Addressed-mode. Only the Type 5 Tag with itsUID matching the UID of the Command will execute the command.When b6 is equal to 0b, command is sent in a Non addressed-mode, and all Type 5 Tags in the state Ready or Selected will execute the command.[RQ_T5T_CSE_001] The NFC Forum Device SHALL set the REQ_FLAG according toTable 7.[RQ_T5T_CSE_002] To use the addressed mode, the NFC Forum Device SHALL set the bitb6 (“AMS”) of REQ_FLAG to 1b, SHALL set the bit b5 (“SMS”) ofREQ_FLAG to 0b, and SHALL set the UID field with the UID of thetargeted tag.[RQ_T5T_CSE_003] To use the non-addressed mode, the NFC Forum Device SHALL setthe bit b6 (“AMS”) of REQ_FLAG to 0b, SHALL set the bit b5(“SMS”) of REQ_FLAG to 0b, and SHALL NOT include any UIDfield into the command.[RQ_T5T_CSE_005] To use the select mode, the NFC Forum Device SHALL set the bit b6(“AMS”) of REQ_FLAG to 0b, SHALL set the bit b5 (“SMS”) ofREQ_FLAG to 1b, and SHALL NOT include any UID field into thecommand.5.2.2 Generic response structureTable 8 specifies the generic response structure for all commands described in this section.Table 8: Generic response structure Length 1 byte N bytes(Conditional)Reponses Normal case RES_FLAG DATA Error case RES_FLAG Error codeIf present, DATA is defined in each response.The coding of the RES_FLAG is specified by Table 9:Table 9: Format of RES_FLAGb8 b7 b6 b5 b4 b3 b2 b1 Meaning0 0 0 0 0 0 0 RFUx ERRORIf the bit b1 of the RES_FLAG “ERROR” is equal to 0b, DATA as defined for each response can follow the RES-FLAG.If the bit b1 of the RES_FLAG “ERROR” is equal to 1b, an error has occurred and RES-FLAG is always followed by a single data byte indicating the error code as defined in Table 10:Table 10: Error codesError Code Meaning01h Command not supported02h Command not recognized03h Command option not supported0Fh No information10h Specified block doesn’t exist11h Specified block already locked and cannot be locked again12h Specified block already locked and cannot be change13h Specified block was not successfully programmed14h Specified block was not successfully lockedA0h – DFh Proprietary error codeOther values RFU[RQ_T5T_CSE_004] The NFC Forum Device SHALL be ready to receive a response asspecified in Table 8.[RQ_T5T_CSE_005] The NFC Forum Device SHALL be ready to receive a response withthe “ERROR” bit b1 of RES_FLAG equal to 1b followed by one bytespecifying the Error Code as defined in Table 10.5.3 READ_SINGLE_BLOCKThe READ_SINGLE_BLOCK command is used to read the content of one memory block. The READ_SINGLE_BLOCK_REQ has the command code 20h and an 1-byte Block Number (BNo) as Parameter.This command has no DATA field.The NFC Forum device can request Type 5 Tag to return in the response the Block security status by setting the bit 7 of REQ_FLAG (OF) to 1b.[RQ_T5T_CSE_006] The NFC Forum device SHALL construct theREAD_SINGLE_BLOCK_REQ as described in table 10Table 10 specifies the READ_SINGLE_BLOCK command and the corresponding response.Table 11: READ_SINGLE_BLOCKLength 1 byte 1 byte 8 bytes 1 byteCommand READ_SINGLE_BLOCK_REQ REQ_FLAG Code20hUID BNoLength 1 byte 1 byte(optional)BLEN bytesResponse READ_SINGLE_BLOCK_RES RES_FLAG Block securityStatusData bytes[RQ_T5T_CSE_009] The NFC Forum Device SHALL be ready to receive aREAD_SINGLE_BLOCK_RES with a payload composed of anRES_FLAG byte and BLEN Data bytes, if the bit 7 of REQ_FLAG(OF) was set to 0b[RQ_T5T_CSE_010] The NFC Forum Device SHALL be ready to receive aREAD_SINGLE_BLOCK Response with a payload composed of anRES_FLAG byte, Block security status and BLEN Data bytes, if thebit 7 of REQ_FLAG (OF) was set to 1b.5.4 WRITE_SINGLE_BLOCKThe WRITE_SINGLE_BLOCK_REQ command is used to update the content of one memory block. This command has the command code 21h and a 1-byte Block Number (BNo) as Parameter. The DATA field contains the new content of the block and has a length of BLEN bytes. The first DATA field byte represents the first byte of the block to update and the last DATA field byte represents the last byte of the block.[RQ_T5T_CSE_011] The NFC Forum device SHALL construct theWRITE_SINGLE_BLOCK_REQ command described in Table 12. Table 12 specifies the WRITE_SINGLE_BLOCK command and the corresponding response.。
CISCO配置命令大全
CISCO配置命令大全路由器的基本配置1 ．配置以太网（Ethernet）端口：# conf t从终端配置路由器。
# int e0指定E0口。
# ip addr ABCD XXXXABCD为以太网地址,XXXX为子网掩码。
# ip addr ABCD XXXX secondaryE0口同时支持两个地址类型。
如果第一个为A类地址，则第二个为B或C类地址。
# no shutdown激活E0口。
# exit2．X.25的配置# conf t# int S0指定S0口.# ip addr ABCD XXXXABCD为以太网S0的IP地址,XXXX为子网掩码.。
# encap X25-ABC封装X.25协议。
ABC指定X.25为DTC或DCE操作，缺省为DTE。
# x25 addr ABCDABCD为S0的X.25端口地址,由邮电局提供。
# x25 map ip ABCD XXXX br映射的X.25地址.ABCD为对方路由器(如:S0)的IP地址,XXXX为对方路由器(如:S0)的X.25端口地址。
# x25 htc X配置最高双向通道数.X的取值范围1-4095,要根据邮电局实际提供的数字配置。
# x25 nvc X配置虚电路数。
X不可超过据邮电局实际提供的数,否则,将影响数据的正常传输。
# exit---- 3 ．专线的配置：# conf t# int S2指定S2口。
# ip addr ABCD XXXXABCD为S2的IP地址,XXXX为子网掩码。
# exit4．帧中继的配置# conf t# int s0# ip addr ABCD XXXXABCD为S0的IP地址,XXXX为子网掩码。
# encap frante_relay封装frante_relay协议。
# no nrzi_encodingNRZI=NO# frame_relay lmi_type q933aLMI使用Q933A标准．LMI（Local management Interface）有3种：ANSI：T1.617；CCITTY：Q933A和CISCO特有的标准。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
• First UK V5 implementation
Epsom & St Helier (Provider Portal & ED White Board)
1/23 ED Whiteboard Demo
3/25 Pilot Go-Live
• In final stages of UAT • Focus on Go-Live prep
Stage C CCAD EBI - $2.6M
Palos CIP - $1M Stage D Phoebe Putney Provider Portal - $1M URMC CIP - $5M Mount Sinai CIP - $5M Stage C
Epsom & St. Helier P2 (UK) - $500K
Allina (Provider Portal)
11/8 Mirth Infrastructure Installed
2/25 Install FusionFx Prod
= On Track
4/14 5/9 Epic Data Express Ingest Core Complete UAT
= At Risk
Harris Proprietary Information |FusionFX™
Harris Proprietary Information | 10
HIMSS14 Highlights
•
• •
20+ pre-arranged customer meetings and demonstrations
6/26 Express Core Live
• Implementation of the Harris Express Core is well underway
= Completed
= Delay Harris Proprietary Information | 7
ES Sales Momentum
/wiki/Sales_lead
If you haven’t heard, HIMSS is about Lead Generation… 1. A qualified & maturing deal (Stage C) in the Pipeline is significantly advanced due to significant time over target with decision makers e.g. KP Provider Portal Opportunity, Phoebe Putney An early stage but identified opportunity in the Pipeline (Stage D) is further qualified and our position is solidified due to interaction at HIMSS e.g. Mount Sinai, Memorial A new potential customer with plans to purchase is identified and made aware of and interested in Harris as a solution • Target 30-40 as a result of HIMSS, with qualification & follow-up over subsequent 3-4 months
3.
Q&A
Harris Proprietary Information | 2
FY14 critical success factors
• FusionFX launch – Presence pilot underway
• Sales development/marketing – Order growth + HIMSS prep
All-Hands Discussion
HCS
February 21st, 2014
Harris Proprietary Information | 1
Today’s discussion
1.
HCS Priorities update
2.
– – –
Performance
FusionFX development and delivery Sales pipeline HIMSS
• Health Services Platform Consortium – Intermountain announcement
Harris Proprietary Information | 3
MU2 Test Results – GREAT JOB!
170.314(a)(15) - Patient-Specific Education Resources 170.314 - NTP_Test 170.314(e)(1) - View Download Transmit to 3rd Party 170.314(e)(3) - Secure Messaging [Ambulatory Only] 170.314(d)(2) - Auditable Events and Tamper-Resistance 170.314(d)(3) - Audit Reports 170.314(d)(1) - Authentication and Access Control 170.314(d)(6) - Emergency Access 170.314(d)(5) - Automated LogOff 170.314(g)(1) - Automated Numerator [EHR Modules Only]
•We’re Live !!!! • Continuing to add clinicians to Pilot
Presence (Provider Portal)
11/8 Install 5.1.1 (Stage)
2/10 Pilot Live
April (tentative) FusionFx Live
ES Key Pursuits (Last Month) Stage A
ES Key Pursuits (This Month) CLOSED/WON! Advocate 5.x upgrade - $3.4M KP Secure Messaging - $200K
SEHA - $5.6M
Advocate 5.x upgrade - $3M KP Secure Messaging - $200K Stage B Cook’s Patient Portal - $1.3M Memorial Hermann - $500K Summa CIP - $5M
• More than 20,000 users
Advocate (Patient Portal)
10/28 5.1 Live
12/4 Install 5.1.0.1
2/17 5.1.2 MU2 Cert
2/24 MU-2 Certified PaP Live
• 1200 unique users per day
• MU-2 certified Patient Portal Go-live on Monday • Contract amendments signed • UAT/remediation prior to March Limited Prod. Live • Final design underway for Full Prod. Release
Harris Proprietary Information | 5
PRESENCE UPDATE
Harris Proprietary Information | 6
Key CIP Program Status
Overall Status Oct Nov Dec Jan Feb Mar Apr May Jun
8-10 sales channel partner discussions 8-10 technology partner discussion
•
• • •
15 media interviews and meetings
12 customer presentations in Harris booth 2 Harris customers official HIMSS speakers (Dr. Lorenz/Cleveland Clinic and Heidi Fox/Florida HIE) Major focus on pre-marketing: Customer VIP event invitations and promotional emails sent to 700+ database of customers, teaming partners and friends of Harris Healthcare Sold-out Harris-sponsored breakfast event with Dr. Richard Ferrans, Presence Health
HIMSS…So what’s a lead anyway?
sales lead Web definitions A sales lead is the identification of a person or entity that has the interest and authority to purchase a product or service. This step represents the first stage of a sales process. ...