Difference between revisions of "Models/Work to Do - SSC EA Team"
Jump to navigation
Jump to search
| Line 368: | 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. | ||
| − | + | ==== Motivation Diagrams (strategic) ==== | |
| − | + | Motivation analysis - many things that should be done.... | |
| − | + | * Strategic drivers/goals/outcomes - analysis | |
| − | + | * TBS Policy drivers/goals/outcomes | |
| − | ==== Motivation Diagrams ==== | + | * g ITSG 22 [Jacques?] |
| − | Motivation analysis - many things that | + | * 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. |
| − | |||
| − | |||
| − | |||
==== 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] | ||
| − | ** | + | ** Need tool modifications to support (Attributes added to Driver template). [Denise, Steve L., Steve A.] |
| − | |||
** Add to conventions and content metamodel. [SKA] | ** Add to conventions and content metamodel. [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 408: | 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 ==== | ==== 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.... | 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 | ||
| + | * ... | ||
Revision as of 12:49, 2 October 2019
Segment and SSC Service Diagrams
| 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 | 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 | ||
| 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 | ||
| Directory Services - Business Process Coop Diagram | Michel Belanger | ||
| Directory Services - Technology Usage Diagram | Michel Belanger | ||
| 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 | |||
| 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 | |||
| Toll-free Voice - Technology Usage Diagram | |||
| Platform Segment Diagram | Craig Hill | Craig Hill | |
| Platform Motivation Diagram | Craig Hill | ||
| Platform Capability Planning Diagram | Craig Hill | ||
| 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 and Management Segment Diagram | TBD | ||
| Internal Support - Determine how to sub-divide, and what priority areas. | TBD | ||
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.
- 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.
Motivation Diagrams (strategic)
Motivation analysis - many things that should be done....
- Strategic drivers/goals/outcomes - analysis
- TBS Policy drivers/goals/outcomes
- g ITSG 22 [Jacques?]
- 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 - Should be a current priority.
SSC 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]
- Need tool modifications to support (Attributes added to Driver template). [Denise, Steve L., Steve A.]
- Add to conventions and content metamodel. [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?
- 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
- ...
