Purchasing DepartmentAddendum #2

Date: November 16, 2017 Title: RFB/RFP #LH-0482 Enterprise Storage Array and Storage Area Network (SAN) Infrastructure

Subject: Questions and Answers

1. Can you describe what percent or number of TB’s of the 300TB usable is block data, and what percent or number of TB’s is the file data?Answer: Block – 75%, File – 25%

2. Of the block data, can you generally describe the types and size of data that will be stored in the SAN? (VMware, SQL, Oracle, Epic, VDI, PACS, etc)Answer: VMware – 70TB, SQL – 30TB, Exchange, 20TB, Epic – 40TB, PACS – 40TB, NAS, 60TB

3. How many TB of data are pertaining to Epic?Answer: 40TB

4. How large is the Epic Cache Database?Answer: 8TB

5. How large is the Epic DR Shadow?Answer: 8TB

6. How large is the Epic Report Shadow?Answer: 8TB

7. How large is the Clarity Database?Answer: 8TB

8. Can you provide your Epic Hardware Configuration Guide?

Answer: No

9. Do any of the data sets stored on the array require Data At Rest Encryption?Answer:

10. Do any of the applications use application level encryption or compression before storing the data on the SAN?Answer: SQL backups use compression before being stored on the SAN.

11. What file protocols and versions are required? (NFS, CIFS/SMB, S3, etc)Answer: NFS, CIFS/SMB

12. What portion of the datasets require array based snapshots?Answer: 10%

13. What are the retention requirements of the snapshots?Answer: 28 days – retention is dependent on uses cases and varies dynamically

14. What file protocols and versions are required (NFS, CIFS/SMB, S3, etc.)?Answer: NFS, CIFS/SMB

15. If CIFS/SMB, what is the total number of users that will be connected to the shares?Answer: 1,500-2,000 end users accessing data concurrently

16. If CIFS/SMB, what is the total size in TB of the shared dataAnswer: 75TB

17. How many ports are needed?Answer: 32-64 ports are required

18. How directors do they need?Answer: 2 Directors

19. Can we get the current SAN topology to understand if you are using directors only or do you need TOR FC switches?

Answer: Proprietary information – will not post SAN topology in a public forum beyond what has already been requested in the RFP

In reference to: SECTION 3: MINIMUM REQUIREMENTSSolution must provide at least 300TB usable capacity to support existing virtual and physical storage utilization at Fort Worth datacenter. Questions:

20. What are the performance requirements? Answer: The storage array needs to be able to support at least 100,000 IOPs

21. Are you leveraging all Flash, all HDD or a Hybrid setup? Answer: Hybrid

22. What are the disk types? SSD, 15,000 rpm, 10,000 rpm, 7,200 rpm?Answer: SSD, 15K rpm, 10K rpm, and 7,200 rpm

23. What is the capacity of each disk?Answer: FMD, 300GB SAS, 600GB SAS, 900GB SAS, 3TB SATA drives

24. What RAID Level or Levels are you using?Answer: 14+2, 7+1, 6+2

25. Will the new 300TB System be integrating with or replacing the HDS HNAS or the VSP Block Storage or both? Understanding that VSP supports 3rd party block storage devices, does the 300TB of block storage need to be a Hitachi Array or would you consider a 3rd party storage device?Answer: Replacing only VSP Block Storage, any vendor solution will be considered

26. Being this is a request for a new block storage solution for your Fort Worth datacenter and not for your Richardson datacenter, is it correct to say that the replication technology would have to be able to replicate to your HDS environment in the Richardson datacenter?Answer: Yes

27. Will this be handled by your existing VSP and HNAS or is going to be provided by the new storage requirement?

Answer: Replication needs to be handled by the new storage array.

28. What is the make and model of Fibre Channel Director Switch you are replacing? What is the FC Director Switch in Richardson? How many FC Ports? What are the Speeds: 16GB, 8GB, Does is need to be highly redundant and available?Answer: 2 x Brocade DCXs, 1st Generation, 8GB, 192 FC ports. Yes, the solution needs to be highly redundant and available

29. Given the holiday season, would you offer an extension for response?Answer: Yes

30. What is the intended purpose for the 300TB capacity? Is it for primary storage, backup or both?Answer: Primary storage

31. How big is the Epic Production database?Answer: Answered above – 8TB

32. How long does it take to do a backup?Answer: Not relevant to RFP

33. How long does it take to do a restore?Answer: Not relevant to RFP

34. Please clarify “must support existing NAS infrastructure in RDC and JDC datacenters” requirement.Answer: The solution should support our block storage requirements in addition to our file storage requirements (i.e. file snapshots, tiering/archiving, and replication).

35. Is the RFP calling for snapshot/volume mirroring/replication/archiving between their existing and this new one?Answer: The new storage array should support snapshots and volume mirroring internally. Replication should be supported between each storage array in the RDC and JDC datacenters.

36. Does JPS consider Mission Critical (MC)?Answer: Yes

37. What type of growth is JPS expecting beyond 3 years?Answer: We expect approximately 30% growth in storage environment

38. Can we pull data for an assessment on the current platform?Answer: No

39. Is JPS mixing workloads with the EPIC, if yes, what are they?Answer: Yes – Epic, VMware, SQL, NAS file shares

40. Is JPS interested in the trade-in value of their current Epic platform once they have migrated off it to the new solution? Answer: No

41. What is the model or size (in raw TB) of JPS’s current HDS array?Answer: HDS VSP – approximately 500TB raw

42. Does the proposed platform to support EPIC need to have a certain number of EPIC deployments to assure success?Answer: Yes

(Replication)43. Is JPS wanting a storage design that included systems in both the Fort Worth and Richardson

data center locations? Or just a single system with the ability to replicate in the future with an additional purchases of the second system?Answer: A single storage array is required for the Fort Worth datacenter with ability to replicate to Richardson datacenter.

44. Does JPS need Synchronous or A-Synchronous replication between the Fort Worth and Richardson data center locations?Answer: JPS needs Synchronous and Asynchronous replication

(File Storage)45. JPS mention’s an HNAS in the proposal. Will this design need to include “File” based storage as

well as “Block” based storage?Answer: The solution needs to support at least 300TB of “block storage” which includes the existing NAS infrastructure

46. If JPS needs “File” based storage, can you please tell us the size of the file store today and an approximate growth rate.Answer: Answered above – approximately 75TB

(SLAs)47. Can you please tell us JPS’s “Recovery Time Objective” RTO for these data sets?

(RTO) is the maximum tolerable length of time that a computer, system, network, or application can be down after a failure or disaster occurs.Answer: Depends of the tier level of the application. Anywhere from an hour to 72 hours

48. Can you please tell us JPS’s “Recovery Point Objective” RPO for these data sets?(RPO) is the age of files that must be recovered from backup storage for normal operations to resume if a computer, system, or network goes down as a result of a hardware, program, or communications failure.Answer: See answer on question 47.

(IP Network)49. Can you please tell us the bandwidth available between the Fort Worth and Richardson data

centers?Answer: Dedicated 10GB link between the Fort Worth and Richardson datacenters

50. Can you please tell us the average and peak latency between the Fort Worth and Richardson data centers?Answer: Average 2ms

(Data Protection)51. Can you please tell us the number of snapshots JPS expects to need and the approximate

schedule (Hourly, Daily, Weekly, Monthly, etc.)Answer: 28 daily snapshots

(FC Network)52. Can you please tell us the number of front-end Fibre Channel storage ports needed so we can

properly size the storage switching infrastructure?Answer: 24 storage ports

53. Does JPS have other Fibre Channel storage systems that may need to utilize the new storage switching infrastructure?Answer: No, not at this time

54. If JPS has other Fibre Channel storage systems, can you please tell us how many back-end ports these systems are utilizing?Answer: 128

55. Do you have any Fibre Channel ports currently running at speeds lower than 8 GB / second?Answer: Yes

56. Will the solution consist of (1) array with 300TB usable storage?Answer: Yes

57. Is the 300TB proposed for only the Epic Application?Answer: No

58. Is there another array that will be the target of the Epic application for DR?Answer: Yes

59. Is there a need to provide a solution that requires replication from our storage array to an array of a different manufacture?Answer: Possibly, if a new storage array vendor is being recommended

60. Can we assume that the 300TB will be used for data outlined in the Primary Storage array defined in Epic’s ‘Hardware Configuration Guide”?Answer: Yes

61. Can you provide the “Storage Specifications” sections of the “Hardware Configuration Guide”?Answer: No

62. Can we assume to use the ratios of types of data that Epic defines in their “Hardware Configuration Guide”?Answer: Yes

63. Can we assume the data reduction ratios we see in other Epic customers to achieve the 300TB of usable storage for our final solution?Answer: No

64. Can/Will you provide specific storage sizing for the Epic application?Answer: 8TB

65. Can/Will you provide specific storage sizing for other applications?Answer: Answered above, VMware – 70TB, SQL – 30TB, Exchange, 20TB, Epic – 40TB, Legacy/Archive – 40TB, NAS, 60TB

66. Can you describe what percent or number of TB’s of the 300TB usable is block data, and what percent or number of TB’s is the file data?Answer: Answered Above, Block – 75%, File – 25%

67. Of the block data, can you generally describe the types and size of data that will be stored in the SAN? (VMware, SQL, Oracle, Epic, VDI, PACS, etc)Answer: Answered above, VMware – 70TB, SQL – 30TB, Exchange, 20TB, Epic – 40TB, Legacy/Archive – 40TB, NAS, 60TB

68. Do any of the data sets stored on the array require Data At Rest Encryption?Answer: Proprietary information, will not post this information on a public forum

69. Would any of the workloads benefit from Quality of Service (QOS)?Answer: Yes

70. Do any of the applications use application level encryption or compression before storing the data on the SAN?Answer: Answered above. SQL backups use compression before being stored on the SAN. No application-level encryption is being used in the environment.

71. What is your current year over year growth?Answer: approximately 10%

72. What portion of the datasets require array based snapshots?Answer: Epic and VMware

73. What are the retention requirements of the snapshots?Answer: 28 days

74. What data reduction rates are you getting today?Answer: Block – 2:1 compression, File – 30% deduplication

75. What percent or number of TB’s require replication?Answer: 100TB minimum

76. How many TB of data are pertaining to Epic?Answer: 40TB

77. How large is the Epic Cache Database?

Answer: Answered above, 8TB

78. How large is the Epic DR Shadow?Answer: Answered Above, 8TB

79. How large is the Epic Report Shadow?Answer: Answered above, 8TB

80. How large is the Clarity Database?Answer: Answered above, 8TB

81. Can you provide your Epic Hardware Configuration Guide?Answer: Answered above / No, proprietary information – will not post EMR requirements on a public forum.

82. Is all NAS data use shares, or are there other workloads (VMware over NFS, big data analytics, etc.)?Answer: NAS is only for department and user shares. No VMware or big data analytics

83. What file protocols and versions are required (NFS, CIFS/SMB, S3, etc.)?Answer: Answered above – NFS, CIFS/SMB, FTP

84. If CIFS/SMB, what is the total number of users that will be connected to the shares?Answer: Answered above – 1,500-2,000 end users at any given time

85. If CIFS/SMB, what is the total size in TB of the shared data?Answer: Answered above, 75TB

86. How many ports for host connections are required?Answer: Answered above, 32-64 ports are required

87. What is the port count for the DCX directors required for this?Answer: 96

All corrections, changes, additions, revisions, and/or clarifications in this Addendum #2 to theRFP are hereby made a part of the RFB/RFP for #LH-0482 Enterprise Storage Array and Storage Area Network (SAN) Infrastructure.

All Respondents to the RFB/RFP shall acknowledge receipt and acceptance of this Addendum #2 bysigning in the space provided and submitting the signed Addendum #2 with the RFB/RFP.

Proposals submitted without an executed copy of this Addendum #2 attached may be consideredinformal and may be rejected.

Received, acknowledged, and conditions agreed to on this _________ day of _________, 2017, by:

Respondent: __________________________________________________________

Company Name: _______________________________________________________

If there are questions pertaining to this addendum please contact Lizzie Harris at lharri05@jpshealth.org