the city of kansas city, missouri request for proposals


[PDF]the city of kansas city, missouri request for proposals - Rackcdn.com000417b6df56f4ae5bbf-f6bd2cfeac0f4625637eac684e9e6a05.r25.cf1.rackcdn.com/...

0 downloads 147 Views 812KB Size

THE CITY OF KANSAS CITY, MISSOURI

REQUEST FOR PROPOSALS

ENTERPRISE PERMITTING SYSTEM

RFP NO. EV1788 PROPOSALS DUE: 09/09/2013 BY 2 P.M. (CT)

PROCUREMENT SERVICES DIVISION KEELY GOLDEN, CPPB (816) 513-3670

ISSUE DATE: 07-19-2013

REQUEST FOR PROPOSALS NO. EV1788 TABLE OF CONTENTS

Section

Page

I.

Instructions and Conditions

3-14

II.

Scope of Services

15-35

III.

Special Instructions and Conditions

36-54

Authorized Signature Form

37

Cooperative Procurement with Other Jurisdictions

38

Standard City Contract

39-53

No Response Form IV.

54

Attachments

55-63

No. I: Pricing/Cost Proposal

56

No. 2: Employee Eligibility Verification Affidavit

57-58

No. 3: References

59-60

No. 4: HRD Forms and Instructions No. 5: Performance Bond

61 62-63

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 2 of 63

SECTION I REQUEST FOR PROPOSALS NO. EV1788 INSTRUCTIONS AND CONDITIONS

1.

PURPOSE The City of Kansas City, Missouri (“City”) invites you to submit a proposal for Enterprise Permitting System.

2.

DUE DATE FOR PROPOSALS Proposers shall submit Proposals to the City Contact Person listed in Section 3 by 2 p.m. (CT) on 9/9/13 (September 9, 2013).

3.

CITY CONTACT PERSONS (a)

General and Technical Questions and Proposal Submissions Proposers shall submit their Proposal and any general questions or issues about any aspect of this RFP to the following City Contact person: Keely Golden, CPPB Procurement Services Division City Hall, 1st Floor, Room 102 W 414 E. 12th Street, Kansas City, Missouri 64106 Office: (816) 513-3670 Fax: (816) 513-1156 E-mail: [email protected]

4.

DEFINITION OF “REQUEST FOR PROPOSALS” AND “PROPOSAL” (a)

This Request for Proposals (“RFP” or “solicitation”) is an invitation by the City for Proposers to submit an offer, which may be subject to subsequent discussions and negotiations by the City and the Proposer. It is not a request for a competitive bid.

(b)

“Proposal” means any document, submittal, interview, presentation, discussion, negotiation, and everything and anything provided in response to this RFP regardless whether the submission is an oral or written submission.

(c)

By submitting a proposal to the City, Proposer agrees that the Proposer does not obtain any right in or expectation to a contract with the City or a vested interest or a property right in a contract with the City regardless of the amount of time, effort and expense expended by Proposer in attempting to obtain a written executed contract with the City that complies with Section 432.070, RSMo, the City Charter and City ordinances.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 3 of 63

5.

ESTIMATED SCHEDULE

07/17/2013 08/01/13 2 p.m. 08/20/13 09/09/13 2 p.m. 10/7/13 10/14/13 – 10/18/13 October – November November – December Late December 2012 Early January 2013

RFP Issued Mandatory Pre-proposal Conference Deadline for questions Due Date for Proposals Notification of shortlisted firms Interviews if deemed necessary Selection/Negotiation Ordinance Process/ Council Approval Contract start date Estimated Project start date

The listed dates in the “Estimated Schedule” are tentative. The City reserves the right to change or extend any and all dates including the due date for proposals for any reason at any time including after the due date for proposals. 6.

RFP DOCUMENTS This RFP consists of the following documents: (a) This RFP (b) Scope of Services (c) Standard City Contract (d) HRD Form 6 Instructions

7.

EXAMINATION OF ALL RFP DOCUMENTS AND REQUIREMENTS (a)

Each proposer shall carefully examine all RFP documents and thoroughly familiarize themselves with all RFP requirements prior to submitting a proposal to ensure that Proposer’s proposal meets the intent of this RFP.

(b)

Before submitting a Proposal to the City, each Proposer shall be responsible for making all investigations and examinations that are necessary to ascertain any and all conditions and requirements that affect the requirements of this RFP. Failure to make such investigations and examinations shall not relieve the Proposer from Proposer’s obligation to comply, in every detail, with all provisions and requirements of the RFP.

(c)

By submitting a Proposal to the City, Proposer certifies that Proposer has provided the City with written notice of all ambiguities, conflicts, mistakes, errors or discrepancies that Proposer has discovered in the RFP, the Proposed Contract, Scope of Services and any other document. By executing a Contract with the City, Proposer certifies that Proposer communicated to City all ambiguities, conflicts, errors or discrepancies that it has discovered in the RFP, the Proposed Contract, Scope of Services and any other document and that written resolution thereof by the City as embodied in the final Contract is acceptable to Proposer.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 4 of 63

8.

QUESTIONS AND CLARIFICATIONS ABOUT THIS RFP (a)

(b)

Question Deadline (1)

Proposers may submit written questions, request clarifications or provide notice to the appropriate City Contact person listed in Section 3 of any ambiguities, conflicts, mistakes, errors or discrepancies that Proposer has discovered in the RFP, the Proposed Contract, Scope of Services and any other solicitation document at any time until one (1) week prior to the due date for proposals.

(2)

The City will answer all inquiries by any Proposer in writing. If any inquiry results in a change in the RFP, the City will issue an Addendum and the Addendum will be posted on the City’s website. It is the responsibility of Proposers to check the City’s website for addenda. http://www.kcmo.org

Questions - Post Deadline If a Proposer discovers any ambiguities, conflicts, mistakes, errors or discrepancies after the deadline for questions and clarifications or after the proposal due date, Proposer shall immediately submit the ambiguity, conflict, mistake, error or discrepancy to the appropriate City Contact person listed in Section 3. The City, in its sole discretion, shall determine the appropriate response to any issue raised by any proposer.

9.

SUBMISSION OF PROPOSALS All proposal documents must be submitted in the exact order as listed in the City RFP. (a)

Where. Proposers shall submit their Proposals to the appropriate City Contact Person listed in Section 3. Proposers shall address their Proposal to the City Contact Person and shall state on the outside of the sealed Proposal envelope the RFP No. and RFP title.

(b)

No. of Copies. Proposers shall submit one (1) signed original general proposal, one (1) copy in Microsoft word format and one (1) copy in Adobe PDF on a CD or DVD. Proposers shall submit one (1) signed original cost proposal, one (1) copy in Microsoft word or excel format and one (1) copy in Adobe PDF on a CD or DVD. The general proposal and the cost proposal may be submitted in the same box for mailing purposes, but the cost must be sealed in a separate envelope.

(c)

Format. In order to assure uniformity of the Proposals and to facilitate the evaluation process, all Proposals shall be organized and their parts labeled with tabs, as shown in Section 10. Each Proposal shall be presented in 12-point font on 8-1/2” x 11” paper, double sided. As part of the City’s green initiatives, Proposers shall limit all excess paper, division tabs, folders, etc., so the Proposals are as eco-friendly as possible.

(d)

Additional Materials. The Proposal also may contain any narrative, charts, tables, diagrams or other materials in addition to those called for herein; to the extent such additions are

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 5 of 63

useful for clarity or completeness of the Proposal. Attachments should clearly indicate on each page the paragraph in the Proposal to which they pertain. 10.

CONTENT OF PROPOSAL 10.1

Proposal Part I – Business/Firm Profile and Legal Structure          

10.2

Legal Name, address, phone, fax, email, Federal ID#, and website address. Brief history of business/firm including date the business/firm was established under the current name. List all services provided by the business/firm. Number of total employees including number of total employees in Kansas City, Missouri and number of employees in Greater Kansas City Area. Type of ownership, or legal structure of business/firm. Proof of financial capacity to perform this contract such as Dunn and Bradstreet, audited financial statements, bonding capacity. Has the business/firm ever failed to complete work for which a contract was issued? If yes, explain the circumstances. Are there any civil or criminal actions pending against the business/firm or any key personnel related in any way to contracting? If yes, explain in detail. Are there any current unresolved disputes/allegations? Provide a brief history of your business/firm contractual litigation, arbitration, and mediation cases for the last five (5) years that are material and relevant to this contract. Has your business/firm ever been disqualified from working for the City or any other public entity? If yes, explain the circumstances.

Proposal Part II – Experience 

Include a list of the five (5) most relevant or comparable contracts completed by your business/firm during the past five (5) years. For each listed contract, provide a narrative that includes: a. b. c. d. e.

the assigned project personnel scope of services provided dollar amount of the contract contractual performance standards versus your actual performance the contracting entity’s contact person, e-mail address, cell number, and telephone number f. summary of how your business/firm delivered services g. pricing and contractual compensation terms

  

Provide three (3) client references for similar projects completed by your business/firm during the past five (5) years. (See Attachment 3 – References) Provide a copy of your most recent relevant ongoing public contract. Provide a list of all public contracts entered into for the last three (3) years. Include the dollar amounts, summary of scope of services, contract terms, Public Owner’s contact person, e-mail address, cell number and telephone number.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 6 of 63

10.3

Proposal Part III – Personnel   

Please provide your staff capacity for meeting the City’s requirements. Identify the Key Employees who are likely to be assigned to this contract if your proposal is selected. [NOTE: Key Employee(s) must be committed to the contract duration, and may not be removed or substituted without the City's prior written consent.] For each of the Key Employee(s), provide a resume and/or summary with at least the following background information: a. b. c. d. e.

    10.4

Please comment on the ability of your business/firm to sustain the loss of Key Employee(s). Provide a staffing plan for the contract including the locations of the positions. Provide an organizational chart for the assigned staff. Provide a plan to address vacations, sicknesses and absences.

Proposal Part IV - Project Approach       

10.5

Description of relevant experience. Years of employment with the business/firm. City and State of residence. State time commitment on other accounts. Applicable professional registrations, education, certifications, and credentials.

Discuss your understanding of the project scope and objectives. Discuss your approach to a project with specific references to the services requested in the RFP. Highlight unique services and management tools and indicate the benefits of them to the City. What makes your business/firm better than the competition? Describe your Quality Assurance Plan. State approximate date your business/firm is available to begin work on the Project. Discuss your transition plan to begin providing services. Propose additional performance measures including why the performance measure is important and how the City will measure and verify performance.

Proposal Part V – Pricing Pricing must be submitted in a separately sealed envelope from the general proposal. 

10.6

Total Cost: Proposed Cost for everything requested in this RFP. Please break down the pricing as required by the Pricing/Cost Proposal Attachment. Include a detailed breakdown of the costs and hours associated with the phases of the project

Proposal Part VI – HRD Form 13  The completed HRD Form 13 – Affidavit of Intended Utilization

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 7 of 63

11.

12.

EVALUATION CRITERIA (a)

Any evaluation criteria or weighting of criteria is used by the City only as a tool to assist the City in selecting the best proposal for the City. Evaluation scores or ranks do not create any right in or expectation to a contract with the City regardless of any score or ranking given to any Proposer by the City. In other words, even if the City gives a proposer the highest rank and highest score, the proposer still has no expectation of a contract with the City and the City may choose to contract with any other proposer regardless of the score or rank of the other proposer.

(b)

The City may change criteria and criteria weights at any time including after the due date for proposals.

INTERVIEWS The City, in its sole discretion, may interview none, one, some or all of the Proposers that submit proposals.

13.

DISCUSSIONS AND NEGOTIATIONS The City, in its sole discretion, may do any or all of the following: (a) (b) (c) (d) (e) (f) (g) (h) (i) (j)

14.

evaluate Proposals and award a contract with or without discussions or negotiations with any or all of the Proposers; discuss and negotiate anything and everything with any Proposer or Proposers at any time; request additional information from any or all Proposers; request a Proposer or Proposers to submit a new Proposal; request one or more best and final offers from any or all Proposers; accept any Proposal in whole or in part; require a Proposer to make modifications to their initial Proposals; make a partial award to any or all Proposers; make a multiple award to any or all of Proposers; terminate this RFP, and reissue an amended RFP.

PROPOSAL MUST REMAIN FIRM IRREVOCABLE OFFER TO CITY FOR 90 DAYS (a)

By submitting a proposal to the City, Proposer agrees that Proposer’s Proposal shall constitute a firm irrevocable offer to the City that Proposer shall not withdraw or modify without the City’s approval for ninety (90) days after the proposal due date. Proposer agrees that even if the City negotiates or makes a counter offer to Proposer on Proposer’s original Proposal or any subsequent Proposal submitted by Proposer to the City, Proposer hereby grants to the City, in the City’s sole discretion, the unconditional right for the City to accept Proposer’s original Proposal and the City’s negotiation or counter offer shall not be deemed to be a counter offer.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 8 of 63

(b)

15.

After ninety (90) days, the City can accept any proposal or subsequent proposals from any Proposer with the consent of the Proposer at any time and regardless of the length of time that has passed from the proposal due date.

SELECTION The City will select the proposal that in the City’s sole judgment the City determines to be the best Proposal. Section 432.070, RSMo requires the City to have a written executed contract signed by both parties prior to anyone performing services or providing any goods, supplies, materials or equipment to the City. The written executed contract must also comply with the City Charter and City Ordinances. This means that a proposer does not have a contract with the City until a written contract is “executed.” A contract is “executed” when all of the following have occurred: (1) the City Council authorizes the execution of a contract with the proposer (if City Council approval is requested by City staff or is required by City Ordinance); (2) persons with actual authority to bind both the City and the Proposer execute the contract; (3) the contract is approved by the Law Department; (4) the City issues a purchase order to the Contractor with the Director of Finance’s certification of availability of funds for the contract; and (5) any other required step. A proposer does not have a contract with the City until all the steps are completed. If the City does not complete all required steps, there is no contract between the City and the proposer and the City has absolutely no contractual or financial obligation to any proposer regardless of the amount of time, effort and money spent by the proposer responding to the RFP and attempting to negotiate and obtain a contract with the City.

16.

REJECTION OF PROPOSALS The City reserves the unconditional right to reject any or all proposals received in response to this RFP at any time prior to the City executing a contract that meets the requirements of Section 432.070, RSMo, the City Charter and all applicable City Ordinances.

17.

18.

WAIVER OF ORDINANCES, REGULATIONS AND RFP REQUIREMENTS (a)

The City, at any time, may waive any requirements imposed in this RFP or by any City regulation.

(b)

The City, may waive any requirement imposed by the City’s Code of Ordinances when failure to grant the waiver will result in an increased cost to the City and the requirement waived would be waived for all Proposers for this RFP and it is in the best interest of the City to grant the waiver.

LATE PROPOSALS The City, in its sole discretion, may consider proposals received by the City after the proposal due date if: (1) the proposal is sent via the U.S. Postal Service, common carrier or contract carrier, by a delivery method that guarantees the proposal will be delivered to the City prior to the proposal due date; or (2) if the proposal is submitted by mail, common carrier or contract carrier it is determined by the City that the late receipt was due to the U.S. Postal Service, common carrier or contract carrier; or (3) the proposal is timely delivered to the City, but the proposal is at a different City location than that specified in this RFP; or (4) the City extends the due date after the deadline for a

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 9 of 63

force majeure event that could potentially affect any or all Proposers meeting the deadline; or (5) the City has not opened any of the proposals; or (6) it is in the best interest of the City to accept the proposal. 19.

20.

21.

CHANGES IN THE RFP (a)

After this RFP is issued, the City, in its sole discretion, may change everything or anything contained in this RFP at any time including after the Proposal due date. If the change is prior to the proposal due date, the City reserves the right, when considered necessary or appropriate, to modify this RFP.

(b)

If the City shall amend the RFP after the proposal due date, the City may, in its sole discretion, solicit new proposals in an amended RFP from anyone or everyone regardless whether a person submitted a proposal in response to the original RFP.

CHANGES IN EXECUTED CONTRACT AND ADDITIONAL WORK (a)

After the City executes a contract in accordance with the requirements of Section 432.070, RSMo, the City Charter and City Ordinances, the City may, in its sole discretion, amend the contract to change anything or everything associated with the contract as long as such change is in the interest of the City and as long as the Contractor agrees to the change.

(b)

The City, in its sole discretion, may award additional contracts for related work or subsequent Project phases to the selected Contractor.

(c)

The City, in its sole discretion, may extend the term of the contract with the selected Contractor notwithstanding the expiration of the initial term or any subsequent term or all options to renew, until the City has a new contract in place with either Proposer or another provider or until the City terminates the Contract.

PROPOSER SOLELY RESPONSIBLE FOR ALL COSTS Regardless of the amount of time, effort, cost and expense incurred by a Proposer in Proposer’s attempt to win this City contract, Proposer agrees that Proposer shall be solely responsible and liable for any and all costs incurred by Proposer. The City shall have no liability or responsibility for any of Proposer’s costs or expenses.

22.

OWNERSHIP OF PROPOSALS By submitting its Proposal, Proposer hereby agrees that Proposer’s Proposal and any supplementary material submitted by the Proposer shall become property of the City.

23.

DISCLOSURE OF PROPRIETARY INFORMATION (a)

A Proposer may attempt to restrict the disclosure of scientific and technological innovations in which the Proposer has a proprietary interest, or other information that is protected from public disclosure by law, which is contained in the Proposal by:

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 10 of 63

24.

1.

marking each page of each such document prominently in at least 16 point font with the words “Proprietary Information”;

2.

printing each page of each such document on a different color paper than the paper on which the remainder of the proposal is printed; and

3.

segregating each page of each such document in a sealed envelope, which shall prominently display, on the outside, the words “Proprietary Information” in at least 16-point font, along with the name and address of the Proposer.

(b)

After either a contract is executed pursuant to the RFP, or all submittals are rejected, if access to documents marked “Proprietary Information”, as provided above, is requested under the Missouri Sunshine Law, the City will notify the Proposer of the request, and it shall be the burden of the Proposer to establish that such documents are exempt from disclosure under the law.

(c)

If the Proposer elects to challenge a formal request for such information made to the City and if the Proposer is unsuccessful in keeping such information closed, the Proposer shall pay for any and all costs, attorney fees and fines that are a result of Proposer’s attempt to keep the information closed.

(d)

Notwithstanding the foregoing, in response to a formal request for information, the City reserves the right to release any documents if the City determines that such information is a public record pursuant to the Missouri Sunshine Law. The City shall have no liability to any Proposer or anyone else for releasing any Proprietary Information of a Proposer even if the City is negligent in releasing or disclosing any Proprietary Information of any Proposer.

CLOSED RECORDS All Proposals including interviews, presentations and documents and meetings relating thereto may remain closed records or meetings under the Missouri Sunshine Law until a contract is executed or until all Proposals are rejected by the City. If the City amends this RFP, Proposals submitted in response to the original RFP may remain closed records until a contract is executed or all proposals submitted in response to the amended RFP are rejected. Proposals shall remain closed records even if the City mistakenly informs all Proposers that it is rejecting any and all Proposals prior to amending the RFP as long as the City intends to amend the RFP and resolicit Proposals.

25.

AFFIRMATIVE ACTION It is the policy of the City that any person or entity entering into a contract with the City, will employ applicants and treat employees equally without regard to their race, color, sex, religion, national origin or ancestry, disability, sexual orientation, gender identity or age. The City’s Affirmative Action ordinance requires that any person or entity who employs fifty (50) or more persons and is awarded a contract from the City totaling more than $300,000.00 must: (a)

Execute and submit an affidavit, in a form prescribed by the City, warranting that the contractor has an affirmative action program in place and will maintain the affirmative action program in place for the duration of the contract.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 11 of 63

(b)

Submit, in print or electronic format, a copy of the contractor’s current certificate of compliance to the City’s Human Relations Department (HRD) prior to receiving the first payment under the contract, unless a copy has already been submitted to HRD at any point within the previous two calendar years. If, and only if, contractor does not possess a current certification of compliance, contractor shall submit, in print or electronic format, a copy of its affirmative action program to HRD prior to receiving the first payment under the contract, unless a copy has already been submitted to HRD at any point within the previous two calendar years.

(c)

Require any subcontractor awarded a subcontract exceeding $300,000.00 to affirm that subcontractor has an affirmative action program in place and will maintain the affirmative action program in place for the duration of the subcontract.

(d)

Obtain from any subcontractor awarded a subcontract exceeding $300,000.00 a copy of the subcontractor’s current certificate of compliance and tender a copy of the same, in print or electronic format, to HRD within thirty (30) days from the date the subcontract is executed. If, and only if, subcontractor does not possess a current certificate of compliance, contractor shall obtain a copy of the subcontractor’s affirmative action program and tender a copy of the same, in print or electronic format, to HRD within thirty (30) days from the date the subcontract is executed.

If you have any questions regarding the City’s Affirmative Action requirements, please contact HRD at (816) 513-1836 or visit the City’s website at www.kcmo.org 26.

TAX CLEARANCE FOR CITY Prior to the City making the first payment under any contract or contract renewal term, Contractor must provide a tax clearance letter from the City’s Commissioner of Revenue dated not more than ninety (90) days from the date of submission. Proposers may obtain this tax clearance letter from the City’s Revenue Division at (816) 513-1135 or (816) 513-1089. http://www.kcmo.org

27.

INDEMNIFICATION The City’s standard contract requires that the Contractor shall indemnify, defend and hold harmless the City and any of its agencies, officials, officers, or employees from and against all claims, damages, liability, losses, costs, and expenses, including reasonable attorneys’ fees, arising out of or resulting from any acts or omissions in connection with the contract, caused in whole or in part by Contractor, its employees, agents, or Subcontractors, or caused by others for whom Contractor is liable, including negligent acts or omissions of the City, its agencies, officials, officers, or employees. The contract requires Contractor to obtain specified limits of insurance to insure the indemnity obligation. Contractor has the opportunity to recover the cost of the required insurance in the Contract Price by including the cost of that insurance in the Proposal.

28.

BUY AMERICAN AND MISSOURI PREFERENCE POLICIES (a)

Buy American Preference

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 12 of 63

It is the policy of the City that any manufactured goods or commodities used or supplied in the performance of any City contract or any subcontract thereto shall be manufactured or produced in the United States whenever possible. When proposals offer quality, price, conformity with specifications, term of delivery and other conditions imposed in the specifications that are equal, the City shall select the proposal that uses manufactured goods or commodities that are manufactured or produced in the United States. (b)

Buy Missouri Preference It is the policy of the City to give preference to all commodities manufactured, produced, or grown within the State of Missouri and to all firms, corporations, or individuals doing business as Missouri firms, corporations, or individuals, when the quality is equal or better and delivered price is the same or less. It is the Proposer’s responsibility to claim these preferences.

29.

MISSOURI SECRETARY OF STATE BUSINESS ENTITY REGISTRATION Prior to execution of a contract with the City, the apparent successful Proposer must submit a current copy of Proposer’s Certificate of Good Standing from the Missouri Secretary of State’s website at http://www.sos.mo.gov.

30.

CITY OF KANSAS CITY MISSOURI BUSINESS LICENSE Prior to execution of a contract with the City, the apparent successful Proposer must submit a current copy of Proposer’s valid business license. Proposers may obtain this business license from the City’s Revenue Division/Business License section at (816) 513-1135 or at http://www.kcmo.org.

31.

PROHIBITED ACTIVITIES BY FORMER CITY EMPLOYEES AND OFFICIALS Section 2-1018 of the City’s Code prohibits former elected City officials and former executive or administrative employees of the City from trying to influence a decision of the City on behalf of an employer or client for one (1) year after that former employee or official leaves the City’s employ. By submitting a proposal, Proposer affirms that Proposer and its team members and employees are in compliance with the requirements of Section 2-1018. Failure to comply with the requirements of Section 2-1018 may cause the Proposal to be rejected.

32.

MBE/WBE GOALS (a)

The City desires that City certified Minority Business Enterprises (MBEs) and City certified Women Business Enterprises (WBEs) have a maximum opportunity to participate in the performance of City contracts. The MBE/WBE participation goals for this Project are 2% MBE participation and 2% WBE participation.

(b)

The City’s HRD Forms and Instructions are incorporated into this Request for Proposals and the Contract Documents.

(c)

Please complete the form HRD 13 Affidavit of Intended Utilization and return it with your Proposal. The City of Kansas City, Missouri has a list of City Certified MBEs/WBEs at

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 13 of 63

http://kcmo.org/CKCMO/Depts/CityManagersOffice/HumanRelationsDivision/Disadvantaged MinorityandWomenBusinessEnterpriseSection/index.htm (click on “DMWBE Directory Search”). Please contact the City’s Human Relations Department at 816-513-1836 for assistance on any aspect of the MBE/WBE program. 33.

WAIVER OF MBE/WBE REQUIREMENTS The City Council, in its sole discretion, may waive any and all MBE/WBE requirements imposed by this solicitation and any Proposal Documents or the MBE/WBE Ordinance, and award the contract to the best Proposer if the City Council determines a waiver is in the best interests of the City.

34.

COOPERATIVE PROCUREMENT WITH OTHER JURISDICTIONS Proposer must acknowledge acceptance or decline by returning the “Cooperative Procurement with Other Jurisdictions” form found under Section III - Special Instructions and Conditions.

35.

MANDATORY PRE-PROPOSAL CONFERENCE

(a)

When:

(b)

Where:

(c)

Mandatory:

The City will hold a Mandatory Pre-Proposal Conference. It will be on Thursday, August 1, 2013 at 2 P.M. Procurement Services Division City of Kansas City, Missouri 1st Floor, Conference Room, City Hall 414 East 12th Street Kansas City, MO 64106 If a representative of your business/firm does not attend the Mandatory Pre-Proposal Conference, your business/firm cannot submit a proposal for this RFP to the City and the City cannot consider your proposal.

For persons with disabilities needing reasonable accommodations, please contact Robert Rives at 816-513-2532. If you need to use the Relay Service, please dial 711.

36.

PERFORMANCE BOND A Performance Bond is required in the amount of the final contract amount. The Performance Bond Template is located in Attachment 5.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 14 of 63

SECTION II REQUEST FOR PROPOSALS NO. EV1788 FOR ENTERPRISE PERMITTING SYSTEM SCOPE OF SERVICES 1.

STATEMENT OF NEED The City of Kansas City is seeking a solution for an Enterprise System for managing and tracking of Land, Permitting, Zoning, Inspections and Licensing process for improved customer service and efficiency for citizens. The system should have Open Architecture to easily integrate via web services or API to other City software systems. The proposed solution should include a state of the art user friendly workflow management system where data can be entered once and shared across multiple modules and subsystems. The system should have the review and approval capability to collaborate with contractors and applicants. The system should also have robust security setup as different departments will be participating in the work flow. The new system should be user friendly and intuitive in data analysis such as creating reports, queries and form. The City is also looking for easier way for the staff to support the system and reduced annual maintenance cost. It is the City’s desire to select and implement a commercial-off-the shelf (COTS) software solution to replace the current software, as well as improve business processes through the software implementation. The City is open to a 3rd party hosted solution or one hosted by the City. The solution should also be accessible at remote sites via handheld devices, laptops, and/or iPads. The solution should be accessible through City internet and intranet sites based upon site security rules. The City of Kansas City should be able to setup the system to define parameters specific to their organization. In addition, the solution should have role-based security profiles tied to specific modules, functions, queries, reporting capabilities including transaction audit logs. It is preferable City staff security is integrated with Microsoft Active Directory. Security must also be available to set up external users to appropriate access to different modules and components. Some departments (City Planning and Development and others) will utilize the electronic document submittal and approval process of drawing etc., which should also allow for citizen/applicant use. The system should provide the tools needed to perform and manage a multi-agency review and approval of submitted plans and documents. Integration with the City’s PeopleSoft Enterprise system, Oracle Database, ESRI GIS, Asset Management systems, Outlook/Exchange, MS Office suite, and other systems are required for this solution as described in the requirements document. The desired solution must be user friendly and simple to navigate with the ability to retain extensive history, and audit trails. The City is looking for an economical Licensing module and the City prefer an enterprise licensing module.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 15 of 63

2.

OBJECTIVE a. The objective of the Project is to replace the current systems with a modern integrated online enterprise solution to meet the needs of the City of Kansas City, Missouri as specified in this scope and in attachment A, functional requirements. b. The selected system will provide permitting, land management, inspection and enforcement (including work order) activities, and licensing. c. Intended systems to be replaced include the current permitting system, KIVA, current implementation of Energov and Paragon, current Field Services implementation d. The new system should interface with multiple other City systems to provide visibility to City activities as listed in the requirements. e. Provide a work flow process to support citizens licensing, permitting and Land Management activities. f. Provide online access to citizens and to city staff.

3.

BACKGROUND The current permitting system, KIVA, is at end of life and is difficult to support, maintain, and configure. Also the multiple permitting, inspection and licensing systems such as KIVA, Energov, Paragon and PeopleSoft’s Field Services can make efficiencies and customer service difficult for City Staff and citizens who need to interact with the City.

4.

HIGH LEVEL SCOPE OF WORK a. The successful vendor will interview and discuss with the different Departments/Divisions (Approximately 10) to understand their work process to finalize the detailed requirements including the required reports, forms, queries and letters etc. and to understand their interdependencies and make suggestions to improve the efficiency where required. b. The chosen solution will be implemented into the City of Kansas City, Missouri technology environment. The Vendor will provide and configure the selected system. Vendor will also provide and/or develop agreed upon customizations. Documentation will be provided for all aspects of the system. The selected system will be implemented to satisfy the requirements and achieve the scope and objectives of the project. c. The chosen Vendor will work with the City’s IT and functional staff on all aspects of the implementation and project. d. Purify, validate and convert the data from the existing systems (KIVA, InterGov, Paragon and Field Services). e. Test the product (unit testing, end to end testing, usability testing etc.). f.

Setup test, development, and production environments (may also include training and staging environments.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 16 of 63

g. Conduct required training and produce documentation for future use. h. State the Hardware requirement and its maintenance. i.

5.

Any subcontractors utilized to complete the scope of work must be identified in bidder’s proposals. Each component should be integrated with the other components.

SUPPLIER SERVICES AND DELIVERABLES In general, the proposer must complete the following tasks: a. Provide a solution that consists of an Enterprise Permitting Solution that can be accessed by both the Citizen and City Staff using different mobile and desk top devices. b. The proposed solution may consist of one or more software packages as required to meet the specific functional requirements. c. Vendors are encouraged to use existing elements of the City’s technology environment to meet the functional requirements. d. Emphasis is placed on a commercial off the shelf (COTS) solution however it may consist of some developed software as required to meet the functional requirements e. Integrate the component parts of turnkey solution within itself and into City’s PeopleSoft Enterprise system, Oracle Database, Revenue System, Asset Management, Outlook/Exchange, MS Office suite, e-builder, ESRI GIS system and other systems as mentioned elsewhere f. Implement the turnkey solution according to the acceptance standards of the City of Kansas City g. Complete data conversion from the existing systems (KIVA, Paragon, PeopleSoft Field Services and EnerGov) into the proposed system logically which will facilitate in extracting the required data for the future reporting etc. h. Develop and conduct training on the solution for system administrators, train the trainers, power users, end users, etc. including training manuals and other documentation as required i. Provide ongoing support and maintenance for the proposed solution *The

City has listed below some specific deliverables required but, but reserves the right to identify other deliverables which will be identified and agreed upon between The City and the Proposer during negotiations and will be incorporated as part of the project plan and payment milestones in the final contract. 5.1

Project Management For this section of the proposal, Proposer must submit a narrative that fully describes the approach, methods, tools, and techniques for managing the project to achieve the goals and objectives stated by the City. Proposer must also submit a Project plan that will be used to create a consistent, logical management plan of action that will be used to guide the Project execution and control the project. The Project Plan must include sufficient detail to give City an understanding of Proposer’s approach to a successful implementation.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 17 of 63

Supplier must provide a Project Manager to directly manage all activities. City will provide a Project Manager to oversee the entire project. As a part of project management duties, Supplier must attend informational, status and any other project related meetings as designated by City. Project deliverables and activities will follow a rigorous quality management process. The following activities are required to achieve this: 5.1.1

Management of Supplier Staff City will provide oversight for the entire project. However, Supplier must provide overall project management for the tasks in the Contract, including the day-to-day management of its staff. Supplier must provide administrative support for its staff and activities. Any staffing changes must be reviewed and approved by City prior to any reassignments.

5.1.2

Project Plan/Updates Within the first four (4) weeks of beginning work, Supplier must refine the detailed Project Work Plan and Resource Schedule using Supplier’s Scheduling tool and should be able to export into Microsoft Project. . These documents must be refined and approved by City before the project continues. This document must contain the following: a. A consolidated view of the work to be performed b. Project activities, task assignments, due dates and resources for both Supplier and City. Dependencies and constraints should be identified. c. Project Milestones clearly identified (Hardware, Software, Testing, Training, etc.) Note the payment schedule should be based on milestones.

5.1.3

Kick-Off Meeting Supplier and City will conduct a joint kick-off meeting.

5.1.4

Status Meetings Throughout the project, Supplier Project Manager and City Project Manager will attend regular status meetings. The meetings must follow a pre-set agenda but must also allow Supplier or City the option to discuss other issues that concern either party. Supplier shall provide written documentation (minutes with items discussed and action items assigned) from each meeting.

5.1.5

Issues Tracking, Analysis and Escalation The creation and updating of these documents, which are part of the overall Project Plan, are the joint responsibility of Supplier Project Manager and the City Project Manager must be refined and approved by the City.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 18 of 63

5.1.6

Change Management Supplier must use, in conjunction with the City’s PMO office, a written Change Management Plan which establishes the Change Management roles and responsibilities, policies, guidelines, processes and procedures necessary for controlling and managing the changes, both technical and other, during the life of the Project. This documented plan will describe how changes are identified, defined, evaluated, approved, and tracked to completion. The Change Management plan should include a Communications plan describing planned communications methods, documents, and audience.

5.1.7

Status Reports City Project Manager will require status reports on a weekly basis. Supplier must provide electronic status reports on the project, every Thursday by Noon. Supplier Project Manager will be given a template to follow. Some information that will be required is as follows: a. Tasks Accomplished b. Any deadlines met or missed c. Any issues encountered and their status or the need to be addressed before proceeding to the next task(s) d. Anticipated tasks to be completed in the next week e. Updated project schedule

5.1.8

Supplier Deliverables Must include a. Updated Project Strategy, Work Plan, and Resource Schedule b. Issues Tracking, Risk, and Communication Plans c. Change Management Plan

5.3

Systems Analysis and Design For this section of the proposal, Proposer must submit a narrative of how Proposer will use systems analysis techniques to affirm the requirements identified for the project. Proposer must fully describe its design approach, methods, tools, and techniques for completing the technical design process. Proposer must depict the design in sufficient detail to allow City to verify that the design meets all the requirements contained in this RFP. Proposer must perform a detailed review and analysis of the requirements and develop the detailed technical specifications required to allow Proposer technical staff to develop/configure the new SOFTWARE for City. The following activities are required to achieve this:

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 19 of 63

5.3.1

System Usage Analysis Supplier must assist City in analyzing how the software can be used to meet City’s requirements for processes, reports, correspondence and other functionality.

5.3.2

Interface Plan and Designs City requires automated interfaces as part of this project. In order to reduce the development and maintenance effort associated with these interfaces, City requires that all inbound and outbound system interfaces be funneled through a standard interface facility/utility. This software must be fully documented to allow City to properly structure current and future interface projects. Supplier must also provide City with a plan, which identifies, analyzes and schedules the interfaces to be developed and implemented. This plan document must cover the identification and resolution of data translation issues and must recommend appropriate strategies and approaches. The plan must also address the sequence in which the interfaces must be developed and moved to production. Any temporary interfaces must also be included in this document. Supplier will also be responsible for producing designs in accordance with the approved Interface Plan.

5.3.3

Custom Report Design

For reporting purposes, Crystal Reports, Oracle report writer, Access/Excel and other software specific reporting tools are being used depending on the software. (Please describe all applicable reporting tools that can be used with the software. The City of Kansas City requires the selected Supplier to provide an agreed upon amount of customized reports. Bidders should include pricing for this in the cost proposal. In addition, standard reports and data download should be provided as described in Attachment A (requirements). . The Supplier and City can also discuss query alternatives where applicable in place of some reports. With the anticipation that City technical staff will be responsible for creating and customizing additional reports after implementation, the supplier must provide design services during the project as well as comprehensive training to City technical staff covering the detailed explanation of the applicable database structure and relationships 5.3.4

Custom Correspondence Design Custom outbound correspondence to be generated by the project will be required to meet the unique needs of City. With the anticipation that City staff will eventually be responsible for creating and customizing correspondence, the Contractor must provide design services during the project as well as comprehensive training to City Staff. City expects custom correspondence forms will be required for the implementation.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 20 of 63

5.3.5

Supplier Deliverables Must include a. Requirements Validation and System Usage Document b. Correspondence, reports, interfaces, and other custom programs or modifications) c. Interface Design and Interface Plan

5.4

Technical Services For this section of the proposal, Proposer must submit a narrative describing how configuration of the solution will be organized, documented, tested, and coordinated with design and development activities. Configuration deliverables must be fully described, as well. Proposer must also describe the development approach and how such development of site-specific code can be performed without affecting the upgrade path. It must also describe methods, tools, and techniques for completing the development process. City requires Supplier to lead the technical tasks associated with installing, configuring and tuning the hardware, software and database to ensure software readiness for production operations. The following activities are required to achieve this: 5.4.1

Technical Environment Design Supplier will work closely with City technical staff to plan and design all technical environments needed on the project (including all project and production environments and related network configuration).

5.4.2

Technical Environment Setup and Maintenance Supplier must work closely with City technical staff to setup and maintain all technical environments used during the course of the project (as required by the schedule included in the approved Project Plan). City IT resources will assist Supplier with physically installing the hardware and operating system using Supplier’s documentation and configuration options. Such environments will include: a. b. c. d.

5.4.3

Sandbox/Development environment Testing environment Training environment Production environment

Performance Testing and System Tuning Supplier must conduct performance testing and system tuning for the fully configured and tested software prior to commencing live operations and at a preliminary point in the project sufficiently in advance of the implementation date to allow reasonable tuning. These tasks will be coordinated and performed with City Project Manager, City Project Team Leaders, City System Support Staff, Database Administrators, and

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 21 of 63

Application Development staff. When modifications are made to the application software to meet City’s unique requirements, Supplier must review and make adjustments to ensure acceptable performance. 5.4.5

Hardware As Part of City Project Supplier must describe the optimal proposed hardware and configuration for all project, test and production technical environments in sufficient detail to allow City to purchase all needed components independent of the proposal if it proves advantageous. Supplier must include estimates of sufficient storage space for project archives and storage of electronically submitted documents, and all templates, standards, etc. Supplier should also estimate storage growth to support the system. Supplier will work closely with City to install the necessary hardware and operating systems. The proposal should also include an offsite Disaster Recovery System. Supplier must assist City IT system administrators with configuring, and testing the servers, server peripherals, utilities, and system management software. The Supplier should provide the minimum required specification for the desk top PCs to use the system successfully.

5.4.5

Installation of Application Software Supplier will work closely with City to install all required supplier and third-party software and assist City in verifying that: all modules are present and installed and the system operates in a stable fashion. Supplier will also ensure all related documentation is completed which will include but is not limited to: Application and system software configuration parameters definitions, hardware requirements, installation procedures, operations instructions, backup and restore procedures, and other operations functions. Supplier must also perform all setup, installation, and verification for all project environments including the development, testing, training, and production environments.

5.4.6

“Sand box” Set-up Supplier will assist City IT staff with setting up a “sandbox”/development environment to help users become familiar with the system. This environment can also be used by Supplier to conduct demos, education sessions, and walkthroughs of how RFP requirements have been met. It must be kept current by Supplier as the project progresses. Supplier will also provide City with all tools and utilities required to automatically refresh the environment after training sessions and to automatically maintain the environment and apply changes to the application system software and databases as future changes are implemented within the Production environment.

5.4.7

Configured Software Supplier will work closely with City project team members, subject matter experts and technical personnel in meeting City process, workflow, and functional requirements via software configuration wherever it is feasible. Supplier must demonstrate the configured software as required during the project so City staff may

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 22 of 63

review and approve it. Approved configurations must be rigorously unit tested and documented as well. 5.4.8

Interface Application Software Based on the Interface Plan and Interface Design document, Supplier will be responsible for completing: a. Program specifications b. Interface programs c. Unit and integration testing of the interface programs Supplier will also be responsible for testing the interfaces and demonstrate to City that the interfaces work.

5.4.9

Supplier Deliverables Must include a. b. c. d. e.

5.5

Technical Environment Design Technical Environment Installation and Setup Performance Testing and System Tuning Installed Software (having assisted City) Configured Software and Client-Specific Programming (including interface programs)

Data Conversion For this section of the proposal, Proposer must submit a comprehensive data conversion plan which includes, tools, methodology, time lines and addresses the requirements in this section. While the City expects the Supplier to be responsible for completing all data conversion activities for data identified by City staff, supplier should indicate the expected amount of time required for the data conversion from City staff. The following activities are required to achieve this: 5.5.1

Data Conversion Plan Supplier must produce a comprehensive data conversion plan. The plan must cover all aspects of creating the production database necessary to take the system “live”. 5.5.1.1 This plan must describe:  

All tables to be built in the new system Field-level specific data sources for those tables (data mapping scheme that identifies any data parsing, concatenation, format changes)

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 23 of 63

      

5.5.2

Expected data volumes Conversions where automated programming will be used to significantly reduce data conversion labor Conversion verification logic (e.g. counts of financial, project and other records converted with summary totals, Roles and responsibilities and timing requirements for the conversion effort A conversion test plan A plan to identify and handle exceptions The City expects the historical data to be converted. The data to be converted may come from the KIVA, PeopleSoft, Energov, Paragon, Field Services, E-builder or other systems. Supplier should indicate experience with data conversions from these systems.

Data Conversion Programs

Based on the Data Conversion Plan, Supplier will be responsible for creating and testing automated conversion programs to support “go-live”. This includes developing programming specifications, coding, unit and integration testing for the conversion programs. City will be responsible for developing test scenarios and conducting the acceptance testing with the assistance of Supplier. As part of this effort Supplier must build any crosswalk file structures required. Supplier must provide a letter certifying that the programs utilized for conversion are error-free and fit for the task of performing the conversion into the new software. 5.5.3

Converting Data Supplier must be responsible for running the conversion programs and assisting City with the verification of the converted data in the production environment. The City expects the supplier to be responsible for data conversion from the current systems or manual entry into the selected system. City will take responsibility for certifying the production database as being accurate. Supplier will be responsible for adapting and re-running conversion programs as necessary to properly convert and load the data.

5.5.4

Supplier Deliverables Must include a. Data Conversion Plan b. Converted Data in Production Database c. Letter certifying the programs are ready to be utilized for conversion

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 24 of 63

5.6

Testing For this section of the proposal, Proposer must submit a description of the testing strategies and approach, methods, tools and techniques for unit, systems, user acceptance, load and regression testing. All system components must be subjected to system testing performed by a test team composed of Supplier and City staff. Supplier will perform unit, system and integration testing, and will facilitate and assist City with their system testing and acceptance testing responsibilities. Supplier will also assist City with test and error identification and resolution. The following activities are required to achieve this: 5.6.1

System /User Acceptance Test Plans Supplier must facilitate and assist City with the preparation of system and user acceptance test plans that are built around City’s most important business scenarios but will include comprehensive testing of the software to ensure that it conforms to requested functionality. It will also verify that: a. The new, configured, modified and unmodified software work in the same environment b. The system has been properly configured for use for City c. Reports and correspondence work in accordance with City requirements d. All scripts or jobs run correctly and timely e. All interfaces function properly f. Test cycles are structured g. All test tracking, outcome tracking, and exception follow-up procedures are organized

5.6.2

Application System Testing Supplier will be responsible for conducting system tests in accordance with the approved system test plans. All system test results must be documented, exceptions analyzed and any software defects corrected. Supplier will work with City Quality and Project Team through the system test process so to verify completion of the test process. This test must be thorough enough to ensure that minimal software or configuration “bugs” are uncovered in the User Acceptance Testing which will follow. Minimal software and configuration bugs are defined as no significant defects that would delay the timely completion of User Acceptance Test.

5.6.3

User Acceptance Test Scripts Supplier will work with City in the preparation of the User Acceptance Test Scripts. The User Acceptance Test Scripts will include the following: a. Explanations of test scenario b. User actions c. Expected outcomes

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 25 of 63

5.6.4

User Acceptance Testing Assistance Supplier will assist City with conducting user acceptance testing of the entire application. Successful completion of these tests shall be required before the software can be approved for production use. This assistance shall include: a. Analyzing and explaining outcomes b. Answering questions as they arise c. Making required changes to the software and documentation as required

The Supplier is required to ensure that the system is functional and operational before scheduling acceptance testing or final acceptance with the City of Kansas City personnel. 5.6.5

Supplier Deliverables Must include a. b. c. d.

5.7

System/User Acceptance Test Plan Application System Testing User Acceptance Test Scripts User Acceptance Testing Assistance

Training/Knowledge Transfer For this section of the proposal, Proposer must submit a description of the training options available to City that will provide a logical knowledge transfer process to the functional, administrative, and technical/operations personnel to support the system upon Supplier’s departure. The Supplier should include different training methods and approaches (i.e. classroom, train-the-trainer, one-on-one, web based, etc.). The City would like to have pricing for each method; however, the City would like the Supplier to recommend a training method and utilize City data during training sessions City staff requiring training will represent a wide cross-section of the employee population. They include system programmers, systems administrators, user support staff, application development staff, operations support personnel, network technicians, and users ranging from administration to senior managers and executives. The training solution must serve the needs of this diverse group. The following activities are required to achieve this: 5.7.1

Project Team Training Supplier must provide training to the project team. This training must cover: a. System architecture, navigation and functionality b. Configurable components and system options c. Online and batch operations i. Security

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 26 of 63

ii. Developing desk level procedures iii. Organizing for the cutover iv. Managing operations during the cutover to the new system d. Establishing procedures for providing user support e. Other relevant topics helpful to project team members in planning organizing, and executing their assigned project roles as well as follow up training, if needed. 5.7.2

Training/ Knowledge Transfer Plans Supplier must provide a detailed training plan. The Training Plan will be based on a comprehensive training needs assessment conducted by Supplier and City and must also describe the types of training to be employed to meet the identified needs. Supplier must also work in conjunction with City staff to document the knowledge transfer activities that will occur in each phase of the project, how they will occur, and the individuals responsible for each activity. As part of the plans produced, Supplier will document the tasks and assignments that City staff will perform to facilitate knowledge transfer. Formal sign-off is mandatory for all Knowledge Transfer Plans.

5.7.3

Training Curriculum/Materials Supplier will identify and document the training curriculum that will be used to educate and train City staff to develop and support the new software. Supplier must also assist City to develop all training materials including training guides, speaker notes, syllabi, and user materials. Supplier must also work with assigned City staff to incorporate policy, procedure, and specific personnel roles into the materials. All training materials must be reviewed and approved by City prior to the start of training. Supplier must provide all electronic source documents and graphics used in the development and presentation of training.

5.7.4

User Training Please describe the user training approach which will be conducted by Supplier to assist City in training employees who will be using the new system. Supplier must provide: Classroom materials to support the classroom training effort; Best practices on training for the proposed software; How to customize the training materials and set up specific reference data in the training environment. Supplier will also provide troubleshooting assistance when end user training is conducted.

5.7.5

Technical and Operations Personnel Training Supplier must supply classroom and substantial hands-on training to ensure that City IT staff has the necessary skills to operate and maintain the system during the post implementation period. Such training must include: systems operations including system startup, backup and recovery, nightly batch operations, workflow, security

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 27 of 63

running of ad-hoc, monthly, and annual jobs, and any other tasks necessary to operate the system. This would include Training on any components of the operating environment that are new to City and on the use of any new development tools related to the system. 5.7.6

Training Facilities/Equipment All of the training is expected to take place at City facilities. City will provide training facilities in which Supplier must use for conducting training for which it is directly responsible. City will rely on the Contractor to recommend the appropriate mode (e.g. classroom, one-on-one, auditorium) in which the training will be conducted. City has not yet determined the minimum or maximum number of users per session and would like Supplier to suggest optimal session sizes.

5.7.7

Supplier Deliverables Must include a. b. c. d. e.

5.8

Project Team Training Training /Knowledge Transfer Plans Training Curriculum/Materials Technical and Operation Personnel Training Training agendas, manuals (hard and soft copies, and quick reference guides for the City personnel

System Implementation/Post Implementation Support For this section of the proposal, Proposer must submit a narrative that fully describes the approach, methods, tools, and techniques for deploying/installing the new system and maintaining software operation throughout the warranty period as well as the life of the system. City requires an extensive and carefully structured approach to the implementation of software. This includes the organization and execution of cutover activities necessary to transition City staff to the new system. Supplier must provide on-site support throughout the entire implementation period. The following activities are required to achieve this: 5.8.1

Implementation Plan Supplier must produce an implementation plan that lists and describes activities needed to successfully implement the software. The plan must detail the approach for coordinating the following: Final data conversion activities; Technical preparation and system changeover activities; Development of an implementation activities check list; Staffing requirements, by role and responsibilities, for both Supplier and City staff for all implementation activities; an Implementation schedule; The process for developing a contingency plan for identifying, communicating, resolving risks and maintaining the current production capability if the implementation is delayed.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 28 of 63

5.8.2

Implementation Readiness Supplier must provide an Implementation Readiness Letter that certifies that the software is ready for implementation. The Readiness letter must confirm: All staff has completed training; User Acceptance Signoff has been obtained from the stakeholders; All data has been converted cleaned and formally, in writing, accepted by City; All site preparation requirements have been met; User Support is established and all user and system supports are in place.

5.8.3

Implementation Report Supplier must implement the software in accordance with the approved implementation plan. Supplier must produce an Implementation Report detailing all implementation activities and certifying that the system is operational and meets performance requirements.

5.8.4

Production Cutover Once the system has been approved, in writing, as ready for production, Supplier must work with City to perform a production cutover procedure. Supplier must ensure that the code, compiled modules (where required), interfaces, job streams, other components of the production environment, and all documentation are ready and organized for “go-live”. City will then ensure all components and modules of the production environment; job streams (or scripts) are properly documented according to agreed upon standards.

5.8.5

Post Implementation Support If not already included in Supplier’s standard support model, Supplier must provide onsite post implementation support for a period of four to six weeks after go-live. This post implementation support must be provided by skilled Supplier staff that has become familiar with City operations over the course of the implementation effort. The City will formally accept the system upon the successful completion of post implementation support and successful operation of the system. The City will determine whether the system meets the standards as outlined in the contractual documents.

5.8.6

Support and Maintenance Requirements Software maintenance and support must be comprehensive, responsive and benefit City upon implementation and into the future. Supplier will describe how software maintenance and support is provided. The following requirements will be included and described: a. Describe how software upgrades are supported. Include frequency and delivery of patches, minor upgrades, and major upgrades.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 29 of 63

b. Describe how technical support for end users and Information Technology support is provided. Include response time expectations and escalation procedures and if there will be a contact team that is familiar with the City’s implementation. c. Describe your various Software Licensing options with costs and benefits of each option d. Please provide in detail all system support models offered once the product has been deployed. Please also describe the benefits/disadvantages for each support model. e. Describe the system/supplier methods for compiling, certifying, and supporting the system and interfaces when other City systems, such as PeopleSoft Enterprise system, Oracle Database, Asset Management, Outlook/Exchange, MS Office suite, Revenue System, Ebuilder, ESRI GIS system, and others are upgraded. *Note that City’s preferred availability includes 24X7 telephone support. If 24x7 support is not available, the response will include descriptions of after-hours and emergency support. 5.8.7

Supplier Deliverables Must include a. b. c. d. e.

5.9

Implementation Plan Implementation Readiness Letter Implementation Report Production Cutover/ Stable, Live Operations Post-Implementation Support

Documentation For this section of the proposal, Proposer must submit a narrative that fully describes the approach, methods, tools, and techniques used for developing user and system documentation. Supplier must develop and provide to City all documentation throughout each phase of the project and prior to final system acceptance. Supplier must provide complete, well-written, and accurate technical, system, and user documentation. For any custom developed applications, Supplier must adhere to City development standards. All documentation must be easy to follow, with screen shots, where applicable. All documentation must also be available in both paper and electronic form. The following activities are required to achieve this: 5.9.1

Security Administrators Guide In order to delegate selected security maintenance tasks and responsibilities, a comprehensive security guide will be required.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 30 of 63

5.9.2

Operations Documentation Supplier must develop a complete operations document. The operations documentation must include overviews of the application, system structure, major processing, required interfaces, report documentation and correspondence documentation. This includes any required periodic maintenance tasks. The operations documentation must also describe the overall batch or background process schedule, including dependencies, sequencing, and timing.

5.9.3

Technical Documentation Supplier must provide complete system documentation that documents the application software and software architecture (e.g. implementation view of the application architecture). This includes all SOFTWARE programs, and executable.

5.9.4

Documentation of All Customization/Configuration Parameters Supplier must document all customization/configuration parameters used. The documentation must reference all parameters and note and explain where dependencies occur and where environmental conditions dictate specific usage and settings.

5.9.5

Workstation Installation Procedures and Automated Installation Tools If there are any workstation-based components to any of the proposed software products and solutions, Supplier must provide City with a set of documented procedures and automated deployment/installation scripts for use with Supplier’s software distribution tools. These scripts and procedures will enable City staff to independently install and connect additional workstations.

5.9.6

Supplier Deliverables Must include a. b. c. d. e. f. g.

Security Administrators Guide (and updates) User Documentation (and updates) Operations Documentation (and updates) Technical Documentation (and updates) Customization Documentation (and updates) Workstation Installations Documentation (and updates) Workflow Administration Guide (and updates)

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 31 of 63

6.

REQUIREMENTS, ROLES AND RESPONSIBILIBITIES

6.1

The City of Kansas City is requesting that the selected Supplier be able to commit to installing on weekends and evenings after 5:00 P.M. if necessary to complete the implementation.

6.2

ROLES AND RESPONSIBILITES Project Management Task/Activity Management of Vendor Staff

Vendor Lead

City Assistance

Project Plan and Updates

Assistance

Lead

Kick Off Meeting

Assistance

Lead

Status Meetings

Assistance

Lead

Issue Tracking, Analysis, and Escalation

Assistance

Lead

Change Management

Joint

Joint

Status Reports

Joint

Joint

System Analysis and Design Task/Activity System Usage Analysis

Vendor Lead

City Assistance

Interface Plan and Designs

Lead

Assistance

Custom Report Designs Lead Assistance

Lead

Assistance

Custom Correspondence Design Lead Assistance

Lead

Assistance

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 32 of 63

Technical Services Task/Activity Technical Environment Design

Vendor Lead

City Assistance

Technical Environment Setup/Maintenance

Lead

Assistance

Performance Testing and System Tuning

Lead

Assistance

Hardware Installation

Lead

Assistance

Installation of Application Software

Lead

Assistance

Sand Box Set-up

Lead

Assistance

Configured Software

Lead

Assistance

Interface Application Software

Lead

Assistance

Task/Activity Data Conversion Plan

Vendor Joint

City Joint

Data Conversion Programs

Lead

Assistance

Converting Data Lead Assistance

Lead

Assistance

Task/Activity System/User Acceptance Test Plans

Vendor Joint

City Joint

Application System Testing

Joint

Joint

User Acceptance Test Scripts

Joint

Joint

User Acceptance Testing

Joint

Joint

Data Conversion

Testing

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 33 of 63

Training/Knowledge Transfer Task/Activity Project Team Training

Vendor Lead

City Assistance

Training/ Knowledge Transfer Plans

Lead

Assistance

Training Curriculum /Materials

Lead

Assistance

Train the Trainers

Lead

Assistance

Technical and Operations Training

Lead

Assistance

Training Facility/Equipment Assistance

Assistance

Lead

System Implementation/Post Implementation Support Task/Activity Implementation Plan

Vendor Lead

City Assistance

Implementation Readiness

Lead

Assistance

Implementation Report

Lead

Assistance

Production Cutover

Lead

Assistance

Post Implementation Support

Lead

Assistance

Support Maintenance Requirements

Lead

Assistance

Vendor Lead

City Assistance

Documentation Task/Activity All Project Documentation

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 34 of 63

7.

TECHNICAL AND FUNCTIONAL REQUIREMENTS Please mark a category for each chart field on the following requirements charts. Do not leave any requirements blank.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 35 of 63

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements

The enclosed requirements are general system requirements.  The successful Vendor shall  meet individual Department / Division stakeholders and develop their requirements based  on their business process including the required Reports, Queries etc. Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # A LAND MANAGEMENT ‐ The system shall have fields for the state of the art land management process, including but  not limited to the fields currently used by the City's  Land Management System. 1 Yes The system shall have the ability to differentiate between billing owner and owner of record  2 and track their billing history. 3 The system shall be able to tie the permit processes to land. Yes 4 The system shall have flexible Geneology: Parcel Geneology, Permit Geneology, and Project   Geneology and allow corrections, including, but not limited to changing the status of parcels or  deleting parcels, while keeping genealogy intact. 5 The system shall have the ability for parent and child level permit functionality and the abilty  to search by these levels. 6 The system shall be able to identify by: Parcel, Line, and Point, and produce graphical images. 7 8 9 10

The system shall be able to differentiate by parcel types. The system shall be able to track structures and business establishments. The sytem shall track activities with public rights of way that are not part of parcels. The system shall be able to track parcels, parts of street right‐of‐ways, and site parcels (TIF's,  CID's, etc.).

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

     

Yes

1

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 11 The system shall be able to identify a parcel by X Y coordinate and publish the representation  on a map, and generate a permit. Also generate notification letters to parcel owners within  defined distances and parameters of the selected X/Y coordinate. Yes 12 The system shall be able to accept or import data in different formats ( tapes etc.) from  Counties and shall be able to match records such as owner and parcel ID numbers etc, and  update the billing owner as being the separate owner of record. 11 The system shall have the ability to access land information and track activities taking place on  Yes a particular parcel of land. 12 The system shall enable a parcel to have master and alias addresses and be able to identify the  county and zipcode of a parcel 13 The system shall automatically populate the structure and establishment based upon permit  actions. 14 The system shall allow for multiple types, including but not limited to land, streets,  intersections, and streetlights. 15 The system shall have a field to capture City‐owned property and fields to indicate the City  Department and person responsible. 16 The system shall be able to accommodate vertical/condo parcels and shall have a  suite/apartment field as part of an address. 17 The system shall be able to open Subdivision Code and Description for a platting. 18 The system shall provide the ability to verify how many permits and the permit types issued for Yes an address. 19 The system shall have have a central idendifier (parcel ID number etc.) that is reflected  in all  Yes modules of the system related to the land. 20 The system shall have the ability to identify and age components of a building (such as a roof).

2

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 21 The system shall provide that a user shall be able to find all available dates of construction,  alteration or demolition associated with structures/parcels in the system.

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

22 The system shall have functionality for Explosive/Flammable operations – An up‐to‐date  registry of Above‐ground Storage Tanks containing pressurized liquids capable of exploding, or  materials that are flammable, shall be maintained and a mapping layer that pinpoints the  center of these tanks by both State Plane Missouri West XY coordinates and  Longitude/Latitude. The address/parcel shall be associated with it and a contact name/number  for the owner/operator shall be maintained. The contents of such tanks shall also be identified  in a database accessible by City staff. Additionally, any historical leaks or ruptures shall be able  to be documented. 23 The system shall be able to produce land information permit processes including, but not  limited to the following, including entry, maintaining, routing, tracking, and coordination: a b c d e f g

ZF01 ‐ Large Apportionments/Subdivisions ‐ Final Plats.  ZF02 ‐ Small Apportionments/Minor Lot Splits.  ZF03 ‐ County Combinations Pending.  ZF04 ‐ Parcel Combinations.  ZF05 ‐ Street and Alley Vacations.  ZF06 ‐ Parcel Ownership Changes.  ZF07 ‐ County Parcel Matching. Matching parcels between the County and City parcel  information resulting from parcel splits and combinations that may have not been initiated  with the City or existing on the City's file as temporary parcel and in the process of being  updated.

3

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # h ZF08 ‐ Parcel Mismatches. Resolution of parcel Mismatch Permits generated in the County  Parcel Matching process between the County and City parcel information resulting from parcel  splits and combinatiosn that may have not been initiated with the City or existing on the City's  file as a temporary parcel and in the process of being updated. i j k l 24

1 2 3 4

4

ZF09 ‐ Land Bank Update.  ZF10 ‐ Parcel Valuation Changes.  ZF11 ‐ County Tax Billing Updates. ZF12‐ Tax Payment History Updates. The sytem's permit process shall enable the entry and  tracking of Tax Payment History Updates. The system shall allow updates (additions, changes, etc.) to property information by  authorized users.  PERMIT / APPLICATION PROCESSING: The system shall facilitate the entire development process, from initial plan development  application request through the issuance of certificate of occupancy. The system shall facilitate the entire licensing process, from initial application through final  delivering of the license. The system shall provide for receipt, review, status checks, updates, and approval of requested  activities and permits  The system shall automatically assign the application number or allow manual assignment  (permit, license, certificate, project, etc.),with the numbering sequence set uniquely for each  application type. The system shall allow the manual assignment of a permit type, for each application type.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes Yes

5 The system shall control and track application number by each application group (building  permits, fire permits, water permits, etc.).

4

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 6 The system shall provide for application types (Health permits, food service, noise variance,  etc.). 7 The system shall enable the recording of personal data information (required on some license  applications) within the limits of the City policy. 8 The system shall use, display, calculate, and store four (4) digit years. 9 The system shall provide a process for holds or conditions from outside agencies. 10 The system shall allow the Investigator or Supervisors to place a hold on an application, to  ensure a license not be issued until the required documents are submitted or fees paid Yes 11 The system shall have 3 or more levels of linkage and be able to manage many‐to‐many  Yes relationships for property. 12 The system shall have the ability of automatically cross referencing projects by address,  applicant name, project number, and other historical and concurrent City applications.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

(gf)

13 The system shall have content sensitive help functionality that is accessible from any screen,  that displays help related to the particular screen in use. 14 The system shall provide for both mandatory and optional fields color coded, as defined by  City. 15 The system shall allow for FireID that remains constant throughout the establishment's history. 16 The system shall provide for autocomplete of Fire Code number and matching code  descriptions. 17 The system shall provide for a  new FireID to be autonumbered  instead of manual entry.

5

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 18 The system shall allow a process to create an umbrella ID for future complexes such as  apartment groups or a tower with a shell and multiple establishment. Sub‐numbering for  complexes with future additions shall be available. 19 The system shall allow for secure sign‐off and comments  by the Fire Department regarding  permits, flags (holds), and inspections where agreement has been made between the two or  more departments.  20 The system shall provide that a user shall be able to see the history from initial application to  Yes inspection and closure. 21 The system shall provide that a citizen shall be able to go to the City's web‐site and apply for  Yes permit or be able to see pending applications, registration etc. 22 The system shall enable the addition of new industries (such as tow drivers). 23 The system shall provide that property owners shall be able to go online into the system to be  Yes able to register their vacant and rental properties. 24 The system shall allow the ability to make entries on a linear basis (such as for parade routes,  etc.) 25 The system shall be able to process attachments to streetlights and the associated permits.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

26 The system shall provide that fees for streetlights and attachments shall be based upon a user‐ defined value of the work. 27 The system shall have a screen to enter and view component prices associated with  streetlights. 28 The system shall enable City Staff to approve or deny permits. 29 The sytem shall provide for the override of permit fees by autorized staff with audit trail. Yes 30 The system shall provide for the ability  to cancel / delete a permit by autorized staff with audit  trail.

6

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 31 The system shall provide the ability to collect split tender for payment by autorized staff with  audit trail. 32 The system shall provide the ability to extend the expiration date for a permit or License   application with proper security clearance. 33 The sytem shall provide the ability for a project to have multiple permits of the same type. 34 The system shall display comments associated with a permit type in order of most recent to  oldest entry. 35 The system shall be able to place a hold on all permits associated with a project. 36 The system shall allow for the capture of basic application data and track status of permit  applications. 37 The sytem shall allow assignment of pseudo or temorary parcel numbers to be used for  permitting purposes until actual parcel numbers are available. 38 The system shall provide for the calculation of standard fee amounts using user provided  formulas or tables.  39 The system shall capture and allow access to complete permit histories by parcel. 40 The system shall allow for user ‐defined structure  detail items based on the type of work being performed. For example, a different set of data may be set up for re‐roof permits than for  single family homes. 41 The system shall allow data entry displays and items to be tailored to the type of permit being  issued. For example, fees displayed for selection shall apply to the type of permit being issued. 42 The system shall allow for an unlimited number of names, addresses, and phone numbers to  be entered for a permit application, and the system shall allow for online searches by any of  these names to locate a permit record.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes

Yes

Yes

7

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 43 The system shall allow for multiple subcontractors to be associated with a single permit. For  example, an electrical permit could have two or more subcontractors. 44 The system shall allow an unlimited amount of free‐form notes to be entered for a permit. 

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes 45 The system shall allow these notes to be flagged to appear automatically at key processing  points (such as inspection entry). 46 The system shall allow for unlimited user defined codes for such items as type of construction,  occupancy type, etc. 47 The system shall allow for the processing of blanket permits where a single permit fee is  charged to cover the issuance of multiple permits. 48 The system shall allow user defined calculations based on a user defined table of construction  values. 49 The system shall allow user‐defined square footage calculations based on a  user defined table  of square footage values. 50 The system shall allow a user to duplicate an existing permit application and all associated  information to a new application at a different location by anwering 'Yes' from the drop down  menu. (e.g. a 'standard plan' type of application that is being built repeatedly by a contrator). Yes 51 The system shall allow quick entry of historical data from manual files. 52 The system shall allow scanning and storing of documents such as plans and application forms.  These scanned documents shall be attached to a permit application and be able to be recalled  later online. 53 The system shall allow for search and retrieval of a permit or application using address, parcel  number, associated names, type of application, application status, responsible department, or  any combination of these items.

Yes

Yes

8

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 54 The system shall allow special notes to be attached to an address or parcel in the property file  yes and flagged for automatic display in the building permits application. 55 The system shall automatically calculate permit expiration date based on user parameters.  Expiration date is extended automatically based on inspection activity. 56 The system shall provide the option to send notification letters via Microsoft Word  to  contractors and/or owners, such as prior to permit expiration. 57 The system shall provide that when a hand‐held device is used, such as a tablet etc., the  system shall  Identify permits that are at a X‐Y coordinate or create a new permit  using X‐Y  coordinates and collect signature for the permit. 58 The system shall provide for multiple applicant name tabs available to track ownership over  years.  The tab needs to track dates of ownership. 59 The system shall provide  screens for both the establishment  address and the applicant/billing   address. 60 The system shall provide that all screens shall have user defined fields similar but not limited to Yes the current system. 61 The system shall provide that the inspection and permitting entries shall affect the same  establishment, and should not require entering duplicate information for each (i.e. applicant  name is the same on both inspection. The permitting dates would have the same expiration  date‐‐ and begin on the inspection date. 62 The system shall allow for an annual permit to be automatically set for the next years  inspection date. 63 The stystem shall provide that when using a mobile device or tablets , all windows and fields  shall be available for retrieving data and information including saved images for individual  Yes permits. 64 The system shall provide the option to send notification letters via e‐mail to licensee or permit  holders, such as prior to permit expiration.

9

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 65 The system shall provide for temporary permit or license entries that will not affect an annual  inspection or license renewal date or status 66 The system shall provide for a temporary permit not being tied to an address.  (i.e. tent permit,  explosive storage). 67 The system shall enable a customer to apply for temporary permits (such as for fireworks)  without affecting the date or status of an annual inspection. 68 The system shall enable a department to view the status of another department's permit (such  Yes as a Certificte of Occupancy)with authorization. 69 The system shall allow customized screen for viewing one's own department's screens for  efficiency in entering data and reviewing history. 70 The system shall provide that only if permits are needed (not hazards needing correcting), the  system shall allow for payment on‐line which will then properly credit the account and reduce  the system fee count owed.  Yes 71 The system shall have the ability to create and renew yearly food establishement and liquor  licenses. 72 The system shall provide for the recording of establishment/customer information, including  but not limited to Federal ID Number, Establishment name and address, Owner's name and  mailing address, its status, Season (such as need to know the range of month's a school is open  and available for inpections),Days (such as  Monday thru Friday, for indicating the days of the  week that an inspection can occur), Hours the establishment is open, the establishment is  open / closed, permit number & type, Risk Category (High, Medium, Low; determine how  often during the year inspections will be scheduled), license's name and type , license status.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

73 The system shall enable a user to determine if approvals for the establishment have been  made by other City Departments (such as by City Planning, Fire, etc.) before issuing a license Yes

10

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 74 The system shall maintain the records of closed establishments 75 The system shall allow duplicates of names for establishments or chain restaurants (making an  unique number or address the unique identifier)   76 The system shall allow access to third party to extract and export information to conduct  required background checks for applicants (Excel export)  77 The system shall provide the ability to generate electronic notification (e‐mail, etc.) to the  applicant pertaining the status of the application and a list of corrections requested and  Yes documents required 78  The system shall have decision‐making workflow, with routing decisions for subsequent  workflows, processes, and cycles for intra and inter City Departments and External  Yes Contractors. 79 The system shall provide the ability to track the status and locations of all applications and  such tracking shall be available for the public to view on‐line 80 The system shall provide the ability to link all applications to investigations and code cases, and  vice versa. 81 The system shall have the ability to create checklists containing requirements for  different  types of application submittals. 82  The system shall not allow a license or permit to be issued until all required documents and  steps are completed. The system shall allow capability to override this condition to issue a  Yes license if necessary by the approved authority. 83 The system shall allow for tracking of the amount of time in days applications and renewals are  being processed and also the response time of the applicant. 84 The system shall be able to tie a business vehicle permit (such as a taxicab) to a  business (and  not tie the driver to the business). 85 The system shall be able to prorate the cost for licenses and permits (such as when someone is  issued a permit mid‐year).

11

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 86 The system must be able to track suspended licenses (including when suspended, fee amount,  etc.). Yes 87 The system shall allow the recording of multiple licenses for an establishment 88 The system shall enable the capturing of an applicant's photo and signature on both a  Yes screen/system page and also on the printed card/license. 89 The system shall be able to process Rental Housing and Vacant Buildings registrations. 90 The system shall be able to generate annual notices for Rental Housing and Vacant Building  registrations. 91 The system shall be able to track the status of Work Access Permits, including but not limited  to time of days, construction workers, contractors, property owners, certificate of compliance  status, etc. 92 The system shall have workflow functionality for the generation of notices, owner research,  inspections, approval of inspection fees, administrative citations, the ordering of bids for  93 The system shall have the ability to add, modify and delete job valuation details by the  authorized staff with audit trail. 94 The system shall be able to track securities (surety) on each project 95 The system shall be able to issue permits by segment parcels and by land parcels. 96 The system shall provide that a deleted permit shall not appear on a report unless the report is  specific for deleted permits. 97 The system shall provide that a user shall be able to define fee codes with variables for the  calculation of permits. 98 The size of the 'location' field on a permit shall be sufficient for the input of a neccesary  information to describe a location 99 The system shall provide for permits with electronic signatures to be stored in the system for a  period of time determined by user.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

CPD  (gf)

Yes

Yes

12

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 100 The system shall provide the ability to scan permits and provide for search conventions. 101 The system shall prohibit the assignment or entry of a duplicate permit number. 102 The system shall be able to combine all permits into a single request 103 The system shall provide notification (e‐mail) by permit type for notification when the permit  is issued and expiring 104 The system shall be able to indicate where a streetplate is located. 105 The system shall provide for the ability to perform a search to determine when a permit was  issued. 106 The system shall be able to reflect a Registration Number on ARC maps. 107 The system shall be able to tie a Parcel Identification Number (PIN) to a map. 108 The system shall be able to tie a Parcel Identification Number (PIN) to the City's Banner billing  system 109 The system shall provide for the entry and storage of fee items and costs, including but not  limited to tap fees, meter fees, plan review fees, excavation fees, streetplate fees, and meter  fees. 110 The system shall provide that if a department (such as Water) indicates that an item, such as a  streetplate, has been removed, the system shall have the ability to close the applicable permit  that was issued by another department (such as Public Works).

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes

111 The system shall provide the ability to enter the water main size, the meter location, the size  of the meter and the service line connection size (this is currenlty done on the KIVA  'Quantities' screen), and other user‐defined sizes and locations.

13

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 112 The system shall provide the ability to issue permits and enter tap/ connection, meter, plan  review fees, etc. (tap /connection fees are based on the size of the water main and the service  line size, meters fees are based on the size of the meter, all fees are set up in the fee Calc  screen in Kiva). 113 The sytem shall provide that permit fees, water main sizes for taps/connections, meter fees,  etc. entered as a default fees.  114 The system shall provide the ability to adjust fees and payments (add meter fee, pay the  difference, charge for a larger tap, etc.). 115 The system shall provide the ability to look up a permit by register number or address.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

116 The system shall have the ability to automatically close  permits based on the final inspection  date from Inspector or Servicer. 117 The system shall have the ability  to manually reopen permits if needed with an audit trail  (Supervisor/ Manager only). 118 The system shall have the ability for read only access for some user group and once a permit is  completed, only a Manager or supervisor can make changes. Yes 119 The system shall have the ability to verify if an address is a Parcel or a Segment (the system  shall provide that you can’t attach a new service permit to a segment). 120 The system shall provide that if a permit is issued for a general ledger accounting string for one  department, but it should have been for  another department's accounting string, the system  shall be able to interface an adjustment to the City's PeopleSoft General Ledger. 121 The system shall have the ability to 'trigger' the City's PeopleSoft financial system that an asset  should be depreciated for applicable certificates of occupancy.

14

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 122 The system shall interface, on a real‐time basis,  with the City's GenTax system to determine if  other liabilities are owed to the City before any permits are issued or licenses are granted. Yes 123 The system shall provide a notification to the staff in advance of the deadline whenever a  special use permit (approved by BZA) has expired or a condition on a project has expired.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

124 LIST OF PERMITS, INSPECTIONS, APPLICATIONS, PROCESSES, ETC. : The system shall be able to  allow users to define unlimited applications, inspections, permits, etc. for the usage of City  planning  & Development, Public Works, Neighborhoods & Housing, Fire , Health Department  Inspection etc. currently totalling a minimum of 211 permit, inspections and application  process.  A list can be found in the appendix XXX. Yes CONTRACTOR TRACKING ‐ 1 The system shall provide for tracking contractor data such as name, address, phone, e‐mail  address, fax, expirations, bond amounts, type of contractor,contact person, licenses and  insurance policies. The system shall provide an area for unlimited free‐form text comments  and notes for each contractor. 2 The system shall perform automatic checking of user‐defiend contractor requirements for  pulling a permit during permit processing. 3 The system shall  allow for establishment and tracking of escrow accounts for contractors.  Escrow accounts shall allow contractors to place money on account and use to pay permit  fees, eliminating the need to bring individual payments for each permit fee.

Yes

Yes 4 The system shall produce on demand statements for escrow accounts. 5 The system shall track Unique Contractor numbers. 6 The system shall provide for Unlimited User‐defined Contractor types.

15

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 7 The system shall track Primary and Sub‐Contractors. 8 The system shall support Unlimited Contract License Types per Contractor with associated  Expiration Cycles. 9 The system shall provide for Internal Flagging for Licensing issues. 10 The system shall provide for Multiple Invoice Management / Individual Fee Payments.

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes Yes

11 The system shall support Free Form Entry Fields for Comments related to individual  contractors. 12 The system shall provide for the ability to enter Trust Account information. 13 The system's application screen with contractor information shall indicate items that have  expired (such as insurance, bonds, etc.) and provide a warning of such expirations. Yes 14 The system shall have a specific identifier for each business and for each contractor; such  identifier will be reflected in all modules of the system and in all systems it interfaces with. Yes 15 The system shall have quality controls for the review and documentation of contractors work,  and to provide for the ability to query the information based on user defined parameters to  review contractor performance. 16 The system shall provide an option for the contractor to upload plans, pre and post  construction photographs and videos for any permit in the system 17 The system shall provide that when a permit is approved for work by the City, the system shall  be able to generate an e‐mail notification to the contractor. 18 The system shall have the ability to notify a maintenance contractor that the City has taken  over an asset (such as a streetlight). 19 The system shall have the ability to interface with the City's eBuilder system to bid on sidewalk  projects in that system.

Yes

16

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 20 The system shall automatically assign the application number (permit, license, certificate,  project, etc.). The system shall control and track the application number by each application  group (such as building permits, water permits, contractor licenses, business licenses,  development plans, code violation cases, etc.).Each Department/ Division will have its own  unique group ID (Such as Health Dept.) within which they will have different types of  Permits(Viz. Food Service Permit) and each type will have a unique permit number.

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes 21 The system shall provide that an application group will be comprised of application types; for  example, Health Permits (application group) may be comprised of the following application  types: Asbestos Notification Permits, Food Service Permits, Noise Variance Permits, etc. Application Review: 1 The system shall provide an online function of departmental review for each application. (Such  as projects,plans,zoning changes, liquor licenses etc.) 2 The system shall provide for both automatic and manual assignment of projects, cases and  applications awaiting review. 3 The system shall provide that users shall be able to check conditions, enter review comments,  and approval responses, including placing 'holds' on applications under review. 4

The system shall provide a hierarchy of “holds” that will enable the system to perform or not perform required application specific processing actions. For example, an “information only” hold may act upon a specific application as a flag to check a certain ordinance. Another level of hold may instruct the system to allow a specific application to be accepted and plans to be submitted, but instruct the system to not allow a permit to be issued until the hold is removed. 

Yes Yes

Yes

17

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 5 The system shall provide an online process for holds or conditions from outside agencies. The system shall be able to generate letters, notices or mailing labels to the applicant and interested parties, describing the requirements or conditions prerequisite to application approval or issuance.  The system shall allow multiple applicants on the same project. 6 The system shall have the ability to allow the issuance of “partial” permits while the application or project is in plan review. The system shall be able to manage the approval of “partial” permits while the plan review process continues. 7 The system shall provide the ability for users/reviewers to view a list of applications waiting their personal and /or department review of approval. The system shall enable users to view all information of an application, including all subordinate/dependent applications linked to the reviewing application. For example, the system shall link all permits to a plan review and the reviewer should be able to view all information of the project. Application Tracking: 1 The system shall track and facilitate online status lists and reports of applications. Departments, agencies, applicants, interested parties shall be able to access lists, by department and application type, of projects, plans, permits, licenses, inspections awaiting review or approval and view the status of a specific application or series of related applications.  2 The system shall track and show all conditions of approval and provide easy determination of  the status of the application and progress through the review and approval process, including  flags, holds or conditions.  3 The system shall track and show all conditions of approval and the system shall automatically apply or relate project approved conditions to all properties involved in the project.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes

Yes

18

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 4 The system tracking features shall provide both automatic and user definition of  review  checklists and approval procedures to be tracked for each application.  The checklists and  approval procedures will be routed and utilized in the application review process.

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

5 The system shall provide that the status tracking features shall include, but not be limited to  Application number; type; application  filed date; Name of applicant; Application status (new,  assigned, consent period, awaiting documents, denied, pending approval, in process, on hold,  incomplete, revisions required, revisions received, approved, etc.); License status (active,  inactive, in renewal etc.; Departmental review, routing, plan check status, holds; Conditions of  approval, status by date, department, individual, agency; Environmental assessment,  determination, status; Date and type of action taken (Plans Review Board, Plans Commission,  recommendation, City Council Approval);  Review comments, Description of work;  Number,  type, description of applications approved; Permits issued and permits finalized;   Application/permit expiration dates; Project/application estimated duration to  approval/issuance;  All changes since project/application was filed; Projects spanning several  years;  Inspections/Reviews performed and remaining;  Property ownership changes;  Property  valuation changes (as resulting from improvement); County notification of improvement;   Property Special Assessment and Fees;  General Fees;  Track and follow changes to the  application.

Application Routing: 1 The system shall have robust workflow and provide both automatic and user defined routing  and tracking  of applications (projects, plans, permits, etc.) between departments, divisions,  individuals, agencies through all stages of review and approval. Yes

19

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 2 The system shall incorporate both automatic and user defined review checklists and approval procedures by application in the routing process.  3 The system shall provide that the routing function shall also include, but not be limited to, Date and time rout; Purpose of routing (Plan check, revised plan(s), review report, etc.); Application number and type; Status of application; Agency, department, division, and individual routed to and from; Date comments, review, and/or approval due; Disposition of review (comments, holds, cleared for approval, etc.); Date review completed; Application priority; Priority routing/review; Date case forwarded; Purpose/next stage of approval process; Dated comments, review and/or approval due; Final date of approval/denial and Priority Project Notification e‐mails when work flow completion is not completed and is within warning periods set by user. Yes Application Inspections: 1 The system shall provide automated and manual inspection and reinspection scheduling for all building construction, street construction, code enforcement, utility service, licensing, and Yes environment management.  2 The system shall provide tracking features that shall provide both automatic and user  definition of  review checklists and approval procedures to be tracked for each application.   The checklists and approval procedures shall be routed and utilized in the application review  process.

20

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 3 The system shall be able to link and track inspection requests and results with the application (such as a permit, code case, project, complaints, inspections or license). The system shall be able through all phases of an application to schedule, track and process inspections or applications, including generating forms, notices and reports, tracking and monitoring conditions, calculating inspection, licensing and permit fees, and assigning and preparing customized work schedules for inspectors based on inspection, value of work, etc.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

4 The system shall provide that inspection functions shall include, but not be limited to: 5 Inspection date and time, inspection type, inspection status, location, violation observed,  inspection items and conditions, comments and their required corrections. Yes 6 Incorporate inspection results from computers used in the field, including hand‐held devices,  electronic transmission over remote devices, and through Internet access 7 List and track types of follow‐up inspections needed a Determine the information that displays for each inspection and the order in which inspections  are listed on inspector work schedules b Flag a requirement for an inspection, such as one time, or for a list of  sites requiring ongoing  inspections with specified time frames c Prepare customized inspection workload report by date and inspection d Print “stop work” orders and inspection reports in the field e Allow inspector to identify illegal or improper construction activity and flag the property to  ensure that penalty fees will be collected when valid permits are issued f Prepare follow‐up report of unscheduled and overdue actions.

21

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # g Automatically track 180 day time limit and expire a permit if no inspection activity has  occurred, along with the ability to generate notices 30 days prior for permits about to expire.

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

h Reject inspection requests for permits not issued, or on hold, or project on hold, or required  reinspection fee not paid i Maintain user defined inspection work calendar of city work days and inspection scheduled  non‐work days (such as vacation or sick leave) that can be used to effectively schedule  inspections j Assign inspection to inspector based on system and user defined parameters (such as  inspection type,project number, inspection zone or area, maximum inspection workload based  on number and projected inspection time, inspector comprehensive work schedules) k Reassign specific inspections or workload to different inspectors from designated inspectors l Prepare report and/or view online current inspection schedules or history by inspector, by  zone or any predefined area, by application (such as a  permit or code case), by project m Verify that all required construction has been completed and all inspections have been passed  by multiple departments prior to issuance of final inspection and  the Certificate of Occupancy.

(gf)

n  Notify investigators of past due or scheduled inspections o  Automatically track 90 day time limit and expire an application if no or limited activity has  occurred, along with the ability to generate notices 30, 60 and 90 days prior to a license being  denied p System shall allow for over‐ride of 90 day time limit by supervisor or system administrator

22

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # q The system shall be able to assign inspectors to permit applications and monitor the status of  inspections. r The system shall provide for user‐defined types of inspections. s The system shall allow the indication of discrepancies. 8 The system shall allow the sign‐off on individual inspection discrepancies.  Shall provide  numbering of individual correction items; shall allow continuation of the same inspection  (including correction item numbering) on a different day/visit.  Shall allow the user to display  only the remaining open items (from an individual inspection or across all inspections on a  permit) vs all items, including the approval of individual items.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

9 the system shall allow the uploading of digital images and supplemental field documents with  the ability to attach images to a specific record (such as location or individual permit) 10 The system shall have the ability to communicate utility release information to utilities. 11 The system shall have the ability to assign inspections from a map, with path‐routing (efficient  route for the trip), with GPS tie‐in. Citizen's online Features: 1 The system shall provide capabilities for customers to be able to complete permitting  applications and comments into the system or request for inspections on line and Email to  appropriate Email account for disposition. 2 The system shall provide that customers shall also be able to make payment for preset and  user‐defined permit fees on the Internet using their credit card or via a payment interface with  another system to have the customer pay the convience fee.

(gf)

Yes

Yes

23

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 3 The system shall provid the Online Information  from a citizen shall be  posted real‐time to the  Yes database. 4 The system shall provide that a citizen shall be able to file a complaint online. 5 The system shall provide that a citizen shall be able to upload electronic plans or files (letters,  Yes pictures, etc.) online 6 The system shall provide that a citizen shall be able to pay fees online. 7 The system shall have a shopping cart feature that Users can log into and pay for fees. Yes 8 The system's shopping cart shall  allow for multiple transactions with a single payment.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

9 The system shall have the ability to create custom forms that are viewable online and collect   the customer inforamtions as a required field. 10 The system shall provide that a citizen shall be able to file a new project application online. 11 The system shall provide that a citizen shall be able to view the status of a permit, project,  license or case online. 12 The system shall allow external inspectors and plan reviewers to input results & comments  online, with a unique login. 13 The system shall provide that the City shall be able to change the configuration and  preferences of the online system. 14 The system shall provide that a citizen shall be able to view the plan review notes and  comments online. 15 The system shall provide that a citizen shall be able to submit a request for service online, to  be notified of the service request receipt and case initiation, and subsequently find and track  the case online. REVIEW: PLAN, PROJECT REVIEW AND TIME TRACKING

Yes

24

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line #

Mandatory 

PLAN REVIEW ‐ 1 The system shall accommodate changes in the review processes, approval conditions,  application issuance requirements, and fee structures, and shall be flexible in adding additional  applications and incorporating technological advances. 2 The system shall provide the ability for users/reviewers to view a list of applications waiting  their personal and/or departmental review of approval. 3 The system shall track and show all conditions of approval and provide easy determination of  the status of the application and progress through the review process, including flags, holds, or  conditions. 4 The system tracking features shall provide both automatic and user definition of review  checklists and approval procedures to be tracked for each application. The checklists and  approval procedures will be routed and utilized in the application review.

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes

5 The system shall allow documentation of staff time spent on each project and project review  time for comparison to stated goals by department, division, activity (e.g. Public Works Plan  Review), in aggregate and total, and for different types of permits. 6 The system shall be able to calculate and assign due dates based upon user‐defined criteria,  with capabilities for manual override with proper security. 7 The system shall have the ability to process both City and private organization projects and be  able to differentiate between the two. 8 The system shall have the ability to have schedules of timelines and work being performed in  an area (such as work closures, capital projects, etc.). 9 The system shall be auditable and provide an audit trail for changes and approvals. 10 The system shall be able to quickly identify the status of each plan review in process and each  plan case in the application process.

25

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 11 The system shall provide the ability for a plans corrections to be entered into the system via  correction codes. 12 The system shall provide the ability to generate electronic notification (e‐mail, etc.) to the  applicant containing the status of the plan review and a list of corrections requested. 13 The system shall provide the ability for City personnel and the general public to view the plan  review comments. 14 The system shall have decision‐making workflow, with routing decisions for subsequent  workflows, processes, and cycles. 15 The system shall provide the ability to recall and display comments entered by different  personnel at different stages of the review. 16 The system shall provide the ability to track the status and location of all plans, including those  sent to outside consultants to review. 17 The system shall provide the ability to generate backlog reports to indicate plans completed,  new plans taken in to review, and plans in process. 18 The system shall provide the ability of the plan review division to review inspection results.

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes

Yes

19 The system shall provide the ability to link all plan reviews to building permits, and vice versa. Yes 20 The system shall allow the approval and management of partial payments while the plan  review process continues. 21 The system shall allow the ability to create a master list of activities and submittals for each  type of Land Development application and use the master list to monitor the progress of the  application approval process. 22 The system shall have the ability to have ordinances and city procedures on‐line to provide  information to City personnel.

Yes

26

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 24 The system shall have the ability to create checklists containing Land Development activities  Yes for different types of application submittals. 25 The system shall have the ability to set up hearing calendars for the City Planning Commission  and the Board of Zoning Adjustment meetings. 26 The system shall allow the ability of City Departments to enter recommendations to the  hearing calendar. 27 The system shall have the ability to prepare agendas for public meetings. 28 The system shall allow user‐defined plan review routing based on type of work performed.  Standard routing shall be based on type of work automatically created when application is  entered. 29 The system shall not allow a permit to be issued until all required plan review steps are  completed. The system shall allow capability to override this condition to issue permit. 30 The system shall allow  for entry of unlimited free‐form comments during plan review. The  system shall allow for the use of a user‐defined table of standard comments that can be  accessed during plan review. 31 The system shall allow for tracking of the amount of time in days that plans were under review  for each plan tracking step. 32 The system shall allow entry of plan corrections items as part of plan review. The system shall  produce a plan correction listing of these items on demand. 33 The system shall provide that electronic documents shall have the option for viewing without  downloading 34 The system shall provide for Fire Prevention's sign‐off of a plan review with reviewer's name,  date, and comments. 35 The system shall provide for the Fire Department's viewing of electronic documents, including  plans in third party software.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes

27

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 36 The system shall provide for logging dates sent, reviewed, due, rejected or approved for  multiple reviewers, as well as a remarks area for each reviewer. 37 The system shall be able to track multiple submittals on any project. 38 The system shall provide for the ability to create a list of standard comments for plan review.

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

39 The system shall be able to link multiple permits, cases, and plans to a single master project. Yes 40 The system shall support multiple Parcels & Addresses (unlimited) for each plan case. 41 The system shall have the ability to merge conditions into letters and other documents. 42 The system shall have a good word processor for notes and comments. 43 The system shall provide for approval options that include approved, not approved, reviewed,  and other user‐defined options. 44 The system shall provide for design consultants, private engineering companies, etc., to be  able to perform reviews and approvals. 45 The system shall provide that after sign‐off of plans, permits, etc., the system shall prevent  changes unless performed by an authorized supervisor. The system shall provide an option to  query and report these changes using user defined parameters. 46 The system shall accept and provide for the attachment of plans and documents, such as .pdf,  Microsoft Office documents, and other file formats. 47 The system shall allow the electronic mark‐up of documents, with colors and version control. 48 The system shall have issue tracking functionality and a user shall be able to determine which  items have been resolved.

Yes

28

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 49 The system shall enable users to view and download as‐built plans. 50 The system shall enable the generation of automatic reviews. 51 The system shall store approved plans in a central repository, with attached permits, design  Yes drawings, and as‐builts. 52 The system shall allow multiple reviews to be performed on a project and track the review  times. 53 The system shall provide the ability to perform plan reviews on development work such as City  wide projectts, other departments, private firms,that does not involve a permit.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

54 The system shall provide the ability to update the plan review default comments as regulations  change. 55 System shall allow attachment of flags to individual permits, to all permits for a project, and to  land records Projecting Review Time: 1 The system shall be able to calculate/estimate in advance the number of days a project will  take to review through all steps in the Plans Review process to final approval 2 The system shall be able to calculate/estimate subdivision Preliminary Plat Reviews and Final  Plat Reviews including City Council approval of ordinance. 3 The system shall be able to estimate the review, investigation, and issuance of all licenses and  permits including Liquor Establishment License, Adult Entertainment License, Taxicab Company  Licenses, Miscellaneous Regulateted Business Permit, etc. 4 The system shall be able to track the completion time of permits. 5 The system shall provide dashboard visuals of response times. 6 The system shall produce performance management data.

Yes

29

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 7 The system shall have a workflow management tool to report on both applicant and city staff  performance. Tracking Staff Time: 1 The system shall allow documentation of staff time spent on each project and project review  time for comparison  to stated goals by department, division, and activity (e.g. Public Works  Plan Review),  in aggregate and total, and for different types of projects.  

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

2 The system shall accommodate default times on activities when not specially entered.   WORK ORDER 1 The system shall have a robust workflow management tool, and shall be able to define  processes. 2 The system shall provide the ability to schedule the installation of streetlights, which may be in  phases and track the records for the schedule. 3 The system shall include a work order system to monitor and track work being perfomed. 4 The system shall be able to create and assign work orders. 5 The system shall interface with the City's PeopleSoft CRM module: 6 The system shall interface with PeopleSoft and shall create a work Order from the PeopleSoft  Provider Group. 8 The establishment's Zip Code shall result in the system assigning the applicable inspector

Yes

Yes Yes Yes Yes

9 The system shall enable the inspector to schedule an inspection on the work order and update  it after inspection with comments and attachments. 10 The system shall enable the inspector to schedule  reinspections and record reinspection  results on the work order.

30

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 11 The system shall enable the inspector to close the work order and upon closing of the work  order, the system shall interface to PeopleSoft and close the Action Center's Support Case.

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

12 If the inspector re‐opens the Service Order, the system shall interface to PeopleSoft and re‐ open the Action Center's Support Case. 13 Other City Departments shall be able to view the status of the service order. 14 In addition to 'citizen complaints' the system shall also provide for service orders associated  with 'regular' inspections, such as for annual, quarterly, or user‐defined periodically scheduled  inspections. 15 The system shall provide that, from the City's PeopleSoft CRM module, the Action Center's  staff's selction of a Provider Group on the Case shall automatically create a work order in the  system and assign the work to a department's division. 16 The system shall provide that the service order that is created shall automatically include  information from the CRM Case including, but not limited to Customer, Contact Name, Phone  Number,Address, Case ID and other information from the Case as defined by the User. 17 The system shall provide that when a service order is created, the system shall generate real‐ time e‐mail notifications of assiged work. 18 The system shall provide that a department/division shall be able to assign the service order  'deeper' within their organization, such as to an inspector. 19 The system shall allow a department to rea‐assign a service order to the City's Action Center  for further re‐assignment to another department/division. 20 The system shall have time‐stamping functionalities, including but not limited to indicate when  each task was assigned and completed, and by whom. 21 The system shall provide a process for escalations, to be deifned by user. 22 The system shall provide that  work orders shall be able to  be created 24/7.

Yes

31

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 23 The system shall provide that an inspector shall be able to cancel a Work Order and send a  notice to the Action Center to update the case for re‐assignment and the creation of a new  Work Order for another department/division. 24 The system shall provide that from a PeopleSoft CRM Case, a user shall be able to look‐up the  applicable Work Order(s) in the system. 25 The system shall have the ability to track work instances and all elements involved including:  people, assets, time, materials, location. 26 The system shall prohibit the assignment or entry of a duplicate work order number.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

27 The system shall have work orders that include the PeopleSoft CRM case number. 28 The system shall have work orders that are able to identify a sign (such as No Parking, Stop,  Yield, Street, etc.), its route, and its distance from cross‐streets. 29 The system shall have work orders that can be assigned to a person and enable the person to  schedule work to be performed. 30 The system shall provide the ability to create a work order for lawn irrigation taps to be sent to  Pipeline (currently it’s done in Hansen and by email). 31 The system shall provide the ability to enter a work order for test shuts for Pipeline. (currently  it’s done in Hansen and by email) INSPECTIONS INSPECTION PROCESSING  ‐ 1 The system shall enable the collection of signatures while the inspector is in the field. 2 3 4 5

The sytem shall be able to collect violation fees. An inspector shall be able to modify an inspection with an audit trail. The system shall be able to track inspections. The system shall allow inspection types to be defined by users.

Yes (gf)

32

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 6 The system shall allow a tracking number to link with the inspection requests and inspection  results. 7 The system shall not accept an inspection request if a reinspection fee was required and the  fee has not been paid. 8 The system shall contain a user maintained schedule of valid work days. 9 The system shall distribute inspection requests to appropriate inspector or backup inspector(s)  by inspection area or inspector project assignment. 10 The system shall allow authorized users to define codes for inspection comments and allow  Yes the inspectors to use the entry of coded inspection comments. 11 The system shall have auto‐complete functionality; a user shall be able to make an entry in a  field, such as a search field, and the system will perform auto‐complete. 12 The system shall individually manage comments and/or correction items; example ‐ 30 Items  are inspected, and 20 are fixed ‐ the system shall be able to resolve the 20 items and sign‐off  on the individual items. 13 The system shall have automatic work assignment of inspections, by geographic, project, or  Yes any other user‐defined criteria. 14 The system shall allow inspection work load to be reassigned to other inspectors. 15 The system shall have automatic notifications to applicants based upon inspection sign‐off Yes 16 The system shall generate a list of enforcement actions requiring follow‐up. 17 The system shall display inspection history of all inspections for a project. Yes 18 The system shall allow inspection scheduling and logging of inspection results. 19 The system shall allow user‐defined and system enforced inspection sequences for each  application based on type of work and system. The system shall allow inspection sequences to  be altered for individual permits as required.

33

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 20 The system shall check inspection scheduling to assure that Contractor's licenses are valid;  Inspections are being performed in the proper sequence; Type of inspection requested is valid  for the permit; All required fees have been paid; Permit has not expired; Permit has not been  placed on hold. 21 The system shall allow user‐defined penalties for failing inspections to be assessed during  inspection results entry. 22 The system shall provide that commonly used comments be contained in a user‐defined  standard comments file that can be accessed during results entry. 23 The system shall allow user definition of security to assure that only authorized persons are  Yes allowed to use an inspector's ID to sign‐off on an inspection. 24 The system shall allow user‐defined automatic assignments of inspections to inspectors by  area. Inspection area assignments shall be retrieved from property database and automatically  applied to inspection request. The system shall allow user to override automatic assignment.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

25 The system shall provide an easy method of reassigning an inspector's scheduled inspections  for such situations as an inspector calling in sick. 26 The system shall have the ability to track utility releases and communicate electronically to  utility companies. 27 The system shall have the ability to manage and track the work of third‐party and special  inspection agencies. 28 The system shall allow for the  storage of a  signature per inspection 29 The system shall provide for the quick screen print of the inspection history or fees for  customer support. 30 The system shall allow for the viewing the history or payments of the fire inspections on one  page .

34

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 31 The system shall provide for an inspection history or payment  be printed hard copy or sent to  pdf. 32 The system shall allow that when all payments made, or infractions corrected, then inspection  status automatically/or with a keystroke moves from Fail to another status‐‐setting per dept. 33 The system shall allow an inspection to remain in "Open" status to keep it on an annual list.   Requires a manually change status to Done only. 34 The system shall automatically adjust the status from "Fail" when all issues have been  resolved.  35 The system shall provide for re‐inspections and their results,  but shall not affect the annual  inspection and permit date. 36 The system shall provide the option of an establishment zip code entered automatically when  none is entered.  It shall not overwrite a prior entered zip code.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

35 The system shall provide that data entry for an annual Fire Inspection shall have a drop down  list to speed up the process. 36 The system shall provide for indicating hazards that are violations and any permits that are  required. 37 The system shall provide for inspector ID numbers, for inspections. 38 The system shall provide for dates for inspections and reinspections, and for recording the  results of all such inspections  without the reinspection dates affecting the annual inspection  date. 39 The system shall provide that the table with the Certificate of Occupancy (CICO) shall have a  Yes/No field (check box) if it’s a new structure vs improvement, a structural use code from a  drop down list, and a zip code with the structure address.

35

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 40 The system shall have the ability to charge or not charge for inspections and reinspections; for  example, an inspection and a re‐inspection may have no cost but subsequent reinspections  may have a cost. 41 The system shall provide that an inspection history screen shall include the transfer from the  Kiva Insp Hist Screen and shall calculate the next years annual inspection date. Yes 42 The system shall provide that an inspection history (Insp Hist) screen shall track (keep a  running count) of corrections as they are resolved. 43 The system shall provide that an inspection results screen shall include the transfer of data  from the  existing  system  on Inspection Correction Summary and include a non‐public drop  down list of inspector comments (i.e. Evidence of Repairs in Progress, Item on Order) Yes 44 An inspection results screen shall allow for an autofill of the Completed By and Date  Completed fields to avoid repeat entries. 45 The system shall be able to transfer pre‐inspection data to the city's preferred mobile device.  The pre‐inspection data is the pre‐printed data (i.e. address, business name, quantities etc.)   that is located on the Notice of Hazard Report. 46 The system shall have the ability to print inspection results at the inspector location (in the  field, at the office, etc.). Yes 47 The system shall have the ability to track and investigate violations. Yes 48 The system shall have the ability to publish results on the City website 49 The system shall provide that inspections shall be able to  be assigned to inspectors based  upon Districts (which is based upon user‐defined groups of zip codes)and also based upon a  Parcel Identification Number (PIN). 50 The system shall provide that Inspectors shall have calendars for monitoring their inspections Yes

36

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 51 The system shall allow inspections to be re‐assigned to another inspector, or deleted, by a  Field Supervisor with an audit trail. 52 The system shall allow for inspections for user defined liquor/taxi code violations including but  not limited to: Initial inspection;  Final inspection;  Renewal Inspection;  Citizen Complaint;   Comprehensive Inspection and  Undercover Investigation. 53 The system shall allow Investigators to have calendars to monitor investigations and due dates  for documents and required items for each application  54 The system shall report the Time In and Time Out for an inspection/investigation. 55 The system shall allow the creation of Establishment Types. 56 The system shall produce all of the City's PeopleSoft CRM Service Order reports including, but  not limited to the 'Dashboard' reports. 57 The system shall provide for violation codes for selection by user. 58 The system shall provide that a case shall remain open in the system while Service Orders and  complaints associated with the case remain open. 59 The system shall provide for deadlines for inspectors to complete tasks. 60 The system shall interface with the City's REGIS system; example ‐ inspection information shall  populate REGIS with information to create a summons to a property owner.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes

Yes

Yes 61 The  system shall provide for re‐inspections and fees that result in the generation of a bill to  cite the violator shall be approved by a supervisor. 62 The system shall be able to process inspections based upon user‐defined critieria, including but  not limited to trash clean‐up, mowing of weeds, dangerous buildings, vehicles, paint,  maintenance of yard areas and structures, the insides and outsides of properties, etc. 63 The system shall provide for functionality to indicate dates and times, lists of violations, and  schedules for activities for the Inspections.

Yes

37

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 64 The system shall provide for priority ranking for demolitions based upon user‐defined criteria. 65 The system shall be able to track demolition activites, including but not limited to contractor,  amount, and time lines. 66 The system shall be able to assign contractors associated with inspections, such as the  assignment of contractor to mow weeds; the system shall notify the contractor via the  generation of an e‐mail of the assigned work. 67 The system shall be able to be updated by photographs taken from phones. 68 The system shall be able to maintain photographs. 69 The system shall be capable of batch scheduling inspections from a single screen. 70 The system shall have the ability to automatically insert a re‐inspection fee based on the failed  status of an inspection. 71 The system shall be able to automatically email the contractor/developer of inspection results.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes Yes

Yes 72 The system shall provide for the ability to view a centralized overview of all inspectors and  assignments. 73 The system shall have the ability to associate a unique duration with each inspection type, or  set quantity to allow for a daily “cap” of inspections. 74 The system shall have the ability to require specific inspections to be completed before  allowing subsequent inspections to be added. 75 The system shall have the ability for Re‐inspection fees to be automatically added based on a  failed inspection. 76 The system shall be able to track inspections by type, inspector, scheduled date and completed  date. 77 The system shall have the a bility to configure security to assure that only authorized persons  are allowed to sign‐off on an inspection.

Yes

38

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 78 The system shall include fields to record inspection information, including permit issuance  date, location(s), and sign‐offs. 79 The system shall be able to schedule and record annual inspections, such as for license  agreements. 80 The sytem shall enable an inspector to indicate ADA compliance. 81 The system shall provide that a department shall be able to view other departments' work that  is occurring. 82 The system shall be able  to display on a map and also report on all of the violations and work  Yes that is occurring in a user‐specified area. 83 The system shall provide that for items such as a liquor license, the system shall be able to  designate that anything within 150 feet of a park, etc., is under the jurisdiction of the Parks &  Recreation Department. 84 The system shall be able to to indicate how close a task/activity is to a school, church, etc.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

85 The system shall allow multiple inspectors to perform inspections and perform sign‐offs, with a  final inspection. 86 The system shall be able to identify the parcel(s) that are associated with sidewalks that are in  need of repairs. 87 The system shall be able to designate +/‐ 1,000 parcels associated with a sidewalk repair. 88 The system shall have the ability to assign sidewalk repairs to a project. 89 The system shall allow an inspector to create a list of parcels in need of sidewalk repairs. 90 The system shall have the ability to track quantities  of square feet of sidewalk, curbs, drives,  approaches (user‐defined types of sidewalks).

39

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 91 The system shall have the ability to track both pre‐construction and post‐construction  quantities and prices  and tie both to a project. 92 The system shall provide that if a section of sidewalk associated with a project is repaired, and  another section of sidewalk is later repaired, the system shall have the ability to create another project for the property. 93 The system shall be able to plot warranty inspections on a map to route inspections. 94 The system shall be able to indicate warranty periods (example ‐ sidewalks may have a two  year warranty) and graphically show locations, and provide notifications when a warranty  inspection is due. 95 The system shall provide that after a  plumber's work and the related inspection, the details  are entered into the Hansen work order system, the system shall be able to accept an interface  for the closing out of the applicable permit. 96 The system shall allow the use of an Interactive Voice Response (IVR) touch‐tone telephone to  enter and cancel inspection requests, perform inquiries on inspection results, and accept  inspection results; the system shall provide assistance to the visually impaired.     For those  with hearing impairments, the system shall incorporate TTY and relay system capabilities into  the system. 97 The system shall  provide a method of assigning inspections to an inspector for specific period  of time (i.e. daily, weekly) and to review by such time period. FOOD INSPECTIONS 1 The system shall have a violation library of FDA violation that are linked to individual items on  an inspection form. The system shall report on the number of risk factor/inspection violations for an  2 establishment.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

 

40

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 3 The system shall report on the number of repeat risk factor/inspection violations for an  establishment. 4 The system shall report the Time In and Time Out for an inspection. 5 The system shall allow the creation of Risk Categories (such as High, Medium, and Low) for  establishments. 6 The system shall allow Risk Categories to have selection periods for inspections (annual,  quarterly, etc.). 7 The system shall allow the creation of Establishment Types. 8 The system shall allow for the recording of inspection results, with user defined codes.

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

The system shall allow for user‐defined inspections, including but not limited to the following: Yes 9 Foodborne Illness Risk Factors and Public Health Interventions related to the following:  Supervision; Employee Health; Good Hygienic Practices; Preventing Contamination by Hands;  Approved Source; Protection from Contamination; Potentially Hazardous Food  Time/Temperature; Consumer Advisory; Highly Susceptible Populations; Chemical;  Conformance with Approved Procedures.  10 Good Retail Practices (Good Retail Practices are preventative measures to control the addition  of pathogens, chemicals, and physical objects into foods).  The system shall provide for the  indication of Not in compliance and Corrected On Site and/or Repeat violation related to the  following items: Safe Food and Water; Food Temperature Control; Food Identification Food  ID); Prevention of Food Contamination; Proper Use of Utensils; Utensils, Equipment and  Vending; Physical Facilities. 11 The system shall provide for the recording of Temperature Observations related to the  following: a) Item Location and Temrature ( Degrees F).

41

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # b The system shall provide for the recording of Observations and Corrective Actions related to  the following: Item Number; Violation, with designation for 'Critical Violations'.

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

c The system shall provide for indicating if a follow‐up inspection is required, if so the date to  occur.  d The system shall provide for recording the establishment's 'Person‐In‐Charge' and the  Inspector in charge during the inspection and capture their signatures after inspection. BUSINESS LICENSE 1 The system shall  capture base data for new business and track review status across multiple  departments. Routing to departments to be user‐defined and controlled by type of license. Yes 2  The system shall  provide an on‐demand list of outstanding applications. 3 The system shall provide for duplication of data elements during transaction entry. 4 The system shall provide for additional (separate) charges for special fees and assessments to  be part of business license billing and collection. 5 The system shall track receivables and calculate late penalties for fees owed (penalty  percentage varies with length of delinquency). 6 The system shall provide fee calculations, billings, and collections. Fees based on flat fees with  user defined 'add‐on' fees as well as fees based on receipts of business.

Yes Yes

7  The system shall allow for progressive rate increases and prorations for partial‐year payments. 8 The system shall provide for multiple fee structures with an effective date for each.  

42

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 9 The system shall automatically determine the appropriate fee structure based on issue date of  the license. 10 The system shall provide  for multiple or user‐defined licensing periods (monthly, quarterly,  semiannual, multi‐year) with separate fees for each period. 11 The system shall provide automatic generation of renewal notices, reminder letters, billings for  use with multi‐part mailers in user‐specified order.  12 The system shall provide for multiple notices to be mailed if license not renewed through the  first mailing. 13 The system shall provide a report of businesses from prior year who have not renewed their  licenses or permits. 14 The system shall provide on‐demand printout of delinquent accounts and delinquency notices  for use with multi‐part mailer forms. Notice shall include space for a free‐form message of  Yes atleast 256 characters. 15 The system shall provide the ability to indentify SIC code for each type of license. 16 The system shall provide periodic or on demand summaries of license activity levels by  business class, licensing period and other user‐defined criteria 17 The system shall provide online search/query by business name, license type, owner name,  location, or business corporate officer's name. The system shall provide partial name capability  Yes on business name and owner name. 18 The system shall provide reports of all newly licensed businesses and of selected business  types for use by other departments. 19 The system shall permit capture of information on hazardous operations or materials by parcel  and address for police/fire/building usage. 20 The system shall provide for businesses that are exempt from normal fees, charges.

43

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

 

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 21 The system shall provide for identification of non‐renewable license types.Renewal notices  shall not be produced for these types of licenses. 22 The system shall provide for identification of types of licenses where no partial year  discounting should be used. The system shall automatically bypass discounting these licenses.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

23 The system shall provide user‐defined check‐list for each type of license for tracking items such  as insurance, state licenses, bonds, and other required documents 24 The system shall provide ability to identify fees to be charged only with the first license and  automatically bypassed renewals (such as initial application fee). 25 The system shall provide the ability to print licenses either in batch or on demand during  license processing without exiting the license processing program. 26 The system shall provide for user definition of print formats for licenses and renewal forms.  Format to be determined by type of license. 27 The system shall allow for entry of license deposits prior to entry of license data. Deposits  entered in this manner can be applied to license charges at time of license entry. 28 The system shall provide the ability to generate a request for refund check for overpayment of  license fees. Refunds to be processed after real‐time interfacing with GenTax to offset  liabilities, through an interface to the City's PeopleSoft Accounts Payable module for review  and approval. 29 The system shall allow access from building permits system to validate contractor's business  license. 30 The system shall provide for interface to the City's iNovah system (which interfaces to the  City's PeopleSoft Accounts Receivable module) for posting cash entries to proper accounts.

Yes Yes

44

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 31 The system shall provide that the parcel management database shall provide address/parcel  information for the Business License system. 32 The system shall provide for cash receipts system to validate accounts and update business  license receipts. 33 The system shall interface with the City's GenTax/RevKC system for that system's business  license information. The system shall have an identifier that would tie a location in the  permitting system to a location in GenTax (the business license/arena  fee/Convention&Tourism account number ).  Since not every location has a business license,  we want to use any account number from one of the tax types for that location.

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes

34 The system shall generate e‐mail notices on renewals and for business licenses about to expire, inspections being signed off, permits being issued and/or approved (by application type). 35 The system shall provide for a comprehensive License History tracking by User, date, time  stamp. 36 The system shall  support Multiple License Cycle Types. 37 The system shall support Unlimited User‐defined License Types & Auto‐Generated License  numbers. 38 The system shall be able to track multiple licenses per single Business. 39 The system shall be able to track Registration, Insurance and Expiration information.

Yes

40 The system shall provide for automatic inspection, reviews and fees based on license  templates. PLANNING, ZONNING AND CODE REVIEW PLANNING AND ZONING ‐

45

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 1 The system shall  capture basic project application information and track status of application. Yes 2 The system shall  provide on‐demand listings of planning projects in various sort orders (by  address, type of project, project number, planner assigned, etc.) and with various selection  criteria (status of project, application date ranges, planner assigned). Yes 3 The system shall provide for user definition of data items to be entered based on type of  project. 4 The system shall provide automatic tracking and routing of projects through various user‐ defined processes consisting of agency and other review functions, with user defined sequence  of routing steps and should edit to ensure that steps are being processed in correct sequence. 

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

 

 

5 The system shall provide for electronic collection of such items as agency comments and  conditions as review progresses. Also, shall provide the ability to record review actions made  by various agencies and the time spent in review. 6 The system shall provide the ability to assess fees and collect payments for planning projects.  Fees displayed during processing shall be determined by the type of project with only the fees  applicable to the project type being displayed. 7 The system shall provide the ability to accumulate charges automatically against projects for  hours spent in review as time is entered for review steps. 8 The system shall calculate user‐defined 'key dates' for projects, automatically as part of the  review process for a project. The system shall provide the ability to tie a key date calculation to  a project review step and have the data calculate automatically when the step is complete. Yes

46

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 9 The system shall provide a function for producing summary documents for a project from the  comments and conditions entered during the project review without the user having to retype  these comments and/or conditions. 10 The system shall provide a method to automatically generate user‐defined notification letters  to property owners and others regarding projects and meetings associated with these projects.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

11 The system shall provide a method of producing meeting documents (such as agendas) for all  projects scheduled for a particular meeting and date. These documents shall have the  capability of accessing without rekeying comments and/or conditions. 12 The system shall provide that, as part of the review process for project, any step(s) that are  meetings shall have a calendar of meeting dates available and shall automatically be scheduled  for the next appropriate meeting date when the previous review steps are complete. 13 The system shall provide the ability to access any project by project number, property address,  project description, any of the names associated with the project (owners, developers, etc.)  property parcel number, type of project, and user‐defined look‐up fields. 14 The system shall provide that parcel management shall provide property information for all  properties associated with a project. An unlimited number of properties may be associated  with an individual project. 15 The system shall provide for  cash receipts for payments and update projects. 16 The sytem shall track zoning history. 17 The sytem shall integrate with the City's "Zoning Plus" web‐site, as a reference to City  ordinances. CODE ENFORCEMENT ‐

Yes

47

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 1 The system shall identify violations by parcel. The system shall provide notifications to  responsible party, and establish user‐defined follow‐up inspection program to ensure  corrections are made. 2 The system shall allow user‐defined violation types and related free‐form text. The system  shall allow multiple violations to be associated with a single case. 3 The system shall provide user‐defined notifications (such as e‐mail) to responsible parties  (multiple parties possible per case).  4 The system shall provide automatic follow‐up of pending actions based on due date. 5 The system shall provide method for preparing agendas and backup documentation for cases  reaching Code Enforcement Board or similar board. 6 The system shall  have the ability to record liens on properties generated by code enforcement  actions. Lien transactions from code enforcement applications tshall be automatically applied  to Parcel Management system. 7 The system shall  provide a method of assigning a case to an inspector for follow‐up. Where  appropriate, allow demand reports to be run, sorted by inspector or supervisor.

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes

Yes

8 The system shall  allow free‐form text at the case level, violation level, inspection level, and for  reporting findings of boards and meetings. 9 The system shall  provide ability to locate a case by property address, any of the names  associated with the case, parcel number or user‐defined look‐up field, as well as by case  number. 10 The system shall  provide a method of processing and tracking inspections not related to an  application, case (pending, etc.), or licensed premise.

48

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 11 The system shall accommodate licensing and permitting for license and applications types for  various industries including liquor, taxi cab, livery vehicles, short term loan businesses, catering  companies/businesses, places of amusement (haunted houses, skating rinks), tire dealers and  haulers, adult entertainment places and book stores etc.  Yes 12 The system must be expandable to accommodate new business types.    13 The system shall provide a method to automatically generate user‐defined notification letters  to property owners and others regarding applications within a user‐defines area by zip code  and GIS location. 14 The system shall  provide a method of establishing penalty calculations based on a 'per day'  calculation. User to input start date for the penalty and the system shall keep a running total to date. 15 The system shall provide that cash receipts shall validate code enforcement account number  and penalty amount and update customer balance. 16 The system shall provide that the parcel management database shall provide address and  parcel information to the Code Enforcement system. 17 The system shall  provide an interface to the City's GenTax billing system to produce invoices  for code enforcement fees and fines; review to occur in GenTax  prior to posting. 18 The system shall allow multiple violations to be added to a single case while tracking each  resolution and status individually. 19 The system shall have the ability to associate one or more Municipal Codes with a violation  case. 20 The system shall provide that user rights determine which users are able to view Case  information/details.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

 

49

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 21 The system shall have the ability to create a Case Details Report which itemizes all details  pertaining to the case, including the photos attached. 22 The system shall  have the ability to view all details of a case from a single screen or report.

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes

23 The system shall have the ability to track all activities on the record, including when a phone  call is made, a letter is printed, etc. 24 The system shall have the ability to restrict access to the Complainant information to only  Code Officers. 25 The system shall have the ability to print images associated with the case into a letter. 26 The system shall be able to designate departmental responsibility, such as which department is  responsible for maintaining a trail on a property, etc. 27 The system shall have the ability to assign permit, project, code violation, and complaint types  to specific departments. 28 The system shall have performance management for turn‐arounds of work performed. 29 The system shall have functinality for Response times –  as a function of the measurement  tool, response times for Fire, PD or MAST shall be able to be calculated for any given property. TRACKING COMPLAINS & VIOLATION 1 The system shall be able to track and report on the number, type, and status of violations and complaints for all applications, including code enforcement activity and performance and maintenance bonds.  

Yes

50

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 2 The systemshall interface with the City PeopleSoft CRM module‐Support‐Action Center Citizen  Complaint Tracking system, which is used by all City departments to record and route citizen  complaints.  The system shall be able to retrieve complaint data from the Citizen Complaint  Tracking system and incorporate the complaints to related applications.   3 The system shall have a citizen complaint module that tracks individual complaints not related  to a licensed premise 4 The system shall provide that the tracking functions shall  include, but not be limited to:Date of  complaint and notice of violation received; Department, division, individual assigned to  respond; Date of inspections; Actions required and taken; Resolutions; Follow‐up and ongoing  monitoring. 5 The system shall track complaints and violations; examples of complaints and violations that  the system shall track include, but are not limited to: Building Code Violations; Zoning Code  Violations; Lack of Permit and Others, as defined by user. 6 The system shall have capabilities for information holds, permit holds without affecting  another department's work and any hard holds. 7 The system shall provide for the ability to create unlimited complaint forms. 8 The system shall provide for the ability to create unlimited Frequently Asked Questions (FAQ).

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

  Yes

9 The system shall provide for the ability to associate FAQ and Complaint forms. 10 The system shall provide the ability to create survey forms and associate forms to specific  complaint forms. 11 The system shall provide for the ability to automatically route complaint information to the  appropriate department. 12 The system shall provide for the ability to store contact information for site of complaint and  complainant.

51

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 13 The system shall have the ability to set up hearing calendars for liquor board and taxi cab  violation meetings. Tracking Legal Action Requirements: 14 The system shall have the ability to indicate the responsible department for a property (such as who will maintain streetlights, cut grass, etc.). 15 The system shall have the ability to establish and track legal deadlines including but not be limited to mentioned here. The system shall allow default dates other than the current system date to be automatically entered for these dates with manual override capability:Date and type of legal action; Required public hearings and meetings; Mandatory action dates; Appeal dates; Ordinance number and effective date; Date of which notices of determination are filed with city county/state.   Yes Fee, Billing, and Payment Requirements: Yes 1 The system shall the ability to calculate and bill permit fees. 2 The system shall be able to calculate fees, and interface with the City’s iNovoh cashiering system; the system shall accept a real‐time interface from iNovah to update the payment status in the system.  3 The system shall provide that the fee and payment collections functions of the system shall include, but not be limited to: 4 Automatic fee and penalty calculation and collection 5 Automatic and user defined fee and penalty schedules for each type of application or groups of Yes applications or types Yes 6 Provide ability to utilize GIS parcel data to calculate fees (footages) 7 Allow manual override and additional fees to be added as needed 8 Issue receipts at multiple locations and workstations (cashiering functions)

52

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

 

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 9 Allow and record fee payments to be made by cash, check, credit card, and money order

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes 10 Assign receipt number to every transaction, even voided payments, and store receipt numbers  permanently in payment history. 11 Verify information during payment entry, including all account numbers, batch dates, and  payment amounts 12 Provide warning messages for partial payments, overpayments, duplicate payments, and cash  only customers 13 Allow reversal of payments from payment history for returned checks 14 Provide the ability to generate refunds back to applicant 15 Allow fees to be based on value, type of service, mathematical calculations, parcel area, and  other user defined fee criteria 16 Generate “no fee” permits/applications for City use, excluded from calculations of general  permit fees  17 Produce revenue collections reports by application type, aggregate and period (monthly,  quarterly, annual, fiscal) 18 The system shall provide  a fee payment screen to see the history of payments for the dept  over years. 19 The system shall  allow for the disabling of old fees and the creation of new fees. 20 The application table design shall allow for determination of a fee paid with the date of the  inspection, rather than solely the paid date.  This query will be designed for Fire Prevention.

Yes

Yes

Yes

 

21 The application  table design shall allow for the attribution of fee quantity per fee type and  total amounts attibuted to the inspector within a parameterized period.  This query will be  designed for Fire Prevention.

53

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 22 The system shall allow for calculation of fees by quantity and varying costs.This could include  an initial cost and a constant cost per permit thereafter.   23 There shall be a yes/no field (checkbox) on the billing screen (Applicant) labelled for internal  billing. (The default will be blank.) 24 A payment screen shall include the transfer of data from the Kiva Fee Pmt screen and allow for  the grouping of FireID's to allow for one check payment to apply to multiple locations (i.e.  school districts, complexes).  If the payment doesn't balance, it should not allow the entries. 25 A payment screen should include a check number field. 26 Generate “no fee” permits/applications for legally excluded applicants and license types   27 The system shall provide for internal billing  (IATV) by allowing for the sending, receiving, and  finance department to approve permit fees by a city department within the system assigning a  unique key to the approval. 28 The system shall have the ability to track fees and issue bills for yearly license renewals. 29 The system shall be able to generate billing letters 30 The systems shall be able to generate bills by user defined criteria, including but not limited to  zoning bills by foot. 31 The system shall be able to process the collection of money. 32 The system shall  provide for reviews and approvals to occur on an application before a  payment can be made. 33 The system shall provide for a code to be provided to an applicant, which the applicant must  enter to enable them to make a payment.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes

Yes Yes

54

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 34 The system shall have the ability to interface with the City's GenTax/RevKC system, to provide  that system with information for assessment billings (including quantities and prices associated with sidewalk work). 35 The system shall have the ability  to create an address for water service billing purposes only. 36 The system shall provide for the ability to search and determine if a reported occurrence is  already in the system, such as the previous reporting of a sign violation at a location, a  basketball goal in the street, etc. 37 The system shall provide for the search for and the reporting of the number of violations at an  address. FINANCIAL 1 The system shall track fee collections and receivable and generate payment receipts. 2 The system shall allow for fees to be charged and collected that result in a credit balance for a  permit application. The system shall allow this credit balance to be applied later to other fees  for the application. 3 The system shall allow tracking of construction bonds posted for permit applications. The  system shall produce refund checks for bond amounts, and other refunds, through an interface  to the City's PeopleSoft Accounts Payable module. 4 The system shall allow 'what if' type of fee calculations to answer inquiries from the public  regarding various permit application possibilities. The system shall produce printed fees listing  for each estimate. 5 The system shall allow for the voiding of bad checks‐clearing amount paid with proper  accounting security

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes

Yes Yes

55

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 6 The system shall provide that the shopping cart shall integrate with the City’s merchant  provider at the time of implementation.  The City’s current merchant provider is Elavon.   Transaction authorization and settlement shall occur through a gateway that is mutually  Yes acceptable to the vendor and the City. CASH RECEIPTS 1 The system shall be updated to reflect receipts associated with permit payments. 2 The system shall enable the recording of payments from customers. 3 The system shall be abe to track monies received and calculatate interest associated with  Yes pending demolitions. 4 The system shall provide for the application of payments to assessments. 5 The system shall provide that cashiering functionalities shall be in the City's iNovah system,  which shall interface with the system. 6 The system shall allow setup of customers for electronic funds transfer for bank drafting from customer saving/checking accounts through automated clearing house (ACH). Yes 7 The system shall have the ability to associate fees to a specific account number. 8 The system shall provide the ability to determine the source of funding for a project and the  costs associated with a project. IT RELATED: GIS AND SECURITY CITY'S WEBSITE ‐ 1 The system shall have real‐time mapping and shall be able to link approved or pending licenses  Yes to a to the City ESRI based maps. Yes 2 The system shall have proper Administrator  defined security to access the system. 3 The system shall provide that an Age of Pavement overlay shall be tied to an address for  measurements, with graphics.

56

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

 

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 4 The system shall provide for the viewing of parking meters and parking lanes on maps.

Mandatory 

5 The system shall include options to save and retrive x,y, and z coordinates, of point and linear  infrastructure, and be able to see the depth of conduits on maps. 6 The system shall have the capability to store and retrive GPS coordinates and time stamps of  pictures, and the system shall show a point on a map when and where a picture was taken  with a hyperlink to the picture. 7 The system shall have the ability for a user to click on a map and assign coordinates. 8 The system shall use a database schema that is non proprietary and shall be owned by the City.

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes Yes Yes

9 The system shall be compatible with handheld devices/App Format 10 The system shall provide the ability to identify who owns a parcel that is next to a streetlight or  an attachment. 11 The system shall have mapping functionality; a user shall be able to click on a streetlight on a  map and see the associated documents such as cooperative and maintenance agreements. 12 The system shall provide the ability to review plot information to obtain addresses associated  with streetlights. 13 The system shall provide the ability to indicate a signage address. 14 The system shall have the ability to identify the location and to indicate whether a property is  owned or leased by the City, and differentiate between the two. 15 The system shall have the ability to look‐up and locate properties on an ARC viewer.

Yes

16 The system shall have the ability to indicate if a property is residential or commercial. 17 The system shall have the ability to identify and track ownership of roads, including 'paper'  streets which have not been paved.

57

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 18 The system shall provide that all  fee schedules existing in the City's systems shall be  converted. 19 The system shall provide that all existing plan reviews and comments in the City's system shall  be converted. 20  The system shall provide that solid color layers (like the KC and National Register listed sites or  Minor Home Repair target areas) shall be transparent on the printed map (like the 500 Year  Floodplain layer) so that parcels and other “covered” layers are visible (the transparency  function is nice while viewing but needs to be made a part of the final printable map. 21 The system shall provide that there shall be be a legend that indicates the specific layers that  have been turned‐out for a given map. 22 The system shall have an interactive measuring tool. 23 The system shall provide that the mapping system shall be capable of easily importing updated  floodplain layer information once FEMA has approved the work the City has invested in, and  has updated their Flood Insurance Rate Maps. There shall be the 100 Year Floodplain, 500 Year  Floodplain, and the Floodway identifiable (the latter would provide a more accurate depiction  of the “regulated streams” as well as provide a satisfactory representation of the Floodway for  Floodplain Management requirements as promulgated at 24 CFR Part 55)

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes

24 The system shall have functionality for Air Quality – The system shall be able to have  monitoring stations in our jurisdiction mapped and data associated with each monitor’s  readings (current and historical) accessible to City staff.

58

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 25 The system shall have functionality for Contamination ‐ Known Brownfields, Superfund (NPL)  Sites, underground storage tanks, and drycleaning facilities (current and historical) ‐ for thesee,  the system hall be able to have them mapped and made accessible to City staff that utilize  such data. The parcels affected, not current and historical addresses, shall be associated with  these sites. 26 The system shall provide that Environmental Site Assessments conducted in association with  tracts of land or corridors (in anticipation of future development)shall be identified in mapping  layers (those that meet the current AAI or ASTM 1527‐05 standards would be identified in one  layer with a certain color, while older, similar ESAs would be identified in their own layer with  their own color (transparent layers that allow the parcels to be visible on the resulting printed  map), and shall be accessible to City staff. 27 The system shall have functionality for Noise / Traffic – data associated with traffic volume on  a given roadway shall be able to be gathered and maintained in a database that would then be  represented in a layer of the mapping system. Both City and State data shall be provided in  separate layers, with historical data accessible within the associated database(s), and shall be  accessible to City staff 28 The system shall provide that a customer shall be able to begin the permit/licensing process  from the City's kcmo.org website 29 The system shall provide that a link on the City's kcmo.org website shall take the customer to  the permit/license system. 30 The system shall provide that after selecting the link and entering the system, a customer shall  be able to complete their application and upload any necessary attachments.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes

31 The system shall provide that the customer shall be able to check a box to indicate acceptance  of conditions (in essence, as their 'signature' of approval)

59

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 32 The system shall provide that as the customer's application is being workflowed for review and  approval, the customer shall be notified electronically (e‐mail, text message, etc.) if their  application is incomplete or has missing information. The customer shall be able to submit  information needed to complete the application.  An e‐mail address and/or telephone number  shall be provided to the customer to enable the customer to ask questions. 33 The system shall provide the ability to apply a digital signature of the person who authorized  the approval of the permit. 34 The system shall provide that if customer's application for permit is not approved, the denying  reason/comments shall be sent to the customer electronically (e‐mail, text message, etc.). 

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes

35 The system shall provide that when the application is approved, the customer shall be notified  electronically (e‐mail, text message, etc.) that their application has been approved for payment and of the amount due, and a link shall be provided for the customer to select to make a  secure, on‐line payment. 36 The system shall provide that after selecting the payment link, a customer shall be able to  enter debit/credit card/ACH  information to enable the processing of their payment. 37 The system shall provide that after a customer's debit/credit card/ACH  payment has  processed, the customer shall receive a payment confirmation, which the customer shall be  able to print. 38 The system shall provide that after a customer's debit/credit card/ACH payment has  processed, the customer shall receive a paid permit that is displayed on their screen, which the  customer shall be able to print.

60

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 39 The system shall provide that if a customer desires not to make an on‐line payment via  debit/credit card/ACH, the customer shall be advised of the City's addresses associated with in‐ person and mailed‐in payments, and the customer shall be able to on‐line print a permit notice  that indicates the amount due.  40 The system shall provide that on‐line applications, approvals, payments, permits issued, etc.,  shall be reflected in the system. 41 The system shall provide for customized forms for different activities  for the customer to fill in  if the customer does not have internet capabilities,  which then the City staff will enter into the  system to process via the approval workflows, etc., indicated within these requirements. 42 The system shall automatically incorporate data (with override capability) from existing files,  such as property ownership information from the GIS database. Automatic data entry shall  include, but not be limited to the current 17 items such as Parcel numbers and its size,  Property Address, propoerty owner information etc. 43 The permit tracking system shall be able to automatically interface and incorporate  information from the City's GIS (Geographic Information Systems) database (e.g. validate  addresses, check zoning, flood zones, easements, property ownership, legal description, etc.).  And be able to pull land information, permit types, ownership, zoning, taxes due etc 44 The system shall be able to access selected information from the City's GIS parcel database and automatically incorporate applicable fields of activities to be tracked. Examples of this  information include: 45 Section, township, and range 46 Validate address accuracy for existing parcels and issue new addresses for new subdivisions, or  parcels with addresses 47 Comprehensive Plan Designations

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes

  Yes

61

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 48 49 50 51 52 53 54 55 56

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Zoning, Land Use Census track and block traffic area zone Resident names, phone numbers Ownership date(s) Parking assessment or other special district Commerical/industrial/residential square footage Number of dwelling units Ad hoc items (such as hazardous materials, easements, special setbacks, number of parking  spaces, etc.) 57 The system shall enable a user to click on a map to retrieve information, including multiple lots  at  a time. 58 The system shall provide that the GIS functionality of the system shall include a display of a  photo with distances (measurement of distances between point‐to‐point). 59 The system shall be able to work with hand‐held devices with GIS, for tieing to a parcel via a  spatial relationship. 60 The system shall extract GIS mapping information from the City’s mapping system and show all  licenses active, and pending or denied by type in a user‐defined geographical area

Yes

Yes 61 The system shall integrate with the latest version of ESRI GIS systems. 62 The system shall be able to create GIS Permits, lot/splits, place the IT/GIS comments for  developers and reviewers, and sign‐off activities for platting 63 The system shall use GIS maps and shall calculate distances and linear feet and accommodate  City ordinances that have formulas for the calculations of permits.

62

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 64 The system shall provide options to query and retrieve information based on user defined  data, including but not limited to spatial quering via a GIS interface. 65 The system shall allow receiving and storing building plans in electronic form (CAD drawings or  images). Security: 1 The system shall have different levels of security based on groups, rolls, department etc.  Within the groups the department supervisor or their designee will be able to provide the type  of access viz: Read, Read and Write Or Read, Write and Delete to that staff.  Wherever the  permission is given for Cancel, Delete or change vital information an audit trail shall be  established.  These activities shall be carried out within the application level and not at the  Yes database level. 2 The system shall provide for security from changes in the inspection history and payment  history without proper accounting processes. 3 The system shall provide for permissions to restrict who can view and run selected reports. Yes 4 The system shall provide that a  calculation screen shall include the transfer of data from the  existing system allowing for a selection of calculation formats including first permit as one fee  plus following fees as a second fee increment.  A zero fee  or fee exempt should be permitted. 5 The system shall allow  invisible, secured fields internally and based on permissions and also  apply the restriction to  Internet publication. 6 The system shall provide for the creation of new fields/text boxes/comment fields listed  viewable only within the originating department. 7 The system shall prevent the exporting of data by departments without proper authorization.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes Yes Yes

63

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 8 The system shall provide that pages shall have the option for field‐level security, and not be  Yes restricted to form/page‐level security. 9 The system shall allow user‐defined security to authorize individuals to approve plan review  steps for each agency. 10 The system shall provide a method for multiple departments to use the system with security  options for each department. Where appropriate, the system shall sort reports by department. Yes 11 The system shall have levels of security and access for but not limited to : Customer Service  (lowest level);  Investigators (moderate level); Supervisors (higher level); Administrator  (highest level)  12 The system shall be able to limit who can create addresses, perform land transactions, create  permits, and perform other functionalities. 13 The system shall allow the ability to add, edit, and inactivate users 14 The system shall be able to disable user accounts that have not been used within a specified  period of time. 15 The system shall be able to integrate with the City's 'Active Directory' for validations of  Yes network users. 16 The system shall provide for determining/designating items that are not part of public records  and therefor are not able to be viewed by the general public (such as pending items); the  system shall be able to tag information that is not available for public viewing. Yes 17 The system shall provide that photos are available for public viewing unless tagged as not for  public view. 18 The system shall provide that a User ID and Password shall be required for both inside (City  employees) and outside (public) users of the system.

64

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 19 The system shall provide that the City's Action Center shall be able to view departmental work  orders. 20 The system shall provide for the ability for public users to access information as read only. A  departmental user shall not be able to change another department's permit. Only authorized  users shall be able to make changes to the system. 21 The system shall have real‐time mapping and shall be able to link permits to a map. 22 The system shall provide controls and capabilities to allow and/or limit accessing system  specific information via web browser. 23 The system shall have the windows Graphical User Interface (GUI) that makes extensive use of  Yes list and pull‐down menus, tables etc. 24 The system shall be able to be used via touch‐screens. 25 The system shall be able to display warning messages to inform users if the system is nearing  capacity of alliowed users. 26 The system shall provide hardware diagnostic assistance and data file integrity checking  through the operating system. 27 The system shall allow for the ability to continue to work with a buffer capacity if tablet  connectivity fails and later is re‐established for an upload. 28 The system shall have an audit log to track who made changes to a field. Yes 29 The system shall be compatible with iPads and other tablets. 30 The system shall be able to archive and purge data based upon criteria. 31 The system shall be able to assign coordinates to photos. 32 The system's mapping functionality shall include the ability of a customer to drag a 'push‐pin'  to indicate where service is needed (such as at a street intersection, area of a park, etc.).

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

33 The system's mapping functionality shall include longitudes & latitudes, cross‐streets, etc. Yes

65

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 34 The system shall be able to configure End‐User settings at the application level with proper  Administration authority without relying on the IT Department or Vendor’s Help Desk. DATA HANDLING 1 The system shall automatically incorporate data for a single application or group of related  application activities once it has been input, such as the owner information entered on the  setup of the building construction general permit shall automatically be incoporated into the  subsequent related building permits and inspections. Likewise, the system shall automatically  incorporate the contractor information from the contractor license application upon setup of  building permits. 2 The system shall allow data input of items including but not limited to the following : a b c d e f g h i j k 3

Manual input of application specific data (such as project description) User controlled defaults for input fields Easy correction and editing of data entries Automatic detection of typical data errors (numeric, dates, time i.e not accept 0208 in a date  field etc.) Default corrections to prevent duplicate updates, deletion errors Holds/comments to be placed on application processing Approvals/issuance of different application dependencies Comments and related text information Applicant(s) information (name, address, etc., if not in system) Personal data information (required on some license applications) Inspection results The system shall allow users to add text and import text or other data files from other data bases into the permitting application (e.g. project descriptions, standard conditions of approval, project comments, etc.).

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes Yes  

Yes

66

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 4 The system shall be menu driven, and shall allow the manual input of application‐specific data  (i.e., description). 5 The system shall maintain permanent storage of all records current,past, deleted and inactive. Yes 6 The system shall provide the ability to archive data, and the ability to access archived data 7 The system shall data map and convert all data in the City's current system. 8 The system shall provide easy retrieval and purging of old data. 9 The system shall provide that all application codes, rates, fee structures, internal lists,  condition or application dependencies (such as plan approval, checklist, or a permit  prerequisite for issuing another type of a permit), or business rules shall be table driven. 10 The system shall be able to convert data into multiple data formats to accommodate different  operating systems and database management systems. 11 The system shall be available in a multiple‐user environment and provide data locking and  buffering routines to prevent loss of information by simultaneous updates.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes Yes

Yes

Yes 12 The system shall provide a robust tool for the use of electronic documents such as building  plans, including the ability to receive, manage, review, and store electronic documents; and  shall include robust plans review tools including, but not limited to, automatic version  comparison, ability to tag plans to review comments, automatic tracking/navigation to review  comments (segregated for an unlimited number of different reviewers), hover zoom tools, etc. Yes 13 The system shall have the ability to record a digital signature and automatically assign it to an  application or a document which will be valid for all legal purposes including  prosecution of  violators.

Yes

67

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 14 The system shall provide for quick data entry‐‐ allowing for typing  one permit/hazard after  another (i.e. autofill, drop down list) for the same inspection, without having to create new  permitting information. 15 The system shall allow the Calculated Date  to be editable by the authorized user. 16 The system shall have the ability to have photographs of applicants on licenses (liquor licenses,  Yes taxicab licenses, etc.) 17 The system shall enable the attachment of .pdf,xml,excel and word documents along with   Yes storing of digital files such as photographs, plans etc. 18 The system shall provide that users shall be able to download information from the system  Yes into formats such as Excel, Word etc. 19 The system shall have additional/free form fields available on screens, for future use. Yes

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

20 The system shall be able to handle/create barcodes.  Example: The system shall have a linked  barcode to print on the permit so that people with bar code apps can scan it and bring up the  permit information.  The system shall be able to scan any paperwork with a barcode on it so  that it gets attached to the correct permits. 21 The system shall have one central repository that all the notes/comments show up, so users  wouldn’t miss notes in one place if they looked in another area of the system. 22 The system shall have the ability to pull external content/website information into the system. 23 The system shall utilize a centralized database of information for contractors, applicants,  property owners, etc. 24 The system shall auto‐populate for repeating information such as Vendor name, fee, standard  scopes, etc. REPORTS,QUERIES AND FORMS 1 The system shall have the ability to create and use standard and ad‐hoc reports.

Yes Yes Yes

68

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 2 The system shall provide that all numerica fields shall be sign‐controlled. Yes 3 The system shall include standard reporting functions. 4 The system shall generate reports on user‐defined topics and on user selected fields and data.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

5 The system shall have logical controls for processing pre‐numbered documents. 6 The system shall generate activity or inactivity reports automatically on a user determined  time schedule. 7 The system shall include the capability to generate additional standardized forms associated  with permits that automatically incorporate permit information such as Public Notices,  Certificates, and other standardized form (e.g. Notices of Incomplete). 8 The system shall provide that all reports shall include organization name, report title, column  headings descriptions, processing date, sequentially numbered pages, and subtotals after  every sort level break on the standard letter head where required. 9 The system shall have the ability to scroll or page through records or files on screen in either  forward or backward direction, or to call up a single record directly by key. 10 The system shall be able to report or query on any data in the system and save those reports  and queries for future repeated useage. 11 The system's reports shall be able to be manipulated (re‐sorted, etc.) by a user after report  generation. 12 The system shall run formal reports from inside the system and avoid sending to a desktop  mail merge technology. 13 The system shall have the ability to generate reports and queries to monitor inspections,  safety, fee data, personnel,and to provide performance measures based on roles/persmission.

Yes

69

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 14 The system shall enable the creation and completion of forms (such as Notice of Hazard  and  Application For Permit). 15 The system shall have the ability to generate a report of annual inspections that are due .

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes

16 The system shall provide that all Fire  views created from tables shall include the Permit Type  and Permit Number. 17 The system shall provide an exportable daily receipt report selected by department with  subtotals and a total.  The parameterized report will delineate by a payment type (i.e check,  credit card),fee type and list the amount  and an ID associated with each where available.  18 The system shall provide that the annual inspection assignment report shall run irrespective of  whether corrections have not been completed. 19 The system shall provide for a customer receipt to be printed directly from a screen. 20

21

22 23 24 25

The system shall provide that the customer receipt shall fit within the window of the envelope  and shall include the the listed fire permits on the a single sheet (a current report). The system shall provide for a report that will list the online payment data including, but not  limited to the fees, date paid, ID, and location.  Those receipts shall also be included with the  daily receipt report. The system shall address document  printing needs.  Shall provide for custom reports to pull  information from fields for mass mailing and individual letters. The system shall have the ability to print renewal notices for licenses and permits with photos  of the applicants if required. The sytem shall be able to generate letters, such as 30, 60, and 90 day letters. The system shall be able to generate the reports currently generated by Regulated Industries  thru their existing EnerGov system.

Yes

Yes

70

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 26 The system shall be able to produce reports of licenses for selected criteria, such as by zip code  and district etc. 27 The system shall provide that a user shall be able to generate renewals based upon user‐ defined criteria (such as expiration date). 28 The system shall have ad hoc reporting in a controlled environment with meta data  Yes capabilities. 29 The system shall generate reports by parcel information, such as accidents within a 6‐mile  radius, abandoned buildings in an area, criteria that includes council district or neighborhood  Yes district, etc. 30 The system shall provide reporting tools that are easy to use by end users. 31 The system shall provide that End‐Users shall not be required to have a copy of a specific  report writer to execute standard reports. 32 The system shall have the ability for Users to select Favorite reports and group them into a  personal archive for future use. 33 The system shall provide that a user shall be able  to view a preview of report prior to printing.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

34 The system shall be able to track the history of reports a user has performed. 35 The system shall provide that a user shall be able to designate criteria for reports and queries,  including but not limited to date parameters, permit types, fee codes, etc. 36 The system shall be able to develop all of the existing permits, forms, letters and reports. Yes 37  The system shall have standard Monthly report capability 38 The system shall provide for the ability to peform user‐defined queries, such as how many  excavation permits were issued during a month / year and other historical reports.

71

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 39 The system shall provide the ability to run a report based on permits issued during a certain  time period (Date, month, year,open, closed, done, canceled, voided, etc).

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

40 The system will generate management reports for  outstanding assignments, past due dates  for investigations and applications 41 The system shall track and facilitate on‐line status lists and reports of applications. 42 The system shall be able to track and report on the number, type, send status of violations and  complaints for all applications, including code enforcement activity and performance and  maintenance bonds. 43 The system shall provide flexible, effective and easy to use search queries capabilities for users  that can seek out and retrieve information quickly from any one or multiple applications. 44 The system shall be able to develop and generate standard forms that incorporate database  information, without depending on customized programming. 45 The system shall be able to track the customer's performance and the system shall advise  applicant of past due items and outstanding documents. (Such as lags due to the customer's  response time; example ‐ incomplete applications by the customer, etc.) 46 The system shall provide for quick searches, to bring up an establishment by a FireID, an  establishment address, or an applicant name. 47 The system shall provide for the ability to create shortcuts or search by fields including the  FireID  (4 or less steps to bring up location). 48 The system shall be able to identify a person to a license, license type or bills/invoices 49 The system shall enable a user to determine the status of items and track and report on  history.

72

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 50 The system shall provide that all end‐Users shall have the ability to edit and save their own  search parameters. 51 The system shall enable an end‐user to configure information that is displayed on their screen.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

52 The system shall allow users to select from different displays to personalize their own screens. 53 The system shall utilize templates for all permit, case, and project types. 54 The system shall enable a user to search and query documents, such as a covenant to  maintain, as‐built records, bonds, insurance, water/sewer/storm records, etc.; users in all  departments shall be able to perform such searches/queries. 55 The system shall provide the ability for user searches, such as by address, intersection,  segment of corridor, timeline, and other user‐defined criteria. 56 An interface shall be provided to pull data from the system into Microsoft Access and for the  running of reports. 57 The system shall produce statistical reports of permits issued by a user‐defined data range.

Yes

58 The system shall produce statistical reports of the types of applications submitted, inspected  and other inspection activities by user‐defined data range. 59 The system shall provide statistical reports of plan review processing including numbers of  applications processed, average days to process, etc. 60 The system shall provide government agency reports (such as the C‐404 report). 61 The system shall provide reports of Certificate of Occupancy activity. 62 The system shall provide reports of permit listings by contractor. 63 The system shall provide contractor file mailing labels. 64 The system shall provide expiration reports with option to print letters for expiring permits.

73

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 65 The system shall provide owner builder reports. 66 The system shall provide turnaround reports; example ‐ how many inspections were  performed within a user‐defined time period. 67 The system shall have the ability to print an audit report by transaction type (vehicle receipts,  utility receipts, etc.) that includes general ledger account number, description, customer  account number, transaction ID number, amount distributed to each GL account, account  totals. 68 The system shall have the ability to report on all payments received by type and by  department on a weekly or monthly basis. 69 The system shall have the ability to print a receipt showing transaction type, description,  payment amount ,date, payer. 70 The system shall provide report features that include, but not be limited to: a Generate routine federal, state, county and local reports b Report on issued permits, expired permits, status of inspections, inspection schedules, list of  renewal notices, fees collected, etc. c Number and type of approvals, permits, inspections for specific periods and time frame (e.g.  weekly, monthly, quarterly and annual reports) d Residential units, lots approved, buildings demolished e Statistics on different types of use permits (e.g. liquor) f Store standard report specifications so that common reports (by user defined subjects such as  area, address, permit type, fees collected, average turnaround time) can be executed with  minimal user definition  g Include statistical reporting functions allowing calculations and totals. h Generate activity or inactivity reports automatically on a user determined time schedule

74

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # i Statistical reporting on additional topic area such as increase in commercial or residential  development. j Generate statistical information though graphic means such as graphs, charts, and other  graphical representations. k  Generate routine and daily reports for cash handing and performance management

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

71 For forms such as permits, licenses, etc., the system shall allow the establishment of templates  for use by departments, and the ability to indicate on the completed form which department  issued it and apply the applicable departmental signature. 72 The system shall provide similar query capabilities and functions listed in Search Queries below  , to allow user to quickly design and develop custom reports 73 The system shall include a reporting design and modeling tools that allow point and click selection of report formats and use of system data  for selection of report data elements. Yes Search Queries: 1 The system shall provide flexible, effective and easy to use search queries capabilities for users  that seek out and retrieve information quickly and efficiently from the applications featuring  standard forms with commonly used fields that do not require custom reports.  Yes 2 The system shall allow users to select data elements from the system and construct both simple and complex query arguments.  3 The system query capabilities shall include, but not be limited to: 4 Use partial name, wild card, and soundex searches 5 Use multiple screens and switch between applications and query functions without having to  exit the system

75

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 6 Use windows type list box forms (screens) and point/click features to scroll through data   table(s) and select data elements and arguments in formulating search queries.

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Define key fields for rapid search and reporting Use default query models to asset users (for example, query wizard) Store user queries (query select statements) for future usage Search for multiple items or a combination of items with one search (List the number of  parameters/ conditions that can be searched) 11 Print reports of search query results and generate user tables of query results and store for  additional query manipulations and reports. 12 The system shall provide that system queries shall include ascending and descending features. 

7 8 9 10

13 The system shall have a query tool to enable users to create their own queries.  Forms: 1 The system shall be able to develop and generate standard forms that incorporate database information, without depending on customized programming. The system should provide easy to use form design features that enable system users to develop and generate standard forms.

Yes

2 The system shall provide form modeling tools (forms wizards) that assist users in selecting and  modifying standard form models, including database elements to be printed. The system  should provide similar data element selection capabilities and functions listed in Search  Queries above , to allow user to quickly develop custom forms. (gf)

3 The system shall be able to produce forms and formats that include, but not be limited to:Applications, Receipts, Permits, Licenses, Certificates, Inspections, Notices, Templates and Letters etc.

76

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 4 The system shall have forms online with auto‐fill capabilities. 5 The system shall provide free‐form memo/comments fields capable of being restricted by  permissions within a department (i.e. billing instructions)  INTERFACES/INTEGRATIONS 1 The system shall interface/integrate with the following City systems: 2 PeopleSoft Financials Management System (FMS) ‐ General Ledger, Accounts Receivable, and  Yes Projects modules Yes 3 PeopleSoft Customer Relationship Management (CRM) ‐ Action Center/Support Yes 4  Geographic Information System (GIS)‐‐ESRI Yes 5  iNovah cashiering system Yes 6 Hansen (Water Service's Work Order/Asset Management System) Yes 7 Social Media, such as FaceBook Yes 8 GenTax (FAST)‐‐City's Revenue System (business license information) Yes 9 The City's Zoning Plus web‐site (reference for City ordinances) Yes 10 The City's kcmo.org web‐site 11 REGIS (citations on the Citys' Municipal Court system); example ‐ inspection information shall  populate REGIS with information to create a summons to a property owner. Yes 12 LUCI (City's ordinances and regulations),  to be able to look up City ordinances  and develop  Yes regulations in Luci. 13  eBuilder  (Capital Projects Management System; also provides for electronic submittal of  Yes documents)  Yes 14 Active Directory for validations of network users. 15 Archibus (a real estate management system used by the City) Yes Yes 16  Banner, the City's Water billing system Yes 17 Fire Record Management System (RMS) 

77

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

 

(gf)

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 18 19 20 21

CAD system MuniCode Elavon (the City's merchant provider) The system shall provide for integration to the City's iNovah cashiering system (which  interfaces with the City's PeopleSoft General Ledger) for posting of cash and other entries to  proper accounts. 22 The system shall have the ability to create bills and invoices, which shall be interfaced to the  City's iNovah system (which interfaces with the City's PeopleSoft system).

23 The system shall be able to issue refunds, which are interfaced to the City's PeopleSoft  Accounts Payable module for reviews and approvals in PS‐AP. 24 The system shall provide that for cash receipts, the system shall validate account number and  penalty amounts and update customer balance. 25 The system shall provide that the parcel management database shall provide address and  parcel information to the building permits system. 26 The system shall provide for verification of contractor's business license from the building  permits system. 27 The system shall  provide communication of conditions and other pertinent information from  planning and zoning projects related to permit property locations.

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Yes Yes Yes

Yes

Yes Yes

28 The system shall be able to automatically create a Work Order from a 311/Action Center case. 29 The system shall interface with the City's PeopleSoft Customer Relationship Management  (CRM) system's Action Center/Support module.  30 The system shall  maintain chart of account information consistent with the City's PeopleSoft  financial system's General Ledger module.

Yes

78

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 31 The system shall keep track of General Ledger accounts for the various permits, licenses, etc.  that are collected within the application. 32 The system shall allow for the ability to connect with multiple reporting tools, M.S. Access,  Crystal Reports, etc. given read only privileges. 33 The system shall provide for the viewing of another department's information, such as if the  Water Department has closed a street for water main repairs, etc. 34 The system shall have permitting and inspection functionalities that interface with the City's  Cartegraph system with an option to automate updating pictures, plans and other relevant  information. 35 The system shall provide that customer calls that are entered into the Hansen system's  compaint module and applicable inspections recorded in Hansen's inspection module shall be  able to be interfaced to the new permitting system for the issuance of permits. Yes 36 The system shall be able to interface with both the City's PeopleSoft CRM Action Center and  the City's Hansen system for requests for services and the resulting generation of permits.

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

 

37 The system shall interface with and populate Public Work's 'Light ID' Access database with  data. MISCELLANEOUS  PRINTING  ‐ 1 The system shall have the ability to record and print permits. 2 The system shall allow for interactive printing of permits using user‐defined permit print  formats. The system shall allow notes from plan review and general application notes to be  flagged to print on the permit. 3 The system shall allow for user option of printing either combination permits (multiple permits  per form) or single permits (one permit per form).

79

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 4 The system shall allow user to define type of certificate to print (example: Temporary  Certificate of Occupancy vs. Certificate of Occupancy). 5 The system shall allow a user to perform edits prior to printing certificate for such items as all  fees paid, all permits finalled, etc. 6 The system shall be able to convert and print permits, forms, query results, etc., into various  formats, including, but not limited to: All Microsoft Office suite (Excel, Word, etc.), pdf, xml  reports, etc. 7 The system shall have the ability to record and print licenses, permits and individual permits  (2”x3 ½” cards) 8 The system shall allow for printing one individual permit card or batch print by date or other  criteria. 9 The system shall allow for the printing of all Fire permits on one page for one inspection   (avoid multiple hard copy permits) 10 The system shall provide printing setup that shall support the following requirements:

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

a Multiple printers b Several printing connection options such as allowing printers to be: c connected to a network printer, allowing groups of computers  to connect to one printer, as  well as allowing individual computers a choice of printer connections  d Printing of permits, receipts, forms etc. with proper alignment, in final letter quality and on  preprinted forms e Printing by screen, document, multiple documents or file f Numerous printing options, such as Preview, to a Printer selected by user, to a File, in formats  such as .pdf, etc. 11 The system shall allow for clear printing from a heavy duty impact printer‐‐a web server should  not affect the quality of the font.

80

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 12 The system shall be able to print permits on a printer (ribbon, etc.) in the field. 13 The system shall provide that all aspects of the software shall comply with the Department of  Justice's ADA requirements. LIST OF PERMITS,INSPECTIONS AND APPLICATIONS USED IN THE CURRENT SYSTEM: City Planning & Development: 1 Board of Zoning Adjustments Conditional User Permits 2 Board of Zoning Adjustments Zoning Variances 3 Land Use Plan Amendments 4 Lot Splits and Minor Plats 5 Plan Amendments 6 Development Plan Reviews 7 Plat Reviews (Preliminary and Final) 8 Street and Valley Vacations 9 Zoning Changes 10 Zoning Changes with Plan 11 353 Projects Codes Administration section of City Planning & Development: 1 Building Plan Reviews ‐ Commercial 2 Building Plan Reviews ‐ Residential 3 Permits ‐ General 4 Permits ‐ Building Demolition 5 Permits ‐ Building Moving 6 Permits ‐ Electrical 7 Permits ‐ Mechanical 8 Permits ‐ Plumbing

81

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Permits ‐ Fire  Protection Permits ‐ Sign Permits ‐ Elevator Permits ‐ Mechanical Refrigeration Permits ‐ Building General Inspections ‐ Building Demolition Inspections ‐ Building Moving Inspections ‐ Electrical Inspections ‐ Mechanical Inspections ‐ Plumbing Inspections ‐ Fire Protection Inspections ‐ Sign Inspections ‐ Elevator Inspections ‐ Mechanical Refrigeration Inspections ‐ Outdoor Advertising Sign Inspections Periodic Inspections ‐ Elevator Periodic Inspections ‐ Communications Tower Periodic Inspections ‐ Mobile Home Development Periodic Inspections ‐ Underground Space Periodic Inspections ‐ Parking Structure Certificates of Occupancy Investigations ‐ Zoning Enforcement Contractor Licenses and Registrations Qualified Supervisor Certificates Floodplan Certificates Encroachment Ordinances

82

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Land Development section of City Planning & Development: Review‐Public Improvement Plan Review Review ‐ Development Agreements : Review, Routing, Digital Signing and Digital Storage Review ‐ As‐built Record Review Review ‐ Shop Drawing Reveiw Review ‐ Easement Release Review Review ‐ Stormwater Drainage Study Reveiw Review ‐ Final Plat and Supplemental Documents Review Permits ‐ Curb Construction Permits ‐ Driveway Construction Permits ‐ Excavation (utility street cuts) Permits ‐ Sanitary Sewer Connection Permits ‐ Sanitary Sewer Construction Permits ‐ Sidewalk Construction Permits ‐ Maintenance Period Permits Permits ‐ Storm Sewer Construction Permits ‐ Street Construction Permits ‐ Signal Construction Permits ‐ Site Disturbance Construction Permits ‐ Street Light Notifications ‐ Blasting Notification Permits ‐ Banners in Street Right‐of‐way Permits ‐ Development Permits {incompasing all individual types above}   Process Types in new system shall accomplish all existing SE% Permit Types, and SEE% Types  ‐ Public Work Department: Permits ‐ Annual Street Utility

83

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45

1 2 3 4

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Permits ‐ Block Party Permits ‐ Dumpster/Trailer Permits ‐ Encroachment Permits ‐ Hauling Permits ‐ Housing Moving Permits ‐ Oversize/Overweight Load Permits ‐ Parade Permits ‐ Residential Parking (Temporary and Annual) Permits ‐ Special Event Permits ‐ Street Closing Permits ‐ Street Use Permits ‐ Traffic Control Permits ‐ Festivals Permits ‐ Races (running, walking, bicycling, etc.) Permits ‐ Emergency No Parking Permits ‐ Street Plate Permit Inspections ‐ Street pavement: rating of streets Inspections‐ Traffic Signals Permits ‐ Streetlights Permits ‐ Attachments to streetlights (such as banners, shot‐spotters, TimeWarner cable,  Google, etc.)  Water Services Department: New residential water service (KIVA permit WS01) New commercial domestic water (WS02) New commercial fire protection water service (WS03) Extension‐ repairs, install meter, extend service  (WS04)

84

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 5 Renewal‐ kill old service and make new tap/connection (WS05) 6 Kill water service @ main (WS06) 7 Backflow‐installed on all new commercial domestic water Lawn irrigation and fire protection.  Also residential units when served by one tap for more than two units (WS07) 8 9 10 11 12 13 14 15 16 17 18 19 20 1 2 3 4 5 6 7

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

New Diversional waste‐ sewer allowance credit meter (WS08) Water main replacement‐ transfer services from one main to another (WS09) To establish account only‐ need register (WS10) Sewer only‐ currently not being used (WS11) Side arm for compound meter‐ full flow fire meter (WS12) Deposit to retain water service‐ must reuse service in one year (WS13) Sewer connection fee‐ slant inspections (WS14) Lawn irrigation (WS15) Full Flow Fire meter‐ service line with private fire hydrants (WS16) Replacement Sac meter‐ existing account in Banner (WS17) Renew Expired permit (WS18) Disconnect Service Line @ the Curb‐ Retainers Only (WS19) Pipeline Kills for Dangerous Buildings (WS20) Neighborhoods & Housing Department ‐ Regulated Industries: Liquor by the Drink License Liquor by the Package License Adult Entertainment License Amusement Device Exhibitor Catered Event Catering License Combo ‐ Restaurant/Bar License

85

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 1 2 3 4

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Combo ‐ Tavern License Combo – Tavern/Amusement License Combo – Theater License Dance Hall License Day Labor License Salvage Yard License Secondary Metal Recyclers License Short Term Loan License Side walk café license (no alcohol) Taxi Permit Theater License Tire Dealer License Vehicle for Hire License Waste Tire Hauler License  Waste Tire Site License Individual licenses and permits, including but not limited to: Adult Liquor Permits Adult Entertainment Permits Taxi Cab Permits Sight‐seeing Permits Tow Truck Driver Certifications Neighborhoods and Housing  Department Dangerous Building Inspections Work Access Permits Vacant Building Registrations Rental Housing Registrations

86

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line #

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Fire Department: The system shall provide for 'Interior' inspections, including, but not limited to the following: 1 a b c 2 a b c d 3 a b c 4 a b a 6 v a b b

Exit Doors  ‐ Locks  ‐ Obstructions  ‐ Marked Exit Ways  ‐ Obstructions  ‐ Marked  ‐ Illumination  ‐ Access to Exit Exit Signs  ‐ Illumination  ‐ Posted  ‐ Condition Aisles  ‐ Arrangement  ‐ Proper Width Fire Walls  ‐ Condition Fire Doors  ‐ Condition  ‐ Operation  ‐ Marked  ‐ Obstructions

87

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 7 a b c 8 a b 9 a b c d e f 10 a b c d 11 a b c d e f

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Fire Stopping  ‐ Vertical Openings  ‐ Horizontal Openings Storage     ‐ Condition  ‐ Height  ‐ Housekeeping Electrical  ‐ Temporary Wiring  ‐ Electrical Hazards  ‐ Electrical Motors  ‐ Extension Cords  ‐ Multi Plug Adapters  ‐ Access to Panels Flammable and Combustibles  ‐ Storage  ‐ Dispensing  ‐ Source of Ignition  ‐ No Smoking Signs Fire Extenguishers  ‐ Condition  ‐ Location  ‐ Type  ‐ Access  ‐ Marking  ‐ Inspection Date

88

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 11 a b 12 a b c d 13 a b c d 14 a b c d e 15 a b 16 a b 17

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Hood System Vents  ‐ Clean  ‐ Filters Hood Extinguishing System  ‐ Condition  ‐ Inspection Date  ‐ Access to Remote Pull  ‐ Instructions Posted Sprinkler/Standpipe  ‐ Condition  ‐ Access  ‐ Inspection Date  ‐ Fire Hose Fire Alarm System  ‐ Panel Access  ‐ Condition  ‐ Pull Station Access  ‐ Detectors  ‐ Supervised Occupant Load  ‐ Posted  ‐ Overloaded Hazardous Materials  ‐ Storage Marked  ‐ Building Marked Compressed Gases

89

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # a  ‐ Secure b  ‐ Storages The system shall provide for 'Exterior' inspections, including, but not limited to the following: 18 a b 19 a b 20 a b c 21 a 22 a b 23 a b c 24 a b

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Address  ‐ Posted  ‐ Visible / Legible Fire Hydrant   ‐ Condition  ‐ Obstruction Housekeeping  ‐ Trash  ‐ Grass & Weeds  ‐ Trash Dumpster Exit Ways  ‐ Clear Fire Dept. Access  ‐ Access Provided  ‐ Fire Lanes Marked Fire Dept. Connections  ‐ Accessible  ‐ Marked  ‐ Condition Outside Storage  ‐ Location  ‐ Neat & Orderly

90

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line Mandatory  SUP # 25 Gas Meter a  ‐ Protection The system shall have the ability to create permits including, but not limited to, the following: 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Aerosol Products Amusement Building Aviation Facility Carnivals and Fairs Battery Systems Cellulose Nitrate Film Combustible Dust‐Producing Materials Combustible Fibers Compressed Gases Covered Mall Buildings Cryogenic Fluids Cutting and Welding Dry Clearing Plants Exhibits and Trade Shows Explosives Fire Hydrants and Valves Flammable and Combustible Liquids Floor Finishing Fruit and Crop Ripening Hazardous Materials HPM Facilities High‐Pile Storage

91

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Hot Work Operation Industrial Ovens Lumber Yards and Woodworking Plants Liquid or Gas‐Fueled Vehicles or Equipment in Assembly Buildings LP‐Gas Magnesium Miscellaneous Combustible Storage Open Flame and Candles Organic Coating Place of Assembly Privant Hydrants Pyroxylin Plastics Refrigeration Equipment Repair Garage Rooftop Hellport Spraying or Dipping Storage of Scrap Tires and Byproducts Temporary Memb., Structures, Tents, and Canopies Tire Rebuilding Plant Waste Hauling Wood Products  ‐ Health  Department inspections: Food Swimming Pools Lodging Child Care

92

7/16/2013

CITY OF KANSAS CITY, MO ENTERPRISE PERMITTING AND LAND MANAGEMENT SYSTEM List of Requirements Key  SUP ‐ Supported as delivered "out of box"  PSUP ‐ Supported through an intergrated partner soultion  PADD ‐ Supported through add‐on products offered by partners 

3RD ‐ Supported through a third party solution  CST ‐ Supported via a customization (changes to source code)  FUT ‐ Will be supported in future release  NS ‐ Not supported  Mandatory  ‐ YES. For 'must have' factors 

System requirements are outlined in the table below . The vendor should carefully review each requirement and mark your response as indicated. One Response Per Requirement Line # 74 75 76 77 78 79

Mandatory 

SUP

PSUP PADD MOD

3RD

CST

FUT

NS

Comments

Septic Trucks Noise Smoking Air Quality General Sanitation Lead Poison Neighborhoods&Housing Services Department‐HUD Environmental Reviews 1 Environmental Reviews Parks and Recreation Department: 1 Construction (replacement of sidewalks, etc.) Others: 1 License agreements (such as for outdoor dining, valet parking, other 'encroachments', etc.) 2  Utility license agreements (such as for Kansas City Power & Light, KCMO Water, Missouri Gas  Energy, Time Warner, Google, etc.), for requirements for the utility such as liability, insurance,  legal, etc. 3 General Services  ‐ Real Estate 4 Permits ‐ Fiber Optics Access ‐ for areas such as the KC Power & Light District

93

7/16/2013

SECTION III SPECIAL INSTRUCTIONS AND CONDITIONS

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 36 of 63

AUTHORIZED SIGNATURE FORM

By submission of the RFP, the undersigned certifies that: 

It has not paid or agreed to pay any fee or commission, or any other thing of value contingent upon the award of this contract, to any City of Kansas City, Missouri employee or official or to any current consultant to the City of Kansas City, Missouri;



It has not paid or agreed to pay any fee or commission or any other thing of value contingent upon the award of this contract, to any broker or agent or any other person;



The prices contained in this proposal have been arrived at independently and without collusion, consultation, communication or agreement intended to restrict competition;



It has the full authority of the Offeror to execute the proposal and to execute any resulting contract awarded as the result of, or on the basis of, the proposal;



Proposer will not withdraw the proposal for ninety (90) days.



By the below signature, I hereby certify that I have both the legal authority from my business/firm and the right to enter into this contractual agreement with the City of Kansas City, Missouri, and have read, understood, and hereby fully accept all the terms, conditions, specifications, and pricing information contained within this document as well as any and all subsequent pages, addenda, and notices.

Authorized Representative: Signature: Title: Business/Firm Name: Address: City, State, Zip: Telephone Number: Fax Number: E-mail Address: E-mail Address for Purchase Orders: Date:

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 37 of 63

COOPERATIVE PROCUREMENT WITH OTHER JURISDICTIONS

The Proposer agrees to provide products and/or services to any municipality, county, state, governmentally public utility, non-profit hospital, educational institute, special governmental agency, and non-profit corporation performing governmental functions that participates in or is represented by the Mid-America Council of Public Purchasing (MACPP) in the greater Kansas City Metropolitan Trade Area and any member of the Mid-America Regional Council (MARC). Yes No

Authorized Representative: Signature: Title: Business/Firm Name: Date:

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 38 of 63

STANDARD CITY CONTRACT

MASTER CONTRACT FOR PRODUCTS AND SERVICES - THE CITY OF KANSAS CITY, MISSOURI CONTRACT NO.: EVXXXX TITLE/DESCRIPTION: XXXX

THIS Contract is between KANSAS CITY, MISSOURI, a constitutionally chartered municipal corporation (“CITY”), and __________________________________________________ (“CONTRACTOR”). Sec. 1. The Contract. The Contract between the CITY and CONTRACTOR consists of the following Contract Documents: (a)

this Contract;

(b)

CONTRACTOR’s Proposal dated _________ that is attached hereto and incorporated into this Contract;

(c)

CITY’s RFP No. _____ that is incorporated into this Contract by reference;

(d)

any and all Attachments and Exhibits attached to the Contract. All documents listed in this Section 1 shall be collectively referred to as the “Contract Documents” and are incorporated into this Contract. CITY and CONTRACTOR agree that the terms “Agreement” and “Contract” and “Contract Documents” are used interchangeably in this Contract and the terms “Agreement” and “Contract” and “Contract Documents” each include all “Contract Documents.”

Sec. 2. Initial Term of Contract and Additional Periods. (a)

Initial Term. The initial term of this Contract shall begin on ____________, ____ and shall end on ______________________, ____. The Manager of Procurement Services is authorized to enter into an amendment of this Contract with CONTRACTOR to extend the term of this Contract and time of performance for this Contract.

(b)

Renewal Terms. At any time prior to the expiration of the initial term or any subsequent term, the CITY, in its sole discretion, may renew this Contract for up to four (4) additional one (1) year terms.

(c)

Transition Term. Notwithstanding the expiration of the initial term or any subsequent term or all options to renew, CONTRACTOR and CITY shall continue performance under this Contract until the CITY has a new contract in place with either CONTRACTOR or another provider or until the CITY terminates the Contract.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 39 of 63

Sec. 3. Compensation. A.

The maximum amount the CITY shall pay CONTRACTOR under this Contract shall not exceed $_____________________. CITY shall pay CONTRACTOR on the following basis: (Fill in how the Contractor is to be paid. For example, by the hour or by the job. Do not use a contingency fee arrangement unless this is the standard industry practice used to compensate the Contractor. Examples: Debt collection, real estate agents, etc.)

B.

CONTRACTOR shall bill the City, in a form acceptable to the City, on the following basis: monthly, one time; other (select when the Contractor will bill the City and delete all others).

C.

CITY shall order all services to be provided by CONTRACTOR under this Contract by means of a Purchase Order issued by the CITY’s Manager of Procurement Services for which funds have been certified and encumbered by the City’s Director of Finance. CITY shall not have any financial obligations to CONTRACTOR under this Contract until the CITY issues a Purchase Order to CONTRACTOR. CONTRACTOR shall not provide any services in excess of the dollar amount contained in any Purchase Order and CONTRACTOR shall not be entitled to any payment in excess of the dollar amount of the Purchase Orders from CITY.

Sec. 4. Effective Date of Contract. (a)

Notwithstanding Section 2 of this Contract, neither party has any obligation under this Contract until the Manager of Procurement Services issues a Purchase Order which shall be signed by the City’s Director of Finance certifying there is a balance, otherwise unencumbered, to the credit of the appropriation to which the expenditure is to be charged, and a cash balance, otherwise unencumbered, in the treasury, to the credit of the fund from which payment will be made, each sufficient to meet the obligation incurred in the Purchase Order.

(b)

The date of the first Purchase Order issued by the CITY is the effective date of this Contract.

(c)

The date of the first Purchase Order issued by the CITY after the CITY renews this Contract shall be the effective date of the renewal term or transition term.

Sec. 5. Invoices. (a)

CONTRACTOR shall submit to CITY a request for payment (hereinafter “Invoice”) for services performed in sufficient detail for the CITY to determine that the amount CONTRACTOR is requesting is in fact due and payable.

(b)

CITY shall not pay any Invoice from CONTRACTOR unless CONTRACTOR is in compliance with, and not in breach or default of, all terms, covenants and conditions of this Contract. If damages are sustained by CITY as a result of breach or default by CONTRACTOR, CITY may withhold payment(s) to CONTRACTOR for the purpose of set off

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 40 of 63

until such time as the exact amount of damages due to CITY from CONTRACTOR may be determined. (c)

CITY shall not process CONTRACTOR’s Invoice unless CONTRACTOR’s Invoice is in proper form, correctly computed, and is approved by CITY as payable under the terms of this Contract.

(d)

CITY is not liable for any obligation incurred by CONTRACTOR except as approved under the provisions of this Contract.

(e)

If CONTRACTOR is required to meet MBE/WBE goals for this Contract, CONTRACTOR shall not submit an Invoice to the City unless CONTRACTOR’s Invoice is accompanied by a copy of the most recent 00485.01 M/WBE Monthly Utilization Report submitted by CONTRACTOR to the City’s Human Relations Department. CONTRACTOR shall remain current on CONTRACTOR’s filing of 00485.01 M/WBE Monthly Utilization Reports. CITY shall not pay CONTRACTOR’s Invoice unless CONTRACTOR is current on CONTRACTOR’s filing of 00485.01 M/WBE Monthly Utilization Reports.

Sec. 6. Representations and Warranties of CONTRACTOR. CONTRACTOR hereby represents and warrants to the CITY the following: (a)

CONTRACTOR is in good standing under the laws of the state of Missouri and each state in which it does business, except any such state where the failure to be in good standing would not have a material adverse effect on CONTRACTOR’s ability to perform this Contract in accordance with its terms.

(b)

The execution, delivery and performance by CONTRACTOR of this Contract have been duly authorized by all necessary corporate action and do not and will not (i) require any consent or approval of CONTRACTOR's board of directors; (ii) require any authorization, consent or approval by, or registration, declaration or filing with, or notice to, any governmental department, commission, board, bureau, agency or instrumentality, or any third party, except such authorization, consent, approval, registration, declaration, filing or notice as has been obtained prior to the date hereof; (iii) violate any provision of any law, rule or regulation or of any order, writ, injunction or decree presently in effect having applicability to CONTRACTOR or its articles or by-laws; and (iv) result in a breach of or constitute a default under any material agreement, lease or instrument to which CONTRACTOR is a party or by which it or its properties may be bound or affected.

(c)

CONTRACTOR shall not enter into any contract for the services to CITY that purports to grant a security interest or right of repossession to any person or entity respecting the services, or any portions thereof or chattels placed thereon.

(d)

There is no litigation, proceeding or other investigation pending or, to the knowledge of CONTRACTOR, threatened against CONTRACTOR which would prevent consummation of the transaction contemplated by this Contract or would have a materially adverse effect on CONTRACTOR.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 41 of 63

Sec. 7. Survival of the Representations, Warranties and Covenants. All representations, warranties and covenants expressed herein shall survive the execution of this Contract for the benefit of the parties hereto. Sec. 8. Governing Law. This Contract shall be construed and governed in accordance with the laws of the State of Missouri without giving effect to Missouri’s choice of law provisions. The CITY and CONTRACTOR: (1) submit to the jurisdiction of the state and federal courts located in Jackson County, Missouri; (2) waive any and all objections to jurisdiction and venue; and (3) will not raise forum non conveniens as an objection to the location of any litigation. Sec. 9. Termination for Convenience. CITY may, at any time upon fifteen (15) days written notice to CONTRACTOR specifying the effective date of termination, terminate this Contract, in whole or in part. Sec. 10. Default and Remedies. (a)

If CONTRACTOR shall be in default or breach of any provision of this Contract, CITY may terminate this Contract, suspend CITY’s performance, withhold payment or invoke any other legal or equitable remedy after giving CONTRACTOR ten (10) days written notice and opportunity to cure such default or breach.

(b)

If CITY shall be in default or breach of any provision of this Contract, CONTRACTOR may terminate this contract or suspend CONTRACTOR’s performance after giving CITY ten (10) days written notice and opportunity to cure such default or breach.

Sec. 11. Waiver. Waiver by CITY of any term, covenant, or condition hereof shall not operate as a waiver of any subsequent breach of the same or of any other term, covenant or condition. No term, covenant, or condition of this Contract can be waived except by written consent of CITY, and forbearance or indulgence by CITY in any regard whatsoever shall not constitute a waiver of same to be performed by CONTRACTOR to which the same may apply and, until complete performance by CONTRACTOR of the term, covenant or condition, CITY shall be entitled to invoke any remedy available to it under this Contract or by law despite any such forbearance or indulgence. Sec. 12. Acceptance. No payment made under this Contract shall be proof of satisfactory performance of the Contract, either wholly or in part, and no payment shall be construed as acceptance of deficient or unsatisfactory services. Sec. 13. Records. (a)

For purposes of this Section: 1.

“CITY” shall mean the City Auditor, the City’s Internal Auditor, the City’s Director of Human Relations, the City Manager, the City department administering this Contract and their delegates and agents.

2.

“Record” shall mean any document, book, paper, photograph, map, sound recordings or other material, regardless of physical form or characteristics, made or received in connection with this Contract and all Contract amendments and renewals.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 42 of 63

(b)

CONTRACTOR shall maintain and retain all Records for a term of five (5) years that shall begin after the expiration or termination of this Contract and all Contract amendments. CITY shall have a right to examine or audit all Records, and CONTRACTOR shall provide access to CITY of all Records upon ten (10) days written notice from the CITY.

(c)

The books, documents and records of CONTRACTOR in connection with this Contract shall be made available to the City Auditor, the City’s Internal Auditor, the City’s Director of Human Relations and the City department administering this Contract within ten (10) days after the written request is made.

Sec. 14. Affirmative Action. If this Contract exceeds $300,000.00 and Contractor employs fifty (50) or more people, Contractor shall comply with City’s Affirmative Action requirements in accordance with the provisions of Chapter 38 of City’s Code, the rules and regulations relating to those sections, and any additions or amendments thereto; in executing any Contract subject to said provisions, Contractor warrants that it has an affirmative action program in place and will maintain the affirmative action program in place for the duration of the Contract. Contractor shall not discriminate against any employee or applicant for employment because of race, color, sex, religion, national origin or ancestry, disability, sexual orientation, gender identity or age in a manner prohibited by Chapter 38 of City’s Code. Contractor shall: (a)

Submit, in print or electronic format, a copy of Contractor’s current certificate of compliance to the City’s Human Relations Department (HRD) prior to receiving the first payment under the Contract, unless a copy has already been submitted to HRD at any point within the previous two (2) calendar years. If, and only if, Contractor does not possess a current certification of compliance, Contractor shall submit, in print or electronic format, a copy of its affirmative action program to HRD prior to receiving the first payment under the Contract, unless a copy has already been submitted to HRD at any point within the previous two (2) calendar years.

(b)

Require any Subcontractor awarded a subcontract exceeding $300,000.00 to affirm that Subcontractor has an affirmative action program in place and will maintain the affirmative action program in place for the duration of the subcontract.

(c)

Obtain from any Subcontractor awarded a subcontract exceeding $300,000.00 a copy of the Subcontractor’s current certificate of compliance and tender a copy of the same, in print or electronic format, to HRD within thirty (30) days from the date the subcontract is executed. If, and only if, Subcontractor does not possess a current certificate of compliance, Contractor shall obtain a copy of the Subcontractor’s affirmative action program and tender a copy of the same, in print or electronic format, to HRD within thirty (30) days from the date the subcontract is executed.

City has the right to take action as directed by City’s Human Relations Department to enforce this provision. If Contractor fails, refuses or neglects to comply with the provisions of Chapter 38 of City’s Code, then such failure shall be deemed a total breach of this Contract and this Contract may be terminated, canceled or suspended, in whole or in part, and Contractor may be declared ineligible for any further contracts funded by City for a period of one (1) year. This is a material term of this Contract. Sec. 15. Tax Compliance. If the CITY’s payments to CONTRACTOR exceed $123,500.01 for the period of May 1st through April 30th, CONTRACTOR shall provide proof of compliance with the CITY’s tax ordinances administered by the CITY’s Commissioner of Revenue as a precondition to the CITY making the first payment under this Contract. CONTRACTOR also shall submit to the CITY proof of compliance Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 43 of 63

with the CITY’s tax ordinances administered by the CITY’s Commissioner of Revenue as a condition precedent to the CITY making final payment under the Contract. Sec. 16. Buy American Preference. It is the policy of the CITY that any manufactured goods or commodities used or supplied in the performance of any CITY Contract or any subcontract thereto shall be manufactured or produced in the United States whenever possible. Sec. 17. Notices. All notices to be given hereunder shall be in writing and may be given, served or made by depositing the same in the United States mail addressed to the party to be notified, postpaid and registered or certified with return receipt requested or by delivering the same in person to such person. Notice deposited in the mail in accordance with the provisions hereof shall be effective unless otherwise stated in such notice or in this Contract from and after the second day next following the date postmarked on the envelope containing such notice. Notice given in any other manner shall be effective only if and when received by the party to be notified. All notices shall be sent to the following addresses: If to the CITY:

City of Kansas City, Missouri Procurement Services Division 414 East 12th Street, 1st Floor, Room 102 W Kansas City, Missouri 64106 Attention: Cedric Rowan, C.P.M., Manager Telephone: (816) 513-1592 Facsimile: (816) 513-1156

With copies to:

William Geary, Esq. City Attorney Law Department of Kansas City, Missouri 414 East 12th Street, 28th Floor Kansas City, Missouri 64106 Telephone: (816) 513-3118

If to the CONTRACTOR: (INSERT Name and Complete Address) Sec. 18. General Indemnification. (a)

(b)

For purposes of this Section only, the following terms shall have the meanings listed: 1.

Claims means all claims, damages, liability, losses, costs and expenses, court costs and reasonable attorneys' fees, including attorneys’ fees incurred by the CITY in the enforcement of this indemnity obligation.

2.

CONTRACTOR's Agents means CONTRACTOR's officers, subcontractors, successors, assigns, invitees, and other agents.

3.

CITY means CITY, its Agencies, its agents, officials, officers and employees.

employees,

CONTRACTOR's obligations under this Section with respect to indemnification for acts or omissions, including negligence, of CITY, shall be limited to the coverage and limits of insurance that CONTRACTOR is required to procure and maintain under this Contract.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 44 of 63

CONTRACTOR affirms that it has had the opportunity to recover all costs of the insurance requirements imposed by this Contract in its contract price. (c)

CONTRACTOR shall defend, indemnify and hold harmless CITY from and against all claims arising out of or resulting from all acts or omissions in connection with this Contract caused in whole or in part by CONTRACTOR or CONTRACTOR's Agents, regardless of whether or not caused in part by any act or omission, including negligence, of CITY. CONTRACTOR is not obligated under this Section to indemnify CITY for the sole negligence of CITY.

(d)

In no event shall the language in this Section constitute or be construed as a waiver or limitation of the CITY’s rights or defenses with regard to sovereign immunity, governmental immunity, or other official immunities and protections as provided by the federal and state constitutions or by law.

Sec. 19. Indemnification for Professional Negligence. If this contract is for professional services, CONTRACTOR shall indemnify, and hold harmless CITY and any of its agencies, officials, officers, or employees from and against all claims, damages, liability, losses, costs, and expenses, including reasonable attorneys’ fees, arising out of any negligent acts or omissions in connection with this Contract, caused by CONTRACTOR, its employees, agents, subcontractors, or caused by others for whom CONTRACTOR is liable, in the performance of professional services under this Contract. CONTRACTOR is not obligated under this Section to indemnify CITY for the negligent acts of CITY or any of its agencies, officials, officers, or employees. Sec. 20. Insurance. (a)

CONTRACTOR shall procure and maintain in effect throughout the term of this Contract insurance policies with coverage not less than the types and amounts specified in this Section. CONTRACTOR must have: 1.

Commercial General Liability Insurance Policy: with limits of $1,000,000 per occurrence and $2,000,000 aggregate, written on an “occurrence” basis. The policy shall be written or endorsed to include the following provisions: a. b. c. d. e.

Severability of Interests Coverage applying to Additional Insureds Contractual Liability Per Project Aggregate Liability Limit or, where not available, the aggregate limit shall be $2,000,000. No Contractual Liability Limitation Endorsement Additional Insured Endorsement, ISO form CG20 10, current edition, or its equivalent.

2.

Workers’ Compensation Insurance and Employers Liability Policies as required by Missouri law.

3.

Commercial Automobile Liability Insurance Policy: with a limit of $1,000,000 per occurrence, covering owned, hired, and non-owned automobiles. The Policy shall provide coverage on an “any auto” basis and on an “occurrence” basis. This insurance policy will be written on a Commercial Business Auto form, or acceptable

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 45 of 63

equivalent, and will protect against claims arising out of the operation of motor vehicles, as to acts done in connection with the Contract, by CONTRACTOR. 4.

If this Contract is for professional services, CONTRACTOR shall obtain Professional Liability Insurance with limits per claim and annual aggregate of $1,000,000.

(b)

All insurance policies required in this Section shall provide that the policy will not be canceled until after the Insurer provides the CITY ten (10) days written notice of cancellation in the event that the cancellation is for CONTRACTOR’s nonpayment of premiums and thirty (30) days written notice of cancellation to CITY for all other reasons of cancellation.

(c)

The Commercial General and Automobile Liability Insurance Policies specified above shall provide that CITY and its agencies, agents, officials, officers, and employees, while acting within the scope of their authority, will be named as additional insureds for the services performed under this Contract. CONTRACTOR shall provide to CITY at execution of this Contract a certificate of insurance showing all required endorsements and additional insureds.

(d)

All insurance policies must be provided by Insurance Companies that have an A.M. Best’s rating of “A-V” or better, and are licensed or approved by the State of Missouri to provide insurance in Missouri.

(e)

Regardless of any approval by CITY, CONTRACTOR shall maintain the required insurance coverage in force at all times during the term of this Contract. CONTRACTOR’s failure to maintain the required insurance coverage will not relieve CONTRACTOR of its contractual obligation to indemnify the CITY pursuant to this Section of this Contract. In the event CONTRACTOR fails to maintain the required insurance coverage in effect, CITY may declare CONTRACTOR in default.

(f)

In no event shall the language in this Section constitute or be construed as a waiver or limitation of the CITY’s rights or defenses with regard to sovereign immunity, governmental immunity, or other official immunities and protections as provided by the federal and state constitutions or by law.

Sec. 21. Interpretation of the Contract. (a)

CITY selected CONTRACTOR through a negotiated procurement process rather than an Invitation for Bids (IFB) solicitation. Unlike the IFB, this process allows the CITY and CONTRACTOR to discuss and negotiate a contract at arms length prior to entering a final contract that is acceptable to both the CITY and the CONTRACTOR. After negotiation and discussion, CONTRACTOR and CITY have incorporated multiple documents into this Agreement and the meaning of some of the words used in the Agreement may be uncertain, incomplete or duplicative and the Agreement may promise something at one place and take that promise away at another. In sum, the Agreement may contain words and provisions that are susceptible of more than one meaning so that reasonable persons of average intelligence may fairly and honestly differ in their construction of the words and provisions. It is the intent of the CITY and the CONTRACTOR that the CITY’s taxpayers receive the benefit or advantage in the construction and interpretation of this Agreement, regardless of

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 46 of 63

the normal judicial rules of contract construction even if the construction and interpretation of the Agreement will cost the CONTRACTOR more money and time. CITY and CONTRACTOR agree that CITY’s Manager of Procurement Services shall resolve all disagreements as to the meaning of this Agreement or any ambiguity in this Agreement, in favor of the CITY and its taxpayers even if it will cost the CONTRACTOR more money and time. The decision of CITY’s Manager of Procurement shall be final and conclusive if the Manager of Procurement Services acted in good faith. (b)

CONTRACTOR acknowledges and agrees that the CITY has provided CONTRACTOR with an opportunity to have CONTRACTOR’s attorney review and advise CONTRACTOR on the Agreement and any potential ambiguities or areas of disagreement and the potential adverse legal consequences of CONTRACTOR agreeing to this Section as well as the entire Agreement. CONTRACTOR certifies that CONTRACTOR has provided the CITY written notice of all ambiguities, conflicts, errors or discrepancies that it has discovered in the Agreement and the written resolution thereof by the CITY as embodied in this final Agreement is acceptable to CONTRACTOR.

(c)

CONTRACTOR certifies that CONTRACTOR has either (1) waived its right to have CONTRACTOR’s attorney review this Section and Agreement; or (2) CONTRACTOR has consulted with an attorney on this Section and Agreement.

(d)

CONTRACTOR knowingly and voluntarily agrees to this Section and the entire Agreement. CONTRACTOR certifies that this contract was not procured by fraud, duress or undue influence.

Sec. 22. Contract Execution. This Contract may be executed in one or more counterparts, each of which will be deemed an original copy of this Contract and all of which, when taken together, will be deemed to constitute one and the same Contract. This Contract shall be effective upon the execution of counterparts by both parties, notwithstanding that both parties may not sign the same counterpart. The parties' signatures transmitted by facsimile or by other electronic means shall be proof of the execution of this Contract and shall be acceptable in a court of law. Sec. 23. Guaranteed Lowest Pricing. CONTRACTOR certifies that this Contract contains CONTRACTOR’s lowest and best pricing for all services supplied by CONTRACTOR to any government, governmental entity, political subdivision, city, state, school district or any other public entity in the United States as of the date of this Contract. Sec. 24. Assignability and Subcontracting. (a)

Assignability. Contractor shall not assign or transfer any part or all of Contractor’s obligation or interest in this Contract without prior written approval of City. If Contractor shall assign or transfer any of its obligations or interests under this Contract without the City’s prior written approval, it shall constitute a material breach of this Contract. This provision shall not prohibit contractor from subcontracting as otherwise provided for herein.

(b)

Subcontracting. Contractor shall not subcontract any part or all of Contractor’s obligations or interests in this Contract unless the subcontractor has been identified in a format required by City. If Contractor shall subcontract any part of Contractor’s obligations or interests under

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 47 of 63

this Contract without having identified the subcontractor, it shall constitute a material breach of this Contract. The utilization of subcontractors shall not relieve Contractor of any of its responsibilities under the Contract, and Contractor shall remain responsible to City for the negligent acts, errors, omissions or neglect of any subcontractor and of such subcontractor’s officers, agents and employees. City shall have the right to reject, at any point during the term of this Contract, any subcontractor identified by Contractor, and to require that any subcontractor cease working under this Contract. City’s right shall be exercisable in its sole and subjective discretion. City shall not be obligated to pay or be liable for payment of any monies which may be due to any subcontractor. Contractor shall include in any subcontract a requirement that the subcontractor comply with all requirements of this Contract in performing Contractor’s services hereunder. Sec. 25. Professional Services – Conflict of Interest Certification. If this Contract is for professional services other than for medical doctors or appraisers, CONTRACTOR certifies that CONTRACTOR is not an expert witness for any party in litigation against the CITY at the time of the issuance of this Contract. Sec. 26. Intellectual Property Rights. CONTRACTOR agrees, on its behalf and on behalf of its employees and agents, that it will promptly communicate and disclose to CITY all computer programs, documentation, software and other copyrightable works (“copyrightable works”) conceived, reduced to practice or made by CONTRACTOR or its agents, whether solely or jointly with others, during the term of this Contract resulting from or related to any work CONTRACTOR or its agents may do on behalf of CITY or at its request. All inventions and copyrightable works that CONTRACTOR is obligated to disclose shall be and remain entirely the property of CITY. It is agreed that all inventions and copyrightable works are works made for hire and shall be the exclusive property of CITY. CONTRACTOR hereby assigns to CITY any rights it may have in such copyrightable works. CONTRACTOR shall cooperate with CITY in obtaining any copyrights or patents. Sec. 27. Minority and Women’s Business Enterprises. CITY is committed to ensuring that minority and women’s business enterprises (M/WBE) participate to the maximum extent possible in the performance of CITY contracts. If M/WBE participation goals have been set for this Contract, CONTRACTOR agrees to comply with all requirements of City’s Minority and Women’s Business Enterprise Program as enacted in CITY’S Code Sections 38-84 through 38-100.8 and as hereinafter amended. CONTRACTOR shall make its good faith efforts in carrying out this policy by implementing its Contractor Utilization Plan, which is attached as Attachment No. _. If CONTRACTOR fails to achieve the M/WBE goals stated in its Contractor Utilization Plan, as amended, the CITY will sustain damages, the exact extent of which would be difficult or impossible to ascertain or estimate at the time of execution of this contract. Therefore, in order to liquidate those damages, the monetary difference between the amount of the M/WBE goals set forth in this Contractor Utilization Plan, as amended, and the amount actually paid to qualified MBEs and WBEs for performing a commercially useful function will be deducted from the CONTRACTOR’S payments as liquidated damages. In determining the amount actually paid to qualified MBEs and WBEs, no credit will be given for the portion of participation that was not approved by the Director of City’s Human Relations Division, unless the Director determines that the CONTRACTOR acted in good faith. No deduction for liquidated damages will be made when, for reasons beyond the control of the CONTRACTOR, the M/WBE participation stated in the Contractor Utilization Plan, as amended and approved by the Director, is not met.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 48 of 63

Sec. 28. Employee Eligibility Verification. CONTRACTOR shall execute and submit an affidavit, in a form prescribed by the CITY, affirming that CONTRACTOR does not knowingly employ any person in connection with the contracted services who does not have the legal right or authorization under federal law to work in the United States as defined in 8 U.S.C. §1324a(h)(3). CONTRACTOR shall attach to the affidavit documentation sufficient to establish CONTRACTOR’s enrollment and participation in an electronic verification of work program operated by the United States Department of Homeland Security to verify information of newly hired employees, under the Immigration and Reform and Control Act of 1986. CONTRACTOR may obtain additional information about E-Verify and enroll at https://everify.uscis.gov/enroll/StartPage.aspx?JS=YES. For those CONTRACTORs enrolled in E-Verify, the first and last pages of the E-Verify Memorandum of Understanding that CONTRACTOR will obtain upon successfully enrolling in the program shall constitute sufficient documentation for purposes of complying with this section. CONTRACTOR shall submit the affidavit and attachments to the CITY prior to execution of the contract, or at any point during the term of the contract if requested by the CITY. Sec. 29. Emergencies. (a)

(b)

Disaster means any large scale event such as an act of terrorism, fire, wind, flood, earthquake or other natural or man-made calamity which results in, or has the potential to result in a significant loss of life or property. During and after a disaster, CONTRACTOR shall provide special services to the CITY including CONTRACTOR shall open CONTRACTOR’s facilities even on nights and weekends as necessary to meet the needs of the City during a disaster.

(c)

CONTRACTOR shall not charge CITY any fee for opening facilities during an emergency or for extending CONTRACTOR’s hours of operation during a disaster. CITY shall pay CONTRACTOR the agreed upon contract prices for all purchases made by CITY during the disaster and CONTRACTOR shall not charge CITY any additional mark-up, fee or cost for any purchases made by CITY during a disaster.

(d)

CONTRACTOR shall quickly mobilize CONTRACTOR’s internal and external resources to assist CITY when a disaster unfolds.

(e)

Extended hours and personnel. During disasters, CONTRACTOR’s facilities shall stay open 24 hours if requested by the CITY. CONTRACTOR shall utilize additional CONTRACTOR personnel to take CITY orders if necessary. CONTRACTOR’s Call Center shall accept phone orders 24 hours a day.

(f)

CONTRACTOR shall have contingency plans with CONTRACTOR’s suppliers to provide additional supplies and equipment quickly to CITY as needed.

(g)

CONTRACTOR shall cooperate with CITY to properly document any and all expenses incurred by CITY with CONTRACTOR and CONTRACTOR shall assist CITY in meeting any and all documentation requirements of the Federal Emergency Management Agency (FEMA).

Sec. 30. Trade-In. If the solicitation requests a price or value for one or more pieces of equipment to be traded in as part of the purchase of new equipment, the CITY retains the option to purchase the new equipment at the full price or to reduce the price of the new equipment by the amount of the trade-in Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 49 of 63

offered. The CITY is not obligated to accept the trade-in offer and may withdraw equipment offered for trade-in at any time up to award. Sec. 31. Time of Delivery. Delivery is required to be made in accordance with the schedule shown in the solicitation and purchase order. Sec. 32. F.O.B. Destination. Unless otherwise directed in the solicitation and purchase order, all deliveries shall be F.O.B. Destination and all freight charges shall be included in the total price. Supplies shall be delivered to the destination consignee’s warehouse unloading platform, or receiving dock, at the expense of the CONTRACTOR. The CITY shall not be liable for any delivery, storage, demurrage, accessorial, or other charges involved prior to the actual delivery (or “constructive placement” as defined in carrier tariffs) of the supplies to the destination, unless such charges are caused by an act or order of the CITY acting in its contractual capacity. If rail carrier is used, supplies will be delivered to the specified unloading platform of the consignee. If motor carrier (including “piggy-back”) is used, supplies will be delivered to truck tailgate at the unloading platform of the consignee. If the CONTRACTOR uses rail carrier or freight forwarder for less than carload shipments, he shall assure that the carrier will furnish tailgate delivery if transfer to truck is required to complete delivery to consignee. One of the following statements usually will appear on the purchase order, although others may be used. If no statement appears, paragraph 22(a) is applicable. (a)

F.O.B. Destination, Freight Prepaid by Seller. The seller pays and bears all freight charges.

(b)

F.O.B. Destination, Freight Prepaid and Charged Back on Invoice. The seller pays the freight and charges the CITY by adding it to the invoice.

(c)

F.O.B. Destination, Freight Collect. The CITY pays and bears the freight charges.

(d)

F.O.B. Destination, Freight Collect and Allowed on Invoice. The CITY pays the freight charges and deducts the amount from the seller’s invoice.

Sec. 33. Quality. Unless otherwise required by terms of the solicitation, all goods, supplies, and materials furnished shall be new, in current production, and the best of their kind. When applicable, parts and maintenance shall be reasonably available. New equipment that is obsolete or technically outdated is not acceptable. Remanufactured or reconditioned items are not considered new. Items shall be properly packaged, packed, labeled, and identified in accordance with commercial standards acceptable to the trade and as required by ICC and other federal and state regulations. Packing slips will accompany the shipment. Sec. 34. Price. Prices quoted are to be firm and final. All prices quoted shall be net and shall reflect any available discount except for discounts for timely payment. All prices are to be F.O.B. designated delivery point. All shipping, packing, and drayage charges are the responsibility of the supplier. C.O.D. shipments will not be accepted unless otherwise agreed to by the City. Sec. 35. Brand Name or Equal. Whenever the name of the manufacturer or the supplier is mentioned on the face hereof and the words “or equal” do not follow, it shall be deemed that the words “or equal” shall follow such designations unless the face hereof specifies “no substitutions”. The CITY may assume that items submitted are equal or it may request samples and proof thereof and unless approved before shipment, reserves right to return at the CONTRACTOR’S expense all items that are not acceptable as Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 50 of 63

equals, said items to be replaced by the CONTRACTOR with satisfactory items at the original submitted price. Sec. 36. Commercial Warranty. The CONTRACTOR agrees that the supplies or services furnished under this contract shall be covered by the most favorable commercial warranties the CONTRACTOR gives to any customer for such supplies or services and that the rights and remedies provided herein are in addition to and do not limit any rights afforded to the CITY by any other clause of this contract. Sec. 37. Discounts. A.

Prompt payment discounts offered for payment within less than twenty (20) calendar days will not be considered in evaluating proposals for award, unless otherwise specified in the solicitation. However, offered discounts of less than twenty (20) days will be taken if payment is made within the discount period, even though not considered in the evaluation of proposals.

B.

In connection with any discount offered, time will be computed from date of delivery of the supplies to the carrier when acceptance is at the point of origin, or from date of delivery at destination when delivery and acceptance is at destination, or from the date the correct invoice or voucher is received in the office specified by the CITY, if the latter is later than the date of delivery. Payment is deemed to be made for the purpose of earning the discount on the date of mailing of the CITY check.

C.

Any discount offered other than for prompt payment should be included in the net price quoted and not included in separate terms. In the event this is not done, the CITY reserves the right to accept the discount offered and adjust prices accordingly on the purchase order.

Sec. 38. Sellers Invoice. Invoices shall be prepared and submitted in duplicate to address shown on the purchase order. Separate invoices are required for each purchase order. Invoices shall contain the following information: purchase order number, item number, description of supplies or services, sizes, unit of measure, quantity, unit price, and extended totals. Sec. 39. Inspection and Acceptance. Inspection and acceptance will be at destination unless specified otherwise, and will be made by the CITY department shown in the shipping address or other duly authorized representative of the CITY. Until delivery and acceptance, and after any rejection, risk of loss will be on the CONTRACTOR unless loss results from negligence of the CITY. CONTRACTOR will be notified of rejected shipments. Unless agreed otherwise, items will be returned freight collect. Sec. 40. Loss and Damaged Shipments. Risk of loss or damage to items prior to the time of their receipt and acceptance by the CITY is upon the CONTRACTOR. The CITY has no obligation to accept damaged shipments and reserves the right to return at CONTRACTOR’s expense damaged merchandise even though the damage was not apparent or discovered until after receipt of the items. Sec. 41. Late Shipments. Supplier or CONTRACTOR is responsible to notify the CITY department receiving the items and the Senior Buyer of any late or delayed shipments. The CITY reserves the right to cancel all or any part of an order if the shipment is not made as promised.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 51 of 63

Sec. 42. Tax Exemption - Federal and State. A.

The CITY is exempt from Federal Excise and Transportation taxes on purchases under Chapter 32, Internal Revenue Code. The federal tax registration number issued by the St. Louis District Director on November 11, 1974 is No. 43740340K.

B.

The CITY is exempt from payment of Missouri Sales and Use Tax in Accordance with Section 39(10) Article 3, of the Missouri Constitution and Sections 144.040 and 144.615 RSMo 1969 and supplement thereto. A copy of the exemption from Missouri Sales and Use Tax is available upon request.

Sec. 43. Annual Appropriation of Funds. A.

Multi-year term supply and service contracts and leases and the exercise of options to renew term contracts are subject to annual appropriation of funds by the City Council. Payments made under term contracts and leases are considered items of current expense. Purchase orders are funded when issued, therefore are current expense items and are not subject to any subsequent appropriation of funds.

B.

In the event sufficient funds are not appropriated for the payment of lease payments or anticipated term contract payments required to be paid in the next occurring lease or contract term and if no funds are legally available from other sources, the lease or contract may be terminated at the end of the original term or renewal term and the CITY shall not be obligated to make further payments beyond the then current original or renewal term. The CITY will provide notice of its inability to continue the lease or contract at such time as the Manager of Procurement Services is aware of the nonappropriation of funds; however, failure to notify does not renew the term of lease or contract. If a lease is cancelled, the events of default will occur as described in the lease and/or the section titled TERMINATION FOR DEFAULT. The CITY has no monetary obligations in event of termination or reduction of a term contract since such contracts represent estimated quantities and are not funded as a contract, but only to the extent of purchase orders issued.

CONTRACTOR I hereby certify that I have the authority to execute this document on behalf of CONTRACTOR. Contractor: By: Title: Date:

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 52 of 63

APPROVED AS TO FORM

Assistant City Attorney

(Date)

KANSAS CITY, MISSOURI By: Title: Date:

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 53 of 63

NO PROPOSAL RESPONSE FORM

If you choose not to submit a proposal, please complete and return only this form, on or before the due date. Thank you for taking this opportunity to help us update and improve our solicitation process. Senior Buyer: Keely Golden, CPPB

Due Date:

09/09/13

Number:

EV1788

Telephone: (816) 513-3670

Return by Fax: (816) 513-1156

Description: Enterprise Permitting System Please check the appropriate response(s). We respectfully submit “No Response” for the following reason(s): 1. We cannot provide a service to meet the required specifications. 2. The closing date does not allow adequate time to prepare a response. 3. We have chosen not to do business with the City. 4. Other (comment below or provide your response on your business/firm letterhead).

Business/Firm Name:

Supplier No.:

Authorized Signature: Print Name: Title: Date:

Telephone No.:

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 54 of 63

SECTION IV ATTACHMENTS

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 55 of 63

ATTACHMENT NO. I PRICING/COST PROPOSAL

Pricing is required to be firm and fixed pricing. Do not submit travel and living expenses or cost of bonds separately in cost proposal. These expenses must be included as part of the overall spend for the categories listed below. Pricing/Cost Proposal must be sealed seperately in proposal response.

Required Cost Categories System Costs Software (if applicable) Hardware (if applicable) Implementation Services Training Annual Maintenance/subscription and/or Support

$ $ $ $ $ $

Total Proposed Cost $

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 56 of 63

ATTACHMENT NO. 2 AFFIDAVIT

EMPLOYEE ELIGIBILITY VERIFICATION AFFIDAVIT (Required for any contract with the City of Kansas City, Missouri in excess of $5,000.00)

STATE OF ___________________ ) ) ss COUNTY OF _________________ ) On this ________ day of _______________________, 20___, before me appeared ____________________________________________, personally known by me or otherwise proven to be the person whose name is subscribed on this affidavit and who, being duly sworn, stated as follows: I am of sound mind, capable of making this affidavit, and personally swear or affirm that the statements made herein are truthful to the best of my knowledge. I am the ______________________________ (title) of _________________________________ (business entity) and I am duly authorized, directed or empowered to act with full authority on behalf of the business entity in making this affidavit. I hereby swear or affirm that the business entity does not knowingly employ any person in connection with the contracted services who does not have the legal right or authorization under federal law to work in the United States as defined in 8 U.S.C. § 1324a(h)(3). I hereby additionally swear or affirm that the business entity is enrolled in an electronic verification of work program operated by the United States Department of Homeland Security (E-Verify) or an equivalent federal work authorization program operated by the United States Department of Homeland Security to verify information of newly hired employees, under the Immigration Reform and Control Act of 1986, and that the business entity will participate in said program with respect to any person hired by the business entity to perform any work in connection with the contracted services. I have attached hereto documentation sufficient to establish the business entity’s enrollment and participation in the required electronic verification of work program.

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 57 of 63

I am aware and recognize that unless certain contractual requirements are satisfied and affidavits obtained as provided in Section 285.530, RSMo, the business entity may face liability for violations committed by its subcontractors, notwithstanding the fact that the business entity may itself be compliant. I acknowledge that I am signing this affidavit as the free act and deed of the business entity and that I am not doing so under duress.

______________________________________ Affiant’s signature

Subscribed and sworn to before me this ______ day of ___________________, 20____.

______________________________________ Notary Public

My Commission expires:

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 58 of 63

ATTACHMENT NO. 3 REFERENCES

PROPOSER REFERENCES FROM CLIENTS

Proposers are required to provide three (3) client references, including contact information, for similar projects that the Proposer has completed within the past five (5) years. It is preferred that at least one (1) client reference be a government sector client. The Proposer is required to include the three (3) references in the Proposal submitted to the City.

CITY OF KCMO REFERENCE CHECK GENERAL INFORMATION Name of Proposer Subcontractor/Third Party Product or Service Reviewed

REFERENCE CHECK INFORMATION Business/Firm Name Business/Firm Address Contact Name Title Telephone Number Fax Number E-mail Address To submit a reference, please respond to the following questions: 1.

What services did the Supplier provide for you?

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 59 of 63

2.

Were the services performed satisfactorily?

3.

Were the invoices detailed and accurate?

If the invoicing was not accurate, explain how easy or difficult it was to reconcile or have the invoicing updated.

4.

Were there any staffing disputes? If so, explain how easy or difficult it was to have staff replaced.

5.

Was the account service satisfactory?

6.

What was included in the account service?

7.

Were you happy with the cost of your services?

8.

Are you still using this Supplier for these services?

9.

Do you plan to continue this relationship?

10.

Additional Comments:

Name of Client Contact (Print)

Signature

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 60 of 63

ATTACHMENT NO. 4 HRD FORMS AND INSTRUCTIONS

The following HRD forms and instructions are included in this Attachment: FORM

TITLE

NO. OF PAGES

HRD 6 HRD 8 HRD 10 HRD 11 HRD 13 00450.01 01290.14 01290.15

HRD Instructions for RFQ/P Contractor Utilization Plan/Request for Waiver Timetable for MBE/WBE Utilization Request for Modification or Substitution Affidavit of Intended Utilization Letter of Intent to Subcontract Contractor Affidavit for Final Payment Subcontractor Affidavit for Final Payment

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

11 4 1 2 2 1 2 1

ISSUE DATE: 07-19-2013

Page 61 of 63

ATTACHMENT NO. 4 HRD FORMS AND INSTRUCTIONS

The following HRD Forms and Instructions are included in this Attachment: FORM

TITLE

HRD 06 HRD 13 HRD 08 00450.01 HRD 10 HRD 11 01290.14 01290.15

RFQ/P Instructions Affidavit of Intended Utilization Contractor Utilization Plan/Request for Waiver Letter of Intent to Subcontract Timetable for MBE/WBE Utilization Request for Modification or Substitution Contractor Affidavit for Final Payment Subcontractor Affidavit for Final Payment

TURKEY CREEK PLC REPLACEMENT RFP NO. EV1846 (REV. 06-17-13)

ISSUE DATE: 07-09-2013

Page 47 of 47

HRD INSTRUCTIONS FOR REQUESTS FOR QUALIFICATIONS/PROPOSALS PART A. MINORITY/WOMEN BUSINESS ENTERPRISE REQUIREMENTS I. City’s MBE/WBE Program. A. The City has adopted a Minority/Women Business Enterprise (“MBE/WBE”) Program (Sections 38-84 through 38-100.8, Code of Ordinances) (the “Program”) to implement the City’s policy of supporting the fullest possible participation in City contracts and change orders of firms owned and controlled by minorities and women. Each construction project may have an MBE and/or WBE goal for participation. An MBE or WBE goal is a numerical objective the City has set for the contract. Goals are stated as a percentage of contract dollars. For example, if an MBE goal for a contract is 10% and a Proposer submits a proposal of $100,000, the goal for MBE participation would equal $10,000. The specific MBE/WBE goals on this project are set forth elsewhere in the proposal specifications. B. By submitting a proposal, the Proposer agrees, as a material term of the contract, to carry out the City’s MBE/WBE Program by making good faith efforts to include certified MBE/WBEs in the project work to the extent of the goals listed for the project and to the fullest extent consistent with submitting the best proposal to the City. Proposer agrees that the Program is incorporated into this document and agrees to follow the Program. Although it is not a requirement that a Proposer in fact meet or exceed both the MBE and WBE Goals, it is a requirement for approval of the proposal that a Proposer objectively demonstrate to the City that good faith efforts have been made to meet the Goals. C. The following HRD Forms are attached and must be used for MBE/WBE submittals: 1. Affidavit of Intended Utilization (HRD Form 13); and 2. Contractor Utilization Plan/Request for Waiver (HRD Form 8A); and 3. Letter of Intent to Subcontract (HRD Form 00450.01); and 4. Timetable for MBE/WBE Utilization (HRD Form 10); and 5. Request for Modification or Substitution (HRD Form 11); and 6. Contractor Affidavit for Final Payment (Form 01290.14); and 7. Subcontractor Affidavit for Final Payment (Form 01290.15). Warning: The City only gives MBE/WBE credit for a Proposer’s use of City certified MBE/WBEs. A certified MBE/WBE firm is a firm that has been certified by the City’s Human Relations Department as such. Certified MBEs and WBEs are listed in the M/W/DBE Kansas City Mo. Online Directory, which is available on the City’s website at www.kcmo.org. Before a Proposer submits a proposal, Proposer should contact HRD and consult the directory to make sure any firm proposed for use for MBE/WBE participation has been certified. HRD 06 RFQ/P Instructions 013012

1 of 12 Contract Central

II. Required Submissions with Proposal. A. Proposer must submit the following document with its proposal: 1. Affidavit of Intended Utilization (HRD Form 13). This form states a Proposer’s intent to use certified MBE/WBEs in the performance of the contract. III. Required Submissions Prior to Contract Award. A. Proposer must submit the following documents prior to contract award. 1. Contractor Utilization Plan/Request for Waiver (HRD Form 8). This form states a Proposer’s plan to use specific certified MBE/WBEs in the performance of the contract and includes the following: a. The work to be performed by each MBE/WBE and the amounts each is to be paid for the work; and b. The name, address, race or ethnic origin, gender and employer identification number or social security number of each MBE/WBE that will perform the work. c. An automatic request for waiver in the event Proposer has not met or exceeded the MBE and/or WBE goals for the contract but believes that it has made good faith efforts to meet or exceed the goals and desires a waiver of the goals. If a waiver is requested, HRD will examine the Proposer’s documentation of good faith efforts and make a recommendation to grant or deny the waiver. HRD will recommend a waiver be granted only if the Proposer has made good faith efforts to obtain MBE/WBE participation. 2. Letter(s) of Intent to Subcontract (HRD Form 00450.01). A letter must be provided from each MBE/WBE listed on the Contractor Utilization Plan. These letters verify that the MBE/WBE has agreed to execute a formal agreement for the work and indicate the scope of work to be performed and the price agreed upon for the work. IV. Additional Required Submissions when Requested by City. A. Proposer must submit the following documents when requested by City: 1. Timetable for MBE/WBE Utilization (HRD Form 10). 2. Documentation of good faith efforts. V. Required Monthly Submissions during term of Contract. A. Proposers must submit the following document on a monthly basis if awarded the contract: 1. M/WBE Monthly Utilization Report (HRD Form 00485.01). This report must be submitted to the Director by the 15th of each month. Failure to submit timely reports may result in delays in processing of current and future contract approvals and payment applications. HRD 06 RFQ/P Instructions 013012

2 of 12 Contract Central

VI. Required Submittals for Final Contract Payment. A. Proposer must submit the following documents with its request for final payment under the contract: 1. Contractor Affidavit for Final Payment (Form 01290.14) 2. Subcontractor Affidavit(s) for Final Payment (Form 01290.15) VII.

Additional Submittals.

A. Proposer may be required to make additional submittals during the term of the Contract, including Request for Modification or Substitution (HRD Form 11). Refer to Section X, Modification of the Contractor Utilization Plan or Substitution of an MBE/WBE, for additional instructions on when this form must be submitted. VIII. MBE/WBE Participation Credit. A. The following shall be credited towards achieving the goals: 1. The total contract dollar amount that a prime contractor has paid or is obligated to pay to a subcontractor that is a qualified MBE or WBE, except as otherwise expressly provided for herein. 2. Twenty-five percent (25%) of the total dollar amount paid or to be paid by a prime contractor to obtain supplies or goods from a supplier who is a qualified MBE or WBE. 3. Ten percent (10%) of the total dollar amount paid or to be paid by a prime contractor to obtain supplies or goods from a supply broker who is a qualified MBE or WBE. 4. One hundred percent (100%) of the total dollar amount paid or to be paid by a prime contractor to a manufacturer of construction supplies who is a qualified MBE or WBE. 5. Subcontractor participation with a lower tier MBE/WBE subcontractor using one of the above methods of participation. B. NO CREDIT, however, will be given for the following: 1. Participation in a contract by a MBE or WBE that does not perform a commercially useful function as defined by the Program; and 2. Any portion of the value of the contract that an MBE or WBE subcontractor subcontracts back to the prime contractor or any other contractor who is not a qualified MBE/WBE; and 3. An MBE or WBE prime contractor’s own participation in its contract with City; and 4. Materials and supplies used on the contract unless the MBE/WBE is responsible for negotiating the price, determining quality and quantity, ordering the materials and installing (where applicable) and paying for material itself; and 5. Work performed by an MBE or WBE in a scope of work other than that in which the MBE or WBE is currently certified. HRD 06 RFQ/P Instructions 013012

3 of 12 Contract Central

IX. Methods for Securing Participation of MBE/WBEs and Good Faith Efforts. A. A Proposer is required to make good faith efforts to achieve the MBE/WBE goals. Good faith efforts are efforts that, given all relevant circumstances, a Proposer actively and aggressively seeking to meet the goals can reasonably be expected to make. Good faith efforts must be made before the Proposer submits a Contractor Utilization Plan/Request for Waiver (HRD Form 8) Warning: Efforts to obtain MBE and/or WBE participation made after a Contractor Utilization Plan is submitted cannot be used to show the Proposer made good faith efforts. B. In evaluating good faith efforts, the Director of HRD will consider whether the Proposer has performed the following, along with any other relevant factors: 1. Advertised opportunities to participate in the contract in general circulation media, trade and professional association publications, small and minority business media, and publications of minority and women’s business organizations in sufficient time to allow MBE and WBE firms to participate effectively. 2. Provided notice to a reasonable number of minority and women’s business organizations of specific opportunities to participate in the contract in sufficient time to allow MBE and WBE firms to participate effectively. 3. Sent written notices, by certified mail or facsimile, to qualified MBEs and WBEs soliciting their participation in the contract in sufficient time to allow them to participate effectively. 4. Attempted to identify portions of the work for qualified MBE and/or WBE participation in order to increase the likelihood of meeting the goals, including breaking down contracts into economically feasible units. A Proposer should send letters by certified mail or facsimile to those MBE/WBE contractors identified by HRD listed in those categories which are in those subcontractors’ scope of work. The portion of work for which a proposal from an MBE/WBE is being solicited shall be as specific as possible. Letters which are general are not acceptable. 5. Requested assistance in achieving the goals from the Director and acted on the Director’s recommendations. 6. Conferred with qualified MBEs and WBEs and explained the scope and requirements of the work for which their bids or proposals were solicited. 7. Attempted to negotiate in good faith with qualified MBEs and WBEs to perform specific subcontracts; not rejecting them as unqualified without sound reasons based on a thorough investigation of their capabilities. Documentation of good faith negotiations with MBE/WBEs from whom proposals were received in an effort to reach a mutually acceptable price should include: a. Names, addresses and telephone numbers of MBE/WBEs that were contacted and date of contact; b. The information provided to MBE/WBEs regarding the plans and HRD 06 RFQ/P Instructions 013012

4 of 12 Contract Central

specifications for portions of the work to be performed by them; c. The reasons no agreement was reached with any MBE/WBE, including the basis for any bid rejection (i.e., availability, price, qualifications or other); d. Descriptions of attempts to provide technical assistance to MBE/WBEs to obtain necessary insurance and/or to obtain necessary supplies at the best prices available. C. A Proposer will be required to give the City documentation to prove that it made good faith efforts. The Proposer will be contacted by the City with further instructions about when this documentation must be submitted. X. Modification of the Contractor Utilization Plan or Substitution of an MBE/WBE. A. A Proposer may need to substitute an MBE and/or WBE or request that the amount of MBE/WBE participation listed in its Contractor Utilization Plan be modified. Proposer must file a Request for Modification or Substitution (HRD Form 11) prior to actual substitution and within a reasonable time after learning that a modification or substitution is necessary. The Director may approve substitutions or modifications and upon approval, the modifications and substitutions will become an amendment to the Contractor Utilization Plan. Modifications or substitutions may be approved when: 1. The Director finds that the Proposer made and provided evidence of good faith efforts to substitute the MBE/WBE listed on the Contractor Utilization Plan with other certified MBE/WBEs for the scope of work or any other scope of work in the contract; AND 2. The Director also finds one of the following: a. The listed MBE/WBE is non-responsive or cannot perform; or b. The listed MBE/WBE has increased its previously quoted price to the bidder, proposer or contractor without a corresponding change in the scope of the work; or c. The listed MBE/WBE has committed a material default or breach of its contract with the contractor; or d. Requirements of the scope of work of the contract have changed and render subcontracting not feasible or not feasible at the levels required by the goals established for the contract; or e. The listed MBE/WBE is unacceptable to the contracting department; or f. The listed MBE/WBE thereafter had its certification revoked; or g. The Proposer or Contractor has not attempted intentionally to evade the requirements of the Program and it is in the best interests of the City to allow a modification or substitution. B. A modification shall not be made unless the modification or substitution has first been requested and approved by the Director. HRD 06 RFQ/P Instructions 013012

5 of 12 Contract Central

XI. Appeals. (Applicable only if the RFQ/P is for a construction project) A. In conformance with the Act, appeals may be made to the City Fairness in Construction Board on the following: 1. The grant or denial of a Request for Waiver; 2. Substitution for an MBE/WBE listed on a Contractor Utilization Plan; 3. Modification of the percentage of MBE/WBE participation on a Contractor Utilization Plan; 4. Liquidated Damages; 5. The amount of MBE/WBE credit the Contractor may receive for MBE/WBE participation identified in the contractor utilization plan. B. Any appeal must be filed in writing with the Director within ten (10) working days of notice of the determination. Mailing, faxing, personal delivery or posting at HRD of determinations shall constitute notice. The appeal shall state with specificity why the Proposer or Contractor believes the determination is incorrect C. Failure to file a timely appeal shall constitute a waiver of a Proposer’s or Contractor’s right to appeal such determination and such person shall be estopped to deny the validity of any determination which could have been timely appealed. XII.

Access to Documents and Records.

A. By submitting a proposal, each Proposer agrees to permit the City, its duly authorized agents or employees, access at all reasonable times to all books and business records of Proposer as may be necessary to ascertain compliance with the requirements of this document and the Act, within ten (10) days of the date of the written request. B. All Proposers agree to cooperate with the contracting department and HRD in studies and surveys regarding the MBE/WBE program. XIII. Miscellaneous. A. A Proposer or Contractor shall bear the burden of proof with regard to all issues on appeal. B. In the event of any conflict between this document and the Program, the provisions of the Program shall control. The terms used in this document are defined in the Program. C. Oral representations are not binding on the City. D. The City Council may waive the requirements of this document and the Program and award the contract to the best proposer if the City Council determines a waiver is in the best interests of the City. XIV. Liquidated Damages – MBE/WBE Program. A. If Contractor fails to achieve the MBE/WBE goals stated in its Contractor Utilization Plan, as amended, the City will sustain damages, the exact extent of which would be difficult or impossible to ascertain. Therefore, in order to liquidate those damages, the HRD 06 RFQ/P Instructions 013012

6 of 12 Contract Central

monetary difference between the amount of the MBE/WBE goals set forth in the Contractor Utilization Plan, as amended, and the amount actually paid to qualified MBEs and WBEs for performing a commercially useful function will be deducted from the Contractor’s payments as liquidated damages. In determining the amount actually paid to qualified MBEs and WBEs, no credit will be given for the portion of participation that was not approved by the Director, unless the Director determines that the Contractor acted in good faith. No deduction for liquidated damages will be made when, for reasons beyond the control of the Contractor, the MBE/WBE participation stated in the Contractor Utilization Plan, as amended and approved by the Director is not met.

[Specifier: The remainder of this document is applicable ONLY IF the RFQ/P is for a construction project that the City estimates will require more than 800 construction labor hours and cost in excess of $324,000.00 to construct. If this is not applicable to your RFQ/P, delete the remainder of this document. Be sure to delete this note before printing] PART B. CONSTRUCTION EMPLOYMENT PROGRAM REQUIREMENTS (THIS PART IS APPLICABLE TO CITY CONSTRUCTION CONTRACTS ESTIMATED BY THE CITY PRIOR TO SOLICITATION AS REQUIRING MORE THAN 800 CONSTRUCTION LABOR HOURS AND COSTING IN EXCESS OF $324,000.00.) I. City’s Construction Employment Program. A. The City has adopted a Construction Employment Program (Sections 38-83.1 through 3883.13, Code of Ordinances) (the “Program”) to implement the City’s policy of supporting the fullest possible utilization of minority and women workers in the construction industry. A person or firm who is awarded a contract to construct, reconstruct, improve, enlarge or alter any fixed work that is estimated by the City prior to solicitation as requiring more than 800 construction labor hours, has an estimated costs that exceeds $324,000.00, and involves the expenditure of public funds, is subject to company-wide construction employment goals. The minimum goals are currently set at 10% for minorities and 2% for women, but public recognition may be provided if the Proposer achieves at least twice the minimum participation. The successful Proposer may meet these company-wide goals by counting the Proposer’s utilization of minorities and women throughout the Kansas City metropolitan statistical area. B. By submitting a proposal, the Proposer agrees, as a material term of the contract, to carry out the City’s Construction Employment Program by making good faith efforts to utilize minority and women workers on the Proposer’s job sites to the fullest extent consistent with submitting the best proposal to the City. Proposer agrees that the Program is incorporated into this document and agrees to follow the Program. Although it is not a requirement that a Proposer in fact meet or exceed the construction employment goals to receive approval from HRD, a Proposer not doing so is required to objectively HRD 06 RFQ/P Instructions 013012

7 of 12 Contract Central

demonstrate to HRD that good faith efforts have been made. C. The following HRD Forms are to be used for Construction Employment Program submittals: 1. Project Workforce Monthly Report (HRD Form 00485.02) 2. Company-Wide Workforce Monthly Report (HRD Form 00485.03) II. Required Monthly Submissions during Term of Contract. A. Proposer must submit the following documents on a monthly basis if awarded the contract: 1. Project Workforce Monthly Report (HRD Form 00485.02). This report is contract specific. Two copies of this report must be submitted to the Director by the 15th of each month. The first copy will be utilized to report the Proposer’s own workforce compliance data with regard to the City’s construction contract. The second copy will be utilized to report consolidated workforce compliance data for every subcontractor retained on the City’s construction contract. Failure to submit timely reports may result in delays in processing of current and future contract approvals and payment applications. 2. Company-Wide Workforce Monthly Report (HRD Form 00485.03). This report is not contract specific; it is used to report on the utilization of females and minorities, by trade, company-wide. Two copies of this report must be submitted to the Director by the 15th of each month. The first copy will be utilized to report the Proposer’s own workforce compliance data with regard to every contract (both privately and publicly funded) Proposer has in progress throughout the Kansas City metropolitan statistical area. The second copy will be utilized to report consolidated workforce compliance data for every subcontractor retained by Proposer on every contract Proposer has in progress throughout the Kansas City metropolitan statistical area. Failure to submit timely reports may result in delays in processing of current and future contract approvals and payment applications. III. Submittal Required for Final Contract Payment. A. The last Project Workforce Monthly Report(s) and Company-Wide Workforce Monthly Report(s) shall serve as the final reports and must be submitted before final payment will be made and/or retainage released. Proposer shall note the submittal of the final reports by notation in the box entitled “Final Cumulative Report” IV. Methods for Securing Workforce Participation and Good Faith Efforts. A. A Proposer is required to make good faith efforts to achieve the construction employment goals. If a Proposer will be unable to secure enough minority and female participation to meet or exceed the construction employment goals, a Proposer must, within a reasonable time after so learning, request a waiver or modification of the goals by the Director of HRD. The Director will examine the Proposer’s request and the Proposer’s documentation of good faith efforts and grant or deny a waiver or modification. The Director will grant a waiver or modification only if the Proposer has made good faith HRD 06 RFQ/P Instructions 013012

8 of 12 Contract Central

efforts to secure minority and female participation. B. In evaluating good faith efforts, the Director will consider whether the Proposer has performed the following: 1. For those Proposers that are not signatories to a collective bargaining agreement with organized labor: a. Requested in writing the assistance of the Director with respect to efforts to promote the utilization of minorities and women in the workforce and acted upon the Director’s recommendations; and b. Advertised in minority or women trade association newsletters and/or minority or women owned media at least 15 calendar days prior to the utilization of any construction services on the city construction contract and used terminology that sufficiently describes the work available, the pay scale, the application process, and anything else that one might reasonably be expected to be informed of relevant to the position being advertised; and c. Maintained copies of each advertisement and a log identifying the publication and date of publication; and d. Conducted real and substantial recruitment efforts, both oral and written, targeting resident, minority and women community-based organization, schools with a significant minority student population, and training organizations serving the recruitment area; and e. Established and maintained a current list of resident, minority and women recruitment sources, providing written notification to the recruitment sources of available employment opportunities, and maintained records of the notices submitted to the organizations and any responses thereto; and f. Maintained a current file for the time period of the city construction contract with the name, address, and telephone number of each resident, minority and woman job applicant, the source of the referral, whether or not the person was hired, and in the event that the applicant was not hired, the reason therefore; and g. Promoted the retention of minorities and women in its workforce with the goals of achieving sufficient annual hours for minorities and women to qualify for applicable benefits; and h. Required by written contract that all subcontractors comply with the above efforts. 2. For those Proposers that are signatories to collective bargaining agreements with organized labor: a. Supported the efforts of the Joint Apprenticeship Training Committee (JATC), a joint effort of Labor Unions and contractors, or some other apprenticeship program, whose purpose is to recruit, train and employ new workers for a full time career in the construction industry; and HRD 06 RFQ/P Instructions 013012

9 of 12 Contract Central

b. Requested in writing from each labor union representing crafts to be employed that: i. the labor union make efforts to promote the utilization of residents of the City, minorities and women in the workforce; and ii. the labor union identify any residents of the City, minorities and women in its membership eligible for employment; and iii. the JATC take substantial and real steps to increase the participation of minorities in the union apprenticeship programs in the aggregate to 30% by 2011 and encourage other labor unions to do the same; and iv. the JATC take substantial and real steps to increase the participation of women in the union apprenticeship programs in the aggregate to 5% by 2011 and encourage other labor unions to do the same; and v. the JATC partner with workforce preparedness programs, community based organizations, employment referral programs and schoolsponsored programs to accomplish these goals. c. Collaborated with labor unions in promoting mentoring programs intended to assist minorities and women in increasing retention with the goals of achieving sufficient annual hours to qualify for applicable benefits; and d. Maintained a current file with the name, address, and telephone number of each resident, minority and women worker identified by the labor union, whether or not the person was hired, and in the event the person was not hired, the reason therefore. e. To the extent the good faith efforts applicable to Proposers that are signatories to collective bargaining agreements with organized labor conflict with the procedures implemented by the Proposer in order to comply with the relevant bargaining agreement, the Proposer shall substitute other procedures as may be approved by the Director in writing. C. A Proposer will be required to give the City documentation to prove that it made good faith efforts. The Proposer will be contacted by the City with further instructions about when this documentation must be submitted. V. Appeals. A. In conformance with the Program, appeals may be made to the Construction Workforce Board on the following: 1. Determinations by the Director that a contractor did not meet the construction employment goals and did not make a good faith effort to meet the goals; 2. Recommendations by the Director to assess liquidated damages; 3. Recommendation by the Director that a contractor be declared ineligible to receive any city construction contract for a period of time up to one year. B. Any appeal must be filed in writing with the Director within ten (10) working days of HRD 06 RFQ/P Instructions 013012

10 of 12 Contract Central

notice of the recommendation or determination. The appeal shall state with specificity why the Proposer believes the recommendation or determination is incorrect. C. Failure to file a timely appeal shall constitute a waiver of a Proposer’s right to appeal such determination or recommendation and such person shall be estopped to deny the validity of any order, determination, recommendation or action of HRD which could have been timely appealed. VI. Access to Documents and Records. A. By submitting a proposal, each Proposer agrees to permit the City, its duly authorized agents or employees, access at all reasonable times to all books and business records of Proposer as may be necessary to ascertain compliance with the requirements of this document and the Program, within ten (10) days of the date of the written request. Each Proposer further agrees to require, if awarded the contract, that every subcontractor permit the City the same access to documents and records. B. All Proposers agree to cooperate with the contracting department and HRD in studies and surveys regarding the construction employment program. VII.

Miscellaneous.

A. A Proposer shall bear the burden of proof with regard to all issues on appeal. B. The successful Proposer may be required to meet with the Director of HRD or the Director’s designee for the purpose of discussing the construction employment program, the Proposer’s efforts to realize the goals, and any other problems and/or issues affecting the realization of the goals or the program in general. C. In the event of any conflict between this document and the Program, the provisions of the Program shall control. The terms used in this document are defined in the Program. D. Oral representations are not binding on the City. VIII. Liquidated Damages; Suspension – Workforce Program. A. If a Proposer fails to achieve the construction employment goals without having previously obtained a waiver or modification of those goals, the City will sustain damages, the exact extent of which would be difficult or impossible to ascertain. These damages are magnified if the failure to abide by the requirements of the Workforce Program is recurring. Therefore, in order to liquidate those damages, City shall be entitled to deduct and withhold the following amounts: If Proposer failed to meet or exceed the minimum employment goals or otherwise establish that Proposer is entitled to a waiver under circumstances in which Proposer has failed to meet or exceed the goals on one prior occasion within the twenty-four month period immediately preceding the completion of the work under the Contract, the sum of three thousand dollars ($3,000.00). If Proposer failed to meet or exceed the minimum employment goals or otherwise establish that Proposer is entitled to a waiver under circumstances in which Proposer has failed to meet or exceed the goals on two or more prior occasions HRD 06 RFQ/P Instructions 013012

11 of 12 Contract Central

within the twenty-four month period immediately preceding the completion of the work under the Contract, the sum of seven thousand dollars ($7,000.00).

B. In addition, Proposer shall be required to attend mandatory compliance training or be declared ineligible to contract with the City for a term provided herein, and as authorized by City’s Code of Ordinances: If Proposer failed to meet or exceed the minimum employment goals or otherwise establish that Proposer is entitled to a waiver under circumstances in which Proposer has not previously failed to meet or exceed the goals within the twentyfour month period immediately preceding the completion of the work under the Contract, Proposer shall be required to attend a mandatory training class on Workforce Program compliance. If Proposer failed to meet or exceed the minimum employment goals or otherwise establish that Proposer is entitled to a waiver under circumstances in which Proposer has failed to meet or exceed the goals on one prior occasion within the twenty-four month period immediately preceding the completion of the work under the Contract, Proposer shall be suspended from participating, either as a contractor or subcontractor, on any future contract with the City for a period of thirty (30) days. Proposer waives any right to invoke any proceeding or procedure under Sections 2-1649 or 2-1801 of City’s Code of Ordinances with regards to any suspension arising hereunder. If Proposer failed to meet or exceed the minimum employment goals or otherwise establish that Proposer is entitled to a waiver under circumstances in which Proposer has failed to meet or exceed the goals on two or more prior occasions within the twenty-four month period immediately preceding the completion of the work under the Contract, Proposer shall be suspended from participating, either as a contractor or subcontractor, on any future contract with the City for a period of six (6) months. Proposer waives any right to invoke any proceeding or procedure under Sections 2-1649 or 2-1801 of City’s Code of Ordinances with regards to any suspension arising hereunder.

HRD 06 RFQ/P Instructions 013012

12 of 12 Contract Central

AFFIDAVIT OF INTENDED UTILIZATION (This Form must be submitted with your Bid/Proposal) ____________________________________________________________ (Department Project) ____________________________________________________________ (Bidder/Proposer) STATE OF ____________________) ) ss COUNTY OF __________________) I, _______________________________, of lawful age and upon my oath state as follows: 1.

This Affidavit is made for the purpose of complying with the provisions of the MBE/WBE submittal requirements in the bid/proposal specifications on the above project and is given on behalf of the Bidder/Proposer listed below.

2.

Bidder/Proposer assures that it presently intends to utilize the following MBE/WBE participation in the above project if awarded the Contract: PROJECT GOALS: BIDDER/PROPOSER PARTICIPATION:

3.

________% MBE ________% MBE

______% WBE ______% WBE

To the best of Bidder’s/Proposer’s knowledge, the following are the names of certified MBEs or WBEs with whom Bidder/Proposer, or Bidder’s/Proposer’s subcontractors, presently intend to contract if awarded the Contract on the above project: (All firms must currently be certified by Kansas City, Missouri Dept. Of Human Relations) a.

Name of M/WBE Firm ___________________________________________ Address ________________________________________________________ Telephone No. __________________________________________________ I.R.S. No. ______________________________________________________ Area/Scope of work _______________________________________________ Subcontract amount ______________________________________________

b.

Name of M/WBE Firm _____________________________________________ Address _________________________________________________________ Telephone No. ____________________________________________________ I.R.S. No. ________________________________________________________ Area/Scope of work _________________________________________________ Subcontract amount _________________________________________________

c.

Name of M/WBE Firm _______________________________________________ Address ___________________________________________________________ Telephone No. _____________________________________________________ I.R.S. No. _________________________________________________________ Area/Scope of work __________________________________________________ Subcontract amount __________________________________________________

(List additional MBE/WBEs, if any, on additional pages and attach to this form) HRD 13 Affidavit of Intended Utilization 021108

Page 1 of 2

Contract Central

4.

Bidder/Proposer will identify before contract award, those MBE/WBE subcontractors with dollar amounts and scopes of work which apply to or exceed the MBE/WBE goals for the Project on the Contractor Utilization Plan/Request for Waiver (HRD 08).

5.

Bidder/Proposer agrees that failure to meet or exceed the MBE/WBE Goals for the above project will automatically render this bid/proposal non-responsive if Bidder/Proposer fails to establish good faith efforts towards meeting the goals as set forth in the HRD Forms and Instructions.

6.

If applicable, Bidder/Proposer assures that it will meet or exceed the minimum employment goals of 10% minority and 2% women during the term of its contract with City, or request a waiver of the goals. NOTE: This paragraph is applicable ONLY if you are submitting a bid/proposal on a construction contract that was estimated by the City, prior to solicitation, as requiring more than 800 construction labor hours and costing in excess of $324,000.00.

7.

I am authorized to make this Affidavit on behalf of the Bidder/Proposer named below as:

_________________________ of ______________________________________ (Title) (Name of Bidder/Proposer)

Dated: _______________________________ By: ___________________________________ (Affiant)

Subscribed and sworn to before me this _____ day of ____________________, 20____.

My Commission Expires: ________________

HRD 13 Affidavit of Intended Utilization 021108

______________________________ Notary Public

Page 2 of 2

Contract Central

CONTRACTOR UTILIZATION PLAN/REQUEST FOR WAIVER

Project Number ____________________________________________ Project Title _______________________________________________

______________________________________________________ _____________________ (Department Project)

Department

____________________________________________________________________________ __ (Bidder/Proposer) STATE OF ____________________ ) ) ss COUNTY OF __________________ ) I, _______________________________, of lawful age and upon my oath state as follows: 1. This Affidavit is made for the purpose of complying with the provisions of the MBE/WBE submittal requirements on the above project and the MBE/WBE Program and is given on behalf of the Bidder/Proposer listed below. It sets out the Bidder/Proposer’s plan to utilize MBE and/or WBE contractors on the project. 2.

Bidder/Proposer assures that it will utilize a minimum of the following percentages of MBE/WBE participation in the above project: PROJECT GOALS:

________% MBE

BIDDER/PROPOSER PARTICIPATION:________% MBE

_______% WBE _______% WBE

3. The following are M/WBE subcontractors with dollar amounts and scopes of work which apply to or exceed the Goals for the project: (All firms must currently be certified by Kansas City, Missouri) a.

Name of M/WBE Firm ______________________________________________ Address __________________________________________________________ Telephone No. _____________________________________________________ I.R.S. No. ________________________________________________________ Area/Scope of work ________________________________________________

00450 HRD 08 Utilization Plan & Req. for Waiver 020408

1 of 5

Contract Central

Subcontract amount ________________________________________________ b.

Name of M/WBE Firm ______________________________________________ Address __________________________________________________________ Telephone No. _____________________________________________________ I.R.S. No. ________________________________________________________ Area/Scope of work _________________________________________________ Subcontract amount ________________________________________________ c.

Name of M/WBE Firm ______________________________________________ Address __________________________________________________________ Telephone No. _____________________________________________________ I.R.S. No. ________________________________________________________ Area/Scope of work ________________________________________________ Subcontract amount ________________________________________________ d.

Name of M/WBE Firm ______________________________________________ Address __________________________________________________________ Telephone No. _____________________________________________________ I.R.S. No. ________________________________________________________ Area/Scope of work _________________________________________________ Subcontract amount ________________________________________________ e.

Name of M/WBE Firm ______________________________________________ Address __________________________________________________________ Telephone No. _____________________________________________________ I.R.S. No. ________________________________________________________ Area/Scope of work ________________________________________________

00450 HRD 08 Utilization Plan & Req. for Waiver 020408

2 of 5

Contract Central

Subcontract amount ________________________________________________ f.

Name of M/WBE Firm ______________________________________________ Address __________________________________________________________ Telephone No. _____________________________________________________ I.R.S. No. ________________________________________________________ Area/Scope of work _________________________________________________ Subcontract amount ________________________________________________ (List additional M/WBEs, if any, on additional page and attach to this form) 4. The following is a compilation of the above M/WBE dollar amounts and scopes of work: MBE/WBE COMPILATION SHEET MBE FIRMS: Weighted % of Total Name of MBE Firm Value* Contract _____________________

_____________________

__________ _______

_______

_____________________

_____________________

__________ _______

_______

_____________________

_____________________

__________ _______

_______

_____________________

_____________________

__________ _______

_______

_____________________

_____________________

__________ _______

_______

_____________________

_____________________

__________ _______

_______

_____________________

_____________________

__________ _______

_______

_____________________

_____________________

__________ _______

_______

Supplier/Contractor

TOTAL MBE $ / TOTAL MBE %:

Base Bid

$____________

______%

____________________________________________________________________________ __ WBE FIRMS: Weighted % of Total Name of WBE Firm Value* Contract

Supplier/Contractor

00450 HRD 08 Utilization Plan & Req. for Waiver 020408

3 of 5

Base Bid

Contract Central

_____________________

_____________________

__________ _______

_______

_____________________

_____________________

__________ _______

_______

_____________________

_____________________

__________ _______

_______

_____________________

_____________________

__________ _______

_______

_____________________

_____________________

__________ _______

_______

_____________________

_____________________

__________ _______

_______

_____________________

_____________________

__________ _______

_______

_____________________

_____________________

__________ _______

_______

TOTAL WBE $ / TOTAL WBE %:

$____________

______%

____________________________________________________________________________ _ *“Weighted Value” means the dollar amount of the subcontract that will be credited toward the Goals. See HRD Forms and Instructions for allowable credit and special instructions for suppliers. 5. If Bidder/Proposer has not achieved both the M/WBE goal(s) set for this Project, Bidder/Proposer hereby requests a waiver of the MBE and/or WBE goal(s) that Bidder/Proposer has failed to achieve

6. Bidder/Proposer will present documentation of its good faith efforts, a narrative summary detailing its efforts and the reasons its efforts were unsuccessful when requested by the City.

7. I hereby certify that I am authorized to make this Affidavit on behalf of the Bidder/Proposer named below as:

Bidder/Proposer primary contact: Address:

_________ _________ _________ _________ _________

Phone Number: Facsimile number: E-mail Address:

By: __________________________________ Title: __________________________________ Date: __________________________________ (Attach corporate seal if applicable) 00450 HRD 08 Utilization Plan & Req. for Waiver 020408

4 of 5

Contract Central

Subscribed and sworn to before me this ______ day of ___________________, 20__.

My Commission Expires: __________________ _________________________________ Notary Public

00450 HRD 08 Utilization Plan & Req. for Waiver 020408

5 of 5

Contract Central

LETTER OF INTENT TO SUBCONTRACT Project Number Project Title

______________________________________ (“Prime Contractor”) agrees to enter into a contractual agreement with ________________________________________ (“M/W/DBE Subcontractor”), who will provide the following goods/services in connection with the above-referenced contract: (Insert a brief narrative describing the goods/services to be provided. Broad categorizations (e.g., “electrical,” “plumbing,” etc.) or the listing of the NAICS Codes in which M/W/DBE Subcontractor is certified are insufficient and may result in this Letter of Intent to Subcontract not being accepted.) _____________________________________________________________________________ _____________________________________________________________________________ _____________________________________________________________________________ _____________________________________________________________________________ _____________________________________________________________________________, for an estimated amount of $____________________ or ______________% of the total estimated contract value.

M/W/DBE Subcontractor is, to the best of Prime Contractor’s knowledge, currently certified with the City of Kansas City’s Human Relations Department to perform in the capacities indicated herein. Prime Contractor agrees to utilize M/W/DBE Subcontractor in the capacities indicated herein, and M/W/DBE Subcontractor agrees to work on the above-referenced contract in the capacities indicated herein, contingent upon award of the contract to Prime Contractor.

_______________________________________ Signature: Prime Contractor

_________________________________ Signature: M/W/DBE Subcontractor

________________________________________ Print Name

_________________________________ Print Name

________________________________________ Title Date

_________________________________ Title Date

00450.01 HRD Letter of Intent to Subcontract 060810

Page 1 of 1

Contract Central

TIMETABLE FOR MBE/WBE UTILIZATION (This form should be submitted to the City after contract award.)

I, __________________________________, acting in my capacity as _____________________ (Name) (Position with Firm) of __________________________________, with the submittal of this Timetable, certify that (Name of Firm) the following timetable for MBE/WBE utilization in the fulfillment of this contract is correct and true to the best of my knowledge. ALLOTTED TIME FOR THE COMPLETION OF THIS CONTRACT (Check one only) 15 days ___ 75 days ___ 30 days ___ 90 days ___ 45 days ___ 105 days ___ 60 days ___ 120 days ___ Other _____________________ (Specify)

135 days 150 days 165 days 180 days

___ ___ ___ ___

Throughout ____________________________ Beginning 1/3 ___________________________ Middle 1/3 _____________________________ Final 1/3 _______________________________ Beginning 1/3 _________% Middle 1/3 _________% Final 1/3 __________% PLEASE NOTE: Any changes in this timetable require approval of the Human Relations Department in advance of the change. If you have any questions regarding the completion of this form, please contact the Department of Human Relations at: (816) 513-1818.

__________________________________________ (Signature) __________________________________________ (Position with Firm) __________________________________________ (Date)

00460 HRD 10 Timetable for MBE/WBE Utilization 082902

Contract Central

REQUEST FOR MODIFICATION OR SUBSTITUTION (This Form must be submitted to HRD to request substitutions for an MBE/WBE listed in the Contractor Utilization Plan or for modification of the amount of MBE/WBE participation listed in the Contractor Utilization Plan. This Form shall be an amendment to the Contractor Utilization Plan)

BIDDER/PROPOSER/CONTRACTOR: _________________________________________________ ADDRESS: ________________________________________________________________________ PROJECT NUMBER OR TITLE: ____________________________________________________ Project Goals: Goals listed in Contractor Utilization Plan:

________% MBE ________% MBE

_______% WBE _______% WBE

1. I am the duly authorized representative of the above Bidder/Contractor/Proposer and am authorized to request this substitution or modification on behalf of the Bidder/Contractor/Proposer. 2. I hereby request that the Director of HRD recommend or approve: (check appropriate space(s)) a. ____ A substitution of the certified MBE/WBE firm _____________________________, (Name of new firm) to perform ______________________________________________________, (Scope of work to be performed by new firm) for the MBE/WBE firm ________________________________ which is currently (Name of old firm) listed on the Bidder’s/Contractor’s/Proposer’s Contractor Utilization Plan to perform the following scope of work: _____________________________. (Scope of work of old firm) b. ____A modification of the amount of MBE/WBE participation currently listed on the Bidder’s/Contractor’s/Proposer’s Contractor Utilization Plan from ______ % MBE ______% WBE (Fill in % of MBE/WBE Participation currently listed on Contractor Utilization Plan) TO ______% MBE ______% WBE (Fill in New % of MBE/WBE Participation requested for Contractor Utilization Plan) 3. Bidder/Contractor/Proposer states that a substitution or modification is necessary because: (check applicable reason(s) ) ___The MBE/WBE listed on the Contractor Utilization Plan is non-responsive or cannot perform. ___The MBE/WBE listed on the Contractor Utilization Plan has increased its previously quoted price without a corresponding change in the scope of work.

00470 HRD 11 Request for Mod. or Sub. 020408

Page 1 of 2

Contract Central

___The MBE/WBE listed on the Contractor Utilization Plan has committed a material default or breach of its contract. ___Requirements of the scope of work of the contract have changed and make subcontracting not feasible or not feasible at the levels required by the goals established for the contract. ___The MBE/WBE listed on the Contractor Utilization Plan is unacceptable to the City contracting department. ___Bidder/Contractor/Proposer has not attempted intentionally to evade the requirements of the Act and it is in the best interests of the City to allow a modification or substitution. 4. The following is a narrative summary of the Bidder’s/Contractor’s/Proposer’s good faith efforts exhausted in attempts to substitute the MBE/WBE firm named above which is currently listed on the Contractor Utilization Plan with other qualified, certified MBE/WBE firms for the listed scope of work or any other scope of work in the project: ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ 5. Bidder/Proposer/Contractor will present documentation when requested by the City to evidence its good faith efforts. Dated:_____________________________

_______________________________________ (Bidder/Proposer/Contractor)

_______________________________________ By: (Authorized Representative) ----------------------------------------------------------------------------------------------------------------------------(Do Not Write in This Space: HRD Use Only) _ Approved

Disapproved

____________________ Director of Human Relations

00470 HRD 11 Request for Mod. or Sub. 020408

Page 2 of 2

Contract Central

CONTRACTOR AFFIDAVIT FOR FINAL PAYMENT Project Number Project Title

STATE OF

) )SS )

COUNTY OF The Undersigned,

of lawful (Name)

age, being first duly sworn, states under oath as follows: 1.

I am the

of

who is the general

(Title)

(CONTRACTOR)

CONTRACTOR for the OWNER on Project No.

and Project Title

.

2.

All payrolls, material bills, use of equipment and other indebtedness connected with the Work for this Project have been paid and all Claims of whatever nature have been satisfied, as required by the Contract.

3

()

Prevailing wage does not apply; or

() All provisions and requirements set forth in Chapter 290, Section 290.210 through and including 290.340, Missouri Revised Statutes, pertaining to the payment of wages to workmen employed on public works projects have been fully satisfied and there has been no exception to the full and complete compliance with these provisions and requirements and the Annual Wage Order contained in the Contract in carrying out the Contract and Work. CONTRACTOR has fully complied with the requirements of the prevailing wage law as required in the Contract and has attached affidavits from all Subcontractors on this Project, regardless of tier, affirming compliance with the prevailing wage law as stipulated in the Contract. 4.

I hereby certify that (a) at project completion and pursuant to contractor’s final request for payment, contractor achieved (______%) Minority Business Enterprise (MBE) participation and (_____%) Women Business Enterprise (WBE) participation on this contract, and (b) listed herein are the names of all certified M/WBE subcontractors, regardless of tier, with whom I, or my subcontractors contracted.

1.

Name of MBE/WBE Firm ______________________________________________ Address _____________________________________________________________ _____________________________________________________________ Telephone Number (_______) __________________________________________ IRS Number _________________________________________________________ Area/Scope*of Work __________________________________________________ Subcontract Final Amount ______________________________________________

2.

Name of MBE/WBE Firm _____________________________________________ Address _____________________________________________________________ _____________________________________________________________ Telephone Number (_______) ___________________________________________ IRS Number _________________________________________________________ Area/Scope*of Work___________________________________________________ Subcontract Final Amount ______________________________________________

01290.14 Contractor Affidavit for Final Payment 063009

1 of 2

Contract Central

List additional subcontractors, if any, on a similar form and attach to the bid. Supplier** Final Amount: ___________________________________ *Reference to specification sections or bid item number. () () ()

Met or exceeded the Contract utilization goals; or Failed to meet the Contract utilization goals (attach waiver, substitution or modification); or No goals applied to this Project.

5.

CONTRACTOR certifies that each Subcontractor has received full payment for its respective work in connection with the Contract.

6.

If applicable, I hereby certify that (a) at project completion and pursuant to contractor’s final request for payment, contractor achieved, company-wide, at least ten percent (10%) minority workforce participation and two percent (2%) women workforce participation and (2) a true and accurate copy of my final project workforce monthly report (HRD Form 00485.02 and final company-wide workforce monthly report (HRD Form 00485.03) are attached. NOTE: This paragraph is only applicable if you completed a construction

contract that was estimated by the City, prior to solicitation, as requiring more than 800 construction labor hours and costing in excess of $324,000.01. If applicable you MUST attach copies of your final monthly workforce reports. 7. This affidavit is made in behalf of the CONTRACTOR for the purpose of securing from Kansas City, Missouri, the certification of completion of the Project and receiving payment therefore. 8. If the Contract amount exceeded $123,500.01, CONTRACTOR has submitted proof of compliance with the City tax ordinances administered by the City’s Commissioner of Revenue and has on file proof of tax compliance from all Subcontractors. If the Contract term exceeded one (1) year, CONTRACTOR has provided proof of compliance with the City tax ordinances administered by the City’s Commissioner of Revenue prior to receiving final payment and has on file proof of tax compliance from all Subcontractors prior to the Subcontractor receiving final payment from CONTRACTOR. CONTRACTOR By (Authorized Signature)

Title On this

day of

,

appeared

, before me

, to me personally known to be the of the

,

and who executed the foregoing instrument and acknowledged that (s)he executed the same on behalf of as its free act and deed. IN WITNESS WHEREOF, I have hereunto set my hand and affixed my official seal on the day and year first above written. My commission expires:

Notary Public

01290.14 Contractor Affidavit for Final Payment 063009

2 of 2

Contract Central

SUBCONTRACTOR AFFIDAVIT FOR FINAL PAYMENT Project Number Project Title

STATE OF MISSOURI

) ) ss:

COUNTY OF ______________ ) After being duly sworn the person whose name and signature appears below hereby states under penalty of perjury that: 1. I am the duly authorized officer of the business indicated below (hereinafter Subcontractor) and I make this affidavit on behalf of Subcontractor in accordance with the requirements set forth in Section 290.290, RSMo. Subcontractor has completed all of the Work required under the terms and conditions of a subcontract as follows: Subcontract with: __________________________________________________________________, Contractor Work Performed: ____________________________________________________________________________ Total Dollar Amount of Subcontract and all Change Orders: $_________________________________________ City Certified MBE  WBE  DBE  NA List certifications: ____________________________________________________________________________ 2. Subcontractor fully complied with the provisions and requirements of the Missouri Prevailing Wage Law set forth in Sections 290.210, RSMo through 290.340, RSMo. Business Entity Type: (___) Missouri Corporation (___) Foreign Corporation (___) Fictitious Name Corporation (___) Sole Proprietor (___) Limited Liability Company (___) Partnership (___) Joint Venture (___) Other (Specify)

Subcontractor’s Legal Name and Address ___________________________________________ ___________________________________________ Phone No. __________________________________ Fax: ______________________________________ E:mail:_____________________________________ Federal ID No._______________________________

I hereby certify that I have the authority to execute this affidavit on behalf of Subcontractor. By: ______________________________________ (Signature) _______________________________________ (Title) NOTARY

__________________________________________ (Print Name) __________________________________________ (Date)

Subscribed and sworn to before me this _____ day of ________________________, 20______. My Commission Expires:______________________

By_____________________________

__________________________________________ Print Name

_______________________________ Title

01290.15 Subcontractor Affidavit for Final Payment 020408

Contract Central

ATTACHMENT NO. 5 PERFORMANCE BOND TEMPLATE

PERFORMANCE BOND Project Number Project Title

KNOW ALL MEN BY THESE PRESENTS: That _______________________________________, as PRINCIPAL (CONTRACTOR), and _____________________________________________, (SURETY), licensed to do business as such in the State of Missouri, hereby bind themselves and their respective heirs, executors, administrators, successors, and assigns unto Kansas City, Missouri, a constitutionally chartered municipal corporation, (OWNER), as obligee, in the penal sum of _________________________________________________________ Dollars ($ _________________ ) for the payment whereof CONTRACTOR and SURETY bind themselves, their heirs, executors, administrators, successors and assigns, jointly and severally, firmly by these presents. WHEREAS, CONTRACTOR has entered into a Contract with OWNER for_________________________________ which Contract, including any present or future amendment thereto, is incorporated herein by reference and is hereinafter referred to as the Contract. NOW, THEREFORE, THE CONDITION OF THIS OBLIGATION is such that, if CONTRACTOR shall promptly and faithfully perform said Contract including all duly authorized changes thereto, according to all the terms thereof, including those under which CONTRACTOR agrees to pay legally required wage rates including the prevailing hourly rate of wages in the locality, as determined by the Department of Labor and Industrial Relations or by final judicial determination, for each craft or type of workman required to execute the Contract and, further, shall defend, indemnify, and hold harmless OWNER from all damages, loss and expense occasioned by any failure whatsoever of said CONTRACTOR and SURETY to fully comply with and carry out each and every requirement of the Contract, then this obligation shall be void; otherwise, it shall remain in full force and effect. WAIVER. That SURETY, for value received, hereby expressly agrees that no change, extension of time, alteration or addition to the terms of the Contract or to the Work to be performed thereunder, shall in any way affect the obligations of this Bond; and it does hereby waive notice of any such change, extension of time, or alteration or addition to the terms of the Contract or the Work to be performed thereunder. IN WITNESS WHEREOF, the above parties have executed this instrument the ____ day of ____________________, ____. Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 62 of 63

CONTRACTOR Name, address and facsimile number of Contractor

I hereby certify that I have authority to execute this document on behalf of Contractor. By: Title:

(Attach corporate seal if applicable) SURETY Name, address and facsimile number of Surety:

I hereby certify that (1) I have authority to execute this document on behalf of Surety; (2) Surety has an A.M. Best rating of B+, V, or better; (3) Surety is named in the current list of “Companies Holding Certificates of Authority as Acceptable Reinsuring Companies: as published in Circular 570 (most current revision) by the Financial Management Service, Surety Bond Branch, U.S. Department of the Treasury; and (4) Surety is duly licensed to issue bonds in the State of Missouri and in the jurisdiction in which the Project is located. By: Title: Date: (Attach seal and Power of Attorney)

Enterprise Permitting System RFP NO. EV1788 (REV. 08-21-12 W/G)

ISSUE DATE: 07-19-2013

Page 63 of 63