HE Sender - 180 Day Integration Implementation Plan - Project Plan Attachment C

Sep 12, 2026

Upload by Levi

180-day integration implementation project plan detailing task sequencing, estimated durations, and responsible roles for deploying an HE Sender solution. The plan covers project planning, technical documentation and resource assignment, configuration and service installation, SSO setup and testing, SIS integration functional analysis and package deployment, transcript parse workflow (input samples, parse template creation, review and approval), training coordination, and final launch activities. It includes notes that durations are estimates and tasks may run in parallel.

LanguageEnglish

CategoryPresentations

FormatPDF

Pages2

Reading Time1 min

AccessFree to download

HE Sender-180 Day Integration Implementation Plan

Project Planning

Configuration

Integration

Parse

Training

Launch

Attachment C Examples below are 180 day project plan. Please identify resources who will lead each high level task in the plan (Example roles have been provided) . More detail related to each high level task can be found in the scope document. 1. HE Sender-180 Day Integration Implementation Plan: | Task | Task Name | Duration* | Resources | | --- | --- | --- | --- | | | Docufide Sender-Electronic Transcript Project | 60 days | | | 1 | Project Planning | 7 days | | | 1.1 | Kickoff Meeting
• Introduction of Project Team
• Scope Overview
• Overview of Transcript Process & Discovery
• Timeline | 1 day | Parchment PM
Institution Team | | 1.2 | Provide Technical Documentation
• Installation Instructions
• SSO Setup Guide
• SFTP Setup Guide | 1 day | Parchment PM | | 1.3 | Assign Resources
• Business Owner
• Technical Owner | 1 Day | Institution PM | | 2 | Configuration | 35 days | | | 2.1 | Technical Overview
• Review Institution SIS configuration
• Recommend deployment options
• Provide technical details and documentation | 1 day | Parchment Technical Resource Institution Technical Resource | | 2.2 | Install and Configure Service
• Deployment Options vary per Institution
o Install Docufide Print Driver
o Configure SFTP Interface | 7 days | Institution Technical Resource | | 2.3 | Generate Samples for Review | | | | 2.3.1 | Generate sample transcript input (from Institution to Parchment) for Parchment testing | 3 days | Institution BA | | 2.3.2 | Provide Registrar Signature, Seal and Legend | 2 days | Institution BA | | 2.3.3 | Generate sample transcript output for Institution Review | 7 days | Parchment Technical Resource | | 2.4 | Deploy Single Sign-On (SSO)
• Configure SSO
• Test SSO | 7 days | Institution Technical Resource | | 2.5 | Testing and Validation | | | | 2.5.1 | Transcript Output Testing | 3 days | Parchment PM
Parchment Technical Resource Institution Team | | 2.5.2 | End-to-End Testing | 2 days | Parchment PM
Parchment Technical Resource Institution Team | | 3 | Integration | 56 days | | | 3.1 | Integration Kickoff Meeting | 1 days | Parchment PM
Parchment Technical Resource Parchment Integration Resource Institution Technical Team | | --- | --- | --- | --- | | 3.2 | SIS Integration Functional Analysis
• Identify gaps in standard integration package
• Develop plan to address gaps
• Assign resources to resolve gaps | 7 days | Parchment BA
Parchment Integration Resource Institution Technical Team | | 3.3 | Integration Package Sizing and Resource Allocation
• Identify resources required
• Allocate resources | 7 days | Parchment Integration Resource Institution Technical Team | | 3.4 | Integration Package Installation | 7 days | Parchment Integration Resource Institution Technical Team | | 3.5 | Integration Package Configuration | 21 days | Parchment Integration Resource | | 3.6 | Integration Package Testing
• End-To-End Testing
• Validation and Signoff | 7 days | Parchment Integration Resource Institution Technical Team | | 3.7 | Integration Package – Production Migration
• Install integration components in Production
• Migrate configuration settings to Production
• Validation and Signoff | 7 days | Parchment Integration Resource Institution Technical Team | | 4 | Parse | 42 days | | | 4.1 | Generate Transcript Samples For Parse Input | 7 days | Institution BA | | 4.2 | Generate Parse Template | 28 days | Parchment Parse Team | | 4.3 | Submit Parse Output for Review and Approval | 1 days | Parchment PM | | 4.4 | Approve Parse Template
• May Require Parse Template Revisions
• Multiple Review Cycles | 14 days | Institution PM
Parchment Parse Team | | 5 | Training | 7 days | | | 5.1 | Coordinate Administrative Training | 4 day | Parchment PM
Institution PM | | 5.2 | Provide Training Class | 1 day | Parchment PM | | 6 | Launch | 7 days | | | 6.1 | Project Launch Planning | 4 days | Parchment PM

FAQs

What are the main phases in the 180-day HE Sender integration plan?

The plan is organized into Project Planning, Configuration, Integration, Parse, Training, and Launch, each with estimated durations and defined responsibilities.

Who leads key high-level tasks according to the resources column?

Roles such as Parchment PM, Parchment Technical Resource, Institution PM, Institution Technical Resource, Institution BA, and Institution Team are assigned per task to cover technical, business, and institutional activities.

How does the plan handle SSO for the integration?

The Configuration phase includes deploying Single Sign-On by configuring SSO and testing it, followed by later validation and end-to-end testing in the testing and integration steps.

Sep 12, 2026

Upload by Levi