WEB Based Monitoring and Management Background and Considerations

WEB Based Monitoring and Management Background and Considerations PWG - Maui /W. Wagner, Net. Silicon 6/9/2021

Background n CAP Ventures White Paper - Software Innovations: From Remote Diagnostics to Device Relationship Management 12 December 2002 PWG - Maui /W. Wagner, Net. Silicon 2 6/9/2021

Primary Third-Party Players n Imaging Portals (www. imagingportals. com ) n n Existing Sites with pager-based collection and SNMP oriented networked collection Call it d 2 B (Device to Business) (Net. Silicon uses D 2 B in a more general way) Electronics for Imaging, Inc. (EFI) (www. efi. com) n n Applies Axeda technology to imaging Axeda has significant experience in medical and industrial Web Based Monitoring and Control applications Calls it DRM (Device Relationship Management) DRM also stands for Digital Rights Management, which may be related PWG - Maui /W. Wagner, Net. Silicon 3 6/9/2021

Imaging Portals Architecture PWG - Maui /W. Wagner, Net. Silicon 4 6/9/2021

EFI Approach PWG - Maui /W. Wagner, Net. Silicon 5 6/9/2021

Players in General WEB Monitoring n n n Axeda (nee e. Mation) (www. axeda. com ) Questra (www. questra. com ) em. WARE (www. emware. com) Embrace ( www. embracenetworks. com) others PWG - Maui /W. Wagner, Net. Silicon 6 6/9/2021

Related Industry Products n n n Docu. Stats 2000 from Document Dynamics (www. documentdynamics. com ), Office. Trac from Equitrac (www. equitrac. com) Uniprint and Blueprint from Pharos Systems (www. pharos. com) Print Auditor from Print Control Solutions Ltd. (www. print-auditor. com), and Xerox’s Page. Trak and XCounter (www. xerox. com) PWG - Maui /W. Wagner, Net. Silicon 7 6/9/2021

CAPV Reference to Standards n Management Information Base (MIB) n Simple Network Management Protocol n e. Xtensible Markup Language (XML) n Simple Object Access Protocol (SOAP) PWG - Maui /W. Wagner, Net. Silicon 8 6/9/2021

What to do next? n n Is there interest in Standardization? Limiting Scope? n n Monitoring only? Default only? (no instructions) Just standardize interface with server? Consider n n Transport (HTTP or custom) Object identification method Report contents, coding and formats Instruction coding, format, PWG - Maui /W. Wagner, Net. Silicon 9 6/9/2021

Device Acquisition/distribution Message Formatting/Reading Transport (authenticate/encrypt/communicate) Message Formatting/Reading Interface to data base/management system PWG - Maui /W. Wagner, Net. Silicon 10 6/9/2021

Suggested Areas to Address n n Overall path for monitor, manage, update Identify Transport compatible with requirements Create messages for different operations Define basic message format (e. g. , n n n Source and destination identification operation Message Time, Action Time and/or periods Affected Parameters in attribute/value format Communication of embedded files PWG - Maui /W. Wagner, Net. Silicon 11 6/9/2021

Areas Not to Address n Acquisition/Distribution n n Specifics of how Firewalls, Proxies, site specific requirements are handled n n Except to suggest use of WEB services type approach Specific content of messages n n Except for noting that it may be via SNMP, Web page, internal, etc Except for “header” Specific parameters or naming of parameters n Except to give examples, such as OID approach PWG - Maui /W. Wagner, Net. Silicon 12 6/9/2021