Hello. I'm newly called to Stake Technology Specialist. I'm discovering, with the pandemic and a number of stake and ward changes, there are a number of computers, printers, etc that are out of date and need attention. Additionally, there are numerous incidents, issues, requests, etc that are coming my way. I'd like to maintain a list of items that come my way, with info about church unit involved, requestor, the issue, priority, etc. Basic information for any incident management system. While I can do this in excel, I'm wondering if the church has a system that I can use? If not, is there a reccommended app, perhaps something in the cloud, etc. that might be free?
As I'm just getting started so part of my effort will include setting up processes which will make ongoing support more effective and efficient not only for me, but for those who need my asssistance.
Thanks in advance.
Request \ Incident Management - Stake Level
-
- New Member
- Posts: 7
- Joined: Sun Nov 27, 2016 5:39 pm
-
- Community Administrator
- Posts: 35207
- Joined: Sat Jan 20, 2007 2:53 pm
- Location: U.S.
Re: Request \ Incident Management - Stake Level
I'm not aware of any such tracking. I do have a spreadsheet that I keep to track the computers so I know to pester FM when they come due for replacement.
Otherwise, even with 10 units in my stake, I don't have enough active issue to bother with any ticket tracking system.
Otherwise, even with 10 units in my stake, I don't have enough active issue to bother with any ticket tracking system.
Have you searched the Help Center? Try doing a Google search and adding "site:churchofjesuschrist.org/help" to the search criteria.
So we can better help you, please edit your Profile to include your general location.
So we can better help you, please edit your Profile to include your general location.
-
- Community Moderators
- Posts: 11643
- Joined: Mon Mar 17, 2008 10:27 pm
- Location: US
Re: Request / Incident Management - Stake Level
If it will involve the FM Group, use the Facility Issue Reporting (FIR) system.
Otherwise, like russellhltn, I keep an inventory of all the administrative computers with serial numbers and dates they were placed in service, so that I will know when they should be replaced on the five-year cycle. I work with an FM Group that is really good about keeping track of the computers we are supposed to have and where they should be.
I am not aware of an online incident tracking system. I just take the calls as they come and resolve them over the phone with the clerks involved.
As the STS, I also keep information on all of the Zoom accounts for the wards and branches so that when the person running the account moves and the information is not passed along, I am able to get them reconnected. Along with the Zoom accounts, I run the associated Gmail account for each of them.
I use the Church Network Manager website to monitor the meetinghouse networks and maintain the Lehi WiFi network for those using it. Those passwords expire every 90 days.
I run the stake YouTube account used for stake conference webcasts and sacrament meetings held at the stake center.
Otherwise, like russellhltn, I keep an inventory of all the administrative computers with serial numbers and dates they were placed in service, so that I will know when they should be replaced on the five-year cycle. I work with an FM Group that is really good about keeping track of the computers we are supposed to have and where they should be.
I am not aware of an online incident tracking system. I just take the calls as they come and resolve them over the phone with the clerks involved.
As the STS, I also keep information on all of the Zoom accounts for the wards and branches so that when the person running the account moves and the information is not passed along, I am able to get them reconnected. Along with the Zoom accounts, I run the associated Gmail account for each of them.
I use the Church Network Manager website to monitor the meetinghouse networks and maintain the Lehi WiFi network for those using it. Those passwords expire every 90 days.
I run the stake YouTube account used for stake conference webcasts and sacrament meetings held at the stake center.
-
- Community Administrator
- Posts: 35207
- Joined: Sat Jan 20, 2007 2:53 pm
- Location: U.S.
Re: Request / Incident Management - Stake Level
5 years is for Windows machines. Chrome has a longer 8 year cycle.
But what you describe is what I do as well. Since I have an Android phone, the few things I track I do in Sheets (a free Google Docs thing). I can update on my phone or from a web browser.
Have you searched the Help Center? Try doing a Google search and adding "site:churchofjesuschrist.org/help" to the search criteria.
So we can better help you, please edit your Profile to include your general location.
So we can better help you, please edit your Profile to include your general location.
-
- New Member
- Posts: 7
- Joined: Sun Nov 27, 2016 5:39 pm
Re: Request \ Incident Management - Stake Level
russellhltn wrote:
> I'm not aware of any such tracking. I do have a spreadsheet that I keep to
> track the computers so I know to pester FM when they come due for
> replacement.
>
> Otherwise, even with 10 units in my stake, I don't have enough active issue
> to bother with any ticket tracking system.
Thank you for the reply!
> I'm not aware of any such tracking. I do have a spreadsheet that I keep to
> track the computers so I know to pester FM when they come due for
> replacement.
>
> Otherwise, even with 10 units in my stake, I don't have enough active issue
> to bother with any ticket tracking system.
Thank you for the reply!
-
- New Member
- Posts: 7
- Joined: Sun Nov 27, 2016 5:39 pm
Re: Request / Incident Management - Stake Level
lajackson wrote:
> If it will involve the FM Group, use the Facility Issue Reporting (FIR)
> system.
>
> Otherwise, like russellhltn, I keep an inventory of all the administrative
> computers with serial numbers and dates they were placed in service, so
> that I will know when they should be replaced on the five-year cycle. I
> work with an FM Group that is really good about keeping track of the
> computers we are supposed to have and where they should be.
>
> I am not aware of an online incident tracking system. I just take the calls
> as they come and resolve them over the phone with the clerks involved.
>
> As the STS, I also keep information on all of the Zoom accounts for the
> wards and branches so that when the person running the account moves and
> the information is not passed along, I am able to get them reconnected.
> Along with the Zoom accounts, I run the associated Gmail account for each
> of them.
>
> I use the Church Network Manager website to monitor the meetinghouse
> networks and maintain the Lehi WiFi network for those using it. Those
> passwords expire every 90 days.
>
> I run the stake YouTube account used for stake conference webcasts and
> sacrament meetings held at the stake center.
Thank you for the reply!
> If it will involve the FM Group, use the Facility Issue Reporting (FIR)
> system.
>
> Otherwise, like russellhltn, I keep an inventory of all the administrative
> computers with serial numbers and dates they were placed in service, so
> that I will know when they should be replaced on the five-year cycle. I
> work with an FM Group that is really good about keeping track of the
> computers we are supposed to have and where they should be.
>
> I am not aware of an online incident tracking system. I just take the calls
> as they come and resolve them over the phone with the clerks involved.
>
> As the STS, I also keep information on all of the Zoom accounts for the
> wards and branches so that when the person running the account moves and
> the information is not passed along, I am able to get them reconnected.
> Along with the Zoom accounts, I run the associated Gmail account for each
> of them.
>
> I use the Church Network Manager website to monitor the meetinghouse
> networks and maintain the Lehi WiFi network for those using it. Those
> passwords expire every 90 days.
>
> I run the stake YouTube account used for stake conference webcasts and
> sacrament meetings held at the stake center.
Thank you for the reply!