Programming[Project|WIP] Internal Faults/Outage System
Posted:
Programming[Project|WIP] Internal Faults/Outage SystemPosted:
Status: Offline
Joined: May 28, 201311Year Member
Posts: 1,236
Reputation Power: 7224
Status: Offline
Joined: May 28, 201311Year Member
Posts: 1,236
Reputation Power: 7224
|
Hey all,
After having spent weeks on end at home bored out my head with this quarantine I decided to start a small project the day before yesterday and all work was done in one day. The project idea I came up with was an internal system for reporting Faults/Outages to a network team where they could then review and if it was the case could open a fault in a specific area or service. the goal for this was to create a fully functioning web application. Please do note I spent no time on the design concept of this and this is not the final design for it either. I was focusing on development (back-end). Please note that this is not a finished project in any way. A lot of work has to be done, I personally prefer to do all functionality on the back-end before looking at the front-end design. There is still a lot of work that is required to be done in order to call this a completed project. Current todo List Both-Ends
Front-End
Back-End
Normal User/Staff Account
These pages are for normal user accounts only. Admins have better access and an Admin controlled area. Login Page I created the website to have to work with logged in users only, due to the nature of the website being that it would be for an internal usage on a closed network of sorts or intranet I put a checkbox that has to be checked agreeing to the ICT policies. Index The index page shows a general how-to-use sort of system, explaining how each outage is represented and also some test data to mess around with when using the search box shown on the main page. This is how all outages are searched for based on the Postal/Zip Code, Reference, Name, and Area. Report Queue The Report Queue shows a list of all reported outages to the team which is pending investigation, this allows for the ability to avoid duplicate reports. It shows limited information but the information showed is most ideal to avoid new outages being reported. Open Faults/Outages Once an outage has been reported and the team has then investigated that outages it then appears on a page that shows all open outages at that time. This information can be used to then identify if an outage is opened or the user needs to send a new report. Reporting a new Fault When the user (staff member) has checked and there are no open outages or pending reports for a specific area they can then send a report to the team. Once the report has been sent there are shown a statement to read to the customer. All sections of the report have to be filled in or the report cannot be sent. View Open Outage All outages follow a similar layout at this time, it shows all the relevant information that may be required for the person searching it up. User Control Panel Each user has a control panel which at this time holds limited content. The contents it does hold is general information about the user. Their name, username, company, manager, etc are all shown here. In addition to this internal numbers are shown where the agent can call another department if they need to. Admin Account/Networks/Server Admin
Networks, Server Admins or just Admins have a separate panel, this allows them more control over the outages than that of a normal user account. Index The admin index page is very different from normal users. The administrator control panel index shows the currently open reports that are being either investigated or monitored and can be updated with the click of a button. New Reports New Reports show differently for members of the administrator groups, this is due to their ability to alter the information for 1st line users to be able to help customers etc. When they visit the new reports page they get the ability to edit and update any report that is currently Awaiting Review. Once they begin to edit a report they get limited options on what they want to do with it. They can Monitor, Disregard, Resolve or Open Outage. Add New Users Within the ACP new user accounts can be added, a lot of information is needed but this allows for filling in details to easily identify each user. Add Outage A lot of information is required to open an outage, this is so that the users can get a lot of valuable information that can support any question added whilst keeping detailed records. Fault List The Open Faults list is different as all faults can be clicked to view and edited from one click on the page. It'll open the current fault and show all information that can then be updated and saved. I appreciate any feedback on this project. The core concept isn't something people who were bored would usually do but I like to try to do things differently. I hope to hear some feedback and suggestions on things that would make this more fun to work on. Thank you for taking the time to have a look at this |
The following 1 user thanked Nasyr for this useful post:
Fold (04-22-2020)
#2. Posted:
Status: Offline
Joined: Oct 01, 201113Year Member
Posts: 2,845
Reputation Power: 19778
Motto: Brandon has stopped paying for his motto advertising space. This motto is now vacant.
Motto: Brandon has stopped paying for his motto advertising space. This motto is now vacant.
Status: Offline
Joined: Oct 01, 201113Year Member
Posts: 2,845
Reputation Power: 19778
Motto: Brandon has stopped paying for his motto advertising space. This motto is now vacant.
|
Looks really cool
Is all of the data stored in a SQL db? How long would you keep expired tickets/faults logged? Looks like a really fun project! |
- 1useful
- 0not useful
#3. Posted:
Status: Offline
Joined: May 28, 201311Year Member
Posts: 1,236
Reputation Power: 7224
Status: Offline
Joined: May 28, 201311Year Member
Posts: 1,236
Reputation Power: 7224
Fold wrote Looks really cool All the data is held within an SQL Database. At the moment I don't see any need to remove the tickets. Closed tickets cannot be seen or searched for at this time, I think it would be good to keep them for archive purposes. What do you think? |
- 0useful
- 0not useful
#4. Posted:
Status: Offline
Joined: Oct 01, 201113Year Member
Posts: 2,845
Reputation Power: 19778
Motto: Brandon has stopped paying for his motto advertising space. This motto is now vacant.
Motto: Brandon has stopped paying for his motto advertising space. This motto is now vacant.
Status: Offline
Joined: Oct 01, 201113Year Member
Posts: 2,845
Reputation Power: 19778
Motto: Brandon has stopped paying for his motto advertising space. This motto is now vacant.
Nasyr wroteFold wrote Looks really cool Nice! I was just curious. The only time it may become problematic is if there are incredibly large amounts (millions of records) of data moving through in which case the storage of the data may become burdensome. I don't imagine such a heavy load, but could be a useful option for admins to be able to set up an expiry time for archives just in case. I had a conversation with someone involved in a license plate reader project that logged the plates of passing cars. They had originally just planned to hold data indefinitely but because of the volume and sensitivity of the data they decided much later after the project was done to add a 6 month expiration on the data. I'm not sure if there'd be any possibly sensitive info stored in the DB, so probably doesn't apply as closely, but it's always something I remember during data archive |
- 0useful
- 0not useful
#5. Posted:
Status: Offline
Joined: May 28, 201311Year Member
Posts: 1,236
Reputation Power: 7224
Status: Offline
Joined: May 28, 201311Year Member
Posts: 1,236
Reputation Power: 7224
Fold wrote I must admit I like the idea behind this, I may create a new table for all resolved tickets that has a delete date in which they are then purged from the table. Realistically from the screenshots shown above it would be more of a record of details about an issue and where it originated (like postal area) where multiple people are affected. No sensitive data would be held about a single person. |
- 0useful
- 0not useful
#6. Posted:
Status: Offline
Joined: Nov 05, 201311Year Member
Posts: 2,753
Reputation Power: 452
Status: Offline
Joined: Nov 05, 201311Year Member
Posts: 2,753
Reputation Power: 452
| Out of curiosity, what is your technology stack? |
- 0useful
- 0not useful
Users browsing this topic: None