DRAFT Attachment 0003 Task Definition Template.docx

DOCX document 67 KB Posted

Attached to
DA01--Microsoft EA Pricing and Alternatives
Solicitation number
36C10B24Q0114
Issued by

About this file

This document is a draft Task Definition Template for an Office of Information & Technology Enterprise Infrastructure Solutions Office (EISO) contract opportunity. The template outlines the objectives, scope, approach, deliverables, and VA responsibilities for the engagement.

The key details are:

  • The objectives are to enable new ways of working, focused on end-user needs and providing communication/collaboration tools to improve productivity and efficiency.
  • The scope includes project coordination, architectural guidance, and other technical support tasks to establish development, testing, and production Azure environments.
  • The approach is an iterative, agile development methodology based on the Scaled Agile Framework (SAFe).
  • Key deliverables include a project plan, vision scope document, architecture design, and input to VA's ESECC and ATO processes.
  • VA responsibilities cover areas such as project management, software licensing, data migration, integrations, testing, training, deployment, and the ATO process.
  • The period of performance is [insert] months from date of award.

View the file

Other files

File Type Posted
DRAFT Attachment 0002 Statement of Work Template.docx DOCX document
DRAFT Attachment 0001 Microsoft Core Professional Services and Support.xlsx XLSX spreadsheet
DRAFT Attachment 0004 Technology Refresh Product Details Template.xlsx XLSX spreadsheet
MICROSOFT PROFESSIONAL SERVICES and PM LANGUAGE EXCERPTS.docx DOCX document
36C10B24Q0114 0002.docx DOCX document
Microsoft RFI - Products by Domain Addendum.xlsx XLSX spreadsheet
36C10B24Q0114_1.docx DOCX document
36C10B24Q0114.docx DOCX document

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

ATTACHMENT 0003: TASK DEFINITION TEMPLATE

Office of Information & Technology Enterprise Infrastructure Solutions Office (EISO)

Table of Contents

1.0ENGAGEMENT OBJECTIVES AND SCOPE3
1.1OBJECTIVES3
1.2SCOPE OF THE ENGAGEMENT3
1.2.1TASK 1: PROJECT COORDINATION4
1.2.2TASK 2: ARCHITECTURAL GUIDANCE4
1.2.3TASK 3: EXAMPLE #35
1.3ASSUMPTIONS5
1.4AREAS OUT OF SCOPE6
2.0APPROACH AND SERVICE DELIVERABLES6
2.1APPROACH6
2.1.1MICROSOFT ENGAGEMENT BASELINES PLANNING ACTIVITIES7
2.1.2AGENCY ENGAGEMENT BASELINES PLANNING7
2.2DELIVERABLES8
3.0VA RESPONSIBILITIES8
3.1RESPONSIBILITIES8
3.1.1PROJECT MANAGEMENT AND GOVERNANCE8
3.1.2SOFTWARE SUBSCRIPTION, LICENSING, AND ENVIRONMENTS8
3.1.3DATA MIGRATION9
3.1.4INTEGRATIONS9
3.1.5TESTING9
3.1.6TRAINING9
3.1.7DEPLOYMENT AND SUPPORT9
3.1.8AUTHORITY TO OPERATE (ATO)10
4.0PROJECT COMPLETION10
4.1COMPLETION10
4.2PERIOD OF PERFORMANCE10
4.3SECURITY REQUIREMENTS10
4.4PROPOSED RESOURCES10

ENGAGEMENT OBJECTIVES AND SCOPE

OBJECTIVES

A brief description of the purpose of this task. See example below:

The Department of Veterans Affairs (VA) is enabling new ways of working, focused on the needs of end-users and providing the communication and collaboration tools needed to improve productivity and efficiency.

This Task Description details the services Microsoft shall provide to assist in meeting VA objectives for the Modern Workplace initiative by providing additional subject matter experts to provide technical support this engagement.

The activities include:

· Project Plan approved by VA Project Manager (PjM)

· Regular meetings with the VA Team to discuss the solution

· Assist in determining requirements and develop the vision scope document for review and approval

· Help determine the <app-name> Azure infrastructure architecture with input from the application owners and project managers to be documented in an architecture design document

· Provide input into VA established Enterprise Security External Change Council (ESECC) processes

· Provide input into VA established Authority to Operate (ATO) processes The objectives listed are for the sole purpose of providing business context for the project. Project scope is specified and limited to that which is stated in the section – Scope of the Engagement.

Furthermore, this Task Description (TD) provides details specific to the additional services desired by VA. Overarching scope, VA responsibilities and assumptions are detailed in the VA Core Services Enterprise Agreement (EA) Statement of Work (SOW) approved and executed at the time of award of the base contract.

SCOPE OF THE ENGAGEMENT

A brief description of the scope of this task including intended outcome and what measures will be used to evaluate successful outcomes. See example below:

Microsoft will provide subject matter specialists as defined in Proposed Resources section to support the VA application development team to envision, plan, build, stabilize, and deploy the necessary infrastructure to host <app-name>. This includes the establishment of development, testing, and production environments. For this engagement to be successful the <app-name> must be fully operational within the production environment and as outlined within the Project Completion Section.

The activities include:

•Regular meetings with the VA Team to discuss the solution where project plan shall be established and maintained with VA concurrence
•Determine requirements and develop the vision scope document for review and approval by VA PjM
•Determine the <app-name> Azure infrastructure architecture with input from the application owners and project managers to be documented in an architecture design document
•Provide input into VA established ESECC processes
•Provide input into VA established ATO processes

It is desired that all subtasks detailed under each task above shall be completed within the period of performance of this TD. However, due to the nature of agile development, VA may seek to re-prioritize In-Scope items listed based on additional or unforeseen scope which may arise from the Scaled Agile Framework (SAFe) process, and backlog developed during this period of performance, as described in the “Approach” section below. If such re-prioritization occurs and is agreed to by both parties, these changes shall be documented by Microsoft, and the re-prioritized in-scope tasks shall be supported per VA’s direction and in accordance with the contract. The Microsoft team will assist VA in determining the priority of the scoped and backlog, as described in the approach section below, allowing the most important activities to be prioritized by VA for completion during this task. Any changes to the prioritization shall be approved by VA in writing and documented in the Project Plan.

TASK 1: PROJECT COORDINATION

•Provide weekly status reports and project plan to report status on development, testing, staffing, issues, risks, and change control related to all tasks on this effort.
•Prepare and facilitate communications for development, training, and deployment activities to internal and external stakeholders.
•Support the program’s risk management process by aggregating risks, logging all risks and mitigation strategies into a centralized Risk Register, and meeting weekly to discuss them to determine if they should become elevated risks.
•Responsible for configuration management activities of assigned projects and interface with the activities of the other teams.

TASK 2: ARCHITECTURAL GUIDANCE

•Design and document the high-level solution architecture aligned with VA priorities and goals.
•Conduct application architecture review, as needed throughout the engagement, and provide recommendations to VA based on these reviews.
•Collaborate with VA stakeholders on milestone planning, identification of risks, and impact of changes on scope and effort.
•Recommend existing tools, processes, and solution components that the team can use from previous engagements.

TASK 3: EXAMPLE #3

[Add additional tasks as required]

ASSUMPTIONS

A brief description of the assumptions of scope of this task. See example below (edit as required):

Contractor Resources, Communications, and Logistics

•If necessary, Microsoft may make individual staffing changes throughout the period of performance. All changes shall be communicated to the VA Contracting Officer’s Representative (COR), Program Management Office (PMO) team, and VA Project PjM within 1 day of changes in accordance with section 6.5.1 Contractor Personnel Security Requirements of the contract.
•Microsoft will format project documents in Microsoft Office formats.

Software Versions and Capabilities

•This project will use [Product 1 and Version], [Product 2 and Version], and [Product 3 and Version]. Unless specifically identified as a part of this TD, all software and third-party extensions will not be used until VA obtains pricing information including a breakdown of total cost of ownership. Licenses shall not be used until VA approval is obtained and Contract Modification is processed.
•If DoD Standard 5015.2 is required for electronics record management, the solution may require a third-party extension or additional customization effort which will impact availability of hours for other project activities. VA will consider design alternatives for document storage that meets VA, National Archives and Records Administration (NARA), and Department of Defense (DoD) 5015.02 Joint Interoperability Test Command (JITC) standards for certified Records Management and compliance.

Integrations

•The project will use [Integration Layer Technology] to read and write data from [On-Premises System], which is installed and running at VA in all environments.
•The <app name> application can connect to [Integration Layer] (connections are allowed, are opened, and an authentication mechanism is in place to support programmatic calls into the integration layer and can receive information back from the integration layer).
•[Integration Layer] can connect to the <app name> application (connections are allowed, are opened, and an authentication mechanism is in place to support programmatic calls into the system and can receive information back from the system).
•The data center that hosts the integration processor will support the transaction processing load, the processing engine execution hosting, performance requirements, connection support, and issue resolution support.
•Microsoft’s resources can access machines and endpoints within the integration layer, necessary to develop, deploy, test, and monitor integration activities.
•All application integration points have an application programming interface (API) to read records.
•All application integration points that require data manipulation (changes) have an API to create and update records.
•A common data key will exist between all source systems, to locate records at runtime.

Training

•The project does not require formal training materials or formal training sessions.
•All training activities will be performed by the technical/development resources on the project and not by the official training resources.

Data Migration

• The project does not require data migration.

Environments, Infrastructure, Deployment, and Transition

• The VA Information Security Officer (ISO) will accept the existing ATO for Microsoft Azure Government (MAG) federal cloud environment for use on this project.

AREAS OUT OF SCOPE

A brief description of the areas out of scope of this task. See example below (edit as required):

Any area not explicitly included in the Scope of the Engagement section is out of scope for Microsoft during this project. Areas out of scope for this project are listed below.

•Code review of other vendors work products
•Modification of existing VA solutions
•Overarching project management, including use of other resources beyond the assigned Microsoft project team
•Management of non-Microsoft resources
•The VA PjM will assume responsibility for the management of all customer personnel and vendors.
•Sole responsibility of the ATO, ESECC or any VA process
•Development of execution of quality assurance plans, test plans or execution of test cases
•User Acceptance Testing (UAT) activities
•Training: Formal training of VA staff is not included.

APPROACH AND SERVICE DELIVERABLES

APPROACH

A brief description of the Approach for this task. See example below (edit as required):

As detailed in the overarching SOW agreed upon and executed at the time of award, Microsoft’s team is supplementary to VA’s technical staff for this engagement. Should changes be needed to the agreed upon staffing mix, VA will work with the Microsoft’s Project Manager to execute a Change Request, if required.

Microsoft shall supplement the VA’s technical staff for this engagement by providing guidance and assistance as directed by the VA COR, utilizing VA designated project methodologies. The VA COR, via the VA PjM will provide direction to the overall project team, of which Microsoft will be a part.

Microsoft shall undertake an iterative development approach that is based on the SAFe product delivery approach. The key tenets are as follows:

•Joint ownership of decisions and risks.
•Conduct transparent work defined in a shared, collaborative environment with clear definitions of done and success criteria.
•Development of program increment objectives that are specific, measurable, achievable, realistic, and time bound.
•Deliver working solutions through short implementation units. (iterations and program increments).
•Maintain a Continuous Delivery Pipeline (CDP) of Continuous Exploration (CE), Continuous Integration (CI), Continuous Deployment (CD), and Release on Demand (RoD), enabled using DevOps.
•Conduct regular retrospective meetings at each iteration that may be used for course correction.
•Assist VA with prioritization (or provide VA with tools/processes to prioritize) of business objectives in the program and/or portfolio backlog(s).

At the end of each iteration the VA PjM and Microsoft Enterprise Task Manager shall review the consumption against the total capacity to determine if adjustments need to be made through the change request process.

MICROSOFT ENGAGEMENT BASELINES PLANNING ACTIVITIES

•Create an initial list of non-functional requirements, such as performance and scalability need.
•Develop a recommended high-level technical architecture.
•Collaborate with the VA Product Owner to create a proposed scope for the first release, including a set of user stories that are ready for sizing, design, and development.
•Collaborate with VA to create a definition of done.

AGENCY ENGAGEMENT BASELINES PLANNING

•Attend and participate in the workshop sessions.
•Provide updated background information, documentation, and business requirements.
•Identify a product owner who is empowered to make business prioritization decisions and act as a single point of contact for requirements questions.
•Identify VA team members who will be available for the duration of the project.
•Clarify requirements as needed.

DELIVERABLES

In addition to the formal deliverables identified in the Product Description, any deliverables identified in this task description shall be considered accepted by VA if no comments are received from the VA PjM within 5 business days.

•Project Plan approved by VA PjM.
•Additional Artifacts based on tasks identified in Scope of the Engagement section including but not limited to milestone plan, backlog(s), vision scope document, training, risk register etc.
•Monthly Project Status will be provided as part of the Monthly CLIN 4 Professional Service Project Status Report.
•Each engagement shall have Closeout summary.

· Identify Points of Contact (POC’s) that must be off boarded.

· Ensure that VA PjM concurrence is obtained before closing out an engagement.

· Include license that need to go through the reclamation process.

· If there are under/over burns, please explain prior to closing out.

VA RESPONSIBILITIES

RESPONSIBILITIES

A brief description of VA’s responsibilities for this task. See example below (edit as required):

In addition to the VA activities defined in the Approach section, VA or designated third party is also required to provide the following:

PROJECT MANAGEMENT AND GOVERNANCE

•VA will manage the VA required documentation & software release processes and Microsoft will support the process.
•VA will provide a Product Owner for Agile development with sufficient availability and authority for the roles, to accept work products and set VA priorities for planned work.
•VA will provide access to functional subject matter experts to provide requirements, feedback, and to answer questions, on a timely basis. (within three business days or as mutually agreed-upon)
•VA will provide priorities for the backlog items related to perfective maintenance, upgrade, and optimization.
•VA will manage external dependencies and will facilitate interactions with related projects or programs.
•VA will prepare, schedule, and submit all artifacts required for Operations and Maintenance (O&M), and release approvals.

SOFTWARE SUBSCRIPTION, LICENSING, AND ENVIRONMENTS

•VA will provide, administer, and maintain stable performance and accessible environments.
•VA will procure all licensing for software and subscriptions required to run the solution, as determined by VA. See the Software Versions and Capabilities Section within the Assumptions for a list of items assumed to be required for this engagement.
•VA will implement all ESECC requests for connection to required servers and endpoints.

DATA MIGRATION

•VA will authorize and implement the agreed upon connections between the source and target systems and the data migration tool so data can be transported by Microsoft between the source application to the target application.
•VA will supply the hardware and software necessary to host data migration components

INTEGRATIONS

•VA will negotiate with and coordinate access to all application integration sources and solution providers for assistance with and access to resources required to implement the integrations.
•VA will authorize the connections and authentication required to connect systems requiring integration.

TESTING

•VA will identify and engage VA users to perform testing and to provide feedback on each iteration of features and functionality.
•VA will manage and assign priority, severity, and relationship linkages between all perfective maintenance tasks and support traceability between requirements, test cases, and defects.
•VA will coordinate testing, create test plans, and conduct UAT and Production Validation Testing (PVT) and all other testing activities.
•VA will create and make available test data needed for end-to-end testing for all environments.

TRAINING

•VA will provide training facilities for Train the Trainer (TTT) sessions and will reproduce training materials for participants as required.
•VA will identify and include all required participants in TTT sessions and will cover travel and expenses as required.
•VA will develop and deliver training to all end users for new components developed or updates to existing components.

DEPLOYMENT AND SUPPORT

•VA will manage and coordinate preparation of all required ATO documentation to include obtaining and incorporating required inputs from other (non-Contractor) organizations, including other contractors and VA organizations.
•VA will coordinate and manage all deployments. (through VA or the designated O&M contractor)
•VA will provide primary sustainment support of Production environment, including Tier 1 and Tier 2 support.
•VA will manage end user machine configuration and deploy client applications for solutions to all required workstations, as needed.

AUTHORITY TO OPERATE (ATO)

•VA will manage the ATO process and Enterprise Mission Assurance Support Service (eMASS)-related activities.
•VA will identify, mitigate, and resolve information assurance (IA) issues and concerns related to VA internal controls, as related to the ATO process.

PROJECT COMPLETION

COMPLETION

Microsoft will provide services defined in this TD to the extent of the credits available and the period of performance specified in the Optional Task. If additional services are required, the change management process will be followed, and the contract modified. The project will be considered complete when the following conditions has been met:

•All fees available have been utilized, and expenses incurred, for agreed upon services.
•The period of performance (Term) of the project has expired and the Optional Task has not been extended as outlined by this TD.
•All Microsoft activities and in-scope items, or agreed upon re-prioritized scope, have been completed.
•The Optional Task has been terminated.

PERIOD OF PERFORMANCE

The period of performance is [insert] (XX) months from date of award.

SECURITY REQUIREMENTS

VA will indicate if a position sensitivity designation or DoD cleared resource is required to staff and deliver against the scope of this Task Definition. A Contract Security Classification Specification or DD254 must be issued for tasks with such requirements.

PROPOSED RESOURCES

The Microsoft team will assist VA in reaching their Objectives by performing the activities listed above, under the direction of the VA COR via the OIT PjM. All work will continue through the period of performance or until all credits have been expended. Any requested changes to period of performance end dates must be proposed by the VA PjM and submitted to the COR for consideration by the Microsoft Team. If both parties agree with the change, a modification/amendment will be executed.

The table lists the proposed Stock Keeping Units (SKU) required to support a team for the period of performance.

Description
SKU
Quantity Required
Enterprise Task Manager (ETM)
VACR-00004
[X]
Enterprise Support Consultant (ESC)
VACR-00003
[X]
Design, Development, & Deployment Flex Credit (DDDC)
VACR-00005
[X]
Technical Assistance Flex Credit (TAC)
VACR-00006
[X]

Table 6: Sample Proposed SKUs Required

File details come from the government source that posted it. Updated .