Attachment_F_-_Requirements.xlsx
XLSX spreadsheet 55 KB Posted
- Solicitation number
- 0000034655
- Issued by
- California
About this file
This is a detailed requirements document for the California Public Utilities Commission (CPUC) focused on developing a comprehensive digital system for managing various regulatory reporting and compliance functions across multiple service provider domains. The system requirements cover seven primary functional areas: ETC (Eligible Telecommunications Carriers) Eligibility, Network Resiliency, Service Quality, Major Service Interruption (MSI), Tariffs, Site Visits, and General Platform Capabilities. The requirements document includes 98 functional requirements and 96 non-functional requirements, totaling 194 specific system specifications that outline detailed technical and operational expectations for a web-based Software as a Service (SaaS) solution.
The proposed system must support multiple concurrent users, integrate with various external systems like FCC databases, PAL system, and Cal OES platforms, and provide robust security, reporting, and workflow management capabilities. Key technical specifications include HTML5 compliance, role-based access control, support for multiple document formats, integration using MuleSoft, encryption standards, and compliance with California state accessibility and security regulations. The system must enable service providers to submit various reports, including resiliency plans, service quality metrics, tariffs, and outage information, while allowing CPUC staff comprehensive review, analysis, and tracking functionalities across different regulatory domains.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachment_C_-_Respondent_Questionaire.docx | DOCX document | |
| Attachment_B-_Solution_Cost_Estimate.xlsx | XLSX spreadsheet | |
| RFI_24ITC0680_-_Communications_Data_Portal.pdf | ||
| Attachment_D_-_Process_Flows-As_Is.pptx | PPTX presentation | |
| Attachment_A-_Letter_of_Interest.docx | DOCX document | |
| Attachment_E_-_Process_Flows-To_Be.pptx | PPTX presentation |
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
Summary
| Requirement Type | Count |
| Functional Requirements | 98 |
| NonFunctional Requirements | 96 |
| Total | 194 |
| Requiremnts tasks (completed before July) | |
| 1. Updated requirements per Anil final review and two reviews with Steve | |
| 2. Moved several requirements to nonfunctional – including Admin category requirements | |
| 3. Fixed categories that only had one requirement each (4) | |
| 4. Cleaned up all fonts and comments | |
| 5. Renumbered requirements | |
| 6. Hid process steps until they are updated from process flow updates (below) | |
| 7. Hid old numbers for traceability | |
| Process Flow updates in July | |
| 1. Reviewed General process steps | |
| 2. Applie As-Is changes to To-Be | |
| 3. Applied General steps to both To-Be and As-Is | |
| 4. Applied subprogram-level steps to both To-Be and As-Is | |
| 5. Reset process steps in Requirements | |
| 6. Cross reviewed As-Is with To-Be flows |
by Subprogram
| old | Process | ID | Source | Code | Subprogram | Category | Summary | Description | |
| 2 | 1 | 1 | Resolution T-17002 | ETC | ETC Eligibility | File uploads | Annual HC self-certification application | The system must be able to accept Annual ETC 54.314 Hi-Cost self-certification applications from providers as a part of annual filing through the advice letter process. | |
| 3 | 1 | 2 | Resolution T-17002 | ETC | ETC Eligibility | Report intake | Two-year service quality improvement plan | The system must be able to accept a quality improvement plan as part of the biannual advice letter recertification submission process. | |
| 4 | 1 | 3 | Resolution T-17002 | ETC | ETC Eligibility | Report intake | Outage information | The system must be able to accept detailed outage information as part of the biannual advice letter recertification submission process. | |
| 5 | 1 | 4 | Resolution T-17002 | ETC | ETC Eligibility | Report intake | Number of unfulfilled requests for service | The system must be able to accept the number of unfulfilled service requests as part of the biannual advice letter recertification submission process. | |
| 7 | 4 | 5 | Best Practice | ETC | ETC Eligibility | Report review | Provide workflow statuses | The system must allow biennial submissions to be statused according to a TBD workflow. | |
| 6 | 4 | 6 | Best Practice | ETC | ETC Eligibility | Report review | Provide interface for reviewing | The system must provide an internal to CPUC interface to review biennial reports, annual ETC applications self-certification summary as well as its detail filed by the providers. | |
| 16 | 4 | 7 | FS 2023-08-22 | ETC | ETC Eligibility | Eligibility Review | Enter any unaddressed filings | The system must allow CPUC staff to enter data on unaddressed filings while reviewing applications and biennial recertifications. | |
| 17 | 4 | 8 | FS 2023-08-22 | ETC | ETC Eligibility | Eligibility Review | Enter any program and/or subprogram history (e.g. RDOF) | The system must allow CPUC staff to enter data on any program or subprogram history (e.g. RDOF) while reviewing ETC applications and biennial reports. | |
| 18 | 4 | 9 | FS 2023-08-22 | ETC | ETC Eligibility | Eligibility Review | Enter any felonies or bankruptcies | The system must allow CPUC staff to enter data on felonies or bankruptcies (including, but not limited to UEB background check information) while reviewing ETC applications, Hi-cost self-certifications, and biennial reports. | |
| 10 | 8 | 10 | FS 2023-08-22 | ETC | ETC Eligibility | GIS | GIS for Outage information | The system must be able to accept ArcGIS compatible shape (SHP) files for detailed outage information submissions. | |
| 11 | 8 | 11 | FS 2023-08-22 | ETC | ETC Eligibility | GIS | GIS for at least two years service quality improvement plan | The system must be able to accept ArcGIS compatible shape (SHP) files for locations associated with ETC applications that include service quality improvement plans for a given geography that they are submitting the application. | |
| 12 | 8 | 12 | FS 2023-08-22 | ETC | ETC Eligibility | Eligibility Review | TUFFS integration to validate Service Provider financial status | The system must be able to integrate with TUFFS to confirm whether a Service Provider is paid up on all financial obligations. | |
| 13 | 8 | 13 | FS 2023-08-22 | ETC | ETC Eligibility | Eligibility Review | UCS integration to update Company information | The system must be able to receive read-only updates from the CPUC UCS system on changes to company account information such as name, address, phone or DBA. | |
| 14 | 8 | 14 | FS 2023-08-22 | ETC | ETC Eligibility | Eligibility Review | UCS integration to update primary contact information | The system must be able to receive read-only updates from the CPUC UCS system on changes to company primary contact information. | |
| 15 | 8 | 15 | FS 2023-08-22 | ETC | ETC Eligibility | Eligibility Review | Service Quality data integration for violations | The system must be able to integrate with Service Quality data to confirm whether a Service Provider has any unresolved violations. | |
| 19 | 8 | 16 | FS 2023-08-22 | ETC | ETC Eligibility | Integration | PAL integration-high priority | The system must be able to automatically send and recieve updates to the PAL system regarding ETC applications filings, and self-certications and/or recertification statuses. | |
| 8 | 12 | 17 | Best Practice | ETC | ETC Eligibility | Notifications | Notify of status changes | The system must be able to send notifications to application submitters or provider to notify them of status changes according to a to-be workflow. | |
| 37 | 1 | 18 | Anil | Gen | General | Report intake | Plan submission | The system must be able to receive online plans from the service providers (e.g. Emergency Operations Plans, Communication Plans). | |
| 87 | 1 | 19 | Anil | Gen | General | Report intake | Report Submission | The system must be able to receive online reports from the service providers | |
| 88 | 2 | 20 | Anil and Risa | Gen | General | Report intake | Report supplements | The system must be able to receive online report supplements from the service providers. | |
| 63 | 2 | 21 | Anil | Gen | General | Analysis | Report supplement submission | The system must permit the recipient(s) to upload the various sets of data in a specific format (e.g. *.csv or *.xlsx) to correlate with a plan or a group of plans or all the plans. | |
| 42 | 2 | 22 | Anil | Gen | General | Report intake | Document formats allowed | The system must permit service providers to upload all plans, reports, supplements and corrections in a suitable format (e.g. *.csv or *.xlsx or *.docx or *.PDF). | |
| 43 | 2 | 23 | Anil | Gen | General | File uploads | CSV upload error checking | The system must detect upload error(s) based on the rules specified for a bulk upload file (plans, reports or raw data) template and permit a submitter to fix those errors before the final submission. | |
| 3 | 24 | Anil | Gen | General | Workflow | Grace period start | The system must log the Grace period start date/time once a report or plan is submitted for review and acceptance by the CPUC. | ||
| 47 | 5 | 25 | FS 2023-08-16 | Gen | General | Report intake | Disposition workflow | The system must support Advice Letter (AL) deadlines and grace periods for submissions. Upon AL submission a 20 day protest period window must be provided followed by a 10-day period to equal the full 30 day initial dispostion period. If no disposition action taken such as approved, reject or suspend within 30 day window then the AL will be by default automatically gets approved as per General Order (G.O.) 96-B. | |
| 46 | 5 | 26 | FS 2023-08-16 | Gen | General | File uploads | CPUC request corrections | The system must allow CPUC staff to request corrections and for file (plans, reports or raw data) submitters to make the corrections (eg missing information, errors) through a web portal. | |
| 48 | 5 | 27 | FS 2023-08-16 | Gen | General | Workflow | Disposition workflow | The system must allow for a suspension if the submitter could not complete the submission on time. | |
| 110 | 5 | 28 | FS 2023-08-16 | Gen | General | Report intake | Disposition workflow | The system must support rejection of a resiliency plan submission. After rejection, a new submission can only occur with a new advice letter filing. | |
| 49 | 6 | 29 | FS 2023-08-16 | Gen | General | Notifications | Notification of deadlines | The system must notify both CPUC staff and service providers of the protest and disposition date deadlines prior to the deadlines for plans and advice letters (triggered from the PAL system). | |
| 89 | 7 | 30 | Anil and Risa | Gen | General | Report intake | Post approval report corrections | The system must be able to receive and process online report corrections from the service providers after approval by the CPUC. | |
| 53 | 8 | 31 | Anil | Gen | General | Integration | Receive data (general) | The system must be able to integrate with other systems to send or receive the information in an automated manner. Examples include ArcGIS, PAL system, Cal OES 911 outage dashboard system and census tract data. | |
| 54 | 8 | 32 | Anil and Risa | Gen | General | Integration | Receive data (general) | The system must provide interfaces to support integrations with future, unknown systems. | |
| 55 | 8 | 33 | Anil | Gen | General | Integration | Receive data (GIS) | The system must permit the recipient(s) to obtain the maps and shapefile from the ArcGIS system. | |
| 56 | 8 | 34 | Anil | Gen | General | Integration | Send data (PAL) | The system must permit the recipient(s) to transmit information to the PAL system for the Advice Letter disposition. | |
| 52 | 9 | 35 | FS 2023-08-16 | Gen | General | Analysis | Ad Hoc reporting | The system must allow a user to query any fields in the data set. | |
| 58 | 9 | 36 | FS 2023-08-16 | Gen | General | Analysis | Dashboard for analysis visualizations | The system must provide a Dashboard view of data visualizations to support analysis (both trending or time-based, and static). | |
| 59 | 9 | 37 | FS 2023-08-16 | Gen | General | Analysis | Report/plan correlation with other reports/plans | The system must be able to reconcile submitted plans/reports with previously submitted plans/reports to ID correlation exceptions. | |
| 60 | 9 | 38 | Anil | Gen | General | Analysis | Report correlation with other reports | The system must permit the plan recipient(s) to create a customized correlation report. | |
| 61 | 9 | 39 | Anil | Gen | General | Analysis | Report on submitter details | The system must provide a customized report for a specific period regarding the plan submitter and other details, such as the date and time stamp of the plan submitted, any system/application errors encountered during the plan submission, etc. | |
| 62 | 9 | 40 | Anil | Gen | General | Analysis | Custom report support | The system must permit the plan recipient(s) to create a customized report. | |
| 65 | 9 | 41 | Anil | Gen | General | File export | Export plans (service providers) | The system must allow service providers to export a submitted plan or report in a suitable format (e.g. *.csv or *.xlsx or *.PDF). | |
| 66 | 9 | 42 | Anil | Gen | General | File export | Export plans (recipients) | The system must allow the recipients(s) to download a plan/report or a group of plans/reports or all the plans/reports in a suitable format (e.g. *.csv or *.xlsx or *.docx or *.PDF). | |
| 32 | 9 | 43 | FS 2023-08-17 | Gen | General | Analysis | Export data to Tableau | The system must allow for data to be exported to Tableau for analysis. | |
| 64 | 12 | 44 | Anil | Gen | General | Analysis | Download notification history | The system must permit the plan recipient(s) to view and download a notification sent report. | |
| 68 | 12 | 45 | Anil | Gen | General | Integration | Provide comment interface (including AI) | The portal requires a real-time collaboration system for information queries, corrections, suggestions, and comments between the plan submitter and the recipient with Artificial Intelligence (AI) chat feature capability. | |
| 69 | 12 | 46 | Anil | Gen | General | Notifications | Notification linked to due dates | The system must permit the plan recipient(s) to send an email to the plan submitter and service provider regulatory Point of Contact (POC) "X" days prior to the scheduled date. | |
| 70 | 12 | 47 | Anil | Gen | General | Notifications | Notification linked to Advice Letter completion | The system must automatically send an email notification to the plan submitter and service provider regulatory POC upon the conclusion of the Advice Letter. | |
| 108 | 1 | 48 | Anil | NR | Network Resiliency | Report intake | Plan submission | The system must be able to receive online resliency plans from the service providers. | |
| 45 | 4 | 49 | FS 2023-08-16 | NR | Network Resiliency | Report intake | Compliance data validation | The system must auto-validate resliency compliance data rules upon entry. | |
| 73 | 4 | 50 | Best Practice | OES | OES Provider Outages | Report review | Provide interface for reviewing | The system must provide an internal to CPUC interface to review service providers community isolation outage updates. | |
| 74 | 4 | 51 | Best Practice | OES | OES Provider Outages | Report review | Provide workflow statuses | The system must allow Cal OES outage updates to be statused as reviewed or unreviewed. | |
| 8 | 4 | 52 | Anil | OES | OES Provider Outages | Notifications | Notify of status changes | The system must be able to send notifications to CPUC system upon service providers' outage report submission to notify of status changes according to a to-be workflow. | |
| 72 | 8 | 53 | FS 2023-08-16 | OES | OES Provider Outages | Integration | Integrate with Cal OES ORS DB | The system must be able to extract real-time community isolation outage data from the Cal OES ORS application database (DB) | |
| 90 | 1 | 54 | Website | SQ | Service Quality | Report attributes | Installation interval metric | The system must be able to receive monthly reports on Installation Intervals from each regulated entity. | revisit later |
| 91 | 1 | 55 | Website | SQ | Service Quality | Report attributes | Installation commitments metric | The system must be able to receive monthly reports on Installation commitments from each regulated entity. | revisit later |
| 92 | 1 | 56 | Website | SQ | Service Quality | Report attributes | Customer trouble metric | The system must be able to receive monthly reports on customer troubles events from each regulated entity. | |
| 93 | 1 | 57 | Website | SQ | Service Quality | Report attributes | Out of service metric | The system must be able to receive monthly reports on out of service events from each regulated entity. | |
| 95 | 1 | 58 | Anil | SQ | Service Quality | Report Intake | Receive GO 133 SQ reports | The system must be able to receive online Service Quality (SQ) Report(s) from the service providers (e.g. GO 133 SQ standards performance metrics). | |
| 96 | 1 | 59 | FS 2023-08-15 | SQ | Service Quality | Trouble Tickets | CTT metric submissions | The system must support the submission of customer trouble ticket (CTT) metrics. | |
| 97 | 2 | 60 | Anil | SQ | Service Quality | Report Intake | Service Provider data upload | The system must permit service providers to upload their raw data in the following formats: *.csv or *.xlsx or *.docx or *.PDF. | |
| 98 | 2 | 61 | Anil | SQ | Service Quality | Report Intake | Recipients data upload | The system must permit the recipient(s) to upload the various sets of data in a specific format (e.g. *.csv or *.xlsx or *.kml or *.Gml or Tab files) to correlate with the SQ report(s) and the raw data information. | |
| 99 | 2 | 62 | Anil and Risa | SQ | Service Quality | Report attributes | Answer Time metric | The system must be able to be configured to receive monthly reports on new, to be determined attributes from regulated entities. | |
| 102 | 4 | 63 | FS 2023-08-15 | SQ | Service Quality | Report intake | Report validation | The system must be able to validate data during upload/entry by the entity. | |
| 103 | 4 | 64 | Anil | SQ | Service Quality | Report intake | Raw data to relational DB | The system must compile the raw data information based on the specified rules and/or formulas. | |
| 104 | 4 | 65 | FS 2023-08-15 | SQ | Service Quality | Trouble Tickets | OOS reports subset of CTTs | The system must enforce that Out of Service notifications are submitted as CTT tickets and included in CTT metrics. | |
| 105 | 7 | 66 | Website | SQ | Service Quality | Report Intake | Corrective action plan reports | The system must allow for submission of a corrective action plan for any service quality quarterly reports that CPUC identifies fail to meet any standards for two or more consecutive months. | |
| 106 | 10 | 67 | FS 2023-08-15 | SQ | Service Quality | Analysis | Group by LEC | The system must be able to group submitted Service Quality reports according to LEC, CLEC, VoIP and wireless types. | |
| 107 | 10 | 68 | Anil | SQ | Service Quality | Analysis | Historical Report generation | The system must be able to reproduce past SQ report(s). | |
| 87 | 2 | 69 | Anil | SV | Site Visit | Checklist | Site Visit Checklist reciept | The system must be able to recieve digitally signed online site visit checklist report from the service providers real-time over the handheld by clicking a link. | |
| 88 | 9 | 70 | Anil | SV | Site Visit | Post Visit | Post site visit collobration on recommendations | The system must be able to follow-up, collobrate, and track recommendations provided by CPUC engineer or staff during site visit to the service provider and able to download the report. | |
| 88 | 10 | 71 | Anil | SV | Site Visit | Visit Plan | Site Visit plan report | The system must be able to download the site visit schedule. | |
| 37 | 10 | 72 | Anil | SV | Site Visit | Checklist | Site Visit Checklist submission | The system must be able to submit digitally signed online site visit checklist report to the service providers real-time over the handheld device by clicking a link. | |
| 88 | 10 | 73 | Anil | SV | Site Visit | Post Visit | Post site visit report | The system must be able to download the post site visit collobration report. | |
| 88 | 11 | 74 | Anil | SV | Site Visit | Visit Plan | Site Visit plan scheduler | The system must be able to schedule and collobrate site visit plan with the service providers. | |
| 76 | 1 | 75 | FS 2023-08-16 | Tar | Tariffs | Tariffs | External search for tariffs | The system must provide search function for Cal OES and to respective providers to search through providers' (SPs) legacy as well as Next Generation (NG) 9-1-1 tariff(s). | |
| 78 | 2 | 76 | Best Practice | Tar | Tariffs | Tariffs | External GUI for tariff MACD | The system must provide a web form user interface for service providers to MACD individual legacy and NG 9-1-1 tariffs. | |
| 82 | 2 | 77 | Best Practice | Tar | Tariffs | Tariffs | External bulk upload of tariffs | The system must allow service providers to upload bulk legacy and NG 9-1-1 tariffs using an excel and/or CSV upload. | |
| 83 | 2 | 78 | Best Practice | Tar | Tariffs | Tariffs | External bulk upload error support | The system must generate a consolidated error list in a bulk upload of legacy and NG 9-1-1 tariff. | |
| 79 | 4 | 79 | Best Practice | Tar | Tariffs | Tariffs | Internal GUI for CPUC to status tariffs | The system mnust allow new tariff submissions to be statused by the CPUC according to a legacy and NG 9-1-1 tariff workflow - details to be determined in the design phase. (e.g. received, reviewed, approved, rejected, etc). | |
| 80 | 4 | 80 | Best Practice | Tar | Tariffs | Tariffs | Internal GUI to review MACD history | The system must provide an internal to CPUC interface to review legacy and NG 9-1-1 tariff MACD activity. | |
| 81 | 4 | 81 | FS 2023-08-16 | Tar | Tariffs | Tariffs | Internal search for tariffs | The system must provide a search capability to find specific legacy and NG 9-1-1 tariffs based on Service Provider (SP) and/or category and/or subcategory (or topics), scenario, carrier, carrier type and geography. | |
| 77 | 9 | 82 | FS 2023-08-16 | Tar | Tariffs | Tariffs | External GUI for tariff violation ID | The system must provide a web-based interface for Cal OES to associate a tariff violation with any 9-1-1 tariff. | |
| 12 | 83 | FS 2023-08-16 | Tar | Tariffs | Tariffs | External GUI for tariff violation alerts | If a Service Provider does not uphold the terms of an approved tariff for them, Cal OES must be able to submit an alert to the CPUC . | ||
| 20 | 1 | 84 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Integration | Fields for CPUC-specific data | The system must allow for CPUC-required data that was not downloaded from the FCC DB. That is, the system must accept, store and present data fields (ie columns) and data instances (ie rows) beyond those provided by the FCC DB. | |
| 21 | 1 | 85 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Report intake | Include MSI data | The system must allow for MSI report data (e.g. affected facility, customer affected and the 911 call centers (PSAP affected) outage metric data) when submitting an MSI report. | |
| 22 | 1 | 86 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Report intake | Submit notification | The system must allow for an MSI notification submission via a web portal. | |
| 23 | 2 | 87 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Report intake | submit initial report | The system must allow for an MSI initial report submission via a web portal. | |
| 24 | 2 | 88 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Report intake | submit final report | The system must allow for an MSI final report submission via a web portal with auto-validation of input data. | |
| 25 | 2 | 89 | Jeff 2023-08-28 | MSI | TSQ/MSI Portal | Report intake | Withdraw final report | The system must allow for an MSI report submitter to withdraw their report via a web portal only after CPUC's approval. | |
| 26 | 2 | 90 | Website | MSI | TSQ/MSI Portal | Report intake | MSI Reports suspensions | The system must be able to temporarily suspend Major Service Interuption (MSI) reporting for outages in areas where DIRS has been activated. | |
| 27 | 4 | 91 | Website | MSI | TSQ/MSI Portal | Report intake | Site visits | The system must allow for identification of a site based on CPUC's defined outage criteria for a site visit (i.e. flagging the site as a candidate for a visit). | |
| 30 | 4 | 92 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Workflow | Dynamic determination of DIRS or NORS | The system must offer choices that in turn determine whether DIRS or NORS is needed for FCC filings. | |
| 28 | 8 | 93 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Integration | FCC data integration | The system must integrate with the FCC database to load NORS outage data. | |
| 31 | 8 | 94 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Integration | Import NORS/DIRS XML or CSV dumps | The system must be able to extract data from the FCC Network Operation Reporting System (NORS)/DIRS system (e.g. API, periodic upload of XML and CSV data). | |
| 29 | 9 | 95 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Report intake | FCC attributes also in MSI reports | The system must ensure that MSI report submissions align with FCC NORS report submissions and must allow to reconfigure the report template based on the CPUC's requirements. That is, all FCC required and CPUC's mandatory attributes must also be in an MSI final report. | |
| 33 | 9 | 96 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Analysis | Allow correlation analysis between reports. | The system must allow for correlation analysis between SQ OOS, Cal OES ORS, PSPS event, NR plans, and MSI reports with different attributes (e.g service provider (SP), geography, service type, etc). | |
| 35 | 9 | 97 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Report intake | OES's ORS reports are can be children of MSI reports. | The system must ensure MSI report data is a superset of OES's ORS report data so that ORS reports can be a child of MSI reports if desired by the CPUC. | |
| 36 | 9 | 98 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Report review | Correlate and diffrentiate OOS from MSI reports | The system must differentiate between Out of Service (OOS) reports and MSI reports, and able to correlate. |
by Category
| old | Process | ID | Source | Code | Subprogram | Category | Summary | Description | |
| 63 | 2 | 21 | Anil | Gen | General | Analysis | Report supplement submission | The system must permit the recipient(s) to upload the various sets of data in a specific format (e.g. *.csv or *.xlsx) to correlate with a plan or a group of plans or all the plans. | |
| 52 | 9 | 35 | FS 2023-08-16 | Gen | General | Analysis | Ad Hoc reporting | The system must allow a user to query any fields in the data set. | |
| 58 | 9 | 36 | FS 2023-08-16 | Gen | General | Analysis | Dashboard for analysis visualizations | The system must provide a Dashboard view of data visualizations to support analysis (both trending or time-based, and static). | |
| 59 | 9 | 37 | FS 2023-08-16 | Gen | General | Analysis | Report/plan correlation with other reports/plans | The system must be able to reconcile submitted plans/reports with previously submitted plans/reports to ID correlation exceptions. | |
| 60 | 9 | 38 | Anil | Gen | General | Analysis | Report correlation with other reports | The system must permit the plan recipient(s) to create a customized correlation report. | |
| 61 | 9 | 39 | Anil | Gen | General | Analysis | Report on submitter details | The system must provide a customized report for a specific period regarding the plan submitter and other details, such as the date and time stamp of the plan submitted, any system/application errors encountered during the plan submission, etc. | |
| 62 | 9 | 40 | Anil | Gen | General | Analysis | Custom report support | The system must permit the plan recipient(s) to create a customized report. | |
| 32 | 9 | 43 | FS 2023-08-17 | Gen | General | Analysis | Export data to Tableau | The system must allow for data to be exported to Tableau for analysis. | |
| 64 | 12 | 44 | Anil | Gen | General | Analysis | Download notification history | The system must permit the plan recipient(s) to view and download a notification sent report. | |
| 33 | 9 | 96 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Analysis | Allow correlation analysis between reports. | The system must allow for correlation analysis between SQ OOS, Cal OES ORS, PSPS event, NR plans, and MSI reports with different attributes (e.g service provider (SP), geography, service type, etc). | |
| 106 | 10 | 67 | FS 2023-08-15 | SQ | Service Quality | Analysis | Group by LEC | The system must be able to group submitted Service Quality reports according to LEC, CLEC, VoIP and wireless types. | |
| 107 | 10 | 68 | Anil | SQ | Service Quality | Analysis | Historical Report generation | The system must be able to reproduce past SQ report(s). | |
| 87 | 2 | 69 | Anil | SV | Site Visit | Checklist | Site Visit Checklist reciept | The system must be able to recieve digitally signed online site visit checklist report from the service providers real-time over the handheld by clicking a link. | |
| 37 | 10 | 72 | Anil | SV | Site Visit | Checklist | Site Visit Checklist submission | The system must be able to submit digitally signed online site visit checklist report to the service providers real-time over the handheld device by clicking a link. | |
| 16 | 4 | 7 | FS 2023-08-22 | ETC | ETC Eligibility | Eligibility Review | Enter any unaddressed filings | The system must allow CPUC staff to enter data on unaddressed filings while reviewing applications and biennial recertifications. | |
| 17 | 4 | 8 | FS 2023-08-22 | ETC | ETC Eligibility | Eligibility Review | Enter any program and/or subprogram history (e.g. RDOF) | The system must allow CPUC staff to enter data on any program or subprogram history (e.g. RDOF) while reviewing ETC applications and biennial reports. | |
| 18 | 4 | 9 | FS 2023-08-22 | ETC | ETC Eligibility | Eligibility Review | Enter any felonies or bankruptcies | The system must allow CPUC staff to enter data on felonies or bankruptcies (including, but not limited to UEB background check information) while reviewing ETC applications, Hi-cost self-certifications, and biennial reports. | |
| 12 | 8 | 12 | FS 2023-08-22 | ETC | ETC Eligibility | Eligibility Review | TUFFS integration to validate Service Provider financial status | The system must be able to integrate with TUFFS to confirm whether a Service Provider is paid up on all financial obligations. | |
| 13 | 8 | 13 | FS 2023-08-22 | ETC | ETC Eligibility | Eligibility Review | UCS integration to update Company information | The system must be able to receive read-only updates from the CPUC UCS system on changes to company account information such as name, address, phone or DBA. | |
| 14 | 8 | 14 | FS 2023-08-22 | ETC | ETC Eligibility | Eligibility Review | UCS integration to update primary contact information | The system must be able to receive read-only updates from the CPUC UCS system on changes to company primary contact information. | |
| 15 | 8 | 15 | FS 2023-08-22 | ETC | ETC Eligibility | Eligibility Review | Service Quality data integration for violations | The system must be able to integrate with Service Quality data to confirm whether a Service Provider has any unresolved violations. | |
| 65 | 9 | 41 | Anil | Gen | General | File export | Export plans (service providers) | The system must allow service providers to export a submitted plan or report in a suitable format (e.g. *.csv or *.xlsx or *.PDF). | |
| 66 | 9 | 42 | Anil | Gen | General | File export | Export plans (recipients) | The system must allow the recipients(s) to download a plan/report or a group of plans/reports or all the plans/reports in a suitable format (e.g. *.csv or *.xlsx or *.docx or *.PDF). | |
| 2 | 1 | 1 | Resolution T-17002 | ETC | ETC Eligibility | File uploads | Annual HC self-certification application | The system must be able to accept Annual ETC 54.314 Hi-Cost self-certification applications from providers as a part of annual filing through the advice letter process. | |
| 43 | 2 | 23 | Anil | Gen | General | File uploads | CSV upload error checking | The system must detect upload error(s) based on the rules specified for a bulk upload file (plans, reports or raw data) template and permit a submitter to fix those errors before the final submission. | |
| 46 | 5 | 26 | FS 2023-08-16 | Gen | General | File uploads | CPUC request corrections | The system must allow CPUC staff to request corrections and for file (plans, reports or raw data) submitters to make the corrections (eg missing information, errors) through a web portal. | |
| 10 | 8 | 10 | FS 2023-08-22 | ETC | ETC Eligibility | GIS | GIS for Outage information | The system must be able to accept ArcGIS compatible shape (SHP) files for detailed outage information submissions. | |
| 11 | 8 | 11 | FS 2023-08-22 | ETC | ETC Eligibility | GIS | GIS for at least two years service quality improvement plan | The system must be able to accept ArcGIS compatible shape (SHP) files for locations associated with ETC applications that include service quality improvement plans for a given geography that they are submitting the application. | |
| 19 | 8 | 16 | FS 2023-08-22 | ETC | ETC Eligibility | Integration | PAL integration-high priority | The system must be able to automatically send and recieve updates to the PAL system regarding ETC applications filings, and self-certications and/or recertification statuses. | |
| 53 | 8 | 31 | Anil | Gen | General | Integration | Receive data (general) | The system must be able to integrate with other systems to send or receive the information in an automated manner. Examples include ArcGIS, PAL system, Cal OES 911 outage dashboard system and census tract data. | |
| 54 | 8 | 32 | Anil and Risa | Gen | General | Integration | Receive data (general) | The system must provide interfaces to support integrations with future, unknown systems. | |
| 55 | 8 | 33 | Anil | Gen | General | Integration | Receive data (GIS) | The system must permit the recipient(s) to obtain the maps and shapefile from the ArcGIS system. | |
| 56 | 8 | 34 | Anil | Gen | General | Integration | Send data (PAL) | The system must permit the recipient(s) to transmit information to the PAL system for the Advice Letter disposition. | |
| 68 | 12 | 45 | Anil | Gen | General | Integration | Provide comment interface (including AI) | The portal requires a real-time collaboration system for information queries, corrections, suggestions, and comments between the plan submitter and the recipient with Artificial Intelligence (AI) chat feature capability. | |
| 20 | 1 | 84 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Integration | Fields for CPUC-specific data | The system must allow for CPUC-required data that was not downloaded from the FCC DB. That is, the system must accept, store and present data fields (ie columns) and data instances (ie rows) beyond those provided by the FCC DB. | |
| 28 | 8 | 93 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Integration | FCC data integration | The system must integrate with the FCC database to load NORS outage data. | |
| 31 | 8 | 94 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Integration | Import NORS/DIRS XML or CSV dumps | The system must be able to extract data from the FCC Network Operation Reporting System (NORS)/DIRS system (e.g. API, periodic upload of XML and CSV data). | |
| 72 | 8 | 53 | FS 2023-08-16 | OES | OES Provider Outages | Integration | Integrate with Cal OES ORS DB | The system must be able to extract real-time community isolation outage data from the Cal OES ORS application database (DB) | |
| 8 | 12 | 17 | Best Practice | ETC | ETC Eligibility | Notifications | Notify of status changes | The system must be able to send notifications to application submitters or provider to notify them of status changes according to a to-be workflow. | |
| 49 | 6 | 29 | FS 2023-08-16 | Gen | General | Notifications | Notification of deadlines | The system must notify both CPUC staff and service providers of the protest and disposition date deadlines prior to the deadlines for plans and advice letters (triggered from the PAL system). | |
| 69 | 12 | 46 | Anil | Gen | General | Notifications | Notification linked to due dates | The system must permit the plan recipient(s) to send an email to the plan submitter and service provider regulatory Point of Contact (POC) "X" days prior to the scheduled date. | |
| 70 | 12 | 47 | Anil | Gen | General | Notifications | Notification linked to Advice Letter completion | The system must automatically send an email notification to the plan submitter and service provider regulatory POC upon the conclusion of the Advice Letter. | |
| 8 | 4 | 52 | Anil | OES | OES Provider Outages | Notifications | Notify of status changes | The system must be able to send notifications to CPUC system upon service providers' outage report submission to notify of status changes according to a to-be workflow. | |
| 88 | 9 | 70 | Anil | SV | Site Visit | Post Visit | Post site visit collobration on recommendations | The system must be able to follow-up, collobrate, and track recommendations provided by CPUC engineer or staff during site visit to the service provider and able to download the report. | |
| 88 | 10 | 73 | Anil | SV | Site Visit | Post Visit | Post site visit report | The system must be able to download the post site visit collobration report. | |
| 90 | 1 | 54 | Website | SQ | Service Quality | Report attributes | Installation interval metric | The system must be able to receive monthly reports on Installation Intervals from each regulated entity. | revisit later |
| 91 | 1 | 55 | Website | SQ | Service Quality | Report attributes | Installation commitments metric | The system must be able to receive monthly reports on Installation commitments from each regulated entity. | revisit later |
| 92 | 1 | 56 | Website | SQ | Service Quality | Report attributes | Customer trouble metric | The system must be able to receive monthly reports on customer troubles events from each regulated entity. | |
| 93 | 1 | 57 | Website | SQ | Service Quality | Report attributes | Out of service metric | The system must be able to receive monthly reports on out of service events from each regulated entity. | |
| 99 | 2 | 62 | Anil and Risa | SQ | Service Quality | Report attributes | Answer Time metric | The system must be able to be configured to receive monthly reports on new, to be determined attributes from regulated entities. | |
| 3 | 1 | 2 | Resolution T-17002 | ETC | ETC Eligibility | Report intake | Two-year service quality improvement plan | The system must be able to accept a quality improvement plan as part of the biannual advice letter recertification submission process. | |
| 4 | 1 | 3 | Resolution T-17002 | ETC | ETC Eligibility | Report intake | Outage information | The system must be able to accept detailed outage information as part of the biannual advice letter recertification submission process. | |
| 5 | 1 | 4 | Resolution T-17002 | ETC | ETC Eligibility | Report intake | Number of unfulfilled requests for service | The system must be able to accept the number of unfulfilled service requests as part of the biannual advice letter recertification submission process. | |
| 37 | 1 | 18 | Anil | Gen | General | Report intake | Plan submission | The system must be able to receive online plans from the service providers (e.g. Emergency Operations Plans, Communication Plans). | |
| 87 | 1 | 19 | Anil | Gen | General | Report intake | Report Submission | The system must be able to receive online reports from the service providers | |
| 88 | 2 | 20 | Anil and Risa | Gen | General | Report intake | Report supplements | The system must be able to receive online report supplements from the service providers. | |
| 42 | 2 | 22 | Anil | Gen | General | Report intake | Document formats allowed | The system must permit service providers to upload all plans, reports, supplements and corrections in a suitable format (e.g. *.csv or *.xlsx or *.docx or *.PDF). | |
| 47 | 5 | 25 | FS 2023-08-16 | Gen | General | Report intake | Disposition workflow | The system must support Advice Letter (AL) deadlines and grace periods for submissions. Upon AL submission a 20 day protest period window must be provided followed by a 10-day period to equal the full 30 day initial dispostion period. If no disposition action taken such as approved, reject or suspend within 30 day window then the AL will be by default automatically gets approved as per General Order (G.O.) 96-B. | |
| 110 | 5 | 28 | FS 2023-08-16 | Gen | General | Report intake | Disposition workflow | The system must support rejection of a resiliency plan submission. After rejection, a new submission can only occur with a new advice letter filing. | |
| 89 | 7 | 30 | Anil and Risa | Gen | General | Report intake | Post approval report corrections | The system must be able to receive and process online report corrections from the service providers after approval by the CPUC. | |
| 21 | 1 | 85 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Report intake | Include MSI data | The system must allow for MSI report data (e.g. affected facility, customer affected and the 911 call centers (PSAP affected) outage metric data) when submitting an MSI report. | |
| 22 | 1 | 86 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Report intake | Submit notification | The system must allow for an MSI notification submission via a web portal. | |
| 23 | 2 | 87 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Report intake | submit initial report | The system must allow for an MSI initial report submission via a web portal. | |
| 24 | 2 | 88 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Report intake | submit final report | The system must allow for an MSI final report submission via a web portal with auto-validation of input data. | |
| 25 | 2 | 89 | Jeff 2023-08-28 | MSI | TSQ/MSI Portal | Report intake | Withdraw final report | The system must allow for an MSI report submitter to withdraw their report via a web portal only after CPUC's approval. | |
| 26 | 2 | 90 | Website | MSI | TSQ/MSI Portal | Report intake | MSI Reports suspensions | The system must be able to temporarily suspend Major Service Interuption (MSI) reporting for outages in areas where DIRS has been activated. | |
| 27 | 4 | 91 | Website | MSI | TSQ/MSI Portal | Report intake | Site visits | The system must allow for identification of a site based on CPUC's defined outage criteria for a site visit (i.e. flagging the site as a candidate for a visit). | |
| 29 | 9 | 95 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Report intake | FCC attributes also in MSI reports | The system must ensure that MSI report submissions align with FCC NORS report submissions and must allow to reconfigure the report template based on the CPUC's requirements. That is, all FCC required and CPUC's mandatory attributes must also be in an MSI final report. | |
| 35 | 9 | 97 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Report intake | OES's ORS reports are can be children of MSI reports. | The system must ensure MSI report data is a superset of OES's ORS report data so that ORS reports can be a child of MSI reports if desired by the CPUC. | |
| 108 | 1 | 48 | Anil | NR | Network Resiliency | Report intake | Plan submission | The system must be able to receive online resliency plans from the service providers. | |
| 45 | 4 | 49 | FS 2023-08-16 | NR | Network Resiliency | Report intake | Compliance data validation | The system must auto-validate resliency compliance data rules upon entry. | |
| 95 | 1 | 58 | Anil | SQ | Service Quality | Report Intake | Receive GO 133 SQ reports | The system must be able to receive online Service Quality (SQ) Report(s) from the service providers (e.g. GO 133 SQ standards performance metrics). | |
| 97 | 2 | 60 | Anil | SQ | Service Quality | Report Intake | Service Provider data upload | The system must permit service providers to upload their raw data in the following formats: *.csv or *.xlsx or *.docx or *.PDF. | |
| 98 | 2 | 61 | Anil | SQ | Service Quality | Report Intake | Recipients data upload | The system must permit the recipient(s) to upload the various sets of data in a specific format (e.g. *.csv or *.xlsx or *.kml or *.Gml or Tab files) to correlate with the SQ report(s) and the raw data information. | |
| 102 | 4 | 63 | FS 2023-08-15 | SQ | Service Quality | Report intake | Report validation | The system must be able to validate data during upload/entry by the entity. | |
| 103 | 4 | 64 | Anil | SQ | Service Quality | Report intake | Raw data to relational DB | The system must compile the raw data information based on the specified rules and/or formulas. | |
| 105 | 7 | 66 | Website | SQ | Service Quality | Report Intake | Corrective action plan reports | The system must allow for submission of a corrective action plan for any service quality quarterly reports that CPUC identifies fail to meet any standards for two or more consecutive months. | |
| 7 | 4 | 5 | Best Practice | ETC | ETC Eligibility | Report review | Provide workflow statuses | The system must allow biennial submissions to be statused according to a TBD workflow. | |
| 6 | 4 | 6 | Best Practice | ETC | ETC Eligibility | Report review | Provide interface for reviewing | The system must provide an internal to CPUC interface to review biennial reports, annual ETC applications self-certification summary as well as its detail filed by the providers. | |
| 36 | 9 | 98 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Report review | Correlate and diffrentiate OOS from MSI reports | The system must differentiate between Out of Service (OOS) reports and MSI reports, and able to correlate. | |
| 73 | 4 | 50 | Best Practice | OES | OES Provider Outages | Report review | Provide interface for reviewing | The system must provide an internal to CPUC interface to review service providers community isolation outage updates. | |
| 74 | 4 | 51 | Best Practice | OES | OES Provider Outages | Report review | Provide workflow statuses | The system must allow Cal OES outage updates to be statused as reviewed or unreviewed. | |
| 76 | 1 | 75 | FS 2023-08-16 | Tar | Tariffs | Tariffs | External search for tariffs | The system must provide search function for Cal OES and to respective providers to search through providers' (SPs) legacy as well as Next Generation (NG) 9-1-1 tariff(s). | |
| 78 | 2 | 76 | Best Practice | Tar | Tariffs | Tariffs | External GUI for tariff MACD | The system must provide a web form user interface for service providers to MACD individual legacy and NG 9-1-1 tariffs. | |
| 82 | 2 | 77 | Best Practice | Tar | Tariffs | Tariffs | External bulk upload of tariffs | The system must allow service providers to upload bulk legacy and NG 9-1-1 tariffs using an excel and/or CSV upload. | |
| 83 | 2 | 78 | Best Practice | Tar | Tariffs | Tariffs | External bulk upload error support | The system must generate a consolidated error list in a bulk upload of legacy and NG 9-1-1 tariff. | |
| 79 | 4 | 79 | Best Practice | Tar | Tariffs | Tariffs | Internal GUI for CPUC to status tariffs | The system mnust allow new tariff submissions to be statused by the CPUC according to a legacy and NG 9-1-1 tariff workflow - details to be determined in the design phase. (e.g. received, reviewed, approved, rejected, etc). | |
| 80 | 4 | 80 | Best Practice | Tar | Tariffs | Tariffs | Internal GUI to review MACD history | The system must provide an internal to CPUC interface to review legacy and NG 9-1-1 tariff MACD activity. | |
| 81 | 4 | 81 | FS 2023-08-16 | Tar | Tariffs | Tariffs | Internal search for tariffs | The system must provide a search capability to find specific legacy and NG 9-1-1 tariffs based on Service Provider (SP) and/or category and/or subcategory (or topics), scenario, carrier, carrier type and geography. | |
| 77 | 9 | 82 | FS 2023-08-16 | Tar | Tariffs | Tariffs | External GUI for tariff violation ID | The system must provide a web-based interface for Cal OES to associate a tariff violation with any 9-1-1 tariff. | |
| 12 | 83 | FS 2023-08-16 | Tar | Tariffs | Tariffs | External GUI for tariff violation alerts | If a Service Provider does not uphold the terms of an approved tariff for them, Cal OES must be able to submit an alert to the CPUC . | ||
| 96 | 1 | 59 | FS 2023-08-15 | SQ | Service Quality | Trouble Tickets | CTT metric submissions | The system must support the submission of customer trouble ticket (CTT) metrics. | |
| 104 | 4 | 65 | FS 2023-08-15 | SQ | Service Quality | Trouble Tickets | OOS reports subset of CTTs | The system must enforce that Out of Service notifications are submitted as CTT tickets and included in CTT metrics. | |
| 88 | 10 | 71 | Anil | SV | Site Visit | Visit Plan | Site Visit plan report | The system must be able to download the site visit schedule. | |
| 88 | 11 | 74 | Anil | SV | Site Visit | Visit Plan | Site Visit plan scheduler | The system must be able to schedule and collobrate site visit plan with the service providers. | |
| 3 | 24 | Anil | Gen | General | Workflow | Grace period start | The system must log the Grace period start date/time once a report or plan is submitted for review and acceptance by the CPUC. | ||
| 48 | 5 | 27 | FS 2023-08-16 | Gen | General | Workflow | Disposition workflow | The system must allow for a suspension if the submitter could not complete the submission on time. | |
| 30 | 4 | 92 | FS 2023-08-17 | MSI | TSQ/MSI Portal | Workflow | Dynamic determination of DIRS or NORS | The system must offer choices that in turn determine whether DIRS or NORS is needed for FCC filings. |
NonFunctionals
| # | Group | Category | Sub-Category | Summary | Description |
| 1 | CPUC Administrators | Architecture | Architecture | System Environments must be accessed according to the contract. | Non-Production and Production environments should be accessed as mentioned in the contract. (Should not be accessed outside of CPUC environment.) |
| 2 | Solution-wide | Architecture | Architecture | Solution be on a SaaS system. | The System will be a Custom Application, or a Modified-off-the-Shelf (MOTS) and Commercial-off-the-Shelf (COTS) web-based Software as a Service (SaaS) system. |
3 Solution-wide Architecture Architecture Browser supported include Edge, Safare, Firefox, Chrome. The System must be accessible via a variety of browsers including, but not limited to, Edge, Safari, Firefox, and Chrome.
4 Solution-wide Architecture Architecture Solution to be accessible by desktop, tablet or phone. The System must be accessible via a variety of devices including, but not limited to, desktop computers, laptops, tablets, and smartphones.
5 Solution-wide Architecture Architecture Five environments must exist. The System will have five environments at minimum--Development, Testing, Training, Staging and Production.
6 Solution-wide Architecture Architecture Admin tools must support tracking of security, peformance and storage. The System must have administrative tools for monitoring security, performance, and storage of the system.
7 Solution-wide Architecture Architecture Data dictionary must be provided. The System Vendor must deliver a Data Dictionary that describes and maintains information on each data element including, but not limited to:
- name and type
- description
- format
- constraints
- last modified date
- last modified user
- validation rules and logic
8 Solution-wide Architecture Architecture Data dictionary must be maintained. The Data Dictionary must be up to date at all times.
9 Solution-wide Architecture Architecture User sessions must be saved after unexpected secion interruption. The System will resume an interrupted user session upon restoration of the System, network service, and re-authentication.
| 10 | Solution-wide | Architecture | Architecture | Ensure user interface is HTML 5 compliance. | The System must ensure the end user interface is HTML 5 compliant. |
| 11 | Solution-wide | Architecture | Architecture | Patching and updates must occur without adversely impacting production. | The System must enable patching and update deployments to be done without impacting the system functional availability. |
| 12 | Solution-wide | Architecture | Architecture | No user-visible text may be "hard-coded.' | The System must ensure no piece of text that is displayed to a user resides in program source code. Every piece of text that a user might see must be modifiable without changing source code. That is, no user-visible text will be “hard-coded.” |
| 13 | Solution-wide | Architecture | Architecture | Notification history between CPUC and external useres must be made available. | The System must provide functionality to track communications (emails, notices, letters generated) between the CPUC and external users. |
| 14 | Solution-wide | Architecture | Architecture | Test environments must be made available. | The System must provide on-line testing environments that support automated repeatable unit testing, system testing, integration testing, regression testing, parallel testing, and prototype development that replicate the full functionality of the production environment. The Contractor must demonstrate that test environments can meet production capability but not affect production data. |
| 15 | Solution-wide | Architecture | Architecture | Files stored on Amazon | All file attachments must be stored on Amazon S3 storage using API or Salesforce recommended best practices for Amazon S3 |
16 CPUC Administrators Audit-Log Audits Log system, event and user activities. The System will capture and create logs of system, event, and user activities.
| 17 | CPUC Administrators | Audit-Log | Audits | Logs must be read only. | The System's audit logs must be protected from modification or deletion. |
| 18 | CPUC Administrators | Audit-Log | Audits | Logs must include error no, date/time, data change, change type. | System logs must include: |
- error numbers and messages generated by the system
- date/time stamps
- any disclosure of information data across the solution
- user activities (create, read, update, delete)
- user ID
| 19 | CPUC Administrators | Audit-Log | Audits | Logs must include before/after states, unique identifier. | The System must ensure that all transaction audit trails contain the user identifier, workstation, or other unique identifier, date and local (Pacific) time, before-state and after-state (i.e., before and after change) of all record components defined by CPUC, in compliance with the CPUC Audit & Accountability Policy. |
| 20 | CPUC Administrators | Audit-Log | Audits | Logs must be retained for 180 days. | The System must retain audit logs for a period of 180 days to allow for investigation(s). |
| 21 | CPUC Administrators | Audit-Log | Audits | Logs can be accessed by key users only. | The System must allow logs to be accessible and visible by privileged/authorized users only. |
| 22 | CPUC Administrators | Audit-Log | Audits | Audit Logs | The system must log all actions to data with a timestamp, how the data changed and who made the change. |
| 23 | Solution-wide | Audit-Log | Timestamp | Audit Logs | The system must log all actions to data with a timestamp, how the data changed and who made the change. |
| 24 | Solution-wide | Capacity-Performance | Capacity-Performance | Solution must be available 24x7 | The System must be available 24x7 all year, subject to maintenance schedules. |
25 Solution-wide Capacity-Performance Capacity-Performance Solution must report on system performance. The System must report on system performance.
26 Solution-wide Capacity-Performance Capacity-Performance Solution must support multiple concurrent users. The System will support multiple concurrent users (CPUC, integration partners, external users), allowing users to create, read, update, and delete transactions based on their user role.
27 Solution-wide Capacity-Performance Capacity-Performance User capacity must not impact performance. The capacity of concurrent users must not impact system performance and response time.
| 28 | Solution-wide | Capacity-Performance | Capacity-Performance | The screens will take no longer than one (1) second to load. | The screens will take no longer than one (1) second to load. |
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 .