We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byBlaine Tower
Modified about 1 year ago
Gemini Systems, Inc. 61 Broadway New York NY 10006 Tel: 212.480.3960 Fax:: 212.480.3963 http://www.gemini-systems.com An Introduction to VRXML December, 2002 Bryan Palmer
© 2002 Gemini Systems, Inc. Confidential Presentation Contents Current Reporting Process VRXML Objectives NYSE’s Strategy VRXML Timeline VRXML Features VRXML Uncovered VRXML – The Business Case Questions
© 2002 Gemini Systems, Inc. Confidential Current Reporting Process Major disconnect between billing and reporting Terminology/Vocabulary issues Customer service issues Tri-Party reconciliation –Inaccurate reporting based on time differences –Intensive reconciliation problems Vendor Exchange Subscriber
© 2002 Gemini Systems, Inc. Confidential Current Reporting Process (cont) Indirect Bill Exchanges Subscribers Vendors Direct Bill Exchanges Report Administrators 3b.2b. Report 1. Data Feed 2. Device or other Data Product 3a. Report 1. Data Feed 3b.2a. Report 3b.1. Report for Multiple Exchanges 3a. Report
© 2002 Gemini Systems, Inc. Confidential Reporting Formats Why create yet another Reporting Format? VRXML has the potential to turn > 100 different reporting formats into 1 standard format. Extensibility – The ability to add additional functionality or modify existing functionality without impacting the existing system functionality. Other Reporting Formats VARS – effective but lacks extensibility and can lead to inconsistent data Excel
© 2002 Gemini Systems, Inc. Confidential VRXML Objectives Keep things as simple as possible Additional features to cover a wider spectrum of reporting possibilities Hardened but extensible A “what is it that you would like to do” interface
© 2002 Gemini Systems, Inc. Confidential NYSE’s Strategy From Transaction to Inventory Reporting –Every product for each location is reported, not just changes –Less errors, more concise –In essence, becomes monthly reconciliation Extensible technology Full support for VARS Poised to become an industry standard
© 2002 Gemini Systems, Inc. Confidential VRXML Timeline February 2002 - Vision established May 2002 - NYSE and GSI designs initial draft June 2002 - NYSE through the FISD publishes V0.6 September 2002 – Pilot Vendor reports October 2002 –NYSE through the FISD publishes V1.0 pre-release –Deutsche Boerse verbally commits to support –Several vendors commit to migrate November 2002 –FISD, NYSE, and GSI finalize version 1.0 –FISD continues to gain industry acceptance December 2002 – Pilot Vendor(s) report 2003 – On going transition for Vendors, Exchanges, and Users with support from GSI and FISD
© 2002 Gemini Systems, Inc. Confidential Efficient Communication Mechanism Explicit Reporting Actions –New Subscribers –New Locations –New Products –Address Changes –Billing Changes –Company Name Changes –Contact Changes Customer Service Options –Vendor Name Change Requests –Deactivating reportable products Upfront validation of files – eliminates bottlenecks in the overall process
© 2002 Gemini Systems, Inc. Confidential Conceptual Model – Meta Data Elements
© 2002 Gemini Systems, Inc. Confidential Conceptual Model – 1 st Level Elements
© 2002 Gemini Systems, Inc. Confidential Conceptual Model – 2 nd Level Elements
© 2002 Gemini Systems, Inc. Confidential Conceptual Model – Core Data Elements
© 2002 Gemini Systems, Inc. Confidential VRXML Uncovered … 2002-12-01 13
© 2002 Gemini Systems, Inc. Confidential VRXML Uncovered (cont.) 2002-12-01 13 2002-11-01 15
© 2002 Gemini Systems, Inc. Confidential Obstacles Vendor / Exchange interpretation of VRXML –Each Exchange may have their own Business Rules –Each Vendor may have their own Business Rules Possible learning curve / Technical resource availability
© 2002 Gemini Systems, Inc. Confidential What will it take to implement VRXML? Inception - Acceptance and Knowledge Elaboration –Analysis of current reporting mechanism –Identification of requirements (where the data comes from, data model modifications, architectural considerations) Construction - From a prototype to an engine Transition - Validation and Deployment Maintenance - Take advantage of new features as VRXML matures GSI’s VRXML FastTrack Program
© 2002 Gemini Systems, Inc. Confidential Conclusion VRXML is absolutely appropriate Significant cost savings (ROI) –Modest upfront effort –Reduction or elimination of data reconciliations –Streamlined services, less time spent utilizing CSRs –Ability to quickly take advantage of new features that also have the potential to save time and money
© 2002 Gemini Systems, Inc. Confidential Next Steps NYSE is accepting VRXML FISD and GSI are prepared to help all parties with the migration process Pilot Vendors report
© 2002 Gemini Systems, Inc. Confidential Questions
Gemini Systems, Inc. 61 Broadway New York NY 10006 Tel: 212.480.3960 Fax: 212.480.3963 http://www.gemini-systems.com An Introduction To VRXML December, 2002 Bryan Palmer
1 Vendor Evaluation: Selecting for Success Dana McCormick Wells Fargo Home Mortgage Delivery Services Baltimore PCC Education Seminar April 27, 2007.
Serena Project Case Study Sapphire, Atlanta April 23, 2007.
1 Dr. Ralph R. Young Director of Software Engineering PRC, Inc. (703) DOORS USER GROUP CONFERENCE Reston, VA September 17,
1 Prism Communications, Inc. Integrated Software Outsourcing Model.
Whole School Attendance Whole School Attendance 94.64% Overall School Absence 5.36%
Ad Hoc Graphical Reports Ad Hoc Graphical Reports Copyright © Team #4 CSCI 6838 Spring CSCI Research Project and Seminar Team# 4 (http://dcm.cl.uh.edu/caps7g4/)
1 MTAC eVS®/PTS User Group Thursday November 10, 2011.
ISIS Project Status Report May 18, 2006 Prepared by MAXIMUS, Inc Education Systems Division for the ABT Committee.
StickyMinds.com and Better Software magazine presents… How to Build a Testing Center of Excellence Sponsored by Cognizant This event aired on July 8, 2008.
PA Department of Environmental Protection Continuous Source Monitoring Manual (Manual, Revision 8)
LEARN. NETWORK. DISCOVER. | #QADexplore Implementing Business Process Management: Steps to Success WCUG – November 18, 2014.
Common Help Desk Deep Dive Tom Bourgeois / Laurel Wadlund
Confluence Wiki Implementation? 14 June Agenda What? Why? Wow! How? When? 2.
This is a customer facing presentation that you can use to present the your assessment findings, recommendations, options, benefits and requirements. This.
Developing an IS/IT Strategy
Problemsolving Problem Solving – 4 Stages Analysis Design Development Evaluate (ADDE) Note: In this unit Evaluate is not covered in depth.
Firefox 2 Feature Proposal: Remote User Profiles TeamOne August 3, 2007 TeamOne August 3, 2007.
1 Annual National Accounts 1. Situation of OECD annual national accounts database 2. New features of the joint OECD-Eurostat questionnaire 3. COFOG2.
INFSO-RI JRA2 Test Management Tools Eva Takacs (4D SOFT) ETICS 2 Final Review Brussels - 11 May 2010.
ISO 9001:2015 Revision overview - General users
CT TEFT 1 November 5, Agenda Introduction Goal of Pilot Tier Piloting Activity to Pilot Role of Connecticut in the pilot Standards and Technologies.
OMKAR Solutions Inc. EMM – Error Message Manager Version 1.0.
BUILDING INFORMATION SYSTEMS
1 State of Connecticut Core-CT Project HRMS Training Registration July, 2003.
Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.
1 IDN 2010 SUPPLY CHAIN EXCELLENCE Resource Efficiencies and Cost Savings Scottsdale Healthcare, Scottsdale, AZ Mark Willmore, Purchasing Manager.
Facilitated Transaction Checkout Improving Operational Efficiency.
24 October 2006 Industry Dialogue on xoserve services – Work Plan.
Next Generation Trnsport Trnsport Users Group Conference Field Management TAG November 7, 2005.
The views expressed in this presentation are those of the presenter, not necessarily those of the IASB or IFRS Foundation. International Financial Reporting.
Web Development Process Description
PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it.
Prescriptive Process models
Software Configuration Management: Selecting the Right Tool Chetan Desai Software Project Management SWEN 5230 Dr. Boetticher.
Confidential 1 HIPAA Compliance at Blue Cross Blue Shield of Minnesota: A Case Study Tim Wittenburg Director of Corporate Architecture & Data Management.
Software Models. A software life-cycle model is a descriptive and diagrammatic representation of the software life-cycle. This includes a series of.
Experience with an IT Asset Management System
APPLICATION Provisioning & Management made EASY EASY to ManageEASY to Manage EASY to MarketEASY to Market.
Chapter 3 Process Models
SNOMED CT Vendor Introduction 27 th October :30 (CET) Implementation Special Interest Group Tom Seabury IHTSDO.
XML - Beyond the Hype Everything you must know to succeed in implementing XML Lisa Shreve - Syscom Strategies Mike Rawlins - Rawlins EDI Consulting.
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
Presented by: Masoud Shams Ahmadi February 2007 Enterprise Resource Planning (ERP) Selection Presented by: Masoud Shams Ahmadi
CS 5380 Software Engineering Chapter 2 – Software Processes Chapter 2 Software Processes1.
“My Business Rules” Business Presentation Template Source: Springboard Presentation Template.
Reuse Standards Dr. Carma McClure Extended Intelligence, Inc. Copyright (c) 1998 by Extended Intelligence, Inc.
HIPAA Security John Parmigiani Director HIPAA Compliance Services CTG HealthCare Solutions, Inc.
© 2017 SlidePlayer.com Inc. All rights reserved.