|
|
(4 intermediate revisions by 2 users not shown) |
Line 1: |
Line 1: |
− | ==== Segment and SSC Service Diagrams ====
| + | {{Delete|reason=Expired content.}} |
− | {| class="wikitable" | |
− | |+
| |
− | !Item
| |
− | !Accountable (Segment Architect)
| |
− | !Responsible
| |
− | !Status
| |
− | |-
| |
− | |Connectivity Segment Diagram
| |
− | |Melissa
| |
− | |Melissa
| |
− | |Completed 20-09-2019
| |
− | |-
| |
− | |Connectivity Motivation Diagram
| |
− | |Melissa
| |
− | |Thomas Simpson
| |
− | |Assigned 01-10-2019
| |
− | |-
| |
− | |Connectivity Capability Planning Diagram
| |
− | |Melissa
| |
− | |Melissa
| |
− | |Started 01-10-2019
| |
− | |-
| |
− | |Intra-building Network Services - Business Process Coop Diagram
| |
− | |Melissa
| |
− | |Team + SKA
| |
− | |Started (GC WiFi) 01-10-2019
| |
− | |-
| |
− | |Intra-building Network Services - Technology Usage Diagram
| |
− | |Melissa
| |
− | |Team + SKA
| |
− | |Started (GC WiFi) 01-10-2019
| |
− | |-
| |
− | |Satellite - Business Process Coop Diagram
| |
− | |Melissa
| |
− | |
| |
− | |Not Started
| |
− | |-
| |
− | |Satellite - Technology Usage Diagram
| |
− | |Melissa
| |
− | |
| |
− | |Not Started
| |
− | |-
| |
− | |Internet - Business Process Coop Diagram
| |
− | |Melissa
| |
− | |
| |
− | |Not Started
| |
− | |-
| |
− | |Internet - Technology Usage Diagram
| |
− | |Melissa
| |
− | |
| |
− | |Not Started
| |
− | |-
| |
− | |GC WAN - Business Process Coop Diagram
| |
− | |Melissa
| |
− | |
| |
− | |Started
| |
− | |-
| |
− | |GC WAN - Technology Usage Diagram
| |
− | |Melissa
| |
− | |
| |
− | |Not Started
| |
− | |-
| |
− | |Hosting Segment Diagram
| |
− | |Craig Bradley
| |
− | |Craig Bradley
| |
− | |
| |
− | |-
| |
− | |Hosting Motivation Diagram
| |
− | |Craig Bradley
| |
− | |
| |
− | |
| |
− | |-
| |
− | |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
| |
− | |
| |
− | |
| |
− | |-
| |
− | |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
| |
− | |
| |
− | |
| |
− | |
| |
− | |-
| |
− | |Internal Credential Management - Technology Usage Diagram
| |
− | |
| |
− | |
| |
− | |
| |
− | |-
| |
− | |External Credential Management - Business Process Coop Diagram
| |
− | |
| |
− | |
| |
− | |
| |
− | |-
| |
− | |External Credential Management - Technology Usage Diagram
| |
− | |
| |
− | |
| |
− | |
| |
− | |-
| |
− | |Firewall - Business Process Coop Diagram
| |
− | |
| |
− | |
| |
− | |
| |
− | |-
| |
− | |Firewall - Technology Usage Diagram
| |
− | |
| |
− | |
| |
− | |
| |
− | |-
| |
− | |Secure Remote Access - Business Process Coop Diagram
| |
− | |
| |
− | |
| |
− | |
| |
− | |-
| |
− | |Secure Remote Access - TechnologysUsage Diagram
| |
− | |
| |
− | |
| |
− | |
| |
− | |-
| |
− | |Classified Infrastructure - Business Process Coop Diagram
| |
− | |
| |
− | |
| |
− | |
| |
− | |-
| |
− | |Classified Infrastructure - Technology Usage Diagram
| |
− | |
| |
− | |
| |
− | |
| |
− | |-
| |
− | |Directory Services - Business Process Coop Diagram
| |
− | |
| |
− | |
| |
− | |
| |
− | |-
| |
− | |Directory Services - Technology Usage Diagram
| |
− | |
| |
− | |
| |
− | |
| |
− | |-
| |
− | |Procurement Management Segment Diagram
| |
− | |TBD
| |
− | |
| |
− | |
| |
− | |-
| |
− | |Procurement Management Motivation Diagram
| |
− | |TBD
| |
− | |
| |
− | |
| |
− | |-
| |
− | |Procurement Management Capability Planning Diagram
| |
− | |TBD
| |
− | |
| |
− | |
| |
− | |-
| |
− | |
| |
− | |
| |
− | |
| |
− | |
| |
− | |-
| |
− | |Platform Segment Diagram
| |
− | |Craig Hill
| |
− | |Craig Hill
| |
− | |
| |
− | |-
| |
− | |Platform Motivation Diagram
| |
− | |Craig Hill
| |
− | |
| |
− | |
| |
− | |-
| |
− | |Platform Capability Planning Diagram
| |
− | |Craig Hill
| |
− | |
| |
− | |
| |
− | |-
| |
− | |
| |
− | |
| |
− | |
| |
− | |
| |
− | |-
| |
− | |Internal Support and Management Segment Diagram
| |
− | |TBD
| |
− | d
| |
− | |
| |
− | |
| |
− | |-
| |
− | |Internal Support - Determine how to sub-divide.
| |
− | |TBD
| |
− | |
| |
− | |
| |
− | |-
| |
− | |
| |
− | |
| |
− | |
| |
− | |
| |
− | |}
| |
− | | |
− | ==== Service Business Diagrams ====
| |
− | * Business Process Cooperation Diagrams for priority services in each segment. To be determined by segment architects and priorities.
| |
− | | |
− | ==== Capability Planning Diagrams ====
| |
− | Link SSC Services to capabilities.
| |
− | * Specifics TBD as service diagrams are initiated.
| |
− | | |
− | ==== Motivation Diagrams ====
| |
− | Motivation analysis - many things that can be done....
| |
− | * 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]
| |
− | * SSC 3.0
| |
− | | |
− | ==== Link Capabilities to Motivation ====
| |
− | Tasks forthcoming....
| |
− | | |
− | ==== SSC IT Standards ====
| |
− | Replace the existing spreadsheet of IT Standards.
| |
− | * 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]
| |
− | ** Choose an appropriate category to distinguish those objects, e.g.: "SSC IT Standard" [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]
| |
− | * Manage the IT Standards henceforth in QW.
| |
− | | |
− | ==== Applications ====
| |
− | * Choose a category to associate with "high-level" applications that we want to report upon/track/list. [SKA]
| |
− | * Add to conventions/metamodel. [SKA]
| |
− | * Apply the category to existing applications in the system (Qualiware, GCDocs, BITS).
| |
− | * Prepare a demonstrative Matrix to display them [SKA]
| |
− | | |
− | ==== Internal Management Models ====
| |
− | * BITS application architecture?
| |
− | * EBIDM/Business Intake... many process documents available. It's not an SSC service, but it should be.
| |
− | * Application management/reporting. CIO? What's in this report? What is that report called? What do we need to report on? Ask JOHN B.
| |
− | * Review and refine the EA process models.
| |
− | * PGoF model?
| |
− | * Service management framework? Service approval processes?
| |
− | | |
− | ==== 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....
| |