Functional_Requirements_Worksheet.xlsx
XLSX spreadsheet 787 KB Posted
- Attached to
- Utility Billing Software Replacement Phase 2
- Solicitation number
- RFP-605021-25/LTT
- Issued by
- Seminole County, Florida
About this file
The provided file is a Functional Requirements Worksheet for a Customer Information System (CIS) for Seminole County Utilities Division in Florida. The document details a comprehensive set of technical requirements for a utility billing software replacement project, specifically Phase 2, which aims to replace the current system and integrate with the county's existing JD Edwards enterprise resource planning (ERP) software. The requirements are extensively documented across multiple functional areas including billing, collections, customer maintenance, credit rating, adjustments, budget billing, and various other utility-specific operational domains.
The worksheet contains an exhaustive list of over 1,000 specific functional requirements organized by category, each with detailed specifications for system capabilities. These requirements cover a wide range of utility billing system needs, such as handling bill adjustments, managing landlord-tenant relationships, processing collections, supporting budget billing, creating service orders, and providing robust customer self-service features. While no specific pricing or budget details are included in this document, the depth and specificity of the requirements suggest a complex, enterprise-level software implementation that will require a sophisticated, configurable utility billing solution capable of handling multiple service types, billing scenarios, and regulatory compliance needs.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Utility_Billing_Software_Replacement_Phase_2_(Addendum_#1_Revision).pdf | ||
| Proposal_Response_REV_8.19.pdf | ||
| Utility_Billing_Software_Replacement_Phase_2.pdf | ||
| Draft_Term_Contract.pdf | ||
| Insurance_Requirements.pdf | ||
| Interface_Experience_Worksheet.xlsx | XLSX spreadsheet | |
| Technical_Requirements_Worksheet.xlsx | XLSX spreadsheet | |
| Staffing_Matrix_Worksheet.xlsx | XLSX spreadsheet | |
| Pricing_Worksheet.xlsx | XLSX spreadsheet | |
| Proposal_Response.pdf | ||
| Sample_Purchase_Order.pdf |
Show all 11
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
_IO
| _Base_Folder | C:\Users\KirkL\OneDrive - ESWCompany.com\WCG_Test\ | _Seed_Sheet | Func_Req |
| Proj_ID | TEMPLATE | Func_Req_ReqIDs | {ADJ.1.1;ADJ.1.10;ADJ.1.11;ADJ.1.12;ADJ.1.13;ADJ.1.14;ADJ.1.15;ADJ.1.16;ADJ.1.17;ADJ.1.18;ADJ.1.19;ADJ.1.2;ADJ.1.20;ADJ.1.21;ADJ.1.22;ADJ.1.23;ADJ.1.24;ADJ.1.25;ADJ.1.3;ADJ.1.4;ADJ.1.5;ADJ.1.6;ADJ.1.7;ADJ.1.8;ADJ.1.9;NEW;NEW;NEW;NEW;NEW;ADJ.2.1;ADJ.2.2;ADJ.2.3;ADJ.2.4;ADJ.2.5;ADJ.2.6;ADJ.2.7;ADJ.2.8;ADJ.3.1;ADJ.3.2;ADJ.3.3;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;DEBT.1.1;DEBT.2.1;NEW;DEBT.3.10;DEBT.3.11;DEBT.3.2;DEBT.3.3;DEBT.3.4;DEBT.3.5;DEBT.3.6;DEBT.3.7;DEBT.3.8;DEBT.3.9;NEW;NEW;NEW;NEW;BCL.1.1;BCL.1.2;BCL.1.3;BCL.1.4;BCL.1.5;BCL.1.6;NEW;BCL.2.1;BCL.2.2;BCL.2.3;BCL.2.4;BCL.2.5;NEW;BCL.3.1;BCL.3.10;BCL.3.2;BCL.3.3;BCL.3.4;BCL.3.5;BCL.3.6;BCL.3.7;BCL.3.8;BCL.3.9;NEW;BCL.4.1;BCL.4.2;BCL.4.3;BCL.4.4;BCL.4.5;BCL.4.6;BCL.4.7;BCL.4.8;BCL.5.1;BCL.5.2;BCL.5.3;BCL.5.4;BCL.5.5;BCL.6.1;BCL.6.10;BCL.6.11;BCL.6.12;BCL.6.13;BCL.6.14;BCL.6.2;BCL.6.3;BCL.6.4;BCL.6.5;BCL.6.6;BCL.6.7;BCL.6.8;BCL.6.9;NEW;BCL.7.1;BCL.7.2;BCL.7.3;BCL.7.4;BCL.7.5;BCL.7.6;BCL.7.7;BCL.7.8;BCL.8.1;BCL.8.2;BCL.8.3;NEW;BCL.9.1;BCL.9.2;BCL.9.3;BCL.9.4;NEW;NEW;NEW;NEW;NEW;BPR.1.1;BPR.1.10;BPR.1.11;BPR.1.12;BPR.1.13;BPR.1.14;BPR.1.15;BPR.1.2;BPR.1.3;BPR.1.4;BPR.1.5;BPR.1.6;BPR.1.7;BPR.1.8;BPR.1.9;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;BPR.2.1;BPR.2.2;BPR.2.3;NEW;BB.1.1;BB.2.1;BB.3.1;BB.4.1;BB.4.2;BB.4.3;BB.4.4;BB.4.5;BB.4.6;BB.5.1;NEW;NEW;COL.1.1;COL.1.10;COL.1.11;COL.1.12;COL.1.13;COL.1.14;COL.1.15;COL.1.2;COL.1.3;COL.1.4;COL.1.5;COL.1.6;COL.1.7;COL.1.8;COL.1.9;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;COL.2.1;COL.3.1;COL.3.2;COL.3.3;COL.3.4;COL.3.5;COL.4.1;COL.4.10;COL.4.2;COL.4.3;COL.4.4;COL.4.5;COL.4.6;COL.4.7;COL.4.8;COL.4.9;NEW;NEW;COL.5.1;COL.5.2;COL.5.3;COL.6.1;COL.6.10;COL.6.11;COL.6.2;COL.6.3;COL.6.4;COL.6.5;COL.6.6;COL.6.7;COL.6.8;COL.6.9;NEW;CR.1.1;CR.1.2;CR.2.1;CR.2.2;CR.2.3;CR.2.4;CR.2.5;CR.2.6;CR.3.1;CR.3.2;CR.3.3;CR.3.4;CR.3.5;NEW;CR.4.1;CR.4.2;CR.4.3;CR.4.4;NEW;CLM.1.1;CLM.1.10;CLM.1.11;CLM.1.12;CLM.1.13;CLM.1.14;CLM.1.15;CLM.1.16;CLM.1.17;CLM.1.18;CLM.1.19;CLM.1.2;CLM.1.20;CLM.1.21;CLM.1.22;CLM.1.23;CLM.1.24;CLM.1.3;CLM.1.4;CLM.1.5;CLM.1.6;CLM.1.7;CLM.1.8;CLM.1.9;CLM.2.1;CLM.2.2;CLM.2.3;CLM.2.4;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;CLM.3.1;CLM.3.10;CLM.3.11;CLM.3.12;CLM.3.13;CLM.3.14;CLM.3.15;CLM.3.16;CLM.3.2;CLM.3.3;CLM.3.4;CLM.3.5;CLM.3.6;CLM.3.7;CLM.3.8;CLM.3.9;NEW;NEW;CLM.4.1;CLM.4.10;CLM.4.11;CLM.4.2;CLM.4.3;CLM.4.4;CLM.4.5;CLM.4.6;CLM.4.7;CLM.4.8;CLM.4.9;NEW;NEW;NEW;CLM.5.1;CLM.5.10;CLM.5.11;CLM.5.12;CLM.5.13;CLM.5.14;CLM.5.2;CLM.5.3;CLM.5.4;CLM.5.5;CLM.5.6;CLM.5.7;CLM.5.8;CLM.5.9;NEW;NEW;NEW;NEW;CLM.6.1;CLM.6.2;CLM.6.3;CLM.6.4;CLM.6.5;CLM.6.6;CLM.6.7;NEW;CLM.7.1;CLM.7.10;CLM.7.11;CLM.7.12;CLM.7.13;CLM.7.14;CLM.7.15;CLM.7.16;CLM.7.17;CLM.7.2;CLM.7.3;CLM.7.4;CLM.7.5;CLM.7.6;CLM.7.7;CLM.7.8;CLM.7.9;CLM.8.1;CLM.8.10;CLM.8.11;CLM.8.2;CLM.8.3;CLM.8.4;CLM.8.5;CLM.8.6;CLM.8.7;CLM.8.8;CLM.8.9;NEW;NEW;NEW;NEW;CLM.9.1;CLM.9.2;CLM.9.3;CLM.9.4;CLM.9.5;NEW;NEW;NEW;CCI.1.1;CCI.1.2;CCI.1.3;CCI.1.4;CCI.1.5;CCI.2.1;CCI.3.1;CCI.3.2;CCI.3.3;CCI.3.4;CCI.3.5;CCI.3.6;CCI.3.7;CCI.3.8;CCI.3.9;CCI.4.1;CCI.4.2;CCI.4.3;CCI.4.4;NEW;NEW;CCI.5.1;CCI.6.1;CCI.6.2;CCI.6.3;CCI.7.1;CCI.7.2;CCI.7.3;CCI.7.4;CCI.8.1;DEP.1.1;DEP.1.10;DEP.1.11;DEP.1.12;DEP.1.13;DEP.1.14;DEP.1.15;DEP.1.16;DEP.1.17;DEP.1.18;DEP.1.19;DEP.1.2;DEP.1.20;DEP.1.21;DEP.1.22;DEP.1.23;DEP.1.24;DEP.1.25;DEP.1.26;DEP.1.27;DEP.1.3;DEP.1.4;DEP.1.5;DEP.1.6;DEP.1.7;DEP.1.8;DEP.1.9;NEW;NEW;NEW;NEW;NEW;NEW;NEW;CSS.1.1;CSS.1.2;CSS.1.3;CSS.1.4;CSS.1.5;CSS.1.6;CSS.1.7;CSS.1.8;CSS.1.9;CSS.3.1;CSS.3.10;CSS.3.11;CSS.3.2;CSS.3.3;CSS.3.4;CSS.3.5;CSS.3.6;CSS.3.7;CSS.3.8;CSS.3.9;NEW;CSS.5.1;CSS.5.2;CSS.5.3;CSS.5.4;CSS.5.5;CSS.6.1;CSS.6.2;CSS.6.3;CSS.6.4;CSS.6.5;CSS.6.6;CSS.10.1;CSS.10.10;CSS.10.11;CSS.10.12;CSS.10.13;CSS.10.14;CSS.10.2;CSS.10.3;CSS.10.4;CSS.10.5;CSS.10.6;CSS.10.7;CSS.10.8;CSS.10.9;CSS.9.1;CSS.9.2;CSS.9.3;CSS.8.1;CSS.8.2;CSS.8.3;CSS.4.1;CSS.4.2;CSS.4.3;CSS.4.4;CSS.4.5;CSS.4.6;CSS.2.1;CSS.2.2;CSS.7.1;CSS.7.10;CSS.7.11;CSS.7.12;CSS.7.13;CSS.7.14;CSS.7.15;CSS.7.16;CSS.7.17;CSS.7.2;CSS.7.3;CSS.7.4;CSS.7.5;CSS.7.6;CSS.7.7;CSS.7.8;CSS.7.9;NEW;NEW;DNP.2.1;DNP.2.2;DNP.2.3;NEW;DNP.1.1;DNP.1.2;DNP.1.3;DNP.1.4;DNP.1.5;NEW;NEW;FM.1.1;FM.1.10;FM.1.11;FM.1.2;FM.1.3;FM.1.4;FM.1.5;FM.1.6;FM.1.7;FM.1.8;FM.1.9;FM.2.1;FM.2.10;FM.2.11;FM.2.12;FM.2.13;FM.2.14;FM.2.15;FM.2.16;FM.2.2;FM.2.3;FM.2.4;FM.2.5;FM.2.7;FM.2.8;FM.2.9;NEW;FM.3.1;FM.3.10;FM.3.11;FM.3.12;FM.3.13;FM.3.14;FM.3.15;FM.3.16;FM.3.17;FM.3.2;FM.3.3;FM.3.4;FM.3.5;FM.3.6;FM.3.7;FM.3.8;FM.3.9;NEW;NEW;NEW;NEW;NEW;MET.1.1;NEW;NEW;NEW;NEW;NEW;NEW;NEW;MET.2.1;MET.2.10;MET.2.11;MET.2.12;MET.2.13;MET.2.2;MET.2.3;MET.2.4;MET.2.5;MET.2.6;MET.2.7;MET.2.8;MET.2.9;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;MET.3.1;MET.3.2;MET.3.3;MET.3.4;MET.4.1;MET.4.2;MET.4.3;NEW;NEW;NEW;MRD.1.1;MRD.1.2;MRD.1.3;MRD.1.4;MRD.1.5;MRD.1.6;MRD.2.1;MRD.2.2;MRD.2.3;MRD.2.4;MRD.2.5;MRD.2.6;NEW;NEW;NEW;MRD.3.1;MRD.3.2;MRD.4.1;MRD.4.2;MRD.4.3;MRD.4.4;MRD.4.5;MRD.4.6;MRD.4.7;MRD.4.8;MRD.4.9;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;MISC.1.1;NEW;NEW;NEW;NEW;MISC.2.1;MISC.2.2;MISC.2.3;MISC.2.4;NEW;MISC.3.1;MISC.3.2;MISC.3.3;MISC.3.4;MISC.3.5;NEW;MISC.4.1;MISC.4.2;MISC.5.1;MISC.5.2;MWM.1.1;MWM.1.2;MWM.1.3;MWM.1.4;MWM.1.5;MWM.1.6;MWM.1.7;MWM.2.1;MWM.2.10;MWM.2.11;MWM.2.12;MWM.2.13;MWM.2.2;MWM.2.3;MWM.2.4;MWM.2.5;MWM.2.6;MWM.2.7;MWM.2.8;MWM.2.9;MWM.3.1;MWM.3.2;MWM.3.3;MWM.3.4;MWM.4.1;MWM.4.2;MWM.4.3;MWM.4.4;MWM.4.5;MWM.5.1;MWM.5.10;MWM.5.11;MWM.5.12;MWM.5.13;MWM.5.14;MWM.5.15;MWM.5.16;MWM.5.17;MWM.5.19;MWM.5.2;MWM.5.3;MWM.5.4;MWM.5.5;MWM.5.6;MWM.5.7;MWM.5.8;MWM.5.9;MWM.6.1;MWM.6.10;MWM.6.11;MWM.6.12;MWM.6.13;MWM.6.14;MWM.6.2;MWM.6.3;MWM.6.4;MWM.6.5;MWM.6.6;MWM.6.7;MWM.6.8;MWM.6.9;NEW;NEW;NEW;NEW;NEW;NEW;MOV.1.1;MOV.1.2;MOV.1.3;NEW;NEW;NEW;NEW;MOV.2.1;MOV.2.10;MOV.2.11;MOV.2.12;MOV.2.13;MOV.2.14;MOV.2.15;MOV.2.16;MOV.2.17;MOV.2.18;MOV.2.19;MOV.2.2;MOV.2.3;MOV.2.4;MOV.2.5;MOV.2.6;MOV.2.7;MOV.2.8;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW.1.1;NEW.1.2;NEW.2.1;NEW.2.2;NEW.2.3;NEW.2.4;NEW.2.5;NEW.2.6;NEW;PAR.1.1;PAR.1.2;PAR.1.3;PAR.1.4;PAR.1.5;PAR.1.6;PAR.2.1;PAR.2.2;PAR.2.3;PAR.2.4;PAR.2.5;PAR.4.1;PAR.4.10;PAR.4.11;PAR.4.12;PAR.4.2;PAR.4.3;PAR.4.4;PAR.4.5;PAR.4.6;PAR.4.7;PAR.4.8;PAR.4.9;NEW;NEW;NEW;PEX.3.1;PEX.3.2;PEX.3.3;NEW;NEW;PEX.1.1;PEX.1.2;PEX.1.3;PEX.1.4;PEX.1.5;NEW;NEW;NEW;NEW;NEW;PEX.2.1;PEX.2.2;PEX.2.3;NEW;PP.1.1;PP.1.2;PP.1.3;PP.1.4;PP.2.1;PP.2.2;NEW;NEW;PP.3.1;PP.3.2;PP.3.3;PP.3.4;NEW;NEW;NEW;PP.4.1;NEW;NEW;NEW;NEW;NEW;NEW;PP.5.1;PP.5.2;PP.5.3;PP.5.4;PP.5.5;PP.5.6;PP.5.7;PP.6.1;PP.6.2;RM.1.1;RM.1.10;RM.1.11;RM.1.12;RM.1.13;RM.1.14;RM.1.15;RM.1.16;RM.1.17;RM.1.18;RM.1.19;RM.1.2;RM.1.20;RM.1.21;RM.1.22;RM.1.23;RM.1.3;RM.1.4;RM.1.5;RM.1.6;RM.1.7;RM.1.8;RM.1.9;RM.2.1;RM.2.2;RM.2.3;RM.2.4;RM.2.5;NEW;NEW;NEW;NEW;NEW;RM.3.1;RM.3.2;RM.4.1;RM.4.10;RM.4.11;RM.4.12;RM.4.2;RM.4.3;RM.4.4;RM.4.5;RM.4.6;RM.4.7;RM.4.8;RM.4.9;NEW;NEW;REB.1.1;REB.1.2;REB.1.3;NEW;NEW;NEW;REB.3.1;REB.2.1;REP.1.1;REP.1.2;REP.1.3;REP.1.4;REP.1.5;REP.1.6;NEW;REP.2.1;REP.2.2;REP.2.3;REP.2.4;REP.2.5;REP.2.6;REP.2.7;REP.2.8;NEW;NEW;REP.3.1;REP.3.2;REP.3.3;REP.4.1;REP.4.2;REP.4.3;REP.4.4;REP.4.5;REP.4.6;REP.4.7;NEW;NEW;NEW;NEW;NEW;NEW;NEW;REP.5.1;REP.5.2;REP.6.1;REP.6.2;REP.6.3;SO.1.1;SO.1.2;SO.1.3;SO.1.4;SO.2.1;SO.2.2;SO.2.3;SO.2.4;SO.3.1;SO.3.2;SO.3.3;SO.3.4;SO.3.5;SO.3.6;SO.4.1;SO.4.10;SO.4.11;SO.4.12;SO.4.13;SO.4.14;SO.4.15;SO.4.16;SO.4.17;SO.4.18;SO.4.19;SO.4.2;SO.4.20;SO.4.21;SO.4.22;SO.4.23;SO.4.24;SO.4.25;SO.4.26;SO.4.27;SO.4.28;SO.4.29;SO.4.3;SO.4.30;SO.4.31;SO.4.32;SO.4.33;SO.4.34;SO.4.35;SO.4.36;SO.4.37;SO.4.38;SO.4.39;SO.4.4;SO.4.40;SO.4.41;SO.4.5;SO.4.6;SO.4.7;SO.4.8;SO.4.9;SO.5.1;SO.5.2;SO.5.3;SO.6.1;SO.6.10;SO.6.11;SO.6.12;SO.6.13;SO.6.14;SO.6.15;SO.6.16;SO.6.17;SO.6.18;SO.6.19;SO.6.2;SO.6.20;SO.6.21;SO.6.22;SO.6.23;SO.6.24;SO.6.25;SO.6.26;SO.6.27;SO.6.28;SO.6.29;SO.6.3;SO.6.4;SO.6.5;SO.6.6;SO.6.7;SO.6.8;SO.6.9;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;NEW;SW.3.1;SW.3.2;SW.3.3;SW.3.4;SW.2.1;NEW;SW.1.1;SW.1.2;NEW;SMB.1.1;SMB.1.3;SMB.1.4;SMB.1.5;SMB.1.6;SMB.1.7;SMB.2.1;SMB.2.2;SMB.2.3;SMB.2.4;SMB.2.5;SMB.2.6;NEW} |
| Proj_Name | TEMPLATE | Func_Req_ReqTypes | {Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Old Client-specific;Old Improvement Opp;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Narrative;Narrative;Narrative;Narrative;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Standard Req't;Standard Req't;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Improvement Opp;Old Improvement Opp;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Improvement Opp;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Improvement Opp;Old Improvement Opp;Old Improvement Opp;Old Improvement Opp;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Improvement Opp;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Improvement Opp;Old Improvement Opp;Old Improvement Opp;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Improvement Opp;Old Improvement Opp;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Old Improvement Opp;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Old Client-specific;Old Improvement Opp;Old Improvement Opp;Standard Req't;Old Client-specific;Old Client-specific;Old Client-specific;Old Improvement Opp;Old Client-specific;Old Client-specific;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Improvement Opp;Old Improvement Opp;Old Client-specific;Old Client-specific;Old Improvement Opp;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Improvement Opp;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Improvement Opp;Old Improvement Opp;Old Improvement Opp;Old Improvement Opp;Old Client-specific;Old Client-specific;Old Client-specific;Old Improvement Opp;Standard Req't;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Improvement Opp;Old Improvement Opp;Old Client-specific;Old Client-specific;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Old Improvement Opp;Old Improvement Opp;Old Improvement Opp;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Improvement Opp;Old Improvement Opp;Old Improvement Opp;Old Client-specific;Old Improvement Opp;Old Client-specific;Old Improvement Opp;Old Improvement Opp;Old Client-specific;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Old Improvement Opp;Old Improvement Opp;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Old Client-specific;Standard Req't;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Improvement Opp;Old Improvement Opp;Old Client-specific;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Improvement Opp;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Old Improvement Opp;Old Improvement Opp;Old Improvement Opp;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Old Client-specific;Old Improvement Opp;Old Improvement Opp;Old Improvement Opp;Old Improvement Opp;Old Improvement Opp;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Improvement Opp;Old Improvement Opp;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Improvement Opp;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Client-specific;Standard Req't;Standard Req't;Old Client-specific;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Standard Req't;Old Improvement Opp} |
| Proj_Active | |||
| Proj_Date_Start | |||
| Proj_Hrly_Rate | |||
| Proj_Location_City | |||
| Proj_Location_State | |||
| Proj_Location_Zip | |||
| Proj_Date_End | |||
| Proj_Date_End_Est | |||
| Proj_Tot_Proj_Value | |||
| Proj_Tot_Proj_Hours | |||
| Proj_Tot_Travel | |||
| Proj_Opps_OppNums | |||
| Proj_Opps_ReqIDs | |||
| Proj_Opps_ReqTypes | |||
| Proj_Opps_CustScores | |||
| Proj_Opps_OperScores | |||
| Proj_Reqts_ReqIDs | |||
| Proj_Reqts_ReqTypes | |||
| Proj_Planning_Tot_Hours | |||
| Proj_Planning_Func_Grps | |||
| Proj_Planning_Func_GrpNums |
Refresh Data & Push to Seed
INPUT DATA
OUTPUT DATA
Refresh "Out" Data (this sheet only) Refresh Data (this Doc only)
Functional Requirements - CIS
| FUNCTIONAL REQUIREMENTS - TEMPLATE | |||||||||||||||||||
| Feed from Improvement Opps doc | Feed from QA doc | Feed from Improvement Opps doc | |||||||||||||||||
| Serialized | Req ID | Group | Topic | Sub Order | Requirement Type | Opp # | Functional Group | Topic | Notes from Discovery | Response Type | Requirement | Demo (Y/N) | Priority | Value | WCG Notes | Customer | |||
| Enhancement | Operational | ||||||||||||||||||
| Improvement | TOTAL | ||||||||||||||||||
| 1 | ADJ.1.1 | ADJ | 1 | 1 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to associate adjustment types with a corresponding G/L account number | N | 1 - Must Have | 25 | - 0 | ||||||
| 2 | ADJ.1.10 | ADJ | 1 | 10 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to identify bills that have been cancel/re-billed | N | 1 - Must Have | 25 | - 0 | ||||||
| 3 | ADJ.1.11 | ADJ | 1 | 11 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to include all transactions on a particular bill in the cancel/rebill process | N | 1 - Must Have | 25 | - 0 | ||||||
| 4 | ADJ.1.12 | ADJ | 1 | 12 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to restrict bill adjustment types by user or user group | Y | 1 - Must Have | 25 | - 0 | ||||||
| 5 | ADJ.1.13 | ADJ | 1 | 13 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to restrict bill adjustment amounts by user or user group | N | 2 - Desirable | 15 | - 0 | ||||||
| 6 | ADJ.1.14 | ADJ | 1 | 14 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to restrict employees of the utility from making adjustments to their own bills | N | 1 - Must Have | 25 | - 0 | ||||||
| 7 | ADJ.1.15 | ADJ | 1 | 15 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to easily capture and display details of bill adjustment activity by user, user group, or system-wide | N | 1 - Must Have | 25 | - 0 | ||||||
| 8 | ADJ.1.16 | ADJ | 1 | 16 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to assign adjustment reason codes to each transaction as defined by the utility | N | 1 - Must Have | 25 | - 0 | ||||||
| 9 | ADJ.1.17 | ADJ | 1 | 17 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to transfer balances in a single transaction between accounts with an audit trail | Y | 1 - Must Have | 25 | - 0 | ||||||
| 10 | ADJ.1.18 | ADJ | 1 | 18 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to easily adjust in one screen for cross connect/switched meters where the system will cancel/re-bill affected accounts with corrected readings for the period of time specified by the user | N | 1 - Must Have | 25 | - 0 | ||||||
| 11 | ADJ.1.19 | ADJ | 1 | 19 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to process cross connects/switched meters that are not installed or billed on the same date for the period of time specified by the user | N | 1 - Must Have | 25 | - 0 | ||||||
| 12 | ADJ.1.2 | ADJ | 1 | 2 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to adjust bills on finaled accounts | N | 1 - Must Have | 25 | - 0 | ||||||
| 13 | ADJ.1.20 | ADJ | 1 | 20 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to automatically remove transactions that were entered as part of an erroneous move-in/move-out with an audit trail, as part of the move-in/move-out UNDO functionality | N | 1 - Must Have | 25 | - 0 | ||||||
| 14 | ADJ.1.21 | ADJ | 1 | 21 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to selectively choose which items on the bill to cancel/re-bill without changing unselected items and have the system automatically re-calculate or populate dependent charges | N | 2 - Desirable | 15 | - 0 | ||||||
| 15 | ADJ.1.22 | ADJ | 1 | 22 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to simplify process to calculate and complete adjustments (e.g. work flow) | Y | 1 - Must Have | 25 | - 0 | ||||||
| 16 | ADJ.1.23 | ADJ | 1 | 23 | Standard Req't | Adjustments | Bill Adjustment | Requirement | When a customer moves-out of a location, the existing balance, FINAL bill, and all payments should be customer-based with no risk of associating balances and payments with any incoming customers to the old premise - thus, no manual adjustments nor transfers will be required | Y | 1 - Must Have | 25 | - 0 | ||||||
| 17 | ADJ.1.24 | ADJ | 1 | 24 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to make an adjustment as a single entry that affects multiple Transaction Codes/Item Types/etc. at one time | Y | 1 - Must Have | 25 | - 0 | ||||||
| 18 | ADJ.1.25 | ADJ | 1 | 25 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to pass responsibility, notes, and actions across groups | Y | 1 - Must Have | 25 | - 0 | ||||||
| 19 | ADJ.1.3 | ADJ | 1 | 3 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to adjust specific historic charges on an account | N | 1 - Must Have | 25 | - 0 | ||||||
| 20 | ADJ.1.4 | ADJ | 1 | 4 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to rebill historic bills using historic effective rates for the date specified | N | 1 - Must Have | 25 | - 0 | ||||||
| 21 | ADJ.1.5 | ADJ | 1 | 5 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to back bill for a user-defined time period using historic effective rates for the time period specified | Y | 1 - Must Have | 25 | - 0 | ||||||
| 22 | ADJ.1.6 | ADJ | 1 | 6 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to correct an inaccurate reading, consumption amount, fee, tax, or other transaction item on a historic bill and adjust the bill accordingly | N | 1 - Must Have | 25 | - 0 | ||||||
| 23 | ADJ.1.7 | ADJ | 1 | 7 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to cancel/re-bill entire routes, book, cycles, or batches | Y | 1 - Must Have | 25 | - 0 | ||||||
| 24 | ADJ.1.8 | ADJ | 1 | 8 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to cancel/re-bill a bill that was previously cancel/re-billed | N | 1 - Must Have | 25 | - 0 | ||||||
| 25 | ADJ.1.9 | ADJ | 1 | 9 | Standard Req't | Adjustments | Bill Adjustment | Requirement | Ability to automatically generate G/L entries related to the services being cancel/re-billed | N | 1 - Must Have | 25 | - 0 | ||||||
| 26 | NEW | ADJ | Old Client-specific | Adjustments | Bill Adjustment | Requirement | Ability to use cancel/rebill for bills that stretch over multiple periods | - 0 | |||||||||||
| 27 | NEW | ADJ | Old Client-specific | Adjustments | Bill Adjustment | Requirement | Ability to provide role based security vs. form security and will also hold the audit trail of the user | - 0 | |||||||||||
| 28 | NEW | ADJ | Old Client-specific | Adjustments | Bill Adjustment | Requirement | Ability to put collection activities on hold temporarily based on nature of the dispute/adjustment | - 0 | |||||||||||
| 29 | NEW | ADJ | Old Improvement Opp | Adjustments | Bill Adjustment | Requirement | In the case of working a customer dispute, the system has the ability to accept notes in a format that can be queried and reported on | - 0 | |||||||||||
| 30 | NEW | ADJ | Old Improvement Opp | Adjustments | Bill Adjustment | Requirement | Ability to standardize the adjustment calculation process and protocols to allow for maximum automation and intelligent calculations/checks inside of the system; needs to take various rates/tiers into consideration along with protocols around whether water/sewer is being adjusted given the scenario | - 0 | |||||||||||
| 31 | ADJ.2.1 | ADJ | 2 | 1 | Standard Req't | Adjustments | Meter Reading & Consumption | Requirement | Ability to manually calculate and enter estimated readings | N | 1 - Must Have | 25 | - 0 | ||||||
| 32 | ADJ.2.2 | ADJ | 2 | 2 | Standard Req't | Adjustments | Meter Reading & Consumption | Requirement | Ability to make meter reading adjustments with an audit trail without overriding the original read or billed reading | N | 1 - Must Have | 25 | - 0 | ||||||
| 33 | ADJ.2.3 | ADJ | 2 | 3 | Standard Req't | Adjustments | Meter Reading & Consumption | Requirement | Ability to make consumption adjustments with an audit trail without changing the amount actually used | N | 1 - Must Have | 25 | - 0 | ||||||
| 34 | ADJ.2.4 | ADJ | 2 | 4 | Standard Req't | Adjustments | Meter Reading & Consumption | Requirement | Ability to make both positive and negative consumption adjustments with an audit trail | N | 1 - Must Have | 25 | - 0 | ||||||
| 35 | ADJ.2.5 | ADJ | 2 | 5 | Standard Req't | Adjustments | Meter Reading & Consumption | Requirement | Ability to restrict utility employees from making meter reading adjustments to their own accounts | N | 1 - Must Have | 25 | - 0 | ||||||
| 36 | ADJ.2.6 | ADJ | 2 | 6 | Standard Req't | Adjustments | Meter Reading & Consumption | Requirement | Ability to restrict meter reading and consumption adjustments by user or user group | N | 1 - Must Have | 25 | - 0 | ||||||
| 37 | ADJ.2.7 | ADJ | 2 | 7 | Standard Req't | Adjustments | Meter Reading & Consumption | Requirement | Ability to limit meter reading and consumption adjustments amounts by user or user group | N | 2 - Desirable | 15 | - 0 | ||||||
| 38 | ADJ.2.8 | ADJ | 2 | 8 | Standard Req't | Adjustments | Meter Reading & Consumption | Requirement | Ability to automate notification when leaks occur with Service Line Care customers | Y | 1 - Must Have | 25 | - 0 | ||||||
| 39 | ADJ.3.1 | ADJ | 3 | 1 | Standard Req't | Adjustments | Non-Consumption Items | Requirement | Ability to make adjustments to non-consumption related items on an account with an audit trail | N | 1 - Must Have | 25 | - 0 | ||||||
| 40 | ADJ.3.2 | ADJ | 3 | 2 | Standard Req't | Adjustments | Non-Consumption Items | Requirement | Ability to make adjustments to penalties and fees with an audit trail | N | 1 - Must Have | 25 | - 0 | ||||||
| 41 | ADJ.3.3 | ADJ | 3 | 3 | Standard Req't | Adjustments | Non-Consumption Items | Requirement | Ability to restrict adjustments to non-consumption items, penalties, and fees by user or user group | N | 2 - Desirable | 15 | - 0 | ||||||
| 42 | NEW | ADJ | Old Client-specific | Adjustments | Customer Disputes | Requirement | In the case of a customer disputing a charge, the system has the ability to put the dispute amount "on-hold" to where it is not affecting the customer's ledger balance while the issue is being investigated and worked. | - 0 | |||||||||||
| 43 | NEW | ADJ | Old Client-specific | Adjustments | Customer Disputes | Requirement | When there is a customer dispute amount on-hold, the system will update the effect to to collections activities and present this updated balance not including the on-hold amount across all balance presentations (e.g. customer bills, notices, CSS portal, customer service views) | - 0 | |||||||||||
| 44 | NEW | AMI | Narrative | AMI | Billing Request/Response | Requirement | Describe how the system is able to generate a bill request and how the response is processed from the AMI system | - 0 | |||||||||||
| 45 | NEW | AMI | Narrative | AMI | On Demand Read | Requirement | Describe the process for a customer service agent to generate an on demand read in the system | - 0 | |||||||||||
| 46 | NEW | AMI | Narrative | AMI | Provisioning | Requirement | Describe your experience integrating with meter and module manufacturing to support AMI deployment and maintenance activities | - 0 | |||||||||||
| 47 | NEW | AMI | Narrative | AMI | Provisioning | Requirement | Describe your experience integrating with meter and module deployment vendors to support AMI deployment and maintenance activities | - 0 | |||||||||||
| 48 | NEW | BFLW | Old Client-specific | Backflow | Charges / Fees | Requirement | Ability to assess unique fees for backflow services while completing the order based upon the type of work performed | - 0 | |||||||||||
| 49 | NEW | BFLW | Old Client-specific | Backflow | Device Management | Requirement | The backflow device must be recorded in the component inventory system and be tracked by serial number. | - 0 | |||||||||||
| 50 | NEW | BFLW | Old Client-specific | Backflow | Testing | Requirement | Backflow devices have the ability to be tested annually and the system will store all backflow test results | - 0 | |||||||||||
| 51 | NEW | BFLW | Old Client-specific | Backflow | Letter Generation | Requirement | System has the ability to automate letter generation and other means of customer communication by utilizing logic driven by the number of days from the annual test date | - 0 | |||||||||||
| 52 | NEW | BFLW | Old Client-specific | Backflow | Communication / Interfaces | Requirement | The system can provide backflow information and testing data to the chosen customer through the self-service module | - 0 | |||||||||||
| 53 | NEW | BFLW | Old Client-specific | Backflow | Site Inspection Service Order | Requirement | The system has the ability to leverage the core service order functionality to generate backflow-related site inspections and other needed service orders, including utility defined service order and resolution codes | - 0 | |||||||||||
| 54 | NEW | BFLW | Old Client-specific | Backflow | Plumber Portal | Requirement | The system provides a web-based functionality allowing plumbing professionals to enter backflow test data that will then feed to the CIS system | - 0 | |||||||||||
| 55 | DEBT.1.1 | DEBT | 1 | 1 | Standard Req't | Bad Debt | Alerts | Requirement | System provides alerts for bankruptcies, write-offs, bad debts, etc. | N | 1 - Must Have | 25 | - 0 | ||||||
| 56 | DEBT.2.1 | DEBT | 2 | 1 | Standard Req't | Bad Debt | Bankruptcy | Requirement | System provides the ability to categorize the different types of bankruptcies | N | 3 - Low Priority | 5 | - 0 | ||||||
| 57 | NEW | DEBT | Old Improvement Opp | Bad Debt | Bankruptcy | Requirement | Once an account has been marked as "Bankrupt", the system should automatically transfer any collectable charges that post after the bankruptcy petition date to a new account | - 0 | |||||||||||
| 58 | DEBT.3.10 | DEBT | 3 | 10 | Standard Req't | Bad Debt | Write-Offs | Requirement | System provides the ability to create a file of written off accounts to send to a collection agency | N | 1 - Must Have | 25 | - 0 | ||||||
| 59 | DEBT.3.11 | DEBT | 3 | 11 | Standard Req't | Bad Debt | Write-Offs | Requirement | System provides the ability to compare written off accounts with city records where customer still owns property. | N | 2 - Desirable | 15 | - 0 | ||||||
| 60 | DEBT.3.2 | DEBT | 3 | 2 | Standard Req't | Bad Debt | Write-Offs | Requirement | System provides the ability to automatically select accounts for write-off, based upon user-defined criteria | N | 1 - Must Have | 25 | - 0 | ||||||
| 61 | DEBT.3.3 | DEBT | 3 | 3 | Standard Req't | Bad Debt | Write-Offs | Requirement | System provides the ability to track when and how much an account was written off for | N | 1 - Must Have | 25 | - 0 | ||||||
| 62 | DEBT.3.4 | DEBT | 3 | 4 | Standard Req't | Bad Debt | Write-Offs | Requirement | System provides the ability to view at the customer-level historical write-offs for accounts that pertain to that customer | N | 1 - Must Have | 25 | - 0 | ||||||
| 63 | DEBT.3.5 | DEBT | 3 | 5 | Standard Req't | Bad Debt | Write-Offs | Requirement | System provides the ability to re-activate customers that have been previously written-off | N | 1 - Must Have | 25 | - 0 | ||||||
| 64 | DEBT.3.6 | DEBT | 3 | 6 | Standard Req't | Bad Debt | Write-Offs | Requirement | System prevents a user from re-activating a customer account in write-off status without collecting the write-off amount, but with the option to override | N | 1 - Must Have | 25 | - 0 | ||||||
| 65 | DEBT.3.7 | DEBT | 3 | 7 | Standard Req't | Bad Debt | Write-Offs | Requirement | System to flag user when a customer with write-off history wants to create a new account | Y | 1 - Must Have | 25 | - 0 | ||||||
| 66 | DEBT.3.8 | DEBT | 3 | 8 | Standard Req't | Bad Debt | Write-Offs | Requirement | Ability for write-off process to include a step that looks for other active accts | Y | 1 - Must Have | 25 | - 0 | ||||||
| 67 | DEBT.3.9 | DEBT | 3 | 9 | Standard Req't | Bad Debt | Write-Offs | Requirement | System provides the ability to manually write-off selected charges | Y | 1 - Must Have | 25 | - 0 | ||||||
| 68 | NEW | DEBT | Old Client-specific | Bad Debt | Notes | Requirement | Ability to add document attachments to an account to support Bankruptcy history and processing | - 0 | |||||||||||
| 69 | NEW | BCL | Old Improvement Opp | Bill Calculation | Bill Adjustments | Requirement | System allows for leak adjustment to be calculated inside the CIS based on calculated tiered usage and not reliant on outside calculations | - 0 | |||||||||||
| 70 | NEW | BCL | Old Improvement Opp | Bill Calculation | Bill Adjustments | Requirement | After completing a leak adjustment, the system has the ability to immediately update the balance and allow the customer to view the updated balance (via CSS) as opposed to having to wait until the following billing period to view the adjusted amount and its affect on the balance | - 0 | |||||||||||
| 71 | NEW | BCL | Old Improvement Opp | Bill Calculation | Bill Adjustments | Requirement | When an adjustment is processed, the system has the ability to trigger a customer notification using the customer's stored communication preference based on user-defined criteria and adjustment types/status | - 0 | |||||||||||
| 72 | BCL.1.1 | BCL | 1 | 1 | Standard Req't | Bill Calculation | Bill Calculations | Requirement | Ability to calculate and bill for all products and services on a single bill, including both metered and unmetered services | N | 1 - Must Have | 25 | - 0 | ||||||
| 73 | BCL.1.2 | BCL | 1 | 2 | Standard Req't | Bill Calculation | Bill Calculations | Requirement | Ability for a line-item charge to be the product of any given rate and any user-defined data items, including but not limited to: consumption amount, multipliers, residential equivalent units, etc. | N | 1 - Must Have | 25 | - 0 | ||||||
| 74 | BCL.1.3 | BCL | 1 | 3 | Standard Req't | Bill Calculation | Bill Calculations | Requirement | Ability to provide an on-screen bill calculation for a single bill and generate a sample bill print | N | 1 - Must Have | 25 | - 0 | ||||||
| 75 | BCL.1.4 | BCL | 1 | 4 | Standard Req't | Bill Calculation | Bill Calculations | Requirement | Ability to provide an on-screen bill calculation for a complete route and generate a sample bill print | N | 1 - Must Have | 25 | - 0 | ||||||
| 76 | BCL.1.5 | BCL | 1 | 5 | Standard Req't | Bill Calculation | Bill Calculations | Requirement | Ability to alter the hi/lo calculations | Y | 1 - Must Have | 25 | - 0 | ||||||
| 77 | BCL.1.6 | BCL | 1 | 6 | Standard Req't | Bill Calculation | Bill Calculations | Requirement | Ability to base hi/lo calculations on percent changes, considering seasonal effects, a combination of month over month, trailing 3 - 12 months, same period prior year, etc. (flexibility with calculation options) | Y | 1 - Must Have | 25 | - 0 | ||||||
| 78 | NEW | BCL | Old Improvement Opp | Bill Calculation | Bill Errors | Requirement | |||||||||||||
| Ability for the system to alert/flag and prioritize re-read service orders based on user defined criteria with the goal of avoiding billing errors (e.g. adjustments for additional days of service). | - 0 | ||||||||||||||||||
| 79 | BCL.2.1 | BCL | 2 | 1 | Standard Req't | Bill Calculation | Bill Exception | Requirement | Ability to exclude certain locations, accounts, and/or meters from the billing exception process | N | 1 - Must Have | 25 | - 0 | ||||||
| 80 | BCL.2.2 | BCL | 2 | 2 | Standard Req't | Bill Calculation | Bill Exception | Requirement | Ability to limit the number of days a bill exception can stay in limbo | N | 2 - Desirable | 15 | - 0 | ||||||
| 81 | BCL.2.3 | BCL | 2 | 3 | Standard Req't | Bill Calculation | Bill Exception | Requirement | Ability to group all exceptions by exception type and have unique metrics | Y | 1 - Must Have | 25 | - 0 | ||||||
| 82 | BCL.2.4 | BCL | 2 | 4 | Standard Req't | Bill Calculation | Bill Exception | Requirement | Ability to exclude Continuous Consumption accounts from the exception report | Y | 1 - Must Have | 25 | - 0 | ||||||
| 83 | BCL.2.5 | BCL | 2 | 5 | Standard Req't | Bill Calculation | Bill Exception | Requirement | Ability to report running 3-month/6-month consumption avg as part of the billing exception validation process (in a portal or something of the sort to quickly see the variance/degree of outlier) | Y | 1 - Must Have | 25 | - 0 | ||||||
| 84 | NEW | BCL | Old Client-specific | Bill Calculation | Bill Exception | Requirement | Ability to identify an account as being in a reading exception status and indicate if the reading is high, low, neg, missing, etc. | - 0 | |||||||||||
| 85 | BCL.3.1 | BCL | 3 | 1 | Standard Req't | Bill Calculation | Bill Generation | Requirement | Ability to not bill an account if active less than a user-defined number of days | N | 1 - Must Have | 25 | - 0 | ||||||
| 86 | BCL.3.10 | BCL | 3 | 10 | Standard Req't | Bill Calculation | Bill Generation | Requirement | Ability to bill both monthly and bi-monthly for the same account | N | 2 - Desirable | 15 | - 0 | ||||||
| 87 | BCL.3.2 | BCL | 3 | 2 | Standard Req't | Bill Calculation | Bill Generation | Requirement | Ability to bill only certain charges if an account is active less than a user-defined number of days | Y | 1 - Must Have | 25 | - 0 | ||||||
| 88 | BCL.3.3 | BCL | 3 | 3 | Standard Req't | Bill Calculation | Bill Generation | Requirement | Ability to accommodate back billing for a single period with a user-defined start and end date | N | 1 - Must Have | 25 | - 0 | ||||||
| 89 | BCL.3.4 | BCL | 3 | 4 | Standard Req't | Bill Calculation | Bill Generation | Requirement | Ability to accommodate back billing for multiple periods with a user-defined start and end date | N | 1 - Must Have | 25 | - 0 | ||||||
| 90 | BCL.3.5 | BCL | 3 | 5 | Standard Req't | Bill Calculation | Bill Generation | Requirement | Ability for on-screen bill production for a single bill that will not require batch or nightly processing; bill will be generated after calculations have been processed | Y | 1 - Must Have | 25 | - 0 | ||||||
| 91 | BCL.3.6 | BCL | 3 | 6 | Standard Req't | Bill Calculation | Bill Generation | Requirement | Ability to identify accounts and bills that did not generate when the account met the system criteria to generate a bill, but due to reading or other errors, a bill was not generated | Y | 1 - Must Have | 25 | - 0 | ||||||
| 92 | BCL.3.7 | BCL | 3 | 7 | Standard Req't | Bill Calculation | Bill Generation | Requirement | Ability to generate a one-time miscellaneous bill to an existing customer | N | 2 - Desirable | 15 | - 0 | ||||||
| 93 | BCL.3.8 | BCL | 3 | 8 | Standard Req't | Bill Calculation | Bill Generation | Requirement | Ability to generate a one-time miscellaneous bill to a non-utility customer | N | 2 - Desirable | 15 | - 0 | ||||||
| 94 | BCL.3.9 | BCL | 3 | 9 | Standard Req't | Bill Calculation | Bill Generation | Requirement | Ability for Continuous Consumption communication and information to be readily available and visible to all parties | Y | 1 - Must Have | 25 | - 0 | ||||||
| 95 | NEW | BCL | Old Improvement Opp | Bill Calculation | Bill Generation | Requirement | Ability to identify active accounts that have not billed in CIS over multiple periods and prompt research of the account | - 0 | |||||||||||
| 96 | BCL.4.1 | BCL | 4 | 1 | Standard Req't | Bill Calculation | Bill Proration | Requirement | Ability to prorate a new bill based on the number of active days | N | 1 - Must Have | 25 | - 0 | ||||||
| 97 | BCL.4.2 | BCL | 4 | 2 | Standard Req't | Bill Calculation | Bill Proration | Requirement | Ability to prorate a final bill based on the number of active days | N | 1 - Must Have | 25 | - 0 | ||||||
| 98 | BCL.4.3 | BCL | 4 | 3 | Standard Req't | Bill Calculation | Bill Proration | Requirement | Ability to turn off specific proration types that included rate change, initial bill, final bill, and number of days in billing period | N | 1 - Must Have | 25 | - 0 | ||||||
| 99 | BCL.4.4 | BCL | 4 | 4 | Standard Req't | Bill Calculation | Bill Proration | Requirement | Ability to prorate non-consumption based charges and credits based on a user-defined number of days in the billing cycle | N | 1 - Must Have | 25 | - 0 | ||||||
| 100 | BCL.4.5 | BCL | 4 | 5 | Standard Req't | Bill Calculation | Bill Proration | Requirement | Ability to prorate dollar amount by number of days (e.g. $3 per month customer charge = $0.10 per day) | N | 1 - Must Have | 25 | - 0 | ||||||
| 101 | BCL.4.6 | BCL | 4 | 6 | Standard Req't | Bill Calculation | Bill Proration | Requirement | Ability to prorate gallon consumption by number of days (e.g. 30 gallon per month = 1 gallon per day) | N | 1 - Must Have | 25 | - 0 | ||||||
| 102 | BCL.4.7 | BCL | 4 | 7 | Standard Req't | Bill Calculation | Bill Proration | Requirement | Ability to not prorate a bill when billing days are less than a user-defined number of days | N | 1 - Must Have | 25 | - 0 | ||||||
| 103 | BCL.4.8 | BCL | 4 | 8 | Standard Req't | Bill Calculation | Bill Proration | Requirement | Ability to reflect prorated detailed amounts on customer's bill due to rate change during billing period | N | 3 - Low Priority | 5 | - 0 | ||||||
| 104 | BCL.5.1 | BCL | 5 | 1 | Standard Req't | Bill Calculation | Charges & Fees | Requirement | Ability to accommodate fee exemptions | N | 1 - Must Have | 25 | - 0 |
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 .