2026-10-19 Request for Information - CIC Software as Service Platform Services ATTACHMENT A

REQUEST FOR INFORMATION (RFI)Communications and Information Capabilities (CIC) BranchSecure Software-as-a-Service (SaaS) Data Platform Support Services

ATTACHMENT A – VENDOR COMPANY DATA

VENDOR COMPANY DATA

Company Name

Company Address

Company Website

Primary Point of Contact
Name:
Address:

E-mail:
Phone:
Secondary Point of Contact
Name:
Address:

E-mail:
Phone:
Unique Identity ID (from SAM.gov)

Cage Code

Registered in SAM (Required to be eligible for award of a federal contract.) Yes:
No:
Socio-Economic Status
(Check all that apply.)
Small Business:
Small Disadvantaged Business:
8(a) Business:
HUB Zone Business:
Service-Disabled Veteran-Owned Small Business:
Veteran-Owned Small Business:
Woman-Owned Small Business:
Large Business:
Manufacturer Status
Original Manufacturer:
Reseller:
GSA MAS Contract Number

NAICS

Additional Focus Instructions:
Vendors or Industry to provide the following:
Capability statementA description of the respondent’s SaaS data-platform and managed-support capabilities relevant to this requirement. Relevant experienceUp to three examples of comparable work, including scope, scale, outcomes, security/compliance environment, and lessons learned. Technical approachA recommended approach for implementation, operations, security, data integration, data governance, and user support. Security and compliance postureIdentify available authorizations, certifications, assessments, and ability to support DHS security authorization and continuous monitoring. Commercial modelDescribe licensing, subscription, consumption-based, managed-service, and implementation pricing models. Provide rough order-of-magnitude cost ranges if feasible. Staffing modelIdentify suggested labor categories, skill sets, staffing levels, onshore/offshore approach, and key personnel qualifications. Service-level recommendationsRecommend availability, support hours, incident response times, recovery objectives, and performance metrics. Data portability and transition approachDescribe how Government data can be exported in usable, non-proprietary formats and how transition-out would be supported. Risks and assumptionsIdentify key dependencies, risks, limitations, and Government decisions needed for successful implementation. Feedback on the draft SOW/PWS (Attachment B)Identify unclear, overly restrictive, missing, or commercially impractical requirements. Recommend revisions that would improve competition, reduce costs, or improve outcomes.