Download presentation
Presentation is loading. Please wait.
1
AbbottLink Technical Overview
AbbottLink Summit Santa Clara Jan 2010 Company Confidential © 2010 Abbott
2
Topics AbbottLink High Level Overview
Types of Instrument Data Collected Displaying Instrument Data AbbottLink Features based on Instrument Data AbbottLink Connection Framework Connectivity Architecture AbbottLink Enterprise Axeda 6 AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
3
AbbottLink High Level Overview
3. Aggregate the data in a centralized data repository(s) Local Users 1. Provide the ability to tap into the operational data resident on instruments in the field (Business Data) Abbott 2. Broadband transfer via network services Internet Customer Clinical Setting Key points: Real Time Data Transfer Web Portal to view data Internal Abbott Users External Customer Users AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
4
AbbottLink High Level Overview
AbbottLink provides a mechanism to capture operational and usage data from a device and transmit electronically back to Abbott Enterprise over Internet and the ability to distribute information to a device. Benefits Improves the ability to remotely troubleshoot instrument issues Improves the efficiency in which instrument or assay issues are identified and resolved Provides the capability to decrease instrument down time Decrease the cost of service for Abbott Increased focus to establish critical mass for connectivity Goal 2010 for Service is to establish 80% connectivity of all ARCHITECT modules to AbbottLink 6/21/2010 – 36% connected AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
5
AbbottLink High Level Overview - Axeda
Firewall-Friendly M2M Connectivity Device Relationship Management Acquired competitor Questra in March 2009 Internet of Things Support Customer Hosted and SaaS (On Demand) Customers Applied Biosystems – DNA Analyzers CareFusion – drug dispersion pumps and neurocare devices – device connected TSA Diebold – ATM machines Data Innovations Hospira – Medication Management Solutions Sysmex Siemens Beckman - Coulter AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
6
Real-time Capture of Data
Instrument State Instrument Notifications Instrument Information Messages Code and text Maintenance and Diagnostic Activities Name Type Frequency Outcome AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
7
On-Demand Capture of Data
System Information Serial Number Software Version Cycle Counts (Odometer) Patients attempted Patients completed Scheduled for automatic daily retrieval Test Counts Categorized by patient, control, and calibrator sample types Partitioned by individual test type Capture Data on Scheduled basis AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
8
On-Demand Capture of Data
Transfer of Instrument Logs and Files to AbbottLink Logs created and maintained by the software Files stored on the hard drive System configuration files Printed reports Retrieval can be tied to Instrument in particular state Protected Health Information (PHI) is filtered from the logs and files Logs and file can be automatically retrieved Scheduled Monitored scenario detection System Commands Execute Native OS Commands on Instrument Transfer of Files from AbbottLink to Instrument SW Updates Configuration files AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
9
Batch Processing Agent Enterprise File is identified on the device
VBScript or Perl script created to parse the device file for the identified information VBScript creates an xml file in a format defined by Axeda XML format defines the data element types for distribution to Enterprise. Stored in Enterprise based on device needs Enterprise File is uploaded to Enterprise Parsing performed in Abbott Enterprise AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
10
AbbottLink Capabilities
Proactive Monitoring Business Rules defined in AbbottLink to monitor defined instrument scenarios Evaluation of Generated Instrument Data against scenarios Instrument scenario encountered AbbottLink sends notification Text Axeda application alarm Preventive Instrument Maintenance Base Instrument Maintenance on instrument usage or time (Oil Change scenario) Define instrument usage data to monitor Define usage and/or time threshold values Define Notification Interval based of threshold (80 % of threshold) Indication Instrument Maintenance is performed resets AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
11
AbbottLink Capabilities
Instrument Workflow Analysis Usage information Test count by day Instrument utilization Automation of Billing Processes Use Instrument data collected by AbbottLink Billing Systems pull data from AbbottLink database Distribution of Instrument Deliverables SW Updates Customer letters Configuration Information Remote Control of Instrument UI Customer has to allow remote desktop sharing request AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
12
AbbottLink User Types Front-line Customer Service
Instrument Specialists Field Service R&D External Customer Abbott Quality AbbottLink Service and Support AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
13
AbbottLink Connectivity Base
ARCHITECT CELL-DYN Ruby and Sapphire Accelerator APS M2000sp, M2000rt, PLEX_ID AxSYM AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
14
AbbottLink Connection Framework
Instrument Channel Abbott Instrument Instrument to Enterprise (I2E) Connection Agent RS232 (ASTM protocol) TCP/IP (Using defined AbbottLink Protocol on top of TCP) Enterprise Channel I2E Connection Agent Abbott Enterprise HTTP messages with SOAP payloads containing XML Encrypted with SSL AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
15
I2E Connection Agent I2E Connection Agent components Axeda Gateway
Axeda application that provides Internet communication over Enterprise channel Allows multiple instruments to be managed by Axeda application Installed on separate Abbott provided PC (AbbottLink PC) to provide Internet connectivity Axeda Connector Allows single instrument to be managed by Axeda application Installed on instrument workstation which provides Internet connectivity Abbott development EDD Drivers Communicates with Axeda Agent via Axeda EDD interface Communicates with Abbott instrument software via AbbottLink-Instrument interfaces Generic Windows Agent No direct interface with Abbott instrument software – base functionality includes uploading files and remote desktop Batch processing is available to collect device data All AbbottLink communication is initiated from the customer site, which eliminates the need for a public IP Address for the Abbott device and prevents visibility from outside the customer firewall. AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
16
Instrument Channel RS232 – Legacy Abbott Systems TCP/IP ASTM Protocol
Send Command Line Interface commands Receive Instrument responses TCP/IP Instrument SW communicates with I2E Connection Agent over AbbottLink Protocol Socket based protocol using TCP ports Synchronous and Asynchronous Channel Instrument Software listens on TCP port to receive synchronous requests I2E Connection Agent listens on TCP port to receive asynchronous requests AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
17
Instrument Channel Instrument Security
Requires Instrument to be able to access customer network Small hardware firewall is used to protect Abbott Instrument from customer network Hardware firewall acts as DHCP server. AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
18
AbbottLink SW Interface package
Abbottlink will provide a library or DLL that would be integrated with the Instrument software. The DLL manages communication with the I2E Connection Agent via the AbbottLink Protocol DLL exposes Object Oriented (OO) software interfaces to support Instrument Channel Interface messages. IAbbottLinkRequest – Synchronous interface IAbbottLinkCallback – Asynchronous interface Instrument Information message is generated with a pop-up on screen Instrument software logs message and sends to AbbottLink AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
19
Architecture – AbbottLink PC
AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
20
AbbottLink 3.00 Production Deployment
AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
21
AbbottLink Enterprise
AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
22
AbbottLink Enterprise
Interception of Agent Transmitted Data CPR – Cost Per Reportable Agent transmits data as Axeda Event (flexible data object supported) – xml containing assay counts by test types formatted by the agent to be consumed by CPR application. Custom java code written deployed in the ServiceLink web application to intercept the Axeda Event before being processed by base ServiceLink. Puts body of Axeda Event on message queue for CPR application CPR application consumes the xml and stores assay count data in defined CPR database tables Presentation is through custom Cognos reports within Axeda ServiceLink Extended Axeda ServiceLink database schema Custom tables were created to organize the storage of data items Database triggers on insert into Axeda data item values table to process Abbott device message Store in Abbott Extended Data (AED) tables. Instrument Notification, Maintenance Completed, Usage Counter data Presentation of data through custom Cognos reports within Axeda ServiceLink Presentation of data through custom module on Axeda device dashboard page AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
23
AbbottLink Enterprise
Copy files to external application Files are uploaded on a scheduled basis using Axeda ServiceLink. Files are stored in AbbottLink file network storage by Axeda generated device Id External application has read-only access to copy files from AbbottLink file network storage Files are copied on defined interval Files are parsed and stored in defined database tables Custom UI developed in .NET for presentation of log data No ServiceLink presentation AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
24
AbbottLink Enterprise
Leverage Axeda ServiceLink FTP of files to external system Axeda base product provides a rule to monitor for a file upload based on a file hint. If a file is uploaded with a name that includes the defined hint an action is executed The action could send the file via FTP to a configured FTP server. Custom rule Custom java code that is deployed in the Axeda ServiceLink web application Custom rule can configured as data expression – evaluates when the defined data item value is updated – Proactive Monitoring (count the number of occurrences of an error code over a defined time period) Custom rules can be configured as a scheduled rule – Evaluates on a defined schedule Performs rule logic to determine if device data triggers rule Trigger executes defined action AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
25
AbbottLink Enterprise
Custom Module on Device Dashboard page Java development to present data from Abbott Extended Data tables Used to make updates to Abbott Extended Data tables Preventive Maintenance (Registration, Override, Perform) – AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
26
AbbottLink Enterprise
Axeda integration points Axeda Java API Provides methods to insert new data item values running within the Axeda web container Axeda Web Services interface Data Item Service – insert new data item value – device, data item, value. Axeda Java API used in custom rules and report setup pages AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
27
AbbottLink 3.00 Migration to Axeda 5.3.3 from Axeda 3.8.4
Enhancement to improve support of proactive monitoring over a global deployment Include assay information from ARCHITECT into test count reports Support Consolidated CELL-DYN Ruby Support Consolidated m2000rt and m2000sp Enhance parameterized interface Enable Host log to be uploaded from Accelerator APS Provide monitoring capabilities on device for files size growth and process memory usage AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
28
AbbottLink Development 2010 - 2011
Finalize Electronic Distribution of Abbott Information Process Pilot Remote Desktop Access to Abbott Instrument (Ruby, Accelerator APS, ARCHITECT) Enhance AbbottLink Instrument Notification report Enhance preventive instrument maintenance monitoring to support all ARCHITECT modules and improve FSE AbbottLink Preventive instrument maintenance workflow Finalize Generic Windows Agent Enhance CPR Test Count calculation BSQ interface using interoperability with Informatics (AIPC and CTL) AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
29
AbbottLink Development 2010 - 2011
Support automation of collection of QC data for Hematology eQC for CELL-DYN Ruby IVIS interface AMO Interface Support ARCHITECT 8.0 Assay Disk distribution feature Consolidated Platform with CELL-DYN Sapphire Interface with Call Management systems for data synchronization AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
30
Axeda ServiceLink 6 Axeda ServiceLink Integration points Message Queue
Database SDK / Web Services Associations Triggers Data Alarm Location File Registration Login Case Expression Rules State Rules Threshold Rules Geofences Actions Groovy Scripting Internet Cellular Satellite Fixed Mobile RFID Sensor Rule Timers ServiceLink Applications Partner / Customer Applications Axeda Platform Config / Admin Customer Hosted Applications AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
31
System of Systems – APIs and Events
Services Events Messages Enterprise solutions span “systems” No islands of data are permitted in 2010! APIs enables software to talk to other software Web Services APIs through the cloud, across firewalls and platforms Events Business events are the triggers to make systems interact Messages Decouples APIs even further, releases synchronous requirement AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
32
System-to-System Integration Patterns – Point to Point
Enterprise System CRM ERP Firewalls Internet Axeda Web Services Examples Query asset status from Axeda to synchronize customer records in CRM Update rule thresholds in Axeda based on current ERP information Query historical data in Axeda to feed analytics system AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
33
System-to-System Integration Patterns – Point to Point
Axeda Rules Scripts Firewalls Internet Enterprise System Web Services Cloud Services Examples Query knowledge base to decorate alarm information or take automatic corrective action Synchronize Axeda system data from ERP data on-event Integrate with cloud services such as voice response (Ribbit, Twilio), or collaborative systems (Yammer, Google Wave) AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
34
System-to-System Integration Patterns – Message Bus
Axeda Rules Scripts Message Queue Data Events Firewalls Internet Enterprise System Web Services Cloud Services Examples Open trouble tickets in CRM systems Train an expert system with data samples Fan-out system events to many enterprise systems AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
35
Expose the Axeda Platform data and configuration Standards
Axeda Web Services Expose the Axeda Platform data and configuration Standards SOAP 1.2, WSI-Profile 1.1 REST dialects for simpler clients Sampling DeviceService – Query, create, and modify assets DataService – query current and historical asset related data AlarmService – find current alarms and related assets MobileLocationService – query current and historical mobile location of an asset RulesService – manage business rules – create, enable, associate with assets ScriptoService – Write your own web service, backed by an in-platform script! Enterprise System CRM ERP Firewalls Internet Axeda Web Services AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
36
Scripts and Outbound WebService Calls
Axeda Rules Scripts Firewalls Internet Enterprise System Web Services Cloud Services Axeda Custom Objects are a place to slide in application specific logic AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
37
Queuing Asset Events event com.abcauto @ abcauto.axeda.com:61616
Rules Scripts Message Queue Data Events Firewalls Internet Enterprise System Web Services Cloud Services event abcauto.axeda.com:61616 AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
38
Consuming Queue Events
OpenWire, HTTP/XML, Stomp protocols abcauto.axeda.com:61616 ABC Integration Agent Subscribe to com.abcauto where MessageType = Alarm AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
39
Axeda ServiceLink 6 Groovy Scripting ActiveMQ
Groovy is a powerful high level language for the Java platform which compiles down to Java bytecode. Groovy is similar to Ruby and Python but allow you to stay on the JVM Groovy scripting is used to call SDK or external cloud services Create customized web services implementations following REST model Client application call customized web services ActiveMQ ActiveMQ is an open sourced implementation of JMS 1.1 as part of the J2EE 1.4 specification. Apache AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
40
Axeda ServiceLink 6 Building RIA applications Axeda Platform
Content served to the application aggregated, formatted, and delivered however is most efficient and convenient for the application developer Whiz-bang Customer Application developed with RIA technology of your choosing (e.g., Flex) Axeda Platform SOAP or REST Services ScriptoService Axeda SDK Groovy Script Repository Other Services… Enabled by Groovy and the full power of the Axeda SDK AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
41
Axeda ServiceLink 6 – Building RIA applications
Leverage Axeda REST based Web Services or custom web services (Scripto) Axeda AuthService to manage user sessions – use user session to call other Axeda Services – session must be managed Deploy directly to the Axeda Platform No need to find somewhere to host your application Upload binary files to Axeda Platform Configure public URL and index.html file Deploy as a Desktop Application Access multiple servers (private and public) and user’s file system Adobe AIR AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
42
Axeda ServiceLink 6 - Extended Objects
Multi-Function Peripheral Example Capabilities Extend existing data object properties Create new data objects Accessible via Web Services & SDK Benefits Facilitates integration with external applications & business systems Device Model = MFP Device Serial number = Customer = Acme Location = Philadelphia ERPSystemID = MFP3113 The business goal of the example is to facilitate integration with an ERP system for consumable reorder purposes. This is done by extending the Device & Data Item objects and adding a new Toner Status object. Data Item Name=PrintJob Value=Job32145 Toner Status Available=72 Used=34 PaperSize=A4 PageCount=36 TonerUsed=3 AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott 42
43
Axeda ServiceLink 6 – Location Based Services
Location-aware real time information What’s near me right now? I have extra vending stock and there’s a vending machine near me that is low on exactly these items Geo-fences Alert me when my equipment strays from it’s home location When a truck is nearing the distribution center AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
44
Axeda ServiceLink 6 - Axeda Wireless Protocol
Efficient Compacts bytes – saves money Messages can be batched in a transmission Capable Expressive Flexible transports Acknowledgements Message Authentication Easy Simple, elegant message structures ASN.1 syntax definition AWPv1 ::= BEGIN Transmission ::= SEQUENCE { … } looked at a lot of proprietary protocols – most were extremely domain specific (I’m a truck monitor with CANBus) Many just missed the point that people have to pay for bytes over cellular networks AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
45
Axeda ServiceLink 6 - Asset Associations
Capabilities Associations between Source & Target Assets Data forwarding from Source to Target Benefits Lifecycle management of components and composite assets Ability to model real-world assets such as test results, batches of paper, pharmaceuticals, etc. Liquid Chromatography Instrument Pump Injector UV LC ServiceLink Agent ServiceLink Enterprise Composite Asset Multiple component subsystems Each with separate identity and operational life Managed as individual components and as a system AbbottLink Technical Overview June 2010 Company Confidential © 2010 Abbott
Similar presentations
© 2025 SlidePlayer.com Inc.
All rights reserved.