Industry_Day_QA_Summary.pdf

HEDC Industry Day (13 June 19) Q&A Summary

Hill Enterprise Data Center (HEDC) Industry Day Q&A Summary

13 June 2019

These Q&As are being provided for informational purposes only. In the event there is a conflict between these answers and the requirement documents (i.e. PWS, CDRLs, etc.) in the RFP (solicitation) and resulting contract the RFP/contract will take precedence and supersede.

1. Q: Are the labor categories listed encompassing of all the categories that the program envisions?

A: As of right now, these are the categories that the Government plans on incorporating into the contract. Logistician not anticipated to be included as a labor category.

2. Q: What version of Teamcenter is the program running? Are there specific versions?

A: Reference PWS

3. Q: What is the approach and timeline from a Government’s perspective?

A: Please see chart…

4. Q: Do you see any challenges moving to the cloud?

A: Legacy applications that don’t fit into native cloud tools.

5. Q: AWS is splitting from Oracle, are you open to something other than Oracle?

A: Based on customer requirement.

6. Q: What is HEDC considered in the FDCCI?

A: Internal Processing Node

7. Q: Are you modeling the data center after a similar DoD Data Center?

A: No, following industry data center standards.

8. Q: Is IL 5 the maximum required?

A: IL 5 is the HEDC’s minimum; IL 6 is the highest requirement at this time

9. Q: Do you have a process for the data center, i.e ticketing center?

A: Yes, 75th ABW BMC ITSM ticketing system.

10. Q: What is the SAAS requirement?

A: Reference PWS

11. Q: What ITSM version are you using?

A: ITSM 9.1; digital workplace

12. Q: Are all of your hosted apps RMF?

A: No.

13. Q: Are you looking at anything other than BMC?

A: Yes, submit system categorization.

14. Q: Do you have a set process for engineering applications?

A: Yes, onboarding processes.

15. Q: Do you have a process to load applications?

A: Yes, onboarding processes.

16. Q: What is the period of performance of the current contract?

A: The current contract will expire in March 2021. Anticipated award date of this acquisition is October 2020 to allow ramp up time.

17. Q: Does the Government intend on having a hybrid cloud or straight cloud?

A: Hybrid cloud.

18. Q: Will the applications only be hosted at Hill AFB or will there be other sites?

A: Currently host at 15 bases across the U.S. Centrally managed at Hill AFB.

19. Q: How are all the applications being supported (what is the amount of SW

Development/Sustainment/MX vs hosting only)?

A: No software development. Only sustainment and onboarding.

20. Q: Has the commercial off-the-shelf (COTS) Depot Maintenance and Logistics system

Modernization effort already begun and if so, what software product was selected?

A: No decision has been made at this time. HEDC does not dictate adoption.

21. Q: Can you please provide the current FTE count in each area identified in the scope of the work?

A: Approximate current FTE is 27-30. However, this contract is expected to have a larger scope.

22. Q: Can you please describe your current use of Oracle?

A: Currently use Oracle database technology, middleware, and e-business

23. Q: Would you be interested in moving to other open source database software products, potentially saving Oracle licensing funds?

A: Open source database software product requirements are customer driven.

24. Q: What is the current percentage distribution with regard to the database software packages mentioned?

A: Distribution is proprietary.

25. Q: Can you please provide an estimate on how many new customer applications/systems are expected for onboarding and consolidation requirements on premises and in commercial clouds?

A: Unknown.

26. Q: With regard to the hosting services provided, can you please describe the level on ongoing maintenance provided to customers? Specifically, is monthly/quarterly security patching provided with this support? What is the response time requirement if any customer application issues arise?

A: Yes, monthly and quarterly security patches are required. Response time is customer dependent based on SLA.

27. Q: Has the government determined the required minimum amount of staffing necessary for effective performance on each task order?

A: No, staffing will be negotiated at the task order level.

28. Q: With regard to mitigating security vulnerabilities and encryption key management, can you describe any use of PKI certificates for authorization and authentication purposes?

What methodology or processes are used for providing access decisions to applications?

What software/hardware products are you currently using? We assume this is the Oracle

Internet Directory as mentioned in the Oracle products utilized?

A: DoD security framework.

29. Q: Can you describe the technologies used for proper load balancing across the current availability zones? Are you utilizing F5 BIG-IP for this service offering?

A: Proprietary. Yes.

30. Q: With regard to the Agile/Rapid Release Upgrade Model, has any level of Devops been implemented? Are any current tools being utilized?

A: No.

31. Q: Can you please describe the current use of AWS and Azure to include the current list of service offerings?

A: Cloud migration is not currently implemented.

32. Q: With regard to the GeoBase application that requires continuous sustainment, we are assuming that GIS products are utilized for this application. Can you please explain the GIS technologies used to properly gauge sustainment costs?

A: Proprietary.

33. Q: Are there any FISMA requirements for individual applications being hosted in this environment? If so, are there currently different levels of SLAs established with them and would the contractor be responsible for aiding the customer in any annual FISMA scanning/testing and reporting?

A: Yes, we have SLAs with our customers. The contractor would be responsible for scanning/testing and reporting.

34. Q: Can you describe any services provided today with regard to testing environments to support customer acceptance and functional testing?

A: Standard staging and integration environment.

35. Q: Can we please be provided with any documentation detailing the current A&A process to properly gauge cost and resources related to that service offering?

A: The current A&A process is RMF (Risk Management Framework).

36. Q: What is the Maintenance and Support for the PODs and where are they located? What is technical infrastructure of the PODs? Is there standardized buildout? What is the purpose of the POD’s? Is it for an AZ?

A: POD locations and specifications are proprietary.

37. Q: Are there OCI concerns with contractors. Can you describe the contracts of concern?

A: No OCI concerns.

38. Q: Define the relevance of the “other technologies”. Are they being used today.

A: The technologies in the Datacenter are driven by customers’ requirements and there is a level of standardization and modernization of other technologies. If a other technologies can meet the customer needs then it will be utilized.

39. Q: Do they have your own AD Domain or are you part of an USAF Domain?

A: We are part of USAF Domain

40. Q: Are you running Oracle on Windows or on Linux?

A: Both

41. Q: Vsphere / RHEV – What is the ratio between the 2. Do you prefer one?

A: We are 100% VMware shop.

42. Q: VSphere was mentioned what about Horizon?

A: We don’t support Horizon in the Datacenter.

43. Q: Who will be the primary cloud provider?

A: Unknown at this point.

44. Q: Is it a challenge to find workload to host or where to host it?

A: No. We a consistent amount of customers that want to onboard in the Datacenter.

45. Q: Do you have a process for license management?

A: Yes.

46. Q: Would the AF considering adding an Infrastructure as a Service as one of the contractor optional services to this opportunity?

A: Maybe.

47. Q: Would the AF consider a Software as a Service for future product acquisition listed for sustainment support?

A: We would in the future but in the case by case bases.

48. Q: Is JRSS fully implemented?

A: We are a customer of the JRSS and not an implanters of the JRSS Stack.