1	"September 20-22" September 20-22, 2011 San Jose, CA Day 1-part 2 Systems Engineering Team connected vehicle Core System Architecture/Requirements Workshop #2
2	"Views that will guide how..." Views that will guide how the system is built, operated, and maintained
3	Architecture Viewpoints Enterprise: Organizational entities and their relationships Focus on Scope and policy For each view: Description Consideration/Concerns Entities and their relationships (diagram) Alternatives explored Other related views
4	Enterprise View 4.1.1 – Security Credentials Distribution Description: Depicts the Enterprise Objects involved in the mission of configuring Security Credentials for Center, Mobile and Field Users. Relies on External Support Systems (ESS) to provide and manage Mobile Users’ credentials (CA & RA) Preserves privacy of Mobile Users Simplifies management of the Cert process Core System does provide digital (X.509) certificates to Field Nodes and Centers.
5	Enterprise View 4.1.1 – Security Credentials Distribution Considerations/Concerns Addressed:
6	Enterprise View 4.1.1 – Security Credentials Distribution
7	Enterprise View 4.1.1 – Security Credentials Distribution
8	Enterprise View 4.1.1 – Security Credentials Distribution Alternatives explored Core as a 1609.2 CA Would require establishing CA hierarchy among Cores, additional system security requirements Core as a 1609.2 RA Led to complex arrangements, unclear if privacy could be preserved Core as CA and RA Potential exposure of mobile user identity
9	Enterprise View 4.1.1 – Security Credentials Distribution Related Views: Functional View – Credentials Distribution Functional View – Misbehavior Management Functional View – Core Backup
10	Enterprise View 4.1.2 – Operations Description Focusing on the relationships between Cores and with external agencies Agreements over data coverage, cert distribution, and data/service backup A national body could maintain a list of all Cores and their service/geographic scope
11	Enterprise View 4.1.2 – Operations Considerations/Concerns Addressed
12	Enterprise View 4.1.2 - Operations
13	Enterprise View 4.1.2 - Operations Alternatives explored None Related Views: Enterprise View – Governance Functional View – Data Distribution Functional View – System Configuration Functional View – User Configuration Functional View – Core Backup
14	Enterprise View 4.1.3 – Core System & Application Development / Deployment Description Addresses the relationships involved in developing and deploying Core Systems and external applications 5 enterprises involved Developers Deployers End Users Specification entities Support Entities
15	Enterprise View 4.1.3 – Core System & Application Development / Deployment Considerations/Concerns Addressed
16	Enterprise View 4.1.3 – Core System & Application Development / Deployment Diagram here
17	Enterprise View 4.1.3 – Core System & Application Development / Deployment Alternatives explored: none Related Views: Enterprise View – Security Credentials Enterprise View – Configuration and Maintenance Enterprise View – Governance
18	Enterprise View 4.1.4 – Configuration & Maintenance Description Relationships involved in the operations and maintenance of the Core System Policy settings may vary across jurisdictions Establishment of maintenance agreements among agencies Coordination with Core Certifying Authority to establish and maintain consistency across Cores
19	Enterprise View 4.1.4 – Configuration & Maintenance Considerations/Concerns Addressed
20	Enterprise View 4.1.4 – Configuration & Maintenance Diagram here
21	Enterprise View 4.1.4 – Configuration & Maintenance Alternatives explored: none Related Views: Enterprise View – Governance Functional View – System Configuration Functional View – User Configuration Functional View – System Monitor and Control
22	Enterprise View 4.1.5 – Governance Description Multiple Cores (federation) allows flexible deployments, allowing for overlap and interactions among Cores Needs to be managed/governed via policy Certifying Core Systems based on a common set of standards/practices Gatekeeper of who can be a Core, remain a Core Manages relationships with External Support Systems (for security)
23	Enterprise View 4.1.5 – Governance Considerations/Concerns Addressed
24	Enterprise View 4.1.5 – Governance
25	Enterprise View 4.1.5 – Governance Core Certifying Authority (CCA) Potential membership: US DOT State/Local DOTs Automakers Equipment Vendors Mobile User telecommunications providers Roles: “the Gatekeeper” – Creates Core Certification Plan (how to become a Core) Certifies and then monitors Core operations per the plan Controls X.509 CA that distributes Core root certificates Determines what ESS’ may provide services to the Core
26	Enterprise View 4.1.5 – Governance Alternatives explored: Market based – letting the market/industry sort it out Not selected as security/privacy could be compromised and interoperability would be difficult to achieve or maintain
27	"Related Views" Related Views
28	Enterprise View 4.1.6 – Business Model Facilitation Description Relationships that may exist as part of business models that leverage the Core System to deploy applications and exchange data between System Users One enterprise in the relationship compensates the other enterprise in the relationship Monetary, information, other mutual benefits
29	Enterprise View 4.1.6 – Business Model Facilitation Considerations/Concerns Addressed
30	Enterprise View 4.1.6 – Business Model Facilitation Diagram here
31	Enterprise View 4.1.6 – Business Model Facilitation Alternatives explored: none Related Views: Enterprise View – Security Credentials Distribution Enterprise View – Core System and Application Development and Deployment Enterprise View – Governance
32	Tuesday Wrap-Up Talked about Core System program ConOps System Architecture organization Requirements organization Enterprise Views Tomorrow Functional & Connectivity Architecture Views