13133-RFP SIGNED CONTRACT.PDF

CONTRACT PURSUANT TO RFP
SERIAL 13133-RFP
This Contract is entered into this 7th day of May, 2014 by and between Maricopa County ("County"), a political
subdivision of the State of Arizona, and Data Transfer Solutions/VUEWorks, a Florida corporation ("Contractor")
for the purchase of asset management and maintenance software application services.
1.0 CONTRACT TERM:
1.1 This Contract is for a term of five (5) years, beginning on the ih day ofMay, 2014 and ending the
31st day ofMay, 2019.
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) years, (or at the County's sole
discretion, extend the contract on a month-to-month basis 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 thirty (30) calendar days prior to the expiration of the original contract term, or any
additional term thereafter.
2.0 PRICE ADJUSTMENTS:
Any request for price adjustments must be submitted sixty (60) days prior to the current Contract expiration
date. Requests for adjustment in cost of labor and/or materials must be supported by appropriate
documentation. If County agrees to the adjusted price, County shall issue written approval of the change.
The reasonableness of the request shall be determined by comparing the request with the (Consumer Price
Index) or by performing a market survey.
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.
3.3 INVOICES:
3.3.1 The Contractor shall submit one (1) legible copy of their detailed invoice before
payment(s) can be made. 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
• County purchase order number
• Invoice number and date
• Payment terms
• Description of Purchase (services)
• Pricing per unit of service

• Extended price
• Total Amount Due
• Milestone Deliverables
3.3.2 Problems regarding billing or invoicing shall be directed to the County 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
3.3.4 EFT payments to the routing and account numbers designated by the Contractor shall
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 STRATEGIC ALLIANCE for VOLUME EXPENDITURES ($AVE):
3.4.1 The County is a member of the $AVE cooperative purchasing group. $AVE includes the
State of Arizona, many Phoenix metropolitan area municipalities, and many K-12 unified
school districts. Under the $AVE Cooperative Purchasing Agreement, and with the
concurrence of the successful Respondent under this solicitation, a member of $AVE
may access a contract resulting from a solicitation issued by the County. If the
Contractor does not want to grant such access to a member of $AVE, please so state in
your proposal. In the absence of a statement to the contrary, the County shall assume that
the Contractor wishes to grant access to any contract that may result from this Request
for Proposal.
3.5 INTERGOVERNMENTAL COOPERATIVE PURCHASING AGREEMENTS (!CPA's)
3.5.1 County currently holds ICP A's with numerous governmental entities throughout the State
of Arizona. These agreements allow those entities, with the approval of the Contractor,
to purchase their requirements under the terms and conditions of the County Contract.
Please indicate on Exhibit A, your acceptance or rejection regarding such participation of
other governmental entities. Your response shall not be considered as an evaluation factor
in awarding a contract
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 shall provide Contractor's personnel with adequate workspace
for consultants and such other related facilities as may be required by Contractor to can·y out its
contractual obligations.
6.0 TERMS and CONDITIONS:
6.1 INDEMNIFICATION:
6.1.1 To the fullest extent permitted by law, Contractor shall defend, indemnify, and hold
harmless County, its agents, representatives, officers, directors, officials, and employees
from and against all claims, damages, losses and expenses, including, but not limited to,
attorney fees, court costs, expert witness fees, and the cost of appellate proceedings,
relating to, arising out of, or alleged to have resulted from the negligent acts, errors,
omissions, mistakes or malfeasance relating to the performance of this Contract.
Contractor's duty to defend, indenn1ify and hold harmless County, its agents,
representatives, officers, directors, officials, and employees shall arise in connection with
any claim, damage, loss or expense that is caused by any negligent acts, errors, omissions
or mistakes in the performance of this Contract by the Contractor, as well as any person
or entity for whose acts, errors, omissions, mistakes or malfeasance Contractor may be
legally liable.
6.1.2 The amount and type of insurance coverage requirements set forth herein shall 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 INSURANCE:
6.2.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.2.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.2.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.
6.2.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.2.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.2.6 County reserves the right to request and to receive, within 10 working days, certified
copies of any or all of the herein required insurance certificates. County shall not be
obligated to review policies and/or endorsements or to advise Contractor of any
deficiencies in such policies and endorsements, and such receipt shall not relieve

Contractor from, or be deemed a waiver of County’s right to insist on strict fulfillment of
Contractor’s obligations under this Contract.
6.2.7 The insurance policies required by this Contract, except Workers’ Compensation, shall
name County, its agents, representatives, officers, directors, officials and employees as
Additional Insureds.
6.2.8 The policies required hereunder, except Workers’ Compensation, 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.2.9 Commercial General Liability:
Commercial General Liability insurance and, if necessary, Commercial Umbrella
insurance with a limit of not less than $1,000,000 for each occurrence, $2,000,000
Products/Completed Operations Aggregate, and $2,000,000 General Aggregate Limit.
The policy shall include coverage for bodily injury, broad form property damage,
personal injury, products and completed operations and blanket contractual coverage, and
shall not contain any provision which would serve to limit third party action over claims.
There shall be no endorsement or modification of the CGL limiting the scope of coverage
for liability arising from explosion, collapse, or underground property damage.
6.2.10 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 under this Contract.
6.2.11 Workers’ Compensation:
6.2.11.1 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.
6.2.11.2 Contractor waives 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 pursuant to
this Contract.
6.2.12 Certificates of Insurance.
6.2.12.1 Prior to commencing work or services under this Contract, Contractor shall have
insurance in effect 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 be made available to the County upon
ten (10) business days. BY SIGNING THE AGREEMENT PAGE THE
CONTRACTOR AGREES TO THIS REQUIREMENT AND FAILURE
TO MEET THIS REQUIREMENT shall RESULT IN CANCELLATION
OF CONTRACT.
6.2.12.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.2.12.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.2.13 Cancellation and Expiration Notice.
Insurance required herein shall not be permitted to expire, be canceled, or materially
changed without thirty (30) days prior written notice to the County.
6.3 WARRANTY OF SERVICES:
6.3.1 The Contractor warrants that all services provided hereunder shall 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.3.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.4 INSPECTION OF SERVICES:
6.4.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.4.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 shall not unduly delay the work.
6.4.3 If any of the services do not conform with Contract requirements, County may require the
Contractor to perform the services again in conformity with Contract requirements, at no
increase in Contract amount. When the defects in services cannot be corrected by re-
performance, County may:
6.4.3.1 Require the Contractor to take necessary action to ensure that future
perfonnance confom1s to Contract requirements; and
6.4.3.2 Reduce the Contract price to reflect the reduced value of the services performed.
6.4.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.4.4.1 By Contract or otherwise, perform the services and charge to the Contractor any
cost incurred by County that is directly related to the performance of such
service; or
6.4.4.2 Terminate the Contract for default.
6.5 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:
Jason Amadori, GISP
VUEW orks, LLC
3680 Avalon Park Blvd. E. Suite 200
Orlando, Florida 32828
6.6 REQUIREMENTS CONTRACT:
6.6.1 Contractor signifies its understanding and agreement by signing this document that this
Contract is a requirements contract. This Contract does not guarantee any purchases shall
be made (minimum or maximum). Orders shall only be placed when County identifies a
need and issues a purchase order or a written notice to proceed.
6.6.2 County reserves the right to cancel purchase orders or notice to proceed within a
reasonable period of time after issuance. Should a purchase order or notice to proceed be
canceled, the County agrees to reimburse the Contractor for actual and documented costs
incurred by the Contractor. The County shall not reimburse the Contractor for any
avoidable costs incurred after receipt of cancellation, or for lost profits, or shipment of
product or performance of services prior to issuance of a purchase order or notice to
proceed.
6.6.3 Purchase orders shall be cancelled in writing.
6.7 TERMINATION FOR CONVENIENCE:
The County reserves the right to terminate the Contract~ in whole or in part at any time, when in
the best interests of the County without penalty or recourse. Upon receipt of the written notice,
the Contractor shall immediately stop all work, as directed in the notice, notify all subcontractors
of the effective date of the termination and minimize all further costs to the County. In the event
of termination under this paragraph, all documents, data and reports prepared by the Contractor
under the Contract shall become the property of and be delivered to the County upon demand.
The Contractor shall be entitled to receive just and equitable compensation for work in progress,
work completed and materials accepted before the effective date of the termination.
6.8 TERMINATION FOR DEFAULT:
6.8.1 In addition to the rights reserved in the Contract, the County may terminate the Contract
in whole or in part due to the failure of the Contractor to comply with any term or
condition of the Contract, to acquire and maintain all required insurance policies, bonds,
licenses and permits, or to make satisfactory progress in performing the Contract. The
Procurement Officer shall provide written notice of the termination and the reasons for it
to the Contractor.
6.8.2 Upon termination under this paragraph, all goods, materials, documents, data and reports
prepared by the Contractor under the Contract shall become the property of and be
delivered to the County on demand.
6.8.3 The County may, upon termination of this Contract, procure, on terms and in the manner
that it deems appropriate, materials or services to replace those under this Contract. The
Contractor shall be liable to the County for any excess costs incurred by the County in
procuring materials or services in substitution for those due from the Contractor.
6.8.4 The Contractor shall continue to perform, in accordance with the requirements of the
Contract, up to the date of termination, as directed in the termination notice.
6.9 TERMINATION BY THE COUNTY:
If the Contractor should be adjudged bankrupt or should make a general assignment for the benefit
of its creditors, or if a receiver should be appointed on account of its insolvency, the County may
terminate the Contract. If the Contractor should persistently or repeatedly refuse or should fail,

except in cases for which extension of time is provided, to provide enough properly skilled
workers or proper materials, or persistently disregard laws and ordinances, or not proceed with
work or otherwise be guilty of a substantial violation of any provision of this Contract, then the
County may terminate the Contract. Prior to termination of the Contract, the County shall give the
Contractor fifteen- ( 15) calendar day's written notice. Upon receipt of such termination notice, the
Contractor shall be allowed fifteen (15) calendar days to cure such deficiencies.
6.10 STATUTORY RlGHT OF CANCELLATION FOR CONFLICT OF INTEREST:
Notice is given that pursuant to A.R.S. §38-511 the County may cancel this 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.11 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 under this contract.
6.12 ADDITIONS/DELETIONS OF SERVICE:
6.12.1 The County reserves the right to add and/or delete materials to a Contract. If a service
requirement is deleted, payment to the Contractor shall be reduced proportionately, to the
amount of service reduced in accordance with the bid price. If additional materials are
required from a Contract, prices for such additions shall be negotiated between the
Contractor and the County.
6.12.2 The County reserves the right of final approval on proposed staff for all Task
Orders. Also, upon request by the County, the Contractor shall be required to remove
any employees working on County projects and substitute personnel based on the
discretion of the County within two business days, unless previously approved by the
County.
6.13 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 constmed as to
create the relationship of employer and employee, partnership, principal and agent, or joint venture
between the County and the Contractor.
6.14 SUBCONTRACTING:
The Contractor may not assign this Contract or subcontract to another party for performance of the
terms and conditions hereof without the written consent of the County, which shall not be
unreasonably withheld. All correspondence authorizing subcontracting must reference the
Proposal Serial Number and identify the job project.
6.15 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.16 ACCESS TO AND RETENTION OF RECORDS FOR THE PURPOSE OF AUDIT AND/OR
OTHER REVIEW:

6.16.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.16.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.16.3 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 claim submitted by the
Contractor by 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.17 AUDIT DISALLOWANCES:
If at any time, County determines that a cost for which payment has been made is a disallowed
cost, such as overpayment, County shall notify the Contractor in writing of the disallowance.
County shall also state the means of correction, which may be but shall not be limited to
adjustment of any future claim submitted by the Contractor by the amount of the disallowance, or
to require repayment of the disallowed amount by the Contractor.
6.18 SEVERABILITY:
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 this Contract.
6.19 RIGHTS IN DATA:
The County shall own and have the use of all data and reports resulting from this Contract without
additional cost or other restriction except as provided by law. Each party shall supply to the other
party, upon request, any available information that is relevant to this Contract and to the
performance hereunder.
6.20 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.21 VERIFICATION REGARDING COMPLIANCE WITH ARIZONA REVISED STATUTES §41-
4401 AND FEDERAL IMMIGRATION LAWS AND REGULATIONS:
6.21.1 By entering into the Contract, the Contractor wmrants 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 waiTanties 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.21.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.21.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 shall 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.
6.22 CONTRACTOR LICENSE REQUIREMENT:
6.22.1 The Respondent 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. The Respondent 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 Respondents furnishing finished products, materials or articles of merchandise that shall
require installation or attachment as part of the Contract, shall possess any licenses
required. A Respondent 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, at (602) 542-1525 to
ascertain licensing requirements for a particular contract. Respondents shall identify
which license(s), if any, the Registrar of Contractors requires for performance of the
Contract.
6.23 CERTIFICATION REGARDING DEBARMENT AND SUSPENSION
6.23 .1 The undersigned (authorized official signing for the Contractor) certifies to the best of his
or her knowledge and belief, that the Contractor, defined as the primary participant in
accordance with 45 CFR Part 76, and its principals:
are not presently debarred, suspended, proposed for debarment, declared
ineligible, or voluntarily excluded from covered transactions by any Federal
Department or agency;
have not within 3-year period preceding this Contract been convicted of or had a
civil judgment rendered against them for commission of fraud or a criminal
offense in connection with obtaining, attempting to obtain, or performing a
public (Federal, State or local) transaction or contract under a public transaction;
violation of Federal or State antitrust statues or commission of embezzlement,
theft, forgery, bribery, falsification or destruction of records, making false
statements, or receiving stolen property;
are not presently indicted or otherwise criminally or civilly charged by a
government entity (Federal, State or local) with commission of any of the
offenses enumerated in paragraph (2) of this certification; and
have not within a 3-year period preceding this Contract had one or more public
transaction (Federal, State or local) terminated for cause of default.

6.23.2 Should the Contractor not be able to provide this certification, an explanation as to why
should be attached to the Contract.
6.23.3 The Contractor agrees to 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.24 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.25 GOVERNING LAW:
This Contract shall be governed by the laws of the state of Arizona. Venue for any actions or
lawsuits involving this Contract shall be in Maricopa County Superior Court or in the United
States District Court for the District of Arizona, sitting in Phoenix, Arizona
6.26 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.
6.27 INFLUENCE
As prescribed in MCl-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 MC 1-902.
An attempt to influence includes, but is not limited to:
6.27.1 A Person offering or providing a gratuity, gift, tip, present, donation, money,
entertainment or educational passes or tickets, or any type valuable contribution or
subsidy,
6.27 .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.28 PUBLIC RECORDS:
All Offers submitted and opened are public records and must be retained by the Records Manager
at the Office of Procurement Services. Offers shall be open to public inspection after Contract
award and execution, except for such Offers deemed to be confidential by the Office of
Procurement Services. If an Offeror believes that information in its Offer should remain
confidential, it shall indicate as confidential, the specific information and submit a statement with
its offer detailing the reasons that the information should not be disclosed. Such reasons shall
include the specific harm or prejudice which may arise. The Records Manager of the Office of
Procurement Services shall determine whether the identified information is confidential pursuant
to the Maricopa County Procurement Code.
6.29 INCORPORATION OF DOCUMENTS:
The following are to be attached to and made part of this Contract:
6.29.1 Exhibit A, Pricing;
6.29.2 Exhibit B, Scope of Work, Maintenance and Support Policy, Implementation
Plan/Schedule, and Technical and Business Requirements;
6.29.3 Exhibit C, Office of Procurement Services Contractor Travel and Per Diem Policy.

SERIAL 13133-RFP
IN WITNESS WHEREOF, this Contract is executed on the date set forth above.
CONTRACTOR
AUTHORIZED SIGNATURE
A. M. 'Trey" Fragala, III, AICP, PMP / Chief Operating Officer
PRINTED NAME AND TITLE
3680 Avalon Park Blvd., Suite 200, Orlando, FL 32828
ADDRESS
04.02.14
DATE
MARICOPA COUNTY
CHAIRMAN, BOARD OF SUPERVISORS DATE
ATTESTED:
CLERK OF THE BOARD DATE
APPROVED AS TO FORM:
LEGAL COUNSEL DATE

EXHIBIT A
PRICING
SERIAL 13133
NIGP CODE: 920
COMPANY NAME: VUEW orks, LLC
DOING BUSINESS AS VUEW orks, LLC
(DBA) NAME:
MAILING ADDRESS: 3680 Avalon Park Blvd. E. Suite 200, Orlando, FL 32828
REMIT TO ADDRESS: 3680 Avalon Park Blvd. E. Suite 200, Orlando, FL 32828
TELEPHONE NUMBER: ( 407)382.5222
FACSIMILE NUMBER: ( 407)382.5420
WEB SITE: www.vueworks.com
REPRESENTATIVE Jason Amadori, GISP
NAME:
REPRESENTATIVE (407)382.5222
PHONE NUMBER:
REPRESENTATIVE E- JASON.AMADORI@vueworks.com
MAIL:
YES NO
WILL ALLOW OTHER GOVERNMENTAL ENTITIES TO PURCHASE FROM THIS
CONTRACT: [x] [ ]
WILL ACCEPT PROCUREMENT CARD FOR
PAYMENT: [ ] [ ]
PAYMENT TERMS: RESPONDENT IS REQUIRED TO PICK ONE OF THE FOLLOWING.
PAYMENT TERMS WILL BE CONSIDERED IN DETERMINING LOW BID. FAILURE TO
CHOOSE PAYMENT TERMS WILL RESULT IN A DEFAULT TO NET 30 DAYS.
[ X ] 2% 10 DAYS NET 30
DAYS
1.0 PRICING:
1.1 SOFTWARE/LICENSE
COST $250,000.00
1.2 3RD PARTY SOFTWARE (IF
APPLICABLE) $5,595.00
1.3 CUSTOM SOFTWARE (IF
APPLICABLE) $0.00
1.4 HARDWARE COST
(SERVERS, MOBILE)
AND OTHER IF APPLICABLE) RESPONDENT TO RECOMMEND THE HARDWARE SOLUTION WITH SUFFICIENT
TECHNICAL SPECIFICATIONS FOR THE RECOMMENDED SOLUTION. COUNTY
RESERVES THE RIGHT TO TAKE HARDWARE REQUIREMENT COSTS INTO
CONSIDERATION.

1.5 IMPLEMENTATION COST
PER EXHIBIT B $3S8,31 0.00 NOT TO EXCEED
1.6 TRAINING COST PER
EXHIBITB $S9,200.00
1.7 TRAVEL RELATED COSTS
PER EXHIBIT C $26,080.00
1.8 TOTAL SYSTEM COST
(YEAR 1) $709,200.00
2.0 MAINTENANCE AND SUPPORT:
2.1 (8AM-8PM Eastern Standard
Time) FULL MAINTENANCE AND
SUPPORT YEAR 1 YEAR2 YEAR3 YEAR4 YEARS
2.2 SOFTWARE $S0,39S.OO $S0,39S.OO $S0,39S.OO $S0,39S.OO $S0,39S.OO
2.3 HARDWARE NA $ $ $ $
2.4 (24 X 7) FULL
MAINTENANCE AND SUPPORT YEAR 1 YEAR2 YEAR3 YEAR4 YEARS
2.5 SOFTWARE $100,000.00 $100,000.00 $100,000.00 $100,000.00 $100,000.00
2.6 HARDWARE COST
(SERVERS, MOBILE)
AND OTHER IF APPLICABLE) NA $ $ $ $
3.0 OTHER PRICING (LIST AS NEEDED):
3.1 SOFTWARE LICENSING NOT INCLUDED IN RESPONDENT
RESPONSE $

Amadori I I l Assistant ! Paine I Carr/ Brown/ Koehn/
Project Project Project Technical Technical Technical GIS and
Executive I Manager Manager Oversight Support Support Implemen
Oversight tation
Lead
$ 165.00 $150.00 $ 100.00 $165.00 $140.00 $75.00 $115.00 .Blended
• I • Ratd
l. Baseline Detailed Project Work Plan
24 40 60 I 24 I 16 I 16 I 40 220 I $27,960.00 $127.09
2. Project Status Reports
2 8 8 18 I $2,330.00 $ 129.44
3. Installation Certification Document
2 4 4 10 I $ 1,330.00 $ 133.00
4. System Configuration Reports
4 I 8 I 12 I 40 I 24 88 I $13,020.00 $ 147.95
5. Configured Software Ready for Test
8 40 60 I 40 I 24 I I 80 252 I $32,480.00 $128.89
6. Test Plan
2 4 10 16 I $1,930.00 $ 120.63
7. Data Conversion Plan
24 60 40 I 60 184 I $26,860.00 $145.98
8. Migrated Data Ready for District
Validation
4 40 60 20 20 I 20 164 I $20,260.00 $123.54
9. Interface Specifications
4 24 40 24 40 132 I $17,820.00 $135.00
1 0. Interfaces Ready for I est
4 10 I 8 22 I $2,960.00 $ 134.55
11. Installation Architecture Specification 1
6 40 40 I 20 106 I $ 14,290.00 $134.81
12. Training Plan and Training
8 24 24 40 I I 40 136 I $ 17,520.00 $128.82
13. Training
32 32 32 40 40 176 I $25,480.00 $144.77
14. Workflows
40 40 60 140 I $18,600.00 $132.86
15. Go-Live and
Stabilization Plan 8 60 80 60 40 I I 40 288 I $38,420.00 $133.40
16. Operations Manual I I
4 8 8 2 40 40 102 I $13,190.00 $129.31
17. Stabilization Services 4 16 16 40 40 I 40 I 40 196 I $24,460.00 $124.80
Flexible-use hours 2
I I I 120 I 120 I 120 I 120 480 I $59,400.00 $123.75
Other: (please detail)
0 I $

$
Labor Total $358,310.00
180 I 458 I 562 1 490 I 444 I 196 I 400
Trips/Nights People Cost Ext. Cost
Airfare
4 4 $800.00 $ 12,800.00
Hotel
16 4 $120.00 $7,680.00
Meals
16 4 $50.00 $3,200.00
Ground transportation 16 1 $150.00 $2,400.00
$ 26,080.00

Project: MCDOT Asset Management and Maintenance Application
Invoicing Schedule by Gate
Gate Price Price (go live with
Gate Name Timeline
Number (documentation) training)
1 Project Management - - -
1 Project Initialization - - -
1 System Implementation - $250,000 May 2014
Plan/License
1 Final Implementation - - May 2014
Plan/Begin Configuration
2a Group A Documentation $25,000 June 2014
2b Group B Documentation $25,000 July 2014
2c Group C Documentation $25,000 July 2014
2d Group D Documentation $20,000 July 2014
3a Adopt-a-Highway $20,000 August 2014
3b Traffic Operations $25,000 August 2014
3c Operations Support $25,000 Sept 2014
3d Field Operations $25,000 Oct 2014
3e 6-1 Office/Dispatch $25,000 Oct 2014
3f Pavement Management $25,000 Nov 2014
3g Traffic Signals $25,000 Nov 2014
3h Bridges $25,000 Dec 2014
3i Inventory/Warehouse $25,000 Dec 2014
3j Finance/GASB $25,000 Jan 2015
3k Executive Management $10,000 Feb 2015
4a Module Level Recheck: $20,000 Feb 2015
Maintenance Management
4b Module Level Recheck: Asset $20,000 Mar 2015
Management Configuration
5 Data Migration $20,000* May 2015
6 Refresher Training/Education $49,200** July 2015
for Productive use
7 System Maintenance Document - -
and Project Closure
8 On Going Maintenance and $50,395 August 2015
Support 1st Year
*Data migration fee to be revised pending discovery of list of external databases.
**Training includes 15 groups over a 2-week span. Traiuing shall be conducted on site at Durango over 5
days and at 3 additional maintenance yards over an additional 5 days. Travel costs are limited to one person
onsite for this period. Additional training sessions, additional traiuing groups, additional personnel, etc. are
available for an additional fee.

EXHIBIT B
SCOPE OF WORK
VUEWorks® software is a web-based, geospatially-enabled, enterprise-level asset and work management system
that provides government agencies with the ability to manage, analyze, integrate and share valuable asset and
work management information. VUEWorks® can manage infrastructure capital assets to minimize the total cost of
owning and operating them, while delivering the service levels MCDOT desires.
VUEWorks' objective is to provide MCDOT with a comprehensive Asset Management and Maintenance System
(AMMS) built on VUEWorks' web-based technology that shall not only address the points that were outlined in the
RFP, but shall also be capable of fully leveraging the MCDOT's current and future geo-spatial data infrastructure
and all required AMMS interfaces.
The following is a listing of some of the advantages of VUEWorks® approach and
solution:
);> VUEWorks® uses the International Infrastructure Management Manual's approved and accredited "all assets"
approach to infrastructure asset management- which eliminates the need for the MCDOT to purchase specific
modules for different work flows or asset types and allows uniformity in the MCDOT's asset management
program.
> VUEWorks® is a 100% web based application coded in .Net- it uses a service-oriented architecture allowing it
to interface with nearly any external database or application; and is 100% mobile.
> The VUEWorks® solution provides seamless integration with Esri's ArcGIS Server platform, fully supports SQL
Server 2008 and Windows Server 2008 Service Pack 2.
Data Transfer Solutions, LLC (DTS}, is the parent company of VUEWorks®, LLC. DTS develops enterprise
resource software applications to help clients: manage information, analyze data, showcase the agency, query data
repositories, and facilitate communication. The company excels at the design, redesign and implementation of
information systems as well as the creation of custom interactive websites and web-based applications that meet
the demands of decision makers. DTS delivers technical solutions to facilitate efficient decision-making through
five primary areas:
1. Web and Database Applications Development - DTS has developed web-based software applications to help
clients solve a variety of enterprise resource management problems. VUEWorks® design and implement
information systems, analyze data, customize software, and provide additional services tailored to specific
client needs. These applications are used for a variety of city, state, and local data management systems.
2. Enterprise Planning & Implementation - DTS provides enterprise planning, business process analysis, systems
implementation, and applications development services to all sectors of government. DTS helps clients define
their spatial information technology vision, mission, and strategic objective~. DTS can implement data from
multiple sources, provide user friendly tools to support various planning activities, improve the efficiency and
effectiveness of performance at the system level, and promote effective communication amongst
stakeholders, including the public. The enterprise resource plan prioritized projects and applications designed
to guide an agency towards its goals.
3. Asset Management - DTS wholly-owns VUEWorks® Software LLC, which it acquired in 2011. VUEWorks®
software helps clients solve a variety of Asset, Facility, Work Order and GIS challenges. VUEWorks® asset
management capabilities enable us to provide VUEWorks® clients with database inventories of any asset type
within a retrievable system that allows clients to maintain, track, and improve their infrastructure.
4. Mobile Asset Collection (MAC} Van - VUEWorks® Mobile Asset Collection vehicle is equipped to visually
locate road assets and condition information for use in databases VUEWorks® create for VUEWorks®
clients. Using two high resolution cameras, a laser scanner and GPS technology the vehicles are able to
calculate, with high accuracy, the geographic location of any above ground asset, ~ 1 opl!,lqt,e a;~:§l~ l"d.atabase
.with collected .assets, and even deliver the assetinve11tory!ffiliJ1 VUEWorks®. VUEWorl<s® 1\nAc fleet"11s 1•hea'vily-

5. GIS and Internet Mapping - Using Internet Map Server technology from Environmental Systems Research
Institute (ESRI) or open-source technologies, DTS provides services for creating and hosting Internet mapping
solutions as diverse as the customer's information needs. DTS has conducted enterprise GIS needs assessment
for city, county, and DOT governments.

VUEWorks® software is an affordable, web-
enabled Integrated GIS, Enterprise Asset
Management solution that was designed for use
by State and Local governments, utilities,
corporations, schools, theme parks, and other
organizations that need to track the condition,
minimize failure risk, and optimize expenditures and
service delivery of their physical assets.
VUEWorks® integrates with GIS data, allowing
users to share geo-spatial and non- geo-spatial
data on any physical asset, including, but not
limited to: public infrastructure assets, such as
roads, bridges, signage, building facilities and
vehicle fleets, water, sewer, pumps/pumping
stations, manholes, catch basins, gas/oil pipelines,
etc.
VUEWorks® software employs an all assets
model
that is based on asset types and asset classes, and
therefore does not require users to purchase
separate modules for individual assets.
Length of Time Product has been on the Market
VUEWorks® has been available on the market
since 1999 as part of the SEA Consultants software
suite, eventually becoming VUEWorks, LLC in
2004.

VUEWorks Core
VUEWorks® Core is the foundation for all other VUEWorks® modules, connecting County's existing GIS data to the
VUEWorks® strategic asset and work management system. County can link documents and databases to specific
assets, conduct multi-level searches, buffer queries, measure distances and create reports. Best of all, it is very
configurable and easy to navigate and use. As a web-based application, VUEWorks® can be accessed with
Microsoft® Internet Explorer via the internet/intra net, WI-FI, and wireless communication cards. This gives the user
the added flexibility to access VUEWorks® from the office, the field, or home using a traditional desktop computer,
notebook, tablet or mobile-enabled platform.
>- Integrated with Esri® ArcGIS® Server.
> Manage read/write/edit permissions by department, role, and or by user.
> User defined dashboards to graphically display statistical data of Service Requests, Work Orders, or any other
Data Source within the application.
> Easily link documents like image files, PDFs, videos, and many other formats to any asset for quick viewing
anytime, anywhere.
>- Use Data Link to seamlessly link external databases in Access, Excel, SQL Server, Oracle or any ODBC compliant
database.

LandVUE
LandVUE is a complete land management system that is capable of handling tract/parcel(s) from acquisition of the
land until its time of disposal. The LandVUE module is tightly integrated with the VUEWorks® so that the
tract/parcel(s) related to its tangible assets contained within the asset management system. This allows personnel
from multiple departments and roles to work collectively in a single system. In turn this provides for greater
productivity and eliminates redundancy.
> Integrated with the VUEWorks® Asset Management System.
> Integrated with Esri® ArcGIS® Server 10.1, 10, and 9.3.1
> Provides for the linking and storage of various documents related to the tract/parcel(s)
> Track important property acquisition or disposition along with project-level details.
> Provides both standard and ad-hoc reporting capabilities.
> Track payments, renewal options, termination tasks, sub-lease information, and cost of living increases.

Request Portal
The VUEWorks® Request Portal module delivers convenient online access for citizens and customers to place their
requests using the Web. There is no customization or third party database required; the Request Portal interfaces
directly with the VUEWorks® Service Request module. And the Request Portal status is kept up-to-date when
a service call has been closed. At any time, a citizen or customer can review the status of their request by entering
the portal and viewing "My Requests" or by searching for a Service Request I D.
> Allows citizens and customers to issue requests directly, reducing the burden on County's call takers or front
office staff
> Minimizes errors by directly populating the Service Request module
> Complete integration between the Request Portal, Service Request, and Work Order modules
> The Request Portal status is kept in sync with Work Orders that have linked Service Calls
> Allow County's agency to receive and share request status after hours, 24/7, 365 days a year
> Access the Request Portal via smart phone mobile devices

Work O,rders
The VUEWorks® Work Order module combines the power of Computerized Maintenance Management Systems
(CMMS) with GIS to manage and plan all work activities. Work Orders can be configured to match County's
existing work order forms to maintain the look-and-feel of County's existing workflow, right down to the activity
level. Easily create preventative maintenance schedules linked to a calendar to view activities by day, week or
month. Trigger work orders based on data measurements or events from SCADA systems or other data links.
The Work Order module can be integrated with other VUEWorks® modules.
>- Work Order forms can be user-defined to fit County's "look and feel" and existing work process
>- Attach work orders to any physical asset on the map or non-GIS asset in Facilities for easy reference
>- Robust reporting features include pre-defined report templates and wizards
>- Automated email notices sent to any email program including Microsoft® Outlook
>- Work Orders can be logged from the field in a fully disconnected mode.

Resource Manager
The VUEWorks® Resource Manager module is tightly integrated with the Work Order module so that
associated time and costs for personnel, crews, contractors, vendors, equipment, and other items pulled from
inventory can be tracked. Time for labor and equipment can be accounted for independently with the Time
Recorder feature, then passed on to external accounting systems. Multiple billing rates can be assigned for
different labor roles and activities. Set up personnel so that employees can be placed on a work order
based on job classification, availability and cost. Personnel managers can be set up to search for an employee job
classification, availability and cost in an easy-to-use calendar interface.
Y Personnel, equipment, and inventory items/costs can be added and tracked in work orders
Y Assign multiple labor rates to special field activities to get quick cost estimates
Y Get real-time inventory tracking with alerts for low inventory
Y Use the calendar interface to track availability of employees and equipment
Y Automatic notification of employees and supervisors when assigned to a work order
Y Import/Export personnel, e.quipment and inventory to accounting systems

Valuation- GASB34
The VUEWorks® Valuation module removes the drudgery and expense of meeting the Government Accounting
Standards Board Statement (GASB) No. 34, or Canadian PSAB 3150 requirements for maintaining and reporting
value and depreciation of infrastructure assets. With reporting under County's contrql, County can leverage
depreciation and related financial information to help plan budgets and projects. Missing historical cost data?
No problem- Valuation shall calculate historical costs back to the time of construction. County can also enter
historical costs directly or enter unit costs and let VUEWorks® calculate the total value.
)> Integrates seamlessly with the VUEWorks® Facilities module & County's GIS
)> Determine and report historical and replacement costs
)> Calculate value and depreciation for all infrastructure assets, including buildings, streets,
bridges, water, sewer, equipment, and any other asset type.
)> Take control of depreciation parameters to realize the full value of County's assets
Y Account for maintenance through work orders that add value and extend asset life
)> Powerful search and filter capabilities allow users to report by location or other criteria

Candition
The VUEWorks® Condition module is highly configurable, allowing County to collect, summarize, analyze, rate, and
report on the condition of any asset (e.g., signs, pipes, roads, trees and more). Develop County's own condition
inspection criteria or use condition data collected with the use of other software. Either way, VUEWorks® provides
configurable tools that allow County to build County's own rating criteria as simple or as detailed as
required. History features show how condition has changed over time for each asset or the entire system. The
Report Designer lets County design just about any style of report with data from all sources including GIS data and
linked databases that contain condition assessment details.
~ Supports condition ratings using the following methods: Simplified, Itemized and Defect
~ Link to external condition data to summarize, analyze, rate, and report
~ Integrates with GIS to visualize color-coded conditions by viewing on a map
~ Integrates with the VUEWorks® Work Order module to capture condition data directly on a work order
form
~ Integrated ASTM templates measure pavement condition for asphalt and concrete
~ Condition inspections can be created and completed in the field in a fully disconnected mode.

Risk
The VUEWorks® Risk module allows County to capture stakeholder concerns in a risk model to strategically
prioritize limited resources and work activities. Determine failure modes or consequences and/or probability of
failure for asset classes and types, and configure priorities by assigning weight factors. Once County has the risk
model configured and calculated, VUEWorks® Risk makes it easy and fast to look at every aspect of the risk model
by highlighting assets on a map and illustrating findings to stakeholders to justify work priorities. Avoid costly
failures before they occur!
Y Use GIS data with VUEWorks® Multi-Edit and Buffer tools to quickly assign consequence of failure values
to assets in the GIS
Y Utilize the Consequence Factor as a measure of Criticality when comparing assets with one another
Y Configure unlimited Consequence and Failure modes for each asset type
Y Use data from the Work Order module (e.g., number of Work Orders as a variable) or any external database,
such as a capacity analysis, to keep risk models current
Y Use Risk data to forecast budgets for asset maintenance and replacement

Budget Forecasting
For multi-year capital improvement budget forecasts
The VUEWorks® Budget Forecasting module delivers configurable, multi-year capital improvement planning
capabilities to help determine long-term budget needs based on deterioration curves. Use one of the supplied
deterioration curves or one of County's own as a basis for forecasting and then identify at what point on the
deterioration curve an asset should be rehabilitated or replaced based on risk and condition. 'What-if' budget
scenarios can be created by adjusting budgets, project types, and prioritization criteria; then run forecasting
models to see if County's budget shall meet service level goals. PCI values can be used to determine the work
activities and cost to maintain a roadway pavement surface condition that supports the needs of the user.
With VUEWorks®, new modes of analysis have been added for benefit - cost analysis that takes into
consideration not only direct life-cycle costs of projects, but also social and environmental costs. These features
allow transportation agencies to take into account the costs of factors such as lost travel time, accident rates, and
fuel consumption when planning projects.

);> View how different budget scenarios impact the overall condition of any asset class
> Select from risk and failure probability criteria to define how rehabilitation shall be prioritized
> Automate the assignment of rehabilitation jobs based on failure modes such as capacity and condition
> Assign number of years to extend the life of an asset as well where it falls on the deterioration curve after a
job is performed

Facilities
The VUEWorks® Facilities module provides access to physical assets not found in a GIS but which still need
historical service/work records, data links, condition assessment, valuation, preventive maintenance scheduling
and access to key operational documentation. The types of facilities that can be managed are virtually limitless,
including pumps, motors, fleet and building components. The Multi-view feature allows assets to be organized in
different categories (e.g., location/floor level, department or manufacturer). The data linking features found in
VUEWorks® Facilities combined with the Work Order module allow automatic work orders to be issued based on
user defined triggers from a SCADA or ITS system database.
>- Manage non-GIS assets like building components and internal equipment
>- Create and organize assets in a hierarchical structure for easy reference
> Inventory County's fleet and mobile equipment in the Resource Manager module and use them on work orders
> Structure County's asset hierarchy to include work orders, condition, valuation and more. Manage facilities
with trigger work orders based on equipment run-time or other data (e.g., SCADA Systems)

Mobile VUE
VUEWorks® MobileVUE is built on ESRI's ArcGIS Mobile platform. MobileVUE allows the VUEWorks® user to take
the application into the field regardless of having connection to the web. Because it is built on ESRI ArcGIS Mobile,
County can even take the map and all the GIS data with you! Perform asset condition inspections, collect new
assets, and interact with County's GIS from County's tablet device in a connected or disconnected mode.
Y Syncs with VUEWorks® for simple "grab and go" field device use
Y Work with County's GIS data in a fully disconnected state
Y Perform asset condition inspections, asset attribute updates, and capture new assets
Y Designed for tablet form factors and touch input

The VUEWorks® team is proposing a solution that shall meet the MCDOT's need for an Optimized Maintenance
Management System that is affordable, GIS-centric Work, Asset, Permit, Inventory and Land Management solution
that s h a II meet the requirements of the RFP. VUEWorks® application database is SQL Server-based and
s h a II integrate with any ODBC-compliant database or set of databases {SQL, Oracle, Access, Excel}. The Data
Linking functionality that is native to the system was designed for integration between the Core application and
any third- party system to ensure that other IT investments can be leveraged. The VUEWorks® application also
runs within a virtualized server environment. A list of hardware and base software required to run VUEWorks®
proposed solution is contained below.
VUEWorks® Server
Specifications
VUEWorks® must be installed on the same server as ArcGIS Server. If purchasing a new server ask Esri to
provide their hardware recommendations for County's ArcGIS Server environment. VUEWorks® supports what
Esri recommends.

SERIAL 13133-RFP
The most resource intensive operations implemented by VUEWorks® occur on the server that hosts SQL Server.
At a minimum this server should have 8 GB of RAM and a dual core processor running at 2.8 GHz. Consult
Microsoft for licensing requirements and edition information.
http://www.microsoft.com/sqlserver/en/us/editions.aspx. Server requirements can vary widely depending on the
number of users, other applications that share the same resources, and the performance that County's users
expect. VUEWorks® and ArcGIS Server shall perform faster with fast multi-core CPUs, more memory and with
no other applications competing for the same resources on the SQL Server machine. Contact VUEWorks®
directly to discuss how VUEWorks® shall perform best in County's environment.
Minimum Server Requirements
MS Windows Server Standard 2003, 2008, or 2008 R2 operating system {32 bit or 64 bit)
Any version of MS SQL Server 2005, MS SQL Server 2008, or MS SQL Server 2008 R2
Hardware configured for ArcGIS Server .NET according to Esri recommendations
Configured for remote access over the Internet utilizing Windows Terminal Server or other remote
access software (for VUEWorks® support)
Esri ArcGIS Server
Esri ArcGIS Workgroup or Enterprise Server 10.1 .NET versions. Standard or Advanced.
Back up
Utilize County's organization's backup policies to back up the VUEWorks® databases and all files associated with
the software. VUEWorks® software is less than 200MB. The VUEWorks® databases rarely get larger than 500MB
for VUEWorks® largest most active sites.
Virtual Servers
VUEWorks® shall run on VMWare and Microsoft Hyper-V. Other virtualization environments are untested
and therefore not supported at this time. See Esri white papers on the subject:
Client Computers
The following are the minimum recommended requirements for a VUEWorks® user work
station:
Intel Atom 1.6 Ghz or faster processor laptop, tablet or desktop
1GB RAM
40 GB Hard drive or SSD with 5 GB free space
Wired 100baseT network connection, and/or Wireless 802.11x, and/or Cellular carrier access card
(see network section)
16 million color 1024 x 768 resolution. Graphics card
1024 x 768 resolution highly recommended but can function with 1024 x 600
Keyboard and mouse
Windows XP, VISTA, or Windows 7 operating system
Microsoft Internet Explorer Version 7 or higher- VUEWorks® works best with IE7
Virus protection software
Document viewing software:
o For TIFF documents try Alternatiff
o For PDF documents use Adobe Acrobat Reader
o i=or;Djivu documents use Document Express fromllza rdtech

These links do not represent endorsement of any of these products by VUEWorks, Inc. They are simply presented
here as options for the convenience of VUEWorks® users.
Network
VUEWorks® is a standard .NET web based application that runs on MS Internet Information Server 6.0 or
greater with no special requirements beyond any other liS web application. The following are the minimum
recommended requirements for a typical VUEWorks® enabled network. Most networks in use today meet
these requirements.
Internal Network for any type of implementation
IP network protocol
Wired network to client computers: lObaseT, lOObaseT or lOOObaseT switched network
Server backbone: lOOObaseT (lgigabit) or faster connection
Wireless network: 802.11x compatible with WAP or better security
For the field:
Wireless or Cellular carrier network capable of 3G, 4G or faster (AT&T, Sprint, Verizon and others can
accommodate this within their coverage areas).

Security
VUEWorks® contains a fully featured security console. All modules can be controlled for user access, and the
extent to which access is granted (read only, read and edit, read and edit and delete, read and edit and delete and
modify, etc.}. VUEWorks® can use windows active directory.
Permissions for Work Orders
Work Request Management & General, Scheduled and Preventative Maintenance
Work Orders encompass the core of the asset management functions of VUEWorks®. Work Orders can be
configured for multiple business entities, Groups and Departments within those entities. Work activities can be
configured specifically for each business entity as well as shared between these entities. These activities are
accessed based on a user's profile and Defaults can be set to auto-fill Work Orders for commonly used Work
Activities. The Work Orders can be accessed on-screen, in HTML format as well as exported to electronic
document format (PDF, Excel, Doc, RTF} or physically printed. Since VUEWorks® is 100% web-based, the
work orders are accessed through a standard web-browser.
The Work Order Manager is the central part of Work Orders and is accessed from any of VUEWorks® methods for
adding a Work Order. The Work Order Manager is composed of 5 main tabs which work in conjunction with one
another: Form View, Table View, Filter, Reports and Assets. Below is an example of the Work Order Manager:

All VUEWorks® Work Order types look and behave in a similar fashion. However, there are some differences in
functionality depending on the type of Work Order. Below is a summary of each type of Work Order, their
differences, and how each type is used in VUEWorks®.
Standard Work Order: This is the most common type of Work Order. It represents a single work order and can be
created directly or from a Pending Work Order. Standard Work Orders created directly are usually associated with
corrective maintenance activity. A standard Work Orders may be a Parent Work Order or a Child Work Order as
described below. A Standard Work Order can be turned into a Recurring Work Order at any time while its status is
Open or Hold. Standard Work Orders that have been spawned from a Recurring Work Order shall appear in a list
of Work Orders.
Recurring Work Order: A Recurring Work Order is a template used to create a schedule to spawn Standard Work
Orders for the purpose of preventive maintenance, predictive maintenance or other recurring events. It is most
easily identified by the label placed in the Status area of the Work Order Header stating that it is a Recurring Work
Order. The presence of the Schedule tab is another characteristic of a Recurring Work Order. Recurring Work
Orders are not really work orders but templates used to spawn work orders.
Pending Work Order: A Pending Work Order is a single occurrence of a Recurring Work Order that has not yet been
accepted as a Standard Work Order. Pending Work Orders are easily identified where ever Work Orders are listed
because they shall appear in italic font with a symbol to indicate their 'pending' status.
Parent Work Order: A Parent Work Order is a work order that has other work orders linked to it. A Parent Work
Order can have Child Work Orders down to six levels deep. A Child Work Order is linked through the Work Order
Link Control. Children of a Parent Work Order are listed in the Work Order Link Control. Costs associated with Child

Work Orders shall be rolled up to the Parent Work Order. A Parent Work Order can have an unlimited number
of Children.
Child Work Order: A Child Work Order is a work order that has been linked to a Parent Work Order. A Child Work
Order can be identified by a hyperlink to the Parent Work Order that shall appear on the left side of the Work
Order Header. A Child Work Order can only have one Parent. A. Child Work Order can also be a Parent. A Child
Work Order can be a Recurring Order as long as the Child Work Order is not also a Parent.
The Notification feature allows MCDOT to notify users of a pending Work Order through two mechanisms. First,
any system user on the notification list shall have the Work Order placed on their personai'My Work Orders' list.
Second, the MCDOT can notify all users on the notification list by email. This shall send an email with an optional
calendar schedule attachment and PDF work order attachment to all the users on the list. Each user can elect to
use the calendar attachment to automatically populate their Calendar program of choice (such as Microsoft
Outlook or Lotus Notes) with the Work Order schedule.
VUEWorks® Work Order module delivers Summary, Form, Tabular, and Embedded Attribute Report templates
from which County can generate reports on the data returned in the Work Order Manager Filter. In the Work
Order Manager Reports tab, MCDOT shall see the list of delivered reports as well as any they have created.
Reporting begins with the creation of report templates that are made available to users in the Existing Report
Templates section of the Report tab. Report templates are created using the Report Designer. Once a Report
Template is created it shall be listed in the Existing Report Templates section of the screen. The Report
Templates are associated with the selected Department I Group. As the user selects different Departments and
Groups the Report Templates that are available shall vary depending on which Department I Group is selected.
Summary Report templates are used to summarize the number of Work Order activities or items from a pick list.
Activity Summary Report Templates are included with VUEWorks® and cannot be modified. Pick List Summary
Report Templates can be created and modified.
Form Report templates are used to print form views from different combinations of the various sections of the
Work Orders
Tabular Report templates are used to create reports in traditional tabular form with columns and rows. Tabular
Reports are most comprehensive and offer features for Grouping, Sorting, and Summarizing when the Report
Template is defined in the Report Designer.

The screenshots below show the Work Order Manager with various report templates available in the different
report style, followed by sample reports.

Service Requests
The Service Request module s h a II enable MCDOT to record and track requests from those they serve. With
it MCDOT can attach requests to assets in the GIS or Facilities, create reports, set up parameters, and more. A
service request can be created quickly. Service Requests can be added as stand-alone, or attached to a parcel,
asset, or any selectable feature on the map. When Service Requests are created there are options available to
designate default values for Department, Group and Issue as well as the ability to automatically populate many of
the fields on the Form shown below.
Customer Request
The Request Portal Module shall enable MCDOT to expose a form to the internet for its citizens. to report and
monitor issues, complaints or problems that are stored in the Service Request module. The components of this
module include the web service that exposes the request form to the citizen over the internet, with configuration
accomplished within the Service Request Administrator area on the Portal tab. The web form is easily integrated
into MCDOT's web site as shown below.

Create Account I In
The VUEWorks® Request Portal is an easy-to-use web-based communication path between the MCDOT's and its
customers. Using the Request Portal, a customer can report issues to the MCDOT, then follow-up, check on
progress and view request history. The system is a registered user type of system, requiring the customer to
register before they can use it. This eliminates most prank reports, and provides a feedback path to contact the
cust~mer after their issue has been resolved, or for additional information that might be useful to resolve the
issue.
The web page that the customer signs in on is designed to be installed in any location that is exposed to the
internet. The County's existing website would be an ideal location. Once the customer has registered, and has
a user id and password, they can then enter the system to report an issue, check on prior issues, or to update their
system profile.
Service Order Management & Service Request Initiation
The Service Request Manager is the central part of Service Requests and is accessed from any of three methods for
adding a service request. The Service Request Manager is composed of 5 tabs which work in conjunction with one
another: Service Request Form, Service Request Table, Filter, Reports and Assets.
The Service Request Manager can be used to:
• Enter Service Request information through a form or table depending on County's preference.
• Quickly record Service Request information with drop down controls for Department, Type, and Issue.

SERIAL 13133-RFP
• Track requester phone number and other information.
• Manage information by creating a filtered list of Service Requests through Advanced Find or Quick Filter.
All controls on all tabs in the Service Request Manager are integrated so that all operations affect just the
current Service Request list. Advanced Find settings can be saved for future re-request.
• Identify and track duplicate requests {requests that refer to the same incident) or s. These features allow
County to create a list of all duplicate requests by time and/or distance parameters and establish one of
them as a master request. Once a master request is set all duplicate requests, while preserved, are
considered to be part of the same issue for reporting purposes.
• Initiate Work Orders. All work orders initiated from a service request are automatically linked to the
service request and can easily be referenced and viewed from the Service Request form.
• Print Service Request forms and optionally include duplicate requests, linked work orders, and the current
map view.
• Create standard reports with all Service Request details, or just print the Service Request headers with a
count of all Service Requests matching the 'summarize by' field. Or, create issue summary reports that
display a count of issues for the last year, month, week, day, or other criteria.
• Export to Excel from the Service Request Table. Excel's formatting, charting, and other functionality
extend VUEWorks® tabular reporting features.
GIS Mapping of all Work Requests, Assets, Asset Type Layers
Access existing ESRI ArcSDE geodatabase(s} without having to duplicate GIS data VUEWorks® consumes published
map services from ArcGIS Server 10.1 or newer. The map services may contain any combination of imagery, shape
files, file or personal geodatabases, and SQL Server or SQL Express SDE geodatabases. Geodatabases may be
versioned. If not versioned, or when using Shapefiles, GIS attribute data may be edited through the VUEWorks®
user interface by system users with appropriate permission.
VUEWorks® supports editing of the GIS data at any time without taking VUEWorks® off line. When edits are
saved, or when and edit session is closed, the changes are reflected in VUEWorks® immediately. There is NO GIS
DATA IMPORT/ EXPORT with VUEWorks®.
Allows user to select GIS feature and see work order history.
This is shown in graphic detail in the preceding pages. Work orders and service requests can be, and almost always
are, attached to GIS features. This allows for spatial queries to be performed against work orders and service
requests, as well as allows spatial selection sets to be made based on planned or completed work.
Provides tools to map service requests and work orders thematically or by user defined queries
VUEWorks® allows the users to place work order points (and service call points} on the map, and to symbolize
those points. In addition, as part of the work order workflow, GIS features can have a value that changes based on
work order status, and the value is tied to the symbology on the layer. This supports real time layer symbology
changes.
Allows for creation of GIS features through the work order VUEWorks® fully supports GIS feature creation on
the fly. Features can be created through ArcGIS Server and within desktop ArcMap/Editor/lnfo sessions. Web
editing of GIS features in VUEWorks® is supported through ArcGIS Server.
Reporting/ Analytics Functionality
VUEWorks® includes its own native reporting engine and query/report Ul for all modules. VUEWorks® supports
full reporting against all data fields in all Ul's, as well as full reporting against linked data and the GIS database.
VUEWorks® also supports the creation of ad-hoc queries through the use of the "Find/Manage/Report"
functions that are available throughout the application. Users can define templates for

their reports and even utilize the SQL-Server reporting capabilities to produce dashboards and reports. All
reports and queries can be reviewed electronically before printing to ensure consistency with desired results.
Furthermore, users can specify specific date ranges, sorting orders, and transaction types and based on any other
combination of data
Reporting access is controlled in the VUEWorks® permissions module. Below is a screen shot showing various
modules within the application and the reporting permissions for a system user.
Data-Driven Dashboards
VUEWorks® is capable of visualizing charts, reports and graphs of various reports available through its User-
Configured Dashboards. These dashboards are data-driven, so the user can specify the data source (GIS, Weather,
Condition, Risk, or Linked Data) and then render a report based on the user's needs. Dashboards are an excellent
way to provide visibility into the user's data to support high-level decision-making.

SERIAL 13133-RFP

Data Management
VUEWorks® is capable of linking directly into spread sheets, MS Access, SQL, Oracle, and any ODBC compliant
database. Linked data can be used to auto populate drop down lists, populate VUEWorks® modules (such
as asset condition like PCI or PACP ratings, or ownership information for Service Calls), trigger work orders
(e.g. SCADA data), is available for reporting, and is a great way to maintain visibility into legacy databases without
the cost or complexity of migrating the data into VUEWorks®. Linked data can also be associated with GIS
features, allowing spatial queries to perform on data that is external to VUEWorks®- such as SCADA.
In the screen shots shown above, a legacy MS Access database for residential water meter reads has been linked
into VUEWorks® and associated with the residential parcels layer. Notice the tab groupings in the lower left panel
of the main screen, which is showing the 'Databases' tab, and the sub-tab labeled 'Res. Meters'.
External databases can have any type of data in their columns, notice the hyperlink labeled '1-90 Form' -this is a
web form that opens, allowing new meter reads to occur and be recorded into the external database. Because
VUEWorks® is a 100% web-based application, as soon as the new data is collected from the web form it is
immediately available for display, reporting, and other uses. Data Link can link to an unlimited number of external
databases and tables, to views of tables, and directly to Excel spreadsheets. Tables can contain links that launch
3'd party applications.

Above VUEWorks® see Utility Billing, Permits, Licensing, and other modules from a leading Finance/ERP system
linked into VUEWorks®. This inherently makes the external Financial & Permitting data geospatially enabled -
supporting such operations as mapping all accounts more than 30 days past due, or showing all parcels with open
permits that need an inspection (for routing purposes), etc. Not only can VUEWorks® read and expose data
from these modules, via the hyperlink shown, the module can be launched and opens directly to the record.
External data can be exposed through VUEWorks® geospatially via the GIS or non-spatially.
VUEWorks® also has the capability to migrate legacy data directly into VUEWorks® forms. A common example of
this is to create a VUEWorks® work order for every historic legacy work order. VUEWorks® has done this for
clients that desire to have a full work order history pulled from their legacy system into VUEWorks®. This requires
separate data migration services, but is typically very simple.
Using the Data Linking functionality VUEWorks® links associated documents directly and can interface with the
external government databases. Below is an example of a VUEWorks® to EPA MS4 data:

Using the Data Linking functionality VUEWorks® links associated documents directly and can interface with a
document management system, like OnBase or SharePoint. Below is an example of a VUEWorks® to the Tahoe
Integrated Information Management System SharePoint site:
Using the Data Linking functionality in VUEWorks® links associated to AutoCAD documents directly and can
interface with a CCTV system, SharePoint. Below is an example of a VUEWorks® linked to the Granite XP:

VUEWorks® was acquired from Kleinfelder in 1999. VUEWorks® product release dates occur on an annual/bi-
annual basis on a schedule that is consistent with ESRI ArcGIS updates. The issues released have been versions:
VUEWorks®, 2009, 2010, 2012, and most recently released version 10.1. Throughout the software's lifetime there
have been no product de-installations or called/rolled back release dates due to issues with the software. In
addition, VUEWorks® has not experienced issues with the systems functionality, performance, or availability
schedule.
System Integration Plan
System integration shall be performed by VUEWorks® in-house programming staff. The integration that is
required shall be defined during the Tier 2 implementation plan and the associated workflows shall be
documented as part of this process (Please refer to lines 22 through 55 of the Project Plan to review business units
for which process documentation shall be performed}. A series of on-site and web-based meetings shall be used
to define the requirements of the integration. This process shall involve the creation of the following plans which
are described below:
• System Implementation Plan,
• Project Management Plan,
• System Implementation Schedule,
• Data Security Plan,
• Master Test Plan,
• Change Management Procedure,
• Training/Education Plan
System Implementation and Support Services
Implementation and training shall also be supported onsite by VUEWorks® staff.
VUEWorks® proposes two Tier 2 Implementation iterations- one each for the MCDOT's departments as part of
Gates 2 (business documentation} and 3 (configuration and go live} of the project plan. Data linking shall be
performed during the two Focused Tier 2 Implementation iterations. Data migration plan shall be developed
based on data requirements and integration needs gathered from existing documents such as the Current State
document and series of discovery meetings with data owners.
VUEWorks® shall support MCDOT with their assessment of bar coding needs, assist with demo of potential
solutions and make a recommendation based on the findings from workflow analysis and mapping process.

Implementation Plan - Requirements Review
The project kickoff meeting shall be held at MCDOT Offices on site with the VUEWorks® staff. This initial task shall
include review of the scope, schedules, confirmation of the project team's contact info and understanding of roles
and responsibilities. Prior to the kickoff meeting the MCDOT shall provide to VUEWorks® a project organizational
chart that contains the MCDOT's VUEWorks® project manager (VWPM). The VWPM is the individual primarily
responsible for the successful implementation and subsequent ownership of the VUEWorks® system. There may
be multiple VWPMs, one for each Department and/or Asset Class. It is paramount the VWPM(s) be prepared to
take ownership of the application during implementation and training to ensure success for both the MCDOT and
VUEWorks® Implementation Team.
• Software Needs Assessment: The MCDOT has determined the VUEWorks® software modules it requires.
See the cost schedule a complete module listing and license count
• Hardware Needs Assessment: The VUEWorks® Implementation Team met with the MCDOT project team
Data Review {Tabular, GIS)
The MCDOT and VUEWorks® Implementation Team shall perform an internal review of the MCDOT's GIS data
and related tabular data. The VUEWorks® implementation shall use existing GIS data. As the MCDOT acquires
additional GIS data during current and planned projects shall use its training from this project to set up and use
the data in VUEWorks®.
Initial Installation
VUEWorks® shall be installed and configured on the MCDOT's network. Specifically, VUEWorks® shall be installed
on the same server that ArcGIS Server is currently installed on. Installation shall include the installation of
VUEWorks® and validating its connection to the ArcGIS Server map connection.
Configuration
Once the software is installed on the MCDOT's servers, The VUEWorks® Implementation Team shall configure
the software for proper use. This shall be performed via the Tier 2 Implementation.
MCDOT shall make a system administrator available to VUEWorks® during the installation process.
1. Ensuring (with IT) that backups are being performed.
2. Appropriate permissions and rights are configured for System Administrators as well as General Users.
3. Initial Performance Testing of the VUEWorks® software.
4. That the "installation" is known to The VUEWorks® Implementation Team for future work on the project.
System-Level Configuration: This phase of the Tier 2 implementation occurs in two steps:
1. Step 1: Includes business documentation and workflow definition for all groups defined in lines 22
through 55 of the Project Plan. This documentation shall include process and workflow definition as
well as best practices. In addition, the order of deployment of each group's configuration shall be
defined in this step.
2. Step 2: shall include the configuration, acceptance testing, formal acceptance, training, and go-live for
each business unit/group, rolled-out in a phased fashion. These functions are defined in lines 56-169 of
the project plan.
Module-Level Configuration (process rechecks): Because all business units/group's VUEWorks® implementation will
be developed in the System Level Configuration above, the module level configuration shall constitute a recheck
between each business unit and reviewing for any potentially overlaps or duplications of configuration. If any are
identified, they shall be remedied as part of this task defined in Gate 4, lines 170-185 of the Project Plan. All
module-based configurations shall be performed per the Tier 2 Implementation description below. The MCDOT is
responsible for providing subject matter experts (SME) on MCDOT work flow procedures and reporting needs. The
VUEWorks® Implementation Team shall meet with a limited number of departments and the appropriate staff in
__ l_l~.t..~--- .... _ .1..L- ·------~----1 f"'ri.Jir' ----1.L1-- \/llf""'\AI- .• 1._@ 1"\ •• _: __ .L 1\11------·-l-\ .&..- -..1-.a.-·-·--:·-- .!..1-- -·-·-·--·-·-:-.&.- ----L:- ...• -.1..:-·- L-··

each of the following modules:
1. Condition Module
2. Work Order Module
3. Projects Module
4. Resource Manager Module
5. Request Portal Module
6. Facilities Module
Configuration activities shall focus on the identification of standard nomenclature that shall be used across
modules and shall identify Asset Classes and Asset Types that shall be managed in VUEWorks®.
The VUEWorks® Implementation Team shall configure, initially document, and train the MCDOT team on
workflows for each of the departments selected for Tier 2 Implementation.
End-User Training
End-user training shall be focused on the productive use of the system. This training is typically done with a 'train
the trainer' in the same room as the end-users, and a The VUEWorks® Implementation Team instructor conducting
the training on site. This puts the MCDOT's trainers in real scenarios where they must participate by using their
Tier 2 Implementation exposure to the application; and marks the beginning of the system's handoff to the
MCDOT.
Users shall be trained based on their specific use of, and involvement with, the system. As training occurs, users
shall be exposed to situations that are specifically related to their job responsibilities and trained on how to enter,
update, and review system data. All users shall have access to the on-line resources created for this project,
specifically user manuals and on-line help available in the VUEWorks® application.
System Support and Maintenance Mode
At this point, VUEWorks® is operational and a period of time shall elapse after Go-Live to let staff settle into the
system and use it productively in their normal business operations. The next phases of any expanded project may
be planned and executed at this time.
Support consists of telephone and remote access support during normal business hours 8am- 8pm EST, Monday-
Friday excluding holidays. Remote access is used to login into the customer's network and directly trouble shoot
issues, install planned upgrades, and install full version releases. Support is covered by the annual software
maintenance agreement. Upgrades and version releases are provided to all customers' current with software
maintenance.
VUEWorks® implementation costs are not tied to staff or hours- they are tied to the tiering of the implementation
(1, 2, Custom). This allows VUEWorks® to seamlessly utilize certified implementation partners or its own staff. This
approach gives the MCDOT insurance that if project staff changes, the cost shall not. See the cost proposal section
of the proposal for VUEWorks® recommended Focused Tier 2 Implementation costs.
Preliminary Implementation Plan
VUEWorks® offers two implementation tiers and for this project the VUEWorks® Implementation Team
recommends a Tier 2 Implementation.
Tier llmplementation: No formal scope of work is provided for Tier llmplementation.
VUEWorks® software training is provided to internal managers and/or VUEWorks® administrators specifically to
create a group of 'train the trainers'. Tier llmplementation is appropriate for organizations that wish to expand
the use of VUEWorks® over a phased time period, where expansion of the system shall be performed by internal
staff. Tier llmplementation does not result in a turnkey VUEWorks® system ready for use by the entire
organization. Instead, it produces a group of managers and/or VUEWorks® administrators that are trained to
configure VUEWorks® and complete the system's build out over time.
Tier llmplementation is composed of both onsite and remote training. On site training typically kicks off the
trai~ing process, and covers the purchased modules in depth in a classroom like setting. R~1j1ot~,ltraini;'fi:~{?il
extremely cost,effectiveway to cover topics that can be addressed'jlr;, a couple hours- whi~h is app~opriate 'once

the initial onsite training is complete. Training is hands on and covers all aspects of VUEWorks®' tools and user
interfaces/screens that provide end user configuration of each purchased module. VUEWorks® can use existing
workflows and business processes, or desired work flows and business processes, to partially structure the training
sessions. This allows training to be based on the actual 'go live} configuration of the system. This benefits the
trainees in that a portion of actual system configuration work is being performed through the course of training.
Tier 2 Implementation: A formal scope of work is developed for Tier 2 Implementation. The scope of work is
developed by VUEWorks® or through VUEWorks® partners and is based on formal scoping meetings. An
implementation scope of work, timeline, and budget are developed for Tier 2 Implementation and approved by the
client prior to starting work.
The VUEWorks® system is fully configured as a turnkey system ready for use by the entire organization. Tier 2
implementation is appropriate for organizations that do not have the internal staff to expand the system's scope of
use and/or wish to 'go live' with multiple departments or lines of business all at once.
Tier 2 Implementation contains Tier llmplementation, and can include the following as part of the scope of work:
• Exhaustive workflow and business process mapping,
• Work order and service call user interface configuration specifications,
• Creation of work order and service call forms,
• Creation of reports and dashboards,
• GIS data development,
• Linking to external databases and migrating data from external systems into the VUEWorks® database,
• Integration with 3rd party software systems such as financial systems (e.g. for payroll, purchase order, or
inventory integration),
• Training all levels of system users, to include managers, VUEWorks® administrators, non-technical field
staff, and mid-level management.
Tier 2 Implementation can be provided to any VUEWorks® client at any time to assist with expanding the system
into new areas of the organization or to improve existing use of the system. Tier 2 Implementation can be scaled
to include myriad services as mentioned above, or it can be tightly focused on a single business process.

Focused Tier 2 Implementation: A common application of a Tier 2 Implementation is what VUEWorks calls a
Focused Tier 2/mp/ementation. This approach to implementation tightly focuses on a small number of very well
understood and documented work management activities. The customer is also prepared to take ownership of the
configuration and subsequent administration of VUEWorks® during the course of the Focused Tier 2
Implementation. This deepens the customer's to participation in the implementation and training process, typically
resulting in significant progress being made in the customer becoming self-sufficient in implementing additional
work and asset management activities without VUEWorks® professional services.
Tier 2 Implementation:
The implementation shall occur in a stepwise process moving from one department to the next over a period of
time. Implementation and training shall focus on the MCDOT's first selected department and specifically
addressing their assets and related work flows.
Kickoff Meeting
The goal of this meeting is to clearly identify the subject matter experts, VUEWorks® Administrator(s), and other
points of contact between VUEWorks® and the Customer. The meeting shall establish dates and over all initial
project timeline.
Workflow Definition Workshop
Implementing the work management modules of VUEWorks® requires careful identification of the work activities
to be managed in the system and the relevant data to be recorded at the work activity level. Work activities are
the most granular level of work management and form the basis for asset specific work and preventive
maintenance management, reporting, and analysis.
Prior to the first onsite implementation workshop, Customer staff shall identify 2-4 well understood asset
specific work activities and 2 to 4 service requests issues related to the same asset types as the work activities.
Any supporting documents such as paper based work orders, inspection forms, service request documentation,
etc. shall be provided to VUEWorks® via email. VUEWorks® shall review the information przior tp 1the workshop;q
VUEWorl<s@ shall hold .2 .separate workshops to step through the W<i>rk activities and servic~ req~'~stls;~es. ·

The goal of the remote workshops is to begin defining how VUEWorks® shall be configured before the first on site
workshop. The process of defining work activities in a work order system can be complex initially. This stems from
the fact that any given work activity is composed of several parts: work planning, work assignment, doing the
actual work, and closing out the task or work order correctly. The challenge in implementing any work
management system is that the above steps are often not completely understood by a single individual; in fact it is
more common for these steps to be handled in a sequential fashion with different staff largely confined one or two
parts of the sequence. In addition, when the client works with VUEWorks® to define these steps it is common for
changes to be introduced to the work flow process now that it's being completely reviewed. Finally, VUEWorks®
can bring a great deal of flexibility to the entire workflow. Collectively, these factors create a time period during
the implementation where the workflow surrounding a work order is somewhat fluid. Therefore, the initial
remote meeting is designed to get the client thinking about all these moving parts so the actual onsite meetings
can be as productive as possible.
Prior to the remote meeting, the MCDOT shall identify the subject matter expert(s) (SME) for each of the work
activities, as well as the overall VUEWorks® Administrator. The SME(s) needs to understand the entire workflow
for any given activity that shall be managed via work orders but they do not necessarily need to be the
employee(s) who perform the work. The purpose of the SME(s) is to break down each of the work activities into a
step by step series of events, where at each step key information to be collected is identified, and the actions
necessary to move to the next step are defined.
The VUEWorks® Administrator is the lead person(s) responsible for administering the application. The VUEWorks®
Administrator is responsible for taking ownership of the system and shall expand it over time. As such, they shall
need to understand the workflows, how to use the various configuration user interfaces to build new workflows,
master the report designer, and more.
Workflow Workshops
The first onsite workshop has two goals:
1. Finalize and sign off on the work order activities, service request issues, and the associated workflows.
We shall spend a half day on each workflow with significant input from the workflow SME(s). The
VUEWorks® Administrator must attend.
2. Expose the SME(s) and VUEWorks® Administrator to the actual work management modules in VUEWorks®
to begin designing actual work order forms, service request issues, reports, and dashboard gadgets.
Furthermore, data entry requirements for employee names, pay rates, rate types (e.g. Standard,
Overtime, etc.); similar information for equipment; information for inventory shall be identified.
Populating VUEWorks® with this data shall be tasked to the VUEWorks® Administrator.
Workshops for Work Order Specification
The actual content of the work order form in VUEWorks® is highly configurable. The contents of the work order
has two drivers: 1) the flow of the work activity, 2) data to be captured in the course of performing the work
activity. This workshop shall be scheduled for each work activity being configured in VUEWorks®. Based on the
completed workflow exercise, the VUEWorks® implementation team shall have a draft work order specification
already built for each work activity, and a concomitant work order form set up in the software for live interaction
during the workshop.

The goals of the remote work order specification workshops are:
1. Sign off on draft work order forms and service request issues for use in VUEWorks®, which shall be
finalized during the second onsite workshop,
2. Have live work order forms in the system for the VUEWorks® Administrator to begin interacting with prior
to the second onsite workshop.
3. Have draft reports set up in VUEWorks® for the VUEWorks® Administrator to begin interacting with prior
to the second onsite workshop.
Workflow Workshops
This workshop marks a turning point in the implementation process. Final changes shall be made to the work
order specification documents as well as the actual work order forms in VUEWorks®. VUEWorks® shall update the
specification documents during the workshop; however the VUEWorks® Administrator shall perform updates to
the actual work order forms in VUEWorks® as well as service request issues. The SME(s) and the VUEWorks®
Administrator shall step through the workflow process in a role playing exercise to test drive the configuration.
VUEWorks® shall step through the reporting capabilities of the system, and the VUEWorks® Administrator (and
others in attendance as appropriate) shall run reports and learn how to create their own reports.
The goals of the 2nd on site workshop are:
1. Sign off on the work order specification and service request issues,
2. Final configuration of the work order forms in VUEWorks®,
3. VUEWorks® Administrator is now responsible for existing work order configuration (both the workflow and the
content of the actual work order forms},
4. VUEWorks® Administrator is now responsible for creating reports.
Data Conversion and Migration Methodology
VUEWorks® has extensive experience in the migration of data from the multiple ERP systems into the VUEWorks®
solution. VUEWorks® is currently conducting a migration for the Springfield, MA Water and Sewer Department
who is currently implementing VUEWorks® and the current systems in use at the MCDOT. The next section
contains a sample migration task list (Assets only) that is being used for this project. VUEWorks® has prior
experience conducting these migrations as a team for other clients with success.
VUEWorks® shall assist the Client with the following:
1. Document the functional requirements for the asset data by asset type.
2. Investigate exiting asset systems operational features and database structure for asset data.
3. Provide Client system administrator(s) with an overview of VUEWorks® table structure, data views and
configuration options.
4. VUEWorks® shall prepare a detailed work plan that covers all aspects ofthe migration with assistance from
the Client. Sections of the work plan shall be created as required to meet the functional requirements
of the Client. The following aspects of the migration shall be covered in the work plan:
a. Functional requirements for the asset data by asset type.
b. Identification of asset types and fields that shall be migrated to GIS feature classes for use by
VUEWorks®
c. Identification of asset types and fields that shall be migrated to the VUEWorks® Facility
module.
d. Identification of the asset hierarchy that shall be replicated in the VUEWorks® Facility
module.

e. Identification and migration of drop down field data that shall be transferred. The functional
aspects of the drop down fields shall be migrated to GIS domains or VUEWorks® drop downs
as appropriate.
f. Define data structure and templates required in the GIS or VUEWorks® Facility
module.
g. Identification of any special considerations for the migration. (For instance, numerical data
should be migrated to a numerical field even if numerical data is currently stored in a text field).
h. Identification of any data that shall not be transferred (obsolete data or data that has no value
to the Client).
i. Document data integrity issues discovered during the process. Data integrity issues consist
mostly of miss-spellings and/or inconsistent terminology. While it may be possible to address
some data integrity issues, VUEWorks® shall be limited to documenting any issues discovered
that may be addressed in the future by the Client.
j. Plan to accommodate final migration of data immediately prior to the Go Live date.
5. Client shall review the work plan with VUEWorks® for approval. The review requires VUEWorks® to
attend one onsite meeting. Additional meeting time can be arranged as needed using telephone and/or
screen sharing technology.
6. VUEWorks® shall execute the work plan collaboratively. VUEWorks® shall be responsible for tasks that
require VUEWorks® expertise with SQL Server and the VUEWorks® database.
Asset Data Migration Work Plan, GIS and VUEWorks® databases populated accordingly. This sample task list can
be used as a gujde for VUEWorks® data discovery, documentation and overall conversion plan for MCDOT as part
of this project. VUEWorks®' past experience, with applications like lnfor/Hansen, Maximo, and HTE shall provide
MCDOT with a seamless transition to the proposed solution.
{Please see Planned Progress Chart attached)
The Agile Process -Applications Development, Documentation, and Maintenance
The agile process is based on collaboration and the ability of the development team and the stakeholder
organization to work together openly and collaboratively. It relies in the constant inspection and adaptation of the
process itself and the backlog of requirements. As such, it is a communications-intensive approach to software
development. The collective group of agile practices VUEWorks® actively employs on software development
projects is known as Serum. It is a set of guidelines and practices that encourages frequent communication and
collaboration and intensely focused developed effort throughout the life of a project. It is an iterative approach
and is described in detail below.
Backlog Development
VUEWorks® shall work closely with MCDOT to develop a backlog of requirements and critical issues for the
database design and implementation and software development. The backlog shall initially be developed at a high
level.
After creating the backlog, VUEWorks® shall work with MCDOT to prioritize the user stories (i.e. requirements)
within the backlog to ensure that the most valuable functionality is developed/addressed first.
Iteration Planning
VUEWorks® teams work in two-week iterations. These iterations are the same whether VUEWorks® are executing
system architecture and workflow, database schema design, or application development user stories. At the start
of each iteration the development team and MCDOT shall conduct an iteration planning meeting. Upon selection
of the backlog items to be addressed during the iteration, MCDOT and VUEWorks® shall collaboratively discuss
the user stories selected in detail. This discussion shall allow everyone involved to adequately define the
requirements and

conditions of satisfaction so that VUEWorks® can provide high quality deliverables at the conclusion of the iteration.
Following this discussion, the VUEWorks® team shall internally decompose the user stories into detailed tasks to be
accomplished during the upcoming iteration. Time estimates are placed against the tasks and VUEWorks® team
members select the tasks they shall work on during the iteration.
The Iteration
Following the Iteration Planning Meeting, the development team shall immediately begin working on the
functionality, to be developed during the iteration. VUEWorks®' development team is completely dedicated to
the user stories in the iteration without disturbance from external influences or other project work. They shall
work closely with MCDOT during the iteration to ensure that what is being produced is precisely what the MCDOT
requires. The work of the sprint typically includes designing, coding, testing, and documenting software
functionality, but frequently shall include data modeling outputs, architecture or workflow diagrams, user
interface mockups, and any other work products developed during the iteration.
Iteration/Release Review
At the conclusion of each iteration, the VUEWorks® development team shall conduct a review meeting in which the
functionality developed during the previous iteration shall be demonstrated live. VUEWorks® shall review the user
stories that were included in the iteration and demonstrate and software functionality developed that correlates to
each user story for the initiative. There shall be no presentations (i.e., PowerPoints) of "prototyped" functionality.
MCDOT shall get to see real live demonstrations of actual functionality.
In addition to the demonstration, VUEWorks® shall solicit feedback from MCDOT on the functionality
developed. These review meetings provide a very high level of visibility into VUEWorks®' project process and
allows for an effective feedback mechanism for the development team.
Agile Engagement Roadmap
---
Overarching approach and technical guidelines
Within the bounds of VUEWorks®' iterative Agile Project Management methodology, VUEWorks® follows the same
generalized approach for all successful projects that VUEWorks® execute. VUEWorks® has continually refined and
validated this software development process on projects ranging from small Metropolitan Planning Organizations
to multi- million dollar federal application development projects.
1. Documentation and validation of user and system workflows
2. Preparation and validation of user interface mockups
3. Approval of workflows and mockups commencing in iterative software development and delivery
4. Iterative testing, QA/QC, and generation of documentation
5. Eliminates scope creep and keeps project on schedule and within budget

System Configuration
Configuration status accounting shall include recording and reporting of the change process. The goal of
configuration status accounting is to maintain a status record of all items in the configuration baseline, thus
providing traceability of all changes to the AMMS. Configuration status accounting shall answer the
following questions:
• What changes have been made to the system and when were they made?
• What components were affected by this change?
The major activities of configuration status accounting include:
• Identifying the configuration status information to be recorded
• Maintaining a record of configuration changes upon release of the code
• Reporting the status of AMMS system configuration management
At the MCDOT's architecture level, only MCDOT's PM shall have the authority to approve and make changes to
the components of the architecture baseline. Before considering any change, the potential change must be
documented using a AMMS Change Request (CR) form. This form describes the desired change, the justification
for the change, the impact of implementing the change, and the eventual PM's decision regarding the proposed
change. CRs normally document code changes originating from the Lead Analyst, but a CR may be submitted by
any of the project stakeholders.
The CR shall be submitted to the PM who shall route the CR to each Lead Analyst. Each Lead Analyst shall fill in
the Impact Assessment (lA) section in the CR documenting the impact of the change upon the phase/component.
if a phase/component shall be affected by the change, the lA shall be returned with notations or comments
documenting the Lead Analyst's technical analysis, the impact on the phase/component schedule, cost, and labor
resources, and any suggested alternatives to the proposed change. if a phase/component shall not be affected by
the change, the lA shall be returned indicating "no impact".
The PM shall meet either in person or by teleconference to discuss proposed changes. The PM shall use the lAs
and the meeting discussion to decide whether to approve or disapprove a proposed change. The PM meeting
minutes shall clearly document its decisions and the rationale supporting its decisions. These PM minutes shall be
distributed to all project stakeholders. Figure 2-1 represents the Change Management process:
FIGURE 2-1 CM Process (Below)

The following sections present the configuration status accounting activities for the AMMS:
Identify Status Tracking Information
The following configuration status information shall be regularly tracked on the AMMS-project level:
• Current architecture document
• Associated components
• Open Change Requests
• Closed Change Requests
• Components affected by Change Requests
At the component level, the CRs shall provide configuration status information for each individual AMMS
component.
Maintain Status Tracking
Project level configuration status information shall be recorded and maintained in a centralized repository that
using Subversion. This repository shall contain the current architecture as well as any proposed and
implemented changes to the project. Component configuration status information shall be recorded and
maintained in respective component folders.
Since the configuration status information is crucial to ensuring the integrity of the baseline, its components, and
the CM process, only authorized personnel should update this data. The PM shall identify the specific personnel
authorized to update the status information changes and the specific changes that each person is authorized to
make.
Report Status Tracking
Regular monitoring of the configuration status information shall enable the Architecture Group and the
Deployment Group to identify trends and potential trouble spots in the AMMS. Each of the two groups and the PM
in collaboration with the County's IT shall determine the reports required for performing this analysis.

User Interface Specification Document
Business Context
Provide an overview of the business organization sponsoring the development of the system, including the mission
statement and organizational objectives ofthe business unit.
The AMMS project shall allow MCDOT to implement an enterprise Asset and Maintenance Management solution
to support uniform business processes, introduce more functionality to the business in an automated system, and
provide better integration with other County systems and technologies such as GIS, OnBase, and payroll systems.
The objective is to collectively discover, design, and implement a solution that, if possible, utilizes an enterprise
system to serve the needs of all departments, or at a minimum, consciously select multiple systems which,
together, offer a comprehensive maintenance management solution.
Scope
Describe the scope of the system to be produced.
The scope of the AMMS Project is to implement a COTS solution that fulfills the requirements as specified in the
RFP document. MCDOT recognizes that some COTS solutions may not have the complete required functionality
needed and that customized code shall be required.
" Asset Management
• Service Request
• Work Request Management
• General, Scheduled and Preventative Maintenance
" GIS Mapping
• Reporting/ Analysis Functionality
• Mobile
User Characteristics
Identify each type of user of the system by function, location, and type of device. Specify the number of users in
each group and the nature of their use of the system.
Data Analysis Requirements
Analysis within the system shall be fully compliant with the with MCDOT requirements.
Data Reporting
The system should provide automated reporting solutions based on user/department needs.
The system shall support ad-hoc and query style reporting that provide for query functions for authorized users to
generate ad-hoc reports without requiring technical staff assistance.
Mapping Requirements
The system shall use the County's current GIS mapping methods and procedures.
Provide GUI support for assets, analysis and mapping functions: All features shall support new and planned.
Provide a complete GIS description using MCDOT's current enterprise GIS system network, including analysis,
reporting, and mapping tools that use the County's GIS data for managing assets.

One item of note- DTS/VUEWorks shall work with the County to determine the correct data model and GIS
data structure to track the temporal nature of the Asset Network. This is a feature available within the Esri
Geodatabase model that can be configured for each Asset Class and Asset Type.
Acceptance Testing
The plan provides the approach that shall be used to manage the testing on MCDOT's Asset and
Maintenance Management Software (AMMS). The process identified within this plan shall not only ensure a
better quality product, but also discuss a process and tools to manage the testing process, which shall meet
the MMS requirements. The development of this document is a requirement as per the AMMS RFP # 13133.
The overall approach that VUEWorks® shall employ to conduct effective testing of the AMMS is to start with
creating well-defined user stories, from reviewing the requirements matrix developed for the project. A user story
(a requirement or a part of a requirement) is a feature oriented task that covers who, what, and why about the
task. A well-defined user story is very closely lined up with a test case specification for a component. Thus, a good
user story leads to a good test case which ensures that a component is accurately completing the task at hand.
Software/Tools for Testing
VUEWorks® developers shall use load and performance testing software/tools as directed by MCDOT. Load
and performance testing and capacity evaluation shall be conducted once the application is installed at the
test environment. Test results shall be tracked and reported as the test deliverables.
Types of Testing
The testing approaches that VUEWorks® shall undertake can broadly be sub-divided into confirmatory and
investigative testing categories. Confirmatory testing is pursued through a combination of test driven
development (TDD) and Agile/Iterative Testing while investigative testing regimes are traditionally defined in
consultation with the client but may include exploratory or scenario based testing along with some component of
user testing of the system components as well.
The types of testing that shall be undertaken to ensure a good quality product overall on the AMMS are:
• Unit Testing
• Integration Testing
• System Testing
• Load Testing
• Security Testing
• Usability Testing
• User Acceptance Testing
• Beta Testing
Managing Testing Processes
Redmine and Microsoft Excel spreadsheets shall be used to manage the testing process on the AMMS. All
issues/defects, test cases for user stories, testing checklists, and integration test items shall be documented
in Redmine, and shall be aligned with the individual specifications/user stories that they are attached to.
Testing cycles shall typically be 1-2 sprint cycles after the development of a software component, or a set of
user stories. This shall ensure that every component gets tested early on, and lead to a good quality product.
Issues/Bugs reported can be classified as "Must Have", "Should Have", and "Nice to Have"- which shall help
the prioritization of tasks. Custom categories or types of Issues/Bugs can be created for the AMMS.

VUEWorks® and its parent, DTS have a wealth of training related
experience. In fact, DTS received an award from the American Planning
Association and Federal Highway Administration for its development of
the Sociocultural Effects Evaluation training program, delivered
throughout the State of Florida. Moreover VUEWorks®'
training staff has conducted training for clients throughout the United States. Specific to VUEWorks®
implementations, training and support is one of the most critical of the project phases. To this end,
VUEWorks® has extensive help documentation as well as routinely creates implementation specific materials.
We have Instructional Systems Designers (lSD) on-staff who are
dedicated to developing training curriculum, resource toolkits, digital
tooltips, and user manuals. Additionally, VUEWorks® have fuil service
multimedia capabilities to support HD video capture and production,
DVD interactive training media, and 3-D animation. VUEWorks®'
company is able to provide under one roof a combination of
experience and services that spans from Transportation Planning
professionals, to GIS and Asset Management technologies, to website
design, programming and data base development, to training
development, and the multimedia production capabilities to provide
graphics, animations and video to support all of VUEWorks®'
disciplines.
VUEWorks® /DTS personnel have delivered numerous training courses for clients from on-line courses, to computer-
based training courses, to interactive CDs, to video, video simulation and tabletop exercises, to stand-up training
courses.
VUEWorks®' personnel have an extensive background in training for a variety of types of delivery. VUEWorks®'
personnel have not only written the courseware content, but have also designed and developed the technology
format in which it is delivered. VUEWorks®' staff includes instructional designers, courseware developers,
videographers, graphic artists, 3-D animators, and programmers.
VUEWorks®' unique combination of in-house video production and in-house web designers and programmers
makes it convenient for VUEWorks®' clients to use us on a variety of projects. VUEWorks®' references, project
history and client list demonstrate the consistency of production and client satisfaction.
VUEWorks® can conduct targeted training for the groups identified by MCDOT in a series of workshops.
VUEWorks® has found that it is usually not good to have more than 20 potential users in any one workshop so
VUEWorks® would suggest breaking up into a series of workshops as well as provide direct training to those
who are performing a specific task. VUEWorks® can do these as one-on-one trainings or in a group as well.
VUEWorks®' training approach s h a II be on-site, however, in terms of follow-up and on-going training,
VUEWorks® provide a series of training types:

In addition, VUEWorks® is willing to work with MCDOT to determine other training types/delivery methods as
VUEWorks® understand that not every user learns a system in the same way. Here is an example of what is
available as potential delivery mechanisms:
Training Workshops
Training workshops shall be an important part of the development and implementation of this training. The
workshops shall be geared specifically to roll out the course and shall include training workshops for:
• Internal Users (a variety of types of users shall be trained)
• External Users
• Training the Trainers
Online or Web-based Training
Web-based or on-line training is the most effective and most contemporary training methodology for software
system training. The training can be modified and changes can be implemented immediately, as opposed to
printed and published handbooks that can be outdated a month after its publication. Decisions shall need to be
address to determine which types of users and courses shall be developed to meet specific
need:
• Employing or not employing an LMS (learning Management System)
• Graded or not-graded structure/design
• Simple confirmation of a trainee finishing the course (non-graded)
• Certificate awards for finishing the course
• Training that is available at the individual's own pace
• On-line training available during certain time frames

Manuals (Handbook) and Documentation
User manuals shall be user-friendly with an inviting style, easy-to-use reference format, and with SMART Tips and
practical information. These shall also be available in on-line, pdf formats, which also makes updating page
changes less costly (instead of re-printing and publishing, the on-line pdf is updated and users are notified).
Resource Toolkit
The Resource Toolkit is a collection of training resources for specific users. These can be developed and targeted
to the user. For instance, an external user of the system does not need to have all of the training information that
a systems operator or program staff person needs. So resource toolkits shall be geared for the end user. These
shall be a combination of quick helps, handouts, ready references. They shall also include:
• Flash Video "How To" demonstrations (audio narration and screen captures that are a few seconds to a
few minutes long)
• Interactive DVD with resources, maps, job aids, videos and animations as required
• Printed Guides for Specific User's
Built-In Tool Tips
The software application shall have built-in tool tips, helps and prompts for
users.
Train the Trainer
Train the trainer courses shall be important for the sustainability of systematic, on-going
training.
Webinars
Training webinars are a real advantageous form of training because the training can be made available as needed
to address specific training needs. These courses can be flexible and customized for large groups of users or for
select, small groups.
Training Plan - End User Training
VUEWorks® shall step through the use of the system with actual end users in a classroom setting. The VUEWorks®
Administrator and the SME(s) shall attend and shall play a dual role: they are both receiving training as well as
assisting with the training. The format is informal, where VUEWorks® staff shall take the new system users
through an overview of the application, and then proceed to walk through each work order activities correctly. It is
critical that the VUEWorks® Administrator and the SME(s) understand that their role throughout the
implementation process has been to correctly define and articulate the workflow process, with signoff at key steps
along the way.
The VUEWorks® Administrator shall be expected to have already taken ownership of the VUEWorks® configuration
prior to the end user training, and s h a II be fully capable of modifying the system as necessary to refine
the processes, workflows, and configurations. Training should occur in a MCDOT room/facility where trainees can
sit at a computer that has access to the VUEWorks® application. Doubling up or sharing a computer is often
beneficial. A projector and screen is useful so students can follow along with the instructor.
Enterprise Training w/ Context Sensitive Focus
This training option is the most thorough and comprehensive. The trainers begin developing the training
curriculum early in the system's implementation. The training staff works closely with the implementation staff
during the business process analysis phases of the project. This allows the training staff to perfectly understand the

MCDOT's workflow within the system on a user group by user group (e.g. "role") basis. The training team develops
comprehensive training programs for each role- where field users shall be trained in the use of the system as it
specifically relates to how they need to get their jobs done, and where supervisors all the way up to senior managers
are each trained to use the system specifically to their roles with the organization. An administrative role is included
-where the customer always has a person(s) trained in the use of the system across *all* roles.
This training option includes "context sensitive" training materials. VUEWorks®' training staff s h a II develop
customized online materials, CD/DVDs, popups, manuals, resource toolkits, job aids, etc. that are specific to the
MCDOT's business processes and user roles.
The model training curriculum is as follows:
Phase 1: Define all customer user roles and related business processes to be supported by the implemented
system. Done in tandem with the implementation team.
Phase 2: Develop training story boards with the customer's administrative user(s). The administrative user(s)
shall be the customer side PM to work with VUEWorks®' training team to approve training course content.
Phase 3: For each role, create context sensitive media/materials that are embedded into the application, help files,
as well as create training manual(s) in hardcopy and digital form.
Phase 4: Training
Number of groups to train is driven by the number of roles in the organization. Size of group is determined by
customer's timeline for training, facility size available, and complexity of the role being trained. Duration of
training is driven by the complexity of the role being trained:
• We prefer to limit training to 3 hours maximum in a given day to maintain optimal focus in the students,
and to allow normal work duties to continue as best as possible.
• Depending on the customer's ability to commit staff to training in lieu of performing their normal work
activities, the number of training sessions and the duration of the sessions may be affected.
Training is done on an exact copy of the production version of the Customer's final Vueworks® implementation.
Enterprise Training
This training option does not include a context sensitive focus. The trainers still begin developing the training
curriculum early in the system's implementation. The training staff works closely with the implementation staff
during the business process analysis phases of the project. This allows the training staff to perfectly understand the
MCDOT's workflow within the on a user group by new system user group (e.g. "role") basis. The training team
develops comprehensive training programs for each role- where field users shall be trained in the use of the
system as it specifically relates to how they need to get their jobs done, and where supervisors all the way up to
senior managers are each trained to use the new system specifically to their roles with the organization. An
administrative role is included- where the customer always has a person{s) trained in the use of the system across
*all* roles.
The model training curriculum is as follows:
Phase 1: Define all MCDOT user roles and related business processes to be supported by the implemented
software. Done in tandem with the implementation team.
Phase 2: Develop training story boards with the customer's administrative user(s). The administrative user(s)
shall be the customer side PM to work with VUEWorks®' training team to approve training course content.
Phase 3: Create digital and hardcopy training manual{s).
Phase 4: Training

Number of groups to train is driven by the number of roles in the organization
Size of group is determined by customer's timeline for training, facility size available, and complexity of the role
being trained.
Duration of training is driven by the complexity of the role being trained:
• We prefer to limit training to 3 hours maximum in a given day to maintain optimal focus in the students,
and to allow normal work duties to continue as best as possible.
• Depending on the MCDOT's ability to commit staff to training in lieu of performing their normal work
activities, the number of training sessions and the duration of the sessions may be affected.
Training is done on an exact copy of the production version of the Customer's final system implementation.
Train the Trainer
This a very effective way to train both the system administrator that is responsible for understanding the total
system, as well as individual users or groups of users. Under this training model, the MCDOT's administrator(s) and
other managers (as desired) can be trained by *either* the Training Team or the actual Implementation Team.
For single department (e.g. only Water, only Sewer, only Transportation) this is a highly effective method. It
creates an in-house expert in the use of the system that keeps external training needs to an absolute minimum.
Under this training model, basic training manuals as well as context sensitive focus can be incorporated where
desired.
The model training curriculum is as follows:
Phase 1: Identify customer staff that shall be trained and subsequently become in-house trainers.
Phase 2: Develop any context sensitive focus desired (can be done at a later date as well).
Phase 3: Train the trainers
This is done in a hands-on immersive setting- typically in a one on one setting. Training is heavily focused on
making the student(s) subject matter experts in the system, and then focusing on how the organization's business
processes have been implemented. By understanding the underlying system architecture it becomes much simpler
to train other users to use the system. This greatly facilitates the MCDOT's ability to configure and expand the
system without any further assistance.
We find that one on one training for a minimum of two 4 to 6 hour sessions is optimal. After the initial one on one
sessions, remote training is highly effective (e.g. Go To Meeting or WebEx). Duration of training is a function of the
number of modules in use more than the number of user groups/roles. As with the Enterprise training options- all
training is done on an exact copy of the production system.
Sample Training Outline
1. VUEWorks® panels (introduce them to the user interface)
a. Menu Area
b. Data Viewer
c. Map Viewer
2. Menu Area
a. The VUEWorks® Menu provides commands for viewing, reporting, managing, calculating,
analyzing, and setting defaults.
b. Shown to the left are all the main menu items available in VUEWorks®.
c. County's menu shall differ depending on which modules are installed, the Asset Classes County
manages, and County's individual user rights.
3. Data Viewer

a. Data Viewer: changes based on what you're looking at! VUEWorks® shall look at how to
customize the look of the home page search which is what displays when County login into
the application.
b. The Data Viewer is located in the lower left corner of the application window and serves as one
of the main points of interaction in VUEWorks® through three different modes:
i. When no assets are selected, the Home Page View is displayed here.
ii. When assets are selected, the Selection Set View is displayed here.
iii. DetFJiled Information about individual assets is displayed here with the Detailed Tab
View.
4. Modules
a. Core: Log Out, Set Preferences, Help, Administration, and Document Link are included in
VUEWorks® Core.
b. Work Management: Service Requests, Work Orders, and Resource Manager and inventory
options shall be shown if these modules are installed.
c. Asset Management modules for Valuation, Condition, Risk, Projects, and Budget Forecasting are
found under each user defined Asset Class.
5. Using the Map interface
a. Tools- Zoom in/out, Extents, Buffer, Identify
b. Print the Map- Setup templates, upload images etc.
c. Measure Tool- Line length, units are specified in the MXD I Polygon area
d. Expand/Shrink the map window -left bar click
e. Highlight Selected- Select individual assets at a time I or a group of assets- map shall refresh and
selected assets shall be highlighted
f. Zoom to Selected- Pick a group of features/and view their results in the data viewer- selected
assets shall be highlighted, and zoomed
to g. Identify assets-
i. Quick identify
ii. Selecting assets and returning results to the data viewer window
1. Selection mode- assets to select, walk through the different selection modes
iii. Using the buffer tool
6. Searching for information within VUEWorks®
a. Home page search: This is the default search window which appears when County login into the
VUEWorks® application. This can be configured for every community using the application. The
heart of the home page search is an address/location layer based on which the searches occur.
The administrator of the application can select the fields to search on -for example- Street
Name, Street No., City and locate any assets that in that area
7. Advanced/Binocular Search
a. For advanced users there is also the binocular search through which the users can search on a
specific layer/field etc. and locate any assets that match a criteria. Advanced search criteria can
be built here, to suit specific searches that some advanced users may want
For each system to be integrated as part of the MCDOT project, the DTS/Gannett Fleming team shall review the
existing business systems, their capabilities, APis, and databases, and shall provide MCDOT with an
Implementation Plan describing the approach to integration and data exchange procedures between the systems
and the enterprise asset management.

LEAD TEAM
Anticipated Duration of
Key Staff Title Roles & Responsibilities
Involvement with the Project
Jason Amadori, GISP Implementation
Principal in Charge Throughout Project
Lead AM/CMMS
Allen lbaugh, AICP, GISP Executive
Principal in Charge Throughout Project
Management Team
Sangeeta Reddy, PMP, GISP Project
Project Management Throughout Project
Manager
Greg Yarbrough Project Management
Throughout Project
Assistant Project Manager
Dave Paine Implementation Support
Throughout Project
Application Development Lead
I
Charles Brown Implementation Support I
Throughout Project
Implementation Lead
Kirsten Koehn, GISP Training Services
Throughout Project
GIS Integration Lead
Mark Sievers, AICP
Implementation Support Throughout Project
Testing and Training Lead/QA/QC
I
SUPPORT TEAM
Key Staff Title Roles & Responsibilities Anticipated Duration of
Involvement with the Project
Gary A. Lasham, P.E.
Implementation Support Throughout Project
Subject Matter Expert
Douglas T. Argall, OCA, GISP Implementation Support Throughout Project
DBA
Rodger E. Pine Implementation Support Throughout Project
Senior Technical Architect
David T. Pheasant Implementation Support Throughout Project
System Administrator
Adam R. Conner Implementation Support Throughout Project
Developer
Shili Implementation Support Throughout Project
Developer

Robert W. Wagner Implementation Support Throughout Project
Developer

1. is available from 8:00am to other
than VUEWorks' includes from Customer over the
cv''VtJ'n-"'" or e-maiL and !he reasonable effort to have the VUEWorks Software <u''"''v"'u
TII"IH1PTI\I in accordance with the documented
2. VUEWorks must be initiated either 252-2402 x2 or'"''"""'
Email: VUEWorks recommends the use of email as it serves as written record
of the event.
3. Customer shall "V'"h'm,,v one individual to
more ''"''""'""'
nangem:ents will be addressed on a case case basis and must be
Custom.er and VUEWorks.
email or issue defines the of a
support incident
5. VUE Works staff member unable to or when the Customer
for a support Customer will include in the message their name, their "'E''"'-'w"'"
of the steps that the and a call back number. Screen shots and r-nmr""''-"
of to the and any related detail
VUEWorks may not be able to rf''"''''"'n
6. related to m
customers' VUEWorks
incident involves a defect in VUEW orks will
reasonable effort to the at no
i. A defect defined as an issue with the software the normal course of onenmcm
the software does not function as documented due to an error in the software code.
ii. A defect is not an error message.
VUEWorks software has many that could generate error messages that are
VUEWorks but arc not VUEWorks software defects. These include
hut are not limited to:
1. ESRI GIS Software Server or
" MS Server
3. Server
4. Permissions
5. Hardware
6. Network
7. individual client computer issues
Individual Client computer issues are identified when the issue occurs
on a limited number of computers but not on all the
same VUEWorks user
b. VUEW orks reserves the to determine if an issue caused a VUEWorks software delect
or not
7. the issue detennined to be other than a defect in the VUEW orks software code then
VUEWorks will up to 30 minutes technical support no followed a of two
hundred dollars per hour per incident.
services do not include support for ESRI Software. While VUEW orks staff may
the Customer
that these of issues are best "'"""'""-r"'" channels.
9. VUEWorks handles incident reports in the

Each incident will be a of 0 to 4 as determined VUEW orlcs technical staff
VUEW orlcs will first attempt to resolve the issue with the Customer upon initial response. If the issue
cannot be resolved initial response then VUEWorks will to the request on the
of the issue as defined in the sections:
a. 0. Critical Issue. VUEWorks will start on the issue within
initial response and continue to work on the issue until the issue is resolved. LAau.'~"'"·"
Issues:
i. No user at the Customer site can on to VUEW orks
ii. The map does not on any user at the Customer's site.
111. No user at the Customer's site can create a Service Call or Work Order
b. .v,·mrn'1 l. Severe Issue. VUEWorks will start on the issue within one business of
initial response and continue to work on the issue nonnal business hours until the issue is
resolved of the occurs:
VUEWorks generates information that is incorrect
11. A feature enor messages that causes an stop
results
2. Issue. If the issue cannot be resolved the initial rcspon:--:e process
then VUEWorks will start on the issue within 5 business and resolve the issue
within 30 thereafter if any of the occurs:
1. An issue Customer that can be resolved on
feature
ii.
incorrect
iii. VUEWorks as a defect that can be avoided without loss of
a work around process
d. issues. If the issue eam1ot be resolved the initial response process
VUEW orks will document the issue but not be within any time
frame for the
l. related to the
11. enhancement request
features in VUEW orks that are not in the ctment
e. related to VUEWorks software. If an issue is determined to be
system malfunction VUEWorks will Customer
substantiated if the issue
occurs on one user cannot he on another user computer at
VUEWorks' test environment
VUEWorks, LLC. will reasonable effort based on the above If is
determined that the effort to resolve the issue is not included in this Annual Maintenance and
and the Customer will be advised that the work is not covered. At
the customer may be an for V UEW orks to continue the work at
to cost and scope.
10. Direct ,)'erver Access: In order for VUEWorks to the Customer agrees to
VUEWorks the means to control and transfer files with the Customer's VUEWorks
server. the GIS server and the the Internet.
a. VUEWorks for remote access but will work with any
system remote control and file transfer v«tJ"~"w"'"'
the Customer
b. allows VUEWorks support stafTto:
1. Offer the Customer software services to install and that
would otherwise Customer resources
u. for VUEW orks staff to VUEW orks at the Customer site for the
purpose of issues rP1'V\1'TPr1
m. to resolve issues an On-Site visit
c. Customers understands and agrees that if remote access to Customers servers is not then
the all response times documented in item 10 above will not

i. VUEWorks agrees to not access any other data or other than for
VUEWorks support ptn1Xlses.

TECHNICAL AND BUSINESS REQUIREMENTS
Business Requirements
ILOR for Service
Request for MCDOT Staff to perform some type of work. This can be initiated from an external citizen or an internal county customer.
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Party
The system shall provide the ability for both internal and external
1.1 M Comply Standard
customers to submit requests for service to the Operations Division
The system shall route the request for service accordingly based on
1.2 M Comply Standard
location and the type of request.
The system shall auto generate a request number for customer
1.3 M Comply Standard
tracking when submitted.
The system will collect the requestor, origin of request (internal or
1.4 external), requestor cmitact information, request location, details of M Comply Standard
request and type of request.
The system shall allow the request to generate work orders when
1.5 M Comply Standard
approved
The system will provide the requestor with automatic notifications of
1.6 M Comply Standard
request status.
The system shall update the status of the request based on any
1.7 M Comply Standard
associated work orders.

12.0 w, ~k Ord
Actual work scheduled or performed to an asset.
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Party
The system shall provide the ability to route, review, approve and
2.1 M Comply Standard
assign work orders based on type of work and location. -
The system shall provide different work order views and permissions
2.2 M Comply Standard
based on security group.
The work order shall include (but not be limited to) the following
2.3 M Comply Standard
information and functionality:
Requestor Comply Standard
Asset Type Comply Standard
Location Comply Standard
On Road/Reference Road, Offset, Offset Direction,
Comply Standard
Travel Direction, Geographic Location or Reference
Asset Inventory Number Comply Standard
Associated Service Request(s) Comply Standard
Date and Time Comply Standard
Accounting String/GL String Comply Standard
Job Number (intemal to MCDOT Finance) Comply Standard
Description Comply Standard
Work Order Priority Comply Standard
Associated Preventative Maintenance Job Plan Comply Standard
Work Order Type (corrective, preventative, Comply Standard
emergency, health or safety, capital project)
2.4 The system shall provide the ability to: M Comply Standard
Assign Crew(s)/Work Group/ Region Comply Standard
Assign Equipment Comply Standard
Assign Vendors Comply Standard
Request to Purchase/Reserve Materials Comply Standard
Display related purchase order( s) Comply Standard
Display Work Order Status and Status History Comply Standard
Actual Labor performed (multiple occurrences of one
or more crew members, date and time and hours worked, Comply Standard
traveled) or vendor work performed I
2.5 The system shall allow the work order to show multiple work tasks M Comply Standard I
for the same work order. I

-
12 !
Actual work scheduled or performed to an asset.
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception 3rd Party exceptions, customizations or 3rd party software
The system shall provide the ability to view a list of labor resources
2.6 and availability based on existing assigmnents and labor work M Comply Standard
schedules.
System provides the ability to associate multiple assets to the same
2.7 M Comply Standard
work order
System shall notifY or display work orders occurring within the same
2.8 geographical region based on work order status or date range to M Comply Standard
assist in determining any potential conflicts.
2.9 System shall update the status of any associated service requests. M Comply Standard
System shall provide the ability to attach/upload one or more
2.10 M Comply Standard
!pictures or documents associated to the work order.
2.11 The System shall track usage of Water by Gallons as needed for all M Comply Standard
Work Orders.
The system shall allow different updates to Work Orders based on
2.12 M Comply Standard
current status up to and before a Work Order is Closed.
2.13 The system shall allow Crew Leads to update Work Orders based on M Comply Standard
the status of work conducted in the field.
The system shall allow Work Group Crew Leads to update Work
2.14 M Comply Standard
Orders in the field based on changes of work crew or equipment.
2.15 The system shall allow the ability to track travel time to work order M Comply Standard
locations.
2.16 The system shall allow supervisors to review and finalize any M Comply Standard
completed but not closed work orders and finalize/close.
The System shall track the location, number and type of barricades
2.17 placed on the street that require removal following a high water M Comply Standard
event or other street closures.
The system shall provide the ability to designate a work order as a
2.18 M Comply Standard
FEMA related event.
The System shall track the number of Loads of Debris delivered to
2.19 M Comply Standard
dump sites from a specific work location/work order. I

3 I' rev
Preventative Maintenance (PM) Plans that can be applied to one or more assets and asset types
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom!
Exception exceptions, customizations or 3rd party software
3rd Party
System shall allow the ability to add, edit, delete or inactivate PM
3.1 M Comply Standard
plans and iob plans.
3.2 System will provide the ability to create job plans for one or more fc .. M Comply Standard
assets and asset types. ~
3.3 System shall provide the ability to associate one or more work tasks M Comply Standard
associated to each iob plan.
3.4 System provides the ability to designate any required materials or M Comply Standard
equipment to the iob plan.
3.5 System provides the ability to designate the frequency and frequency M Comply Standard I
type of the PM plan. I
System provides the ability to automatically generate work orders for I
3.6 any assets that are associated to the PM Plan when due based on M Comply Standard
asset's assigned lifecycle (time, condition monitoring).
System shall provide the ability to manually create preventative
3.7 M Comply Standard
maintenance work orders for an asset based on a given job plan.
System shall provide the ability to collect pavement management
3.8 condition rating information and produce a lifecycle maintenance M Comply Standard
plan.
4J) \Vorl;;;floyr and Routing
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom!
Exception exceptions, customizations or 3rd party software
3rd Party
System shall provide the ability to create work flows that can be
applied to, but not limited to, service requests, work orders, material
4.1 M Comply Standard
requests and purchases based on priority, geographical location and
type of asset.
System shall provide the ability to send notifications or apply
4.2 escalations where necessary in the workflow based on record M Comply Standard
condition or state.
4.3 The system shall support mles-based workflow routing. M Comply Standard

-
!5,0 Asset~
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Party
5.1 System shall provide a unique identifier that can either be auto- M Comply Standard
I generated or user-defined.
5.2 System shall provide the ability to view asset maintenance history. M Comply Standard
5.3 System shall provide the ability to add, modify, retire assets. M Comply Standard
System shall provide the ability to search for assets using either asset
5.4 type, attributes (i.e. material, MUTCD Code, ownership, assigned M Comply Standard
maintenance yard, etc. ) or location (geographic location, On Road,
Reference Road).
System shall allow the ability to track warranty periods for roads and
5.5 M Comply Standard
associated assets.
System shall provide the ability to change asset status and provide an
5.6 ongoing history of date modified, user that modified the asset/record M Comply Standard
and any associated notes.
5.7 System shall have the ability to show asset hierarchy or subsystems M Comply Standard
i.e. traffic signals and associated components).
System shall allow assets to have defined priorities and allow those
5.8 priorities to be used when generating service requests and work M Comply Standard
orders.
System shall allow the ability to move an asset or group of assets
association from one parent to another and maintain the assets work
5.9 M Comply Standard
and cost history from the previous parent/child relationship (i.e.
move traffic signal subcomponents from one signal to another).
System shall allow the creation of an unlimited number of user-
definable attributes for an asset or class of assets (i.e. roadway
5.10 M Comply Standard
surface, pavement markings, width, ownership/right of way,
shoulder, base, sub-base, classification, maintenance district).
System shall have the ability to replace existing assets with new
5.11 M Comply Standard
assets (i.e. signs, guardrails, headwalls, traffic signals etc.).
5.12 System shall be able to develop asset hierarchies for each asset M Comply Standard
group, including location.

16.0 ln:;pr;:tiz:m :uul Condition :'ilnnitoring
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Party
System shall allow condition updates of assets based on asset type,
6.1 M Comply
type of work completed on work orders (i.e. 'New' or replaced sign).
6.2 System shall have the ability to store inspection records and images M Comply
for multiple asset inspections.
System shall provide the ability to define and set up inspection
6.3 M Comply
templates and associate them with an Asset and\or Asset Type.
System shall provide the ability to assign multiple inspection
6.4 M Comply
templates to asset classes.
System shall provide the ability to trigger prevel}tative maintenance
6.5 M Comply
work orders for inspection and include inspection template.
MCDOT has an existing inventory system and would be open to replace or integrate the existing system. The current inventory
system manages inventory for MCDOT Operations as well as other MCDOT Divisions and other County Departments.
Comply/ • Standard/ I Please . provide a brief . explanation . for any
# Requirement Priority ExceptiOn . I C usto Part-· ml exceptiOns, custonuzatwns or 3 r d party so f tware
3rd
ystem shall be able to track inventory by inventory consumption
7.1 M Comply Standard
tvoe ( consumables. non-consumables ).
System shall provide the ability to categorize inventory by material
type (paint, sign posts, sheet posts, reflective material, Chemical I M I Comply I Standard
inventory such as pesticides and herbicides, etc.).
I
The system shall provide the ability to track Barricades in stock. M Comply Standard
The system shall inventory and track Materials used for all Work I M I Comply I Standard
Orders. ...
he System shall allow Material Inventory to be updated based on I M I Comply I Standard
hanges in planned work across different Work Groups.

17 ?h
MCDOT has an existing inventory system and would be open to replace or integrate the existing system. The current inventory
system manages inventory for MCDOT Operations as well as other MCDOT Divisions and other County Departments.
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom!
Exception exceptions, customizations or 3rd party software
3rd Party
The System shall inventory and track Materials based on continuous
7.6 status of Material purchases, delivery, usage, surplus, salvage and M Comply Standard
unit cost.
The System shall allow designated users to add Material into
7.7 M Comply Standard
Inventory upon receipt of Material Invoice.
7.8 The System shall provide the ability to track items in multiple M Comply Standard
storerooms/locations.
The System shall track Disposal of Material including hazardous
7.9 M Comply Standard
waste such as; Waste Oil, Asphalt Chunk and Concrete.
The System shall track permanent and temporary stock pile
7.10 inventory of materials on hand by material type and storeroom M Comply Standard
location.
System shall support transfer of inventory from one storeroom to
7.11 another (either the main warehouse or one of the existing storerooms M Comply Standard
to another storeroom).
System shall identify items that have dropped below minimum
7.12 M Comply Standard
quantities and issue reorder reports.
7.13 System shall provide the ability to issue and return multiple items, to M Comply Standard
and from work orders and storerooms.
System shall provide the ability to track storeroom notes on
7.14 Comply Standard
transactions.
System shall provide the ability to capture last cost, moving average
7.15 M Comply Standard
cost by part.
System shall provide the ability to transfer stock from one fund
7.16 M Comply Standard
inventory to another.
7.17 System shall provide the ability to display year-to-date transactions M Comply Standard
at various levels within the inventory control.
System shall provide the ability to tie inventories to different funds
7.18 M Comply Standard
and accounts.

I7JJ'W ·ch I
MCDOT has an existing inventory system and would be open to replace or integrate the existing system. The current inventory
system manages inventory for MCDOT Operations as well as other MCDOT Divisions and other County Departments.
Standard/
# Requirement Priority Comply/ Custom/ Please provide a brief explanation for any
Exception exceptions, customizations or 3rd party software
3rd Party
7.19 System shall provide the ability to receive product/materials directly M Comply Standard
to a work order.
System shall provide detailed information for each transaction (i.e.
7.20 user, work order, task, asset, invoice number, purchase order, date, M Comply Standard
etc.).
System shall provide the ability to adjust and track inventory
7.21 M Comply Standard
balances cvcle counts and stock counts.
7.22 System shall provide the ability to store and update vendor and M Comply Standard
loricing information.
System shall provide the ability to create user definable part
7.23 M Comply Standard
numbers.
System shall provide the ability to identify minimum and maximum
7.24 M Comply Standard
lauantities of a specific item bv storeroom location.
System shall allow the use of stock types (e.g. stocked, non-stocked,
7.25 M Comply Standard
special order).
System shall allow the ability to identify economic breaks for order
7.26 M Comply Standard
lauantities.
System shall provide the ability to identify items as spare parts for
7.27 M Comply Standard
assets.
7.28 System shall provide the ability to associate manufacturer/vendor M Comply Standard
information for each uart.
System shall provide the ability to receive non-inventory materials
7.29 M Comply Standard
and outside services to work orders, tasks, assets, and accounts.
7.30 System shall provide the ability to receive inventory items into M Comply Standard
multiple inventorv storerooms.
7.31 System shall allow receipts to be partial or full receipts. M Comply Standard

18.0 Rcsou
Labor and Vendors
Standard/
# Requirement Priority Comply/ Custom! Please provide a brief explanation for any
Exception exceptions, customizations or 3rd party software
3rd Party
System shall provide the ability to enter employees and vendors and
8.1 assign appropriate hourly rates, craft, maintenance yard or work M Comply Standard
groups (i.e. Northeast Maintenance Yard, Sign Crew, Patch Crew,
etc.).
System shall have the ability to apply calendars with different I
8.2 working hours/hours of availability to each employee or groups of M Comply Standard
employees.
8.3 System shall allow the ability to add holidays to a master calendar. M Comply Standard
8.4 System shall provide the ability to enter vendors used for contracted M Comply Standard
maintenance work and hourly rates.
System shall provide the ability to change the status of employees
8.5 M Comply Standard
and vendors (active inactive).
System shall prevent employees and vendors from being made
8.6 inactive when open work orders are assigned to the resource that is M Comply Standard
being deactivated. -----------------···--·····---·····--·-···--·····-·--
19.0 Equipment I
Standard/
I # Requirement Priority Comply/ Custom! Please provide a brief explanation for any
l Exception 3rd Party exceptions, customizations or 3rd party software
The system shall provide the ability to track equipment, current
19.1 status and allow active equipment to be assigned for use on work M Comply Standard
i orders.
19.2 The system shall provide the ability to track equipment type. M Comply Standard
I
9.3 The system shall provide the ability to track hourly equipment rates. M Comply Standard
9. The system shall prevent inactive equipment from being used as a
M Comply Standard
resource on any work orders. -----------·-··--····--····---·····---·······--······--

' I
l_!)J)_ lntcgndi(Hl ''l'it!l Outsi_dc Data Sources
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom!
Exception exceptions, customizations or 3rd party software
3rd Party
System shall integrate with HR data to determine employee status,
10.1 M Comply Standard
hourly rates.
10.2 System shall have the ability to import data from and export data to M Comply Standard
in-house or enterprise SQL based applications.
lUlGm !I
Search and Reporting
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Exception Custom! exceptions, customizations or 3rd party software
3rd Party
System shall provide the ability to integrate SQL Server Reporting
11.1 Services or provide the ability to add custom reports or modify out M Comply Standard
of the box reports.
11.2 System shall provide the user the ability to run ad hoc reporting. M Comply Standard
11.3 System shall allow the user to export reports to multiple formats M Comply Standard
includingMicrosoft Word Excel PDF .txt html. etc.
11.4 System shall provide for robust search, query and reporting M Comply Standard
functionality that is intuitive and easy to use.
11.5 System shall provide the ability to easily disseminate information M Comply Standard
through standard reports and dashboard views.
System shall provide a variety of standard reports including
11.6 executive summary and detail which allow analysis on historical M Comply Standard
------- infonnatig!!_[QJ: executive decisign making.

12.0 lVIobile Solutions for Staff
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Party
Any hardware device (3rd party), software is
12.1 Devices shall be GPS enabled. M Comply 3rdParty
standard VUEW orks
Devices shall include Cameras to allow photos and video to be taken Any hardware device (3rd party), software is
12.2 M Comply 3rd Party
and attached to work orders and assets. standard VUEW orks
Devices shall have the ability to read bar codes and populate Any hardware device (3rd party), software is
12.3 appropriate fields and related information regarding the specific M Comply 3rd Party
standard VUEW orks
asset.
Devices shall allow the user to select one or more assets based on Any hardware device (3rd party), software is
12.4 M Comply 3rdParty
GPS location or On Road/Reference Road location. standard VUEW orks
Devices shall allow the user to verifY assets based on GPS or Any hardware device (3rd party), software is
12.5 M Comply 3rd Party
address/intersection. standard VUEW orks .
Any hardware device (3rd party), software is
12.6 Devices shall allow the user to request to add a new asset. M Comply 3rd Party •
standard VUEW orks
Devices shall allow user to request to remove/retire an existing asset Any hardware device (3rd party), software is
12.7 M Comply 3rd Party
standard VUEW orks
The device shall provide a defined interface of Mobile applications Any hardware device (3rd party), software is
12.8 for data collection, use of data in the field, and data updates in the M Comply 3rd Party
standard VUEW orks
field.
The device shall provide the appropriate applications available to the Any hardware device (3rd party), software is
12.9 M Comply 3rd Party
logged in user based on user/security group permissions. standard VUEW orks
Device shall allow users to create new and edit existing work orders
12.10 Any hardware device (3rd party), software is
and add time, date, start, stop, labor, materials, equipment used and M Comply 3rd Party
standard VUEW orks
any other data that pertains to a specific work order.
12.11 Device shall allow users to obtain inventory levels from authorized Any hardware device (3rd party), software is
M Comply 3rd Party
storerooms. standard VUEW orks
12.12 Device shall allow users to request inventory from authorized Any hardware device (3rd party), software is
M Comply 3rd Party
storerooms. standard VUEW orks
12.13 Device shall allow users to synchronize data either real time or when Any hardware device (3rd party), software is
M Comply 3rd Party
within range of maintenance yards or county wireless networks. standard VUEW orks
12.14 Devices shall support access through the use of3G/4G Wireless Any hardware device (3rd party), software is
M Comply 3rd Party
service and the use of a VPN. standard VUEW orks
•

-
It
Vendor will provide facilitation on discussions and considerations on where the GIS data will reside that will best meet the needs of the entire
organization and provide one source of information.
Standard/
# Requirement Priority Comply/ Custom! Please provide a brief explanation for any
Exception exceptions, customizations or 3rd party software
3rd Party
The system shall integrate with ESRI GIS (ArcSDE) to display both
13.1 linear and point data types from within the application and must be M Comply Standard
non-proprietary.
13.2 The system shall support a linear-referenced road network. M Comply Standard
The system shall have data fields to capture Start and End points for
13.3 M Comply Standard
GPS Linear Features and Feature Length in feet.
The system shall allow bi-directional updates of assets and attributes
13.4 M Comply Standard
between the application and a central geodatabase.
The system shall have the ability to prepare reports and view
13.5 attribute summaries on a map. Some examples include but are not M Comply Standard
limited to:
13.5.1 The system shall use spatial search functions to
M Comply Standard
identify records based onproxirnity, buffer overlay
13.5.2 System shall provide the ability to use GIS to review
M Comply Standard
condition and asset information
13.5.3 System shall provide the ability to use GIS to review
open or pending work orders or service requests from all M Comply Standard
work groups within a specified area
System shall allow assets and work orders to be plotted on
13.6 M Comply Standard
interactive maps.
13.7 System shall expose GIS attributes for display, use and editing. M Comply Standard
System shall provide appropriate security settings for modification
13.8 M Comply Standard
of GIS attributes and assets.
System shall provide multiple layers of assets and location to relate
13.9 M Comply Standard
different types of assets by location.
System shall provide the ability to add and remove additional
13.10
available map layers as needed (i.e. jurisdiction, M Comply Standard
section/township/range annexation).
13.11 System shall allow the ability to set a default map view extent based
M Comply Standard
on security group.

Technical Requirements
114.0 System Architecture
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Party
14.1 Vendor must provide the architecture landscape of the application, M Comply Standard Yes, Refer to System Requirements in Proposal
network etc.
Does the recommended system architecture requirements allow for Yes, system is web-based and RDBMS-compliant
14.2 M Comply Standard
scalability of the system for a growing end user base? Describe. and can scale as your needs grow.
14.3 Does your proposed solution run on dedicated servers? p Comply Standard Yes, On-premise or Cloud-based hosting are
available options.
Option for the application to be hosted internally running on County Both options are available based on the County's
14.4 standard servers, operating systems, and database platforms or M Comply Standard preference. Detailed in System Requirements
hosted externally on vendor provided hardware. Please describe. section of proposal.
Does your proposed solution run in a Windows 2008 R2 operating
14.5 systems that are supported for specific hardware components? What M Comply Standard Yes, Refer to System Requirements in Proposal
is your preferred operating environment?
Vendor must provide the minimum and recommended server
14.6 specifications- type, memory size, number of processors, 'Public M Comply Standard Yes, Refer to System Requirements in Proposal
Network" connectivity, etc. Please provide specifications.
Vendor must provide the minimum and recommended workstations
14.7 (desktops, laptops, netbook, tablets, handheld, mobile devices, etc) M Comply Standard Yes, Refer to System Requirements in Proposal
specifications. Please provide.
Does your proposed solution support several network topologies
14.8 (Ethernet, QMOE, WAN, VDI, WiFi, FDDI, ATM, etc.) and M Comply Standard Yes, Refer to System Requirements in Proposal
protocol (IP, etc) as needed? Please describe.
Does your proposed solution support local vs remote networking
14.9 environment to support multiple devices in multiple locations? M Comply Standard Yes, Refer to System Requirements in Proposal
[Note: QMOE and Ethenet as well as WiFi and WAN are High
priority for us l. Please describe.
Proposed solution shall not require any special or proprietary
14.10 hardware (printer, desktops, scanners, etc.) requirements? Please p Comply Standard None required
identify.
Does your proposed solution support a multi-user web based
environment? Describe the web technologies the vendor uses. The
14.11 County's preference is XML (Extensible Markup Language) based, M Comply Standard Yes,XML
SOA (Service Oriented Architecture), WOA (Web Oriented
Architecture) and Web 2.0.

!J4.0Systcm Architecture
~ Comply/ Standard/ Please provide a brief explanation for any
# Requirement Priority Custom!
Exception exceptions, customizations or 3rd party software
3rd Party
Does your proposed solution safely scale-up and extend functionality
of the system to accommodate increasing numbers of authenticated
14.12 Yes, VUEWorks is proposing a "site-license"
users (user accounts), growth in the amount of data, and enablement M Comply Standard
offering unlimited users access to the software.
of additional future functionality? Please explain. Additionally,
explain the impact on licensing costs.
VUEWorks maintains logs of usage and
Does your proposed solution initiate or perform capacity planning performance metrics of server response time. We
14.13 and sizing guidelines as the business environment changes? Please M Comply Standard are tightly coupled with ArcGIS Server, so as long
provide process description and methodology. as the GIS server is scaling with business
requirements, VUEW orks will scale in the same
wav.
14.14 Can your proposed solution be used on mobile devices (i.e. App-based iOS and Android solutions are available
Blackberry, !Phones, IPads, Android, Windows Tablet, etc.)? Please M Comply Standard
as well as Windows Tablet-based solutions.
describe.
14.15 Does your proposed solution align with the Maricopa County IT M Comply Standard Yes, Refer to System Requiremens in Proposal
standards and policies:
Supported Server Hardware Comply Standard Yes, Refer to System Requiremens in Proposal
HP and Dell are the supported hardware vendors Comply Standard Yes, Refer to System Requiremens in Proposal
VMware vSphere 4.0 for server virtualization Comply Standard Yes, Refer to System Requiremens in Proposal
Citrix for server and desktop virtualization
(standard under current evaluation but likely to be Comply Standard Yes, Refer to System Requiremens in Proposal
approved)
Email: Exchange 2007 Comply Standard Yes, Refer to System Requiremens in Proposal
Instant Messaging I Collaboration: Office Comply Standard Yes, Refer to System Requiremens in Proposal
Communication Server 2007 R2 Comply Standard Yes, Refer to System Requiremens in Proposal
Database Engine: SQL Server 2008 or later Comply Standard Yes, Refer to System Requiremens in Proposal
FTP: adhoc FTP Comply Standard Yes, Refer to System Requiremens in Proposal
Web Server: IIS-7 Comply Standard Yes, Refer to System Requiremens in Proposal
Web Browser: IE8 or above Comply Standard Yes, Refer to System Requiremens in Proposal
Active Directory: Support of a multi-domain forest Comply Standard Yes, Refer to System Requiremens in Proposal
AntiVirus: Trend OfficeScan!ServerProtect Comply Standard Yes, Refer to System Requiremens in Proposal
Backup Agent: County only supports CommVault Simpana Comply Standard Yes, Refer to System Requiremens in Proposal
as its backup vendor
ArcGIS 10.1 or later Comply Standard Yes, Refer to System Requiremens in Proposal
--······---······--·····-------------------------

!15.0 SofhYr~rc
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Party
Vendor must describe the language and development environment of
C# and .NET are primarily used throughout the
15.1 the application including mobile components (Microsoft .NET, M Comply Standard
application.
J2EE etc.).
Vendor must indicate where the application's business rules and/or
application logic reside (application layer, rules engine, database, Application layer/Users with appopriate
etc.)? Please describe. [Note: Important to know to determine the permissions can define rules, DBA not required.
15.2 M Comply Standard
skills of business analysts that will be creating, updating and W orkflows are created using Wizards and GUis
configuring business rules ... is it a high level interface or do they within the application.
require DB skills?l.
Vendor must list all third party tools, drivers, and software SQL Server and ArcGIS Server Advanced
(including their versions) that must be licensed to use your
15.3 M Comply Standard Enterprise is preferred, but it can run on any
application. Can this software be licensed separately (i.e. directly ArcGIS Server software.
from the software vendor)? Please specifv.
l6.0DBMS
Standard/
Comply/ Please provide a brief explanaltion for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Party
Application shall support the use of Microsoft SQL Server 2008 or
16.1 M Comply Standard
higher.
Does your proposed solution provide specific guidelines to tune the
VUEW orks can provide optimization strategies for
16.2 application at a database level to ensure that the application will M Comply Standard
SQL server.
perform effectively and efficiently? Please describe.
Does your proposed solution allow for database security to include I
16.3 encryption capability for defined data fields within database objects M Comply Standard This would utilize native SQL server tools.
such as tables or views? Please describe.
Does your proposed solution prevent unauthorized database access? Yes, the application requires user authentication via
16.4 M Comply Standard
Please describe. Username and Password to access VUEWorks.
This is controlled by the SQL Server administration
Does your proposed solution prevent unauthorized access to schema I
16.5 M Comply Standard configuration. VUEW orks can provide
objects? Please describe.
recommendations.
Yes, VUEW orks logs specific transactions as
16.6 Does your proposed solution audit user actions and database M Comply Standard defined by the County. By limiting this auditing,
transactions through security/application logs? Please describe. the application can perform more efficiently.
- --------······---······-- ---------····--····---····----···· ---···· ----···· ·- 1_5 __ --····-·--

--
116.0 DBMS I I
Standard/ l
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom!
Exception exceptions, customizations or 3rd party software I
3rd Party
Vendor must provide documentation and schematic/visual data I
16.7 model of the data base (including data dictionary useable for M Comply Standard This will be provided as an Attachment to the i
proposal.
reporting). Please provide.
Does your proposed solution provide guidelines about the prefened
16.8 backup schedule/plan/type for the database/s? (This should include M Comply Standard Yes, Refer to System Requiremens in Proposal
transactions logs etc.). Please provide.
Vendor must provide best-practice guidelines about the preferred
16.9 amount of disk space that should be made available for nonnal M Comply Standard Yes, Refer to System Requiremens in Proposal
operations? Please provide. --------····------- ------------------ --~ - --·····--····------------
117-Q SystcrnJ>~tfutlmlnt·c
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception 3rd Party exceptions, customizations or 3rd party software
Does your proposed solution indicate how the application and
17.1 database environments are monitored to maintain our requirements p Comply Standard Yes, Refer to System Requirements in Proposal
for performance and response time? Please specify.
17.2 Does your proposed solution determine and enforce who needs or p Comply Standard Yes, Refer to System Requirements in Proposal
has access to key system performance metrics?
Does your proposed solution provide end-to-end monitoring
capabilities from the client perspective and from the server p
17.3 perspective, to help determine the distributed component causing Comply Standard Yes, Refer to System Requirements in Proposal
issues (client, network, server, database, storage, etc.)?
Vendor must provide the requirements for network throughput for
17.4 your recommended application environment to serve the number of M Comply Standard Yes, Refer to System Requirements in Proposal
clients, process the amount of data to be managed. Please specify.
Does your proposed solution determine if clients can efficiently
17.5 access the server(s) over other network topologies (Wifi, 3G, 4G, M Comply Standard Yes, Refer to System Requirements in Proposal
etc)? Explain.

- .
17.0 Systrm Pcrfonmmcc
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Party
Does your proposed solution provide load testing functionality to
detennine the effect on performance if the original number of
17.6 concurrent users doubles or even triples, as well as scalability p Comply Standard Yes, Refer to System Requirements in Proposal
guidelines to appropriately achieve desired "performance quality of
service" (SLAs Y?
Network traffic generated is minimal because the
Vendor must describe the network traffic that the software or majority of the computing is completed on the
17.7 M Comply Standard
hardware will generate. server and delivered as XML data across the
network.
Does your proposed solution maintain greater than 50-100
17.8 concurrent users in an internally multi-tiered environment or M Comply Standard Yes, Refer to System Requirements in Proposal
externally hosted environment without taking a performance hit?
-
17.9 Does your proposed solution allow for redundancy and rapid M Comply Standard Yes, Refer to System Requirements in Proposal
recovery capabilities to satisfY high up time requirements? _ -----····· ------ ' ... -
18Jl Raclmp & Recovery/Archiving
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Party
Given the Current Back Up Process and Restore Process below,
We do not institute "record locing", so all data is
18.1 vendor must determine if there will be any issues with adding the M Comply Standard
always available for backups without interruption.
application and database to the existing processes. Please explain.
- --- - __ ......._,

lt8.0 Backup & Rcl~on::ry/Archiving
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Party
18.1.1 MCDOT Current Back Up Process Comply Standard
MCDOT Network Solutions uses CommVault Simpana as
the primary backup software application. Currently all
systems perform a differential backup starting at 4:00PM,
Monday thru Thursday, and also perform a full backup
starting at 4:00PM on Friday. The full jobs run all weekend
long. All backup tapes are kept for 12 weeks. Tapes that
Comply Standard Yes
are 13 weeks old are reused and over-written for the start of
the next 12 week cycle. On every Monday tapes for the
previous week are identified and removed from all tape
libraries. On Tuesday, the county vendor arrives with a
scheduled box delivery and takes this week's boxes. Is your
solution compatible with the existing backup process?
18.1.2 MCDOT Current Disk Jobs and Restore Process Comply Standard
Backup jobs are also run to a disk farm and are kept for 2
weeks. The disk backup jobs are the first place used as the
source to do any restore for the key server systems. This
allows for quicker response time. It also prevents the need
to recall a tape canister from the county vendor, and avoid
the canister handling charge. If the restore request is for Comply Standard Yes
information that is not in the disk backup system, the
vendor must be notified to recall the needed tape canisters.
Once the tapes arrive, the restore job is executed and
should run for short period of time .. Is your solution
compatible with the existing restore process?
18.2 Vendor must provide formal guidelines and recommendations for M Comply Standard Yes, Refer to System Requirements in Proposal
optimum backup and recovery. Please provide.
Does your proposed solution satisfy the Public Records statues in Yes, based on our limited understanding of these
18.3 Arizona (i.e., entry, access, retention, legal holds, and purging)? M Comply Standard
requirements, we comply.
Please describe.
Can your proposed solution segregate data for periods of time, or per
18.4 M Comply Standard Yes
active/inactive status?

i 19.0 Re-porting
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Party
Does your proposed solution support SQL Server Reporting Yes, VUEW orks support S SRS and contains an
19.1 Services? Does your product include other report generation tools? p Comply Standard internal reporting engine. Either type of reporting
Can these reports be incorporated into the product's menus? can be used currently.
Vendor must indicate if reporting capability costs are included in I
your software license or if they require separate licensing? Vendor
19.2 M Comply Standard Included
must describe how the product is licensed (e.g. per seat, server,
developer runtime)? Please provide.
Yes, caned reports ship with the system and are
Does your proposed solution provide canned reports with your p available for every Form type created in the system.
19.3 Comply Standard
products? Please provide a list and descriptions. These can be copied, edited and modified easily to
serve as a starting point for the County.
19.4 Does your proposed solution allow for reports to be on a scheduled p Comply Standard Yes
basis?
Does your proposed solution have a configurable and centralized
19.5 dashboard based on user roles and permissions which includes M Comply Standard Yes
functionality such as alerts, notifications, key measures, thresholds,
targets, flags and reports?
19.6 Does your proposed solution provide secure and remote access to M Comply Standard Yes
report information? -
19.7 Can your proposed solution send reports via system generated M Comply Standard Yes
emails?
Does your proposed solution create views targeted to a specific
19.8 audience, i.e. configurable dashboards to address the information M Comply Standard Yes
needs of a Call Center or a Maintenance Yard Supervisor?
120.0 O::mfi!!uratinn
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Partv
SQL Server, ArcGIS Server are the only 2
Vendor must describe skill sets and development tools required to
20.1 M Comply Standard applications that need to be supported outside of
support the application.
the application.
Does your proposed solution extend, configure the application Yes, VUEW orks has a published API that is used
20.2 through documented tools and standard mechanisms? Please M Comply Standard for integration with 3rd party systems.
des_cribe._ ---

Does your proposed solution rename, add, move, or delete fields on Yes, new fields can be added to forms and are then
20.3 I the user interface? Explain how this is accomplished and the impact M Comply Standard lcreated in the database -reserved for
it has on the database. administrators.

120.0 Confi~uratifm
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Party
Does your proposed solution allow for authorized users to add new
functionality (data elements, user interfaces and business logic) as Yes, all modules ship with administrative menus
20.4 M Comply Standard
needed within your system/application? Please explain how this is that allow configuration of the software.
accomnlished.
Does your proposed solution log the impact of any customer changes All releases are backward-compliant, meaning that
20.5 in the event of an upgrade, how are those changes retained and p Comply Standard the data schema is preserved within any upgrade -
integrated to the new release, and what costs may be incurred? meaning no cost to upgrade.
Vendor must provide support policy for configurations, a description All configurations are supported within the
application. Any 3rd-party customization may not
20.6 of the supported versus non-supported ways to configure, and what M Comply Standard
be supported if it impacts the native VUEW orks
costs may be incurred. Please provide.
application.
Vend or must provide documented best -practices about assessing Typically, VUEW orks requires an application
20.7 development staff size to support an organization of our size. Please M Comply Standard administrator, database administrator and a
describe your assessment methodology. configuration manager.
20.8 Vendor must provide the current development staffing level M Comply Standard Currently, 7 staff are assigned to the application
dedicated to tl1is product and how big it was a year ago. and last year it was 6 staff.
20.9 Can your proposed solution incorporate contextual help information p Comply Standard Yes
as a standard configuration feature on the interface design? !
Does the vendor have documentation that assesses the impact of This can be provided, but is not formally
20.10 support requirements on other customers of a similar size (internal p documented we suggest calling references for
Comply Standard
County staff? such as business analysis/project management, their opinion based on the size and scope of the
development, business and network management staff)? County.
2LO Vt>mlor Support
p . . 1 Comply/ I s;:-nda~/ Plem p<ovide a bdef explanation '"' any
# Requirement nonty E . usto . . . I
xceptwn Jrd Party exceptiOns, custonnzatlons or 3rd party software
Vendor must provide documentation and examples about the service
21.1 M Comply Standard
level agreements\policies offered.
Do you provide 24 x 365 support coverage? Indicate any associated
21.2 costs in Attachment A. Provide costs for other levels of support p Comply Custom Please refer to cost sheet
offered.
Vendor must describe problem reporting process and tools (phone, All modes of problem reporting are supported
21.3 M Comply Standard
online email). Please explain. (phone, emai~ort portal).

2 LO V!;n1_io_! SUJ11ll_lr!
Standard/
# Requirement Priority Comply/ Custom/ Please provide a brief explanation for any
Exception exceptions, customizations or 3rd party software
3rd Party
21.4 Vendor must describe issue escalation process. Please provide. M Comply Standard Provided in Attachment to Proposal
Can vendor provide technical and business documentation that
includes ER diagrams [Entity-Relationship diagrams], database
21.5 M Comply Standard This can be provided using the SQL reporting tools.
schemas, and table and colunm level descriptions including data
formats? Please provide.
Does vendor provide Tier 3 (senior level) telephone technical Yes, a dedicated 800 number is used to collect
support during prime business operating hours (7 am-6pm PT,
21.6 M Comply Standard these phone calls and senior-level support techs are
Monday through Friday) for the county through a toll-free number?
available.
Please describe.
21.7 Does vendor remotely access and assist local technicians as M Comply Standard Yes, we utilize Gotomeeting or Live Meeting,
required? Please describe. depending upon client's requirements.
21.8 Does vendor provide online support to log and view system issues p Comply Standard
along with proposed resolutions?
Does vendor enable the County to receive notifications about
21.9 M Comply Standard
upgrades as they become available?
Does the maintenance agreement allow the County to receive
21.10 upgrades and bug fixes on a regular interval to ensure the system These are included in the annual maintenance and
M Comply Standard
maintains security standards according to a negotiated SLA? Are support costs.
there any additional costs?
Does your proposed solution maintain configuration settings after
21.11
application of system/application upgrades (no need to reconfigure M Comply Standard
after upgrades)?
Vendor must provide technical documentation which describes the
21.12 administration, operation, installation steps, common issue
M Comply Standard
resolution, application interface block diagrams, database schemas,
database diction(!ries and routine maintenance items.
21.13 Vendor must describe and provide examples of the technical
documentation and assistance available for the installation and M Comply Standard
technical support of the application.

I2LO Vendor Support
Standard/
# Requirement Priority Comply/ Custom/ Please provide a brief explanation for any
Exception exceptions, customizations or 3rd party software
3rd Party
Vendor must describe all licensing models and maintenance fees
21.14 including additional licenses required for development and test
infrastructure. If there are multiple licensing models such as by M Comply Standard Yes, please refer to Proposal
server, workstation, physical location, enterprise, etc., please
describe all ontions.
Vendor must describe what a chargeable modification for the system Chargeable- Custom modification to software that
21.15 would be versus one covered under the maintenance agreement. is not available through the administrator tools.
M Comply Standard
Provide an example of a chargeable and a non-chargeable Non-chargeable- configuration using administrator
modification. tools.
21.16 Vendor must describe what version of the operating systems, and Detailed in the proposal Standard Specifications
platforms supported (as far back and as far forward in version M Comply Standard
section.
numbers with patches).
21.17 Vendor must describe how the change control process tracks vendor We utilize a CRM software called Jira that tracks
M Comply Standard
support activities. all support requests and reolution.
21.18 These are tracked in Jira and prioritized based on
Vend or must provide your process for future enhancements requests. M Comply Standard the criticality, number of requests and how it
applies to the entire user base.
21.19 Does the vendor allow the County to take advantage of other p Yes, VUEWorks allows users to exchange Forms
Comply Standard
customer modifications at no cost? Please describe. between installations at no cost.
122.0 System Updates (Cih:nt and Server)
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Party
Vendor must describe the company's philosophy for software
Detailed in the proposal Standard Specifications
22.1 updates, upgrades, hot fixes, maintenance releases and new versions M Comply Standard
section.
for your product. Provide a schedule for the past three years.
Vendor must describe how application updates are applied. Are they
22.2 incremental patches or whole replacement software images. Describe M Comply Standard Detailed in the proposal Standard Specifications
if during the update process, you replace individual components or section.
the entire apQlication?
Vendor must describe how long old releases are supported, after a
Detailed in the proposal Standard Specifications
22.3 new release. Please indicate typical support schedules of older M Comply Standard
section.
releases. --------------------------------··-··--····-------------------····---·····--------- - - -- ,_ L..

22.0 System Updates (Client and Server)
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Party
Vend or must describe what constitutes an upgrade, modification,
configuration, new release or .x version of the system and if it can be
Detailed in the proposal Standard Specifications
22.4 deployed through the use of automated tools to push the new M Comply Standard
section.
versions to client PCs and other end devices. Describe the frequency
of a new release or version upgrade of the application.
Vendor must describe how you test and certifY the application,
Detailed in the proposal Standard Specifications
22.5 including database, operating security patches and other M Comply Standard
section.
components.
Describe any standards that your proposed solutions meets, i.e.
22.6 M Comply Standard No Certifications
-- I~0900X certified, COBIT 3_.1, ISO 38500. ---·····---····---···- --------
123.0 Se\".urity
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Party
For each item below, describe how users are authenticated and given
23.1 M
privileges to your application (AD, application directory, other):
23.1.1 Does your product identifY users trying to login? M Comply Standard
23 .1.2 Does your product authenticate predetermined valid
M Comply Standard
users?
23.1.3 Does your product authorize users with selected
M Comply Standard
access rights within the application?
Does your proposed solution manage authorization internally or
23.2 M Comply Standard Both are supported
interface with LDAP (AD)?
Does your proposed solution provide user access with a web-
23.3 browser (for thin client users) to the application/data while inside p Comply Standard
and outside of the Countv's network?
Does your proposed solution allow for system access over VPN
23.4 M Comply Standard
running on the public internet infrastructure?

-
I23JJ Security
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Party
The proposed solution shall not require any direct coding to
23.5 execute/implement changes for security setup and/or administration? M Comply Standard
If it does vendor must explain.
This is inherited from the ArcGIS Server
23.6 Does your proposed solution support field-level security? Explain p Comply Standard configuration for GIS data and is handled through
how this is implemented.
SOL server for database securitv.
Does your proposed solution provide functionality to allow
configuration of end user roles, (i.e., Maintenance Yard Supervisor,
Crew Leader, Crew Member, administrative) to allow enforcement
of role base security? (For example does your proposed solution
23.7 M Comply Standard
control access to information based on individual and/or group
permissions granting authorization to: read, write, modifY, print and
delete). Please explain how this can be configured through your
application. Describe how you:
User roles and groups are administrated within the
23.7.1 create flexible roles and groupings, M Comply Standard
application.
23.7.2 define secure access to information based on roles and
M Comply Standard User Management within VUEW orks
users
23.7.3 manage access control (including the access/
management/configuration of assets and attributes and workflow M Comply Standard User Management within VUEW orks
processes)
Does your proposed solution require or allow security controls and
23.8 access rights to stored documents apart from the system level p Comply Standard
security? If yes, can this be turned on or off as needed?
Does your proposed solution enable secure conditional access to
23.9 M Comply Standard
reports?
23.10 Does your proposed solution employ session timeouts after periods
of inactivity? If yes, describe how the application has password M Comply Standard Yes, these are set in the application administrator.
controls for timeout complexity, and reuse.
23.11 Does your proposed solution allow for the placement of a user- p Comply Standard
defined banner when logging into the system?
23.12
Vendor must describe available Security Reports and Controls. M Comply Standard
23.12.1 Does your proposed solution lock account after x # p
Comply Standard Yes, these are set in the application administrator.
of attempts and alert the system administrator?
23.12.2 Does your proposed solution support Local p Comply Standard Yes, these are set in the application administrator.
Password rules iflocal passwords are elected?

23.0 SecuriJy
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom!
Exception exceptions, customizations or 3rd party software
3rd Party
23.13 Does your proposed solution provide reports or logs to monitor I
M Comply Standard
security for the following: I
23.13.1 User activity M Comply Standard
23.13 .2 Inactive users p Comply Standard I
23.13.3 Failed access attempts M Comply Standard
23.14 Vendor must describe how and who is able to create, edit and delete
M Comply Standard This is handled by the application administrator.
groups and assign permissions to those groups.
Vendor must describe how and who is able to create, edit and delete
a user, for example create a user profile and define attributes, such
This is handled by the application administrator.
23.15 as, unique identifier, first name, middle initial, last name, password,
M Comply Standard The administrator has complete control over these
title, organization, job code, e-mail, phone, etc. If create, edit and
activities.
delete a user cannot be done, describe how the application manages
user access for administrators.
Does your proposed solution provide descriptive error logging of all The user is notified that their usemame or password
23.16 errors, including error messages when login validation fails? Please M Comply Standard are incorrect. They can request their password
provide examples of error handling for a failed login attempt. from the application administrator if needed.
23.17 Does your proposed solution follow industry accepted enterprise This can be discussed with VUEWorks application
security best practices for access and disclose all "back doors" to the M Comply Standard
architects, but has not been documented.
svstem? Please describe.
23.18 Does your proposed solution allow for MCDOT IT to grant limited
and closely-controlled remote access to the system by authorized M Comply Standard I
Vendor technical support engineers?
Vendor must describe how and who is able to reset a password for
23.19
logon access to the application if Active Directory (AD) is not M Comply Standard This is handled by the application administrator.
supported.
23.20 Vendor must describe and provide documentation on the
M Comply Standard
application's security model.
Vendor must describe the security processes maintained, pertaining i
23.21
to the application entities/capabilities and to the support of the M Comply Standard I
(lpQlication. I
23.22 Does your proposed solution automatically disable accounts that These accounts can be disabled after a period of I
have gone unused for a specific period of time? If so, please p Comply Standard
time using the User Administrator.
describe.
23.23 Does your proposed solution allow for back up rotation and archive p Comply Standard Yes, handled with SQL Server tools.
- (lctivity logs? If so, please descti_bt_:. ------------···-·- -- ,_ -

23JJ Security
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority ! Custom!
Exception exceptions, customizations or 3rd party software
3rd Party
23.24 Does your proposed solution have the ability to specify maximum M Comply Standard Yes, handled with SQL Server tools.
log file size? If so,_]Jlease describe.
23.25 Vendor must describe how the proposed solution ensures that data is This can be discussed with VUEWorks application
M Comply Standard
not corrupted, infected or tampered with. architects, but has not been documented.
24.0 Ar•p1kati(m!ntcgratio_l_t
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom!
Exception exceptions, customizations or 3rd party software
3rd Party
Does your proposed solution integrate (bi-directionally) with other
24.1 M Comply Standard API is available for integration
data sources? Please eX]Jlain.
24.2 Does your proposed solution have any built-in integrations p Comply Standard Refer to data management section in RFP
provided? Please explain.
24.3 Does your proposed solution include methods or tools for custom M Comply Standard Handled using .NET webservices
integration? Please list and explain.
VUEW orks can do either during the data and
Does your proposed solution support data integration operations to
implementation review our team will preform the
24.4 be executed in real-time or in the background during non-peak M Comply Standard
service that will not impact normal MCDOT
hours?
functions
Does your proposed solution integrate with OnBase, which is used Can link via webservices VUEW orks has been
24.5 for electronic document and records management at Maricopa p Comply Standard linked to document management systems such as
County? Define your experience with integration to products like SharePoint, KnowledgeBase ...
this for document and records management.
Does your proposed solution integrate with ESRI GIS
24.6 (ArcMap/ ArcS DE/ ArcGIS 10.1 or later)? Describe your experience M Comply Standard GIS-Centric Application built on ESRI Technology
with integration to these products.
Does your proposed solution import user account information MCDOT can choose VUEWorks built-in user
24.7 M Compley Standard
through LDAP integration, Active Directory? Please describe. settings or AD
-~ -----········------·········----

-
24J) Application Integration
Comply/ Standard/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Party
Does your proposed solution allow for handling multiple message
24.8 M Comply Standard
formats for data integration i.e. XML EDI etc?
24.9 Does your proposed solution ensure data integrity when integrating M Comply Standard
with other enterprise data? Please explain.
Vendor must describe the integration capabilities with other products
24.10 like SQL server, Microsoft Windows server platform, Windows 7
desktop PCs, Microsoft Internet Explorer 9.0 and higher, Adobe M Comply Standard Refer to data management section in RFP
Acrobat, and file formats such as: .pdf documents, Flat files .txt
and .csv formats?
24.11 Does your proposed solution allow for access through links to p I
Comply Standard Refer to data management section in RFP
documents stored in an EDMS? Please explain.
24.12 Does your proposed solution support access to photos? Please I
M Comply Standard
describe. I
24.13 Does your proposed solution send notifications or alerts via
M Comply Standard
Exchange/Outlook according to business-configurable parameters?
24.14 Vendor must describe integration frequency, models and methods for
M Comply Standard
sharing data between systems for each below:
real-time Comply Standard
background processing Comply Standard
batch processing Comply Standard
24.15 Vendor must describe integration techniques and tools used
M Comply Standard I
!integration engine migration products, etc). !
24.16 Vendor must describe Barcode and other scanning technologies the
M Comply Standard
proposed solution supports.
24.17 Can your proposed solution support integration with RFID (Radio p Comply Standard
Frequency Identification) technologies?

lilll Implementation Services
Standard/
Comply/ Please provide a briief explanation for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Party
25.1 Specify the standard implementation services and processes that are M Comply Standard Refer to Implementation section in RFP
included in your proposal.
SpecifY the responsibilities, roles, experience, skills and
25.2 M Comply Standard Refer to Implementation section in RFP
!qualifications for the Vendor's team.
SpecifY the responsibilities, roles, experience, skills and
25.3 M Comply Standard Refer to Implementation section in RFP
I qualifications recommended for the County's team.
Describe the manner in which the vendor will organize and prioritize
25.4 your finn's resources to perform the services including project M Comply Standard Refer to Implementation section in RFP
management, testing, and development if appropriate.
Specify the tools and/or services you offer for workflow analysis of
25.5 M Comply Standard Refer to Implementation section in RFP
the current processes and the redesigned processes.
Specify the level of system design and build that is required from the
25.6 County (e.g.: menus, user security, order and documentation M Comply Standard Refer to Implementation section in RFP
templates, code set/dictionaries, alerts).
List and describe the recommended pre-implementation activities a
25.7 M Comply Standard Refer to Implementation section in RFP
customer should perform to support the implementation process.
25.8 Specify the organization's support staff required to go live. Please M Comply Standard Refer to Implementation section in RFP
include the following:
25 .8.1 Number and type of County staff Vendor requires Comply Standard Refer to Implementation section in RFP
25.8.2 Estimated duration and timeframe for use of County
Comply Standard Refer to Implementation section in RFP
staff time
25.8.3 Provide an example of a go live staffing schedule Comply Standard Refer to Implementation section in RFP
---······----------- - ---····------ - ---····-- ---·····--·····----····- -------

126.0 Quaiity/Assur:mcc Testin~
Standard/
Comply/ Please provide a brief explanation for any
# Requirement Priority Custom/
Exception exceptions, customizations or 3rd party software
3rd Party
Does the vendor provide and recommend a testing methodology and
26.1 Quality Assurance Plan that meets the County's business M Comply Standard Refer to Implementation section in RFP
requirements? Please describe.
Does the vendor provide structured testing and comprehensive
26.2 M Comply Standard Refer to Implementation section in RFP
analysis of test data during implementation? Please describe.
Does the vendor assist with the set up and configuration of the
County's test environment? [Note: The test environment will be an
26.3 M Comply Standard Refer to Implementation section in RFP
exact replica of the production environment with any differences
documented in detaill. Please describe.
Does the vendor manage testing at multiple levels of the deployed
26.4 application implementation, for example, unit, application, system, M Comply Standard Refer to Implementation section in RFP
integration, enterprise, etc.? Please describe.
26.5 Does the vendor manage and assist with data validation and clean M Comply Standard Refer to Implementation section in RFP
up? Please describe.
Does the vendor support "Requirements Traceability" to ensure that
26.6 each County requirement (features, functions, and fit) is met and M Comply Standard Refer to Implementation section in RFP
works as needed by the customer? Please describe.
25.8.3 Provide an example of a go live staffing schedule Comply Standard Refer to Implementation section in RFP

PROPOSED IMPLMENTATION PLAN/SCHEDULE
ID Task Name Duration Start End Predecessors
1 Project Kickoff Meeting 1 day 5/5/2014 5/5/2014
2 System Integration Plan (Gate 1) 8 days 5/6/2014 5/15/2014 1
3 System Implementation Plan 4 days 5/6/2014 5/9/2014
4 System Implementation Schedule 4 days 5/6/2014 5/9/2014
5 Data Security Plan 4 days 5/6/2014 5/9/2014
6 Master Test Plan 4 days 5/6/2014 5/9/2014
7 Project Management Plan 4 days 5/12/2014 5/15/2014 3,4,5,6
8 Change Management Procedure 4 days 5/12/2014 5/15/2014 3,4,5,6
9 Training/Education Plan 4 days 5/6/2014 5/9/2014
System Implementation & Support
10 Services{Gate 1} 11 days 5/5/2014 5/19/2014
'Show & Tell' Briefing For MCDOT
11 Management & Director 1 day 5/16/2014 5/16/2014 7
GATE 1 PAYMENT & License Fee
12 {$250,000) 1 day 5/19/2014 5/19/2014
13 Data Review 30 days 5/12/2014 6/20/2014 9
Implementation Plan -
14 Requirements Review 15 days 5/19/2014 6/6/2014
Review Existing MCDOT Process
15 Documentation 15 days_ 5/19/2()14 6/6/2014
16 Tabular 15 days 5/19/2014 6/6/2014
17 GIS 15 days 5/19/2014 6/6/2014
Evaluate Data and Plan Data
18 Migration 25 days 5/19/2014 6/20/2014
19 Data Retention and Archiving Plan 15 days 5/19/2014 6/6/2014
Coordinate & Assist with Server{s)
20 Spec & Purchase 5 days 5/12/2014 5/16/2014
21 Initial Installation & Testing 10 days 5/6/2014 5/19/2014
22 Business Documentation (Gate 2) 105 days 3/3/2014 7/25/2014
23 Group A 85 days 3/3/2014 6/27/2014
24 Signs 1 day 6/9/2014 6/9/2014
25 Pavement Markings 1 day 6/10/2014 6/10/2014 24
26 Signals 1 day 6/11/2014 6/11/2014 25
27 Traffic Management 1 day 3/3/2014 3/3/2014
28 61 Office and Work Zone 1 day 3/3/2014 3/3/2014
Draft and Review of Workflow
29 Process Documentation 5 day~ 3/4/2014 3/10/2014 28
Refine and Revision of
30 Workflows, and Best Practices 5 days 3/11/2014 3/17/2014 29
GATE 2 PAYMENT and Final
31 Workflows for GroupA {$25,000) 1 day 6/27/2014 6/27/2014
32 Group B 17 days 6/11/2014 7/3/2014
33 Field Operations 1 day 6/16/2014 6/16/2014
34 Yards 1 day 6/11/2014 6/11/2014
35 Patch Crews 1 day 6/12/2014 6/12/2014
36 Bridges 1 day 6/13/2014 6/13/2014
Draft and Review of Workflow
37 Process Documentation 5 days 6/16/2014 6/20/2014 36

Refine and Revision of
38 Workflows, and Best Practices 5 days 6/23/2014 6/27/2014 37
GATE 2b PAYMENT and Final
39 Workflows for GroupB ($25,000) 1 day 7/3/2014 7/3/2014
40 Group C 14 days 6/30/2014 7/17/2014
41 Operations Support 1 day 6/30/2014 5/30/2014
42 Adopt a Highway 1 day 7/1/2014 7/1/2014 41
43 Pavement Management 1 day 7/2/2014 7/2/2014 42
44 Maintenance Projects 1 day 7/3/2014 7/3/2014 43
Draft and Review of Workflow
45 Process Documentation 5 days 7/4/2014 7/10/2014 44
Refine and Revision of
46 Workflows, and Best Practices 5 days 7/11/2014 7/17/2014 45
GATE 2c PAYMENT and Final
47 Workflows for Group C ($2S,QOO) 1 day 7/17/2014 7/17/2014
48 Group D 15 days 7/7/2014 7/25/2014
49 Inventory/Warehouse 1 day 7/7/2014 7/7/2014
so Finance 1 day 7/8/2014 7/8/2014 49
51 Executive Management 1 day 7/9/2014 7/9/2014 so
Draft and Review of Workflow
52 Process Documentation 5 days 7/10/2014 7/16/2014 51
Refine and Revision of
53 Workflows, and Best Practices 5 ~ays 7/17/2014 7/23/2014 52
GATE 2d PAYMENT and Final
54 Workflows for Group D ($20,000) 1 day 7/24/2014 7/24/2014 53
55 Confirm Order of Deployment 1 day 7/25/2014 7/25/2014 54
56 ConfigiJration 202 days 6/23/2014 3/31/2015 13
57 System level Configuration (Gate 3) 168 days 6/23/2014 2/11/2015
58 Adopt-a-Highway (Gate 3a) 11 days 7/28/2014 8/11/2014
59 Configuration 3 days 7/28/2014 7/30/2014
60 Acceptance Testing 5 days 7/31/2014 8/6/2014 59
61 Formal Acceptance 1 day 8/7/2014 8/7/2014 60
62 Training 1 day 8/8/2014 8/8/2014 61
63 Go-Live 1 day 8/11/2014 8/11/2014 62
GATE 3a Deliverable System
64 PAYMENT($20,~00Qgo live} 1 day 8/11/2014 8/11/2014
65 Traffic Operations (Gate 3b) 35 days 7/14/2014 8/29/2014
66 Signs 14 days 8/12/2014 8/29/2014
67 Configuration 6 days 8/12/2014 8/19/2014
68 Acceptance Testing 5 days 8/20/2014 8/26/2014 67
69 Formal Acceptance 1 day 8/27/2014 8/27/2014 68
70 Training 1 day 8/28/2014 8/28/2014 69
~ ~~-~' "' --~-~
71 Go-Live 1 day 8/29/2014 8/29/2014 70
72 Work Zones 14 days 8/12/2014 8/29/2014
73 Configuration 6 days 8/12/2014 8/19/2014
74 Acceptance Testing 5 days 8/20/2014 8/26/2014 73
75 Formal Acceptance 1 day 8/27/2014 8/27/2014 74
76 Training 1 day 8/28/2014 8/28/2014 75
77 Go-Live 1 day 8/29/2014 8/29/2014 76
78 Pavement Marking 34 days 7/14/2014 8/28/2014
79 Configuration 6 days 8/12/2014 8/19/2014

80 Acceptance Testing 5 days 8/20/2014 8/26/2014 79
81 Formal Acceptance 1 day 8/27/2014 8/27/2014 80
82 Training 1 day 8/28/2014 8/28/2014 81
83 Go-Live 1 day 7/14/2014 7/14/2014
GATE 3b Deliverable System
84 PAYMENT($25,000~0 live) 1 day 8/29/2014 8/29/2014
85 Operations Support (Gate 3c) 14 days 9/1/2014 9/18/2014
86 Maintenance Projects 13 days 9/1/2014 9/17/2014
87 Configuration 5 days 9/1/2014 9/5/2014
88 Acceptance Testing 5 days 9/8/2014 9/12/2014 87
89 Formal Acceptance 1 day 9/15/2014 9/15/2014 88
90 Training 1 day 9/16/2014 9/16/2014 89
91 Go-Live 1 day 9/17/2014 9/17/2014 90
92 Asset Management 13 days 9/1/2014 9/17/2014
93 Configuration 5 days 9/1/2014 9/5/2014
94 Acceptance Testing 5 days 9/8/2014 9/12/2014 93
95 Formal Acceptance 1 day 9/15/2014 9/15/2014 94
96 Trainin~ lday 9/16/2014 9/16/2014 95
97 Go-Live 1 day 9/17/2014 9/17/2014 96
98 Fleet Services 13 days 9/1/2014 9/17/2014
99 Configuration 5 days 9/1/2014 9/5/2014
100 Acceptance Testing 5 days 9/8/2014 9/12/2014 99
101 Formal Acceptance 1 day 9/15/2014 9/15/2014 100
102 Training 1 day 9/16/2014 9/16/2014 101
103 Go-Live 1 day 9/17/2014 9/17/2014 102
GATE 3c Deliverable System
104 PAYMENT ($25,000 go live) 1 day 9/18/2014 9/18/2014
105 Field Operations (Gate 3d) 97 days 7/29/2014 12/10/2014
106 Maintenance Yards 97 days 7/29/2014 12/10/2014
107 Configuration 5 days 9/22/2014 9/26/2014
108 Acceptance Testing 5 days 7/29/2014 8/4/2014
109 Formal Acceptance 1 day 12/8/2014 12/8/2014 152
110 Tr~inin~··· 1 day. 12/9/2014 12/9/2014 109
111 NE Yard 1 day 12/9/2014 12/9/2014
112 NW Yard 1 day 12/9/2014 12/9/2014
113 SE Yard 1 day 12/9/2014 12/9/2014
114 SW Yard 1 day 12/9/2014 12/9/2014
115 Go-Live 1 day 12/10/2014 12/10/2014 110
116 Utility/Patch Crew 13 days 9/22/2014 10/8/2014
117 Configuration 5 days 9/22/2014 9/26/2014
118 Acceptance Testing 5 days 9/29/2014 10/3/2014 117
119 Formal Acceptance 1 day 10/6/2014 10/6/2014 118
120 Training 1 day 10/7/2014 10/7/2014 119
121 Go-Live 1 day 10/8/2014 10/8/2014 120
GATE 3d Deliverable System
122 PAYMENT ($25,000 go live) 1 day 10/9/2014 10/9/2014
123 6-1 Office/Dispatch (Gate 3e) 45 days 8/27/2014 10/28/2014
124 co,figuration S~..<JYS 10/13/2014 10/17/2014
125 Acceptance Testing 5 days 10/20/2014 10/24/2014 124
126 Formal Acceptance 1 day 10/27/2014 10/27/2014 125
127 Training 1 day 10/28/2014 10/28/2014 126

128 Go-Live 1 day 8/27/2014 8/27/2014
GATE 3e Deliverable System
129 PAYMENT ($25,000 go live) 1 day 10/30/2014 10/30/2014
130 Pavement Management (Gate 3f) 13 days 11/3/2014 11/19/2014
131 Configuration 5 days 11/3/2014 11/7/2014
132 Acceptance Testing 5 days 11/10/2014 11/14/2014 131
133 Formal Acceptance 1 day 11/17/2014 11/17/2014 132
134 Training 1 day 11/18/2014 11/18/2014 133
135 Go" Live 1 day 11/19/2014 11/19/2014 134
GATE 3f Deliverable System
136 PAYMENT ($25,000 go live) 1 day 11/20/2014 11/20/2014
137 Traffic Signals (Gate 3g) 13 days 11/10/2014 11/26/2014
138 Configuration 5 days 11/10/2014 11/14/2014
139 Acceptance Testi~g 5 days 11/~ZPQ14 11/21/2014 138
140 Formal Acceptance 1 day 11/24/2014 11/24/2014 139
141 Training 1 day 11/25/2014 11/25/2014 140
142 Go-Live 1 day 11/26/2014 11/26/2014 141
GATE 3g Deliverable System
143 PAYMENT ($25,000 go live) 1 day 11/27/2014 11/27/2014
144 Bridges (Gate 3h) 18 days 11/17/2014 12/10/2014
145 Configuration 5 days 11/17/2014 11/21/2014
146 Acceptance Testing 10 days 11/24/2014 12/5/2014 145
147 Formal Acceptance 1 day 12/8/2014 12/8/2014 146
148 Training 1 day 12/9/2014 12/9/2014 147
149 Go-Live 1 day 12/10/2014 12/10/2014 148
GATE 3h Deliverable System
150 PAYMENT ($25,000 go live) 1 day 12/11/2014 12/11/2014
Inventory/Warehouse/BarCode
151 Tech Review {Gate 3i) 18 days 11/24/2014 • 12/17/2014
152 Configuration 10 days 11/24/2014 12/5/2014
153 Acceptance Testing 5 days 12/8/2014 12/12/2014 152
154 Formal Acceptance 1 day 12/15/2014 12/15/2014 153
155 Training 1 day 12/16/2014 12/16/2014 154
156 Go-Live 1 day 12/17/2014 12/17/2014 155
GATE 3i Deliverable System
157 PAYMENT ($25,000 go live) 1 day 12/17/2014 12/17/2014
158 Finance/GASB (Gate 3j) 13 days 1/12/2015 1/28/2015

159 Configuration 5 days 1/12/2015 1/16/2015
160 Acceptance Testing 5 days 1/19/2015 1/23/2015 159
161 Formal Acceptance 1 day 1/26/2015 1/26/2015 160
162 Training 1 day 1/27/2015 1/27/2015 161
163 Go-Live 1 day 1/28/2015 1/28/2015 162
GATE 3j Deliverable System
164 PAYMENT ($25,000 go live) 1 day 1/29/2015 1/29/2015
165 Executive Management (Gate 3k) 7 days 6/23/2014 7/1/2014
Configuration of Executive
166 Reporting 7 days 2/2/2015 2/10/2015
Configuration of Records
167 Management and Retention 7 days 2/2/2015 2/10/2015
Gate 3k Deliverable- System
168 PAYMENT ($10,000go live) 1 da'{ 2/11/2015 2/11/2015
FINAL: Module level Configuration
(Gate 4): Recheck for any conflicts in all
169 processes across modules 42 days 2/2/2015 3/31/2015
Maintenance Management (Gate
170 4a) 20 days 2/2/2015 2/27/2015
171 Work Orders Deployment 20 days 2/2/2015 2/27/2015
Service Request
172 Deploxment 20 days 2/2/2015 2/27/2015
Resource Manager
173 Deployment 20 days 2/2/2015 2/27/2015
Request Portal
174 Deployment 20 days 2/2/2015 2/27/2015
Asset Management Modules
175 (Gate 4b) 22 days 3/2/2015 3/31/2015
176 Condition Deployment 20 days 3/2/2015 3/27/2015
177 Valuation Deployment 20 days 3/2/2015 3/27/2015
178 Risk Deployment 20 dax.s 3/2/2015 3/27/2015
Budget Forecasting
179 Deployment 20 days 3/2/2015 3/27/2015
180 Projects Deployment 20 days 3/2/2015 3/27/2015
181 Reports Deployment 20 days 3/2/2015 3/27/2015
182 Dashboards Deployment 20cl~ys 3/2/2D15 3/27/2015
183 Facilities Deployment 20 days 3/2/2015 3/27/2015
184 MobileVUE Deployment 20 days 3/2/2015 3/27/2015
GATE 4 Deliverable- Recheck for
conflicts and delivery of
reconfigurations as necessary
185 PAYMENT ($40,000) 1 day 3/31/2015 3/31/2015

186 Mobile Device Procurement 1 day 6/23/2014 6/23/2014
187 Mobile Device Configuration 1 day 7/2/2014 7/2/2014
188 Data Mig~~:ti()n (GateSL 45 days. 3/30/2015 5/2~/2015
GATE 5 Deliverable of migrated data
189 into VUEWorks PAYMENT ($20,000) 1 day 5/29/2015 5/29/2015
190 Training/Education (Gate 6) 40 days 6/1/2015 7/24/2015 188
Manuals & Documentation
191 Development 20 days 6/1/2015 6/26/2015
192 Resource toolKit Design 20 days 6/1/2015 6/26/2015
193 Train the Trainer 1 day 6/29/2015 6/29/2015 192
194 Administrator Training 1 day 6/29/2015 6/29/2015
195 Business owner Training 6/29/2015 6/2:9/2015
196 Daily Use Training 1 day 6/29/2015 6/29/2015
Productive Use User
197 Training/Process Documentation 5 days ?/}3/2015 7/17/2015
198 Durango On-Site Training 5 days 7/13/2015 7/17/2015
199 Adopt-a-Highway 5 days 7/13/2015 7/17/2015
Dashboards
200 Deployment 5 days 7/13/2015 7/17/2015
201 Operations Support 5 days 7/13/2015 7/17/2015
202 Patch/Utility Operations ~days .. 7[13/2015 7/17/2015
203 6-1 Office/Dispatch 5 days 7/13/2015 7/17/2015
204 Pavement Management 5 days 7/13/2015 7/17/2015
205 Traffic Signals 5 days 7/13/2015 7/17/2015
206 Bridges 5 days 7/13/2015 7/17/2015
207 Inventory/Warehouse 5 days 7/13/2015 7/17/2015
208 Finance/GASB 5 days 7/~3/2015 7/17/2015
Maintenance Yard Onsite
209 Training 5 days 7/20/2015 7/24/2015
210 NE Yard ~ days 7/20/2015 7/24/2015
' " ' ~~~
211 NWYard 5 days 7/20/2015 7/24/2015
212 SE Yard 5 days 7/20/2015 7/24/2015
213 SWYard 5 days 7/20/2015 7/24/2015
214 GATE 6 PAYMENT ($49,200) 1 day 7/24/2015 7/24/2015
System Maintenance
215 Document/Pr()j~ct Closure(Gate !l 20 days 8/3/2015 8/28/2015

Year 1 Maintenance & Support (Gate
216 8} 263 days 8/31/2015 8/31/2016
217 GATE 8 PAYMENT ($50,395) 1 day 8/31/2015 8/31/2015

EXHIBIT C
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 perfom1ance 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 shall 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 shall 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) shall be reimbursed. Under no circumstances shall the County reimburse
for airfares related to transportation to or from an alternate site.
3.3 The County shall 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 shall 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 shall not reimburse contractor if the contractor chooses to purchase these
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 shall 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 shall reimburse for the lowest rate, long-term uncovered (e.g. covered or enclosed parking
shall not be reimbursed) airport parking only if it is less expensive than shuttle service to and from
the airport.
4.5 The County shall 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,
fuel costs associated with non-County activities, tips that exceed the per diem allowance, health club fees,
and entertaimnent costs. Claims for unauthorized travel expenses shall 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