Request for Proposals

Fort Collins Utilities

Computerized Maintenance Management System

RFP 7275

PROPOSAL DUE DATE: 2:00 p.m. (our clock) November 23rd, 2011

REQUEST FOR PROPOSAL

RFP # 7275

The City of Fort Collins Utilities Department (FCU) is requesting proposals from qualified firms to provide an enterprise computerized maintenance management system (CMMS) for its water, wastewater, storm water, and light & power businesses. This CMMS will serve both distributed and plant-based assets. Written proposals, ten (10) copies, along with a master digital copy on CD will be received at the City of Fort Collins' Purchasing Division, 215 North Mason St., 2nd floor, Fort Collins, Colorado 80524. Proposals will be received before 2:00 p.m. (our clock), November 23rd, 2011 and referenced as Proposal No. 7275. If delivered, they are to be sent to 215 North Mason Street, 2nd Floor, Fort Collins, Colorado 80524. If mailed, the address is P.O. Box 580, Fort Collins, 80522-0580. Questions concerning the scope of the project should be directed to the Project Manager, Chris Parton, by email to cparton@fcgov.com, with a copy to the Buyer, Opal Dick, whose email address is odick@fcgov.com. A non-mandatory pre-proposal meeting will be held on Wednesday, October 26th, at 1:00 PM at Fort Collins Utilities Service Center, located at 700 Wood Street, Fort Collins, Colorado, 80521. Interested parties may attend in person or via telephone conference. A number to dial into will be provided to interested parties upon written email request to Chris Parton at cparton@fcgov.com, with a copy to Opal Dick at odick@fcgov.com, five (5) days prior to the date of the pre-proposal meeting.

Questions regarding bid submittal or process should be directed to Opal Dick, Buyer, at (970) 221-6778.

A copy of the Request for Proposal may be obtained as follows:

1. Download the Request for Proposal/Bid from the BuySpeed Webpage, www.fcgov.com/eprocurement

The City of Fort Collins is subject to public information laws, which permit access to most records and documents. Proprietary information in your response must be clearly identified and will be protected to the extent legally permissible. Proposals may not be marked ‘Proprietary’ in their entirety. Information considered proprietary is limited to material treated as confidential in the normal conduct of business, trade secrets, discount information, and individual product or service pricing. Summary price information may not be designated as proprietary as such information may be carried forward into other public documents. All provisions of any contract resulting from this request for proposal will be public information. Sales Prohibited/Conflict of Interest: No officer, employee, or member of City Council, shall have a financial interest in the sale to the City of any real or personal property, equipment, material, supplies or services where such officer or employee exercises directly or indirectly any decision-making authority concerning such sale or any supervisory authority over the services to be rendered. This rule also applies to subcontracts with the City. Soliciting or accepting any gift, gratuity favor, entertainment, kickback or any items of monetary value from any person who has or is seeking to do business with the City of Fort Collins is prohibited.

Financial Services Purchasing Division 215 N. Mason St. 2nd Floor PO Box 580 Fort Collins, CO 80522

970.221.6775 970.221.6707 fcgov.com/purchasing

Collusive or sham proposals: Any proposal deemed to be collusive or a sham proposal will be rejected and reported to authorities as such. Your authorized signature of this proposal assures that such proposal is genuine and is not a collusive or sham proposal. The City of Fort Collins reserves the right to reject any and all proposals and to waive any irregularities or informalities. Sincerely,

James B. O'Neill II, CPPO, FNIGP Director of Purchasing & Risk Management

City of Fort Collins Request for Proposal No. 7275

Computerized Maintenance Management System A. Summary Fort Collins, Colorado is a community of approximately 150,000 people located about 60 miles north of Denver. Fort Collins Utilities is a municipal utility that provides water, wastewater, storm water, and electric services to the community. The assets in FCU’s portfolio include:

550 miles of water pipelines and appurtenances; 87 MGD water production facility and associated high mountain water supply facilities; 437 miles of wastewater pipelines and appurtenances; 23 MGD and 6 MGD wastewater reclamation facilities; 188 miles of storm water pipelines; 7 electric substations; 1,840 miles of electric cable and appurtenances 120 miles of fiber optic cable

Fort Collins is home to Colorado State University with an enrollment of approximately 30,000 students. Fort Collins is also home to numerous microbreweries throughout town, as well as a vibrant downtown area. Fort Collins Utilities (FCU) is seeking proposals from vendors for an enterprise computerized maintenance management system (CMMS) for its water, wastewater, storm water, and light & power businesses. FCU currently uses a number of custom homegrown applications for various work management and materials management tasks. FCU is seeking to replace these custom applications with an enterprise application that can better leverage the existing data and information and allow managers to make informed decisions around managing FCU assets and the associated investment planning process. The CMMS should be capable of handling both distributed and plant-based assets. Example tasks, among others, that a CMMS should perform would be:

Scheduling and tracking of preventive maintenance activities; Recording and tracking of corrective maintenance activities; Facilitation of life cycle cost calculations through integration with the City’s ERP, JD

Edwards; Tracking of asset condition, risk or criticality, and other items related to asset

management; Handling of materials management or warehouse applications; Reporting on assets, work orders, work history and more; Warranty tracking; Integration with the City’s enterprise document management system to facilitate retrieval

of owner’s manuals, record drawings, wiring diagrams, etc.; Viewing of distributed assets with similar properties (age, condition, material, etc.)

through integration with the City’s enterprise ESRI GIS application.

In addition to the CMMS tool, the selected vendor will be tasked with providing services to support a successful CMMS system implementation and data migration from current in-house developed applications to the CMMS. The vendor will be expected to work collaboratively with FCU and MWH on the following:

Provide an implementation methodology and approach, Configure and test the solution jointly with FCU staff, Facilitate the pilot deployment and roll out, Complete configuration adjustments as identified during the pilot phase Convert and migrate existing data

o Supporting documentation regarding current system size and configuration of the current systems can be found in Appendix G – Data Migration Effort

B. Asset Management Program Implementation In 2009, FCU began implementation of an asset management program. The goal of the program is to provide long-term financial forecasts to maintain existing infrastructure and ensure that enterprise fund resources are going to the places and resources that most need them. To achieve this desired result, FCU staff, with the assistance of MWH Business Solutions Group, in 2009 developed a roadmap for the Asset Management program. This roadmap outlined suggested tasks for FCU staff to undertake and a timeline for these tasks to better facilitate the implementation of an asset management program. Examples of suggested work items included development of levels of service to internal and external customers, development of risk scores and financial forecasts for linear and plant-based assets, development of lifecycle management plans for all major asset groups, implementation of an enterprise geographic information system (GIS), implementation of a commercial off-the-shelf CMMS, and development and implementation of business processes around capital renewal. In 2010, FCU staff’s major focus was development of levels of service for its “wet” (water, wastewater, and stormwater) infrastructure and development of risk scores for the wet infrastructure. These risk scores were then used to generate 100-year financial forecasts for each of the “wet” enterprise funds for linear and plant-based assets. The risk scores were also used to generate inspection schedules and priorities for FCU’s wastewater collection system. This same methodology of inspection schedules and priorities will be used for the water distribution and stormwater collection systems in the near future. Another important piece of work performed in 2010 was development of an asset hierarchy and subsequent asset registers for all FCU infrastructure in advance of CMMS procurement and GIS implementation. The data framework is available for use by the CMMS vendor in implementing the system. The asset hierarchy and a sample asset register are included in Exhibit E. .

In 2011, FCU staff began the effort of defining the business’s requirements for a CMMS in anticipation of beginning procurement of this system later in the year. Also in 2011 staff began conversion of linear asset spatial data to an ESRI-compatible in advance of moving to the City of Fort Collins’s enterprise ESRI GIS platform. This enterprise GIS will be deployed within Utilities along with the CMMS along the timeline in Section E of this request for proposal. Procurement of a CMMS that meets the business requirements as outlined in Exhibits C & D is seen as a key step in implementation of the Asset Management program. A sample Level of Service document is included in Exhibit F. Levels of service like the one provided for Potable Water were developed for all of FCU’s wet infrastructure and will eventually be developed for the Light & Power business. A key outcome of a successful CMMS implementation would be easier reporting to these levels of service at the desired interval (quarterly, annually, etc.). C. Existing Systems The City of Fort Collins and Fort Collins Utilities use a number of enterprise systems to conduct business. Some level of integration is expected with several of the systems listed below: Name Purpose/Description Version/Release

SIRE Enterprise Document Management Version 5.2MS Access Various database applications 2002JD Edwards Financial Enterprise Resource Planning Tool Version 9.0Azteca CityWorks Asset Management for Streets & Traffic Desktop Version 2010.1 Service Pack 1Milsoft Electric Load Modeling Version 7.3.7.6 H2OMap Water distribution hydraulic modeling Water 9.6 update #4.ESRI GIS Geographic Information System (GIS) 10Ventyx Customer Suite Customer Information System (CIS) & Billing Version 4.1 CISMeter Data Management Automated electric and water meter reads eMeter's EnergyIP version 7.2Bentley Redline Map viewer/editor 5.6.2100 Service Pack 3 Buiild 2600Next Axiom Enterprise Service Bus Development Tool 7.6Accela Permit Tracking 7.1

D. Submittal Qualified consultants interested in the work described in the RFP should submit at a minimum the following information to the City:

1. Statement of understanding of the Utilities’ situation, needs and objectives, along with their proposed implementation of a CMMS for the four utilities within FCU.

2. Detailed response to the requirements listed in the spreadsheet in Exhibit C titled “Core and Strategic Requirements”

3. Written responses to each of the questions listed in Exhibit D on the document titled “Technical Qualifications and Qualifications to Respond.”

4. Proposed scope of services to include a list of deliverables such as project management plans, implementation plans, data migration plans for asset work history data, test scripts, risk management plans, quality management plans, training plans, disaster

recovery plans, data models, system architecture, user guides, hardware specs, interfaces and more;

5. Proposed project team resumes; 6. Proposed schedule of milestones and activities; 7. Service rate schedule (hourly rates applicable to consulting team members) 8. A pricing model for both licensing and implementation costs based on the anticipated

implementation schedule and number of users from each work group, both of which are listed below under the “CMMS Implementation Timeline,” including a not-to-exceed fee for full implementation.

9. Information on warranties and maintenance contracts. 10. Reseller Certification (if appropriate). 11. Vendor’s qualifications including reference projects and contacts. As part of the

qualifications, vendor shall submit information on successful implementations for mid-size (100,000 people or larger) utilities for linear and facilities-based implementations. If vendor cannot provide this specific implementation example, their proposal may be disqualified.

Excel files for exhibits C & D requiring written responses will be provided. Written and electronic responses for these sections are required. E. Schedule Request for Proposal Schedule: Request for proposal distributed: October 7, 2011 Pre-Proposal Meeting: October 26, 2011 Deadline for Questions to be Submitted: November 4, 2011 Responses Due to Vendors: November 10, 2011 Proposals Due: November 23, 2011 (2:00 p.m.) Notification of Highest Ranked Firms: by December 15, 2011 Interviews: Mid-January, 2012 The project manager will be out of the office and unavailable between the dates of October 13 and 20, 2011. Any emails or phone calls submitted during that time regarding the request for proposal will be answered upon his return to the office.

Projected CMMS Implementation Schedule Fort Collins Utilities anticipates the following phased implementation timeline across the areas that will utilize the CMMS.

FCU CMMS Implementation Schedule2011 2012 2013 2014

Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4Proc./Req./Contracts

WTFWW Coll.

WDS/Storm/WRF'sL&P/Metering

Licensed users within each group are listed below: Water Production - 25 Wastewater Collection - 10 Water Distribution System & Water Metering Division - 32 Storm water Collection System - 12 Water Reclamation Facilities - 30 Light & Power – 50 Water Quality and Pollution Control Laboratories - 16

F. Questions Questions concerning the scope of the project should be directed to the Project Manager, Chris Parton, by email to cparton@fcgov.com, with a copy to the Buyer, Opal Dick, whose email address is odick@fcgov.com, on or before Thursday, November 4, 2011. Responses will be provided in writing on or before the end of the business day on Thursday, November 10, 2011. A non-mandatory pre-proposal meeting will be held on Wednesday, October 26th, at 1:00 PM at Fort Collins Utilities Service Center, located at 700 Wood Street, Fort Collins, Colorado, 80521. Interested parties may attend in person or via telephone conference. A number to dial into will be provided to interested parties upon written email request to Chris Parton at cparton@fcgov.com, with a copy to Opal Dick at odick@fcgov.com, five (5) days prior to the date of the pre-proposal meeting.

G. Review and Assessment Vendors will be evaluated based on the following criteria:

WEIGHTING FACTOR

QUALIFICATION STANDARD

2.0 Scope of Proposal Does the proposal show an understanding of the project objective, methodology to be used and results that are desired from the project?

2.0 Availability &

Motivation

Can the work be completed in the necessary time? Can the target start and completion dates be met? Are other qualified personnel available to assist in meeting the project schedule if required? Is the project team available to attend meetings as required by the Scope of Work?

3.0 Cost and

Work Hours

Do the proposed cost and work hours compare favorably with the Project Manager's estimate? Are the work hours presented reasonable for the effort required in each project task or phase?

3.0 Responses to

Business Requirements

Do the responses to the core and strategic requirements in Exhibit C compare favorably with expectations with the FCU team? Is a large amount of additional configuration required, or is most of the solution provided “out of the box”?

1.0

Responses to Technical

Requirements & Qualifications Statements

Do the responses to the technical requirements and qualifications statements in Exhibit D fit favorably with the City of Fort Collins MIS standards? Do the architecture and platform fit within available skillsets that MIS has in-house?

2.0

Firm Capability

&

Assigned Team

Does the firm have the support capabilities the assigned personnel require? Has the firm done previous projects of this type and scope? Do the persons who will be working on the project have the necessary skills (PMP, etc.)? Are sufficient people of the necessary skills assigned to the project?

These criteria will be the basis for review of the written proposals and interview session. The rating scale on the written proposals shall be from 1 to 5, with 1 being a poor rating, 3 being an average rating, and 5 being an outstanding rating.

Upon completion of the review of the written proposals, the top 3 vendors will be selected for in-person interviews and demonstrations of their products. Selected proposers will be asked to present demonstrations of their products using FCU data and specific demonstration scripts.

The data and scripts will be the same for each proposer and will be provided upon notification to each of the vendors selected for interviews.

Reference Evaluation (Top Rated Firm)

The Project Manager will check references of the selected firm using the following criteria. The evaluation rankings will be labeled Satisfactory/Unsatisfactory.

QUALIFICATION STANDARD

Overall Performance Would you hire this Professional again? Did they show the skills required by this project?

Timetable

Was the original Scope of Work completed within the specified time? Were interim deadlines met in a timely manner?

Completeness Was the Professional responsive to client needs; did the Professional anticipate problems? Were problems solved quickly and effectively?

Budget Was the original Scope of Work completed within the project budget?

Job Knowledge

a) If a study, did it meet the Scope of Work?

b) If Professional administered a construction contract, was the project functional upon completion and did it operate properly? Were problems corrected quickly and effectively?

EXHIBIT “A” PROFESSIONAL SERVICES AGREEMENT

THIS AGREEMENT made and entered into the day and year set forth below, by and

between THE CITY OF FORT COLLINS, COLORADO, a Municipal Corporation, hereinafter

referred to as the "City" and , hereinafter referred to as "Professional".

WITNESSETH:

In consideration of the mutual covenants and obligations herein expressed, it is agreed

by and between the parties hereto as follows:

1. Scope of Services. The Professional agrees to provide services in accordance

with the scope of services attached hereto as Exhibit "A", consisting of ( ) pages, and

incorporated herein by this reference.

2. The Work Schedule. [Optional] The services to be performed pursuant to this

Agreement shall be performed in accordance with the Work Schedule attached hereto as

Exhibit "B", consisting of ( ) pages, and incorporated herein by this reference.

3. Contract Period. The services to be performed pursuant to this Agreement

shall be initiated within five (5) days following execution of this Agreement. Services shall be

completed no later than , 20 . Time is of the essence. Any extensions of the time

limit set forth above must be agreed upon in writing by the parties hereto.

4. Early Termination by City. Notwithstanding the time periods contained herein,

the City may terminate this Agreement at any time without cause by providing written notice of

termination to the Professional. Such notice shall be delivered at least fifteen (15) days prior to

the termination date contained in said notice unless otherwise agreed in writing by the parties.

All notices provided under this Agreement shall be effective when mailed, postage prepaid and

sent to the following addresses:

Professional:

City: City of Fort Collins Attn: PO Box 580 Fort Collins, CO 80522

With Copy to: City of Fort Collins, Purchasing PO Box 580 Fort Collins, CO 80522

In the event of any such early termination by the City, the Professional shall be paid for services

rendered prior to the date of termination, subject only to the satisfactory performance of the

Professional's obligations under this Agreement. Such payment shall be the Professional's sole

right and remedy for such termination.

5. Design, Project Indemnity and Insurance Responsibility. The Professional shall

be responsible for the professional quality, technical accuracy, timely completion and the

coordination of all services rendered by the Professional, including but not limited to designs,

plans, reports, specifications, and drawings and shall, without additional compensation,

promptly remedy and correct any errors, omissions, or other deficiencies. The Professional

shall indemnify, save and hold harmless the City, its officers and employees in accordance with

Colorado law, from all damages whatsoever claimed by third parties against the City; and for the

City's costs and reasonable attorneys fees, arising directly or indirectly out of the Professional's

negligent performance of any of the services furnished under this Agreement. The Professional

shall maintain commercial general liability insurance in the amount of $500,000 combined single

limits and errors and omissions insurance in the amount of $ .

6. Compensation. [Use this paragraph or Option 1 below.] In consideration of

the services to be performed pursuant to this Agreement, the City agrees to pay Professional a

fixed fee in the amount of ($ ) plus reimbursable direct costs. All such fees and

costs shall not exceed ($ ). Monthly partial payments based upon the Professional's

billings and itemized statements are permissible. The amounts of all such partial payments

shall be based upon the Professional's City-verified progress in completing the services to be

performed pursuant hereto and upon the City's approval of the Professional's actual

reimbursable expenses. [Optional] Insert Subcontractor Clause Final payment shall be made

following acceptance of the work by the City. Upon final payment, all designs, plans, reports,

specifications, drawings, and other services rendered by the Professional shall become the sole

property of the City.

6. Compensation. [Option 1] In consideration of the services to be performed

pursuant to this Agreement, the City agrees to pay Professional on a time and reimbursable

direct cost basis according to the following schedule:

Hourly billing rates:

Reimbursable direct costs:

with maximum compensation (for both Professional's time and reimbursable direct costs) not to

exceed ($ ). Monthly partial payments based upon the Professional's billings and

itemized statements of reimbursable direct costs are permissible. The amounts of all such

partial payments shall be based upon the Professional's City-verified progress in completing the

services to be performed pursuant hereto and upon the City's approval of the Professional's

reimbursable direct costs. Final payment shall be made following acceptance of the work by the

City. Upon final payment, all designs, plans, reports, specifications, drawings and other

services rendered by the Professional shall become the sole property of the City.

7. City Representative. The City will designate, prior to commencement of work, its

project representative who shall make, within the scope of his or her authority, all necessary and

proper decisions with reference to the project. All requests for contract interpretations, change

orders, and other clarification or instruction shall be directed to the City Representative.

8. Project Drawings. [Optional] Upon conclusion of the project and before final

payment, the Professional shall provide the City with reproducible drawings of the project

containing accurate information on the project as constructed. Drawings shall be of archival,

prepared on stable Mylar base material using a non-fading process to provide for long storage

and high quality reproduction. "CD" disc of the as-built drawings shall also be submitted to the

City in an AutoCAD version no older then the established city standard.

9. Monthly Report. Commencing thirty (30) days after the date of execution of this

Agreement and every thirty (30) days thereafter, Professional is required to provide the City

Representative with a written report of the status of the work with respect to the Scope of

Services, Work Schedule, and other material information. Failure to provide any required

monthly report may, at the option of the City, suspend the processing of any partial payment

request.

10. Independent Contractor. The services to be performed by Professional are those

of an independent contractor and not of an employee of the City of Fort Collins. The City shall

not be responsible for withholding any portion of Professional's compensation hereunder for the

payment of FICA, Workers' Compensation, other taxes or benefits or for any other purpose.

11. Personal Services. It is understood that the City enters into this Agreement

based on the special abilities of the Professional and that this Agreement shall be considered as

an agreement for personal services. Accordingly, the Professional shall neither assign any

responsibilities nor delegate any duties arising under this Agreement without the prior written

consent of the City.

12. Acceptance Not Waiver. The City's approval of drawings, designs, plans,

specifications, reports, and incidental work or materials furnished hereunder shall not in any way

relieve the Professional of responsibility for the quality or technical accuracy of the work. The

City's approval or acceptance of, or payment for, any of the services shall not be construed to

operate as a waiver of any rights or benefits provided to the City under this Agreement.

13. Default. Each and every term and condition hereof shall be deemed to be a

material element of this Agreement. In the event either party should fail or refuse to perform

according to the terms of this agreement, such party may be declared in default.

14. Remedies. In the event a party has been declared in default, such defaulting

party shall be allowed a period of ten (10) days within which to cure said default. In the event

the default remains uncorrected, the party declaring default may elect to (a) terminate the

Agreement and seek damages; (b) treat the Agreement as continuing and require specific

performance; or (c) avail himself of any other remedy at law or equity. If the non-defaulting

party commences legal or equitable actions against the defaulting party, the defaulting party

shall be liable to the non-defaulting party for the non-defaulting party's reasonable attorney fees

and costs incurred because of the default.

15. Binding Effect. This writing, together with the exhibits hereto, constitutes the

entire agreement between the parties and shall be binding upon said parties, their officers,

employees, agents and assigns and shall inure to the benefit of the respective survivors, heirs,

personal representatives, successors and assigns of said parties.

16. Law/Severability. The laws of the State of Colorado shall govern the

construction, interpretation, execution and enforcement of this Agreement. In the event any

provision of this Agreement shall be held invalid or unenforceable by any court of competent

jurisdiction, such holding shall not invalidate or render unenforceable any other provision of this

Agreement.

17. Prohibition Against Employing Illegal Aliens. Pursuant to Section 8-17.5-101,

C.R.S., et. seq., Professional represents and agrees that:

a. As of the date of this Agreement:

1. Professional does not knowingly employ or contract with an illegal alien

who will perform work under this Agreement; and

2. Professional will participate in either the e-Verify program created in

Public Law 208, 104th Congress, as amended, and expanded in Public Law 156,

108th Congress, as amended, administered by the United States Department of

Homeland Security (the “e-Verify Program”) or the Department Program (the

“Department Program”), an employment verification program established

pursuant to Section 8-17.5-102(5)(c) C.R.S. in order to confirm the employment

eligibility of all newly hired employees to perform work under this Agreement.

b. Professional shall not knowingly employ or contract with an illegal alien to

perform work under this Agreement or knowingly enter into a contract with a

subcontractor that knowingly employs or contracts with an illegal alien to perform work

under this Agreement.

c. Professional is prohibited from using the e-Verify Program or Department

Program procedures to undertake pre-employment screening of job applicants while this

Agreement is being performed.

d. If Professional obtains actual knowledge that a subcontractor performing work

under this Agreement knowingly employs or contracts with an illegal alien, Professional

shall:

1. Notify such subcontractor and the City within three days that Professional

has actual knowledge that the subcontractor is employing or contracting with an

illegal alien; and

2. Terminate the subcontract with the subcontractor if within three days of

receiving the notice required pursuant to this section the subcontractor does not

cease employing or contracting with the illegal alien; except that Professional

shall not terminate the contract with the subcontractor if during such three days

the subcontractor provides information to establish that the subcontractor has not

knowingly employed or contracted with an illegal alien.

e. Professional shall comply with any reasonable request by the Colorado

Department of Labor and Employment (the “Department”) made in the course of an

investigation that the Department undertakes or is undertaking pursuant to the authority

established in Subsection 8-17.5-102 (5), C.R.S.

f. If Professional violates any provision of this Agreement pertaining to the duties

imposed by Subsection 8-17.5-102, C.R.S. the City may terminate this Agreement. If this

Agreement is so terminated, Professional shall be liable for actual and consequential

damages to the City arising out of Professional’s violation of Subsection 8-17.5-102,

C.R.S.

g. The City will notify the Office of the Secretary of State if Professional violates this

provision of this Agreement and the City terminates the Agreement for such breach.

18. Red Flags Rules. Professional must implement reasonable policies and

procedures to detect, prevent and mitigate the risk of identity theft in compliance with the

Identity Theft Red Flags Rules found at 16 Code of Federal Regulations part 681. Further,

Professional must take appropriate steps to mitigate identity theft if it occurs with one or more of

the City’s covered accounts.

19. Special Provisions. Special provisions or conditions relating to the services to be

performed pursuant to this Agreement are set forth in Exhibit “ “ - Confidentiality, consisting of

one (1) page, attached hereto and incorporated herein by this reference.

THE CITY OF FORT COLLINS, COLORADO

By: _________________________________

James B. O'Neill II, CPPO, FNIGP Director of Purchasing & Risk Management

DATE: ______________________________

ATTEST: _________________________________ City Clerk APPROVED AS TO FORM: ________________________________ Assistant City Attorney

[Insert Professional's name] or [Insert Partnership Name] or [Insert individual's name] or Doing business as [insert name of business]

By: __________________________________

Title: _______________________________ CORPORATE PRESIDENT OR VICE PRESIDENT

Date: _______________________________

ATTEST: _________________________________ (Corporate Seal) Corporate Secretary

SOFTWARE LICENSE AGREEMENT This Software License Agreement (“Agreement”) is entered in to between THE CITY OF FORT COLLINS, COLORADO, a municipal corporation (“City”) and , hereinafter (“Company”), and shall be effective on the date signed by the City. 1. Definitions

a. Software. The term “Software” shall mean the computer program in object code and source code and the user manuals described in the specifications set forth in Exhibit “A,” Statement of Work. The term “Software” includes any corrections, bug fixes, enhancements, updates or other modifications, including custom modifications, to such computer program and user manuals. b. Certificate of Installation. The term “Certificate of Installation” shall mean a written notice, signed by Company and acknowledged by the City, certifying that the Software has been installed, that the Software substantially complies with the specifications set forth in Exhibit “A,” that the software has been fully configured and that the master records (“rules”) for the operation of the program have been established and that the training of City employees is complete.

2. License

a. Grant of License. Company grants City, pursuant to the terms and conditions of this Agreement, a perpetual, nonexclusive, nontransferable license to use the Software. b. Authorized Equipment and Site. City shall use the Software on the computers used for City business. c. Restrictions on Use. City agrees to use the Software only for City’s business, including any collaborative services with other governmental entities, provided appropriate licensing fees have been paid to the Company. d. Copies. City may make archival copies of the Software’s computer program, provided that the copies shall include Company’s copyright and any other proprietary notices. e. Modifications, Reverse Engineering. City agrees that only Company shall have the right to alter, maintain, enhance or otherwise modify the Software. City shall not disassemble, decompile or reverse engineer the Software’s computer program. f. User Manuals. Company shall provide City with a minimum of three paper copies and one CD copy of the user manuals, and the manuals shall be updated with each new release of the Software and shall be updated no less than annually. g. Personnel. Company personnel working with the City shall be acceptable to the City.

3. Delivery, Installation, Data Conversion, Testing and Acceptance.

All activities related to the implementation of the Software shall proceed in accordance with Exhibit “B”, Implementation Schedule. Each activity listed in Exhibit B shall include both a start date and completion date. In addition, the Implementation Schedule shall incorporate the following specific activities.

a. Delivery. Company shall deliver the Software to the City location(s) specified by the Information Services Director of the City within a mutually agreed time after the effective date of this Agreement. b. Installation. Company shall install the Software at the locations designated. City shall grant Company access to the location(s) and the computer system(s) for the period of time required for such installation. c. Data Conversion. Data conversion, data entry and verification of data shall be completed in accordance with the specifications of City as set forth in Exhibit “A.” d. Testing. City shall have thirty (30) days, commencing upon delivery of the Certificate of Installation, to test the Software for substantial compliance with the specifications set forth in Exhibit “A” (the “Testing Period). City shall provide notice to Company of any failure of the Software to comply with such specifications. Upon receipt of such notice, Company shall use its best efforts to remedy the failure and install a fix within five (5) days. If City provides such notice to Company, the Testing Period, at City’s option, may be extended for thirty (30) days after Company asserts to City that the problem has been fixed. e. Acceptance. Acceptance shall occur (i) upon City’s delivery of notice to Company that the Software substantially complies with the specifications set forth in Exhibit “A”, or (ii) if City does not provide notice of a failure of the Software after thirty (30) days from the close of the Testing Period, then after thirty (30) days after the close of the Testing Period, Acceptance shall be deemed to have occurred.

4. License Fee

a. In General. In consideration for the license(s) granted by Company under this Agreement as set forth in Exhibit “C”, Pricing Quotation, City shall pay Company a fee, not to exceed $ . b. Payment Terms. Each installation of the License Fee shall be due and payable in accordance with the Payment Schedule, which is incorporated into Exhibit “B”, Implementation Schedule. All amounts are due thirty (30) days from receipt of invoice by City from Company.

5. Ownership

a. Title. City and Company agree that Company owns all proprietary rights, including patent, copyright, trade secret, trademark and other proprietary rights, in and to the Software and any corrections, bug fixes, enhancements or updates to the Software.

b. Transfers. Under no circumstances shall City sell, license, publish, display, distribute, assign or otherwise transfer to a third party the Software or any copy thereof, in whole or in part, without Company’s prior written consent, except in when City is using the Software to provide collaborative services with other governmental entities and the appropriate licensing fees have been paid to the Company for this usage.

6. Confidential Information

Company agrees not to use City data except when specifically authorized by City, and to treat all City data as confidential. City agrees to maintain the confidentiality of proprietary information identified as such by Company to the extent allowed by law.

7. Warranty

Company warrants to City that for a period of one year commencing upon Acceptance, the Software will substantially comply with the specifications set forth in Exhibit “A.” During this warranty period, Company shall also provide City the support and maintenance services set forth in the Software Maintenance Agreement appended hereto as Exhibit “D.” After expiration of the warranty period, Company shall provide support and maintenance for the Software pursuant to the terms of such Maintenance Agreement.

8. Indemnification

Indemnity Company shall indemnify and hold harmless City from and against any claims, including reasonable legal fees and expenses, based upon infringement of any copyright or patent by the Software. City agrees to notify the Company of any such claim promptly in writing and to allow Company to control the proceedings. City agrees to cooperate fully with Company during such proceedings. Company shall defend and settle at its sole expense all proceedings arising out of the foregoing. In the event of such infringement, Company may replace, in whole or in part, the software with a substantially compatible and functionally equivalent computer program or modify the Software to avoid the infringement.

9. Insurance

Company agrees to maintain workers’ compensation and employer’s liability insurance at the statutory limits. Company will also maintain a commercial general liability policy in the amount of $500,000.00 per occurrence; $1,000,000.00 aggregate’ $1,000,000.00 products and completed operations aggregate

10. Source Code

The uninterrupted availability of the Software is critical to City in the operation of its business. Company agrees to provide the source code to the Information Services Director of City.

11. Term and Termination

a. Effective Date. This Agreement and the license granted hereunder shall take effect upon the date the City executes this Agreement. b. Termination. City shall have the right to terminate this Agreement upon giving thirty (30) days notice. c. Within thirty (30) days after termination of the license, City will return to

Company, at Company’s expense, the Software and all copies thereof or delete or

destroy all other copies of the Software and inform the Company that the Software has

been returned or all copies deleted or destroyed, and its use discontinued.

12. Force Majeure

Neither party shall be in default or otherwise liable for any delay in or failure of its performance under this Agreement if such delay or failure arises due to any act of God, any acts of the common enemy, the elements, earthquakes, floods, fires, epidemics, riots, failures or delay in transportation or communications; provided, however, that lack of funds shall not be deemed to be a reason beyond a party’s reasonable control. The parties will promptly inform and consult with each other as to any of the above causes, which in their judgment may or could be the cause of a delay in the performance of this Agreement.

13. Default

Each and every term and condition hereof shall be deemed to be a material element of this Agreement. In the event either party should fail or refuse to perform according to the terms of this agreement, such party may be declared in default thereof.

14. Remedies

In the event a party has been declared in default, such defaulting party shall be allowed a period of ten (10) days within which to cure said default. In the event the default remains uncorrected, the party declaring default may elect to (a) terminate the Agreement and seek damages; (b) treat the Agreement as continuing and require specific performance; or (c) avail himself of any other remedy at law or equity. If the non-defaulting party commences legal or equitable actions against the defaulting party, the defaulting party shall be liable to the non-defaulting party for the non-defaulting party's reasonable attorney fees and costs incurred because of the default.

15. Notices

All notices under this Agreement shall be effective when mailed, postage prepaid and sent to the following addresses:

COMPANY:

CITY: City of Fort Collins, Purchasing P.O. Box 580 Fort Collins, CO 80522 With a Copy To:

16. General Provisions.

a. Complete Agreement. This Agreement, its attachments, the City’s Request for Proposal and the Company’s Response to the Request for Proposal are the complete and exclusive statement of the agreement between the parties, which supersedes and merges all prior proposals, understandings and all other agreements, oral or written, between the parties relating to this Agreement. b. Order of Precedence. In the event of any conflict or inconsistency among documents related to this Agreement, said conflict or inconsistency shall be resolved by giving precedence to the later dated document. Unless otherwise agreed to by both parties, document precedence shall be as follows: (1) the Software License Agreement; (2) the Request for Proposal; (3) the Company’s response to the Request for Proposal. c. Amendment. This Agreement may not be modified, altered or amended except by written instrument duly executed by both parties, except that address for notice may be changed as provided in section 13. d. Waiver. The waiver or failure of either party to exercise in any respect any right provided for in this Agreement shall not be deemed a waiver of any further right under this Agreement. e. Severability. If any provision of this Agreement is invalid, illegal or unenforceable under any applicable statute, court decision or rule of law, it is to that extent to be deemed omitted. The remainder of the Agreement shall be valid and enforceable to the maximum extent possible.

f. Survival. All provisions of this agreement that by their nature would

reasonably be expected to continue after the termination of this Agreement will survive the termination of this Agreement. g. Governing Law. This Agreement and performance hereunder shall be governed by the laws of the State of Colorado. Venue for any cause of action arising hereunder shall be in Larimer County, Colorado. h. Read and Understood. Each party acknowledges that it has read and understands this Agreement and agrees to be bound by its terms.

THE CITY OF FORT COLLINS, COLORADO By: __________________________________ James B. O’Neill II, CPPO, FNIGP Director of Purchasing and Risk Management Date: ________________________________

ATTEST: _________________________________ City Clerk APPROVED AS TO FORM: ________________________________ Assistant City Attorney

[Insert Corporation's name] or [Insert Partnership name] or [Insert individual's name] Doing business as ____[insert name of business] By:_______________________________ __________________________________ PRINT NAME __________________________________ CORPORATE PRESIDENT OR VICE PRESIDENT

Date:_____________________________

ATTEST: (Corporate Seal) _____________________________ CORPORATE SECRETARY

EXHIBIT “A”

Statement of Work

EXHIBIT “B”

Implementation and Payment Schedule

EXHIBIT “C”

Pricing Quotation

EXHIBIT “D”

Software Maintenance Agreement

SOFTWARE MAINTENANCE AGREEMENT

This Software Maintenance Agreement (“Agreement”) is entered into between the CITY OF FORT COLLINS, COLORADO, a municipal corporation , hereinafter “City” and , hereinafter “Company”, and shall be effective on the date signed by the City.

1. Scope of Agreement.

a. General. Company agrees to provide City standard maintenance, on-site support, and training services for the computer programs and user manuals listed below (collectively “Software”) and regular upgrades including enhancements and user manuals. b. Software. This agreement covers the software described in Exhibit “A” of the Software License Agreement between the City of Irving, Texas and Company dated _________. Company shall provide updates to the software as required in order that the software reflect current federal and state laws or requirements of the federal or state government or federal or state regulatory agencies. c. User Manuals. When this agreement refers to “User Manuals,” it shall include any user manuals which are designed for the software and any user manuals listed in Exhibit “A” and all manuals provided to users for the software listed above. At least three (3) user manuals shall be provided in paper format and one (1) in CD format. The user manuals shall be updated with each new release of the software and shall be update at least annually.

2. Term

This Agreement shall be effective for one year from the effective date, and may be shall automatically renew for up to four additional one year periods unless sooner terminated as provided herein. Such renewals shall be subject to sufficient funds being appropriated annually by the Fort Collins City Council, which appropriations are in the Council’s sole discretion.

3. Standard Maintenance Services

Scope of Services. During the term of this Agreement, Company will provide City the following Standard Maintenance Services for the Software:

a. Corrections of substantial defects in the Software so that the Software will operate as described in the user manuals listed above, as modified by the City’s Specifications, set forth in Exhibit “A” of the Software License Agreement.

b. Periodic updates of the Software that may incorporate (A) corrections of any substantial defects; (B) fixes of any bugs; (C) enhancements to the Software; and (D) upgrades to user manuals as sets out above.

c. Telephone support, including dial-up support, between the hours of 7:00 a.m. to 7:00 p.m. Central Time, Monday through Friday, excluding City of Fort Collins holidays, to assist City in using the Software.

d. In the event of emergencies, or systems failures caused by Company’s software upgrades which occur outside of the designated support hours established by Section 3(c), telephone support, including dial-up support, twenty-four (24) hours per day, seven (7) days per week for the term of the Agreement.

e. Maintenance at Company’s office of a test version, including a test database, for the most recent version of City’s Software.

4. On-Site Support

Company, upon receipt of a written request from City, will provide City On-Site Support at a mutually agreed time. City agrees to pay Company’s costs associated with the provision of on-site support, including charges for (i) Company’s personnel; (ii) charges for travel, lodging and miscellaneous expenses (if personnel must travel more than 75 miles) in accordance with City guidelines for travel expenses; and (iii) applicable taxes.

5. Training

Upon receipt of a written request from City, Company will provide Training at a mutually agreed time at the offices of City, unless City agrees to receive the Training elsewhere. City agrees to pay Company all costs associated with this Training in accordance with costs reflected in Exhibit “C”, Pricing Quotation, including (i) charges for Company’s personnel, which may include a surcharge for training conducted at City’s location; (ii) charges for travel, lodging and miscellaneous (if personnel must travel more than 75 miles) in accordance with City guidelines for travel expenses; and (iii) applicable taxes.

6. Maintenance Fee

a. Warranty Period. Company will not charge City any Maintenance Fee for the Warranty Period, as defined in City’s Software License Agreement for the Software. b. Amount of Fee. City agrees to pay Company an annual Maintenance Fee, the amount set forth in Exhibit “C”, Pricing Quotation for Standard Maintenance Services provided by Company pursuant to this Agreement. The amount charged for these services shall not increase by more than five (5) percent from one year to the next, in the event of renewal.

7. Payment Terms

City agrees to pay Company by thirty (30) days after receipt by City of invoices for agreed upon fees.

8. Obligations Of City

a. City Contact. City shall notify Company of City’s designated City Contact. To the maximum extent practicable, City’s communications with Company will be through the City Contact. b. Installation. City agrees to install all corrections of substantial defects, minor bug fixes and updates, including any enhancements, for the Software in accordance with the instructions and in order of receipt from Company. c. Facility and Personnel Access. City agrees to grant Company reasonable access to City’s facilities and personnel concerned with the operation of the Software to enable Company to provide services. d. No Modification of Software. City agrees not to modify, enhance or otherwise alter the Software, unless and only to the extent such modification, enhancement or other alteration is specifically authorized in the user manuals identified in this Agreement or through the consent of Company. e. Error Documentation. Upon detection of any error in the Software, City, as requested by Company, agrees to provide Company a listing of output and any other data, including databases and backup systems, that Company reasonably may request in order to reproduce operating conditions similar to those present when the error occurred.

9. Termination

City shall have the right to terminate this Agreement at any time upon giving thirty (30) days notice to Company. Upon termination, City shall be entitled to a pro rata refund. Company shall have the right to terminate this Agreement and all services provided pursuant to this Agreement (i) upon termination of City’s Software License Agreement by either party for any reason; and (ii) if City violates any provision of this Agreement and City fails to cure such violation within fifteen (15) days after receipt of written notice from Company.

10. Indemnification Company shall indemnify and hold harmless City, its officers, agents and employees against and from any all actions, suits, claims, demands or liability of any character whatsoever arising out of, resulting from, or occurring in connection with the performance of any services hereunder.

11. Insurance

Company agrees to maintain workers’ compensation and employer’s liability insurance at the statutory limits. Company will also maintain a commercial general liability policy in the amount of $500,000.00 per occurrence; $1,000,000.00 aggregate’ $1,000,000.00 products and completed operations aggregate

12. Source Code

The uninterrupted availability of the Software is critical to City in the operation of its business. Company agrees to provide the source code to the Information Services Director of City.

13. Force Majeure

Neither party shall be in default or otherwise liable for any delay in or failure of its performance under this Agreement if such delay or failure arises due to any act of God, any acts of the common enemy, the elements, earthquakes, floods, fires, epidemics, riots, failures or delay in transportation or communications; provided, however, that lack of funds shall not be deemed to be a reason beyond a party’s reasonable control. The parties will promptly inform and consult with each other as to any of the above causes, which in their judgment may or could be the cause of a delay in the performance of this Agreement.

14. Default

Each and every term and condition hereof shall be deemed to be a material element of this Agreement. In the event either party should fail or refuse to perform according to the terms of this agreement, such party may be declared in default thereof.

15. Remedies

In the event a party has been declared in default, such defaulting party shall be allowed a period of ten (10) days within which to cure said default. In the event the default remains uncorrected, the party declaring default may elect to (a) terminate the Agreement and seek damages; (b) treat the Agreement as continuing and require specific performance; or (c) avail himself of any other remedy at law or equity. If the non-defaulting party commences legal or equitable actions against the defaulting party, the defaulting party shall be liable to the non-defaulting party for the non-defaulting party's reasonable attorney fees and costs incurred because of the default.

16. Notices

All notices under this Agreement shall be effective when mailed, postage prepaid and sent to the following addresses: COMPANY: CITY: City of Fort Collins, Purchasing P.O. Box 580 Fort Collins, CO 80522 With a Copy To:

17. General Provisions.

a. Complete Agreement. This Agreement, its attachments, the City’s Request for Proposal and the Company’s Response to the Request for Proposal are the complete and exclusive statement of the agreement between the parties, which supersedes and merges all prior proposals, understandings and all other agreements, oral or written, between the parties relating to this Agreement. b. Order of Precedence. In the event of any conflict or inconsistency among documents related to this Agreement, said conflict or inconsistency shall be resolved by giving precedence to the later dated document. Unless otherwise agreed to by both parties, document precedence shall be as follows: (1) the Software License Agreement; (2) the Request for Proposal; (3) the Company’s response to the Request for Proposal. c. Amendment. This Agreement may not be modified, altered or amended except by written instrument duly executed by both parties, except that address for notice may be changed as provided in section 13. d. Waiver. The waiver or failure of either party to exercise in any respect any right provided for in this Agreement shall not be deemed a waiver of any further right under this Agreement. e. Severability. If any provision of this Agreement is invalid, illegal or unenforceable under any applicable statute, court decision or rule of law, it is to that extent to be deemed omitted. The remainder of the Agreement shall be valid and enforceable to the maximum extent possible.

f. Survival. All provisions of this agreement that by their nature would

reasonably be expected to continue after the termination of this Agreement will survive the termination of this Agreement. g. Governing Law. This Agreement and performance hereunder shall be governed by the laws of the State of Colorado. Venue for any cause of action arising hereunder shall be in Larimer County, Colorado. h. Read and Understood. Each party acknowledges that it has read and understands this Agreement and agrees to be bound by its terms.

THE CITY OF FORT COLLINS, COLORADO By: __________________________________ James B. O’Neill II, CPPO, FNIGP Director of Purchasing and Risk Management Date: ________________________________

ATTEST: _________________________________ City Clerk APPROVED AS TO FORM: ________________________________ Assistant City Attorney

[Insert Corporation's name] or [Insert Partnership name] or [Insert individual's name] Doing business as ____[insert name of business] By:_______________________________ __________________________________ PRINT NAME __________________________________ CORPORATE PRESIDENT OR VICE PRESIDENT

Date:_____________________________

ATTEST: (Corporate Seal) _____________________________ CORPORATE SECRETARY

EXHIBIT “B” CONFIDENTIALITY

IN CONNECTION WITH SERVICES provided to the City of Fort Collins (the “City”) pursuant to this Agreement (the “Agreement”), the Professional hereby acknowledges that it has been informed that the City has established policies and procedures with regard to the handling of confidential information and other sensitive materials. In consideration of access to certain information, data and material (hereinafter individually and collectively, regardless of nature, referred to as “information”) that are the property of and/or relate to the City or its employees, customers or suppliers, which access is related to the performance of services that the Professional has agreed to perform, the Professional hereby acknowledges and agrees as follows: That information that has or will come into its possession or knowledge in connection with the performance of services for the City may be confidential and/or proprietary. The Professional agrees to treat as confidential (a) all information that is owned by the City, or that relates to the business of the City , or that is used by the City in carrying on business, and (b) all information that is proprietary to a third party (including but not limited to customers and suppliers of the City) . The Professional shall not disclose any such information to any person not having a legitimate need-to-know for purposes authorized by the City. Further, the Professional shall not use such information to obtain any economic or other benefit for itself, or any third party, except as specifically authorized by the City. The foregoing to the contrary notwithstanding, the Professional understands that it shall have no obligation under this Agreement with respect to information and material that (a) becomes generally known to the public by publication or some means other than a breach of duty of this Agreement, or (b) is required by law, regulation or court order to be disclosed, provided that the request for such disclosure is proper and the disclosure does not exceed that which is required. In the event of any disclosure under (b) above, the Professional shall furnish a copy of this Agreement to anyone to whom it is required to make such disclosure and shall promptly advise the City in writing of each such disclosure. In the event that the Professional ceases to perform services for the City, or the City so requests for any reason, the Professional shall promptly return to the City any and all information described hereinabove, including all copies, notes and/or summaries (handwritten or mechanically produced) thereof, in its possession or control or as to which it otherwise has access. The Professional understands and agrees that the City’s remedies at law for a breach of the Professional’s obligations under this Confidentiality Agreement may be inadequate and that the City shall, in the event of any such breach, be entitled to seek equitable relief (including without limitation preliminary and permanent injunctive relief and specific performance) in addition to all other remedies provided hereunder or available at law.

EXHIBIT “C” Core and Strategic Requirements

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Select one of the following responses:

OOBCON MODCUSTPRTFRNA

WM1 Manage the routing, escalation and approval of work requests and work ordersThe system must be able to electronically route work orders to the appropriate person(s) for approval. The system must also have the ability to escalate a WO based upon pre-determined parameters.

WM2Enable user classification of work orders (such as proactive and reactive- PM and CM)

The system must have the ability to differentiate between Proactive and Reactive work orders

WM3 Associate work orders with an asset, facility or asset componentIn the lab, many assets have multiple parts. The system must be able to assign work orders to a specific part as well as the asset, and asset parent (facility)

WM4Manage a work order that relates to a group of assets, location or function (e.g. valve exercising)

allow one work order to apply to many identical activities. Valve exercising or hydrant flushing are examples where you don’t want to create a WO for each hydrant that needs to be flushed. The system must allow the one WO to cover all these identical activities.

WM5Include/Manage template work orders (that have work and safety steps, inspection checklists and standard operating procedures)

To more efficiently perform the work order, include the steps, safety precautions, and inspection checklists to have all essential information listed on the WO.

WM6 Provide the ability to have parent and child work orders (associate work orders)If a person is out in the field to perform a work order and notices an issue with the same of another asset, they need to be able to create a work order and tie it to the original.

WM7Provide high visibility (alert) safety notifications - both asset/location/work order based

For a situation such as confined space, or high voltage, the work order needs to have a highly visible alert to let the field technician know what they are facing while performing the WO.

WM8Manage work permits (such as confined space and hot work) Incl.Tailboard sheets.

The system must be able to link permits to a work order to assure the proper permit is in place to allow the work to be performed.

WM9Manage material handling safety requirements (e.g. material safety data sheets (MSDS)

Associate the proper MSDS with the assets to give the technician the proper knowledge in handling whatever might arise.

WM10 Manage reactive maintenance work orders and related asset failure informationAllow the user to view reactive maintenance work orders and see which assets the reactive work orders are against. The goal is to see which assets cause the most reactive work orders and cost the most money to maintain.

WM11 Ability to associate documents & images to work orders & work order templatesThe documents don’t need to reside in the CMMS, but the work order needs to have specific documents and images associated.

WM12 Avoid duplicate work order numbers (offline)When the system is run offline (typically by the field crew) and a WO is entered, the WO numbers must remain unique.

WM13Allow for information to be added to a "closed" work order in the case where the work in not all done at once (road repair not done until spring) Add as script

WM14Dropdown lists must be dynamic - constrain the options to only those applicable - the first choice limits the second

This is an interface component where only valid dropdown choices are available to the user. The typical example of this is if you choose a state, the next dropdown list shows only the cities in that state.

Core Functionality

Work Management

Proposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software, or special hardware items noted must be included under the separate Pricing submittal, unless otherwise specified. Proposers must clearly indicate one (1) of the listed responses to each requirement and provide comment to describe approach. Also indicate whether fulfillment of the requirement is included in the Cost Proposal.

For each requirement answer: Is the System Requirement supported by the EAM System?

Fully provided Out of the BoxProvided through ConfigurationProvided through a technical modification of the software product baselineProvided through a technical modification of the software as a customization for the clientThird party software requiredProvided through a reporting toolProvided through a future releaseNot available

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Core FunctionalityProposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software, WM15 Ability to query work by area and function

In the plant we heard that often times work is divided into area or function. The system must contain the proper metadata to allow all work orders in a certain area or function to be filtered out.

WM16 Associate a Bill of Materials to the WOThe system must have the ability to show a list of all materials needed to perform the work and the cost of each part

WM17Track water quality complaints - would tie to access Fort Collins. Service request would be entered and may become a work request/work order

The system must have the ability to convert a service request into a work order through an automated workflow

WM18Mapping that tracks real time location - GPS in trucks (NOT for tracking truck location or logging)

The mapping system must show the current location of the truck on the map and as the person drives the truck, they can always see on the map where they are.

WM19 GPS for tracking vehicle locationThe ability for the vehicle location, speed, and other key components to be tracked remotely.

WM20 Send automatic alerts for assigned and overdue work - for certain types of workThe system needs to be able to send alerts when certain types of work is not done within the pre-determined time period.

WM21 Executives and managers can sign up for alerts on certain critical assets

If there is a certain customer or asset that is very key to the organization and an executive would like to be notified of any disruption in service or asset malfunction, the system must allow the executive to set up and alert where an email or txt message is sent upon the alert being triggered.

WM22 allow individuals to set notification preferencesAllow users to decide if alerts will be sent upon occurrence, once a day, once a week, once a month, etc… this is to ensure that people are not bombarded with unwanted emails thus reducing their effectiveness.

WM23 Manage work orders against the same asset - determine if they are duplicateWhen a work order is assigned against an asset, the system must be able to pull up all WOs against the asset to allow the user to determine if the WO is a duplicate.

WM24 Comment (Text) fields must be searchable The system must full text index all fields in the system and allow them to be searchable

WM25 Quickly find and view last WO for an assetThe system must allow for quick discovery and display of the last WO against an asset. The reason is to allow an operator to quickly see the last time work was performed.

WM26Allow a user to easily create and complete a work order AFTER the work is completed

If a person is out in the field to perform a work order and notices an issue with the same of another asset, they need to be able to create a work order and tie it to the original. They also must be able to enter the WO and since it's already complete, they must be able to close it without routing the WO through the approval chain.

WM27 Ability to find an asset in the CMMS system with a URL The ability to get to an asset with a URL would help in integration of disparate systems

WM28 Ability to automatically rotate PMs amongst staffIn cases where preventative maintenance work is constantly rotated to give all employees cross training, the system must have the ability to perform the work rotation automatically

WM29 Ability to assign and re-assign work ordersIf a WO has been assigned, but the assignment must be changed, the system must all this to happen

WM30Ability to read/write/edit and asset and a WO with the computer in a disconnected mode (offline usage of the system)

The FCU field crews do not have connectivity, but they require use of the CMMS in the field. The system must be able to operate in the field in an offline mode while still allowing read/write/edit capabilities.

WM31 Must store a capital project number on a WOMany work orders are tied to capital work. System must have the ability to store the capital project number on the WO

WM32When the work order is created, include the ability to capture required data for the asset

Brad's "flushing" example - collecting turbidity values every 15 minutes.

WM33 Creation of a work order from an emailWM34 Creation of a work order from another system E.G. Using web services

GIS

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Core FunctionalityProposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software, GIS1 Ability to view ESRI powered GIS maps within the CMMS

The CMMS must have an integration mechanism such that the ESRI GIS maps can be viewed from within the CMMS allowing users to interact with the maps.

GIS2 Ability to search for an asset from the map interfaceAbility to search for an asset or location from the map interface. "Fuzzy" search is important.

GIS3 Ability to zoom, pan and center the map at a specific location

GIS4 Ability to perform electric and water line tracing from the CMMS mapping interface E.G. Showing customers affected by outage, associating customers to a work order.

GIS5 Offline map viewingGIS6 Offline map editingGIS7 Offline map tracingGIS8 Ability to view asset information from the map interfaceGIS9 Ability to view work orders from the map interface

GIS10 Ability to edit spatial information from the map interfaceGIS11 Ability to edit asset information from the map interface Using Role-Based Permissions (not all users can edit)GIS12 Ability to "redline" the mapGIS13 Supports Offline Maps on Mobile DevicesGIS14 Ability to quickly turn on and off many background layersGIS15 Ability to quickly turn on and off the various Utility layers

GIS16Ability to select a standard “theme” of layers commonly used by Electric, Water, etc.

GIS17 Ability to search for an asset on the map by street intersections:GIS18 Ability to search for an asset on the map by addressGIS19 Identify Electric circuit numberGIS20 Ability to view multiple types of information related to an asset from the map e.g. CCTV, WO, Work history, asset attributesGIS21 Ability to show thematic maps based upon asset information E.G. By Asset condition, material, criticalityGIS22 Ability to show thematic maps based upon work orders E.G. By Work Type, Crew, failure modeGIS23 Measure linear distancesGIS24 Measure areas of a user entered polygon.GIS25 Ability to print a map with assets/work orders indicated

GIS26Ability to keep maps on field devices up to date taking into consideration various schedules of field workers.

PM1 Manage labor groups and technicians and their availability (Resource level tasks) Help to resource balance work loads

PM2 Manage the recording of technician labor hours Allow for hours to be recorded against work ordersPM3 Manage craft / certification requirements per work type "Annual demonstration of capabilities"

PM4 CMMS has access to accurate labor ratesWhether they are actual or labor rate "bands", there needs to labor rates in order to support asset lifecycle cost tracking.

PM5 DOT License Tracking (expiration dates) for operators Added by L&P Field

PM6Training and certification management (CPR & First Aid, trench safety, confined space, EPA, FEMA, etc.)

Added by L&P Field

PM7 Apprentice hours / skills tracking Added by L&P Field

PMM1 Automatically create proactive maintenance work orders (Requests) Automatically create a PM based upon a pre-established schedule

Personnel Management

PM Management

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Core FunctionalityProposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software,

PMM2Manage proactive asset maintenance work schedules based on usage, condition and calendar

Allow PM work orders to be created based on multiple criteria. Many times PMs are established solely on a calendar schedule, however the system must allow for PM tasks to be established based upon the asset's condition or on amount of usage (running cycles or whatever other metric is appropriate)

PMM3Ability to mass update proactive maintenance work schedules based on a selected group of assets

If there are multiple PM work orders that are accomplished as a group, allow the system to close them out and a group and allocate cost equally across each asset.

PMM4 Route creation and maintenance (order and sequence)The system shall advise of the most efficient route to travel in accomplishing the PM work orders.

PMM5 Manually create proactive maintenance work orders (Requests) Allow the user to manually create PMs

PMM6 Allocate a block of time against a group of similar assets - based on a PMThe system should be able to take the time required to perform maintenance against a block of assets and equally distribute that time across the assets.

PMM7 Ability to print out a map of the route. The computer generated route should be available to print in a readable format.

AM1Manage the configuration information related to the City’s planned, installed and de-commissioned assets (ownership, management responsibility, etc.) (Simplify)

Storm water and fiber - commercial electric service

AM2 Manage asset hierarchy and locations The assets in the system must be a part of a customizable hierarchy

AM3Manage assets and asset attributes including criticality (make sure you can add custom attributes)

The system must have the ability to capture and store key asset attributes such as criticality and then use those attributes in determining the PM work orders

AM4 Manage asset placement history within locationsFor assets that are not in a fixed place, need to track the history of where and when it was used in other locations

AM5 Monitor asset condition and usageRegularly examine asset to determine condition. System must be able to retain the condition and usage values

AM6 Manage asset failure modes When an asset fails, the reason (failure mode) must be captured

AM7 Manage work safety requirements per assetIf an asset has specific safety requirements, they must be captured and recorded against the asset.

AM9 Ability to associate documents & images to assets and asset groupsThe system should not be required to store documents and images in the system, but should be able to associate documents and images to an asset and class of asset

AM10 Warranty TrackingFor any and all assets with a warrantee, the warrantee dates much be recorded and the expiration date managed.

AM11 Manage assets not owned by utilityCertain assets (Fiber is a good example) are not owned by the utility, but are maintained by the utility. Proper management of these assets is important

AM12Need to include outside entities in the work order system to support work orders against FCU assets

There are occasions where outside firms are brought in to perform work on FCU assets. An example is roof work on the water plant.

AM13 Manage work performed by non-FCU City staffthere are occasions where city staff (non-FCU) is brought in to perform work on FCU assets. This work must be managed by the system

AM14 Track Reliability At the asset level, reliability must be tracked within the system

AM15 Track AvailabilityAt the asset level, availability (% of the time the asset is available for use) must be tracked within the system

AM16Must be able to handle replacement of a section of a pipe/asset - retain history and deal with condition scoring

If a section of pipe is replaced, the one asset has now become 2 or 3 separate assets. The details of all two/three assets must now be tracked.

AM17 Caution code - if the maintenance has a caution message, alert the user

AM18Can associate an asset with multiple physical addresses - using a connectivity tracing mechanism

AM19Critical services - flag if the asset supplies a critical service such as a hospital, medical equip. etc.

designates services that must always be online

AM20Project when assets will need to be replaced - automatically depreciate the asset and account for inflation in the predicting the future replacement cost

Dwight's example of tracking his trucks on a sheet that predicts when the truck will need to be replaced.

Asset Management

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Core FunctionalityProposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software,

AM21 Set asset condition to "assumed" or "verified" depending upon the situation

When putting a scoring system in place, some asset will have their condition assumed based upon a subset of inspections. As those asset are specifically examined, the condition will be changed from assumed to verified. The system must have this capability

AM22 Asset Work History All history on an asset must be recorded and available for query

AM23 RFID (Radio Frequency Identifier) or other tagging for assets The inventory and laboratory systems need a method for tracking inventory whether chemicals or other materials. The CMMS must be able to incorporate the use of tracking mechanisms

AM24 Maintenance Contract TrackingThe system should have the capability of linking maintenance contracts to specified assets.

AM25 Track Asset PriorityAsset priority is a calculated value taking into consideration asset condition and asset criticality. The system should calculate this value and store it for capital investment planning use.

AM26 Add a placeholder for a new asset in the systeme.g. valve was located, but is not in the system. Add a placeholder to be completed later

PUR1 Management of purchase requisitions

PUR2Pull purchase order records from JDE and import into CMMS - Pull PO#, amount, etc.

PUR3 Integrate with JDE to obtain up to date blanket purchase order balancesPUR4 Integrate with JDE to obtain vendor recordsPUR5 Integrate with JDE to obtain invoice records

PUR6Associate purchase requisitions, purchase orders and service agreements with work orders

PUR7 The routing and approval of purchase requisitions

IM1 Manage storerooms and inventory The CMMS should have an inventory module

IM2 Manage materials re-ordering triggersThe CMMS should be able to automatically create a materials re-order list based upon an inventory threshold being reached.

IM3Define material requirements within work orders and automatically debit inventory when issued or when WOs is closed

The inventory module should be linked to work orders where a work order will automatically debit the materials inventory database.

IM4Manage material item master (official list of material items and their manufacturer, model and specifications)

The inventory module should hold product specifications and not rely on manufacturer's part numbers

IM5 Manage material issues, receipts and transfers including MSDS The inventory module should use MSDS to suggest proper handling of materials

IM6 Scanning or bar coding abilityThe inventory module would need to incorporate scanning or bar coding for easy inventory tracking

IM7 Hold photo of each part type in the warehouseEach part type held in inventory must have an image of the part linked to the inventory system for ease of part identification

IM8 Hold list of associated parts

IM9Manage cable on a per reel level - can see how much is remaining on each reel - weight per unit length and the tare weight of a reel - also by length (using the sequential footage markers - both directions)

Reels of cable are stored in inventory and lengths of cable are used. It is important that the amount of material remaining on the reel be managed.

IM10Vendor list and specification - can update the specs so the part description is not vendor dependent - e.g. per Fort Collins spec 369100

The inventory module should hold product specifications and not rely on manufacturer's part numbers

IM11 Track per year costs on repairs

IM12 Track repairs on serialized assets in the warehouseSome serialized assets are "loaned" assets in that they go to the field and then return. These assets although part of the warehouse, must be tracked

Inventory Management

Purchasing Management

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Core FunctionalityProposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software, IM13

View up to date inventory levels including inventory reserved by work orders but not picked up yet

The inventory levels must be real time and on-line for viewing by users

IM14 Ability to mark materials as hazardous

IM15Automatically update price db and track price history when a new price is entered on a PO

Keeps the most current price in the master list.

IM16 Automatic creation of a materials re-order listBased upon pre-established inventory thresholds, when an inventory threshold is reached, create a purchase list.

IM17 Automatically update quantities when the ordered materials arrivesWhen the order arrives, the system should have a means of updating quantities whether it be from scanning the invoice or another method, but the inventory should not have to be entered manually.

IM18Flexibility around distribution inventory accounting methods- e.g. First In First Out (FIFO), LIFO, specific identification, and Weighted Average unit cost calculation.

Sometimes the FIFO method is best, but not all times. The system must allow certain material types to specify a specific distribution approach.

IM19Ability to handle long lead items - set a time period for receiving new inventory and a typical usage rate

The system should be able to handle long lead items such that it informs the user of the need to order those items where there will be no shortage.

IM20 Remote (Field Staff) order ability Remote staff must be able to place an order through the systemIM21 Support inventory expiration dates Managing the expiration of materialsIM22 Notification that inventory levels are insufficient for WO requirements Ability for the system to compare WO needs against available materials

IM23 Ability to track multiple locations for inventoryInventory will exist at the warehouse as well as at the plants. The system needs to track inventory at all locations in a consolidated view.

IM24 Inventory counting cycles derived from unit cost and volume classifications Added by L&P Field

IM25Return for credit processing against original work orders (particularly important for transformers and unused portions of cable reels)

Added by L&P Field

IM26Post-transaction validation of issue documents against work order requirements

Added by L&P Field

IM27Accounting of shipping and USPS postage expenditures against unique work orders or account codes

Added by L&P Field

EM1Manage special tools/equipment including reservations, checkout, condition and returns

EM2Manage special tools/equipment inspection schedules (Fall protection equipment, AEDs, hotsticks, meters, rubber gloves, etc.)

EM3 Help determine costs to bill for rolling stock Use industry standard rates for rolling stockEM4 Track dates when equipment status changedEM5 Collect and report historical equipment calibration Allows the organization to see trending and determine if an asset is degrading.EM6 Show historical equipment calibration specs as a graph Tracking calibration specs helps to identify equipment that is failingEM7 Track equipment location

SR1 Report the status of customer service request and related work ordersSR2 The creation, routing and approval of service requests To replace trouble call systemSR3 Display copies of customer service requests imported from CISSR4 Creation of a service request from an email

Equipment Management

Service Requests

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Core FunctionalityProposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software, SR5 Creation of a service request from another system E.G. Using web services

FDM1 View work order & asset on hand-heldFDM2 Collect asset information on hand-heldFDM3 Create new service request on hand-heldFDM4 Complete work order on hand-heldFDM5 Dock or sync hand-held at day's start/endFDM6 Wireless connection to live CMMS

FM1 Vehicle Maintenance Tracking to store a subset of the full data set. Only the maintenance that is NOT done by fleet

FM2 Vehicle Location Tracking

REP1 Report full lifecycle costs per assetREP2 Ad-Hoc Reporting CapabilitiesREP3 Pre-Defined Reporting CapabilitiesREP4 KPI / Dashboard ReportingREP5 Export to ExcelREP6 Gantt chart or other visual view of all PMs

Vendor Scoring OptionsOOBCON MODCUSTPRTFRN/A

Reporting

Field Data Management

Fleet Management

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Select one of the following responses:

OOBCON MODCUSTPRTFRNA

StrategicS1 Vendor Industry PositionS2 Vendor StabilityS3 Limit Usage of 3rd Party Applications (for core functionality)S4 Strength of Product RoadmapS5 MIS Strategic FitS6 Alignment with the Utility's Training Program Accredited training program to count towards continuing education. (CEUs)S7 Culture Team (CVA)S8 Triple Bottom Line - Criteria for all Large Purchases and Consulting HiresS9 Workforce Team - Knowledge Capture - Succession Planning

S10 Utility Sustainability

S11 Performance Excellence - ICMA involvementCity Manager project to help the city stand out amongst its peers. (ICMA - International City Managers Association)

S12 Successful Deployment at a Similar UtilitySimilar Utility is 100,000 customers covering both wet and dry distribution/network utilities.

S13 Support for ISO 14,001 complianceS14 Compliance with National Institute of Standards and Technology NIST800-53 S15 PMP Certified Project ManagersS16 Ease of Interface with Vendor Ability to easily interface with the vendor in making changes.

RiskR1 Risk of Technical Failure Are we comfortable with the technology they are built on?R2 Risk of Data Failure Can you show us where you've done this before, your import engine,etc.R3 Risk of Business Failure Usability of the system - user interaction and buy in on the system.R4 Nature and Magnitude of Change for Core UsersR5 Robust Training Methodology and Materials Online training, CBTs, Classroom, Local, etc.

Proposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software, or special hardware items noted must be included under the separate Pricing submittal, unless otherwise specified. Proposers must clearly indicate one (1) of the listed responses to each requirement and provide comment to describe approach. Also indicate whether fulfillment of the requirement is included in the Cost Proposal.

Strategic, Financial & Risk-Based Requirements

Provided through a reporting toolProvided through a future releaseNot available

For each requirement answer: Is the System Requirement supported by the EAM System?

Fully provided Out of the BoxProvided through ConfigurationProvided through a technical modification of the software product baselineProvided through a technical modification of the software as a customization for the clientThird party software required

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Proposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional

Strategic, Financial & Risk-Based Requirements

FinancialF1 License and Annual Support CostsF2 Hardware CostsF3 Implementation CostsF4 Licensing Includes Test & Training Environments

EXHIBIT “D” Technical Requirements

And Qualifications Statements

# Question Definition

1 Provide list of web services that you expose2 Which mapping solutions does your system integrate with?3 What IT industry standards do you adhere to?

4Which IT industry standards boards do you actively participate in and influence?

5 Hardware Sizing Recommendation, include optimal user load for recommended hardware. need to provide numbers in RFP (community, asset estimates, number of users)6 Provide License pricing model look into potential user numbers7 Does your solution come with a built in mapping capability? E.G. Built on ESRI

8 Does your appliction provide mapping for electric,water,stormwater,wastewater,fiber,backflow?

9Provide a list of web service APIs and adapters that are included with your product? List additional costs for adapters if applicable.

10Provide typical db and application server sizing for a 150,000 customer utility that includes water, stormwater, wastewater and electric utilities.

11 Network Bandwidth Requirements to retain optimal performance What is the recommended network speed (Mb/sec)for the application to perform well?12 Average page render time in a real world scenario In Seconds

13 What is the technology/platform/architecture used? MIS Ability to Support (Alignment with City of Fort Collins IT - Infrastructure and Apps)

14 Active User Community Provide references (Websites, regional user groups, etc)15 Active Developer Community Provide references (Websites, regional user groups, etc)16 Provide Examples of your Out-Of-The-Box Reports for Work Orders and Assets17 Describe your typical UAT process.

18 Describe your cut-over / go-live process. (Ideally we want some kind of 60-day ‘stabilization’ period before go-live is considered complete.)

1920212223

Qualifications for Written Statements

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Select one of the following responses:

OOBCON MODCUSTPRTFRNA

Compatibility & Compliance CC1 Web-Browser Support - IE8

CC2 Web-Browser Support - IE7 CC3 Virtualized Server Support CC4 DB Support - Oracle (11gR1, R2) CC5 Support Oracle 10 and11g app servers If J2EE container required CC6 Windows Server 2008 R2 OS Support

CC7 Tablet Device Compatibility -- Windows OS CMMS must be able to run in a fully functional mode on tabletCC8 Droid OS Compatibility CMMS must be able to run in a fully functional mode on tablet or phoneCC9 iOS Compatibility CMMS must be able to run in a fully functional mode on tablet or phone

CC10 Active Directory Integration CC11 Single Sign-On / Pass-Through Authentication Support 90 day password rotation - 25 password cache - (If not using AD) CC12 Support Crystal Reporting

CC13 FCU Password Policy Compliance 8+ characters, alpha +numeric required if not using ADCC14 Standard Web Image Format Support e.g. .PNG, .JPG, .GIFCC15 Support Database ClusteringCC16 Support SAP (Xcelcius) Dashboard DesignCC17 Support Internet Protocol v6CC18 Windows XP CompatibleCC19 Windows 7 CompatibleCC20 Must be able to Operate over a 3G ConnectionCC21 Provide Flexible Integration Framework via Web Services For integration and data transaction purposesCC22 Support Bar Code Standards

CC23Allow Direct Database Read-Only Access (odbc/jdbc) for Reporting Purposes (Crystal Reports)

CC24 Supports SQL Server 2005 and 2008CC25 Application Supports Data Guard or Similar for Database Disaster Recovery

Integrations

I1 Integrate with Enterprise Service Bus (Next Axiom)Assumption is that ESB would provide integration with all below applications if they are connected to ESB

I2 Integrate with ESRI GIS ArcGIS/ArcGIS Server v9.3.1 and v10I3 Integrate with Utility CAD File Systems Including Object Data Identifier UVIEW in house mapping based upon AutoCAD/Bentley redlineI4 Integrate with CIS (Ventyx Customer Suite v4.1 CIS)

Proposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software, or special hardware items noted must be included under the separate Pricing submittal, unless otherwise specified. Proposers must clearly indicate one (1) of the listed responses to each requirement and provide comment to describe approach. Also indicate whether fulfillment of the requirement is included in the Cost Proposal.

Technical Requirements

Provided through a reporting toolProvided through a future releaseNot available

For each requirement answer: Is the System Requirement supported by the EAM System?

Fully provided Out of the BoxProvided through ConfigurationProvided through a technical modification of the software product baselineProvided through a technical modification of the software as a customization for the clientThird party software required

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Proposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software,

Technical Requirements

I5 Integrate with JDE v9I6 Integrate with DMS (Sire v5.2)

I7Secure information transfer with Water SCADA (Genesis 64) - No Connectivity Between Water SCADA and CMMS

Note: SCADA on separate network

I8 Integrate with Public Works Asset Management System (CityWorks) For assets which cross division boundaries (Fleet?)I9 Integrate with MS Access 2002 Required to pull information from homegrown "WetLIMDS" system.

I10 Integrate with Corporate Email System (MS Outlook Exchange 2010) MS Outlook will be brought in-house fall 2011.I11 Integrate with Accela v 7.1 (Electric Meters)I12 Integrate with eMeter's EnergyIP version 7.2 or later CSU's MDMS

I13Integrate with MS Outlook Calendar to Populate Calendars with Work Orders, Service Requests, etc.

ArchitectureA1 Concurrent User Support (300 total 50-100 concurrent)A2 Standards-BasedA3 Web-Based Modern Architecture E.G. .NET, J2EEA4 Architecture Supports High Availability (Failover/Clustering) Technologies Target availability is 99.99%A5 Hot System Backup (App Server) Supported Backing up the application server without taking it down.A6 Role-Based Security Enforced

ToolsT1 Includes Administrator ToolsT2 Includes Web-Based Administrator Tools

T3 Includes Developer ToolsT4 Includes Web-Based Developer ToolsT5 Includes Configuration ToolsT6 Includes Web-Based Configuration ToolsT7 Published APIs or Adapters

SupportS1 Hotfix Support Patch can be applied without taking the server(s) down.S2 Product Updates Can Be Rolled BackS3 Efficient Product Updates (less than 4hrs)S4 Planned Patch Support and Notification (from Vendor)S5 Robust Error Logging

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Proposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software,

Technical Requirements

S6 Is there a Local Implementer?

ConfigurationC1 Web-Based ConfigurationC2 Web-Based Workflow AuthoringC3 Configurable Screens

C4Add New / Additional Lookup Values On the Fly (pre-identified, non MIS power users to modify field values) when appropriate.

Adding to dropdown lists and such on the fly.

DataD1 Data Import/Export Capabilities (e.g. MS Excel)D2 Encrypted Password Support If not using ADD3 System Domain Account Support in Both OS and DB. (not coding in personal credentials)D4 Rigorous and Granular Data Backup/Restore Procedures We would expect to provide these procedures in FC. D5 Flexible, Robust, Data Load Procedures

D6Ability to Access Data External to the CMMS and Display it on custom CMMS Screens

e.g., using modern standards such as SOAP, Web Services

D7 Supports Transactions. Logical Units of Work Committed in a Single Transaction.

D8 Documented Data Model To be provided to Ft. CollinsD9 Normalized Data Model

D10 Referential Integrity Enforced We expect Referential Integrity to be enforced within the Database. D11 Configurable DB Auditing with TimestampsD12 Front-End Data Validation

OtherO1 Supports On-Line Mode and Off-Line Mobile SyncO2 Date Format Flexibility/Synchronization Between Systems No dates in text mode. Must be date data type.O3 Utilization LoggingO4 Maintain User Preference Settings (configurable, persistent settings)O5 Adjustable Auto Log Out of Idle UsersO6 Full Audit Trail Capabilities (Non-db triggers driven) Triggers hinder scalability. O7 Ability to Copy / Paste System Objects e.g. assets (from the UI) O8 Structured/Canned WorkflowsO9 Ad-Hoc Workflows

O10 Field-Level Security EnforcedO11 All SQL will be Parameterized or use Bind Variables For better performance and to prevent SQL injection

Exhibit “E” Asset Hierarchy

And Sample Asset Register

FCU

WE&FO WR&T

Process Areas

System #1

System #3

System #2

System #4

Civil

Mechanical

Electrical

Instrumentation

Site

Fencing / WallsRoadways

LandscapingSite Lighting

Security

City of Fort Collins Utilities – Asset Hierarchy

L&P

Infrastructure/Piping

Yardpiping Manhole

Yard Valves

Rolling Stock

Vehicles

Generator (Portable)

Pump (Portable)

Lift/Bucket Truck Tractor Truck

Trailer (Tractor Truck)

Spreaders (Solid)

Electrical

SCADA

Distribution Network

Pipes

Water

Laterals/

Service

Connections

Locator

Stations

Wastewater

Drainage Basin

Area

Stormwater

Basins

Sub Basins

Open

Channels

Bridges &

Culverts

Dams &

Levees

Outlets

Detention

Basins

Pipelines

Flood Warning Systems

Maintenance Equipment

Placeholder – assets yet to be determined (FCU to update in the future)

Infrastructure Equipment

Infrastructure Equipment

Secondary SystemHeavy Equipment

* WR&T Process Areas would include processes such as Headworks, Pump Stations, A-Basins, Clarifiers, Reservoirs, etc.

Service Valves

Maintenance Equipment

600 Amp Distribution

Maintenance Equipment

Mulberry Water

Reclamation Facility

Infrastructure Equipment

Cathodic

Protection

Mechanical

Facilities

Access Points

Hydrants

Blowoffs

Monitoring

Stations

Distribution

Valves

Drake Water

Reclamation Facility

Water Treatment

Facility

Meadow Springs

Ranch

Offsite Pumping and

StorageSource of Supply

Servers

SoftwarePLCs

Network Equipment

200 Amp

Distribution

Curb Stops

Meter

Backflow

Vaults

Pipes

Buildings

Building #1

Building #3

Building #2

Building #4

Civil

Mechanical

Electrical

Instrumentation

Vehicles

Equipment

Vehicles

Equipment

Diversion

Structures

Stubs

Cleanouts

Manholes

Laterals/

Service

Connections

Vehicles

Equipment

Civil

Mechanical

Electrical

Structures

Outdoor

Classrooms

Water Quality

Facilities

Laterals Inlets Chases Manholes

Buildings

HVAC Units

Site

Maintenance

Fencing/Walls

Roadways

Landscaping

Relays

Transformers

Security

Systems

Power Meters

Bushings

Oil

ContainmentBattery

Systems

Breakers

SCADA

RTU’s

900 MHZ

Radio

Ethernet

Switches

Conduit

Duct Banks

Vaults-600A

(Manhole)

Voltage

Regulators

Cable

Splices

Switches

Meters

Connections

Equipment Vehicles

Conduit

Wood Poles

Cable

Sectionalizing

Cabinets

Junctions

Cutouts

Insulators

Overhead

Conductor

Splices

Distribution

Transformer

Vaults

Meters 200A

Customers

Lamps

Poles

Cable

Vaults

Conduit

Cable

Conduit

Meters –

Secondary

Customers

Street Lights

Vaults

Water Production Water Reclamation Substations Rolling Stock Fiber Optic System

Connections

Wastewater Main Wastewater Main

Cit

yD

ocs M

ap

s

Attributes Field Type/Domain Parameter Default Field Description

Active x 1 1 x DB E L x

Area x 1 1 x DB E L x

C3 x 1 1 x DB E L x

CautionCode x 1 1 x DB E L x

CkBy x 1 1 x DB E L x

CkDate x 1 1 x DB E L x

Company x 1 1 x DB E L x

DateInst x 1 1 x DB E L x

Diameter x 1 1 x x DB E L x

DwnElev x 1 1 x x DB E L x

ExpireDate x 1 1 x DB E L x

FManHole x 1 1 x DB E L x

Gen_SpecInst x 1 1 x DB E L x

HotSpotFreq x 1 1 x DB E L x

InMainCount x 1 1 x DB E L x

Inv x 1 1 x x DB E L x

JointLength x 1 1 x x DB E L x

LChgDate x 1 1 x DB E L x

LChgUser x 1 1 x DB E L x

Length x 1 1 x x DB E L x

LinedMethod x 1 1 x x DB E L x

MainID x 1 1 x DB E L x

MapIndex x 1 1 x DB E L x

MapLoc x 1 1 x DB E L x

NewDate x 1 1 x DB E L x

NewUser x 1 1 x DB E L x

OldFManHole x 1 1 x DB E L x

OldTManHole x 1 1 x DB E L x

PipeType x 1 1 x x DB E L x

ProjectName x 1 1 x DB E L x

ProjectType x 1 1 x DB E L x

s_ColLineage x 1 1 x DB E L x

s_Generation x 1 1 x DB E L x

s_GUID x 1 1 x DB E L x

s_Lineage x 1 1 x DB E L x

SpecInst x 1 1 x DB E L x

Status x 1 1 x DB E L x

StatusDate x 1 1 x DB E L x

TManHole x 1 1 x DB E L x

UniqueID x 1 1 x DB E L x

UpsElev x 1 1 x DB E L x

WarrantyDate x 1 1 x DB E L x

YearLined x 1 1 x DB E L x

Common Fields Cu

rren

tly C

ollecte

d

To

tal

% Migration Type

High Priority 13 17 76% Common Fields

Medium Priority 6 19 32% Drawing 0

Low Priority 0 1 0% Report 0

Spreadsheet 3

Object Fields Database 16

High Priority 18 18 ###

Medium Priority 25 25 ### Object Fields

Low Priority 0 0 ### Drawing 0

Report 0

Spreadsheet 0

Database 43

Typ

e o

f D

ata

(M

: M

an

ua

l; E

:

Ele

ctr

on

ic)

Oth

er

Data Location

GIS

CM

MS

CIS

FIS

SC

AD

A

Ha

rdco

py R

ep

ort

s,

Ma

ste

r P

lan

nin

g D

oc,

En

gin

eeri

ng

Rep

ort

, O

&M

Ma

nu

al

En

terp

rise D

ocs.

FU

PS

GIS

A: Asset Identifier

T: Technical Data

V: Valuation/Depreciation Data

M: Maintenance Data

C: Condition Data

R: Risk Data

L: Lifecycle Data

F: Failure Data

B: Budget Data

WR: Works/Resource

ORDM: Optimal Renewal Data

P: Performance Data

I: Inventory Data

Level of Importance

Ob

ject

Fie

lds

Pri

ma

ry (

Ph

ysic

al)

Seco

nd

ary

(C

on

dit

ion

)

Tert

iary

(C

ost)

Priority Performance Management Source Migration

Mo

ve (

L:

Lin

k;

V:

Va

lue)

En

gin

eeri

ng

Op

era

tio

ns

Sr.

Ma

na

gem

en

t / F

ina

nce

Reso

urc

e M

an

ag

em

en

t

Fo

rma

t (D

: D

raw

ing

; R

: R

ep

ort

; S

:

Sp

rea

dsh

eet;

DB

: D

ata

ba

se)

Cu

rren

t R

eg

ula

tio

ns

Do

es N

ot

Cu

rren

tly E

xis

t

Hig

h (

Bu

sin

ess C

riti

ca

l -

op

s n

eed

s)

Med

ium

(N

ice t

o H

ave -

decis

ion

ma

kin

g)

Lo

w (

No

t N

eed

ed

- O

ther

an

aly

sis

)

Sta

ff K

no

wle

dg

e

Co

llecte

d? (

1=

TR

UE

, 0

=FA

LS

E)

Source Priority

Oth

er

Sp

rea

dsh

eet,

Da

tab

ase,

etc

.

Perm

it T

rack

Po

nd

In

sp

ecti

on

Da

tab

ase

S4

Perm

it

Sit

e V

isit

Info

Wa

ter

MD

I

MW

HS

oft

H2

oM

ap

Sew

er

MW

HS

oft

H2

OM

ap

Wa

ter

Oth

er

– E

lectr

on

ic (E

xcel,

UN

IX,

e-S

erv

er)

Ap

pro

pri

ati

on

s S

tatu

s D

ata

ba

se

Ca

tho

dic

Pro

tecti

on

Da

tab

ase

CIS

WEWE&FO Wastewater_PDF.xlsxO Wastewater 10

Exhibit “F” Sample Level of Service Document

Asset Management Levels of Service Owner: Dwight Dufloth & Lisa VoytkoPotable Water Treatment and Distribution

Key Service Criteria

Performance Indicator Target Level of Service Measurement Process Current Performance (end of 2010 calendar year)

Comments

Taste, Odor, and Color Complaints

82 Total Rusty/Dirty water complaints over last 4 years

T&O complaints related to water treatment

41 T&O Complaints over last 4 years

Rusty/dirty water complaints related to line flushing/water main breaks.

T&O Complaints = 0.85/mo.

Data that tracks number of customer complaints and what type re: water quality is kepy by the Water Quality Lab. This data is an average of the last 4 years for T&O and rusty/dirty water complaints.

Rusty/Dirty Water = 1.7 complaints/mo.

Regulatory Maximum Contaminant Limits & City Water Treatment Facility Limits

100% compliance with Maximum Contaminant Limits & City Water Treatment Facility Limits

Continuous sampling at plant 100% compliance 100% compliance is required and is continuously achieved at the WTF.

Reliability Pressure at meter Pressure in distribution system > 20 PSI

Undertake pressure and flow tests at time of meter installation

Average frequency of outages

Average frequency of outages less than one per yearNo more than 2% of customers receive more than two outages per year

Average duration of outages

Average duration of outages less than two to four hoursNo more than 2% of customers receive an outage of more than three hours duration

Fire fighting flow at hydrant

Fire flow (residential = 1000 gpm, commercial = 1500 gpm)

Pressure > 20psi in fire-fighting condition

Availability Number of days where water restrictions are in place

Water restrictions in place for no more than 30 days per year on average

Record number of days per year water restrictions are in place

100% compliance since 2003

Responsiveness to outages

Response time to customer complaints due to a loss of supply

Respond to customer complaints regarding loss of supply within 30 minutes 99% of the time

Measure time that complaint is received versus time of arrival onsite

99% within 30 minutes

Water Loss Unaccounted water < 6% unaccounted water loss/revenue

Measure water production versus metered sales

TBD This will be investigated further once AMI is operational.

TBD

Measure flow at fire hydrants as part of maintenance and testing program

Quality <1 complaint /month regarding taste, odor, or rusty/dirty water

Number of complaints regarding taste, odor, or rusty/dirty water

Record duration and number of customers affected for all outages

Exhibit “G” Data Migration Effort

Utility System Name # WOs

Field

Water WUMS 48,000

Wastewater WIST 53,000

Stormwater SWIMS 1,500

Total Field WOs 54,500

Plant

Water Treatment Facility 19,311

Waste Water Treatment Facility 27,705

Total Plant WOs 47,016

Total 101,516

Utility Work Order Summary

Utility Asset Type # Assets

Field Assets

Water

Mains 10,000

Valves 12,000

Hydrants 3,600

Wastewater

Mains 10,700

Manholes 10,600

Stormwater

Lines 13,700

Points 14,000

Inlets 6,800

Manholes 3,200

Electric

Lines 18,800

Transformers 7,500

Switch Points 17,800

Total Field Assets 128,700

Plant Assets

Water Treatment Facility 4,511

Waste Water Treatment Facility 4,169

Total Plant Assets 8,680

Total 137,380

Utility Asset Summary

IntakeCountByBlockName

CountOfPointID

AcadBlockName

TVIConditionRoot

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

TVIConditionDebris

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

LINE

PK LineID

U2 UniqueID

I12 OldUniqueID

I6 CompType

I8 FPoint

OldFPoint

I18 TPoint

OldTPoint

AKA

I3 Area

FK1,I1 MatType

WDiameter

HDiameter

Length

JointLength

UpsElev

DwnElev

SpecInst

InLineCount

I9 HotSpotFreq

DateInst

WarrantyDate

CityOwned

CityMaintained

FK3,I11 MapLoc

MapIndex

FK2,I5,I4 CautionCode

ProjectType

ProjectName

CkDate

CkBy

I7 ConditionCode

LastInspDate

CoFScore

CoFDate

I2 Active

FK4,FK5,FK6,I17,I16,I15,I14 Status

StatusDate

ExpireDate

I10 Inv

Aen_SpecInst

LChgDate

LChgUser

U1 s_GUID

Gen_SpecInst

NewDate

NewUser

s_ColLineage

I13 s_Generation

s_Lineage

COMPACTPRBCDE

PK,I2 Comp

PK,I1 ActCde

PK,I3 PrbCde

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

OutfallsWithoutScreening

PointNum

STREETNO

STREETNAME

Qualifier

Area

ACTCDE

PK ActCde

I1 Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

SCREENSAMPLEINFRASTRUCTURE

PK,I3 ScreeningId

PK,I2 SampleId

SampleDate

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

MSysAccessStorage_Conflict

I1 ConflictRowGuid

DateCreate

DateUpdate

Id

Lv

Name

ParentId

Type

Gen_Lv

I2 s_Generation

I3 s_GUID

s_Lineage

Location

PK,I1 Code

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

BASINMAT

PK,I1 MatCde

Description

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

WQFEATURE

PK WQFeature

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

tblBasinAttach_old

PK,I2 ID

I1 BasinID

Attachment

U1 s_GUID

POINT_Conflict

I1 ConflictRowGuid

PointID

PointNum

OldPointNum

CompType

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

AKA

Qualifier

Area

Measurements

Drop

Depth

CoverDiam

BarrelDiam

Material

StepsMat

SurfCover

InletType

GrtType

InWidth

InHeight

GrtWidth

GrtLength

Capacity

SpecInst

DateInst

WarrantyDate

DumpNoWasteMarker

WtrQltyFeature

CityOwned

DumpNoWasteDate

FloodPlain

CityMaintained

PermitStartDate

DateCertified

MapLoc

MapIndex

CautionCode

ProjectType

CkDate

ProjectName

CkBy

Active

NewDate

NewUser

LChgDate

LChgUser

Status

ConditionCode

StatusDate

ExpireDate

LastInspDate

CoFScore

Gen_Measurements

CoFDate

Gen_SpecInst

Aen_Measurements

Aen_SpecInst

I3 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

EMREVENT

PK EventNum

I1 Date

I2 Description

I3 Quadrant

s_ColLineage

I4 s_Generation

U1 s_GUID

s_Lineage

OutfallsWithScreening

PointNum

Date

STREETNO

STREETNAME

Qualifier

Area

SampleId

WOLINELIST

PK,FK1,I5,I1 WoNum

PK,FK2,I3,I2 LineID

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

TVIConditionStructural

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

CUSTCONT

PK DateTime

PK Name

Address

Phone

Notes

I1 CompletionDate

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

AREA

PK,I1 Area

Desc

Frequency

I2 NextDueDate

U1 s_GUID

s_ColLineage

I3 s_Generation

s_Lineage

WOEMPLOYEE

PK,FK1,I2,I1 WoNum

PK,I3 EmpID

PK Date

RegHours

OTHours

RegRate

OTRate

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

TVIConditionInflow

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

STATUS

PK StatCde

Desc

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

POINTWQFEATURE

PK,FK1,I2,I1 PointID

PK WQFeature

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

LINETVINSP_Conflict

I1 ConflictRowGuid

WoNum

LineID

TVOperator

FlowDepth

Summary

I3 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

tblNextNodeNumber

PK NextNodeNumber

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

SCREENSAMPLEOUTFALL

PK,FK1,I4,I3 ScreeningId

PK,I2 SampleId

SampleDate

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

MAPLOC

PK MapLoc

LocDesc

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

LINETVINSPFEET_Conflict

I1 ConflictRowGuid

WoNum

LineID

Setup

Feet

ClockPosition

CrackRC

CrackLC

JointMJ

JointBJ

Lateral

Roots

Debris

Inflow

Align

StructDS

StructOS

StructCS

Comments

I3 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

LINE_Log

PK LineID

PK UserName

PK DateTime

UniqueID

OldUniqueID

CompType

FPoint

OldFPoint

TPoint

OldTPoint

AKA

Area

MatType

WDiameter

HDiameter

Length

JointLength

UpsElev

DwnElev

SpecInst

InLineCount

HotSpotFreq

DateInst

CityOwned

CityMaintained

MapLoc

MapIndex

I1 CautionCode

ProjectType

CkDate

CkBy

Active

Status

StatusDate

ExpireDate

I2 Inv

LChgDate

LChgUser

NewDate

NewUser

Aen_SpecInst

Gen_SpecInst

Ben_SpecInst

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

BRIDGEMAT

PK,I1 MatCde

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

WOLINELIST_Conflict

I1 ConflictRowGuid

WoNum

LineID

I3 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

POINT_Log

PK PointID

PK UserName

PK DateTime

PointNum

OldPointNum

CompType

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

AKA

Qualifier

Area

Measurements

Drop

Depth

CoverDiam

BarrelDiam

Material

StepsMat

SurfCover

InletType

GrtType

InWidth

InHeight

GrtWidth

GrtLength

Capacity

SpecInst

DateInst

WarrantyDate

WtrQltyFeature

CityOwned

CityMaintained

MapLoc

MapIndex

I1 CautionCode

ProjectType

CkDate

CkBy

Active

NewDate

NewUser

LChgDate

LChgUser

Status

StatusDate

ExpireDate

Aen_Measurements

Aen_SpecInst

Gen_Measurements

Gen_SpecInst

Ben_Measurements

Ben_SpecInst

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

PRBCDE

PK PrbCde

U1 Description

U2 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

POINTINSPECTION

PK,I1 PointID

PK Date

I2 RefId

Inspector

I4 WoNum

OverAllCondition

01Condition

01Comment

02Condition

02Comment

03Condition

03Comment

04Condition

04Comment

05Condition

05Comment

06Condition

06Comment

07Condition

07Comment

08Condition

08Comment

09Condition

09Comment

10Condition

10Comment

11Condition

11Comment

12Condition

12Comment

13Condition

13Comment

14Condition

14Comment

15Condition

15Comment

16Condition

16Comment

17Condition

17Comment

18Condition

18Comment

19Condition

19Comment

20Condition

20Comment

MaintenanceNeededNote

GeneralAppearanceNote

Gen_GeneralAppearanceNote

Gen_MaintenanceNeededNote

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

INLETMAT

PK,I1 MatCde

Description

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

GRATETYPE

PK,I1 Type

Description

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

EQUIPMENT

PK UnitID

I2 Description

Type

Location

I4 SerialNum

I1 ModelNum

Manufacturer

PurchDate

PurchCost

ChgAmount

AssignedTo

Year

LicenseNo

Dept

FuelType

Unit

AdditionalCostDate

AdditionalCostAmt

AdditionalCosts

Inuse

I5 Status

StatusDate

ExpireDate

NewDate

NewUser

LChgDate

s_ColLineage

LChgUser

I3 s_Generation

U1 s_GUID

s_Lineage

TYPESITE

TYPESITE

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

TVIConditionJoint

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

TVIConditionAlignment

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

STEPMAT

PK,I1 MatCde

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

OTRATE

OTRate

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

CAUTIONCDE

PK CautionCode

I1 Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

BARRELDIAM

PK,I1 Diameter

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

StateReport

PK,I1 ReportID

A

B

C

D

E

F

G

H

I

J

K

L

M

N

O

ReportDate

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

MATERIAL

PK MatID

Description

Units

Price

I1 Active

ExpireDate

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

DUMPNOWASTEMARKERTYPE

PK DumpNoWasteMarkerType

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

WOMATERIAL

PK,FK1,I3,I1 WoNum

PK,FK2,I4,I2 MatID

Qty

Price

U1 s_GUID

s_ColLineage

I5 s_Generation

s_Lineage

LINETVINSPFEET

PK,FK1,I1 WoNum

PK,FK1,I14,I1 LineID

PK Setup

PK Feet

ClockPosition

FK3,I3 CrackRC

FK4,I4 CrackLC

FK7,I7 JointMJ

FK8,I8 JointBJ

FK9,I9 Lateral

FK10,I10 Roots

FK5,I5 Debris

FK6,I6 Inflow

FK2,I2 Align

FK11,I11 StructDS

FK12,I12 StructOS

FK13,I13 StructCS

Comments

U1 s_GUID

s_ColLineage

I15 s_Generation

s_Lineage

bar

PointNum

STREETNO

STREETNAME

STREETDIR

TYPESITE

Area

GrtType

SpecInst

WOEQUIPLIST

PK,FK1,I1,I4 WoNum

PK,I2 UnitID

U1 s_GUID

s_ColLineage

I3 s_Generation

s_Lineage

WO

PK WoNum

Gen_Comments

I11 CompType

FK2,I2 ActCde

FK1,I1 PrbCde

I7 Project

FK4,I9,I8 ProjectType

I3 Area

Priority

SchedStartDate

AssignedTo

RequestDate

Originator

CompletionDate

Comments

CallTime

ContactTime

ArrivalTime

CallName

CallPhone

I4 CompNum

Company

Aen_Comments

Phone

Attention

U1 s_GUID

Address1

PermitNo

s_ColLineage

Address2

I10 s_Generation

FK3,I6,I5 EventNum

s_Lineage

PROJECTTYPE

PK,I1 ProjectType

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

OUTLETMAT

PK,I1 MatCde

Description

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage LINE_Conflict

I1 ConflictRowGuid

LineID

UniqueID

OldUniqueID

CompType

FPoint

OldFPoint

TPoint

OldTPoint

AKA

Area

MatType

WDiameter

HDiameter

Length

JointLength

UpsElev

DwnElev

SpecInst

InLineCount

HotSpotFreq

DateInst

WarrantyDate

CityOwned

CityMaintained

MapLoc

MapIndex

CautionCode

ProjectType

ProjectName

CkDate

CkBy

Active

ConditionCode

LastInspDate

Status

CoFScore

StatusDate

CoFDate

ExpireDate

Inv

LChgDate

LChgUser

Aen_SpecInst

NewDate

NewUser

I3 s_GUID

Gen_SpecInst

s_ColLineage

I2 s_Generation

s_Lineage

INLETTYPE

PK,I1 Type

Description

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

HOAInfo

PK,I2 HOAID

Company

ContactName

HOAName

Address

City

StateOrProvince

I3 PostalCode

Country

I1 EmailAddress

WebAddress

WorkPhone

WorkExtension

DateLastTalkedTo

DateUpdated

Notes

Gen_EmailAddress

Gen_Notes

Gen_WebAddress

s_ColLineage

I4 s_Generation

U1 s_GUID

s_Lineage

Basin

PK,I1 BasinID

QS

SW #

Name

Address

Subdivision

HOA

Notes

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

WO_Conflict

I1 ConflictRowGuid

Gen_Comments

WoNum

CompType

ActCde

PrbCde

Project

ProjectType

Area

Priority

SchedStartDate

AssignedTo

RequestDate

Originator

CompletionDate

Comments

CallTime

ContactTime

ArrivalTime

CallName

CallPhone

CompNum

Company

Aen_Comments

Phone

Attention

I3 s_GUID

Address1

PermitNo

s_ColLineage

Address2

I2 s_Generation

EventNum

s_Lineage

TVIConditionLateral

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

TVIConditionCrack

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

SURFMAT

PK,I1 MatCde

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

LINEMATTYPE

PK LineMatType

Description

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

LEVEEMAT

PK,I1 MatCde

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

EMPLOYEE

PK EmpID

I3 EmpCde

FirstName

I2 LastName

RegRate

OTRate

I1 Active

ExpireDate

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

COMPACT

PK,I2 Comp

PK,I1 ActCde

s_ColLineage

I3 s_Generation

s_Lineage

U1 s_GUID

WOEQUIPMENT

PK,FK1,I2,I1 WoNum

PK,I4 UnitID

PK Date

Hours

Rate

U1 s_GUID

s_ColLineage

I3 s_Generation

s_Lineage

WOPOINTLIST

PK,FK2,I5,I2 WoNum

PK,FK1,I3,I1 PointID

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

WOCONTRACT

PK,FK1,I1,I4 WoNum

PK,I2 Contractor

Hours

Rate

Materials

Labor

Total

U1 s_GUID

s_ColLineage

I3 s_Generation

s_Lineage

tblBasinAttach

PK,I2 ID

I1 BasinID

Attachment

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

SCREENOUTFALL

PK,I6 ScreeningId

FK1,FK2,I3,I2,I1 PointID

Date

WaterBody

RainOrSnow

Flow

FlowEstimate

WaterQty

Floatables

FloatablesDesc

Odor

OdorDesc

Stained

StainedDesc

Damage

DamageDesc

VegetationChange

VegetationDesc

BiomatCoating

InvestigateFurther

InvestigateFurtherDesc

SampleDate

I5 SampleId

InvestigateFurtherWQL

InvestigateFurtherWQLDesc

SourceOfFlow

ImproperConnectionSource

DateRemoved

Note

Gen_Note

s_ColLineage

I4 s_Generation

U1 s_GUID

s_Lineage

SCREENINFRASTRUCTURE

FK1,FK2,I7,I6 ScreeningId

I1 Id

I2 PointNum

InfraType

Date

Flow

FlowEstimate

WaterQty

Floatables

FloatablesDesc

Odor

OdorDesc

Stained

StainedDesc

Damage

DamageDesc

VegetationChange

VegetationDesc

BiomatCoating

InvestigateFurther

InvestigateFurtherDesc

SampleDate

I4 SampleId

InvestigateFurtherWQL

InvestigateFurtherWQLDesc

Note

Gen_Note

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

POINT

PK PointID

U2 PointNum

I9 OldPointNum

I6 CompType

I16 STREETNO

STREETNOHALF

STREETDIR

I15 STREETNAME

TYPESITE

STREETSUFX

APARTNO

AKA

Qualifier

FK1,I3,I2 Area

Measurements

Drop

Depth

CoverDiam

BarrelDiam

Material

StepsMat

SurfCover

InletType

GrtType

InWidth

InHeight

GrtWidth

GrtLength

Capacity

SpecInst

DateInst

WarrantyDate

DumpNoWasteMarker

DumpNoWasteDate

WtrQltyFeature

FloodPlain

PermitStartDate

DateCertified

CityOwned

CityMaintained

FK3,I8 MapLoc

MapIndex

FK2,I5,I4 CautionCode

ProjectType

ProjectName

CkDate

CkBy

I7 ConditionCode

LastInspDate

CoFScore

CoFDate

I1 Active

NewDate

NewUser

Gen_SpecInst

LChgDate

Aen_SpecInst

LChgUser

Gen_Measurements

FK4,FK5,FK6,I14,I13,I12,I11 Status

Aen_Measurements

StatusDate

ExpireDate

U1 s_GUID

s_ColLineage

I10 s_Generation

s_Lineage

MHMAT

PK,I1 MatCde

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

LINETVINSP

PK,FK1 WoNum

PK,FK1 LineID

TVOperator

FlowDepth

Summary

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

LINEINSPECTION

PK,I1 LineID

PK Date

I2 RefId

Inspector

I4 WoNum

OverAllCondition

01Condition

01Comment

02Condition

02Comment

03Condition

03Comment

04Condition

04Comment

05Condition

05Comment

06Condition

06Comment

07Condition

07Comment

08Condition

08Comment

09Condition

09Comment

10Condition

10Comment

11Condition

11Comment

12Condition

12Comment

13Condition

13Comment

14Condition

14Comment

15Condition

15Comment

16Condition

16Comment

17Condition

17Comment

18Condition

18Comment

19Condition

19Comment

20Condition

20Comment

MaintenanceNeededNote

GeneralAppearanceNote

Gen_GeneralAppearanceNote

Gen_MaintenanceNeededNote

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

Inspections

PK,I2 RecordID

Date

BasinName

BasinAddress

Inspector

I1 HOAID

HOAName

HOAContact

HOAAddress

ReasonForInspection

Enforcement

Outlet

Inlet

TricklePan

Vegetation

Erosion

OverflowWeir

MiscNotes

CurrentState

CorrectionDate

Subdivision

Gen_MiscNotes

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

Stormwater CMMS (SWIMS) ERD

WOEMPLOYEE

PK,FK1,I2,I1 WoNum

PK,I3 EmpID

PK Date

RegHours

OTHours

RegRate

OTRate

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

MHMAT

PK,I1 MatCde

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

MAINTVINSPFEET

PK,FK1,I1 WoNum

PK,FK1,I14,I1 MainID

PK Setup

PK Feet

ClockPosition

FK3,I3 CrackRC

FK4,I4 CrackLC

FK7,I7 JointMJ

FK8,I8 JointBJ

FK9,I9 Lateral

FK10,I10 Roots

FK5,I5 Debris

FK6,I6 Inflow

FK2,I2 Align

FK11,I11 StructDS

FK12,I12 StructOS

FK13,I13 StructCS

Comments

U1 s_GUID

s_ColLineage

I15 s_Generation

s_Lineage

LABORGRP

PK LaborGrp

Description

RegRate

OTRate

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

TVInspect

UniqueID

TVIConditionStructural

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

TVIConditionInflow

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

ACTCDE

PK ActCde

I1 Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

COMPACTPRBCDE

PK,I2 Comp

PK,I1 ActCde

PK,I3 PrbCde

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

WOMANHLIST

PK,FK2,I5,I2 WoNum

PK,FK1,I3,I1 ManHoleID

Bugs

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

tblNextNodeNumber

PK NextNodeNumber

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

OTRATE

OTRate

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

AREA

PK,I1 Area

Frequency

I2 NextDueDate

U1 s_GUID

s_ColLineage

I3 s_Generation

s_Lineage

TYPESITE

PK TYPESITE

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

STATUS

PK StatCde

Desc

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

LINECOMPANY

PK CompanyName

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

WOEQUIPLIST

PK,FK1,I4,I1 WoNum

PK,I2 UnitID

U1 s_GUID

s_ColLineage

I3 s_Generation

s_Lineage

TVIConditionJoint

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

TVIConditionAlignment

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

PRBCDE

PK PrbCde

U1 Description

U2 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

MAINPIPETYPE

PK PipeType

Description

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

EMPLOYEE

PK EmpID

I3 EmpCde

LaborGrp

FirstName

I2 LastName

RegRate

OTRate

I1 Active

ExpireDate

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

Infiltration

MainID

UniqueID

Status

WoNum

DateInst

YearLined

CompletionDate

Inflow

Feet

Comments

WOMATERIAL

PK,FK1,I1,I3 WoNum

PK,FK2,I2,I4 MatID

Qty

Price

U1 s_GUID

s_ColLineage

I5 s_Generation

s_Lineage

MAPLOC

PK MapLoc

LocDesc

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

WO

PK WoNum

Gen_Comments

I9 CompType

FK2,I2 ActCde

FK1,I1 PrbCde

I5 Project

I6 ProjectType

I3 Area

Priority

SchedStartDate

AssignedTo

RequestDate

Originator

CompletionDate

Comments

CallTime

ContactTime

ArrivalTime

CallName

CallPhone

Aen_Comments

I4 CompNum

Company

Attention

s_ColLineage

Address1

Address2

I7 s_Generation

Phone

U1 s_GUID

s_Lineage

PermitNo

I8 TaskNum

STEPMAT

PK,I1 MatCde

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

Location

PK,I1 Code

Description

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

BARRELDIAM

PK,I1 Diameter

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

MainTVeed2011

UniqueID

MainID

MaxOfCompletionDate

Expr1

WOEQUIPMENT

PK,FK1,I2,I1 WoNum

PK,I4 UnitID

PK Date

Hours

Rate

U1 s_GUID

s_ColLineage

I3 s_Generation

s_Lineage

WOCONTRACT

PK,FK1,I1,I4 WoNum

PK,I2 Contractor

Hours

Rate

Materials

Labor

Total

U1 s_GUID

s_ColLineage

I3 s_Generation

s_Lineage

TVIConditionLateral

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

TVIConditionCrack

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

PROJECTTYPE

PK,I1 ProjectType

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

TASKMAINLIST

PK,I3 TaskNum

PK,I1 MainID

Footage

Condition

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

MATERIAL

PK MatID

Description

Units

Price

I1 Active

ExpireDate

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

NoTVInspections

MainID

UniqueID

Status

WoNum

DateInst

YearLined

CompletionDate

Inflow

Feet

Comments

WOSLLIST

PK,FK1,I3,I1 WoNum

PK,FK2,I2,I5 ServLineID

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

SURFMAT

PK,I1 MatCde

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

MAINTVINSP

PK,FK1 WoNum

PK,FK1 MainID

TVOperator

FlowDepth

Summary

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

MAIN

PK MainID

U2 UniqueID

FK3,I7 FManHole

I8 OldFManHole

FK2,I14 TManHole

I15 OldTManHole

I3 Area

FK1,I1 PipeType

Diameter

Length

C3

ProjectType

ProjectName

JointLength

UpsElev

DwnElev

SpecInst

InMainCount

I9 HotSpotFreq

DateInst

WarrantyDate

YearLined

LinedMethod

Company

YearFoamed

FoamCompany

MapLoc

MapIndex

FK4,I5,I4 CautionCode

CkDate

CkBy

I2 Active

I10 Inv

I6 ConditionCode

LastInspDate

CoFScore

CoFDate

s_ColLineage

FK5,I13,I12 Status

I11 s_Generation

StatusDate

ExpireDate

Gen_SpecInst

U1 s_GUID

LChgUser

s_Lineage

LChgDate

NewDate

NewUser

CAUTIONCDE

PK CautionCode

I1 Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

MANHOLE

PK ManHoleID

U3 ManHoleNum

U1 OldManHoleNum

I11 STREETNO

STREETNOHALF

STREETDIR

I10 STREETNAME

TYPESITE

STREETSUFX

APARTNO

Qualifier

FK1,I1,I3 Area

Measurements

Drop

Depth

CoverDiam

BarrelDiam

MHMaterial

StepsMat

SurfCover

C3

ProjectName

ProjectType

SpecInst

DateInst

WarrantyDate

YearLined

MapLoc

MapIndex

FK2,I5,I4 CautionCode

CkDate

CkBy

I2 Active

I6 ConditionCode

LastInspDate

CoFScore

CoFDate

LChgUser

LChgDate

NewUser

Gen_Measurements

NewDate

Gen_SpecInst

FK3,I9,I8 Status

StatusDate

ExpireDate

U2 s_GUID

s_ColLineage

I7 s_Generation

s_Lineage

TVIConditionRoot

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

TVIConditionDebris

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

SERVICELINE

PK ServLineID

Gen_SpecInst

FK2,I5,I2 MainID

I6 ManHoleNum

I7 Premise

UniqueID

I12 STREETNO

STREETNOHALF

STREETDIR

I11 STREETNAME

TYPESITE

STREETSUFX

APARTNO

FK1,I1 Area

Diameter

TapLocation

TapLocationFrom

I8 CleanoutLoc

Taps

SumpPump

SpecInst

WashContact

WashContactName

WashContactRegHrs

WashContactAftHrs

WashContactInst

MapLoc

MapIndex

FK3,I4,I3 CautionCode

Aen_SpecInst

ProjectType

CkDate

CkBy

s_ColLineage

NewDate

I9 s_Generation

NewUser

s_Lineage

FK4,I10 Status

ExpireDate

StatusDate

LChgDate

LChgUser

U1 s_GUID

FOAMCOMPANY

PK CompanyName

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

EQUIPMENT

PK UnitID

I2 Description

Type

Location

I4 SerialNum

I1 ModelNum

Manufacturer

PurchDate

PurchCost

ChgAmount

AssignedTo

Year

LicenseNo

Dept

FuelType

Unit

AdditionalCostDate

AdditionalCostAmt

AdditionalCosts

Inuse

I5 Status

StatusDate

ExpireDate

NewDate

NewUser

LChgDate

LChgUser

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

WOMAINLIST

PK,FK1,I5,I1 WoNum

PK,FK2,I3,I2 MainID

Footage

Condition

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

COMPACT

PK,I2 Comp

PK,I1 ActCde

U1 s_GUID

s_ColLineage

I3 s_Generation

s_Lineage

TASKMANHLIST

PK,I3 TaskNum

PK,I1 ManHoleID

Bugs

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

TASK

PK,I7 TaskNum

SchedType

Period

Frequency

LastPerfDate

I3 NextDueDate

I2 CompType

ActCde

PrbCde

I4 Project

I5 ProjectType

I1 Area

Priority

AssignedTo

Originator

Comments

Gen_Comments

s_ColLineage

I6 s_Generation

U1 s_GUID

s_Lineage

Wastewater CMMS (WIST) ERD

WOVALVELIST

PK,FK2,I5,I4 WoNum

PK,FK1,I3,I2 UnitID

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

WOHYDLIST

PK,FK1,I4,I3 WoNum

PK,I2 UnitID

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

VALMOD

PK MODEL

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

TESTSTATIONTYPE

PK TestStationType

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

CPDATA_Conflict

I1 ConflictRowGuid

CPID

ReadingDate

PSVolts1

PSVolts2

PSVolts3

PSVolts4

PSVolts5

PSVolts6

AnodeCurrent

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

BEAMDIST

Distance

Fraction

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

Query4

PressZone

WumsServLineInvID

WOCPLIST

PK,FK2,I5,I4 WoNum

PK,FK1,I1,I3 UnitID

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

OTRATE

PK OTRate

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

METERSIZE

PK Index

Size

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

MAINTRACER

PK,FK2,I3,I2 MainID

PK,FK1,I5,I1 UnitID

s_ColLineage

I4 s_Generation

U1 s_GUID

s_Lineage

MAIN

PK,I5 MainID

FK5,I8 MainType

I12 UniqueID

BLOCKNO

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

MAINDIR

FK4,I7 PipeType

PipeDiameter

Location

Area

PressZone

FK3,I6 Manufacturer

Length

DateInst

WarrantyDate

Depth

SpecInst

FK2,I4 Inspector

CP

C3

Project

MapLoc

MapIndex

FK1,I2,I1 CautionCode

I3 ConditionCode

LastInspDate

CoFScore

CoFDate

Active

FK6,I11,I10 Status

StatusDate

ExpireDate

ProjectType

ConfinedSpaceType

CkDate

CkBy

NewUser

NewDate

Gen_SpecInst

LChgDate

LChgUser

Aen_SpecInst

s_ColLineage

I9 s_Generation

U1 s_GUID

s_Lineage

ACCESSMANHOLE

PK,I7 UnitID

I4 Old_UnitID

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

Location

Area

I3 MainID

DateInst

WarrantyDate

BelowGroundDepth

SpecInst

Inspector

Comments

ProjectType

ConfinedSpaceType

C3

Project

Above_Below

MapLoc

MapIndex

I1 CautionCode

CkDate

CkBy

I2 ConditionCode

LastInspDate

CoFScore

CoFDate

Active

I6 Status

NewUser

NewDate

Gen_Comments

LChgUser

Gen_SpecInst

LChgDate

Aen_Comments

StatusDate

ExpireDate

s_ColLineage

I5 s_Generation

U1 s_GUID

s_Lineage

Turbidity

HydrantNodeNumber

FlushStartDateTime

GaveUpOnTurbidity

TestDateTime

Turbidity

EDITS

MatID

Description

Price

Cost

Units

Active

ExpireDate

WOEQUIPLIST

PK,FK2,I5,I4 WoNum

PK,FK1,I3,I1 UnitID

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

WO_Conflict

I1 ConflictRowGuid

WoNum

CompType

ActCde

PrbCde

Project

ProjectType

Area

Priority

SchedStartDate

AssignedTo

RequestDate

Originator

CompletionDate

CallTime

ArrivalTime

CallName

ContactTime

CallPhone

Comments

CompNum

Company

Attention

Address1

Address2

Phone

RevAcct

Aen_Comments

MapX

Gen_Comments

MapLocationX

MapY

s_ColLineage

MapLocationPlacedBy

I2 s_Generation

MapLocationDate

I3 s_GUID

s_Lineage

MapLocationY

SUBMITTAL

I1 IdNum

RecDate

Type

Sentdate

DueDate

RevDate

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

LEAKDATASERVICE

PK,I2 WoNum

LeakType

LeakMaterial

NoServ

TimeOutage

FeetCorrelated

PipeDiam

DetectionMethod

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

LABORGRP

PK LaborGrp

Description

RegRate

OTRate

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

HYDMODEL

PK Model

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

FILEMAPAREA

PK,I2 FileNum

PK,FK1,I1 MapArea

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

CONDITION

PK,I1 ConditionCode

Description

LongDesc

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

WOHYDMTRREQ

PK,I4 WoNum

TakenBy

Contact

Phone

SubName

Use

Size

SetDate

SetTime

SetBy

RemovDate

RemovTime

RemovNote

LocateReq

LocateApp

Direction

HWrenchIssued

HMeterChained

RateExlp

RespExlp

I3 UnitId

DateRem

DateInst

SetRdg

RemRdg

WtrUse

Gal

GalTot

KGalRate

Rental

DailyRate

RenTotal

TripRate

Trips

TripTot

Other

OtherTot

Note

I1 HydUnitID

Aen_Note

Gen_Note

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

VALVE_Conflict

I1 ConflictRowGuid

UnitID

Old_UnitID

ValveType

MainID

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

Location

Area

IsolationValve

ModelNum

Manufacturer

ManufacturerDate

Size

DateInst

WarrantyDate

OperatingExt

OperatingDepth

ValveDepth

SpecInst

Saver

PermaLog

NumTurns

Direction

Inspector

Comments

ConfinedSpaceType

ProjectType

C3

Project

TracerWire

LocStationUnitID

MapLoc

MapIndex

CautionCode

CkDate

CkBy

Active

ConditionCode

LastInspDate

Status

CoFScore

StatusDate

CoFDate

NewUser

NewDate

LChgUser

LChgDate

Aen_Comments

Ben_Comments

Gen_Comments

Gen_SpecInst

Aen_SpecInst

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

VALVE

PK,I10 UnitID

I7 Old_UnitID

FK3,I13 ValveType

I4 MainID

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

Location

Area

IsolationValve

FK2,I5,I12 ModelNum

FK1,I11 Manufacturer

ManufacturerDate

Size

DateInst

WarrantyDate

OperatingExt

OperatingDepth

ValveDepth

SpecInst

Saver

PermaLog

I6 NumTurns

Direction

Inspector

Comments

ConfinedSpaceType

ProjectType

C3

Project

TracerWire

I3 LocStationUnitID

MapLoc

MapIndex

I1 CautionCode

CkDate

CkBy

I2 ConditionCode

LastInspDate

CoFScore

CoFDate

Active

I9 Status

StatusDate

Aen_Comments

NewUser

NewDate

Gen_Comments

LChgUser

Gen_SpecInst

LChgDate

s_ColLineage

I8 s_Generation

U1 s_GUID

s_Lineage

TYPESITE

PK TYPESITE

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

SERVICELINE_Conflict

I1 ConflictRowGuid

ServLineID

ServType

MainID

MatchQty

AlsoServ

Premise

UniqueID

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

Area

PressZone

CurbStopLoc

WarrantyExp

Inspector

DateInst

Diameter

Length

PipeType

Comments

ExistingMeterBox

OutSideSpkrCon

CriticalCde

CriticalContactName

CriticalContactRegHrs

CriticalContactAftHrs

CriticalCheckCmt

ProjectType

ConfinedSpaceType

Source

MapLoc

MapIndex

CautionCode

Active

ConditionCode

LastInspDate

Status

CoFScore

StatusDate

CoFDate

ExpireDate

Provider

CkMp

CkMpDate

CkBy

SewerOnly

Meterno

NewUser

NewDate

LChgUser

LChgDate

Aen_Comments

Gen_Comments

Ben_Comments

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

SERVICELINE

PK,I7 ServLineID

FK3,I8 ServType

I5 MainID

MatchQty

AlsoServ

Premise

I12 UniqueID

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

FK5,I11 TYPESITE

STREETSUFX

APARTNO

Area

PressZone

CurbStopLoc

WarrantyExp

FK2,I4 Inspector

DateInst

Diameter

Length

FK4,I9 PipeType

Comments

ExistingMeterBox

OutSideSpkrCon

FK1,I3 CriticalCde

CriticalContactName

CriticalContactRegHrs

CriticalContactAftHrs

CriticalCheckCmt

ProjectType

ConfinedSpaceType

Source

MapLoc

MapIndex

I1 CautionCode

I2 ConditionCode

LastInspDate

CoFScore

CoFDate

Active

I10 Status

StatusDate

ExpireDate

Provider

CkMp

CkMpDate

CkBy

SewerOnly

Meterno

Aen_Comments

NewUser

Gen_Comments

NewDate

LChgUser

LChgDate

s_ColLineage

I6 s_Generation

U1 s_GUID

s_Lineage

MAPAREA

PK MapArea

Quadrant

Section

Township

Range

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

DEPARTMENT

PK Dept

Domicile

BegBalance

AnnualContr

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

WOVALVELIST_Conflict

I1 ConflictRowGuid

WoNum

UnitID

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

WOMATERIAL_Conflict

I1 ConflictRowGuid

WoNum

MatID

Date

Qty

Price

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

WOLOCLIST

PK,FK2,I5,I4 WoNum

PK,FK1,I3,I1 UnitID

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

WOEMPLOYEE

PK,FK2,I5,I4 WoNum

PK,FK1,I2,I1 EmpID

PK Date

LaborGrp

RegHours

OTHours

RegRate

OTRate

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

VALVEGRP

PK Group

Desc

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

PRBCDE

PK PrbCde

Description

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

MSysAccessXML

PK Id

LValue

U1 ObjectGuid

U2 ObjectName

U2,U1 Property

Value

MAINTRACER_Conflict

I1 ConflictRowGuid

MainID

UnitID

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

HYDTYPE

PK HydType

Description

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

HYDRANT_Conflict

I1 ConflictRowGuid

UnitID

Old_UnitID

HydType

ShutOffV

MainID

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

MainSize

Location

Area

PressZone

SerialNum

ModelNum

Manufacturer

Size

VendorID

DateInst

WarrantyDate

Life

OriginalCost

ReplacementCost

SpecInst

Inspector

Color

Height

ApprovedToFill

C3

Project

MapLoc

MapIndex

CautionCode

Active

ConditionCode

LastInspDate

Status

CoFScore

StatusDate

CoFDate

ExpireDate

ProjectType

ConfinedSpaceType

CkDate

CkBy

NewUser

NewDate

LChgUser

LChgDate

Aen_SpecInst

Ben_SpecInst

Gen_SpecInst

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

EQUIPMENT_Conflict

I1 ConflictRowGuid

UnitID

Description

Type

Location

SerialNum

ModelNum

Manufacturer

Domicile

KeyBoxNum

PurchDate

PurchCost

ChgAmount

Life

PricingDate

AssignedTo

PricingAmount

UsedBy

Year

LicenseNo

Dept

FuelType

Emergency

Unit

AdditionalCostDate

AdditionalCostAmt

AdditionalCosts

Inuse

Status

StatusDate

ExpireDate

NewUser

NewDate

LChgUser

LChgDate

Note

Gen_AdditionalCosts

Aen_AdditionalCosts

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

EMPLOYEE

PK,I1 EmpID

EmpCde

FK1,I2 LaborGrp

FirstName

LastName

RegRate

OTRate

Active

ExpireDate

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

BEAMWIDTH

Width

Fraction

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

Water Mains Age

Age

Length Pct

SumOfLength

Total Length

WOEQUIPMENT

PK,FK1,I4,I3 WoNum

PK,I2 UnitID

PK Date

Hours

Rate

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

tblHydrantTurbidityTests

PK,I1 FlushID

PK TestDateTime

Turbidity

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

SERVTYPE

PK ServType

Description

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

LOCSTATION_Conflict

I1 ConflictRowGuid

UnitID

Old_UnitID

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

BoxMaterial

Location

Measurements

Area

MainID

DateInst

WarrantyDate

Inspector

Comments

Project

ProjectType

ConfinedSpaceType

MapLoc

MapIndex

CautionCode

CkDate

CkBy

Active

ConditionCode

LastInspDate

Status

CoFScore

NewUser

CoFDate

NewDate

LChgUser

LChgDate

StatusDate

ExpireDate

Aen_Comments

Gen_Comments

Gen_Measurements

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

HYDRANT

PK,I12 UnitID

I8 Old_UnitID

FK3,I5 HydType

ShutOffV

I6 MainID

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

MainSize

Location

Area

PressZone

I10 SerialNum

FK2,I7,I4 ModelNum

FK1,I3 Manufacturer

Size

I13 VendorID

DateInst

WarrantyDate

Life

OriginalCost

ReplacementCost

SpecInst

Inspector

Color

Height

ApprovedToFill

C3

Project

MapLoc

MapIndex

I1 CautionCode

I2 ConditionCode

LastInspDate

CoFScore

CoFDate

Active

I11 Status

StatusDate

ExpireDate

ProjectType

ConfinedSpaceType

CkDate

CkBy

Aen_SpecInst

NewUser

NewDate

Gen_SpecInst

LChgUser

LChgDate

s_ColLineage

I9 s_Generation

U1 s_GUID

s_Lineage

HydrantsOn4InchOrSmallerMains

UnitID

MainSize

STREETNO

STREETNAME

Status

LEAKDATAHYDRANT

PK,I2 WoNum

LeakType

LeakMaterial

NoServ

TimeOutage

FeetCorrelated

PipeDiam

DetectionMethod

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

FIRM

I1 FirmNum

FirmName

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

CONFINEDSPACETYPE

PK ConfinedSpaceType

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

WTP_CPs

Location

UnitID

Area

ReadingDate

PSVolts1

PSVolts2

PSVolts3

PSVolts4

PSVolts5

PSVolts6

AnodeCurrent

WOMAINLIST

PK,FK2,I5,I4 WoNum

PK,FK1,I2,I1 MainID

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

WOACCESSLIST

PK,FK2,I4,I5 WoNum

PK,FK1,I3,I1 UnitID

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

VALVETRACER

PK,FK2,I5,I4 ValveUnitID

PK,FK1,I3,I1 TracerUnitID

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

USER_DATA_ENTRY_DEFAULT

PK UserName

Area

DateInst

WarrantyDate

Inspector

Project

MapLoc

MapIndex

ProjectType

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

PROJECT

PK,I1 ProjectNum

Description

ProjectType

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

MAINCONDITION

PK,I1 ConditionCode

Description

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

LEAKDATAMAIN_Conflict

I1 ConflictRowGuid

WoNum

LeakType

LeakMaterial

BeamWidth

DistanceAround

LongWidth

LongLength

HoleDiam

PSI

EstDaysLeaking

NoServ

TimeOutage

FeetCorrelated

PipeDiameter

DetectionMethod

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

INFLATION_FACTOR

InflationFactor

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

CAUTIONCDE

PK,I1 CautionCode

Description

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

tblHydrantChlorineTests

PK,I1 FlushID

PK TestDateTime

Chlorine

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

oldtblPix

PK,I1 ID

I3 WoNum

Attachment

Gen_Attachment

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

MAPLOC

PK MapLoc

LocDesc

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

DEVREV

PK,I4 IdNum

I2 FileNum

Project

Location

I3 FirmNum

Type

Signed

Basin

Note

WMTapComment

WSTapComment

Rating

I1 EngNum

AccptDate

Repay

RepayNote

Irrigation Tap

Aen_Note

Gen_Note

s_ColLineage

I5 s_Generation

U1 s_GUID

s_Lineage

CPSTATBOXMTRL

PK BoxMaterial

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

New

MatID

StkNum

Description

Units

Cost

WOSLLIST

PK,FK1,I4,I3 WoNum

PK,I2 ServLineID

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

SHUNTTYPE

PK ShuntType

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

MAINTYPE

PK MainType

Description

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

LEAKDATAVALVE

PK,I2 WoNum

LeakType

LeakMaterial

NoServ

TimeOutage

FeetCorrelated

PipeDiam

DetectionMethod

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

FUELTYPE

PK FuelType

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

CPDATA

PK,FK1,I2,I1 CPID

PK ReadingDate

PSVolts1

PSVolts2

PSVolts3

PSVolts4

PSVolts5

PSVolts6

AnodeCurrent

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

CONTRACTOR

PK,I1 CompNum

Company

Attention

Address1

Address2

Phone

Note

Active

Gen_Note

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

tblNextNodeNumber

NextNodeNumber

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

MAINMANUF

PK Manufacturer

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

LOCSTATBOXMTRL

PK BoxMaterial

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

INFLATIONRATE

PK InflationRate

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

ACTCDE

PK ActCde

Description

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

WOMAINLIST_Conflict

I1 ConflictRowGuid

WoNum

MainID

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

WOEQUIPMENT_Conflict

I1 ConflictRowGuid

WoNum

UnitID

Date

Hours

Rate

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

WOEMPLOYEE_Conflict

I1 ConflictRowGuid

WoNum

EmpID

Date

LaborGrp

RegHours

OTHours

RegRate

OTRate

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

WOCONTRACT

PK,FK1,I3,I2 WoNum

PK Contractor

PK Date

Hours

Rate

Materials

Labor

Total

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

VALVETYPE

PK ValveType

Description

FK1,I3,I1 Group

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

PROJECTTYPE

PK ProjectType

Description

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

MAIN_Conflict

I1 ConflictRowGuid

MainID

MainType

UniqueID

BLOCKNO

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

MAINDIR

PipeType

PipeDiameter

Location

Area

PressZone

Manufacturer

Length

DateInst

WarrantyDate

Depth

SpecInst

Inspector

CP

C3

Project

MapLoc

MapIndex

CautionCode

ConditionCode

LastInspDate

Active

CoF

CoFScore

CoFDate

Status

StatusDate

ExpireDate

ProjectType

ConfinedSpaceType

CkDate

CkBy

NewUser

NewDate

LChgUser

LChgDate

Gen_SpecInst

Ben_SpecInst

Aen_SpecInst

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

EQUIPTYPE

PK EquipType

DefaultLife

RollingStock

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

CRITCDE

PK CritCde

Description

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

COMPACT

PK Comp

PK,FK1,I1 ActCde

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

qryResidualChlorine

HydrantNodeNumber

Concerns

PRESSZONE

PREM

WOHYDMTRREQ_Conflict

I1 ConflictRowGuid

WoNum

TakenBy

Contact

Phone

SubName

Use

Size

SetDate

SetTime

SetBy

RemovDate

RemovTime

RemovNote

LocateReq

LocateApp

Direction

HWrenchIssued

HMeterChained

RateExlp

RespExlp

UnitId

DateRem

DateInst

SetRdg

RemRdg

WtrUse

Gal

GalTot

KGalRate

Rental

DailyRate

RenTotal

TripRate

Trips

TripTot

Other

OtherTot

Note

HydUnitID

Aen_Note

Gen_Note

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

tblHydrantFlush

PK,I2 FlushID

PK HydrantNodeNumber

PK FlushStartDateTime

I1 CrewID

LooksClearDateTime

StaticPressure

DrainageIssues

Concerns

GaveUpOnTurbidity

GaveUpOnChlorine

FromValveNumber

Dechlorinated

Residual

ResidualAfterDeChlorination

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

SLPIPETYPE

PK PipeType

Description

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

MATERIAL

PK,I1 MatID

Description

Units

Price

Active

ExpireDate

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

MAINVALVE

PK,FK1,I2,I1 MainID

PK,I4 ValveID

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

HOLEDIAM

PK HoleDiam

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

ENGINEER

I1 EngNum

EngName

EngName2

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

Wums

MatID

Description

Units

Price

Active

ExpireDate

WOSLLIST_Conflict

I1 ConflictRowGuid

WoNum

ServLineID

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

tblPix

I1 ID

I3 WoNum

Attachment

Gen_Attachment

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

OPERATINGINSTR

PK,I1 Comp

PK,I2 Id

OperatingInstr

Gen_OperatingInstr

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

LOCSTATION

PK,I7 UnitID

I5 Old_UnitID

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

FK1,I3 BoxMaterial

Location

Measurements

Area

I4 MainID

DateInst

WarrantyDate

Inspector

Comments

Project

ProjectType

ConfinedSpaceType

MapLoc

MapIndex

I1 CautionCode

CkDate

CkBy

I2 ConditionCode

LastInspDate

CoFScore

CoFDate

Active

Status

NewUser

NewDate

Aen_Comments

LChgUser

LChgDate

Gen_Comments

StatusDate

ExpireDate

Gen_Measurements

s_ColLineage

I6 s_Generation

U1 s_GUID

s_Lineage

LEAKDATAMAIN

PK,I2 WoNum

LeakType

LeakMaterial

BeamWidth

DistanceAround

LongWidth

LongLength

HoleDiam

PSI

EstDaysLeaking

NoServ

TimeOutage

FeetCorrelated

PipeDiameter

DetectionMethod

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

INSPECTOR

PK,I1 InspID

FName

LName

CellPhone

HomePhone

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

Query1

PressZone

WumsServLineInvID

VALMANUF

PK Manufacturer

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

MAINPIPETYPE

PK PipeType

Description

LifeExpectancy

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

LONGWIDTH

PK Width

Faction

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

CustomersInPressureZone

PremID

WumsServLineInvID

COMPACTPRBCDE

PK,FK1,I1 Comp

PK,FK1,I1 ActCde

PK PrbCde

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

AREA

PK Area

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

Query2

PressZone

WumsServLineInvID

WOMATERIAL

PK,FK2,I5,I4 WoNum

PK,FK1,I1,I2 MatID

PK Date

Qty

Price

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

WO

PK,I4 WoNum

CompType

ActCde

FK1,I2 PrbCde

Project

ProjectType

Area

Priority

SchedStartDate

AssignedTo

RequestDate

Originator

CompletionDate

CallTime

ContactTime

ArrivalTime

CallName

CallPhone

Comments

I1 CompNum

Company

Attention

Address1

Address2

Aen_Comments

Phone

RevAcct

MapLocationX

MapLocationY

MapLocationPlacedBy

Gen_Comments

MapLocationDate

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

STATUS

PK StatCde

Desc

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

REVACCT

PK RevAcct

Fund

Center

AccountNo

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

Query3

PressZone

WumsServLineInvID

Chlorine

HydrantNodeNumber

FlushStartDateTime

GaveUpOnChlorine

Dechlorinated

TestDateTime

Chlorine

MAINVALVE_Conflict

I1 ConflictRowGuid

MainID

ValveID

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

LOCATE

PK TicketNo

Foreman

County

City

Address

Inters

Type2

Rem

Other

Other1

Other2

Area

GasDate

ElecDate

USWestDate

CableDate

WaterDate

SewerDate

OthDate

OthDate1

OthDate2

GasTime

ElecTime

USWestTime

CableTime

WaterTime

SewerTime

OthTime

OthTime1

OthTime2

Type

Date

PSDate

PSTime

Meet

AmPm

MeetLoc

AMDate

Cancelled

CanDate

Emerg

EmergDate

InterDate

InterTime

Gen_Rem

Gen_Type2

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

HYDMANUF

PK Manufacturer

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

FILEAKA

I1 FileNum

FileName

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

EQUIPMENT

PK,I8 UnitID

Description

FK2,I2 Type

Location

I7 SerialNum

I5 ModelNum

Manufacturer

Domicile

I4 KeyBoxNum

PurchDate

PurchCost

PricingDate

PricingAmount

Life

ChgAmount

AssignedTo

UsedBy

Year

LicenseNo

FK1,I1 Dept

FK3,I3 FuelType

Emergency

Unit

AdditionalCostDate

AdditionalCostAmt

AdditionalCosts

Inuse

Status

StatusDate

ExpireDate

NewUser

NewDate

LChgUser

Gen_AdditionalCosts

s_ColLineage

LChgDate

Note

I6 s_Generation

U1 s_GUID

s_Lineage

DEFAULTVALUE

TripRate

DailyRate

WaterRate

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

CP

PK,I10 UnitID

I5 Old_UnitID

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

FK1,I3 BoxMaterial

Location

Measurements

Area

FK2,I7 ShuntType

I4 MainID

DateInst

WarrantyDate

Inspector

Comments

Project

FK3,I9 TestStationType

ProjectType

ConfinedSpaceType

MapLoc

MapIndex

I1 CautionCode

CkDate

CkBy

I2 ConditionCode

LastInspDate

CoFScore

CoFDate

Active

I8 Status

NewUser

NewDate

Aen_Comments

LChgUser

LChgDate

Gen_Comments

StatusDate

ExpireDate

Gen_Measurements

s_ColLineage

I6 s_Generation

U1 s_GUID

s_Lineage

Water (WUMS) ERD

Water CMMS Sample Screenshot

Water CMMS Sample Screenshot

MDI.MAINT_ALIAS

MDI.MAINT_CAL

MDI.MAINT_CALINSTR

MDI.MAINT_CLASS

MDI.MAINT_DRAWING

MDI.MAINT_EMP

MDI.MAINT_EQTYPE MAINT_EQUIP_COND_DEFINITION

MDI.MAINT_ID

MDI.MAINT_ID_ALIAS

MDI.MAINT_INVTYPE

MDI.MAINT_INVY

MDI.MAINT_PERIOD

MDI.MAINT_PRIORITY

MDI.MAINT_PROBCDE

MDI.MAINT_PROCESS_AREA

MDI.MAINT_ROS

MDI.MAINT_SCHEDTYPE

MDI.MAINT_TASK

MDI.MAINT_TASKID

MDI.MAINT_TASKITEM

MDI.MAINT_VENDOR

MDI.MAINT_WO

MDI.MAINT_WOCONT

MDI.MAINT_WOCONT_HISTORY

MDI.MAINT_WOE

MDI.MAINT_WOE_HISTORY

MDI.MAINT_WOGENMDI.MAINT_WOID

MDI.MAINT_WOID_HISTORY

MDI.MAINT_WOITEM

MDI.MAINT_WOITEM_HISTORY

MDI.MAINT_WOTASK

MDI.MAINT_WOTYPE

MDI.MAINT_WO_CATEGORY

MDI.MAINT_WO_COSTS

MDI.MAINT_WO_EMAIL

MDI.MAINT_WO_HISTORY

MDI.MAINT_WO_STATUS

MDI.MAINT_ZONE

MDI.MDI_DEFAULT_PRINTER

MDI.MDI_STATUS_PROFILE

MAINT_EQUIP_CONDITION

MAINT_EQUIP_CONDITION_COMMENTS

MDI.PRINT_REPORT

MDI.UTILITY_DEPARTMENTS

MDI ER DiagramAuthor: Rick MorfordDate: 07/29/2010

Water Treatment Facility: Tag count: 4511

Work Order count: 19311

Waste Water Treatment Facility:

Tag count: 4169

Work Order count: 27705

Maintenance ID/Tag table column list: "ID" VARCHAR2(15 BYTE),

"DRAWINGNUM" VARCHAR2(10 BYTE),

"PARENTID" VARCHAR2(15 BYTE),

"EQTYPE" VARCHAR2(16 BYTE),

"DESCRIPTION" VARCHAR2(255 BYTE),

"UCASEDESC" VARCHAR2(255 BYTE),

"SYSTEM" VARCHAR2(40 BYTE),

"PHYSLOCATION" VARCHAR2(100 BYTE),

"ZONE" VARCHAR2(4 BYTE),

"DESCRIPTOR" VARCHAR2(255 BYTE),

"POWERSOURCE" VARCHAR2(40 BYTE),

"PLC" VARCHAR2(20 BYTE),

"SERIALNUM" VARCHAR2(255 BYTE),

"MODELNUM" VARCHAR2(255 BYTE),

"MANUFACTURER" VARCHAR2(255 BYTE),

"STARTUPDATE" DATE,

"REFLIBNUM" VARCHAR2(50 BYTE),

"CITYBIDNUM" VARCHAR2(15 BYTE),

"NOTE" VARCHAR2(4000 BYTE),

"CLASS" CHAR(1 BYTE),

"INSERVICE" NUMBER,

"UPDATEDRAWING" NUMBER,

"UPDATEDWGDATE" DATE,

"UPDATEDWGUSER" VARCHAR2(50 BYTE),

"UPDATEDATA" NUMBER,

"UPDATEDATADATE" DATE,

"UPDATEDATAUSER" VARCHAR2(50 BYTE),

"MISC01" VARCHAR2(50 BYTE),

"MISC02" VARCHAR2(50 BYTE),

"MISC03" VARCHAR2(50 BYTE),

"MISC04" VARCHAR2(50 BYTE),

"MISC05" VARCHAR2(50 BYTE),

"MISC06" VARCHAR2(50 BYTE),

"MISC07" VARCHAR2(50 BYTE),

"MISC08" VARCHAR2(50 BYTE),

"MISC09" VARCHAR2(50 BYTE),

"MISC10" VARCHAR2(50 BYTE),

Plant CMMS (MDI) Fields

"MISC11" VARCHAR2(50 BYTE),

"MISC12" VARCHAR2(50 BYTE),

"MISC13" VARCHAR2(50 BYTE),

"MISC14" VARCHAR2(50 BYTE),

"MISC15" VARCHAR2(255 BYTE),

"MISC16" VARCHAR2(50 BYTE),

"MISC17" VARCHAR2(50 BYTE),

"MISC18" VARCHAR2(50 BYTE),

"MISC19" VARCHAR2(50 BYTE),

"MISC20" VARCHAR2(50 BYTE),

"MISC21" VARCHAR2(50 BYTE),

"MISC22" VARCHAR2(50 BYTE),

"MISC23" VARCHAR2(50 BYTE),

"MISC24" VARCHAR2(640 BYTE),

"MISC25" VARCHAR2(640 BYTE),

"MISC26" VARCHAR2(640 BYTE),

"MISC27" VARCHAR2(50 BYTE),

"MISC28" VARCHAR2(50 BYTE),

"MISC29" VARCHAR2(50 BYTE),

"MISC30" VARCHAR2(50 BYTE),

"MISC31" VARCHAR2(50 BYTE),

"MISC32" VARCHAR2(80 BYTE),

"MISC33" VARCHAR2(50 BYTE),

"MISC34" DATE,

"MISC35" DATE,

"MISC36" NUMBER,

"MISC37" NUMBER,

"UPDATEDRAWING_YES_NO" VARCHAR2(3 BYTE),

"UPDATEDATA_YES_NO" VARCHAR2(3 BYTE),

"DEPTNO" NUMBER,

"PROCESS_AREA" VARCHAR2(40 BYTE),

"AMPS" VARCHAR2(80 BYTE),

"GEAR_RATIO" VARCHAR2(10 BYTE),

"REGISTER_NUM" VARCHAR2(6 BYTE),

"GPM" VARCHAR2(20 BYTE),

"PO_NUM" VARCHAR2(50 BYTE),

"MOTOR_STARTUPDATE" DATE,

"HORSEPOWER" VARCHAR2(50 BYTE),

"VOLTAGE" VARCHAR2(50 BYTE),

"RPM" VARCHAR2(50 BYTE),

"MOTOR_MANUF" VARCHAR2(255 BYTE),

"MOTOR_SERIALNUM" VARCHAR2(255 BYTE),

"MOTOR_PONUM" VARCHAR2(50 BYTE),

"MOTOR_MODELNUM" VARCHAR2(255 BYTE),

"MCC_NUM" VARCHAR2(50 BYTE),

"ROOM_LOCATION" VARCHAR2(50 BYTE),

Plant CMMS (MDI) Fields

"FACILITY" VARCHAR2(50 BYTE),

"PIPE_SIZE" VARCHAR2(50 BYTE),

"INSTALLDATE" DATE,

"COST" NUMBER,

"MATERIAL" VARCHAR2(50 BYTE),

"CONDITION" VARCHAR2(50 BYTE),

"ELEVATION" VARCHAR2(50 BYTE),

"NORTH" VARCHAR2(50 BYTE),

"EAST" VARCHAR2(50 BYTE),

"LATITUDE" VARCHAR2(50 BYTE),

"LONGITUDE" VARCHAR2(50 BYTE),

"DRAWING" VARCHAR2(50 BYTE)

Maintenance Work Order table column list: "WONUM" NUMBER,

"TASKNUM" NUMBER,

"TASKDESC" VARCHAR2(4000 BYTE),

"WOTYPE" VARCHAR2(2 BYTE),

"SCHEDSTARTDATE" DATE,

"SCHEDFINISHDATE" DATE,

"ASSIGNEDTO" VARCHAR2(40 BYTE),

"PRIORITY" NUMBER,

"PROBCDE" VARCHAR2(5 BYTE),

"STATUS" NUMBER NOT NULL ENABLE,

"STATUSDATE" DATE,

"CLOSEDCAT" VARCHAR2(3 BYTE),

"REQSTAT" NUMBER,

"AUTH1" VARCHAR2(50 BYTE),

"AUTH2" VARCHAR2(50 BYTE),

"PROJECT" VARCHAR2(15 BYTE),

"REQUESTDATE" DATE,

"ORIGINATOR" VARCHAR2(40 BYTE),

"ESTHRS" NUMBER,

"ESTMAT" NUMBER,

"LOGINID" VARCHAR2(50 BYTE),

"PRINTED" NUMBER,

"NOTE" VARCHAR2(4000 BYTE),

"LASTUSER" VARCHAR2(50 BYTE),

"LASTUPDATE" DATE,

"DEPTNO" NUMBER,

Plant CMMS (MDI) Fields

09/20/2011 11:45:19 AMDate Printed:1Page:

62511WO #:

9925Task#: Clean cabinet inside and out

MechanicalWork Group: Preventive (Facility)

09/01/2011Request Date:

09/15/2011 NAZone:

3

Reason:

Supervisor:

3_RES respirator inspection

Clean cabinet inside and out

Inspect harness,cylinder,and regulator

Do flow test

Check cylinder pressure fill if below 3500 on 4500

Report any problem to your supervisor.

Bring broken or worn parts to Scott for repairs and or replacement.

Note

Instructions

Comments:

Cost InformationDate Emp Code Reg Hrs Ot Hrs Material Code Qty Used

Date Completed:

ID #: Description: Physical Location:Equipment Information

Scheduled Start: Priority:

Plant CMMS (MDI) Sample Work Order Form

Completed Work Orders ReportBetween 06/01/2009 And 09/17/2009

1Page: of

Total Report Hours: 641.6 89Total Report Work Orders:

10

46492

54038

54251

54117

53914

53915

53869

53625

53763

47710

WO #:

WO #:

WO #:

WO #:

WO #:

WO #:

WO #:

WO #:

WO #:

WO #:

6294Task #:

Task #:

Task #:

Task #:

Task #:

Task #:

Task #:

Task #:

Task #:

Task #:

09/14/2009

09/14/2009

09/10/2009

09/08/2009

09/01/2009

09/01/2009

08/31/2009

08/27/2009

08/25/2009

08/24/2009

Completion Date:

Completion Date:

Completion Date:

Completion Date:

Completion Date:

Completion Date:

Completion Date:

Completion Date:

Completion Date:

Completion Date:

Instr & Electrical

Instr & Electrical

Instr & Electrical

Instr & Electrical

Instr & Electrical

Instr & Electrical

Instr & Electrical

Instr & Electrical

Instr & Electrical

Instr & Electrical

Work Grp:

Work Grp:

Work Grp:

Work Grp:

Work Grp:

Work Grp:

Work Grp:

Work Grp:

Work Grp:

Work Grp:

Safety

Process (tag < ???999)

Calibration

Process (tag < ???999)

Process (tag < ???999)

Process (tag < ???999)

Process (tag < ???999)

Plant Projects, Security

Process (tag < ???999)

Facility (tag > ???999)

Reason:

Reason:

Reason:

Reason:

Reason:

Reason:

Reason:

Reason:

Reason:

Reason:

Have Poudre fire authority test their Opticom front gate interface

Flow meter starts off reading at full flow, but then drops off to the point that

the filter goes into automatic backwash. This occurred after only two hours in

this case.

Ph meter is reading about 0.26 units too high. Instr reading 8.12 , lab result

7.82, later second grab sample: Instr reading 8.12, lab result 7.89.

Reading spikes up multiple times per day, causing pH and alk control problems.

Instr reading low. Instr reading 0.44 mg/l, lab resul was 1.03 mg/l.

Inst reading high. Instr reading was 7.02, lab results were 6.67.

Filter #7 is not coming up to the full flow set point. In this case it should have

came up to 3.273 MGD, but only made it to 2.110 MGD. Got filter 607 effluent flow

low alarm. This was the second time this occurred.

New unit is being installed. Need to run 480 Volt power to it. Unit pulls 4.5

ampns at 480 volt.

Instr reading high. Instr reading 1.03 NTU, lab value 0.54 NTU.

Outlet cover on outside outlet, westside of polymer room, near corner of building

will not close. Outlet is not weatherproof in current state.

Description:

Description:

Description:

Description:

Description:

Description:

Description:

Description:

Description:

Description:

Hours:

Hours:

Hours:

Hours:

Hours:

Hours:

Hours:

Hours:

Hours:

Hours:

SGO1001

F613

H901

A702

R731

H531

F607

ADU111

N311

WS_150

Tag #:

Tag #:

Tag #:

Tag #:

Tag #:

Tag #:

Tag #:

Tag #:

Tag #:

Tag #:

1.0

2.0

1.0

2.0

2.5

1.0

2.0

31.0

0.1

1.0

Tested this with Dave Lehman

Adjusted limits

AF 8.10, AL 7.83

Replaced sample valve and unit seems to be performing better.

Polished membrane, calibrated twice. Instrument reading 1.06, work complete.

Calibrated, instrument reading 6.75. Work complete.

Drained filter down and removed flow tube, cleaned out pressure lines to transmitte

ordered parts 8-20-09 installed conduit and hooked up power. will hook up unit when

As per our QA/QC procedure, this will be addressed during the normal frequency cali

outlet cover was stuck, freed up cover

Note:

Note:

Note:

Note:

Note:

Note:

Note:

Note:

Note:

Note:

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Select one of the following responses:

OOBCON MODCUSTPRTFRNA

WM1 Manage the routing, escalation and approval of work requests and work ordersThe system must be able to electronically route work orders to the appropriate person(s) for approval. The system must also have the ability to escalate a WO based upon pre-determined parameters.

WM2Enable user classification of work orders (such as proactive and reactive- PM and CM)

The system must have the ability to differentiate between Proactive and Reactive work orders

WM3 Associate work orders with an asset, facility or asset componentIn the lab, many assets have multiple parts. The system must be able to assign work orders to a specific part as well as the asset, and asset parent (facility)

WM4Manage a work order that relates to a group of assets, location or function (e.g. valve exercising)

allow one work order to apply to many identical activities. Valve exercising or hydrant flushing are examples where you don’t want to create a WO for each hydrant that needs to be flushed. The system must allow the one WO to cover all these identical activities.

WM5Include/Manage template work orders (that have work and safety steps, inspection checklists and standard operating procedures)

To more efficiently perform the work order, include the steps, safety precautions, and inspection checklists to have all essential information listed on the WO.

WM6 Provide the ability to have parent and child work orders (associate work orders)If a person is out in the field to perform a work order and notices an issue with the same of another asset, they need to be able to create a work order and tie it to the original.

WM7Provide high visibility (alert) safety notifications - both asset/location/work order based

For a situation such as confined space, or high voltage, the work order needs to have a highly visible alert to let the field technician know what they are facing while performing the WO.

WM8Manage work permits (such as confined space and hot work) Incl.Tailboard sheets.

The system must be able to link permits to a work order to assure the proper permit is in place to allow the work to be performed.

WM9Manage material handling safety requirements (e.g. material safety data sheets (MSDS)

Associate the proper MSDS with the assets to give the technician the proper knowledge in handling whatever might arise.

WM10 Manage reactive maintenance work orders and related asset failure informationAllow the user to view reactive maintenance work orders and see which assets the reactive work orders are against. The goal is to see which assets cause the most reactive work orders and cost the most money to maintain.

WM11 Ability to associate documents & images to work orders & work order templatesThe documents don’t need to reside in the CMMS, but the work order needs to have specific documents and images associated.

WM12 Avoid duplicate work order numbers (offline)When the system is run offline (typically by the field crew) and a WO is entered, the WO numbers must remain unique.

WM13Allow for information to be added to a "closed" work order in the case where the work in not all done at once (road repair not done until spring) Add as script

WM14Dropdown lists must be dynamic - constrain the options to only those applicable - the first choice limits the second

This is an interface component where only valid dropdown choices are available to the user. The typical example of this is if you choose a state, the next dropdown list shows only the cities in that state.

Core Functionality

Work Management

Proposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software, or special hardware items noted must be included under the separate Pricing submittal, unless otherwise specified. Proposers must clearly indicate one (1) of the listed responses to each requirement and provide comment to describe approach. Also indicate whether fulfillment of the requirement is included in the Cost Proposal.

For each requirement answer: Is the System Require ment supported by the EAM System?

Fully provided Out of the BoxProvided through ConfigurationProvided through a technical modification of the software product baselineProvided through a technical modification of the software as a customization for the clientThird party software requiredProvided through a reporting toolProvided through a future releaseNot available

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Core FunctionalityProposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software, WM15 Ability to query work by area and function

In the plant we heard that often times work is divided into area or function. The system must contain the proper metadata to allow all work orders in a certain area or function to be filtered out.

WM16 Associate a Bill of Materials to the WOThe system must have the ability to show a list of all materials needed to perform the work and the cost of each part

WM17Track water quality complaints - would tie to access Fort Collins. Service request would be entered and may become a work request/work order

The system must have the ability to convert a service request into a work order through an automated workflow

WM18Mapping that tracks real time location - GPS in trucks (NOT for tracking truck location or logging)

The mapping system must show the current location of the truck on the map and as the person drives the truck, they can always see on the map where they are.

WM19 GPS for tracking vehicle locationThe ability for the vehicle location, speed, and other key components to be tracked remotely.

WM20 Send automatic alerts for assigned and overdue work - for certain types of workThe system needs to be able to send alerts when certain types of work is not done within the pre-determined time period.

WM21 Executives and managers can sign up for alerts on certain critical assets

If there is a certain customer or asset that is very key to the organization and an executive would like to be notified of any disruption in service or asset malfunction, the system must allow the executive to set up and alert where an email or txt message is sent upon the alert being triggered.

WM22 allow individuals to set notification preferencesAllow users to decide if alerts will be sent upon occurrence, once a day, once a week, once a month, etc… this is to ensure that people are not bombarded with unwanted emails thus reducing their effectiveness.

WM23 Manage work orders against the same asset - determine if they are duplicateWhen a work order is assigned against an asset, the system must be able to pull up all WOs against the asset to allow the user to determine if the WO is a duplicate.

WM24 Comment (Text) fields must be searchable The system must full text index all fields in the system and allow them to be searchable

WM25 Quickly find and view last WO for an assetThe system must allow for quick discovery and display of the last WO against an asset. The reason is to allow an operator to quickly see the last time work was performed.

WM26Allow a user to easily create and complete a work order AFTER the work is completed

If a person is out in the field to perform a work order and notices an issue with the same of another asset, they need to be able to create a work order and tie it to the original. They also must be able to enter the WO and since it's already complete, they must be able to close it without routing the WO through the approval chain.

WM27 Ability to find an asset in the CMMS system with a URL The ability to get to an asset with a URL would help in integration of disparate systems

WM28 Ability to automatically rotate PMs amongst staffIn cases where preventative maintenance work is constantly rotated to give all employees cross training, the system must have the ability to perform the work rotation automatically

WM29 Ability to assign and re-assign work ordersIf a WO has been assigned, but the assignment must be changed, the system must all this to happen

WM30Ability to read/write/edit and asset and a WO with the computer in a disconnected mode (offline usage of the system)

The FCU field crews do not have connectivity, but they require use of the CMMS in the field. The system must be able to operate in the field in an offline mode while still allowing read/write/edit capabilities.

WM31 Must store a capital project number on a WOMany work orders are tied to capital work. System must have the ability to store the capital project number on the WO

WM32When the work order is created, include the ability to capture required data for the asset

Brad's "flushing" example - collecting turbidity values every 15 minutes.

WM33 Creation of a work order from an emailWM34 Creation of a work order from another system E.G. Using web services

GIS

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Core FunctionalityProposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software, GIS1 Ability to view ESRI powered GIS maps within the CMMS

The CMMS must have an integration mechanism such that the ESRI GIS maps can be viewed from within the CMMS allowing users to interact with the maps.

GIS2 Ability to search for an asset from the map interfaceAbility to search for an asset or location from the map interface. "Fuzzy" search is important.

GIS3 Ability to zoom, pan and center the map at a specific location

GIS4 Ability to perform electric and water line tracing from the CMMS mapping interface E.G. Showing customers affected by outage, associating customers to a work order.

GIS5 Offline map viewingGIS6 Offline map editingGIS7 Offline map tracingGIS8 Ability to view asset information from the map interfaceGIS9 Ability to view work orders from the map interface

GIS10 Ability to edit spatial information from the map interfaceGIS11 Ability to edit asset information from the map interface Using Role-Based Permissions (not all users can edit)GIS12 Ability to "redline" the mapGIS13 Supports Offline Maps on Mobile DevicesGIS14 Ability to quickly turn on and off many background layersGIS15 Ability to quickly turn on and off the various Utility layers

GIS16Ability to select a standard “theme” of layers commonly used by Electric, Water, etc.

GIS17 Ability to search for an asset on the map by street intersections:GIS18 Ability to search for an asset on the map by addressGIS19 Identify Electric circuit numberGIS20 Ability to view multiple types of information related to an asset from the map e.g. CCTV, WO, Work history, asset attributesGIS21 Ability to show thematic maps based upon asset information E.G. By Asset condition, material, criticalityGIS22 Ability to show thematic maps based upon work orders E.G. By Work Type, Crew, failure modeGIS23 Measure linear distancesGIS24 Measure areas of a user entered polygon.GIS25 Ability to print a map with assets/work orders indicated

GIS26Ability to keep maps on field devices up to date taking into consideration various schedules of field workers.

PM1 Manage labor groups and technicians and their availability (Resource level tasks) Help to resource balance work loads

PM2 Manage the recording of technician labor hours Allow for hours to be recorded against work ordersPM3 Manage craft / certification requirements per work type "Annual demonstration of capabilities"

PM4 CMMS has access to accurate labor ratesWhether they are actual or labor rate "bands", there needs to labor rates in order to support asset lifecycle cost tracking.

PM5 DOT License Tracking (expiration dates) for operators Added by L&P Field

PM6Training and certification management (CPR & First Aid, trench safety, confined space, EPA, FEMA, etc.)

Added by L&P Field

PM7 Apprentice hours / skills tracking Added by L&P Field

PMM1 Automatically create proactive maintenance work orders (Requests) Automatically create a PM based upon a pre-established schedule

Personnel Management

PM Management

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Core FunctionalityProposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software,

PMM2Manage proactive asset maintenance work schedules based on usage, condition and calendar

Allow PM work orders to be created based on multiple criteria. Many times PMs are established solely on a calendar schedule, however the system must allow for PM tasks to be established based upon the asset's condition or on amount of usage (running cycles or whatever other metric is appropriate)

PMM3Ability to mass update proactive maintenance work schedules based on a selected group of assets

If there are multiple PM work orders that are accomplished as a group, allow the system to close them out and a group and allocate cost equally across each asset.

PMM4 Route creation and maintenance (order and sequence)The system shall advise of the most efficient route to travel in accomplishing the PM work orders.

PMM5 Manually create proactive maintenance work orders (Requests) Allow the user to manually create PMs

PMM6 Allocate a block of time against a group of similar assets - based on a PMThe system should be able to take the time required to perform maintenance against a block of assets and equally distribute that time across the assets.

PMM7 Ability to print out a map of the route. The computer generated route should be available to print in a readable format.

AM1Manage the configuration information related to the City’s planned, installed and de-commissioned assets (ownership, management responsibility, etc.) (Simplify)

Storm water and fiber - commercial electric service

AM2 Manage asset hierarchy and locations The assets in the system must be a part of a customizable hierarchy

AM3Manage assets and asset attributes including criticality (make sure you can add custom attributes)

The system must have the ability to capture and store key asset attributes such as criticality and then use those attributes in determining the PM work orders

AM4 Manage asset placement history within locationsFor assets that are not in a fixed place, need to track the history of where and when it was used in other locations

AM5 Monitor asset condition and usageRegularly examine asset to determine condition. System must be able to retain the condition and usage values

AM6 Manage asset failure modes When an asset fails, the reason (failure mode) must be captured

AM7 Manage work safety requirements per assetIf an asset has specific safety requirements, they must be captured and recorded against the asset.

AM9 Ability to associate documents & images to assets and asset groupsThe system should not be required to store documents and images in the system, but should be able to associate documents and images to an asset and class of asset

AM10 Warranty TrackingFor any and all assets with a warrantee, the warrantee dates much be recorded and the expiration date managed.

AM11 Manage assets not owned by utilityCertain assets (Fiber is a good example) are not owned by the utility, but are maintained by the utility. Proper management of these assets is important

AM12Need to include outside entities in the work order system to support work orders against FCU assets

There are occasions where outside firms are brought in to perform work on FCU assets. An example is roof work on the water plant.

AM13 Manage work performed by non-FCU City staffthere are occasions where city staff (non-FCU) is brought in to perform work on FCU assets. This work must be managed by the system

AM14 Track Reliability At the asset level, reliability must be tracked within the system

AM15 Track AvailabilityAt the asset level, availability (% of the time the asset is available for use) must be tracked within the system

AM16Must be able to handle replacement of a section of a pipe/asset - retain history and deal with condition scoring

If a section of pipe is replaced, the one asset has now become 2 or 3 separate assets. The details of all two/three assets must now be tracked.

AM17 Caution code - if the maintenance has a caution message, alert the user

AM18Can associate an asset with multiple physical addresses - using a connectivity tracing mechanism

AM19Critical services - flag if the asset supplies a critical service such as a hospital, medical equip. etc.

designates services that must always be online

AM20Project when assets will need to be replaced - automatically depreciate the asset and account for inflation in the predicting the future replacement cost

Dwight's example of tracking his trucks on a sheet that predicts when the truck will need to be replaced.

Asset Management

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Core FunctionalityProposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software,

AM21 Set asset condition to "assumed" or "verified" depending upon the situation

When putting a scoring system in place, some asset will have their condition assumed based upon a subset of inspections. As those asset are specifically examined, the condition will be changed from assumed to verified. The system must have this capability

AM22 Asset Work History All history on an asset must be recorded and available for query

AM23 RFID (Radio Frequency Identifier) or other tagging for assets The inventory and laboratory systems need a method for tracking inventory whether chemicals or other materials. The CMMS must be able to incorporate the use of tracking mechanisms

AM24 Maintenance Contract TrackingThe system should have the capability of linking maintenance contracts to specified assets.

AM25 Track Asset PriorityAsset priority is a calculated value taking into consideration asset condition and asset criticality. The system should calculate this value and store it for capital investment planning use.

AM26 Add a placeholder for a new asset in the systeme.g. valve was located, but is not in the system. Add a placeholder to be completed later

PUR1 Management of purchase requisitions

PUR2Pull purchase order records from JDE and import into CMMS - Pull PO#, amount, etc.

PUR3 Integrate with JDE to obtain up to date blanket purchase order balancesPUR4 Integrate with JDE to obtain vendor recordsPUR5 Integrate with JDE to obtain invoice records

PUR6Associate purchase requisitions, purchase orders and service agreements with work orders

PUR7 The routing and approval of purchase requisitions

IM1 Manage storerooms and inventory The CMMS should have an inventory module

IM2 Manage materials re-ordering triggersThe CMMS should be able to automatically create a materials re-order list based upon an inventory threshold being reached.

IM3Define material requirements within work orders and automatically debit inventory when issued or when WOs is closed

The inventory module should be linked to work orders where a work order will automatically debit the materials inventory database.

IM4Manage material item master (official list of material items and their manufacturer, model and specifications)

The inventory module should hold product specifications and not rely on manufacturer's part numbers

IM5 Manage material issues, receipts and transfers including MSDS The inventory module should use MSDS to suggest proper handling of materials

IM6 Scanning or bar coding abilityThe inventory module would need to incorporate scanning or bar coding for easy inventory tracking

IM7 Hold photo of each part type in the warehouseEach part type held in inventory must have an image of the part linked to the inventory system for ease of part identification

IM8 Hold list of associated parts

IM9Manage cable on a per reel level - can see how much is remaining on each reel - weight per unit length and the tare weight of a reel - also by length (using the sequential footage markers - both directions)

Reels of cable are stored in inventory and lengths of cable are used. It is important that the amount of material remaining on the reel be managed.

IM10Vendor list and specification - can update the specs so the part description is not vendor dependent - e.g. per Fort Collins spec 369100

The inventory module should hold product specifications and not rely on manufacturer's part numbers

IM11 Track per year costs on repairs

IM12 Track repairs on serialized assets in the warehouseSome serialized assets are "loaned" assets in that they go to the field and then return. These assets although part of the warehouse, must be tracked

Inventory Management

Purchasing Management

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Core FunctionalityProposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software, IM13

View up to date inventory levels including inventory reserved by work orders but not picked up yet

The inventory levels must be real time and on-line for viewing by users

IM14 Ability to mark materials as hazardous

IM15Automatically update price db and track price history when a new price is entered on a PO

Keeps the most current price in the master list.

IM16 Automatic creation of a materials re-order listBased upon pre-established inventory thresholds, when an inventory threshold is reached, create a purchase list.

IM17 Automatically update quantities when the ordered materials arrivesWhen the order arrives, the system should have a means of updating quantities whether it be from scanning the invoice or another method, but the inventory should not have to be entered manually.

IM18Flexibility around distribution inventory accounting methods- e.g. First In First Out (FIFO), LIFO, specific identification, and Weighted Average unit cost calculation.

Sometimes the FIFO method is best, but not all times. The system must allow certain material types to specify a specific distribution approach.

IM19Ability to handle long lead items - set a time period for receiving new inventory and a typical usage rate

The system should be able to handle long lead items such that it informs the user of the need to order those items where there will be no shortage.

IM20 Remote (Field Staff) order ability Remote staff must be able to place an order through the systemIM21 Support inventory expiration dates Managing the expiration of materialsIM22 Notification that inventory levels are insufficient for WO requirements Ability for the system to compare WO needs against available materials

IM23 Ability to track multiple locations for inventoryInventory will exist at the warehouse as well as at the plants. The system needs to track inventory at all locations in a consolidated view.

IM24 Inventory counting cycles derived from unit cost and volume classifications Added by L&P Field

IM25Return for credit processing against original work orders (particularly important for transformers and unused portions of cable reels)

Added by L&P Field

IM26Post-transaction validation of issue documents against work order requirements

Added by L&P Field

IM27Accounting of shipping and USPS postage expenditures against unique work orders or account codes

Added by L&P Field

EM1Manage special tools/equipment including reservations, checkout, condition and returns

EM2Manage special tools/equipment inspection schedules (Fall protection equipment, AEDs, hotsticks, meters, rubber gloves, etc.)

EM3 Help determine costs to bill for rolling stock Use industry standard rates for rolling stockEM4 Track dates when equipment status changedEM5 Collect and report historical equipment calibration Allows the organization to see trending and determine if an asset is degrading.EM6 Show historical equipment calibration specs as a graph Tracking calibration specs helps to identify equipment that is failingEM7 Track equipment location

SR1 Report the status of customer service request and related work ordersSR2 The creation, routing and approval of service requests To replace trouble call systemSR3 Display copies of customer service requests imported from CISSR4 Creation of a service request from an email

Equipment Management

Service Requests

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Core FunctionalityProposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software, SR5 Creation of a service request from another system E.G. Using web services

FDM1 View work order & asset on hand-heldFDM2 Collect asset information on hand-heldFDM3 Create new service request on hand-heldFDM4 Complete work order on hand-heldFDM5 Dock or sync hand-held at day's start/endFDM6 Wireless connection to live CMMS

FM1 Vehicle Maintenance Tracking to store a subset of the full data set. Only the maintenance that is NOT done by fleet

FM2 Vehicle Location Tracking

REP1 Report full lifecycle costs per assetREP2 Ad-Hoc Reporting CapabilitiesREP3 Pre-Defined Reporting CapabilitiesREP4 KPI / Dashboard ReportingREP5 Export to ExcelREP6 Gantt chart or other visual view of all PMs

Vendor Scoring OptionsOOBCON MODCUSTPRTFRN/A

Reporting

Field Data Management

Fleet Management

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Select one of the following responses:

OOBCON MODCUSTPRTFRNA

StrategicS1 Vendor Industry PositionS2 Vendor StabilityS3 Limit Usage of 3rd Party Applications (for core functionality)S4 Strength of Product RoadmapS5 MIS Strategic FitS6 Alignment with the Utility's Training Program Accredited training program to count towards continuing education. (CEUs)S7 Culture Team (CVA)S8 Triple Bottom Line - Criteria for all Large Purchases and Consulting HiresS9 Workforce Team - Knowledge Capture - Succession Planning

S10 Utility Sustainability

S11 Performance Excellence - ICMA involvementCity Manager project to help the city stand out amongst its peers. (ICMA - International City Managers Association)

S12 Successful Deployment at a Similar UtilitySimilar Utility is 100,000 customers covering both wet and dry distribution/network utilities.

S13 Support for ISO 14,001 complianceS14 Compliance with National Institute of Standards and Technology NIST800-53 S15 PMP Certified Project ManagersS16 Ease of Interface with Vendor Ability to easily interface with the vendor in making changes.

RiskR1 Risk of Technical Failure Are we comfortable with the technology they are built on?R2 Risk of Data Failure Can you show us where you've done this before, your import engine,etc.R3 Risk of Business Failure Usability of the system - user interaction and buy in on the system.R4 Nature and Magnitude of Change for Core UsersR5 Robust Training Methodology and Materials Online training, CBTs, Classroom, Local, etc.

Proposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software, or special hardware items noted must be included under the separate Pricing submittal, unless otherwise specified. Proposers must clearly indicate one (1) of the listed responses to each requirement and provide comment to describe approach. Also indicate whether fulfillment of the requirement is included in the Cost Proposal.

Strategic, Financial & Risk-Based Requirements

Provided through a reporting toolProvided through a future releaseNot available

For each requirement answer: Is the System Require ment supported by the EAM System?

Fully provided Out of the BoxProvided through ConfigurationProvided through a technical modification of the software product baselineProvided through a technical modification of the software as a customization for the clientThird party software required

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Proposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional

Strategic, Financial & Risk-Based Requirements

FinancialF1 License and Annual Support CostsF2 Hardware CostsF3 Implementation CostsF4 Licensing Includes Test & Training Environments

# Question Definition

1 Provide list of web services that you expose2 Which mapping solutions does your system integrate with?3 What IT industry standards do you adhere to?

4Which IT industry standards boards do you actively participate in and influence?

5 Hardware Sizing Recommendation, include optimal user load for recommended hardware. need to provide numbers in RFP (community, asset estimates, number of users)6 Provide License pricing model look into potential user numbers7 Does your solution come with a built in mapping capability? E.G. Built on ESRI

8 Does your appliction provide mapping for electric,water,stormwater,wastewater,fiber,backflow?

9Provide a list of web service APIs and adapters that are included with your product? List additional costs for adapters if applicable.

10Provide typical db and application server sizing for a 150,000 customer utility that includes water, stormwater, wastewater and electric utilities.

11 Network Bandwidth Requirements to retain optimal performance What is the recommended network speed (Mb/sec)for the application to perform well?12 Average page render time in a real world scenario In Seconds

13 What is the technology/platform/architecture used? MIS Ability to Support (Alignment with City of Fort Collins IT - Infrastructure and Apps)

14 Active User Community Provide references (Websites, regional user groups, etc)15 Active Developer Community Provide references (Websites, regional user groups, etc)16 Provide Examples of your Out-Of-The-Box Reports for Work Orders and Assets17 Describe your typical UAT process.

18 Describe your cut-over / go-live process. (Ideally we want some kind of 60-day ‘stabilization’ period before go-live is considered complete.)

1920212223

Qualifications for Written Statements

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Select one of the following responses:

OOBCON MODCUSTPRTFRNA

Compatibility & Compliance CC1 Web-Browser Support - IE8

CC2 Web-Browser Support - IE7 CC3 Virtualized Server Support CC4 DB Support - Oracle (11gR1, R2) CC5 Support Oracle 10 and11g app servers If J2EE container required CC6 Windows Server 2008 R2 OS Support

CC7 Tablet Device Compatibility -- Windows OS CMMS must be able to run in a fully functional mode on tabletCC8 Droid OS Compatibility CMMS must be able to run in a fully functional mode on tablet or phoneCC9 iOS Compatibility CMMS must be able to run in a fully functional mode on tablet or phone

CC10 Active Directory Integration CC11 Single Sign-On / Pass-Through Authentication Support 90 day password rotation - 25 password cache - (If not using AD) CC12 Support Crystal Reporting

CC13 FCU Password Policy Compliance 8+ characters, alpha +numeric required if not using ADCC14 Standard Web Image Format Support e.g. .PNG, .JPG, .GIFCC15 Support Database ClusteringCC16 Support SAP (Xcelcius) Dashboard DesignCC17 Support Internet Protocol v6CC18 Windows XP CompatibleCC19 Windows 7 CompatibleCC20 Must be able to Operate over a 3G ConnectionCC21 Provide Flexible Integration Framework via Web Services For integration and data transaction purposesCC22 Support Bar Code Standards

CC23Allow Direct Database Read-Only Access (odbc/jdbc) for Reporting Purposes (Crystal Reports)

CC24 Supports SQL Server 2005 and 2008CC25 Application Supports Data Guard or Similar for Database Disaster Recovery

Integrations

I1 Integrate with Enterprise Service Bus (Next Axiom)Assumption is that ESB would provide integration with all below applications if they are connected to ESB

I2 Integrate with ESRI GIS ArcGIS/ArcGIS Server v9.3.1 and v10I3 Integrate with Utility CAD File Systems Including Object Data Identifier UVIEW in house mapping based upon AutoCAD/Bentley redlineI4 Integrate with CIS (Ventyx Customer Suite v4.1 CIS)

Proposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software, or special hardware items noted must be included under the separate Pricing submittal, unless otherwise specified. Proposers must clearly indicate one (1) of the listed responses to each requirement and provide comment to describe approach. Also indicate whether fulfillment of the requirement is included in the Cost Proposal.

Technical Requirements

Provided through a reporting toolProvided through a future releaseNot available

For each requirement answer: Is the System Require ment supported by the EAM System?

Fully provided Out of the BoxProvided through ConfigurationProvided through a technical modification of the software product baselineProvided through a technical modification of the software as a customization for the clientThird party software required

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Proposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software,

Technical Requirements

I5 Integrate with JDE v9I6 Integrate with DMS (Sire v5.2)

I7Secure information transfer with Water SCADA (Genesis 64) - No Connectivity Between Water SCADA and CMMS

Note: SCADA on separate network

I8 Integrate with Public Works Asset Management System (CityWorks) For assets which cross division boundaries (Fleet?)I9 Integrate with MS Access 2002 Required to pull information from homegrown "WetLIMDS" system.

I10 Integrate with Corporate Email System (MS Outlook Exchange 2010) MS Outlook will be brought in-house fall 2011.I11 Integrate with Accela v 7.1 (Electric Meters)I12 Integrate with eMeter's EnergyIP version 7.2 or later CSU's MDMS

I13Integrate with MS Outlook Calendar to Populate Calendars with Work Orders, Service Requests, etc.

ArchitectureA1 Concurrent User Support (300 total 50-100 concurrent)A2 Standards-BasedA3 Web-Based Modern Architecture E.G. .NET, J2EEA4 Architecture Supports High Availability (Failover/Clustering) Technologies Target availability is 99.99%A5 Hot System Backup (App Server) Supported Backing up the application server without taking it down.A6 Role-Based Security Enforced

ToolsT1 Includes Administrator ToolsT2 Includes Web-Based Administrator Tools

T3 Includes Developer ToolsT4 Includes Web-Based Developer ToolsT5 Includes Configuration ToolsT6 Includes Web-Based Configuration ToolsT7 Published APIs or Adapters

SupportS1 Hotfix Support Patch can be applied without taking the server(s) down.S2 Product Updates Can Be Rolled BackS3 Efficient Product Updates (less than 4hrs)S4 Planned Patch Support and Notification (from Vendor)S5 Robust Error Logging

System Requirements

# Title The system shall provide the ability to … Vendor Response Comments

Proposers shall respond to each Requirement, noting all versions, releases, patches, and certification dates, where applicable. Any product version upgrades, additional software,

Technical Requirements

S6 Is there a Local Implementer?

ConfigurationC1 Web-Based ConfigurationC2 Web-Based Workflow AuthoringC3 Configurable Screens

C4Add New / Additional Lookup Values On the Fly (pre-identified, non MIS power users to modify field values) when appropriate.

Adding to dropdown lists and such on the fly.

DataD1 Data Import/Export Capabilities (e.g. MS Excel)D2 Encrypted Password Support If not using ADD3 System Domain Account Support in Both OS and DB. (not coding in personal credentials)D4 Rigorous and Granular Data Backup/Restore Procedures We would expect to provide these procedures in FC. D5 Flexible, Robust, Data Load Procedures

D6Ability to Access Data External to the CMMS and Display it on custom CMMS Screens

e.g., using modern standards such as SOAP, Web Services

D7 Supports Transactions. Logical Units of Work Committed in a Single Transaction.

D8 Documented Data Model To be provided to Ft. CollinsD9 Normalized Data Model

D10 Referential Integrity Enforced We expect Referential Integrity to be enforced within the Database. D11 Configurable DB Auditing with TimestampsD12 Front-End Data Validation

OtherO1 Supports On-Line Mode and Off-Line Mobile SyncO2 Date Format Flexibility/Synchronization Between Systems No dates in text mode. Must be date data type.O3 Utilization LoggingO4 Maintain User Preference Settings (configurable, persistent settings)O5 Adjustable Auto Log Out of Idle UsersO6 Full Audit Trail Capabilities (Non-db triggers driven) Triggers hinder scalability. O7 Ability to Copy / Paste System Objects e.g. assets (from the UI) O8 Structured/Canned WorkflowsO9 Ad-Hoc Workflows

O10 Field-Level Security EnforcedO11 All SQL will be Parameterized or use Bind Variables For better performance and to prevent SQL injection

FCU

WE&FO WR&T

Process Areas

System #1

System #3

System #2

System #4

Civil

Mechanical

Electrical

Instrumentation

Site

Fencing / WallsRoadways

LandscapingSite Lighting

Security

City of Fort Collins Utilities – Asset Hierarchy

L&P

Infrastructure/Piping

Yardpiping Manhole

Yard Valves

Rolling Stock

Vehicles

Generator (Portable)

Pump (Portable)

Lift/Bucket Truck Tractor Truck

Trailer (Tractor Truck)

Spreaders (Solid)

Electrical

SCADA

Distribution Network

Pipes

Water

Laterals/

Service

Connections

Locator

Stations

Wastewater

Drainage Basin

Area

Stormwater

Basins

Sub Basins

Open

Channels

Bridges &

Culverts

Dams &

Levees

Outlets

Detention

Basins

Pipelines

Flood Warning Systems

Maintenance Equipment

Placeholder – assets yet to be determined (FCU to update in the future)

Infrastructure Equipment

Infrastructure Equipment

Secondary SystemHeavy Equipment

* WR&T Process Areas would include processes such as Headworks, Pump Stations, A-Basins, Clarifiers, Reservoirs, etc.

Service Valves

Maintenance Equipment

600 Amp Distribution

Maintenance Equipment

Mulberry Water

Reclamation Facility

Infrastructure Equipment

Cathodic

Protection

Mechanical

Facilities

Access Points

Hydrants

Blowoffs

Monitoring

Stations

Distribution

Valves

Drake Water

Reclamation Facility

Water Treatment

Facility

Meadow Springs

Ranch

Offsite Pumping and

StorageSource of Supply

Servers

SoftwarePLCs

Network Equipment

200 Amp

Distribution

Curb Stops

Meter

Backflow

Vaults

Pipes

Buildings

Building #1

Building #3

Building #2

Building #4

Civil

Mechanical

Electrical

Instrumentation

Vehicles

Equipment

Vehicles

Equipment

Diversion

Structures

Stubs

Cleanouts

Manholes

Laterals/

Service

Connections

Vehicles

Equipment

Civil

Mechanical

Electrical

Structures

Outdoor

Classrooms

Water Quality

Facilities

Laterals Inlets Chases Manholes

Buildings

HVAC Units

Site

Maintenance

Fencing/Walls

Roadways

Landscaping

Relays

Transformers

Security

Systems

Power Meters

Bushings

Oil

ContainmentBattery

Systems

Breakers

SCADA

RTU’s

900 MHZ

Radio

Ethernet

Switches

Conduit

Duct Banks

Vaults-600A

(Manhole)

Voltage

Regulators

Cable

Splices

Switches

Meters

Connections

Equipment Vehicles

Conduit

Wood Poles

Cable

Sectionalizing

Cabinets

Junctions

Cutouts

Insulators

Overhead

Conductor

Splices

Distribution

Transformer

Vaults

Meters 200A

Customers

Lamps

Poles

Cable

Vaults

Conduit

Cable

Conduit

Meters –

Secondary

Customers

Street Lights

Vaults

Water Production Water Reclamation Substations Rolling Stock Fiber Optic System

Connections

Wastewater Main Wastewater Main

Cit

yD

ocs M

ap

s

Attributes Field Type/Domain Parameter Default Field Description

Active x 1 1 x DB E L x

Area x 1 1 x DB E L x

C3 x 1 1 x DB E L x

CautionCode x 1 1 x DB E L x

CkBy x 1 1 x DB E L x

CkDate x 1 1 x DB E L x

Company x 1 1 x DB E L x

DateInst x 1 1 x DB E L x

Diameter x 1 1 x x DB E L x

DwnElev x 1 1 x x DB E L x

ExpireDate x 1 1 x DB E L x

FManHole x 1 1 x DB E L x

Gen_SpecInst x 1 1 x DB E L x

HotSpotFreq x 1 1 x DB E L x

InMainCount x 1 1 x DB E L x

Inv x 1 1 x x DB E L x

JointLength x 1 1 x x DB E L x

LChgDate x 1 1 x DB E L x

LChgUser x 1 1 x DB E L x

Length x 1 1 x x DB E L x

LinedMethod x 1 1 x x DB E L x

MainID x 1 1 x DB E L x

MapIndex x 1 1 x DB E L x

MapLoc x 1 1 x DB E L x

NewDate x 1 1 x DB E L x

NewUser x 1 1 x DB E L x

OldFManHole x 1 1 x DB E L x

OldTManHole x 1 1 x DB E L x

PipeType x 1 1 x x DB E L x

ProjectName x 1 1 x DB E L x

ProjectType x 1 1 x DB E L x

s_ColLineage x 1 1 x DB E L x

s_Generation x 1 1 x DB E L x

s_GUID x 1 1 x DB E L x

s_Lineage x 1 1 x DB E L x

SpecInst x 1 1 x DB E L x

Status x 1 1 x DB E L x

StatusDate x 1 1 x DB E L x

TManHole x 1 1 x DB E L x

UniqueID x 1 1 x DB E L x

UpsElev x 1 1 x DB E L x

WarrantyDate x 1 1 x DB E L x

YearLined x 1 1 x DB E L x

Common Fields Cu

rren

tly C

ollecte

d

To

tal

% Migration Type

High Priority 13 17 76% Common Fields

Medium Priority 6 19 32% Drawing 0

Low Priority 0 1 0% Report 0

Spreadsheet 3

Object Fields Database 16

High Priority 18 18 ###

Medium Priority 25 25 ### Object Fields

Low Priority 0 0 ### Drawing 0

Report 0

Spreadsheet 0

Database 43

Typ

e o

f D

ata

(M

: M

an

ua

l; E

:

Ele

ctr

on

ic)

Oth

er

Data Location

GIS

CM

MS

CIS

FIS

SC

AD

A

Ha

rdco

py R

ep

ort

s,

Ma

ste

r P

lan

nin

g D

oc,

En

gin

eeri

ng

Rep

ort

, O

&M

Ma

nu

al

En

terp

rise D

ocs.

FU

PS

GIS

A: Asset Identifier

T: Technical Data

V: Valuation/Depreciation Data

M: Maintenance Data

C: Condition Data

R: Risk Data

L: Lifecycle Data

F: Failure Data

B: Budget Data

WR: Works/Resource

ORDM: Optimal Renewal Data

P: Performance Data

I: Inventory Data

Level of Importance

Ob

ject

Fie

lds

Pri

ma

ry (

Ph

ysic

al)

Seco

nd

ary

(C

on

dit

ion

)

Tert

iary

(C

ost)

Priority Performance Management Source Migration

Mo

ve (

L:

Lin

k;

V:

Va

lue)

En

gin

eeri

ng

Op

era

tio

ns

Sr.

Ma

na

gem

en

t / F

ina

nce

Reso

urc

e M

an

ag

em

en

t

Fo

rma

t (D

: D

raw

ing

; R

: R

ep

ort

; S

:

Sp

rea

dsh

eet;

DB

: D

ata

ba

se)

Cu

rren

t R

eg

ula

tio

ns

Do

es N

ot

Cu

rren

tly E

xis

t

Hig

h (

Bu

sin

ess C

riti

ca

l -

op

s n

eed

s)

Med

ium

(N

ice t

o H

ave -

decis

ion

ma

kin

g)

Lo

w (

No

t N

eed

ed

- O

ther

an

aly

sis

)

Sta

ff K

no

wle

dg

e

Co

llecte

d? (

1=

TR

UE

, 0

=FA

LS

E)

Source Priority

Oth

er

Sp

rea

dsh

eet,

Da

tab

ase,

etc

.

Perm

it T

rack

Po

nd

In

sp

ecti

on

Da

tab

ase

S4

Perm

it

Sit

e V

isit

Info

Wa

ter

MD

I

MW

HS

oft

H2

oM

ap

Sew

er

MW

HS

oft

H2

OM

ap

Wa

ter

Oth

er

– E

lectr

on

ic (E

xcel,

UN

IX

, e-S

erv

er)

Ap

pro

pri

ati

on

s S

tatu

s D

ata

ba

se

Ca

tho

dic

Pro

tecti

on

Da

tab

ase

CIS

WEWE&FO Wastewater_PDF.xlsxO Wastewater 10

Asset Management Levels of Service Owner: Dwight Dufloth & Lisa VoytkoPotable Water Treatment and Distribution

Key Service Criteria

Performance Indicator Target Level of Service Measurement Process Current Performance (end of 2010 calendar year)

Comments

Taste, Odor, and Color Complaints

82 Total Rusty/Dirty water complaints over last 4 years

T&O complaints related to water treatment

41 T&O Complaints over last 4 years

Rusty/dirty water complaints related to line flushing/water main breaks.

T&O Complaints = 0.85/mo.

Data that tracks number of customer complaints and what type re: water quality is kepy by the Water Quality Lab. This data is an average of the last 4 years for T&O and rusty/dirty water complaints.

Rusty/Dirty Water = 1.7 complaints/mo.

Regulatory Maximum Contaminant Limits & City Water Treatment Facility Limits

100% compliance with Maximum Contaminant Limits & City Water Treatment Facility Limits

Continuous sampling at plant 100% compliance 100% compliance is required and is continuously achieved at the WTF.

Reliability Pressure at meter Pressure in distribution system > 20 PSI

Undertake pressure and flow tests at time of meter installation

Average frequency of outages

Average frequency of outages less than one per yearNo more than 2% of customers receive more than two outages per year

Average duration of outages

Average duration of outages less than two to four hoursNo more than 2% of customers receive an outage of more than three hours duration

Fire fighting flow at hydrant

Fire flow (residential = 1000 gpm, commercial = 1500 gpm)

Pressure > 20psi in fire-fighting condition

Availability Number of days where water restrictions are in place

Water restrictions in place for no more than 30 days per year on average

Record number of days per year water restrictions are in place

100% compliance since 2003

Responsiveness to outages

Response time to customer complaints due to a loss of supply

Respond to customer complaints regarding loss of supply within 30 minutes 99% of the time

Measure time that complaint is received versus time of arrival onsite

99% within 30 minutes

Water Loss Unaccounted water < 6% unaccounted water loss/revenue

Measure water production versus metered sales

TBD This will be investigated further once AMI is operational.

TBD

Measure flow at fire hydrants as part of maintenance and testing program

Quality <1 complaint /month regarding taste, odor, or rusty/dirty water

Number of complaints regarding taste, odor, or rusty/dirty water

Record duration and number of customers affected for all outages

Utility System Name # WOs

Field

Water WUMS 48,000

Wastewater WIST 53,000

Stormwater SWIMS 1,500

Total Field WOs 54,500

Plant

Water Treatment Facility 19,311

Waste Water Treatment Facility 27,705

Total Plant WOs 47,016

Total 101,516

Utility Work Order Summary

Utility Asset Type # Assets

Field Assets

Water

Mains 10,000

Valves 12,000

Hydrants 3,600

Wastewater

Mains 10,700

Manholes 10,600

Stormwater

Lines 13,700

Points 14,000

Inlets 6,800

Manholes 3,200

Electric

Lines 18,800

Transformers 7,500

Switch Points 17,800

Total Field Assets 128,700

Plant Assets

Water Treatment Facility 4,511

Waste Water Treatment Facility 4,169

Total Plant Assets 8,680

Total 137,380

Utility Asset Summary

IntakeCountByBlockName

CountOfPointID

AcadBlockName

TVIConditionRoot

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

TVIConditionDebris

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

LINE

PK LineID

U2 UniqueID

I12 OldUniqueID

I6 CompType

I8 FPoint

OldFPoint

I18 TPoint

OldTPoint

AKA

I3 Area

FK1,I1 MatType

WDiameter

HDiameter

Length

JointLength

UpsElev

DwnElev

SpecInst

InLineCount

I9 HotSpotFreq

DateInst

WarrantyDate

CityOwned

CityMaintained

FK3,I11 MapLoc

MapIndex

FK2,I5,I4 CautionCode

ProjectType

ProjectName

CkDate

CkBy

I7 ConditionCode

LastInspDate

CoFScore

CoFDate

I2 Active

FK4,FK5,FK6,I17,I16,I15,I14 Status

StatusDate

ExpireDate

I10 Inv

Aen_SpecInst

LChgDate

LChgUser

U1 s_GUID

Gen_SpecInst

NewDate

NewUser

s_ColLineage

I13 s_Generation

s_Lineage

COMPACTPRBCDE

PK,I2 Comp

PK,I1 ActCde

PK,I3 PrbCde

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

OutfallsWithoutScreening

PointNum

STREETNO

STREETNAME

Qualifier

Area

ACTCDE

PK ActCde

I1 Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

SCREENSAMPLEINFRASTRUCTURE

PK,I3 ScreeningId

PK,I2 SampleId

SampleDate

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

MSysAccessStorage_Conflict

I1 ConflictRowGuid

DateCreate

DateUpdate

Id

Lv

Name

ParentId

Type

Gen_Lv

I2 s_Generation

I3 s_GUID

s_Lineage

Location

PK,I1 Code

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

BASINMAT

PK,I1 MatCde

Description

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

WQFEATURE

PK WQFeature

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

tblBasinAttach_old

PK,I2 ID

I1 BasinID

Attachment

U1 s_GUID

POINT_Conflict

I1 ConflictRowGuid

PointID

PointNum

OldPointNum

CompType

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

AKA

Qualifier

Area

Measurements

Drop

Depth

CoverDiam

BarrelDiam

Material

StepsMat

SurfCover

InletType

GrtType

InWidth

InHeight

GrtWidth

GrtLength

Capacity

SpecInst

DateInst

WarrantyDate

DumpNoWasteMarker

WtrQltyFeature

CityOwned

DumpNoWasteDate

FloodPlain

CityMaintained

PermitStartDate

DateCertified

MapLoc

MapIndex

CautionCode

ProjectType

CkDate

ProjectName

CkBy

Active

NewDate

NewUser

LChgDate

LChgUser

Status

ConditionCode

StatusDate

ExpireDate

LastInspDate

CoFScore

Gen_Measurements

CoFDate

Gen_SpecInst

Aen_Measurements

Aen_SpecInst

I3 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

EMREVENT

PK EventNum

I1 Date

I2 Description

I3 Quadrant

s_ColLineage

I4 s_Generation

U1 s_GUID

s_Lineage

OutfallsWithScreening

PointNum

Date

STREETNO

STREETNAME

Qualifier

Area

SampleId

WOLINELIST

PK,FK1,I5,I1 WoNum

PK,FK2,I3,I2 LineID

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

TVIConditionStructural

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

CUSTCONT

PK DateTime

PK Name

Address

Phone

Notes

I1 CompletionDate

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

AREA

PK,I1 Area

Desc

Frequency

I2 NextDueDate

U1 s_GUID

s_ColLineage

I3 s_Generation

s_Lineage

WOEMPLOYEE

PK,FK1,I2,I1 WoNum

PK,I3 EmpID

PK Date

RegHours

OTHours

RegRate

OTRate

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

TVIConditionInflow

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

STATUS

PK StatCde

Desc

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

POINTWQFEATURE

PK,FK1,I2,I1 PointID

PK WQFeature

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

LINETVINSP_Conflict

I1 ConflictRowGuid

WoNum

LineID

TVOperator

FlowDepth

Summary

I3 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

tblNextNodeNumber

PK NextNodeNumber

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

SCREENSAMPLEOUTFALL

PK,FK1,I4,I3 ScreeningId

PK,I2 SampleId

SampleDate

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

MAPLOC

PK MapLoc

LocDesc

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

LINETVINSPFEET_Conflict

I1 ConflictRowGuid

WoNum

LineID

Setup

Feet

ClockPosition

CrackRC

CrackLC

JointMJ

JointBJ

Lateral

Roots

Debris

Inflow

Align

StructDS

StructOS

StructCS

Comments

I3 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

LINE_Log

PK LineID

PK UserName

PK DateTime

UniqueID

OldUniqueID

CompType

FPoint

OldFPoint

TPoint

OldTPoint

AKA

Area

MatType

WDiameter

HDiameter

Length

JointLength

UpsElev

DwnElev

SpecInst

InLineCount

HotSpotFreq

DateInst

CityOwned

CityMaintained

MapLoc

MapIndex

I1 CautionCode

ProjectType

CkDate

CkBy

Active

Status

StatusDate

ExpireDate

I2 Inv

LChgDate

LChgUser

NewDate

NewUser

Aen_SpecInst

Gen_SpecInst

Ben_SpecInst

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

BRIDGEMAT

PK,I1 MatCde

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

WOLINELIST_Conflict

I1 ConflictRowGuid

WoNum

LineID

I3 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

POINT_Log

PK PointID

PK UserName

PK DateTime

PointNum

OldPointNum

CompType

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

AKA

Qualifier

Area

Measurements

Drop

Depth

CoverDiam

BarrelDiam

Material

StepsMat

SurfCover

InletType

GrtType

InWidth

InHeight

GrtWidth

GrtLength

Capacity

SpecInst

DateInst

WarrantyDate

WtrQltyFeature

CityOwned

CityMaintained

MapLoc

MapIndex

I1 CautionCode

ProjectType

CkDate

CkBy

Active

NewDate

NewUser

LChgDate

LChgUser

Status

StatusDate

ExpireDate

Aen_Measurements

Aen_SpecInst

Gen_Measurements

Gen_SpecInst

Ben_Measurements

Ben_SpecInst

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

PRBCDE

PK PrbCde

U1 Description

U2 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

POINTINSPECTION

PK,I1 PointID

PK Date

I2 RefId

Inspector

I4 WoNum

OverAllCondition

01Condition

01Comment

02Condition

02Comment

03Condition

03Comment

04Condition

04Comment

05Condition

05Comment

06Condition

06Comment

07Condition

07Comment

08Condition

08Comment

09Condition

09Comment

10Condition

10Comment

11Condition

11Comment

12Condition

12Comment

13Condition

13Comment

14Condition

14Comment

15Condition

15Comment

16Condition

16Comment

17Condition

17Comment

18Condition

18Comment

19Condition

19Comment

20Condition

20Comment

MaintenanceNeededNote

GeneralAppearanceNote

Gen_GeneralAppearanceNote

Gen_MaintenanceNeededNote

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

INLETMAT

PK,I1 MatCde

Description

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

GRATETYPE

PK,I1 Type

Description

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

EQUIPMENT

PK UnitID

I2 Description

Type

Location

I4 SerialNum

I1 ModelNum

Manufacturer

PurchDate

PurchCost

ChgAmount

AssignedTo

Year

LicenseNo

Dept

FuelType

Unit

AdditionalCostDate

AdditionalCostAmt

AdditionalCosts

Inuse

I5 Status

StatusDate

ExpireDate

NewDate

NewUser

LChgDate

s_ColLineage

LChgUser

I3 s_Generation

U1 s_GUID

s_Lineage

TYPESITE

TYPESITE

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

TVIConditionJoint

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

TVIConditionAlignment

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

STEPMAT

PK,I1 MatCde

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

OTRATE

OTRate

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

CAUTIONCDE

PK CautionCode

I1 Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

BARRELDIAM

PK,I1 Diameter

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

StateReport

PK,I1 ReportID

A

B

C

D

E

F

G

H

I

J

K

L

M

N

O

ReportDate

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

MATERIAL

PK MatID

Description

Units

Price

I1 Active

ExpireDate

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

DUMPNOWASTEMARKERTYPE

PK DumpNoWasteMarkerType

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

WOMATERIAL

PK,FK1,I3,I1 WoNum

PK,FK2,I4,I2 MatID

Qty

Price

U1 s_GUID

s_ColLineage

I5 s_Generation

s_Lineage

LINETVINSPFEET

PK,FK1,I1 WoNum

PK,FK1,I14,I1 LineID

PK Setup

PK Feet

ClockPosition

FK3,I3 CrackRC

FK4,I4 CrackLC

FK7,I7 JointMJ

FK8,I8 JointBJ

FK9,I9 Lateral

FK10,I10 Roots

FK5,I5 Debris

FK6,I6 Inflow

FK2,I2 Align

FK11,I11 StructDS

FK12,I12 StructOS

FK13,I13 StructCS

Comments

U1 s_GUID

s_ColLineage

I15 s_Generation

s_Lineage

bar

PointNum

STREETNO

STREETNAME

STREETDIR

TYPESITE

Area

GrtType

SpecInst

WOEQUIPLIST

PK,FK1,I1,I4 WoNum

PK,I2 UnitID

U1 s_GUID

s_ColLineage

I3 s_Generation

s_Lineage

WO

PK WoNum

Gen_Comments

I11 CompType

FK2,I2 ActCde

FK1,I1 PrbCde

I7 Project

FK4,I9,I8 ProjectType

I3 Area

Priority

SchedStartDate

AssignedTo

RequestDate

Originator

CompletionDate

Comments

CallTime

ContactTime

ArrivalTime

CallName

CallPhone

I4 CompNum

Company

Aen_Comments

Phone

Attention

U1 s_GUID

Address1

PermitNo

s_ColLineage

Address2

I10 s_Generation

FK3,I6,I5 EventNum

s_Lineage

PROJECTTYPE

PK,I1 ProjectType

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

OUTLETMAT

PK,I1 MatCde

Description

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage LINE_Conflict

I1 ConflictRowGuid

LineID

UniqueID

OldUniqueID

CompType

FPoint

OldFPoint

TPoint

OldTPoint

AKA

Area

MatType

WDiameter

HDiameter

Length

JointLength

UpsElev

DwnElev

SpecInst

InLineCount

HotSpotFreq

DateInst

WarrantyDate

CityOwned

CityMaintained

MapLoc

MapIndex

CautionCode

ProjectType

ProjectName

CkDate

CkBy

Active

ConditionCode

LastInspDate

Status

CoFScore

StatusDate

CoFDate

ExpireDate

Inv

LChgDate

LChgUser

Aen_SpecInst

NewDate

NewUser

I3 s_GUID

Gen_SpecInst

s_ColLineage

I2 s_Generation

s_Lineage

INLETTYPE

PK,I1 Type

Description

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

HOAInfo

PK,I2 HOAID

Company

ContactName

HOAName

Address

City

StateOrProvince

I3 PostalCode

Country

I1 EmailAddress

WebAddress

WorkPhone

WorkExtension

DateLastTalkedTo

DateUpdated

Notes

Gen_EmailAddress

Gen_Notes

Gen_WebAddress

s_ColLineage

I4 s_Generation

U1 s_GUID

s_Lineage

Basin

PK,I1 BasinID

QS

SW #

Name

Address

Subdivision

HOA

Notes

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

WO_Conflict

I1 ConflictRowGuid

Gen_Comments

WoNum

CompType

ActCde

PrbCde

Project

ProjectType

Area

Priority

SchedStartDate

AssignedTo

RequestDate

Originator

CompletionDate

Comments

CallTime

ContactTime

ArrivalTime

CallName

CallPhone

CompNum

Company

Aen_Comments

Phone

Attention

I3 s_GUID

Address1

PermitNo

s_ColLineage

Address2

I2 s_Generation

EventNum

s_Lineage

TVIConditionLateral

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

TVIConditionCrack

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

SURFMAT

PK,I1 MatCde

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

LINEMATTYPE

PK LineMatType

Description

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

LEVEEMAT

PK,I1 MatCde

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

EMPLOYEE

PK EmpID

I3 EmpCde

FirstName

I2 LastName

RegRate

OTRate

I1 Active

ExpireDate

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

COMPACT

PK,I2 Comp

PK,I1 ActCde

s_ColLineage

I3 s_Generation

s_Lineage

U1 s_GUID

WOEQUIPMENT

PK,FK1,I2,I1 WoNum

PK,I4 UnitID

PK Date

Hours

Rate

U1 s_GUID

s_ColLineage

I3 s_Generation

s_Lineage

WOPOINTLIST

PK,FK2,I5,I2 WoNum

PK,FK1,I3,I1 PointID

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

WOCONTRACT

PK,FK1,I1,I4 WoNum

PK,I2 Contractor

Hours

Rate

Materials

Labor

Total

U1 s_GUID

s_ColLineage

I3 s_Generation

s_Lineage

tblBasinAttach

PK,I2 ID

I1 BasinID

Attachment

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

SCREENOUTFALL

PK,I6 ScreeningId

FK1,FK2,I3,I2,I1 PointID

Date

WaterBody

RainOrSnow

Flow

FlowEstimate

WaterQty

Floatables

FloatablesDesc

Odor

OdorDesc

Stained

StainedDesc

Damage

DamageDesc

VegetationChange

VegetationDesc

BiomatCoating

InvestigateFurther

InvestigateFurtherDesc

SampleDate

I5 SampleId

InvestigateFurtherWQL

InvestigateFurtherWQLDesc

SourceOfFlow

ImproperConnectionSource

DateRemoved

Note

Gen_Note

s_ColLineage

I4 s_Generation

U1 s_GUID

s_Lineage

SCREENINFRASTRUCTURE

FK1,FK2,I7,I6 ScreeningId

I1 Id

I2 PointNum

InfraType

Date

Flow

FlowEstimate

WaterQty

Floatables

FloatablesDesc

Odor

OdorDesc

Stained

StainedDesc

Damage

DamageDesc

VegetationChange

VegetationDesc

BiomatCoating

InvestigateFurther

InvestigateFurtherDesc

SampleDate

I4 SampleId

InvestigateFurtherWQL

InvestigateFurtherWQLDesc

Note

Gen_Note

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

POINT

PK PointID

U2 PointNum

I9 OldPointNum

I6 CompType

I16 STREETNO

STREETNOHALF

STREETDIR

I15 STREETNAME

TYPESITE

STREETSUFX

APARTNO

AKA

Qualifier

FK1,I3,I2 Area

Measurements

Drop

Depth

CoverDiam

BarrelDiam

Material

StepsMat

SurfCover

InletType

GrtType

InWidth

InHeight

GrtWidth

GrtLength

Capacity

SpecInst

DateInst

WarrantyDate

DumpNoWasteMarker

DumpNoWasteDate

WtrQltyFeature

FloodPlain

PermitStartDate

DateCertified

CityOwned

CityMaintained

FK3,I8 MapLoc

MapIndex

FK2,I5,I4 CautionCode

ProjectType

ProjectName

CkDate

CkBy

I7 ConditionCode

LastInspDate

CoFScore

CoFDate

I1 Active

NewDate

NewUser

Gen_SpecInst

LChgDate

Aen_SpecInst

LChgUser

Gen_Measurements

FK4,FK5,FK6,I14,I13,I12,I11 Status

Aen_Measurements

StatusDate

ExpireDate

U1 s_GUID

s_ColLineage

I10 s_Generation

s_Lineage

MHMAT

PK,I1 MatCde

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

LINETVINSP

PK,FK1 WoNum

PK,FK1 LineID

TVOperator

FlowDepth

Summary

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

LINEINSPECTION

PK,I1 LineID

PK Date

I2 RefId

Inspector

I4 WoNum

OverAllCondition

01Condition

01Comment

02Condition

02Comment

03Condition

03Comment

04Condition

04Comment

05Condition

05Comment

06Condition

06Comment

07Condition

07Comment

08Condition

08Comment

09Condition

09Comment

10Condition

10Comment

11Condition

11Comment

12Condition

12Comment

13Condition

13Comment

14Condition

14Comment

15Condition

15Comment

16Condition

16Comment

17Condition

17Comment

18Condition

18Comment

19Condition

19Comment

20Condition

20Comment

MaintenanceNeededNote

GeneralAppearanceNote

Gen_GeneralAppearanceNote

Gen_MaintenanceNeededNote

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

Inspections

PK,I2 RecordID

Date

BasinName

BasinAddress

Inspector

I1 HOAID

HOAName

HOAContact

HOAAddress

ReasonForInspection

Enforcement

Outlet

Inlet

TricklePan

Vegetation

Erosion

OverflowWeir

MiscNotes

CurrentState

CorrectionDate

Subdivision

Gen_MiscNotes

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

Stormwater CMMS (SWIMS) ERD

WOEMPLOYEE

PK,FK1,I2,I1 WoNum

PK,I3 EmpID

PK Date

RegHours

OTHours

RegRate

OTRate

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

MHMAT

PK,I1 MatCde

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

MAINTVINSPFEET

PK,FK1,I1 WoNum

PK,FK1,I14,I1 MainID

PK Setup

PK Feet

ClockPosition

FK3,I3 CrackRC

FK4,I4 CrackLC

FK7,I7 JointMJ

FK8,I8 JointBJ

FK9,I9 Lateral

FK10,I10 Roots

FK5,I5 Debris

FK6,I6 Inflow

FK2,I2 Align

FK11,I11 StructDS

FK12,I12 StructOS

FK13,I13 StructCS

Comments

U1 s_GUID

s_ColLineage

I15 s_Generation

s_Lineage

LABORGRP

PK LaborGrp

Description

RegRate

OTRate

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

TVInspect

UniqueID

TVIConditionStructural

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

TVIConditionInflow

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

ACTCDE

PK ActCde

I1 Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

COMPACTPRBCDE

PK,I2 Comp

PK,I1 ActCde

PK,I3 PrbCde

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

WOMANHLIST

PK,FK2,I5,I2 WoNum

PK,FK1,I3,I1 ManHoleID

Bugs

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

tblNextNodeNumber

PK NextNodeNumber

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

OTRATE

OTRate

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

AREA

PK,I1 Area

Frequency

I2 NextDueDate

U1 s_GUID

s_ColLineage

I3 s_Generation

s_Lineage

TYPESITE

PK TYPESITE

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

STATUS

PK StatCde

Desc

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

LINECOMPANY

PK CompanyName

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

WOEQUIPLIST

PK,FK1,I4,I1 WoNum

PK,I2 UnitID

U1 s_GUID

s_ColLineage

I3 s_Generation

s_Lineage

TVIConditionJoint

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

TVIConditionAlignment

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

PRBCDE

PK PrbCde

U1 Description

U2 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

MAINPIPETYPE

PK PipeType

Description

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

EMPLOYEE

PK EmpID

I3 EmpCde

LaborGrp

FirstName

I2 LastName

RegRate

OTRate

I1 Active

ExpireDate

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

Infiltration

MainID

UniqueID

Status

WoNum

DateInst

YearLined

CompletionDate

Inflow

Feet

Comments

WOMATERIAL

PK,FK1,I1,I3 WoNum

PK,FK2,I2,I4 MatID

Qty

Price

U1 s_GUID

s_ColLineage

I5 s_Generation

s_Lineage

MAPLOC

PK MapLoc

LocDesc

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

WO

PK WoNum

Gen_Comments

I9 CompType

FK2,I2 ActCde

FK1,I1 PrbCde

I5 Project

I6 ProjectType

I3 Area

Priority

SchedStartDate

AssignedTo

RequestDate

Originator

CompletionDate

Comments

CallTime

ContactTime

ArrivalTime

CallName

CallPhone

Aen_Comments

I4 CompNum

Company

Attention

s_ColLineage

Address1

Address2

I7 s_Generation

Phone

U1 s_GUID

s_Lineage

PermitNo

I8 TaskNum

STEPMAT

PK,I1 MatCde

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

Location

PK,I1 Code

Description

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

BARRELDIAM

PK,I1 Diameter

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

MainTVeed2011

UniqueID

MainID

MaxOfCompletionDate

Expr1

WOEQUIPMENT

PK,FK1,I2,I1 WoNum

PK,I4 UnitID

PK Date

Hours

Rate

U1 s_GUID

s_ColLineage

I3 s_Generation

s_Lineage

WOCONTRACT

PK,FK1,I1,I4 WoNum

PK,I2 Contractor

Hours

Rate

Materials

Labor

Total

U1 s_GUID

s_ColLineage

I3 s_Generation

s_Lineage

TVIConditionLateral

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

TVIConditionCrack

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

PROJECTTYPE

PK,I1 ProjectType

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

TASKMAINLIST

PK,I3 TaskNum

PK,I1 MainID

Footage

Condition

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

MATERIAL

PK MatID

Description

Units

Price

I1 Active

ExpireDate

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

NoTVInspections

MainID

UniqueID

Status

WoNum

DateInst

YearLined

CompletionDate

Inflow

Feet

Comments

WOSLLIST

PK,FK1,I3,I1 WoNum

PK,FK2,I2,I5 ServLineID

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

SURFMAT

PK,I1 MatCde

Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

MAINTVINSP

PK,FK1 WoNum

PK,FK1 MainID

TVOperator

FlowDepth

Summary

U1 s_GUID

s_ColLineage

I1 s_Generation

s_Lineage

MAIN

PK MainID

U2 UniqueID

FK3,I7 FManHole

I8 OldFManHole

FK2,I14 TManHole

I15 OldTManHole

I3 Area

FK1,I1 PipeType

Diameter

Length

C3

ProjectType

ProjectName

JointLength

UpsElev

DwnElev

SpecInst

InMainCount

I9 HotSpotFreq

DateInst

WarrantyDate

YearLined

LinedMethod

Company

YearFoamed

FoamCompany

MapLoc

MapIndex

FK4,I5,I4 CautionCode

CkDate

CkBy

I2 Active

I10 Inv

I6 ConditionCode

LastInspDate

CoFScore

CoFDate

s_ColLineage

FK5,I13,I12 Status

I11 s_Generation

StatusDate

ExpireDate

Gen_SpecInst

U1 s_GUID

LChgUser

s_Lineage

LChgDate

NewDate

NewUser

CAUTIONCDE

PK CautionCode

I1 Description

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

MANHOLE

PK ManHoleID

U3 ManHoleNum

U1 OldManHoleNum

I11 STREETNO

STREETNOHALF

STREETDIR

I10 STREETNAME

TYPESITE

STREETSUFX

APARTNO

Qualifier

FK1,I1,I3 Area

Measurements

Drop

Depth

CoverDiam

BarrelDiam

MHMaterial

StepsMat

SurfCover

C3

ProjectName

ProjectType

SpecInst

DateInst

WarrantyDate

YearLined

MapLoc

MapIndex

FK2,I5,I4 CautionCode

CkDate

CkBy

I2 Active

I6 ConditionCode

LastInspDate

CoFScore

CoFDate

LChgUser

LChgDate

NewUser

Gen_Measurements

NewDate

Gen_SpecInst

FK3,I9,I8 Status

StatusDate

ExpireDate

U2 s_GUID

s_ColLineage

I7 s_Generation

s_Lineage

TVIConditionRoot

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

TVIConditionDebris

PK,I1 Code

Description

Factor

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

SERVICELINE

PK ServLineID

Gen_SpecInst

FK2,I5,I2 MainID

I6 ManHoleNum

I7 Premise

UniqueID

I12 STREETNO

STREETNOHALF

STREETDIR

I11 STREETNAME

TYPESITE

STREETSUFX

APARTNO

FK1,I1 Area

Diameter

TapLocation

TapLocationFrom

I8 CleanoutLoc

Taps

SumpPump

SpecInst

WashContact

WashContactName

WashContactRegHrs

WashContactAftHrs

WashContactInst

MapLoc

MapIndex

FK3,I4,I3 CautionCode

Aen_SpecInst

ProjectType

CkDate

CkBy

s_ColLineage

NewDate

I9 s_Generation

NewUser

s_Lineage

FK4,I10 Status

ExpireDate

StatusDate

LChgDate

LChgUser

U1 s_GUID

FOAMCOMPANY

PK CompanyName

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

EQUIPMENT

PK UnitID

I2 Description

Type

Location

I4 SerialNum

I1 ModelNum

Manufacturer

PurchDate

PurchCost

ChgAmount

AssignedTo

Year

LicenseNo

Dept

FuelType

Unit

AdditionalCostDate

AdditionalCostAmt

AdditionalCosts

Inuse

I5 Status

StatusDate

ExpireDate

NewDate

NewUser

LChgDate

LChgUser

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

WOMAINLIST

PK,FK1,I5,I1 WoNum

PK,FK2,I3,I2 MainID

Footage

Condition

U1 s_GUID

s_ColLineage

I4 s_Generation

s_Lineage

COMPACT

PK,I2 Comp

PK,I1 ActCde

U1 s_GUID

s_ColLineage

I3 s_Generation

s_Lineage

TASKMANHLIST

PK,I3 TaskNum

PK,I1 ManHoleID

Bugs

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

TASK

PK,I7 TaskNum

SchedType

Period

Frequency

LastPerfDate

I3 NextDueDate

I2 CompType

ActCde

PrbCde

I4 Project

I5 ProjectType

I1 Area

Priority

AssignedTo

Originator

Comments

Gen_Comments

s_ColLineage

I6 s_Generation

U1 s_GUID

s_Lineage

Wastewater CMMS (WIST) ERD

WOVALVELIST

PK,FK2,I5,I4 WoNum

PK,FK1,I3,I2 UnitID

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

WOHYDLIST

PK,FK1,I4,I3 WoNum

PK,I2 UnitID

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

VALMOD

PK MODEL

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

TESTSTATIONTYPE

PK TestStationType

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

CPDATA_Conflict

I1 ConflictRowGuid

CPID

ReadingDate

PSVolts1

PSVolts2

PSVolts3

PSVolts4

PSVolts5

PSVolts6

AnodeCurrent

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

BEAMDIST

Distance

Fraction

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

Query4

PressZone

WumsServLineInvID

WOCPLIST

PK,FK2,I5,I4 WoNum

PK,FK1,I1,I3 UnitID

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

OTRATE

PK OTRate

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

METERSIZE

PK Index

Size

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

MAINTRACER

PK,FK2,I3,I2 MainID

PK,FK1,I5,I1 UnitID

s_ColLineage

I4 s_Generation

U1 s_GUID

s_Lineage

MAIN

PK,I5 MainID

FK5,I8 MainType

I12 UniqueID

BLOCKNO

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

MAINDIR

FK4,I7 PipeType

PipeDiameter

Location

Area

PressZone

FK3,I6 Manufacturer

Length

DateInst

WarrantyDate

Depth

SpecInst

FK2,I4 Inspector

CP

C3

Project

MapLoc

MapIndex

FK1,I2,I1 CautionCode

I3 ConditionCode

LastInspDate

CoFScore

CoFDate

Active

FK6,I11,I10 Status

StatusDate

ExpireDate

ProjectType

ConfinedSpaceType

CkDate

CkBy

NewUser

NewDate

Gen_SpecInst

LChgDate

LChgUser

Aen_SpecInst

s_ColLineage

I9 s_Generation

U1 s_GUID

s_Lineage

ACCESSMANHOLE

PK,I7 UnitID

I4 Old_UnitID

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

Location

Area

I3 MainID

DateInst

WarrantyDate

BelowGroundDepth

SpecInst

Inspector

Comments

ProjectType

ConfinedSpaceType

C3

Project

Above_Below

MapLoc

MapIndex

I1 CautionCode

CkDate

CkBy

I2 ConditionCode

LastInspDate

CoFScore

CoFDate

Active

I6 Status

NewUser

NewDate

Gen_Comments

LChgUser

Gen_SpecInst

LChgDate

Aen_Comments

StatusDate

ExpireDate

s_ColLineage

I5 s_Generation

U1 s_GUID

s_Lineage

Turbidity

HydrantNodeNumber

FlushStartDateTime

GaveUpOnTurbidity

TestDateTime

Turbidity

EDITS

MatID

Description

Price

Cost

Units

Active

ExpireDate

WOEQUIPLIST

PK,FK2,I5,I4 WoNum

PK,FK1,I3,I1 UnitID

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

WO_Conflict

I1 ConflictRowGuid

WoNum

CompType

ActCde

PrbCde

Project

ProjectType

Area

Priority

SchedStartDate

AssignedTo

RequestDate

Originator

CompletionDate

CallTime

ArrivalTime

CallName

ContactTime

CallPhone

Comments

CompNum

Company

Attention

Address1

Address2

Phone

RevAcct

Aen_Comments

MapX

Gen_Comments

MapLocationX

MapY

s_ColLineage

MapLocationPlacedBy

I2 s_Generation

MapLocationDate

I3 s_GUID

s_Lineage

MapLocationY

SUBMITTAL

I1 IdNum

RecDate

Type

Sentdate

DueDate

RevDate

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

LEAKDATASERVICE

PK,I2 WoNum

LeakType

LeakMaterial

NoServ

TimeOutage

FeetCorrelated

PipeDiam

DetectionMethod

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

LABORGRP

PK LaborGrp

Description

RegRate

OTRate

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

HYDMODEL

PK Model

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

FILEMAPAREA

PK,I2 FileNum

PK,FK1,I1 MapArea

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

CONDITION

PK,I1 ConditionCode

Description

LongDesc

U1 s_GUID

s_ColLineage

I2 s_Generation

s_Lineage

WOHYDMTRREQ

PK,I4 WoNum

TakenBy

Contact

Phone

SubName

Use

Size

SetDate

SetTime

SetBy

RemovDate

RemovTime

RemovNote

LocateReq

LocateApp

Direction

HWrenchIssued

HMeterChained

RateExlp

RespExlp

I3 UnitId

DateRem

DateInst

SetRdg

RemRdg

WtrUse

Gal

GalTot

KGalRate

Rental

DailyRate

RenTotal

TripRate

Trips

TripTot

Other

OtherTot

Note

I1 HydUnitID

Aen_Note

Gen_Note

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

VALVE_Conflict

I1 ConflictRowGuid

UnitID

Old_UnitID

ValveType

MainID

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

Location

Area

IsolationValve

ModelNum

Manufacturer

ManufacturerDate

Size

DateInst

WarrantyDate

OperatingExt

OperatingDepth

ValveDepth

SpecInst

Saver

PermaLog

NumTurns

Direction

Inspector

Comments

ConfinedSpaceType

ProjectType

C3

Project

TracerWire

LocStationUnitID

MapLoc

MapIndex

CautionCode

CkDate

CkBy

Active

ConditionCode

LastInspDate

Status

CoFScore

StatusDate

CoFDate

NewUser

NewDate

LChgUser

LChgDate

Aen_Comments

Ben_Comments

Gen_Comments

Gen_SpecInst

Aen_SpecInst

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

VALVE

PK,I10 UnitID

I7 Old_UnitID

FK3,I13 ValveType

I4 MainID

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

Location

Area

IsolationValve

FK2,I5,I12 ModelNum

FK1,I11 Manufacturer

ManufacturerDate

Size

DateInst

WarrantyDate

OperatingExt

OperatingDepth

ValveDepth

SpecInst

Saver

PermaLog

I6 NumTurns

Direction

Inspector

Comments

ConfinedSpaceType

ProjectType

C3

Project

TracerWire

I3 LocStationUnitID

MapLoc

MapIndex

I1 CautionCode

CkDate

CkBy

I2 ConditionCode

LastInspDate

CoFScore

CoFDate

Active

I9 Status

StatusDate

Aen_Comments

NewUser

NewDate

Gen_Comments

LChgUser

Gen_SpecInst

LChgDate

s_ColLineage

I8 s_Generation

U1 s_GUID

s_Lineage

TYPESITE

PK TYPESITE

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

SERVICELINE_Conflict

I1 ConflictRowGuid

ServLineID

ServType

MainID

MatchQty

AlsoServ

Premise

UniqueID

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

Area

PressZone

CurbStopLoc

WarrantyExp

Inspector

DateInst

Diameter

Length

PipeType

Comments

ExistingMeterBox

OutSideSpkrCon

CriticalCde

CriticalContactName

CriticalContactRegHrs

CriticalContactAftHrs

CriticalCheckCmt

ProjectType

ConfinedSpaceType

Source

MapLoc

MapIndex

CautionCode

Active

ConditionCode

LastInspDate

Status

CoFScore

StatusDate

CoFDate

ExpireDate

Provider

CkMp

CkMpDate

CkBy

SewerOnly

Meterno

NewUser

NewDate

LChgUser

LChgDate

Aen_Comments

Gen_Comments

Ben_Comments

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

SERVICELINE

PK,I7 ServLineID

FK3,I8 ServType

I5 MainID

MatchQty

AlsoServ

Premise

I12 UniqueID

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

FK5,I11 TYPESITE

STREETSUFX

APARTNO

Area

PressZone

CurbStopLoc

WarrantyExp

FK2,I4 Inspector

DateInst

Diameter

Length

FK4,I9 PipeType

Comments

ExistingMeterBox

OutSideSpkrCon

FK1,I3 CriticalCde

CriticalContactName

CriticalContactRegHrs

CriticalContactAftHrs

CriticalCheckCmt

ProjectType

ConfinedSpaceType

Source

MapLoc

MapIndex

I1 CautionCode

I2 ConditionCode

LastInspDate

CoFScore

CoFDate

Active

I10 Status

StatusDate

ExpireDate

Provider

CkMp

CkMpDate

CkBy

SewerOnly

Meterno

Aen_Comments

NewUser

Gen_Comments

NewDate

LChgUser

LChgDate

s_ColLineage

I6 s_Generation

U1 s_GUID

s_Lineage

MAPAREA

PK MapArea

Quadrant

Section

Township

Range

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

DEPARTMENT

PK Dept

Domicile

BegBalance

AnnualContr

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

WOVALVELIST_Conflict

I1 ConflictRowGuid

WoNum

UnitID

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

WOMATERIAL_Conflict

I1 ConflictRowGuid

WoNum

MatID

Date

Qty

Price

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

WOLOCLIST

PK,FK2,I5,I4 WoNum

PK,FK1,I3,I1 UnitID

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

WOEMPLOYEE

PK,FK2,I5,I4 WoNum

PK,FK1,I2,I1 EmpID

PK Date

LaborGrp

RegHours

OTHours

RegRate

OTRate

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

VALVEGRP

PK Group

Desc

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

PRBCDE

PK PrbCde

Description

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

MSysAccessXML

PK Id

LValue

U1 ObjectGuid

U2 ObjectName

U2,U1 Property

Value

MAINTRACER_Conflict

I1 ConflictRowGuid

MainID

UnitID

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

HYDTYPE

PK HydType

Description

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

HYDRANT_Conflict

I1 ConflictRowGuid

UnitID

Old_UnitID

HydType

ShutOffV

MainID

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

MainSize

Location

Area

PressZone

SerialNum

ModelNum

Manufacturer

Size

VendorID

DateInst

WarrantyDate

Life

OriginalCost

ReplacementCost

SpecInst

Inspector

Color

Height

ApprovedToFill

C3

Project

MapLoc

MapIndex

CautionCode

Active

ConditionCode

LastInspDate

Status

CoFScore

StatusDate

CoFDate

ExpireDate

ProjectType

ConfinedSpaceType

CkDate

CkBy

NewUser

NewDate

LChgUser

LChgDate

Aen_SpecInst

Ben_SpecInst

Gen_SpecInst

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

EQUIPMENT_Conflict

I1 ConflictRowGuid

UnitID

Description

Type

Location

SerialNum

ModelNum

Manufacturer

Domicile

KeyBoxNum

PurchDate

PurchCost

ChgAmount

Life

PricingDate

AssignedTo

PricingAmount

UsedBy

Year

LicenseNo

Dept

FuelType

Emergency

Unit

AdditionalCostDate

AdditionalCostAmt

AdditionalCosts

Inuse

Status

StatusDate

ExpireDate

NewUser

NewDate

LChgUser

LChgDate

Note

Gen_AdditionalCosts

Aen_AdditionalCosts

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

EMPLOYEE

PK,I1 EmpID

EmpCde

FK1,I2 LaborGrp

FirstName

LastName

RegRate

OTRate

Active

ExpireDate

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

BEAMWIDTH

Width

Fraction

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

Water Mains Age

Age

Length Pct

SumOfLength

Total Length

WOEQUIPMENT

PK,FK1,I4,I3 WoNum

PK,I2 UnitID

PK Date

Hours

Rate

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

tblHydrantTurbidityTests

PK,I1 FlushID

PK TestDateTime

Turbidity

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

SERVTYPE

PK ServType

Description

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

LOCSTATION_Conflict

I1 ConflictRowGuid

UnitID

Old_UnitID

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

BoxMaterial

Location

Measurements

Area

MainID

DateInst

WarrantyDate

Inspector

Comments

Project

ProjectType

ConfinedSpaceType

MapLoc

MapIndex

CautionCode

CkDate

CkBy

Active

ConditionCode

LastInspDate

Status

CoFScore

NewUser

CoFDate

NewDate

LChgUser

LChgDate

StatusDate

ExpireDate

Aen_Comments

Gen_Comments

Gen_Measurements

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

HYDRANT

PK,I12 UnitID

I8 Old_UnitID

FK3,I5 HydType

ShutOffV

I6 MainID

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

MainSize

Location

Area

PressZone

I10 SerialNum

FK2,I7,I4 ModelNum

FK1,I3 Manufacturer

Size

I13 VendorID

DateInst

WarrantyDate

Life

OriginalCost

ReplacementCost

SpecInst

Inspector

Color

Height

ApprovedToFill

C3

Project

MapLoc

MapIndex

I1 CautionCode

I2 ConditionCode

LastInspDate

CoFScore

CoFDate

Active

I11 Status

StatusDate

ExpireDate

ProjectType

ConfinedSpaceType

CkDate

CkBy

Aen_SpecInst

NewUser

NewDate

Gen_SpecInst

LChgUser

LChgDate

s_ColLineage

I9 s_Generation

U1 s_GUID

s_Lineage

HydrantsOn4InchOrSmallerMains

UnitID

MainSize

STREETNO

STREETNAME

Status

LEAKDATAHYDRANT

PK,I2 WoNum

LeakType

LeakMaterial

NoServ

TimeOutage

FeetCorrelated

PipeDiam

DetectionMethod

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

FIRM

I1 FirmNum

FirmName

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

CONFINEDSPACETYPE

PK ConfinedSpaceType

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

WTP_CPs

Location

UnitID

Area

ReadingDate

PSVolts1

PSVolts2

PSVolts3

PSVolts4

PSVolts5

PSVolts6

AnodeCurrent

WOMAINLIST

PK,FK2,I5,I4 WoNum

PK,FK1,I2,I1 MainID

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

WOACCESSLIST

PK,FK2,I4,I5 WoNum

PK,FK1,I3,I1 UnitID

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

VALVETRACER

PK,FK2,I5,I4 ValveUnitID

PK,FK1,I3,I1 TracerUnitID

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

USER_DATA_ENTRY_DEFAULT

PK UserName

Area

DateInst

WarrantyDate

Inspector

Project

MapLoc

MapIndex

ProjectType

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

PROJECT

PK,I1 ProjectNum

Description

ProjectType

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

MAINCONDITION

PK,I1 ConditionCode

Description

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

LEAKDATAMAIN_Conflict

I1 ConflictRowGuid

WoNum

LeakType

LeakMaterial

BeamWidth

DistanceAround

LongWidth

LongLength

HoleDiam

PSI

EstDaysLeaking

NoServ

TimeOutage

FeetCorrelated

PipeDiameter

DetectionMethod

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

INFLATION_FACTOR

InflationFactor

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

CAUTIONCDE

PK,I1 CautionCode

Description

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

tblHydrantChlorineTests

PK,I1 FlushID

PK TestDateTime

Chlorine

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

oldtblPix

PK,I1 ID

I3 WoNum

Attachment

Gen_Attachment

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

MAPLOC

PK MapLoc

LocDesc

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

DEVREV

PK,I4 IdNum

I2 FileNum

Project

Location

I3 FirmNum

Type

Signed

Basin

Note

WMTapComment

WSTapComment

Rating

I1 EngNum

AccptDate

Repay

RepayNote

Irrigation Tap

Aen_Note

Gen_Note

s_ColLineage

I5 s_Generation

U1 s_GUID

s_Lineage

CPSTATBOXMTRL

PK BoxMaterial

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

New

MatID

StkNum

Description

Units

Cost

WOSLLIST

PK,FK1,I4,I3 WoNum

PK,I2 ServLineID

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

SHUNTTYPE

PK ShuntType

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

MAINTYPE

PK MainType

Description

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

LEAKDATAVALVE

PK,I2 WoNum

LeakType

LeakMaterial

NoServ

TimeOutage

FeetCorrelated

PipeDiam

DetectionMethod

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

FUELTYPE

PK FuelType

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

CPDATA

PK,FK1,I2,I1 CPID

PK ReadingDate

PSVolts1

PSVolts2

PSVolts3

PSVolts4

PSVolts5

PSVolts6

AnodeCurrent

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

CONTRACTOR

PK,I1 CompNum

Company

Attention

Address1

Address2

Phone

Note

Active

Gen_Note

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

tblNextNodeNumber

NextNodeNumber

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

MAINMANUF

PK Manufacturer

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

LOCSTATBOXMTRL

PK BoxMaterial

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

INFLATIONRATE

PK InflationRate

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

ACTCDE

PK ActCde

Description

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

WOMAINLIST_Conflict

I1 ConflictRowGuid

WoNum

MainID

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

WOEQUIPMENT_Conflict

I1 ConflictRowGuid

WoNum

UnitID

Date

Hours

Rate

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

WOEMPLOYEE_Conflict

I1 ConflictRowGuid

WoNum

EmpID

Date

LaborGrp

RegHours

OTHours

RegRate

OTRate

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

WOCONTRACT

PK,FK1,I3,I2 WoNum

PK Contractor

PK Date

Hours

Rate

Materials

Labor

Total

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

VALVETYPE

PK ValveType

Description

FK1,I3,I1 Group

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

PROJECTTYPE

PK ProjectType

Description

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

MAIN_Conflict

I1 ConflictRowGuid

MainID

MainType

UniqueID

BLOCKNO

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

MAINDIR

PipeType

PipeDiameter

Location

Area

PressZone

Manufacturer

Length

DateInst

WarrantyDate

Depth

SpecInst

Inspector

CP

C3

Project

MapLoc

MapIndex

CautionCode

ConditionCode

LastInspDate

Active

CoF

CoFScore

CoFDate

Status

StatusDate

ExpireDate

ProjectType

ConfinedSpaceType

CkDate

CkBy

NewUser

NewDate

LChgUser

LChgDate

Gen_SpecInst

Ben_SpecInst

Aen_SpecInst

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

EQUIPTYPE

PK EquipType

DefaultLife

RollingStock

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

CRITCDE

PK CritCde

Description

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

COMPACT

PK Comp

PK,FK1,I1 ActCde

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

qryResidualChlorine

HydrantNodeNumber

Concerns

PRESSZONE

PREM

WOHYDMTRREQ_Conflict

I1 ConflictRowGuid

WoNum

TakenBy

Contact

Phone

SubName

Use

Size

SetDate

SetTime

SetBy

RemovDate

RemovTime

RemovNote

LocateReq

LocateApp

Direction

HWrenchIssued

HMeterChained

RateExlp

RespExlp

UnitId

DateRem

DateInst

SetRdg

RemRdg

WtrUse

Gal

GalTot

KGalRate

Rental

DailyRate

RenTotal

TripRate

Trips

TripTot

Other

OtherTot

Note

HydUnitID

Aen_Note

Gen_Note

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

tblHydrantFlush

PK,I2 FlushID

PK HydrantNodeNumber

PK FlushStartDateTime

I1 CrewID

LooksClearDateTime

StaticPressure

DrainageIssues

Concerns

GaveUpOnTurbidity

GaveUpOnChlorine

FromValveNumber

Dechlorinated

Residual

ResidualAfterDeChlorination

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

SLPIPETYPE

PK PipeType

Description

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

MATERIAL

PK,I1 MatID

Description

Units

Price

Active

ExpireDate

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

MAINVALVE

PK,FK1,I2,I1 MainID

PK,I4 ValveID

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

HOLEDIAM

PK HoleDiam

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

ENGINEER

I1 EngNum

EngName

EngName2

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

Wums

MatID

Description

Units

Price

Active

ExpireDate

WOSLLIST_Conflict

I1 ConflictRowGuid

WoNum

ServLineID

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

tblPix

I1 ID

I3 WoNum

Attachment

Gen_Attachment

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

OPERATINGINSTR

PK,I1 Comp

PK,I2 Id

OperatingInstr

Gen_OperatingInstr

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

LOCSTATION

PK,I7 UnitID

I5 Old_UnitID

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

FK1,I3 BoxMaterial

Location

Measurements

Area

I4 MainID

DateInst

WarrantyDate

Inspector

Comments

Project

ProjectType

ConfinedSpaceType

MapLoc

MapIndex

I1 CautionCode

CkDate

CkBy

I2 ConditionCode

LastInspDate

CoFScore

CoFDate

Active

Status

NewUser

NewDate

Aen_Comments

LChgUser

LChgDate

Gen_Comments

StatusDate

ExpireDate

Gen_Measurements

s_ColLineage

I6 s_Generation

U1 s_GUID

s_Lineage

LEAKDATAMAIN

PK,I2 WoNum

LeakType

LeakMaterial

BeamWidth

DistanceAround

LongWidth

LongLength

HoleDiam

PSI

EstDaysLeaking

NoServ

TimeOutage

FeetCorrelated

PipeDiameter

DetectionMethod

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

INSPECTOR

PK,I1 InspID

FName

LName

CellPhone

HomePhone

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

Query1

PressZone

WumsServLineInvID

VALMANUF

PK Manufacturer

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

MAINPIPETYPE

PK PipeType

Description

LifeExpectancy

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

LONGWIDTH

PK Width

Faction

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

CustomersInPressureZone

PremID

WumsServLineInvID

COMPACTPRBCDE

PK,FK1,I1 Comp

PK,FK1,I1 ActCde

PK PrbCde

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

AREA

PK Area

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

Query2

PressZone

WumsServLineInvID

WOMATERIAL

PK,FK2,I5,I4 WoNum

PK,FK1,I1,I2 MatID

PK Date

Qty

Price

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

WO

PK,I4 WoNum

CompType

ActCde

FK1,I2 PrbCde

Project

ProjectType

Area

Priority

SchedStartDate

AssignedTo

RequestDate

Originator

CompletionDate

CallTime

ContactTime

ArrivalTime

CallName

CallPhone

Comments

I1 CompNum

Company

Attention

Address1

Address2

Aen_Comments

Phone

RevAcct

MapLocationX

MapLocationY

MapLocationPlacedBy

Gen_Comments

MapLocationDate

s_ColLineage

I3 s_Generation

U1 s_GUID

s_Lineage

STATUS

PK StatCde

Desc

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

REVACCT

PK RevAcct

Fund

Center

AccountNo

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

Query3

PressZone

WumsServLineInvID

Chlorine

HydrantNodeNumber

FlushStartDateTime

GaveUpOnChlorine

Dechlorinated

TestDateTime

Chlorine

MAINVALVE_Conflict

I1 ConflictRowGuid

MainID

ValveID

s_ColLineage

I2 s_Generation

I3 s_GUID

s_Lineage

LOCATE

PK TicketNo

Foreman

County

City

Address

Inters

Type2

Rem

Other

Other1

Other2

Area

GasDate

ElecDate

USWestDate

CableDate

WaterDate

SewerDate

OthDate

OthDate1

OthDate2

GasTime

ElecTime

USWestTime

CableTime

WaterTime

SewerTime

OthTime

OthTime1

OthTime2

Type

Date

PSDate

PSTime

Meet

AmPm

MeetLoc

AMDate

Cancelled

CanDate

Emerg

EmergDate

InterDate

InterTime

Gen_Rem

Gen_Type2

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

HYDMANUF

PK Manufacturer

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

FILEAKA

I1 FileNum

FileName

s_ColLineage

I2 s_Generation

U1 s_GUID

s_Lineage

EQUIPMENT

PK,I8 UnitID

Description

FK2,I2 Type

Location

I7 SerialNum

I5 ModelNum

Manufacturer

Domicile

I4 KeyBoxNum

PurchDate

PurchCost

PricingDate

PricingAmount

Life

ChgAmount

AssignedTo

UsedBy

Year

LicenseNo

FK1,I1 Dept

FK3,I3 FuelType

Emergency

Unit

AdditionalCostDate

AdditionalCostAmt

AdditionalCosts

Inuse

Status

StatusDate

ExpireDate

NewUser

NewDate

LChgUser

Gen_AdditionalCosts

s_ColLineage

LChgDate

Note

I6 s_Generation

U1 s_GUID

s_Lineage

DEFAULTVALUE

TripRate

DailyRate

WaterRate

s_ColLineage

I1 s_Generation

U1 s_GUID

s_Lineage

CP

PK,I10 UnitID

I5 Old_UnitID

STREETNO

STREETNOHALF

STREETDIR

STREETNAME

TYPESITE

STREETSUFX

APARTNO

FK1,I3 BoxMaterial

Location

Measurements

Area

FK2,I7 ShuntType

I4 MainID

DateInst

WarrantyDate

Inspector

Comments

Project

FK3,I9 TestStationType

ProjectType

ConfinedSpaceType

MapLoc

MapIndex

I1 CautionCode

CkDate

CkBy

I2 ConditionCode

LastInspDate

CoFScore

CoFDate

Active

I8 Status

NewUser

NewDate

Aen_Comments

LChgUser

LChgDate

Gen_Comments

StatusDate

ExpireDate

Gen_Measurements

s_ColLineage

I6 s_Generation

U1 s_GUID

s_Lineage

Water (WUMS) ERD

Water CMMS Sample Screenshot

Water CMMS Sample Screenshot

MDI.MAINT_ALIAS

MDI.MAINT_CAL

MDI.MAINT_CALINSTR

MDI.MAINT_CLASS

MDI.MAINT_DRAWING

MDI.MAINT_EMP

MDI.MAINT_EQTYPE MAINT_EQUIP_COND_DEFINITION

MDI.MAINT_ID

MDI.MAINT_ID_ALIAS

MDI.MAINT_INVTYPE

MDI.MAINT_INVY

MDI.MAINT_PERIOD

MDI.MAINT_PRIORITY

MDI.MAINT_PROBCDE

MDI.MAINT_PROCESS_AREA

MDI.MAINT_ROS

MDI.MAINT_SCHEDTYPE

MDI.MAINT_TASK

MDI.MAINT_TASKID

MDI.MAINT_TASKITEM

MDI.MAINT_VENDOR

MDI.MAINT_WO

MDI.MAINT_WOCONT

MDI.MAINT_WOCONT_HISTORY

MDI.MAINT_WOE

MDI.MAINT_WOE_HISTORY

MDI.MAINT_WOGENMDI.MAINT_WOID

MDI.MAINT_WOID_HISTORY

MDI.MAINT_WOITEM

MDI.MAINT_WOITEM_HISTORY

MDI.MAINT_WOTASK

MDI.MAINT_WOTYPE

MDI.MAINT_WO_CATEGORY

MDI.MAINT_WO_COSTS

MDI.MAINT_WO_EMAIL

MDI.MAINT_WO_HISTORY

MDI.MAINT_WO_STATUS

MDI.MAINT_ZONE

MDI.MDI_DEFAULT_PRINTER

MDI.MDI_STATUS_PROFILE

MAINT_EQUIP_CONDITION

MAINT_EQUIP_CONDITION_COMMENTS

MDI.PRINT_REPORT

MDI.UTILITY_DEPARTMENTS

MDI ER DiagramAuthor: Rick MorfordDate: 07/29/2010

Water Treatment Facility: Tag count: 4511

Work Order count: 19311

Waste Water Treatment Facility:

Tag count: 4169

Work Order count: 27705

Maintenance ID/Tag table column list: "ID" VARCHAR2(15 BYTE),

"DRAWINGNUM" VARCHAR2(10 BYTE),

"PARENTID" VARCHAR2(15 BYTE),

"EQTYPE" VARCHAR2(16 BYTE),

"DESCRIPTION" VARCHAR2(255 BYTE),

"UCASEDESC" VARCHAR2(255 BYTE),

"SYSTEM" VARCHAR2(40 BYTE),

"PHYSLOCATION" VARCHAR2(100 BYTE),

"ZONE" VARCHAR2(4 BYTE),

"DESCRIPTOR" VARCHAR2(255 BYTE),

"POWERSOURCE" VARCHAR2(40 BYTE),

"PLC" VARCHAR2(20 BYTE),

"SERIALNUM" VARCHAR2(255 BYTE),

"MODELNUM" VARCHAR2(255 BYTE),

"MANUFACTURER" VARCHAR2(255 BYTE),

"STARTUPDATE" DATE,

"REFLIBNUM" VARCHAR2(50 BYTE),

"CITYBIDNUM" VARCHAR2(15 BYTE),

"NOTE" VARCHAR2(4000 BYTE),

"CLASS" CHAR(1 BYTE),

"INSERVICE" NUMBER,

"UPDATEDRAWING" NUMBER,

"UPDATEDWGDATE" DATE,

"UPDATEDWGUSER" VARCHAR2(50 BYTE),

"UPDATEDATA" NUMBER,

"UPDATEDATADATE" DATE,

"UPDATEDATAUSER" VARCHAR2(50 BYTE),

"MISC01" VARCHAR2(50 BYTE),

"MISC02" VARCHAR2(50 BYTE),

"MISC03" VARCHAR2(50 BYTE),

"MISC04" VARCHAR2(50 BYTE),

"MISC05" VARCHAR2(50 BYTE),

"MISC06" VARCHAR2(50 BYTE),

"MISC07" VARCHAR2(50 BYTE),

"MISC08" VARCHAR2(50 BYTE),

"MISC09" VARCHAR2(50 BYTE),

"MISC10" VARCHAR2(50 BYTE),

Plant CMMS (MDI) Fields

"MISC11" VARCHAR2(50 BYTE),

"MISC12" VARCHAR2(50 BYTE),

"MISC13" VARCHAR2(50 BYTE),

"MISC14" VARCHAR2(50 BYTE),

"MISC15" VARCHAR2(255 BYTE),

"MISC16" VARCHAR2(50 BYTE),

"MISC17" VARCHAR2(50 BYTE),

"MISC18" VARCHAR2(50 BYTE),

"MISC19" VARCHAR2(50 BYTE),

"MISC20" VARCHAR2(50 BYTE),

"MISC21" VARCHAR2(50 BYTE),

"MISC22" VARCHAR2(50 BYTE),

"MISC23" VARCHAR2(50 BYTE),

"MISC24" VARCHAR2(640 BYTE),

"MISC25" VARCHAR2(640 BYTE),

"MISC26" VARCHAR2(640 BYTE),

"MISC27" VARCHAR2(50 BYTE),

"MISC28" VARCHAR2(50 BYTE),

"MISC29" VARCHAR2(50 BYTE),

"MISC30" VARCHAR2(50 BYTE),

"MISC31" VARCHAR2(50 BYTE),

"MISC32" VARCHAR2(80 BYTE),

"MISC33" VARCHAR2(50 BYTE),

"MISC34" DATE,

"MISC35" DATE,

"MISC36" NUMBER,

"MISC37" NUMBER,

"UPDATEDRAWING_YES_NO" VARCHAR2(3 BYTE),

"UPDATEDATA_YES_NO" VARCHAR2(3 BYTE),

"DEPTNO" NUMBER,

"PROCESS_AREA" VARCHAR2(40 BYTE),

"AMPS" VARCHAR2(80 BYTE),

"GEAR_RATIO" VARCHAR2(10 BYTE),

"REGISTER_NUM" VARCHAR2(6 BYTE),

"GPM" VARCHAR2(20 BYTE),

"PO_NUM" VARCHAR2(50 BYTE),

"MOTOR_STARTUPDATE" DATE,

"HORSEPOWER" VARCHAR2(50 BYTE),

"VOLTAGE" VARCHAR2(50 BYTE),

"RPM" VARCHAR2(50 BYTE),

"MOTOR_MANUF" VARCHAR2(255 BYTE),

"MOTOR_SERIALNUM" VARCHAR2(255 BYTE),

"MOTOR_PONUM" VARCHAR2(50 BYTE),

"MOTOR_MODELNUM" VARCHAR2(255 BYTE),

"MCC_NUM" VARCHAR2(50 BYTE),

"ROOM_LOCATION" VARCHAR2(50 BYTE),

Plant CMMS (MDI) Fields

"FACILITY" VARCHAR2(50 BYTE),

"PIPE_SIZE" VARCHAR2(50 BYTE),

"INSTALLDATE" DATE,

"COST" NUMBER,

"MATERIAL" VARCHAR2(50 BYTE),

"CONDITION" VARCHAR2(50 BYTE),

"ELEVATION" VARCHAR2(50 BYTE),

"NORTH" VARCHAR2(50 BYTE),

"EAST" VARCHAR2(50 BYTE),

"LATITUDE" VARCHAR2(50 BYTE),

"LONGITUDE" VARCHAR2(50 BYTE),

"DRAWING" VARCHAR2(50 BYTE)

Maintenance Work Order table column list: "WONUM" NUMBER,

"TASKNUM" NUMBER,

"TASKDESC" VARCHAR2(4000 BYTE),

"WOTYPE" VARCHAR2(2 BYTE),

"SCHEDSTARTDATE" DATE,

"SCHEDFINISHDATE" DATE,

"ASSIGNEDTO" VARCHAR2(40 BYTE),

"PRIORITY" NUMBER,

"PROBCDE" VARCHAR2(5 BYTE),

"STATUS" NUMBER NOT NULL ENABLE,

"STATUSDATE" DATE,

"CLOSEDCAT" VARCHAR2(3 BYTE),

"REQSTAT" NUMBER,

"AUTH1" VARCHAR2(50 BYTE),

"AUTH2" VARCHAR2(50 BYTE),

"PROJECT" VARCHAR2(15 BYTE),

"REQUESTDATE" DATE,

"ORIGINATOR" VARCHAR2(40 BYTE),

"ESTHRS" NUMBER,

"ESTMAT" NUMBER,

"LOGINID" VARCHAR2(50 BYTE),

"PRINTED" NUMBER,

"NOTE" VARCHAR2(4000 BYTE),

"LASTUSER" VARCHAR2(50 BYTE),

"LASTUPDATE" DATE,

"DEPTNO" NUMBER,

Plant CMMS (MDI) Fields

09/20/2011 11:45:19 AMDate Printed:1Page:

62511WO #:

9925Task#: Clean cabinet inside and out

MechanicalWork Group: Preventive (Facility)

09/01/2011Request Date:

09/15/2011 NAZone:

3

Reason:

Supervisor:

3_RES respirator inspection

Clean cabinet inside and out

Inspect harness,cylinder,and regulator

Do flow test

Check cylinder pressure fill if below 3500 on 4500

Report any problem to your supervisor.

Bring broken or worn parts to Scott for repairs and or replacement.

Note

Instructions

Comments:

Cost InformationDate Emp Code Reg Hrs Ot Hrs Material Code Qty Used

Date Completed:

ID #: Description: Physical Location:Equipment Information

Scheduled Start: Priority:

Plant CMMS (MDI) Sample Work Order Form

Completed Work Orders ReportBetween 06/01/2009 And 09/17/2009

1Page: of

Total Report Hours: 641.6 89Total Report Work Orders:

10

46492

54038

54251

54117

53914

53915

53869

53625

53763

47710

WO #:

WO #:

WO #:

WO #:

WO #:

WO #:

WO #:

WO #:

WO #:

WO #:

6294Task #:

Task #:

Task #:

Task #:

Task #:

Task #:

Task #:

Task #:

Task #:

Task #:

09/14/2009

09/14/2009

09/10/2009

09/08/2009

09/01/2009

09/01/2009

08/31/2009

08/27/2009

08/25/2009

08/24/2009

Completion Date:

Completion Date:

Completion Date:

Completion Date:

Completion Date:

Completion Date:

Completion Date:

Completion Date:

Completion Date:

Completion Date:

Instr & Electrical

Instr & Electrical

Instr & Electrical

Instr & Electrical

Instr & Electrical

Instr & Electrical

Instr & Electrical

Instr & Electrical

Instr & Electrical

Instr & Electrical

Work Grp:

Work Grp:

Work Grp:

Work Grp:

Work Grp:

Work Grp:

Work Grp:

Work Grp:

Work Grp:

Work Grp:

Safety

Process (tag < ???999)

Calibration

Process (tag < ???999)

Process (tag < ???999)

Process (tag < ???999)

Process (tag < ???999)

Plant Projects, Security

Process (tag < ???999)

Facility (tag > ???999)

Reason:

Reason:

Reason:

Reason:

Reason:

Reason:

Reason:

Reason:

Reason:

Reason:

Have Poudre fire authority test their Opticom front gate interface

Flow meter starts off reading at full flow, but then drops off to the point that

the filter goes into automatic backwash. This occurred after only two hours in

this case.

Ph meter is reading about 0.26 units too high. Instr reading 8.12 , lab result

7.82, later second grab sample: Instr reading 8.12, lab result 7.89.

Reading spikes up multiple times per day, causing pH and alk control problems.

Instr reading low. Instr reading 0.44 mg/l, lab resul was 1.03 mg/l.

Inst reading high. Instr reading was 7.02, lab results were 6.67.

Filter #7 is not coming up to the full flow set point. In this case it should have

came up to 3.273 MGD, but only made it to 2.110 MGD. Got filter 607 effluent flow

low alarm. This was the second time this occurred.

New unit is being installed. Need to run 480 Volt power to it. Unit pulls 4.5

ampns at 480 volt.

Instr reading high. Instr reading 1.03 NTU, lab value 0.54 NTU.

Outlet cover on outside outlet, westside of polymer room, near corner of building

will not close. Outlet is not weatherproof in current state.

Description:

Description:

Description:

Description:

Description:

Description:

Description:

Description:

Description:

Description:

Hours:

Hours:

Hours:

Hours:

Hours:

Hours:

Hours:

Hours:

Hours:

Hours:

SGO1001

F613

H901

A702

R731

H531

F607

ADU111

N311

WS_150

Tag #:

Tag #:

Tag #:

Tag #:

Tag #:

Tag #:

Tag #:

Tag #:

Tag #:

Tag #:

1.0

2.0

1.0

2.0

2.5

1.0

2.0

31.0

0.1

1.0

Tested this with Dave Lehman

Adjusted limits

AF 8.10, AL 7.83

Replaced sample valve and unit seems to be performing better.

Polished membrane, calibrated twice. Instrument reading 1.06, work complete.

Calibrated, instrument reading 6.75. Work complete.

Drained filter down and removed flow tube, cleaned out pressure lines to transmitte

ordered parts 8-20-09 installed conduit and hooked up power. will hook up unit when

As per our QA/QC procedure, this will be addressed during the normal frequency cali

outlet cover was stuck, freed up cover

Note:

Note:

Note:

Note:

Note:

Note:

Note:

Note:

Note:

Note: