Your SlideShare is downloading. ×
0
eGovernment Program Technical Architecture   Version 11 January 2003
Table of Contents <ul><li>Introduction </li></ul><ul><li>Technical Architecture - Conceptual Architecture Overview </li></...
<ul><li>USDA is creating a suite of “enterprise services” to support its strategic initiatives, enable agency and enterpri...
Introduction <ul><li>We are taking the following approach in developing these enterprise services: </li></ul>Marketing and...
Agency Roll-Out Once the enterprise eGovernment components have been deployed, agencies can roll-out these capabilities to...
Introduction <ul><li>As part of the enterprise services vision, a robust technical architecture must be defined. In defini...
Introduction <ul><li>User requirements, assessment of existing USDA infrastructure and direction of other major enterprise...
Introduction <ul><li>Three main areas are being addressed to define the technical architecture: </li></ul><ul><ul><li>Conc...
Non-Web  Centric  Application Web Presence / User Interface (Standards) Strategic Initiative (e.g. eLoans) Agency  Applica...
Conceptual Architecture Overview <ul><li>The following are definitions of the key components of the architecture: </li></u...
Conceptual Architecture Overview <ul><li>Conceptual Architecture components continued: </li></ul><ul><ul><li>eLearning </l...
Logical Architecture Overview Portal Server Web Server Web Server Application Server Database Web Server Business Partner ...
Portal Services Overview A portal integrates application systems, knowledge systems, and content in a centralized place fo...
Internet Firewall Citizen, Employee, Business Partner Employee Document Management Databases Production Environment Web Se...
Web Content Management Overview Web Content Management provides a suite of tools that enable the creation and maintenance ...
Logical Architecture Detail: Web Content Management The following is the detailed logical architecture as it relates to we...
Document/Records Management Overview Document Management facilitates the sharing of document assets across an enterprise r...
Logical Architecture Detail: Document/Records Management The following is the detailed logical architecture as it relates ...
eLearning Overview KEY FEATURES/CAPABILITIES/REQUIREMENTS INTEGRATION COMPONENT VALUE PROPOSITION eLearning provides self-...
Internet Firewall Learner (employee, citizen, partner)  Learner (employee) Document Management Production Environment Web ...
eAuthentication Overview eAuthentication offers common authentication services to applications within USDA KEY FEATURES/CA...
Logical Architecture Detail: eAuthentication The following is the detailed logical architecture as it relates to eAuthenti...
Central Data Repositories Overview Central data repositories allow re-use of data and decrease the burden on our customers...
The following is the detailed logical architecture as it relates to central data repositories: Logical Architecture Detail...
Content Aggregation / Application Integration Overview Content aggregation spawns re-use of content and enables powerful i...
The following is the detailed logical architecture as it relates to content aggregation and application integration: Logic...
Content Distribution Overview Content distribution ensures timely delivery of content and services by physically locating ...
The following is the detailed logical architecture as it relates to content distribution: Logical Architecture Detail: Con...
Existing Physical Architecture <ul><li>We will leverage existing assets within USDA to rollout the proposed architecture <...
Relationship to Other Enterprise Efforts <ul><li>The technical architecture has been designed to function within the conte...
Technical Architecture Next Steps <ul><li>Upon completion of the technical architecture, the following next steps are nece...
Upcoming SlideShare
Loading in...5
×

Technical Architecture Overview Presentation (updated 1/30/2003)

817

Published on

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
817
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
33
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • This approach is not just about technology. I mentioned that we are trying to work on a consolidated approach for all the enabling technologies. That doesn’t just mean the combining of technologies, but a holistic approach where we involve people, we have a standard methodology for delivering services to the enterprise, and processes that we all follow The text on the right is the “value proposition” if you will, for delivering these services in an integrated fashion. If you add up the costs from all the individual business cases, it’s a lot of money. But if you start to think of this as an enterprise delivery capability, you can use resources more efficiently, you can decrease the implementation times, and obviously increase coordination This approach is also a new way for the enterprise to work with OCIO on eGovernment initiatives. This can be a new customer facing view; it’s about doing business differently with a much higher focus on delivery and collaboration as opposed to one way communication.
  • Transcript of "Technical Architecture Overview Presentation (updated 1/30/2003)"

    1. 1. eGovernment Program Technical Architecture Version 11 January 2003
    2. 2. Table of Contents <ul><li>Introduction </li></ul><ul><li>Technical Architecture - Conceptual Architecture Overview </li></ul><ul><li>Conceptual Architecture Detail </li></ul><ul><li>Logical Architecture </li></ul><ul><li>Existing Physical Architecture </li></ul><ul><li>Agency Roll-Out </li></ul><ul><li>Relation to Other Enterprise Efforts </li></ul><ul><li>Next Steps </li></ul>
    3. 3. <ul><li>USDA is creating a suite of “enterprise services” to support its strategic initiatives, enable agency and enterprise program delivery, leverage investments, and save costs </li></ul>Introduction <ul><ul><li>The creation of enterprise services does not only mean the purchase and implementation of technologies, but a holistic approach involving people, operational processes, technology, and an underlying delivery methodology </li></ul></ul><ul><ul><li>Enterprise-level services allow USDA to: </li></ul></ul><ul><ul><ul><li>Use its resources to focus on program delivery instead of technical infrastructure </li></ul></ul></ul><ul><ul><ul><li>Leverage its current and future investments and realize significant cost avoidance </li></ul></ul></ul><ul><ul><ul><li>Facilitate the sharing of best practices through collaborative design, development, and operations </li></ul></ul></ul><ul><ul><ul><li>Implement standard technology and development methodology across the Department </li></ul></ul></ul><ul><ul><ul><li>Decrease implementation times by leveraging best practices and utilizing a skilled central team </li></ul></ul></ul><ul><ul><ul><li>Communicate as “one voice” to business partners, technology vendors, and employees </li></ul></ul></ul><ul><ul><li>This presentation will focus on the technology piece of the Enterprise Services concept </li></ul></ul>Standard Methodology Agency programs and strategic initiatives Enterprise Services People Technology Operational Processes
    4. 4. Introduction <ul><li>We are taking the following approach in developing these enterprise services: </li></ul>Marketing and Communications Program Management Approach (Enterprise Solutions Center) 2Q02 3Q02 4Q02 1Q03 2Q03 3Q03 4Q03 1Q04 <ul><li>Develop eGovernment Strategic Plan </li></ul><ul><ul><li>Strategic direction </li></ul></ul><ul><ul><li>24 Strategic initiatives </li></ul></ul><ul><ul><ul><li>Enabling initiatives </li></ul></ul></ul><ul><ul><ul><li>Strategic initiatives </li></ul></ul></ul><ul><li>Pre-Select Business Cases </li></ul><ul><ul><li>Initial vision </li></ul></ul><ul><ul><li>Cost/benefit analysis </li></ul></ul><ul><ul><li>Initial impact analysis </li></ul></ul><ul><li>Implementation and Investment Planning </li></ul><ul><ul><li>Functional & Technical requirements </li></ul></ul><ul><ul><li>Program management approach </li></ul></ul><ul><ul><li>Comprehensive technical architecture </li></ul></ul><ul><ul><li>Implementation Plans </li></ul></ul><ul><ul><li>Cost/benefit analysis </li></ul></ul><ul><ul><li>Impact analysis </li></ul></ul>Select-level Business Cases Change Management Planning and Implementation Decision to plan and implement Enabling initiatives <ul><li>Vendor Assessment & Detailed Planning </li></ul><ul><ul><li>Secure hosting SLA’s </li></ul></ul><ul><ul><li>Determine early adopters </li></ul></ul><ul><ul><li>Issue vendor RFP’s </li></ul></ul><ul><ul><li>Conduct formal product selection </li></ul></ul>Signed Contracts & Procurement <ul><li>Installation & Testing </li></ul><ul><ul><li>Set up hardware </li></ul></ul><ul><ul><li>Install software </li></ul></ul><ul><ul><li>Perform necessary custom development (integration) </li></ul></ul><ul><ul><li>System test </li></ul></ul><ul><li>eAuthentication Services </li></ul><ul><ul><li>Publish guide for application developers </li></ul></ul><ul><ul><li>Build out service </li></ul></ul>Early Adopter Development / Strategic Initiative Development <ul><li>Rollout of version 1 of eDeployment capabilities </li></ul><ul><li>Development of version X of eDeployment capabilities </li></ul>Project Management (ongoing) (ongoing) (Basic services available) Technology
    5. 5. Agency Roll-Out Once the enterprise eGovernment components have been deployed, agencies can roll-out these capabilities to their users under a “Subscriber Agency Model” or a “Hosting Agency Model” Subscriber Agency Model <ul><ul><li>Under this model agencies would use the shared, enterprise instance of the eGovernment capabilities </li></ul></ul><ul><ul><li>Each agency would be provided with its own secure, virtual space on the enterprise solution which will contain: </li></ul></ul><ul><ul><ul><li>Secure content storage area </li></ul></ul></ul><ul><ul><ul><li>User and administrator accounts </li></ul></ul></ul><ul><ul><ul><li>Workflows specific to the agency’s business processes </li></ul></ul></ul><ul><ul><ul><li>Content authoring, workflow authoring, user and application administration capabilities </li></ul></ul></ul><ul><ul><li>This model is cost effective to the agency and best leverages department and agency resources </li></ul></ul><ul><ul><li>eGovernment team would provide rollout support </li></ul></ul>Hosting Agency Model <ul><ul><li>The Hosting Agency Model would allow an agency to host and use its own instance of the enterprise eGovernment solutions </li></ul></ul><ul><ul><li>This model is designed for agencies which have very unique business needs that require a high amount of customization and integration of the eGovernment solutions </li></ul></ul><ul><ul><li>Under the Hosting Model, an agency would be provided with: </li></ul></ul><ul><ul><ul><li>Copies of select eGovernment components to host on agency servers </li></ul></ul></ul><ul><ul><ul><li>Strict guidelines on customization and integration of eGovernment components to ensure compatibility with future eGovernment releases </li></ul></ul></ul><ul><ul><ul><li>Development support to install, customize and integrate eGovernment components </li></ul></ul></ul><ul><ul><li>This model would be more expensive for an agency to roll-out and maintain </li></ul></ul>
    6. 6. Introduction <ul><li>As part of the enterprise services vision, a robust technical architecture must be defined. In defining a technical architecture, we had the following goals in mind: </li></ul><ul><ul><li>Support eGovernment initiatives throughout the Enterprise </li></ul></ul><ul><ul><ul><li>Enterprise-wide initiatives </li></ul></ul></ul><ul><ul><ul><li>Cross-agency strategic initiatives </li></ul></ul></ul><ul><ul><ul><li>Single-agency initiatives </li></ul></ul></ul><ul><ul><ul><li>Federal Government initiatives </li></ul></ul></ul><ul><ul><li>Define a scalable and robust architecture that would integrate and leverage current capabilities at the Department and agency level </li></ul></ul><ul><ul><li>Complement current initiatives already underway such as efforts around defining our Enterprise Architecture and expanding our telecommunication capabilities </li></ul></ul><ul><ul><ul><li>Support of initiatives that support common business processes </li></ul></ul></ul><ul><ul><ul><li>Help define the technical layer of the enterprise architecture </li></ul></ul></ul><ul><ul><li>The definition of a technical architecture does NOT: </li></ul></ul><ul><ul><ul><li>Replace existing business-specific agency applications </li></ul></ul></ul><ul><ul><ul><li>Force agency applications to be hosted in a centralized location </li></ul></ul></ul><ul><ul><ul><li>Take control of business applications from agencies </li></ul></ul></ul>
    7. 7. Introduction <ul><li>User requirements, assessment of existing USDA infrastructure and direction of other major enterprise initiatives were used as input into developing the technical architecture </li></ul><ul><ul><li>Functional and technical requirements were collected from agency representatives </li></ul></ul><ul><ul><ul><li>Working groups representing the different agencies within USDA were formed around different technology areas of the architecture. These groups generated and refined a list of requirements around each solution area </li></ul></ul></ul><ul><ul><li>Assessment of existing initiatives & infrastructure to see how our effort fits into the bigger picture </li></ul></ul><ul><ul><ul><li>Meetings with Enterprise Architecture initiative. Read through and understood vision documentation for Enterprise Architecture </li></ul></ul></ul><ul><ul><ul><li>Site visit of major USDA hosting facility (NITC). Planned visits of Service Center facilities </li></ul></ul></ul><ul><ul><ul><li>Collaboration with UTN effort </li></ul></ul></ul><ul><ul><li>Leverage best practices from the private and public sectors </li></ul></ul><ul><ul><ul><li>Expertise and lessons learned from other Federal government agencies such as Department of Education, Department of Defense, Department of State and FCC proved to be valuable resources in developing our technical architecture </li></ul></ul></ul><ul><ul><ul><li>Best practices from private sector organizations and standards bodies were used also used as input to the technical architecture process </li></ul></ul></ul>
    8. 8. Introduction <ul><li>Three main areas are being addressed to define the technical architecture: </li></ul><ul><ul><li>Conceptual architecture </li></ul></ul><ul><ul><ul><li>The conceptual architecture shows the components of the architecture and how they relate to one another. It is the highest-level view of the architecture and is not specific to any particular technology </li></ul></ul></ul><ul><ul><li>Logical architecture </li></ul></ul><ul><ul><ul><li>The logical architecture takes the conceptual architecture and adds to it by showing the data/information flows and integration points between the components of the architecture </li></ul></ul></ul><ul><ul><ul><li>The logical architecture shows how USDA expects the components of its architecture to work cohesively. It is not specific to particular technologies, but is an excellent tool to leverage during the vendor selection process </li></ul></ul></ul><ul><ul><li>Physical architecture </li></ul></ul><ul><ul><ul><li>The physical architecture defines the specifications for the hardware and software for the components discussed in the logical architecture. It also states where the hardware and software is located, number of licenses required, and other specific information </li></ul></ul></ul><ul><ul><ul><li>The physical architecture will be defined as part of the vendor assessment phase of the eGovernment Program </li></ul></ul></ul>
    9. 9. Non-Web Centric Application Web Presence / User Interface (Standards) Strategic Initiative (e.g. eLoans) Agency Applications DigiTop eAuthentication (Single sign-on, Digital Signatures) Enterprise Web Content Enterprise Document Content Shared Database Agency Database Content Aggregation/Application Integration (enterprise search) External Content Source Web Content Management Document/ Records Management Data Management Program (Standards,Policies,Services) eLearning Presentation Business Logic/Application Data Citizens Content Distribution Support Capability Non eGov Component Enabler Initiative Component Strategic Initiative Component Standards & Policies Employees Business Partners Customers Portal(s) USDA Strategic Plan Enterprise Architecture Inter-agency Applications Conceptual Architecture Overview Data/Content Department Metadata and Taxonomy Standards
    10. 10. Conceptual Architecture Overview <ul><li>The following are definitions of the key components of the architecture: </li></ul><ul><ul><li>Web Presence </li></ul></ul><ul><ul><ul><li>Web Presence will create standards and guidelines to standardize look and feel of web pages and applications across USDA </li></ul></ul></ul><ul><ul><ul><li>Navigation standards will enhance usability of all internal and external USDA web sites </li></ul></ul></ul><ul><ul><li>Portal(s) </li></ul></ul><ul><ul><ul><li>A portal integrates application systems, knowledge systems, and content in a centralized place for a targeted audience </li></ul></ul></ul><ul><ul><li>Web Content Management </li></ul></ul><ul><ul><ul><li>An enterprise Web Content Management capability will provide tools to aid in the creation, review, deployments and maintenance of web application content </li></ul></ul></ul><ul><ul><li>Document/Records Management </li></ul></ul><ul><ul><ul><li>Through publishing and search tools, a document management system will orchestrate the sharing of document assets across USDA </li></ul></ul></ul><ul><ul><li>eAuthentication </li></ul></ul><ul><ul><ul><li>The eAuthentication component will provide user authentication and digital signature services to existing and future USDA applications </li></ul></ul></ul>
    11. 11. Conceptual Architecture Overview <ul><li>Conceptual Architecture components continued: </li></ul><ul><ul><li>eLearning </li></ul></ul><ul><ul><ul><li>eLearning provides self-paced and collaborative learning experiences, delivered over the web, designed to promote comprehension and retention </li></ul></ul></ul><ul><ul><li>Data Management </li></ul></ul><ul><ul><ul><li>The Data Management component represents standards, policies and services around database/data design and implementation. These standards will reduce data redundancy, improve data quality, promote interoperability and data reuse </li></ul></ul></ul><ul><ul><li>Content Aggregation/Application Integration </li></ul></ul><ul><ul><ul><li>The Content Aggregation/Application Integration component provides integration of content and application services for use by portals and other agency and cross agency applications </li></ul></ul></ul><ul><ul><ul><li>A centralized index will allow ubiquitous searching of distributed, heterogeneous content/data repositories </li></ul></ul></ul><ul><ul><li>Content Distribution </li></ul></ul><ul><ul><ul><li>The Content Distribution component will facilitate the deployment of content to distributed servers for optimal delivery of content. Distribution of content will reduce application response time, ultimately enhancing the user experience </li></ul></ul></ul>
    12. 12. Logical Architecture Overview Portal Server Web Server Web Server Application Server Database Web Server Business Partner Database Citizen Employee Agency II Application Agency I Application Enterprise Portal Application Hypertext Link Content aggregation/ Indexing server EAI Server Firewall Legacy Systems Deploy Content Index, Search, Integrate Index Index App Integration Access Index, Search Existing Legacy Integration App Integration User name, Pass authenticate eLearning User Info Token Central Data Repositories eAuthentication Web Server App Integration Index Content Management Document/ Records Management Intranet
    13. 13. Portal Services Overview A portal integrates application systems, knowledge systems, and content in a centralized place for a targeted audience KEY FEATURES/CAPABILITIES/REQUIREMENTS INTEGRATION COMPONENT VALUE PROPOSITION <ul><ul><li>Flexible feature set based on the type of portal being created: </li></ul></ul><ul><ul><ul><li>Internal and External Horizontal portals span a large range of information topics or large range of services </li></ul></ul></ul><ul><ul><ul><li>Internal and External Vertical portals cover one or multiple topic areas very deeply or are integrated with specific applications </li></ul></ul></ul><ul><ul><ul><li>Internal workgroup portals focus on aggregating internal services and information and often house collaboration capabilities </li></ul></ul></ul><ul><ul><li>Legacy system integration </li></ul></ul><ul><ul><li>Personalization of user experience </li></ul></ul><ul><ul><ul><li>Personalization of the user interface </li></ul></ul></ul><ul><ul><ul><li>Personalization of content delivery / application functionality </li></ul></ul></ul><ul><ul><ul><li>Role-based personalization </li></ul></ul></ul><ul><ul><li>Integration with eAuthentication solutions </li></ul></ul><ul><ul><ul><li>Single/enterprise sign-on </li></ul></ul></ul><ul><ul><li>Aggregate existing agency and enterprise applications and content </li></ul></ul><ul><ul><li>Integrate with existing legacy systems to provide web-based user experience, access to legacy system business logic and data </li></ul></ul><ul><ul><li>Work tightly with web content management solution to drive standard user-interface design and content automation </li></ul></ul><ul><ul><li>eAuthentication </li></ul></ul><ul><ul><li>Vital to the aggregation of content across agencies: helps achieve goal of intentions-based design vs. organization-based design </li></ul></ul>Non-Web Centric Application Web Presence / User Interface Strategic Initiative (e.g. eLoans) Agency Applications DigiTop eAuth (Single sign-on, Digital Sig.) Enterprise Web Content Enterprise Document Content Shared Database Content Agency Database Content Content Aggregation/Application Integration External Content Source Web Content Management Document Management Data Management Program (Standards,Policies,Services) eLearning Presentation Business Logic Data Content Distribution Portal(s) Inter-agency Applications
    14. 14. Internet Firewall Citizen, Employee, Business Partner Employee Document Management Databases Production Environment Web Servers Portal Server Database Media Server Legacy Apps Web Server Portal Server Load Testing Environment Load Simulation Server Media Server Database Web Server Database Development/Configuration Environment Reporting Server Indexing Server Agency/Cross-Agency Web Applications Media Server Collaboration Server Email Servers eAuthentication App Integration/ Content Aggregation Logical Architecture Detail: Portal(s) The following is the detailed logical architecture as it relates to portals: Web Content Management Internet Intranet Non-Web Centric Application Web Presence / User Interface Strategic Initiative (e.g. eLoans) Agency Applications DigiTop eAuth (Single sign-on, Digital Sig.) Enterprise Web Content Enterprise Document Content Shared Database Content Agency Database Content Content Aggregation/Application Integration External Content Source Web Content Management Document Management Data Management Program (Standards,Policies,Services) eLearning Presentation Business Logic Data Content Distribution Portal(s) Inter-agency Applications
    15. 15. Web Content Management Overview Web Content Management provides a suite of tools that enable the creation and maintenance of web application content more efficiently and with higher quality KEY FEATURES/CAPABILITIES/REQUIREMENTS INTEGRATION COMPONENT VALUE PROPOSITION <ul><ul><li>Integration with document management solution to make documents available via the web when applicable </li></ul></ul><ul><ul><li>Integration with common content repositories and common data repositories </li></ul></ul><ul><ul><li>Support of portal component to deliver content </li></ul></ul><ul><ul><li>To achieve strategic goals, cannot continue to manage content manually. At the crux of changing the way we do business by exposing information and business processes to our stakeholders </li></ul></ul><ul><ul><li>Supports the lifecycle of content for web-based applications: </li></ul></ul><ul><ul><ul><li>Create -The development and maintenance of standard templates that dictate standard layout </li></ul></ul></ul><ul><ul><ul><li>Review – Workflow capabilities to enable reviews of content by the right people during a designated period of time </li></ul></ul></ul><ul><ul><ul><li>Aggregate and Manage – Aggregating content from multiple content sources and supporting the classification of content using meta-data and other techniques </li></ul></ul></ul><ul><ul><ul><li>Distribute and Deliver -- Content is published to one or multiple production environments </li></ul></ul></ul><ul><ul><ul><li>Archive and Delete – Automated processes to archive or delete content </li></ul></ul></ul><ul><ul><li>Enables the publishing of content to alternative platforms such as PDA’s and cell phones </li></ul></ul><ul><ul><li>Supports the creation and delivery of interactive forms online </li></ul></ul>Non-Web Centric Application Web Presence / User Interface Strategic Initiative (e.g. eLoans) Agency Applications DigiTop eAuth (Single sign-on, Digital Sig.) Enterprise Web Content Enterprise Document Content Shared Database Content Agency Database Content Content Aggregation/Application Integration External Content Source Web Content Management Document Management Data Management Program (Standards,Policies,Services) eLearning Presentation Business Logic Data Content Distribution Portal(s) Inter-agency Applications
    16. 16. Logical Architecture Detail: Web Content Management The following is the detailed logical architecture as it relates to web content management: Content Delivery Mediums Load Testing Environment Template Development Desktop Document Management Content Development Workstation Template/ Content Development Server Web Server Application Server Database Content Staging Environment Content Approval Workstation Web Server Application Server Database Load Simulation Server Portal Agency/Cross-Agency Web Applications Applications on Wireless Devices Legacy Apps Web Server Media Server Database App Integration/ Content Aggregation eAuthentication Employee Employee Employee Email Servers Non-Web Centric Application Web Presence / User Interface Strategic Initiative (e.g. eLoans) Agency Applications DigiTop eAuth (Single sign-on, Digital Sig.) Enterprise Web Content Enterprise Document Content Shared Database Content Agency Database Content Content Aggregation/Application Integration External Content Source Web Content Management Document Management Data Management Program (Standards,Policies,Services) eLearning Presentation Business Logic Data Content Distribution Portal(s) Inter-agency Applications
    17. 17. Document/Records Management Overview Document Management facilitates the sharing of document assets across an enterprise reducing rework, enhancing productivity and quality of work KEY FEATURES/CAPABILITIES/REQUIREMENTS INTEGRATION COMPONENT VALUE PROPOSITION <ul><ul><li>Supports the lifecycle for documents and other electronic assets: </li></ul></ul><ul><ul><ul><li>Create - Support for all commonly used file types and appendage of meta-data upon creation of asset </li></ul></ul></ul><ul><ul><ul><li>Review - Web-based or desktop-based workflow tools for contributors or reviewers of content </li></ul></ul></ul><ul><ul><ul><li>Aggregate and Manage - Check-in and check-out capabilities to control versions. Automated processes to maintain integrity of assets and clean up asset repositories </li></ul></ul></ul><ul><ul><ul><li>Distribute and Deliver - Multiple search mechanisms to find information, including browsing subject hierarchies, keyword, natural language, etc. </li></ul></ul></ul><ul><ul><ul><li>Archive and Delete - Integration with the National Archives to preserve electronic assets </li></ul></ul></ul><ul><ul><li>Collaboration tools </li></ul></ul><ul><ul><li>Support for a dynamic corporate taxonomy, i.e. classification of assets can be changed </li></ul></ul><ul><ul><li>Integration with content aggregation component to provide robust searching </li></ul></ul><ul><ul><li>Integration with web content management solution to push documents/assets to the web </li></ul></ul><ul><ul><li>Integration with common content repositories and common data repositories </li></ul></ul><ul><ul><li>Key to meeting goals around records management. Enables information to stay in electronic format throughout its lifecycle and enables robust information retrieval capabilities through the classification of all assets - promotes knowledge sharing through asset sharing </li></ul></ul>Non-Web Centric Application Web Presence / User Interface Strategic Initiative (e.g. eLoans) Agency Applications DigiTop eAuth (Single sign-on, Digital Sig.) Enterprise Web Content Enterprise Document Content Shared Database Content Agency Database Content Content Aggregation/Application Integration External Content Source Web Content Management Document Management Data Management Program (Standards,Policies,Services) eLearning Presentation Business Logic Data Content Distribution Portal(s) Inter-agency Applications
    18. 18. Logical Architecture Detail: Document/Records Management The following is the detailed logical architecture as it relates to document/Records management: Desktop Publishing Tools Document Delivery Mediums Content Management Document Management Server Document Approval Workstation Agency File Servers File Server Scanning Station Fax Fax Server eFax Batch Import Process Portal Agency/Cross-Agency Applications Print Citizen Legacy Systems Employee Employee Deploy Documents eAuthentication Application Integration/Content Aggregation Application Integration/Content Aggregation Email Non-Web Centric Application Web Presence / User Interface Strategic Initiative (e.g. eLoans) Agency Applications DigiTop eAuth (Single sign-on, Digital Sig.) Enterprise Web Content Enterprise Document Content Shared Database Content Agency Database Content Content Aggregation/Application Integration External Content Source Web Content Management Document Management Data Management Program (Standards,Policies,Services) eLearning Presentation Business Logic Data Content Distribution Portal(s) Inter-agency Applications
    19. 19. eLearning Overview KEY FEATURES/CAPABILITIES/REQUIREMENTS INTEGRATION COMPONENT VALUE PROPOSITION eLearning provides self-paced and collaborative learning experiences, delivered over the web, designed to promote comprehension and retention <ul><ul><li>Features to improve learning management and training administration activities such as: </li></ul></ul><ul><ul><ul><li>Administration of curriculum </li></ul></ul></ul><ul><ul><ul><li>Self-registration </li></ul></ul></ul><ul><ul><ul><li>Content creation and publishing tools </li></ul></ul></ul><ul><ul><ul><li>Standardized skills assessment </li></ul></ul></ul><ul><ul><li>Enhanced training experiences through new technologies: </li></ul></ul><ul><ul><ul><li>Individualized training </li></ul></ul></ul><ul><ul><ul><li>Online course delivery </li></ul></ul></ul><ul><ul><ul><li>Collaboration tools </li></ul></ul></ul><ul><ul><li>Seamless integration with legacy training data, human resources systems, and financial systems </li></ul></ul><ul><ul><li>Aggregate existing Agency and enterprise applications and content </li></ul></ul><ul><ul><li>Integrate with existing legacy training systems, access to legacy system business logic and data </li></ul></ul><ul><ul><li>eAuthentication </li></ul></ul><ul><ul><li>Mandated by the Presidential Management Agenda and required for USDA to maintain an effective and productive of workforce </li></ul></ul>Non-Web Centric Application Web Presence / User Interface Strategic Initiative (e.g. eLoans) Agency Applications DigiTop eAuth (Single sign-on, Digital Sig.) Enterprise Web Content Enterprise Document Content Shared Database Content Agency Database Content Content Aggregation/Application Integration External Content Source Web Content Management Document Management Data Management Program (Standards,Policies,Services) eLearning Presentation Business Logic Data Content Distribution Portal(s) Inter-agency Applications
    20. 20. Internet Firewall Learner (employee, citizen, partner) Learner (employee) Document Management Production Environment Web Servers LMS/LCMS Server Database Media Server Legacy Apps Web Server LMS/LCMS Server Load Testing Environment/Content Staging Environment Load Simulation Server Media Server Database Web Server Database Content Development/Software Configuration Environment Agency/Cross-Agency Web Applications Media Server Email Servers eAuthentication App Integration/ Content Aggregation Logical Architecture Detail: eLearning The following is the detailed logical architecture as it relates to eLearning: Internet Intranet eLearning Administrator Instructional Content Designer Portal Web Content Management Non-Web Centric Application Web Presence / User Interface Strategic Initiative (e.g. eLoans) Agency Applications DigiTop eAuth (Single sign-on, Digital Sig.) Enterprise Web Content Enterprise Document Content Shared Database Content Agency Database Content Content Aggregation/Application Integration External Content Source Web Content Management Document Management Data Management Program (Standards,Policies,Services) eLearning Presentation Business Logic Data Content Distribution Portal(s) Inter-agency Applications
    21. 21. eAuthentication Overview eAuthentication offers common authentication services to applications within USDA KEY FEATURES/CAPABILITIES/REQUIREMENTS INTEGRATION COMPONENT VALUE PROPOSITION <ul><ul><li>The following types of authentication may be created or leveraged over time, as requirements dictate: </li></ul></ul><ul><ul><ul><li>PKI Class 4 (High) Certificate </li></ul></ul></ul><ul><ul><ul><li>Biometric </li></ul></ul></ul><ul><ul><ul><li>PKI Class 3 (Medium) Certificate </li></ul></ul></ul><ul><ul><ul><li>Password </li></ul></ul></ul><ul><ul><ul><li>PKI Class 2 (Basic) Certificate </li></ul></ul></ul><ul><ul><li>Using these authentication techniques, the Department will be able to offer a comprehensive authentication service: </li></ul></ul><ul><ul><ul><li>Corroborative Authentication Mechanisms </li></ul></ul></ul><ul><ul><ul><ul><li>Used in conjunction with each other </li></ul></ul></ul></ul><ul><ul><ul><li>Additive Authentication Mechanisms </li></ul></ul></ul><ul><ul><ul><ul><li>Independent use of same type of authentication </li></ul></ul></ul></ul><ul><ul><ul><li>Strong Authentication mechanisms </li></ul></ul></ul><ul><ul><ul><ul><li>Independent use of different types of authentication </li></ul></ul></ul></ul><ul><ul><li>Provide authentication for electronic services </li></ul></ul><ul><ul><li>Interaction with Agency/Enterprise Web Based applications to provide authentication </li></ul></ul><ul><ul><li>Agency/Department Legacy Applications interface via a web based proxy </li></ul></ul><ul><ul><li>Agency applications to support GPEA </li></ul></ul><ul><ul><li>Critical capability in allowing stakeholders to conduct secure transactions with agencies. Legislative mandate states transactions must be conducted online - major cost avoidance in doing enterprise solution </li></ul></ul><ul><ul><ul><li>Synchronous Token </li></ul></ul></ul><ul><ul><ul><li>Asynchronous Token </li></ul></ul></ul><ul><ul><ul><li>Cognitive Password </li></ul></ul></ul><ul><ul><ul><li>PIN </li></ul></ul></ul><ul><ul><ul><li>PKI Class 1 (Rudimentary) </li></ul></ul></ul>Non-Web Centric Application Web Presence / User Interface Strategic Initiative (e.g. eLoans) Agency Applications DigiTop eAuth (Single sign-on, Digital Sig.) Enterprise Web Content Enterprise Document Content Shared Database Content Agency Database Content Content Aggregation/Application Integration External Content Source Web Content Management Document Management Data Management Program (Standards,Policies,Services) eLearning Presentation Business Logic Data Content Distribution Portal(s) Inter-agency Applications
    22. 22. Logical Architecture Detail: eAuthentication The following is the detailed logical architecture as it relates to eAuthentication: Authenticator Credential Manager Authentication Data Store(s) Credential Store Federal Bridge CA Audit Log/ Reporting Store Registration Report Generator USDA Internal Applications USDA Web Presence Customers & Business Partners Employees Citizens USDA Web Applications eGov Portal IDS IDS IDS IDS Document Management Web Content Management Portal CA Non-Web Centric Application Web Presence / User Interface Strategic Initiative (e.g. eLoans) Agency Applications DigiTop eAuth (Single sign-on, Digital Sig.) Enterprise Web Content Enterprise Document Content Shared Database Content Agency Database Content Content Aggregation/Application Integration External Content Source Web Content Management Document Management Data Management Program (Standards,Policies,Services) eLearning Presentation Business Logic Data Content Distribution Portal(s) Inter-agency Applications Audit Monitor IDS Monitor Management Station Data Enclave Management Enclave Registration & Reporting DMZ eAuthentication DMZ Certification DMZ USDA Certificate Store USDA WAN
    23. 23. Central Data Repositories Overview Central data repositories allow re-use of data and decrease the burden on our customers during data collection processes KEY FEATURES/CAPABILITIES/REQUIREMENTS INTEGRATION COMPONENT VALUE PROPOSITION <ul><ul><li>Will facilitate sharing of data </li></ul></ul><ul><ul><ul><li>Groups of applications that need the same data will leverage centralized repositories </li></ul></ul></ul><ul><ul><ul><li>Data stewardship processes defined within the Data Management Program result in database of records to ensure integrity and quality of shared data </li></ul></ul></ul><ul><ul><ul><li>Central repositories will allow packaging of data from different sources to enhance existing USDA services and define new data centric services </li></ul></ul></ul><ul><ul><ul><li>Data Warehouses will power Enterprise and Agency applications </li></ul></ul></ul><ul><ul><ul><li>Effort around system integration and data migration tasks during system development will be greatly reduced resulting in USDA cost savings </li></ul></ul></ul><ul><ul><li>eGovernment Strategic initiatives will leverage shared data repositories </li></ul></ul><ul><ul><li>Based on data needs Agency/Enterprise web and non –web based applications may use shared data repositories </li></ul></ul><ul><ul><li>Sharing of data outside of the department (business partners, educational institutions, government bodies etc) </li></ul></ul><ul><ul><li>Redundant and inaccurate data hinders our ability to provide optimal value to our customers. Shared data repositories will heighten availability, integrity and quality of relevant data to our clients. This will help improve quality of existing services and create opportunities to define new services </li></ul></ul>Non-Web Centric Application Web Presence / User Interface Strategic Initiative (e.g. eLoans) Agency Applications DigiTop eAuth (Single sign-on, Digital Sig.) Enterprise Web Content Enterprise Document Content Shared Database Content Agency Database Content Content Aggregation/Application Integration External Content Source Web Content Management Document Management Data Management Program (Standards,Policies,Services) eLearning Presentation Business Logic Data Content Distribution Portal(s) Inter-agency Applications
    24. 24. The following is the detailed logical architecture as it relates to central data repositories: Logical Architecture Detail: Central Data Repositories Agency/Cross-Agency Web Application Legacy Systems Strategic Initiative Shared Data Shared Data Data Warehouse External Database Repositories (Universities, other government organizations etc) Non-Web Centric Application Web Presence / User Interface Strategic Initiative (e.g. eLoans) Agency Applications DigiTop eAuth (Single sign-on, Digital Sig.) Enterprise Web Content Enterprise Document Content Shared Database Content Agency Database Content Content Aggregation/Application Integration External Content Source Web Content Management Document Management Data Management Program (Standards,Policies,Services) eLearning Presentation Business Logic Data Content Distribution Portal(s) Inter-agency Applications
    25. 25. Content Aggregation / Application Integration Overview Content aggregation spawns re-use of content and enables powerful information retrieval capabilities KEY FEATURES/CAPABILITIES/REQUIREMENTS INTEGRATION COMPONENT VALUE PROPOSITION <ul><ul><li>An enterprise content index will deliver powerful searching capabilities across a multitude of data repository types: </li></ul></ul><ul><ul><ul><li>Content Management Repositories </li></ul></ul></ul><ul><ul><ul><li>Document Management Repositories </li></ul></ul></ul><ul><ul><ul><li>Databases </li></ul></ul></ul><ul><ul><ul><li>Web Servers </li></ul></ul></ul><ul><ul><ul><li>File Servers </li></ul></ul></ul><ul><ul><ul><li>Content originated outside of USDA and migrated to USDA Databases/File Servers </li></ul></ul></ul><ul><ul><li>An enterprise application integration framework will allow the integration of disparate applications in a cost effective manner </li></ul></ul><ul><ul><ul><li>Out of the box connectors will minimize custom development </li></ul></ul></ul><ul><ul><ul><li>Promote industry standard integration mechanisms such as XML </li></ul></ul></ul><ul><ul><li>Portal search capability will leverage enterprise content index and application integration to aggregate content and services </li></ul></ul><ul><ul><li>eGovernment Strategic and Enabler initiatives </li></ul></ul><ul><ul><li>Agency/Department web and non-web Based applications </li></ul></ul><ul><ul><li>This is a key component in allowing the integration of eGovernment capabilities into our current infrastructure. Enables ubiquitous access of data and content in a heterogeneous, distributed environment </li></ul></ul>Non-Web Centric Application Web Presence / User Interface Strategic Initiative (e.g. eLoans) Agency Applications DigiTop eAuth (Single sign-on, Digital Sig.) Enterprise Web Content Enterprise Document Content Shared Database Content Agency Database Content Content Aggregation/Application Integration External Content Source Web Content Management Document Management Data Management Program (Standards,Policies,Services) eLearning Presentation Business Logic Data Content Distribution Portal(s) Inter-agency Applications
    26. 26. The following is the detailed logical architecture as it relates to content aggregation and application integration: Logical Architecture Detail: Content Aggregation / Application Integration Document Management Web Content Management Agency/ Cross Agency databases Agency/Cross Agency File Server Web Servers, Existing CM and WCM Repositories Content/Data Index Agency/Cross-Agency Web Application Portal Content Aggregation Server Content/data Index Search Results Search Results Enterprise Index Database External Database Repositories Non-Web Centric Application Web Presence / User Interface Strategic Initiative (e.g. eLoans) Agency Applications DigiTop eAuth (Single sign-on, Digital Sig.) Enterprise Web Content Enterprise Document Content Shared Database Content Agency Database Content Content Aggregation/Application Integration External Content Source Web Content Management Document Management Data Management Program (Standards,Policies,Services) eLearning Presentation Business Logic Data Content Distribution Portal(s) Inter-agency Applications
    27. 27. Content Distribution Overview Content distribution ensures timely delivery of content and services by physically locating content in specific geographic areas KEY FEATURES/CAPABILITIES/REQUIREMENTS INTEGRATION COMPONENT VALUE PROPOSITION <ul><ul><li>Content distribution scheme will determine the optimal location to place content based on: </li></ul></ul><ul><ul><ul><li>User physical location </li></ul></ul></ul><ul><ul><ul><li>Network infrastructure </li></ul></ul></ul><ul><ul><ul><li>Available bandwidth </li></ul></ul></ul><ul><ul><ul><li>System administrator settings </li></ul></ul></ul><ul><ul><li>Ensure consistency of content across distributed servers </li></ul></ul><ul><ul><li>Portal content will be distributed via content distribution scheme </li></ul></ul><ul><ul><li>Web Content Management solution will integrate with Content Distribution during content deployment </li></ul></ul><ul><ul><li>Agency/Department Web Based applications </li></ul></ul><ul><ul><li>Application performance is a key criteria for the success of a solution. A content distribution scheme will allow us to ensure minimal response time for enabler, strategic and agency applications </li></ul></ul>Non-Web Centric Application Web Presence / User Interface Strategic Initiative (e.g. eLoans) Agency Applications DigiTop eAuth (Single sign-on, Digital Sig.) Enterprise Web Content Enterprise Document Content Shared Database Content Agency Database Content Content Aggregation/Application Integration External Content Source Web Content Management Document Management Data Management Program (Standards,Policies,Services) eLearning Presentation Business Logic Data Content Distribution Portal(s) Inter-agency Applications
    28. 28. The following is the detailed logical architecture as it relates to content distribution: Logical Architecture Detail: Content Distribution Content Distribution Server Monitoring/Configuration Station Database Portal Location 1 Portal Location 2 Agency/Cross-Agency Web Application Location 1 Agency/Cross-Agency Web Application Location 2 Web Content Web Content Web Content Web Content Web Content Management Deploy Non-Web Centric Application Web Presence / User Interface Strategic Initiative (e.g. eLoans) Agency Applications DigiTop eAuth (Single sign-on, Digital Sig.) Enterprise Web Content Enterprise Document Content Shared Database Content Agency Database Content Content Aggregation/Application Integration External Content Source Web Content Management Document Management Data Management Program (Standards,Policies,Services) eLearning Presentation Business Logic Data Content Distribution Portal(s) Inter-agency Applications
    29. 29. Existing Physical Architecture <ul><li>We will leverage existing assets within USDA to rollout the proposed architecture </li></ul><ul><ul><li>We understand the existing infrastructure at the NITC hosting center </li></ul></ul><ul><ul><ul><li>As part of the architecture development effort, an assessment of the current capabilities was conducted </li></ul></ul></ul><ul><ul><ul><li>Storage, physical security, redundant power supply, onsite and offsite backup, Storage Area Network, and application monitoring amongst other services offered by the hosting center will be critical to the successful of our architecture </li></ul></ul></ul><ul><ul><li>Service Centers and agency field offices will play a critical role in the deployment of a distributed architecture </li></ul></ul><ul><ul><ul><li>The Service Center Common Computing Environment(CCE) effort will provide a technology and operational infrastructure for our proposed architecture </li></ul></ul></ul><ul><ul><ul><li>Service Center Interoperability Lab provides an environment for evaluating technologies which may be part of the architecture </li></ul></ul></ul><ul><ul><li>Agency business specific applications that will leverage the proposed, common architecture will reside in the preferred location and under the control of the agency </li></ul></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                             
    30. 30. Relationship to Other Enterprise Efforts <ul><li>The technical architecture has been designed to function within the context of other enterprise efforts: </li></ul><ul><ul><li>Enterprise architecture </li></ul></ul><ul><ul><ul><li>Contributes to the technology, data and application layers of enterprise architecture in supporting the information and business layers </li></ul></ul></ul><ul><ul><ul><li>Lays the groundwork for enabling enterprise applications supporting common Department-wide business processes </li></ul></ul></ul><ul><ul><li>Universal telecommunications network </li></ul></ul><ul><ul><ul><li>Proposed use of data centers in the architecture support UTN vision of having centralized data centers as “high-bandwidth” centers </li></ul></ul></ul><ul><ul><li>Common Computing Environment / Service Center Modernization Efforts </li></ul></ul><ul><ul><ul><li>Potential for distributed architecture will utilize service center data centers </li></ul></ul></ul><ul><ul><ul><li>Potential to leverage existing hardware already available in web farms </li></ul></ul></ul>
    31. 31. Technical Architecture Next Steps <ul><li>Upon completion of the technical architecture, the following next steps are necessary to continue towards the goal of developing enterprise services: </li></ul><ul><ul><li>Confirm feasibility of conceptual and logical architecture with agencies </li></ul></ul><ul><ul><li>Create Requests for Proposal (RFP’s) based on technical architecture and implementation approach </li></ul></ul><ul><ul><li>Conduct formal product selection process </li></ul></ul><ul><ul><li>Develop physical architecture based on products selected </li></ul></ul><ul><ul><li>Determine custom development efforts to achieve stated goals for initial rollout of architecture </li></ul></ul><ul><ul><li>Finalize level of effort estimates based on delivery of physical architecture </li></ul></ul>Technology
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×