Line 15: |
Line 15: |
| |Melissa | | |Melissa |
| |Thomas Simpson | | |Thomas Simpson |
− | |Assigned 01-10-2019 | + | |Started 01-10-2019 |
| |- | | |- |
| |Connectivity Capability Planning Diagram | | |Connectivity Capability Planning Diagram |
| |Melissa | | |Melissa |
| |Melissa | | |Melissa |
− | |Started 01-10-2019 | + | |Completed 01-10-2019 |
| |- | | |- |
| |Intra-building Network Services - Business Process Coop Diagram | | |Intra-building Network Services - Business Process Coop Diagram |
| |Melissa | | |Melissa |
− | | | + | |Team + SKA |
− | |Startedd(GC WiFi) 01-10-2019 | + | |Started (GC WiFi) 01-10-2019 |
| |- | | |- |
| |Intra-building Network Services - Technology Usage Diagram | | |Intra-building Network Services - Technology Usage Diagram |
| + | |Melissa |
| + | |Team + SKA |
| + | |Started (GC WiFi) 01-10-2019 |
| + | |- |
| + | |Satellite - Business Process Coop Diagram |
| |Melissa | | |Melissa |
| | | | | |
− | |Started (GC WiFi) 01-10-2019iitr | + | |Not Started |
| |- | | |- |
− | |Satellite - Business Process Coop Diagram | + | |Satellite - Technology Usage Diagram |
| |Melissa | | |Melissa |
| | | | | |
Line 38: |
Line 43: |
| |- | | |- |
| |Internet - Business Process Coop Diagram | | |Internet - Business Process Coop Diagram |
| + | |Melissa |
| + | | |
| + | |Not Started |
| + | |- |
| + | |Internet - Technology Usage Diagram |
| |Melissa | | |Melissa |
| | | | | |
Line 43: |
Line 53: |
| |- | | |- |
| |GC WAN - Business Process Coop Diagram | | |GC WAN - Business Process Coop Diagram |
| + | |Melissa |
| + | | |
| + | |Started |
| + | |- |
| + | |GC WAN - Technology Usage Diagram |
| |Melissa | | |Melissa |
| | | | | |
Line 58: |
Line 73: |
| |- | | |- |
| |Hosting Capability Planning Diagram | | |Hosting Capability Planning Diagram |
| + | |Craig Bradley |
| + | | |
| + | | |
| + | |- |
| + | |Cloud Brokering - Business Process Coop Diagram |
| + | |Craig Bradley |
| + | | |
| + | | |
| + | |- |
| + | |Cloud Brokering - Technology Usage Diagram |
| + | |Craig Bradley |
| + | | |
| + | | |
| + | |- |
| + | |Data Center Facilities Management - Business Process Coop Diagram |
| + | |Craig Bradley |
| + | | |
| + | |Started |
| + | |- |
| + | |Data Center Facilities Management - Technology Usage Diagram |
| + | |Craig Bradley |
| + | | |
| + | | |
| + | |- |
| + | |High-performance Computing - Business Process Coop Diagram |
| + | |Craig Bradley |
| + | | |
| + | | |
| + | |- |
| + | |High-performance Computing - Technology Usage Diagram |
| + | |Craig Bradley |
| + | | |
| + | | |
| + | |- |
| + | |Midrange - Business Process Coop Diagram |
| + | |Craig Bradley |
| + | | |
| + | | |
| + | |- |
| + | |Midrange - Technology Usage Diagram |
| + | |Craig Bradley |
| + | | |
| + | | |
| + | |- |
| + | |Storage - Business Process Coop Diagram |
| + | |Craig Bradley |
| + | | |
| + | | |
| + | |- |
| + | |Storage - Technology Usage Diagram |
| + | |Craig Bradley |
| + | | |
| + | | |
| + | |- |
| + | |Bulk Print - Business Process Coop Diagram |
| + | |Craig Bradley |
| + | | |
| + | | |
| + | |- |
| + | |Bulk Print - Technology Usage Diagram |
| + | |Craig Bradley |
| + | | |
| + | | |
| + | |- |
| + | |Mainframe - Business Process Coop Diagram |
| + | |Craig Bradley |
| + | | |
| + | | |
| + | |- |
| + | |Mainframe - Technology Usage Diagram |
| + | |Craig Bradley |
| + | | |
| + | | |
| + | |- |
| + | |Facilities-as-a-service - Business Process Coop Diagram |
| + | |Craig Bradley |
| + | | |
| + | | |
| + | |- |
| + | |Facilities-as-a-service - Technology Usage Diagram |
| |Craig Bradley | | |Craig Bradley |
| | | | | |
Line 63: |
Line 158: |
| |- | | |- |
| |Security Segment Diagram | | |Security Segment Diagram |
| + | |Michel Belanger |
| + | |Michel Belanger |
| + | | |
| + | |- |
| + | |Security Motivation Diagram |
| + | |Michel Belanger |
| + | | |
| + | | |
| + | |- |
| + | |Security Capability Planning Diagram |
| + | |Michel Belanger |
| + | | |
| + | | |
| + | |- |
| + | |Internal Credential Management - Business Process Coop Diagram |
| + | |Michel Belanger |
| + | | |
| + | | |
| + | |- |
| + | |Internal Credential Management - Technology Usage Diagram |
| + | |Michel Belanger |
| + | | |
| + | | |
| + | |- |
| + | |External Credential Management - Business Process Coop Diagram |
| + | |Michel Belanger |
| | | | | |
| + | | |
| + | |- |
| + | |External Credential Management - Technology Usage Diagram |
| + | |Michel Belanger |
| | | | | |
| | | | | |
| |- | | |- |
− | |Security Motivation Diagram | + | |Firewall - Business Process Coop Diagram |
| + | |Michel Belanger |
| + | | |
| + | | |
| + | |- |
| + | |Firewall - Technology Usage Diagram |
| + | |Michel Belanger |
| + | | |
| + | | |
| + | |- |
| + | |Secure Remote Access - Business Process Coop Diagram |
| + | |Michel Belanger |
| + | | |
| + | | |
| + | |- |
| + | |Secure Remote Access - TechnologysUsage Diagram |
| + | |Michel Belanger |
| + | | |
| + | | |
| + | |- |
| + | |Classified Infrastructure - Business Process Coop Diagram |
| + | |Michel Belanger |
| + | | |
| | | | | |
| + | |- |
| + | |Classified Infrastructure - Technology Usage Diagram |
| + | |Michel Belanger |
| | | | | |
| | | | | |
| |- | | |- |
− | |Security Capability Planning Diagram | + | |Directory Services - Business Process Coop Diagram |
| + | |Michel Belanger |
| + | | |
| | | | | |
| + | |- |
| + | |Directory Services - Technology Usage Diagram |
| + | |Michel Belanger |
| | | | | |
| | | | | |
| |- | | |- |
| |Procurement Management Segment Diagram | | |Procurement Management Segment Diagram |
| + | |TBD |
| + | | |
| + | | |
| + | |- |
| + | |Procurement Management Motivation Diagram |
| + | |TBD |
| + | | |
| + | | |
| + | |- |
| + | |Procurement Management Capability Planning Diagram |
| + | |TBD |
| + | | |
| + | | |
| + | |- |
| + | |WTD Provisioning - Business Process Coop Diagram |
| + | | |
| + | | |
| + | | |
| + | |- |
| + | |WTD Provisioning - Technology Usage Diagram |
| + | | |
| + | | |
| + | | |
| + | |- |
| + | |Mobile Devices - Business Process Coop Diagram |
| + | | |
| + | | |
| + | | |
| + | |- |
| + | |Mobile Devices - Technology Usage Diagram |
| + | | |
| + | | |
| + | | |
| + | |- |
| + | |Fixed Line - Business Process Coop Diagram |
| | | | | |
| | | | | |
| | | | | |
| |- | | |- |
− | |Procurement Management Motivation Diagram | + | |Fixed Line - Technology Usage Diagram |
| + | | |
| + | | |
| + | | |
| + | |- |
| + | |Conferencing Services - Business Process Coop Diagram |
| + | | |
| + | | |
| + | | |
| + | |- |
| + | |Conferencing Services - Technology Usage Diagram |
| + | | |
| + | | |
| + | | |
| + | |- |
| + | |Contact Center - Business Process Coop Diagram |
| + | | |
| + | | |
| + | | |
| + | |- |
| + | |Contact Center - Technology Usage Diagram |
| + | | |
| + | | |
| + | | |
| + | |- |
| + | |Toll-free Voice - Business Process Coop Diagram |
| | | | | |
| | | | | |
| | | | | |
| |- | | |- |
− | |Procurement Management Capability Planning Diagram | + | |Toll-free Voice - Technology Usage Diagram |
| | | | | |
| | | | | |
Line 107: |
Line 322: |
| | | | | |
| |- | | |- |
− | |Internal Support and Management Segment Diagram | + | |Email - Business Process Coop Diagram |
| + | |Craig Hill |
| + | | |
| + | | |
| + | |- |
| + | |Email - Technology Usage Diagram |
| + | |Craig Hill |
| + | | |
| + | | |
| + | |- |
| + | |Database - Business Process Coop Diagram |
| + | |Craig Hill |
| + | | |
| + | | |
| + | |- |
| + | |Database - Technology Usage Diagram |
| + | |Craig Hill |
| + | | |
| + | | |
| + | |- |
| + | |Middleware - Business Process Coop Diagram |
| + | |Craig Hill |
| + | | |
| | | | | |
| + | |- |
| + | |Middleware - Technology Usage Diagram |
| + | |Craig Hill |
| | | | | |
| | | | | |
| |- | | |- |
− | |Internal Support - Determine how to sub-divide. | + | |Internal Support and Management Segment Diagram |
| + | |TBD |
| | | | | |
| + | | |
| + | |- |
| + | |Internal Support - Determine how to sub-divide, and what priority areas. |
| + | |TBD |
| | | | | |
| | | | | |
Line 123: |
Line 368: |
| |} | | |} |
| | | |
− | ==== Service Business Diagrams ==== | + | ==== Segment Diagrams ==== |
| + | For each main segment (6): |
| + | * Segment (Business Process Cooperation) Diagram (defines the functions/services in that segment) |
| + | * Motivation Diagram (links capabilities to drivers/goals/outcomes) |
| + | * Capability Planning Diagram (links services to capabilities) |
| + | |
| + | ==== Service Business Process Cooperation Diagrams ==== |
| * Business Process Cooperation Diagrams for priority services in each segment. To be determined by segment architects and priorities. | | * Business Process Cooperation Diagrams for priority services in each segment. To be determined by segment architects and priorities. |
| + | * Technology Usage Diagram (FOR that SERVICE only). Other diagrams will be needed in future for common infrastructure components. |
| + | * As necessary, application and technology (detail) diagrams. |
| | | |
− | ==== Capability Planning Diagrams ====
| + | ==== Motivation Diagrams (strategic) ==== |
− | Link SSC Services to capabilities.
| + | Motivation analysis - many things that should be done.... |
− | * Specifics TBD as service diagrams are initiated.
| + | * Strategic drivers/goals/outcomes - analysis |
− | | + | * TBS Policy drivers/goals/outcomes |
− | ==== Motivation Diagrams ==== | + | * g ITSG 22 [Jacques?] |
− | Motivation analysis - many things that can be done.... | + | * ITSG 33 [Jacques?] |
− | * Create a motivation diagram detailing ITSG 22 [Jacques?] | |
− | * Create a motivation diagram detailing ITSG 33 [Jacques?] | |
| * ITSP 22. There's a model (reference model) in the tool now. How to link to motivation? [SKA/Jacques] | | * ITSP 22. There's a model (reference model) in the tool now. How to link to motivation? [SKA/Jacques] |
− | * SSC 3.0 | + | * SSC 3.0 - Should be a current priority. |
− | | |
− | ==== Link Capabilities to Motivation ====
| |
− | Tasks forthcoming....
| |
| | | |
| ==== SSC IT Standards ==== | | ==== SSC IT Standards ==== |
| Replace the existing spreadsheet of IT Standards. | | Replace the existing spreadsheet of IT Standards. |
| + | * Represent IT Standards as drivers, with goals/outcomes/requirements/constraints. |
| * Determine proper object to use to represent standards in ArchiMate. (Driver, Goal, Requirement, Constraint?) [SKA] | | * Determine proper object to use to represent standards in ArchiMate. (Driver, Goal, Requirement, Constraint?) [SKA] |
− | ** And determine how to link to motivation (Driver/Goals/Outcome....) [SKA] | + | ** Need tool modifications to support (Attributes added to Driver template). [Denise, Steve L., Steve A.] |
− | ** Choose an appropriate category to distinguish those objects, e.g.: "SSC IT Standard" [SKA]
| |
| ** Add to conventions and content metamodel. [SKA] | | ** Add to conventions and content metamodel. [SKA] |
− | * Modify the chosen object to have the attributes needed to support IT Standards (as we did based on the DND standard template). [Denise/SKA]
| |
| * Populate the known IT Standards as a catalogue within Qualiware. [TBD] | | * Populate the known IT Standards as a catalogue within Qualiware. [TBD] |
| * Manage the IT Standards henceforth in QW. | | * Manage the IT Standards henceforth in QW. |
Line 163: |
Line 410: |
| * PGoF model? | | * PGoF model? |
| * Service management framework? Service approval processes? | | * Service management framework? Service approval processes? |
| + | * SISD (should be covered under SIS Service - but they need integration help from EA in particular - focus. Identify inefficiencies/gaps.) |
| + | |
| + | ==== Bottom-Up - Foundation Technology Service Models ==== |
| + | Services down may not always produce all the supporting architecture needed. May wish to consider a parallel "bottom-up" approach, identifying key areas of infrastructure, drawing from recently prepared RAD functional decompositions to identify reusable and key parts/pieces, e.g.: Data Center, Inter-building network, DNS, Active Directory, etc.... |
| + | * Email infrastructure |
| + | * Data centers |
| + | * Data Center Networks |
| + | * Intra-building network/GC WAN |
| + | * Networks - Conceptual |
| + | * ... |