3/25/24 Weekly Status Report

 

Project Risk Analysis Status for Deliverables

As we enter in the 4th quarter of the FY, several deliverables are approaching their deadlines. Below is a risk based analysis of the Parchment deliverables and the current status of each deliverable.

 

at risk - The project has hit a serious roadblock(s), and no clear plan is in place to hit the date.

Some Risk - The project has hit a roadblock(s), but a plan is in place to finish on time.

On Track - The project is on track. Risks are understood and mitigation plans are in place.

Deliverable Item

Status

Deliverable Item

Status

2.3.4.1 Financial Aid Integration

at risk - based on college feedback, current plan may not work and may need to redesign solution.

2.3.4.5 CSU/UC Student Management

On Track

2.3.4.5 Preferred Name

On Track

2.3.4.2 Student Eligibility Checker

On Track

2.3.4.3 Refining Searches

Some Risk - CVC has not seen a demo of this yet and deliverable to end of July.

2.3.4.4 eTranscripts Reporting To Colleges

On Track

Product Project Risks

Item #

Severity Level

Escalated Y/N

Description/Risk

Owner

Mitigation Strategy

Next Step

Priority

JIRAs

Date

Item #

Severity Level

Escalated Y/N

Description/Risk

Owner

Mitigation Strategy

Next Step

Priority

JIRAs

Date

1.

Severe: Affects Financial Aid Integration

N

Financial Aid Pilot:

  • Issues with Workflow

  • Peoplesoft college dropped out of pilot

  • At CISOA, colleges expresses concerns about marker courses and how it will negatively affect the A&R process.

Parchment

  • We may need to deviate away from the original architecture that has been because of the pushback from colleges.

  • In process with Allan Hancock for the P2 Teaching College Implementations

  • CVC leadership is investigating a possible new path.

high

https://cvc-oei.atlassian.net/browse/BLQ-1015

3/28/24

2.

Moderate: Users Were Not Able to Authenticate to CVC via Proxy

 

Yes

 

 

On Friday, Dec 15th, all student attempts to authenticate to our platform via the proxy seem to be failing. No one was been able to sign in. We've seen 100% failure rate on all attempts from every user who has tried at every college since about 6 AM Friday morning.

CVC reached out to CCCTC support team but they didn’t seem to have any insight into what could be causing this as they have shared that no one else has reported any issues.

However, we kept receiving a 403 Forbidden error message when we try to connect to any college via the Proxy. This is impacting both production and pilot and began failing around the same time on Friday. Whenever a user selects any college where we would normally route them to the appropriate SSO page, we instead are getting this error.

CVC Exchange - Sign In - Powered by Quottly (select any college)

 

  • CVC and CCCTC

  • We escalated this to Mike Caruso at the CCCTC and he advised they were able to log in with no issues.

  • After further research, it looks like the CCCTC had some additional IP restrictions and our IP was possibly whitelisted.

  • This issue was resolved same day, but we are working with the CCCTC and Parchment to ensure this does not happen in the future.

  • CVC and Jason from Parchment are working to investigate to ensure this doesn't happen again in the future.

    Jason has provided the following update about next steps and continuing research with the CCCTC: “I've gotten some additional information on this, the net of which is that this part of our application isn't capable of being configured on a guaranteed static IP. There's work we can do to make it semi-static, meaning it still may change with some, but even so change of the outbound IP can happen for reasons outside our control. 

    A "more static IP" change is not something we can implement immediately, given the holidays and that such a change may impact other users.

    I can't speak to if this was also a risk in the Heroku infrastructure days or not, but I'm slightly concerned as in our current state, as this could happen again based on factors we can't really control.

    So, I have these questions for the Tech Center:

    • Is this a new practice? If so, can it be rescinded until we have time to ensure there's a lesser risk configuration on our side?

    • Can the Tech Center whitelist by fqdn, rather than by IP? On our end, this is the best solution because we can implement what we have in the rest of the platform, which ensures traffic will always be sourced from 

    egress.parchment.com even though the IP addresses assigned to that may change in a way we can't control.

    As an aside, we don't have great logging of this on our side, so normally we'd put a monitor in place that fires the moment we start seeing it. We're not in a position to do that yet.”

  • Mike Caruso advised the workaround is still in place, but what you described was an idea that was never implemented. We rolled back the security update that affected you guys and have not re-released it. Separately, we’re working on some stuff that will allow us to push it (and future updates) out to protect against bad web traffic without affecting our APIs.

  • CVC has added this to the 4.2.24 CRM meeting.

high

https://cvc-oei.atlassian.net/browse/BLQ-1041

3/28/24

3.

Severe: Will Affect All eTranscripts Sending Colleges Who Are on SaaS

Y

Manage The CCCTC/Ellucian SaaS Shared Application Staging Tables In Conjunction With The GLUE Data Model - SaaS Migration Process

Mike V.

For colleges who are either a SaaS client or migrating over to SaaS, the current Ellucian APIS will not support eTranscript CA sending infrastructure. This affects colleges that are already live with eTranscript sending through Parchment/XAP as well as the ones who are migrating.

  • Parchment submitted requirements to Ellucian.

  • Ellucian received and is actively looking into this and advise if this is configurable or if they need to do development.

high

https://cvc-oei.atlassian.net/browse/BLC-138

3/28/24


Weekly Project/Product Summary

Item #

Topic

Item Details: Weekly Activity/Decisions

Next Steps

Priority

Important Links & Documentation

Last Update Date

Item #

Topic

Item Details: Weekly Activity/Decisions

Next Steps

Priority

Important Links & Documentation

Last Update Date

1.

Weekly Combined Requirements Meeting Notes & Recordings

  • We meet every Tuesday to discuss items that need attention, analysis, escalated, or enhanced. All recordings, notes, and next steps can be found on the running combined requirements meeting agenda.

  • Next meeting is 4.2.24

high

https://docs.google.com/document/d/1S3zLxqu6CLDmIO6Eq1YmOlo-gPG_Hwn6-lyaEiTpkQE/edit

3/28/24

2.

Canvas Solution for ILP Colleges

  • Database access to ILP team today

  • Test environment is not updated for Kern, so will work to get this updated.

  • Development will be done by 12/19/23.

  • No new updates this week.

high

 

3/28/24

3.

Parchment Weekly Sprint Jira Status Updates

Lane 1: Major Functional and Implementation Blockers

  • Financial Aid Integration Workflow BLQ-1015 - Moving forward with Copper Mountain College and Allan Hancock College as meetings are scheduled. Will update if there are any new blockers. 

  • System time zone for CVC Test and Prod sites PICE-537 - Parchment team to review and find solution in coming weeks.  

Lane 2: Renewal Enhancements

  • Financial Aid implementations  - Allan Hancock KO meeting was on 3/4/2024. Copper Mountain meeting scheduled for 4/1/24. Next steps to be determined as AHC is available.   

  • Document search result output sorting methods BLQ-979 & BLQ-1008 - Questions regarding whether this will be elastic search or something similar have been raised. CVC is hoping for a demo of the planned changes during the week of April 15th to prepare for a meeting on April 26, 2024. 

  • Student Eligibility Checker - Parchment testing in the Banner sandbox. 

    • BLN-729 N2N To Create API Specs, Place on Conf, And Send To Parchment

    • BLN-745 Parchment To Develop Feature Flag To Enable College Rollout Enablement

    • BLN-746 Parchment To Develop Progress Bar

    • BLN-748 Parchment To Develop Ability To Consume eligibilityStatus = and eligibilityStatusReason =

    • BLN-837 Parchment to Add/Display CVC Provided URL To Student Ineligible Page

Lane 3: Prioritized Enhancements and Research

  1. Add The Student's Teaching College SIS ID To Congratulations Page BLQ-1023 This has been moved to production. 

  2. Payment Status, Errors, and Reconciliation BLQ-724  - CVC has provided updated language, Parchment work pending.

  3. Add Additional Text To The Drop Email Notification BLQ-1031 - In the work queue.  

  4. Determine Method to Identify Students Who Exist in the Teaching College Canvas Instance BLQ-572 - In progress. CVC to provide language to be displayed to students when a duplicate canvas account is created.

  5. Parchment to Analyze and Provide Results for Expected APIs and Final States BLQ-1067 - Ongoing, goal to have completed by end of this week.  (This is also related to Complete application/integration diagram - BLQ-673 Diagram to be shared with CVC when available.)

  6. Session Management Changes BLQ-1026 and  UI Changes for Open Registration Dates and Inventory Imports BLQ-967 - No change. 

  7. Course Audit Needs to Still Run if the Student Dropped BLQ-1056 - This has been moved into the in progress queue for the Parchment team. 

  8. Need Address Validation on the AER Form BLQ-1029 - Next steps to be determined. 

  9. Prevention Solution/Future Proofing For Issue That Occurred Where Users Were Not Able to Authenticate to CVC via Proxy BLQ-1041 - Mike believes we need to reconnect to finalize a permanent solution between Parchment and the Tech Center. Next steps TBD.  

  10. Change The Text and Adjust The Layout in the Home California College Section on cvc.edu BLQ-1038 - This is still being discussed with the Parchment team. 

Parchment to Provide Technical Requirements for SaaS eTranscripts CompatibilityBLQ-1061- this has been provided to Ellucian. Next steps are TBD.

 

high

 

3/28/24

4.

eTranscript Implementations & Follow up with colleges

Below is the latest updates on where we are with each college:

  • Allan Hancock: 3.20.24: Met with the college and from a XAP and Parchment perspective, the infrastructure is in place and transcripts should be trickling in. Amanda requested a call to go over how the CVC unsolicited transcripts will work. Once they provide dates, I'll schedule a meeting.

  • Barstow 3.28.24: Met with Barstow and got their XAP communicator installed. Next steps is for Parchment to respond after they send over the pathways.

  • Cabrillo CCD - 3.5.24: Emailed Parchment back advising that we are blocked on moving forward with Cabrillo until we have a SaaS solution in place. I will keep them informed with updates.

  • Compton CCD - 3.25.24: Tynay sent an email and she is going to schedule the call for us on APril 4th from 1-2 PST. She will send out my zoom link in the invite for everyone to join.

  • Copper Mountain CCD (ECA) - 4.1.24: I sent them a follow up email on 3.27.24 to get a meeting on the books for May. no response so Amanda to follow up with them the week of April 22nd to get a calendar invite on the books.

  • College of the Desert CCD (ECA) 3.25.24: Florantine from the college responded that Sonia and Noelle need to reply to the the email thread when they complete their review of the XAP Communicator process and test files on each folders (//dccdsys/XAP).

  • Feather River CCD (ECA) -4.1.24: Sent flw up email for them to advise their availability on when we can meet.

  • Grossmont-Cuyamaca CCD (ECA) -3.21.24: Sent email to college asking for us to meet next week. Will follow on 4/4 if not response.

  • Marin CCD - 3.21.24: emailed Jon at the college and asked to set up a kickoff meeting to get this process started. No cohort established yet.

  • Merced CCD (ECA) 4.1.24: College and Parchment troubleshooting back and forth via email.

  • Napa Valley CCD - 3.5.24: Napa Valley reached out and advised they are ready to meet for next steps. Amanda scheduled meeting for April 3rd.

  • Porterville - Kern CCD: 3.25.25: College responded with this, "Marie will be leading this and will follow up." If no respond by 2nd week of April - Amanda to flw up."

  • Palo Verde CCD - 3.25.24: College emailed me back stating, " I currently use parchment for sending electronically, will this satisfy those requirements perhaps?" Amanda responded back that no, it wont meet the reqs. She asked that I send her some dates of availability. Amanda sent email with date and will schedule when she responds.

  • Peralta CCD (ECA) 3.25.24: College responded that she will provide my availability once she hears back from their IT department as to where we are with this project. She will be back in touch with you and your team within the next 2-weeks to setup a meeting.

  • Riverside CCD (ECA) 4.1.24 - Sent email to college and XAP to see if we need to meet to get the issues taken care of.

  • San Diego CCD (ECA) 3:25.24: Colleges responded and I sent out a calendar invite for April 2nd to meet to have the kickoff meeting with Parchment.

  • San Francisco CCD 3.25.24: The college emailed me back asking if they had to be a part of an active cohort to set up for sending. I emailed them back with the explanation.

  • San Joaquin Delta CCD (ECA) 3.25.24: College responded with I’m following up with Aubrey. Shawna needed to know how to get to the sample review and had asked Aubrey to assist. Not sure if that was successful." Will flw up with them end of first week of April if no response."

  • San Mateo County CCD - 3.21.24 - Sent email to demellon@smccd.edu to schedule meeting to do a kickoff call. No cohort established yet and they are not a home college.

  • Santa Monica CCD - 11.2.23 - Per Mike- hold off on reaching out.

  • Shasta-Tehama-Trinity Joint CCD (ECA) -3.18.24: Update from Parchment...Kevin Klemke, from Parchment let me know that he resent our test transcripts this morning. He noticed that our initial test files were still in the upload folder, and that the data was malformed. This has been corrected and new transcripts have been sent. The files from today will have overwritten the previously sent data. When you are able, please start the XAP communicator so that it can process these files. The hope is that they will process as expected and move into the success folder.

  • Sierra Joint CCD - 11.2.23- no cohort established, hold off on sending until then.

  • Siskiyou Joint CCD (ECA) 3.11.24: Received signed contract and sent to Sean. Emailed Sean and the college to ask if Sean sent test files yet/needs users set up for accts or password resets. Amanda to flw up on 3.14 if no response.

  • Solano CCD - 11.14.23 - Parchment sent email to Solano advising they need a status update. The college emailed us back stating: "Yes – our SaaS go-live date is April 8th, 2024. As noted by Amanda, I believe we have Parchment sending on pause until we have our integrations set up for SaaS. Our new timeline to become a “Teaching” College is to be part of the Fall 2024 Cohort. Once SaaS has been implemented with the given timeline, we can revist our setup for Parchment sending. I apologize if any of these plans have changed, as I am going off my previous meeting notes documented at the time. Parchment responded that they have canceled this project and will pick it back up when they are ready.

  • Victor Valley CCD (ECA) 9.16.23: Victor Valley is going to switch to SaaS in April 2024, so we will be placing this one on hold until after that migration.

  • West Hills - 4.1.24: Todd from Parchment emailed college to check on status/updates.

  • West Kern CCD (ECA) 2.19.24: Sent email to Kyle and asked how testing is going/see if they will be ready to go live this week or next.

  • West Valley-Mission CCD (ECA) 7.12.23 - Sent flw up email to college to check in on how things are progressing. They dont have a cohort established yet, so if no response follow up in end of Aug.

  • Yuba CCD (ECA) 3.4.24: Met to set up XAP communicator. Next steps is for them to set up process internally. Amanda to check in 3 weeks from now to check on progress.

 

 

  • Amanda and Sean to continue reaching out to colleges next week to continue getting them set up on sending and receiving.

high

In Process

Tracking HC and TC transcripts here: Teaching Colleges Sending Transcripts

https://cvc-oei.atlassian.net/wiki/spaces/CVCOEI/pages/1749647361

https://cvc-oei.atlassian.net/wiki/spaces/CVCOEI/pages/1731002371

Weekly Meeting Notes and Action Items will be here each week: https://drive.google.com/drive/folders/12_-PObf7ii0hgvV3g4S-EfWzUamAi8zd

Weekly Status Call Recordings Here: https://drive.google.com/drive/folders/1LF4RbCkYhAdKjPwhoEw2SdArlvo4-u9i

3/28/24

 

Active Production Issues

Q3 Sprint JIRAs- COMPLETED and CLOSED

Legend

Backlog = Prioritized, Development Not Started

in Progress = In Development/Status

In Testing = In Review or Testing

DONE = Finished/Closed

Low = Low Priority

medium = Medium Priority

High = High Priority

 

Jira, Description, and Status

Priority

Component

Date Started

Date Completed

Jira, Description, and Status

Priority

Component

Date Started

Date Completed

https://cvc-oei.atlassian.net/browse/BLC-129

High

idP/EPPN

4.27.23

4.1.24

https://cvc-oei.atlassian.net/browse/BLQ-972

High

Financial Aid Integration

6.8.23

1.23.24

https://cvc-oei.atlassian.net/browse/BLQ-855

High

Product Maintenance

1.18.23

1.18.24

https://cvc-oei.atlassian.net/browse/BLN-675

medium

Reverse Import

5.17.23

2.6.24

https://cvc-oei.atlassian.net/browse/BLN-664

medium

eTranscripts

3.2.23

1.23.24

https://cvc-oei.atlassian.net/browse/BLQ-977

 

Financial Aid Integration

6.12.23

3.14.24

https://cvc-oei.atlassian.net/browse/BLQ-713

high

Preferred Name

10/10/23

1.16.24

https://cvc-oei.atlassian.net/browse/BLN-683

high

Preferred Name

10/10/23

2/22/24

https://cvc-oei.atlassian.net/browse/BLN-771

high

Seat Counts

10/16/23

2/23/24

https://cvc-oei.atlassian.net/browse/BLN-730

high

Program Code

7/6/23

2.6.24

https://cvc-oei.atlassian.net/browse/BLQ-989

medium

Sync/Asynch

7.13.23

2.14.24

https://cvc-oei.atlassian.net/browse/BLQ-1037

medium

Admin Panel

11/28/23

1.4.24

https://cvc-oei.atlassian.net/browse/BLQ-1022

medium

Preferred Name

10/24/23

1.10.24

https://cvc-oei.atlassian.net/browse/BLN-803

medium

Sandbox

12/19/23

2/22/24

https://cvc-oei.atlassian.net/browse/BLN-686

high

Preferred Name

6.6.23

1.9.24

https://cvc-oei.atlassian.net/browse/BLQ-976

highest

Financial Aid

6.12.23

1.9.24

https://cvc-oei.atlassian.net/browse/BLQ-1028

high

Financial Aid

11.2.23

2.13.24

https://cvc-oei.atlassian.net/browse/BLQ-1017

medium

UI Language update

10/18/23

3.28.24

https://cvc-oei.atlassian.net/browse/BLQ-1033

medium

Seat Filter

11.9.23

3.1.24

https://cvc-oei.atlassian.net/browse/BLC-138

medium

eTranscripts SaaS

3.5.23

3.27.24

https://cvc-oei.atlassian.net/browse/BLN-846

medium

API

3.18.24

3.20.24

https://cvc-oei.atlassian.net/browse/BLQ-1071

highest

 

Search

3.15.24

3.25.24

https://cvc-oei.atlassian.net/browse/BLQ-1023

high

UI Updates

3.18.24

3.29.24

 

 

Q4 23/24 Sprint Priority JIRAs

Jira, Description, and Status

Priority

Component

Date Started

Date Completed

Jira, Description, and Status

Priority

Component

Date Started

Date Completed

https://cvc-oei.atlassian.net/browse/BLQ-1067

High

Analysis & Documentation

2.29.24

 

https://cvc-oei.atlassian.net/browse/BLQ-1026

High

Session Management

11.21.23

 

https://cvc-oei.atlassian.net/browse/BLQ-967

High

Session Management

11.21.23

 

https://cvc-oei.atlassian.net/browse/BLQ-1064

High

Financial Aid Integration

2.29.24

 

https://cvc-oei.atlassian.net/browse/BLQ-952

High

Financial Aid Integration

4.19.23

 

https://cvc-oei.atlassian.net/browse/BLQ-920

High

Financial Aid Integration

2.22.23

 

https://cvc-oei.atlassian.net/browse/BLQ-1061

High

SaaS

2.9.24

 

https://cvc-oei.atlassian.net/browse/BLQ-979

High

Search Engine

6.12.23

 

https://cvc-oei.atlassian.net/browse/BLQ-572

High

Canvas

2.13.24

 

https://cvc-oei.atlassian.net/browse/BLQ-1003

High

eTranscripts

9.12.23

 

https://cvc-oei.atlassian.net/browse/BLQ-1073

High

C-ID

3.21.24

 

https://cvc-oei.atlassian.net/browse/BLQ-1080

High

Drop Email Notifications

3.26.24

 

https://cvc-oei.atlassian.net/browse/BLQ-1002

High

eTranscripts

9.12.23

 

https://cvc-oei.atlassian.net/browse/BLQ-1010

High

Financial Aid Integration

9.14.23

 

https://cvc-oei.atlassian.net/browse/BLQ-673

High

Documentation

12.3.21

 

https://cvc-oei.atlassian.net/browse/BLQ-988

High

Admin Dashboard

7.12.23

 

https://cvc-oei.atlassian.net/browse/BLQ-1015

High

Financial Aid Integration

10.16.23

 

https://cvc-oei.atlassian.net/browse/BLQ-1029

High

Address Verification

11.2.23

 

https://cvc-oei.atlassian.net/browse/BLQ-724

High

Payment Processor

11.17.24

 

https://cvc-oei.atlassian.net/browse/BLQ-1056

High

Course Audit

2.6.24

 

https://cvc-oei.atlassian.net/browse/BLN-835

High

Program Code

2.27.24

 

https://cvc-oei.atlassian.net/browse/BLN-789

High

Term Activate

11.21.23

 

https://cvc-oei.atlassian.net/browse/BLN-280

High

Student Eligibility Checker

4.22.21

 

https://cvc-oei.atlassian.net/browse/BLN-845

High

API

4.14.24

 

https://cvc-oei.atlassian.net/browse/BLN-775

High

API Errors

11.8.23

 

https://cvc-oei.atlassian.net/browse/BLN-799

High

Search Match

11.28.23

 

https://cvc-oei.atlassian.net/browse/BLN-841

High

API

3.11.24

 

https://cvc-oei.atlassian.net/browse/BLN-848

medium

Research

3.26.24

 

https://cvc-oei.atlassian.net/browse/BLQ-991

medium

ASSIST

4.1.24

 

https://cvc-oei.atlassian.net/browse/BLQ-845

medium

Course Units & Seat Counts

7.25.22

 

https://cvc-oei.atlassian.net/browse/BLQ-1031

medium

Emails

11.6.23

 

https://cvc-oei.atlassian.net/browse/BLQ-1036

medium

UI Text Updates

11.21.23

 

https://cvc-oei.atlassian.net/browse/BLQ-286

low

Accessibility

2.2.24

 

https://cvc-oei.atlassian.net/browse/BLN-842

medium

Person Match

3.11.24

 

https://cvc-oei.atlassian.net/browse/BLN-739

medium

Documentation

8.14.23

 

https://cvc-oei.atlassian.net/browse/BLN-727

medium

Error Improvements

7.5.23

 

https://cvc-oei.atlassian.net/browse/BLC-139

High

Duplicate CCCIDs

2.20.24

 

https://cvc-oei.atlassian.net/browse/BLC-140

medium

CVC Website

2.29.24

 

 

Quarterly Dates

CVC Quarterly Dates

Parchment Quarterly Dates

N2N Quarterly Dates

CVC Quarterly Dates

Parchment Quarterly Dates

N2N Quarterly Dates

Q1: July 1-Sept 30

Q2: Oct 1-Dec 31

Q3: Jan 1-March 31

Q4: April 1-June 30

Q1: Jan 1-March 31

Q2: April 1-June 30

Q3: July 1-Sept 30

Q4: Oct 1-Dec 31

Q1: Jan 1-March 31

Q2: April 1-June 30

Q3: July 1-Sept 30

Q4: Oct 1-Dec 31