Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Receive "Authority to operate" (ATO) for Calfresh Confirm API #2276

Open
1 of 4 tasks
indexing opened this issue Aug 6, 2024 · 5 comments
Open
1 of 4 tasks

Receive "Authority to operate" (ATO) for Calfresh Confirm API #2276

indexing opened this issue Aug 6, 2024 · 5 comments
Assignees
Labels
deliverable Work that ends with a non-code deliverable (e.g. Google doc) product Issue captures work for the product team

Comments

@indexing
Copy link
Member

indexing commented Aug 6, 2024

The final aspect of the "path to go live" for low-income eligibility in the Benefits application is completing the contracting process with the CA DSS that grants us authority to operate and use the API in production. We've been in the final stages of this process since September of 2023.

I'm creating this issue now to capture official approval when contracting is complete.
cc// @jarrettkrumrei @johnatstate anirban sen @thekaveman

Acceptance Criteria

  • CDT completes the contracting process with CA DSS.

What is the definition of done?

  • CDT notifies the Benefits team contracting is complete.
  • The CalFresh Cardholders enrollment pathway is available in our test environment.
  • We can enable the The CalFresh Cardholders enrollment pathway in production for any agency using Benefits.
@indexing indexing added the deliverable Work that ends with a non-code deliverable (e.g. Google doc) label Aug 6, 2024
@indexing indexing self-assigned this Aug 6, 2024
@indexing indexing added product Issue captures work for the product team deliverable Work that ends with a non-code deliverable (e.g. Google doc) and removed deliverable Work that ends with a non-code deliverable (e.g. Google doc) labels Aug 7, 2024
@indexing
Copy link
Member Author

CDT team escalated this issue to its senior leadership in early August to work with senior leadership at the DSS to bring contracting to completion.

At our weekly check-in on Monday, 8/12, CDT reported contracting was not complete.
cc// @jarrettkrumrei @thekaveman

@indexing
Copy link
Member Author

At our weekly check-in on Monday, 8/21, CDT reported contracting was not complete.

@indexing
Copy link
Member Author

At our weekly check-in on Monday, 8/26, CDT reported contracting was not complete.

CDT and DSS leadership have established a deadline for resolution of contracting for Friday, August 30, 2024.

@thekaveman
Copy link
Member

At our weekly check-in on Monday, 9/9, CDT reported contracting was not complete.

@indexing
Copy link
Member Author

At our weekly check-in on Monday, 9/16, CDT reported contracting was not complete.

However, both CDT and DSS have agreed in principle to sign the now completed contract. CDT will sign first and is in the process of final contract reviews (legal, security, etc.) this week. We anticipate CDT will complete signing in the next couple days and, once complete, will send the contract to DSS for final review and signing. We hope this final step at the DSS proceeds quickly, but we don't have guidance on timeline.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deliverable Work that ends with a non-code deliverable (e.g. Google doc) product Issue captures work for the product team
Projects
Status: In progress
Development

No branches or pull requests

2 participants