Questions_for_DHQCAP15P60007.docx

1. Will DISA only consider COTS software products that currently meet 100% of the stated requirements "out-of-the-box" or will considerations also be given to COTS products that require some enhancements to meet 100% of the requirements?

DISA Response: COTS products that do not meet 100% of the requirements will be considered technically unacceptable to DISA and not make the competitive range for further evaluation.

2. With respect to "Architecture/CMDB" Item 4 in the PWS, please confirm exactly what is meant by "configurable printing options".

DISA Response: The COTS tool should enable printing to Word, PDF, Excel, or other formats based on user preferences.

3. With respect to "Architecture/CMDB" Item 6 in the PWS, please provide examples of many-to-many and many-to-one CIs.

DISA Response: A configurable item could have more than one parent and each parent could have multiple children (many-to-many). A configurable item could have more than one parent, but a parent could have only one child (many-to-one). The COTS tool should be flexibility enough to support all of these types of CI relationships based on DISA’s requirements.

4. With respect to "Architecture/CMDB" Item 10 in the PWS, please confirm exactly what is meant by "configurable user screens" and provide examples.

DISA Response: DISA requires the layout of user screens based on their requirements without custom coding of that user screen. Many COTS tools provide the capability for user defined screens for maximum flexibility with no customizations.

5. With respect to "Architecture/CMDB" Items 16, 17, and 19 in the PWS, please clarify what types of interfaces to these systems are acceptable in each case? Would data import/export between the COTS product and these systems be an acceptable solution?

DISA Response: DISA prefers a COTS tool which support web service interface based on standard protocols such as SOAP, and application APIs for integrating with other products. The use of JAVA is not acceptable.

6. With respect to "Architecture/CMDB" Item 28 in the PWS, what types of designated customers must be supported? Are these external to DISA and would they have access only to WO submission functions?

DISA Response: DISA would not have external customers submitting Work Orders. Internal DISA personnel would be the only ones submitting Work Orders.

7. With respect to "Architecture/CMDB" Item 40 in the PWS, please confirm exactly what is meant by "...reports which combine a graphic view...", in particular what is expected in terms of "a graphic view". Also please provide an example.

DISA Response: DISA requires a tool that can produce graphical views of attributes for specific CIs. For example, a screen showing a chart of CIs with the highest number of maintenance work order associated with them for managerial attention.

8. With respect to "Architecture/CMDB" Item 40 in the PWS, please confirm exactly what is meant by "graphic reports". Also please provide an example.

DISA Response: DISA requires a tool that can produce graphical reports of attributes for specific CIs. For example, a report showing a chart of CIs with the highest number of maintenance work order associated with them for managerial attention.

9. What methods/options are available to the vendor and the COTS product for "interfacing with the DISA enterprise ITSM tool suite"?

DISA Response: ITSM is deploying standard APIs (aka Common Connection Interface) that can be used to interface to any application that supports APIs.

10. Regarding section 3.d. of DISA’s RFP, if a U.S. company staffed entirely by cleared U.S. citizens intends to offer a vendor’s COTS software as part of its solution to meet DISA’s CMMS requirements and the vendor is a from a non-U.S. allied nation, would a non-U.S. vendor representative be allowed in the lab?

DISA Response: All personnel performing on this contract will be U.S. citizens according to section 12.2 of the PWS. Also, Please see FAR 25.4, we can NOT purchase any software from a country that is NOT included in the approved trade agreements.

11. Regarding the Functional Test Plan, is it the Government’s intent or desire that the offeror seek information assurance approval(s) prior to testing? If so, please provide a detailed description of what approvals should be sought in advance of testing.

DISA Response: For typical implementations and VOE provisioning by DISA, there's usually minimal OS STIGing that occurs by site SA's before IOE (Initial Operating Environment) is achieved and the OE's are turned over to the application manager to load and configure their software. The meat of STIG compliance, mitigation, and documentation is performed post application configuration/testing. So, DISA will load the OS and application and then tighten to STIG tolerances and determine any variance afterwards to be documented. The mandatory publications listed herein and other guidance that can be obtained from http://iase.disa.mil will be critical in the contractor's successful implementation of the CMMS tool. The following publications are anticipated to be the absolute minimum IA documents necessary for the contractor to maintain certification and accreditation; other documents are possible dependent on the system(s) and components that are selected for implementation.

· DoDI 8510.01, Risk Management Framework (RMF) for DoD IT RMF

· Web Server STIG

· Database STIG

12. RFP section 3.g.(1)(b) requests that offerors include detailed information regarding required resources, including travel. RFP section 3.g.(1)(c) provides additional requirements for detailed information related to travel. This guidance appears inconsistent with the Government’s direction in RFP section 3.g.(1)(d) which provides plug numbers for Travel ODCs and directs that offerors load these “EXACT amounts.” We request the Government clarify what detailed information should be included for Travel ODCs.

DISA Response: If the offeror has exact amounts in mind, these can be included in your response; otherwise the out-year travel default amounts can be used for the out-year travel costs. Implementation in the base year must include both labor and travel for the offeror to stand-up their solution in our environment.

13. Regarding RFP section 3.g.(1)(b) and PWS sections 6 and 9, is it accurate to interpret the Government’s intent that the offeror’s employees only visit DISA facilities as needed for installation and maintenance related activities? Specifically, is it the Government’s intent and desire that offerors propose to station contractor staff at DISA facilities on a full-time basis during the period of performance?

DISA Response: Offeror staff will be available during the functional testing and the base year implementation on an as needed basis. Travel in out-years can also be specified on an as needed basis. There will be an implementation, training and turnover to Government personnel for this project. No offeror should be required to be at a DISA facility on a full-time basis during the base or option years.

14. RFP section 3.g.(1)(d) provides plug numbers for Travel ODCs. The base year figure is blank. Should offerors interpret this blank to indicate that the Government desires that they load $0.00 (zero dollars) for Travel ODCs in the base year?

DISA Response: The base year is blank for special travel since the offeror should include all labor and travel costs with the implementation fees to be incurred during the base year of the contract.

15. RFP states contractor will submit IT-1 SSBI through DSS to OPM and JPAS must reflect Open investigation. DoD contractors are not authorized to submit investigations to OPM through DSS for IT level investigations. Unless the clearance eligibility is required for access to classified information. Will DISA security process investigation request for IT level access?

DISA Response: DISA will submit all investigation requirements for public trust positions. Since this is unclassified contract, all computer access requests will be sent to the COR who will send a request to DISA MP62 requesting an eQIP be opened for a public trust position.

16. We are in the process of reviewing the RFP that was put out to bid and in order for us to best determine if we should respond we wanted to ask if your team is open to evaluating web-based systems. By this we mean a system that is backed up and maintained on our servers rather than a one-time purchase and install. It appears that the RFP is tailored to a preference for standalone systems so we wanted to make sure we would be a good fit.

DISA Response: We would like to purchase a system to be installed and run in our DECCs with capital set-aside for this project. A lease type scenario would require different funding (different color of money), which we do not have set-aside for this project. Hopefully, you can bid a system that we can purchase and run in our DECCs for security and financial reasons.

17. Please define the final “End User” count for the CMMS solution in total for DISA and projected by Data Center.

DISA Response: DISA estimates between 25 – 50 end users for the CMMS tool.

18. The selection methodology described in paragraph 3, Evaluation Factors, on page 2 of the RFP describes the intent of the government to select the lowest price bidder to conduct a proof of concept, which will ultimately determine their true technical capability. However, the requested solution is quite complex and spans locations CONUS as well as OCONUS. It seems likely that a bidder that has never implemented and deployed such a solution within the DoD or the Federal government could underestimate the complexity of this project, underbid the price and ultimately not be able to deliver the desired solution. As described in the solicitation, the LPTA evaluation may not allow sufficient discretion on the part of the selection committee to properly assess the capabilities of the bidders per price realism and demonstrated successful experience at that price. Therefore DISA faces a significant risk that they will not gain any benefits from this solution if the selection is solely based on price. Would the government consider adjusting the evaluation factors of this solicitation to include past performance references of the offerors, to increase the likelihood that the LPTA selection is made of a proven solution?

DISA Response: At this time DISA will not be adjusting the evaluation factors.

19. We are in the process of reviewing the RFP that was put out to bid and in order for us to best determine if we should respond, we wanted to ask if your team is open to evaluating web-based systems? By this we mean a system that is backed up and maintained on our servers rather than a one-time purchase and install. It appears that the RFP is tailored to a preference for standalone systems so we wanted to make sure we would be a good fit.

DISA Response: We would like to purchase a system to be installed and run in our DECCs with capital set-aside for this project. A lease type scenario would require different funding (different color of money), which we do not have set-aside for this project. Hopefully, you can bid a system that we can purchase and run in our DECCs for security and financial reasons.

20. I would like to request an extension of two weeks on the submission of this proposal. In order to have a hard copy proposal delivered to the set location on time, it would have to be shipped no later than next Friday. I'm afraid this would not give us time to prepare a proper response to the solicitation. I do feel like our application would be a viable option for DISA based on my initial review of the documentation. I thank you for your consideration of extending the Due Date for the proposals to be April 5, 2016.

DISA Response: Per the RFP, proposals are due no later than March 30, 2016 at 2:00pm (EST) and should be submitted to the contracting officer at DITCO via the following email address: cindy.m.goshorn.civ@mail.mil . You are not required to deliver a hard copy proposal to the set location. This should provide you additional time with electronic submission.

21. Can you provide the expected number of users for the solution based on the license type descriptions below. The Software solution we are proposing supports the following different license type:

· Primary user license - named full time user

· Concurrent user licenses - a license that is shared between multiple part time users, users that are only on the system for an hour to two day.

· Requestor User - a user that is only able to submit a work request, e.g. my office is too hot.

DISA Response: We would have the 25-50 Primary Users only. There will be no concurrent and no requestor users.

22. To be able to provide services pricing to implement/configure the interfaces from the new system to the above legacy systems listed in the PWS, additional information will need to be known such as the number of data elements that need to be passed between the new and existing systems on a per "flow" basis? Which system will be the system of record for the data the legacy system or the new system? How many "flows" will each interface require and in which direction. Just saying "bi-directional" is not enough, we need to know how many flows will be required in each direction to or from the new system to the legacy systems for each of the 4 interfaces or will the legacy system need to transfer data to the new systems?

DISA Response: New application - There will need to be a one-time data import of 10,000 items with up to 5 -6 records associated with each of these items from MP2 and the Maximo/Access database into the new application. The new application will be the system of record.

ITSM - ITSM will be the system of record for tickets and work orders will be created into the new application manually from ITSM ticket data as required.

DCIM – There may be a future need to import data from the new application into the DCIM application on a weekly or monthly basis.

BAS - Alarm data from BAS would be used to create work orders within the new application. These alarms could occur on an infrequent daily basis within BAS.

BUILDER SMS - There will be a requirement to import data from BUILDER SMS into the new application, this import will be on an ongoing basis as facility information is updated in Builder SMS. This data will be Facility Assessment, Cost categories, Project Cost and Work order cost and status. Cost/work order data would need to be exported from the new application into BUILDER on an ongoing basis (weekly/monthly) for budgetary planning purposes and facility assessment condition updates. BUILDER will remain as the repository for facility sustainment requirements on an on-going basis at DISA.

SharePoint - Reporting data would need to be exported from the new application into SharePoint on a monthly basis for reporting/dashboard purposes.

23. Test Plan, “self-contained” solution– Will the offeror have access to an internet connection for testing and setup.

DISA Response: There is no internet access in the DISA test facility/pre-production lab in Montgomery. For Proof-of-Concept (POC) testing, the Offeror shall deliver two sets of their complete solution to include: Software on Digital Versatile Disc (DVD) media in International Standards Organization (ISO) format ready to upload to the Government’s VMware Virtual Operating Environment (VOE) environment. Two sets are required in case one DVD is damaged or unusable once it arrives at the DISA test facility in Montgomery. “Complete solution” means that whatever architecture (self-contained) the Offeror is submitting for testing (software) at the functional stage of this effort must be provided for testing. It also means that each Offeror MUST have all installation documentation at the site location ready for testing. The Offeror shall indicate which server requires which ISO image. The Offeror will also include all installation documentation for testing prior to the start of testing at the DISA test facility.

24. Can the CMMS solution request pass-through the firewall to synchronize data through an internet connection?

DISA Response: During the POC testing, there is no access to the internet in the Montgomery test facility/Pre-Production lab. For a production implementation of CMMS, there will have to be a firewall exemption and the access will have to be approved and document in the System Security Plan (SSP), and security will have to approve this.

25. Does the government see technical acceptable total solution to include a Software-as-a-Service application in FISMA Level 3 cloud service provider?

DISA Response: We would like to purchase a system to be installed and run in our DECCs with capital set-aside for this project. A lease type scenario would require different funding (different color of money), which we do not have set-aside for this project. Hopefully, you can bid a system that we can purchase and run in our DECCs for security and financial reasons.

26. Any of the CMMS data provided by the government servers considered higher than FISMA Impact Level 3 (Moderate) data storage?

DISA Response: There will need to be a one-time data import of 10,000 items with up to 5 -6 records associated with each of these items from MP2 and the Maximo/Access database into the new application. This would just require a moderate amount of storage.

27. Paragraph 5 Scope - Is the requirement for unlimited users specifically for the ability for anyone in the department to submit a Work Request? If so, how many users are expected that are NOT solely Requester Type Users?

DISA Response: No, there is no requirement for unlimited users specifically with the ability to submit a Work Request. Our primary users would be doing this function. We would have the 25-50 Primary Users only. There will be no concurrent and no requestor users.

28. In 6.1 Software, Item 3 - States that an UNLIMITED number of user defined fields be allowed. What is the practical expected maximum number of user defined fields needed?

DISA Response: By “unlimited” DISA means that we would not be restricted to some set number of fields that could be added to the new CMMS without additional costs and/or custom coding required. DISA would require the typical asset fields such as unique equipment identification number, drawing asset number, description, system, site, building number, building name, floor, room number, make, model, serial number, capacity (kW, tons), voltage, number of phases, amps, fuel type, panel #/controller #, use in FPT number(s), responsible, drawing number/spec section, scheduled PM hours, year installed, base cost, year of base, manufacturer life cycle, programmed replacement year, replacement year cost, condition, master format code, uniformat code, RS means number, RS means cost, RS means year, remarks, bar Code, UID#s, Parent UID#s, Child UID#s, Warranty Period data for purposes of replacing these assets when they reach their service life, with data such as Mfr. name, model #, installation date, installation cost, condition assessment (done every two years), replacement date and cost. Additional fields such as history of work orders regarding equipment assets, condition assessment data of assets, and lifecycle replacement data for all assets are also required to be stored in the new CMMS.

29. In 6.1 Software, Item 6 - Explain a Use Case scenario where a Configurable Item (Asset) can have multiple parents and multiple children (i.e. many-to-many hierarchical relationship).

DISA Response: A configurable item could have more than one parent and each parent could have multiple children (many-to-many). A configurable item could have more than one parent, but a parent could have only one child (many-to-one). The COTS tool should be flexibility enough to support all of these types of CI relationships based on DISA’s requirements.

30. Will the submission deadline be extended?

DISA Response: Yes the deadline will be extended until 30th March, 2017 at 2:00pm EST.

31. Are there any other types of Oracle, SAP and proprietary connections required to integrate with the CMMS solution?

DISA Response: No, see response to question #22 for further interface details.

32. Will the Tier 2/3 support be part of the DECC call center infrastructure to escalate the CMMS trouble tickets?

DISA Response: No, the Severity 1 – 4 items identified in the PWS have nothing to do with our internal DECC call center support. This is the process that should be used once an issue gets identified and escalated over to the offeror from our CMMS application administrator. There will be a very limited number of DISA personnel funneling issues over to the offeror via this process.

33. RFP Letter Section 3, (1) Price Factor (b) Requirements indicated the price proposal should include detailed information. Can a price document in MS Word be provided to supplement the Price Proposal in MS Excel?

DISA Response: No, please embed your text into the MS Excel document as needed.

34. RFP Letter Section 4 - A payment plan is requested. Could this be provided with explanation in a price document in MS Word?

DISA Response: No, please embed your text into the MS Excel document as needed.

35. PWS, Price Spreadsheet Section 6.6 & 6.7 -Optional Tasks 6 & 7 were added to the final PWS. Should these be added to the spreadsheet as CLINs 0006 & 0007?

DISA Response: If additional CLINs are needed, please add them as CLIN 0006, 0007, etc. - as instructed on the Attachment 4, CLIN pricing worksheet from the RFP.

36. RFP Letter Section 10 -In order to incorporate the answers to the questions and provide the lowest pricing possible, we request a one week extension, with a new due date of 28 March at 2:00PM EST.

DISA Response: Yes the deadline will be extended until 30th March, 2017 at 2:00pm EST.

37. PWS Section 6.1 -Will a mobile solution using hand-held devices be required for use of bar codes with the facilities?

DISA Response: Yes, we require the system to be able to accept data inputs from a bar code reading device. The bar code readers would not be mobile devices that transmit an RF signal, as these are not allowed in many areas of our facilities, but a hand held reader that scans and saves the data to the device or a laptop connected to the reader. This information would then be imported into the CMMS.

38. PWS Section 6.1 -Will standard office laser printers by used or will specialized printers used?

DISA Response: Yes, standard office laser printers will be used.

39. PWS Section 6.3 -Will the production system be in a central location or deployed to each of the sites?

DISA Response: The production system will be deployed to a central management site and a potential fail-over site. Users could be located at the various CONUS/OCONUS sites listed in section 9 of the PWS.

40. PWS Section 6.4.1 -Training numbers are 60+ although previous question response indicated user base of 25 – 50. Can the Government explain the difference in numbers?

DISA Response: The training numbers were estimated on the high side for number of attendees. Also, the 25 – 50 primary users could attend both the end user training and the reporting training since some of them could perform both functions within CMMS.

41. PWS Section 6.1 / Reports -Do we interpret requirement 40 in Reporting and Analysis correctly that the system will provide the ability to combine a graphic view along with metadata (attributes) from the solution repository?

DISA Response: DISA requires a tool that can produce graphical views of attributes for specific CIs. For example, a screen showing a chart of CIs with the highest number of maintenance work order associated with them for managerial attention.

42. Do we understand correctly that there is no requirement to deliver a pre-defined number of reports?

DISA Response: There are typically standard/canned reports that are included with all software applications please provide that information in your response. There is also requirements for specific reports that are listed in the reporting and analytics section of the PWS #35 – 44.

43. PWS Section 6.2.1 - Is our understanding of the Toll Free support line correct is that “at no cost” is for the phone call and not resources providing the call support?

DISA Response: The internet and toll-free based support, the call as well as the resources providing the call support will be at no cost to DISA. These costs should be covered in the maintenance costs that DISA pays to the offeror on an annual and on-going basis of typically 20% of license costs (industry standard).

44. Is DISA just looking to confirm the software vendors have the ability to interface to the ITSM, DCIM, BAS, SharePoint/DEPS and the Army CORP of Engineers Builder product, or is the intention to actually have the CMMS vendors provide this ability in their Fixed Price Proposals? There is not much information in which to understand the requirements of these interfaces. Is the intention to have these properly scoped out and quoted after the selection of the vendor? DISA Response: See response to questions #22 and #5 for further interface details. These interfaces will be part of the implementation costs that the offeror should include in their bid to DISA.

45. Functional Test Plan: --In the Functional test plan, TESTING DELIVERABLES - Testing deliverables from the offeror include the job aide and detailed use cases. We have three questions:

(1) How does offeror ensure the detailed use cases provided for testing meet DISA use case requirements?

DISA Response: The Offeror will provide a test job aid to the Government to assist in validation of the test plan requirements during the functional/end-to-end testing phase. That way, the offeror specifies how the Government users test their system to get the desired result since the Government personnel are not yet trained or familiar with the offeror solution.

(2) Does DISA have use cases documented?

DISA Response: DISA does not have use cases documented. The functional test plan includes items to be tested in section 2.4.

(3) Please describe the job aid requirement.

DISA Response: The job aid is used to test out the items to be tested in the functional test plan. It would assist the Government in testing each item – step-by-step directions to achieve the desired result in the offeror’s application.

46. Performance Work Statement (PWS): --The PWS states “Maintenance does not become effective until the Government approves 100% solution.” Can you please define what 100% approval requires? For example does this mean JITC must certify?

DISA Response: Deliverable 20 is an implementation sign-off letter which means that all the deliverables are completed and the solution is ready to move to operations support (i.e. maintenance). The contractor will work with the Government to ensure all STIG findings are mitigated and application reviews are successfully conducted. Any outstanding items shall be mitigated by the contractor or shall have a POA&M document submitted to the Information Assurance team to ensure compliance with the certification and accreditation process.

Once the solution is installed, configured, and in production by the contractor, the contractor shall load each site's data immediately after data is collected. As soon as the site data is loaded and validated, the site will assume responsibility for data and will update as changes are made. The contractor will have responsibility for the initial data load and validation with each respective site.

47. --The PWS states “This solution should include unlimited (non-restrictive) user licensing to support the enterprise.”

(1) Can you please define enterprise?

DISA Response: The enterprise solution will include the CMMS application available to the 25-50 primary users who are located across the DISA enterprise (users could be located at the various CONUS/OCONUS sites listed in section 9 of the PWS). The enterprise data would include the 10,000 items with up to 5 -6 records associated with each of these items from MP2 and the Maximo/Access database in the new CMMS application.

(2) How many users?

DISA Response: 25-50 primary users.

(3) Are mission partners included and will mission partners have access to this system?

DISA Response: Mission partners are not included; this is an internal DISA system. The mission partners would not have access to this system.

48. --The PWS states “The CMMS tool is required to communicate with and integrate equipment and change control management information with other Government systems including, but not necessarily limited to, the DISA enterprise building automation system (BAS), the DISA enterprise information technology service management (ITSM) tool suite, the Data Center Information Management (DCIM) solution and the SharePoint/DoD Enterprise Portal Service (DEPS).”

(1) Can you please define integrate? For example, is the requirement to share data between systems, initiate workflow processes, etc…?

DISA Response: See response to questions #22 and #5 for further interface details. These interfaces will be part of the implementation costs that the offeror should include in their bid to DISA.

(2) What existing software solution is used to support the following systems, DISA enterprise building automation system (BAS) and Data Center Information Management (DCIM)?

DISA Response: THE BAS-G solution is Ionics Genesis 64. The DCIM solution has not been selected yet; this project is still in the acquisition phase.

49. In the PWS Performance Requirements section 6.1 Software #13 states - Architecture includes software for a centralized database using one of the DISA standard enterprise database servers for the solution repository. Is there a preferred database solution? Oracle, MySQL, IBM DB2, etc…(1) Is there a preferred database solution? Oracle, MySQL, IBM DB2, etc… DISA Response: DISA prefers a database that we have experience with, which would be SQL, MySQL or Oracle as the best options.

50. On page 4 of the RFP, you list fixed amounts for Travel ODCs for Option Year 1 and Option Year 2 but there is no dollar amount for the Base Year. Can you please clarify how we are to handle Travel costs for the base year?

DISA Response: See responses to questions #12, #13 and #14 for further details.

51. Given the amount of detail required for this response, we are concerned that we will not be able to provide a complete, detailed response by March 21. Will you consider a 1-week extension of the due date?

DISA Response: Yes, and solicitation will be extended until 30th March, 2016 at 2:00 pm EST.

52. Has the government decided where the "proof of concept" phase will be done locally to DISA HQ at Ft. Meade, MD or elsewhere?

DISA Response: The POC will be conducted in DISA pre-production lab/test facility in Montgomery, AL.

53. Would implementation and testing documentation for RMF packaged or ATO?

DISA Response: We will require an RFM package for ATO. Please see section 6.3.4 subtask 4 of the PWS for full details.

54. RFP Page 2, #3 - What connectivity will be available in the testing lab?

DISA Response: There is no internet connectivity in the pre-production lab/test facility. There is also no connection to production systems since this is a pre-production area only.

55. RFP Page 2, #3- What pricing will be evaluated for LPTA? As there are option periods, surge pricing, and 6 month extension are not guaranteed, will they be excluded from the price evaluation?

DISA Response: Please include all pricing as specified on the Attachment 4, CLIN pricing worksheet from the RFP. We must consider all of it in the pricing evaluation portion of this acquisition.

56. RFP Page 2, #3 -Will any contractors be used in the evaluation of the solutions, to include the setup of the lab?

DISA Response: We do have contractors in the pre-production lab/test facility; however, contractors can NOT provide evaluation input to the evaluation team. The evaluation team will be all civilian personnel.

57. PWS Page 2, #5 Scope -The government requires an "unlimited (non-restrictive)" user licensing. Can the government please provide the number of users, facilities, and assets under management to be enable the calculation of this license? What is the expected change in these numbers over the life of the contract?

DISA Response: The enterprise solution will include the CMMS application available to the 25-50 primary users who are located across the DISA enterprise (users could be located at the various CONUS/OCONUS sites listed in section 9 of the PWS). The enterprise data would include the 10,000 items with up to 5 -6 records associated with each of these items from MP2 and the Maximo/Access database in the new CMMS application. The expected volume of changes over the life of the contract for the items will be 5 -6 new records each year. Asset replacement within this system will be fairly infrequent due to the nature of the assets. The lifecycle on these items could be quite lengthy.

58. PWS Page 5, Reporting & Analytics, #44 -Can you please provide your supported interfaces for allowing the insertion or display of reports and graphs on the SharePoint/DEPS dashboard?

DISA Response: Exporting data would be in one of the following formats listed in required #20 of the PWS: Supports the capability to import and export data from the following file formats: .xml, .html, .htm, .pdf, .xlsx, .doc, .docx, Office 2010 - current releases.

59. PWS Page 6, Para 1 -Can you please list and provide full details on the "targeted DoD architectures" you require interoperability with? Can you please provide full DODAF meta-models, viewpoints, and models for these targeted architectures to ensure interoperability?

DISA Response: Please see response to question #22 and #5 for further interface details.

60. PWS Page 6, Para 1 -How is the government willing to guarantee prompt access to resources, data, and personnel to ensure a timely approval of the solution?

DISA Response: Unfortunately, the Government can’t guarantee this. Non-consecutive days of on-site installation support will be required for pre-production installation in the test environment.

61. Testing Page 3, Para 2.4 -What third party mapping services are being used to integrate with MP2.

DISA Response: There are no third party mapping services, DISA utilizes a maintenance and operations service contract for MP2.

62. Testing Page 3, Para 2.4 - What third party mapping services are being used to integrate with MP2.

DISA Response: There are no third party mapping services, DISA utilizes a maintenance and operations service contract for MP2.

63. In the RFP, on Pg 2, #3, what is the recourse of the offeror to refute any technical "unacceptable" ratings provided by the government during the POC?

DISA Response: There is a process where the Government documents Evaluation Notices (ENs) for any unacceptable responses/ratings and the offeror will respond back to those ENs.

64. In the PWS, on Pg 2, #5 Scope, 2nd Para., the government requests "This project will use DISA-furnished and administered infrastructure resources (computing platforms including all required hardware, connectivity components, operating system, and Enterprise Systems Management (ESM) utilities for development, test, and production (e.g., operating environment)." This is in direct contrast recent Government / DoD Initiatives and Memorandums. Is DISA not requiring a cloud solution for this system?

DISA Response: We would like to purchase a system to be installed and run in our DECCs with our equipment. DISA is not requiring a cloud solution for this.

65. In the PWS, on Pg 7, Table, the table states "Managed Software", but the government is not asking for managed software - they are asking for "Operations Support" at a fixed cost. Can the government please define what they means by "Managed Software" and "Operations Support" as these conflict to standard usage.

DISA Response: Operations support includes all the items listed in 6.2 Task 2 and 6.4 Task 4 in the PWS. The contractor shall provide software support for all software under the contract for the option years. Software support consists of software support, updates, revisions, error detection and correction, and rights to new releases and/or versions. These costs should be covered in the maintenance costs that DISA pays to the offeror on an annual and on-going basis of typically 20% of license costs (industry standard).

66. In the PWS, on Pg 2, #5 Scope, can the government provide the scope of facilities in and for which the CMMS solutions will be used? Is the solution limited to the DISA datacenters? How are the facilities demarked in buildings that all provide other, non-datacenter functions? Please help industry understand the extent of the scope to enable us to limit licenses only to what is required.

DISA Response: The scope will include DISA datacenters as well as assets from the Ft. Meade location. The enterprise data would include the 10,000 items with up to 5 -6 records associated with each of these items from MP2 and the Maximo/Access database in the new CMMS application. The expected volume of changes over the life of the contract for the items will be 5 -6 new records each year. Asset replacement within this system will be fairly infrequent due to the nature of the assets. The lifecycle on these items could be quite lengthy.

67. In the PWS, on Pg 2, #5 Scope, can the government please provide the underlying software tools, versions, interfaces, and standards supported by the DISA enterprise building automation system (BAS), the DISA enterprise information technology service management (ITSM) tool suite, the Data Center Information Management (DCIM) solution and the SharePoint/DoD Enterprise Portal Service (DEPS)?

DISA Response: Please see response to question #22 and #5 for further interface details.

68. In the PWS, on Pg 2, #5 Scope, can the government confirm the interfaces, ports, and protocols available in the existing DISA enterprise building automation system (BAS), the DISA enterprise information technology service management (ITSM) tool suite, the Data Center Information Management (DCIM) solution and the SharePoint/DoD Enterprise Portal Service (DEPS) systems are authorized for use in accordance with current DIACAP / RMF accreditation?

DISA Response: DISA Response: Please see response to question #22 and #5 for further interface details. The offeror will need to provide ports and protocols information in a solution document which are pending security approval.

69. In the PWS, on Pg 2, #5 Scope, 2nd Para., the government asks for a a site migration and implementation plan that addresses data collection, procedural and reporting requirements for inclusion in CMMS, application training, and site operational transition support" - this is contrary to the first sentence in the paragraph where the government asks for commercial off the shelf (COTS) software product including software licenses, implementation, data collection and/or data migration". Can the government confirm that it would like a tailored / custom implementation, data collection, and data migration plan to support transition?

DISA Response: The COTS tool is separate from the data collection, migration, and implementation and training efforts. We aim to minimize any customizations to the COTS tool itself. We would like a tool that has the ability to customize data fields and reports built-into the tool itself.

70. In the PWS, on Pg 2, #5 Scope, 2nd Para., can the government please provide the timelines for "information assurance (IA) and Security Technical Implementation Guidance (STIG) compliance" and "government security guidelines and schedules"?

DISA Response: That depends upon how STIG compliant your tool is. It must be STIG compliant prior to being put into production.

71. In the PWS, on Pg 2, #5 Scope, 2nd Para., can the government indicate the level of ongoing support they require for the tools (i.e. 24x7x365, 24x7-MF, 8x5-MF).

DISA Response: The level of support is specified in the Software Errors table of the PWS, which is dependent upon the severity of the software error. These costs should be covered in the maintenance costs that DISA pays to the offeror on an annual and on-going basis of typically 20% of license costs (industry standard).

72. In the RFP, on Pg 2, #3, of the RFP it states the government will be doing a single technical evaluation up to 6 weeks. How many single vendor iterations will the government go through before re-issuing the RFP if the first vendor fails?

DISA Response: The Lowest Price vendor will get a total of 6 weeks of POC testing. Any failures would be documented via the Evaluation Notice (EN) process which get sent to the offeror and they respond back to the EN in writing. If the Lowest Price vendor receives an unacceptable technical rating, the next lowest price vendor will proceed with POC testing.

73. In the RFP, on Pg 2, #3, can the government confirm test data will be available as part of the POC evaluation? Is the Offeror expected to collect the data? Will the government provide the current data model?

DISA Response: The government will provide each offeror with the exact same set of test data to ensure fairness and consistency across the POC testing process.

74. In the PWS, on Pg 2, #5 Scope, 2nd Para., can the government please provide the timelines for "information assurance (IA) and Security Technical Implementation Guidance (STIG) compliance" and "government security guidelines and schedules"?

DISA Response: That depends upon how STIG compliant your tool is. It must be STIG compliant prior to being put into production.

75. In the PWS, on Pg 2, #5 Scope, 2nd Para., can the government indicate the level of ongoing support they require for the tools (i.e. 24x7x365, 24x7-MF, 8x5-MF).

DISA Response: The level of support is specified in the Software Errors table of the PWS, which is dependent upon the severity of the software error. These costs should be covered in the maintenance costs that DISA pays to the offeror on an annual and on-going basis of typically 20% of license costs (industry standard).

76. In the PWS, on Page 2, #5 Scope, 2nd Para., is the government willing to take responsibility for the result of any patches that haven't been tested and approved by the vendor?

DISA Response: Any application patches come from the offeror and are fully tested and approved by the offeror. The contractor shall provide software support for all software under the contract for the option years as part of the maintenance costs paid for on an on-going and annual basis by the Government. Software support consists of software support, updates, revisions, error detection and correction, and rights to new releases and/or versions.

77. In the PWS, on Pg 3, Integrations/Interface #19, can the government confirm what are the supported US Army Corp of Engineers Build product interfaces?

DISA Response: See response to #22 (BUILDER section) for interface details.

78. Our questions for the CMMS RFP are related to the overall solution and the backup requirements (Subtask 6, Stage 6):

(1) Is the government looking for a single CMMS system accessed from one location, or federated solution across each DECC?

DISA Response: The Government requires a production system that will be deployed to a central management site and a potential fail-over site. Users could be located at the various CONUS/OCONUS sites listed in section 9 of the PWS.

(2) Is the government looking to integrate this solution with an existing backup solution?

DISA Response: No, there is no existing backup solution. See response to #22 for full list of interfaces.

(3) If so, can the government please provide information on the backup systems currently in use at DISA that will be used to backup the system?

DISA Response: See response to #22 for full list of interfaces. There is no existing backup solution.

(4) Can you please provide the RPO and RTO objectives required for CMMS Solution?

DISA Response: No RPO/RTO have been identified in the PWS.

(5) What type of database systems can the current system backup (in an online mode)?

DISA Response: There is no current system backup.

(6) What type of storage array snapshotting capability is available?

DISA Response: There is no current system backup.

79. Does DISA require GSA pricing for this RFP?

DISA Response: No, this is not required; this is a small business set-aside on the open market.

80. There is not a reference to mobile technology in the RFP. Does DISA require the use of smart phones or iPads to electronically manage work orders by technicians? If so, how many technicians would DISA have using this technology?

DISA Response: Any type of device which transmits an RF signal is not allowed in many areas of our facilities

81. There is not a reference to mobile technology in the RFP. Does DISA require the use of iPads for Supervisors to accept requests, schedule work orders to technicians and view KPI Dashboards while in the field?

DISA Response: Any type of device which transmits an RF signal is not allowed in many areas of our facilities

82. In Phase Two of the evaluation process, the “simulated environment” will be comprised on a limited data set for testing. Can you provide more detail as to amount of data that will be expected to be populated in this environment?

DISA Response: There will be a limited amount of data that is representative of various types of assets.

83. Testing Process – It appears the testing time will consist of 5 weeks for Installation/STIG and 1 week for testing. What periods during that 6 weeks will require a representative from the vendor be onsite and for what amount of time? It appears unclear in several different location in the information.

DISA Response: The pre-production lab/test facility is located in Montgomery, AL. The Lowest Price Offeror l will proceed to the POC testing phase to evaluate technical acceptance. During the POC, the offeror must be present at the test facility each test date in a mutually agreed upon by both the offeror and the government test schedule.

84. Is it a requirement that the vendor supply these resources during the testing period and is the vendor completely responsible for all expenses incurred with this support?

DISA Response: The offer would provide software and manpower resources, while the Government provides the hardware and test facilities during the POC.

85. In section 2.4 of the Functional Test Plan, it states under “Import Data” that the “User will import data from a legacy system.”

DISA Response: The government will provide each offeror with the exact same set of test data to ensure fairness and consistency across the POC testing process. There will be a limited amount of data that is representative of various types of assets.

86. Is this only the small sample data set that will be imported?

DISA Response: Yes, see response to #85.

87. Will this be conducted by a DISA employee or by a Vendor representative?

DISA Response: The DISA employee will be hands-on the keyboard during this POC, the offeror will provide direction/instruction to the DISA employee to complete the testing functions.

88. Please define expectations for the information that will eventually be loaded from the MP2 application. Do you intend to just capture static data and open work orders/pm’s, or do you intend to capture all historical data transactions?

DISA Response: There will need to be a one-time data import of 10,000 items with up to 5 -6 records associated with each of these items from MP2 and the Maximo/Access database into the new application. The new application will be the system of record.

89. If you intend to capture all historical data, how many records does this entail?

DISA Response: See response to #88.

90. How many open work orders does the MP2 solution currently have?

DISA Response: On average, there are about 400 open work orders enterprise-wide.

91. How many future Preventive Maintenance work orders are in the MP2 system?

DISA Response: On average, there are about 5,400 work orders opened and worked each month enterprise-wide.

92. Please explain the purpose of the pricing requirement for the Optional 6-MO extension? Is this just a 6 month extension of the annual support contract for the proposed software?

DISA Response: No, this is just a requirement for a six month extension. The six month extension would be required only if the contract exceeded the base and option periods.

93. Please define the extent of the data collection needs for the various DISA locations?

DISA Response: The on-site data collections would require physical travel to the site and an inventory of CMMS assets at that site.

94. Is there any location that does not have any information in the current MP2 solution?

DISA Response: Ft. Meade does not have any information in the current MP2 solution.

95. What is the reliability of the data inside the current MP2 solution?

DISA Response: The data within the MP2 solution is very reliable but must be utilized through a maintenance and operations service contract. DISA does not own MP2.

96. Is the awarded vendor responsible for physically verifying the accuracy of the data per location?

DISA Response: Yes, that is the site collection requirement within the PWS.

97. Please provide examples of the type of data that would need to be collected from these locations.

DISA Response: See response #28 to include the data fields required for the following types of assets: Air handler unit, CRAC, distribution panel, electric water heater, elevator, exhaust fan, horizontal ceiling fan coil unit, horizontal ducted fan coil unit, lighting panel, mechanical panel, Micro Net Lon (MNL) controller, MV switch disconnect, power panel, preheat coil circ. Pump, secondary unit substation, sprinkler systems, transformer, Underfloor Fan Powered VAV terminal (UFT), unit heater, vertical stack fan coil unit, automatic transfer switch, battery, constant air volume terminal, controls, hot water unit heater, maintenance bypass, preheat unit heater, etc.

98. Surge Support – Please clearly define DISA’s…