1 / 22

Collaboration and SOA: The HUD CIO Perspective

Collaboration and SOA: The HUD CIO Perspective. Agenda. A New HUD – iMPACT 200 HUD Modernization Plan Target Enterprise Architecture SOA Infrastructure Transition to SOA. HUD Business Overview – Impact200. Promote responsible, sustainable homeownership for all Americans

shira
Download Presentation

Collaboration and SOA: The HUD CIO Perspective

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. Collaboration and SOA:The HUD CIO Perspective

  2. Agenda • A New HUD – iMPACT 200 • HUD Modernization Plan • Target Enterprise Architecture • SOA Infrastructure • Transition to SOA

  3. HUD Business Overview – Impact200 • Promote responsible, sustainable homeownership for all Americans • Maximize options for safe and affordable housing so all Americans can embark on a path to self-sufficiency • Deliver effective, timely service to our customers, employees and partners

  4. HUD Business Architecture Services

  5. FY2008 IT Portfolio

  6. HUD Modernization Plan • Modernization Plan • Define Baseline Architecture • Analyze Baseline to Identify Improvements • Define Target Architecture • Perform Gap Analysis Between Target and Baseline Architecture • Develop Sequence Plan • Monitor Performance

  7. Target Enterprise Architecture • Structured on SOA model • Characteristics of Target Architecture • Agility • Scalability • Interoperatibility • Flexibility • Innovation • Re-usability • Portability • Reduced Complexity • Extensibility

  8. Target Enterprise Architecture

  9. Competing SOA Solutions…? Microsoft SOA …How We Collaborate Internally How we Conduct Business… User Focus Business Focus Business Focus User Focus A Product Trend to Watch

  10. Oracle SOA at HUD - Business

  11. SharePoint Approach Traditional Approach SharePoint Portal Approach • Cost per user = High • Seat license includes functionality most users will never use • High Training Costs – High Difficulty • Use InfoPath and SharePoint services to interact with one or more LOB applications • Low cost of integration/ Development • Uses Tools already on Desktop • Reduces LOB Application Seat Licenses required

  12. Platform Services Storage Repository Metadata Versioning Backup Security Rights/Roles Pluggable AuthN Per Item Rights Trimming Management Admin UX Delegation Provisioning Monitoring Topology Config Mgmt Farm Services Feature Policy Extranet Site Model Rendering Templates Navigation Visual Blueprint APIs Fields/Forms OM and SOAP Events Deployment Operating System Services ASP.NET (Web Parts, Personalization, Master Pages, Provider Framework (Navigation, Security, etc.) Database Services Workflow Services Search Services SharePoint 2007 SOA Applications Collaboration DiscussionsCalendarsE-Mail IntegrationAlertsProject Mgmt “Lite”Offline Lists/Docs Portal MySitesTargetingPeople Finding Social NetworkingPrivacyProfiles Site Directory Search IndexingRelevanceMetadataCustomizable UX Content Mgmt AuthoringApprovalWeb PublishingPolicy & AuditingRights MgmtRetentionMulti-LingualStaging Biz Processes Rich/Web FormsLOB ActionsSingle Sign-OnBizTalk Integration BI Excel ServicesDashboards KPIsReport Center SQL RS/AS Integ. Biz Data in Lists Biz Data Catalog

  13. SharePoint SOA at HUD - User SharePoint Web Facing Portal Customers Partners Enterprise Portal Application Integration/ Custom Apps Portals Employees XML Web Services Team Collaboration Line Of Business Applications (PS, data warehouse, custom . . .) Personal Unified, enterprise-ready solution = organizational effectiveness Controlling content Decision making Information sharing

  14. Benefits of SOA at HUD • Align Business with IT by driving IT through Business Process Management • Improve Customer satisfaction by streamlining and automating business processes • Achieve Business Agility using collaborative infrastructure • Reusability of services lower the maintenance cost for IT

  15. Transition to SOA • Establish an Enterprise-Wide Vision • Use a SOA Maturity Model to transition to SOA • Adopt SOA Framework to align to EA • Business Processes Management • Blueprints • Service Identification and realization • Flexible and scalable Infrastructure • Best Practices • Develop a SOA Roadmap • Communicate SOA Governance

  16. Initial Steps at HUD for Transition • Current Steps • Standardize the Presentation Layer using Portal Technologies • Use the SOA Infrastructure for transitioning • Identify Services performed by the current applications • Identify new/re-usable services • Establish standards for interoperation • Orchestrate current business processes using these services • Going Forward • Optimize the business processes • Re-engineer the current applications using SOA

  17. Current Projects in Transition • National Housing Locator System (NHLS) • FEMA Interfaces to Disaster Information System

  18. National Housing Locator System • NHLS provides disaster affected citizens help by allowing them to search for temporary housing • Citizens can easily navigate the NHLS application with no help. • Can Look for Current Disasters • User friendly with familiar tools; Google Maps, simple searches, navigable interface • Resource/Disaster locator: one stop shop for a citizen to find disaster information • they can look for disaster related resources near their current location (find a shelter nearby) • HUD will be able to provide briefs using Announcement tools on NHLS (in development) • 24/7 available public access via web • Citizens able to get HUD Disaster announcements • This improves communication between Agency and the Citizen

  19. A SOA Success Story: NHLS • Rich User Experience • User friendly • Utilizes AJAX for fluid user navigation • Commenting & Mapping system • Desktop application look-and-feel under a distributed Web environment • Long-Tail Approach to Data Collection • Accept data from a large number of sources • No data set is too small • Ability to collect data from numerous sources to increase the total number of units available • Rapid Application Development (RAD) • Short iterative development cycles • Developed using the RAD methodology • Utilized an Integrated Development Environment (IDE) to reduce development time • Quick and flexible development • Data Mashups • Utilizing APIs (e.g., Google Maps) as a data mashup platform • Overlays • Potential to display other overlays • Displaying grouped data enhances overall user experience • Web Service/REST • Means of data exchange between systems • Direct access to property data to outside organizations • Transfer of data using a simple form of Web service • Adhere to a standard transportation method • Perpetual Beta • Constantly accepting requirements • Soliciting requirements direct from Users • Adaptive/Corrective Maintenance

  20. Technical  Business Value • Technical  Rich User Experience • User Friendly • Utilizes AJAX for fluid user navigation • Commenting & Mapping system • Desktop application look and feel under a distributed Web environment • Business Value  User Acceptance • Reduces cost of deployment and acceptance • Reduces training costs (when Disaster Centers hire temporary workers or social volunteers – need to get them using the system fast) • We were able to train 110 FEMA users assisting Katrina disaster affected families in a 30 min. web cast • Technical  Rapid Application Development (RAD) • Short iterative development cycles • Developed using the RAD methodology • Utilized an Integrated Development Environment (IDE) to reduce development time • Quick and flexible development • Business Value  Robust • Reduces time to market • Requirements are met in a rapidly changing environment. • Ability to respond to requirements that are unpredictable like the weather • Continuous Improvement

  21. Technical  Business Value • Technical  Long-Tail Approach to Data Collection • Accept data from a large number of sources • No data set is too small • Ability to collect data from numerous sources to increase the total number of units available • Business Value  Adaptable • Accept data from a large number of sources • No data set is too small • Ability to collect data from numerous sources to increase the total number of units available • Technical  Data Mashups • Utilizing Google’s map API as a data mashup platform • Overlays • Potential to display other overlays • Displaying grouped data enhances overall user experience • Business Value  Enterprise Integration • Reduce cost by re-use (adopt) • Collaborate between program areas • Leverage existing investments • Technical  Web Service/REST • Means of data exchange between systems • Direct access to property data to outside organizations • Transfer of data using a simple form of Web service • Adhere to a standard transportation method • Business Value  SOA • Adoption to a Service Oriented Architecture • Operational Efficiency • Faster and less expensive integration

  22. What Our Partners Can Do • Understand our Business Needs • Help CIOs Lead Cultural Change • Promote Service Reuse across the Federal Government • Make it Plug and Play – Google Example Help The Government Provide Flexible Business Processes Supported by Customer-Focused Applications, which can be Altered in a Matter of Days Instead of Months!

More Related