1 / 12

WEB Based Monitoring and Management

WEB Based Monitoring and Management. Background and Considerations. Background. CAP Ventures White Paper - Software Innovations: From Remote Diagnostics to Device Relationship Management - 12 December 2002. Primary Third-Party Players. Imaging Portals ( www.imagingportals.com )

sotoh
Download Presentation

WEB Based Monitoring and Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WEB Based Monitoring and Management Background and Considerations PWG - Maui /W. Wagner, NetSilicon

  2. Background • CAP Ventures White Paper - Software Innovations: From Remote Diagnostics to Device Relationship Management - 12 December 2002 PWG - Maui /W. Wagner, NetSilicon

  3. Primary Third-Party Players • Imaging Portals (www.imagingportals.com ) • Existing Sites with pager-based collection and SNMP oriented networked collection • Call it d2B (Device to Business) • (NetSilicon uses D2B in a more general way) • Electronics for Imaging, Inc. (EFI) (www.efi.com) • 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, NetSilicon

  4. Imaging Portals Architecture PWG - Maui /W. Wagner, NetSilicon

  5. EFI Approach PWG - Maui /W. Wagner, NetSilicon

  6. Players in General WEB Monitoring • Axeda (nee eMation) (www.axeda.com ) • Questra (www.questra.com ) • emWARE (www.emware.com) • Embrace ( www.embracenetworks.com) • others PWG - Maui /W. Wagner, NetSilicon

  7. Related Industry Products • DocuStats 2000 from Document Dynamics (www.documentdynamics.com ), • OfficeTrac 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 PageTrak and XCounter (www.xerox.com) PWG - Maui /W. Wagner, NetSilicon

  8. CAPV Reference to Standards • Management Information Base (MIB) • Simple Network Management Protocol • eXtensible Markup Language (XML) • Simple Object Access Protocol (SOAP) PWG - Maui /W. Wagner, NetSilicon

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

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

  11. Suggested Areas to Address • Overall path for monitor, manage,update • Identify Transport compatible with requirements • Create messages for different operations • Define basic message format (e.g., • 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, NetSilicon

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

More Related