171125- CONTRACT.PDF

CONTRACT PURSUANT TO RFP
SERIAL 171125-RFP
This Contract is entered into this 27th day of June, 2018 by and between Maricopa County (“County”), a political
subdivision of the State of Arizona, and UNICON International, Inc., an Ohio corporation (“Contractor”) for the
purchase of Hosted Environmental Management services.
1.0 CONTRACT TERM:
1.1 This Contract is for a term of five (5) years, beginning on the 1st of July of 2018 and ending the
30th of June, 2023.
1.2 The County may, at its option and with the agreement of the Contractor, renew the term of this
Contract for additional terms up to a maximum of five (5) additional years, (or at the County’s
sole discretion, extend the contract on a month-to-month bases for a maximum of six (6) months
after expiration). The County shall notify the Contractor in writing of its intent to extend the
Contract term at least sixty (60) calendar days prior to the expiration of the original contract term,
or any additional term thereafter.
1.3 CONTRACT COMPLETION:
The Contractor shall make all reasonable efforts for an orderly transition of its duties and
responsibilities to another provider and/or to the County. This may include but is not limited to
preparation of a transition plan and cooperation with the County or other providers in the
transition. The transition includes the transfer of all records, and other data in the possession,
custody or control of Contractor required to be provided to the County either by the terms of this
agreement or as a matter of law. The provisions of this clause shall survive the expiration or
termination of this agreement.
2.0 FEE ADJUSTMENTS:
Any request for a fee adjustment must be submitted sixty (60) days prior to the current Contract expiration
or annual. Requests for adjustment in cost of labor and/or materials must be supported by appropriate
documentation. The reasonableness of the request will be determined by comparing the request with the
Consumer Price Index or by performing a market survey. If County agrees to the adjusted price terms,
County shall issue written approval of the change and provide an updated version of the Contract. The new
change shall not be in effect until the date stipulated on the Contract.
3.0 PAYMENTS:
3.1 As consideration for performance of the duties described herein, County shall pay Contractor the
sum(s) stated in Exhibit “A.”
3.2 Payment shall be made upon the County’s receipt of a properly completed invoice.

SERIAL 171125-RFP
3.3 INVOICES:
3.3.1 The Contractor shall submit one (1) legible copy of their detailed invoice before
payment(s) can be made. Incomplete invoices will not be processed. At a minimum, the
invoice must provide the following information:
• Company name, address and contact
• County bill-to name and contact information
• Contract Serial Number or
• County purchase order number
• Invoice number and date
• Payment terms
• Description of payable deliverable
• Total Amount Due
3.3.2 Problems regarding billing or invoicing shall be directed to the using agency as listed on
the Purchase Order.
3.3.3 Payment shall be made to the Contractor by Accounts Payable through the Maricopa
County Vendor Express Payment Program. This is an Electronic Funds Transfer (EFT)
process. After Contract Award the Contractor shall complete the Vendor Registration
Form located on the County Department of Finance Vendor Registration Web Site
(http://www.maricopa.gov/Finance/Vendors.aspx).
3.3.4 Discounts offered in the contract shall be calculated based on the date a properly
completed invoice is received by the County (ROI).
3.3.5 EFT payments to the routing and account numbers designated by the Contractor will
include the details on the specific invoices that the payment covers. The Contractor is
required to discuss remittance delivery capabilities with their designated financial
institution for access to those details.
3.4 PAYMENT RETENTION:
3.4.1 Twelve percent (12%) of monies paid for Project Management and Project Labor earned
by Contractor related to work under this agreement shall be retained by County until
Final Completion of the services. County may elect to release specific retention payments
based on mutually agreed milestones, but in no case shall retention be released prior to
Final Completion. All other payment terms and conditions shall not be affected by the
retention. In the event of termination or cancellation of this contract by County through
no fault of Contractor, Contractor shall be entitled to the refund of any funds in the
retention account.
3.4.2 After fifty percent (50%) of the work has been completed, the Maricopa County
Executive Steering Committee may reduce the retainage to six percent (6%) of all monies
previously earned and all monies earned thereafter. Any reduction in retainage shall be
in the discretion of the Maricopa County Executive Steering Committee. Any interest
earned on retainage shall accrue solely to the benefit of County.
3.4.3 The Contractor shall have the right, pursuant to Arizona Revised Statues, to submit
securities in lieu of retention for all work completed. The Contractor is required to
request this option at least ten (10) business days prior to submission of first Application
for Payment to allow time for preparation of forms. The Contractor shall request and
obtain securities forms through County. The County must identify either securities
option or retention option prior to first Application for Payment.

SERIAL 171125-RFP
3.5 APPLICABLE TAXES:
3.5.1 Payment of Taxes: The Contractor shall pay all applicable taxes. With respect to any
installation labor on items that are not attached to real property performed by Contractor
under the terms of this Contract, the installation labor cost and the gross receipts for
materials provided shall be listed separately on the Contractor’s invoices.
3.5.2 State and Local Transaction Privilege Taxes: To the extent any State and local transaction
privilege taxes apply to sales made under the terms of this contract it is the responsibility
of the seller to collect and remit all applicable taxes to the proper taxing jurisdiction of
authority.
3.5.3 Tax Indemnification: Contractor and all subcontractors shall pay all Federal, State, and
local taxes applicable to its operation and any persons employed by the Contractor.
Contractor shall, and require all subcontractors to hold Maricopa County harmless from
any responsibility for taxes, damages and interest, if applicable, contributions required
under Federal, and/or State and local laws and regulations, and any other costs including;
transaction privilege taxes, unemployment compensation insurance, Social Security, and
Worker’s Compensation.
3.6 TAX: (SERVICES):
No tax shall be invoiced or paid against Contractor’s labor. It is the responsibility of the
Contractor to determine any and all applicable taxes and include the cost in the proposal price.
4.0 AVAILABILITY OF FUNDS:
4.1 The provisions of this Contract relating to payment for services shall become effective when funds
assigned for the purpose of compensating the Contractor as herein provided are actually available
to County for disbursement. The County shall be the sole judge and authority in determining the
availability of funds under this Contract. County shall keep the Contractor fully informed as to the
availability of funds.
4.2 If any action is taken by any state agency, Federal department or any other agency or
instrumentality to suspend, decrease, or terminate its fiscal obligations under, or in connection
with, this Contract, County may amend, suspend, decrease, or terminate its obligations under, or in
connection with, this Contract. In the event of termination, County shall be liable for payment
only for services rendered prior to the effective date of the termination, provided that such services
are performed in accordance with the provisions of this Contract. County shall give written notice
of the effective date of any suspension, amendment, or termination under this Section, at least ten
(10) days in advance.
5.0 DUTIES:
5.1 The Contractor shall perform all duties stated in Exhibit “B”, or as otherwise directed in writing
by the Procurement Officer.
5.2 During the Contract term, County may provide Contractor’s personnel with adequate workspace
for consultants and such other related facilities as may be required by Contractor to carry out its
contractual obligations.
6.0 TERMS and CONDITIONS:
6.1 INDEMNIFICATION:
To the fullest extent permitted by law, and to the extent that claims, damages, losses or expenses
are not covered and paid by insurance purchased by the Contractor, the Contractor shall defend
indemnify and hold harmless the County (as Owner), its agents, representatives, agents, officers,
directors, officials, and employees from and against all claims, damages, losses, and expenses

SERIAL 171125-RFP
(including, but not limited to attorneys' fees, court costs, expert witness fees, and the costs and
attorneys' fees for appellate proceedings) arising out of, or alleged to have resulted from the
negligent acts, errors, omissions, or mistakes relating to the performance of this Contract.
Contractor's duty to defend, indemnify, and hold harmless the County, its agents, representatives,
agents, officers, directors, officials, and employees shall arise in connection with any claim,
damage, loss, or expense that is attributable to bodily injury, sickness, disease, death or injury to,
impairment of, or destruction of tangible property, including loss of use resulting there from,
caused by negligent acts, errors, omissions, or mistakes in the performance of this Contract, but
only to the extent caused by the negligent acts or omissions of the Contractor, a subcontractor, any
one directly or indirectly employed by them, or anyone for whose acts they may be liable,
regardless of whether or not such claim, damage, loss, or expense is caused in part by a party
indemnified hereunder.
The amount and type of insurance coverage requirements set forth herein will in no way be
construed as limiting the scope of the indemnity in this paragraph.
The scope of this indemnification does not extend to the sole negligence of County.
6.2 INFRINGEMENT DEFENSE INDEMNIFICATION
6.2.1 Defense and Indemnity: Contractor shall defend, Participate and Share in the Cost, as
defined below, in the full defense of the County against any Claim, as defined below, and
will indemnify and hold harmless the County as provided for in this Section for any
judgments, settlements and court awarded attorney’s fees resulting from a Claim where
the claimant is adjudged the successful party in the Claim. Contractor’s obligations under
this Section are conditioned on the following: (i) County promptly notifies Contractor of
the Claim in writing upon made aware of the Claim; (ii) County gives Contractor lead
authority and County being control of the defense and (if applicable) settlement of the
Claim, provided that County’s legal counsel may participate in such defense and
settlement, at County’s expense, and (iii) County provides all information and assistance
reasonably requested by Contractor to handle the defense or settlement of the Claim. For
purposes of this Section, “Claim” means any cause of action in a third party action, suit
or proceeding against County alleging that CONTRACTOR software, or its upgrades,
modifications, or revisions, as of its delivery date under this Agreement, infringes a valid
U.S. patent, copyright or trademark. For the purposes of this section, “Participate and
Share in the Costs” means Contractor will assist the County in the defense of the claim,
to the extent agreed to by the parties, except that Contractor shall be solely responsible
for any and all costs adjudged in a successful Claim against the County.
6.2.2 Remedial Measures: If software becomes, or Contractor reasonably believes use of
software may become, the subject of a Claim, Contractor may, at its own expense and
option: (i) procure for County the right to continue use of the Product; (ii) replace or
modify the software; or to the extent that neither (i) nor (ii) are deemed commercially
practicable, (iii) refund to County a pro-rated portion of the applicable fees for software
based on a linear depreciation monthly over 10 year useful life, in which case County will
cease all use of software and return it to Contractor.
6.2.2.1 Exceptions: Contractor will have no defense or indemnity obligation for any
Claim based on: (i) modifications by someone other than Contractor; (ii)
software has been modified by Contractor in accordance with County-provided
specifications or instructions; (iii) use or combination by the County of software
with Third Party Products, open source or freeware technology; (iv) Third Party
Products, open source or freeware technology; (v) a product that is used or
located by County in a country other than the country in which or for which it
was supplied by Contractor; (vi) possession or use of a product after Contractor
has informed County of modifications or changes required to avoid such Claim
and offered to implement those modifications or changes, if such Claim would
have been avoided by implementation of Contractor's suggestions and to the
extent County did not provide Contractor with a reasonable opportunity to

SERIAL 171125-RFP
implement Contractor's suggestions; or (vii) the amount of revenue or profits
earned or other value obtained by the use of Products, or the amount of use of
the Products. “Third Party Products” means any products made by a party other
than Contractor, and may include, without limitation, products ordered by
County from third parties. However, components of Contractor-branded
Products are not Third Party Products if they are both: (i) embedded in Third
Party Products (i.e., not recognizable as standalone items); and (ii) not identified
as separate items on Contractor’s price list, quotes, order specifications forms or
Documentation.
6.2.3 The foregoing states Contractor’s entire liability, and County’s sole and exclusive remedy
except as provided at law or equity, with respect to any infringement or misappropriate of
any intellectual property rights of another party.
6.3 OWNERSHIP OF CONTRACT MATERIALS:
6.3.1 Contractor agrees that all Contract materials, reports, and other data or materials
generated or developed by Contractor under this Agreement or furnished by the County
to the Contractor shall be and remain the property of the County. Contractor specifically
agrees that all copyrightable material developed or created under this Contract shall be
considered works made for hire by Contractor for the County and that such material shall,
upon creation, be owned exclusively by the County.
6.3.2 To the extent that any such material, under applicable law, may not be considered work
made for hire by Contractor for County, Contractor agrees to assign and, upon its
creation, automatically assigns to County the ownership of such material, including any
copyright or other intellectual property rights in such materials, without the necessity of
any further consideration. County shall be entitled to obtain and hold in its own name all
copyrights in respect of such materials. Contractor shall perform any acts that may be
deemed necessary or desirable by County to evidence more fully the transfer of
ownership of all materials referred to in this section 7 to County to the fullest extent
possible, including, without limitation, by executing further written assignments in a form
requested by County.
6.3.3 To the extent that any preexisting rights of Contractor are embodied in the Contract
Materials, Contractor hereby grants to County the irrevocable, perpetual, nonexclusive,
worldwide royalty-free right and license to (1) use, execute, reproduce, display, perform,
distribute copies of, and prepare derivative works based upon such pre-existing rights and
any derivative works thereof and (2) authorize others to do any or all of the foregoing.
6.3.4 Contractor represents and warrants that it either owns or has valid, paid-up licenses for all
software used by it in the performance of its obligations under this Agreement.
6.4 INSURANCE:
6.4.1 Contractor, at Contractor’s own expense, shall purchase and maintain the herein
stipulated minimum insurance from a company or companies duly licensed by the State
of Arizona and possessing a current A.M. Best, Inc. rating of B++. In lieu of State of
Arizona licensing, the stipulated insurance may be purchased from a company or
companies, which are authorized to do business in the State of Arizona, provided that
said insurance companies meet the approval of County. The form of any insurance
policies and forms must be acceptable to County.
6.4.2 All insurance required herein shall be maintained in full force and effect until all work or
service required to be performed under the terms of the Contract is satisfactorily
completed and formally accepted. Failure to do so may, at the sole discretion of County,
constitute a material breach of this Contract.
6.4.3 Contractor’s insurance shall be primary insurance as respects County, and any insurance
or self-insurance maintained by County shall not contribute to it.

SERIAL 171125-RFP
6.4.4 Any failure to comply with the claim reporting provisions of the insurance policies or any
breach of an insurance policy warranty shall not affect the County’s right to coverage
afforded under the insurance policies.
6.4.5 The insurance policies may provide coverage that contains deductibles or self-insured
retentions. Such deductible and/or self-insured retentions shall not be applicable with
respect to the coverage provided to County under such policies. Contractor shall be
solely responsible for the deductible and/or self-insured retention and County, at its
option, may require Contractor to secure payment of such deductibles or self-insured
retentions by a surety bond or an irrevocable and unconditional letter of credit.
6.4.6 The insurance policies required by this Contract, except Workers’ Compensation and
Errors and Omissions, shall name County, its agents, representatives, officers, directors,
officials and employees as Additional Insureds.
6.4.7 The policies required hereunder, except Workers’ Compensation and Errors and
Omissions, shall contain a waiver of transfer of rights of recovery (subrogation) against
County, its agents, representatives, officers, directors, officials and employees for any
claims arising out of Contractor’s work or service.
6.4.8 Commercial General Liability
Commercial General Liability insurance and, if necessary, Commercial Umbrella
insurance with a limit of not less than $2,000,000 for each occurrence, $4,000,000
Products/Completed Operations Aggregate, and $4,000,000 General Aggregate Limit.
The policy shall include coverage for premises liability, bodily injury, broad form
property damage, personal injury, products and completed operations and blanket
contractual coverage, and shall not contain any provisions which would serve to limit
third party action over claims. There shall be no endorsement or modifications of the
CGL limiting the scope of coverage for liability arising from explosion, collapse, or
underground property damage.
6.4.9 Automobile Liability
Commercial/Business Automobile Liability insurance and, if necessary, Commercial
Umbrella insurance with a combined single limit for bodily injury and property damage
of not less than $1,000,000 each occurrence with respect to any of the Contractor’s
owned, hired, and non-owned vehicles assigned to or used in performance of the
Contractor’s work or services or use or maintenance of the Premises under this Contract.
6.4.10 Workers’ Compensation
Workers’ Compensation insurance to cover obligations imposed by federal and state
statutes having jurisdiction of Contractor’s employees engaged in the performance of the
work or services under this Contract; and Employer’s Liability insurance of not less than
$1,000,000 for each accident, $1,000,000 disease for each employee, and $1,000,000
disease policy limit.
Contractor, its contractors and its subcontractors waive all rights against County and its
agents, officers, directors and employees for recovery of damages to the extent these
damages are covered by the Workers’ Compensation and Employer’s Liability or
commercial umbrella liability insurance obtained by Contractor, its contractors and its
subcontractors pursuant to this Contract.

SERIAL 171125-RFP
6.4.11 Errors and Omissions (Professional Liability) Insurance
Errors and Omissions (Professional Liability) insurance and, if necessary, Commercial
Umbrella insurance, which will insure and provide coverage for errors or omissions or
professional liability of the CONTRACTOR, with limits of no less than $2,000,000 for
each claim.
6.4.12 Cyber – If a vendor is “getting into” County computer systems
Policy Limit:
6.4.12.1 The policy shall be issued with minimum limits of $100,000.
6.4.12.2 The policy shall include coverage for all directors, officers, agents and
employees of the Contractor.
6.4.12.3 The policy shall include coverage for third party fidelity.
6.4.12.4 The policy shall include coverage for theft.
6.4.12.5 The policy shall contain no requirement for arrest and conviction.
6.4.12.6 The policy shall cover loss outside the premises of the Named Insured.
6.4.12.7 The policy shall endorse (Blanket Endorsements are not acceptable) the
Department as Loss Payee as our interest may appear.
6.4.13 Technology Errors & Omission Insurance
• Each claim $2,000,000
• Annual Aggregate $2,000,000
Such insurance shall cover any, and all errors, omissions, or negligent acts in the delivery
of products, services, and/or licensed programs under this contract.
In the event that the Tech E&O insurance required by this Contract is written on a claims-
made basis, Contractor warrants that any retroactive date under the policy shall precede
the effective date of this Contract and, either continuous coverage will be maintained or
an extended discovery period will be exercised for a period of two (2) years, beginning at
the time work under this Contract is completed.
6.4.14 Network Security (Cyber) and Privacy Liability
• Each Claim $2,000,000
• Annual Aggregate $2,000,000
Such insurance shall include, but not be limited to, coverage for third party claims and
losses with respect to network risks (such as data breaches, unauthorized access or use,
ID theft of data) and invasion of privacy regardless of the type of media involved in the
loss of private information, crisis management and identity theft response costs. This
should also include breach notification costs, credit remediation, and credit monitoring,
defense and claims expenses, regulatory defense costs plus fines and penalties, cyber
extortion, computer program and electronic data restoration expenses coverage (data
asset protection), network business interruption, computer fraud coverage, and funds
transfer loss.
In the event that the Network Security and Privacy Liability insurance required by this
Contract is written on a claims-made basis, Contractor warrants that any retroactive date
under the policy shall precede the effective date of this Contract and, either continuous
coverage will be maintained, or an extended discovery period will be exercised for a
period of two (2) years beginning at the time work under this Contract is completed.
The policy shall be endorsed, as required by this written agreement, to include the
County, its agents, representatives, officers, directors, officials, employees and additional

SERIAL 171125-RFP
insureds with respect to liability arising out of the activities performed by or on behalf of
the Contractor.
Policy shall contain a waiver of subrogation endorsement, as required by this written
agreement, in favor of the County, its agents, representatives, officers, directors, officials,
employees for losses arising from work performed by or on behalf of the Contractor.
6.4.15 Certificates of Insurance
6.4.15.1 Prior to Contract AWARD, Contractor shall furnish the County with valid and
complete certificates of insurance, or formal endorsements as required by the
Contract in the form provided by the County, issued by Contractor’s insurer(s),
as evidence that policies providing the required coverage, conditions and limits
required by this Contract are in full force and effect. Such certificates shall
identify this contract number and title.
6.4.15.2 In the event any insurance policy (ies) required by this contract is (are) written
on a “claims made” basis, coverage shall extend for two years past completion
and acceptance of Contractor’s work or services and as evidenced by annual
Certificates of Insurance.
6.4.15.3 If a policy does expire during the life of the Contract, a renewal certificate must
be sent to County fifteen (15) days prior to the expiration date.
6.4.16 Cancellation and Expiration Notice
Applicable to all insurance policies required within the Insurance Requirements of this
Contract, Contractor’s insurance shall not be permitted to expire, be suspended, be
canceled, or be materially changed for any reason without thirty (30) days prior written
notice to Maricopa County. Contractor must provide to Maricopa County, within 2
business days of receipt, if they receive notice of a policy that has been or will be
suspended, canceled, materially changed for any reason, has expired, or will be expiring.
Such notice shall be sent directly to Maricopa County Office of Procurement Services
and shall be mailed or hand delivered to 320 West Lincoln Street, Phoenix, AZ 85003, or
emailed to Procurement Officer noted in solicitation.
6.5 SOURCE CODE:
6.5.1 Upon commencement of the services described in Exhibit B, Scope of Work, Contractor
shall provide County with a copy of the base source code for the system. Contractor shall
also provide County any and all updates to the source code over the life of this
agreement.
6.6 CONTRACTOR EMPLOYEE MANAGEMENT:
6.6.1 Contractor shall endeavor to maintain the core personnel proposed in their offer
throughout the implementation of the Solution. In the event that Contractor personnel’s
employment status changes, Contractor shall provide County a list of proposed
candidates with equivalent experience with the Solution. County reserves the right to
assist in the selection of the replacement candidate. Under no circumstances is it
acceptable for the implementation schedule to be impacted by a personnel change on the
part of the Contractor.
6.6.2 Contractor shall not reassign any provided core personnel without the express consent of
the County.
6.6.3 County reserves the right to immediately remove from its premises any Contractor
personnel it determines is a risk to County operations.

SERIAL 171125-RFP
6.6.4 County reserves the right to request the replacement of Contractor personnel at any time,
for any reason.
6.7 FORCE MAJEURE:
6.7.1 Neither party shall be liable for failure of performance, nor incur any liability to the other
party on account of any loss or damage resulting from any delay or failure to perform all
or any part of this Contract if such delay or failure is caused by events, occurrences, or
causes beyond the reasonable control and without negligence of the parties. Such events,
occurrences, or causes will include Acts of God/Nature (including fire, flood, earthquake,
storm, hurricane or other natural disaster), war, invasion, act of foreign enemies,
hostilities (whether war is declared or not), civil war, riots, rebellion, revolution,
insurrection, military or usurped power or confiscation, terrorist activities,
nationalization, government sanction, lockout, blockage, embargo, labor dispute, strike,
interruption or failure of electricity or telecommunication service.
6.7.2 Each party, as applicable, shall give the other party notice of its inability to perform and
particulars in reasonable detail of the cause of the inability. Each party must use best
efforts to remedy the situation and remove, as soon as practicable, the cause of its
inability to perform or comply.
6.7.3 The party asserting Force Majeure as a cause for non-performance shall have the burden
of proving that reasonable steps were taken to minimize delay or damages caused by
foreseeable events, that all non-excused obligations were substantially fulfilled, and that
the other party was timely notified of the likelihood or actual occurrence which would
justify such an assertion, so that other prudent precautions could be contemplated.
6.7.4 The County shall reserve the right to terminate this Contract and/or any applicable order
or contract release purchase order upon non-performance by Contractor. The County
shall reserve the right to extend the Contract and time for performance at its discretion.
6.8 ACCEPTANCE PROCESS:
The acceptance process and criteria set out in this section shall apply strictly to the initial
implementation project and will not apply post warranty. Further details of the process and criteria
are provided in Exhibit B of this agreement.
6.8.1 Acceptance for the Application Package and the System Testing shall be an on-going,
iterative activity which shall be performed throughout the Contract, provided that
Deliverables that have passed Acceptance will not be subject to re-testing for Acceptance
except (a) to the extent they interoperate with, or are modified by, further Deliverables
undergoing Acceptance, or (b) as part of Final Acceptance. The timing for completion of
testing activities shall be mutually agreed upon and included in the Project Plan.
6.8.2 The Contractor will perform initial testing from its premises prior to delivery of a
Deliverable. County may ask to see the initial testing results from Contractor, but only
for comparison to the County’s Onsite results.
6.8.3 The process for pre-user acceptance testing of Application Package Deliverables shall
include the following steps:
6.8.3.1 Contractor completes an Application Package Deliverable;
6.8.3.2 Contractor configures the Deliverable and/or the Application Package in the
Delivery Platform with assistance from County;
6.8.3.3 Contractor provides a conference room pilot to demonstrate functionality
included in the Application Package including such Deliverable and how it is
intended to be used;

SERIAL 171125-RFP
6.8.3.4 County completes additional testing of such Deliverable to validate the
configuration as part of the Application Package in the Delivery Platform; and
6.8.3.5 County provides Contractor with feedback about the current Deliverable, which
Contractor shall consider and, to the extent consistent with the SOW,
incorporate into the next Deliverable (or as may be mutually agreed pursuant to
a change order).
6.9 CRITERIA FOR DELIVERY AND ACCEPTANCE OF DELIVERABLES:
Further details of the process and criteria are provided in Exhibit B of this agreement.
6.9.1 The Contractor shall submit all Deliverables to the County Representative. Each
Deliverable will be in the requisite format specified in the SOW and contain the content
required by the SOW prior to the Deliverable being submitted. Documentation shall be
delivered in one electronic version with accompanying transmittal letters.
6.9.2 County Representative shall review and validate Contractor’s Deliverables product prior
to Acceptance. Acceptance criteria for Deliverables shall consist of the following:
6.9.2.1 Specific Deliverables are completed as specified in this Contract and the final
Deliverable has been rendered.
6.9.2.2 Plans, schedules, designs, documentation, and reports are approved and
completed as specified in this Contract.
6.9.2.3 All supporting Documentation is provided and complete.
6.9.2.4 All Deliverables are presented to County in the approved format (or if no such
format is approved, in an industry-standard format).
6.9.2.5 All Deliverables are at the agreed upon acceptable level of quality as defined in
this Contract.
6.10 SOFTWARE UPDATES, WARRANTY, MAINTENANCE & ROADMAP/ENHANCEMENTS:
6.10.1 Contractor shall make available to County at no additional charge all Enhancements to
the Application Package as they are released so long as the County is currently under the
Contractor’s agreement for Support and is using a Current Release. The County shall
decide at its discretion whether or not to take advantage of such Enhancement and
support it under the Support agreement. Notwithstanding the foregoing, County
acknowledges that Support will be limited to a commercially reasonable effort basis if the
County elects not to maintain a Current Release of the Application Package.
6.10.2 To ensure that Documentation is consistent with the operating environment, updated
Documentation shall be delivered concurrently with every Enhancement where the
functionality documented has materially been changed, or the cumulative effect of
previous Enhancements has rendered the functionality documented to have materially
changed.
6.10.3 The Contractor shall ensure that the software remains compatible with the latest versions
of all software languages, database management systems, operating environments, and
any other related software functionality that may be used in the operation of the
Application. The Contractor shall update the Application Package in a timely manner as
necessary to maintain said compatibility.
6.10.4 Maricopa County will, on a periodic basis, perform security scans utilizing a third-party
industry standard tool. Maricopa County and the Contractor will collaborate on reviewing
the findings generated by the tool. The Contractor agrees to remediate high and medium
vulnerabilities within a reasonable amount of time as agreed to with the Maricopa County
Office of Information Security. Security scans shall be performed no less than fifteen (15)

SERIAL 171125-RFP
business days prior to initial deployment of the software and to major software updates,
and may be performed at other times at the discretion of Maricopa County.
6.11 WARRANTY OF SERVICES:
6.11.1 The Contractor warrants that all services provided hereunder will conform to the
requirements of the Contract, including all descriptions, specifications and attachments
made a part of this Contract. County’s acceptance of services or goods provided by the
Contractor shall not relieve the Contractor from its obligations under this warranty.
6.11.2 In addition to its other remedies, County may, at the Contractor's expense, require prompt
correction of any services failing to meet the Contractor's warranty herein. Services
corrected by the Contractor shall be subject to all the provisions of this Contract in the
manner and to the same extent as services originally furnished hereunder.
6.12 INSPECTION OF SERVICES:
6.12.1 The Contractor shall provide and maintain an inspection system acceptable to County
covering the services under this Contract. Complete records of all inspection work
performed by the Contractor shall be maintained and made available to County during
contract performance and for as long afterwards as the Contract requires.
6.12.2 County has the right to inspect and test all services called for by the Contract, to the
extent practicable at all times and places during the term of the Contract. County shall
perform inspections and tests in a manner that will not unduly delay the work.
6.12.3 If any of the services do not conform to Contract requirements, County may require the
Contractor to perform the services again in conformity with Contract requirements, at no
cost to the County. When the defects in services cannot be corrected by re-performance,
County may:
6.12.3.1 Require the Contractor to take necessary action to ensure that future
performance conforms to Contract requirements; and
6.12.3.2 Reduce the Contract price to reflect the reduced value of the services performed.
6.12.4 If the Contractor fails to promptly perform the services again or to take the necessary
action to ensure future performance in conformity with Contract requirements, County
may:
6.12.4.1 By Contract or otherwise, perform the services and charge to the Contractor,
through direct billing or through payment reduction, any cost incurred by
County that is directly related to the performance of such service; or
6.12.4.2 Terminate the Contract for default.
6.13 ORDERING AUTHORITY:
Any request for purchase shall be accompanied by a valid purchase order, issued by Office of
Procurement Services, a Purchase Order issued by the using Department or direction by a
Certified Agency Procurement Aid (CAPA) with a Purchase Card for payment.
6.14 NO MINIMUM OR MAXIMUM PURCHASE OBLIGATION:
6.14.1 This Contract does not guarantee any minimum or maximum purchases will be made.
Orders will only be placed under this Contract when the County identifies a need and
proper authorization and documentation have been approved.
6.14.2 Contractors agree to accept verbal notification of cancellation of Purchase Orders from
the County Procurement Officer with written notification to follow. Contractor
specifically acknowledges to be bound by this cancellation policy.

SERIAL 171125-RFP
6.15 PURCHASE ORDERS:
County reserves the right to cancel Purchase Orders within a reasonable period of time after
issuance. Should a Purchase Order be canceled, the County agrees to reimburse the Contractor for
actual and documentable costs incurred by the Contractor in response to the Purchase Order. The
County will not reimburse the Contractor for any costs incurred after receipt of County notice of
cancellation, or for lost profits, shipment of product prior to issuance of Purchase Order, etc.
6.16 BACKGROUND CHECK:
Contractors need to be aware that there may be multiple background checks (Sheriff’s Office,
County Attorney's Office, Courts as well as Maricopa County general government) to determine if
the respondents employees are acceptable for the contractor to do business with the County. This
applies to (but is not limited to) the company and sub-contractors. Employees or others who fail to
pass these checks shall not be allowed to work on County projects. Failure to meet these
requirements may lead to termination of the contract.
6.17 SUSPENSION OF WORK:
The Procurement Officer may order the Contractor, in writing, to suspend, delay, or interrupt all or
any part of the work of this contract for the period of time that the Procurement Officer determines
appropriate for the convenience of the County. No adjustment shall be made under this clause for
any suspension, delay, or interruption to the extent that performance would have been so
suspended, delayed, or interrupted by any other cause, including the fault or negligence of the
Contractor. No request for adjustment under this clause shall be granted unless the claim, in an
amount stated, is asserted in writing as soon as practicable after the termination of the suspension,
delay, or interruption, but not later than the date of final payment under the Contract.
6.18 STOP WORK ORDER:
The Procurement Officer may, at any time, by written order to the Contractor, require the
Contractor to stop all, or any part, of the work called for by this contract for a period of 90 days
after the order is delivered to the Contractor, and for any further period to which the parties may
agree. The order shall be specifically identified as a stop work order issued under this clause.
Upon receipt of the order, the Contractor shall immediately comply with its terms and take all
reasonable steps to minimize the incurrence of costs allocable to the work covered by the order
during the period of work stoppage. Within a period of 90 days after a stop-work is delivered to
the Contractor, or within any extension of that period to which the parties shall have agreed, the
Procurement Officer shall either;
6.18.1 Cancel the stop-work order; or
6.18.2 Terminate the work covered by the order as provided in the Default, or the Termination
for Convenience clause of this contract.
6.18.3 The Procurement Officer may make an equitable adjustment in the delivery schedule
and/or contract price, or otherwise, and the contract shall be modified, in writing
accordingly, if the Contractor demonstrates that the stop work order resulted in an
increase in costs to the Contractor.
6.19 TERMINATION FOR CONVENIENCE:
Maricopa County may terminate the resultant Contract for convenience by providing sixty (60)
calendar days advance notice to the Contractor.

SERIAL 171125-RFP
6.20 TERMINATION FOR DEFAULT:
The County may, by written notice of default to the Contractor, terminate this contract in whole or
in part if the Contractor fails to:
6.20.1 Deliver the supplies or to perform the services within the time specified in this contract or
any extension;
6.20.2 Make progress, so as to endanger performance of this contract; or
6.20.3 Perform any of the other provisions of this contract.
The County’s right to terminate this contract under these subparagraph may be exercised if the
Contractor does not cure such failure within 10 business days (or more if authorized in writing by
the County) after receipt of the notice from the Procurement Officer specifying the failure.
6.21 STATUTORY RIGHT OF CANCELLATION FOR CONFLICT OF INTEREST:
Notice is given that pursuant to A.R.S. § 38-511 the County may cancel any Contract without
penalty or further obligation within three years after execution of the Contract, if any person
significantly involved in initiating, negotiating, securing, drafting or creating the Contract on
behalf of the County is at any time while the Contract or any extension of the Contract is in effect,
an employee or agent of any other party to the Contract in any capacity or consultant to any other
party of the Contract with respect to the subject matter of the Contract. Additionally, pursuant to
A.R.S § 38-511 the County may recoup any fee or commission paid or due to any person
significantly involved in initiating, negotiating, securing, drafting or creating the Contract on
behalf of the County from any other party to the contract arising as the result of the Contract.
6.22 CONTRACTOR LICENSE REQUIREMENT:
6.22.1 Contractor shall procure all permits, insurance, licenses and pay the charges and fees
necessary and incidental to the lawful conduct of his/her business, and as necessary
complete any required certification requirements, required by any and all governmental
or non-governmental entities as mandated to maintain compliance with and in good
standing for all permits and/or licenses. Contractor shall keep fully informed of existing
and future trade or industry requirements, Federal, State and Local laws, ordinances, and
regulations which in any manner affect the fulfillment of a Contract and shall comply
with the same. Contractor shall immediately notify both Office of Procurement Services
and the using agency of any and all changes concerning permits, insurance or licenses.
6.22.2 Contractor furnishing finished products, materials or articles of merchandise that will
require installation or attachment as part of the Contract, shall possess any licenses
required. Contractor is not relieved of its obligation to possess the required licenses by
subcontracting of the labor portion of the Contract. Respondents are advised to contact
the Arizona Registrar of Contractors, Chief of Licensing, to ascertain licensing
requirements for a particular contract.
6.23 SUBCONTRACTING:
6.23.1 The Contractor may not assign to another Contractor or Subcontract to another party for
performance of the terms and conditions hereof without the written consent of the
County. All correspondence authorizing subcontracting must reference the Bid Serial
Number and identify the job project.
6.23.2 The Subcontractor’s rate for the job shall not exceed that of the Prime Contractor’s rate,
as bid in the pricing section, unless the Prime Contractor is willing to absorb any higher
rates or the County has approved the increase. The Subcontractor’s invoice shall be
invoiced directly to the Prime Contractor, who in turn shall pass-through the costs to the

SERIAL 171125-RFP
County, without mark-up. A copy of the Subcontractor’s invoice must accompany the
Prime Contractor’s invoice.
6.24 AMENDMENTS:
All amendments to this Contract shall be in writing and approved/signed by both Parties.
Maricopa County Office of Procurement Services shall be responsible for approving all
amendments for Maricopa County.
6.25 ADDITIONS/DELETIONS OF SERVICE:
The County reserves the right to add and/or delete materials and services to a Contract. If a
service requirement is deleted, payment to the Contractor will be reduced proportionately, to the
amount of service reduced in accordance with the bid price. If additional materials or services are
required from a Contract, prices for such additions will be negotiated between the Contractor and
the County.
6.26 VALIDITY:
The invalidity, in whole or in part, of any provision of this Contract shall not void or affect the
validity of any other provision of the Contract.
6.27 SEVERABILITY:
The removal, in whole or in part, of any provision of this Contract shall not void or affect the
validity of any other provision of this Contract.
6.28 RIGHTS IN DATA:
The County shall have the use of data and reports resulting from a Contract without additional cost
or other restriction except as may be established by law or applicable regulation. Each party shall
supply to the other party, upon request, any available information that is relevant to a Contract and
to the performance thereunder.
6.29 NON-DISCRIMINATION:
CONTRACTOR agrees to comply with all provisions and requirements of Arizona Executive
Order 2009-09 including flow down of all provisions and requirements to any subcontractors.
Executive Order 2009-09 supersedes Executive order 99-4 and amends Executive order 75-5 and
may be viewed and downloaded at the Governor of the State of Arizona’s website
http://azmemory.azlibrary.gov/cdm/singleitem/collection/execorders/id/680/rec/1 which is hereby
incorporated into this contract as if set forth in full herein. During the performance of this contract,
CONTRACTOR shall not discriminate against any employee, client or any other individual in any
way because of that person’s age, race, creed, color, religion, sex, disability or national origin.
6.30 ISRAEL BOYCOTT:
By signing this Contract, the Contractor certifies that they are in compliance with Article 9,
Arizona Revised Statutes Section 35-393 et seq.
6.31 CERTIFICATION REGARDING DEBARMENT AND SUSPENSION:
6.31.1 The undersigned (authorized official signing on behalf of the Contractor) certifies to the
best of his or her knowledge and belief that the Contractor, it’s current officers and
directors;
6.31.1.1 are not presently debarred, suspended, proposed for debarment, declared
ineligible, or voluntarily excluded from being awarded any contract or grant
by any United States Department or Agency or any state, or local jurisdiction;

SERIAL 171125-RFP
6.31.1.2 have not within three (3) year period preceding this Contract;
6.31.1.3 been convicted of fraud or any criminal offense in connection with obtaining,
attempting to obtain, or as the result of performing a government entity
(Federal, State or local) transaction or contract; and
6.31.1.4 been convicted of violation of any Federal or State antitrust statues or
conviction for embezzlement, theft, forgery, bribery, falsification or
destruction of records, making false statements, or receiving stolen property
regarding a government entity transaction or contract;
6.31.1.5 are not presently indicted or criminally charged by a government entity
(Federal, State or local) with commission of any criminal offenses in
connection with obtaining, attempting to obtain, or as the result of performing
a government entity public (Federal, State or local) transaction or contract;
and are not presently facing any civil charges from any governmental entity
regarding obtaining, attempting to obtain, or from performing any
governmental entity contract or other transaction; and have not within a three
(3) year period preceding this Contract had any public transaction (Federal,
State or local) terminated for cause or default.
6.31.2 If any of the above circumstances described in the paragraph are applicable to the entity
submitting a bid for this requirement, include with your bid an explanation of the matter
including any final resolution.
6.31.3 The Contractor shall include, without modification, this clause in all lower tier covered
transactions (i.e. transactions with subcontractors) and in all solicitations for lower tier
covered transactions related to this Contract.
6.32 VERIFICATION REGARDING COMPLIANCE WITH ARIZONA REVISED STATUTES §41-
4401 AND FEDERAL IMMIGRATION LAWS AND REGULATIONS:
6.32.1 By entering into the Contract, the Contractor warrants compliance with the Immigration
and Nationality Act (INA using e-verify) and all other federal immigration laws and
regulations related to the immigration status of its employees and A.R.S. §23-214(A). The
contractor shall obtain statements from its subcontractors certifying compliance and shall
furnish the statements to the Procurement Officer upon request. These warranties shall
remain in effect through the term of the Contract. The Contractor and its subcontractors
shall also maintain Employment Eligibility Verification forms (I-9) as required by the
Immigration Reform and Control Act of 1986, as amended from time to time, for all
employees performing work under the Contract and verify employee compliance using the
E-verify system and shall keep a record of the verification for the duration of the
employee’s employment or at least three years, whichever is longer. I-9 forms are available
for download at USCIS.GOV.
6.32.2 The County retains the legal right to inspect contractor and subcontractor employee
documents performing work under this Contract to verify compliance with paragraph 6.32.1
of this Section. Contractor and subcontractor shall be given reasonable notice of the
County’s intent to inspect and shall make the documents available at the time and date
specified. Should the County suspect or find that the Contractor or any of its subcontractors
are not in compliance, the County will consider this a material breach of the contract and
may pursue any and all remedies allowed by law, including, but not limited to: suspension
of work, termination of the Contract for default, and suspension and/or debarment of the
Contractor. All costs necessary to verify compliance are the responsibility of the
Contractor.

SERIAL 171125-RFP
6.33 INFLUENCE:
As prescribed in MC1-1202 of the Maricopa County Procurement Code, any effort to influence an
employee or agent to breach the Maricopa County Ethical Code of Conduct or any ethical conduct
may be grounds for Disbarment or Suspension under MC1-902.
An attempt to influence includes, but is not limited to:
6.33.1 A Person offering or providing a gratuity, gift, tip, present, donation, money,
entertainment or educational passes or tickets, or any type of valuable contribution or
subsidy,
6.33.2 That is offered or given with the intent to influence a decision, obtain a contract, garner
favorable treatment, or gain favorable consideration of any kind.
If a Person attempts to influence any employee or agent of Maricopa County, the Chief
Procurement Officer, or his designee, reserves the right to seek any remedy provided by the
Maricopa County Procurement Code, any remedy in equity or in the law, or any remedy provided
by this contract.
6.34 UNIFORM ADMINISTRATIVE REQUIREMENTS:
By entering into this Contract the Contractor agrees to comply with all applicable provisions of
Title 2, Subtitle A, Chapter II, PART 200—UNIFORM ADMINISTRATIVE REQUIREMENTS,
COST PRINCIPLES, AND AUDIT REQUIREMENTS FOR FEDERAL AWARDS contained in
Title 2 C.F.R. § 200 et seq.
6.35 ACCESS TO AND RETENTION OF RECORDS FOR THE PURPOSE OF AUDIT AND/OR
OTHER REVIEW:
6.35.1 In accordance with section MCI 371 of the Maricopa County Procurement Code the
Contractor agrees to retain all books, records, accounts, statements, reports, files, and
other records and back-up documentation relevant to this Contract for six (6) years after
final payment or until after the resolution of any audit questions which could be more
than six (6) years, whichever is latest. The County, Federal or State auditors and any
other persons duly authorized by the Department shall have full access to, and the right to
examine, copy and make use of, any and all said materials.
6.35.2 If the Contractor’s books, records , accounts, statements, reports, files, and other records
and back-up documentation relevant to this Contract are not sufficient to support and
document that requested services were provided, the Contractor shall reimburse Maricopa
County for the services not so adequately supported and documented.
6.36 AUDIT DISALLOWANCES:
If at any time it is determined by the County that a cost for which payment has been made is a
disallowed cost, the County shall notify the Contractor in writing of the disallowance. The course
of action to address the disallowance shall be at sole discretion of the County, and may include
either an adjustment to future invoices, request for credit, request for a check or a deduction from
current invoices submitted by the Contractor equal to the amount of the disallowance, or to require
reimbursement forthwith of the disallowed amount by the Contractor by issuing a check payable
to Maricopa County.
6.37 OFFSET FOR DAMAGES:
In addition to all other remedies at Law or Equity, the County may offset from any money due to
the Contractor any amounts Contractor owes to the County for damages resulting from breach or
deficiencies in performance of the contract.

SERIAL 171125-RFP
6.38 CONFIDENTIAL INFORMATION:
Any information obtained in the course of performing this contract may include information that is
proprietary or confidential to the County. This provision establishes the contractor’s obligation
regarding such information.
The Contractor shall establish and maintain procedures and controls that are adequate to assure
that no information contained in its records and/or obtained from the County or from others in
carrying out its functions (services) under the Contract shall be used by or disclosed by it, its
agents, officers, or employees, except as required to efficiently perform duties under the Contract.
The Contractor’s procedures and controls at a minimum must be the same procedures and controls
it uses to protect its own proprietary or confidential information. If, at any time during the
duration of the Contract, the County determines that the procedures and controls in place are not
adequate, the Contractor shall institute any new and/or additional measures requested by the
County within 15 days of the written request to do so.
Any requests to the Contractor for County proprietary or confidential information shall be referred
to the County for review and approval, prior to any dissemination.
6.39 PUBLIC RECORDS:
Under Arizona law, all Contracts are public records and must be retained by the Records Manager
at the Office of Procurement Services. Contracts shall be open to public inspection and copying
after Contract award and execution, except for such Contracts or sections thereof determined to
contain proprietary or confidential information by the Office of Procurement Services.
6.40 PRICES:
Contractor warrants that prices extended to County under this Contract are no higher than those
paid by any other customer for these or similar services.
6.41 INTEGRATION:
This Contract represents the entire and integrated agreement between the parties and supersedes
all prior negotiations, proposals, communications, understandings, representations, or agreements,
whether oral or written, express or implied.
6.42 RELATIONSHIPS:
In the performance of the services described herein, the Contractor shall act solely as an
independent contractor, and nothing herein or implied herein shall at any time be construed as to
create the relationship of employer and employee, co-employee, partnership, principal and agent,
or joint venture between the County and the Contractor.
6.43 GOVERNING LAW:
This Contract shall be governed by the laws of the state of Arizona. Venue for any actions or
lawsuits involving this Contract will be in Maricopa County Superior Court or in the United States
District Court for the District of Arizona, sitting in Phoenix, Arizona
6.44 ORDER OF PRECEDENCE:
In the event of a conflict in the provisions of this Contract and Contractor’s license agreement, if
applicable, the terms of this Contract shall prevail.

SERIAL 171125-RFP
6.45 INCORPORATION OF DOCUMENTS:
The following are to be attached to and made part of this Contract:
6.45.1 Exhibit A, Pricing;
6.45.2 Exhibit B, Scope of Work;
6.45.3 Exhibit C, Software Maintenance and Support Agreement;
6.45.4 Exhibit D, Office of Procurement Services Contractor Travel and Per Diem Policy;
6.45.5 Exhibit E, Requirements
6.45.6 Exhibit F, Project Change Request Form
6.45.7 Exhibit G, Deliverable Acceptance Form
NOTICES:
All notices given pursuant to the terms of this Contract shall be addressed to:
For County:
Maricopa County
Office of Procurement Services
ATTN: Contract Administration
320 West Lincoln Street
Phoenix, Arizona 85003-2494
For Contractor:
UNICON International
ATTN: Chris Anderson
241 Outerbelt Street
Columbus, OH 43213


SERIAL 171125-RFP
EXHIBIT A
PRICING
SERIAL 171125-RFP
CONTRACTOR'S NAME: UNICON International
COUNTY VENDOR NUMBER :
ADDRESS: 241 Outerbelt Street
Columbus, OH 43213
P.O. ADDRESS:
TELEPHONE NUMBER: (614) 861-7070
FACSIMILE NUMBER: (614) 861-7096
WEB SITE: www.unicon-intl.com
CONTACT (REPRESENTATIVE): Chris Anderson
REPRESENTATIVE'S E-MAIL ADDRESS: jcanderson@unicon-intl.com
ANY PAYMENTS ARE BASED ON ACCEPTANCE BY THE COUNTY.
1. TOTAL NOT TO EXCEED FOR INITIAL FIVE (5) YEAR TERM : $2,717,460.00
1.1 PHASE I- DISCOVERY, ENVIRONMENTS AND BASIC FUNCTIONALITY:
Discovery:
Scoping and High-Level Requirements Document Completed and Approved,
including Development of Implementation Timeline acceptable
By and agreed to by County $ 189,067.00
Software Architecture and Design Document Completed and Approved $ 115,733.00
Implementation of Basic Functionality:
Completion and acceptance of all public records requirements
(Exhibit E, Sections 3.1.1 through 3.1.1.5, and Section 3.1.1.7) $ 20,000.00
Implementation of Shared CROMERR Services (Exhibit E, Section 3.1.2) $ 20,000.00
Implementation of EPA Data Exchanges (Exhibit E, Sections 3.15 through 3.1.5.6) $ 20,000.00
Successful testing and acceptance of internal data integration functionality
(Exhibit E, Section 3.14) $ 20,000.00
Completion and acceptance of online customer interaction requirements
(Exhibit E, Sections 3.1.3 through 3.1.3.5) $ 20,000.00
1.2 PHASE II – IMPLEMENTATION – Release 1: $ 230,580.00
Inclusive of Emissions Inventory System and all other Phase 2 items noted in Requirements (Exhibit E).
1.3 PHASE III – IMPLEMENTATION – Release 2: $ 89,760.00
Inclusive of Permitted Sources Common Requirements and all other Phase 3 items noted in Requirements
(Exhibit E).
1.4 PHASE IV – IMPLEMENTATION – Release 3: $ 348,480.00
Inclusive of Fess and Payments and all other Phase 4 items noted in Requirements (Exhibit E).

SERIAL 171125-RFP
1.5 PHASE V – IMPLEMENTATION – Release 4: $ 283,360.00
Inclusive of Compliance, Enforcement, Performance Test and all other Phase 5 items noted in
Requirements (Exhibit E).
1.6 PHASE VI – IMPLEMENTATION – Release 5: $ 326,600.00
Inclusive of GIS Integration, Dust Control and all other Phase 6 items noted in Requirements (Exhibit E).
1.7 PHASE VII – IMPLEMENTATION – Release 6: $ 358,280.00
Inclusive of Complaints, Unpermitted Sources and all other Phase 7 items noted in Requirements (Exhibit
E).
1.8 PHASE VIII – IMPLEMENTATION – Release 7: $ 413,600.00
Inclusive of User Training, Documentation and all other Phase 8 items noted in Requirements (Exhibit E).
1.9 ON-GOING DEVELOPMENT & SUPPORT:
1.9.1 YEAR 1 $ 50,000.00*
1.9.2 YEAR 2 $ 50,000.00
1.9.3 YEAR 3 $ 50,000.00
1.9.4 YEAR 4 $ 50,000.00
1.9.5 YEAR 5 $ 50,000.00
1.10 TRAVEL ALLOWANCE (Per Exhibit D): $ 12,000.00
*YEAR 1: Payment shall be prorated in accordance with the number of months remaining during the year of
completion and acceptance of Phase VIII- Release 7.

SERIAL 171125-RFP
EXHIBIT B
SCOPE OF WORK
Introduction to Statement of Work (SOW):
This document contains the overall EMS (Environmental Management System) approach and Statement of Work
(SOW) for the planning, design, data migration, development, testing, training, and Go-Live project activities.
Software Description:
The software is a comprehensive system to perform air quality permitting, compliance, emissions inventory, and
related and ancillary functions, to improve customer experience, advance productivity, increase automation of tasks,
and enhance MCAQD’s ability to communicate electronically with customers, the U.S. Environmental Protection
Agency, and other entities. It replaces the legacy EMS system and has capabilities far in advance of those of EMS. It
builds and expands upon the IMPACT system currently in use by the State of Wyoming.
Project Management
The Contractor shall manage this project through the methods described below and by closely monitoring the
progress of the members of the Contractor’s team through daily stand-up meetings. Meetings between the
Contractor and the County shall include but not limited to:
Project Kick-Off Meeting: This meeting introduces the team members, and establishes their roles and
expected interactions with other team members.
Weekly Project Status Meetings: This is the primary project management vehicle, where relevant issues are
raised, prioritized, and documented. The Contractor Project Manager shall work with the County Project
Manager to establish the agenda. The Contractor and County Project Managers shall attend each of these
meetings, either via conference call or in-person. Both project managers must ensure that the appropriate
personnel attend the meeting or provide updates before the meeting.
Frequent ongoing informal communications: Includes items such as phone calls, informal meetings and
emails between the Contractor team and the designated County contacts. The Contractor shall provide the
County with Project Management Tools to monitor the progress of the timelines and the fulfillment of the
deliverables.
Project Timeline: This is a high-level timeline showing Software releases and key project milestones. The
Contractor’s project manager shall ensure that the timeline is accurate and represents a realistic plan.
Project Issues List: This list tracks and resolves real or potential issues before they affect the project. Each
issue shall contain an owner and a priority.
Scoping and High Level Requirements Document: The Contractor shall write this document and formally
review it with the County. This document must then serve as the description for the capabilities to be
delivered.
Agile methodology artifacts: This shall include the Product Backlog and the team’s electronic project task
board, including tasks for the current and completed Sprints.
Project Communication
The Contractor shall engage in frequent and open communication with the County regarding the status of the
project. To facilitate this communication, the Contractor and the County shall establish formal communication
mechanisms as follows:
Weekly project status meetings: The project management team shall establish a standing agenda for the
project status meeting that shall include a review of The Project’s Issues List (described above in section
(1.1) at a minimum. Both the Contractor’s project manager and the County’s project manager shall be
required attendees. The project management team may optionally invite other team members to attend.
Monthly project status reports: The Contractor shall write a project status report once per month and
provide it to The County’s project manager for review and approval. The status report shall contain (at a

SERIAL 171125-RFP
minimum) a list of notable accomplishments since the last report, a list of goals for the coming quarter, and
a current copy of The Project’s Issues List. Once The County has confirmed that the status report is
accurate and complete, The Contractor shall distribute the quarterly project status report to all stakeholders.
In addition to the formal mechanisms, the Contractor’s project team shall engage in frequent informal
communication with the County, including timely and professional interactions via email messages, telephone calls,
and text messages.
Executive Steering Committee
For the duration of the project prior to the ongoing support phase, the Contractor shall participate in the
predetermined monthly Executive Steering Committee meetings at the Department’s discretion. The Maricopa
County project manager shall notify the Contractor at least one (1) week prior if a meeting will take place on-site,
on-line or if the meeting will be cancelled for the month. Members will consist of executive sponsors and assigned
project owners and project personnel. Agenda items will include a project update, review of key issues and risks, go-
live approval and status and other relevant project topics.
Creation of Development and Testing Environments
The contractor shall utilize multiple environments to support testing and execute protocols to ensure the solution
operates according to specified configurations, both prior to initial deployment and prior to any upgrades,
enhancements, modifications, or changes to configurations.
Software Versions
The software system will be defined, developed and implemented according to the requirements and version listing
as noted in Exhibit E. The Contractor shall target a release of the software that aligns with the version listing
starting upon the approval of the Scoping and High-Level Requirements document. Note that the number of releases
depends on the scope of the project. The following outline of activity will be followed for each version of the
software:
Discovery
Contractor shall review all functional requirements and corresponding software functionality with County.
Contractor shall provide County with a Functional Gap Report that indicates any deltas between County
requirements and Contractor capabilities as well as the mitigation recommendation. The parties shall collaborate on
any revisions to the requirements document.
Scoping and High-Level Requirements Document approved – The Contractor shall write this document as
soon as is practicable after the kickoff meeting and have it reviewed and approved by The County.
Software architecture and design document – The Contractor shall write this document as soon as
practicable after the Scoping and High-Level Requirements document has been approved. The Contractor
shall have it reviewed and approved by The County.
Implementation Plan and Timeline
The Contractor will prepare an implementation plan and timeline. This deliverable will require reports that shall be
created as part of this SOW, with a defined set to be available at the Go-Live Date. This work may be accomplished
as part of the project tasking.
Data Conversion
The Contract will manage a series of data conversion tasks including:
Data profiling: With the County, The Contractor will review the source of the data that needs to be moved
to the target Software. The Contractor will develop a profile of the data, which will estimate the cleanliness
of the data, such as invalid data or missing data that is required in the target Software.
Cleansing data: The County will review the findings of the data profiling effort and update the legacy data
source, where it is feasible to determine the correct value. The Contractor assumes that The County corrects
the erroneous or missing data in the legacy source, and that it is not part of the migration procedure. To
prevent missing data in future legacy records, The County may need to adapt work instructions or
procedures to ensure that the data is available in new legacy source records.
Data Gap Analysis: Typically, it is not feasible to correct all erroneous data in the legacy data source. The
County and the Contractor shall work together to analyze the data quality gap and develop feasible
strategies to mitigate the impact so that the data conversion does not delay the overall project.

SERIAL 171125-RFP
Mapping data from sources to targets: The Contractor shall develop a data mapping from the source data
item to the target data items, while describing any transformations.
Extract, Transform and Load (ETL): The Contractor shall develop a step-by-step procedure to extract the
data from the legacy data source, transform the data to meet the structure of the target data, and load the
data into the target Software data store.
The County and the Contractor will review the migration results to determine if the migration was
successful.
• The Contract shall design the migration procedure to be executed once, at which time all legacy
source records shall be migrated. It is not an incremental or differential procedure. The
Contractor shall design the procedure so that it can be executed in a test environment before the
final migration.
• The County and The Contractor will determine a cutover date, where the migration procedure
will update the production data associated with The Software.
Interface Development
The Contractor will develop all interfaces per the requirements outlined in Exhibit E. The Contractor will also
develop the necessary interfaces from the Software to the US EPA. The list of Interfaces to be developed shall be
based on the final scope of the project as determined by The County. The list may include interfaces such as the
Emissions Inventory System (EIS), the Integrated Compliance Information System for Air (ICIS-Air), and the
Facility Registry System (FRS). For each interface, the contractor shall develop an interface between The Software
and the appropriate EPA endpoint – such as the Central Data Exchange (CDX). The Contractor shall develop the
interface to meet the interface specifications established by the US EPA. The Contractor shall develop the interface
to exchange the data in a reasonable, efficient manner using standard industry techniques. The Contractor shall
demonstrate the successful exchange of data across each interface to The County using test scenarios consisting of
realistic test data.
Testing
Testing is conducted during each release of the software. County is responsible for Functional Testing, User
Acceptance Testing and Final User Acceptance Testing, with guidance from the Contractor.
Testing includes:
- Load Testing
- User Acceptance Testing
- Final User Acceptance Testing
- Security Testing
The purpose of testing is to verify that all components of the System are functioning properly and ready for use in
the production environment, and for the conduct of normal business as the System of record. County reserves the
right to revise the Testing Plans, provided that reasonable notice is given to the Contractor. County maintains sole
authority to certify the successful completion of any and all tests performed by the Contractor on the System.
Contractor shall provide a comprehensive system test plan, the test scripts shall be developed in conjunction with
MCAQD staff according to processes and requirements.
The Contractor shall conduct adequate testing of the Software to ensure a high-quality product. The Contractor shall
perform the following steps as part of its software development process:
1. Each member of the Contractor’s development team shall conduct unit testing of his/her coding changes
within the Contractor’s unit test environment. The developer shall execute these unit tests within the
context of a fully compiled and operational system (The Software) using realistic user scenarios and test
data.
2. After the coding change has successfully passed the unit testing phase, the Contractor shall conduct
integration testing for the change within the Contractor’s integration testing environment, using realistic
user scenarios and test data. Any significant defects or anomalies will cause The Software change to be
rejected.

SERIAL 171125-RFP
3. Prior to final delivery of a release of The Software, the Contractor shall conduct system testing of the release
in The Contractor’s system testing environment. The Contractor shall ensure that all required changes are
contained in the release and that the system is meeting all its requirements.
4. The Contractor shall assemble all coding changes that have successfully passed the system testing phase into
deliverable packages (releases). The Contractor shall then ensure that the release is properly loaded into
The Project’s staging environment for the County’s User Acceptance Testing (UAT). The Contractor shall
support The County in its UAT by promptly responding to requests for assistance in conducting the UAT.
Each release of the software will be subject to security screening and testing as outlined and executed by the County.
Test failures identified will be promptly remedied by the Contractor at no additional cost to the County.
Any defects or anomalies that cause a failure in security screening and testing shall be corrected and The Software
resubmitted within sixty (60) calendar days of the initial rejection by The County. Rejection conditions lasting more
than sixty (60) days may trigger Termination actions as outlined in Section 6.20 of the Contract.
Training:
Contractor shall provide a comprehensive training plan and associated materials. The Contractor shall provide web-
based, online training materials for the software. The links to the training web pages will be accessible from The
Software.
The County will be responsible for all logistical support for these training classes, including identifying participants,
scheduling, providing training room(s), computers, training equipment, and handouts.
The scope of the Contractor’s training is the functionality of the Software. If the County wishes to integrate non-IT
policies and procedures into The Software training material, the County will need to provide the additional content
and incorporate it into the training. However, the Contractor can discuss approaches and provide technical advice.
The Contractor shall provide web-based training materials that can adapt to a variety of delivery models:
Web-based delivery model - The Software contain a hyperlink to access the web-based training materials,
so that the user can navigate to the training materials from The Software at the user’s convenience.
Train-the-Trainer delivery model –The Contractor would lead on-site, instructor-led training with hands-on
exercises for County staff. In turn, these County staff members will train other staff as well as industry
users, using the Contractor provided training materials
The County staff will conduct the training of industry users and consultants, as policy and procedure questions often
arise during their training. To support the initial Software rollout, The Contractor shall be available (either in person
or virtually) for up to two industry/consultant training sessions to provide technical support and consultation.
The Contractor shall keep the training up-to-date with new releases. Release-specific training shall be provided for
County project team members to support Release-specific testing, and will be delivered as solution demonstrations
at the start of the Release Testing Period. The Release-specific training format is a walk-through of Release-specific
test scripts in the test environment.
Go-Live:
Once testing is completed and the version of the software has been accepted by the County, the Contractor will work
with the County to outline specific Go-Live steps to insure County readiness and support. The Contractor will
provide a Go-Live checklist that will provide overall guidance to the Go-Live process.
Post Go-Live Support:
For a period of 2 weeks following the Go-Live, the Contractor will provide support as required to insure the
stability, operability and functionality of the new software release. This support will be in addition to the ongoing
support outlined in the Software Maintenance and Support Agreement.
Final County Acceptance: (Go Live + 30 Calendar Days):
Within 30 days past the Go-Live, the County will either Accept or Reject the new software release and will notify
Contractor accordingly. If the software release is rejected, the County will outline the areas of concern and the

SERIAL 171125-RFP
Contractor will provide appropriate response and action plans. Rejection conditions lasting more than 60 days may
trigger Termination actions as outlined in Section 6.20 of the Contract.
Documentation and Architecture:
The Contractor shall provide a comprehensive set of system documentation to include but not limited to the
following.
• Database schema and architecture
• Initial System Installation Instructions
• Software Architecture
• Software configurations
• Code structures
The Contractor will host a number of meetings with County technical and software personnel to review the system
documentation and conduct knowledge transfer to County persons.
Acceptance:
Deliverable Acceptance Criteria:
The County and The Contractor will complete the deliverable acceptance form (Exhibit G) as provided in the
respective SOW for each of the deliverables that is defined in the SOW under this Agreement.
Acceptance criteria for deliverables will be defined in SMART terms:
• Specific
• Measurable
• Agreed between Organization and Provider at definition
• Realistic in the sense that the deliverable can be realized and the criteria can be measured
• Timely in the sense that deliverables can be realized in the provided or available time frame
Deliverable Readiness Notification:
The Contractor will forward the respective deliverable acceptance form with the specified deliverable to The County
for review.
Review Period:
Unless specified differently in the respective SOW, The County will have ten (10) business days to review and
accept the associated deliverable or provide feedback on nonconformance required for acceptance. The County may
extend the review period for up to an additional five (5) business days. The County will notify The Contractor
within five (5) days of submittal of the deliverable(s) that the review period is being extended.
Acceptance/Rejection Notification:
Electronic transmission and electronic signatures are acceptable for all notifications that must be delivered in
writing.
• If The County is satisfied that the deliverable conforms to the acceptance criteria as defined, The County
will notify The Contractor in writing of its acceptance.
• If The County determines that the deliverable does not conform to the relevant acceptance criteria, The
County will notify The Contractor in writing, describing in detail why such deliverable does not conform.
• If at the end of the Review Period, The County has not filed a written notice stating acceptance or
rejection, the deliverable shall be deemed accepted. Similarly, if the deliverable has been put to
productive use by The County for more than 30 days, the deliverable shall be deemed accepted (unless an
alternative time period is stated in the respective SOW).
Rework Period:
Within ten (10) business days (or such other time period as may be agreed upon in writing by the parties) after
receipt of the nonconformance of a deliverable, The Contractor will, at no additional cost to The County, cause such
deliverable to conform with the acceptance criteria, and acceptance review will then be re-performed in accordance
with the procedure set out above
Reworked Deliverables Not Accepted:
If The Contractor fails to cause such deliverable to conform to the acceptance criteria within the Rework Period, The
County may:
• Extend the Rework Period to allow The Contractor additional time to correct the deliverable nonconformity
and re-perform the acceptance review in accordance with the procedure set out above.

SERIAL 171125-RFP
• Accept the deliverable "as is" and agree with The Contractor on a reduction in the fees to reflect the reduced
functionality and/or performance.
• Instruct The Contractor to refund amounts paid by The County for the nonconforming deliverable.
• Exercise any or all rights under the contract.
Roles and Responsibilities:
Maricopa County
The County shall provide a project manager who shall serve as the Contractor’s primary point of contact for The
Project. The County shall allocate sufficient time among the Air Quality Division’s Subject Matter Experts to
answer pertinent questions and resolve project issues in a timely manner. The County shall also provide the contact
information – including phone number and email address – for an escalation contact (presumably, but not
necessarily The Project’s sponsor). The Contractor may escalate project issues to The County’s escalation contact if
The Contractor believes that The County’s named project manager is not adequately resolving any project issue.
Key Position/Project Position Key Responsibilities
Executive Sponsor Overall project sponsor and escalation contact
IS Project Manager/Project Manager Project Management
Business Systems Analyst Support technical and business needs
Subject Matter Experts Provide subject matter expertise
Database Support Provide database support
Technical Platform Support Provide technical support for computing platform
Contractor
Contractor shall provide a project team composed of a project manager and a group of implementation professionals.
The named project manager shall be the primary point of contact for The County for The Project and shall lead the
other Contractor team members. The Contractor shall provide the contact information – including phone number and
email address – for an escalation contact person. The County will retain the option to escalate project issues to The
Contractor’s escalation person if The County believes that The Contractor’s project manager is not adequately
resolving any project issue.
Key Position/Project Position Key Responsibilities
Project Manager Overall responsibility for the success of the project. Provides
project management for all project tasks.
Primary Business Analyst Eliciting functional requirements from County staff. Provides
insights into potential process improvements.
Lead Developer Creates and maintains the architecture and high-level design of
the solution system and interfaces. Oversees system testing.
Oversees the design and structure of the solution system’s
Database Developer relational database system. Oversees data conversion activities
notes in SOW.
Executive to be contacted in the event of unsatisfactory
Escalation Contact performance of the project manager or other project related issues
needing executive attention.
Additional Roles and Responsibilities
P= Primary, S = Support
Item/Role Contractor County
Project Management P S
Project Communication P S
Executive Steering Committee P S
Technical Environment S P
Software Versions
Discovery P S
Development P S

SERIAL 171125-RFP
Data Conversion
Profiling P S
Cleansing S P
Data Gap Analysis P S
Mapping Data P S
Extract, Transform and Load P S
Interface Development P S
Testing
Software Testing P S
Functional Testing S P
User Acceptance Testing S P
Final Acceptance Testing S P
Security Testing S P
Training
Training Plan and Materials P S
Training Facilities P
Training Materials Updates P
Go-Live Plan P S
Post Go-Live Support P S
Final Acceptance P
Documentation and Architecture P
Change Control P S
Project Marketing P
Change Management Processes
Change Control Process:
The Contractor and The County shall establish a project Change Request Review process early in the
project to manage potential changes to the project’s scope. The process shall include artifacts including a
Project Change Request (PCR) form (See Exhibit F) and a PCR log. The form shall include information
such as the date of the request, name of the requestor, description of the requested change, and an
explanation of the expected benefits from the change.
The project team, as part of normal project operation, will meet periodically to review PCRs, ensuring that
each has an assigned PCR ID. The team shall ensure that the PCR contains sufficient descriptive detail for
the Contractor to estimate the cost; else, the team shall return it to the requestor for additional clarification.
The Contractor and the County shall utilize the Executive Steering Committee to determine a disposition
for the PCR, which may include Rejected, Accepted, or Deferred. If the ESC decides to accept the PCR,
then the Contractor and the County shall make any required contractual changes, which shall include a
price, payment terms, and target delivery date for the change.
Issue Resolution and Escalation Process:
The Contractor shall maintain a project Issues List that shall be a repository of all potential, project-
affecting issues. Each Issue shall contain (at a minimum) an Issue number, Issue Description, Date Created,
Owner, Priority, and Status.
The List shall consist of two lists – an Active and an Inactive List. As project team members identify
issues, they will log entries in the Active List. The project management team – consisting of the County’s
project manager and the Contractor’s project manager at a minimum – shall review the list periodically
(presumably weekly) and review all items in the Active List. The project management team shall be
responsible for ensuring that each item in the list has an adequate description. The team shall ensure that it
assigns an owner and a priority to each item and shall update the Status field to reflect progress made in
resolving the issue. Once the team has addressed the Issue, it will update the Status field with the final
resolution and move it from the Active List to the Inactive List.

SERIAL 171125-RFP
It is expected that the Contractor and the County will work diligently and effectively to review these items
and resolve them in a timely, professional manner.
Program Marketing:
The County is responsible for developing and implementing a plan for introduction of the new software to
internal and external stakeholders, in accordance with Phase I, Section 4 (above).

SERIAL 171125-RFP
EXHIBIT C
SOFTWARE MAINTENANCE AND SUPPORT AGREEMENT
The purpose of this agreement is to document the service delivery of Contractor to County for a web-based software
application (“Application”). Contractor shall deliver the services set forth in this document. The County shall pay
for the services covered by this Agreement in accordance with billing and payment terms that have been agreed
upon by Contractor and County.
Maintenance Services Provided – Web-Based software application
Contractor shall provide the following services to County:
Service Description Examples
User Support Receive, document, and prioritize issue • Provide help desk support
tickets and assist County staff in the use • Answer queries about Application.
of Application. • Receive and document bug reports.
• Collect and document requests for
changes.
• Share status of requests.
Problem Bring Application back to its original • Fix bugs.
Correction functionality before the problem arose. • Retrieve functionality after abnormal
This may include a permanent fix or a program terminations.
temporary work around until a • Complete root cause analysis.
permanent fix is found.
Application Modify the functionality of • Apply new functionality.
Enhancement Application. • Enhance run-time efficiency.
• Modify applications based on new releases
of hardware or software.
REPORTING:
The County, in consultation with the Contractor, shall develop a software application performance scorecard to
provide monthly reporting of application and database performance and availability, service level performance
metrics, and issue summaries.
The following processes shall be used in order to manage this agreement:
Weekly Status Report:
Contractor shall provide County with a weekly status report that gives an overall summary of the following:
• Project health
• On-going activities
• Completed tasks
• Upcoming milestones and releases
• Bug fixes
• Risk identification and mitigation plan
• Action items across different application areas
Monthly Review Meeting:
Metrics will be tracked by Contractor, summarized in a dashboard format, and discussed in a monthly meeting. This
activity includes the following:

SERIAL 171125-RFP
• Tracking unresolved issues from maintenance projects which impact the Availability Service Level
Agreement (SLA)
• Updating maintenance project progress and resolving critical issues
• Capturing agreements and disagreements and items needing escalation
Quarterly Review Meeting:
A quarterly review meeting shall include the following:
• This agreement will be reviewed by Contractor and County and an amendment addendum will be created if
required
• Review process will be through teleconference or face-to-face meeting session which will be booked in
advance
• Review document prepared by Contractor will include overall project status, issues list, metrics reporting,
supporting reasons for metrics deviation, and items that need adjustment within SLA (e.g. scope, metrics,
etc.)
• Agreement changes will be tracked by version number and date
Reporting Service Levels
Type Measurement
Weekly Status Report Delivered at not less than seven calendar day intervals
Monthly Status Report Delivered at monthly intervals and not less than two business days
before scheduled review meeting
Quarterly Status Report Delivered at quarterly intervals and not less than five business
days before scheduled review meeting
User Support and Problem Correction:
Contractor shall use the following procedures to respond to problems that are received by the help desk. A problem
is defined as an unplanned system event which adversely affects application processing or application deliverables.
Support Hours:
Contractor shall provide help desk support for the Application on a 24 hours a day, 7 days per week basis.
Contractor shall provide a telephone number and email address to the County for support purposes.
Prioritization Approach:
Service requests for problems received by the help desk will be given a Severity Code from 1 – 4 based on the
importance of the problem to the primary business of County as a whole, as well as the availability of workarounds.
The Severity Code shall be the basis for scheduling work on the backlog and assigning resources to the request.
Critical, important, and supportive application functions are defined in the section below on Application Function
Types.

SERIAL 171125-RFP
Severity Code Definition
1 A problem has made a critical application function unusable or unavailable and no
workaround exists.
2 A problem has made a critical application function unusable or unavailable but a
workaround exists.
or
A problem has made an important application function unusable or unavailable and no
workaround exists.
3 A problem has diminished critical or important application functionality or performance
but the functionality still performs as specified in the user documentation.
4 A problem has diminished supportive application functionality or performance.
Application Function Types
Function Type Description Example
Critical Application function that is critical to County’s business. IMPACT’s Emissions
Extended failure will interfere with County’s profit or Inventory or Permit
reputation Application functions
Important Application function that is important to business IMPACT’s
productivity, but does not affect County’s profit or reputation Correspondence
tracking functions
Supportive Application function that support County’s business process Ability to sort rows in a
but is not essential table by clicking on a
column header
Response and Resolution Times:
Severity codes are used in order to determine appropriate response and resolution times. Response and resolution
times are measured from when the incident is opened by the help desk. If the problem is not resolved within the
defined timeframe, continuous effort will be applied until the problem is resolved.
Severity Initial Response Resolution
Code
1 30 minutes 24 hours
2 2 hours 72 hours
3 4 business hours 5 business days
4 1 business day Next patch/point release
• Initial Response is when a ticket is opened and acknowledged by help desk staff.

SERIAL 171125-RFP
• Resolution is the point at which the problem is resolved and the application function is returned to a usable
and available state.
Application Availability:
Availability is generally defined as the ability of an end user to access and execute any of the included application
functions from a functioning County device and active network connection. For an application to be available, all of
its supporting systems must be operational.
Application Availability Measurement – Web Application:
The measurement period for the availability SLA is a calendar month. For each month that the Application does not
meet its availability SLA, Contractor shall apply a credit for the penalty amount to its invoice for that month.
The availability measurement for the Application shall be the percentage of time during the calendar month when
the Application is deemed as “available”. The Application is unavailable when it is not meeting its response time
requirement. Note that the Application may be failing to meets its response time requirement because it is down, or
because it is impaired due to an internal software fault. Regardless of the reason, it shall be considered “unavailable”
if it is not meeting its response time requirement.
Application Response Time Requirement:
The Application is required to respond to County HTTP or HTTPS requests with a valid response within its
response time requirement. The requirement has two parts:
1. The Application must transmit the initial response within 10 seconds of receiving the request. Assuming
optimal operating conditions, the user will see the page beginning to render on their browser.
2. Within 10 seconds of transmitting the initial response, the Application must complete the transmission of its
response. Under optimal conditions, the user will see the completely rendered web page on their browser.
This part of the requirement applies to standard web application pages only. Longer running operations –
such as file downloads and batch operations - are not subject to this part of the requirement.
In this context, a valid response is one that provides reasonable information according to the system’s functional
business rules. A static “System Down” reply shall not be considered a valid response.
The response time requirement shall be applied to the Application’s software only. Other factors that contribute to
the user’s perceived system response time, such as the performance of intermediate networking components or the
County’s device, shall be excluded when measuring the Application’s response time. CONTRACTOR shall be
prepared to make available the Application’s internal, timestamped system logs, which exclude these factors, to
document the Application’s response time performance.
The Application’s monthly availability measurement calculation shall include unscheduled down time only;
scheduled down time shall be excluded.
The Application’s monthly availability measurement calculation shall exclude any outages due to the unavailability
of the Application’s operating environment, including server hardware, networking components, operating system,
or other base software unless the Application directly caused the outage.

SERIAL 171125-RFP
Application Availability Service Levels:
Monthly Application Availability Credit amount as % of
Measurement monthly support fee
Greater than or equal to 99.99% 0%
Between 99.0% and 99.98% 10%
Less than 99.0% 30%
Application Enhancement:
Application enhancement projects involve functional enhancements made to a properly working application to
accommodate new or changed user requirements. Examples include increasing an application’s performance,
enhancing a user interface, or optimizing code.
Application enhancements can be requested by County or proposed by Contractor. The County will prioritize the
order in which enhancements are performed.
Contractor shall manage application enhancement projects in a structured, organized, and cost effective manner.
Additionally, Contractor shall apply appropriate process and practices in order to deliver high quality software to the
County containing as few defects as is practical.

SERIAL 171125-RFP
EXHIBIT D
OFFICE OF PROCUREMENT SERVICES CONTRACTOR TRAVEL AND PER DIEM POLICY
1.0 All contract-related travel plans and arrangements shall be prior-approved by the County Contract
Administrator.
2.0 Lodging, per diem and incidental expenses incurred in performance of Maricopa County/Special District
(County) contracts shall be reimbursed based on current U.S. General Services Administration (GSA)
domestic per diem rates for Phoenix, Arizona. Contractors must access the following internet site to
determine rates (no exceptions): (www.gsa.gov).
2.1 Additional incidental expenses (i.e., telephone, fax, internet and copying charges) shall not be
reimbursed. They should be included in the contractor’s hourly rate as an overhead charge.
2.2 The County will not (under no circumstances) reimburse for Contractor guest lodging, per diem or
incidentals.
3.0 Commercial air travel shall be reimbursed as follows:
3.1 Coach airfare will be reimbursed by the County. Business class airfare may be allowed only when
preapproved in writing by the County Contract Administrator as a result of the business need of
the County when there is no lower fare available.
3.2 The lowest direct flight airfare rate from the Contractors assigned duty post (pre-defined at the
time of contract signing) will be reimbursed. Under no circumstances will the County reimburse
for airfares related to transportation to or from an alternate site.
3.3 The County will not (under no circumstances) reimburse for Contractor guest commercial air
travel.
4.0 Rental vehicles may only be used if such use would result in an overall reduction in the total cost of the trip,
not for the personal convenience of the traveler. Multiple vehicles for the same set of travelers for the same
travel period will not be permitted without prior written approval by the County Contract Administrator.
4.1 Purchase of comprehensive and collision liability insurance shall be at the expense of the
contractor. The County will not reimburse contractor if the contractor chooses to purchase this
coverage.
4.2 Rental vehicles are restricted to sub-compact, compact or mid-size sedans unless a larger vehicle
is necessary for cost efficiency due to the number of travelers. (NOTE: contractors shall obtain
pre-approval in writing from the County Contract Administrator prior to rental of a larger vehicle.)
4.3 County will reimburse for parking expenses if free, public parking is not available within a
reasonable distance of the place of County business. All opportunities must be exhausted prior to
securing parking that incurs costs for the County. Opportunities to be reviewed are the DASH;
shuttles, etc. that can transport the contractor to and from County buildings with minimal costs.
4.4 County will reimburse for the lowest rate, long-term uncovered (e.g. covered or enclosed parking
will not be reimbursed) airport parking only if it is less expensive than shuttle service to and from
the airport.
4.5 The County will not (under no circumstances) reimburse the Contractor for guest vehicle rental(s)
or other any transportation costs.
5.0 Contractor is responsible for all costs not directly related to the travel except those that have been pre-
approved by the County Contract Administrator. These costs include (but not limited to) the following: in-
room movies, valet service, valet parking, laundry service, costs associated with storing luggage at a hotel,

SERIAL 171125-RFP
fuel costs associated with non-County activities, tips that exceed the per diem allowance, health club fees,
and entertainment costs. Claims for unauthorized travel expenses will not be honored and are not
reimbursable.
6.0 Travel and per diem expenses shall be capped at 15% of project price unless otherwise specified in individual
contracts.
7.0 Contractor shall provide, (upon request) with their invoice(s), copies of receipts supporting travel and per
diem expenses, and if applicable with a copy of the written consent issued by the Contract Administrator.
No travel and per diem expenses shall be paid by County without copies of the written consent as described
in this policy and copies of all receipts.

SERIAL 171125-RFP
EXHIBIT E
REQUIREMENTS
In the table of requirements, Section Numbers and Section Titles refer to section numbers and section titles in Section 3.0 SCOPE OF WORK, Maricopa County
RFP 171125 (attached as Exhibit I). These Requirements are presented in the order of section numbers in RFP 171125.
Functional requirements are as specified in RFP 171125-RFP. Level of Effort is based on the Unicon’s response to RFP 171125. As part of Implementation
Phase I- (Discovery, Environments and Basic Functionality; Discovery; Scoping and High-Level Requirements—See Exhibit A), the Contractor shall work with
the County to develop an implementation timeline. Upon completion of the implementation timeline and acceptance of it by the County, the “Implementation
Timeline” shall be included in this Contract.
Phase specifies which phase (as described in Exhibits A and B) is expected to contain these deliverables. Any entries with an assigned release number are
deliverables within the scope of this contract. Any entries in the requirements table marked ‘N/A’ in the Phase column do not have associated deliverables. Any
entries marked ‘TBD’ are subject to further discussion and mutual agreement between the County and the Contractor. Any entries marked ‘X’ are beyond the
scope of these requirements.
Cost refers to the quoted price for each deliverable.
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.1.1 Public Records Arizona public records law is strict and its
Requirements scope is expansive. Any software solution must 1 $ —
be capable of compliance with Arizona public
records law. (http://www.azleg.gov/arstitle/).
3.1.1.1 Definition of Arizona Revised Statutes § 41-1350 defines The design of IMPACT will provide support
'Record' ‘record’ as: “…all books, papers, maps, for "records" including complex records
photographs or other documentary materials, composed of both web form and file Included in the
regardless of physical form or characteristics, attachment data. quoted base
including prints or copies of such items price for items
produced or reproduced on film or electronic 3.1.1 (except
media pursuant to § 41-1348, made or received 1 3.1.1.6), 3.1.2,
by any governmental agency in pursuance of 3.1.3, 3.1.4,
law or in connection with the transaction of and 3.1.5
public business and preserved or appropriate $404,800.00
for preservation by the agency or its legitimate
successor as evidence of the organization,
functions, policies, decisions, procedures,

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
operations or other activities of the
government, or because of the informational
and historical value of data contained therein.”
3.1.1.2 Redaction of All data are public records except for those IMPACT has extensive support for confidential
Confidential data that have been granted an exemption as attachment files. Minor changes are needed to
Data trade secrets. In order for those data to receive support confidential data fields on web screens.
an exemption, the submitter must file a request
in writing specifying which data are asked to
be withheld from public records and justifying
that request. Data may be withheld from public
records if and only if MCAQD, upon review,
grants such requests. Functional areas in which
this process may be applied include permitting,
performance testing, inspections, and
emissions inventory reporting. Included in the
Any software solution must be able to tag (a) quoted base
those data fields that have been requested to be price for items
exempt from public records and (b) those data 1 3.1.1 (except
fields that have been granted a public records 3.1.1.6), 3.1.2,
exemption. If and when such exemptions are 3.1.3, 3.1.4,
granted, either two versions of the data must be and 3.1.5
recorded by the solution, or two methods of $404,800.00
access (with different security permissions)
must be available: one must be or access a
redacted version for public records requests,
and one must be or access an unredacted
(confidential) version for internal MCAQD use
only. Any documents generated by or stored in
the solution must likewise be potentially
available in two versions: a redacted version
for public records requests, and one must be or
access an unredacted (confidential) version for
internal MCAQD use only.
3.1.1.3 Public Records Any software solution must be able to generate IMPACT has extensive support for packaging Included in the
Request Copies copies of online submittals, such as permit online submittals into zip archive files which 1 quoted base
of Online applications and annual EI submittals, in can then be emailed in response to public price for items
Submittals response to public records requests in a format records requests. 3.1.1 (except

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
in which the public is reasonably likely to be 3.1.1.6), 3.1.2,
able to access it (e.g., MS Word or PDF). 3.1.3, 3.1.4,
and 3.1.5
$404,800.00
3.1.1.4 Records All data and reports (such as permit data and IMPACT currently does not destroy (remove)
Retention and annual EI reports) must be able to be assigned records. However, it does have the capability to
Destruction a destruction date. On that destruction date, all run scheduled (e.g.) jobs plus the ability to
Procedures data in those reports must be permanently and store and manage system configuration data.
completely purged from the database. Six UNICON will implement an enhancement to Included in the
months prior to the destruction date, an IMPACT that maintains the records retention quoted base
automated notification of upcoming records parameters and destroys the appropriate price for items
destruction must be provided to the MCAQD records accordingly. 1 3.1.1 (except
custodian of records, who must have the ability 3.1.1.6), 3.1.2,
to delay that destruction date for individual 3.1.3, 3.1.4,
records. An exportable report of destroyed and 3.1.5
records must be available. $404,800.00
It should be possible to assign record
destruction dates automatically by applying
stored records retention schedules.
3.1.1.5 Legal Holds It must be possible to preserve an uneditable By default IMPACT preserves uneditable
copy of any record in a secure manner in copies of all user submissions. UNICON will Included in the
response to a legal hold. Records subject to a extend this capability to include a toggle-like quoted base
legal hold may be ‘live’ records. Hence, it must capability and corresponding indicator that a price for items
be possible to preserve the uneditable version legal hold is in place. IMPACT records 3.1.1 (except
of a record while continuing to use and modify retention and destruction capabilities will be 1 3.1.1.6), 3.1.2,
an active version. implemented to honor the "legal hold" status 3.1.3, 3.1.4,
such that the system will not destroy any and 3.1.5
Records preserved in a legal hold may only be records that are in the held state. $404,800.00
released from that hold or destroyed by the
MCAQD custodian of records.
3.1.1.6 Electronic Reports and associated documents should be IMPACT has its own, embedded document
Document automatically stored in MCAQD’s OnBase management capabilities. UNICON's proposed
Management EDMS. It is preferable that users of the approach is to retain the solution's role as the
System (EDMS) proposed solution also be able to access "master" of the document and store a separate, 4 $61,600.00
Integration documents stored in OnBase through the "shadow" copy in OnBase.
proposed solution. MCAQD is currently using
OnBase version 16.

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.1.1.7 Record The proposed solution must maintain versioned IMPACT facility inventory subsystem
Versioning data for permits, emissions inventory reports maintains a complete historical record of
and other records so that uneditable versions of changes over time. Our permit application and
entire records are preserved whenever there are permitting records store all relevant Included in the
changes to those records. (A change log does information. Subsequent permitting operations quoted base
not suffice for compliance with CROMERR. require a new application and permit - thus price for items
See section 3.1.2.) Versioning is not just a preserving the history of prior permitting 1 3.1.1 (except
saved report or document: the data and actions. 3.1.1.6), 3.1.2,
metadata must be preserved in the database. 3.1.3, 3.1.4,
Users must have access to historic and current and 3.1.5
information on a given record, be able to $404,800.00
generate or reproduce reports, or respond to
database queries based on historical data from
any point in a record’s lifecycle.
3.1.2 CROMERR A number of MCAQD programs are operated IMPACT partially implements CROMERR
Compliance: under delegated authority from the EPA and services in all three high-level CROMERR
are subject to EPA requirements. Among those categories - Registration and Identity
requirements is the Cross-Media Electronic Management, Signature Ceremony, and Copy Included in the
Reporting Rule (CROMERR) of Record Management. UNICON will quoted base
[https://www.epa.gov/cromerr]. CROMERR integrate with the US EPA's Shared price for items
specifies the requirements for identity CROMERR services to provide a fully 1 3.1.1 (except
verification and management, and for compliant CROMERR solution. Please refer to 3.1.1.6), 3.1.2,
document and data security, in electronic Section 14 of the main proposal document for a 3.1.3, 3.1.4,
transactions for EPA and EPA-delegated more complete description of UNICON's plan and 3.1.5
programs. Any software solution must have a to achieve CROMERR certification. $404,800.00
CROMERR-certified portal for electronic
transactions and CROMERR-compliant data
and document management protocols.
3.1.3 Online Customers must be able to submit payments IMPACT currently implements all of these Included in the
Customer and emissions inventory data, permit capabilities except for online payments. quoted base
Interaction: applications, permit modifications, compliance UNICON will integrate with FIS (county price for items
records, and other applications and documents online payment system). 1 3.1.1 (except
securely online. Customers and the general 3.1.1.6), 3.1.2,
public should be able to search for submitted 3.1.3, 3.1.4,
data online. and 3.1.5
$404,800.00

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.1.3.1 CROMERR- For those programs requiring CROMERR IMPACT will implement CROMERR Included in the
Compliant compliance, all online submittals must be Compliance. Submittals will include but not be quoted base
Submittals CROMERR compliant. MCAQD must also be limited to documents submitted to MCAQD as price for items
able to send revised drafts of applications and part of a program that is regulated under Title 1 3.1.1 (except
other documents to its customers in a 40 CAA. 3.1.1.6), 3.1.2,
CROMERR-compliant manner. 3.1.3, 3.1.4,
and 3.1.5
$404,800.00
3.1.3.2 Non- It is preferable that there also be a non- IMPACT will support non-CROMERR Included in the
CROMERR CROMERR online submission environment submittals. Submittals will include but not be quoted base
Submittals for those programs that do not require limited to: Dust Control Permit applications price for items
CROMERR compliance, so that customers do and amendment forms; citizen complaints; 1 3.1.1 (except
not have to endure the CROMERR process. Subcontractor Registration applications and 3.1.1.6), 3.1.2,
amendment forms; Open Burning application 3.1.3, 3.1.4,
and amendment forms; Fireplace Exemption and 3.1.5
applications. $404,800.00
3.1.3.3 Email It should be possible to configure email IMPACT shall support email notifications.
Notifications notifications to customers to provide them with Included in the
updates about the status of their applications, quoted base
enforcement cases, inventories, etc., and to price for items
provide reminder notifications prior to the 1 3.1.1 (except
expiration of their permits or late payments. 3.1.1.6), 3.1.2,
Specify how such notifications are created and 3.1.3, 3.1.4,
managed. Specify who (MCAQD, vendor, or and 3.1.5
some combination thereof) would have the $404,800.00
authority to manage such notifications.
3.1.3.4 Customer Customers should be able to query the current IMPACT supports this. Applicants can view Included in the
Queries status of their applications. their submitted application and can view the quoted base
event log to determine the application's price for items
progress through the permitting process. 1 3.1.1 (except
3.1.1.6), 3.1.2,
3.1.3, 3.1.4,
and 3.1.5
$404,800.00
3.1.3.5 General Public The general public should have a portal UNICON shall collaborate with county in the Included in the
Access through which they can retrieve information design of the public facing website. Final quoted base
about permits, permit applications, emissions design and functionality shall be subject to 1 price for items
inventories, enforcement actions, etc. That further county review. 3.1.1 (except

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
portal must not make available any data 3.1.1.6), 3.1.2,
designated as confidential or as trade secrets 3.1.3, 3.1.4,
(see § 3.1.1.2, above). Wherever possible, the and 3.1.5
solution should be designed with future online $404,800.00
capabilities in mind, including Section 508
compliance (https://www.access-
board.gov/guidelines-and-
standards/communications-and-it/about-the-
section-508-standards).
3.14 Internal Data Permitting, performance testing, emissions IMPACT supports this. Internal data Included in the
Integration: inventory, compliance, inspections, and integration is a foundational component of quoted base
enforcement all rely on each other’s data. IMPACT's system design price for items
Source data (such as equipment lists, pollutant 1 3.1.1 (except
tables, permit conditions, processes, emissions 3.1.1.6), 3.1.2,
limits, facility locations, emissions inventories 3.1.3, 3.1.4,
and violation history) should be integrated and 3.1.5
among processes as much as possible. $404,800.00
3.15 EPA Data (N/A — Section heading only) Included in the
Exchanges: quoted base
price for items
1 3.1.1 (except
3.1.1.6), 3.1.2,
3.1.3, 3.1.4,
and 3.1.5
$404,800.00
3.1.5.1 EPA Exchange Any proposed software solution must have an UNICON will modify IMPACT to use EPA's
Node or EPA-approved means of interacting with the Virtual Exchange Service. Included in the
Exchange EPA Central Data Exchange (CDX) quoted base
Services [https://cdx.epa.gov/] and other Exchange price for items
Network (http://www.exchangenetwork.net/) 3.1.1 (except
products. Acceptable means of interaction are: 1 3.1.1.6), 3.1.2,
(1) an EPA-approved node that is internal to 3.1.3, 3.1.4,
the proposed software; (2) an EPA-approved and 3.1.5
Node 2 product, such as (but not limited to) $404,800.00
OpenNode 2; or (3) the EPA Virtual Exchange
Service (formerly known as the Virtual Node).
3.1.5.2 Emissions The solution must include the ability to UNICON will create a CERS compliant XML Included in the
Inventory generate emissions data in Consolidated formatted Emissions Inventory data exchange 1 quoted base

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
Exchanges Emissions Reporting Schema (CERS) package. price for items
[http://www.exchangenetwork.net/data- 3.1.1 (except
exchange/consolidated-emissions-reporting- 3.1.1.6), 3.1.2,
schema/] extensible markup language (XML) 3.1.3, 3.1.4,
format for submittal to EPA’s Emissions and 3.1.5
Inventory System (EIS) $404,800.00
[http://www.exchangenetwork.net/data-
exchange/emissions-inventory-system/] for a
given emissions inventory year and to submit
those data to the EIS. The solution must be
compatible with EIS codes and schema by
enforcing range requirements and validation of
codes.
3.1.5.3 Code Tables The solution should allow complete integration IMPACT integrates both SCC and FIRE tables
of all applicable EPA code tables, such as the including the ability to update individual table
Source Classification Code (SCC) tables and entries as well as bulk import support for the
Web Factor Information Retrieval System FIRE table. The FIRE import capability Included in the
(WebFIRE) [https://cfpub.epa.gov/webfire/] includes historical tracking of rows including quoted base
tables, along with a method to automate start/end dates. IMPACT's emissions inventory price for items
updates for each, so that code updates are calculation capabilities are designed to apply 3.1.1 (except
applied automatically. Dates of updates of the correct factor based on the date of the 1 3.1.1.6), 3.1.2,
codes (and versions of update tables, if emissions 3.1.3, 3.1.4,
available) must be recorded in the database and and 3.1.5
be reportable. The database must record the $404,800.00
codes actually used for each year, and updates
made in later years must not be applied
retrospectively to closed emissions inventories,
permits, or other records.
3.1.5.4 ICIS-Air There should be integration with the EPA’s IMPACT supports all of the necessary Included in the
Integrated Compliance Information System for underlying data. UNICON will implement the quoted base
Air (ICIS-Air) data extraction and integration with ICIS-Air price for items
[http://www.exchangenetwork.net/data- (through the Virtual Exchange Service) 1 3.1.1 (except
exchange/icis-air/] for reporting stationary 3.1.1.6), 3.1.2,
source compliance and permits, including 3.1.3, 3.1.4,
generation of reports in the approved ICIS-Air and 3.1.5
XML schema. $404,800.00

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.1.5.5 Facility Registry There should be complete integration with the IMPACT supports all of the necessary Included in the
System EPA Facility Registry System (FRS), so that underlying data for FRS interface. UNICON quoted base
facility information may be both downloaded intends to use the FacID 3.0 flow. price for items
from and uploaded to the FRS. The Facility 1 3.1.1 (except
Identification (FacID) 3.1.1.6), 3.1.2,
[http://www.exchangenetwork.net/data- 3.1.3, 3.1.4,
exchange/facility-identification/] flow 3.0 is and 3.1.5
preferred. $404,800.00
3.1.5.6 Other CDX This section (3.1.5) includes some of the most IMPACT's fundamental data models -
Exchanges important EPA data exchanges, but it is not an including the facility inventory, emissions
exhaustive list. Furthermore, it is expected that inventory, permits, inspections, and stack tests
the EPA Exchange Network will continue to - have been patterned after models used by the
integrate further. Proposals should include a EPA. To date, UNICON has been able to
description of the vendor’s plans to update and quickly create data extractions from IMPACT's
expand their data exchange capabilities as the database that meet the format and structure Future cost —
Exchange Network evolves. requirements imposed by the EPA. The data X not included in
transformations have typically been easy for this SOW
UNICON to understand and implement.
UNICON will evolve our EMS solution to
support other Exchange Network data
exchanges according to our client's demands.
All desired future exchanges will be
implemented as part of ongoing IMPACT
enhancements.
3.1.6 Other External In addition to EPA data exchanges, there are
Data several other external data exchanges that
Exchanges: should be addressed in all proposals. Items N/A N/A
3.1.6.1 and 3.1.6.2 are important needs for
current functionality. Item 3.1.6.3 details an
expectation for future functionality.
3.1.6.1 Maricopa The solution should provide functionality to be UNICON will interface IMPACT with
County Assessor able to look up parcels or addresses at the Maricopa County Assessor for ownership,
office of the Maricopa County Assessor parcel, and address information. 2 $17,600.00
(http://mcassessor.maricopa.gov/Assessor/Parc
elApplication/Default.aspx) and to retrieve
parcel, address and owner information.

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.1.6.2 Arizona MCAQD must be able to verify information UNICON will interface IMPACT with Arizona
Corporation about corporate entities with the Arizona Corporation Commission.
Commission Corporation Commission (ACC)
[http://ecorp.azcc.gov/]. The solution should
provide functionality to be able to look up 7 $17,600.00
corporate names at the ACC. (The ACC has an
API for lookups. See
https://apistore.az.gov/store/apis/info?name=ac
c&version=1.0.0&provider=admin%40az.gov
%40cc.az.gov&tenant=cc.az.gov )
3.1.6.3 ETL to Regional MCAQD is exploring data sharing with other IMPACT supports a SQL-query based
Data Sharing regional air quality regulatory bodies. This extraction of emissions inventory data into
sharing will require an extract-transform-load XML formatted data for external (EPA)
(ETL) process of a selection of permit and consumption. 2 $26,400.00
emissions inventory data to staging tables for
sharing. Proposals should address the
amenability of the solution to such an ETL
process.
3.1.6.4 Exchanged Data Provide a description of all means and methods IMPACT is based on industry standard
Encryption of encryption that are proposed to be used in technology and can support any of the
any exchanges of data. commonly used data transport encryption
technologies including SFTP, HTTPS,
SSL/TLS, or IPSec. The technology choice 2 $8,800.00
depends on the capabilities and preferences of
the receiver of the data. In the event that there
was a need to encrypt the "data at rest",
IMPACT would use Microsoft SQL Server's
Transparent Data Encryption (TDE).

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.1.7 Integrated GIS Maricopa County uses ArcGIS (server, online IMPACT does not have inherent GIS mapping
Functionality: and desktop) for its GIS services. MCAQD capabilities but does incorporate GIS
plans to expand its GIS capabilities. All functionality. IMPACT supports geographic
proposals should include a complete area definitions (defined through shapefiles)
description of the solution’s GIS capabilities, stored as a spatial datatype of type "geography"
specifying which functionalities are native to in our database. IMPACT uses these
the solution and which require an API to geographic areas to perform spatial queries to
ArcGIS. Any API to ArcGIS should be determine, for example, if a specified point
RESTful. Their supported development kits source facility is located within a specified
should include JavaScript. area. UNICON will implement an API with the 6 $26,400.00
County's ArcGIS platform.to enable the use of
The following are some needs that must be these data in the County's ArcGIS
incorporated into MCAQD records. (This list is environment.
illustrative and is not exhaustive.) Proposals
should specify, for each of these needs, if they
are available as inherent functionality in the
proposed solution, if they are configurable by
means of a JavaScript API to ArcGIS, or if
they are not available and must be created and
maintained independently in ArcGIS.
3.1.7.1 Ability to Create Permit data (including geographical locations, UNICON will integrate IMPACT with County
Layers Showing type of permit, permit number, and some basic ArcGIS.
Sources by Type data) should be exportable to .csv files.
Unpermitted source record data (such as de
minimis sources and non-traditional dust 6 $17,600.00
sources
[http://www.maricopa.gov/aq/divisions/compli
ance/dust/dust_sources/Default.aspx]) should
also be exportable to map layers.
3.1.7.2 Ability to Latitude and longitude must be recorded for IMPACT supports this requirement.
Assign Multiple multiple emissions points at many permitted
Points to a sources. Those points must be uniquely 6 $8,800.00
Single Record identified, so that emissions limits and
performance test results for those points may
be included in dispersion modelling.
3.1.7.3 Ability to Because many permitted sources are IMPACT currently allows multiple geographic
Assign Multiple geographically large or (in the case of, e.g., references for a single record, but not 6 $17,600.00
Polygons to a utility lines or highways) are very long, permit polygons. UNICON will add the capability for

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
Single Record records must be able to be geolocated not only multiple polygons in a single record.
as points but as polygons.
3.1.7.4 Ability to Create Permit applicants should be able to select UNICON will integrate IMPACT with County
Record Data parcels or draw polygons of their proposed site ArcGIS.
from a Map when applying for a permit. It is preferable that 6 $35,200.00
these data be integrated so that the proposed
solution can consume them from a
geodatabase.
3.1.7.5 Ability to Track Inspectors should be able to select parcels from UNICON will work with the County to
Inspections in a a map layer or draw polygons on a map when implement a flexible solution for tracking *all*
Geodatabase recording inspections. Inspections should be of the County's record keeping needs around
recorded in a geodatabase so that there is sites that are not traditional, permitted, point-
current information about the dates and kinds source facilities. UNICON will create a
of inspections. tracking mechanism that kept track of "sites"
(including dust-generating activities, non- 6 $26,400.00
traditional sites, gravel operations, asbestos
sites, commercial fireplaces, etc.). The support
will include site data such as name, type,
location (coordinates), spatial description
(polygon), inspection history, notes,
attachments, etc. The site data will then be
searchable and exportable to a map layer.
3.1.7.6 Ability to MCAQD uses data from external sources, such UNICON will integrate IMPACT with County
Integrate Layers as the Maricopa County Assessor (see item ArcGIS.
from External 3.1.6.1, above), the Maricopa County Flood
Sources Control District, the Maricopa County
Department of Transportation, ArcGIS online, 6 N/A
the Federal Geographic Data Committee
(FGDC), and the United States Census Bureau.
If there is inherent GIS functionality in the
proposed solution, the proposal should specify
how these sources may be incorporated.
3.1.7.7 Metadata If the proposed solution has inherent GIS UNICON will integrate IMPACT with County
functionality, or if it is capable of exporting ArcGIS.
data to be consumed by GIS services, the 6 N/A
proposal should specify methods for creation
of and standards for geospatial metadata.

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
Metadata should meet EPA standards. The
EPA Metadata Editor (EME)
[https://edg.epa.gov/EME/] produces and edits
metadata that meet EPA standards. The
documentation for the EME provides useful
information about production of metadata that
meets EPA standards and the FGDC Content
Standard for Digital Geospatial Metadata
(https://www.fgdc.gov/standards/projects/meta
data/base-metadata/v2_0698.pdf).
3.1.8 Reporting Any data that go into the MCAQD database IMPACT provides three categories of system
Capabilities: must be capable of being retrieved from the reports:
database. The following are the most common 1. Flexible searching with results exported to
types of required reporting capabilities. Excel format
Proposals must specify the ability to provide at 2. Embedded, purpose-built reports
least these reporting capabilities and must 3. User defined report files in Excel format
specify whether those capabilities are inherent (using read-only connection to the EMS
to the proposed solution or are provided database)
through the integration of an external reporting Note that IMPACT uses an industry standard 1 $ —
tool. Relational Database Management System
(SQL Server); users who wish to leverage
It is expected that selected MCAQD personnel third-party report generation or business
will have direct data access for reporting intelligence tools such as Microsoft SSRS,
purposes. Provide specific information about Cognos, or Microsoft Power BI can connect to
any limitation on data access. our solution's database using a read-only
connection. IMPACT design is open (no
obfuscation of table or attribute name) and
intuitive.
3.1.8.1 Recurring A substantial number of reports are required Users of IMPACT have determined that they
Management periodically. Selected users should be able to can satisfy a large percentage of their
Reports create and save reports that are needed management reporting needs by using
periodically so that they do not have to be IMPACT's flexible searching mechanisms
recreated each time they are run. combined with the ability to export the search 8 $8,800.00
results to Excel. This capability has proven to
be very powerful and has greatly reduced the
need for our users to seek other "report
writing" solutions.
In addition, the system provides a set of

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
custom-developed management reports
3.1.8.2 Ad Hoc Reports Any combination of data may be needed on IMPACT allows users to create their own ad
and Business short notice and may require joining and hoc reports using a read-only database
Intelligence sorting data from different functional areas connection and tools such as Excel or Access
(such as permitting and compliance). Ad hoc to create the report. IMPACT allows users to
reporting capabilities are required. Their upload these standalone report files into the
capabilities and limits should be clearly stated. system where they can be organized into 8 $8,800.00
logical groups and then downloaded and
Provide specifications for business intelligence, executed by other internal system users
business analytics, dashboards, and related
capabilities. Include information about the
means used to design, save and share custom
reports and dashboards.
3.1.8.3 Data Quality Selected users should be able to execute IMPACT does not currently provide the types
Assurance queries and create reports for data quality of reports described in this section of the RFP.
Reports assurance purposes, to check for, e.g., data that IMPACT has extensive input validation checks
are out of expected parameters or fields that which prevent the user from entering invalid or 8 $17,600.00
have inappropriate content types. out-of-range data. However, based on
identified needs, UNICON will implement
such reports and integrate them into IMPACT.
3.1.8.4 Records Request Public records requests often are or include IMPACT provides explicit capabilities for
Reports requests for data. Fulfillment of such requests assembling all of the composite data that
is required by state statute. Such requests represents a user submission - such as a permit
include, but are not limited to: requests for all application, emissions inventory, or
data related to a permit; requests for all data compliance report. These capabilities assemble
related to a permittee (including all permits, all of the user-provided attached files as well as
complaints, inspections, enforcement actions, PDF-formatted reports of the completed web 8 $8,800.00
etc.); requests for all records related to a forms. IMPACT compiles a zip archive and
specified geographic area (parcels, blocks, or provides this for easy download to internal
other areas); or requests for all records users who can then email the zip file to the
(including inspections, emissions data, etc.) requestor.
related to a permit type or a pollutant for a
specified period of time.

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.1.9 Testing and (N/A — Section heading only) Maricopa County has determined that the cloud
Development hosting will be in Amazon Web Services. 1 N/A
Environments:
3.1.9.1 Testing The solution should include a testing UNICON proposes that the project configure
Environment environment and the ability to conduct testing and support a Staging (Testing) environment in
and execute protocols to ensure the solution the hosting system. UNICON has not included
operates according to specified configurations, the cost in the cost spreadsheet since we
both prior to initial deployment and prior to propose that the County contract directly with 1 N/A
any upgrades, enhancements, modifications, or the hosting vendor.
changes to configurations. Test scripts will be
developed in conjunction with MCAQD staff
according to processes and requirements.
3.1.9.2 Development A development environment should also be UNICON proposes that the project configure
Environment provided for development of enhancements, and support a Staging (Testing) environment in
modifications, or changes to configurations. the hosting system. UNICON has not included 1 N/A
the cost in the cost spreadsheet since we
propose that the County contract directly with
the hosting vendor.
3.1.10 Hosted Services Any software solution must be either (a) hosted UNICON proposes that the project configure
and Cloud by the provider or (b) deployed to a cloud and support a Staging (Testing) environment in
Environments environment. (For the latter, Maricopa County the hosting system. UNICON has not included
prefers Microsoft Azure Government the cost in the cost spreadsheet since we
Community Cloud Solution.) MCAQD propose that the County contract directly with
strongly prefers not to have an on-premises the hosting vendor.
solution.
Any software solution must meet Maricopa
County hosting requirements (see Exhibit 7). X N/A
In addition, because much of the data that are
reported to the EPA must be gathered and
stored in a manner that proceeds in an
unbroken path that meets federal security
requirements, the hosted environment should
be FedRAMP certified.
Maricopa County will conduct a security
assessment of proposed solutions. Vendors
must complete and submit Exhibit 2 with

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
responses to this RFP.
3.1.11 User Training (N/A — Section heading only) 8 N/A
3.1.11.1 Initial and The response to this RFP should include UNICON has prior experience developing user
Subsequent information on initial and subsequent training training courses for IMPACT and will develop
Training offered by the provider or by third parties, and customized versions tailored specifically for
terms and conditions thereof. the County for IMPACT. We have typically
developed three separate training offerings:
1. Internal (MCAQD) users
2. Internal system administrator users
3. Portal (industry) users 8 $8,800.00
UNICON will train MCAQD staff. UNICON
suggests that MCAQD train the portal users,
which allows them to frame the training in the
context of the business practices, preferences
and policies of MCAQD. UNICON would be
available to answer technical questions on
IMPACT.
3.1.11.2 Training and The solution should include online training and UNICON will create all training and reference
Reference reference materials, and detailed user manuals, materials per MCAQD requirements in
Materials for two distinct audiences: internal (i.e., for electronic form and include them as a
MCAQD staff), and external (i.e., for component of the delivered IMPACT.
representatives of regulated facilities). UNICON will create designated web links
(URLs) so that users of both the internal and
portal systems will have online access to the
training materials for their system. Materials 8 $17,600.00
for internal IMPACT will consist of both
standard user training and system administrator
user training. Note that UNICON will make all
source documents/files for the training
materials available to MCAQD for their use.
UNICON does not intend to claim any
proprietary or exclusive rights to the training
and reference materials.

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.1.11.3 Training for The proposal should specify the methods and UNICON will update the online training
Version Updates timing of, and any terms and conditions of, materials as part of the software version update
supplemental training to accompany solution process. Depending on the scope of the 8 $8,800.00
version updates. changes contained in the version update,
UNICON will discuss with MCAQD the best
training delivery model for version updates
3.1.12 Administrative The proposal should include information An integral component of IMPACT is the
Control detailing means, methods and levels of "administrator" user privilege level which can
administrative control in the proposed solution. be given to multiple users of the internal
Those details should explain the authorities and system. UNICON strongly recommends that
responsibilities for administrative control, MCAQD grant this privilege level to a small
which person or persons shall have those number of users - preferably no more than 3. 2 $ —
authorities and responsibilities, how many
users can have various authorities and
responsibilities, and which authorities and
responsibilities are reserved by the vendor.
This information should include (but should
not be limited to) the following items.
3.1.12.1 User Specify the authorities and methods for adding, IMPACT is designed to accept all users who
Management updating and retiring users, and for retrieving are authenticated AD users. UNICON will
and resetting passwords and user names (unless configure IMPACT to work with County active
passwords and user names are managed directory.
through active directory). 2 $8,800.00
MCAQD prefers support for SAML-enabled
single sign-on. Maricopa County’s preferred
single sign-on service is Okta.
3.1.12.2 Permissions, Explain how permissions, security levels and IMPACT supports three primary user privilege
Security Levels user roles are managed in the proposed levels - administrator, general user, read-only
and User Roles solution. Include the names, authorities and user - for the internal system. The portal
responsibilities of user roles, the number and system supports two user roles - eSigner and
nature of security levels (or the customizations editor. IMPACT supports a flexible mechanism
of them that may be available). for creating new roles on the internal system. 2 $ —
Administrator users can create new roles (no
programming changes) with specific privileges,
allowing the administrator users a great deal of
control in assigning privilege/access levels.
Refer to a further description of these

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
capabilities in section 14 of our proposal
3.1.12.3 Change Audit Detail how user activity is recorded and can be IMPACT provides three mechanisms for
reported by the proposed solution. Explain if tracking user activity. The first (and primary)
user activity information is available through a method is IMPACT's Field Audit Log (FAL).
report, through a user interface, or is recorded For a specified set of data elements, the FAL
in the background to be recovered by a records all of the following regarding the
database query. Specify if all, none or some of change in value: time and date of change,
user activity is recorded. If only some is person who made the change, old value, and
recorded, specify if the range of activities is new value. IMPACT performs this tracking
configurable and what the limitations of seamlessly. Internal users can query this log
activity recording are. using a set of search criteria and the results are
shown in a datagrid format that can be
Provide full specifications for record change exported to Excel. By targeting a specific set of
history recording and management. Explain data elements, rather than every element in the
how change history is available (through a system, the FAL imposes only a small
report, through a database query, etc.). Specify processing overhead. There are no known
if all, none or some changes to records are performance issues. 2 $8,800.00
logged. If only some is recorded, specify if the The second mechanism is IMPACT's facility
range of activities is configurable and what the inventory history feature which maintains a
limitations of activity recording are. detailed history of configuration changes at the
facility composed of successive, contiguous,
If there are any known performance issues non-overlapping versions of the facility. Users
caused by any of the functionality listed in this can view prior versions of the facility including
section, provide a detailed explanation. start and end dates for the version.
The third mechanism is the Gateway
Submission Log which records all industry
user submissions from the portal system. The
log includes the facility, submission type,
portal user name, and submission Date/Time.
Internal users can search this log by using a set
of search criteria. IMPACT shows the results
in a datagrid which the user can export to
Excel.

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.1.12.4 Configuration Provide specific information about the kinds of IMPACT's design makes extensive use of user
Changes configurations changes (modifications to configurable parameters. Changes to these
screens, workflows, automated emails, etc., as parameters can be made by the administrator
applicable to the proposed solution) that are user and do not require programming changes
available, whether they may be managed by from the vendor. IMPACT uses the concept of
designated users, or, if they may not be "Definition Lists" to store these parameters.
managed by designated user, the vendor Definition lists are represented as tables with
performance requirements for making any rows and columns and span all functional areas
changes that cannot be made by designated in the system including facility inventory,
user. permitting, emissions inventory, compliance 2 $ —
tracking, ambient monitoring, billing, and
reporting. IMPACT currently supports
approximately 200 lists that range in
complexity from simple lists of enumerated
values (which drive the content of drop-down
lists shown elsewhere in the system) to
complex tables containing numerous flags and
indicators which govern IMPACT's processing
logic. Access to IMPACT's definition lists is
restricted to the administrator user.
3.1.12.5 Field Validation Fields should have available validation to limit Most field validations can be controlled
available choices (e.g., compass directions in through a definition list (see above). Other
address fields) or ranges of values (e.g., infrequently changed validations are
lat/long values). Specify the available field implemented in IMPACT's Java code and
validation functionality and the management of require programming changes. UNICON 2 $8,800.00
that functionality. proposes to work with the County prior to
initial delivery of IMPACT to ensure that all of
the Java-based validations are implemented
properly.
3.1.12.6 Drop-Down, Lists of standard choices may include drop- IMPACT maintains drop-down, drill-down,
Drill-Down and downs, drill-downs or more extensive lists and reference lists in definition lists (described
Reference Lists (such as rules, statutes, ordinances, sections, above). The definition lists are used system-
and related standard language). Explain how wide and can be changed by internal users with
those lists are controlled and maintained. Are administrator privileges 2 $ —
they, for example, configured as look-up
tables? Can tables used in multiple locations be
maintained in a single location? Specify how
permissions for updating such lists are

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
structured.
3.1.12.7 Changes For all authorities and responsibilities reserved All changes to IMPACT base functionality
Reserved by the by the vendor, specify the processes and the shall be governed by a mutually agreed to
Vendor vendor performance requirements for making change order. 2 $ —
any changes that cannot be made by the
customer.
3.1.13 Service Level A service level agreement is required. The
Agreement SLA should include (but should not be limited X N/A
(SLA) to) the following items.
3.1.13.1 Service Include system availability levels and the
Availability methods for calculating them. Include details
Levels of credit for service levels below target levels,
how those credits are to be applied, and any
limits on those credits. Maricopa County’s X N/A
expected monthly uptime is 99.99%. Our usual
expectation is that less than 99.99% results in a
10% credit of monthly fees, and less than
99.00% results in a 30% credit of monthly fees.
3.1.13.2 Recovery Times Specify recovery time objectives and recovery Per Software Maintenance and Support
and Points point objectives to be attained in the event of Agreement X N/A
any failures.
3.1.13.3 Technical Include the availability of technical support UNICON proposes 24/7 support with a 30
Support (hours, contact methods [email, telephone, minute response time target for severity 1
etc.], response time objectives, and response issues as part of our maintenance and support
time coverage (i.e., days and hours when those offering. X N/A
objectives are applicable). Maricopa County’s Refer to the Software Maintenance and
strongly prefers 24/7 live person assistance and Support Agreement
30 minute response time to critical support
issues.

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.1.13.4 Product Updates Specify how product updates and scheduled IMPACT will consist of a dedicated instance of
and Scheduled downtime events are managed, including our software application (not shared with other
Downtime timing and methods of advanced notifications. clients) executing in an MCAQD-specific
Include an estimated schedule of projected production environment. Any scheduled
updates and scheduled downtime for the next outages - including product updates - will be
twelve months and an actual schedule of the coordinated in advance with MCAQD. The
same for the past twelve months. frequency and lead-time requirements for
system downtime will be discussed and agreed
Specify regularly scheduled maintenance times upon with MCAQD. Our typical product
of day. MCAQD’s business hours are from upgrade cycle is approximately once every
6:00 AM Mountain Standard Time (MST) to quarter, but that depends on the specific X N/A
5:00 PM MST. (Note that Arizona does not contractual arrangement between UNICON
observe Daylight Savings Time.) Maintenance and the client.
should be performed outside of MCAQD Any regularly scheduled maintenance would
business hours. take place outside of MCAQD's business
hours.
Regarding the request for the past 12 months
downtime history, our other IMPACT clients
host their own IMPACT instances and they
control the maintenance and downtimes. They
do not make that information explicitly
available to UNICON.
3.1.14 Migration of Historical data must be migrated from EMS UNICON has experience migrating Air Quality
Data from EMS into its replacement solution. It will not be data from legacy systems into IMPACT. We
possible to retain EMS for historical reference have a defined methodology and tools for
purposes. The number of years of historical performing the migration. We focus heavily on
data that must be migrated differs depending data analysis and cleansing (Excel is the tool
on the record type, since each record type has we use most often) before proceeding to the
its own records retention schedule. The current data conversion and loading steps (where we
database contains approximately 315,643 leverage basic SQL querying capabilities and 8 $105,600.00
records (116 GB). ETL tools such as SSIS). We approach the data
migration as a separate, related project with its
Processes (in general), estimated time frames own timeline and expectations for the client
and any necessary tools for the migration of and for UNICON.
data from EMS into its replacement should be
included in proposals. The responsibilities of
each party should be clear. Estimated costs for
migration should be specified.

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.1.15 Ownership of All data are and remain the property of UNICON will never "own" the County's data.
Data and MCAQD. At the termination of any IMPACT will reside on Amazon Web Services
Return of Data relationship with any software and/or database hosted cloud.
at Termination provider, all data must be returned to MCAQD
of Contract in a standard format. Processes for and terms X $ —
related to the return of data to MCAQD
(including the responsibilities of each party,
costs or responsibilities for costs, and time
frames) must be provided as part of the
response to this RFP.
3.1.16 Upgrades to Proposals should include procedures for UNICON follows a documented procedure for
New Versions upgrades to new versions. These procedures installing IMPACT software upgrades. The
should include the amount of time from release procedure includes steps for stopping the
of each new version to implementation, application, backing up the database, installing
processes for conversion of any customizations the new software files, executing DB upgrade
or scripting from the existing version, scripts (if required), updating configuration
processes for testing and validation of new files (if required), re-starting the application in
versions prior to implementation, and a controlled mode, executing sanity and
documentation and user training for new acceptance testing, and finally restoring the X $ —
versions. Specify if upgrades to new versions application to its fully operational mode.
and associated services are included in the UNICON will assist the County in planning
quoted cost or, if not, what the costs of each of these upgrades including the estimation of
those services (and their projected frequency) system downtime, and preparing and
will be. conducting user training (if necessary).
UNICON also provides release notes with each
version of the EMS system listing all of the
changes included in the new version.

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.1.17 Documentation All software customizations (such as scripting UNICON will provide a system architecture
or screen configurations) and any database and design document as part of this
architecture (other than proprietary structures) deliverable. The document will describe each
must be fully documented, and that of IMPACT's software layers and how they are
documentation must be provided to MCAQD organized. It will list all software components
and to the Maricopa County Office of including version numbers (if applicable). It
Enterprise Technology (OET). Procedures for will describe how IMPACT's source code files
providing such documentation should be are organized and explain all of IMPACT's
included in the response to this RFP. source code file naming conventions.
IMAPCT's underlying relational database
system employs a high degree of referential
integrity with explicitly declared primary and
foreign key relationships. IMPACT's table and
column names follow an intuitive naming 8 $26,400.00
convention (no obfuscation). Users familiar
with a tool such as Microsoft SQL Server
Management Studio can examine the database
structure and quickly understand the database's
Entity Relationships (and generate their own
ERD, if they wish). IMPACT uses two DB
schemas - one for the internal and public
systems and one for the portal system.
UNICON will provide updated documentation
upon completion of all deliverables, updates,
and enhancements. The documentation will
undergo technical review prior to final
acceptance.
3.1.18 List of Modules Some software solutions consist of multiple IMPACT consists of multiple functional
and functional modules or other functionality units. subsystems - permitting, compliance,
Functionalities Proposals that include such solutions should emissions inventory, etc. - that are packaged
provide a complete list of all of the modules or and delivered as a single, comprehensive,
units required to perform the tasks reported in integrated system. Administrator users can
the proposal. It is advantageous to provide, then "turn off" or hide selected subsystems 1 $ —
also, a complete list of, or a reference to a through the system's user access control
source where there is a complete list of, all features (i.e., use cases, roles, users). UNICON
available modules or units, since MCAQD may will work with the County prior to system
find possibilities in them that are not delivery to determine which IMPACT
immediately evident. functional subsystems should be initially

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
hidden and which should be shown.
3.1.19 External Some solutions recommend or require IMPACT requires no external software other
Software and integration with external products for some than the base components - MS Windows
Solutions discrete business processes, such as customer Server, MS SQL Server, Java, Apache Tomcat,
relations management tools or cashiering etc. - described earlier.
software. If any such external software or IMPACT does not include an integrated
solutions are recommended or required, a cashiering capability and UNICON will work
complete list should be provided, along with with the County to select an external cashiering
integration methods (existing API, custom system to support the requirements N/A $ —
API, etc.). If specific products are IMPACT does not include an integrated email
recommended, contact information for their server (Mail Transfer Agent). UNICON
suppliers should be included. intends to interface with the County's emailing
system to support system-generated outgoing
email messages.
All required external software licenses will be
held by MCAQD.
3.2 Cross-Program This section includes requirements that apply
Requirements to all or most record types across all or most of
MCAQD’s programs. MCAQD recognizes that
there are many possible ways to design a
solution that will meet its requirements. N/A N/A
Required data elements and functionality are
described below, while remaining, as much as
is possible, agnostic about the design of
proposed solutions.
3.2.1 Contacts (N/A — Section heading only) 2 N/A
3.2.1.1 Multiple All records may have more than one contact IMPACT supports a robust contact
Contacts and (person or office), and it should be possible to management system that allows internal users
Contacts on assign the same contact to more than one to assign the same contact person to multiple
Multiple record. Specify how contact information is contact types within a single facility or across
Records managed, and how duplicate contacts are to be multiple facilities. It also includes capabilities 2 $ —
avoided. to merge duplicate contacts - which can be
particularly useful when reconciling data that
originated from multiple, migrated legacy data
repositories

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.2.1.2 Multiple Types It should be possible to distinguish among IMPACT supports a robust contact
of Contacts various types of contacts. A permit, for management system including user-defined
example, may have a primary contact, a site contact types (e.g. compliance contact,
contact, an emergency contact, a permit holder, emissions inventory contact, NSR billing
a company owner, and one or more contact, on site operator, responsible official,
professionals (such as environmental etc.). Internal users can assign multiple
consultants) associated with it. Specify which contacts (people) to a single contact type (e.g. a
contact types are available and how multiple facility may have home than one compliance 2 $ —
contact types are managed. contact). Each contact type record has an
associated start and end date. UNICON will
work with the County prior to initial system
delivery to configure the desired set of contact
types. Afterward, the administrative user can
edit the list of existing contact types or add
new contact types to accommodate changing
business needs.
3.2.2 Personal Personal names must include first, middle and IMPACT supports a single "last name" field.
Names last (family) names. Specify how the solution The field may contain hyphens. It also supports
will manage records for persons with multiple data elements for title and suffix. 2 $ —
surnames (hyphenated and unhyphenated). The
solution should be able to capture titles and
suffixes.
3.2.3 Business and Business and organization names must include IMPACT provides support for "Company"
Organization the business name and suffix (LLC, etc.) and records that includes the company name and
Names the ability to capture a DBA (doing business other data elements. UNICON proposes to add 2 $1,760.00
as) name. "suffix" and "DBA name" as additional data
elements.
3.2.4 Addresses and (N/A — Section heading only)
Other Contact 2 $ —
Information
3.2.4.1 Multiple It must be possible to record multiple addresses IMPACT supports addresses for contacts,
Address Types and multiple address types (mailing, business companies, and facilities. It supports multiple
and site) in a single record. addresses (address history) for portable 2 $8,800.00
facilities. UNICON will consult with the
County to understand which of these record
types need multiple address types.
3.2.4.2 Mailing Mailing addresses must include: P.O. Box IMPACT supports addresses including addr1,
Addresses number, street number, street direction, street addr2, city, state, zip, and country. UNICON 2 $8,800.00

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
name, street type, unit type, unit number, city, will add street type, and unit number
state, country, and zip or postal code.
3.2.4.3 Business Physical business addresses must include: IMPACT supports addresses including addr1,
Addresses street number, street direction, street name, addr2, city, state, zip, and country. UNICON 2 $5,300.00
street type, unit type, unit number, city, state, will add street type, and unit number
country, and zip or postal code.
3.2.4.4 Site Addresses Site addresses must include: street number, IMPACT supports facility locations that
street direction, street name, street type, unit include mailing address, Long/Lat and
type, unit number, city, state, zip or postal Section/Township/Range. UNICON will add
code, cross streets (N/S and E/W), corner (NE, parcel information and inspection zone 2 $8,800.00
NW, SE, SW), parcel information, inspection
zone, and latitude and longitude (digital
degrees).
3.2.4.5 Parcel Parcel information should include parcel IMPACT supports Section/Township/Range.
Information number, township/range/section, legal UNICON will add parcel number, legal 2 $8,800.00
description, and MCR (Maricopa County description, and MCR number
Recorders) number.
3.2.4.6 Inspection The MCAQD Compliance Division designates IMPACT does not currently support inspection
Zones inspection zones within the county. Those zone zones. UNICON will add support for this to
numbers should auto-populate in all site our system.
records. The zones are reconfigured
periodically, to reflect changes in population
and business distribution. Specify the means
for updating these zones in the site records. 2 $17,600.00
When zone numbers are updated, the original
zone information should be preserved in
completed inspections, closed permits or any
other terminated records. The zone information
should be updated in any open, active records.
3.2.4.7 Emails and Email is MCAQD’s primary means of IMPACT supports a single email address for
Websites communication with its customers. Email contacts. UNICON will add support for
format should be validated. Every record for a multiple addresses and email addresses for
person, business or organization must be able businesses (companies) 2 $8,800.00
to record at least one email address. The ability
to record multiple email addresses for a record
is strongly preferred.

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
The ability to capture website URL’s for
persons, businesses or organizations is
preferred.
3.2.4.8 Telephone and Multiple telephone number types (land line, IMPACT supports three phone numbers per
Fax Numbers cell, and fax) should be available on all person, contact - Primary, Secondary, and Mobile.
business and organization records. Person UNICON will re-label them if the County
records should also allow the designation of at wishes to do so 2 $3,520.00
least one number as ‘work’ and one number as
‘home’. It should be possible to capture
extensions and international numbers.
3.2.5 Communica- It is important that all communications made in IMPACT supports a robust Correspondence
tion Logs relation to a record (in person, email, phone subsystem which provides numerous data
calls, etc.) be recorded on that record, along elements (many of them optional) including
with notes about those communications. direction (to/from), City, type, category, receipt
Specify the method(s) for recording these date, generated date, to field, from field, 2 $ —
communications and notes. subject, additional info, and attached
documents. The internal user can search for
correspondence records using multiple search
criteria.
3.2.6 HPA/No Burn MCAQD is required to record the occurrence UNICON proposes to implement this tracking
Days of high pollution advisories and no burn days. on a per-calendar day basis. This information
It is strongly preferred that the proposed can then be linked to inspection and complaint
solution be able to record HPAs and no burn records based on a specified date field
days, that it be able to populate that 8 $26,400.00
information on inspection and complaint
records that are created on those days, and that
reports can be created to analyze violation and
complaint data by HPA/no burn status.
3.2.7 Complaints MCAQD has two very different kinds of
complaint processes. The smoking vehicle 7 $ —
program has requirements that are quite unlike
those of all other complaints.
3.2.7.1 Smoking Members of the public may report smoking IMPACT currently does not support this type
Vehicles vehicles. (Approximately 2,000 reports were of complaint tracking. However, UNICON will
received in FY2015.) MCAQD staff have add the support including the ability to 7 $35,200.00
access to the Arizona Department of Motor generate letters and record a complaint "state"
Vehicles license plate database solely for the (e.g., open, closed).
purpose of determining the address of the

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
owners of reported smoking vehicles. Advisory
letters are then sent to the owners of the
reported smoking vehicles.
This program requires that the solution be able
to produce addressed form letters for mailing,
but that the license plate information and the
personal information about the owners of the
vehicles not be retained in the MCAQD
database after the letters have been created. In
addition, it must be possible to close a smoking
vehicle complaint record if a license plate is
out of state, since MCAQD does not have
access to out of state registration information.
3.2.7.2 All Other (N/A — Section heading only) 7 $ —
Complaints
3.2.7.2 Complaint Currently, members of the public may report IMPACT currently supports complaints as a
Intake potential violations by phone, email or through type of correspondence. UNICON proposes to
a web form. (Nearly 3,000 reports were split complaints out as a new type of record
received in FY2015.) Complaint information is and allow users of the solution's public portal
then entered into EMS by MCAQD staff. to create and view these records
MCAQD seeks to improve customer access
and reduce manual data entry by instituting a
system for direct reporting by the public. It will
still be necessary, however, for MCAQD staff
to be able to enter complaints manually. 7 $26,400.00
Information collected should include at least
the type of complaint, the date and time of the
complaint, the date and time of the air quality
problem (which may be the same as the date
and time of the complaint), the location of the
problem (which may be either exact or
approximate), the name of the source (if
known), and notes (text field). All complainant
contacts should be logged (see section 3.2.5).

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.2.7.2 Complainant It must be possible for the public to submit UNICON will add logic to the system so that
Information anonymous complaints. Even if the complaint only those internal users with appropriate 7 $8,800.00
is not anonymous, complainant information privileges (assigned use cases) can view the
should be confidential. complainant information
3.2.7.2 Types of It must be possible to differentiate among types UNICON will add this as an inherent part of
Complaints of complaints (e.g., fugitive dust or odors). It is the complaint intake capability
likely that the list of complaint types will
change periodically. It should, therefore, be
easy to edit. 7 $ —
It must also be possible to change the type of
complaint after it has been reviewed or after it
has been investigated.
3.2.7.2 Aggregation of It should be possible to aggregate multiple IMPACT supports optionally associating a
Complaints complaints about a single source or event, correspondence record with a facility (source). 7 $8,800.00
either by uniting them in a single record or by UNICON will preserve this capability when
associating them to a single record. UNICON splits out complaints.
3.2.7.2 Source When possible, complainants report the Internal users will be able to edit the complaint
Information suspected source of an air quality problem. On record and associate or disassociate it with a
investigation, it is sometimes determined that facility.
the source is not the reported source. It must be 7 $5,280.00
possible to amend the complaint record to
reflect those findings. It should also be possible
to record multiple sources for a single
complaint.
3.2.7.2 Complaint- Once a complaint has been received, an IMPACT supports the concept of generating a
Based inspection is conducted. There should be a single task workflow (sometimes simply called
Inspections system for alerting inspectors or supervisors of a To-Do list item). UNICON will implement
complaints that have been received, for the support for this feature to automatically
assigning complaints to an inspector or generate a To Do list item when the complaint 7 $8,800.00
supervisor (or for inspectors to assign is created.
complaints to themselves), and for notifying
designated MCAQD staff if a complaint has
not been handled.

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.2.7.2 Relating Complaint records must be able to be IMPACT will support the optional association
Complaints to associated with permit records or unpermitted of a complaint with a facility. UNICON will
Other Records source records, so that they become a part of add a screen navigation point ("Complaints") 7 $5,280.00
the compliance history for that source. to the facility inventory record so that users can
quickly view the list of complaints associated
with a facility.
3.2.7.2 Results of There must be a method for recording UNICON will add data elements to the
Complaints complaint findings and for closing complaint Complaints record to keep track of results and
records. Complaint records may be closed state (e.g. open, closed) 7 $3,520.00
because of the results of MCAQD
investigations or because the subject matter is
not within MCAQD jurisdiction.
3.2.7.2 Responding to Complainants may request that they be UNICON will prompt the complainant for
Complainants informed of the results of the investigation of his/her email address on the complaint entry
their complaints. It is preferable that this screen. If he/she provides it, UNICON will 7 $8,800.00
process be as automated as is practicable. provide a hyperlink on the complaint detail
screen that allows the internal user to quickly
send an email to that address.
3.2.7.2 Reporting on It must be possible to report on complaint data IMPACT has a search screen for
Complaints (for selected periods of time and selected Correspondence that includes numerous search
geographic areas), including the number of criteria fields including date ranges. UNICON 7 $17,600.00
complaints, the types of complaints, and the will create a similar search screen for
resolution of complaints. Complaints that allows the internal user to
specify search criteria.
3.2.8 Printed Official It must be possible to print official documents, IMPACT supports an integrated document
Documents such as permits, notifications, certifications, generation capability. The capability uses
registrations, exemptions, inspection reports, Microsoft Word template files coupled with a
opportunities to correct, notices of violation, parameter substitution capability (similar to
and orders of abatement by consent. Specify Word's Mail Merge feature) to generate
the means for producing such documents and editable Microsoft Word (.docx) files.
the methods for configuring them (e.g., IMPACT uses this capability throughout the 3 $5,280.00
produced by report-writing tools or exported system and can be used in cases where a single
into a word processing program by inherent document (e.g. a permit document for a
functionality of the proposed solution). specified facility) is needed and also in a bulk
generation context (e.g. "send this letter to all
Title V facilities"). Internal users may save the
generated document(s) on their PC, edit them
further (if necessary), upload them as

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
attachments into IMPACT, and attach them to
outgoing emails.
3.2.9 Processing The amount of time (most often specified as
Time business days) allowed for the completion of
some processes (e.g., permit application
processing, complaint handling and public 3 $ —
records requests) is governed by State of
Arizona permitting time frames and other
regulatory requirements. Hence, it must be
possible to record and manage processing time.
3.2.9.1 Recording Start and end times should be recorded IMPACT supports a powerful and flexible
Processing Time automatically for those processes that have Workflow subsystem that records start and end
defined time requirements. It should also be times for the entire workflow (all tasks) and for
possible to record start and end times manually each component task in the workflow. This 3 $31,680.00
for undefined processes. subsystem will meet the County's needs as
described in this RFP.
3.2.9.2 Notifications of There should be a process for alerting An integral part of the Workflow subsystem is
Upcoming designated MCAQD staff prior to the the "Home" tab that contains a list of all tasks
Deadlines expiration of mandated processing times for currently assigned to the user. The list is
individual records. ordered in chronological order (ascending)
based on the workflow task due date. Thus, 3 $ —
users can see the tasks that are due the soonest
at the top of the list. The Home tab screen
displays numerous other data fields to enable
the user to view the details of their workload at
a glance.

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.2.9.3 Pauses in Some events (e.g., a request for information IMPACT's workflow subsystem supports a
Recorded from a source or an EPA review) are not "referral" action for workflow tasks. User can
Processing Time considered part of MCAQD processing time. define whether the referral takes the task "off
Those events pause the recording of processing the clock" or not. There are several summary
time. As much as is practicable, it is preferred reports that show the total accumulated days
that those events be configurable to pause for both "on the clock" and "off the clock"
process time recording automatically. It must categories. This capability includes manual and
also be possible to pause and restart processing automatic "unreferrals" after a specified 3 $ —
time recording manually, and to record the interval. Most of these referral parameters are
reasons for the pauses and restarts. contained in a definition list - allowing the
administrator user to adjust these values if
necessary. The subsystem includes a "Notes"
capability that allows users to manually record
notes. IMPACT automatically adds a system-
generated note each time a task is referred.
3.2.9.4 Reporting Processing time will be associated with a IMPACT's workflow subsystem records the
Processing Time specific record, task and user. There should amount of time spent on each task. A task can
also be a process for reporting aggregated be assigned to exactly one user (no shared
process time data (including reporting by tasks) at a time although users can reassign 3 $ —
categories such as permit type or process type). tasks to other users. IMPACT has several
summary reports that detail the amount of time
(elapsed days) spent on each task.
3.2.10 Forms and MCAQD uses forms that are submitted by IMPACT supports an integrated template-
Documents customers (e.g., permit applications), forms based document generation capability that
that are used by inspectors and other MCAQD generates MS Word formatted files. After
staff, standard reports that are posted to the generation, IMPACT allows for the user to
MCAQD website, standardized form letters, attach theses files to the relevant record within
and standardized emails. Proposals should IMPACT. For example, a user may generate a
include detailed information on the capacity of permit document (.docx file) and then attach
the proposed solution to produce and receive the document to the permit record in the EMS 1 $ —
such forms and documents, including system. As an attachment, IMPACT makes no
information on any external programs or further attempt to open, parse, or process the
utilities that are necessary to create and manage file. The generated file is simply treated as an
those forms and documents. Specify, at a attached artifact to the permit record.
minimum, how documents are generated, if IMPACT also provides a bulk document
their creation can be automated (or created generation capability, allowing users to select a
through batch processes), if data from set of facilities (and an underlying template
submitted forms can be extracted directly into document) and generate a set of documents in

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
the proposed solution, how and if standardized one operation.
emails can be generated, and if such
standardized emails can include attachments. IMPACT is a web application composed of
many "web forms". These forms are standard,
browser-based forms. IMPACT does not use
fillable PDFs or any other type of fillable form
based on an external program.
UNICON proposes to integrate with the
County's email system for system-generated
outgoing emails. UNICON does not currently
support bulk-generated emails (with or without
attachments) but could certainly design and
implement such a capability in the future
3.2.11 Fees and (N/A — Section heading only) 4 $ —
Payments
3.2.11.1 Fee Schedules Fee schedules are typically updated annually IMPACT supports fee schedules for NSR
and take effect on January 1st with the permits and Title V Emissions Inventories. The
possibility of additional changes in a given schedules are adjustable by the administrator
year. Designated MCAQD staff should be able user and include a simple history mechanism
to update the fee schedules. It should be with associated effective dates for each
possible to perform a quality control check on version. UNICON proposes to add schedules 4 $17,600.00
any updated fees prior to implementation in a for other billable services such as dust control
production environment. The fee schedule for permits, subcontractor registrations, and annual
previous years must remain available, so that administrative fees.
charges from previous years may be assessed.
Fee schedules should be available for MCAQD
staff to view.
3.2.11.2 Fee Calculations Fees for all items for which there is a IMPACT supports quantity-based fee
scheduled fee should be calculated calculations for emissions inventories
automatically when records are created. These (tons/year) and NSR permits (hours spent *
calculations should include fees that are based hourly rate). UNICON will work with the 4 $17,600.00
on quantities provided by the customer, as in, County to understand their business rules for
for example, asbestos notifications, dust charging for asbestos notifications and dust
control permit applications and emissions fees. control permits and implement changes to
IMPACT accordingly.

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.2.11.3 Manual Fee It must also be possible to assess fees IMPACT currently supports fees associated
Assessment manually, both for items for which there are with a specific record - such as a permit or an
scheduled fees and for miscellaneous emissions inventory. UNICON proposes to add 4 $31,680.00
(unscheduled) fees. Only designated MCAQD a manual fee assessment, invoice history, and
staff should have this authority. balance tracking capabilities to IMPACT
Company record.
3.2.11.4 Late Fees It must be possible to assess late fees. The IMPACT does not currently provide support
proposed solution should be able to be for automatically assessing late fees. UNICON
configured to assess some late fees when will work with the County to understand your 4 $26,400.00
specified conditions have been met. business rules including late fee criteria and
amounts. UNICON will then implement the
changes to IMPACT accordingly.
3.2.11.5 Waivers, Voids It should be possible to waive, void or IMPACT supports manual fee adjustments
and Manual manually adjust fees before or after a payment. (debit or credit) for NSR permit invoices and
Adjustments There should be a means of recording the for Emissions Inventories. UNICON will work
reasons for the waivers, voids or adjustments. with the County to understand its business 4 $8,800.00
Only designated MCAQD staff should have rules for manual fee adjustments for asbestos
this authority. notifications and dust control permits (if any)
and implement changes to IMPACT
accordingly.
3.2.11.6 Automatically Fees that are based on quantities provided by IMPACT supports this capability for NSR
Updated Fee the customer should update whenever those permits and emissions inventories. UNICON
Assessments quantities are changed. will add it (as appropriate) to other billable 4 $3,520.00
service categories such as asbestos
notifications, dust control permits, and annual
administrative fees.

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.2.11.7 Invoicing and Invoices should be created in a standard IMPACT generates invoice documents in MS
Due Dates electronic format when an intake process is Word format using the system's template-based
completed for any billable activity. It must also document generation capability. IMPACT's
be possible to create or recreate invoices on users typically attach these generated
demand, to automate the sending of invoices in documents to the corresponding IMPACT
a standard electronic format, and to print or record - such as the NSR permit record or the
reprint invoices. emissions inventory record. Users can
download the document for review, re-printing
It should also be possible to create or to trigger or re-sending as necessary. Users may also re-
the creation of invoices from other processes, generate the document if necessary. The
such as performance test records or invoice template can include numerous
enforcement records. substitution parameters corresponding to 4 $17,600.00
various data elements in IMPACT including
All invoices should have a unique identifier, elements such as company name, company id,
show the date that the invoice was created, and facility name, facility id, permit number,
show a due date based on the type of record. application number, contact name, contact
address, invoice amount, date of service, etc.
Invoices for periodic fees, such as annual IMPACT documents the complete list of these
permit or registration fees, should be generated substitutable elements in a concise document
automatically (either individually or as batch available to administrator users.
jobs). IMPACT supports batch jobs for invoice
generation although this capability will likely
need to be adjusted to meet MCAQD's needs.
3.2.11.8 Receipts and Receipts should be created in a standard IMPACT currently supports tracking of
Acceptance of electronic format when payments are received. payment amounts for NSR permits and
Payments It must also be possible to create or recreate emissions inventories. It does not currently
receipts on demand, to automate the sending of generate receipts but UNICON will work with
receipts in a standard electronic format, and to the County to understand the detailed
print or reprint receipts. requirements and then implement the needed 4 $17,600.00
changes
All receipts should have a unique identifier and
show the date that the payment was received,
the method(s) of payment, the records for
which payment was received, and payor
information.

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.2.11.9 Partial Payments It must be possible to receive and record partial IMPACT supports the partial payment need
payments. Some permits (e.g., Non-Title V) described for Non-Title V (NSR) permits
require an application fee to be paid with the although some minor tweaks to the business
initial application, with a later payment for rules are needed. UNICON will implement
additional charges once those charges have additional changes to support dust control
been calculated. Some (e.g., dust control permits 4 $17,600.00
permits) may be modified in a way that triggers
additional charges. In any such cases, it must
be possible to create a new invoice that shows
the complete charge and payment history, and
to accept and accurately apply the later
payments.
3.2.11.10 Payment Plans It should be possible to create payment plans IMPACT does not currently support payment
and to record payments made against those plans. UNICON will work with the County to 4 $17,600.00
payment plans. define detailed requirements before proceeding
to implement changes.
3.2.11.11 Acceptance and It should be possible to accept and record IMPACT supports the recording of payments
Application of payments in different forms (e.g., cash, check, against invoices for NSR permitting, but does
Payments credit card, or journal voucher). It should also not currently integrate with a cashiering
be possible to accept multiple methods of system. UNICON will develop an intersystem 4 $44,000.00
payment for one transaction. interface between a county cashiering system
and IMPACT.
It should also be possible to apply a single
payment to multiple records.
3.2.11.12 Unpaid or It should be possible to report on unpaid or IMPACT currently supports some of this
Outstanding outstanding invoices. A permit, registration, functionality - particularly with respect to
Invoices etc., shall not be issued or renewed if there are invoices for NSR permitting. Additional 4 $31,680.00
unpaid or outstanding invoices against that changes will be made to fully meet this need.
record, unless that restriction is explicitly
overridden by designated MCAQD staff.
3.2.11.13 Overpayment It should be possible to record overpayments IMPACT does not currently support this.
and to issue refunds after overpayments. UNICON will define requirements and 4 $17,600.00
implement additional changes.
3.2.11.14 Payment MCAQD currently uses FIS and RPower as This is dependent on item (Acceptance and
Systems payment systems (but note that these payment Application of Payments) (24.10)
systems are currently under review and are 4 $8,800.00
subject to change). Proposals should specify
how the proposed systems will integrate with

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
external systems and/or if they have inherent
payment acceptance, processing and tracking
capabilities.
3.2.11.15 Transaction, The proposed solution should produce This is dependent on item (Acceptance and
Transmittal and transaction reports and transmittal reports. It Application of Payments) (24.10)
Other Reporting should also be able to report on outstanding
balances (for individual records and as 4 $8,800.00
aggregated data) and to produce ad hoc reports
for cost accounting and fee modelling
purposes.
3.2.11.16 PCI Compliance Payment systems should be PCI compliant. This is dependent on item (Acceptance and
(See https://www.pcisecuritystandards.org/) Application of Payments) (24.10) 4 N/A
3.2.12 Daily Activity (N/A — Section heading only) 8 $ —
Tracking
3.2.12.1 Activity Although time spent on tasks is not captured IMPACT includes a flexible timesheet entry
Tracking – for all tasks, it must be possible to track time system that allows internal users to record time
General spent by department personnel on tasks. spent against configurable lists of categories
Requirements Tracking should include the user’s name, and subcategories. It includes a feature to
activity type and amount of time, and it should associate timesheet hours with an NSR or Title
be associated with a specific record and task. V application or permit. UNICON can extend 8 $ —
An individual user may perform multiple this feature to track time spent against
different tasks and kinds of tasks associated additional record types other than
with the same record. It should be possible to permits/applications.
track the multiple different tasks and kinds of
tasks performed by one individual in one
record.
3.2.12.2 Reporting of Activity tracking should be reportable both by IMPACT supports a timesheet report feature.
Tracked individual record and by record or task type, to To meet the County's reporting requirements,
Activities allow tracking of direct costs and to support UNICON will extend this feature to support a
process improvement efforts. It should be form of criteria based searching 8 $5,280.00
possible to report multiple different tasks and
kinds of tasks performed by one individual in
one record.
3.2.12.3 Recording and Recording of individual’s time spent for direct IMPACT supports the ability to record hours
Billing cost activities does not always result in invoice against a specific NSR or Title V permit (or
Employee Hours creation, but it must be possible to bill for time. permit application). UNICON will implement 8 $8,800.00
It is essential to record engineering hours, the necessary changes to meet MCAQD needs.
assess fees based on those hours, and create an

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
invoice for engineering hours. It should be
possible to assess fees for public notices and
public hearings based on employee hours
associated with those notices and hearings.
3.2.13 Business MCAQD has a Business Assistance program IMPACT supports Business Assistance
Assistance that allows businesses to receive help personnel as internal users. Note that these
completing applications and to have actions comments apply to IMPACT's internal system
that affect them reviewed. It should be possible only.
to assign active records to the Business 8 $8,800.00
Assistance program from any division in
MCAQD and return them back to those
divisions. It is preferable that it also be possible
to have concurrent assignment to Business
Assistance and to another program or division.
3.2.14 Ombudsman The Maricopa County Ombudsman may IMPACT complaint record will include a
review and respond to public complaints and generalized "Notes" capability (present on
concerns. The Ombudsman is independent of most of our system's record types) so that
MCAQD, but should be able to request and internal users can record the fact that a
receive complaint information from MCAQD, complaint has been forwarded. IMPACT 8 $3,520.00
and MCAQD should be able to note on public complaint record will also support a
complaint records that those records have been "Download/Print" capability (also present on
forwarded to the Ombudsman. most of our system's record types) so that
internal users can send (email) a complaint to
an external party, such as the Ombudsman.
3.3 Programmatic This section includes descriptions of
Requirements MCAQD’s programs and a high-level
overview of their requirements (to the extent
that those requirements extend beyond those
described in section 3.2). MCAQD recognizes
that there are many possible ways to design a
solution that will meet its requirements. N/A N/A
Required data elements and functionality are
described generally below (with the exception
of emissions inventory), while remaining, as
much as is possible, agnostic about the design
of proposed solutions. Emissions inventory is
described in more detail than are other
programs, because most of the detailed

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
requirements are imposed by EPA processes or
regulations. Compliance and enforcement
requirements are reserved for section 3.4.
3.3.1 Emissions When MCAQD retires its current emissions
Inventory inventory (EI) system, it intends to implement
System a web-based emissions reporting system, by
means of which regulated sources can submit
detailed air emissions inventories. It must be
able to integrate with internal MCAQD data
from permitting, compliance and enforcement,
and with external data from the EPA. In
addition, it should be able to extract data for
reporting and research purposes, perform at
least some of the tasks required for the periodic
emissions inventories, and allow submittal of
inventories to the EPA (either directly or
through an integrated node). Any proposed
solution must be compliant with EPA 2 $ —
regulations and with Arizona public records
laws. The department also envisions that the
solution will expandable and flexible to
accommodate future requirements and
enhancements (e.g., the addition of air toxics or
greenhouse gases to the reporting system, or
the development of regional modeling and data
sharing among air regulatory agencies).
Features and functionalities of the desired
solution and its program elements are
enumerated in the sections below. Respondents
should provide a description of how their
solutions will satisfy the requirements or, when
necessary, when and how those requirements
will be met by third-party solutions.

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.3.1.2 Annual The solution should include the ability to IMPACT supports a comprehensive emissions
Emissions designate mandatory fields and required data inventory subsystem. UNICON has described
Inventory Data types for regulated source facilities. MCAQD it in section 14 - Supporting Information. The
requires that regulated source facility IDs subsystem supports the ability to designate
retain their historic, unique values. Any new mandatory data fields.
regulated source facility IDs added to the UNICON understands the County's
system will exist without duplication, and are requirement to retain the historic, unique
to be added only by authorized MCAQD users values for existing source facilities. Our other
or received from the FRS (see section 3.1.5.5). EMS clients have had the same requirement
These unique IDs have been and will continue and UNICON has successfully migrated this
to be submitted to EPA’s EIS. Regulated information from their legacy systems into
source facility data includes but is not limited IMPACT.
to: IMPACT does not allow for batch uploads via
• Facility Data (permit number, address, template files - although we can provide a
geographic coordinates, etc.). separate time and cost estimate for that
capability outside of this proposal. Instead,
• Facility Contact Data (name, address, IMPACT provides many convenience features
telephone, email, etc.) on its web user interface for the portal system
that make it easy for industry users to quickly 2 $8,800.00
• At least three facility contacts along enter their emissions inventory information.
with associated addresses, telephone numbers, One of these features is the ability to copy a
and email addresses previous year's inventory as a starting point for
the current year's inventory. In this case, users
• Facility data should follow EPA/EIS typically need to adjust only the hours of
formatting conventions where applicable. operation and material amounts before
validating and submitting the inventory.
The solution should include the ability to
capture and verify mandatory and required data
elements at a number of different levels of
aggregation. It will collect, validate, store, and
report information on:
• individual emission components
(defined as either a piece of equipment or an
activity), including, e.g., component ID
number, component type, component
description, design capacity rate, emissions,
and related units of measure
• fugitive and stack release points (e.g.,

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
longitude/latitude in decimal degrees,
descriptor, height, diameter, exit gas velocity,
etc.)
• control devices (e.g., device ID number,
control device type code, primary and
secondary control efficiencies, etc.)
• process-level and stack release points
(e.g., process ID number, description,
associated release point(s), material type,
throughput levels, emission factors, units of
measure, etc.)
• process-level operating schedule data
(e.g., start/end times, hours/day, days/week,
hours/year, throughput by quarter, etc.)
• The solution’s design should allow
users to batch-upload required emissions data
into online system via templates that regulated
source users can populate and import into the
online emissions inventory system.
3.3.1.3 Annual Regulated sources must be able to submit, IMPACT includes a feature-rich emissions
Emissions review and edit their data through a web GUI inventory subsystem that supports all of the
Inventory Data or through printed forms. requirements that MCAQD has listed in this
Submission • New, blank reports must be able to be section. The subsystem has similar screens for
generated for sources who are new or who the industry (portal) users and the internal users
were not surveyed in prior years. Blank reports - enabling them to enter inventories sent in
must include the current year’s emissions fees paper or spreadsheet form.
schedule. It relies on web forms and does not make use 2 $8,800.00
of fillable PDFs. No OCR option is provided.
• Simplified reports should be available
and customizable for source types that do not
require extensive reports.
• Annual EI data submission reports must
be able to be generated for each source or

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
facility, based on the previous year’s final,
edited report. Estimated fees, based on the
current year’s emissions fee schedule, must be
included.
• Annual EI data submission reports must
be available through a CROMERR-compliant
(see section 3.1.3.1) web GUI.
• Sources must be able to submit updated
reports or to correct submitted reports, until
MCAQD lock those reports.
• Each time a source submits an annual
report or submits an updated version of a report
or edits an electronic report, a copy of that
version of the data must be preserved (with an
uneditable electronic date stamp) in an
uneditable form for records purposes.
• If printed reports are sent to sources,
then MCAQD staff must be able either (a) to
enter manually the data from those reports, or
(b) to scan those reports and capture the data
through optical character recognition (OCR).
(The OCR option is preferable.)
• If annual EI data submission reports are
also produced as editable electronic forms
(such as fillable PDFs) to be sent to sources,
then the data in the reports when they are
received from the sources must be able to be
extracted automatically (and not have to be
entered manually).

SERIAL 171125-RFP
Section Section Title Functional Requirements Level of Effort Phase Cost
Number
3.3.1.4 Annual MCAQD staff must be able to review, and IMPACT's emissions inventory subsystem
Emissions determine accuracy and completeness, of implements a notification/review/update
Inventory Data submitted data process that supports all of the requirements
Review • MCAQD staff must be able to review that MCAQD has listed in this section. It
copies of submitted data. While reviewing provides extensive tracking and history
those copies, the copies should be in a capabilities and IMPACT creates an associated
‘working draft’ status. workflow instance whenever an emissions
inventory is submitted (either internally or
• MCAQD staff should be able to correct through the portal). UNICON will design
errors, edit data, add data, or otherwise automated emails to be sent to the designated
improve data quality in working drafts of industry EI contact person.
submitted reports. Once MCAQD’s corrections
or enhancements to those reports are complete,
a copy must be able to be re-submitted to the
source for review and correction (if necessary)
or acceptance. MCAQD corrections or
enhancements should be clearly indicated.
Sources must be able to review and accept 2 $ —
MCAQD staff changes through the web
interface or through printed reports. When a
revised version of a report is sent to a source,
or when a source is notified that a revised
version is available for review through the
web, that information must be captured in the
database.
• When revisions are made to annual EI
reports, any applicable fees must be updated
(based on the current year’s fee schedule).
• When MCAQD staff have determined
that annual EI reports are acceptable, they must
be able to accept and finalize those reports.
Once reports are accepted and finalized,
sources may no longer edit them.

SERIAL 171125-RFP
3.3.1.5 Annual MCAQD users must be able to extract data in IMPACT's emissions inventory subsystem
Emissions several different ways. implements all of the requirements listed
Inventory • MCAQD users must be able to generate except search by GIS criteria. Search by GIS
Reports and reports showing which sources: criteria will be accomplished through
Queries integration with County ArcGIS.
o have submitted their annual reports;
have had their annual reports finalized;
o have annual reports still pending review
by MCAQD;
o have revised reports about which they
have been notified and which are still pending
review;
o have not submitted reports.
• Data must be able to be selected or
reported using data fields, data ranges, and/or
GIS criteria.
• Selected data must be extractable to a
reporting database (e.g., an MS Access 2 $17,600.00
database or an ArcGIS geodatabase), either
directly or to a .csv file.
• It must be possible to store reports that
are used frequently.
• MCAQD users must be able to generate
ad-hoc reports via a report generation tool
(either inherent to the solution or through an
integrated report-writing tool).
• The solution must generate summary
emissions reports for any given emissions
inventory year including summaries by facility,
by process type, by source classification code
(SCC), industry, and SIC or NAICS (industry)
codes.
• The solution must calculate and

SERIAL 171125-RFP
generate site-wide summary emissions reports
for invoicing purposes for any given emissions
inventory year using MCAQD specifications
for “billable” pollutants and processes. These
reports will be filled using summed detailed
emissions data. This should be integrated with
an invoicing system.
3.3.1.6 MCAQD The solution’s design should allow authorized IMPACT's emissions inventory subsystem
Emissions MCAQD users the ability to manage the online implements the requirements listed. IMPACT's
Inventory emissions inventory system, including: facility inventory, role-based user access,
Manual • Setting user rights for MCAQD and service catalog, portal user role management
Interface regulated source users. (eSigner vs. editor), and workflow subsystems
all work in concert with the EI subsystem to
• Creating, modifying, resetting, and provide these capabilities.
managing of passwords for MCAQD and
regulated source users.
• Creating accounts for new regulated
source facilities.
• Authorizing regulated sources to have
access to their corresponding facility and data.
• Restricting or locking individual 2 $8,800.00
inventories so that regulated sources can no
longer modify emissions inventories.
• Setting a submittal deadline whereby
entire submittal system is restricted or locked
so that regulated sources can no longer submit
emissions inventories for that inventory year.
The solution’s design should allow authorized
MCAQD users the ability to manage
inventories and data, including:
• Pre-filling data such as components,
release points, emissions etc. from a selected
previous year inventory into a new emissions
inventory for a new inventory year.

SERIAL 171125-RFP
• Creating a new blank emissions
inventory for a given regulated source facility
for a new inventory year.
• Adding existing components into an
emissions inventory for a given regulated
source facility.
• Deleting components from an emissions
inventory along with release points, processes,
process emissions, and controls.
• Adding new components to an
emissions inventory.
• Adding new fugitive or stack release
points to an emissions inventory.
• Adding new processes to an emissions
inventory.
• Adding new process emissions to an
emissions inventory.
• Adding new component controls to an
emissions inventory.
The solution’s design should allow authorized
MCAQD users the ability to manage emissions
data submitted by regulated sources, including:
• Notifications to MCAQD users when a
source has successfully submitted an emissions
inventory.
• Review by MCAQD users of emissions
inventory data that have been submitted by
regulated source users
• Approval and locking, by MCAQD
users, of regulated source-submitted emissions
inventories upon completion of the review
process.

SERIAL 171125-RFP
• Locked inventories can only be
unlocked and modified or edited by authorized
MCAQD users with administrative privileges.
• The ability for authorized MCAQD
users to allow a regulated source to submit an
updated inventory after the deadline and after
the initial inventory has been locked.
3.3.1.7 Regulated Regulated source users should have the ability IMPACT's feature-rich portal system meets all
Source to view, manage, modify, and interact with of these requirements except for the batch
Emissions their emissions inventory data (subject to uploading capability. UNICON can develop
Inventory restrictions noted elsewhere in this document), such a capability, but has not included that in
Interface including: our cost estimate for this line item since we
• Access through a secure login. This believe that more requirements definition
access must be either a certified CROMERR- would need to occur.
compliant portal or be able to be integrated
with a CROMERR-compliant portal.
• Viewing but not modifying (except for
the currently active emissions inventory)
regulated source facility data
• A process to request that MCAQD
make changes to or delete existing facility data,
components, fugitive or stack release points, 2 $ —
processes, and/or controls in the record for the
regulated source
• Viewing but not modifying detailed
emissions inventory data from previous year
inventories
• Viewing, exporting, and/or printing the
total site summary of emissions from any
current or previous year’s emissions inventory
report
• Viewing, exporting, and/or printing a
summary of emissions by component from any
current or previous year’s emissions inventory
report

SERIAL 171125-RFP
• Making changes to a current emissions
inventory report until such time as the report
has been submitted, up until the designated
deadline
Regulated sources that are required to submit
detailed data should be able to update or
modify their current, unlocked emissions
inventories.
Regulated source users should have a method
for batch uploading of required emissions data
into the online system by means of template,
.csv files, or spreadsheets, and for official
submission of the emissions inventory report
once required data has been entered or batch
upload has been completed.
3.3.1.8 Periodic Every three years, MCAQD must produce a IMPACT supports the ability to flexibly define
Emissions periodic emissions inventory (PEI), a set of required emissions inventories on a
Inventories incorporating data from source inventories, yearly basis. Administrator users can define a
monitoring data, area source (non-point- varying number of inventories along with
source) data (and estimates), demographic data, facility selection criteria that includes facility
EPA estimation factors, and other resources not type, facility class (Title V, Non-Title V,
typically included in an annual EI. MCAQD SMTV), and facility location. MCAQD can use
prefers that the proposed solution, to the extent this feature to define periodic inventories and
practicable, be able to: define which facilities owe the inventory.
• Aggregate annual EI data for use in the IMPACT does not currently support the
PEI inclusion of non-point source data such as area 2 $35,200.00
• Calculate and aggregate other data for sources, or demographic data, although
use in the PEI UNICON can provide a separate time and cost
• Produce components of comprehensive estimate for that capability outside of this
PEI reports proposal.
• Transmit PEI reports to the EPA Regarding the transmission of PEI data to
• Receive revisions and comments from USEPA, IMPACT supports gathering the
the EPA on PEI reports, compile and transmit facility and emissions inventory data into
revised reports, and retain all reports and CERS format. It does not perform any other
comments with appropriate recording of calculation or aggregation of data.
versions for records purposes.
3.3.2 Unpermitted Regulated sources (including, but not limited 7 $ —
Sources to, vacant lots) without permits are inspected

SERIAL 171125-RFP
frequently. Some of those sources are not
required to obtain permits but must be
regularly reviewed, and some of those sources
are required to apply for permits.
3.3.2.1 Unpermitted It must be possible to create unpermitted IMPACT does not currently track unpermitted
Sources Records source records that are not associated with a sources. UNICON will support for them in a
permit number but that have a unique way that is consistent with our solution's
identifier. Unpermitted source records must overall design, including generalized searching
include the ability to record parcel information, plus the ability to associate these sources with
including ownership information obtained from owners and contacts.
the Maricopa County Assessor and ownership 7 $53,800.00
information obtained from other sources
(which may differ from Assessor information).
Unpermitted source records must be searchable
by parcel number, business name and owner
name. Unpermitted source records must
include the ability to record latitude and
longitude.
3.3.2.2 Unpermitted It must be possible to track process and UNICON will design these capabilities into our
Source Changes condition changes at an address, and to initial support for unpermitted source records 7 $8,800.00
categorize an unpermitted source so that a (27.2.1)
follow-up inspection is scheduled.
3.3.2.3 Conversion to When an unpermitted source is required to UNICON will implement our design for
Permitted apply for a permit, it may be required to pay a unpermitted sources with this requirement in
Source late fee. It should be possible to trigger the mind.
initiation of a new permit record, and to
indicate (if applicable, that there is a requisite 7 $8,800.00
late fee.
When an unpermitted source applies for a
permit, there must be a way to relate the
unpermitted source record to the permit record.
3.3.3 Permitted This section includes requirements that are
Sources – common to all or most permit records and
Common processes. Requirements that are unique to 3 $ —
Requirements specific permit programs are included in their
respective sections.
3.3.3.1 Legacy Permit For all permits migrated from or recreated from IMPACT's permitting subsystem currently
Numbers legacy applications, it must be possible to supports a searchable data element for legacy 3 $ —
record the original permit number, and to numbers in permit records

SERIAL 171125-RFP
search for and retrieve the record by using that
legacy number alone.
3.3.3.2 Permit All permit applications (include modification IMPACT supports a feature-rich permitting
Application and or renewal requests) are reviewed prior to subsystem and an integrated workflow
Review permit issuance. During the review process, the subsystem. IMPACT supports the entire
permit application must be assigned to an permitting process from creating, validating,
engineer or other designated staff based on and submitting applications through the permit
source, type of source, equipment, process, or construction and issuance process. The 3 $ —
type of permit. Staff assignments, processing processing is tracked through a detailed
statuses and dates must all be recorded. There workflow that explicitly tracks individual tasks
should also be a method for recording including start and end dates. IMPACT
prioritization of applications for review. provides a comprehensive series of validation
checks to ensure that permit writers, reviewers
and issuers are following agency business rules
3.3.3.3 Permit Types It must be possible to differentiate permits and IMPACT's permitting subsystem is built upon
applications based on status, type of permit, IMPACT's facility inventory subsystem which
and type of source. If, upon review, it is eliminates much of the need to re-enter data in
determined that a permit application was the event the applicant selected the incorrect
submitted for the incorrect permit type, it type of application. IMPACT permit
should be possible to transfer the information application user interface screens provide many 3 $ —
to the new permit type and to maintain a record convenience features - such as "jump-starting"
of the original permit application. the application by copying a previously
submitted one - that make it easy for the
applicant to provide the required information.
3.3.3.4 Permit In addition to the information noted in Section IMPACT supports a permit record that
Information and 3.2, permits must be able to include contains meta-data about the permit such as
Conditions information specific to that permit type (as public notice date, public hearing date, Rules
noted in the sections for individual permit applicability indicators, process checklists,
types, below) and to record all permit description, and notes. IMPACT also contains 3 $ —
conditions as determined by MCAQD staff. a customized file attachment capability. The
permit document containing the Terms and
Conditions is managed as one of these file
attachments (presumably, but not necessarily,
in Microsoft Word format).

SERIAL 171125-RFP
3.3.3.5 Permit Supervisors must be able to select individual IMPACT workflow subsystem supports this
Application permit applications for review, and random need. UNICON recommends including the
Supervisor samples of permit applications must be supervisor review as an explicit step in the
Review generated for supervisor review. Supervisors permitting workflow (it is for our other
must be able to log their reviews and to record clients). The supervisor has the option of
their comments and recommendations. reviewing the application, and marking it as 3 $ —
Supervisors must be able to return applications complete, or else marking it as skipped to
to intake or engineering staff for additional denote the fact that no review was performed.
work or to advance permit applications to the IMPACT workflow subsystem also supports
next processing stage. the "loop back" action to return the workflow
back to a previous task for rework.
3.3.3.6 Permit Permittees must be able to submit requests for IMPACT supports the ability to copy a
Revisions and revisions (minor or non-minor) to permits and previously submitted application and re-submit
Modifications renewals for permits. Revisions and renewals it as an amended application. This capability is
then proceed through the review and issuance available on both the internal system for
process. Note that more than one revisions or MCAQD users and on the portal for industry
modification to the same permit may be in users. Applicants wishing to request a minor
process at the same time. change can simply copy a previously submitted
application and mark it as a revision. Once 3 $ —
Designated MCAQD staff must have the submitted, IMPACT will create a permit and
ability to make administrative updates outside workflow instance to allow for MCAQD
of the normal review process when minor and processing but preserves the application's
non-substantive corrections need to be made. designation as an amended application. In these
cases, internal staff may elect to skip certain
steps in the workflow if the step is not
applicable or not warranted by a minor request.
3.3.3.7 Permit Every permit must have an expiration date. The IMPACT supports permit expiration dates.
Expiration Dates expiration dates should be calculated UNICON will add the automatic email
automatically based on the permit type and notification capability. 3 $8,800.00
date. An email notification of upcoming permit
expiration should be generated automatically.
3.3.3.8 Permit Versions Each version of every permit must be retained It is a fundamental design principle of
in the database (and not merely as a document). IMPACT that each permit application is
A system of version numbering must make it associated with a particular version of the
easy for staff to recognize each version of the facility inventory (Refer to the Executive
permit. Summary for a description of the versioning 3 $ —
capabilities of the facility inventory). Once the
Each version of a permit must be capable of application is submitted, the permit record is
retaining equipment lists, permit conditions, associated with the permit application and
technical information, diagrams, etc., specific therefore to the facility inventory version.

SERIAL 171125-RFP
to that version alone. IMPACT implements business rules that
prevent any of these records being changed
When a new version of a permit is created, all after they have been "locked". For example,
information from the ‘current’ version of the internal users cannot alter information in a
permit should initially populate the new submitted permit application. Nor can they edit
version. When details within the new version a preserved facility inventory. Once a permit
are changed, information in the older versions has been issued final, internal users cannot add,
of the permit must remain unaffected. change, or delete any of its data elements or
any of the attached documents (including the
When a permit is finalized (issued), all data issued permit document).
within that permit version must be locked such
that it cannot be changed.
3.3.3.9 Review of It should be possible to open multiple permits IMPACT places no restrictions on the number
Multiple Permits and/or multiple versions of the same permit at of web forms or MS Word documents open at
or Permit the same time to allow comparisons between the same time. Users can use the comparison 3 $ —
Versions permitted sources. feature of MS Word if desired to compare
document versions.
3.3.3.10 Record of It must be possible to record all rules, statutes, IMPACT stores permit documents as word
Applicable ordinances, and/or federal regulations; all processor documents - which MCAQD can
Rules, et al relevant sections thereof; and regulatory structure to meet their needs including
language associated with items in a permit. specifications of applicable rules and
regulations and associated regulatory language. 3 $8,800.00
IMPACT also supports data elements within
the permit record to indicate that the entire
permit is subject to particular rules, such as
PSD and Non-attainment NSR.
3.3.4 Dust Control (N/A — Section heading only) 6 $ —
3.3.4.1 Traditional Any activity capable of generating fugitive IMPACT does not currently support dust
Dust- dust (such as construction, earthmoving, control permits but UNICON can add support
Generating demolition, or weed abatement), regardless of for them in a manner consistent with the
Activities (Rule the size of the site, must comply with Rule 310 system's architecture. UNICON
310) and control potential dust. In addition, a dust implementation will retain the same permit 6 $53,800.00
control permit is required by Rule 310 for number across renewals and support variable
many types of sites, such as: activities that will permit durations.
disturb a surface area equal to or greater than
0.1 acre; bulk material handling; and the
demolition of buildings.

SERIAL 171125-RFP
3.3.4.1 Dust Control Dust control permits are valid for one year,
Permits after which a new permit may be issued for the
same site or project. It should be possible to
retain the same permit number when a new
permit is issued for the same site or project. In
order to allow for flexibility in the future, it is
also preferred that multiple permit durations
(e.g., six or 18 months) be available.
3.3.4.1 Site Information Applications include a dust control plan and a UNICON implementation of dust control
site map. It is important that site information permits will include the support for site
(including parcel information, site geometry, information.
site size, and site coordinates) is recorded 6 $8,800.00
accurately, is easily accessible to inspectors in
the field, and can be revised repeatedly as
permit revisions are made. (See section 3.1.7
regarding GIS functionality.)
3.3.4.1 Fees Fees are based on site size and may need to be UNICON implementation of dust control
recalculated when permit revisions are made. permits will include the ability to assess fees 6 $8,800.00
based on the site size.
3.3.4.1 Block Permits Block permits are a special instance of dust UNICON implementation of dust control
control permit that are issued for dust- permits will be designed to accommodate
generating activities that may occur at more support for block permits including the ability
than one location and/or may occur repeatedly. to upload site location lists in .xlsx or .csv
They are issued for routine operations (such as format
canal bank and road grading), maintenance
(such as weed control around a prison), and
expansion or extension of utilities, roads,
pipelines, and other linear projects. Block
permits require a dust control plan.
6 $35,200.00
Holders of block permits are required to notify
MCAQD at least three days in advance of
commencing dust-generating operations.
Notices must include site locations, size, type
of activity, and start date. It must be possible to
incorporate those notices into block permit
records. Site location lists are often lengthy
(especially in the case of roadway or utility
projects). It is strongly preferred that there be a
mechanism for uploading site information from

SERIAL 171125-RFP
.xlsx or .csv files submitted by the permit
holder.
3.3.4.2 Non-Traditional The following sources of dust must comply UNICON can identify common areas when
Dust-Generating with Rule 310.01: vehicle use in open areas designing support for traditional dust control
Activities (Rule and vacant lots; open areas and vacant lots; permits so support for non-traditional dust
310.01) unpaved parking lots; unpaved roadways generating activities will be straightforward.
(including alleys); livestock activities; erosion-
caused deposition of bulk materials onto paved
surfaces; and easements, rights-of-way, and
access roads for utilities (transmission of
electricity, natural gas, oil, water, and gas).
Although these sources are not required to have
dust control permits, they still must comply 6 $26,400.00
with dust control regulations. It must be
possible to create records for non-traditional
sources so that ownership, compliance history
and site location may be recorded. Non-
traditional source records must be searchable
by location (parcel number and/or coordinates).
Non-traditional sources may also transform
into traditional sources. There should be a way
to associate such non-traditional source records
with the subsequent dust control permit
records.
3.3.4.3 Gravel Processing plants that mine, excavate, separate, Based on the description in the RFP, these
Operations, combine, crush or grind any nonmetallic facilities would fall under IMPACT's Non-
Concrete and/or mineral are governed by Rule 316. Title V permitting program - perhaps with
Asphalt Plants & ‘Nonmetallic minerals’ includes (but is not special rules for required attachments (e.g.,
Related limited to) crushed and broken stone, sand and dust control plan), and specific validation
Activities (Rule gravel, clay, rock salt, gypsum, sodium checks on the corresponding facility inventory
316) compounds, and mixtures of these minerals - such as requiring all of the site location and 6 $26,400.00
such as concrete and asphalt. Some types of geometry information to be present.
facilities or activities governed by Rule 316
are: crushing and screening of nonmetallic
minerals; sand and gravel operations; asphalt
plants; and concrete batch plants. A permit is
required for all types of facilities and activities
governed by Rule 316. Most of these facilities

SERIAL 171125-RFP
operate under Non-Title V permits (as
described in section 3.3.8.2).
Applications include a dust control plan,
process information, equipment list, control
device information, and a site map. It is
important that site information (including
parcel information, site geometry, site size, site
coordinates, and the coordinates of emissions
points) is recorded accurately, is easily
accessible to inspectors in the field, and can be
revised repeatedly as permit revisions are
made. (See section 3.1.7 regarding GIS
functionality.)
3.3.5 Portable Portable sources (such as crushers) are subject
Sources to Rule 200. If a source operates entirely within
Maricopa County, it will have a permit issued
by MCAQD. If it operates both within and
outside Maricopa County, it will have a permit 7 $ —
issued by the Arizona Department of
Environmental Quality (ADEQ). Even if it has
an ADEQ permit, the owner of the source must
still notify MCAQD whenever the source is
located in Maricopa County.
3.3.5.1 Portable Source Portable Source records must be able to record IMPACT provides support for portable point
Permit Numbers either an MCAQD permit number or an ADEQ source facilities. UNICON will add support for 7 $8,800.00
permit number. recording an ADEQ permit number.
3.3.5.2 Portable Source Portable Source records must be able to record IMPACT supports an address history for
Location all source locations within Maricopa County portable source including the effective date of
Notifications (including dates at those locations, addresses, the move. UNICON will add the data element
site information, latitude/longitude, and for "move out" date
processes performed) and to retain the history
of locations of each portable source. They must 7 $8,800.00
also be able to record dates when sources are
moved out of Maricopa County. Locations
outside of Maricopa County are not recorded
by MCAQD, but sources are required to notify
MCAQD when sources are removed from the
county.

SERIAL 171125-RFP
3.3.6 Rapid The Rapid Response Program triggers IMPACT does not currently support this record
Response notifications when air quality monitoring type although the requirements for it look to be
equipment report unusually high particulate straightforward. UNICON will add support for
matter concentrations. When a Rapid Response it.
notification is broadcast, the department will
ask air quality permit holders with dust
generating activities to inspect their site as
soon as possible and employ Best Available
Control Measures to stabilize all disturbed soils
to reduce blowing dust. MCAQD inspectors 8 $26,400.00
will canvass the area to ensure compliance with
its dust control standards.
Rapid Response records must be able to record
monitor locations (sometimes more than one
for a single event) that have high readings,
record inspector activity and comments, record
information of suspected sources, and generate
standard e-mail notifications from data
captured in the field.
3.3.7 Stationary A stationary source may have a Title V permit
Sources (for major sources), Non-Title V permit (for
non-major sources), or an Authority to Operate
(ATO) under a General Permit. In addition, a
source with the emissions potential to be a 3 $ —
Title V source may be a Synthetic Minor
source by refraining from emissions. All
permits have recordkeeping, monitoring and
reporting conditions.
3.3.7.1 Title V Most Title V facilities regulated by MCAQD IMPACT has extensive support for Title V
are large generating stations, large facilities, Title V permit applications, Title V
manufacturing facilities or large landfills. Title permits, and the associated workflows.
V permits are usually complex, require large
amounts of documentation, have a relatively
high frequency of modifications, and tend to be 3 $8,800.00
renewed regularly and remain open for very
long periods of time. Permit information may
include, but is not limited to, equipment lists
(including information that identifies
individual pieces of equipment), emissions

SERIAL 171125-RFP
control equipment, emissions, emissions
factors, SIC or NAICS codes, process
descriptions, site diagrams, and operations and
maintenance plans. Permit conditions may
include, but are not limited to, emissions limits,
operating requirements, control technologies,
and recordkeeping requirements. Summary
information must be generated for public
notices whenever there is a permit application,
modification request or renewal.
New major sources or major modifications to
existing sources may require a Prevention of
Significant Deterioration (PSD) permit. PSDs
require information and workflows similar to
those for Title V permits, and require and air
quality analysis and additional impact analyses.
3.3.7.2 Non-Title V Non-Title V facilities include a wide variety of IMPACT has extensive support for Non-Title
business, industry and activity types. Non-Title V facilities, Non-Title V permit applications,
V permits range from fairly simple to quite Non-Title V permits, and the associated
complex, require moderate amounts of workflows.
documentation, have a moderate frequency of
modifications, and tend to be renewed
regularly and remain open for long periods of
time. Permit information may include, but is
not limited to, equipment lists (including
information that identifies individual pieces of
equipment), emissions control equipment, 3 $8,800.00
emissions, emissions factors, SIC or NAICS
codes, process descriptions, site diagrams, and
operations and maintenance plans. Permit
conditions may include, but are not limited to,
emissions limits, operating requirements,
control technologies, and recordkeeping
requirements. Summary information must be
generated for public notices whenever there is
a permit application, modification request or
renewal.

SERIAL 171125-RFP
3.3.7.3 General Permits General Permits are Non-Title V permits held IMPACT supports a permitting program called
by MCAQD. Regulated sources operate under "Permit By Rule" which is a close match to
an Authority to Operate (ATO) under the MCAQD's requirements for General Permits.
appropriate General Permit. (There are UNICON will re-label our PBR screens and
presently nine MCAQD general permits, with make any other adjustments as necessary.
more in preparation.) General Permits are
renewed every five years. All ATOs under a
General Permit expire on the date that the 3 $17,600.00
General Permit under which they operate
expires, regardless of the date when they were
issued, and may be reissued under the renewed
General Permit. ATOs are less complex than
Title V or Non-Title Permits, but may still
require the same kinds of information. ATOs
do not require public notices when there is an
application, modification request or renewal.
3.3.7.4 Conversion Sources may change from one type of IMPACT has extensive support for
among Permit stationary source permit to another, sometimes maintaining facility inventory history and
Types later reverting to their original permit type or permitting history. When a source changes
even making multiple changes between types. types, a new permit (of the new type) is issued,
The history of the source, including permit and is associated to that facility. 3 $ —
conditions and compliance history, must be
preserved when those changes are made. The
history of permit types, permit numbers, dates
of changes, and notes about changes must be
recorded.
3.3.8 Performance Performance tests are conducted according to IMPACT supports stack test records including
Test established procedures in order to quantify the ability to create, edit, validate, and submit
emissions and provide an objective means for them. There is support on both the internal and
determining compliance with established portal systems. When a user submits a stack
emission limits. It is important that each test be test, the system creates a single task Workflow
performed in a valid, representative manner to for agency staff to review it. IMPACT stack
ensure that the results provide an accurate test record includes numerous dates 5 $8,800.00
representation of a source’s actual emissions. (scheduled, tested, received, reviewed),
equipment lists (emission units, processes,
Performance test records must be able to control equipment, and monitoring equipment),
proactively manage equipment lists and test pass fail criteria, attached files, comments,
schedules, schedule and track audits based on category, testing method, witnesses, etc.
test and permit criteria, record maintenance and IMPACT also supports a "legacy" indicator for
testing schedules, record test criteria submitted stack tests that allows agency users to enter

SERIAL 171125-RFP
by permit holders based on permit and legacy stack test data, bypassing some of the
equipment type, record test results, record system's stringent validation and quality
pass/fail and data based on test results, and control checks.
record updated emission factors.
3.3.9 Asbestos This section is for informational purposes only. IMPACT does not currently support this but
It is not currently MCAQD’s plan to move this UNICON can add the support.
program into the proposed solution.
MCAQD regulates all asbestos renovation and
demolition within Maricopa County, including
all demolitions and regulated renovation
activities containing friable asbestos-containing
material greater than or equal to 160 square
feet, 260 linear feet, or 35 cubic feet as
determined by an Asbestos Hazard Emergency
Response Act (AHERA) certified asbestos
building inspector prior to demolition or 6 $35,200.00
renovation.
MCAQD receives renovation and demolition
notices, and inspects for asbestos removal
compliance. It must be able to gather site
information (including location and building
type), work type, work schedule (for inspection
purposes), and removal methods. Revisions are
common as work progresses.
Fees are based on the amount of asbestos to be
removed and may need to be recalculated when
revisions are submitted.
3.3.10 Diesel Idling Diesel idling is, in most circumstances, IMPACT does not currently support this but
prohibited by Maricopa County ordinance. A UNICON can add the support.
relatively simple record type is needed to 8 $26,400.00
record diesel idling violations (including date,
time, location, violator information, and details
of the violation) and to assess penalties.

SERIAL 171125-RFP
3.3.11 Fireplaces 7 $ —
3.3.11.1 Residential To reduce particulate pollution, the use of
Fireplaces residential fireplaces is prohibited on declared
No Burn Days, unless the residence has 7 $26,400.00
received an exemption. MCAQD staff patrol
selected residential areas on some of those No
Burn Days.
Fireplace Fireplace exemption applications must be IMPACT does not currently support this but
Exemptions processed, approved or denied, and recorded. UNICON can add the support.
3.3.11.1 Burn Patrol The staff assignments (dates and times) and IMPACT does not currently support this but
geographic areas covered during a burn patrol UNICON can add the support.
route must be recorded. It should be possible to
capture addresses of possible fireplace 7 $26,400.00
emissions sources so that outreach materials
can be distributed to them, and to capture the
addresses of sources found to be in violation.
3.3.11.1 Pilot Retrofit MCAQD is instituting a pilot program to IMPACT does not currently support this but
Program retrofit residential fireplaces. It is expected that UNICON can add the support.
the information that will need to be recorded
will include, at least: the geographic areas 7 $26,400.00
canvassed; names, addresses and contact
information of program participants; dates that
retrofit work is assigned and completed; and
types of retrofit.
3.3.11.2 Commercial/Inst Fireplaces in commercial or institutional IMPACT does not currently support this but
itutional settings are not required to have permits. UNICON can add the support.
Fireplaces However, the use of commercial or
institutional fireplaces is prohibited on declared 7 $8,800.00
No Burn Days. It must be possible to create an
unpermitted source record for commercial or
institutional fireplaces to track inspections
and/or violations.
3.3.12 MCAQD Several MCAQD programs are managed in a
Optional solution other than EMS. It is not MCAQD’s
Programs immediate plan to move these programs into
the proposed solution. It is at the option of the N/A N/A
Respondent to provide solutions for the
following programs and to detail their pricing
separate from the total proposal price.

SERIAL 171125-RFP
3.3.12.1 Dust Control MCAQD conducts a basic dust control training IMPACT does not currently support this but
Training program for persons involved in dust- UNICON can add the support.
generating activities, and a comprehensive
training program for dust control officers.
There are separate programs for Rule 310 and
Rule 316 dust control certification.
Certifications are valid for three years from
date of issue. 8 $26,400.00
Classes are held in English and Spanish.
Classes are offered at MCAQD’s home office,
online, and at customer locations. There are
different fees for basic and comprehensive
classes, and each of those is different still for
classes held at customer locations. Fees may be
charged to participants or to their employers.
3.3.12.2 Open Burn MCAQD regulates many kinds of open IMPACT does not currently support this but
outdoor burning, such as scrub vegetation UNICON can add the support.
clearance, destruction of tumbleweeds,
agricultural disease or pest prevention,
firefighting training, and watershed
rehabilitation. Applications include 7 $35,200.00
information about the type of proposed burn,
requested date range and locations(s). Sites are
inspected prior to issuance of a burn permit.
MCAQD must then be notified prior to the
actual burning activity. An application fee is
required.
3.3.12.3 Subcontractor Any subcontractor who is engaged in dust- IMPACT does not currently support this but
Registration generating operations at a site that is subject to UNICON can add the support.
a Maricopa County dust control permit is
required to register with MCAQD prior to
performing dust-generating activities on a site
where the subcontractor is not the permit 8 $35,200.00
holder. A registration may be issued to an
individual, a partnership, a limited liability
company, or a corporation. Registration
requires an annual fee and is subject to legal
presence verification.

SERIAL 171125-RFP
3.3.12.4 Tanker Truck All gasoline delivery vessels must first pass the IMPACT does not currently support this but
Certification Maricopa County Pressure Test before UNICON can add the support.
delivering or onloading gasoline, and must
pass the test each year thereafter. Tests are
conducted by certified testing facilities. Test 8 $35,200.00
results are submitted to MCAQD. Upon
submission of passing certification test results
and payment of a registration fee, operators are
provided with vehicle details that display the
certification number.
3.4 Compliance Compliance, inspection and enforcement
and activities may be related to any permit type and
Enforcement to unpermitted sources. This section includes
Requirements descriptions of MCAQD’s compliance,
inspection and enforcement activities, and a
high-level overview of their requirements (to
the extent that those requirements extend
beyond those described in section 3.2). N/A N/A
MCAQD recognizes that there are many
possible ways to design a solution that will
meet its requirements. Required data elements
and functionality are described generally
below, while remaining, as much as is possible,
agnostic about the design of proposed
solutions.
3.4.1 Compliance (N/A — Section heading only) 5 $ —
and Inspections
3.4.1.1 Creation and (N/A — Section heading only)
Scheduling of 5 $ —
Inspections

SERIAL 171125-RFP
3.4.1.1 Creation of The proposed solution should have processes IMPACT provides extensive support for
Inspections for automating the creation and scheduling of facility (point source) inspections. The support
inspections using any of the following criteria: includes the ability to create, edit, and delete
inspector, location of source, last inspection inspection records. The records contain many
type, date of last inspection, compliance data elements including staff assigned, quarter
history, permit type, and/or inspection zone. It scheduled, inspection type, inspector,
must also be possible to schedule re- completed date, report completed date, sent to
inspections, perform ad-hoc inspections and EPA date, associations with site visit and stack
manually create inspections records. test records, attachments (files), and notes.
The capability also includes an inspection
scheduler feature which has been designed to
allow users to schedule inspections for an
upcoming federal fiscal year. The scheduler
allows users to specify search criteria to help 5 $26,400.00
select the targeted set of facilities that need to
be inspected. After progressing through the
search process and selecting the staff person
assigned to each inspection, the system will
create "scheduled" (future) inspection records
in a bulk manner for all selected facilities. The
scheduled inspection records are created with
the designated target quarter and assigned
inspector. Staff member can search for and
review their upcoming inspections.
UNICON will need to add support for non-
point source facilities to IMPACT inspection
capabilities.
3.4.1.1 Pre-Populated Inspection records should include inspection IMPACT supports many of these requirements
Information zone and map area based on for point source facilities. UNICON will meet
township/section/range. New inspection all of the requirements and provide support for
records should be pre-populated with current non-point source sites.
permit information. (Existing inspection
records should not be updated if the permit 5 $26,400.00
information is updated.) It should be possible
to update pre-populated information if the
inspector determines that it was not valid at the
time of the inspection. When updates are
required, they should update all relevant
records.

SERIAL 171125-RFP
3.4.1.1 Assigning Inspectors should be able to be assigned to an IMPACT supports separate data fields for
Inspections inspection task through completion, review, assigned staff and inspector (which may be
and approval, but it should also be possible to different). IMPACT will need some tweaking 5 $8,800.00
reassign inspections at any point in the to support multiple inspectors.
inspection process. Multiple inspector names
are required on some inspections.
3.4.1.1 Inspection Multiple geographical locations may be UNICON will design support for the "pre-
Location associated to a permit. It should be possible to populated information" item with this
Information associate contiguous parcels with the same capability in mind.
owner with aggregate acreage reporting.
Aggregate acreage is used for contiguous 5 $5,280.00
vacant lots with the same owner (e.g., an owner
with three contiguous 5 acre parcels would
have an inspection frequency for 10 acres and
greater).
3.4.1.2 Performing (N/A — Section heading only) 5 $ —
Inspections
3.4.1.2 Recording The inspector must be able to record all time IMPACT's timesheet subsystem will meet
Inspection Time spent on an inspection (including non- MCAQD's needs.
continuous blocks of time that occur on several
different days before, during and after the on- 5 $8,800.00
site inspection) and to differentiate among
types of effort (e.g., office time for reviewing
documents or field time for site inspections).
3.4.1.2 Inspection It should be possible to generate inspection IMPACT does not currently support this but
Rights and Other rights documents (pre-populated with permit or UNICON will add the support.
Documents source information where available)
electronically and to capture electronic 5 $26,400.00
signatures. The proposed solution must also
support emailing or printing of inspection
records, inspection rights and other documents
in the field.
3.4.1.2 Recording Inspectors must be able to gather inspection IMPACT provides an inspection record with
Inspection Data information specific to a permit type, many data elements. UNICON will configure
equipment type, process, or applicable rule. It to meet MCAQD's needs.
must be possible to record information on 5 $8,800.00
multiple pieces of the same type of equipment
during an inspection and to record identifying
information for each piece of equipment.
Inspectors should be able to record test method

SERIAL 171125-RFP
results and to attach various kinds of files
(including photographs and video recordings)
to an inspection.
3.4.1.2 Rules, Sections It must be possible to record the rule (and/or IMPACT does not currently support this but
and Descriptions statute, ordinance or federal regulation), UNICON will add the support.
section(s) and regulatory language associated
with items in an inspection. These should be
available through pre-configured drill-downs.
The content of these drill-downs is revised 5 $26,400.00
regularly. Specify the method for updating
these drill-downs (e.g., manual update and/or
uploading .csv files). It is preferable that
inspectors have the option to choose between
standardized regulatory language and manually
entered descriptions.
3.4.1.2 Inspections on Not all inspections are completed on a single IMPACT supports the entry of multiple
Multiple Days day. It must be possible to continue inspections calendar days for an inspection. 5 $ —
and to record information from a multi-day
inspection as a single inspection.
3.4.1.3 Mobile Device MCAQD does not presently have, but is very UNICON believes there are many potential
Capabilities interested in, capabilities to record inspections implementations to achieve a mobile device
on mobile devices such as phones and tablets. capability and would need to discuss the
Mobile capabilities may include: the ability to requirements and review options with the
record inspections; the ability to retrieve County before proposing a solution and
reference information; field navigation and corresponding cost.
routing; inspection schedule management; Currently, IMPACT's user interface renders
communications with MCAQD and with accurately on all mobile devices UNICON has X N/A
regulated sources; and the ability to take a tested (both Android and iOS). However,
photo and attach it to a record. Onscreen IMPACT is not optimized for display on small-
controls and navigation should be touch screen format devices.
compatible: users should not be required to use
a mouse or keyboard. Windows is the county
preferred operating system, but some IOS
systems are used.
3.4.1.4 Results of It must be possible to close an inspection with IMPACT currently provides a text box to enter
Inspections a result of ‘In violation’ or ‘No violations the inspection's compliance status. Based on
noted’ (or equivalent terms). It must be MCAQD's desires, UNICON can alternately 5 $8,800.00
possible, after an inspection, to hold an (or in addition to) implement a drop-down list
inspection open with a provisional result of
‘Pending determination’ or ‘Inspection

SERIAL 171125-RFP
continued’ (or equivalent terms). All results
and changes to results must be recorded.
3.4.1.5 Supervisor (N/A — Section heading only)
Review and 5 $ —
Approval
3.4.1.5 Selection of Supervisors review a percentage of compliant IMPACT supports the ability to create ad-hoc
Inspections for inspections and all inspections that result in "To Do" list items (To Do list items are
Review violations. It should be possible to select standard workflows that consist of only one
samples of compliant inspections and to component task). Staff members completing an
prioritize inspections for review. It should also inspection record may create a To-Do list item
be possible to select individual inspections for for the supervisor.
review. IMPACT also supports a flexible search 5 $5,280.00
mechanism for inspection records that includes
search criteria such as inspector, completed
status (Y/N), and scheduled and completed
Federal Fiscal Year (FFY). Supervisors can
search recently completed inspections and
select specific records to review
3.4.1.5 Supervisor Supervisor reviews must be recorded, Based on the description in the RFP, UNICON
Review Process including comments, recommendations, date will implement a brief workflow consisting of
and time of review, and supervisor name. 2-4 tasks (depending on MCAQD's business
Reviewed inspections may be approved and process). IMPACT can automatically create the
moved to the next step in their process, or they workflow once the inspection record has been 5 $26,400.00
be sent back to the inspector for revisions. created. This will allow MCAQD users to use
Revised inspections may be returned to the the capabilities of the workflow subsystem -
supervisor for further review. It should be including the ability to skip, look-back, and
possible to save versions of reviewed change task assignments, all while keeping
inspections when revisions are required. detailed processing time records.
3.4.1.5 Approval of It should be possible to perform approvals IMPACT does not currently support batch
Reviewed through a batch, set or group update process or approvals for inspections. UNICON will add
Inspections to approve inspections individually. The support for this to IMPACT.
inspection record should be record whether the
approval was part of a batch process or was an 5 $ —
individual approval. Once supervisors have
reviewed and approved inspections, it should
not be possible to change the data in those
inspections.

SERIAL 171125-RFP
3.4.1.6 Creation of It should be possible to create, generate and IMPACT currently supports the creation of an
Enforcement pre-populate an enforcement case from enforcement action record directly from an 5 $ —
Cases inspection findings. inspection record.
3.4.1.7 Inspection Inspection data must be accessible for standard IMPACT's standard WF reports will support
Reporting and ad hoc reports, such as workload analyses, inspection workflows. In addition, the
rule effectiveness studies, and summaries of inspection records are stored in the IMPACT's 5 $ —
inspection and outcomes by applicable rules. underlying SQL Server database and are thus
accessible to users wanting to write ad hoc
reports
3.4.2 Enforcement (N/A — Section heading only) 5 N/A
3.4.2.1 Creation and Enforcement cases may be created IMPACT supports a record type of
Content of automatically by inspections with violations enforcement action. The record supports
Enforcement noted, or they may be created manually. All several data elements including violation start
Cases enforcement cases must incorporate or include and end dates, docket number, enforcement
references to any relevant inspections or other action type, referral type, description,
documents. Enforcement cases must include environmental impact flag (Y/N),
references to applicable rules and rule language Supplemental Environmental Project flag
for reporting and research purposes. (Y/N), and penalty amount ($). Our EA record
also includes a flexible mechanism for 5 $8,800.00
capturing a sequence of "events" (e.g., "Draft
SA mailed to Company", or "Referred to AG").
The administrator user may define the set of
events including specifications for predecessor
events. IMPACT captures the date and user id
for each event.
Users can associate correspondence records
with the EA record, and attach files and notes.
3.4.2.2 Penalties and The proposed solution must support IMPACT supports the capture of a penalty
NFAs assessment and invoicing of enforcement amount. The disposition of NFA will be
penalties where applicable, including the handled by an event of that type in the record's 5 $26,400.00
management of payment plans. It must also be list of events.
able to close records with a disposition of No
Further Action (NFA).
3.4.2.3 Negotiations and The proposed solution must be able to track IMPACT enforcement action record supports a
Referrals time and events in enforcement negotiations. It series of "events". Each event has a date and a
must also be able to record referrals to the user id associated with it. Events may include
County Attorney or to the EPA. It should be referrals to other agencies. 5 $17,600.00
possible to report on enforcement case If MCAQD needs to record "effort hours"
processing time with or without including spent on an enforcement action, then UNICON
negotiations and referrals. recommends IMPACT's timesheet entry

SERIAL 171125-RFP
capability to track this data.
3.4.2.4 Orders of The proposed solution should be able to IMPACT does not currently support this but
Abatement by produce and print standardized Orders of UNICON can add the support described in the
Consent Abatement by Consent (OACs). An OAC RFP using IMPACT's template-based MS
should be a potential result of an enforcement Word document generation capability. The EA 5 $8,800.00
case. record supports IMPACT's generalized "file
attachment" feature - providing a logical place
to store the OAC document.
3.4.2.5 Supplemental MCAQD has a program that allows IMPACT enforcement action record supports
Environmental Supplemental Environmental Projects (SEPs) the recording of an SEP associated with the
Projects in lieu of some penalties in enforcement cases. action. UNICON will add some additional
The solution must be able to record SEPs, their features to the EA record to meet MCAQD's 5 $17,600.00
value, and milestones in completing a SEP. needs in tracking the milestones associated
The dates of completion of milestones must be with an SEP.
recorded.
3.4.2.6 Settlements Settlement information must include tracking IMPACT enforcement action record does not
of total and current value of the settlement, currently support the capture of a settlement 5 $17,600.00
supplemental environmental project value and amount. UNICON will add additional data
milestones, abeyance value, and case events. fields to the EA record.
3.4.2.7 Results of Results of enforcement cases should be IMPACT supports explicit linking between EA
Enforcement recorded in related inspection records. records and associated correspondences 5 $ —
Cases

SERIAL 171125-RFP
EXHIBIT F
PROJECT CHANGE REQUEST FORM
This form shall be used to document any material change to the SOW that results in a measurable change in scope
from that defined in the Contract. It shall serve as a guideline and may be modified to suit the needs of the project.
This form shall be filled out and signed by Contractor and presented to the County for approval. Upon approval, the
County will then counter sign the form and return one copy to the Contractor.
Project Change Request (PCR) Number (ID):
Effective Date:
Effect of Change:
UNICON International Activities:
Maricopa County Activities:
UNICON International Deliverables:
Maricopa County Deliverables:
Acceptance Criteria for Deliverables:
Reason for Change/Notes:
Associated Cost:
Contract Price Adjustments:
Original Value
Note: Original Value is the amount listed as Amounts for previous PCRs
the “TOTAL NOT TO EXCEED FOR Original Amount for //////////////////////////////////
INITIAL FIVE (5) YEAR TERM” this Requirement //////////////////////////////////
(Ref: SERIAL 171125-RFP, EXHIBIT A, Revised Amount for //////////////////////////////////
PRICE AGREEMENT). this Requirement //////////////////////////////////
Net Change for this Requirement
New Value
UNICON International Agreement – Signature/Title/Date:
___________________________ __________________________ _______________________ ____________
Signature Name (Print) Title Date
Maricopa County Agreement – Signature/Title/Date:
___________________________ __________________________ _______________________ ____________
Signature Name (Print) Title Date
___________________________ __________________________ _______________________ ____________
Signature Name (Print) Title Date
___________________________ __________________________ _______________________ ____________
Signature Name (Print) Title Date

SERIAL 171125-RFP
EXHIBIT G
DELIVERABLE ACCEPTANCE FORM
Deliverable Acceptance Form
Work Package Deliverable Name: Deliverable Number:
SOW name:
Deliverable Owner: Deliverable Implementer: Scheduled Fulfillment Date:
The role that signs off for this The role responsible for the dd-mm-yyyy
deliverable. realization of this deliverable.
Deliverable Description:
Describe the deliverable in specific and measurable terms.
Acceptance Criteria:
List the acceptance criteria that reflect successful realization of this deliverable.
Ensure that acceptance criteria are specific, measurable, agreed, realistic and timely.
Back-Out Plan:
Specify the process and all required resources that are initiated in case the deliverable is deemed a
failure.
Deliverable Dependencies (if applicable):
List all the dependencies that affect this deliverable. Differentiate between prerequisite deliverables (that
is, deliverables required before this deliverable can be realized) and dependent deliverables (deliverables
that can be realized only if this deliverable is realized).
Required Resources (if applicable):
Specify the documentation, technology, process and people that are required to realize this deliverable.
Installation Document (if applicable):
Document the provided detailed steps for installation. It is a common document provided by application
development to production.
Handover Document (if applicable):
Document all configuration item (CI) artifacts. Differentiate between CIs per group that owns these CIs —
for example, handover of application configuration definitions and settings by the application development
group to the application maintenance groups responsible for the involved or affected applications.
Involved or Affected CIs (if applicable):
List all the CIs that are affected by the deliverable.
Changes to Involved or Affected CIs (if applicable):
Describe per CI, or group of CIs, any changes to the CIs that result from the realization of this
deliverable.
Approved or Rejected by Deliverable Owner:
Approved
Rejected
Signature:...............................................
Name:......................................................
Date:.........................................................