FY25 DAAS SOW 10SEP25.pdf
PDF 147 KB Posted
- Attached to
- FY25 DAAS; Legislative Software Subscription
- Solicitation number
- FA701425Q0045
About this file
This Statement of Work (SOW) details a Congressional & Custom Data Subscription for the Secretary of the Air Force, Office of the Legislative Liaison (SAF/LL) and Secretary of the Air Force, Deputy Assistant Secretary for Congressional Budget and Appropriations Liaison (SAF/FML). The subscription requires a comprehensive software platform providing advanced legislative tracking, reporting, and engagement tools with extensive capabilities including real-time legislative event monitoring, social media tracking, committee hearing alerts, member of Congress profiles, voting records, email communication tools, meeting logging, and custom data mapping.
Key technical requirements include simultaneous online access for all users, personalized search and alert capabilities, AI-powered legislative analysis, full-text searchable databases spanning congressional activities, detailed member and committee profiles, integrated email outreach functionality, and mobile application access. The platform must enable users to create customized reports, track legislative actions, log interactions with congressional offices, and communicate the Department of the Air Force's impact across congressional districts. The solution must provide API connectivity, ensure data transferability, and maintain robust security protocols for handling government information.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Solicitation - FA701425Q0045.pdf | ||
| FAR 52 212 1 and 52 212 2 Addendum.pdf |
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
Contract #: TBD
Attachment: TBD
Statement of Work (SOW)
Congressional & Custom Data Subscription SAF/LL
10 September 2025
1.0 Description of Services
The Contractor shall provide timely access to legislative events via a subscription service that shall execute the requirements described below. These events include legislative action, social media monitoring, amendments, votes, derived analytics and possible congressional action that could have an impact on the military. The software shall also enable users to contact congressional offices, log engagements with elected officials and staff, and display the impact of the military in key congressional districts.
1.1 Scope
The Contractor shall provide a suite of public affairs tools via one continuous online product covered in this subscription service for the Secretary of the Air Force, Office of the Legislative Liaison (SAF/LL) and Secretary of the Air Force, Deputy Assistant Secretary for Congressional Budget and Appropriations Liaison (SAF/FML). The information must be readily available and include historic data and derived analytics for trending purposes. The Government will use the information to provide senior leadership with real-time information and recommendations while conducting business with members of Congress and their staffs. The scope of this requirement includes:
On-Site Training and Support Named Dedicated Vendor Account Manager Advanced Federal Legislative Tracking, Reporting and Notification Derived Legislative Analytics Robust Document and Social Media Tracking Integrated Email Tool Meeting Tracking Capabilities Custom Email Alerts Mobile Application Display of Custom Government Data One-pager ‘Leave Behinds’ Customizable Data Mapping.
2.0 Capabilities Requirements
Provide the Government access to a comprehensive database system of federal legislative information and include the ability to track legislation and social media, analytics on legislators, contact information for legislative staff, and outreach tools to log meetings with legislators in addition to email capabilities for sending mass emails. The “System” shall consist of baseline data, derived analytics, official contact information, email tool, and custom contacts database. The System shall enable customized functionality, capability to store, display, and download reports.
This functionality shall include:
1. Simultaneous online access for all users in SAF/LL and SAF/FML, including on-site training and support as requested. Travel will not be charged.
2. The ability for all users to create and easily update personal search lists (i.e., bill numbers, laws, members, floor votes and committees).
Users must be able to use previously saved lists in creating e-mail alerts, voting and member reports, and for searching all available content, including global searches.
3. The ability for each user to create and update personally customized e-mail alerts so they receive new information pertinent to their areas of responsibility based on their delivery preferences, with same-day availability.
Alert options must include keyword searches supported by Boolean operators and assisted by AI suggested enhancements for bills, committees, subcommittees, member profiles, staffer profiles, externally uploaded contact profiles, committee documents, committee reports, regulatory documents, statements (press release, floor statement, House proxy letter, newsletters to constituents, letter, statements in committee hearings, statements from Presidential appearances), White House documents (executive order, White House press briefing, White House Proclamation, Presidential Nomination, White House statement, Presidential action, White House speech or remarks), social media posts (Twitter (X), Facebook, YouTube), GAO reports, CBO reports, CRS reports, and member actions.
Committee hearing alerts and analysis: The solution must provide real-time alerts for statements made in committee hearings, enabling users to access the specific point in the video and transcript where the statement occurred. Users must be able to associate statements with SAF/LL’s issues, categorize them into lists, take a stance, and generate reports as needed. The system must allow the full transcript of any hearing to be downloaded seamlessly. Additionally, the solution must ensure all non-classified hearings are available within one hour of being posted to Congress.gov, including the full transcript and an identification of all speakers. An AI-powered assistant must be available to provide immediate analysis of hearing content and answer user inquiries related to the proceedings. This capability ensures timely and actionable insights into legislative activities critical to SAF/LL's mission.
Alert options must include the ability to create, pause, and delete alerts by user.
Alert options must include the ability to change the frequency at which the alert is sent.
4. The solution must enable each user to upload notes, apply personalized tags, and securely store all historical notes for future reference across legislation, committees, and subcommittees. SAF/LL requires the ability to create custom and conditional fields to capture critical data specific to the type of note or engagement and allow the capture of specific DAF legislative data. These custom fields must integrate seamlessly with reporting functionalities, ensuring that all data is both searchable and readily accessible to support SAF/LL’s mission-critical activities.
5. The ability to track events around Washington, D.C., such as congressional hearings and other legislative actions on Capitol Hill.
Event listings must include dates, times, locations, agendas, contact information and witnesses (when applicable) with a searchable archive.
Must be able to receive alerts of hearings as provider has them in the database.
6. Detailed reports on floor activity and actions in the House of Representatives.
Must include text-searchable access to floor statements, updated every two hours as they are available from www.gpo.gov.
Must include the capability to build a report offering a summary of key legislation the Government is watching for the upcoming week, providing alerts for any major changes throughout the week.
Must include the ability to download all floor statements.
Must include access to legislation in the Contractor’s mobile application.
7. Detailed reports on floor activity and actions in the Senate.
Must include text-searchable access to floor statements, updated every two hours as they are available from www.gpo.gov.
Must include the capability to build a report offering a summary of key legislation the Government is watching for the upcoming week, providing alerts for any major changes throughout the week.
Must include the ability to download all floor statements.
Must include access to legislation in Contractor mobile application.
8. Access to all new and updated Congressional Research Service (CRS) Reports as they become available. CRS Reports must be full-text searchable, with e-mail alerts.
9. Library of Congress summaries of major legislation with updates available within two hours of www.congress.gov updating information.
Bill profiles must include synopsis of the bill, key timeline actions, text-searchable versions of every version of the bill, list of bill sponsors, and access to votes, amendments, and related legislation relevant to that bill.
The solution must provide bill profiles equipped with an AI chat assistant to deliver actionable analysis of legislation. This assistant must enable users to ask detailed questions about the legislation’s impact on existing statutes, potential implications for agencies, and other relevant considerations. Additionally, the AI assistant must support users in drafting synopses and emails related to the legislation, ensuring streamlined communication and enhanced operational efficiency for SAF/LL’s legislative activities.
Bills must be archived dating back to the 104th Congress.
10. Access to comprehensive profiles for every current member of Congress.
Each profile must include a robust biography with extensive personal and professional history, a quantitative data-centric biography curated by the Contractor, a qualitative provided by the member of Congress, and a section for the Government to upload their own biography.
Each profile must include the member’s staff contact information (office locations, titles, responsibilities, issue portfolio, e-mail addresses, and phone numbers), Twitter, Facebook, YouTube, newsletters to constituents, demographic data from their district, voting and electoral histories, committee assignments, derived analytics representing bills sponsored and cosponsored, floor votes, amendments offered, floor speeches and committee amendments offered.
Must provide detailed analytical analysis of strength of relationship with other members of the same body (Senate or House), sorted by issue and/or legislative session, and provide visualization of those relationships.
Must provide full district United States Census data for each members district including population 25 years and over, population 1 year and over, different house-in the U.S. or abroad, different house in the U.S., different county, workers 16 years and over, occupied housing units, owner-occupied units, occupied units paying rent, total population 25 to 34 years, total population 35 to 44 years, population 25 years and over, population 16 years and over, in labor force, total housing units, owner-occupied units, occupied units paying rent, and sub-categories: population (sex & age, race, race alone or in combination with one or more other races, Hispanic or Latino and race, relationship, marital status, fertility, grandparents), employment (employment status, industry, occupation, class of worker, commuting to work, veteran status), financial (income and benefits, percentage of families and people whose income is below the poverty level, school enrollment, educational attainment, health insurance coverage, disability status of the civilian noninstitutionalized civilian population, computers and internet use), residential (households by type, gross rent, gross rent as a percentage of household income GRAPI, value, mortgage status, selected characteristics, vehicles available, selected owner monthly costs SMOCS), ancestry (U.S. citizenship status, residence 1 year ago, ancestry, place of birth, year of entry, world region of birth of foreign born, language spoken at home).
Must provide the ability for users to build Government branded custom reports on members of Congress and their profile sections.
Must provide option to bulk-download profile reports.
Must provide access to profiles from Contractor mobile application.
Each profile must display all logged interactions with that member of Congress or corresponding staff.
Government must be able to add additional custom tags and notes to a member of Congress’ profile to denote important information about the member (e.g., supports an issue area or has stakeholders in district) and have the ability to use that data in actionable reports.
11. Detailed facts files on members of Congress.
Each file must include birth date, birthplace, education, minority, pronunciation guide, religion, spouse(s), name(s) or number of children, gender, photo directory, phone, room number, district office addresses, district phone number, website, e-mail addresses, committee memberships, caucus memberships, seniority, military veteran, next election date, district map(s), and updated congressional calendar.
12. A database of updated Committee and Subcommittee Rosters, which link to a detailed profile of each member of Congress.
Must include list of staff names, e-mail addresses, issue portfolio, and title on each committee and subcommittee.
Must include descriptions of jurisdiction for every committee and subcommittee.
Must include links between committees and relevant subcommittees.
Committee profiles must be accessible in Contractor mobile application.
13. A database providing status and chronology of every bill in Congress dating back to the 104th Congress.
Must include the ability to track all appropriation and authorization bills (e.g., the NDAA) for the coming year prior to introduction.
Capabilities must allow for e-mail alerts to be sent to users for same-day bill action based on keywords, bill number, committee, sponsors, cosponsors, chamber, legislative stage, and date introduced.
Legislative histories must include links to relevant information, such as amendment text, derived analytics, related social media posts, and government reports (e.g., Congressional Budget Office (CBO), Government Accountability Office (GAO) and CRS).
Must be able to manage legislative tracking with modern dashboards customized by issue area, keyword, region, and priority. Dashboards should be collaborative across Government accounts to stay on top of every bill impacting the Government organization.
Must include capability to access legislation in Contractor mobile application.
14. A searchable database, updated daily, with optional e-mail alerts, of every bill introduced in Congress. The database must include the ability to search by keywords, bill numbers, members, committees, sponsors, chamber, legislative stage, date introduced, bill version and date, appropriations bills, and fiscal year.
Government users must be able to run a report at any time that identifies the differences in language between bill text documents and compare the wording found in two versions of the same bill, in two different bills or in selected sections of any two versions of a bill.
A full-text searchable database, updated daily, with e-mail alerts, of every Committee Report must include the ability to search by keywords, bill numbers, committees, publication date, committee type (House, Senate, Joint & Conference), report number, appropriations bills, and fiscal year.
All tables and charts in Appropriation and Authorization Committee Reports must allow for full text searching and the ability to receive e-mail alerts on specific keywords.
Reports must also be available in PDF format and be downloadable.
15. A full-text searchable database, updated daily, with e-mail alerts, of every CRS Bill Digest (the official synopsis of legislation).
Must have the ability to search by keywords, bill numbers, members, publication date, title of the bill, sponsors, chamber, legislative stage, date introduced, appropriations bills, and fiscal year.
A full-text searchable database, updated daily, with e-mail alerts, of all votes.
The database must clearly outline how every member voted on the House and Senate floors and include a link to relevant legislation, the vote count and outcome including members who abstained.
Access to a tool that allows a user to compare any set of votes back to the 104th Congress, and any set of members in the House or Senate and assemble custom reports showing the positions of how members voted compared to each other and the party line.
Database will update every two hours.
16. Full-text of amendments introduced in Congress.
Must include a description of each amendment integrated with legislative history and markup coverage of the specific bill.
17. Committee transcripts, with e-mail alerts, of selected congressional hearings.
Transcript must be available within four (4) hours after conclusion of the committee hearing, with the expectation that selected committees will have a fully searchable streaming video coverage available within one hour of upload to Congress.gov.
Transcript must be full-text searchable.
18. Streaming transcripts of selected speeches, press conferences, think tank events, political debates, etc.
Database must be searchable, with e-mail alerts, by keyword.
Transcript must be full-text searchable.
Streaming congressional hearings (and recordings) must allow play-back and keyword searches to easily document and review topics of interest to the Government.
Software must have a built-in artificial intelligence (AI) feature to quickly analyze and summarize congressional hearings.
19. A comprehensive database of government documents, including press releases, floor statements, newsletters to constituents, "Dear Colleague" letters, letters to the administration, tweets, Facebook posts, YouTube videos, medium posts, White House press briefings, White House proclamations, Presidential memorandums, Presidential nominations, Statements of Administrative Policy, CBO and GAO documents, CRS reports, live transcripts, committee documents, and Executive Orders.
Database must be searchable with e-mail alerts, by keyword, bill number, member, subject, committee, subcommittee, document type, and issuing agency.
Documents must be accessible by Contractor mobile application.
20. Software should include an integrated email tool for outreach to members of Congress and their staff to communicate policy priorities, schedule meetings, and manage engagement with key stakeholders.
Must be able to keep key congressional offices up to date on the work the Government is doing by sending personalized, blast emails.
Emails must be able to appear as though they were sent through a Government inbox through email domain authentication.
Must be able to send plain text and HTML-style newsletter emails.
The solution must enable users to create, edit, and send mass emails or newsletters while ensuring each recipient receives a uniquely personalized email. The system must not rely on blind carbon copy (BCC) functionality but instead deliver each email as an individual message, maintaining the highest level of deliverability and ensuring personalized engagement, even when created through a single streamlined workflow.
Government users must be able to create list of staffers based on legislative history of the member of Congress, previous correspondence with that staffer, or based on custom fields created by the Government (e.g., “Champion”).
Must be able to regenerate emails for contacts who had a particular interaction with the email (i.e., did not open the initial email, did not respond to the initial email, did not click on links provided in the initial email, etc.).
Must be able to cc and bcc other contacts on email correspondence.
Must be able to schedule emails to deliver as required.
Must pull email correspondence into the profiles for members of Congress.
21. Software should include the capability to log Government team members’ meetings with members of Congress and staffers to preserve institutional knowledge, easily manage compliance reports, and measure your impact.
Must be able to add meeting information on behalf of other Government team members and senior leadership.
Must be able to add meeting notes from desktop and Contractor mobile application.
Must be able to access historic meeting notes from desktop and Contractor mobile application.
All notes must be text searchable by keyword, user, member of Congress, staffer, topic of meeting, date of meeting, or other custom fields pre-assigned by the Government.
22. Software should be able to map custom Department of the Air Force information to states and congressional districts to communicate the impact of the Government to key stakeholders on Capitol Hill.
Must be able to download custom data into downloadable profiles for members of Congress.
Custom data must be accessible via Contractor mobile application.
Must be able to include custom map of congressional districts of members, in relation to the state, and include major cities/landmarks as well as Department of the Air Force installations within the district
23. Software should be able to allow users to create and download customizable one pagers for both internal use and as ‘Leave Behinds’.
One pagers should allow information on legislators, voting records, legislation, staff contact listing etc. to be used.
One pagers should also allow users to incorporate legislative information that cannot be obtained from public sources as well as add the custom fields (information from paragraph 4 of this section); i.e. “Department of the Air Force Member priorities”, “Member’s Military interest” and “DAF Equities in District/State.
One pagers should be able to be branded with any official and approved Air Force logos and color schemes.
24. Software should be able to customize data using geographic and aggregate data mapping.
Geographic data shall use latitude and longitude information to create customized reports.
Aggregate data shall use statistical information to create customized reports.
25. Data stored on the software application should be easily transferrable electronically in a format that will work on other platforms.
Contractor shall provide an API connection for the purpose of enabling two-way communication with the Government internal platform endpoints.
All custom data created and collected by the Government that is stored on the software must be available via endpoints that can be accessed by an API connection.
26. Emergency Operations/Mission Essential Personnel.
Continuation of Essential Contractor Services During Crisis. All services in this SOW HAVE NOT been defined or designated as essential services for performance during crisis IAW DFARs 252.237-7023, “Continuation of Essential Contractor Services.”
27. Security Instructions and Conduct
Physical Security. The Contractor shall safeguard all Government property, documents and controlled forms provided for Contractor use and adhere to the Government property requirements contained in this contract. At the end of each work day, all Government facilities, equipment, and materials shall be secured by a Government POC. Contractors are not allowed to secure Government facilities, equipment, and materials.
Access Control. The Contractor shall establish and implement methods of ensuring that no building access instruments issued by the Government are lost, misplaced or used by unauthorized persons. Access codes shall not be shared with any person(s) outside the organization. The Contractor shall control access to all Government provided lock combinations to preclude unauthorized entry. The Contractor is not authorized to record lock combinations without written approval by the Government COR. Records with written combinations to authorized secure storage containers, secure storage rooms, or certified vaults, shall be marked and safeguarded at the highest classification level as the classified material maintained inside the approved containers.
Pass and Identification Items. The Contractor shall ensure the pass and identification items required for contract performance are obtained for employees and non-government owned vehicles.
Retrieving Identification Media. The Contractor shall retrieve all identification media, including vehicle passes, from employees who depart for any reason before the contract expires.
Communications Security (COMSEC). Contractors may require access to COMSEC information on Air Force installations. The Contractor shall not require a COMSEC account. Access shall be controlled by the sponsoring agency. Access to COMSEC material by personnel is restricted to US citizens holding final US Government clearances. Such information is not releasable to personnel holding only reciprocal clearances. If it is determined the Contractor is required to access COMSEC information, the necessary training information and courses shall be provided by the COR. The DD Form 254 shall give further instructions on safeguarding and managing COMSEC material.
Contractor professionalism. The contractor shall:
i. Present a professional appearance and maintain professional demeanor and conduct at all times.
ii. Conduct their work assignments IAW project schedules
iii. Function effectively and efficiently during extended periods of high pressure and stress.
iv. Function as an integral member of a team of highly trained professionals responsible for the safety and security of USAF personnel and resources.
Controlled Unclassified Information (CUI). All DoD CUI must be controlled until authorized for public release in accordance with DoD Instruction (DoDI) 5200.01. This regulation set policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding of CUI material.
Privacy Act. Work on this contract may require that personnel have access to information protected by the Privacy Act. Contractor personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations when handling such information.
Records. All custom records created by the Government and received by the Contractor in the performance of this contract shall be maintained and readily accessible. Records shall remain the property of the Government. All custom records created by the Government and received by the Contractor in the performance of this contract shall be erased / destroyed at the request of the Government. These records shall be made available at the request of the Government in accordance with paragraph 2.0 Item #26 of this document.
Inherently Governmental Functions. The Contractor shall not perform inherently Governmental functions as defined in the Federal Acquisition Regulation (FAR) Subpart 7.5 in relation to this PWS.
Ethics. The Contractor shall not employ any person who is an employee of the US Government if employing that person would create a conflict of interest.
Additionally, the Contractor shall not employ any person who is an employee of the Department of the Air Force, either military or civilian, unless such person seeks and receives approval according to DoDD 5500.07, Joint Ethics Regulation.
Non-Personal Services. The Government shall not supervise or task Contractor employees in any manner that generates actions of the nature of personal services, or that creates the perception of personal services. It is the responsibility of the Contractor to manage its employees directly and to guard against any actions that are of the nature of personal services or give the perception of personal services to the Government or to Government personnel. If the Contractor feels that any actions constitute, or are perceived to constitute personal services, it is the Contractor’s responsibility to notify the CO immediately. Non-personal Contractor services shall not be used to perform work of a policy/decision making or management nature.
File details come from the government source that posted it. Updated .