11-Appendix J - Platform Integration Reference Sheet.docx

Request for Proposal (RFP) APPENDIX J — Platform Integration Reference Sheet

Version: 2.0 (Small Business Accessible) | Classification: UNCLASSIFIED | Date: March 27, 2026

Purpose & Scope This Appendix J provides a comprehensive reference for all platform integrations relevant to the AFI Translation Services contract. It documents compatible government platforms, video conferencing integrations, API references, and SSO compatibility requirements for all systems that the awarded Supplier may be required to interface with during contract performance.

This version of Appendix J has been structured to support small business participation. Integration requirements are tiered across three phases post-award so that qualified suppliers— including small, small disadvantaged, and 8(a) businesses — are not eliminated by infrastructure requirements that are not needed until later in the period of performance. Suppliers are evaluated on Day 1 requirements only at proposal submission; Phase 2 and Phase 3 capabilities are assessed through an Integration Milestone Review process.

Small Business Participation Notice This RFP is structured to maximize competition and is open to businesses of all sizes, including small, small disadvantaged, women-owned, veteran-owned, HUBZone, and 8(a) certified firms. No Supplier is expected to have all integrations operational at the time of proposal submission. Phased requirements exist to allow capable suppliers ramp time after contract award.

Teaming arrangements and subcontracting plans that leverage small business partners for technical integrations are encouraged and will be evaluated favorably under the Small Business Subcontracting Plan evaluation factor.

Integration Phase Definitions All integration requirements in this Appendix are tagged with one of the four phases below. Suppliers must confirm Day 1 requirements at proposal submission and demonstrate 90-Day requirements at the Integration Milestone Review (IMR-1) and 180-Day requirements at IMR-2.

Day 1 (Award) Required before contract performance begins. Supplier must demonstrate capability at proposal submission.

90-Day Post-Award Required within 90 calendar days of contract award. Acceptance testing with government IT team.

180-Day Post-Award Required within 180 calendar days of contract award. Full operational capability expected.

Optional / As-Needed Not required for contract performance. Activates only if the relevant agency tasks are issued.

Acceptable Interim Measures Where API integrations are not yet in place, the following interim approaches are acceptable during the phased ramp-up period:

• Secure file transfer via SFTP or encrypted email (for file exchange requirements)

• Manual data entry or spreadsheet reporting (for reporting/analytics requirements through Day 179)

• Email-based notification workflows (in place of webhook notification services)

• Web portal access in lieu of programmatic API access (where the platform permits) Suppliers must document all interim approaches in their Integration Plan and obtain COR written approval.

Section 1 — Compatible Government Platforms The platforms below represent the full universe of government systems relevant to this contract. Suppliers are only required to have SAM.gov, login.gov, and E-Verify access at the time of award — the three platforms every active federal contractor already uses. All remaining platforms are tiered by phase and are only required when corresponding task orders are issued or milestones are reached.

(Award) Required — standard for all federal contractors

(Award) Required — government-provisioned; no Supplier infrastructure needed

(Award) Required — web portal access sufficient; API optional

Post-Award Required if grants-related task orders are issued

Post-Award Government submits; Supplier provides data inputs only

Post-Award Account provisioned by agency; Supplier connects via SSO

Post-Award Read-only for Suppliers; no heavy integration required

Post-Award Low-effort; RSS/web access only

Post-Award Only if HHS task orders are awarded; agency assists with onboarding

Post-Award Only if DHS task orders are awarded

As-Needed Required only if DOD task orders are issued; DOD provides CAC enrollment support

As-Needed Required only if solicitation method requires eOffer submission

Notes

• Compatibility means the ability to exchange data, authenticate, and submit documentation — web portal access is acceptable where API access is not yet in place.

• DOD PIEE/WAWF and agency-specific portals are only required if DOD or agency-specific task orders are issued. The government will provide onboarding support.

• Suppliers must provide an Integration Milestone Plan (IMP) within 60 days of award covering all 90-Day and 180-Day platforms.

• FedRAMP-authorized integrations take precedence where agency-mandated systems overlap.

Section 2 — Video Conferencing Integrations The Supplier must support real-time interpretation across government-approved video conferencing platforms. At a minimum, suppliersmust demonstrate proficiency on Zoom for Government and Microsoft Teams GCC at proposal submission, as these are the two most widely used platforms across civilian agencies. Webex is required by 90 days post-award. Google Meet is optional and applies only to unclassified, low-sensitivity sessions.

Note: The government will provide platform access through government-provisioned accounts. Suppliers do not need to independently procure or maintain FedRAMP-authorized instances of these platforms.

(Award)

(Award)

Post-Award

Notes

• 'Full' = native simultaneous interpretation channels, language audio routing, and compliant session recording.

• 'Partial' = supplementary interpretation workflow required (e.g., relay interpretation); acceptable for low-complexity sessions.

• Google Meet (Partial) is acceptable for unclassified, low-sensitivity sessions only — no DOD or CUI content.

• The government will provision platform accounts; suppliersare responsible for interpreter training and certification on each platform.

• All session recordings with interpreted content are subject to applicable NARA retention schedules.

Section 3 — API Documentation Reference The APIs below define the technical integration framework for translation services delivery. Three core APIs are required at award — Translation Memory, Project Management, and File Exchange — as these directly support day-to-day task order execution. Machine Translation, Terminology, and QA APIs are required by 90 days. Reporting and Webhook services are required by 180 days or are optional.

Small business suppliers that use a commercial TMS platform (such as memoQ, XTM, Plunet, or equivalent) will generally satisfy Day 1 and 90-Day API requirements through their existing platform without custom development.

(Award) Core delivery — required at award

(Award) Core delivery — required at award

(Award) Required; SFTP alone acceptable at award

Post-Award MT optional at award; required by Day 90 if used

Post-Award TBX/XLIFF export sufficient at award

Post-Award Manual QA acceptable at award

Post-Award Spreadsheet reporting acceptable through Day 179

Recommended; email notification acceptable alternative

Notes

• API endpoints must use TLS 1.2+ minimum. FIPS 140-2 cryptographic modules are required for all systems processing CUI.

• For Day 1 requirements, suppliersmay submit API documentation from their existing TMS platform in lieu of custom-built APIs.

• API credentials must be rotated at least annually (quarterly rotation preferred but not required for small businesses at award).

• Sandbox/test environments for government acceptance testing must be available by IMR-1 (90-Day milestone).

• API activity logs must be retained for a minimum of three (3) years and provided to the government upon request.

• Rate limits, uptime targets, and DR provisions must be documented in the Integration Milestone Plan.

Section 4 — SSO Compatibility Matrix The following matrix identifies supported Identity Providers (IdPs). At a minimum, suppliers must support login.gov and Microsoft Azure AD (GCC) by Day 1, as these cover the majority of agency users. Additional IdPs are phased in based on agency-specific task order requirements. Government users will authenticate through government-provisioned accounts — suppliers are not required to procure or manage IdP infrastructure independently.

(Award)

(Award)

Post-Award

Post-Award

Post-Award

Post-Award

As-Needed

Notes

• ✓ = Fully supported | — = Not supported / Not applicable

• SCIM provisioning automates user lifecycle management; manual user provisioning is acceptable through the 180-Day milestone.

• PIV/CAC authentication is required only for systems handling CUI — standard MFA is sufficient for unclassified workflows.

• login.gov is the preferred IdP for public-facing government digital services per OMB M-19-17.

• SSO integration acceptance testing with the government IT team is required at IMR-1 for Day 1 IdPs.

• All IdP configurations must be documented in the System Security Plan (SSP) submitted with the Supplier's Authority to Operate (ATO) package.

Section 5 — Integration Performance Standards The following performance standards apply to all active integrations. Standards are tiered to reflect the ramp-up period and are calibrated to be achievable by small businesses without dedicated enterprise IT staff.

Small Business Flexibility Note Phase 1 standards are intentionally set at levels achievable by a small business using a commercial TMS platform with standard hosting.

Suppliers are not required to maintain dedicated 24/7 NOC staff or enterprise-grade monitoring infrastructure during Phase 1.

The government will work collaboratively with the contractor during the ramp-up period to resolve integration issues before escalating to formal cure notice procedures. The first 90 days are treated as an integration refinement period, not a performance period.

Section 6 — Supplier Attestation By submitting a proposal in response to this RFP, the Supplier attests to the following:

1. The Supplier has verified or will verify operational compatibility with all Day 1 platforms and APIs listed in this Appendix prior to contract award.

2. The Supplier will submit a draft Integration Milestone Plan (IMP) covering 90-Day and 180-Day requirements within 60 calendar days of contract award.

3. The Supplier will participate in Integration Milestone Reviews (IMR-1 at Day 90, IMR-2 at Day 180) with the government IT team.

4. All integrations will comply with applicable NIST SP 800-53 Rev. 5 controls for the contract's system security categorization.

5. The Supplier will not store government user credentials outside of the government-authorized Identity Provider.

6. Any integration failure impacting task order delivery will be reported to the COR per the applicable phase reporting standard.

7. Interim approaches (SFTP, manual workflows, portal access) are documented in the IMP and will be phased out per the agreed schedule.

END OF APPENDIX J — Platform Integration Reference Sheet (v2.0)

Questions regarding this Appendix should be directed to the Contracting Officer in writing prior to the proposal due date.

Controlled Distribution — Do Not Reproduce Without Authorization Page 1