Attachment 3 - DTC Process - How to Submit a Request to Move a Module to Sustainment.docx

ATTACHMENT 3 – How to Submit a Request to Move a Module to Sustainment How to Submit a Request to Move a Module to Sustainment Sustainment Stage Module Sustainment-Steady-State Definition Sustainment – Steady State refers to operating and maintaining completed IT solutions/services that have been deployed/adopted as Initial Operational Capability (IOC) to a production environment functioning as designed at the current capabilities and performance levels.

Steady State can include performing routine patches and fixes to meet continuous or recurring operational requirements without replacing existing IT solution/service resulting in no enhancement or modernization.

Application Management Team - Sustainment Phase Application Management Team - Sustainment Phase

1. Critical updates module testing

a. Release updates

b. Major releases (Spring, Summer, Winter)

i. Patches (Spring, Summer, Winter)

2. Security implications or remediations

3. Request for minor development, including bug fixes

a. Examples include but are not limited to

i. Picklist update

ii. Permission Set update

iii. Page Layout update

iv. List View update

v. Field Help Text update

vi. Email Template update

4. Release activities associated with module updates (#1-3)

a. Requirement gathering & analysis

b. Design and Document

c. Build

d. Release / Deploy to Production

i. DTC Architectural Approval

ii. DTC code review

iii. DTC quality assurance testing

iv. Conduct UAT with BO

v. Deploy to production via the DTC release process Module Sustainment Request In the Sustainment Entry Stage, development is complete, all components have been deployed to Production, the module is stable, user support documentation has been provided, a demo of the module has been provided to the DTC, automated testing suites have been provided (once enforcement begins), and the BO has signed off on functionality and user experience in Production. To enter sustainment, the SI must complete a Sustainment Transition with the DTC Sustainment Team.

· Please initiate the sustainment transition process at least two months before transition (last day of contractual SI development support).

· Initiate a Sustainment request by opening a Helpdesk Case

· Attach a completed SI Sustainment Readiness Self-Assessment Form

· In the Business Objective Section please indicate

· Request for transition to Sustainment

· Transition Date Details:

IMPORTANT: A module is only considered ready for DTC Sustainment if:

· All components have been deployed and it has been in production for at least 1 month with no significant changes planned.

· The module is stable; it contains

· NO critical bugs/defects

· No 508 compliance issues (non-COTS), or security defects

· End user support documentation has been created.

· A demo of the module has been provided to the DTC (Service Desk and Sustainment Team – one demo).

· Testing documentation has been created and ready to provide to DTC.

· The Business Owner has signed-off on functionality and user experience in Production.

Enhancement requests that do not meet the Sustainment Stage Criteria will require an OIT Market Place Product Request.

· Marketplace | DigitalVA

· VA approved SaaS and PaaS products – Request a product not found in the marketplace.

Complete and send the Sustainment Readiness Self-Assessment survey to DTC.SF.COE.Sustainment@va.gov. See attachments below:

· SI Sustainment Readiness Self-Assessment Form

· VA BO Module Stability Assessment Form Details:

To prevent transition delays, complete and return the assessments One month prior to entry to handoff.