1 / 20

Rust Enterprise Transitions

Rust Enterprise Transitions. Reactive to Proactive. History. Processes 100% Custom Application Development for each Case – cut and paste at best Completely Isolated environments and process allowing little planning as requirement

garson
Télécharger la présentation

Rust Enterprise Transitions

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. Rust Enterprise Transitions Reactive to Proactive

  2. History Processes • 100% Custom Application Development for each Case – cut and paste at best • Completely Isolated environments and process allowing little planning as requirement • Fits Specific Clients Very Well; but scales and is repeatable at high cost • Good if all time is billable and cost is not an object Limitations • All Clients Require Custom Development or heavy modification • Minimal Reuse of Previous Efforts • Limited Clients who Fit Domain Model resulting in many different applications, tools, technologies, and teams. • Unfeasible to Add a New Business Services

  3. From Past to Present

  4. Present Process • Configure claims processing versus modify and develop • If required build custom business rule enforcement • If required build custom web site Limitations • Duplication of effort in rules enforcement • 100% of web sites require development • Significant effort to add new business service(s)

  5. From Present to Near Future

  6. Near Future Process • Pricing Model Moves From Time Based to Service or Unit Based • Information Technology Configure Business Rules • Business Line(s) Configure Case Web Sites • Costs Per Case Go Down • Profits Per Case Go Up (in a unit price model) Limitations • 100% Business Rules Still Involve Information Technology Involvement • Still Solving Problems With Significant Effort

  7. From Near Future to End Game

  8. Service Orientation Process • Business lines perceive company as a combination of all or some services to clients and vendors • Information technology perceives company as services to business and clients • Business can monitor services for inefficiencies and performance • Services can be added, replaced, or removed or re-orchestrated as the market flexes or inefficiencies are discovered • Inefficiencies are easy if not transparent to discover.

  9. Accidental Architecture • Architecture of an enterprise: • Grown by adding silo processes • Acquired by acquisition • Common when trees block view of forest • Causes inflexibility and high costs when: • Expanding business processes • Automating repeated tasks in business processes • Minimizing duplication in business processes • Merging business processes • Searching for places to improve

  10. Columnar inventory of apps

  11. Interaction of current apps - solutions

  12. Columnar stack view of near term

  13. Near Future Interaction

  14. Service Oriented Architecture

  15. Enterprise Transition

  16. Enterprise Transition

  17. New / Changing Services…

More Related