Exhibit_1_-_Detailed_System_Application_Requirements.xlsm
XLSM spreadsheet 669 KB Posted
- Attached to
- Enterprise Asset Management - Software & Implementation State and local contract opportunity
- Solicitation number
- RFP 26-0007
- Issued by
- Maricopa County, Phoenix City, Arizona
About this file
The file is an Excel spreadsheet titled "Exhibit_1_-_Detailed_System_Application_Requirements.xlsm" related to the City of Phoenix's Enterprise Asset Management (EAM) software and implementation project. The document provides a comprehensive, detailed breakdown of system requirements across multiple functional areas including Work Management, Asset Management, Preventative Maintenance, Supply Chain, Resource Management, Fleet Management, Mobile Workforce, Views and Analytics, and Technical Characteristics. The spreadsheet meticulously catalogs 2,894 specific requirements with prioritization, complexity levels, vendor response codes, and point allocations, covering aspects such as work order processing, asset tracking, maintenance scheduling, resource allocation, mobile field operations, and reporting capabilities.
The requirements document reflects a sophisticated, multi-departmental approach targeting integration across Aviation, Public Works, Street Transportation, and Water Services departments. Each requirement is systematically categorized with priority levels (High, Medium, Low), response complexity (Simple to Very Complex), and vendor response options (Base Feature, Configuration, User Defined Field, etc.). The system seeks comprehensive functionality with mandatory integration capabilities with existing systems like SAP, PeopleSoft, HARS, SCADA, and GIS, emphasizing robust security protocols, real-time data synchronization, and flexible configuration options. The requirements suggest a complex technological ecosystem designed to support extensive asset management across multiple municipal operations, with a strong focus on scalability, user-defined customization, and comprehensive reporting and analytics capabilities.
View the file
Other files for this state and local contract opportunity
Show all 50
Enterprise Asset Management - Software & Implementation has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Set-Up
| # | Include | Tab Name | Tab Description | 🔗 | ------Permanent ID------ | Highest | Starting Counts | Added | Deleted | Masked | Ending Counts | No Priority Assigned | % Complete | Priority | Unused Priorities | Unadj Maximum Points | Unadj Percent | Weight | Adj Maximum Points | Adj Percent | Vendor Response | Description | Complex | Description | Current State | Description | Minimum % Match | Activate Error Checking | √ | Priority | Description | Flag if Response > | Flag if No Response | Flag if Comment | Vendor Response | ||||||||||||||
| (DO NOT CHANGE HERE) | Prefix | Next # | Next ID | Row | S | H | M | L | I | 6 | 7 | 8 | 9 | From | To | Color | A | B | C | ||||||||||||||||||||||||||||||
| 1 | √ | Work Mgmt | Work Management Requirements | 🔗 | 909 | 882 | - 0 | - 0 | - 0 | 882 | - 0 | - 0 | 821 | 18 | 43 | - 0 | - 0 | - 0 | - 0 | - 0 | 8,386 | 34.0% | 1.00 | 8,386 | 34.0% | Base | Base Feature | Simple | Simple | C | Currently Available | 0% | 0% | R | Auto-Assign Permanent Numbers | √ | S | Strategic - Must Have | B | √ | √ | 25 | 15 | 0 | |||||
| 2 | √ | Asset Mgmt | Asset Management Requirements | 🔗 | 536 | 514 | - 0 | - 0 | - 0 | 514 | 3 | - 0 | 458 | 9 | 44 | - 0 | - 0 | - 0 | - 0 | - 0 | 4,713 | 19.1% | 1.00 | 4,713 | 19.1% | Configuration | Configuration | x | Moderate | Moderate | M | Manual Process | 1% | 50% | Y | H | High - Must Have | C | √ | √ | 10 | 5 | 0 | ||||||
| 3 | √ | Maintenance | Preventative Maintenance Requirements | 🔗 | 241 | 230 | - 0 | - 0 | - 0 | 230 | - 0 | - 0 | 217 | 7 | 6 | - 0 | - 0 | - 0 | - 0 | - 0 | 2,217 | 9.0% | 1.00 | 2,217 | 9.0% | UDF | User Defined Field | x | Complex | Complex | N | Cannot Do Today | 51% | 99% | LG | Show Vendor Match Colors | X | M | Medium - Important | √ | √ | 5 | 2 | 0 | |||||
| 4 | √ | Supply Chain | Supply Chain Requirements | 🔗 | 330 | 314 | - 0 | - 0 | - 0 | 314 | 4 | - 0 | 157 | 71 | 80 | 2 | - 0 | - 0 | - 0 | - 0 | 2,085 | 8.4% | 1.00 | 2,085 | 8.4% | Product Calendar | Product Calendar | Very Complex | Very Complex | F | Future Requirement | 100% | 100% | G | L | Low - Optional | √ | 2 | 1 | 0 | |||||||||
| 5 | √ | Resource Mgmt | Resource Management Requirements | 🔗 | 89 | 82 | - 0 | - 0 | - 0 | 82 | - 0 | - 0 | 64 | 7 | 11 | - 0 | - 0 | - 0 | - 0 | - 0 | 697 | 2.8% | 1.00 | 697 | 2.8% | New Report | New Report | x | N/A | Not Applicable | Protect Password | TMG1 | I | Information Only | 0 | 0 | 0 | ||||||||||||
| 6 | √ | Fleet | Fleet Maintenance Requirements | 🔗 | 80 | 74 | - 0 | - 0 | - 0 | 74 | - 0 | - 0 | - 0 | - 0 | - 0 | 74 | - 0 | - 0 | - 0 | - 0 | - 0 | 0.0% | 1.00 | - 0 | 0.0% | New Interface | New Interface | x | |||||||||||||||||||||
| 7 | √ | Mobile | Mobile Work Force Requirements | 🔗 | 251 | 247 | - 0 | - 0 | - 0 | 247 | - 0 | - 0 | 204 | 23 | 20 | - 0 | - 0 | - 0 | - 0 | - 0 | 2,195 | 8.9% | 1.00 | 2,195 | 8.9% | Extension | Extension | x | DEL | Delete Requirement | |||||||||||||||||||
| 8 | √ | Views & Analytics | Views and Analytics Requirements | 🔗 | 243 | 219 | - 0 | - 0 | - 0 | 219 | - 0 | - 0 | 182 | 11 | 15 | 11 | - 0 | - 0 | - 0 | - 0 | 1,905 | 7.7% | 1.00 | 1,905 | 7.7% | Enhancement | Enhancement | x | |||||||||||||||||||||
| 9 | √ | Technical | Technical Characteristics Requirements | 🔗 | 328 | 308 | - 0 | - 0 | - 0 | 308 | - 0 | - 0 | 202 | 35 | 34 | 37 | - 0 | - 0 | - 0 | - 0 | 2,263 | 9.2% | 1.00 | 2,263 | 9.2% | New Form | New Form | x | |||||||||||||||||||||
| 10 | √ | Portals | Portal Requirements | 🔗 | 29 | 24 | - 0 | - 0 | - 0 | 24 | - 0 | - 0 | 21 | 3 | - 0 | - 0 | - 0 | - 0 | - 0 | - 0 | 225 | 0.9% | 1.00 | 225 | 0.9% | New Workflow | New Workflow | x | |||||||||||||||||||||
| 11 | 3rd-Party App | Third-Party Application | x | DEL | Delete Requirement | Requirements Deleted During Review | |||||||||||||||||||||||||||||||||||||||||||
| 12 | Cannot Meet | Cannot Meet | MASK | Mask Requirement | Requirements Removed (N/A Service) | ||||||||||||||||||||||||||||||||||||||||||||
| 13 | N/A | Not Applicable | REM | Remove from Master (TMG) | Permanently Remove Requirement | ||||||||||||||||||||||||||||||||||||||||||||
| 14 | Vendor Response | Description | Flag if Comment | √ | |||||||||||||||||||||||||||||||||||||||||||||
| 15 | Yes | Yes | |||||||||||||||||||||||||||||||||||||||||||||||
| 16 | No | No | |||||||||||||||||||||||||||||||||||||||||||||||
| 17 | N/A | Not Applicable | |||||||||||||||||||||||||||||||||||||||||||||||
| 18 | |||||||||||||||||||||||||||||||||||||||||||||||||
| 19 | |||||||||||||||||||||||||||||||||||||||||||||||||
| 20 | |||||||||||||||||||||||||||||||||||||||||||||||||
| 21 | |||||||||||||||||||||||||||||||||||||||||||||||||
| 22 | |||||||||||||||||||||||||||||||||||||||||||||||||
| 23 | |||||||||||||||||||||||||||||||||||||||||||||||||
| 24 | |||||||||||||||||||||||||||||||||||||||||||||||||
| 25 | |||||||||||||||||||||||||||||||||||||||||||||||||
| 26 | |||||||||||||||||||||||||||||||||||||||||||||||||
| 27 | |||||||||||||||||||||||||||||||||||||||||||||||||
| 28 | |||||||||||||||||||||||||||||||||||||||||||||||||
| 29 | |||||||||||||||||||||||||||||||||||||||||||||||||
| 30 | |||||||||||||||||||||||||||||||||||||||||||||||||
| 31 | |||||||||||||||||||||||||||||||||||||||||||||||||
| 32 | |||||||||||||||||||||||||||||||||||||||||||||||||
| 33 | |||||||||||||||||||||||||||||||||||||||||||||||||
| 34 | |||||||||||||||||||||||||||||||||||||||||||||||||
| 35 | |||||||||||||||||||||||||||||||||||||||||||||||||
| 36 | |||||||||||||||||||||||||||||||||||||||||||||||||
| Total Count | 2,894 | - 0 | - 0 | - 0 | 2,894 | 7 | 99.76% | - 0 | 2,326 | 184 | 253 | 124 | - 0 | - 0 | - 0 | - 0 | 24,686 | 100% | 24,686 | 100% |
| Base = Base Feature | Simple = Simple |
| Base = Base Feature Configuration = Configuration | Simple = Simple Moderate = Moderate |
| Base = Base Feature Configuration = Configuration UDF = User Defined Field | Simple = Simple Moderate = Moderate Complex = Complex |
| Base = Base Feature Configuration = Configuration UDF = User Defined Field Product Calendar = Product Calendar | Simple = Simple Moderate = Moderate Complex = Complex Very Complex = Very Complex |
| Base = Base Feature Configuration = Configuration UDF = User Defined Field Product Calendar = Product Calendar New Report = New Report | Simple = Simple Moderate = Moderate Complex = Complex Very Complex = Very Complex N/A = Not Applicable |
| Base = Base Feature Configuration = Configuration UDF = User Defined Field Product Calendar = Product Calendar New Report = New Report New Interface = New Interface | Simple = Simple Moderate = Moderate Complex = Complex Very Complex = Very Complex N/A = Not Applicable |
| Base = Base Feature Configuration = Configuration UDF = User Defined Field Product Calendar = Product Calendar New Report = New Report New Interface = New Interface Extension = Extension | Simple = Simple Moderate = Moderate Complex = Complex Very Complex = Very Complex N/A = Not Applicable |
| Base = Base Feature Configuration = Configuration UDF = User Defined Field Product Calendar = Product Calendar New Report = New Report New Interface = New Interface Extension = Extension Enhancement = Enhancement | Simple = Simple Moderate = Moderate Complex = Complex Very Complex = Very Complex N/A = Not Applicable |
| Base = Base Feature Configuration = Configuration UDF = User Defined Field Product Calendar = Product Calendar New Report = New Report New Interface = New Interface Extension = Extension Enhancement = Enhancement New Form = New Form | Simple = Simple Moderate = Moderate Complex = Complex Very Complex = Very Complex N/A = Not Applicable |
| Base = Base Feature Configuration = Configuration UDF = User Defined Field Product Calendar = Product Calendar New Report = New Report New Interface = New Interface Extension = Extension Enhancement = Enhancement New Form = New Form New Workflow = New Workflow | Simple = Simple Moderate = Moderate Complex = Complex Very Complex = Very Complex N/A = Not Applicable |
| Base = Base Feature Configuration = Configuration UDF = User Defined Field Product Calendar = Product Calendar New Report = New Report New Interface = New Interface Extension = Extension Enhancement = Enhancement New Form = New Form New Workflow = New Workflow 3rd-Party App = Third-Party Application | Simple = Simple Moderate = Moderate Complex = Complex Very Complex = Very Complex N/A = Not Applicable |
| Base = Base Feature Configuration = Configuration UDF = User Defined Field Product Calendar = Product Calendar New Report = New Report New Interface = New Interface Extension = Extension Enhancement = Enhancement New Form = New Form New Workflow = New Workflow 3rd-Party App = Third-Party Application Cannot Meet = Cannot Meet | Simple = Simple Moderate = Moderate Complex = Complex Very Complex = Very Complex N/A = Not Applicable |
B = Base Feature C = Configuration U = User Defined Field P = Product Calendar R = New Report I = New Interface E = Extension/Enhancement F = New Form W = New Workflow T = Third-Party Application X = Cannot Meet N/A = Not Applicable S = Simple M = Moderate C = Complex V = Very Complex N/A = Not Applicable
All Requirements
| LEVEL | Permanent ID # | Ref # | Requirement Description | Utility Priority | Vendor Response | Complexity Level | Product (Module) | ||||||||||||||||||||||||||
| & Version | Reference / Comments | Internal Notes | Current State | All Requirements | ROW | FORMAT CONTROL | Tab | Tab | Max | Seq | FORMAT CONTROL | Priority in TCO | Current State | Response | Column | Unadj Points | Priority % | Current State % | Adjusted Points | ||||||||||||||
| Major | WM.0001 | 1. | Work Management Requirements | 1 | Work Mgmt | 909 | 2 | Major | |||||||||||||||||||||||||
| Minor | WM.0002 | 1.1. | Work Management | 1 | Work Mgmt | 909 | 3 | Minor | |||||||||||||||||||||||||
| WM.0003 | 1.1.1 | The solution shall allow users to provide a description of work to be performed. | H | C | H | Mandatory | 1 | Work Mgmt | 909 | 4 | REQ | ERROR:#REF! | ERROR:#REF! | ||||||||||||||||||||
| WM.0004 | 1.1.2 | The solution shall allow the generation of a design/estimate without a work order (financial) or work request number. | L | N | L | Optional | 1 | Work Mgmt | 909 | 5 | REQ | ERROR:#REF! | ERROR:#REF! |
Table of Contents
| Filters: | Worksheet | Level | WORKSHEET | CATEGORY / ▪ SUB CATEGORY | ROW | HYPERLINK | Tab | Tab | Max | Seq | Section | Level | Row | ▪ | [Exhibit_1_-_Detailed_System_Application_Requirements_(2) (1).xlsm] |
| Work Mgmt | Major | Work Mgmt | ҉ | 1 | Work Mgmt | 5 | 1 | 1. Work Management Requirements | Major | 2 | Sub Symbol | ҉ | |||
| Work Mgmt | Minor | 1.1. Work Management ………………………………………………………………………………………………………………………………………………………………………………………… | 3 | ҉ | 1 | Work Mgmt | 5 | 2 | 1.1. Work Management | Minor | 3 | Ͱ | ………………………………………………………………………………………………………………………………………………………………………………………… | ||
| Work Mgmt | Minor | 1.2. Work Planning/ Management ………………………………………………………………………………………………………………………………………………………………………………………… | 377 | ҉ | 1 | Work Mgmt | 5 | 3 | 1.2. Work Planning/ Management | Minor | 377 | ҉ | |||
| Work Mgmt | Minor | 1.3. Work Execution ………………………………………………………………………………………………………………………………………………………………………………………… | 620 | ҉ | 1 | Work Mgmt | 5 | 4 | 1.3. Work Execution | Minor | 620 | → | |||
| Work Mgmt | End | ………………………………………………………………………………………………………………………………………………………………………………………… | 909 | ҉ | 1 | Work Mgmt | 5 | 5 | End | 909 | ▪ | ||||
| Asset Mgmt | Major | Asset Mgmt | ҉ | 2 | Asset Mgmt | 3 | 1 | 2. Asset Management Requirements | Major | 2 | ˧ | ||||
| Asset Mgmt | Minor | 2.1. Asset Management ………………………………………………………………………………………………………………………………………………………………………………………… | 3 | ҉ | 2 | Asset Mgmt | 3 | 2 | 2.1. Asset Management | Minor | 3 | ∆ | |||
| Asset Mgmt | Minor | 2.2. Building Requirements ………………………………………………………………………………………………………………………………………………………………………………………… | 531 | ҉ | 2 | Asset Mgmt | 3 | 3 | 2.2. Building Requirements | Minor | 531 | √ | |||
| Maintenance | Major | Maintenance | ҉ | 3 | Maintenance | 3 | 1 | 3. Preventative Maintenance Requirements | Major | 2 | » | ||||
| Maintenance | Minor | 3.1. Preventative Maintenance ………………………………………………………………………………………………………………………………………………………………………………………… | 3 | ҉ | 3 | Maintenance | 3 | 2 | 3.1. Preventative Maintenance | Minor | 3 | ◊ | |||
| Maintenance | End | ………………………………………………………………………………………………………………………………………………………………………………………… | 241 | ҉ | 3 | Maintenance | 3 | 3 | End | 241 | ● | ||||
| Supply Chain | Major | Supply Chain | ҉ | 4 | Supply Chain | 4 | 1 | 4. Supply Chain Requirements | Major | 2 | |||||
| Supply Chain | Minor | 4.1. Supply Chain ………………………………………………………………………………………………………………………………………………………………………………………… | 3 | ҉ | 4 | Supply Chain | 4 | 2 | 4.1. Supply Chain | Minor | 3 | ||||
| Supply Chain | Minor | 4.2. Contracts Management ………………………………………………………………………………………………………………………………………………………………………………………… | 272 | ҉ | 4 | Supply Chain | 4 | 3 | 4.2. Contracts Management | Minor | 272 | ||||
| Supply Chain | End | ………………………………………………………………………………………………………………………………………………………………………………………… | 330 | ҉ | 4 | Supply Chain | 4 | 4 | End | 330 | |||||
| Resource Mgmt | Major | Resource Mgmt | ҉ | 5 | Resource Mgmt | 3 | 1 | 5. Resource Management Requirements | Major | 2 | |||||
| Resource Mgmt | Minor | 5.1. Resource Management ………………………………………………………………………………………………………………………………………………………………………………………… | 3 | ҉ | 5 | Resource Mgmt | 3 | 2 | 5.1. Resource Management | Minor | 3 | ||||
| Resource Mgmt | End | ………………………………………………………………………………………………………………………………………………………………………………………… | 89 | ҉ | 5 | Resource Mgmt | 3 | 3 | End | 89 | |||||
| Fleet | Major | Fleet | ҉ | 6 | Fleet | 3 | 1 | 6. Fleet Maintenance Requirements | Major | 2 | |||||
| Fleet | Minor | 6.1. Fleet Maintenance ………………………………………………………………………………………………………………………………………………………………………………………… | 3 | ҉ | 6 | Fleet | 3 | 2 | 6.1. Fleet Maintenance | Minor | 3 | ||||
| Fleet | End | ………………………………………………………………………………………………………………………………………………………………………………………… | 80 | ҉ | 6 | Fleet | 3 | 3 | End | 80 | |||||
| Mobile | Major | Mobile | ҉ | 7 | Mobile | 3 | 1 | 7. Mobile Work Force Requirements | Major | 2 | |||||
| Mobile | Minor | 7.1. Mobile Work Force ………………………………………………………………………………………………………………………………………………………………………………………… | 3 | ҉ | 7 | Mobile | 3 | 2 | 7.1. Mobile Work Force | Minor | 3 | ||||
| Mobile | End | ………………………………………………………………………………………………………………………………………………………………………………………… | 251 | ҉ | 7 | Mobile | 3 | 3 | End | 251 | |||||
| Views & Analytics | Major | Views & Analytics | ҉ | 8 | Views & Analytics | 3 | 1 | 8. Views and Analytics Requirements | Major | 2 | |||||
| Views & Analytics | Minor | 8.1. Views and Analytics ………………………………………………………………………………………………………………………………………………………………………………………… | 3 | ҉ | 8 | Views & Analytics | 3 | 2 | 8.1. Views and Analytics | Minor | 3 | ||||
| Views & Analytics | End | ………………………………………………………………………………………………………………………………………………………………………………………… | 243 | ҉ | 8 | Views & Analytics | 3 | 3 | End | 243 | |||||
| Technical | Major | Technical | ҉ | 9 | Technical | 3 | 1 | 9. Technical Characteristics Requirements | Major | 2 | |||||
| Technical | Minor | 9.1. Technical Characteristics ………………………………………………………………………………………………………………………………………………………………………………………… | 3 | ҉ | 9 | Technical | 3 | 2 | 9.1. Technical Characteristics | Minor | 3 | ||||
| Technical | End | ………………………………………………………………………………………………………………………………………………………………………………………… | 328 | ҉ | 9 | Technical | 3 | 3 | End | 328 | |||||
| Portals | Major | Portals | ҉ | 10 | Portals | 3 | 1 | 10. Portal Requirements | Major | 2 | |||||
| Portals | Minor | 10.1. Contractor Portal ………………………………………………………………………………………………………………………………………………………………………………………… | 3 | ҉ | 10 | Portals | 3 | 2 | 10.1. Contractor Portal | Minor | 3 | ||||
| Portals | End | ………………………………………………………………………………………………………………………………………………………………………………………… | 29 | ҉ | 10 | Portals | 3 | 3 | End | 29 |
99. Template Format
| LEVEL | Permanent ID # | Ref # | Requirement Description | Priority | Vendor Response | Complexity Level | Product (Module) | |||||||||||||||||||||||||||||||||||||||||
| & Version | Reference / Comments | Internal Notes | Current State | Complexity Req'd | Business Area: | WSD Priority | City Priority | Public Works | PCC | Aviation | Open | Open | Open | Open | Open | Open | Open | Next Permanent ID | 99. Template Format | ROW | FORMAT CONTROL | MAJOR NUMBER | MINOR NUMBER | SEQUENCE NUMBER | REFERENCE NUMBER | ADDED/ REMOVED | SEQ | LEVEL | TITLE / Y/N | ROW | Priority/ Response | Errors Activated (Set-Up) | √ | Errors/ Warnings | No Response | Bad Response | Check Comment | % Match | Color | New Req. w/o ID | ||||||||
| Major | TP.0001 | 0. | Template Format | ERROR:#N/A | 1 | 2 | Major | 0 | 0 | 0 | 0. | 1 | Major | 0. Template Format | 2 | |||||||||||||||||||||||||||||||||
| Group | TP.0002 | GROUP CATEGORY | 2 | 3 | Group | 0 | 0 | 2 | Group | GROUP CATEGORY | 3 | |||||||||||||||||||||||||||||||||||||
| Minor | TP.0003 | 0.1. | Minor Category | 3 | 4 | Minor | 0 | 1 | 0 | 0.1. | 3 | Minor | 0.1. Minor Category | 4 | ||||||||||||||||||||||||||||||||||
| Sub | TP.0004 | Sub Category | 4 | 5 | Sub | 0 | 1 | 0 | 4 | Sub | Sub Category | 5 | ||||||||||||||||||||||||||||||||||||
| TP.0005 | Does your product provide...: | 5 | 6 | GRP | 0 | 1 | 0 | |||||||||||||||||||||||||||||||||||||||||
| TP.0006 | 0.1.1 | > Electric | H | Configuration | H | Mandatory | 6 | 7 | REQ | 0 | 1 | 1 | 0.1.1 | H/Configuration | WARN1 | ERROR:#REF! | ||||||||||||||||||||||||||||||||
| TP.0007 | 0.1.2 | > Gas? | M | Enhancement | Very Complex | M | Preferred | 7 | 8 | REQ | 0 | 1 | 2 | 0.1.2 | M/Enhancement | ERROR:#REF! | ||||||||||||||||||||||||||||||||
| TP.0008 | 0.1.3 | > Water? | L | UDF | L | Optional | 8 | 9 | REQ | 0 | 1 | 3 | 0.1.3 | L/UDF | ERROR:#REF! | |||||||||||||||||||||||||||||||||
| TP.0009 | 0.1.4 | > New Requirement Added? | I | Base | I | Info Only | 9 | 10 | REQ | 0 | 1 | 4 | 0.1.4 | I/Base | ERROR:#REF! | |||||||||||||||||||||||||||||||||
| TP.0010 | 0.1.5 | > Waste Water? | H | UDF | H | Mandatory | 10 | 11 | REQ | 0 | 1 | 5 | 0.1.5 | H/UDF | WARN1 | ERROR:#REF! | ||||||||||||||||||||||||||||||||
| TP.0011 | 0.1.6 | > Solid Waste? | 11 | 12 | REQ | 0 | 1 | 6 | 0.1.6 | / | ERROR:#REF! | |||||||||||||||||||||||||||||||||||||
| TP.0012 | 0.1.7 | > Storm Water? | 12 | 13 | REQ | 0 | 1 | 7 | 0.1.7 | / | ERROR:#REF! | |||||||||||||||||||||||||||||||||||||
| TP.0013 | 0.1.8 | > Cable? | 13 | 14 | REQ | 0 | 1 | 8 | 0.1.8 | / | ERROR:#REF! | |||||||||||||||||||||||||||||||||||||
| Sub | TP.0014 | Sub Category | 14 | 15 | Sub | 0 | 1 | 8 | 5 | Sub | Sub Category | 15 | ||||||||||||||||||||||||||||||||||||
| TP.0015 | 0.1.9 | Does your product provide xyz? (Y/N) | 15 | 16 | REQ | 0 | 1 | 9 | 0.1.9 | Y/N | / | ERROR:#REF! | ||||||||||||||||||||||||||||||||||||
| TP.0016 | 0.1.10 | Does your product provide abc? (Y/N) | 16 | 17 | REQ | 0 | 1 | 10 | 0.1.10 | Y/N | / | ERROR:#REF! | ||||||||||||||||||||||||||||||||||||
| Group | TP.0017 | GROUP CATEGORY | 17 | 18 | Group | 0 | 0 | 6 | Group | GROUP CATEGORY | 18 | |||||||||||||||||||||||||||||||||||||
| Minor | TP.0018 | 0.2. | Minor Category | 18 | 19 | Minor | 0 | 2 | 0 | 0.2. | 6 | Minor | 0.2. Minor Category | 19 | ||||||||||||||||||||||||||||||||||
| Sub | TP.0019 | Sub Category | 19 | 20 | Sub | 0 | 2 | 0 | 7 | Sub | Sub Category | 20 | ||||||||||||||||||||||||||||||||||||
| TP.0020 | Does your product provide...: | 20 | 21 | GRP | 0 | 2 | 0 | |||||||||||||||||||||||||||||||||||||||||
| TP.0021 | 0.2.1 | > Electric? | 21 | 22 | REQ | 0 | 2 | 1 | 0.2.1 | / | ERROR:#REF! | |||||||||||||||||||||||||||||||||||||
| TP.0022 | 0.2.2 | > Gas? | 22 | 23 | REQ | 0 | 2 | 2 | 0.2.2 | / | ERROR:#REF! | |||||||||||||||||||||||||||||||||||||
| TP.0023 | 0.2.3 | > Water? | 23 | 24 | REQ | 0 | 2 | 3 | 0.2.3 | / | ERROR:#REF! | |||||||||||||||||||||||||||||||||||||
| TP.0024 | 0.2.4 | > Waste Water? | 24 | 25 | REQ | 0 | 2 | 4 | 0.2.4 | / | ERROR:#REF! | |||||||||||||||||||||||||||||||||||||
| TP.0025 | 0.2.5 | > Solid Waste? | 25 | 26 | REQ | 0 | 2 | 5 | 0.2.5 | / | ERROR:#REF! | |||||||||||||||||||||||||||||||||||||
| TP.0026 | 0.2.6 | > Storm Water? | 26 | 27 | REQ | 0 | 2 | 6 | 0.2.6 | / | ERROR:#REF! | |||||||||||||||||||||||||||||||||||||
| TP.0027 | 0.2.7 | > Cable? | 27 | 28 | REQ | 0 | 2 | 7 | 0.2.7 | / | ERROR:#REF! | |||||||||||||||||||||||||||||||||||||
| End | TP.0028 | 28 | 29 | End | 0 | 2 | 7 | 8 | End | 29 | Y |
Insert a New Requirement
Instructions Tab Responses to questions should be as they pertain to the proposed version of the solution or system that is in production use in an environment that is comparable to the City as of the proposal due date. Please provide a Response Code for all requirements and Complexity Code value for all requirements that require additional work to implement. Sample guidelines for complexity values are listed in Exhibit 4.
| Response Codes | Description | |
| B | Base Feature | This requirement currently exists in the proposed version of the solution that is in production use in an environment that is comparable to the City’s and can be demonstrated. |
| C | Configuration | This requirement can be satisfied as a base feature configuration. |
| U | User Defined Field | This requirement can be satisfied with the use of a user-defined field (UDF). |
| P | Product Calendar | This requirement will be available for production use prior to acceptance testing by the City and will be incorporated at no additional charge as part of the baseline solution. |
| R | New or Modified Report | This requirement can be satisfied with either the development of a new report or the modification of an existing report. |
| I | New or Modified Interface | This requirement can be satisfied with either the development of a new interface or the modification of an existing interface. |
| E | Extension/Enhancement | This requirement is not currently available but can be provided as an enhancement to the baseline solution or as an extension or modification. |
| F | New or Modified Form | This requirement can be satisfied with either the development of a new form or the modification of an existing form. |
| W | New or Modified Workflow | This requirement can be satisfied with either the development of a new workflow or the modification of an existing workflow. |
| T | Third-Party Application | This requirement can be satisfied with a third-party application (specify in the application/module column and include any costs in the costing spreadsheet). |
| X | Cannot Meet Requirement | This requirement is not included in the proposed solution (provide a brief explanation of why it cannot be met in the comments column). |
| N/A | Not Applicable | This requirement is not applicable to the proposed solution (provide a brief explanation of why it is not applicable in the comments column). |
| Note 1: If multiple responses apply (e.g., requires a new form and a new report), select the response for the most complex change and adjust the complexity level accordingly based the total effort. | ||
| Note 2: If multiple requirements are satisfied by the same report, extension, etc., indicate the group of requirements that are included in the "Reference / Comments" column. This should also provide a reference to the cost line items in the costing spreadsheet. | ||
| Complexity Codes | Description | |
| S | Simple | This requirement can be satisfied with a simple work effort. |
| M | Moderate | This requirement can be satisfied with a moderate work effort. |
| C | Complex | This requirement can be satisfied with a complex work effort. |
| V | Very Complex | This requirement can be satisfied with a very complex work effort. |
| N/A | Not Applicable | This requirement requires no additional development effort (e.g., Base Feature). |
Work Mgmt
| LEVEL | Permanent ID # | Ref # | Requirement Description | Priority | Vendor Response | Complexity Level | Product (Module) | |||||||||||||||||||||||||||||||||||||||
| & Version | Reference / Comments | Internal Notes | Current State | Business Area: | WSD Priority | City Priority | Public Works | PCC | Aviation | Streets | Open | Open | Open | Open | Open | Open | Next Permanent ID | Work Mgmt | ROW | FORMAT CONTROL | MAJOR NUMBER | MINOR NUMBER | SEQUENCE NUMBER | REFERENCE NUMBER | ADDED/ REMOVED | SEQ | LEVEL | TITLE / Y/N | ROW | Priority/ Response | Errors Activated (Set-Up) | √ | Errors/ Warnings | No Response | Bad Response | Check Comment | % Match | Color | New Req. w/o ID | |||||||
| Major | WM.0001 | 1. | Work Management Requirements | 1 | 2 | Major | 1 | 0 | 0 | 1. | 1 | Major | 1. Work Management Requirements | 2 | ||||||||||||||||||||||||||||||||
| Minor | WM.0002 | 1.1. | Work Management | 2 | 3 | Minor | 1 | 1 | 0 | 1.1. | 2 | Minor | 1.1. Work Management | 3 | ||||||||||||||||||||||||||||||||
| WM.0003 | 1.1.1 | The solution shall allow users to provide a description of work to be performed. | H | C | H | Mandatory | 3 | 4 | REQ | 1 | 1 | 1 | 1.1.1 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0004 | 1.1.2 | The solution shall allow the generation of a design/estimate without a work order (financial) or work request number. | L | N | L | Optional | 4 | 5 | REQ | 1 | 1 | 2 | 1.1.2 | L/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0005 | 1.1.3 | The solution shall enable the drafting, proposing, or modeling of a design, without the design being included in active work management stream. | L | N | L | Optional | 5 | 6 | REQ | 1 | 1 | 3 | 1.1.3 | L/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0006 | 1.1.4 | The solution shall compare multiple work designs for optimum cost. Allow the user to vary items such as equipment, material and labor selection. | L | N | L | Optional | 6 | 7 | REQ | 1 | 1 | 4 | 1.1.4 | L/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0007 | 1.1.5 | The solution shall identify the labor disciplines and skill sets required to complete the work. | H | C | H | Mandatory | 7 | 8 | REQ | 1 | 1 | 5 | 1.1.5 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0008 | 1.1.6 | The solution shall provide gross estimates for labor hours and cost using burdened (with overhead allocations) or unburdened rates. | H | C | H | Mandatory | 8 | 9 | REQ | 1 | 1 | 6 | 1.1.6 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0009 | 1.1.7 | The solution shall identify and record materials required to complete the work. | H | C | H | Mandatory | 9 | 10 | REQ | 1 | 1 | 7 | 1.1.7 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0010 | 1.1.8 | The solution shall provide gross estimates for material cost. | H | C | H | Mandatory | 10 | 11 | REQ | 1 | 1 | 8 | 1.1.8 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0011 | 1.1.9 | The solution shall identify and record any vehicles, special tools or safety equipment required to complete the work. | H | C | H | Mandatory | 11 | 12 | REQ | 1 | 1 | 9 | 1.1.9 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0012 | 1.1.10 | The solution shall provide gross estimates for tool and equipment (including vehicle) hours and cost. | H | C | H | Mandatory | 12 | 13 | REQ | 1 | 1 | 10 | 1.1.10 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0013 | 1.1.11 | The solution shall identify and record any special items such as non-stock material or contractor costs (e.g., trenching crew, contract labor, flaggers). | H | C | H | Mandatory | 13 | 14 | REQ | 1 | 1 | 11 | 1.1.11 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0014 | 1.1.12 | The solution shall provide gross estimates for special items such as non-stock material or contractor costs (e.g., trenching crew, contract labor, flaggers). | H | C | H | Mandatory | 14 | 15 | REQ | 1 | 1 | 12 | 1.1.12 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0015 | 1.1.13 | The solution shall enable the City to provide initial labor, tool and equipment (including vehicles) costs and allow these to be updated at user-defined intervals. | H | C | H | Mandatory | 15 | 16 | REQ | 1 | 1 | 13 | 1.1.13 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0016 | 1.1.14 | The solution shall allow for defined labor classes. | H | F | H | Mandatory | 16 | 17 | REQ | 1 | 1 | 14 | 1.1.14 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0017 | 1.1.15 | The solution shall allow the assigning of employees, workgroups, crews, rotations to a labor class. | H | C | H | Mandatory | Mandatory | Mandatory | Mandatory | Mandatory | 17 | 18 | REQ | 1 | 1 | 15 | 1.1.15 | H/ | ERR1 | |||||||||||||||||||||||||||
| WM.1013 | 1.1.16 | The solution shall allow for work orders to be assigned to more than one individual. | H | H | Mandatory | Mandatory | Mandatory | Mandatory | 1013 | 19 | REQ | 1 | 1 | 16 | 1.1.16 | H/ | ERR1 | |||||||||||||||||||||||||||||
| WM.0018 | 1.1.17 | The solution shall allow material costs to come directly from the inventory system or subsystem and be updated in real time. | H | C | H | Mandatory | 18 | 20 | REQ | 1 | 1 | 17 | 1.1.17 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0019 | 1.1.18 | The solution shall allow designs/estimates to be locked to cost updates once approved. An update can be manually triggered. | H | F | H | Mandatory | 19 | 21 | REQ | 1 | 1 | 18 | 1.1.18 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0020 | 1.1.19 | The solution shall allow for a factor to increase or decrease the estimate such as by work location (e.g., to accommodate travel costs, etc.). | H | F | H | Mandatory | 20 | 22 | REQ | 1 | 1 | 19 | 1.1.19 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0021 | 1.1.20 | The solution shall support the allocation of estimated costs in a design to the City and to the customer. | L | N | L | Optional | 21 | 23 | REQ | 1 | 1 | 20 | 1.1.20 | L/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0022 | 1.1.21 | The solution shall support work authorization approvals based on estimated dollar amount or other user-defined criteria once a design/estimate has been completed. | H | F | H | Mandatory | 22 | 24 | REQ | 1 | 1 | 21 | 1.1.21 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0023 | 1.1.22 | The solution shall configure a supplementary review step If work is re-designed or re-estimated after approval has been obtained and the dollar amount is X% higher or lower than the previously approved amount. | H | F | H | Mandatory | 23 | 25 | REQ | 1 | 1 | 22 | 1.1.22 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0024 | 1.1.23 | The solution shall allow the above to be configurable by work type and/or department. | H | F | H | Mandatory | 24 | 26 | REQ | 1 | 1 | 23 | 1.1.23 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0025 | 1.1.24 | The solution shall provide for the viewing and printing of a bill of material. | H | C | H | Mandatory | 25 | 27 | REQ | 1 | 1 | 24 | 1.1.24 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0026 | 1.1.25 | The solution shall allow for the entry of the crew size and type (City or contractor, etc.) required to complete the work. | H | C | H | Mandatory | 26 | 28 | REQ | 1 | 1 | 25 | 1.1.25 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0027 | 1.1.26 | The solution shall allow for the entry of permit, easement, and tagging requirements required to complete the work. | H | C | H | Mandatory | 27 | 29 | REQ | 1 | 1 | 26 | 1.1.26 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0028 | 1.1.27 | The solution shall provide for adjustment of estimates for existing account/project budget numbers. | H | C | H | Mandatory | 28 | 30 | REQ | 1 | 1 | 27 | 1.1.27 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0029 | 1.1.28 | The solution shall flag when account/project budget has been exceeded or is being approached, with appropriate approval process if budget is being exceeded. | L | C | L | Optional | 29 | 31 | REQ | 1 | 1 | 28 | 1.1.28 | L/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0030 | 1.1.29 | The solution shall provide for the ability to request/establish a new account/project number. | L | C | L | Optional | 30 | 32 | REQ | 1 | 1 | 29 | 1.1.29 | L/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.1011 | 1.1.30 | The solution shall have the ability to record price quotes. | H | H | Mandatory | Mandatory | Mandatory | Mandatory | 1011 | 33 | REQ | 1 | 1 | 30 | 1.1.30 | H/ | ERR1 | |||||||||||||||||||||||||||||
| WM.1012 | 1.1.31 | The solution shall have the ability to store project deliverables / documents. | H | H | Mandatory | Mandatory | Mandatory | Mandatory | 1012 | 34 | REQ | 1 | 1 | 31 | 1.1.31 | H/ | ERR1 | |||||||||||||||||||||||||||||
| WM.0031 | 1.1.32 | The solution shall provide for the generation of a work order and assignment of a unique work order number based upon an approved work estimate/design. | H | C | H | Mandatory | 31 | 35 | REQ | 1 | 1 | 32 | 1.1.32 | H/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0032 | 1.1.33 | The solution shall enable the ability to copy/duplicate existing designs. | L | N | L | Optional | 32 | 36 | REQ | 1 | 1 | 33 | 1.1.33 | L/ | ERR1 | |||||||||||||||||||||||||||||||
| WM.0033 | 1.1.34 | The solution shall provide viewable and printable overall gross estimated costs for work order. |
| Include accounting overheads in appropriate estimates (e.g., load company crew labor estimate but not contract crew estimate). | H | C | H | Mandatory | 33 | 37 | REQ | 1 | 1 | 34 | 1.1.34 | H/ | ERR1 | ||||||||||||
| WM.0034 | 1.1.35 | The solution shall receive and store the finalized and as-built versions of a design. | M | N | M | Preferred | 34 | 38 | REQ | 1 | 1 | 35 | 1.1.35 | M/ | ERR1 | ||||||||||
| WM.0035 | 1.1.36 | The solution shall provide for identifying, capturing, and tracking work requests originating from various sources and to indicate the source in the work request. |
| This includes any customer requests (leak, water quality, etc.), outside agency requests, and internal department requests. | H | C | H | Mandatory | 35 | 39 | REQ | 1 | 1 | 36 | 1.1.36 | H/ | ERR1 | ||||||||||||
| WM.0036 | 1.1.37 | The solution shall assign a unique identifier to the work request. | H | C | H | Mandatory | 36 | 40 | REQ | 1 | 1 | 37 | 1.1.37 | H/ | ERR1 | ||||||||||
| WM.0037 | 1.1.38 | The solution shall support a description of work to be performed. | H | C | H | Mandatory | 37 | 41 | REQ | 1 | 1 | 38 | 1.1.38 | H/ | ERR1 | ||||||||||
| WM.0038 | 1.1.39 | The solution shall provide the ability to associate or disassociate a customer, an asset/premise or miscellaneous work location to a work request. | H | C | H | Mandatory | 38 | 42 | REQ | 1 | 1 | 39 | 1.1.39 | H/ | ERR1 | ||||||||||
| WM.0039 | 1.1.40 | The solution shall provide the ability to associate or disassociate a customer to a work activity. | H | C | H | Mandatory | 39 | 43 | REQ | 1 | 1 | 40 | 1.1.40 | H/ | ERR1 | ||||||||||
| WM.0040 | 1.1.41 | The solution shall provide the ability to associate or disassociate an asset to a work activity. | H | C | H | Mandatory | 40 | 44 | REQ | 1 | 1 | 41 | 1.1.41 | H/ | ERR1 | ||||||||||
| WM.0041 | 1.1.42 | The solution shall provide the ability to associate or disassociate a work location to a work activity. | H | C | H | Mandatory | 41 | 45 | REQ | 1 | 1 | 42 | 1.1.42 | H/ | ERR1 | ||||||||||
| WM.0042 | 1.1.43 | The solution shall support review of the work request for completeness at all times. | H | C | H | Mandatory | 42 | 46 | REQ | 1 | 1 | 43 | 1.1.43 | H/ | ERR1 | ||||||||||
| WM.0043 | 1.1.44 | The solution shall provide for the review of a work request to identify the criticality of the work and the priority to be assigned. | H | C | H | Mandatory | 43 | 47 | REQ | 1 | 1 | 44 | 1.1.44 | H/ | ERR1 | ||||||||||
| WM.0044 | 1.1.45 | The solution shall provide the ability to change a work request (the reason code) with the appropriate authorizations to the type of work that actually needs to be completed. | H | C | H | Mandatory | 44 | 48 | REQ | 1 | 1 | 45 | 1.1.45 | H/ | ERR1 | ||||||||||
| WM.0045 | 1.1.46 | The solution shall identify requests that are subject to compliance and track the follow up activity and ensure that the order (and all related/subsequent orders) is completed according to compliance requirements. | H | C | H | Mandatory | 45 | 49 | REQ | 1 | 1 | 46 | 1.1.46 | H/ | ERR1 | ||||||||||
| WM.0046 | 1.1.47 | The solution shall allow the above to be configurable. | H | F | H | Mandatory | 46 | 50 | REQ | 1 | 1 | 47 | 1.1.47 | H/ | ERR1 | ||||||||||
| WM.0047 | 1.1.48 | The solution shall assign (by user-defined categories, such as by geographical area, by work type, by spatial grid, etc.) the work request to the appropriate department or individual for follow-up and routing of the request using an automated work queue, including messaging to inform the appropriate department or individual that the work request has been assigned to them. | H | C | H | Mandatory | 47 | 51 | REQ | 1 | 1 | 48 | 1.1.48 | H/ | ERR1 | ||||||||||
| WM.0048 | 1.1.49 | The solution shall provide the ability to identify duplicate requests with user defined verification parameters (e.g., look across order types, premises, customers, etc.). | H | C | H | Mandatory | 48 | 52 | REQ | 1 | 1 | 49 | 1.1.49 | H/ | ERR1 | ||||||||||
| WM.0049 | 1.1.50 | The solution shall enable the ability to copy/duplicate existing request. | H | C | H | Mandatory | 49 | 53 | REQ | 1 | 1 | 50 | 1.1.50 | H/ | ERR1 | ||||||||||
| WM.0050 | 1.1.51 | The solution shall allow attaching electronic documents to a work request or work order. | H | C | H | Mandatory | 50 | 54 | REQ | 1 | 1 | 51 | 1.1.51 | H/ | ERR1 | ||||||||||
| WM.0051 | 1.1.52 | The solution shall provide for the generation of a work order and assignment of a unique work order number based upon an approved work request. | H | C | H | Mandatory | 51 | 55 | REQ | 1 | 1 | 52 | 1.1.52 | H/ | ERR1 | ||||||||||
| WM.0052 | 1.1.53 | The solution shall provide for multiple levels of approval for the work request. | H | C | H | Mandatory | 52 | 56 | REQ | 1 | 1 | 53 | 1.1.53 | H/ | ERR1 | ||||||||||
| WM.0053 | 1.1.54 | The solution shall provide a drop down list of work request disposition codes and reasons. |
| System also allows for free-form comments. Entering in the disposition code will update the work request status. | H | C | H | Mandatory | 53 | 57 | REQ | 1 | 1 | 54 | 1.1.54 | H/ | ERR1 | |||
| WM.0054 | 1.1.55 | The solution shall provide multiple access paths to find the work request including: requester name, address, request number, individual assigned to request, etc. |
| Include wild card search capability to accommodate miscellaneous work locations (not based on an established premise). | H | C | H | Mandatory | 54 | 58 | REQ | 1 | 1 | 55 | 1.1.55 | H/ | ERR1 | ||||||||||||
| WM.0055 | 1.1.56 | The solution shall provide work requests reporting based on user-defined parameters. | H | C | H | Mandatory | 55 | 59 | REQ | 1 | 1 | 56 | 1.1.56 | H/ | ERR1 | ||||||||||
| WM.0056 | 1.1.57 | The solution shall enable the tracking and viewing the status (such as in design, hold for customer, hold for money, hold for permits, open, closed, canceled, scheduled (and date), etc.) of a work request or work order at any time throughout the work process. |
| Provide a viewable history of status changes, users who performed the changes, and the dates that the changes were performed. | H | C | H | Mandatory | 56 | 60 | REQ | 1 | 1 | 57 | 1.1.57 | H/ | ERR1 | ||||||||||||
| WM.0057 | 1.1.58 | The solution shall provide for the ability to interface with the CIS to convert a field activity in the CIS system to a request in WAM. | L | C | L | Optional | 57 | 61 | REQ | 1 | 1 | 58 | 1.1.58 | L/ | ERR1 | ||||||||||
| WM.0058 | 1.1.59 | The solution shall interface with the utility's CIS system to provide the ability to convert miscellaneous work locations to actual premises if the actual premise exists. |
| System will warn user if an actual premise exists with the option to edit. | L | C | L | Optional | 58 | 62 | REQ | 1 | 1 | 59 | 1.1.59 | L/ | ERR1 | ||||||||||||||||||
| WM.0059 | 1.1.60 | The solution shall track that the CIAC fee payment has been received and initiate refund to the original customer as other customers are connected. | L | N | L | Optional | 59 | 63 | REQ | 1 | 1 | 60 | 1.1.60 | L/ | ERR1 | ||||||||||||||||
| WM.0060 | 1.1.61 | The solution shall have the ability to capture Corrective descriptions, including but not limited to: labor resources, equipment resources, material resources, condition after work completed, outage duration, task duration, work description, etc. | H | C | H | Mandatory | 60 | 64 | REQ | 1 | 1 | 61 | 1.1.61 | H/ | ERR1 | ||||||||||||||||
| WM.0061 | 1.1.62 | The solution shall have the ability to capture Maintenance descriptions, including but not limited to: labor resources, equipment resources, material resources, condition after work completed, task duration, work description, unit costs for parts, etc. | H | C | H | Mandatory | 61 | 65 | REQ | 1 | 1 | 62 | 1.1.62 | H/ | ERR1 | ||||||||||||||||
| WM.0062 | 1.1.63 | The solution shall have the ability to capture Inspection descriptions, including but not limited to: labor resources, equipment resources, material resources, condition after work completed, task duration, due date for next inspection, etc. | H | C | H | Mandatory | 62 | 66 | REQ | 1 | 1 | 63 | 1.1.63 | H/ | ERR1 | ||||||||||||||||
| WM.0063 | 1.1.64 | The solution shall have the ability to capture Capital descriptions, including but not limited to: initial design, labor resources, equipment resources, material resources, task duration, as-built designs, etc. | H | C | H | Mandatory | 63 | 67 | REQ | 1 | 1 | 64 | 1.1.64 | H/ | ERR1 | ||||||||||||||||
| WM.1008 | 1.1.65 | The solution shall track both planned and actual work order data, including: labor, materials, contractor, other data. | |||||||||||||||||||||||||||||
| (Example: One can view the results and see the actual vs. planned timing and expense to assist with budgeting, forecasting, and operational performance) | H | H | Mandatory | Mandatory | Mandatory | Mandatory | 1008 | 68 | REQ | 1 | 1 | 65 | 1.1.65 | H/ | ERR1 | ||||||||||||||||
| WM.1014 | 1.1.66 | The solution shall include a required data field to record real time asset condition with algorithmic capabilities. | H | H | Mandatory | Mandatory | Mandatory | Mandatory | 1014 | 69 | REQ | 1 | 1 | 66 | 1.1.66 | H/ | ERR1 | ||||||||||||||
| WM.0064 | 1.1.67 | The solution shall allow for the creation of custom work templates with a pre-configured list of steps (activities), labor, equipment and material requirements. | H | C | H | Mandatory | 64 | 70 | REQ | 1 | 1 | 67 | 1.1.67 | H/ | ERR1 | ||||||||||||||||
| WM.0065 | 1.1.68 | The solution shall provide a "quick" work template for use by field supervisors. |
| Would allow for collection of labor and materials for small, emergent, routine work (e.g., repair of minor damage). | H | C | H | Mandatory | 65 | 71 | REQ | 1 | 1 | 68 | 1.1.68 | H/ | ERR1 | ||||||||||||
| WM.0066 | 1.1.69 | The solution shall support simple and quick creation of work templates for work that occurs frequently (I.e., a "hot-key" or button may be used to create the starting data or configuration for a given work type). | H | C | H | Mandatory | 66 | 72 | REQ | 1 | 1 | 69 | 1.1.69 | H/ | ERR1 | ||||||||||
| WM.0067 | 1.1.70 | The solution shall allow the creation of an unlimited number of work "templates" (step combinations) to include inspections, any type of work steps (activities), reviews, etc. | H | C | H | Mandatory | 67 | 73 | REQ | 1 | 1 | 70 | 1.1.70 | H/ | ERR1 | ||||||||||
| WM.0068 | 1.1.71 | The solution shall allow for modification of any work-step or labor, equipment and material requirement for any work template with proper authorization. | H | C | H | Mandatory | 68 | 74 | REQ | 1 | 1 | 71 | 1.1.71 | H/ | ERR1 | ||||||||||
| WM.0069 | 1.1.72 | The solution shall allow the creation of a work order to track labor and materials that acts as a child to an existing work order. | H | C | H | Mandatory | 69 | 75 | REQ | 1 | 1 | 72 | 1.1.72 | H/ | ERR1 | ||||||||||
| WM.0070 | 1.1.73 | The solution shall have the ability to identify and indicate type of work, automatically assigning appropriate accounting/project numbers. | H | C | H | Mandatory | 70 | 76 | REQ | 1 | 1 | 73 | 1.1.73 | H/ | ERR1 | ||||||||||
| WM.0071 | 1.1.74 | The solution shall allow for multiple combinations of accounting project/task numbers per work order. | H | C | H | Mandatory | 71 | 77 | REQ | 1 | 1 | 74 | 1.1.74 | H/ | ERR1 | ||||||||||
| WM.0072 | 1.1.75 | The solution shall provide the ability for accounting/project numbers to be modified after the work order has been created/approved. | H | C | H | Mandatory | 72 | 78 | REQ | 1 | 1 | 75 | 1.1.75 | H/ | ERR1 | ||||||||||
| WM.0073 | 1.1.76 | The solution shall provide for the ability to add contact information for relevant parties or stakeholders to a work request or work order. |
| Examples: contractor, developer, property owner, foreman, engineer, etc. | H | C | H | Mandatory | 73 | 79 | REQ | 1 | 1 | 76 | 1.1.76 | H/ | ERR1 | ||||||||||||
| WM.0074 | 1.1.77 | The solution shall allow the user to specify the labor hours, materials, equipment required to perform the activity. | H | C | H | Mandatory | 74 | 80 | REQ | 1 | 1 | 77 | 1.1.77 | H/ | ERR1 | ||||||||||
| WM.0075 | 1.1.78 | The solution shall allow the specification of the labor hours, materials, equipment required to perform the activity from a template. | H | C | H | Mandatory | 75 | 81 | REQ | 1 | 1 | 78 | 1.1.78 | H/ | ERR1 | ||||||||||
| WM.0076 | 1.1.79 | The solution shall allow generation of a simple work order to record labor and materials for corrective maintenance (emergent work). | H | C | H | Mandatory | 76 | 82 | REQ | 1 | 1 | 79 | 1.1.79 | H/ | ERR1 | ||||||||||
| WM.0077 | 1.1.80 | The solution shall produce a "pick-list" from inventory for use on a given work order. | H | C | H | Mandatory | 77 | 83 | REQ | 1 | 1 | 80 | 1.1.80 | H/ | ERR1 | ||||||||||
| WM.0078 | 1.1.81 | The solution shall allow for the configuration of a "request" step and recording a start date associated with the activity. |
| This accommodates the tracking of customer requests that are on "hold" due to required customer action or other investigation. | H | C | H | Mandatory | 78 | 84 | REQ | 1 | 1 | 81 | 1.1.81 | H/ | ERR1 | |||
| WM.0079 | 1.1.82 | The solution shall have the ability to add free-form remarks to work order and choose whether or not the remarks will print (and on mobile) on the work order. |
| System will indicate user and timestamp for each remark. | H | C | H | Mandatory | 79 | 85 | REQ | 1 | 1 | 82 | 1.1.82 | H/ | ERR1 | ||||||||||||
| WM.0080 | 1.1.83 | The solution shall have the ability to add information to work orders such as locate descriptions for use in the "Call Before You Dig" system. | L | C | L | Optional | 80 | 86 | REQ | 1 | 1 | 83 | 1.1.83 | L/ | ERR1 | ||||||||||
| WM.0081 | 1.1.84 | The solution shall have the ability to automatically transmit locate description to the "Call Before You Dig" system, including date for the work to begin. | L | C | L | Optional | 81 | 87 | REQ | 1 | 1 | 84 | 1.1.84 | L/ | ERR1 | ||||||||||
| WM.0082 | 1.1.85 | The solution shall provide the ability to create a blanket work order. |
| Blanket work orders remain open for an indefinite period of time and may be charged by resources that have not been specifically assigned to the work order. This functionality should be available for all work order types. | H | C | H | Mandatory | 82 | 88 | REQ | 1 | 1 | 85 | 1.1.85 | H/ | ERR1 | ||||||||||||||||
| WM.0083 | 1.1.86 | The solution shall provide for the association of a parent work order number with multiple work orders. | H | C | H | Mandatory | 83 | 89 | REQ | 1 | 1 | 86 | 1.1.86 | H/ | ERR1 | ||||||||||||||
| WM.0084 | 1.1.87 | The solution shall support work authorization approvals for work based on dollar amount or other user-defined criteria. | H | C | H | Mandatory | 84 | 90 | REQ | 1 | 1 | 87 | 1.1.87 | H/ | ERR1 | ||||||||||||||
| WM.0085 | 1.1.88 | The solution shall provide for the association of a valid customer or outside agency with a work order for subsequent billing of work related charges. | H | C | H | Mandatory | 85 | 91 | REQ | 1 | 1 | 88 | 1.1.88 | H/ | ERR1 | ||||||||||||||
| WM.0086 | 1.1.89 | The solution shall assign a default priority based on job reason and asset or component, with the ability for the user (based on security) to modify the priority assigned. | H | C | H | Mandatory | Mandatory | Mandatory | Mandatory | Mandatory | 86 | 92 | REQ | 1 | 1 | 89 | 1.1.89 | H/ | ERR1 | ||||||||||
| WM.0087 | 1.1.90 | The solution shall provide for the identification and generation of emergency service requests. | H | C | H | Mandatory | 87 | 93 | REQ | 1 | 1 | 90 | 1.1.90 | H/ | ERR1 | ||||||||||||||
| WM.0088 | 1.1.91 | The solution shall provide for the identification of critical facilities/assets experiencing an emergency. | H | C | H | Mandatory | 88 | 94 | REQ | 1 | 1 | 91 | 1.1.91 | H/ | ERR1 | ||||||||||||||
| WM.0089 | 1.1.92 | The solution shall provide for bypassing approval levels as required to generate work orders for dispatching of work crews to locate and correct the situation, with appropriate security / permissions by role. | H | C | H | Mandatory | 89 | 95 | REQ | 1 | 1 | 92 | 1.1.92 | H/ | ERR1 | ||||||||||||||
| WM.0090 | 1.1.93 | The solution shall allow the scheduling of inspections based on user directive and/or condition based criteria. | H | C | H | Mandatory | 90 | 96 | REQ | 1 | 1 | 93 | 1.1.93 | H/ | ERR1 | ||||||||||||||
| WM.0091 | 1.1.94 | The solution shall provide a workflow through creation, update and approval of the analysis. | H | F | H | Mandatory | 91 | 97 | REQ | 1 | 1 | 94 | 1.1.94 | H/ | ERR1 | ||||||||||||||
| WM.0092 | 1.1.95 | The solution shall enable detailed projection of project costs defined by major task or milestone to provide sufficient granularity to manage cost to deliverables and milestones. | L | C | L | Optional | 92 | 98 | REQ | 1 | 1 | 95 | 1.1.95 | L/ | ERR1 | ||||||||||||||
| WM.0093 | 1.1.96 | The solution shall have the ability to capture, maintain and access standard costs, planning assumptions and actual costs associated with each project. | H | C | H | Mandatory | Mandatory | Mandatory | Mandatory | Mandatory | 93 | 99 | REQ | 1 | 1 | 96 | 1.1.96 | H/ | ERR1 | ||||||||||
| WM.0094 | 1.1.97 | The solution shall have the ability to incorporate Compatible Units (CUs) and Compatible Unit (CU) groupings into designs. | H | C | H | Mandatory | 94 | 100 | REQ | 1 | 1 | 97 | 1.1.97 | H/ | ERR1 | ||||||||||||||
| WM.0095 | 1.1.98 | The solution shall have the ability to manually create a tabular design/estimate using CUs. | H | F | H | Mandatory | 95 | 101 | REQ | 1 | 1 | 98 | 1.1.98 | H/ | ERR1 | ||||||||||||||
| WM.0096 | 1.1.99 | The solution shall have the ability to add additional resources to a piece of work other than what is already specified on a CU. | H | F | H | Mandatory | 96 | 102 | REQ | 1 | 1 | 99 | 1.1.99 | H/ | ERR1 | ||||||||||||||
| WM.0097 | 1.1.100 | The solution shall have the ability to remove a CU from CU groupings for a specified design alternative. | H | F | H | Mandatory | 97 | 103 | REQ | 1 | 1 | 100 | 1.1.100 | H/ | ERR1 | ||||||||||||||
| WM.0098 | 1.1.101 | The solution shall have the ability to link and require a specific sequence of CU operation. | H | F | H | Mandatory | 98 | 104 | REQ | 1 | 1 | 101 | 1.1.101 | H/ | ERR1 | ||||||||||||||
| WM.0099 | 1.1.102 | The solution shall have the ability to store CU components in a central database. | H | F | H | Mandatory | 99 | 105 | REQ | 1 | 1 | 102 | 1.1.102 | H/ | ERR1 | ||||||||||||||
| WM.0100 | 1.1.103 | The solution shall have the ability to import/export compatible unit library to a design tool / CAD. | L | N | L | Optional | 100 | 106 | REQ | 1 | 1 | 103 | 1.1.103 | L/ | ERR1 | ||||||||||||||
| WM.0101 | 1.1.104 | The solution shall have the ability to create and modify CUs and CU groupings. | H | F | H | Mandatory | 101 | 107 | REQ | 1 | 1 | 104 | 1.1.104 | H/ | ERR1 | ||||||||||||||
| WM.0102 | 1.1.105 | The solution shall have the ability to logically search for CUs based on the CU parameters. | H | F | H | Mandatory | 102 | 108 | REQ | 1 | 1 | 105 | 1.1.105 | H/ | ERR1 | ||||||||||||||
| WM.0103 | 1.1.106 | The solution shall have the ability to translate CUs into material requests to be sent to materials management system. | H | F | H | Mandatory | 103 | 109 | REQ | 1 | 1 | 106 | 1.1.106 | H/ | ERR1 | ||||||||||||||
| WM.0104 | 1.1.107 | The solution shall have the ability to translate CUs into material requests to be fulfilled by the contractor. | L | N | L | Optional | 104 | 110 | REQ | 1 | 1 | 107 | 1.1.107 | L/ | ERR1 | ||||||||||||||
| WM.0105 | 1.1.108 | The solution shall allow for the entry of compatible units (with labor, material, and special item components) and correlate them to the appropriate accounting task numbers for the associated activity. | H | F | H | Mandatory | 105 | 111 | REQ | 1 | 1 | 108 | 1.1.108 | H/ | ERR1 | ||||||||||||||
| WM.0106 | 1.1.109 | The solution shall, in the creation of compatible units, allow for the ability to load or not load the portion of the estimate associated with a Compatible Unit with overheads. | H | F | H | Mandatory | 106 | 112 | REQ | 1 | 1 | 109 | 1.1.109 | H/ | ERR1 | ||||||||||||||
| WM.0107 | 1.1.110 | The solution shall provide for the viewing and printing of an equipment removal list based on the Compatible Units within the work order. | H | F | H | Mandatory | 107 | 113 | REQ | 1 | 1 | 110 | 1.1.110 | H/ | ERR1 | ||||||||||||||
| WM.0108 | 1.1.111 | The solution shall provide the ability to eliminate the generation of additional work orders based on previous work order completion satisfying an inspection or condition for an asset. |
| The WAM solution should use all information available on the asset/work history when generating work orders. | H | C | H | Mandatory | 108 | 114 | REQ | 1 | 1 | 111 | 1.1.111 | H/ | ERR1 | ||||||||||||
| WM.0109 | 1.1.112 | The solution shall provide the ability to automatically generate a unique and sequential work order number and populate fields such as creation date, time, originator name upon creation of a new work order. | H | C | H | Mandatory | 109 | 115 | REQ | 1 | 1 | 112 | 1.1.112 | H/ | ERR1 | ||||||||||
| WM.0110 | 1.1.113 | The solution shall provide the ability to copy work orders to minimize data entry. | H | C | H | Mandatory | 110 | 116 | REQ | 1 | 1 | 113 | 1.1.113 | H/ | ERR1 | ||||||||||
| WM.0111 | 1.1.114 | The solution shall provide the ability to automatically generate work orders per user defined and configured and/or calculated compliance due dates, including any required lead or "pad" time, by asset type and geographic location. |
The WAM solution should recalculate the next due date upon completion of a work order. For example: Annual, monthly, calendar of reoccurring work ( e.g., Leak Survey, Pipeline Inspection, Patrol, Regulator Station Inspection etc.).
| H | C | H | Mandatory | 111 | 117 | REQ | 1 | 1 | 114 | 1.1.114 | H/ | ERR1 | ||||||||||||
| WM.0112 | 1.1.115 | The solution shall provide the ability to generate work orders based on asset types and/or a selection of assets from a pick list of all assets identified within one or more user defined geographic areas (e.g., by Division/Operating Centers/Area of Responsibility etc.). | H | C | H | Mandatory | 112 | 118 | REQ | 1 | 1 | 115 | 1.1.115 | H/ | ERR1 | |||||||||
| WM.0113 | 1.1.116 | The solution shall provide the ability to identify and initiate required compliance work on a configurable schedule and calculations based on the number of a specific asset type and its attributes. |
| For example: Compliance requirement is that X% isolated section test points need to be inspected at a regular interval. The System should be able to calculate the required number of test points based on criteria defined for the asset type. | H | F | H | Mandatory | 113 | 119 | REQ | 1 | 1 | 116 | 1.1.116 | H/ | ERR1 | |||
| WM.0114 | 1.1.117 | The solution shall provide the ability to automatically approve work orders based on a list of pre-approved work types. |
| For example: Compliance driven inspection work orders may be defined as pre-approved work and the solution will auto-approve such requests. | H | C | H | Mandatory | 114 | 120 | REQ | 1 | 1 | 117 | 1.1.117 | H/ | ERR1 | ||||||||||||
| WM.0115 | 1.1.118 | The solution shall provide the ability for originator to receive acknowledgement when work order approval is rejected. | H | C | H | Mandatory | 115 | 121 | REQ | 1 | 1 | 118 | 1.1.118 | H/ | ERR1 | ||||||||||
| WM.0116 | 1.1.119 | The solution shall provide the ability to automatically release work orders to field resources when permitted by business rules (e.g., in case of customer reported emergency, the work order can be directly sent to scheduling/dispatch). | H | C | H | Mandatory | 116 | 122 | REQ | 1 | 1 | 119 | 1.1.119 | H/ | ERR1 | ||||||||||
| WM.0117 | 1.1.120 | The solution shall provide the ability for work orders to increase in priority as their expiration date approaches. |
| The solution should provide alerts on overdue work. | H | C | H | Mandatory | 117 | 123 | REQ | 1 | 1 | 120 | 1.1.120 | H/ | ERR1 | |||
| WM.0118 | 1.1.121 | The solution shall provide the ability to define priority for any work order created automatically or manually in the system. |
| Priority is utilized in scheduling/assignment process for awareness and to expedite completion of urgent requests. | H | C | H | Mandatory | 118 | 124 | REQ | 1 | 1 | 121 | 1.1.121 | H/ | ERR1 |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .