Enterprise Service Provisioning
ProPath
Table of Contents
Enterprise Service Provisioning Process Map ... 1
Process: Enterprise Service Provisioning ... 2
Enterprise Service Provisioning Description and Goals ... 3
Description... 3
Goals... 3
Enterprise Service Provisioning RACI Information ... 4
Enterprise Service Provisioning Process ... 7
Process Activity Name: ESPRO-1 Create Detailed Service Implementation Design... 7
Process Activity Name: ESPRO-2 Conduct Review to Assess Infrastructure Impacts ... 8
Process Activity Name: ESPRO-3 Develop Service Integration Plan ... 9
Process Activity Name: ESPRO-4 Develop Service ... 10
Process Activity Name: ESPRO-5 Develop Service Integration Components ... 12
Process Activity Name: ESPRO-6 Test Service... 13
Process Activity Name: ESPRO-7 Coordinate Integration Testing and Service Acceptance ... 14
Process Activity Name: ESPRO-8 Provide Service Documentation ... 16
Process Activity Name: ESPRO-9 Verify Documentation Available for MS 2 Review ... 18
Process Activity Name: ESPRO-10 Confirm Technical Service Ownership ... 19
Process Activity Name: ESPRO-11 Coordinate eMI Modifications as Needed ... 20
Process Activity Name: ESPRO-12 Confirm Service Deployment Readiness21 Process Activity Name: ESPRO-13 Activate New Service ... 22
Enterprise Service Provisioning Process Map
Ser vi ce Ow ne r Pr oj ec t M an ag er Ser vi ce A rc hi te ct Te ch nic al Ser vi ce Ow ne r So ftw ar e Q ual ity As su ran ce An al ys t Ser vi ce In te gr ato r D ev el op erEnterprise Service Provisioning
From: ESPEC Enterprise Service Specification ESPRO-4 Develop Service ESPRO-2 Conduct Review to Assess Infrastructure Impacts ESPRO-14 Monitor Service Performance ESPRO-6 Test Service ESPRO-8 Provide Service Documentation ESPRO-11 Coordinate eMI Modifications as Needed ESPRO-13 Activate New Service ESPRO-1 Create Detailed Service Implementation Design ESPRO-7 Coordinate Integration Testing and Service Acceptance ESPRO-5 Develop Service Integration Components
home overview raci help
ESPRO-9 Verify Documentation Available for MS 2 Review ESPRO-10 Confirm Technical Service Ownership ESPRO-3 Develop Service Integration Plan ESPRO-12 Confirm Service Deployment Readiness
Process: Enterprise Service Provisioning
Overview: The process map for Enterprise Service Provisioning cycles through the following process and review activities:
ESPRO-1 Create Detailed Service Implementation Design ESPRO-2 Conduct Review to Assess Infrastructure Impacts ESPRO-3 Develop Service Integration Plan
ESPRO-4 Develop Service
ESPRO-5 Develop Service Integration Components ESPRO-6 Test Service
ESPRO-7 Coordinate Integration Testing and Service Acceptance ESPRO-8 Provide Service Documentation
ESPRO-9 Verify Documentation Available for MS 2 Review ESPRO-10 Confirm Technical Service Ownership
ESPRO-11 Coordinate eMI Modifications as Needed ESPRO-12 Confirm Service Deployment Readiness ESPRO-13 Activate New Service
Enterprise Service Provisioning Description and Goals
Description
The Enterprise Service Provisioning process is used when a new service or new service version is required by a solution that has been approved as an Active State project at Milestone 1. The scope of this process encompasses service development, testing, activation, and integration and monitoring within the enterprise Messaging Infrastructure (eMI) environment.
Goals
The goals of the Enterprise Service Provisioning process are to:
-Create the detailed service design and incorporate the design in the Service Oriented Architecture / Enterprise Shared Service (SOA/ESS) Detailed Design section of the System Design Document
- Develop associated service interfaces that meet the defined standards for use of services for the provisioning method utilized
- Develop a new service or update an existing service
- Conduct Unit Testing, Integration Testing and Service Acceptance
- Ensure the Technical Service Owner is assigned to exercise managerial ownership of the service in production
- Place the new service into eMI production environment for use by authorized applications and systems
Enterprise Service Provisioning RACI Information
The following describes the RACI information for this process:
ESPRO-1 Create Detailed Service Implementation Design
Responsible Role: Service Architect Accountable Role: Project Manager Consulted Role: Developer
Informed Role: Service Integrator
ESPRO-2 Conduct Review to Assess Infrastructure Impacts
Responsible Role: Service Integrator Accountable Role: Project Manager Consulted Role: Service Owner
Informed Role: Developer, Enterprise Shared Service Center of Excellence, Service Architect
ESPRO-3 Develop Service Integration Plan
Responsible Role: Service Integrator Accountable Role: Project Manager
Informed Role: Developer, Service Architect, Service Owner
ESPRO-4 Develop Service
Responsible Role: Developer Accountable Role: Project Manager Consulted Role: Service Architect
Informed Role: Service Integrator, Service Owner
ESPRO-5 Develop Service Integration Components
Responsible Role: Service Integrator Accountable Role: Project Manager
Consulted Role: Developer
Informed Role: Service Architect, Service Owner
ESPRO-6 Test Service
Responsible Role: Developer Accountable Role: Project Manager Consulted Role: Service Architect
Informed Role: Service Integrator, Service Owner, Software Quality Assurance Analyst
ESPRO-7 Coordinate Integration Testing and Service Acceptance
Responsible Role: Software Quality Assurance Analyst Accountable Role: Project Manager
Consulted Role: Developer, Service Architect, Service Integrator, Enterprise Shared Service Center of Excellence Technical Working Group
Informed Role: Service Owner
ESPRO-8 Provide Service Documentation
Responsible Role: Service Integrator Accountable Role: Project Manager
Consulted Role: Developer, Information Security Officer, Service Architect
Informed Role: Software Quality Assurance Service Independent Verification and Validation Manager
ESPRO-9 Verify Documentation Available for MS 2 Review
Responsible Role: Project Manager
Accountable Role: Director, Product Assessment
Consulted Role: Developer, Enterprise Shared Service Center of Excellence, Service Integrator Informed Role: Service Owner
Responsible Role: Project Manager
Accountable Role: Director, Product Assessment
Informed Role: eMI Project Manager, Enterprise Shared Service Center of Excellence, Service Integrator, Service Owner, Technical Service Owner
ESPRO-11 Coordinate eMI Modifications as Needed
Responsible Role: Technical Service Owner Accountable Role: eMI Project Manager
Consulted Role: Enterprise Shared Service Center of Excellence, Service Integrator Informed Role: Service Owner
ESPRO-12 Confirm Service Deployment Readiness
Responsible Role: Project Manager
Accountable Role: Director, Product Assessment Consulted Role: Service Integrator
Informed Role: Technical Service Owner
ESPRO-13 Activate New Service
Responsible Role: Technical Service Owner Accountable Role: eMI Project Manager
Consulted Role: Enterprise Shared Service Center of Excellence, Service Integrator Informed Role: Service Owner
ESPRO-14 Monitor Service Performance
Responsible Role: Technical Service Owner Accountable Role: eMI Project Manager
Consulted Role: Enterprise Shared Service Center of Excellence, Service Integrator Informed Role: Service Owner
Enterprise Service Provisioning Process
Process Activity Name: ESPRO-1 Create Detailed Service
Implementation Design
Previous Process Activity
Note: There is a flow from the Enterprise Service Specification Process into the Enterprise Service Provisioning Process.
Next Process Activity
ESPRO-2 Conduct Review to Assess Infrastructure Impacts
Description
The Service Architect updates the Service Oriented Architecture / Enterprise Shared Service (ESS) Detailed Design section of the System Design Document and creates the Service Test Plan. The Service Architect follows the architectural principles and standards established by the Enterprise Shared Service Center of Excellence as specified in the Enterprise Messaging
Infrastructure (eMI) Service Oriented Architecture (SOA) Governance policies to create the detailed service implementation design for the service. The completed System Design Document and Service Test Plan are stored in the Technical Services Project Repository (TSPR) if needed for Project Management Accountability System.
Artifacts Used
Initial Automated Tests Mock Service
Service Deployment Architecture Service Description(s)
Service Implementation Architecture Service Level Agreement(s)
Service Provisioning Method Service Specification Architecture System Design Document
Artifacts Created
Service Test Plan
System Design Document (Updated)
Responsible Role
Service Architect
Tools and Websites
Agiliance RiskVision Enterprise Operations GRC Instance Agiliance RiskVision National Release GRC Instance
CA LISA Service Virtualization
Enterprise Messaging Infrastructure (eMI) WIKI Home
IBM Rational Team Concert/Change and Configuration Management (RTC/CCM) Rational Software Architect
Service Registry Dashboard
Technical Services Project Repository (TSPR) VA EA ESS Center of Excellence
Wiley Introscope
Standards
None Listed
More Info
Refer to the eMI WIKI Technical Corner How To segment for questions on SOA-based services creation methods, both business and system.
Refer to the eMI SOA Governance segment for policies and procedures.
Process Activity Name: ESPRO-2 Conduct Review to Assess
Infrastructure Impacts
Previous Process Activity
ESPRO-1 Create Detailed Service Implementation Design
Next Process Activity
ESPRO-3 Develop Service Integration Plan
Description
The Service Integrator, in collaboration with the Service Owner, conducts a review of the service to identify any impacts related to the current Enterprise Messaging Infrastructure (eMI) to
determine the effect on the current configuration, capacity or performance requirements. For services built using COTS software, software licensing requirements need to be identified, estimates are prepared, and a plan is developed for the licensing. eMI enhancement funding is allocated from existing operational resources.
Artifacts Used
Service Description(s) System Design Document
Artifacts Created
Responsible Role
Service Integrator
Tools and Websites
Agiliance RiskVision Enterprise Operations GRC Instance Agiliance RiskVision National Release GRC Instance CA LISA Service Virtualization
Enterprise Messaging Infrastructure (eMI) WIKI Home
IBM Rational Team Concert/Change and Configuration Management (RTC/CCM) Rational Software Architect
Service Registry Dashboard
Technical Services Project Repository (TSPR) VA EA ESS Center of Excellence
Wiley Introscope
Standards
None Listed
More Info
Refer to the eMI WIKI Technical Corner How To segment for questions on SOA-based services creation methods, both business and system.
Process Activity Name: ESPRO-3 Develop Service Integration Plan
Previous Process Activity
ESPRO-2 Conduct Review to Assess Infrastructure Impacts
Next Process Activity
Note: The following process activities are performed concurrently: ESPRO-4 Develop Service
ESPRO-5 Develop Service Integration Components ESPRO-6 Test Service
Description
The Service Integrator develops the Service Integration Plan which identifies the integration activity needs and interactions with other external, dependent system components applications and systems or services. The Service Integrator uses the System Design Document system and/or subsystem(s) architecture section to guide the choices for inclusion in the Service Integration Plan.
Artifacts Used
System Design Document
Artifacts Created
Service Integration Plan
Responsible Role
Service Integrator
Tools and Websites
Agiliance RiskVision Enterprise Operations GRC Instance Agiliance RiskVision National Release GRC Instance CA LISA Service Virtualization
Enterprise Messaging Infrastructure (eMI) WIKI Home
IBM Rational Team Concert/Change and Configuration Management (RTC/CCM) Rational Software Architect
Service Registry Dashboard
Technical Services Project Repository (TSPR) VA EA ESS Center of Excellence
Wiley Introscope
Standards
Enterprise Testing Service Testing Guide
More Info
None Listed
Process Activity Name: ESPRO-4 Develop Service
Note: This activity is performed concurrently with the following activities: ESPRO-5 Develop Service Integration Components
ESPRO-6 Test Service
Previous Process Activity
ESPRO-3 Develop Service Integration Plan
Next Process Activity
Description
The Developer reviews the requirements in the Service Description and depending on the provisioning method either updates the Service component to enhance the service in the
enterprise Messaging Infrastructure (eMI) allowing service consumers to use the Service release or Service version, or develops the new Service from scratch. The Developer uses the
Development Test Environment (DTE) and architectural guidance provided in the Enterprise Messaging Infrastructure (eMI) WIKI to guide the development of the service. The Developer determines if additional tests need to be defined and adds them to the Service Test Plan. The Developer generates and unit tests the Service Build using the Service Test Plan. The System Design Document is updated to include interface control definitions.
Artifacts Used
Service Description(s) Service Test Plan
System Design Document
Artifacts Created
Service Build
Service Test Plan (Updated)
System Design Document (Updated)
Responsible Role
Developer
Tools and Websites
Agiliance RiskVision Enterprise Operations GRC Instance Agiliance RiskVision National Release GRC Instance CA LISA Service Virtualization
Enterprise Messaging Infrastructure (eMI) WIKI Home
IBM Rational Team Concert/Change and Configuration Management (RTC/CCM) Rational Software Architect
Service Registry Dashboard
Technical Services Project Repository (TSPR) VA EA ESS Center of Excellence
Wiley Introscope
Standards
More Info
Refer to the eMI WIKI eMI SOA Governance segment for policies and procedures.
Process Activity Name: ESPRO-5 Develop Service Integration
Components
Note: This activity is performed concurrently with the following activities: ESPRO-4 Develop Service
ESPRO-6 Test Service
Previous Process Activity
ESPRO-3 Develop Service Integration Plan
Next Process Activity
ESPRO-7 Coordinate Integration Testing and Service Acceptance
Description
The Service Integrator develops the service integration components, called a wrapper, for the provisioned service using the applicable Commercial Off the Shelf Software (COTS) / Government Off the Shelf Software (GOTS) Services Application Programming Interfaces (APIs). The Service Integration Plan, the Service Implementation Architecture, the System Design Description and Enterprise Messaging Infrastructure (eMI) WIKI are used to guide the development.
Artifacts Used
COTS/GOTS Application Programming Interfaces Specifications Service Implementation Architecture
Service Integration Plan System Design Document
Artifacts Created
Wrappers for Application Programming Interfaces
Responsible Role
Service Integrator
Tools and Websites
Agiliance RiskVision Enterprise Operations GRC Instance Agiliance RiskVision National Release GRC Instance CA Service Desk Manager
Enterprise Messaging Infrastructure (eMI) WIKI Home
Rational Software Architect Service Registry Dashboard
Technical Services Project Repository (TSPR) VA EA ESS Center of Excellence
Wiley Introscope
Standards
None Listed
More Info
Refer to the eMI WIKI Technical Corner How To segment for questions on SOA-based services creation methods, both business and system.
Refer to the eMI SOA Governance segment for policies and procedures.
Process Activity Name: ESPRO-6 Test Service
Note: This activity is performed concurrently with the following activities: ESPRO-4 Develop Service
ESPRO-5 Develop Service Integration Components
Previous Process Activity
ESPRO-3 Develop Service Integration Plan
Next Process Activity
ESPRO-7 Coordinate Integration Testing and Service Acceptance
Description
The Developer performs tests that satisfy the requirements in the Service Test Plan using the Performance Environment to ensure the service meets the business cycle testing, error handling, and performance testing. The Developer documents findings in the Test Evaluation.
Artifacts Used
Service Build Service Test Plan
System Design Document
Artifacts Created
Service Build (Repaired) Test Evaluation
Responsible Role
Developer
Tools and Websites
Agiliance RiskVision Enterprise Operations GRC Instance Agiliance RiskVision National Release GRC Instance CA LISA Service Virtualization
Enterprise Messaging Infrastructure (eMI) WIKI Home
IBM Rational Team Concert/Change and Configuration Management (RTC/CCM) Rational Software Architect
Service Registry Dashboard
Technical Services Project Repository (TSPR) VA EA ESS Center of Excellence
Wiley Introscope
Standards
Enterprise Testing Service Testing Guide
More Info
Software Developer Kits are covered in the Enterprise Messaging Infrastructure (eMI) WIKI eMI Training library segment.
The Performance Environment is one of the available Development Test Environments
referenced in the eMI WIKI eMI Software Oriented Architecture (SOA) Environment. Contact the VA eMI Support mail group for access to Development Test Environments.
Process Activity Name: ESPRO-7 Coordinate Integration Testing and
Service Acceptance
Previous Process Activity
Note: The following process activities are performed concurrently: ESPRO-4 Develop Service
ESPRO-5 Develop Service Integration Components ESPRO-6 Test Service
Next Process Activity
Description
The Software Quality Assurance (SQA) Analyst coordinates the integration testing from the Service Test Plan in conjunction with Service Integrator, Developer, Enterprise Shared Service (ESS) Center of Excellence Technical Working Group, and the Technical Service Owner using the Development Test Environments Integration Test Environment. The integration testing ensures the service software successfully realizes all required interfaces, performs the functions intended, and performs within the required ESS Service Level Agreement tolerance. The SQA Analyst works with the Service Integrator to revise the Service Build to address any deficiencies identified during integration testing. The SQA Analyst works with the Service Owner to confirm that the service works as required by the Service Description and obtains an acknowledgement. The Acknowledgement and Test Evaluation are stored in the Technical Services Project
Repository (TSPR).
Artifacts Used
Service Build
Service Description(s) Service Integration Plan Service Level Agreement(s) Service Test Plan
System Design Document Test Evaluation
Wrappers for Application Programming Interfaces
Artifacts Created
Acknowledgement of Service Acceptance Service Build (Approved)
Test Evaluation (Updated)
Responsible Role
Software Quality Assurance Analyst
Tools and Websites
Agiliance RiskVision Enterprise Operations GRC Instance Agiliance RiskVision National Release GRC Instance CA LISA Service Virtualization
Enterprise Messaging Infrastructure (eMI) WIKI Home
IBM Rational Team Concert/Change and Configuration Management (RTC/CCM) Rational Software Architect
Service Registry Dashboard
VA EA ESS Center of Excellence Wiley Introscope
Standards
None Listed
More Info
Software Developer Kits are covered in the Enterprise Messaging Infrastructure (eMI) WIKI, eMI Training Library segment.
For information on Development Test Environments refer to the eMI WIKI eMI Software
Oriented Architecture (SOA) Environment segment. Contact the VA eMI Support mail group for access to Development Test Environments.
Process Activity Name: ESPRO-8 Provide Service Documentation
Previous Process Activity
ESPRO-7 Coordinate Integration Testing and Service Acceptance
Next Process Activity
ESPRO-9 Verify Documentation Available for MS 2 Review
Description
The Service Integrator reviews the Production Operations Manual (POM) or and Deployment Plan and updates as needed or creates POM and Deployment Plan when the service is not covered in an existing POM and Deployment Plan. The Service Integrator confirms that the service is within the system boundary of an Authority to Operate. The Service Integrator confers with the assigned Information Security Officer to update the System Security Plan as needed.
When the service is used by more than one Service Consumer, a brief Service Developer User WIKI is built that contains examples of service calls in a solution build. Any additional required Service Documentation is completed.
The Service Integrator confers with the Project Manager on which updated documents need to be stored in the Technical Services Project Repository (TSPR).
The Service Integrator creates the enterprise Messaging Infrastructure (eMI) Service Level Agreement which is required to promote the service into production.
Artifacts Used
Authority to Operate Deployment Plan
Production Operations Manual Service Documentation
Service Test Plan System Security Plan
Artifacts Created
Deployment Plan (New or Updated)
Production Operations Manual (New or Updated) Service Developer User Guide (WIKI)
Service Documentation (Updated) Service Level Agreement(s) System Security Plan (Updated)
Responsible Role
Service Integrator
Tools and Websites
Agiliance RiskVision Enterprise Operations GRC Instance Agiliance RiskVision National Release GRC Instance CA LISA Service Virtualization
Enterprise Messaging Infrastructure (eMI) WIKI Home
IBM Rational Team Concert/Change and Configuration Management (RTC/CCM) Rational Software Architect
Service Registry Dashboard
Technical Services Project Repository (TSPR) VA EA ESS Center of Excellence
Wiley Introscope
Standards
None Listed
More Info
The Developer's Corner on the eMI WIKI allows Service Integrator, Developer and others to add, modify, or delete content in collaboration with others involved or impacted by the service.
Services using the eMI need to complete and sign an eMI SLA. Please email the SLA back to the eMI team at [email protected].
The eMI WIKI eMI Training contains an eMI Glossary.
Process Activity Name: ESPRO-9 Verify Documentation Available for
MS 2 Review
Previous Process Activity
ESPRO-8 Provide Service Documentation
Next Process Activity
ESPRO-10 Confirm Technical Service Ownership
Description
The Project Manager verifies that all required documents are complete to support the Approved Service Build and checked into the Technical Services Project Repository (TSPR).
Artifacts Used
Acknowledgement of Service Acceptance Deployment Plan
Production Operations Manual Service Build (Approved) Service Documentation Service Test Plan
System Design Document System Security Plan Test Evaluation
Artifacts Created
Notification of MS 2 Service Readiness
Responsible Role
Project Manager
Tools and Websites
Agiliance RiskVision Enterprise Operations GRC Instance Agiliance RiskVision National Release GRC Instance CA LISA Service Virtualization
Enterprise Messaging Infrastructure (eMI) WIKI Home
IBM Rational Team Concert/Change and Configuration Management (RTC/CCM) Rational Software Architect
Service Registry Dashboard
Technical Services Project Repository (TSPR) VA EA ESS Center of Excellence
Wiley Introscope
Standards
None Listed
More Info
The Integrated Project Team identifies which additional documents are required for Program Management and Accountability System (PMAS) Milestone 2 Review.
Process Activity Name: ESPRO-10 Confirm Technical Service
Ownership
Previous Process Activity
ESPRO-9 Verify Documentation Available for MS 2 Review
Next Process Activity
ESPRO-11 Coordinate eMI Modifications as Needed
Description
The Project Manager ensures that a clear designation of technical service ownership occurs prior to the execution of the Deployment Plan for service sustainment. The Technical Service Owner information is updated in the Service Registry if needed.
Artifacts Used
Deployment Plan
Planned Upgrades to Enterprise Messaging Infrastructure Production Operations Manual
Service Description(s) Service Documentation Service Registry Entry
Artifacts Created
Appointment of Technical Service Owner Service Registry Entry (Updated)
Responsible Role
Project Manager
Agiliance RiskVision National Release GRC Instance CA LISA Service Virtualization
Enterprise Messaging Infrastructure (eMI) WIKI Home
IBM Rational Team Concert/Change and Configuration Management (RTC/CCM) Rational Software Architect
Service Registry Dashboard
Technical Services Project Repository (TSPR) VA EA ESS Center of Excellence
Wiley Introscope
Standards
None Listed
More Info
None Listed
Process Activity Name: ESPRO-11 Coordinate eMI Modifications as
Needed
Previous Process Activity
ESPRO-10 Confirm Technical Service Ownership
Next Process Activity
ESPRO-12 Confirm Service Deployment Readiness
Description
The Technical Service Owner coordinates with the Service Integrator to make Enterprise Messaging Infrastructure (eMI) configurations changes as specified in the planned updates. Software documentation is reviewed for configuration requirements. Any software is installed and tested in the eMI to ensure the planned upgrade is compatible and adequate for the Service.
Artifacts Used
Deployment Plan
Planned Upgrades to Enterprise Messaging Infrastructure Production Operations Manual
Service Description(s) Service Documentation
Artifacts Created
Responsible Role
Technical Service Owner
Tools and Websites
None Listed
Standards
None Listed
More Info
None Listed
Process Activity Name: ESPRO-12 Confirm Service Deployment
Readiness
Previous Process Activity
ESPRO-11 Coordinate eMI Modifications as Needed
Next Process Activity
ESPRO-13 Activate New Service
Description
The Project Manager ensures that the Service Documentation, System Security Plan, Production Operations Manual, Test Evaluation and Deployment Plan have undergone required reviews and verifies applicable items on the Deployment Plan have been executed. These actions confirm that the service is ready for activation in the production environment.
Artifacts Used
Deployment Plan
Production Operations Manual Service Documentation
Service Registry Entry System Security Plan Test Evaluation
Artifacts Created
Deployment Plan (Updated)
Responsible Role
Tools and Websites
Agiliance RiskVision Enterprise Operations GRC Instance Agiliance RiskVision National Release GRC Instance CA LISA Service Virtualization
Enterprise Messaging Infrastructure (eMI) WIKI Home
IBM Rational Team Concert/Change and Configuration Management (RTC/CCM) Rational Software Architect
Service Registry Dashboard
Technical Services Project Repository (TSPR) VA EA ESS Center of Excellence
Wiley Introscope
Standards
None Listed
More Info
None Listed
Process Activity Name: ESPRO-13 Activate New Service
Previous Process Activity
ESPRO-12 Confirm Service Deployment Readiness
Next Process Activity
ESPRO-14 Monitor Service Performance
Description
The Technical Service Owner confirms that all the necessary actions in the Service Activation Checklist have been completed, ensures the Service is running properly, and activates the new Service in the production environment using the configuration information from the Service Registry and the Service Deployment Architecture. The Technical Service Owner interacts with Service Integrator or Developer to resolve questions if needed and activates the new Service in the production environment. The Technical Service Owner sends an Activation Notice to the Enterprise Shared Service Center of Excellence, the Service Owner and other stakeholders. Versioning and Change Management are in effect.
Artifacts Used
Deployment Plan
Production Operations Manual Service Activation Checklist Service Deployment Architecture Service Documentation
Service Registry Entry System Security Plan Test Evaluation
Artifacts Created
Service Activation Notice
Service Registry Entry (Updated)
Responsible Role
Technical Service Owner
Tools and Websites
Agiliance RiskVision Enterprise Operations GRC Instance Agiliance RiskVision National Release GRC Instance CA LISA Service Virtualization
Enterprise Messaging Infrastructure (eMI) WIKI Home
IBM Rational Team Concert/Change and Configuration Management (RTC/CCM) Rational Software Architect
Service Registry Dashboard
Technical Services Project Repository (TSPR) VA EA ESS Center of Excellence
Wiley Introscope
Standards
None Listed
More Info
Process Activity Name: ESPRO-14 Monitor Service Performance
Previous Process Activity
ESPRO-13 Activate New Service
Next Process Activity
None
Description
The Technical Service Owner monitors the service performance to make sure that the service in production is up and running and maintains operations within permitted range of performance in accordance with the Enterprise Shared Service (ESS) Service Level Agreement and the
Enterprise Messaging Infrastructure (eMI) Service Level Agreement. Improvements to
Production Operations Manual are incorporated as needed. When the service performance falls outside of the permitted range of performance, corrective action is taken.
Artifacts Used
Production Operations Manual Service Level Agreement(s)
Artifacts Created
Production Operations Manual (Updated)
Responsible Role
Technical Service Owner
Tools and Websites
Agiliance RiskVision Enterprise Operations GRC Instance Agiliance RiskVision National Release GRC Instance CA LISA Service Virtualization
Enterprise Messaging Infrastructure (eMI) WIKI Home
IBM Rational Team Concert/Change and Configuration Management (RTC/CCM) Rational Software Architect
Service Registry Dashboard
Technical Services Project Repository (TSPR) VA EA ESS Center of Excellence
Standards
None Listed
More Info
None Listed