FM: Facility Issue Reporting (FIR) Pilot

Pilot

Facility Issue Reporting (FIR)

"The Facility Issue Reporting (FIR) system provides LDS Church leaders, building representatives, and facilities management groups the ability to report and review facility issues electronically. It uses a web interface to streamline reporting, viewing, and resolving facility issues."

This system is currently only a Pilot. Only users in those stakes that have been contacted as being participants in the pilot phase of the system should attempt to use the system at this time.

It appears at this time that they have enough stakes for the Pilot, about thirty (30) stakes

PLEASE PLEASE PLEASE PLEASE PLEASE let this be a quick pilot with NO bugs to find.... WE NEED THIS VERY BADLY

Who has or will have access to the facilities reporting feature? Just wondering how we define "leaders".

Thanks.

If you log in and look in the help sections, there is a manual and that manual has a matrix of leaders and their access

JohnShaw wrote:If you log in and look in the help sections, there is a manual and that manual has a matrix of leaders and their access

Unless you are in one of those stakes participating in the beta test you cannot log in and look in the help sections.

jdlessley wrote:Unless you are in one of those stakes participating in the beta test you cannot log in and look in the help sections.

Our stake was not invited to participate, but I could log in just fine. There is a warning as you login that you shouldn't use the system unless you have been invited, but if you have an appropriate calling you should be able to login and see the system, including the help system.

aebrown wrote:Our stake was not invited to participate, but I could log in just fine. There is a warning as you login that you shouldn't use the system unless you have been invited, but if you have an appropriate calling you should be able to login and see the system, including the help system.

I tried to log in but was given the denied message. My point is that not everyone has access to the matrix of leaders and their access. Which in my view is only informative to those who already have the access and does nothing to inform others to identify issues or just a simple lack of the appropriate calling.

I was able to log in just fine. I was pleased to see that STS has a role in the system.

jdlessley wrote:I tried to log in but was given the denied message. My point is that not everyone has access to the matrix of leaders and their access. Which in my view is only informative to those who already have the access and does nothing to inform others to identify issues or just a simple lack of the appropriate calling.

Well, we are all jumping the gun a bit here. When the system is officially rolled out, those who are authorized to access the system will be informed of that through regular channels. For stakes on the pilot, they already know. For those who are not authorized but try to access the system, simply being told that you are not authorized is an entirely appropriate response.

aebrown wrote:Well, we are all jumping the gun a bit here. When the system is officially rolled out, those who are authorized to access the system will be informed of that through regular channels. For stakes on the pilot, they already know. For those who are not authorized but try to access the system, simply being told that you are not authorized is an entirely appropriate response.

The question was asked in post #4 as to who will have access and what the definition of leaders is. I do not think it is jumping the gun to ask such questions. I was merely pointing out to the response in post #5 that not everyone has the access to see who has access. I also think that if it is going to be announced to the entire community then it is only appropriate to provide the parameters of access.

Personally I don't think the post starting this thread should have been made since the audience for the pilot as well as the final product is such a limited group. It only begs the questions that have been asked.

jdlessley wrote:Personally I don't think the post starting this thread should have been made since the audience for the pilot as well as the final product is such a limited group. It only begs the questions that have been asked.

You're probably right that it was inappropriate for someone participating in the pilot to make such a broad announcement. However, I would note that I (as an STS) can now see the FIR system on my Tools menu on lds.org (even though my stake has not been notified that it is participating in the pilot). I assume (but don't know) that other people with callings that allow access to FIR can now see a similar link on their Tools menu. If that is true, then it is entirely appropriate to have a discussion about the tool, since a broad set of people will be seeing the link, which would naturally spark some curiosity.

The list of callings in stakes and wards that have access to FIR is as follows:

• Ward Building Representative
• Stake Physical Facilities Representative (Stake PFR)
• Stake Presidency
• Stake Assistant Clerk, Technology Specialist
• Ward Bishopric member
• Ward Assistant Clerk
• Seminary Teacher

There are many other positions listed in the documentation, but they are at the FM, area, temple, CHQ, or other level.

Some questions come to mind:

• Why is a Ward Clerk not mentioned (only an assistant)?
• Alternatively, why is a Ward Assistant Clerk mentioned at all? (the only stake clerk -- including assistants -- that is listed is the STS, who clearly does have responsibilities in this area)
• When I login, I am asked to choose between my regular Assistant Stake Clerk calling and my STS calling. That implies that an Assistant Stake Clerk has access, but that is not listed on the access matrix.
• How does the FM group know who the PFR is? Clearly they do, but it's not through MLS, since there is no standard calling for PFR in stake MLS. In our stake, when the PFR changes, we simply communicate the new PFR's contact information to the FM Director by email. Do they then enter the person into FMAT, and somehow connect it to their membership number? Otherwise, I don't see how the PFR can have special access privileges for FIR.

aebrown wrote:I assume (but don't know) that other people with callings that allow access to FIR can now see a similar link on their Tools menu. If that is true, then it is entirely appropriate to have a discussion about the tool, since a broad set of people will be seeing the link, which would naturally spark some curiosity.

The FIR link shows up before you even log in to lds.org so the link can indeed be seen very widely.

aebrown wrote:Some questions come to mind:

Why is a Ward Clerk not mentioned (only an assistant)?

What is the definition of "Ward Bishopric member"? Some people stop at councilors. Others may include Executive Secretary and/or Ward Clerk.

eblood66 wrote:The FIR link shows up before you even log in to lds.org so the link can indeed be seen very widely.

I get the "Facility Issue Reporting" link in my Tools menu yet I am not in a calling that is on the list aebrown posted. I am a ward assistant clerk - finance. Using the same logic used for access to other Tools menu items such as "Leader and Clerk Resources" I should not even see the "Facility Issue Reporting" menu item.

jdlessley wrote:I get the "Facility Issue Reporting" link in my Tools menu yet I am not in a calling that is on the list aebrown posted. I am a ward assistant clerk - finance. Using the same logic used for access to other Tools menu items such as "Leader and Clerk Resources" I should not even see the "Facility Issue Reporting" menu item.

I agree that it would make more sense if it only showed up for those with access. But that's not how it's working right now. It is showing unconditionally even if the user isn't logged in at all (unlike the Leder and Clerk Resources which only show up after you log in).

We have Stake Building Specialists, I wonder if that is the standard position

aebrown wrote:Well, we are all jumping the gun a bit here. When the system is officially rolled out, those who are authorized to access the system will be informed of that through regular channels. For stakes on the pilot, they already know. For those who are not authorized but try to access the system, simply being told that you are not authorized is an entirely appropriate response.

Access is controlled specifically by approved role. If you have the 'role' but can't get in, then your official calling isn't in the church directory of leaders (which we ping to ensure valid access).

We'll be modifying the training material to include details about getting this done properly. We want everyone in proper callings to use FIR to help maintain our buildings. And yes, we are planning on as short of a PILOT period as possible. 3-5 years ought to be enough time.:p Actually our hope is less than 60 days.

We're also clarifying roles, since they are called slightly different things in different areas or systems. Which is why we have the PILOT. Thanks for the interest. We are hurrying.

redforddj wrote:Access is controlled specifically by approved role. If you have the 'role' but can't get in, then your official calling isn't in the church directory of leaders (which we ping to ensure valid access).

OK, this just went from murky to totally muddy. So what are you talking about when you say "role"? What is a "role"? That last I checked in CDOL only callings were listed there. Are there now "roles" from some other system that is going to be added? What is an "approved role"?

jdlessley wrote:OK, this just went from murky to totally muddy. So what are you talking about when you say "role"? What is a "role"? That last I checked in CDOL only callings were listed there. Are there now "roles" from some other system that is going to be added? What is an "approved role"?

It seems pretty clear to me that redforddj is simply using the term "role" because not every person with access to FIR does so because of a standard calling in CDOL. There are 23 different roles that have access, only 6 of which are at the ward and stake level. One of those 6 roles is the stake PFR, which does not have a standard calling. Some of the 17 non-stake/ward roles look like employee roles to me (not callings). So the note about standard callings definitely doesn't apply to all 23 roles -- there must be other systems involved that control access. So the term "role" is more accurate for this application.

So what is a role?

jdlessley wrote:So what is a role?

The term "role" is used in the realm of software to refer to actors in a system that perform different functions, either by their choice, or by limitations the system places on them. Clearly, redforddj is using the term in the second meaning I noted. These 23 different roles perform different functions (some roles may perform fundamentally different functions, and some may perform the same function as others, but in a different realm).

The term "role" in the context of FIR is a convenient term for referring to a collection of people who perform different functions in the FIR system; some of them have callings (e.g., bishopric member), some have specific assignments within a calling (e.g., a high councilor assigned to be the PFR), some are employees (e.g., Facilities Manager), and others may well be assigned to a role by name (I would guess that this is the case with "HQ Administrator – Help Desk").

Some of these roles are listed in CDOL because of a calling, and others are listed in CDOL because of employment. Still others (PFR for certain; there may be others) are not listed in CDOL at all and must come from some other system.

I can't think of a better term than "role" in this situation. The list of approved roles is:

• Ward Building Representative
• Stake Physical Facilities Representative (Stake PFR)
• Stake Presidency
• Stake Assistant Clerk, Technology Specialist
• Ward Bishopric member
• Ward Assistant Clerk
• Temple Presidency
• Seminary Teacher
• Seminary Principal
• Mission President
• Welfare Grain Storage Manager
• Welfare DI Store Manager
• LDS Family Services Manager
• Distribution Services Manager
• Family History Center Regional Manager
• HQ Administrator – Help Desk
• Facilities Manager (FM)
• FM Assistant Facilities Manager
• Administrative Assistant (AA)
• Mechanic
• Area Physical Facilities Manager
• Area O&M Manager
• O&M Regional Manager

On the same theme about "roles", does the Ward Building Representative have to be a priesthood holder or can a sister be called to this position?

Biggles wrote:On the same theme about "roles", does the Ward Building Representative have to be a priesthood holder or can a sister be called to this position?

See Handbook 1, Section 8.2.7 for a description of this role. That section talks about the possibility of calling a "member" to serve in this position, but does use male pronouns to refer to that person. In our stake a member of the bishopric always fills that role, so your particular question has never come up.

aebrown wrote:See Handbook 1, Section 8.2.7 for a description of this role. That section talks about the possibility of calling a "member" to serve in this position, but does use male pronouns to refer to that person. In our stake a member of the bishopric always fills that role, so your particular question has never come up.

Thanks for quick the response. I checked that entry in Handbook 1. As you rightly pointed out it does infer a male to be called to that position.

We have a sister who has effectively been involved in the building, cleaning and organizing maintenance etc., for the last 20+ years. Her expertise in this calling would be invaluable, if she was eligible.

Attached is the manual

Let your Stake Presidency make the call, they have the keys

Facility Issue Reporting (FIR) functions in the following environments, if you have an acceptable role in MLS/CDOL

Microsoft Operating Systems:
Windows 7 SP1
Windows XP SP3
Browsers: Internet Explorer (IE), Firefox, Safari, Google Chrome

AppleOperating Systems and Devices:
IOS
iPad 1 and iPad 2
iPhone 3G, 3GS, 4G, 4GS
Android Based Telephone/Tablet:
Android HTC Inspire Telephone from ATT
Kindle Fire from Amazon (Silk web browser)
Device that need to be tested:
Nook from Barnes and Noble. if you have one, please give it a try and report back

You must have an acceptable role in MLS/CDOL, the following error message was provided when a member with only a role of "Primary Pianist", which is not an acceptable role, tried to access the FIR application

------------------------------------------------
Windows platform:
Permission Denied

Error: You do not currently have rights to access the resource you requested.

------------------------------------------------
Apple IOS iPAD 2 (mobile) platform:
FIR Mobile - Error Mobile Error

Well, turns out that great minds think alike!

I have been talking about creating a ticketing system for our Stake to submit issues to the FM group. If they liked it, they would have been welcome to ask their remaining stakes to use it. My hope was that the church would see it and want to duplicate (replace) it with one that was church-wide.

I registered "myPFR.org" just for this purpose. I had installed a free ticketing system (OTRS) and was dragging my feet on configuring it. I think the procrastination was actually inspiration!

I read through the flowcharts of how issues are reported and escalated and it is exactly how I was going to design the ticketing system, and is how I have insisted that issues get reported by my stake.

So, I'm feeling pretty good

Ok, all kidding aside, this addresses a HUGE problem that I was blind-sighted by: lack of customer service and accountability in the stake/FM relationship.

dotson98.... This is one of those areas that I've mentioned earlier. There are a few key things that ALL Wards and Stakes do, like the ticketing solution for MF.. you've spent dozens of hours, I've spent a dozen hours, and on and on... how many thousands of dozens of hours volunteers put in. We are all in the same position when it comes to considering, selecting, calling, sustaining, setting apart.. that happens at both ward and stake levels, there is also the issue of MP advancement, and positions in the ward that require stake approval, sustaining, calling, setting apart, etc... again, my thinking is that thousands of dozens of hours of volunteer time spent doing something the church can centralize.

We hadn't heard that FIR was being developed, could someone maybe leak the fact that this other area is being considered or not? If not, please, how do we get it requested?

I'm part of the pilot - and I've just added an 'Issue'. A couple of things I was wondering are why the system asks me for my phone number and email address when it should already have it from my LDS Account credentials? Also - I logged an issue - but the fields for setting the Priority weren't available to me? Is the priority a local request, or what the FM deem the priority to be?

JohnShaw wrote:dotson98.... This is one of those areas that I've mentioned earlier. There are a few key things that ALL Wards and Stakes do, like the ticketing solution for MF.. you've spent dozens of hours, I've spent a dozen hours, and on and on... how many thousands of dozens of hours volunteers put in. We are all in the same position when it comes to considering, selecting, calling, sustaining, setting apart.. that happens at both ward and stake levels, there is also the issue of MP advancement, and positions in the ward that require stake approval, sustaining, calling, setting apart, etc... again, my thinking is that thousands of dozens of hours of volunteer time spent doing something the church can centralize.

We hadn't heard that FIR was being developed, could someone maybe leak the fact that this other area is being considered or not? If not, please, how do we get it requested?

I've got to say, it seems that more development time is spent with applications that regular members will use. Applications that would be used by unit administrators seem to get less development resources and attention. Your assessment seems to hit the nail on the head.

Hello, everyone. I'm new to LDS Tech. I'm the Stake Physical Facilities Rep in our stake. We just joined the FIR Pilot. And we're in the process of getting all our Ward Physical Facilities Reps (PFRs) entered into MLS so that they can participate. Reporting facilities issues and monitoring their progress has been a big issue in our stake, so we're thrilled to be in the pilot. We'll see how it goes. Wish us luck.

Headquarters is working on updating the FIR user manual so that it will have a section about using standard MLS positions and not custom MLS positions
Ward/Branch: Building Representative
Stake: Stake Physical Facilities Representative

There are several sources:
1) Click here to access the official source: Handbook 2: Administering the Church
Then scroll down and click on "19. Callings in the Church"
Then scroll down and click on "Chart of Callings"

2) Click here to access the WiKi: Callings
Then scroll down to "Resources" and select the PDF of MLS callings you want to view:
Standard Ward Callings: (PDF) A list of all the standard ward callings
Standard Stake Callings: (PDF) A list of all the standard stake callings

3) MLS (Ward/Branch or Stake) desktop:Click here to access the WiKi about how to view in MLS application the "Difference between standard positions and custom positions"

This Pilot has been going on for a while, is there an end in sight? FM got a message that said 2 weeks about 1 month ago? Can someone sign up for the pilot?

They are getting closer

Please review and post any comments or suggestions to this thread about the attached updated FIR user's manual

Facility Issue Reporting (FIR) System
User’s Manual
Dated: 29 March 2012

Rumor: "The Pilot of FIR will be officially expanded to all of US and Canada as of May 14, 2012. Notice will be forthcoming to all Stake Presidents with in the week."

Note: It is still a pilot system


Facility Issue Reporting (click here to view the FIR Wiki)

won't be here fast enough!

Join the Pilot system early:
Ask your local FM Group if your stake can be added to the FIR pilot system

FIR start up can be very smooth if the members of your units have a valid e-mail address associated with their LDSAccount and if they have a standard MLS calling

Please ask your Clerks to verify that your units are NOT using custom MLS callings for Building Representatives, (e.g.,"Building Cleanup Specialist" or ""Building Maintenance Specialist")

Suggest that you change the above type of callings to an MLS standard calling so that they will have access to the new "Facility Issue Reporting" system:
1) ward/branches: "Building Representative"
2) stake: "Stake Building Specialist"

Has anyone heard about this 'communication' going to stake presidents? Are we still on track for a May 14th roll-out of the eternal beta?

The FIR Wiki appears to have been updated with the user manual that has been approved by the Correlation.Council [url=https://tech.lds.org/wiki/Facility_Issue_Reporting]Facility Issue Reporting (click here to view the FIR Wiki)

Rumor: They just need the Correlation.Council approval of the letter (process) to be sent to the Stake Presidents.

Anyone heard anything?

When trying to log in FIR Pilot and I click on Continue the following error message comes up: "Data Tables warning: JSON data from server failed to load or be parsed. This is most likely to be caused by a JSON formatting error"
I have been trying to Escalate reports, if any, I cannot even get there since yesterday, Monday, June 18, 2012.

Thank you,
ramirezla@ldschurch.org

Another month has gone by.... Can anyone out there speak to the actual issues involved with why this solution has not rolled out? We put several items on stand-by in our Stake feeling that a few months and they would be solved, it's now been almost 6 months since we've all first started seeing the app on the Tools list. It would be helpful to have some kind of indication - that isn't speculation.

I just got an email advising that FIR was now available to the general membership. I can't log in, and the site still says that it's in Pilot. I'll be checking MLS to make sure that I have a Standard Calling assigned. I don't think that I do.

dotson98 wrote:I just got an email advising that FIR was now available to the general membership. I can't log in, and the site still says that it's in Pilot. I'll be checking MLS to make sure that I have a Standard Calling assigned. I don't think that I do.

Who was that email from? Do you know who it was sent to? Our stake has received no such communication.

aebrown wrote:Who was that email from? Do you know who it was sent to? Our stake has received no such communication.

It was sent to me by the FM group. It was a forward of a forward, originally sent by the Church Meetinghouse Facilities Department. I re-read the email and it doesn't say anything about "generally available". It just says the it is available "for your use". Additionally, the FIR website says that it is still in Pilot.

Sorry, folks. I think I jumped the gun. Appears that they just rolled it out to our FM group.

Perhaps it's being rolled out as an "expanding pilot"?

RussellHltn wrote:Perhaps it's being rolled out as an "expanding pilot"?

You mean, like a "co-pilot"?

No, more like adding more FM groups in larger chunks until they are all added.

dotson98 wrote:You mean, like a "co-pilot"?

Good one!

Anyone know if the FIR system has been taken down? We were using it in our stake for awhile with no problems. Today I logged in to lds.org to report a new issue, and the link is gone from my Tools. Can't find it anywhere.

mwgrover wrote:Anyone know if the FIR system has been taken down? We were using it in our stake for awhile with no problems. Today I logged in to lds.org to report a new issue, and the link is gone from my Tools. Can't find it anywhere.

It does seem to have been removed from the Tools menu, but you can still access it at https://lds.org/fir

Thanks! Couldn't remember the address, although that is pretty intuitive and I should have tried that myself...

Facility Issue Reporting (FIR) has returned to the lds.org Tools menu

From:FMG Support FMD
Sent: Monday, July 09, 2012 11:05 AM
Subject: Facility Issue Reporting System (FIR) Now Available (Corrected Version)

We are pleased to announce the Facility Issue Reporting (FIR) system is available for your use. The FIR system will allow local leaders to more easily communicate facility issues with your office.

FMs will be the primary driver in the implementation of the FIR system in the stakes they serve. As soon as you are ready, provide the attached information to the stakes you serve. The information should go to stake presidencies, bishoprics, stake PFRs, and ward building representatives.

Webinar training on use of FIR has been provided previously. A session recording titled “Using the Facility Issue Reporting (FIR) System” is available in the recordings page of the MFD Training and Resources site.

For access issues please contact Global Services. For questions or problems regarding the system itself please contact Meetinghouse Facilities System Support, as noted on the last page of the User Manual.

pete.arnett wrote:FMs will be the primary driver in the implementation of the FIR system in the stakes they serve. As soon as you are ready, provide the attached information to the stakes you serve. The information should go to stake presidencies, bishoprics, stake PFRs, and ward building representatives.

It sounds to me as if the FM Group decides when a stake will begin using the FIR system, and then sends instructions from the FM Group to the Stake as they begin to implement the process.

It appears that all of the Stake Physical Facilities Representative (Stake PFR) have now been changed to "Stake Building Specialist"

See CDOL.org or your LDS.org/directory, select "Stake Information" > "Stake Leaders and Organizations" > "Other Callings" > and see if your Stake PFR is listed as a "Stake Building Specialist"

And they just got the Facility Issue Reporting (FIR) System User’s Manual approved

pete.arnett wrote:It appears that all of the Stake Physical Facilities Representative (Stake PFR) have now been changed to "Stake Building Specialist"

I didn't know that there ever was a standard calling in stake MLS for "Stake Physical Facilities Representative"; there has always been a "Stake Building Specialist", but that seems like a different position. Our stake has never had any entry in MLS for Stake PFR, and we don't have any SBSs (not in the past, nor at this moment).

Are you basing this statement on some communication? If so, from whom? Or is it based on your own observation of a change in your stake's CDOL? You said "all of the ..." -- do you have evidence or documentation beyond just your stake?

Just an observation over several stakes PFR position in MLS - interesting

I added our Stake Facilities people as Stake Building Specialists after logging into the FIR app and seeing that was the Role assigned with permissions. So mine weren't changed, but were manually done.

So, are you saying that I need to change the calling in MLS to "Stake Building Specialist"? Because he can't get access right now while he is the "Stake Physical Facilities Representative (PFR)".

kerrybird wrote:So, are you saying that I need to change the calling in MLS to "Stake Building Specialist"? Because he can't get access right now while he is the "Stake Physical Facilities Representative (PFR)".

I suggest you run the Custom Position Review tool described in this link to make sure he has a standard position. If it's not standard, it won't work regardless of what the position is titled.

Information that was sent to Facilities Management Groups (FMG)

“The issue that we have had with Stake PFR’s not being able to access the FIR program should now be fixed. If you are aware of any of your Stake PFR’s who have not been able to access FIR, would you please let them know this has been resolved? If they continue having problems logging into FIR, please have them verify they have a valid LDS account and that they were set up specifically with the calling of Stake Physical Facilities Representative. If they still can’t get in please have them contact the Administrative Support team at 801-240-5688 or FMD-FMG-Support@ldschurch.org.”

I've just submitted this via the Fir Feedback link : -

Our Stake Physical Facilities Representative (SPFR) was unable to gain access to the FIR application on the web. He was correctly entered into the Stake MLS, using the Standard Calling. Entering him as the Stake Building Specialist (SBS) enabled him to gain access and then his SPFR selection showed up.
The manual makes no mention of the SBS, only the SPFR.
It would appear that the correct Login authentication has got mixed up somewhere!

Also sent via email as in pete.arnetts post above.

Just to clarify he is now entered with both callings, in the Stake MLS

I wish I'd remembered this post before now

I believe the FIR tool is out of Pilot. Is that correct? Our FM stated that they were awaiting final word from Salt Lake and that they had not received that yet. Any official word that I missed on this forum?

heyring wrote:I believe the FIR tool is out of Pilot. Is that correct? Our FM stated that they were awaiting final word from Salt Lake and that they had not received that yet. Any official word that I missed on this forum?

I have not yet seen anything at this forum. If the FIR tool is no longer a pilot program, I do not recall seeing that announced here at the Forum.

lajackson wrote:I have not yet seen anything at this forum. If the FIR tool is no longer a pilot program, I do not recall seeing that announced here at the Forum.

As stated, I also have not seen anything official posted on the Forum!

We have/are being given training, in the use of FIR, by our FM Group. We have been using the FIR Tool for about 3 weeks now!

I'm also waiting a response, from official sources, about my post #68 above!

Suggestion...Have the first 3 rows automatically filled in, name, phone number and email when creating a new issue. Currently the name is auto filled, that's good.

Anyone have knowledge about FIR e-mail notifications not working?

Several stakes in our region are having issues with not receiving FIR e-mail notifications

Sent feedback to FIR

I am listed as building rep, but still get permission denied when trying to access fir

whats wrong

others in stake have same problem

members of bishopric no problem

garyblds wrote:I am listed as building rep, but still get permission denied when trying to access fir

You must be listed in stake MLS with the correct standard calling. There is no standard calling of "building rep"; you would most likely need the standard calling of "Stake Building Specialist". Ask your stake clerk to make sure your calling is entered correctly.

Bishopric members are more likely to be entered in MLS with the standard calling, which would explain why they have access.

Has this ticketing system been fully implemented? If so is it going to be expanded to include technology? Might be good for it to be public to the users in case there is a problem with TV's and such.

ryan8382 wrote:Has this ticketing system been fully implemented?

Not all stakes or FM groups are using the FIR system at this point. But the system is certainly functional, and is being used in many places.

ryan8382 wrote:If so is it going to be expanded to include technology?

The FIR system can already be used for any issues, including technology-related issues. So it requires no expansion for that area.

ryan8382 wrote:Might be good for it to be public to the users in case there is a problem with TV's and such.

The FIR system is designed to be accessed only by authorized users. Others who need to know the status of an issue can communicate with appropriate authorized users.

As in several above posts, our Stake PFR cannot access the FIR. I verified he is in the standard position in MLS 3.5.1, which appears in Organizations > Other Organizations > Facilities. The FIR manual Permissions table shows the SPFR is an authorized FIR position. I looked in CDOL's Show All Positions for our stake and there is no entry for "Facilities" or SPFR. I wonder if this lack of an entry in CDOL is keeping SPFRs out of FIR, though there's no CDOL entry for SBS either and that role seems to be able to get in according to above posts.

jeromer7 wrote:I wonder if this lack of an entry in CDOL is keeping SPFRs out of FIR

That seems almost certain, since FIR can't possibly know that the PFR is authorized to use FIR unless CDOL says he has an appropriate calling.

Our stake's PFR shows up in CDOL in the Facilities organization with the standard calling of "Stake Physical Facilities Representative."

jeromer7 wrote:... though there's no CDOL entry for SBS either and that role seems to be able to get in according to above posts.

That's certainly odd. Is there any chance that your SBS has some other calling as well that allows access to FIR?

And I'm not quite sure what you mean by "that role seems to be able to get in according to above posts." Do you mean that you don't see a CDOL entry for an SBS in your stake, but the person with the SBS calling in your stake can still get in to FIR? Or are you assuming that situation is true for other stakes? I've never heard of a case where an SBS has no entry in CDOL but still can get into FIR.

jeromer7 wrote:I wonder if this lack of an entry in CDOL is keeping SPFRs out of FIR. . .

Go into MLS and change the set apart flag, save it, then change it back, save it again and do a send/receive. This will cause MLS to resend the calling position to CDOL. CDOL should update within a few seconds. It may take up to a day, or even two, for the FIRS system to get that update and allow access.

aebrown wrote:Our stake's PFR shows up in CDOL in the Facilities organization with the standard calling of "Stake Physical Facilities Representative."

jeromer7 wrote:... though there's no CDOL entry for SBS either and that role seems to be able to get in according to above posts.

That's certainly odd. Is there any chance that your SBS has some other calling as well that allows access to FIR?

I do not have an SBS assigned in my Stake MLS.

aebrown wrote:And I'm not quite sure what you mean by "that role seems to be able to get in according to above posts." Do you mean that you don't see a CDOL entry for an SBS in your stake, but the person with the SBS calling in your stake can still get in to FIR? Or are you assuming that situation is true for other stakes? I've never heard of a case where an SBS has no entry in CDOL but still can get into FIR.

I was referring to previous posts, e.g. #68, that indicated the SBS, if defined in Stake MLS, could access FIR. I see now I was just confusing the issue.

My point was that I do have an individual identified in the standard position of Stake Physical Facilities Representative showing in the Facilities area of Other Organizations in Stake MLS, but there is no "Facilities" area in CDOL for my stake as there is in your stake.

I will try this tonight, however, I'm not confident it will work. I had the SPFR defined prior to MLS 3.5.1 and didn't realize there was a problem until the high councilor in that role contacted me last week saying he couldn't access FIR. So I checked the Stake MLS and sure enough, the PFR was not defined in the Facilities area of "Other Organizations." I added him in and did a S/R. I waited two days and saw no change in CDOL for that. Last Sunday I made other changes and they show up today, but still no "Facilities" or PFR.

jeromer7 wrote: I added him in and did a S/R. I waited two days and saw no change in CDOL for that.

If you added him in early December that could be the problem. CDOL was losing data sent from MLS during that time.

jeromer7 wrote:Last Sunday I made other changes and they show up today, but still no "Facilities" or PFR.

That won't show up until you do something to trigger MLS to resend it.

The PFR was added on Jan 18, but never showed up in CDOL even though changes I made on Jan 20 did.

Anyway, last night I changed the set apart radio button as suggested and did a Send/Receive. When I checked CDOL this morning, much to my surprise, the Facilities section is now there in Show All Positions and the PFR entry is defined. Not sure why it didn't take the first time, but the end result is all that matters.

So, after using FIR for several months, I'd sure like to offer suggestions to the developers. I've clicked on the link provided and submitted it, but so far, seems to have been ignored / unanswered.

The main problem I have is that I don't get notified when a new issue is submitted...

Hello,

I have been using FIR for a long time now and I went to check the status of my issues on Monday March 4 and was unable to access the site. Today I tried again and the site is giving me random errors and not loading properly.

1. login at lds.org
2. click tool and then FIR
3. click continue on the information popup: https://www.lds.org/fir
4. Receive the following error at this url: https://www.lds.org/FIR/ViewIssues
Sorry, an error occurred while processing your request:
Error: Error executing child request for handler 'System.Web.Mvc.HttpHandlerUtil+ServerExecuteHttpHandlerWrapper'.
The website administrator has been notified. Please click here to return to the website.

It was working fine last Sunday, but it's definitely having some problems now. Once every 3 or 4 attempts I can get past the initial error screen, but even then it just sits and spins trying to bring up our stake's FIR issues. Smells like a database that needs rebuilding.

Looks like it's working again.

Just a quick note: If your FM group hasn't notified your stake that you're in the pilot, it won't matter if you use it or not.

Our FM didn't even know it existed. A couple of bishops in our stake submitted items through it and then were frustrated when it didn't work. There is now a message that pops up notifying users that if they haven't heard about it from other sources (ie, their priesthood leaders who learn about it from the local FM) that they shouldn't use it.

Our FM Group is encouraging the stakes reporting to them to utilize FIR, but can anyone verify if it's still considered a Pilot? It's been well over a year now and I don't remember seeing anything official either way.

I can confirm it is working for me. Now to clear out my backlog of issues.

Mikerowaved wrote:Looks like it's working again.

I have downloaded the User Manual for FIR and our Stake is an approved pilot for FIR. The Manual states that a Ward Building Representative would have access to FIR. However, we have the most current version of MLS and the Standard Position is not available to select as a calling. We still have to use the Custom Building Rep calling. How do we get an updated list in MLS of Standard Callings so that our Ward Building Rep can use FIR?

Our Stake (Venice Italy) is using it and BRs (Building Rappresentative) are allowed, and really did, to insert new issue.
I can't see wich calling are they holding on MLS (I've no access to it and web directory is not in sync) so I can't be useful on this.

ericbbuhler wrote:I have downloaded the User Manual for FIR and our Stake is an approved pilot for FIR. The Manual states that a Ward Building Representative would have access to FIR. However, we have the most current version of MLS and the Standard Position is not available to select as a calling. We still have to use the Custom Building Rep calling. How do we get an updated list in MLS of Standard Callings so that our Ward Building Rep can use FIR?

I'm not in front of MLS at the moment, but if you check under Facilities the Standard Calling of Building Representative should be listed. The sub heading of Facilities might be under Other.

New Mobile App, if your Stake/District is using FIR

"The Meetinghouse Facilities Department is widening the release of an application called Facility Issue Reporting or FIR that simplifies the reporting of facility issues to the local facilities management office. This tool makes it simple and easy to report facility issues directly to the facilities manager or administrative assistant.

Please note that the stake physical facilities representative is no longer required to escalate issues to the facilities manager.

The updated desktop version will be accessible on the Internet March 19, 2015 at lds.org/fir or on LDS.org.

The mobile version will be available April 17, 2015 and can then be downloaded to tablets or smart phones from the Apple® App Store or Google® Play store by searching for LDS FIR.

Members of stake or ward councils can access the system using their authorized LDS account.

FIR is also accessible by other Church department personnel in Seminaries and Institutes, welfare facilities, and missions."

If your Stake/District is using FIR

The new FIR website has been updated using the same URL

The great news is that it has been simplified

From "Help" on the new version of the FIR website
"How do I report an issue to my Facilities Manager in FIR?"
"In the FIR system, you can report an issue directly to the FM office. By using the ‘Report Issue’ screen, you can report all applicable information on a specific issue found in the facility and add pictures to help the FM better understand the issue you are reporting. After you submit the issue, the system automatically notifies the FM immediately."

"How can I access the Facility Issue Reporting (FIR) tool?"
"An LDS account is required to access the FIR system. If you need an LDS Account, you can set one up at https://ldsaccount.lds.org. The ward or stake clerk must also set up the user with the appropriate authorized position in Member and Leader Services (MLS) before they can access the FIR system."

If your Stake/District is using FIR

The mobile version should be available May 21, 2015 and can then be downloaded to tablets or smart phones from the Apple® App Store or Google® Play store by searching for LDS FIR.

Members of stake or ward councils can access the system using their authorized LDS account.

FIR is also accessible by other Church department personnel in Seminaries and Institutes, welfare facilities, and missions.

It appears that the mobile FIR application will be available at a later date than previously stated

I cannot find the app on google play

AcheampongIK wrote:I cannot find the app on google play

Please see the post just before yours.

I am an employee and and Administrative Assistant at the Ephraim Utah Institute of Religion. Yesterday for the first time I was unable to access Facility Issue Reporting for the Ephraim Utah Institute. It let me access my home stake buildings. I have never reported a facility problem through my home stake. I need to access the Ephraim Utah Institute so I can report a problem at our Institute Building. Thank you. Julie B. Whipple

whipplejb wrote:I need to access the Ephraim Utah Institute so I can report a problem at our Institute Building.

The forum is primarily user-to-user support. You'll have to contact the Global Service Desk to check your access.

Need assistance in accessing and placing FIR requests.

See the Wiki article Facility Issue Reporting for information. It has a link to a dated (2012) Facility Issue Reporting (FIR) System User's Manual. The introduction has a table of those callings/positions with user access. The manual is a good start, but due to it's age, the information may not reflect changes that have occurred since then. It also references out of use systems and terms.

For direct access to FIR, go to https://fir.churchofjesuschrist.org/

Additionally, GHB 35.4.2 talks about Requesting Repairs, and links to a Help Center article about FIR. That article is dated 2016, so it's a full 4 years newer than the manual! That said, it likewise probably doesn't have the info you are looking for.

My best suggestion would be to contact the Ward Building Representative (GHB 35.2.9), and then try the Stake Building Representative (per GHB 35.2.4 and 35.2.5 it should be one of the High Councilors). They should be able to provide training and support to any Stake or Ward Council member trying to use FIR.

How in the world is anyone able to get into FIR to report building problems?

CDCypert48 wrote: Wed Apr 03, 2024 7:01 pm How in the world is anyone able to get into FIR to report building problems?

This is the direct link: https://fir.churchofjesuschrist.org/, however, only those with specific callings are allowed to access it. If you have building issues, I'd suggest contacting your local leaders. They can open a ticket in FIR.

good pm po paki pa check po ng kisami ng naujan unit may mga lick po
salamat po.

Electrical Malfunction in our Relief Society and Young Women Rooms. Thank You!

2mike3 wrote: Wed Feb 05, 2025 6:34 pm Electrical Malfunction in our Relief Society and Young Women Rooms. Thank You!

There is nothing anyone here on the Tech Forum can do. The Tech Forum is user-to-user discussion and collaborative self help. Facilities Issue Reporting (FIR) is done either through the FIR mobile app or the online app (fir.churchofjesuschrist.org) for those unit and stake leaders that have access. Contact a member of your bishopric or a clerk if you do not have access.