Enterprise Architecture in the Intelligence Community:

Enterprise Architecture in the Intelligence Community: The Joint Architecture Working Group (JAWG) Randy Marks; Chair, Joint Architecture Working Group NSA/TE Deputy Chief System Engineer for Enterprise Architecture

KBs KBs Obtain Data Manage the Production Process Assess Options Obtain Data Manage the Production Process Assess Options Event Store IIB EP Process Data Manage Requirements Process Data Manage Requirements Analyze & Produce Intelligence Manage Customer Relations Analyze & Produce Intelligence Manage Customer Relations Event Store IIB EP Data Info KBs Collect Process Exploit Disseminate Task Intel KBs Tasking Planning & Tasking Obtain Data Manage the Production Process Assess Options Collection Processing Analysis Event Store IIB EP Requirements Process Data Manage Requirements Production & Dissemination Signal Data Info KBs Intel Acquire Data Analyze & Produce Intelligence Manage Customer Relations Targeting Process Data & Perform Cryptanalysis Tasking Coordinate Cryptologic Operations Perform Cryptologic Analysis INDB KBs Tailor & Deliver Results SIGDEV SIGDEV SIGDEV Data Info KBs Intel Tasking Planning & Tasking Collection Processing Analysis Requirements Production & Dissemination Obtain Data Manage the Production Process Assess Options Data Info KBs Intel Event Store IIB EP Process Data Manage Requirements Detect/ Find Strike/ Engage Analyze & Produce Intelligence Manage Customer Relations Data Info KBs Collect Process Exploit Disseminate Locate/ Fix Task Data Info KBs Assess Tasking Planning & Tasking Collection Processing Analysis Requirements Identify/ Track Decide/ Target Production & Dissemination Data Info KBs Intel Intel Detect/ Find Strike/ Engage Data Info KBs Locate/ Fix Assess Identify/ Track Decide/ Target Detect/ Find Strike/ Engage Detect/ Find Strike/ Engage Data Info KBs Locate/ Fix Assess Locate/ Fix Identify/ Track Decide/ Target Data Info KBs Assess Identify/ Track Decide/ Target Info Sharing/Integration is a grassroots effort not an enterprise principle Phone call, email, word of mouth Warfighters are unaware of solutions Current implementation hampers Information Integration Point-to-point interfaces Inability to find information Service provider Private libraries Standards need to be enterprise focused National Tactical DCGS GSTs DCGS Intelligence JOINT ARCHITECTURE WORKING GROUP 4

Enterprise Architecture to the rescue! 5

UNCLASSIFIED//FOR OFFICIAL USE ONLY

The Architecture Trifecta The AS IS Architecture The To Be Architecture The Architecture Transition Plan - Roadmap JOINT ARCHITECTURE WORKING GROUP

Multiple ways to produce an architecture JOINT ARCHITECTURE WORKING GROUP 8

DOD Architecture Framework

Enterprise Architecture (circa 2006) * Acknowledgement to Dr. Scott Bernard, Introduction to Enterprise Architecture

The Joint Architecture Reference Model: 10 Layer Model Operational Drivers Abstract Models and Architectures used to build the lower layers People using IT that is provided below Operations-specific Services Software performing specific activities Undercarriage Services Enterprise -wide software and hardware services utilizing shared networks and facilities For unique mission capabilities, these layers may be dedicated to specific operations 10. Operational Objectives & Policies 9. Capability Areas (and Threads) 8. Enterprise Activities and Exchanges 7. Applications and Content 6. Software Frameworks and Content Structure 5. Enabling Services for Applications and Content 4. Computing and Storage Platforms (HW & OS) 3. Networks (OSI Layers 2 & 3) Security Data 2. Physical Connectivity Infrastructure (OSI Layer 1) 1. Facilities Infrastructure (Power, Space, & HVAC) JOINT ARCHITECTURE WORKING GROUP 11

Model Comparisons Other Enablers

Example of the way we did EA Enter the Joint Architecture Working Group JAWG 13

The JAWG s Objective to define the IC Federated Enterprise Architecture and provide tools to support IC Element and IC Enterprise investment (acquisition) decisions across the IC JOINT ARCHITECTURE WORKING GROUP 14

JAWG Timeline NRO NSA NGA ODNI DIA OUSD(I) CIA FBI DHS USN (N2) DoD CIO JCS Sep 08 Sep 08 Sep 08 Oct 08 Oct 08 Nov 08 Dec 08 Jan 09 Feb 09 Jul 09 Aug 09 Apr 10 Membership 2008 2009 2010 2011 Significant Events May 08: NRO Ground transformation Aug 08: JSEF forms Dec 08: 1 st Community Review (IGCR) Sep 08: IC Architecture-focused forum established (JAWG) May 09: 2 nd Community Review (JAR); JAWG subsumed into IC CIO under ICI2P Oct 09: Community Status Review (JASR); JSEF became the Architecture Standards & Engineering Committee (ASEC) Mar 10: 3 rd Community Review (AER) Jul 10: IC Core TEM 1 Sep 10: IC Core TEM 2 Nov 10: Community Status Review (JICSR) Apr 11: DoD EA Conference JOINT ARCHITECTURE WORKING GROUP May 11: 4 th Community Review 15

JOINT ARCHITECTURE WORKING GROUP 16

The Joint Architecture Reference Model The Tools To be effective, we need to use the JARM in a standard way toward a shared goal JOINT ARCHITECTURE WORKING GROUP 17

The Joint Architecture Reference Model: 10 Layer Model Supports Top Down Specific Areas of Interest Bottoms Up JOINT ARCHITECTURE WORKING GROUP 18

The Joint Architecture Reference Model: 10 Layer Model JOINT ARCHITECTURE WORKING GROUP 19

The Joint Architecture Reference Model: 10 Layer Model JOINT ARCHITECTURE WORKING GROUP 20

Enterprise Competency Model (ECM) The ECM is a standard characterization of mission and business functions and activities It s a way to represent what our agencies do It s related to the FEA Business Reference Model Functions identified within the ECM represent Layer 8 Enterprise Activities and Exchanges The ECM introduces three concepts Enterprise Competencies Enterprise Components Accountability Levels The ECM provides a more in-depth representation of IC mission and business functions than the current IC BRM JOINT ARCHITECTURE WORKING GROUP 21

A Closer Look at the ECM JOINT ARCHITECTURE WORKING GROUP 22

Enterprise Services List (ESL) The ESL provides a mission/business-driven, functional framework classifying enterprise services ESL terminology is consistent with the FEA Service Reference Model Service Domains Service Types Service Components UNCLASSIFIED The ESL provides a more comprehensive list of enabling services for the IC JOINT ARCHITECTURE WORKING GROUP 23

The Joint Architecture Reference Model: 10 Layer Model JOINT ARCHITECTURE WORKING GROUP 24

So why do we care? 25

Start With A Common Language JOINT ARCHITECTURE WORKING GROUP 26

That s the Enterprise let s narrow our focus a bit more 27

A Federated Environment Enabling Information Integration Any data, any time, any place, usable by any authorized consumer; preventable only by law or policy, not technology. JOINT ARCHITECTURE WORKING GROUP 28

The IC Core Defined The IC Core is a focused set of joint & community services, specifications and standards, processes, and policies for enabling the Business of Intelligence for the federated Intelligence Community Enterprise IC Core elements must: be foundational enable the Business of Intelligence, and foster interoperability and integration The focus of the IC Core is on the technical service capabilities and discrete services JOINT ARCHITECTURE WORKING GROUP 29

IC Core Baseline Increment 1 Service Offerings Identity & Access (IdAM) Collaboration Content Discovery & Retrieval (CDR) Infrastructure Enablers General Enterprise Enablers Access Control Email Information Retrieval Network Document Categorization Digital Policy Organizational Messaging Subscriptions Communications Indexing Intrusion Prevention Cryptography Voice Communication Audio Conferencing Alerts & Notifications Data Exchange Enterprise Infrastructure Assessment Virus Protection Document Classification Security Classification Legend Service Offering IC Core Enterprise Service Component Enterprise Service Component Digital Resource Identification Audit Trail Capture & Analysis Forensics Identification and Authentication Digital Signature Computers / Automation Workgroup / Groupware Video Conferencing Computer / Telephony Integration Real-Time Chat Threaded Discussion Shared Calendaring Instant Messaging Personalization Community Document Library Task Text Messaging Multimedia Metadata Knowledge Distribution and Delivery Knowledge Categorization Precision / Recall Ranking Intrusion Detection Incident Response Cross Domain Data Transfer Requires synchronization with ESL Service Monitoring Service Discovery Service Publication Content Acquisition Directory Services Workforce / Directory Locator Information Mapping / Taxonomy Mission Assessment Personnel Administration JOINT ARCHITECTURE WORKING GROUP 30

So we ve got another framework, another taxonomy What do we do with it? 31

Need to make acquisition decisions based on functions (capabilities) rather than individual programs So how do we use the JAWG products to better inform acquisition decisions? JOINT ARCHITECTURE WORKING GROUP 32

Enterprise Architecture to Investment Portfolio Alignment 10 Layer Architecture Model Information Portfolio (IP) Structure Agency Strategy Agency Concise Look Forward Investment Portfolio Strategy Agency Program Guidance Team Effort with SME support Agency Transformation Operations Enterprise Mgt Processing Exploitation Analytics Production Enterprise IT Enterprise Mgt Mission JOINT ARCHITECTURE WORKING GROUP 33

Overlaps, Possible Duplication, or areas of Common Concern Then look for hotspots or concentrations of activity Budget Center Bxxx Effort 1 Material Labor Mgmt, Sys Engr, HW Main, SW Dev Travel, Transportation & Supplies Infrastructure Facilities Effort 2 Material Labor Mgmt, Sys Engr, HW Main, SW Dev Travel, Transportation & Supplies Infrastructure Facilities Budget Center Byyy Effort 1 Material Labor Mgmt, Sys Engr, HW Main, SW Dev Travel, Transportation & Supplies Infrastructure Facilities Effort 2 Material Labor Mgmt, Sys Engr, HW Main, SW Dev Travel, Transportation & Supplies Infrastructure Facilities Operational objectives and policy layer Capability Areas and Thread Layer Enterprise Activites and Exchange Layer Accomplish the Mission A1 Coordinate Operations (1.2) A1.1 Manage Mission Resources & Capabilities A1.1.1 Provide Mission Planning A1.1.2 Manage Health, status and perfo A1.1.3Maintain Tradecraft A1.1.4 Provide target planning A1.1.4.1 Identify requirements A1.1.4.2 Command & Control A1.1.4.3 Manage Discovery A1.1.4.4 Provide IA Tasking A1.1.4.5 Endpoint Resources A1.1.5 Mange IA portfolio A1.1.6 Manage gig protfolio A1.2 Maintain implementation plans A1.3 Manage external relationships A1.3.1 Manage IA community education A1.3.2 Manage international relations A2 Direct Operations A2.1 Acquire Data A2.1.1 Provide Mission Planning A2.1.2 Manage Health, status and perfo A2.1.3Maintain Tradecraft A2.2 Process intercept A2.2.4.1 Select & promote objects A2.2.4.2 reconstruct packet streams A2.2.4.3 Create objects A2.2.4.4 Analyze objects A2.3 Process Data A2.3.1 Provide Mission Planning A2.3.2 Manage Health, status and perfo A2.3.3Maintain Tradecraft A2.3.3.1 Identify personnel information A2.3.3.2 transform processed data A2.3.3.3Recognize activity of interest A3 Enable Analysis A3.1 Manage Mission Resources & Capabilities A3.1.1 Provide Mission Planning A3.1.2 Develop Analytic Techniques A3.1.3Maintain Tradecraft A3.1.4 Provide target planning A3.1.4.1 Identify requirements A3.1.4.2 Conduct Discovery A3.1.4.3 Manage Discovery A3.1.4.4 Display Results A3.1.4.5 (U)Perform Analysis A3.1.5 Mange IA portfolio A3.1.6 Understand Netorks A3.2 Maintain implementation plans A3.3 Apply Information Policy A3.3.1 Manage IA community education A3.3.2 Content Analysis Capability GAP! Mission Critical Capability but no evidence of financial support JOINT ARCHITECTURE WORKING GROUP 34

Within an Agency Programs A, B & C C A B What do I have on the floor? What do I have in Development? What areas am I doing research in?

So why not do it on a grander scale? UNCLASSIFIED 36

IC CIO Requirement for FY12 Program Build Exhibit 53 & 300 Mapping to the JARM Exhibit 300 Data Required: Mapping to the ECM Required: Mapping to the ESL Exhibit 53 Data Optional: Mapping to the ECM Optional: Mapping to the ESL Required pre-2010 Reporting data for the FYDP, not just a single FY Percentage of the Budget allocated to the BRM Percentage of the Budget allocated to the SRM JOINT ARCHITECTURE WORKING GROUP 37

JARM Enterprise Competency Model (ECM) JARM Enterprise Services List (ESL) Service Types Customer Relationship Customer Preferences Customer Initiated Assistance Tracking & Workflow Routing & Scheduling of Process Organizational Investment Supply Chain Content Document Knowledge Records Analysis & Statistics Mission Performance Inelligence Analysis Visualization Knowledge Discovery Business Inelligence Reporting Data Human Resources Financial Service Domain Customer Services Process Automation Services Business Services Digital Asset Services Business Analytics Services Back Office Services Support Services 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 1 8.1.1 8.2.1 8.3.1 8.4.1 8.5.1 8.6.1 8.7.1 8.8.1 8.9.1 8.10.1 8.11.1 8.12.1 8.13.1 8.14.1 8.15.1 8.16.1 8.17.1 8.18.1 8.19.1 8.20.1 8.21.1 8.22.1 8.23.1 8.24.1 8.25.1 8.26.1 8.27.1 8.28.1 8.29.1 8.30.1 8.31.1 8.32.1 8.33.1 2 8.1.2 8.2.2 8.3.2 8.4.2 8.5.2 8.6.2 8.7.2 8.8.2 8.9.2 8.10.2 8.11.2 8.12.2 8.13.2 8.14.2 8.15.2 8.16.2 8.17.2 8.18.2 8.19.2 8.20.2 8.21.2 8.22.2 8.23.2 8.24.2 8.25.2 8.26.2 8.27.2 8.28.2 8.29.2 8.30.2 8.31.2 8.32.2 8.33.2 3 8.1.3 8.2.3 8.3.3 8.4.3 8.6.3 8.8.3 8.9.3 8.10.3 8.11.3 8.12.3 8.13.3 8.14.3 8.15.3 8.16.3 8.17.3 8.18.3 8.19.3 8.20.3 8.21.3 8.22.3 8.23.3 8.24.3 8.25.3 8.26.3 8.27.3 8.28.3 8.29.3 8.30.3 8.31.3 8.33.3 4 8.1.4 8.3.4 8.6.4 8.9.4 8.10.4 8.11.4 8.12.4 8.13.4 8.14.4 8.15.4 8.16.4 8.17.4 8.21.4 8.22.4 8.23.4 8.24.4 8.25.4 8.26.4 8.27.4 8.28.4 8.29.4 8.30.4 8.31.4 8.33.4 5 8.1.5 8.3.5 8.6.5 8.9.5 8.10.5 8.11.5 8.12.5 8.14.5 8.15.5 8.16.5 8.17.5 8.21.5 8.22.5 8.23.5 8.24.5 8.25.5 8.26.5 8.27.5 8.28.5 8.29.5 8.30.5 8.31.5 8.33.5 6 8.1.6 8.3.6 8.6.6 8.9.6 8.11.6 8.12.6 8.15.6 8.16.6 8.17.6 8.21.6 8.22.6 8.23.6 8.26.6 8.27.6 8.28.6 8.30.6 8.31.6 7 8.1.7 8.3.7 8.6.7 8.9.7 8.11.7 8.12.7 8.15.7 8.16.7 8.17.7 8.21.7 8.22.7 8.23.7 8.26.7 8.27.7 8.28.7 8.30.7 8.31.7 8 8.1.8 8.6.8 8.9.8 8.11.8 8.12.8 8.15.8 8.16.8 8.21.8 8.22.8 8.23.8 8.26.8 8.27.8 8.30.8 9 8.1.9 8.6.9 8.9.9 8.11.9 8.15.9 8.16.9 8.21.9 8.22.9 8.23.9 8.26.9 8.27.9 10 8.1.10 8.9.10 8.15.10 8.21.10 8.22.10 8.23.10 8.27.10 11 8.1.11 8.9.11 8.15.11 8.21.11 8.22.11 8.23.11 8.27.11 12 8.1.12 8.9.12 8.15.12 8.21.12 8.27.12 13 8.1.13 8.9.13 8.15.13 8.21.13 8.27.13 14 8.1.14 8.15.14 8.21.14 8.27.14 15 8.15.15 8.21.15 8.27.15 16 8.15.16 8.21.16 8.27.16 17 8.15.17 8.21.17 8.27.17 18 8.15.18 8.21.18 19 8.15.19 8.21.19 20 8.15.20 8.21.20 21 8.15.21 22 8.15.22 23 8.15.23 Service Components Assets / Materials Development & Integration Human Capital / Workforce Security Collaboration Search Communication Systems Forms Service JOINT ARCHITECTURE WORKING GROUP 38

All (22) Ex 300 Programs Mapped to ESL for FY12 (U) Do the circled boxes indicate potential critical business service gaps? We do not know. Data set is incomplete. Service Types Customer Relationship Customer Preferences Customer Initiated Assistance Tracking & Workflow Routing & Scheduling of Process Organizational Investment Supply Chain Content Document Knowledge Records Analysis & Statistics Mission Performance Inelligence Analysis Service Domain Customer Services Process Automation Services Business Services Digital Asset Services Business Analytics Services Back Office Services Visualization Support Services 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 1 4 6 6 10 3 12 4 8 11 4 4 9 4 1 1 0 4 4 3 9 10 1 6 8 10 2 13 7 9 4 10 2 8 2 2 4 6 4 3 12 8 3 5 4 3 6 8 1 0 2 1 3 2 8 7 1 5 6 9 1 13 5 1 4 6 2 4 3 2 6 6 1 13 4 7 2 4 7 3 0 2 1 1 5 4 5 9 2 5 7 9 4 7 6 3 4 10 4 4 7 2 15 5 3 7 6 0 0 3 2 2 5 2 2 5 9 1 8 6 2 3 7 5 5 2 0 9 8 0 4 4 2 2 1 2 4 3 4 8 9 0 7 3 4 5 9 9 6 8 2 13 10 3 7 2 0 0 4 1 4 1 8 4 5 12 7 4 8 8 3 4 5 2 0 3 7 1 2 0 6 4 1 11 8 8 14 4 5 2 0 3 10 1 4 0 9 4 9 5 10 1 6 1 2 6 3 4 0 10 10 7 2 0 4 1 2 5 11 4 3 1 9 2 1 6 12 5 2 1 11 9 13 7 1 0 12 2 14 6 0 3 5 15 2 10 5 16 2 1 2 17 (U) ESL Component 8.3.5 Multi-Lingual Support 1 2 1 18 1 2 19 defines the set of capabilities that allow access to 1 3 20 data and information in multiple languages. 0 1 21 1 22 2 23 3 Service Components Knowledge Discovery Business Inelligence Reporting Data Human Resources Financial Assets / Materials Development & Integration Human Capital / Workforce Security Collaboration Search Communication Systems Forms Service JOINT ARCHITECTURE WORKING GROUP 39

Most Common JARM ESL Mappings in Ex 300s for FY12 At least five (out of six) of the reporting agencies mapped to each of the following service components for FY12 within the JARM ESL: Product Customer/Account Alerts and Notifications Process Tracking Requirements Program/Project Governance/Policy Quality Business Rule Risk Procurement Invoice Requisition Track/Approve Library Storage Document Creation/Validation Information Retrieval Information Mapping/Taxonomy Information Sharing Knowledge Capture Document Classification Ad-Hoc Standardized/Canned Data Exchange Data Warehouse Data Recovery Data Access Cross Domain Data Transfer Software Development Identification and Authentication Access Control Query Systems Engineering Mapping of all Ex 300 reporting programs across the community highlights areas where the IC might collaborate today in our respective development efforts The heat map shows all service component mappings across all six agencies [for illustration only] (Source: Exhibit 300s) JOINT ARCHITECTURE WORKING GROUP 40

ESL Mapping Snapshot: IC Core Overlay (U) The circled boxes indicate Enterprise Service components in which 1 or fewer of the 6 reporting agencies are investing. (Exhibit 300s, FY12) Service Domain. Customer Services Process Automation Services Business Services Digital Asset Services Business Analytics Services Back Office Services Support Services Service Types Customer Relationship Customer Preferences Customer Initiated Assistance Tracking & Workflow Routing & Scheduling of Process Organizational Investment Supply Chain Content Document Knowledge Records Analysis & Statistics Mission Performance Inelligence Analysis Visualization 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 1 1000 4 1000 1000 1000 1000 4 1000 1000 1000 1000 6 1000 1000 1000 1000 1000 1000 1000 1000 5 1000 1000 1000 1000 1000 5 3 6 2 1000 1000 3 2 1000 4 1000 1000 1000 1000 4 1000 1000 1000 1000 5 5 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 5 3 1 2 1000 1000 4 3 1000 5 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1 1000 1000 1000 1000 1000 1000 1000 1000 2 2 4 1000 1000 1000 3 4 1000 1000 1000 1000 3 1000 4 1000 0 1000 1000 1000 3 1000 1000 1000 1000 1000 3 3 1000 2 1000 4 5 1000 1000 1000 1000 1000 1000 1000 2 1000 1000 1000 1000 1000 1000 3 1000 1000 3 2 1000 4 1000 1000 6 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 4 2 3 1000 7 1000 1000 1000 1000 4 4 1000 1000 1000 1000 1000 1000 1000 3 2 1 1000 8 1000 1000 1000 4 1000 1000 1000 1000 1 1000 1000 4 2 9 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 10 1000 1000 1000 1000 1000 1000 1000 11 1000 1000 1000 1000 1000 1000 3 12 1000 1000 1000 1000 4 13 1000 1000 1000 1000 1000 14 1000 1000 2 1000 Service Components 15 1000 5 1000 16 1000 1000 1000 17 1000 1000 1000 18 1000 1000 19 1000 1000 20 1000 1000 21 1000 22 1000 23 2 Knowledge Discovery Business Inelligence Reporting Data Human Resources Financial Assets / Materials 8.29.2 Precision / Recall Ranking Defines the set of capabilities that support selection and retrieval of records ranked to optimize precision against recall. Development & Integration Human Capital / Workforce Security JOINT ARCHITECTURE WORKING GROUP Collaboration Search Communication Systems Forms Service 41

Less than 5% of the budget accounted for in the Exhibit 300 s yet we still find overlaps in capability. Think about what we might find if everything was aligned to a common framework 42

Some Final Thoughts regarding IT Efficiencies and Enterprise Architecture Where will the cost savings come from? 43

People attending the conference ~600 Annual Loaded Cost to Government ($300K/per year) $180,000,000/year ($300K per contractor, $250K per govie, say, 2/3 of audience is contractor, 1/3 govie) $120,000,000 + $ 50,000,000 ------------------ $170,000,000/year Associated Activity: Architecture 50% to 75% of an Agency s budget goes to manpower! 44

JOINT ARCHITECTURE WORKING GROUP 45

The Bottom Line on the JAWG We work together collaboratively Each IC Element has unique skills and abilities, that when combined with other IC Elements respective skills and abilities supports the overarching Mission of the Intelligence Community IT is all about providing agility for the Mission; a force multiplier! Our JARM tools can scale and are usable at multiple levels of an organization/enterprise/community, for many different perspectives. It is all about providing any data, any time, any place, usable by any authorized consumer; preventable only by law or policy, not technology. JOINT ARCHITECTURE WORKING GROUP 46

For More Information: JAWG on Intelink: (JWICS) www.intelink.ic.gov/wiki/joint_architecture_working_group (NIPR) www.intelink.gov/wiki/joint_architecture_working_group More Questions: jawgleadershipsupport@ugov.gov randy.c.marks@ugov.gov JOINT ARCHITECTURE WORKING GROUP

Questions The greater danger for most of us lies not in setting our aim high and falling short; but in setting our aim too low, And achieving our mark. Michelangelo JOINT ARCHITECTURE WORKING GROUP 48