The VA just posted an RFP for a FedRamp accredited SaaS Facilities Management System. Looks like their current GoTO app is not accredited.

This is very necessary to compete n the Federal Gov't space. We are responding to an RFP and we know at least 3 of our competitors have FedRamp compliance.

We had a very successful demo on Friday for a federal opportunity that had a FedRamp and FRPP component. During the Q&A we were asked by the evaluation team about Fed Ramp accreditation. They were surprised with the number of IC customers why ARCHIBUS was not accredited. We advised the customer that we know ARCHIBUS has begun the accreditation process but were not aware as to where they are. They asked if we could find out what org was sponsoring ARCHIBUS in the accreditation process. If you review the accredited apps on the FedRamp page https://marketplace.fedramp.gov/#!/products?sort=productName you will find that FM Systems, IMMS, infor, Maximo, Tririga, ServiceNow, ESRI, and Sales Force.

https://www.nuvolo.com/industry/government/ Novolo reports that they are FedRamp authorized however they do not show up on the FedRamp.gov page. Looks like they may be leveraging ServiceNow's accreditation.

FEDRAMP requirements are becoming more and more common in the RFPs issued by the federal government. It is likely that all agencies will be following suit. We have already been precluded from bidding on several opportunities because of the FEDRAMP requirement.

This is DESPERATLY needed! More and more Federal RFPs are requiring this.

The Department of Veteran's Affairs just put out a solicitation for a facilities management solution (VA-20-00019685). The solicitation requires a FedRAMP solution, so ARCHIBUS cannot be quoted. This is the second RFP/RFQ in as many weeks that we will not be able to pursue. If ARCHIBUS does not place this at the top of their priority list, they will be pushed out of the federal market within 18 months to 2 years.

We have already lost or been disqualified from several pursuits due to this. Most recently, there was a National Archives response that ARCHIBUS was a perfect fit for. We were not able to submit a response because ARCHIBUS is not FedRAMP certified or compliant.

In the federal sector, we have been asking for this since FedRAMP was announced in 2012 and nothing has been done. If this isn't made a top priority for ARCHIBUS, the federal sector will be lost to another, lesser solution that has taken the initiative and become FedRAMP authorized.

My suggestion is to find an agency sponsor to give you the government push that you'll need to get through the process.

Bob, we are not seeing a tremendous need in county government at this point. Some trickle down into state and some large cities.

I am starting a County campaign. Will FedRamp affect my efforts? If so, This will need to be addressed by AI

I also completely agree with Dan. We lose new business due to Archibus not being FedRAMP certified and it needs to be perpetual/term first and then cloud. While we have rarely been able to cover the FedRAMP requirement by having Archibus hosted in a FedRAMP-certified data center, that is always a stretch and not good enough in the long run.

We have come across several opportunities where Archibus was the best fit in the market; however, FedRAMP was a mandatory requirement that got us disqualified before we could even bit on the RFP.

We have been asking for this for over a decade and it is essential to keeping Archibus at the forefront of solutions within the US Government.

Agree completely with Dan. There are 2 tiers that apply to Archibus here. The environments must be FedRAMP certified and the platforms then must be FedRAMP authorized. Government team is actively seeking agency sponsorship which can expedite the process in some ways.

Fred, you are correct, there may be changes that need to happen within the product to comply with issues found during the FedRamp process. From our experience, we are not aware of any specific features that need to change, though other BPs can chime in. As a first step, I would recommend starting discussions with a company that can guide Archibus through the FedRamp process as quickly as possible. The longer the product is not certified, the more business we lose.

In addition, please make sure this is not just an Archibus Cloud issue within Archibus. We need the Enterprise application certified. Most (if not all) Government implementations are perpetual onsite or hosted.

Is this a certification process first and foremost? It looks like it is. The product would undergo changes to comply with items identified during an evaluation - is that correct? If so, then would the first step to be sign up for certification. or are there items we know we need to fix before that step?

We have seen this requirement grow quickly and has become a part of every open solicitation that gets posted for response. This is a critical step in staying relevant in the Public Sector space. We receive questions from partners and customers alike almost daily on the status of our authorization. Operating in a certified environment is no longer sufficient enough to pass.

FedRAMP certification for Archibus Cloud and Private Cloud Environments. FedRAMP authorization for all Archibus platforms - Enterprise & Cloud. This is a must do for Federal government and increasingly important for State & Local government in the US. https://www.fedramp.gov/

Will this certification apply to ARCHIBUS Enterprise as well? If not, the primary push should be to get ARCHIBUS Enterprise FedRamp compliant. There are many Civilian US Government agencies that have ARCHIBUS installed onsite, and most US Government ARCHIBUS installations could not migrate to ARCHIBUS Cloud due to the level of customization applied to the system.