Read the full stored bill text
MURIELBOWSERMAYOR
May15,2025
Honorable PhilMendelson
Chairman
Councilofthe Districtof Columbia
John A. Wilson Building
1350 PennsylvaniaAvenue, NW, Suite504
Washington,DC 20004
Dear Chairman Mendelson:
Pursuantto section451 of the Districtof Columbia Home Rule Act (D.C. OfficialCode § 1-
204.51)and section202 of theProcurement PracticesReform Actof 2010 (D.C. OfficialCode §
2-352.02),enclosedforconsiderationand approvalby theCouncil of theDistrictof Columbia is
proposed ModificationNo. M0008 to ContractNo. CW90729 with Geographic Solutions,Inc.to
exerciseoptionyearfourintheamountof $3,547,451.The periodofperformance isfrom June 11,
2025 throughJune 10,2026.
Undertheproposedmodification,GeographicSolutions,Inc.willcontinuetoprovidethehosting.licensing,maintenanceandsupportfortheUnemploymentInsuranceBenefitsSystem.
My administrationisavailabletodiscussanyquestionsyoumayhaveregardingtheproposed
contractmodification.Inordertofacilitatearesponsetoanyquestionsyoumayhave,pleasehaveyourstaffcontactMareScott,ChiefOperatingOfficer,OfficeofContractingandProcurement,at(202)724-8759.
I look forwardtotheCouncil'sfavorableconsiderationof this contractmodification.
Sigcerely,
1
GOVERNMENT OF THE DISTRICT OF COLUMBIA
Office of Contracting and Procurement
Pursuant to section 202(c) of the Procurement Practices Reform Act of 2010, as amended, D.C.
Official Code § 2-352.02(c), the following contract summary is provided:
COUNCIL CONTRACT SUMMARY
(Option Year Contract)
(A) Contract Number: CW90729
Modification M0008
Proposed Contractor: Geographic Solutions, Inc.
Contract Amount: $3,547,451
Term of Contract: June 11, 2025 through June 10, 2026
(Option Year Four)
Type of Contract: Firm Fixed Price
(B) For a contract containing option periods, the contract amount for the base period and for
each option period. If the contract amount for one or more of the option periods differs from
the amount for the base period, provide an explanation of the reason for the difference:
Base Period Amount: $3,621,312
Council Approval: CA24-0132
Option Period One Amount: $5,823,417
Council Approval: CA24-0529
Option Period Two Amount: $4,136,962
Council Approval: CA24-0132 and CA24-0529
Option Period Three Amount: $3,106,639
Council Approval: CA25-0714
Option Period Four Amount: $3,547,451
Council Approval:
(C) A certification that the Citywide Clean Hands database indicates that the proposed contractor
is current with its District taxes. If the Citywide Clean Hands Database indicates that the
proposed contractor is not current with its District taxes, either: (1) a certification that the
2
contractor has worked out and is current with a payment schedule approved by the District;
or (2) a certification that the contractor will be current with its District taxes after the District
recovers any outstanding debt as provided under D.C. Official Code § 2-353.01(b):
The contractor is current with its District taxes according to the Clean Hands certification dated
April 9, 2025.
(D) A statement that the proposed contract is within the appropriated budget authority for the
agency for the fiscal year and is consistent with the financial plan and budget adopted in
accordance with D.C. Official Code §§ 47-392.01 and 47-392.02:
The Office of the Chief Financial Officer certified that there is available funding in the amount of
$3,547,451 in the operating budget for option year four, in accordance with D.C. Official Code §§
47-392.01 and 47-392.02.
1101 4th Street, SW
Washington, DC 20024
Date of Notice: April 9, 2025 L0014009353Notice Number:
FEIN: **-***7769
Case ID: 18559976
Government of the District of Columbia
Office of the Chief Financial Officer
Office of Tax and Revenue
GEOGRAPHIC SOLUTIONS, INC.
2570 CORAL LANDINGS BLVD
PALM HARBOR FL 34684-5123
Branch Chief, Collection and Enforcement Administration
Authorized By Melinda Jenkins
To validate this certificate, please visit MyTax.DC.gov. On the MyTax DC homepage, click the
“Validate a Certificate of Clean Hands” hyperlink under the Clean Hands section.
CERTIFICATE OF CLEAN HANDS
As reported in the Clean Hands system, the above referenced individual/entity has no outstanding
liability with the District of Columbia Office of Tax and Revenue or the Department of Employment
Services. As of the date above, the individual/entity has complied with DC Code § 47-2862, therefore
this Certificate of Clean Hands is issued.
TITLE 47. TAXATION, LICENSING, PERMITS, ASSESSMENTS, AND FEES
CHAPTER 28 GENERAL LICENSE
SUBCHAPTER II. CLEAN HANDS BEFORE RECEIVING A LICENSE OR PERMIT
D.C. CODE § 47-2862 (2006)
§ 47-2862 PROHIBITION AGAINST ISSUANCE OF LICENSE OR PERMIT
1101 4th Street SW, Suite W270, Washington, DC 20024/Phone: (202) 724-5045/MyTax.DC.gov
GOVERNMENT OF THE DISTRICT OF COLUMBIA
OFFICE OF THE CHIEF FINANCIAL OFFICER
GOVERNMENT OPERATIONS CLUSTER
DEPARTMENT OF EMPLOYMENT SERVICES
A
gency Fiscal Officer
M E M O R A N D U M
TO: Unique Morris‐Hughes
Director
FROM: Shilonda Wiggins
Agency F iscal Officer
DA
TE: May 7, 2025
SU
BJECT: FY 25 to 26 Funding Certification‐ Geographic Solutions
T
his is to certify that the Department of Employment Services’ (DOES) has funding within
the FY 25 Unemployment Insurance special purpose fund budget to support the service
contract with Geographic Solutions.
Th
e FY 25 certified amount is $1,182,483.67 and the FY 26 certified amount is
$2,364,967.33. The total certified amount is $3,547,451.00
F
Y 26 funding is contingent upon final approval of FY 26 proposed budget.
Cost
Center
Program Fund Award (If
applicable)
Award Description
(If applicable)
Amount
500180 50252 1060117 1,182,483.67
Total $1,182,483.67
Pl
ease contact me if you have any questions regarding this funding certification. I can be
reached via email at shilonda.wiggins@dc.gov.
4058 M
innesota Ave, NE | Suite 5700 | Washington, DC 20019
eFax: (202) 698‐5729
Shilonda Wiggins
Contract Number: CW90729
AMENDMENT OF SOLICITATION / MODIFICATION OF CONTRACT
1. Contract Number Page of Pages
CW90729 1 8
2. Amendment/Modification Number 3. Effective Date 4. Requisition/Purchase Request No. 5. Solicitation Caption
M0008 See Box 16c Unemployment Insurance
Benefits System
6. Issued by: Code 7. Administered by (If other than line 6)
Office of Contracting and Procurement
441 4th Street NW, Suite 700S
Washington, DC 20001
Department of Employment Services
4058 Minnesota Avenue N.E.
Washington, DC 20019
8. Name and Address of Contractor (No. street, city, county,
state and zip code)
Geographic Solutions Inc.
1001 Omaha Circle
Palm Harbor, Florida
9A. Amendment of Solicitation No.
9B. Dated (See Item 11)
X
10A. Modification of Contract/Order No.
CW90729
Code Facility 10B. Dated (See Item 13)
June 11, 2021
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers is extended. is not extended.
Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:
(a) By completing Items 8 and 15, and returning __________ copies of the amendment: (b) By acknowledging receipt of this amendment on each copy of the offer
subm
itted; or (c) BY separate letter or fax which includes a reference to the solicitation and amendment number. FAILURE OF YOUR ACKNOWLEDGMENT TO
BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION
OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such may be made by letter or fax, provided each letter or
telegram makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.
12. Accounting and Appropriation Data (If Required)
13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS,
IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14
A. This change order is issued pursuant to (Specify Authority): 27 DCMR, Chapter 36, Contract Modifications
The changes set forth in Item 14 are made in the contract/order no. in item 10A. X
B. The above numbered contract/order is modified to reflect the administrative changes (such as changes in paying office, appropriation data
etc.) set forth in item 14, pursuant to the authority of 27 DCMR, Chapter 36, Section 3601.3.
C. This supplemental agreement is entered into pursuant to authority of:
X D. Other (Specify type of modification and authority Option to extend
E. IMPORTANT: Contractor is not is required to sign this document.
14. Description of Amendment/Modification (Organized by UCF Section headings, including solicitation/contract subject matter where feasible.)
The contract CW90729 for the Unemployment Insurance Benefits System is hereby modified as follows:
1. Adde
d CLIN 4004 under section B.3.5 Option Year Four of the contract in the amount of $387,500 per
the Statement of Work (SOW) attachment A. This adjustment is based on an hourly rate of $155 and
requirement for 2500 hours. As a result of this change, the total price for option year four of the contract
revised from $3,159,951 to $3,547,451 by $387,500.
2. In a
ccordance with Section F, Option to Extend the Term of the Contract, the Government of District of
Columbia, Office of Contracting and Procurement, hereby exercises Option Year Four to extend the
term of the contract for the period of June 11, 2025, through June 10, 2026, in the total amount of
$3,547,451.
3. All o
ther terms and conditions remain the same.
Except as provided herein, all terms and conditions of the contract remain unchanged.
15A. Name and Title of Signer (Type or print) 16A. Name of Contracting Officer
Camille Christian
15B. Geographic Solutions, Inc.
(Signature of person authorized to sign)
15C. Date Signed 16B. District of Columbia
(Signature of Contracting Officer)
16C. Date Signed
Paul Toomey, President
05/06/2025
A
ttachment A
DC
DEPARTMENT OF EMPLOYMENT SERVICES
Office of Contracting and Procurement
Statement of Work for Contract Medication CW90729
Application Developer Services
1. Purpose
The Office of Contracting and Procurement, on behalf of the Department of Employment Services (DOES), Office of
Information Technology (OIT), is seeking a modification to contract CW90729.
T
he purpose of this modification is to develop value-added solutions that enhance or augment the functionality of the
Unemployment Insurance Benefits System (UIBS). These solutions will be developed pursuant to task orders issued under
a new CLIN, CLIN 2004.
T
hrough CLIN-2004, OIT will procure a GSI-furnished application developer who will develop software solutions
through Indefinite Delivery Indefinite Quantity (IDIQ) task order(s) at a labor rate of $155/hour.
T
he value of this contract modification is a minimum of 5 labor hours and a maximum of 2,500 labor hours.
Hours Rate Value
Minimum 5 $155.00 $775
Maximum 2,500 $155.00 $387,500
2. Scope of Work
C
LIN 2004 – Task Orders for Software Solutions
T
he contractor shall provide application development services to supplement, augment, or enhance the utility of
the UIBS.
Specific tasks shall include, but are not limited to:
• Developing solutions to streamline or automate system-generated notices and print jobs such as the
creation and printing of IRS 1099 tax forms.
• GSI Data Model Enhancement and Knowledge Transfer encompassing:
• Developing new reports and enhancing existing ones
• Providing direct query access to the GSI data warehouse for UIBS.
• Developing a staff resource to explain the GSI data structure and relationships that are of value
to the Office of Unemployment Compensation.
• Creating additional user-friendly reports for consumption by DOES staff.
• Modifying the Reemployment Services and Eligibility Assessment (RESEA) processes and related
communications.
• A project to align the National Directory of New Hires (NDNH) and State Directory of New Hires
(SDNH) crossmatch rules with the Department of Employment Services (DOES) Benefit Payment
Control (BPC) processes.
• Separating NDNH processes into two distinct crossmatches: New hire and quarterly wage
• Implementing different frequencies for each crossmatch type
• Establishing unique selection criteria for each crossmatch
• Creating differentiated issue codes based on crossmatch type
• Updating associated letters to reflect this change.
• Develop applications, middleware, or other utilities that integrate with the existing enterprise system via
database or API triggers.
• Implementing improvements to reduce manual labor and increase efficiency in various system
processes.
4. Contractor Responsibilities
4.1 Project Plan
The contractor shall:
• Review and analyze OPC’s submitted by DOES Staff.
• Develop and submit detailed project plans for each proposed solution, including:
• Estimated hours required for completion for each required delivery.
• Architecture Reference Diagram (as appropriate)
• List of the systems and resources that vendor will need OIT to provide access to.
4.2 Solution Development
Upon approval of a project plan, the contractor shall:
• Design and develop the proposed solution.
• Integrate the solution with the existing enterprise software or systems.
• Conduct thorough testing to ensure functionality and compatibility.
• Provide documentation for the developed solution.
• Implement the solution in coordination with the contract administrator and other DOES
personnel and support contractors.
4.3 Reporting and Communication
The contractor shall:
• Provide regular progress reports to the contract administrator.
• Attend scheduled meetings to discuss project status and any issues.
• Promptly communicate any challenges or risks that may impact project timelines or deliverables.
• Respond promptly to questions raised by project stakeholders.
4.4. Billing
The contractor shall create and submit monthly electronic invoices for each task order
through https://vendorportal.dc.gov/.
Invoices shall include the following details:
• The name of the project or projects being worked on.
• The list of milestones completed within the month includes the related deliverable that they are
tied to.
• The number of hours worked.
5. DOES Responsibilities
The contract administrator shall:
• Propose projects for development.
• Issue Task order bearing requirements and customer acceptance criteria to commission a project or
software solution.
• Review and approve or reject submitted project plans.
• Provide access to the application database or databases for development purposes.
• Provide access to the required systems and data.
• Oversee the contractor's work and pay properly laid invoices.
• Facilitate necessary coordination, access to systems and resources, and with other government
departments or stakeholders.
6. Deliverables
For each approved project, the contractor shall provide:
1. A project plan.
2. An application or software solution that is consistent with task order requirements.
3. Source code and technical documentation.
4. User manuals or guides, or technical descriptions.
6.1 Project Plan
The vendor shall furnish a project plan within 14 business days of task order issuance. The project plan will serve as a
roadmap for the task order development process. It will encompass all necessary components, including the project scope,
estimated timeline, required resources (systems and software), list of technical documents to be developed, and risk
assessment. The plan will clearly define vendor tasks and what it will need from OIT or other stakeholders to develop the
project.
• Risk Management: Identifies potential risks and includes mitigation strategies. The risk management plan shall
identify prospective systems and data sources that the vendor will need OIT to provide access to. The plan will
identify when that access is needed and the consequences if the deadline is missed.
• Milestones and Criteria: Includes clear, successful criteria for each task order deliverable (I.E. The Project Plan,
the Developed Application or Solution, Source Code, and Technical Documentation).
• The project plan shall include an estimated number of hours needed to fulfil deliverables for each approved
project.
• To aid in project plan development, the contract administrator shall organize a project orientation meeting within
5 business days of task order issuance to help explain project goals and expectations.
6.2 Project or Solution
The vendor will design and implement a software solution that is consistent with the requirements of each task order. The
final developed solutions shall:
• Functionality: Meets all specified requirements and solves the intended problem.
• Performance: Operates efficiently under expected load conditions.
• User Interface: user-friendly design
• Compatibility and Portability: Works across required platforms and integrates with existing systems or systems.
• Security: Implements appropriate security measures to protect data and access as appropriate.
• Reliability: Functions consistently without errors or crashes.
• Customizability: Allows for necessary customizations or user-selectable configurations.
6.3 Source Code
The vendor shall furnish source code that conforms to the following standards:
• Readability: Well-organized and easy to understand
• Documentation: Includes clear, comprehensive inline comments
• Modularity: Structured in a modular way for easy maintenance and updates
• Efficiency: Optimized for performance and resource usage
• Consistency: Follows consistent coding standards and best practices
• Error Handling: Implements error handling and logging
• Security: Free from common vulnerabilities and follows secure coding practices.
• Testability: Includes unit tests and is structured to facilitate testing
• Version Control: The vendor shall implement and properly manage version control of source code development.
6.4 Technical Documentation
For each task order, the vendor shall produce comprehensive technical documentation. The scope and nature of this
documentation will be subject to OIT approval during the project planning phase. As part of the project plan
submission, the vendor will provide a list of proposed technical documents deemed appropriate for the specific
project.
The vendor will be responsible for developing all technical documentation included in the approved project plan.
Technical Documentation shall conform to the standards below:
• Comprehensiveness: Covers all aspects of the system architecture and design or specific aspects of the system
architecture as appropriate.
• Clarity: Written in clear, concise language accessible to technical staff.
• Structure: Well-organized with a logical flow of information.
• Accuracy: Correctly reflects the current state of the application.
• Troubleshooting: Provides guidance for common issues and their resolution.
• Maintainability: Structured to be easily updated as the solution evolves.
• Consistency: Maintains consistent terminology and formatting throughout.
A nonexclusive list of potential technical documentation includes:
• Diagrams: If applicable, includes relevant system diagrams, flowcharts, data models, other visualization.
• API Documentation: If applicable, provides clear API documentation.
• Configuration Guide: If applicable, it includes set-up and configuration instructions.
• User Guide: If applicable, includes instruction for end users on how to utilize the developed solution.
• Other: As appropriate, the vendor shall develop other useful works or authorships that help technical staff use,
operate, modify or maintain vendor developed software solutions.
The standard for technical documentation shall be whether a person with ordinary skills or abilities in the art of
application development could understand how the application is structured and how it functions (I.E. sufficiently
documented so that an average application developer, not a genius, can understand how the application works end-to-end).
6.7 Deliverables Summary Chart
Deliverable Responsible Party Deliverable Due Date Delivery Method
Project Plan
Vendor Within 14 business days of task
order issuance Sent to CA via email
Project Orientation
Meeting
CA 5 business days of task order
issuance
Virtual Meeting (ex. MS
Teams)
Project or Solution
Vendor Due date proposed by vendor
through project plan and approved
by CA.
Sent to CA via email or
alternative electronic delivery
method approved by CA..
Source Code
Vendor Due date proposed by vendor
through project plan and approved
by CA.
Sent to CA via email or
alternative electronic delivery
method approved by CA.
Technical
Documentation
Vendor Due date proposed by vendor
through project plan and approved
by CA.
Sent to CA via email or
alternative electronic delivery
method approved by CA.
7. Period of Performance
The term of this modification shall commence on the date of the contract award and continue through {Option
Year Expiration Date}.
In the event that DOES exercises one or more option periods under Section F.2 to extend the term of CW90729,
this modification will remain in full force and effect for the duration of the exercised option period(s).
10. Property Rights
DOES shall retain, in perpetuity, the right to use, modify, maintain, or develop derivative solutions using the
source code and other resources developed under task order for any DOES purpose excluding commercial (I.E.
governmental, not commercial) purposes. In exchange for the above-mentioned right to use, modify or develop
derivative works, the vendor shall retain the intellectual property of source code developed under each project
task order.
11. Definitions:
11.1. Technology Stack: sometime referred to as a "tech stack" or "solution stack," is a comprehensive set of
software tools, programming languages, frameworks, and technologies used to develop and run a
specific software application. DOES tech stacks usually consist of a Front End, Back-end technologies
(usually proprietary technology developed under contract), databases, server infrastructure, APIs, and
sometime middleware.
11.2. Front-end: The part of a software application that interacts directly with users.
11.3. Back-end: The server-side of a software application, which processes data and performs operations not
visible to the end user.
11.4. Databases: A database is a structured collection of information stored electronically in a computer
system, designed for efficient access, management, and updating.
11.5. Middleware: is software that acts as an intermediary layer between different applications, systems, or
components, facilitating communication and data management.
11.6. Task order: A specific work assignment issued under a larger contract, detailing the work to be
performed and deliverables required.
11.7. Version control: A system that records changes to files over time so that specific versions can be
recalled later.
11.8. Application Programming Interface (API): is a set of protocols and tools for building software
applications that specify how software components should interact.
11.9. Project or Software Solution: is synonymous with task order. It encompasses a comprehensive
software solution designed to address a specific business or technical challenge. This solution includes
the four key deliverables outlined in the "Deliverables" section.
11.10. Composable Software: An architectural approach to software development where applications are
built from independent, interchangeable, and reusable components or modules. These components can
be rapidly assembled, disassembled, and reassembled to create new functionalities or applied to new
or different use cases.
DOES Terms and Acronyms:
11.11. DOES (Department of Employment Services): The government agency responsible for connecting
District residents, job seekers, and employers to opportunities and resources. The Office of
Unemployment Compensation is administered by DOES.
11.12. OIT (Office of Information Technology): The department within DOES responsible for managing
and maintaining its technological infrastructure and systems.
11.13. OUC (Office of Unemployment Compensation): The division within DOES that manages
unemployment insurance benefits.
11.14. OPFL (Office of Paid Family Leave): The division within DOES that administers the paid family
leave program.
11.15. National Directory of New Hires (NDNH): A national database containing employment and
unemployment insurance information.
11.16. State Directory of New Hires (SDNH): A state-level database containing information on newly hired
employees.
11.17. Benefit Payment Control (BPC): A unit or process within DOES that oversees and manages benefit
payments to prevent fraud and ensure accuracy.
11.18. Reemployment Services and Eligibility Assessment (RESEA): A program that provides
personalized reemployment services to unemployment insurance claimants.
11.19. Unemployment Insurance Benefits System (UIBS): The electronic system used by DOES to manage
and administer unemployment insurance benefits.
11.20. DOES Enterprise Systems: DOES enterprise systems refer to contractor developed technology
platforms, consisting of one or multiple technology stacks, that are used to administer the services
provided by DOES. Examples include:
• The D.C. Office of Unemployment Compensation (OUC) benefit system developed pursuant to
public contract CW90729.
• The Office of Paid Family Leave (OPFL) benefit system developed pursuant to public contract
CW76223.
• The Virtual OneStop System (VOS) – A Workforce management system developed pursuant to public
contract CW83797.
11.21. CLIN (Contract Line-Item Number): A specific line item in a contract that identifies a particular
product or service to be provided.
11.22. GSI (Geographic Solutions Inc.): The vendor providing software solutions for DOES's
unemployment and workforce systems.
11.23. Indefinite Delivery Indefinite Quantity (IDIQ): A type of contract that provides for an indefinite
quantity of supplies or services during a fixed period.
11.24. IRS 1099 tax forms: is a federal tax form used to report various incomes other than wages such as
benefit payments made by OUC and OPFL.