Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Schreiner

458 views

Published on

  • Be the first to comment

  • Be the first to like this

Schreiner

  1. 1. AGA Conference So-A-What? Department of Transportation Enterprise Services Center (ESC) Sandra Schreiner
  2. 2. Who is the ESC? <ul><li>We are the Enterprise Services Center </li></ul><ul><ul><li>Department of Transportation Shared Service Center for Financial Management </li></ul></ul><ul><ul><li>Located in Oklahoma City </li></ul></ul><ul><ul><li>800+ employees </li></ul></ul><ul><ul><li>Support over 15 distinct agencies </li></ul></ul><ul><ul><li>Services include: </li></ul></ul><ul><ul><ul><li>Financial Management Application Hosting (Delphi) </li></ul></ul></ul><ul><ul><ul><li>Accounting Operations Service </li></ul></ul></ul><ul><ul><ul><li>System Hosting </li></ul></ul></ul>
  3. 3. Office of the Director Enterprise Services Center Marshal Gimpel Staff and Support Services Nina Henson Office of Application Systems Sara Smith Office of Information Technology Cheryl Rogers Office of Customer Services Robert Stevens Office of Operational Services Bo Peeler Enterprise Services Center
  4. 4. ESC Office of Application Services Office of Application Services Sara Smith Enterprise & Departmental Systems Sandra Schreiner Custom Solutions Division Jodie Griffin Financial Systems Russell Dobbs Administrative Systems <vacant> Web & Application Development Mary Moore FAA Mission Support Systems David Thompson Simulation Development and Support Richard Oberhofer Process & Performance Support Emerging Technologies and Research & Development (R&D) Testing Team
  5. 5. ESC Road to SOA <ul><li>How did ESC get started? </li></ul><ul><ul><li>Prior experience developing Web Services </li></ul></ul><ul><ul><ul><li>E-travel </li></ul></ul></ul><ul><ul><ul><li>USBank Interface </li></ul></ul></ul><ul><ul><li>SOA hype </li></ul></ul><ul><ul><li>Needed to understand how this applies to us </li></ul></ul><ul><ul><ul><li>We need more than the sales hype! </li></ul></ul></ul><ul><ul><ul><li>Researched application of technology and the “problem” it is attempting to solve. </li></ul></ul></ul><ul><ul><ul><li>Developed a white paper that described the application to our environment and our challenges. </li></ul></ul></ul><ul><ul><li>OMB Architecture direction described for e-government and LOB initiatives </li></ul></ul><ul><ul><ul><li>Described in “Services and Component Based Architecture (SBCA), A Strategic Guide for Implementing Distributed and Reusable Components in Federal Government” </li></ul></ul></ul>
  6. 6. ESC road to SOA <ul><li>Need to support multiple solutions for multiple customers </li></ul><ul><ul><li>Support 2 different payroll interfaces (NFC, NBC) </li></ul></ul><ul><ul><li>Support multiple acquisition interfaces for different customers </li></ul></ul><ul><li>Need to support integration to external e-government solutions </li></ul><ul><ul><li>E-travel </li></ul></ul><ul><ul><li>USBank </li></ul></ul><ul><ul><li>E-payroll </li></ul></ul><ul><li>Need to leverage prior integration efforts </li></ul>
  7. 7. Our road to SOA <ul><li>Buy-in from management </li></ul><ul><li>Purchased Oracle SOA Suite (version?) </li></ul><ul><li>Benefits Sought (PRISM Integration) </li></ul><ul><li>Early Success </li></ul><ul><li>Build out SOA Infrastructure </li></ul><ul><li>Promote Reuse </li></ul><ul><li>Enterprise Architecture </li></ul>
  8. 8. SOA Maturity Model
  9. 9. ESC road to SOA <ul><li>Maturity Level 1 (Opportunistic) </li></ul><ul><ul><li>PRISM Integration w/ GAO (Quick Win) </li></ul></ul><ul><ul><ul><li>Services developed in phases </li></ul></ul></ul><ul><ul><ul><li>Dedicated resources </li></ul></ul></ul><ul><ul><li>Get experience building, deploying and consuming services </li></ul></ul><ul><li>Maturity Level 2 (Systematic) </li></ul><ul><ul><li>Apply SOA to Simple Integration Projects </li></ul></ul><ul><ul><ul><li>GAO PRISM – go understanding of integration points </li></ul></ul></ul><ul><ul><li>Initial SOA Planning </li></ul></ul>
  10. 10. ESC road to SOA <ul><li>Identified Best Project Candidates would have following characteristics: </li></ul><ul><ul><li>Event driven project/initiative </li></ul></ul><ul><ul><ul><li>Did not want to apply to batch driven processes since ROI would be minimized </li></ul></ul></ul><ul><ul><li>Initiative that included: </li></ul></ul><ul><ul><ul><li>Lookups </li></ul></ul></ul><ul><ul><ul><li>Transactional processing </li></ul></ul></ul><ul><ul><li>Initiative that an iterative approach could be applied </li></ul></ul><ul><ul><ul><li>So lessons learned from prior iterations could be applied rapidly </li></ul></ul></ul><ul><ul><li>Initiative that involved the Delphi financial system </li></ul></ul>
  11. 11. ESC First SOA Project <ul><li>Oracle Federal Financial (Delphi) integration with Compusearch PRISM </li></ul><ul><ul><li>Currently tightly integrated using OCI </li></ul></ul><ul><li>Redeveloping OCI calls into Web Services </li></ul><ul><li>Focus is on reuse with Delphi/PRISM as the first consumer of services </li></ul><ul><li>First implementation is for GAO </li></ul>
  12. 12. SOA Project Selection Criteria <ul><li>OCI intrusive to Delphi environment </li></ul><ul><ul><li>Bypasses Oracle business rule enforcements </li></ul></ul><ul><ul><li>Data issues </li></ul></ul><ul><ul><li>Many hours expended by Delphi staff to support </li></ul></ul><ul><li>OCI supported by expensive consultants </li></ul><ul><li>PRISM system availability impacted by Financial system down time </li></ul><ul><li>Not reusable by other acquisition solutions or other environments </li></ul>
  13. 13. SOA Services in Scope <ul><li>Create Purchase Order </li></ul><ul><li>Modify Purchase Order </li></ul><ul><li>Release Purchase Order </li></ul><ul><li>Close Purchase Order </li></ul><ul><li>Create Standard Purchase Order </li></ul><ul><li>Create BPA </li></ul><ul><li>Modify BPA </li></ul><ul><li>Create Contract </li></ul><ul><li>Modify Contract </li></ul><ul><li>Cancel Award (PO) </li></ul><ul><li>Create Requisition </li></ul><ul><li>Cancel Requisition </li></ul><ul><li>Create Vendor </li></ul><ul><li>Process Transmittal </li></ul><ul><li>Process Acceptance (receipts) </li></ul><ul><li>Create Invoice </li></ul><ul><li>Modify Invoice </li></ul><ul><li>Cancel Invoice </li></ul><ul><li>Create Ship To </li></ul><ul><li>Modify Ship To </li></ul><ul><li>Create Bill To </li></ul><ul><li>Modify Bill To </li></ul><ul><li>Accounting Flex Fields (AFF) </li></ul><ul><li>Account CCID </li></ul><ul><li>Project </li></ul><ul><li>Task </li></ul><ul><li>Expenditure Type </li></ul><ul><li>Expenditure Org </li></ul><ul><li>USSGL Trans Code </li></ul><ul><li>Payment Terms </li></ul><ul><li>Funds Checker </li></ul><ul><li>Dynamic insert </li></ul>
  14. 15. Initial SOA Objectives <ul><li>Install SOA Infrastructure </li></ul><ul><ul><li>Configure Middle Tier </li></ul></ul><ul><li>Develop experience implementing and using tools </li></ul><ul><li>Ensure reusability </li></ul><ul><li>Develop standards </li></ul><ul><li>Loose Integration </li></ul><ul><ul><li>Less dependency on system availability </li></ul></ul><ul><ul><li>Tight data integration </li></ul></ul>
  15. 17. Project Timeline
  16. 18. Project Challenges <ul><li>Resources </li></ul><ul><ul><li>Resources not provided for a “build it and they will come” type initiative </li></ul></ul><ul><ul><li>Financial centric project team too focused on financials and not focused enough on enterprise </li></ul></ul><ul><li>Lessons Learned </li></ul><ul><ul><li>ESC needed an initiative to allocate resources to embark on a SOA initiative (Delphi/PRISM Integration) </li></ul></ul><ul><ul><li>Project team includes expertise from other ESC enterprise systems </li></ul></ul>
  17. 19. Project Challenges <ul><li>Technical </li></ul><ul><ul><li>Product Learning Curve </li></ul></ul><ul><ul><li>Interoperability (XML standards) </li></ul></ul><ul><ul><li>Product Maturity </li></ul></ul><ul><ul><ul><li>Suite incompatibilities </li></ul></ul></ul><ul><ul><ul><li>Software bugs </li></ul></ul></ul><ul><ul><li>Existing Oracle packages for interfaces are not very reusable </li></ul></ul><ul><li>Lessons Learned </li></ul><ul><ul><li>Having expertise in other development environments (ie. Microsoft Developer) </li></ul></ul><ul><ul><li>Spend time upfront developing design, approach, and standards </li></ul></ul><ul><ul><li>Keep services simple and “pure” to maximize reusability </li></ul></ul>
  18. 20. SO-A What’s Next? <ul><li>Complete Delphi / PRISM integration effort for GAO </li></ul><ul><li>Implement other DOT agencies on integrated solution </li></ul><ul><li>Replace FAA OCI interface </li></ul><ul><li>Re-engineer original e-travel and USBank web services </li></ul><ul><li>Leverage services on new integration opportunities </li></ul>
  19. 21. ESC Enterprise Goal

×