Appendix F Requirements.xlsx
XLSX spreadsheet 49 KB Posted
- Attached to
- Telephony Providers for Okta MFA via Inline Hook
- Solicitation number
- 2025-RFQQ-001
- Issued by
- Adams County, Asotin County, Benton County, Chelan County, Clallam County, Clark County, Columbia County, Cowlitz County, Douglas County, Ferry County, Franklin County, Garfield County, Grant County, Grays Harbor County, Island County, Jefferson County, King County, Kitsap County, Kittitas County, Klickitat County, Lewis County, Lincoln County, Mason County, Okanogan County, Pacific County, Pend Oreille County, Pierce County, San Juan County, Skagit County, Skamania County, Snohomish County, Spokane County, Stevens County, Thurston County, Wahkiakum County, Walla Walla County, Whatcom County, Whitman County, Yakima County, Asotin City, Clarkston City, Clarkston Heights-Vineland CDP, West Clarkston-Highland CDP, Benton City, Chelan City, Chelan Falls CDP, Clallam Bay CDP, Lewisville CDP, Rock Island City, Pacific Beach CDP, Whidbey Island Station CDP, Mercer Island City, Pacific City, Bainbridge Island City, Kingston CDP, Kitsap Lake CDP, Kittitas City, Klickitat CDP, Okanogan City, Anderson Island CDP, Fort Lewis CDP, Fox Island CDP, Herron Island CDP, Ketron Island CDP, North Fort Lewis CDP, Raft Island CDP, Stevenson City, Hat Island CDP, Lake Stevens City, Snohomish City, Spokane City, Spokane Valley City, Puget Island CDP, Garfield Town, Yakima City, Washington
About this file
I apologize, but the file you've referenced (Appendix F Requirements.xlsx) was not actually provided in the context. I can only see the State and Local Contract Opportunity description, which indicates the Washington State Board of Technical and Community Colleges (SBCTC) is seeking telephony service providers for Multi-Factor Authentication (MFA) integration with Okta via Inline Hooks. Without the actual Appendix F Requirements file contents, I cannot provide a comprehensive summary of its specific details. If you can share the contents of the Excel file, I would be happy to analyze and summarize it precisely.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| APPENDIX B Contract.doc | DOC document | |
| Preproposal Teleconference information.docx | DOCX document | |
| SBCTC 2025-RFQQ-001.doc | DOC 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
Bidder Instructions
| Response Instructions to Scored Requirements | ||
| This section of the RFP contains requirements for the solution desired by SBCTC. In responding to the requirements located in the spreadsheet tabs labeled, the following codes must be used, where applicable. | ||
| Please use the appropriate response code listed below in the "Code" column for each of the requirements. | ||
| Bidder must not alter, modify, insert or delete any part of the spreadsheets other than providing Bidder's response as per the instructions detailed below. Failure to comply may result in disqualification of the proposal. | ||
| Response to Requirement | Code | Definition and Criteria |
| Yes | Y | Functional capability exists (out-of-the-box). Requirement is installed and operational at other sites and can be demonstrated to SBCTC. |
| Configuration | C | Requirement will be met through changes to the existing solution using built-in tools to perform the specific function. |
Note: In the Comments column next to this response, indicate estimated level of complexity (Simple, Medium or Complex) Modification M Requirement will be met through changes to the source code which would require analysis and re-application during updates, upgrades, or when applying software patches.
Note: In the Comments column next to this response, indicate estimated level of complexity (Simple, Medium or Complex) Supplied by 3rd Party (Embedded) 3E Requirement is met or provided by third-party software package. License fees for this software are included in this proposal. Capability is fully embedded in and does not require maintenance of the integration with the core package. Functionality to meet this requirement is installed and operational at other sites and can be demonstrated to the organization.
Note: In the Comments column, indicate the name of the proposed third-party software package.
Supplied by Third Party (Non-Embedded) 3 Requirement is met or provided by third-party software package. License fees for this software are included in this proposal. Capability is “bolt-on” and will require maintenance of the integration with the core package as well as future updates, upgrades, or software patches to the 3rd party component. Functionality to meet this requirement is installed and operational at other sites and can be demonstrated to the organization.
Note: In the Comments column, indicate the name of the proposed third-party software package.
Future F Requirement will be met by the solution that is currently under development, in Beta test, or not yet released.
Note: In the Comments column next to this response, indicate the date when requirement will be available for implementation.
| No | N | Requirement will not be provided. |
| Note: | ||
| 1. An omitted response will be assumed to be the same as a response code of “N”. | ||
| 2. Any deviation from the response codes will be re-coded at the discretion of SBCTC. |
&14ERP Functional Requirements - Student Version &D
&9CONFIDENTIAL - For SBCTC Use Only &9Appendix A5 - Functional Requirements Student__Page &P of &N &9&A
Required Information
| Functional Requirements | ||||
| 5.1 | Required Integration Module | |||
| Level | Requirement | Code | Comment | |
| The selected vendor must support direct integration via Okta's Telephony Inline Hook functionality. (Reference: https://help.okta.com/oie/en-us/content/topics/telephony/telephony-inline-hook.htm) Specifically: | ||||
| 5.1.1 | M | Accept secure HTTP POST requests from Okta containing phoneNumber, message, and optional messageProfile | ||
| 5.1.2 | M | Respond within 3 seconds to avoid timeout behavior | ||
| 5.1.3 | M | Return structured JSON responses including a commands object indicating success/failure | ||
| 5.1.4 | M | Support HTTPS and preferably HMAC request signature validation | ||
| 5.1.5 | M | Enable logging and correlation ID tracing using the correlationId field | ||
| 5.1.6 | M | Design endpoints to be idempotent and retry-safe |
| 5.2 | Scope of Work | |||
| Code | Requirement | Code | Comment | |
| Proposal must contain a comprehensive description of how the proposed solution meets including the following requirements | ||||
| 5.2.1 | M | Provide reliable, scalable SMS and voice messaging services with global coverage | ||
| 5.2.2 | M | Fully support Okta Telephony Inline Hooks, including configuration via the Okta Admin Portal | ||
| 5.2.3 | M | Expose secure, performant API endpoints that comply with Okta’s inline hook request/response model | ||
| 5.2.4 | M | Allow for dynamic message customization, localization, and template management | ||
| 5.2.5 | M | Offer detailed delivery tracking, usage reporting, and real-time analytics | ||
| 5.2.6 | M | Provide clear, developer-friendly documentation and SDKs, with support for quick implementation | ||
| 5.2.7 | M | Maintain strong security and compliance posture, including TLS encryption, token or HMAC-based authentication, and adherence to standards such as GDPR, SOC 2, and CCPA |
| 5.3 | Technical Requirements | |||
| Code | Requirement | Code | Comment | |
| Proposal must contain a comprehensive description of how the proposed solution meets including the following requirements | ||||
| 5.3.1 | M | Okta Integration: Must support Okta Inline Hooks (custom API endpoint) | ||
| 5.3.2 | M | API Security: OAuth2/token or HMAC-based auth; TLS required | ||
| 5.3.3 | M | Delivery Reporting: Real-time delivery status, logs, error handling | ||
| 5.3.4 | M | Coverage: Global SMS and voice support across key regions | ||
| 5.3.5 | M | Compliance: GDPR, CCPA, SOC 2 (or equivalents) | ||
| 5.3.6 | M | Latency & Availability: <5s average delivery time, 99.9% uptime SLA | ||
| 5.3.7 | M | Scalability: Must support over 500,000 SMS messages per month and global voice delivery |
| 5.4 | Required Integration Module | |||
| Level | Requirement | Code | Comment | |
| Proposal must contain a comprehensive description of how the proposed solution meets including the following requirements | ||||
| 5,4,1 | M | Describe your solution's direct compatibility with Okta Telephony Inline Hooks, including configuration via the Okta Admin Portal | ||
| 5.4.2 | M | Explain your solution's reliability and global reach of SMS and voice message delivery | ||
| 5.4.3 | M | Describe your solution's strength and clarity of security posture and compliance certifications (e.g., GDPR, SOC 2, HIPAA if applicable) | ||
| 5.4.4 | M | Describe the quality and completeness of your developer documentation, SDKs, and implementation guidance | ||
| 5.4.5 | M | Provide your Service Level Agreements (SLAs), including uptime guarantees and support response times | ||
| 5.4.6 | M | Describe your implementation support and onboarding assistance. |
| 5.5 | Costs SMS | ||
| Code | Requirement | Comment | |
| Proposal must contain a clear response to the following pricing elements AND include all fees chargable | |||
| 5.5.1 | MS | SMS: Per-message rates by region or country | |
| 5.5.2 | MS | SMS: Volume discount tiers (500,000+ messages/month) | |
| 5.5.3 | MS | SMS: Setup or provisioning fees | |
| 5.5.4 | MS | SMS: Monthly minimums or platform access charges |
| 5.6 | Costs Voice | ||
| Code | Requirement | Comment | |
| Proposal must contain a clear response to the following pricing elements AND include all fees chargable | |||
| 5.6.1 | M | Voice: Per-call or per-minute pricing by region/country | |
| 5.6.2 | M | Voice: Setup/connection fees | |
| 5.6.3 | M | Voice: Volume-based pricing or bundled plans |
| 5.7 | Costs Billing | ||
| Code | Requirement | Comment | |
| Proposal must contain a clear response to the following pricing elements AND include all fees chargable | |||
| 5.7.1 | M | General: Billing frequency | |
| 5.7.2 | M | General: Included usage tiers or bundles | |
| 5.7.3 | M | General:Thresholds fro next tier | |
| 5.7.4 | M | General:Minimum spend commitments |
| 5.8 | Costs Other one time and on going fees | ||
| Code | Requirement | Comment | |
| Proposal must contain a clear response to the following pricing elements AND include all fees chargable | |||
| 5.8.1 | M | Other: Setup or onboarding fees | |
| 5.8.2 | M | Other: Platform access cost or account maintenance fees | |
| 5.8.3 | M | Other: Premium support or escalation charges | |
| 5.8.4 | M | Other: Dedicated account management costs | |
| 5.8.5 | M | Other: Early termination fees | |
| 5.8.6 | M | Other: usage-based billing |
File details come from the government source that posted it. Updated .