1 / 28

Open and Shared Information System (OaSIS)

Open and Shared Information System (OaSIS). Today’s Agenda. Introduction to SUNCOM’s OaSIS: Mike Kyvik: Chief of Operations, Division of Telecommunications, DMS (michael.kyvik@dms.myflorida.com) What is OaSIS? Why are we building OaSIS? OaSIS development and deployment strategies

apria
Download Presentation

Open and Shared Information System (OaSIS)

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. Open and SharedInformation System(OaSIS)

  2. Today’s Agenda • Introduction to SUNCOM’s OaSIS: Mike Kyvik: Chief of Operations, Division of Telecommunications, DMS (michael.kyvik@dms.myflorida.com) • What is OaSIS? • Why are we building OaSIS? • OaSIS development and deployment strategies • Revolutionary development • Evolutionary deployment • Samples from OaSIS: Jeremy Daniell, DivTel Project Manager, (jeremy.daniell@dms.myflorida.com) • Questions & Answers

  3. Open and Shared Information System Components • Customer account management • Billing • Inventory management • Order processing

  4. Conditions Leadingto OaSIS Development • Patchwork of legacy SUNCOM systems • System enhancements driven by events rather than strategies • Data structure did not effectively use relational models • Customer interfaces lacking • Duplication of “shadow” systems among customers

  5. Evolutionary Migration • Data and algorithms from existing systems reused in backend • Piecemeal replacement of existing components • Deployment overlaps legacy system • (no “flash-cut”)

  6. Revolutionary Technical Approach(click for linked detail) m Metadata tags Open & Shared Library Database restructuring <xml/> Messaging Framework

  7. List of available applications OaSIS Management Tools

  8. Drop down menus Application Library

  9. Direct navigation View Organizations and Accounts in context

  10. View invoices by month View bill information by organization Cascade bill information by service category

  11. Expand service detail Tag item with supplemental information Expand item detail Reverse lookup & Filter by phone number

  12. Add supplemental information Identify public or personal

  13. Available downloads Tag follows item through OaSIS

  14. Delete Tag

  15. Graph service detail

  16. View bill information by invoice Expand billed items by invoice Download PDF invoices

  17. View bill information by account Summarization

  18. View bill information by service category and service

  19. View bill information by Item

  20. Next Steps • OaSIS Beta Bill Viewer available now with Production data • Contact us when you are ready to use it • Will pick a date and announce Bill Viewer training within next two weeks • Soon moving Bill Viewer to pure Production status • Inventory module coming soon • Order process in development • Integration of Mobile Communications Services in design phase

  21. Questions? Mike Kyvik: Chief of Operations Division of Telecommunications Department of Management Services Michael.Kyvik@DMS.MyFlorida.com 921-6481 Jeremy Daniell: OaSIS Project Manager Division of Telecommunications Department of Management Services Jeremy.Daniel@DMS.MyFlorida.com 413-9172

  22. Metadata Tags m • Metadata is in SUNCOM systems but exclusively controlled by the customer • Related to SUNCOM data • Will allow customers to label any data they can see like… • phone numbers with the name of the phone user • circuits with specific locations • any service with grant IDs, project IDs, etc. • Become permanent, universal tag until customer changes it • Can insert tags at any stage and use in any other stage • Order • Inventory • Invoice • Audit

  23. Database Restructuring • Establish new relationships between data • Eliminate the restrictions of intelligent codes (like CSA) and the need to understand them • Empower customers to… • Create accounts • Establish hierarchy (like organization structure) • Move services between accounts • Consolidate bills

  24. Open and Shared Library m • Customers will be able to write custom applications using… • SUNCOM dataMeta data • Application Program Interfaces (APIs) • Standard functions written by SUNCOM • Customers will be able to use and modify software written by others • Shared software application library • Community of developers

  25. Messaging <xml/> • Allow vendors and SUNCOM to pass data to each other in real time • Example uses: • Customers order from vendor’s web site, OASIS immediately gets all necessary CSA data from vendor • Centralizes order and inventory data no matter where order is submitted • Vendor updates vendor records upon service activation, then sends updates to OASIS • Eliminate double entry and improve accuracy

  26. OaSIS Framework • Standardized interfaces (APIs) • For customers writing applications • For vendors exchanging data and processes • Simplify future development • Functions developed once, reused in many areas and by many developers • Eliminate duplicated functions

  27. Empowering SUNCOM Customers m • Permanently tag services and charges • Create/modify accounts • Consolidate or separate bills • Establish and empower users • Write own custom applications for… • Orders • Invoices • Audits • etc. • …using standardized interfaces and routines • …and modifying applications written by others • Order from anywhere <xml/>

More Related