Transportation Worker Identification Credential (TWIC

Request for Quotation and Qualification

RFQQ 2020 1215

for a

Transportation Worker Identification Credential

(TWIC) Validation System Replacement

by the Washington State

Department of Transportation

Release Date: December 15, 2020

Due Date and Time

January 18, 2021 at 2:00 PM

The RFQQ Coordinator is the SOLE POINT OF CONTACT at WSDOT for this procurement.

All communication between the bidding Proposers and WSDOT shall be with the RFQQ

Coordinator.

Timothy Carroll, RFQQ Coordinator

Phone: 360-705-7595

Email: [email protected]

mailto:[email protected]

i

Table of Contents

1. INTRODUCTION ............................................................................................................................................ 1

1.1. Background ..................................................................................................................... 1 1.2. Purpose ............................................................................................................................ 1

1.3. Acquisition Authority ..................................................................................................... 1 1.4. Contract Term ................................................................................................................. 2 1.5. Definitions....................................................................................................................... 2 1.6. Award .............................................................................................................................. 3 1.7. Types and Components of Contract ................................................................................ 3

1.8. Funding ........................................................................................................................... 3

2. SCHEDULE ...................................................................................................................................................... 4

3. ADMINISTRATIVE REQUIREMENTS ...................................................................................................... 5

3.1. RFQQ Coordinator (Proper Communication) ................................................................ 5

3.2. Vendor Questions............................................................................................................ 5 3.3. Vendor Comments Invited .............................................................................................. 5

3.4. Delivery of Responses .................................................................................................... 5 3.5. Response Contents .......................................................................................................... 6 3.6. Response Presentation and Format Requirements .......................................................... 7

3.7. Cost of Response Preparation ......................................................................................... 8 3.8. No Best and Final Offer .................................................................................................. 8

3.9. Response Property of WSDOT ....................................................................................... 8

3.10. Proprietary or Confidential Information ......................................................................... 8

3.11. Waive Minor Administrative Irregularities .................................................................... 9 3.12. Errors in Response .......................................................................................................... 9

3.13. Withdrawal of Response ................................................................................................. 9 3.14. Amendments/Addenda .................................................................................................... 9 3.15. Right to Cancel ............................................................................................................... 9

3.16. Selection of Apparently Successful Vendor ................................................................... 9

3.17. Contract Requirements.................................................................................................. 10 3.18. Contract Exception Log ................................................................................................ 10 3.19. No Costs or Charges ..................................................................................................... 10 3.20. Incorporation of Documents into Contract ................................................................... 11 3.21. Minority and Women Business Enterprise, Small Business, and Veteran Business

Participation .................................................................................................................. 11 3.22. No Obligation to Contract/Buy ..................................................................................... 11

3.23. Non-Endorsement and Publicity ................................................................................... 11 3.24. Optional Vendor Debriefing ......................................................................................... 11 3.25. Complaint, Debrief, and Protest Procedures ................................................................. 12 3.26. Wage Theft Prevention ................................................................................................. 12 3.27. Gifts............................................................................................................................... 12

3.28. Equal Employment Opportunity ................................................................................... 12 3.29. Title VI Notice to the Public ......................................................................................... 12 3.30. Public Disclosure .......................................................................................................... 13

ii

3.31. Federal Requirements ................................................................................................... 13

3.32. PCB Certification Requirements................................................................................... 13

4. VENDOR REQUIREMENTS ....................................................................................................................... 14

4.1. (M) Vendor Requirements ............................................................................................ 14

4.2. (M) Vendor Profile ....................................................................................................... 14 4.3. (M) Vendor Account Manager...................................................................................... 14 4.4. (M) Use of Subcontractors ............................................................................................ 14 4.5. (M) Prior Contract Performance ................................................................................... 14 4.6. (M) Insurance ................................................................................................................ 15

4.7. (M) Documentation ....................................................................................................... 15

5. EXPERIENCE AND SKILL QUALIFICATIONS ..................................................................................... 16

5.1. (MS) Client References................................................................................................. 16

6. TRANSPORTATION WORKER IDENTIFICATION CREDITATIONAL REQUIREMENTS ........ 17

6.1. Functional Design Specifications ................................................................................. 17

6.2. Optional Technical Requirements for Control Center Software ................................... 23

7. FINANCIAL QUOTE .................................................................................................................................... 29

7.1. Overview ....................................................................................................................... 29 7.2. Grounds for Disqualification ........................................................................................ 29

7.3. Taxes ............................................................................................................................. 29

7.4. (M) Presentation of All Cost Components.................................................................... 29

7.5. (M) Appendix D, Price List .......................................................................................... 29 7.6. (M) Price Protection ...................................................................................................... 30

7.7. (M) Price Decrease Guarantee ...................................................................................... 30 7.8. (M) Costs Not Specified ............................................................................................... 30

8. EVALUATION PROCESS ........................................................................................................................... 32

8.1. Overview ....................................................................................................................... 32 8.2. Administrative Screening.............................................................................................. 32

8.3. Mandatory Requirements .............................................................................................. 32 8.4. Allocation of Points ...................................................................................................... 32

8.5. Qualitative Review and Scoring ................................................................................... 32

8.6. Vendor Total Score ....................................................................................................... 33

8.7. Selection of Apparently Successful Vendor ................................................................. 33

iii

Appendices Appendix A Certifications and Assurances

Appendix B Proposed Contract

Appendix C OMWBE Participation Form

Appendix D Proposed Price List

Appendix E Contract Exception Log

Appendix F References

Appendix G Complaint, Debrief, Protest Process

Appendix H Wage Theft Prevention Certification

Appendix I Executive Order 18-03 - Worker's Rights Certification

Appendix J Specification Requirements

Appendix K PCB Certification

Appendix L SLA Requirements

Exhibit A Form FHWA 1273

Exhibit B Standard Form LLL

State of Washington Transportation Worker Identification Credential

(TWIC) validation system replacement

Department of Transportation 1 RFQQ 2020 1215

SECTION 1

1. INTRODUCTION

1.1 Background

Washington State Ferries (WSF) is seeking to procure an electronic Transportation Workers

Identification Credential (TWIC) access control system in compliance with 33CFR parts 101,

104 and 105 and the TWIC Final Rule regulating Risk Group A. The TWIC electronic

reader rule applies to almost all WSF’s terminals, but not our vessels. In WSF’s approved

ASP, the electronic checks would only apply to employees and authorized TWIC holding

vendors accessing restricted areas at the terminals.

Current Data Center Environment WSF currently runs a VMWARE virtual environment comprised of a minimum install of

Windows Server 2016 and MS SQL Server 2016. WSF’s PACs solution is hosted in this

virtual environment and running AMAG Symmetry Enterprise v9.

Current Terminal Environment

The current hardware environment at each terminal includes physical access to restricted

access spaces currently controlled by a card reader and keypad, electronic lock, intrusion

detector and request to exit. Cabling infrastructure to these locations is a BELDEN

658AFS cable, functionality of the ID/REX needs to be maintained.

Each terminal includes an electronic key control system manufactured by Key Systems

Inc. These Security Asset Managers (SAMs) are located in a NEMA rated stainless steel

enclosure manufactured by Hoffman currently secured by a physical lock and key.

Directly adjacent to these enclosures exists a fiberglass enclosure that can house the

TWIC reader if desired. The existing cable infrastructure to these enclosures includes a

CAT6 network cable and Belden 6545FE 6PR22 shielded cable.

Tahlequah terminal is an unmanned terminal with a free-standing roadside cabinet. This

stainless-steel cabinet has doors on either side and has a manual latch with a hasp and pad

lock. The doors each have intrusion detectors that are masked by an HID card reader

mounted to the side of the enclosure.

1.2 Purpose

Procure a replacement Transportation Worker Identification Credential (TWIC)

validation system to meet the Federal Transportation Security Administration (TSA) and

United States Coast Guard (USCG) regulation known as the TWIC Final Rule.

1.3 Acquisition Authority

Under the authority of RCW 39.26 of the Revised Code of Washington (RCW), as amended,

WSDOT issues this Request for Quotation and Qualifications (RFQQ) acting under the delegated

authority of the Department of Enterprise Services and consistent with the policies and standards

of the OCIO.




1.4 Contract Term

It is anticipated that the term of the resulting Contract will commence on the effective date of the

Contract, with all deliverables including Acceptance Testing completed by April 30, 2021. The

initial term of the Contact inclusive of a one year warranty will extend through April 30, 2022.

WSDOT, at its sole discretion, may initiate extending the Contract for up to four (4) one year

extensions.

1.5 Definitions

“Acceptable Alternative” shall mean a Vendor-proposed option that WSDOT considers

satisfactory in meeting a Mandatory requirement. WSDOT, at its sole discretion, will determine if

the proposed alternative meets the intent of the original Mandatory requirement.

“Apparently Successful Vendor” (ASV) shall mean the Vendor(s) who: (1) meets all the

requirements of this RFQQ, and (2) receives the highest number of total points.

“Business Days” or “Business Hours” shall mean Monday through Friday, 8 AM to 5 PM, local

time in Olympia, Washington, excluding Washington State holidays.

“Contract” shall mean the RFQQ, the Vendor Response, Contract documents, all schedules and

exhibits, and all amendments awarded pursuant to this RFQQ.

“Delivery Date” shall mean the date by which the ordered <Project Title> and supporting

services must be delivered.

“Desirable Scored” or “(DS)” shall mean the requirement is important but not mandatory, and

the Response will be scored.

“WSDOT” shall mean the Washington State Department of Transportation.

“License” shall mean the right to use the software.

“Mandatory” or “(M)” shall mean the Vendor must comply with the requirement, and the

Response will be evaluated on a pass/fail basis.

“Mandatory Scored” or “(MS)” shall mean the Vendor must comply with the requirement, and

the Response will be scored.

“Optional” shall mean the requirement is useful but not mandatory. The Response will not be

scored.

“Products” shall mean Software and/or Services as defined in this section.

“RCW” means the Revised Code of Washington.

“Response” shall mean the written proposal submitted by Vendor to WSDOT in accordance with

this RFQQ. The Response shall include all written material submitted by Vendor as of the date

set forth in the RFQQ schedule or as further requested by WSDOT.

“Services” may include both Professional Services and shall mean those Services provided by

Vendor relating to the solicitation, deployment, development and/or implementation activities

that are appropriate to the scope of this solicitation.

“Software” shall mean the object code version of computer programs Licensed pursuant to the

Contract. Software also means the source code version, where provided by Vendor. Embedded

code, firmware, internal code, microcode, and any other term referring to software residing in the

Equipment that is necessary for the proper operation of the Equipment is not included in this




definition of Software. Software includes all prior, current, and future versions of the Software

and all maintenance updates and error corrections.

“State” shall mean the state of Washington.

“Statement of Work” (SOW) shall mean the statement of work included in, or attached to, the

resulting Contract between Vendor and WSDOT for Vendor’s Software, and/or Services to be

accomplished under the terms and conditions of the resulting Contract.

“Subcontractor” shall mean one not in the employment of Vendor, who is performing all or part

of the Software, and/or Services under the resulting Contract under a separate contract with

Vendor. The term “Subcontractor” means Subcontractor(s) of any tier.

“Vendor” shall mean a company, organization, or entity submitting a Response to this RFQQ.

1.6 Award

Only one (1) ASV will be identified via this procurement. WSDOT intends to award

only one (1) Contract.

1.7 Types and Components of Contract

General

WSDOT may award one (1) contract to provide the TWIC replacement system described in this

RFQQ. Additional TWIC replacement system components that are appropriate to the scope of

this RFQQ, as determined by WSDOT, may be added to the resulting Contract by a written

amendment mutually agreed to and executed by both parties.

Statements of Work (SOW)

All services to be performed for a WSDOT under the Contract shall be documented in a

Statement of Work (SOW) established between the WSDOT and the Vendor. The SOW

will reference the Contract by number, describe the scope of work to be performed, and

the estimated total cost of the project.

1.8 Funding

Any contract awarded as a result of this procurement is contingent upon the availability of

funding.




SECTION 2

3. SCHEDULE

This RFQQ is being issued under the following Schedule. The Response deadlines are mandatory and

non-negotiable. Failure to meet any of the required deadlines will result in disqualification from

participation.

All times are local time, Olympia, WA.

WSDOT reserves the right to revise the above schedule.

Date of Issue December 15, 2020

Final Vendor Questions and

Comments due Period Ends December 23, 2020 2:00 PM PT

States Final Written Answers Issued January 4, 2021

Bids Due January 18, 2021 2:00 PM PT

Evaluation Period January 19 – January 26, 2021

Apparent Successful Bidder

Announced (Intent to Award) January 26, 2021

Debrief Request Period Ends January 29, 2021

Protest Period Ends February 10, 2021

Formal Award Announced and

Contract finalization begins February 11, 2021




SECTION 3

3. ADMINISTRATIVE REQUIREMENTS

3.1. RFQQ Coordinator (Proper Communication)

Upon release of this RFQQ, all Vendor communications concerning this solicitation must be

directed to the RFQQ Coordinator listed below. With the exception of the Office of Minority and

Women’s Business Enterprises, (reference Subsection 3.23), unauthorized contact regarding this

solicitation with other state employees involved with the solicitation may result in

disqualification. All oral communications will be considered unofficial and non-binding on the

State. Vendors should rely only on written statements issued by the RFQQ Coordinator.

Tim Carroll, RFQQ Coordinator

WSDOT Contract Services Office

7345 Linderson Way SW

Tumwater, WA 98501

PO Box 47408

Olympia, WA 98504-7408

Telephone: (360) 705-7595

E-mail:[email protected]

3.2. Vendor Questions

Vendor questions regarding this RFQQ will be allowed until the date and time specified in the

Schedule (Section 3). Vendor questions must be submitted in writing (e-mail preferred) to the

RFQQ Coordinator. An official written WSDOT response will be provided for Vendor questions

received by this deadline. Written responses to Vendor questions will be posted on the

Washington Electronic Business Solution (WEBS) website at https://fortress.wa.gov/ga/webscust/

.

The Vendor that submitted the questions will not be identified. Verbal responses to questions will

be considered unofficial and non-binding. Only written responses posted in WEBS will be

considered official and binding.

3.3. Vendor Comments Invited

Vendors are encouraged to review the mandatory requirements of this RFQQ carefully, and

submit any comments and recommendations to the RFQQ Coordinator. Where mandatory

requirements appear to prohibit or restrict your firm’s participation, an explanation of the issue

with suggested alternative language should be submitted in writing to the RFQQ Coordinator by

the deadline for Vendor Questions, Comments, and Complaints in the Schedule (Section 3).

3.4. Delivery of Responses

It is mandatory that Vendors submit all copies of their Responses by the date and time in Section

3, Schedule, to the RFQQ Coordinator at the address specified in RFQQ Coordinator (Section

3.1).

The RFQQ Coordinator in accordance with the Solicitation Schedule must receive the Response,

in its entirety. Responses are to be sent via e-mail unless the RFQQ Coordinator agrees upon in

advance and in writing other arrangements. Late Responses will not be accepted and will be


https://fortress.wa.gov/ga/webscust/




automatically disqualified from further consideration. The "receive date/time" posted by the

RFQQ Coordinator's e-mail system will be used as the official time stamp and may not be the

exact time. WSDOT assumes no responsibility for delays caused by network problems or any

other party.

3.5. Response Contents

The Response must contain information responding to all mandatory requirements in Section 3.5,

and must include the signature of an authorized Vendor representative, as required, on all

documents in the appendices.

The Response should be submitted in two (2) separate folders containing what is listed below.

This separation of documentation protects the integrity of the State’s evaluation process. No

mention of the cost response may be made in Folder 1.

Folder 1:

1. A Letter of Submittal, on official company letterhead, and signed by a person authorized to

bind your organization to a contract. The Letter of Submittal must include the following in

the order given:

a) Vendor legal name, address, name of authorized representative, phone number, and

email address,

b) Legal status (e.g., corporation, sole proprietor, etc.) and the year the entity was

organized to do business as the entity now substantially exists,

c) The names and titles of Vendor’s principal officers.

d) An organizational chart of the Vendor company

e) A brief description of its entity (including business locations, size, areas of

specialization and expertise, client base and any other pertinent information that

would aid an evaluator in formulating a determination about the stability and strength

of the entity), including the Vendor organization’s experience and history with the

solution being requested by WSDOT.

f) The name of the proposed Vendor Project Manager.

g) The lead time needed before work can begin after the formal award is announced.

h) A statement that the Vendor received the proposed contract (Appendix B).

i) If Vendor has no exceptions to the proposed contract (Appendix B) include a

statement that the Vendor does not have exceptions to the proposed contract

(Appendix B). If exceptions exist Vendor shall submit them using the Contract

Exception Log (Appendix E).

j) Provide Vendor Washington Uniform Business Identification (UBI) number. A UBI

number is a nine-digit number that registers the Vendor with several State agencies

and allows a vendor to do business in Washington State. Visit the Washington State

Department of Revenue’s website for more information on business registration

requirements.

http://dor.wa.gov/Content/DoingBusiness/RegisterMyBusiness/Default.asp

If Vendor does not have a UBI number, indicate in your response to this section as

follows: “<Vendor Name> confirms that it will register for a UBI number within ten

(10) Business Days of notification of being the Apparent Successful Vendor.”

http://dor.wa.gov/Content/DoingBusiness/RegisterMyBusiness/Default.aspx




k) Vendor must provide its Washington Statewide Vendor (SWV) number. If the

Vendor does not have a SWV at the time of response submittal then affirmatively

state that it will, within ten (10) Business Days of being notified as the ASV, register

with the Washington State Department of Enterprise Services as a SWV. For more

information related to obtaining an SWV number, visit the following website:

http://www.des.wa.gov/services/ContractingPurchasing/Business/VendorPay/Pages/d

efault.aspx

2. Response to Vendor Requirements (Section 4)

3. Response to Experience and Skill Requirements (Section 5)

4. Response to TWIC Requirements and Technology Requirements (Section 6)

Folder 2:

1. A copy of the Letter of Submittal

2. Financial Quote (Price List) (Section 7 and Appendix D)

3. Vendor’s signed and completed Certifications and Assurances (Appendix A)

4. Vendor’s exceptions and/or proposed revisions to the proposed contract (Appendix B)

5. Vendor’s Appendix I Executive Order 18-03 - Worker's Rights Certification

6. Vendor’s Appendix J, Specification Requirements

7. Vendor’s Federal Requirments Certification ( Section 3.31)

8. Vendor’s PCB Requirements Certification (Section 3.32)

Failure to provide any requested information in the prescribed format may result in

disqualification of the Vendor.

3.6. Response Presentation and Format Requirements

The following requirements are mandatory (M) in responding to this RFQQ. Failure to follow

these requirements may result in Vendor disqualification.

A. The signature block in Appendix A, Certifications and Assurances, must be signed by a

representative authorized to bind the company to the offer.

B. Vendor must respond to each question/requirement contained in Sections: 4, 5 and 6 of

this RFQQ, and complete the Price List, Appendix D. Failure to comply with any

applicable item may result in the Response being disqualified.

C. Each of the RFQQ requirements are numbered and titled. In each requirement title is a

designation indicating how the Response will be evaluated:

i. For Mandatory requirements (M), the Response must always indicate explicitly

whether or not the Vendor’s proposed solution meets the requirement. A

statement, “(Vendor Name) has read, understands, and fully complies with this

requirement” is acceptable, along with any additional information requested.

ii. For Mandatory Scored (MS) and Desirable Scored (DS) items, the Response

must always indicate explicitly whether or not the Vendor's proposed solution

meet the requirement, and describe how the proposed Vendor’s solution will

accomplish each requirement or are desirable as it relates to the service(s)

proposed.

http://www.des.wa.gov/services/ContractingPurchasing/Business/VendorPay/Pages/default.aspx

http://www.des.wa.gov/services/ContractingPurchasing/Business/VendorPay/Pages/default.aspx




iii. Items marked Optional will not be scored. Vendors must indicate explicitly

whether or not the Vendor's proposed solution meet the requirement, and

describe how the proposed Vendor’s solution will accomplish each requirement

or are desirable as it relates to the service(s) proposed.

D. Pages must be numbered consecutively within each section of the Response showing

Response section number and page number.

E. Figures and tables must be numbered and referenced in the text of the Response by that

number. Foldouts containing charts, spreadsheets, and oversize exhibits are permissible.

F. Response prices must be submitted using the Price List, Appendix D. Separate price

quotes attached to this document or submitted in some other form will not be accepted as

a valid Response.

G. The Response, as well as any reference materials presented by Vendor, must be written in

English and Vendor must provide all rates in United States dollars.

H. The Response must be in Word, Excel, or PDF. Other file formats may be accepted with

prior approval of the RFQQ Coordinator.

3.7. Cost of Response Preparation

WSDOT will not reimburse Vendors for any costs associated with preparing or presenting a

Response to this RFQQ.

3.8. No Best and Final Offer

WSDOT reserves the right to make an award without further discussion of the Response

submitted; i.e., there will be no best and final offer request. Therefore, the Response should be

submitted on the most favorable terms that Vendor intends to offer.

3.9. Response Property of WSDOT

All materials submitted in response to this solicitation become the property of WSDOT, unless

received after the deadline in which case the Response is returned to the sender. WSDOT has the

right to use any of the ideas presented in any material offered. Selection or rejection of a

Response does not affect this right.

3.10. Proprietary or Confidential Information

Any information contained in the Response that is proprietary or confidential must be clearly

designated. Marking of the entire Response or entire sections of the Response as proprietary or

confidential will not be accepted nor honored. WSDOT will not accept Responses where pricing

is marked proprietary or confidential, and the Response will be rejected.

To the extent consistent with chapter 42.17 RCW, the Public disclosure Act, WSDOT shall

maintain the confidentiality of Vendor’s information marked confidential or proprietary. If a

request is made to view Vendor’s proprietary information, WSDOT will notify Vendor of the

request and of the date that the records will be released to the requester unless Vendor obtains a

court order enjoining that disclosure. If Vendor fails to obtain the court order enjoining

disclosure, WSDOT will release the requested information on the date specified.

The State’s sole responsibility shall be limited to maintaining the above data in a secure area and

to notify Vendor of any request(s) for disclosure for so long as WSDOT retains Vendor’s




information in WSDOT records. Failure to so label such materials or failure to timely respond

after notice of request for public disclosure has been given shall be deemed a waiver by Vendor

of any claim that such materials are exempt from disclosure.

3.11. Waive Minor Administrative Irregularities

WSDOT reserves the right to waive minor administrative irregularities contained in any

Response. Additionally, WSDOT reserves the right, at its sole option, to make corrections to

Vendors’ Responses when an obvious arithmetical error has been made in the price quotation.

Vendors will not be allowed to make changes to their quoted price after the Response submission

deadline.

3.12. Errors in Response

Vendors are liable for all errors or omissions contained in their Responses. Vendors will not be

allowed to alter Response documents after the deadline for Response submission. WSDOT is not

liable for any errors in Responses. WSDOT reserves the right to contact Vendor for clarification

of Response contents.

In those cases where it is unclear to what extent a requirement or price has been addressed, the

evaluation team(s) may, at their discretion and acting through the RFQQ Coordinator, contact a

Vendor to clarify specific points in the submitted Response. However, under no circumstances

will the responding Vendor be allowed to make changes to the proposed items after the deadline

stated for receipt of Responses.

3.13. Withdrawal of Response

Vendors may withdraw a Response that has been submitted at any time up to the Response due

date and time (identified on the Schedule, Section 3). To accomplish Response withdrawal, a

written request signed by an authorized representative of Vendor must be submitted to the RFQQ

Coordinator. After withdrawing a previously submitted Response, Vendor may submit another

Response at any time up to the Response submission deadline.

3.14. Amendments/Addenda

WSDOT reserves the right to change the Schedule or other portions of this RFQQ at any time.

WSDOT may correct errors in the solicitation document identified by WSDOT or a Vendor. Any

changes or corrections will be by one or more written amendment(s), dated, and attached to or

incorporated in and made a part of this solicitation document. All changes must be authorized and

issued in writing by the RFQQ Coordinator. If there is any conflict between amendments, or

between an amendment and the RFQQ, whichever document was issued last in time shall be

controlling. In the event that it is necessary to revise or correct any portion of the RFQQ, a notice

will be posted in WEBS.

3.15. Right to Cancel

With respect to all or part of this RFQQ, WSDOT reserves the right to cancel or reissue at any

time without obligation or liability.

3.16. Selection of Apparently Successful Vendor

All Vendors responding to this solicitation will be notified by mail or e-mail when WSDOT has

determined the ASV. The ASV will be the respondent who: (1) meets all the requirements of this




RFQQ; and (2) receives the highest number of total points as described in Section 8.6, Vendor

Total Score. The date of announcement of the ASV will be the date the announcement letter is

postmarked, or if emailed the date the e-mail is sent.

3.17. Contract Requirements

To be responsive, Vendors must indicate a willingness to enter into a Contract substantially the

same as the proposed contract in Appendix B, by signing the Certifications and Assurances

located in Appendix A.

Any specific areas of dispute with the attached terms and conditions must be identified in the

Response using Appendix E, Contract Exception Log and may, at the sole discretion of WSDOT,

be grounds for disqualification from further consideration in the award of a Contract.

Under no circumstances is a Vendor to submit their own standard contract terms and conditions

as a response to this solicitation. WSDOT expects the final Contract signed by the ASV to be

substantially the same as the proposed contract located in Appendix B.

The foregoing should not be interpreted to prohibit either party from proposing additional

contract terms and conditions during negotiation of the final Contract.

The ASV will be expected to execute the Contract within 5 Business Days of its receipt of the

final Contract. If the selected Vendor fails to sign the Contract within the allotted 5 days’ time

frame, WSDOT may elect to cancel the award, and award the Contract to the next ranked Vendor,

or cancel or reissue this solicitation (see Section 3.17, Right to Cancel). Vendor’s submission of a

Response to this solicitation constitutes acceptance of these contract requirements.

3.18. Contract Exception Log

If applicable, Vendor must utilize Appendix E, Contract Exception Log, to submit any exceptions

to the proposed contract terms set forth in Appendix B, or recommendations for additional

Contract language. The Vendor shall submit any exceptions it wants WSDOT to consider as part

of the submission of its response. No new Contract language changes/exceptions may be raised

during negotiations if the exception was not initially documented as part of the Vendor’s Contract

Exception Log submitted with its Response. If the Vendor has no contract exceptions, it should

state as such in the Letter of Submittal and on the Contract Exception Log.

The Contract Exception Log must set out, by section or paragraph, a description of each

exception. In completing the Contract Exception Log, Vendor must describe, in business terms

and not in proposed Contract or legal language, the issue, concern, exception or objection and

then propose a compromise that is reasonable in light of the commitment being sought. The

Contract Exception Log must provide the reason or rationale supporting the issue, concern,

exception or objection. Simply stating that a paragraph is "not acceptable" or supplying proposed

Contract terms without describing (in business language) the reason or rationale will be

considered non-responsive.

Vendors are reminded that this is a competitive solicitation for a public contract and that WSDOT

cannot accept a response or enter into a contract that substantially changes the material terms and

specifications published in this RFQ.

3.19. No Costs or Charges

No costs or charges under the proposed Contract may be incurred before the Contract is fully

executed.




3.20. Incorporation of Documents into Contract

This solicitation document and the Response will be incorporated into any resulting Contract.

3.21. Minority and Women Business Enterprise, Small Business, and Veteran

Business Participation

WSDOT encourages participation in this contract by Minority and Women Business Enterprise,

Small Business, and Veteran Business as defined in WAC 326-02-030 and RCW 43.60A.010.

Voluntary Minority and Women Business Enterprise, Small Business, and Veteran-owned

Business participation goals have been established for the Contract in the following amounts:

10% Minority and Women Business Enterprise, 5% Small Business, 5% Veteran-owned

Business. Achievement of these goals is encouraged. However, no minimum level of Minority,

Women, Small Business, or Veteran participation shall be required as a condition of Contract

award. Vendors will not be rejected or considered non-responsive if they do not include Minority

and Women Business Enterprise, Small business, and Veteran business.

To find out the names of potential sub-contractor firms, Vendors may contact the Office of

Minority and Women’s Business Enterprises (OMWBE) for information on certified Minority

and Women Business Enterprise firms at (360) 664-9750; WSDOT’s Office of Equal Opportunity

(OEO) for information on available Small Businesses at (360) 705-7090; and the Washington

State Department of Veterans Affairs (WDVA) for information on certified Veteran and Service

member owned Businesses at (360) 725-2200.

Vendors who are OMWBE certified or intend on using OMWBE certified subcontractors should

identify such participation in OMWBE Participation form, Appendix C.

3.22. No Obligation to Contract/Buy

WSDOT reserves the right to refrain from Contracting with any and all Vendors. Neither the

release of this solicitation document nor the execution of a resulting Contract obligates WSDOT

to make any purchases.

3.23. Non-Endorsement and Publicity

In selecting a Vendor to supply Products or Services to the state of Washington, the State is

neither endorsing Vendor’s Products, nor suggesting that they are the best or only solution to the

State’s needs. By submitting a Response, Vendor agrees to make no reference to WSDOT or the

state of Washington in any literature, promotional material, brochures, sales presentation or the

like, regardless of method of WSDOT attribution, without the prior review and express written

consent of WSDOT.

3.24. Optional Vendor Debriefing

Only Vendors who submit a Response may request an optional debriefing conference to discuss

the evaluation of their Response. The requested debriefing conference must occur on or before

the date specified in the Schedule (Section 3). The request must be in writing (e-mail preferred)

addressed to the RFQQ Coordinator.

The optional debriefing will not include any comparison between the Response and any other

Responses submitted. However, WSDOT will discuss the factors considered in the evaluation of

the requesters Response and address questions and concerns about Vendor’s performance with




regard to the solicitation requirements. Further information regarding the grounds for, filing and

resolution of protests is contained in Appendix G, Complaint, Debrief and Protest Procedures.

3.25. Complaint, Debrief, and Protest Procedures

Vendors who have submitted a Response to this solicitation and have had a debriefing conference

may make protests. Upon completion of the debriefing conference, a Vendor is allowed five (5)

Business Days to file a formal protest of the solicitation with the RFQQ Coordinator. Further

information regarding the grounds for, filing and resolution of protests is contained in Appendix

G, Complaint, Debrief and Protest Procedures.

3.26. Wage Theft Prevention

Vendors must represent and warrant that neither it nor its principals or affiliates have, within the

three-year period prior to the date of this solicitation, been determined, by a final order of the

Washington Department of Labor and Industries or a court of competent jurisdiction, to be in

willful violation of state wage laws. Said signed certification shall be in the form attached as the

Wage Theft Prevention Certification form, Appendix H.

3.27. Gifts

Vendors shall comply with all applicable sections of the State Ethics law, RCW 42.52, which

regulates gifts to State officers and employees. Under that statute, any State officer or employee

who has or will participate with the Vendor regarding any aspect of the Contract involving the

purchase of goods or services is prohibited from seeking or accepting any gift, gratuity, favor or

anything of economic value from the Vendor. Neither the Vendor nor any agent or representative

shall offer anything of economic value as a gift, gratuity or favor directly or indirectly to any such

officer or employee.

3.28. Equal Employment Opportunity

Discrimination in all phases of contracted employment, consultant activities, contracting

activities, and training is prohibited by Title VI, Non-Discrimination, Title 49 C.F.R. Part 21 and

Title VII of the Civil Rights Act; 42 U.S.C. § 12101 et seq.; Americans With Disabilities Act and

Chapter 49.60 RCW, Washington Law Against Discrimination, and other Laws and Regulations.

The referenced legal citations establish the minimum requirements for affirmative action efforts

and define the basic nondiscrimination provisions that will be detailed in the Contract.

3.29. Title VI Notice to the Public

It is Washington State Department of Transportation (WSDOT) policy to ensure no person shall,

on the grounds of race, color, national origin, or sex, as provided by Title VI of the Civil Rights

Act of 1964, be excluded from participation in, be denied the benefits of, or be otherwise

discriminated against under any of its federally funded programs and activities. Any person who

believes his/her Title VI protection has been violated may file a complaint with WSDOT’s Office

of Equal Opportunity (OEO). For Title VI complaint forms and advice, please contact OEO’s

Title VI Coordinator at 360-705-7082 or 509-324-6018.




3.30. Public Disclosure

Materials submitted in response to this RFQ shall become the property of WSDOT. All responses

received shall remain confidential until the apparent successful bidder is announced, per RCW

39.26.030. Thereafter, the responses shall be deemed public records as defined in chapter 42.56

RCW.

In the event a Vendor desires to claim portions of its response as exempt from public disclosure,

the Vendor shall identify those portions as an attachment to their response and provide the legal

basis for the exemption. Vendor’s identifying the entire response or entire sections of the

response as proprietary or confidential will considered non-responsive. WSDOT will not accept

responses in which pricing is marked proprietary or confidential, and the response will be deemed

non-responsive and rejected.

To the extent consistent with chapter 42.56 RCW, the Public Disclosure Act, WSDOT shall

maintain the confidentiality of Vendor’s information marked confidential or proprietary. If a

request is made to view the portions of the response a Vendor has marked as proprietary or

confidential, WSDOT will notify the Vendor of the request and of the date that the records will be

released to the requester unless Vendor obtains a court order enjoining that disclosure. If Vendor

fails to obtain the court order enjoining disclosure, WSDOT will release the requested

information on the date specified.

WSDOT’s sole responsibility shall be limited to maintaining the Vendor identified proprietary or

confidential information in a secure area and to notify the Vendor of any request(s) for disclosure

for so long as WSDOT retains the Vendor’s information in WSDOT records. Failure to so label

such materials or failure to timely respond after notice of request for public disclosure has been

given shall be deemed a waiver by Vendor of any claim that such materials are exempt from

disclosure.

3.31. Federal Requirements

The Vendor shall comply with all applicable federal requirements and shall complete and

submit the following certifications, declarations and assurances as part of their response

to the RFQ.

Federal Form FHWA 1273 Certification Exhibit A.

Standard Form LLL – Disclosure of Lobbying Activities (only if Vendor

has engaged in lobbying) Exhibit B

3.32 Polychlorinated Biphenyls (PCB) Pursuant to RCW 39.26.280, the Washington State Department of Social and Health Services is

providing a bid preference in the amount of five (5) percent weight to the evaluation total, to any

bidder that provides products or products-in-packaging that do not contain Polychlorinated

Biphenyls (PCBs). All bidders must certify in the form attached as Appendix K - Statutory

Preference for PCBs, whether they are seeking the Statutory Preference for PCB-Free Products or

Products-In-Packaging.




SECTION 4

4. VENDOR REQUIREMENTS

Respond to the following requirements per the instructions in Section 3.

4.1. (M) Vendor Requirements

If the Vendor is not the owner of the solution being offered the Response must include a letter

from the owner of the solution certifying that (1) Vendor is an authorized Account Reseller (AR)

for the complete product line; (2) Vendor is authorized to conduct business as an AR in

Washington State; and (3) sufficient quantities of the required solution will be available to

Vendor to satisfy contract performance.

4.2. (M) Vendor Profile

Vendor must provide the information asked for in the Letter of Submittal, per Section 3.6. The

Letter of Submittal shall be included in each folder of the response as identified in Section 3.6.

4.3. (M) Vendor Account Manager

Vendor must designate an account manager who will be the principal point of contact the

WSDOT Contract Administrator for the duration of the Contract. Vendor’s account manager will

serve as the focal point for business matters and administrative activities.

4.4. (M) Use of Subcontractors

WSDOT will accept Responses that include third party involvement only if the Vendor

submitting the Response agrees to take complete responsibility for all actions of such

Subcontractors. Vendors must state whether Subcontractors are/are not being used, and if they are

being used, Vendor must list them in response to this subsection. WSDOT reserves the right to

approve or reject any and all Subcontractors that Vendor proposes. Any Subcontractors engaged

after award of the Contract must be pre-approved, in writing, by WSDOT.

Specific restrictions apply to contracting with current or former state employees pursuant to

chapter 42.52 RCW. Vendors should familiarize themselves with the requirements prior to

submitting a Response.

4.5. (M) Prior Contract Performance

Vendor must submit full details of all Terminations for Default for performance similar to the

solution requested by this RFQQ experienced by the Vendor in the past five (5) years, including

the other party’s name, address and telephone number.

“Termination for Default” is defined as notice to Vendor to stop performance due to the Vendor’s

non-performance or poor performance and the issue was either: (a) not litigated; or (b) litigated

and such litigation determined the Vendor to be in default.

Vendor must describe the deficiencies in performance, and describe whether and how the

deficiencies were remedied. Vendor must present any other information pertinent to its position

on the matter.




WSDOT will evaluate the information and may, at its sole discretion, reject the Response if the

information indicates that completion of a Contract resulting from this RFQQ may be jeopardized

by selection of the Vendor.

If the Vendor has experienced no such Terminations for Default in the past five years, so declare.

4.6. (M) Insurance

The ASV whose solution requires the vendor to perform any form of work related to this Contract

at WSDOT locations is required to obtain insurance to protect the State should there be any

claims, suits, actions, costs, or damages or expenses arising from any negligent or intentional act

or omission of the Vendor or its Subcontractor(s), or their agents, while performing work under

the terms of any Contract resulting from this solicitation. Vendors will find a complete

description of the specific insurance requirements in the proposed contract terms in Appendix B

4.7. (M) Documentation

Vendor must describe all documentation associated with the solution being offered and is

available to WSDOT. Description will include the available documentation, the format of the

documentation (e.g. electronic, digital media, hard copy), quantity provided with solution, the

frequency of documentation updates and how updates are delivered.




SECTION 5

5. EXPERIENCE and SKILL QUALIFICATIONS

5.1. (MS) Client References

Vendor must ensure that a minimum of two (2) of its commercial and/or government clients

submit completed reference forms (see Appendix F) for each skill category directly to the RFQQ

Coordinator by the deadline set forth in the Schedule (Section 3). Tim will update

The Products/Services purchased by these clients must be similar to those requested by this

RFQQ. Each client must currently use the Product/Service for at least one year.

References must not be from a person, company or organization with any special interest,

financial or otherwise, in the Vendor.

Vendor is responsible for ensuring that its clients submit their reference information directly to

the RFQQ Coordinator by the date and time Vendor Responses are due as specified in the

Schedule (Section 3). Vendor must select clients who will respond in a timely manner with

objective information concerning the Products/Services they have purchased. WSDOT reserves

the right to contact Vendor’s client references directly. In the event forms are not received by the

date specified in the schedule WSDOT will make one attempt to contact the client and obtain the

reference. If contact cannot be made, the reference will be disallowed.

WSDOT reserves the right to eliminate from further consideration in the RFQQ process any

Vendor who, in the opinion of WSDOT, receives an unfavorable report from a client. WSDOT

may, at its discretion, contact other Vendor clients for references.




SECTION 6

6. Transportation Worker Identification Credential (TWIC) validation system

REQUIREMENTS

All requirements in this section must be responded to by each vendor providing a proposal to the

RFQQ. Failure to respond to all requirements will disqualify the vendor’s proposal.

Mandatory Management Requirements (Section 6 of the RFQQ)

1. Functional Design Specification Vendor shall provide a Functional Design Specification (FDS) of the proposed system as part of the

proposal.

The proposed solution is required to comply with 33CFR parts 101, 104 and 105 as well as the

published TWIC Final Rule for Risk Group A.

1.a

1a Vendor Support and Testing Requirements (1-12) Yes/N

o Alternative Appendix B

1 The equipment provided by the vendor must be installed and ready for use in the WSF current security system environment and final invoicing received no later than May 10, 2021.

2

The Vendor is required to provide a delivery and implementation project schedule including project milestones to demonstrate their ability to meet the required implementation date.

3 The vendor shall provide standard warranty information that the hardware provided is capable of all functions listed in the technical requirements.

4

Vendor provided TWIC card readers, provided software, and required installation shall be supplied with a minimum one-year warranty from time of installation, for parts and labor to repair or replace failed hardware or resolve installation and/or software deficiencies. Reference (SLA) Appendix L

5

Vendor shall provide separate cost line item and pricing for an extended warranty / maintenance contract to cover all provided TWIC readers, any annual software licenses, software updates, and any server updates for a period of three years, in one-year increments after the initial one-year warranty expires. Reference Appendix D

6 The vendor shall provide a comprehensive testing plan for WSF’s approval to be used for testing the end-to-end proposed solution.

7 Vendor shall provide training materials detailing the operations and administration of the proposed solution.




8 Vendor shall provide 4 hours of end user training and 4 hours of administrator training for up to 12 class members. 8.1 explain how you meet that requirement. Reference Appendix D

9 The Vendor shall provide a duplicate software solution in WSF’s identical “test lab” for testing software upgrades and integrations prior to deployment into production.

10 Vendor shall fully test the end-to-end proposed solution before acceptance by WSF.

11 The vendor shall include all licensing cost and non-recurring cost for individual readers in the cost proposal submitted for the TWIC readers and not as a separate item. (Reference Appendix D

12

If the proposed devices are not compatible with the current environment and additional software or hardware is required to meet the requirements listed, this includes any integration established between contractor-supplied hardware and software and hardware- Or software provided by 3rd parties, then vendor shall assume full responsibility to support the end-to-end solution as proposed and installed. Any issues arising from or having an impact upon the use of the TWIC readers and software supplied by the vendor are wholly the responsibility of the vendor to resolve.




1.b Mandatory Technical Requirements – Detailed Hardware Requirements (1-9) Yes/No

Alternative Appendix B

1

Vendor shall provide TWIC readers that conform and perform to the most current TWIC reader hardware and card application specifications. • Verification of a TWIC card’s CHUID • Verification of a TWIC card’s PIN • Validate fingerprints with the templates on TWIC card. • Extract all data elements from the TWIC card.

2 Vendor shall provide outdoor TWIC readers that must be compliant with IP-54 or higher for outdoor use.

3 Vendor shall provide TWIC readers that must be capable of verifying TWIC against the Canceled Card List (CCL).

4 Vendor confirms-TWIC readers shall be capable of reading cards in proximity and contact mode and include a built-in biometric reader.

5

Enrollment stations capable of registering TWIC and linking with WSF’s existing PACS must be installed at the terminals and 2901 building, either as part of the fixed TWIC reader station at the key box location, attached to a PC/tablet or handheld reader. Appendix D

6 The Vendor proposed TWIC reader shall have the ability to operate in a standalone capacity when network is unavailable.

7

Hardening of physical key assets enclosures to be controlled by TWIC CHUID verification + user biometric authentication. Options: 1. Vendor shall propose a solution to harden these current

installations; for example, controlling access to the stainless Hoffman enclosure with a mag lock, integrating into the Security Asset Manager (SAM) directly

2. Vendor can propose a new key management solution all together.




8

Hardening the roadside cabinet at Tahlequah Terminal; this is a double door stainless enclosure and access to this enclosure needs to be controlled by TWIC CHUID verification + user biometric authentication. Examples -could include using a mag lock or protecting a physical key for a pad lock managed with a Knox Box. The key is required to be electronically audited for status.

9

Vendor solution provides remote ability to validate TWIC cards and check them against the CCL for WSF’s security officers to include the following:

This ability could be part of a solution utilizing the staff’s existing tablets or a vendor supplied handheld device.

These units are required to validate TWIC cards in an offline mode and send and receive updates when docked or plugged back into WSF’s network depending on the proposed solution.




1.c

Software Requirements (1-10) Yes/No Alternative Appendix B

1 Vendor provided TWIC readers shall be capable of communication to a central management software to store transactional data

2

Any additional server-side software required for PACS and TWIC reader integration shall be provided and capable of being installed in WSF’s virtual environment, comprised of Windows Server 2016 and MS SQL Server 2016. Integration into WSF’s existing PACS requires the successful Vendor to collaborate and partner with G4S Secure Integration. G4S is WSF Security Integrator and under an existing contract supporting WSF’s AMAG Symmetry solution.

3 Vendor shall confirm that Access logs will be maintained for two years.

4

To conduct electronic TWIC inspection, the owner or operator of a vessel or facility must ensure the following actions are performed. 33CFR 101.520 (Vendor confirm A, B, C) a. Card authentication. The TWIC must be authenticated by performing a challenge/response protocol using the Certificate for Card Authentication (CCA) and the associated card authentication private key b. Card validity check. The TWIC must be checked to ensure the TWIC has not expired and against TSA's list of cancelled TWICs, and no match on the list. c. Identification verification. i. One of the biometric templates stored in the TWIC must be matched to the TWIC-holder's live sample biometric or, by matching to the PACS enrolled reference biometrics linked to the FASC-N of the TWIC; Or ii. If an individual is unable to provide a valid live sample biometric, the TWIC-holder must enter a Personal Identification Number (PIN) and pass a visual TWIC inspection.

5 Vendors confirm- CCL updates happen on at least a 24-hour interval.

6 Vendor shall provide centralized management of reader firmware.

7 Vendor provided centralized management application shall be capable of formatting and generating reports using available data.




8

Vendor shall provide centralized management application capable of generating emails to selected WSF management notifying recipients and present an indication to the reader if the TWIC card is on the CCL.

9

Vendor provided solution shall have the ability to enroll TWIC into AMAG Symmetry Enterprise v9 database and assign TWIC information to existing cardholder within the AMAG database by utilizing WSF’s HID Corporate 1000 ID card number during the TWIC enrollment process. If the WSF ID Cardholder’s TWIC appears on the CCL, report this on the associated device.

10

The TWIC credential will be used for access control into a restricted space based on a configurable access code assigned to the cardholder within the AMAG Symmetry PACs system. (Vendor confirm)

1.d

Cyber Security Requirements Yes/No Alternative

All Services implemented in the State of Washington on state computer systems and networks must be compliant with the security policy and standards of the Office of the Chief Information Officer (OCIO). The OCIO Security Standards is available at: https://ocio.wa.gov/policy/securing-information-technology-assets-standards . The Vendor will be required to represent and warrant that it will comply with all applicable elements of the OCIO Security Standards in its performance of any Services awarded under a Contract.

N/A

https://ocio.wa.gov/policy/securing-information-technology-assets-standards

https://ocio.wa.gov/policy/securing-information-technology-assets-standards




2.0 Optional Technical Requirements for Control Center Software – Detailed (not

mandatory)

Note: These optional software requirements are necessary only if the items proposed require Control

Center Software in addition to what is detailed in the Current Environment, section 19. Please provide

and itemized cost breakdown for these additional items detailed in

1. Download CCL from TSA at a definable frequency and perform a validation of enrolled

TWIC cards.

2. Ability to automatically deactivate an individual’s PACS card in Symmetry upon the

individual’s enrolled TWIC card being on the CCL. PACS integration would need to follow

the requirements listed out in 33CFR 101.530. The process shall also include generating an

email to selected WSF management notifying recipients of any WSF ID cardholder that

appear on the CCL.

3. Any additional software, programming or API’s required to make this system functional shall

be identified and provided by the selected Vendor.

2.1 Terminal Installation Scopes: Please provide a yes/no or alternative solution (1-16)

Anacortes Terminal: Yes/No Alternative Appendix B

1

Add an exterior rated TWIC biometric card reader to the fiber glass enclosure adjacent to the key box on the exterior of the main terminal building. • Install mag lock or alternative solution inside the key box enclosure to harden access to physical keys. • Replace the legacy HID card reader on the electrical room with an exterior rated TWIC biometric card reader.

Bainbridge Terminal Yes/No Alternative

Appendix B

2

Add an exterior rated TWIC biometric card reader to the fiber glass enclosure adjacent to the key box on the exterior of the main terminal building. • Install mag lock or alternative solution inside the key box enclosure to harden access to physical keys. • Replace the legacy HID card reader on the electronic equipment room with a TWIC biometric card reader. • Replace the legacy HID card reader on the electrical room with an exterior rated TWIC biometric card reader.• Replace the legacy HID card reader on the electrical room with an exterior rated TWIC biometric card reader.




Bremerton Terminal Yes/No Alternative

Appendix B

3

Add an exterior rated TWIC biometric card reader to the fiber glass enclosure adjacent to the key box on the exterior of the agent’s office building. • Install mag lock or alternative solution inside the key box enclosure to harden access to physical keys. • Replace the legacy HID card reader on the electronic equipment room with a TWIC biometric card reader. • Replace the legacy HID card reader on the electrical room with an exterior rated TWIC biometric card reader.

Clinton Terminal Yes/No Alternative

Appendix B

4

Add an exterior rated TWIC biometric card reader to the fiber glass enclosure adjacent to the key box on the exterior of the main terminal building. • Install mag lock or alternative solution inside the key box enclosure to harden access to physical keys. • Replace the legacy HID card reader on the electronic equipment room with an exterior rated TWIC Biometric Card Reader.

Coupeville Terminal Yes/No Alternative

Appendix B

5

Add an exterior rated TWIC biometric card reader to the fiber glass enclosure adjacent to the key box on the exterior of the main terminal building. • Install mag lock or alternative solution inside the key box enclosure to harden access to physical keys. • Replace the legacy HID card reader on the electrical room with an exterior rated TWIC biometric card reader.




Edmonds Terminal Yes/No Alternative

Appendix B

6

Add an exterior rated TWIC biometric card reader to the fiber glass enclosure adjacent to the key box on the exterior of the agent’s office building. • Install mag lock or alternative solution inside the key box enclosure to harden access to physical keys. • Replace the legacy HID card reader on the electronic equipment room with an exterior rated biometric card reader. • Replace the legacy HID card reader on the electrical room with a TWIC biometric card reader.

Fauntleroy Terminal Yes/No Alternative

Appendix B

7

Add an exterior rated TWIC biometric card reader to the fiber glass enclosure adjacent to the key box on the exterior of the Main Terminal building. • Install mag lock or alternative solution inside the key box enclosure to harden access to physical keys. • Replace the legacy HID card reader on the electronic equipment room with an exterior rated TWIC biometric card reader.

Friday Harbor Terminal Yes/No Alternative

Appendix B

8

Add an exterior rated TWIC biometric card reader to the fiber glass enclosure adjacent to the key box on the exterior of the main terminal building. • Install mag lock or alternative solution inside the key box enclosure to harden access to physical keys. • Replace the legacy HID card reader on the electronic equipment room with an exterior rated TWIC Biometric Card Reader. • Replace the legacy HID card reader on the electrical room by holding lanes with an exterior rated TWIC biometric card reader.




Kingston Terminal Yes/No Alternative

Appendix B

9

Add an exterior rated TWIC biometric card reader to the fiber glass enclosure adjacent to the key box on the exterior of the Agent’s Office building. • Install mag lock or alternative solution inside the key box enclosure to harden access to physical keys. • Replace the legacy HID card reader on the electronic equipment room with a TWIC biometric card reader. • Replace the legacy HID card reader on the electrical room with an exterior rated TWIC biometric card reader.

Mukilteo Terminal Yes/No Alternative

Appendix B

10

Add an exterior rated TWIC biometric card reader at the key box on the exterior of the main terminal building. • Install mag lock or alternative solution inside the key box enclosure to harden access to physical keys. • Replace the legacy HID card reader on the maintenance electronics room with an exterior rated TWIC biometric card reader • Replace the legacy HID card reader on the maintenance electrical room with an exterior rated TWIC biometric card reader. • Replace the legacy HID card reader on the main terminal electrical room with an exterior rated TWIC biometric card reader. • Replace the legacy HID card reader on the main terminal communications room with a TWIC biometric card reader. • Replace the legacy HID card reader on the toll plaza communications room with an exterior rated TWIC biometric card reader. • Replace the legacy HID card reader on the toll plaza electrical room with an exterior rated TWIC biometric card reader.

Point Defiance Terminal Yes/No Alternative

Appendix B

11

Add an exterior rated TWIC biometric card reader at key box on the exterior of the electronic equipment room. • Install mag lock or alternative solution inside the key box enclosure to harden access to physical keys. • Replace the legacy HID card reader on the electronic equipment room with an exterior rated TWIC biometric card reader. • Replace the legacy HID card reader on the Seller Safe Room with a TWIC biometric card reader.




Port Townsend Terminal Yes/No Alternative

Appendix B

12

Add an exterior rated TWIC biometric card reader to the fiber glass enclosure adjacent to the key box on the exterior of the main terminal building. • Install mag lock or alternative solution inside the key box enclosure to harden access to physical keys. • Replace the legacy HID card reader on the Electronic Equipment Room with a TWIC biometric card reader.

Seattle Terminal Yes/No Alternative

Appendix B

13

Add an exterior rated TWIC biometric card reader to the fiber glass enclosure adjacent to the key box on the exterior of the agent’s office building. • Install mag lock or alternative solution inside the key box enclosure to harden access to physical keys. • Replace the legacy HID card reader on the electronic equipment room with a TWIC biometric card reader. • Replace the legacy HID card reader on the electrical room (upper main terminal) with a TWIC biometric card reader. • Replace the legacy HID card reader on the passenger seller safe room with an exterior rated TWIC biometric card reader. • Replace the legacy HID card reader on the electrical room #1(lower-Seattle City Light) with an exterior rated TWIC biometric card reader. • Replace the legacy HID card reader on the electrical room #2(lower-Seattle City Light) with an exterior rated TWIC biometric card reader. • Replace the legacy HID card reader on the entry IDF with an exterior rated TWIC Biometric Card Reader. • Replace the legacy HID card reader on the VPAC IDF with a TWIC biometric card reader. • Replace the legacy HID card reader on the toll plaza electronics room with an exterior rated TWIC biometric card reader.

Southworth Terminal Yes/No Alternative

Appendix B

14

Add an exterior rated TWIC biometric card reader to the fiber glass enclosure adjacent to the key box on the exterior of the main terminal building. • Install mag lock or alternative solution inside the key box enclosure to harden access to physical keys. • Replace the legacy HID card reader on the electronic equipment room with an exterior rated TWIC biometric card reader.




Tahlequah Terminal Yes/No Alternative

Appendix B

15

Add an exterior rated TWIC biometric card reader to the outside of the network/server roadside cabinet. • Install mag locks or alternative solution inside the network/server roadside cabinet to harden access through the front and back doors of the cabinet.

Vashon Terminal Yes/No Alternative

Appendix B

16

Add an exterior rated TWIC biometric card reader to the fiber glass enclosure adjacent to the key box on the exterior of the main terminal building. • Install mag lock or alternative solution inside the key box enclosure to harden access to physical keys. • Replace the legacy HID card reader on the electronic equipment room with an exterior rated TWIC biometric card reader.




SECTION 7

7. FINANCIAL QUOTE

Respond to the following requirements per the instructions in Section 3. Use Appendix C for your

responses.

7.1. Overview

WSDOT seeks to acquire the TWIC Validation System Replacement that best meet the State’s

needs at the lowest cost and best value.

Contract prices must include all cost components needed for the provisioning of the proposed

TWIC Validation System Replacement.

7.2. Grounds for Disqualification

Failure to identify all costs in a manner consistent with the instructions in this RFQQ is sufficient

grounds for disqualification.

7.3. Taxes

Vendor must not include taxes on the Price List.

7.4. (M) Presentation of All Cost Components

All elements of recurring and non-recurring costs must be identified and included in Appendix D,

Price List. This must include, but is not limited to, all administrative fees, maintenance, manuals,

documentation, shipping charges, labor, travel, training, consultation services, wiring and

supplies needed to perform the work defined in this RFQQ and subsequent Contract.

Expenses related to day-to-day performance under any Contract, including but not limited to,

travel, lodging, meals, incidentals will not be reimbursed to the Vendor. Costs for such expenses

must be incorporated into the overall cost of the solution being offered.

7.5. (M) Appendix D, Price List

7.5.1. Line one (1) of Appendix D, Price List shall reflect the first year system costs to include,

but not limited to, the cost of system/services, installation support, technical support, ,

warranty, and other costs needed to establish the Vendor solution with the WSDOT.

Items are to be quoted FOB destination, Olympia, Washington. All anticipated shipping

costs necessary to meet the delivery schedule must be included in the quote. No additional

charges for shipping or handling will be allowed. Where we shipping

7.5.2. Line two (2) of Appendix D, Price List, shall reflect training costs for up to 12 staff.

Include as an attachment to the Price List a statement that details how the training is

delivered (in person or Web based), the estimated time commitment for staff and estimated

expenses for in-person and on-line trainers. (in person or web based? Preference)

In-person training costs must include all documentation and materials.

Web based training is an acceptable alternative if the organization has success training in

that forum.




7.5.3. Line three (3) of Appendix D, Price List, shall reflect any miscellaneous costs not reflected

in lines one or two. Include as an attachment to the Price List a detailed list of what

comprises the miscellaneous costs.

7.5.4. Lines four (4) through nine (9) of Appendix D Price List, shall reflect the cost of

Maintenance, Support, and or Services for the years following the initial year of support

(years 2 through 5).

7.5.5. Line three (5) of Appendix D, Price List, shall reflect the cost of Hardening the roadside

cabinet at Tahlequah Terminal; this is a double door stainless enclosure and access to this

enclosure needs to be controlled by TWIC CHUID verification + user biometric

authentication. RFQQ requirement #8.

7.5.6. Line three (6) of Appendix D, Price List, shall reflect all Service Level agreement

requirements per Appendix L

7.5.7. Line three (7) of Appendix D, Price List, shall reflect additional Software, Hardware and licenses if required-

7.5.8. Line three (8) of Appendix D, Price List, shall reflect all licensing cost and non-recurring

cost for individual requirements

7.5.9. Line three (9) of Appendix D, Price List, shall reflect additional itemized mobile enrollment

stations either part of an existing tablet or optional handheld readers

7.5.10. Line item (10) of Appendix D, Price List, shall reflect additional itemized mobile

enrollment stations either part of an existing tablet or optional handheld if they become

necessary

7.5.11. Line item (11) of Appendix D, Price List, shall reflect Outdoor TWIC readers Compliant

with IP-54 or higher outdoor use

7.5.12. Line item (12) of Appendix D, Price List, shall reflect Indoor or outdoor TWIC card

readers

7.6. (M) Price Protection

For the entire term(s) of the Contract, the Vendor must guarantee to provide the Transportation

Worker Identification Credentials System (TWIC) system at the proposed rates. TWIC rates

cannot increase during any term of the Contract.

7.7. (M) Price Decrease Guarantee

The ASV, at its discretion, may elect to provide Transportation Worker Identification Credential

System specified in this RFQQ at a lower price than originally quoted at any time during the term

of the Contract. If the Manufacturer’s suggested retail price decreases at any time during the term

of the Contract, Vendor must pass on the decrease for all subsequent purchases. The decrease

must be proportionate to the percentage decrease of the Manufacturer’s suggested retail price.

7.8. (M) Costs Not Specified

Where there is no charge or rate for Transportation Workers Identification Credential System

(TWIC) enter N/C (no charge) or zero (0) on the Price List, as applicable. If the Vendor fails to

provide a price, the State will assume the item is free. If the Vendor states “no charge” for an item




the State will receive that item free for the period represented on the Price List. Look at this

section

5ertifications and Assurances Transportation Worker Identification Credential


Department of Transportation RFQQ 2020 1215

SECTION 8

8. EVALUATION PROCESS

8.1. Overview

The Vendor who meets all of the RFQQ requirements and receives the highest number of total points as

described in Section 8.6, Vendor Total Score, will be declared the ASV and will enter into contract

negotiations with WSDOT.

8.2. Administrative Screening

Responses will be reviewed initially by the RFQQ Coordinator to determine pass/fail compliance with

the administrative requirements as specified in Section 3, Administrative Requirements. The evaluation

team will only evaluate Responses meeting all administrative requirements.

8.3. Mandatory Requirements

Responses meeting all of the administrative requirements will then be reviewed on a pass/fail basis to

determine if the Response meets the Mandatory requirements found in Sections 4-7. Only Responses

meeting all Mandatory requirement will be further evaluated.

The State reserves the right to determine at its sole discretion whether Vendor’s response to a

Mandatory requirement is sufficient to pass. If, however, all responding Vendors fail to meet any single

Mandatory item, WSDOT reserves the following options: (1) cancel the procurement, or (2) revise or

delete the Mandatory item.

8.4. Allocation of Points

The scores for Response will be assigned a relative importance for each scored section. The relative

importance for each section is as follows:

Client References (Section 5.1)

TWIC Validation System Replacement Requirements (Section 6)

Pricing (Section 7, Appendix D)

10 points/percent

65 points/percent

25 Points/percent

Total Possible Points 100 100 points/percent

Note: Per Section 3.32: Pursuant to RCW 39.26.280, the Washington State Department of Social and

Health Services is providing a bid preference in the amount of five (5) percent weight to the evaluation

total, to any bidder that provides products or products-in-packaging that do not contain Polychlorinated

Biphenyls (PCBs).

8.5. Qualitative Review and Scoring

Only Responses that pass the administrative screening and Mandatory requirements review will be

evaluated and scored based on responses to the scored requirements in the RFQQ. Responses receiving

a “0” on any Mandatory Scored (MS) element(s) will be disqualified.

A. TWIC Validation System Replacement Requirements Evaluation




Each scored element in the Transportation Workers Identification System (TWIC) will be given

a score by each team evaluator. Then, the scores will be totaled and an average score for each

Vendor will be calculated as set forth below. This will be used in the calculation of Vendor’s

total score, as set forth in Section 8.6, Vendor Total Score.

Evaluation points will be assigned based on the effectiveness of the Response to each

requirement. A scale of zero to four will be used, defined as follows:

0 Unsatisfactory Response is non-responsive or wholly inadequate.

1 Partial

Compliance

The response includes some elements of the requirement

but not all requirements.

2 Average The response provided demonstrates all elements of the

requirement

3 Above Average Capability is better than that which is average or expected as the

norm.

4 Exceptional Capability is clearly superior to that which is average or expected as

the norm.

Sum of Evaluators’ TWIC Requirement Scores = Vendor’s Avg. TWIC Requirement Score

Number of Evaluators

B. Client Reference Evaluation

The RFP Coordinator will calculate the scores for each Client Reference Form, Appendix F.

The total scores of all the Vendor’s Client References will be summed together and an average

point score will be calculated as set forth below. This will be used in the calculation of Vendor’s

total score, as set forth in Section 8.6, Vendor Total Score.

Total Reference Scores = Vendor’s Avg. Reference Score

Number of References

C. Financial Quote Evaluation

The RFQQ Coordinator will calculate the financial score using Vendor’s Appendix D response..

This financial score will be used in the calculation of Vendor’s total score, as set forth in

Section 8.6, Vendor Total Score. Lowest Price Quote x 25 points = Financial Score

Vendor’s Price Quote

8.6. Vendor Total Score

Vendors will be ranked using the Vendor’s Total Score for its Response, with the highest score ranked

first and the next highest score ranked second, and so forth. Vendor’s Total Score will be calculated as

follows:

Total Score = (Reference Score) + (Financial Quote Score) + (TWIC Validation System Replacement

Requirements Score)

Note: Per Section 3.32: Pursuant to RCW 39.26.280, the Washington State Department of Social

and Health Services is providing a bid preference in the amount of five (5) percent weight to the

evaluation total, to any bidder that provides products or products-in-packaging that do not contain

Polychlorinated Biphenyls (PCBs).




8.7. Selection of Apparently Successful Vendor

The Vendor with the highest Vendor total score will be declared the ASV. WSDOT will enter into

contract negotiations with the ASV. Should contract negotiations fail to be completed within one week

after initiation, WSDOT may immediately cease contract negotiations and declare the Vendor with the

second highest score as the new ASV and enter into contract negotiations with that Vendor. This

process will continue until the Contracts are signed or no qualified Vendors remain.




APPENDIX A CERTIFICATIONS AND ASSURANCES

TWIC Validation System Replacement Services

Issued by the State of Washington We make the following certifications and assurances as a required element of the Response to which it is attached,

affirming the truthfulness of the facts declared here and acknowledging that the continuing compliance with these

statements and all requirements of the RFQQ are conditions precedent to the award or continuation of the resulting

Audit Services Contract.

The prices in this Response have been arrived at independently, without, for the purpose of restricting competition,

any consultation, communication, or agreement with any other offeror or competitor relating to (i) those prices, (ii)

the intention to submit an offer, or (iii) the methods or factors used to calculate the prices offered. The prices in this

Response have not been and will not be knowingly disclosed by the offeror, directly or indirectly, to any other offeror

or competitor before Contract award unless otherwise required by law. No attempt has been made or will be made by

the offeror to induce any other concern to submit or not to submit an offer for the purpose of restricting competition.

However, we may freely join with other persons or organizations for the purpose of presenting a single proposal or

bid.

The attached Response is a firm offer for a period of 120 days following the Response Due Date specified in the

RFQQ, and it may be accepted by WSDOT without further negotiation (except where obviously required by lack of

certainty in key terms) at any time within the 120-day period. In the case of protest, your Response will remain valid

for 180 days or until the protest is resolved, whichever is later.

In preparing this Response, we have not been assisted by any current or former employee of the state of Washington

whose duties relate (or did relate) to the State's solicitation, or prospective Audit Services Contract, and who was

assisting in other than his or her official, public capacity. Neither does such a person nor any member of his or her

immediate family have any financial interest in the outcome of this Response. (Any exceptions to these assurances

are described in full detail on a separate page and attached to this document.)

We understand that the State will not reimburse us for any costs incurred in the preparation of this Response. All

Responses become the property of the State, and we claim no proprietary right to the ideas, writings, items or samples

unless so stated in the Response. Submission of the attached Response constitutes an acceptance of the evaluation

criteria and an agreement to abide by the procedures and all other administrative requirements described in the

solicitation document.

We understand that any TWIC Validation System Replacement Contract awarded, as a result of this Response will

incorporate all the solicitation requirements. Submission of a Response and execution of this Certifications and

Assurances document certify our willingness to comply with the TWIC Validation System Replacement Contract

terms and conditions appearing in Appendix B, or substantially similar terms, if selected as a contractor. It is further

understood that our standard contract will not be considered as a replacement for the terms and conditions appearing

in Appendix B of this solicitation.

We (circle one) are / are not submitting proposed TWIC Validation System Replacement System Contract

exceptions (see Subsection 3.15,).

Vendor Signature Vendor Company Name

Title Date




Model Contract Appendix B

Department of Transportation Page B-1

APPENDIX B

MODEL CONTRACT

Terms and Conditions

For

See attached Appendix B

MWBE Appendix C

Department of Transportation Page C-1 RFQQ 2020 1215

APPENDIX C

MWBE Participation Form (Optional)

Minority and Women's Business Enterprises (MWBE)

Participation Form

MWBE participation is defined as: Certified MBEs and WBEs bidding as prime contractor, or prime

contractor firms subcontracting with certified MWBEs. For questions regarding the above, contact Office

of MWBE, (360) 753-9693.

In accordance with WAC 326-30-046, WSDOT goals for acquisitions have been established as follows:

12% MBE or WBE.

MBE FIRM NAME *MBE CERTIFICATION NO. PARTICIPATION %

WBE FIRM NAME *WBE CERTIFICATION NO. PARTICIPATION %

*Certification number issued by the Washington State Office of Minority and Women's Business Enterprises.

Name of Vendor completing this Certification: ______________________________________________

Response Checklist


APPENDIX D

COST MODEL (attached)

Response Checklist


APPENDIX E

RFQQ-2020-1214

TWIC Validation System Replacement

CONTRACT EXCEPTION LOG

The Proposer shall utilize the following template to document exceptions that the Proposer has for the terms or conditions contained in the Contract as per the instructions in the RFQQ.

Item Contract Section #

Issue Vendor’s Proposed Solution/Rationale

1

2

3

4

5

6

7

8

9

10

11

12

13

14




APPENDIX F

CLIENT REFERENCE FORM

TWIC VALIDATION SYSTEM REPLACEMENT RFQQ

Name of Vendor for whom reference is given: __________________________________________

Your organization’s business name: ___________________________________________________

Your Name and title: _______________________________________________________________

Telephone number: ___________________ E-Mail address: _____________________________

Describe the type of Vendor’s Audit Services completed for your organization:

_______________________________________________________________________________

_______________________________________________________________________________

_________________________________________________________________________________

_________________________________________________________________________________

PLEASE RATE THE FOLLOWING ITEMS (circle one):

Unsatisfactory

Below

Average

Average

Above

Average

Exceptional

1. [Ability to communicate clearly & effectively:]

0 1 2 3 4

Comments:________________________________________________________________________

2. [Responsiveness to contractual issues:] 0 1 2 3 4

Comments:________________________________________________________________________

3. [Ability to resolve problems:] 0 1 2 3 4

Comments:________________________________________________________________________

4. [Competency of staff:] 0 1 2 3 4

Comments:________________________________________________________________________

5. [Reliability of Audit Services ] 0 1 2 3 4

Comments:________________________________________________________________________




PLEASE RATE THE FOLLOWING ITEMS (circle one):

Unsatisfactory

Below

Average

Average

Above

Average

Exceptional

6. [Quality of Services provided:] 0 1 2 3 4

Comments:________________________________________________________________________

7. [Responsiveness to resolving invoicing issues:] 0 1 2 3 4

Comments:________________________________________________________________________

8. [Ability to meet project deadlines:] 0 1 2 3 4

Comments:________________________________________________________________________

9. [Overall satisfaction with Vendor:] 0 1 2 3 4

Comments:________________________________________________________________________

Any other information that you would like to share about the Vendor:

_________________________________________________________________________________

_________________________________________________________________________________

_________________________________________________________________________________

Your Signature: _________________________________________

Please return the reference (may be Faxed) by December 11, 2020, no later than 2:00 Pm PT Olympia, WA local time,

to:

Tim Carroll, RFQQ Coordinator

Washington State Department of Transportation

310 Maple Park Ave.

Olympia, WA 98501

Telephone: (360) 705-7595

E-mail: [email protected]

Thank you for your time and cooperation.





APPENDIX G

COMPLAINT AND PROTEST PROCEDURES

1.0 COMPLAINT

This complaint procedure is available to Vendors with unresolved issues or concerns that were

not addressed or resolved during the question and answer period of the solicitation.

Vendor complaints must be received, in writing, by the Solicitation Coordinator not less than

five (5) business days prior to the deadline for bid submission.

1.1 Grounds for Complaint

Written complaints may be based only on the following:

The solicitation unnecessarily restricts competition;

The solicitation evaluation or scoring process is unfair or flawed; or

The solicitation requirements are inadequate or insufficient to prepare a response.

Complaints not based on these criteria will not be considered.

1.2 Format and Content

Vendors making a complaint shall include in their written complaint to WSDOT all facts and

arguments upon which the Vendor relies. Vendors shall, at a minimum, provide the following

in their written complaint:

The name of the protesting Vendor, its mailing address and phone number, and the

name of the individual responsible for submission of the protest;

The solicitation document name and number and reference to WSDOT as the issuing

agency ;

Specific and complete statement of WSDOT’s action(s) that is the subject of the

complaint;

Specific reference to the basis for the complaint; and

Description of the relief or corrective action requested.

1.3 WSDOT Review Process

Upon receipt of a complaint, the Solicitation Coordinator or his or her designee will consider

all the facts available and respond in writing prior to the deadline for bid submissions. The

complaint response and any changes to the solicitation arising from the complaint shall be

posted on WEBS as an amendment to the solicitation.

The Solicitation Coordinator’s response to the complaint is final and not subject to

administrative appeal. A copy of this response will be sent to the Secretary’s Office or

designee.




Issues raised in a complaint may not be raised again during the protest period.2.0 Protests

This protest procedure is available to Vendors who submitted a Response to this solicitation

and have requested and attended a debriefing conference. Protests must be made to WSDOT

after the Apparently Successful Vendor (ASV) has been announced. To be considered, Vendor

protests must be received, in writing, by WSDOT within five (5) Business Days after the

Vendor debriefing conference.

2.1 Grounds for Protest

Protests may be made on only these grounds:

A matter of bias, discrimination, or conflict of interest on the part of an evaluator;

Errors in computing the scores; or

Non-compliance with procedures described in the procurement document or agency protest

process or DES requirements.

Protests not based on these criteria will not be considered

2.2 Procedure for Protest

A Vendor must file a written protest with WSDOT within five (5) Business Days after their

debriefing conference. WSDOT will immediately notify Department of Enterprise Services

(DES) of receipt of the protest. WSDOT will also postpone further steps in the acquisition

process until the protest has been resolved.

A protest shall be in writing, shall contain the facts and arguments upon which the protest is

based, and shall be signed by a person authorized to bind the Vendor to a contractual

relationship. At a minimum, the protest shall include the following information:

The name of the protesting Vendor, its mailing address and phone number, and the

name of the individual responsible for submission of the protest.

The solicitation document name and number and reference to WSDOT as the issuing

agency.

Specific and complete statement of WSDOT’s action(s) being protested.

Specific reference to the grounds for the protest.

Description of the relief or corrective action requested.

Protests shall be addressed to:

Chief Information Officer

Washington State Department of Transportation

7345 Linderson Way SW

Tumwater, WA 98501-7430

The Vendor shall also forward a copy to the WSDOT Solicitation Administrator at the same

time the protest is sent to the Chief Information Officer.




2.3 WSDOT Review Process

Upon receipt of a protest, a protest review will be held by WSDOT. WSDOT will postpone

signing Contracts with ASVs until the Vendor protest has been resolved. Individuals not

involved in the protested acquisition will objectively review the written protest material

submitted by the Vendor and all other relevant facts known to WSDOT. All available facts

will be considered, and the director of the department responsible for administration of the

Contract, or his/her delegate will issue a decision within five Business Days of receipt of the

protest. If additional time is required, the protesting party will be notified of the delay within

five Business Days of receipt of the protest.

2.4 WSDOT Determination

The final determination shall:

Find the protest lacking in merit and uphold the agency’s action;

Find only technical or harmless errors in the agency’s acquisition process conduct,

determine the agency to be in substantial compliance, and reject the protest;

Find merit in the protest and provide the agency with options that may include:

o Correct errors and reevaluate all proposals; or

o Reissue the solicitation document; or

o Make other findings and determine other courses of action as appropriate.

Not require the agency to award a Contract to the protesting party or any other Vendor,

regardless of the outcome.

The determination of WSDOT is final and no further administrative appeals are

available.