Below is an example of a functional decomposition created for a legacy portal. Since there was little-to-no documentation for the legacy site, this functional decomposition served as both site documentation as well as the base to begin creating stories for the new portal. |
| Portal Functional Decomposition | ||||
| Category | Feature ID | Feature Name | Feature Description | Notes |
| Events | ||||
| Events | 1.0 | Event Category | The system shall include an events category | |
| Events | 1.1 | Event Query | The system shall allow users to query on events | |
| Events | 1.1.1 | Maintenance Ticket Query | The system shall allow users to query Maintenance Tickets | |
| Events | 1.1.1.1 | Query by Ticket ID | The system shall allow users to query Maintenance Tickets by Ticket ID | |
| Events | 1.1.1.1.1 | Result from Ticket ID | When querying by Ticket ID the user should be taken directly to the Maintenance Ticket Screen if an exact match is found | |
| Events | 1.1.1.2 | Query by Site | The system shall allow users to query Maintenance Tickets by Site | |
| Events | 1.1.1.3 | Query by Multiple Sites | The system shall allow users to query Maintenance Tickets by Multiple Sites | See Site Selection Utility |
| Events | 1.1.1.4 | Query by Site Data | The system shall allow users to query Maintenance Tickets by Site Data (State, City, Street, Suite) | |
| Events | 1.1.1.5 | Query by Customer | The system shall allow users to query Maintenance Tickets by Customer | Super and Channel Users only |
| Events | 1.1.1.6 | Query by Status | The system shall allow users to query Maintenance Tickets by ticket status | |
| Events | 1.1.1.6.1 | Query by Status - All | The system shall allow users to query All Maintenance Tickets | Default |
| Events | 1.1.1.6.2 | Query by Status - Open | The system shall allow users to query only Open Maintenance Tickets | |
| Events | 1.1.1.6.3 | Query by Status - Closed | The system shall allow users to query only Closed Maintenance Tickets | |
| Events | 1.1.1.6.4 | Query by Status - Auto Closed | The system shall allow users to query only Auto Closed Maintenance Tickets | |
| Events | 1.1.1.6.5 | Query by Status - Escalated | The system shall allow users to query only Escalated Maintenance Tickets | |
| Events | 1.1.1.7 | Query by Date | The system shall allow users to query by user-definable dates within the last 90 days | With a preset "last 90 days" radio button |
| Events | 1.1.2 | Query Results | The system shall return a list of Maintenance Tickets matching the user selected query criteria | If none leave blank |
| Events | 1.1.2.1 | Query Results - Product | The system shall include in the returned list the product of the Maintenance Ticket | Example: "WAN", If none leave blank |
| Events | 1.1.2.2 | Query Results - Ticket Number | The system shall include in the returned list the "Ticket Number" of the Maintenance Ticket | Example: "123456", If none leave blank |
| Events | 1.1.2.2.1 | Action - Clicking Ticket Number | The system shall link the user to the Maintenance Ticket Detail screen when they click on the Maintenance Ticket Number | |
| Events | 1.1.2.3 | Query Results - Status | The system shall include in the returned list the "Status" of the Maintenance Ticket | Example: "Closed Confirmed", If none leave blank |
| Events | 1.1.2.3.1 | Action - Clicking Status | The system shall pop up a window of definitions when the user clicks on the status | |
| Events | 1.1.2.3.2 | Action - Targetted Status Clicks | The system shall target the user to the appropriate definition when the user clicks | Example: User clicks "Cancel Ticket" and the popup window auto scrolls to the "Cancel Ticket" definition |
| Events | 1.1.2.4 | Query Results - Date Opened | The system shall include in the returned list the "Date Opened" of the Maintenance Ticket | Example: "31-May-03 07:57 CDT", If none leave blank |
| Events | 1.1.2.5 | Query Results - Date Closed | The system shall include in the returned list the "Date Closed" of the Maintenance Ticket | Example: "31-May-03 07:57 CDT", If none leave blank |
| Events | 1.1.2.6 | Query Results - Sites Affected | The system shall include in the returned list the "Sites Affected" in the Maintenance Ticket | Example: "NILES (CORPORATE)", If none leave blank |
| Events | 1.1.2.6.1 | Action - Clicking Sites Affected | The "Sites Affected" field should link to the associated Site Info screen for each site | |
| Events | 1.1.2.7 | Query Results - Resolution | The system shall include in the returned list the "Resolution" of the Maintenance Ticket | Example: "POWER RESTORED", If none leave blank |
| Events | 1.1.2.8 | Query Results - Download Option | The system shall include the option to download the returned list | |
| Events | 1.1.2.9 | Query Results - Customer Name | The system shall include the customer name at the top of the query results | Example: "AB Dick" |
| Events | 1.1.3 | Maintenance Ticket Download | The system shall allow users to download Maintenance Ticket data by the query options defined above | |
| Events | 1.1.3.1 | Maintenance Ticket Download - Product | The system shall include "Product" as a download option | Example: "WAN", If none leave blank |
| Events | 1.1.3.2 | Maintenance Ticket Download - SubProduct | The system shall include "SubProduct" as a download option | If none leave blank |
| Events | 1.1.3.3 | Maintenance Ticket Download - Ticket Number | The system shall include "Ticket Number" as a download option | Example: "123456", If none leave blank |
| Events | 1.1.3.4 | Maintenance Ticket Download - Current Status | The system shall include "Current Status" as a download option | Example: "Closed Confirmed", If none leave blank |
| Events | 1.1.3.5 | Maintenance Ticket Download - Date Opened | The system shall include "Date Opened" as a download option | Example: "5/31/2003", If none leave blank |
| Events | 1.1.3.6 | Maintenance Ticket Download - Date Closed | The system shall include "Date Closed" as a download option | Example: "5/31/2003", If none leave blank |
| Events | 1.1.3.7 | Maintenance Ticket Download - Time Opened | The system shall include "Time Opened" as a download option | Example: "22:46:08 CDT", If none leave blank |
| Events | 1.1.3.8 | Maintenance Ticket Download - Time Closed | The system shall include "Time Closed" as a download option | Example: "22:46:08 CDT", If none leave blank |
| Events | 1.1.3.9 | Maintenance Ticket Download - Sites Affected | The system shall include "Sites Affected" as a download option | Example: "NILES (CORPORATE)", If none leave blank |
| Events | 1.1.3.10 | Maintenance Ticket Download - Problem | The system shall include "Problem" as a download option | Example: "BIRMINGHAM - Canvass Auto Open", If none leave blank |
| Events | 1.1.3.11 | Maintenance Ticket Download - Source | The system shall include "Source" as a download option | Example: "CUSTOMER", If none leave blank |
| Events | 1.1.3.12 | Maintenance Ticket Download - Resolution | The system shall include "Resolution" as a download option | Example: "POWER RESTORED", If none leave blank |
| Events | 1.1.3.13 | Maintenance Ticket Download - Ticket Type | The system shall include "Ticket Type" as a download option | Example: "MAINTENANCE", If none leave blank |
| Events | 1.1.3.14 | Maintenance Ticket Download - Major Cause | The system shall include "Major Cause" as a download option | Example: "EQUIPMENT", If none leave blank |
| Events | 1.1.3.15 | Maintenance Ticket Download - Detail Cause | The system shall include "Detail Cause" as a download option | Example: "POWER OUTAGE", If none leave blank |
| Events | 1.1.3.16 | Maintenance Ticket Download - Managed Flag | The system shall include "Managed Flag" as a download option | Example: "Y" If none leave blank |
| Events | 1.1.3.17 | Maintenance Ticket Download - Availability Flag | The system shall include "Availability Flag" as a download option | Example: "N", If none leave blank |
| Events | 1.1.3.18 | Maintenance Ticket Download - Availability Type | The system shall include "Availability Type" as a download option | Example: "NON-MANAGED COMPONENT FAILURE", If none leave blank |
| Events | 1.1.3.19 | Maintenance Ticket Download - Reported By | The system shall include "Reported By" as a download option | Example: "NMC", If none leave blank |
| Events | 1.1.3.20 | Maintenance Ticket Download - Customer | The system shall include "Customer" in the download report | Example: "AB Dick" |
| Events | 1.1.3.21 | Maintenance Ticket Download - Customer Number | The system shall include "Customer Number" in the download report | |
| Events | 1.1.4 | Work Ticket Query | The system shall allow the user to query Work Tickets | |
| Events | 1.1.4.1 | Query by Ticket ID | The system shall allow users to query Work Tickets by Ticket ID | |
| Events | 1.1.4.1.1 | Result from Ticket ID | When querying by Ticket ID the user should be taken directly to the Work Ticket Screen if an exact match is found | |
| Events | 1.1.4.2 | Query by Site | The system shall allow users to query Work Tickets by Site | |
| Events | 1.1.4.3 | Query by Multiple Sites | The system shall allow users to query Work Tickets by Multiple Sites | |
| Events | 1.1.4.4 | Query by Site Data | The system shall allow users to query Work Tickets by Site Data (State, City, Street, Suite) | |
| Events | 1.1.4.5 | Query by Customer | The system shall allow users to query Work Tickets by Customer | Super and Channel Users only |
| Events | 1.1.4.6 | Query by Status | The system shall allow users to query Work Tickets by ticket status | |
| Events | 1.1.4.6.1 | Query by Status - All | The system shall allow users to query All Work Tickets | Default |
| Events | 1.1.4.6.2 | Query by Status - Open | The system shall allow users to query only Open Work Tickets | |
| Events | 1.1.4.6.3 | Query by Status - Closed | The system shall allow users to query only Closed Work Tickets | |
| Events | 1.1.4.7 | Query by Date | The system shall allow users to query by user-definable dates within the last 90 days | With a preset "last 90 days" radio button |
| Events | 1.1.5 | Query Results | The system shall return a list of Work Tickets matching the user selected query criteria | If none leave blank |
| Events | 1.1.5.2 | Query Results - Ticket Number | The system shall include in the returned list the "Ticket Number" of the Work Ticket | Example: "123456", If none leave blank |
| Events | 1.1.5.2.1 | Action - Clicking Ticket Number | The system shall link the user to the Work Ticket Detail screen when they click on the Work Ticket Number | |
| Events | 1.1.5.3 | Query Results - Status | The system shall include in the returned list the "Status" of the Work Ticket | Example: "Closed Confirmed", If none leave blank |
| Events | 1.1.5.3.1 | Action - Clicking Status | The system shall pop up a window of definitions when the user clicks on the status | |
| Events | 1.1.5.3.2 | Action - Targetted Status Clicks | The system shall target the user to the appropriate definition when the user clicks | Example: User clicks "Cancel Ticket" and the popup window auto scrolls to the "Cancel Ticket" definition |
| Events | 1.1.5.4 | Query Results - Date Opened | The system shall include in the returned list the "Date Opened" of the Work Ticket | Example: "31-May-03 07:57 CDT", If none leave blank |
| Events | 1.1.5.5 | Query Results - Date Closed | The system shall include in the returned list the "Date Closed" of the Work Ticket | Example: "31-May-03 07:57 CDT", If none leave blank |
| Events | 1.1.5.6 | Query Results - Sites Affected | The system shall include in the returned list the "Sites Affected" in the Work Ticket | Example: "NILES (CORPORATE)", If none leave blank |
| Events | 1.1.5.6.1 | Action - Clicking Sites Affected | The "Sites Affected" field should link to the associated Site Info screen for each site | |
| Events | 1.1.5.7 | Query Results - Download Option | The system shall include the option to download the returned list | |
| Events | 1.1.5.8 | Query Results - Customer Name | The system shall include the customer name at the top of the query results | Example: "AB Dick" |
| Events | 1.1.6 | Maintenance Ticket Download | The system shall allow users to download Maintenance Ticket data by the query options defined above | |
| Events | 1.1.6.1 | Work Ticket Download - Category | The system shall include "Category" as a download option | Example: "Implementation", If none leave blank |
| Events | 1.1.6.2 | Work Ticket Download - SubCategory | The system shall include "SubCategory" as a download option | Example: "PWE MAC", If none leave blank |
| Events | 1.1.6.3 | Work Ticket Download - Ticket Number | The system shall include "Ticket Number" as a download option | Example: "123456", If none leave blank |
| Events | 1.1.6.4 | Work Ticket Download - Current Status | The system shall include "Current Status" as a download option | Example: "Completed", If none leave blank |
| Events | 1.1.6.5 | Work Ticket Download - Date Opened | The system shall include "Date Opened" as a download option | Example: "5/31/2003", If none leave blank |
| Events | 1.1.6.6 | Work Ticket Download - Date Closed | The system shall include "Date Closed" as a download option | Example: "5/31/2003", If none leave blank |
| Events | 1.1.6.7 | Work Ticket Download - Time Opened | The system shall include "Time Opened" as a download option | Example: "22:46:08 CDT", If none leave blank |
| Events | 1.1.6.8 | Work Ticket Download - Time Closed | The system shall include "Time Closed" as a download option | Example: "22:46:08 CDT", If none leave blank |
| Events | 1.1.6.9 | Work Ticket Download - Sites Affected | The system shall include "Sites Affected" as a download option | Example: "NILES (CORPORATE)", If none leave blank |
| Events | 1.1.6.10 | Work Ticket Download - Ticket Description | The system shall include "Ticket Description" as a download option | Example: "MAC DISCONNECT SITE", If none leave blank |
| Events | 1.1.7 | Alarm Query | The system shall allow the user to query alarms | |
| Events | 1.1.7.1 | Query by Site | The system shall allow users to query Work Tickets by Site | |
| Events | 1.1.7.2 | Query by Multiple Sites | The system shall allow users to query Work Tickets by Multiple Sites | |
| Events | 1.1.7.3 | Query by Site Data | The system shall allow users to query Work Tickets by Site Data (State, City, Street, Suite) | |
| Events | 1.1.7.4 | Query by Customer | The system shall allow users to query Work Tickets by Customer | Super and Channel Users only |
| Events | 1.1.7.5 | Query by Date | The system shall allow users to query by user-definable dates within the last 90 days | With a preset "last 90 days" radio button |
| Events | 1.1.8 | Query Results | The system shall return a list of Active Alarms matching the user selected query criteria | If none leave blank |
| Events | 1.1.8.1 | Query Results - Ticket Number | The system shall include in the returned list the "Sites Affected" of the Alarm | |
| Events | 1.1.8.1.1 | Action - Clicking Sites Affected | The "Sites Affected" field should link to the associated Site Info screen for each site | |
| Events | 1.1.8.2 | Query Results - Device Name | The system shall include "Device Name" in the query results | Example: "AO-CM-PUB1" |
| Events | 1.1.8.3 | Query Results - IP Address | The system shall include "IP Address" in the query results | Example: "5.18.84.1" |
| Events | 1.1.8.4 | Query Results - Alarm Date | The system shall include "Alarm Date" in the query results | Example: "05-Jun-03 09:58 CDT" |
| Events | 1.1.8.5 | Query Results - Description | The system shall include "Description" in the query results | Example: "Interface failed." |
| Tickets | ||||
| Tickets | 2.0 | Maintenance Tickets | The system shall show Maintenance Tickets | |
| Tickets | 2.1 | Maintenance Ticket - Ticket Number | The system shall display the Maintenance Ticket Number on each Maintenance Ticket | |
| Tickets | 2.2 | Maintenance Ticket - Contact NetSolve | The system shall include the ability to contact the NetSolve via an email form from the Maintenance Ticket | |
| Tickets | 2.2.1 | Contact NetSolve Screen - Email | The system shall query the user for the email address they wish to coorespond on this topic with NetSolve over. | Required Field |
| Tickets | 2.2.2 | Contact NetSolve Screen - Phone | The system shall query the user for the phone number they wish to coorespond with NetSolve on this topic over | Optional Field |
| Tickets | 2.2.3 | Contact NetSolve Screen - Body | The system shall include a textarea for users to type in their message | Required Field |
| Tickets | 2.2.4 | Contact NetSolve Screen - Maintenance Ticket ID | The system shall display the Maintenance Ticket Number on Contact Us Form | Display Only |
| Tickets | 2.3 | Maintenance Ticket - Download Ticket | The system shall include the ability to download the ticket details directly from the ticket. | |
| Tickets | 2.3.1 | Maintenance Ticket Download - Product | The system shall include "Product" as a download option | Example: "WAN", If none leave blank |
| Tickets | 2.3.2 | Maintenance Ticket Download - SubProduct | The system shall include "SubProduct" as a download option | If none leave blank |
| Tickets | 2.3.3 | Maintenance Ticket Download - Ticket Number | The system shall include "Ticket Number" as a download option | Example: "123456", If none leave blank |
| Tickets | 2.3.4 | Maintenance Ticket Download - Current Status | The system shall include "Current Status" as a download option | Example: "Closed Confirmed", If none leave blank |
| Tickets | 2.3.5 | Maintenance Ticket Download - Date Opened | The system shall include "Date Opened" as a download option | Example: "5/31/2003", If none leave blank |
| Tickets | 2.3.6 | Maintenance Ticket Download - Date Closed | The system shall include "Date Closed" as a download option | Example: "5/31/2003", If none leave blank |
| Tickets | 2.3.7 | Maintenance Ticket Download - Time Opened | The system shall include "Time Opened" as a download option | Example: "22:46:08 CDT", If none leave blank |
| Tickets | 2.3.8 | Maintenance Ticket Download - Time Closed | The system shall include "Time Closed" as a download option | Example: "22:46:08 CDT", If none leave blank |
| Tickets | 2.3.9 | Maintenance Ticket Download - Sites Affected | The system shall include "Sites Affected" as a download option | Example: "NILES (CORPORATE)", If none leave blank |
| Tickets | 2.3.10 | Maintenance Ticket Download - Problem | The system shall include "Problem" as a download option | Example: "BIRMINGHAM - Canvass Auto Open", If none leave blank |
| Tickets | 2.3.11 | Maintenance Ticket Download - Source | The system shall include "Source" as a download option | Example: "CUSTOMER", If none leave blank |
| Tickets | 2.3.12 | Maintenance Ticket Download - Resolution | The system shall include "Resolution" as a download option | Example: "POWER RESTORED", If none leave blank |
| Tickets | 2.3.13 | Maintenance Ticket Download - Ticket Type | The system shall include "Ticket Type" as a download option | Example: "MAINTENANCE", If none leave blank |
| Tickets | 2.3.14 | Maintenance Ticket Download - Major Cause | The system shall include "Major Cause" as a download option | Example: "EQUIPMENT", If none leave blank |
| Tickets | 2.3.15 | Maintenance Ticket Download - Detail Cause | The system shall include "Detail Cause" as a download option | Example: "POWER OUTAGE", If none leave blank |
| Tickets | 2.3.16 | Maintenance Ticket Download - Managed Flag | The system shall include "Managed Flag" as a download option | Example: "Y" If none leave blank |
| Tickets | 2.3.17 | Maintenance Ticket Download - Availability Flag | The system shall include "Availability Flag" as a download option | Example: "N", If none leave blank |
| Tickets | 2.3.18 | Maintenance Ticket Download - Availability Type | The system shall include "Availability Type" as a download option | Example: "NON-MANAGED COMPONENT FAILURE", If none leave blank |
| Tickets | 2.3.19 | Maintenance Ticket Download - Reported By | The system shall include "Reported By" as a download option | Example: "NMC", If none leave blank |
| Tickets | 2.3.20 | Maintenance Ticket Download - Customer | The system shall include "Customer" in the download report | Example: "AB Dick" |
| Tickets | 2.3.21 | Maintenance Ticket Download - Customer Number | The system shall include "Customer Number" in the download report | |
| Tickets | 2.4 | Sites on Maintenance Ticket | The system shall show the sites loaded into the Maintenance Ticket | |
| Tickets | 2.4.1 | Sites on Maintenance Ticket - Site Name | The system shall show the "Site Name" of the site loaded into the Maintenance Ticket | |
| Tickets | 2.4.1.1 | Action - Clicking on Site Name | The system shall link the user to the "Site Information Screen" when the user clicks the "Site Name" | |
| Tickets | 2.4.2 | Sites on Maintenance Ticket - Street | The system shall show the "Street" of the site loaded into the Maintenance Ticket | |
| Tickets | 2.4.3 | Sites on Maintenance Ticket - State/Province | The system shall show the "State/Province" of the site loaded into the Maintenance Ticket | |
| Tickets | 2.4.4 | Sites on Maintenance Ticket - Country | The system shall show the "Country" of the site loaded into the Maintenance Ticket | |
| Tickets | 2.5 | Maintaince Ticket - Current Status | The system shall show details about the current status of the Maintenance Ticket | Display Only |
| Tickets | 2.5.1 | Maintaince Ticket - Current Status: Product | Example: "WAN", If blank leave empty | Display Only |
| Tickets | 2.5.2 | Maintaince Ticket - Current Status: SubProduct | Display Only | |
| Tickets | 2.5.3 | Maintaince Ticket - Current Status: Date Opened | Example: "31-May-03 07:57 CDT", If blank leave empty | Display Only |
| Tickets | 2.5.4 | Maintaince Ticket - Current Status: Date Closed | Example: "31-May-03 07:57 CDT", If blank leave empty | Display Only |
| Tickets | 2.5.5 | Maintaince Ticket - Current Status: Problem | Example: "BIRMINGHAM - Canvass Auto Open", If blank leave empty | Display Only |
| Tickets | 2.5.6 | Maintaince Ticket - Current Status: Major Cause | Example: "EQUIPMENT", If blank leave empty | Display Only |
| Tickets | 2.5.7 | Maintaince Ticket - Current Status: Current Status | Example: "CLOSED CONFIRMED ", If blank leave empty | Display Only |
| Tickets | 2.5.8 | Maintaince Ticket - Current Status: Detail Cause | Example: "POWER OUTAGE", If blank leave empty | Display Only |
| Tickets | 2.5.9 | Maintaince Ticket - Current Status: Source | Example: "CUSTOMER", If blank leave empty | Display Only |
| Tickets | 2.5.10 | Maintaince Ticket - Current Status: Resolution | Example: "POWER RESTORED", If blank leave empty | Display Only |
| Tickets | 2.5.11 | Maintaince Ticket - Current Status: Ticket Type | Example: "MAINTENANCE", If blank leave empty | Display Only |
| Tickets | 2.5.12 | Maintaince Ticket - Current Status: Availability Type | Example: "NON-MANAGED COMPONENT FAILURE", If blank leave empty | Display Only |
| Tickets | 2.5.13 | Maintaince Ticket - Current Status: Managed Flag | Example: "Y", If blank leave empty | Display Only |
| Tickets | 2.5.14 | Maintaince Ticket - Current Status: Availability Flag | Example: "N", If blank leave empty | Display Only |
| Tickets | 2.5.15 | Maintaince Ticket - Current Status: Reported By | Example: "NMC", If blank leave empty | Display Only |
| Tickets | 2.6 | Maintenance Ticket - Dispatch Info | The system shall include vendor dispatch information | Display Only |
| Tickets | 2.6.1 | Maintenance Ticket - Dispatch Info: Vendor Ticket ID | The system shall include the "Vendor Ticket ID" in the dispatch information | Example: "2080 F/T 31ST", If blank leave empty; Display Only |
| Tickets | 2.6.2 | Maintenance Ticket - Dispatch Info: Vendor Name | The system shall include the "Vendor Name" in the dispatch information | Example: "MCI", If blank leave empty; Display Only |
| Tickets | 2.6.3 | Maintenance Ticket - Dispatch Info: Dispatch Type | The system shall include the "Dispatch Type" in the dispatch information | Example: "IXC", If blank leave empty; Display Only |
| Tickets | 2.7 | Maintenance Ticket - Ticket Activities | The system shall include the chronology of the ticket activities | |
| Tickets | 2.7.1 | Maintenance Ticket - Ticket Activities: Time Stamp | The system shall include a timestamp of every Activity | |
| Tickets | 2.7.2 | Maintenance Ticket - Ticket Activities: Milestone | The system shall associate a milestone with every activity | |
| Tickets | 2.7.2.1 | Maintenance Ticket - Milestone Definitions | The system shall include a link on every milestone to a popup window with the definitions of the milestone | |
| Tickets | 2.7.3 | Maintenance Ticket - Ticket Activities: Tech | The system shall indicate who completed an Activity by showing the tech or system who entered the Activity note | |
| Tickets | 2.7.3.1 | Maintenance Ticket - Tech Contact Info | The system shall provide a popup window from a link on each tech's and systems initials indicating the contact information for the person entering the activity | |
| Tickets | 2.7.4 | Maintenance Ticket - Ticket Activities: Escalation | The system shall show the escalation list for each technician who enters Activities into the ticket | |
| Tickets | 2.7.5 | Maintenance Ticket - Ticket Activities: Detail | The system shall show the details of each Activity as entered by the tech or system | |
| Tickets | 2.8 | Maintenance Ticket - Filtering Activities | The system shall allow users to filter the list of Activities | |
| Tickets | 2.8.1 | Maintenance Ticket - Filtering Activities: All | The system shall allow users to filter Activities by "All" | Default |
| Tickets | 2.8.2 | Maintenance Ticket - Filtering Activities List | The system shall support the ability to limit the activity types available for filtering to externally viewable activities existing in the selected ticket. | |
| Tickets | 2.9 | Maintenance Ticket - Activity Chronology - Ascending | The system shall allow users to change the display order of Activities by sorting by timestamp in an ascending manner | |
| Tickets | 2.9.1 | Maintenance Ticket - Activity Chronology - Descending | The system shall allow users to change the display order of Activities by sorting by timestamp in a descending manner | |
| Tickets | 2.10 | Maintenance Ticket - Add Activity | The system shall allow end users to add Note Only Activities to the Maintenance Ticket | |
| Tickets | 3.0 | Work Tickets | The system shall show Work Tickets | |
| Tickets | 3.1 | Work Ticket - Ticket Number | The system shall display the Work Ticket Number on each Work Ticket | |
| Tickets | 3.2 | Work Ticket - Contact NetSolve | The system shall include the ability to contact the NetSolve via an email form from the Work Ticket | |
| Tickets | 3.2.1 | Contact NetSolve Screen - Email | The system shall query the user for the email address they wish to coorespond on this topic with NetSolve over. | Required Field |
| Tickets | 3.2.2 | Contact NetSolve Screen - Phone | The system shall query the user for the phone number they wish to coorespond with NetSolve on this topic over | Optional Field |
| Tickets | 3.2.3 | Contact NetSolve Screen - Body | The system shall include a textarea for users to type in their message | Required Field |
| Tickets | 3.3 | Work Ticket - Download Ticket | The system shall include the ability to download the ticket details directly from the ticket. | |
| Tickets | 3.3.1 | Work Ticket Download - Ticket Number | The system shall include "Ticket Number" as a download option | Example: "123456", If none leave blank |
| Tickets | 3.3.2 | Work Ticket Download - Current Status | The system shall include "Current Status" as a download option | Example: "Closed Confirmed", If none leave blank |
| Tickets | 3.3.3 | Work Ticket Download - Date Opened | The system shall include "Date Opened" as a download option | Example: "5/31/2003", If none leave blank |
| Tickets | 3.3.4 | Work Ticket Download - Date Closed | The system shall include "Date Closed" as a download option | Example: "5/31/2003", If none leave blank |
| Tickets | 3.3.5 | Work Ticket Download - Time Opened | The system shall include "Time Opened" as a download option | Example: "22:46:08 CDT", If none leave blank |
| Tickets | 3.3.6 | Work Ticket Download - Time Closed | The system shall include "Time Closed" as a download option | Example: "22:46:08 CDT", If none leave blank |
| Tickets | 3.3.7 | Work Ticket Download - Sites Affected | The system shall include "Sites Affected" as a download option | Example: "NILES (CORPORATE)", If none leave blank |
| Tickets | 3.3.8 | Work Ticket Download - Category | The system shall include "Category" as a download option | |
| Tickets | 3.3.9 | Work Ticket Download - SubCategory | The system shall include "SubCategory" as a download option | |
| Tickets | 3.3.10 | Work Ticket Download - Ticket Description | The system shall include "Ticket Description" as a download option | |
| Tickets | 3.4 | Work Ticket - Current Status | The system shall show details about the current status of the Maintenance Ticket | |
| Tickets | 3.4.1 | Work Ticket - Current Status: Date Opened | The system shall show the "Date Opened" of the Work Ticket | Example: "31-May-03 07:57 CDT", If blank leave empty |
| Tickets | 3.4.2 | Work Ticket - Current Status: Date Closed | The system shall show the "Date Closed" of the Work Ticket | Example: "31-May-03 07:57 CDT", If blank leave empty |
| Ticket | 3.4.3 | Work Ticket - Current Status: Category | The system shall show the "Category" of the Work Ticket | |
| Ticket | 3.4.4 | Work Ticket - Current Status: SubCategory | The system shall show the "SubCategory" of the Work Ticket | |
| Ticket | 3.4.5 | Work Ticket - Current Status: Current Status | The system shall show the "Current Status" of the Work Ticket | |
| Ticket | 3.4.6 | Work Ticket - Current Status: Description | The system shall show the "Description" of the Work Ticket | |
| Tickets | 3.5 | Work Ticket - Ticket Activities | The system shall include the chronology of the ticket activities | |
| Tickets | 3.5.1 | Work Ticket - Ticket Activities: Time Stamp | The system shall include a timestamp of every Activity | |
| Tickets | 3.5.2 | Work Ticket - Ticket Activities: Milestone | The system shall associate a milestone with every activity | |
| Tickets | 3.5.3 | Work Ticket - Milestone Definitions | The system shall include a link on every milestone to a popup window with the definitions of the milestone | |
| Tickets | 3.5.4 | Work Ticket - Ticket Activities: Tech | The system shall indicate who completed an Activity by showing the tech or system who entered the Activity note | |
| Tickets | 3.5.5 | Work Ticket - Tech Contact Info | The system shall provide a popup window from a link on each tech's and systems initials indicating the contact information for the person entering the activity | |
| Tickets | 3.5.6 | Work Ticket - Ticket Activities: Detail | The system shall show the details of each Activity as entered by the tech or system | |
| Tickets | 3.6 | Work Ticket - Activity Chronology | The system shall allow users to change the chronological display order of Activities in an ascending or descending manner | |
| Network Tree | ||||
| Network Tree | 4.0 | Network Tree | The system shall include a hierarchical network tree | |
| Network Tree | 4.1 | Network Tree - Shown Elements: Channels | The system shall show available channels as the top level of the tree | Superusers only |
| Network Tree | Network Tree - Element Appearance: Channels | The system shall show an icon for Channels that visually indicates that it is a channel | ||
| Network Tree | 4.2 | Network Tree - Shown Elements: Customers | The system shall show available customers as the 2nd level of the tree | Superusers and Channel Users |
| Network Tree | Network Tree - Element Appearance: Customers | The system shall show an icon for Customers that visually indicates that it is a Customer | ||
| Network Tree | 4.2.1 | Network Tree - Shown Elements: Countries | The system shall show countries that contain sites as the 3rd level of the tree | All users; IF only one country has sites (ie USA), then skip this tree level and show states/provinces as 3rd level |
| Network Tree | 4.2.2 | Network Tree - Element Appearance: Country | The system shall show an icon for Countries that visually indicates that it is a Country | |
| Network Tree | 4.3 | Network Tree - Shown Elements: State/Province | The system shall show states/provinces that contain sites as the 4th level of the tree | |
| Network Tree | 4.3.1 | Network Tree - Element Appearance: State/Province | The system shall show an icon for State/Provinces that visually indicates that it is a State/Province | |
| Network Tree | 4.4 | Network Tree - Shown Elements: Site | The system shall show sites as the 5th level of the tree | |
| Network Tree | 4.4.1 | Network Tree - Element Appearance: Site | The system shall show an icon for sites that visually indicates that it is a site | |
| Network Tree | 4.5 | Network Tree - Shown Elements: Device | The system shall show devices as the 6th level of the tree | |
| Network Tree | 4.5.1 | Network Tree - Element Appearance: Device | The system shall show an icon for devices that visually indicates that it is a device | |
| Network Tree | 4.6 | Network Tree - Shown Elements: Port | The system shall show port (as available on the device) as the 7th level of the tree | |
| Network Tree | 4.6.1 | Network Tree - Element Appearance: Port | The system shall show an icon for ports that visually indicates that it is a port | |
| Network Tree | 4.7 | Network Tree - Shown Elements: Sub-Port | The system shall show sub-port (as available on the device) as the 8th level of the tree | |
| Network Tree | 4.7.1 | Network Tree - Element Appearance: Sub-Port | The system shall show an icon for sub-ports that visually indicates that it is a sub-port | |
| Network Tree | 4.8 | Network Tree - Elements in Event | The system shall provide icons for elements in Event | |
| Network Tree | 4.8.1 | Network Tree - Elements in Event: Ticket Open | The system shall provide icons for elements with a Ticket Open event below them | |
| Network Tree | 4.8.2 | Network Tree - Elements in Event: Active Alarm | The system shall provide icons for elements with Active Alarms below them | |
| Network Tree | 4.8.3 | Network Tree - Elements in Event: Ticket in Autoclose | The system shall provide icons for elements with Tickets in Autoclose below them | |
| Network Tree | 4.9 | Network Tree - Channel Action | The system shall take users to the customer view when clicking on the channel | This should change to include visual representation of the status of customers inside the channels |
| Network Tree | 4.10 | Network Tree - Customer Action | The system shall take users to the country view when clicking on the customer | |
| Network Tree | 4.11 | Network Tree - Country Action | The system shall take users to the State/Province view when clicking on the country | New action |
| Network Tree | 4.12 | Network Tree - State/Province Action | The system shall take users to the Site view when clicking on the State/Province | |
| Network Tree | 4.13 | Network Tree - State/Province Action: Events | The system shall take users to the event associated with the state (if one event), or to a list of events associated with the state (if multiple events) | |
| Network Tree | 4.14 | Network Tree - Site Action | The system shall take users to the Device view when clicking on the Site | |
| Network Tree | 4.15 | Network Tree - Site Action: Events | The system shall take users to the event associated with the site (if one event), or to a list of events associated with the site (if multiple events) | |
| Network Tree | 4.16 | Network Tree - Site Action: Inventory | The system shall provide a popup from the site menu called "Inventory." When the user clicks Inventory they shall be taken to the site inventory screen. | |
| Network Tree | 4.17 | Network Tree - Device Action | The system shall take users to the Port view when clicking on the Device | |
| Network Tree | 4.18 | Network Tree - Device Action: Events | The system shall take users to the event associated with the Device (if one event), or to a list of events associated with the Device (if multiple events) | |
| Network Tree | 4.19 | Network Tree - Device Action: Reports | The system shall provide a popup list of reports that are available on-demand from the device when the user clicks on the device. Clicking the report will take the user to that report for the device. | |
| Network Tree | 4.20 | Network Tree - Device Action: Inventory | The system shall provide a popup from the Device menu called "Inventory." When the user clicks Inventory they shall be taken to the site inventory screen with the device targetted. | |
| Network Tree | 4.21 | Network Tree - Port Action | The system shall take users to the Sub-Port view when clicking on the Sub-Port | |
| Network Tree | 4.22 | Network Tree - Port Action: Events | The system shall take users to the event associated with the Port (if one event), or to a list of events associated with the Port (if multiple events) | |
| Network Tree | 4.23 | Network Tree - Port Action: Reports | The system shall provide a popup list of reports that are available on-demand from the Port when the user clicks on the Port. Clicking the report will take the user to that report for the Port. | |
| Network Tree | 4.24 | Network Tree - Port Action: Inventory | The system shall provide a popup from the Port menu called "Inventory." When the user clicks Inventory they shall be taken to the site inventory screen with the Sub-Port targetted. | |
| Network Tree | 4.26 | Network Tree - Sub-Port Action: Events | The system shall take users to the event associated with the Sub-Port (if one event), or to a list of events associated with the Sub-Port (if multiple events) | |
| Network Tree | 4.27 | Network Tree - Sub-Port Action: Reports | The system shall provide a popup list of reSub-Ports that are available on-demand from the Sub-Port when the user clicks on the Sub-Port. Clicking the reSub-Port will take the user to that reSub-Port for the Sub-Port. | |
| Network Tree | 4.28 | Network Tree - Sub-Port Action: Inventory | The system shall provide a popup from the Sub-Port menu called "Inventory." When the user clicks Inventory they shall be taken to the site inventory screen with the Sub-Sub-Port targetted. | |
| Network Tree | 4.29 | Network Tree - Filters: Product (WAN) | The system shall provide the ability to filter the Elements in the tree by WAN elements. Filtration will propegate up from the Device to the Channel. | |
| Network Tree | 4.30 | Network Tree - Filters: Product (LAN) | The system shall provide the ability to filter the Elements in the tree by LAN elements. Filtration will propegate up from the Device to the Channel. | |
| Network Tree | 4.31 | Network Tree - Filters: Product (IP Telephony) | The system shall provide the ability to filter the Elements in the tree by IP Telephony elements. Filtration will propegate up from the Device to the Channel. | New Action |
| Network Tree | 4.32 | Network Tree - Filters: Product (Security) | The system shall provide the ability to filter the Elements in the tree by Security elements. Filtration will propegate up from the Device to the Channel. | |
| Network Tree | 4.33 | Network Tree - Filters: Product (Server) | The system shall provide the ability to filter the Elements in the tree by Server elements. Filtration will propegate up from the Device to the Channel. | |
| Network Tree | 4.34 | Network Tree - Filters: Events | The system shall provide the ability to filter on Elements with open Events or All Elements. Filtration will propegate up from the Element in Event to the Channel | |
| Network Tree | 4.35 | Network Tree - Filter Combinations | The system shall support multi-filters and allow filters to be toggled on and off independantly. | |
| Network Tree | 4.36 | Network Tree - Expand Collapse | The system shall support the ability to hide/show levels by expanding and collapsing as a tree | |
| Inventory | ||||
| Inventory | 5.0 | Inventory | The system shall provide an inventory of all customer devices loaded into it. | |
| Inventory | 5.1 | Inventory Query | The system shall provide a query interface to customer infrastructure devices | |
| Inventory | 5.1.1 | Query by Site | The system shall allow users to query Inventory by Site | |
| Inventory | 5.1.2 | Query by Multiple Sites | The system shall allow users to query Inventory by Multiple Sites | See Site Selection Utility |
| Inventory | 5.1.3 | Query by Site Data | The system shall allow users to query Inventory by Site Data (State, City, Street, Suite) | |
| Inventory | 5.1.4 | Query by Customer | The system shall allow users to query Inventory by Customer | Super and Channel Users only |
| Inventory | 5.2 | Inventory Query Results | The system shall provide query results by state | |
| Inventory | 5.2.1 | Inventory Query Results - Circuit Site Info | The system shall provide a link to hide/expose the circuit site info for each site returned by the query | Circuit Type, Circuit ID, Port Speed |
| Inventory | 5.3 | Site Inventory | The system shall provide a site inventory screen containing details about the site and its inventory | |
| Inventory | 5.3.1 | Site Inventory - Site Name | The system shall display the site name on the inventory screen | |
| Inventory | 5.3.2 | Site Inventory - Site ID | The system shall display the site ID on the inventory screen | |
| Inventory | 5.3.3 | Site Inventory - Customer | The system shall display the customer name on the inventory screen | Super and Channel Users only |
| Inventory | 5.3.4 | Site Inventory - Customer Notification | The system shall display the customer notification procedure for the site. | |
| Inventory | 5.3.4.1 | Site Inventory - Customer Notification: Toggle | The system shall provide the option to turn on/off the Customer Notification information from the screen | |
| Inventory | 5.3.5 | Site Inventory - Site Information | The system shall provide a Site Information area | |
| Inventory | 5.3.5.1 | Site Inventory - Site Information: Toggle | The system shall provide the option to turn on/off the Site Information area. | |
| Inventory | 5.3.5.2 | Site Inventory - Site Information: Site Name | The system shall display the Site Name in the Site Information area. | |
| Inventory | 5.3.5.3 | Site Inventory - Site Information: Street | The system shall display the Street in the Site Information area. | |
| Inventory | 5.3.5.4 | Site Inventory - Site Information: Country | The system shall display the Country in the Site Information area. | |
| Inventory | 5.3.5.5 | Site Inventory - Site Information: Site ID | The system shall display the Site ID in the Site Information area. | |
| Inventory | 5.3.5.6 | Site Inventory - Site Information: City | The system shall display the City in the Site Information area. | |
| Inventory | 5.3.5.7 | Site Inventory - Site Information: Zip/Postal Code | The system shall display the Zip/Postal Code in the Site Information area. | |
| Inventory | 5.3.5.8 | Site Inventory - Site Information: Site Type | The system shall display the Site Type in the Site Information area. | |
| Inventory | 5.3.5.9 | Site Inventory - Site Information: State/Province | The system shall display the State/Province in the Site Information area. | |
| Inventory | 5.3.5.10 | Site Inventory - Site Information: Phone | The system shall display the Phone in the Site Information area. | |
| Inventory | 5.3.6 | Site Inventory - Site Contact | The system shall provide a Site Contact area | |
| Inventory | 5.3.6.1 | Site Inventory - Site Contact: Toggle | The system shall provide the option to turn on/off the Site Contact area. | |
| Inventory | 5.3.6.2 | Site Inventory - Site Contact: Contact Name | The system shall provide a list of Site Contact Names in the Site Contact area. | |
| Inventory | 5.3.6.3 | Site Inventory - Site Contact: Contact Type | The system shall provide the Contact Type for each Site Contact in the Site Contact area. | |
| Inventory | 5.3.6.3.1 | Site Inventory - Site Contact: Contact Type Popup | The system shall popup a window with definitions of each Contact Type | |
| Inventory | 5.3.6.3.2 | Site Inventory - Site Contact: Contact Type Popup Targetting | The system shall target the window to the definition that was clicked in the Site Contact area. | |
| Inventory | 5.3.6.4 | Site Inventory - Site Contact: Phone | The system shall display the Primary Phone for each Site Contact in the Site Contact area. | |
| Inventory | 5.3.6.5 | Site Inventory - Site Contact: Notes | The system shall display the Notes for each Site Contact in the Site Contact area. | |
| Inventory | 5.3.7 | Site Inventory - Site Contact: Request Modification | The system shall provide a link to the "Contact Us" screen to request modifications to the Contact information. | Super, Channel Logins, Customer Admin Login. |
| Inventory | 5.3.7.1 | Site Inventory - Site Contact: Request Modification Prefill | The
system shall prefill the following information into the "Contact
Us" screen when being used to request changes to the Site Contacts:
Routing selected to "Support," text box to read "Contact
Modification Request for AB DICK BIRMINGHAM (BIRMINGHAM), Site ID: 129911 <Enter your request below>" |
|
| Inventory | 5.3.8 | Site Inventory - WAN, LAN, Server, Security | The system shall provide inventory for WAN, LAN, Server, and Security Devices | |
| Inventory | 5.3.8.1 | Site Inventory - Device Name | The system shall display the device name of each device shown in the inventory. | |
| Inventory | 5.3.8.2 | Site Inventory - Device Number | The system shall display the device number of each device shown in the inventory. | |
| Inventory | 5.3.8.3 | Site Inventory - Device Reports | The system shall provide links to the reports available for each element displayed in the Site Inventory. | |
| Inventory | 5.3.8.4 | Site Inventory - Device Attributes: System Description | The system shall display the system description for each device shown in the inventory. | |
| Inventory | 5.3.8.5 | Site Inventory - Device Attributes: System Maintenance Vendor | The system shall display the maintenance vendor for each device shown in the inventory. | |
| Inventory | 5.3.8.6 | Site Inventory - Device Attributes: Serial Number | The system shall display the Serial Number for each device shown in the inventory. | |
| Inventory | 5.3.8.7 | Site Inventory - Device Attributes: Coverage Type | The system shall display the Coverage Type for each device shown in the inventory. | |
| Inventory | 5.3.8.8 | Site Inventory - Device Attributes: Contract Number | The system shall display the Contract Number for each device shown in the inventory. | |
| Inventory | 5.3.8.9 | Site Inventory - Device Attributes: Config Last Archived | The system shall display the Config Last Archived Date for each device shown in the inventory. | |
| Inventory | 5.3.8.10 | Site Inventory - Device Attributes: Out of Band Access | The system shall display the Out of Band Access Number for each device shown in the inventory. | |
| Inventory | 5.3.9 | Site Inventory - Card | The system shall display the name for any Card attached to devices in the system. | |
| Inventory | 5.3.9.1 | Site Inventory - Card: Card Slot Name | The system shall display the Card Slot Name for each card shown in the inventory. | |
| Inventory | 5.3.10 | Site Inventory - Port | The system shall display the Port name for each Port in the system. | |
| Inventory | 5.3.10.1 | Site Inventory - Port: Comp Type | The system shall display the Comp Type for each Port in the system. | |
| Inventory | 5.3.10.2 | Site Inventory - Port: Carrier ID | The system shall display the Carrier ID for each Port in the system. | |
| Inventory | 5.3.10.3 | Site Inventory - Port: Carrier Name | The system shall display the Carrier Name for each Port in the system. | |
| Inventory | 5.3.10.4 | Site Inventory - Port: D/V Channels | The system shall display the D/V Channels for each Port in the system. | |
| Inventory | 5.3.10.5 | Site Inventory - Port: Port Speed | The system shall display the Port Speed for each Port in the system. | |
| Inventory | 5.3.11 | Site Inventory - Sub-Port | The system shall display the name for each Sub-Port in the system. | |
| Inventory | 5.3.11.1 | Site Inventory - Sub-Port: Protocol | The system shall display the Protocol for each Sub-Port in the system. | |
| Inventory | 5.3.11.2 | Site Inventory - Sub-Port: Address | The system shall display the Address for each Sub-Port in the system. | |
| Inventory | 5.3.11.3 | Site Inventory - Sub-Port: DLCI | The system shall display the DLCI for each Sub-Port in the system. | |
| Inventory | 5.3.11.4 | Site Inventory - Sub-Port: Customer IP Address | The system shall display the Customer IP Address (Only if NATed) for each Sub-Port in the system. | |
| Inventory | 5.3.12 | Site Inventory - Virtual Circuit | The system shall display the virtual circuit ID for each virtual circuit in the system. | |
| Inventory | 5.3.12.1 | Site Inventory - Virtual Circuit: Description | The system shall display the Description for each virtual circuit in the system. | |
| Inventory | 5.3.12.2 | Site Inventory - Virtual Circuit: Availability Flag | The system shall display the Availability Flag for each virtual circuit in the system. | |
| Inventory | 5.3.12.3 | Site Inventory - Virtual Circuit: Virtual Network Type | The system shall display the Virtual Network Type for each virtual circuit in the system. | |
| Inventory | 5.3.12.4 | Site Inventory - Virtual Circuit: Start Date | The system shall display the Start Date for each virtual circuit in the system. | |
| Inventory | 5.3.12.5 | Site Inventory - Virtual Circuit: Remote Virtual Port | The system shall display the Remote Virtual Port for each virtual circuit in the system. | |
| Inventory | 5.3.12.5.1 | Site Inventory - Remote Virtual Port Action | The system shall link the user to the Site Information screen for the remote site when the user clicks the Remote Virtual Port link. | |
| Inventory | 5.3.13 | Site Inventory - Request Inventory Modification | The system shall provide a link to the "Contact Us" screen to request modifications to the Inventory information. | |
| Inventory | 5.3.13.1 | Site Inventory - Request Inventory Modification Prefill | The
system shall prefill the following information into the "Contact
Us" screen when being used to request changes to the Inventory: Routing
selected to "Support," text box to read "Inventory
Modification Request for AB DICK BIRMINGHAM (BIRMINGHAM), Site ID: 129911 <Enter your request below> " |
|
| Inventory | 5.3.14 | Site Inventory - Site Notes | The system shall display the Site Notes for the site. | |
| Inventory | 5.3.14.1 | Site Inventory - Site Notes | The system shall provide the option to turn on/off the Site Notes from the screen | |
| Inventory | 5.3.14.2 | Site Inventory - Site Notes: Time Stamp | The system shall display the Time Stamp for each note in the Site Notes area. | |
| Inventory | 5.3.14.3 | Site Inventory - Site Notes: Author | The system shall display the Author for each note in the Site Notes area. | |
| Inventory | 5.3.14.4 | Site Inventory - Site Notes: Notes | The system shall display the Notes for each note in the Site Notes area. | |
| Inventory | 5.3.15 | Site Inventory - Install Events | The system shall display the Install Events for the Site | |
| Inventory | 5.3.15.1 | Site Inventory - Install Events: Event Description | The system shall display the Event Description for each Install Event for the Site | |
| Inventory | 5.3.15.1.1 | Site Inventory - Install Events: Event Description Link | The system shall link the user to a popup window of descriptions for each event description. | |
| Inventory | 5.3.15.1.2 | Site Inventory - Event Description Targetting | The system shall target the window to the definition that was clicked in the Site Contact area. | |
| Inventory | 5.3.15.2 | Site Inventory - Install Events: Status | The system shall display the Status for each Install Event for the Site | |
| Inventory | 5.3.15.2.1 | Site Inventory - Install Events: Status Link | The system shall link the user to a popup window of descriptions for each Status. | |
| Inventory | 5.3.15.2.2 | Site Inventory - Status Definition Targetting | The system shall target the window to the definition that was clicked in the Site Contact area. | |
| Inventory | 5.3.15.3 | Site Inventory - Install Events: Planned Completion Date | The system shall display the Planned Completion Date for each Install Event for the Site | |
| Inventory | 5.3.15.4 | Site Inventory - Install Events: Actual Completion Date | The system shall display the Actual Completion Date for each Install Event for the Site | |
| Help | 6.0 | Help | The system shall include a Help category | |
| Help | 6.1 | Help - General | The system shall include a help for cookies, navigation, | |
| Help | 6.1 | Help - Home | The system shall include help for home and preferences | |
| Help | 6.2 | Help - Active Map | The system shall include help for Active Map | |
| Help | 6.3 | Help - Trouble Ticket | The system shall include help for Trouble Tickets | Rename Maintainance Tickets |
| Help | 6.4 | Help - Installations | The system shall include help for Installs | |
| Help | 6.5 | Help - Inventory | The system shall include help for Inventory | |
| Help | 6.6 | Help - Reports | The system shall include help for Reports | |
| Help | 6.7 | Tutorial | The system shall include a clickable tutorial supplied by Marketing | |
| 7.0 | The system shall provide a print option | |||
| 7.1 | Print area | The print option shall print only the right frame | Probably not relevant under the new UI | |
| Active Map | ||||
| Active Map | General | Active Map - Generation | The system shall support the ability to geographically map the site locations for a specific customer. | |
| Active Map | General | Active Map - Reference Labels | The system shall provide site names for each site plotted on the map. | |
| Active Map | General | Active Map - Generation | The system shall support the ability to modify the color of a site plot point to reflect status. | |
| Active Map | General | Active Map - Account Selection | The system shall allow Channel users to select from customers associated to their channel. | |
| Active Map | General | Active Map - Generation | The system shall support the ability to modify the color of each state/province to reflect associated site status. | |
| Active Map | General | Active Map - Generation | The system shall support the ability to geographically map the WAN connections between sites for a specific customer. | |
| Active Map | General | Active Map - Generation | The system shall support the ability to modify the color of a WAN connection to reflect status. | |
| Active Map | General | Active Map - Visualization | The system shall support zoom magnification at 1.4x. | |
| Active Map | General | Active Map - Visualization | The system shall support zoom magnification at 1.6x. | |
| Active Map | General | Active Map - Visualization | The system shall support zoom magnification at 1.8x. | |
| Active Map | General | Active Map - Visualization | The system shall support zoom magnification at 2.0x. | |
| Active Map | General | Active Map - Visualization | The system shall support zoom magnification at 2.5x. | |
| Active Map | General | Active Map - Visualization | The system shall support zoom magnification at 3.0x. | |
| Active Map | General | Active Map - Visualization | The system shall support zoom magnification at 3.5x. | |
| Active Map | General | Active Map - Visualization | The system shall support zoom magnification at 4.0x. | |
| Active Map | General | Active Map - Visualization | The system shall support the ability to provide 14 levels of zoom magnification | |
| Active Map | Navigation | Active Map - Navigation | The system shall support the ability to navigate to open tickets by selecting a state/province/body of water from the map. | |
| Active Map | Navigation | Active Map - Navigation | The system shall support the ability to navigate to open tickets by selecting a site plot point from the map. | |
| Active Map | Navigation | Active Map - Navigation | The system shall support the ability to navigate to open tickets by selecting a WAN connection from the map. | |
| Active Map | Navigation | Active Map - Navigation | The system shall support the ability to navigate to a different section of the map by selecting a water body on the map. This selection will recenter the map based on the selected body of water. | |
| Active Map | Navigation | Active Map - Compass Navigation | The system shall support the ability to navigate to a different section of the map by utilizing a compass. | |
| Active Map | Navigation | Active Map - Thumbnail Navigation | The system shall support the ability to navigate to a different section of the map by utilizing a thumbnail map of the world. | |
| Active Map | Navigation | Active Map - Thumbnail Navigation | The system shall display the region name when the user mouses over a region in the navigational aid thumbnail map of the world. | |
| Active Map | Navigation | Active Map - Visualization | The system shall support the ability to decrease the area displayed in the map by selecting to 'zoom in'. The reduced map will be the center of the map displayed when the user selected to resize. | |
| Active Map | Navigation | Active Map - Visualization | The system shall support the ability to increase the area displayed in the map by selecting to 'zoom out'. The enlarged map will be the center of the map displayed when the user selected to resize. | |
| Active Map | Navigation | Active Map - Navigation | The system shall support the ability to navigate to site information by selecting a state/province/body of water from the map. | |
| Active Map | Navigation | Active Map - Navigation | The system shall support the ability to navigate to site information by selecting a site plot point from the map. | |
| Active Map | Navigation | Active Map - Navigation | The system shall support the ability to navigate to site information by selecting a WAN connection from the map. | |
| Active Map | Navigation | Active Map - Visualization | The system shall support the ability to navigate to a different section of the map by selecting a state/province/body of water on the map. This selection will recenter the map based on the selected point. | |
| Active Map | Navigation | Active Map - Visualization | The system shall support the ability to navigate to a different section of the map by selecting a site plot point on the map. This selection will recenter the map based on the selected point. | |
| Active Map | Navigation | Active Map - Visualization | The system shall support the ability to navigate to a different section of the map by selecting a WAN connection on the map. This selection will recenter the map based on the selected point. | |
| Active Map | Navigation | Active Map - Visualization | The system shall support multiple magnification levels for zoom magnification behavior. | |
| Active Map | Preference | Active Map - zoom default setting | The system shall utilize, as the default, zoom magnification level 2.0. | |
| Active Map | Preference | Active Map - WAN connection default setting | The system shall utilize yellow, as a default, to represent WAN connections with one or more maintenance tickets in a state of autoclose, while containing 0 maintenance tickets with a state of open. | |
| Active Map | Preference | Active Map - site plot points default setting | The system shall utilize yellow, as a default, to represent site plot points with one or more maintenance tickets in a state of autoclose, while containing 0 maintenance tickets with a state of open. | |
| Active Map | Preference | Active Map - site plot points default setting | The system shall utilize red, as a default, to represent site plot points on dial backup. | |
| Active Map | Preference | Active Map - WAN connection default setting | The system shall utilize red, as a default, to represent WAN connections on dial backup. | |
| Active Map | Preference | Active Map - site labels default setting | The system shall utilize black, as a default, to display site labels. | |
| Active Map | Preference | Active Map - refresh default setting | The system shall utilize the activated state, as a default, for the Map refresh user preference. | |
| Active Map | Preference | Active Map - site plot points default setting | The system shall utilize light green, as a default, to represent site plot points with no open maintenance tickets. | |
| Active Map | Preference | Active Map - site plot points default setting | The system shall utilize light red, as a default, to represent site plot points with open maintenance tickets. | |
| Active Map | Preference | Active Map - state/province default setting | The system shall utilize red, as a default, to represent states/provinces containing one or more sites with a maintenance ticket in a state of autoclose, while containing 0 sites with a state of down. | |
| Active Map | Preference | Active Map - state/province default setting | The system shall utilize red, as a default, to represent states/provinces containing one or more sites on dial backup, while containing 0 sites with a state of down. | |
| Active Map | Preference | Active Map - state/province default setting | The system shall utilize black, as a default, to represent states/provinces containing 1 or more sites with 1 or more open maintenance tickets. | |
| Active Map | Preference | Active Map - state/province default setting | The system shall utilize blue, as a default, to represent states/provinces containing 1or more sites, none of which are associated to open maintenance tickets. | |
| Active Map | Preference | Active Map - state/province default setting | The system shall utilize beige, as a default, to represent states/provinces containing 0 sites. | |
| Active Map | Preference | Active Map - WAN connection default setting | The system shall utilize, by default, light green to represent WAN connections with no open maintenance tickets. | |
| Active Map | Preference | Active Map - WAN connection default setting | The system shall utilize, by default, light red to represent WAN connections with open maintenance tickets. | |
| Active Map | Preference | Active Map - Preferences | The system shall support the ability to capture user preferences for viewing Active Map. | |
| Active Map | Preference | Active Map - drill down preferences | The system shall support the ability to capture drill down behavior in the user preferences. | |
| Active Map | Preference | Active Map - refresh preferences | The system shall support the ability to activate Active Map screen refresh in the user preferences. | |
| Active Map | Preference | Active Map - state/province preferences | The system shall support the ability to capture the display color for states/provinces containing 1 or more sites, none of which are associated to open maintenance tickets in the user preferences. | |
| Active Map | Preference | Active Map - state/province preferences | The system shall support the ability to capture the display color for states/provinces containing 1 or more sites with 1 or more open maintenance tickets in the user preferences. | |
| Active Map | Preference | Active Map - state/province preferences | The system shall support the ability to capture the display color for states/provinces containing 1 or more sites with 1 or more tickets in a state of autoclose in the user preferences. | |
| Active Map | Preference | Active Map - state/province preferences | The system shall support the ability to capture the display color for states/provinces containing 1 or more sites on dial backup, none of which are associated to open maintenance tickets, in the user preferences. | |
| Active Map | Preference | Active Map - site plot point preferences | The system shall support the ability to capture the display color for site plot points with no open maintenance tickets in the user preferences. | |
| Active Map | Preference | Active Map - site plot point preferences | The system shall support the ability to capture the display color for site plot points with 1 or more maintenance tickets with a state of open in the user preferences. | |
| Active Map | Preference | Active Map - site plot point preferences | The system shall support the ability to capture the display color for site plot points with one or more maintenance tickets in a state of autoclose, while containing 0 maintenance tickets with a state of open in the user preferences. | |
| Active Map | Preference | Active Map - site plot point preferences | The system shall support the ability to capture the display color for site plot points with a status of On Dial Backup with no open maintenance tickets in the user preferences. | |
| Active Map | Preference | Active Map - site label preferences | The system shall support the ability to capture the display color for site labels in the user preferences. | |
| Active Map | Personalization | Active Map - state/province personalization | The system shall support the ability to display the user selected color for states/provinces containing 1 or more sites, none of which are associated to open maintenance tickets. | |
| Active Map | Personalization | Active Map - state/province personalization | The system shall support the ability to display the user selected color for states/provinces containing 1 or more sites with 1 or more open maintenance tickets. | |
| Active Map | Personalization | Active Map - state/province personalization | The system shall support the ability to display the user selected color for states/provinces containing 1 or more sites with 1 or more open maintenance tickets. | |
| Active Map | Personalization | Active Map - state/province personalization | The system shall support the ability to display the user selected color for states/provinces containing 1 or more sites in a state of on dial backup | |
| Active Map | Personalization | Active Map - site plot point personalization | The system shall support the ability to display the user selected color for site plot points with no open maintenance tickets. | |
| Active Map | Personalization | Active Map - site plot point personalization | The system shall support the ability to display the user selected color for site plot points with 1 or more maintenance tickets in a state of open. | |
| Active Map | Personalization | Active Map - site plot point personalization | The system shall support the ability to display the user selected color for site plot points with one or more maintenance tickets in a state of autoclose, while containing 0 maintenance tickets with a state of open. | |
| Active Map | Personalization | Active Map - site plot point personalization | The system shall support the ability to display the user selected color for site plot points with a status of On Dial Backup. | |
| Active Map | Personalization | Active Map - site label personalization | The system shall support the ability to display site labels with the user selected color. | |
| Active Map | Preference | Active Map - zoom personalization | The system shall support the ability to capture the zoom magnification level in the user preferences. | |
| Active Map | Personalization | Active Map - WAN connection personalization | The system shall support the ability to display the user selected color for WAN connections with no open maintenance tickets. | |
| Active Map | Personalization | Active Map - WAN connection personalization | The system shall support the ability to display the user selected color for WAN connections with 1 or more maintenance tickets in a state of open. | |
| Active Map | Personalization | Active Map - WAN connection personalization | The system shall support the ability to display the user selected color for WAN connections with one or more maintenance tickets in a state of autoclose, while containing 0 maintenance tickets with a state of open. | |
| Active Map | Personalization | Active Map - WAN connection personalization | The system shall support the ability to display the user selected color for WAN connections with a status of On Dial Backup. | |
| Home Page | ||||
| Home Page | Personalization | Home Page - personalization | The system shall provide multiple versions of the Home Page. | |
| Home Page | Personalization | Home Page - personalization | The system shall determine which home page to display based on user role. | |
| Home Page - Customer | General | Home Page - Customer content | The system shall display the current version number of the portal on the customer home page. | |
| Home Page - Customer | General | Home Page - Customer Open Tickets | The system shall display a list of the 3 most recently opened maintenance tickets for the customer on the customer home page. | |
| Home Page - Customer | General | Home Page - Customer Open Tickets - Ticket ID | The system shall display the Ticket ID in the list of open maintenance tickets for the customer on the customer home page. | |
| Home Page - Customer | General | Home Page - Customer Open Tickets - Ticket ID | The system shall support the ability to present the Ticket ID as a hyperlink. When selected, the link shall display the ticket details page. | |
| Home Page - Customer | General | Home Page - Customer Open Tickets - Date and Time Opened | The system shall display the Date and Time Opened in the list of open maintenance tickets for the customer on the customer home page. | |
| Home Page - Customer | General | Home Page - Customer Open Tickets - Sites Affected | The system shall display the Sites Affected in the list of open maintenance tickets for the customer on the customer home page. | |
| Home Page - Customer | General | Home Page - Customer Open Tickets - Sites Affected | The system shall support the ability to present each Site Affected as a hyperlink. When selected, the link shall display the site details page. | |
| Home Page - Customer | General | Home Page - Customer Installs | The system shall display a list of the 3 closest scheduled install activities for the customer on the customer home page. | |
| Home Page - Customer | General | Home Page - Customer Installs - Site ID | The system shall display the Site ID in the list of scheduled install activities for the customer on the customer home page. | |
| Home Page - Customer | General | Home Page - Customer Installs - Site ID | The system shall support the ability to present the Site ID as a hyperlink. When selected, the link shall display the site details page. | |
| Home Page - Customer | General | Home Page - Customer Installs - Planned Completion Date | The system shall display the Planned Completion Date in the list of scheduled install activities for the customer on the customer home page. | |
| Home Page - Customer | General | Home Page - Customer NMC News | The system shall display the NMC News on the customer home page. | |
| Home Page - Customer | General | Home Page - Customer NMC News - Posted Date | The system shall display the Posted Date for each NMC News item on the customer home page. | |
| Home Page - Customer | General | Home Page - Customer NMC News - News Title | The system shall display the News Title for each NMC News item on the customer home page. | |
| Home Page - Customer | Navigation | Home Page - Customer NMC News - News Title | The system shall support the ability to present the News Title as a hyperlink for each NMC News item. When selected, the link shall display the article page. | |
| Home Page - Customer | General | Home Page - Customer What's New | The system shall display the What's New in this Version on the customer home page. | |
| Home Page - Customer | Navigation | Home Page - Customer - Privacy Statement | The system shall display a link to the Privacy Statement on the customer home page. | |
| Home Page - Customer | Navigation | Home Page - Customer Contact Us | The system shall display a link to the Contact Us form on the customer home page. | |
| Home Page - Customer | Navigation | Home Page - Customer Training | The system shall display a link to the Training page on the customer home page. | |
| Home Page - Channel | General | Home Page - Channel Welcone | The system shall display a welcome message on the channel home page. | |
| Home Page - Channel | General | Home Page - Channel Image | The system shall display an image on the channel home page. | |
| Home Page - Administrator | General | Home Page - Admin Image | The system shall display an image on the administrator home page. | |
| General | ||||
| General | Preferences | Preferences - time zone | The system shall support the ability to capture the user time zone in the user preferences. | |
| General | Preferences | Preferences - navigation bar | The system shall support the ability to capture the vertical navigation bar width in the user preferences. | |
| General | Preferences | Preferences - event type | The system shall support the ability to capture the event type in the user preferences. | |
| General | Preferences | Preferences - time zone default | The system shall utilize, as the default, (GMT -6.00) America Chicago for the user time zone. | |
| General | Preferences | Preferences - navigation bar default | The system shall utilize, as the default, 200 pixels for the vertical navigation bar width. | |
| General | Preferences | Preferences - event type default | The system shall utilize, as the default, Tickets for the event type. | |
| General | Preferences | Preferences - commit | The system shall allow a user to save their preferences. | |
| General | Preferences | Preferences - commit confirmation | The system shall display a dialog window when a user commits new preferences. The dialog window shall display the following text - "New Preferences Saved. You might want to refresh the browser window to see the new changes." The dialog window shall contain a single button labeled 'OK'. | Remove this requirement |
| General | Preferences | Preferences - commit confirmation | The system shall close the New Preferences Saved dialog window when a user selects 'OK' | Remove this requirement |