PWB533: PowerBuilder Applications Form Service-Oriented Architecture

1. PWB533: PowerBuilder Applications Form Service-Oriented Architecture Chris Swearingen Principal, System Strategies, Inc c.swearingen@SystemStrategies.com August 15-19, 2004

2. History • Naval Facilities Engineering Command • NAVFAC manages planning, design, construction and maintenance of shore facilities for U.S. Navy activities around the world. Effort includes over 20,000 annual acquisition projects worth $5B. • NAVFAC’s 20K annual projects generate 64K contract actions that are managed by a global, 5,000 person “engineer-acquisition team”. • Standard Procurement System • Deployed to over 23,000 users at 360+ plus sites (DoD) • When fully implemented, over 43,000 users at over 900 Defense procurement sites will be using this system. • Facilities Information System • NAVFAC Legacy Mainframe Application

3. ‘Untouchable’ systems prevent collaborative, end-to-end delivery PROGRAM MGMT What does NAVFAC Do? 1st Qtr 2nd Qtr 3rd Qtr 4th Qtr

4. The $5B Acquisition Quagmire 1st Qtr 2nd Qtr 3rd Qtr 4th Qtr

5. Defining the problem • Multiple systems, one process • Contract Management, Financial, Planning and tracking, etc. • Duplicate sometimes triplicate entry. • No consolidate means of tracking progress. • Collaboration needs • “Admiral Clark foresees a Navy that needs fewer people to accomplish its mission as it relies more on speed and agility. It will achieve this goal by integrating… it must include a faster, more collaborative acquisition process…” • Reduce Costs • NAVFAC has the mandate to demonstrate leadership and operational agility in streamlining acquisition processes and cutting costs. Each support dollar saved can be leveraged to acquire more ships and aircraft. • Estimated 9 work years involved with keeping SPS and FIS in synch.

6. Cumbersome Manual Process Step 1: Enter Order in SPS Step 2: Print out approved orders Step 3: Enter order into FIS Step 4: Enter return code back to SPS

7. Automation Consolidation Integration 1st Qtr 2nd Qtr 3rd Qtr 4th Qtr

8. Defining the Constraints • Contractual, Time and Budget • No access to data models • No modification to the applications • No “new” batch interfaces

9. Alternatives • Rewrite for integration • Too time consuming • Re-code business logic • Not enough ROI (cost > $1M, deliver in months to years)

10. Defining the Solution • Interface • Expose data from the 16 regional SPS installations • Reduce or eliminate duplicative data entry • Integrate • “You can incorporate business function into new composite applications in arelatively low-risk way using programmatic integration servers. They noninvasively access legacy systems, but are limited to the current granularity of those systems. Use them for tactical solutions when you need to cross traditional application stovepipes and combine information in a new way for new constituents, within or outside your organization. Programmatic Integration for Composite Applications,” 9 October 2003 Dale Vecchio GARTNER • Improve • Capture metrics to identify best practices and improve the process.

11. Solution • “Service-enable” SPS and FIS • Process initiated once / day • Fully automated process • Pull approved contracts from SPS • Enter them into the mainframe • Attach return codes back into SPS

12. The big question: HOW? • Programmatic Interface Servers • Jacada Fusion by Jacada -- allows “virtual user” to navigate Powerbuilder SPS application gathering required information and exposing it via web services to any platform, web, host or Windows. • Model Driven Application Framework • AppsCreate by Logical Apps -- an architecture-based code generation tool allows rapid development. • Strategic Composite Applications • Combining SOA of Jacada Fusion with the rapid development of AppsCreate allows NAVFAC to produce new interfaces in months, sometimes weeks.

13. More on: HOW? • Strategic Integration • Composite Application Development has galvanized Business, Acquisition, and Financial leaders around a common solution that preserves their core, legacy systems and provides new web-based, end-to-end capability. • Phased approach • Pilot effort to interface SPS to FIS underway at NAVFAC’s Southern Division • Composite app to integrate business processes into single application undergoing final testing now, expected to roll out before the end of the calendar year

14. Automated Process • Step 1 - Enter Order in SPS • Step 2 Initiate Data Transformation & Routing Logic

15. NAVFAC Architecture

16. Reactions • User Community • “WOW – I only have to enter information in one place?” • Leadership • “WOW – I only have to look for information in one place?”

17. Results • PowerBuilder SPS application is fully integrated -- using non-intrusive service-enablement – with NAVFAC’s mainframe transactional systems and Web collaboration-centric business systems • For the first time, NAVFAC transactions are automated and data integrated for the solicitation, awarding and modification of contracts. • SPS-to-FIS interface was developed in two months and deployed to a pilot site within 4 months. • Now, for the first-time, NAVFAC is able to cost-effectively integrate their legacy systems and combine with the value-added, Web-based solutions that their users and business leaders demand.