S160005_Questions_and_Answers.docx

QUESTIONS AND ANSWERS

AUGUST 5, 2016

1. Is there a solution in place currently? If so, what is the current solution or is all data on spreadsheets only?

There is not a solution currently in place. Current data is available in Excel format.

2. How many named users would be utilizing the system? (Pricing is based on a named user. The solicitation said 12 then up to 24.

There would be an initial number of 12. Please provide pricing for the initial 12 and pricing for additional users if necessary.

3. In regard to users, can you provide the number by type? How many Admin, Power Users, and Requestors?

We plan to have a total of 3 administrative users, with the remainder being base users. (Section 3.2 (i) (1) User Roles addresses “base” and “administrative” roles)

4. Is mobile access desired?

No.

5. If mobile access is desired is there any need for offline (not connected) capabilities?

Mobile access is not desired.

6. Based on the CLINs, there is not line for travel other than related to training. If the vendor expects travel other than training how should this be accounted for?

The government does not expect there to be any travel required outside of training.

7. Is it expected to put the labor effort for the initial stand up and tailoring of the system in CLIN 005?

Please include initial standup and tailoring of the system in the Initial Purchase. See updated Schedule of Items.

8. Are there any parameters for the hosting provider? (FEDRAMP certified, up time, etc.?)

Hosting will be provided by the government. Please see revised schedule of items and Delivery Requirements.

9. How many initial asset records are to be uploaded to the new system?

It is unknown at this time how many initial asset records will be required to be uploaded to the system. Please see updated Schedule of Items for pricing regarding upload of data.

10. Being that this solicitation not only requires the vendor to describe the solution and also the company providing it and the services, can the page limitation be relaxed to be greater than 15?

Please see revised requirements in Section 4.4.

11. Should Section 3 CFR requirements tables be extracted from the RFP or should the vendor respond within the RFP document itself?

The tables can be extracted from the RFP or responded to within the RFP document.

12. Please confirm that pricing is firm fixed price?

Yes, this is a Firm Fixed Price acquisition.

13. How many environments are required? (Development, Test, Training, Production, etc.?)

As this is a COTS program, the USFS only requires a production environment.

14. Please confirm that there are NO integrations with any systems expected?

There are no integrations with any systems expected.

15. Service-wide aircraft and logistics information management system to support U.S. Forest Service aircraft at multiple associated facilities. How many facilities will the CMMS support? (this goes into our pricing model)

Please see revised requirements in Section 3.2 (i).

16. Compatibility: CMMS will be compatible with win2008 server or win 2012 server. Desktop client should be compatible with win7 and next business version (win10) - Any concerns with a web-based Software as a Service offering? (we host, you don’t have to)

There is not a hosting requirement. Please see revised schedule of items and Delivery Requirements.

17. Does Forest Service already have a COTS product in mind and just need implementation/support? Or does Forest Service need to be guided through the selection process based on specific business requirements?

The USFS does not have a product in mind and does not need a selection process.

18. If a selection process is needed, then what are Forest Service’s specific requirements?

See question 17.

19. What is the size of the Forest Service fleet of aircraft? How many of what types?

Please see revised requirements in Section 3.2 (i).

20. What is the state of the legacy data system currently in use?

See question 1.

21. What data cleaning does Forest Service anticipate before the current data can be loaded into a COTS?

The USFS plans to give the vendor clean and accurate data and anticipates little to no corrupt data.

22. What is the regulatory structure under which Forest Service operates its fleet?

Title 14 of the Code of Federal Regulations

23. Regarding Page 22, SECTION 3, CONTRACT DOCUMENTS, EXHIBITS, OR ATTACHMENTS; (i) MISCELLANEOUS INFORMATION, Item (1) “There will be an initial number of 12 users, with potential growth for 24 or more.”

Question: Could the USFS provide guidance with an estimate or range on the “…or more.” part of this sentence. How much more could it be? This affects how we initially size the system and the related infrastructure. It can affect how we will price it.

We are unable to predict any user numbers past 24 users. If the USFS aircraft fleet grows or shrinks, the number of required users could grow or shrink.

24. Also, can you provide guidance on the number of locations? Perhaps an estimate or range?

See question 15.

25. Will there be a need for disconnected functionality when operating in austere areas and the ability to re-sync upon return to a primary user location?

Yes.

26. Delivery of proposal packet – It is my assumption that once I pull the packet all together in PDF format, it might be too large to transfer via email. If that is the case, is it ok to provide a link to “dropbox” or other file transfer platforms that allows the sharing of larger files as a download?

Please see updated information in Section 4.4.

27. In section 3.2, Technical Requirements, Part A, Maintenance Management Functions, part 4, component maintenance repair and overhaul (MR&O), it mentions “tracking Traveler Forms” – I am hoping to get some additional information on the requirements behind traveler forms. Please confirm my assumption that this requirement is related to the aircraft travel logs and would be provided by pilots to be associated with the aircraft asset. Is it a scanned document or is the requirement an interface to collect data from pilots at the time of flight preparation / closing?

A “traveler form” is a document that accompanies an aircraft component from one location or shop to another during maintenance, repair and overhaul. For example: an aircraft wheel and tire assembly has a traveler form generated upon its induction for repair or overhaul. This form accompanies the assembly as it is disassembled, cleaned and inspected, even though these three individual processes may take place in different locations. This form, and the aircraft component, including the items that make up the component assembly, may need to be tracked. The tracking may include both physical location and condition, with condition possibly being expressed in hours in service, landings, calendar age etc.