2020 Census Program Management Review 2020 Decennial Architecture Activities Terry Galloway, Enterprise Solution Architect (2020)

Transcription

1 2020 Census Program anagement eview 2020 Decennial Architecture Activities Terry Galloway, nterprise Solution Architect (2020) June 21,

2 Building 2020 From IT nterprise Perspective 2

3 2020 Decennial Architecture Notional Diagram Due to the 2020 Decennial architecture effort consisting of multiple solutions depicted in a single architecture the team felt the importance of a multi-view snapshot of a notional target state architecture for the 2020 Census: The initial concentration covered the esponse Data Collection component of the Survey Lifecycle (SLC) because this area was the major IT cost driver for 2010 The diagrams begins to show the complexity of the high-level system dependencies and the four degrees of current system/solution capability readiness for 2020: existing, modification, re-engineering, and new. Initial purpose was to start the 2020 IT system evaluation process, highlight issues, and foster IT conversations around items such as complexity, level of effort, scalability, and in-house versus outsourced systems. nd Goal: To be a driver for completing the 2020 Decennial Architecture and IT oadmap xecution Plan. The plan will layout the overall tasks, schedule, resources, and risks associated with delivering the 2020 Decennial Architecture and IT oadmap 3

4 High-Level Architecture Activities Planned Task 2020 Notional Target- State Architecture View 20PO Field Test Architecture equest 2020 Census equirements Analysis System-to- equirements valuation Technical Analysis/ Alternative Analysis Technology Forecast 2020 Decennial Architecture (Living Document) 2020 Decennial IT oadmap Description Create a complete view of all IT systems/solutions that are expected to be deployed in order to conduct the 2020 Census Determine certain activities and/or testing needs that should be conducted during field test to help support architecture and design decisions valuate the requirements presented from 20PO team to determine if efficient to start the system evaluation process Initiate system deep-dive analysis to evaluate current systems and/or solutions against the 2020 functional requirements, including cost/benefit trade-offs Certain solutions will require in-depth technical and alternative analysis to determine a recommendation for a specific set of capabilities Need to understand external IT drivers that have potential impact on 2020 design (i.e. FedAP, mobile code standardization, new IT products, electronic ID, etc.) Will provide segment level architecture guidance to the different solution/system implementation owners and/or contractors by laying out 2020 IT blueprint in the following areas: strategy/business architecture, application architecture, data/information architecture, infrastructure architecture, and security architecture The overall transition and implementation strategy for each solution/system that will be deployed for 2020 Census including: key milestones, deadlines, decision points, risks, contingency plans, and testing activities (functional and performance) 4

5 Architecture Dependent Activities (20PO) Name Architecture Documentation Dependency 2020 Census ConOps and The overall strategy/thinking on the Census Bureau s approach to conducting the Function aps 2020 and high-level business capabilities - key to the business architecture module esearch & Field Test The system related results may need to be integrated into the architecture design esults 2020 Project Breakdown The operational setup of the 2020 Census will drive IT decisions (i.e. system deployment, network infrastructure, HW/SW infrastructure, etc.) 2020 equirements The development of the requirements taking them from mission, to business, to project/system level is the foundation for the architecture designs and all systems/solutions should map back to a specific requirement and/or set 2020 Helpdesk Strategy Provides the functional and nonfunctional Helpdesk system requirements Approval Process (IT Based on the System Technical Analysis/Alternative Analysis the team will make Investment) system recommendations which require executive level approval 2020 Workload etrics Drives how to properly size systems and determine scaling needs which impacts system design and architecture 2010 Lessons Learned and Identify and understand previous issues and areas of high risk to minimize repeating ecommendations them Ongoing eassessments Policy, workforce, budget, and operations decisions may impact the overall design 5

6 Architecture Dependent Activities (nterprise) Name SOA Strategy IT Infrastructure oadmap ASDI B1 Deployment obile Architecture Strategies Cloud Computing Strategy Headquarters Dissemination Initiatives Security Policy & Procedures nterprise Architecture Software Development Lifecycle (SDLC) IT Shared Services Program Architecture Documentation Dependency Provides guidance and design patterns relating to deployment of service oriented architecture and how the enterprise service bus will be deployed and architected Provides enterprise vision and guidance relating to the physical IT infrastructure Successful deployment sets the stage for the Baseline 2 (2020 Census centric) and any changes and/or slippage may impact the 2020 Census design Provides the guidance, framework, and application patterns for all mobile deployments Provides the guidance/criteria for the implementation of cloud computing Will drive the dissemination design for 2020 and may recommend changes to Data Access & Dissemination System or upstream systems that feed into dissemination Security policy and procedures will drive all design recommendations (i.e. U.S. citizen identity management, external HW provisioning, etc.) Informs and guides IT design and architecture decisions by providing standards, design patterns, governance, architecture reviews, IT portfolio information, etc. Provides consistent life-cycle development methodology processes which also includes a consistent requirements development and management process Candidate services are being identified and evaluated at enterprise level to make deployment recommendations 6

7 2020 Notional Target Architecture Diagram IF26 IF1.5 IF5 SYS5: CAA Non-ID Case w/ nhanced Address Address Admin ecord Frame/Instrument/Sample Design Systems IF20 IF22.20 SYS26 QUI/GIDS Questionnaire Content/etada Design/Publish Instrument IF22.17 IF17 IF15.17 ission nabled Support SYS17: NPC Services mergency Printing DAPPS W2 ail Services SYS20: ACSD Service Center HQ Printing Postal Tracking nterprise Support Services IF30 IF22.30 SYS6: GO Services xtract Data esolve Non-ID Case Address GeoCoding Address Frame IF5.6 IF22.6 IF1.6 IF 10.6 IF6 IF2 IF6.1 IF5.1 SYS2 Concurrent Analysis & stimation Coding & diting Imputation, stimation & Quality Computation IF2.1 SYS1: ulti ode Operation Control System (UC and DIS) Workflow Business ules Case anagement Input/Output Processing esponse Data Integration Operational eporting SYS3 UTS (C&P) Paradata epository BI/Dashboard Cost & Progress eporting SYS27 nterprise Service Bus/SYS28 TL (xtract, Transform, Load) System/ SYS29 Product Service essage Queuing SYS30: Census nterprise LDAP User Authentication User Authorization SYS96 /CHC Background Validation SYS95 /HQ Costing Activity Base Costing IF96 N IF26.15 IF11.1 IF15.1 IF12.1 IF19.1 Paper Capture Services IF3 IF22.3 IF15 IF22 ecapture Services SYS22 Payroll Temp mployee (DAPPS) Time & Cost Activity anage Staff & Payroll Data Create Temp JB ID IF 10 SYS10 CADS esponse Processing Data Products, eporting Operational eporting Check-in eceived Paradata ail (Tracking Integration Quality Analysis IF19 esponse Data IF3.1 User Interface Non- ID Cases Integration DAFT CY15 ASDI Systems Decennial Systems IF10.1 IF95 IF99 IF IF18 SYS15: Paper Data SYS11 Operation Control System (Field Usage) SYS18: Help Desk Collection SYS99 /CBS Support Portal anage NFU Capture Paper Commerce T&A Self Service IF98 Help esponse IF11 Workload numeration Desk SYS98 /WebTA Census HQ/ egional T&A SYS97 /JAS Census NPC T&A SYS27 /CNDocs Print aterial IF97 N Display FAQ Status Updates User Help Desk espondent Help Desk Online Chat IF1.15 IF18.1 IF1.3 IF15.USPS IF6.22 IF1.19 IF6.11 IF22.11 IF1.11 IF14 SYS19 Census/Pii ACS eceive Interview esults einterview Selection Security and Privacy Services IT Support Services/Systems (Technical Help Desk, Asset anagement, Operational anagement and onitoring) Network & Communication Support IF1 IF97.3 IF95.3 IF99.3 IF98.3 Serve as Conduit for NPC Services Check-In eceived ail Interface w/usps ail Tracking anage Image Capture Process IF96.22 IF99.22 anage CATI/CAPI/ numeration/ Listing anage F Devices SYS14 lectronic Correspondence eail/text Self egistration N IF1.10 Listing anage Contact Paradata Integration Input/Output Processing SYS12 Internet Data Capture Web Self esponse CATI N IF26.11 IF12 IF26.12 IF1.12 IF14.PUP IF18.PUP IF12..PUP IF1.IUP IF17.IUP IF18.IUP IF12.IUP IF15.IUP IF11.IUP Public User Portal Internal User Portal USPS Internet espondants Census Systems Assistance Centers/Kiosk numeration Listing obile LCO Field Offices Service Providers Cloud Service TQA Offices USPS Tracking Print/ailing Service Version 2.1 7

8 Understanding the Notional Architecture Diagram Name Symbol eaning xisting System requires no Decennial specific changes New odified e-engineered Targeted Production Date Data Provider (System) Data Consumer (System) xternal Interface Arrow Colors Arrow Numbering (i.e. ICD# or ICD#.#) Blocks of Color Gray Box System Number/ Name White Box N CYxx System that currently does not exist inor architectural changes (i.e. interface changes, service enable, etc.) ajor design changes as direct result of meeting Decennial requirements The targeted calendar year the system is to be ready for production The system that will be providing data to be consumed The system that will be consuming data from the provider Depicts interface with external component/system Identifies which system group ( blocks of color ) the data provider resides The first number identifies the system number of the data provider and second number identifies the system number of the data consumer Groups systems into common areas specific to Decennial processing Used to symbolize a specific system or set of subsystems Used to reference and identify a specific systems within the diagram Identify core system functionality in respect to Decennial processing 8

9 Initial IT Architecture Insight 2010 workload peak of 8.15 million questionnaires processed per day is approximately 2.5x greater than the next highest survey/census yearly workload (ACS 3.5 million per year), highly impacting the processing in the data collection segment system area The systems (in-house or outsourced) should be designed to properly allow for scaling elasticity the ability to physically expand and compress based on workload, this will allow for more efficiencies in system processing and cost The business strategy related to operational deployment (i.e. BYOD, real-time processing, targeted address canvassing, use of admin records, field operation consolidation, help-desk strategy, etc.) will drive IT designs and increase operational dependency on IT systems New Feature ffect - Internet response processing and adaptive design will create a different workload processing characteristic relative to 2010 and need to be taken into consideration In-house system development may still require Census Bureau to leverage external service providers to assist in building and hosting our systems A service based architecture (i.e. cloud services, SOA implémentation, etc.) is recommended to allow for the various types of disparate systems to integrate and/or interoperate with one another A ideal system deployment model would maximize the number of systems that are in full operation prior to actual 2020 deployment, duplicating a Pilot scenario via other survey/census usage 9

10 Questions 10