Pursuit brief: 2026-02 - 2026 Multifactor Authentication (MFA)
High-level requirements overview — if we go, turn this into a compliance matrix and pursuit plan.
| Field | Value |
|---|---|
| ID | 9293068107 |
| Buyer | Charter Township of Washington |
| Triage | review (76) |
| Abstract | BidNet |
Contacts
Vendor fit
Remote IT/software/design contractor — cloud, cybersecurity, integration, managed services, and design for public-sector buyers (any geography).
If we pursue
- Read primary source doc end-to-end
- Confirm remote vs onsite / partner needs
- Build compliance matrix from requirement checklist
- Draft timeline to due date (questions, submission format)
- Go / no-go decision with operator
Delivery signals
- Remote signal in docs:
remote - remote_signal: remote
- keywords_positive: software, cloud, cybersecurity, integration, help desk, IT
Submission & compliance signals
- Bids to receive consideration shall be received prior to the specified deadline time.
- All bids must be labeled RFP-2026-02 Multifactor Authentication (MFA).
- Bids must be sealed when submitted.
- Bids must be typewritten or printed in ink and legibly prepared.
- Bids must be received at the Township Clerk’s Office by the stated deadline.
- Any vendor who submits a bid and later claims it had no knowledge of any change, modifications or additions made by the Charter Township of Washington to the bid specifications, shall be bound by the bid, including any changes, modifications or additions made by the Charter Township of Washington to the bid specifications, and that vendor fails to accept the bid award, the Charter Township of Washington may pursue costs and expenses to re-bid the item from that vendor.
- Firm Prices - Once the Contract is awarded, the prices offered by the successful bidder shall remain firm for the duration of the contract.
- No oral statement of any person shall modify or otherwise change, or affect the terms, conditions or specifications stated in the resulting contract.
- Formal Change Management Process- Vendor shall implement a documented change management process.
- All changes to Township systems, configurations, or services shall be classified as: (a) Emergency Change — immediate action for active incidents; notify Township within one (1) hour, document within twenty-four (24) hours; (b) Standard Change — routine pre-approved low-risk changes; (c) Normal Change — all other changes requiring a written Change Request submitted to the Township's designated contact at least forty-eight (48) hours in advance, including scope, impact assessment, implementation window, and rollback plan.
- Vendor shall maintain a change log reviewed in monthly reporting.
- Implementation Plan —The successful vendor must prepare and submit a final implementation plan and timeline within fourteen (14) days of contract execution.
Source documents
Full parsed text — click to read.
- Municipal Multifactor Authentication (MFA).pdf (50,838 chars parsed)
Primary scope doc: Municipal Multifactor Authentication (MFA).pdf
Triage rationale
- document_parse (+12): 1 scope doc(s) parsed (pdf)
- remote_signal (+6): remote
- keywords_positive (+20): software, cloud, cybersecurity, integration, help desk, IT
- keywords_negative (-12): construction
Open gaps
- Due date not auto-extracted — verify in source PDF
Generated 2026-07-03T14:41:08.279Z · ms-scout bidnet-spec v1