______The Electric Reliability Council of Texas, Inc. (ERCOT) Contract Administration and Procurement

Request for Information For Enterprise File Shares Improvement RFI_6- 14_JKR Date of Release: May 30, 2014

1

______

1 GENERAL INFORMATION 4 1.1 RFI Objective 4 1.2 ERCOT Background 4 1.3 Basic Philosophy: Vendor Relations 5 1.4 Legal and Regulatory Constraints 5 1.5 ERCOT Point of Contact 5 1.6 ERCOT Timeline 6 1.7 RFI Cancellation 6 1.8 Right to Reject Responses 6 1.9 No Reimbursement for Costs of Responses 6

2 SCOPE, PURPOSE, AND OBJECTIVE 7 2.1 Project Background 7 2.2 Project Overview and Objective 7 2.3 ERCOT File Shares Requirements 8 2.4 Project Timeline 13 2.5 Vendor Questions and Required Feedback 13

3 GENERAL INSTRUCTIONS AND RESPONSE REQUIREMENTS 14 3.1 Notice of Intent to Respond 14 3.3 News Releases 14 3.4 ERCOT Use of Vendor Ideas 14 3.5 Additional Information 15 3.6 Instructions for Submitting Responses 15 3.7 Format and Content 16

4 EVALUATION 18 4.1 Evaluation of Response 18 4.2 Success Criteria 18 4.3 Evaluation Criteria 18 4.4 Discussions with Respondents 18

5 ATTACHMENTS 19 2

______5.1 Attachment A – ERCOT Standard Agreement 19 5.2 Attachment B – Non-Disclosure Agreement 19 5.3 Attachment C – Vendor Information Form and W-9 Form 19 5.4 Attachment D – DFS-R Architecture – Current Configuration 20

3 ______

1 GENERAL INFORMATION

1.1 RFI Objective This is a Request for Information (RFI) only and does not constitute a commitment, implied or otherwise, that the Electric Reliability Council of Texas, Inc. (ERCOT) will take procurement action in this matter.

The objective of this RFI is to gain information on Network Attached Storage Solutions (NAS) solutions available to help ERCOT administrators overcome current complexities with managing department file shares and production application shared file systems between servers with Linux, Windows, and AIX operating systems. ERCOT relies heavily on file shares for day to day operations and as critical components to support ERCOT business applications. Today, ERCOT’s file shares are configured on SAN storage disks allocated to Windows servers at both the production and DR sites. To ensure continuous availability, even in the event of complete site failure, Microsoft's implementation of Distributed File System Replication (DFS-R) is configured for file replication and synchronization between the sites.

DFS-R has become an increasing challenge due to the size of files and growth rate of several file shares. ERCOT is looking for a NAS solution that improves the reliability, scalability, ease of administration, and management of the backups for its department file shares and production application shared file systems.

1.2 ERCOT Background

1.2.1 Overview of the Electric Reliability Council of Texas, Inc.

The Electric Reliability Council of Texas (ERCOT) manages the flow of electric power to approximately 23 million Texas customers –representing 85 percent of the state’s electric load and 75 percent of the Texas land area. As the Independent System Operator for the region, ERCOT schedules power on an electric grid that connects 40,500 miles of transmission lines and more than 550 generation units. ERCOT also manages financial settlement for the competitive wholesale bulk-power market and administers customer switching for 6.6 million premises in competitive choice areas. ERCOT is a membership-based 501(c)(4) nonprofit corporation, governed by a board of directors and subject to oversight by the Public Utility Commission of Texas and the Texas Legislature. Additional information about ERCOT can be found on its website at: http://www.ercot.com/.

4 ______1.3 Basic Philosophy: Vendor Relations ERCOT’S fundamental commitment is to contract for value and successful results. A successful result is defined as the generation of defined, measurable, and beneficial outcomes that support ERCOT’s Missions, Objectives, and Goals, and satisfies all defined contract requirements.

1.4 Legal and Regulatory Constraints

1.4.1 Conflicts of Interest ERCOT seeks to ensure a level playing field in all vendor relations. ERCOT has implemented an aggressive policy concerning actual or potential conflicts of interest to ensure fair and open competition, and has included language concerning actual and potential conflicts of interest in Section 8 of the Master Agreement (Attachment A). Respondents must carefully review and understand this language when developing proposals.

1.4.2 Former Employees of ERCOT The Respondent must disclose any past employment of its employees and agents, or its subcontractors’ employees and agents, by ERCOT, including the individual’s name and the date such individual’s employment at ERCOT ended.

1.5 ERCOT Point of Contact The sole point of contact for inquiries concerning this RFI is:

Jana Richardson, CTPM, CPP, MBA. ERCOT 2705 West Lake Drive Taylor, Texas 76574 (512) 248-4226 Fax: (512) 248-3118 [email protected]

All communications relating to this RFI must be directed to ERCOT contact person named above

5 ______

1.6 ERCOT Timeline ERCOT Timeline RFI Release Date 05/30/2014 Notice of Intent to Respond 06/11/2014 Vendor Questions Due 6/13/2014 Response to Vendor Questions 6/20/2014 Vendor Responses Due 7/1/2014 at 2 p.m. Vendor Presentations (if Necessary) TBD Future Solicitation for Proposal/Quote TBD

1.7 RFI Cancellation ERCOT reserves the right to cancel this RFI

1.8 Right to Reject Responses ERCOT may, in its discretion, reject any and all Responses, submitted in response to this RFI.

1.9 No Reimbursement for Costs of Responses ERCOT will not reimburse any respondent for costs of developing a in response to this RFI.

6 ______

2 SCOPE, PURPOSE, AND OBJECTIVE

2.1 Project Background ERCOT’s department file shares (currently 52 TB at each site, and growing at 200 GB monthly at each site) has become complex and a challenge to manage. DFS-R fails on a regular basis and backups are time-consuming. See [Section 5.4 Current Configuration] for more information on ERCOT’s current infrastructure deployment for its department file shares.

ERCOT’s high-level requirements are to:  Improve reliability of file shares  Improve administration efficiency  Ensure scalability to meet growing demands  Reduce backup times, delays, and complexity of file shares  Provide cost avoidance reclaiming and redeploying existing storage  Reduce cost by removing servers, licenses, and operational costs  Provide NAS services for other opportunities

2.2 Project Overview and Objective ERCOT plans to implement an enterprise Network Attached Storage (NAS) solution and leverage the NAS architecture to help administrators overcome the complexities of the current environment. Specifically, the solution must satisfy the following objectives:  Reduce administrative overhead  Admin group and Control Room Operators must maintain access to their home folders even in the event of complete site failure  Provide redundancy against local or complete site failure  Reduce backup time and complexity  Recover consistently from failure  Expand easily to add additional file shares  Provide snapshot capabilities for protecting data  Provide 90 days of Backups within the NAS  Provide both CIFS and NFS sharing capability for all shares  Scale to provide capacity for file shares currently growing at 200 GB per month, per site  Provide end-users the ability to restore a file without administrator engagement  Provide the ability to restore files in file shares from different points during the day 7 ______ Support disk quotas

2.3 ERCOT File Shares Requirements ERCOT seeks to review and implement an enterprise NAS (Network Attached Storage) solution and has defined the current requirements and specifications.

2.3.1 The solution must have:  High availability and remote disaster recovery: sync or async replication between sites. There must be no single points of failure, with redundancy at every level and between sites, to include storage, compute, and network.  Scalable capacity is a mandatory requirement of this solution. The system must be capable of incrementally scaling with minimal, if any, disruption to service  Users must be able to reconnect with the same URL/drive mapping in case of local or complete site failure  Active Directory security group support (NTFS security style)  The solution must have robust monitoring capabilities to provide a global view of the health of the system and the ability to promptly alert administrators if any component of the infrastructure fails or is operating in a degraded state.

Capacity: For the purposes of this RFI assume that Primary and DR sites will be provisioned identically. ERCOT requires that the solution present, at a minimum, but not limited to the following:  Support for Quotas (could be implemented during the initial phase or later)  At least 80TB usable space, with growth rate of 200 GB per month, and snapshot retention of 90 days at the Primary Site, all of which will be replicated to the DR Site. Snapshots will be taken every hour for one week and then weekly snaps taken once a day for 90 days. o Please describe your Thin Provisioning, Compression and Deduplication support. o Describe anything that pertains to capacity not included above that differentiates your solution from that of others.

Tiering: ERCOT proposes that the vendor examine the subject of Tiering data among varying speeds of disks.  Explain why your solution does or does not include Tiering. Explain how your proposed solution accomplishes Tiering manually or automatically. Demonstrate that your solution addresses ERCOT’s needs for industry standard data access times for its use cases and applications.

8 ______ Based on your understanding of our environment, recommend the appropriate disk speeds including Solid State for our applications.  Detail the number and type of disks, disk speed, block size, and access time of each tier.  If tiered automatically: o How frequently is usage scanned? o How frequently is data moved among the tiers? o How large are the blocks of data moved among the tiers? o Describe how Tiering can be customized to suit the City’s needs. o Describe anything that pertains to Tiering not included above that differentiates your solution from that of others.

Physical Hardware: ERCOT requires a solution that can be mounted on a standard server rack. It should allow for future addition of drives, shelves, and controllers.  Describe your solution’s use of controllers.  How many total disk drives does your proposed solution include?  Define the disk size, rotational speed, access times, and quantity of each type of drives used, their capacity, and MTBF.  Describe the disk shelves including their physical size, number of drives they can contain, types of drives they can contain, connectivity, power, and cooling requirements.  Explain your solution's layout per shelf of disks.  Define the total number of IOPS for the proposed solution.  Describe redundant and/or hot-swappable components of your proposed solution (i.e. Raid Controllers, PSU’s, etc.).  Explain your proposed solution’s use of cache and SSDs.  Explain how non-disruptive maintenance is achieved.  Explain how your solution addresses the addition of disks, shelves, and controllers.  Describe anything that pertains to the physical characteristics of your solution not included above that differentiates it from that of others.

Redundancy:

9 ______ Describe all redundant features of your proposed solution. Include a description of the elimination of all single points of failure.  Describe the number of spares drives included in your solution and how they can be brought online in the event of a drive failure.  Describe the solution’s ability to recover from hardware failures of various components in your solution  Detail the RAID levels or other technology that your proposed solution uses to achieve resilience.  Explain the amount of raw storage that is consumed by your redundancy method.  Describe anything that pertains to spare drives not included above that differentiates your solution from that of others.

Upgrades: ERCOT requires that all software is upgradeable and updateable without cost while under warranty or maintenance agreement.

Support: ERCOT requires support for your proposed solution for a period of 5 years.  Define your level of support detailing items covered and the process for contacting support  Describe anything that pertains to support not included above that differentiates your solution from that of others.

Warranty/Maintenance: ERCOT requires all hardware to be warrantied against failure for a period 5 years.  Detail your proposed solution’s hardware warranty  Detail the SLA (Service Level Agreement) included in your proposed solution. Include the time for replacement parts to arrive and be installed.  Explain the levels of the warranty proposed. Include software and hardware that is covered.  Explain which updates and upgrades are included, how notifications about updates are made, and the process of applying updates to your proposed solution.  Explain the availability of an onsite engineer and the conditions under which one would be dispatched.  Describe anything that pertains to Warranty/Maintenance not included above that differentiates your solution from that of others.

Management: 10 ______ERCOT requires that your proposed solution can be easily managed.  Describe the process of managing your solution. Include screen shots of the management interface  How are multiple controllers managed?  Describe key features of the management system.  Detail your solution’s integration with VMware.  Explain the reporting features of your proposed solution. Include sample reports about usage, capacity, errors, and logs.  Explain notification capabilities of your proposed solution.  Describe anything that pertains to management not included above that differentiates your solution from that of others.  Describe how your product supports encryption.

Connectivity:  Unified storage: support for file (CIFS/NFS) and block storage (FC) is highly desired  Explain the ability of the storage system to support SAN/NAS protocols such as Fibre Channel, iSCSI, CIFS, NFS etc.  Detail all connectivity options including 10Gb Ethernet, 4Gb+ FC, redundancy and aggregation methods.  As a storage platform, the solution shall be compatible with VMware.  Multipath support is required. Describe support for VMware vSphere 5.x, Windows Server 2003, 2008, 2008 R2, 2012 R2, RedHat Linux 5.x, RedHat Linux 6.x, RedHat Linux 7.x, AIX 5.3, AIX 6.1, and AIX 7.1. The multipath software can be native to the OS or storage vendor-supplied.  Must support Microsoft Clustering with Windows Server 2012, 2008 R2, MS SQL 2008, MS SQL 2012, MS SQL 2014  Describe anything that pertains to connectivity not included above that differentiates your solution from that of others.

Replication: ERCOT requires that all data housed at the Primary site be replicated either asynchronously and/or synchronously across the network infrastructure to the DR site.  Describe the manner of replication used in your proposed solution.  Describe the process of failing over to the DR Site in the event of an outage at the Primary Site.  Describe the process of failing back to the Primary Site after the Primary Site is again available.  Describe anything that pertains to replication not included above that differentiates your solution from that of others. 11 ______

Snapshots / Data Protection: ERCOT requires that snapshots be utilized  Describe your solution’s ability to take snapshots.  Detail your solution’s ability to point to and recover a snapshot.  Must support current versions of Symantec NetBackup.  Describe anything that pertains to snapshots not included above that differentiates your solution from that of others.

Test / Lab environment: Ercot desires to have a lab environment for the purposes of testing changes and configurations before deployment to production systems. The physical hardware should be the same as the production systems, but minimal in scale. o Please provide an option and cost for setting up a test environment with your solutions

Deployment: ERCOT will require onsite deployment services to install the proposed solution.  Detail the process of deploying the new solution and migrating data from our current storage.  Describe the involvement of project managers, engineers, and others in the deployment  Detail the time required to install your proposed solution.  Describe anything that pertains to the deployment not included above that differentiates your solution from that of others.

Training:  Include the training required for a minimum two persons to manage, maintain, and upgrade the proposed storage system.  Describe the type, location, and duration of all training.  Detail the options for training after deployment.  Describe anything that pertains to training not included above that differentiates your solution from that of others.

Migration: ERCOT will require a detailed plan to move the current environment to the new solution  Describe the services available to support the migration.

12 ______Software:  Describe all software features, included and optional, available in your proposed solution.

2.3.2 ERCOT would like the solution to have:  Deduplication / Compression  Tiering 2.4 Project Timeline

2.4.1 Project timeline is currently planned for 2014

2.5 Vendor Questions and Required Feedback ERCOT seeks vendor responses to the following questions and solicits general feedback regarding ideal methodologies and approaches to enterprise NAS architecture / solution.

2.5.1 Corporate Background and Experience  How long have you been providing Enterprise NAS solutions?  Are NAS solutions a core competency of your business?  What experiences have you had implementing NAS solutions?  What market are your customers primarily in?  What is your experience with NAS and DFS integration architecture?  What is your methodology for transferring data or migrating between different platforms?

2.5.2 Total Cost of Ownership  What are the initial (one-time) costs for this type of solution?  Is there an annual subscription or software fees required for long term support? If so, please describe.  If managed internally by ERCOT, what additional hardware and/or software needs should ERCOT consider?  What other costs will contribute to the total cost of ownership of this type of solution?  Should ERCOT require a POC, does your company provide (and fund) the necessary resources to support it?

3 GENERAL INSTRUCTIONS AND RESPONSE REQUIREMENTS

13 ______3.1 Notice of Intent to Respond A prospective vendor may submit a Notice of Intent to Respond to the ERCOT Point of Contact identified in Section 1.5 no later than 5:00PM Central Time on the deadline listed in Section 1.6 ERCOT Timeline. The Notice of Intent should be delivered via email. Only vendors who submit a Notice of Intent to respond will receive the answers to questions from all vendors, and / or any clarifications, amendments, and addenda to the Request for Information. Vendors who provide a notice of intent are not required to submit responses.

3.2 Vendor Questions and Comments All questions and comments regarding this RFI must be submitted electronically to the e-mail address contained in Section 1.5 (ERCOT Point of Contact). All questions must reference the appropriate RFI page and section number. In order to receive a response, vendor questions and comments must be received no later than the deadline set forth in Section 1.6 (ERCOT Timeline). Inquiries received after the due date may be reviewed by ERCOT but will not receive a response. Answers to vendor questions will be e-mailed to the point of contact listed on the Notice of Intent to Propose.

A respondent must inquire in writing as to any ambiguity, conflict, discrepancy, exclusionary specification, omission or other error in this RFI prior to submitting a proposal. If a respondent fails to notify ERCOT of any error, ambiguity, conflict, discrepancy, exclusionary specification or omission, the respondent shall submit a proposal at its own risk and, if awarded the contract, shall have waived any claim that the RFI and Master Agreement were ambiguous and shall not contest ERCOT’s interpretation. If no error or ambiguity is reported by the deadline for submitting written questions, the respondent shall not be entitled to additional compensation, relief or time by reason of the error or its later correction.

ERCOT reserves the right to amend answers prior to the submission deadline.

3.3 News Releases A respondent may not issue press releases or provide any information for public consumption regarding its participation in this RFI without specific, prior written approval of ERCOT.

3.4 ERCOT Use of Vendor Ideas  ERCOT reserves the right to use any and all ideas presented in any response that are not the respondent’s proprietary information and so designated in the response. The respondent’s proprietary materials do not include information that is already published or available to the public, or subsequently becomes available;

14 ______ is received from a third party who, to ERCOT’s knowledge, is not in breach of any obligation of confidentiality; or  is independently developed by personnel or agents of ERCOT without reliance on the respondent’s proprietary materials.

3.5 Additional Information By submitting a response, the respondent grants ERCOT the right to obtain information from any lawful source regarding: (i) the past business history, practices, conduct and ability of a respondent to supply goods, services and deliverables; and (ii) the past business history, practices, conduct and ability of the respondent’s directors, officers and employees. ERCOT may take such information into consideration in evaluating responses.

3.6 Instructions for Submitting Responses 3.6.1 Number of Copies

Three (3) hard copies and one (1) electronic copy (soft copy) is requested for the response via email. The file size must not exceed 20MB.

3.6.2 Submission

Submit responses to the ERCOT Point of Contact no later than 2:00 p.m. Central Time on the submission deadline (See Section 1.6 & 1.7).

3.6.3 Additional Requirements All responses must be:  Clearly legible;  Sequentially page-numbered;  Organized in the sequence outlined in Section 3.7;  Bound in a notebook or cover;  Responsive to the requirements of this RFI;  Responses should include the respondent’s name at the top of each page, and should not include unrequested materials or pamphlets.

3.7 Format and Content The proposal must consist of two parts:  Part 1 – Business Response; and

15 ______ Part 2 – Cost Proposal.

3.7.1 Part 1 -- Business Response The Business Response must include:  Section 1 – Transmittal Letter;  Section 2 – Executive Summary;  Section 3 – Corporate Background and Experience;  Section 4 – Methodology and Services Approach  Section 5 – Assumptions;  Section 6 – Vendor Information and Other Required Forms.

Section 1 -- Transmittal Letter Respondents must include a transmittal letter printed on official company letterhead. The transmittal letter must include:  Disclosure of all pending, resolved, or completed litigation, mediation, arbitration, or other alternate dispute resolution procedures involving the respondent (including subcontractors,) and its client(s) within the past 24 months.  Disclosure of all affiliations with or ownership relationships with any ERCOT Market Participant or its affiliates.  A description of any personal or business interest that may present an actual, potential or apparent conflict of interest with the performance of the contract and an explanation of how the respondent can assure ERCOT that these relationships will not create an actual conflict of interest.  A list of key personnel previously employed by ERCOT in accordance with the requirements of Section 1.4.2.

Section 2 -- Executive Summary In this section, the respondent should condense and highlight the content of the Business Response to provide ERCOT with a broad understanding of the respondent’s approach to meeting ERCOT’s objectives for this RFI.

Section 3 -- Corporate Background and Experience

Respondent Background and Experience

16 ______This section details the respondent’s corporate background and experience. If the respondent proposes to use subcontractor(s), it must describe any existing on ongoing relationships with such subcontractor(s), including project descriptions. The section should include the following information:  Respondent’s full organization, company or corporate name;  Headquarter address;  Type of ownership (e.g. partnership, corporation);  Federal taxpayer identification;  Name and title of person responsible for responding to questions regarding the response, with telephone number, facsimile number and email address.  Describe the respondent’s corporate background as it relates to projects similar in scope and complexity to the project described in this RFI.

Section 4 – Methodology and Services Approach Describe the respondent’s methodology for providing the services/requirements identified in Section 2. Include a proposed project schedule (for a POC), including start and finish dates of the terminal and summary elements that essential to developing a NAS solution as required in Section 2 or proposed by the vendor.

Section 5 -- Assumptions State any business, economic, legal, or practical assumptions that underlie the respondent’s Response.

Section 6 – Vendor Information and Other Required Forms Respondents must complete the following required forms:  Nondisclosure Statement (Attachment B)  Vendor information form (Attachment C)  Except for current ERCOT suppliers who have an active Master Agreement with ERCOT or who have completed the Vendor Information Form (VIF) within the last six months, all Respondents must provide a completed Supplier Vendor Information Form, attached hereto as Attachment C along with the proposal.

3.7.2 Part 2 -- Cost Proposal The Cost Proposal must be based on the Scope of Work described in Section 2. This section should include any business, economic, legal, or practical assumptions that underlie the Cost Proposal.

17 ______

4 EVALUATION

4.1 Evaluation of Response ERCOT will select the successful vendor through an internal evaluation process. ERCOT will consider capabilities or advantages that are clearly described in the proposal, which may be confirmed by oral presentations, site visits or demonstrations if required, and verified by information from reference sources contacted by ERCOT. ERCOT reserves the right to contact individuals, entities, or organizations that have had dealings with the respondent or staff proposed for this effort, whether or not identified in the proposal.

4.2 Success Criteria Vendor Criterion Measurement Propose solution comment/suggestion Complete Redundancy Replication between Install NAS Appliance at both Production and DR sites sites and configure storage replication Reduce backup time TBD NAS architecture should have integrated backup solution Uninterrupted access for Simulate site failure and Use DFS-R assigned from Admins/Control Room verify continued access block storage for home folders User should always use Simulate site failure and Solution 1 (Automatic) same URL/drive verify users reconnect with Implement DFS and map NAS mapping existing URL/drive shares as Targets mapping Solution 2 (Manual) Administrators will use CNAME to re-map shares after replica is activated to Read/write

Similar or better TBD Provide sufficient cache and performance as existing disks to ensure high solution performance

4.3 Evaluation Criteria The primary criteria for evaluating the proposals as they relate to this RFI are as follows: 1. The vendor’s ability to meet the requirements set forth in Section 2 and information provided in the table in section 4.2 above. 2. The vendor’s fees or cost structure.

4.4 Discussions with Respondents ERCOT may, but is not required to, conduct discussions and negotiations with all, some, or none of the respondents for the purpose of obtaining the best value for ERCOT.

18 ______

5 ATTACHMENTS

5.1 Attachment A – ERCOT Standard Agreement

ERCOT Master Agreement

Professional Service Agreement

Professional Services Agreement saved as 2003 version 2.19.09.doc

5.2 Attachment B – Non-Disclosure Agreement

Non-disclosure Agreement

NDA for Vendor RFP Response.dot

5.3 Attachment C – Vendor Information Form and W-9 Form

New Vendor Information and W-9 form

Vendor Information Form VIF 6.23.08.doc

IRS Form W-9.pdf

19 ______5.4 Attachment D – DFS-R Architecture – Current Configuration

NAMESPACE SERVERS (Domain Controllers )

Server 34 Server 35 Server 36 Server 37 Namespace root: \\ercot.com

DFS SHARES \\ercot.com\Departments \\ercot.com\Windows BASTROP FILE SERVERS (DFS Targets ) TAYLOR FILE SERVERS (DFS Targets) \\ercot.com\Users \\ercot.com\business \\ercot.com\Settlements

CorpCorp 2222 CorpCorp 2626 CorpCorp 3131 CorpCorp 3535 CorpCorp 5050 CorpCorp 8484

CorpCorp 2323 CorpCorp 2727 CorpCorp 04BB CorpCorp 4545 CorpCorp 5151 REPLICATION DFS-R REPLICATION CorpCorp 2424 CorpCorp 8383 CorpCorp 4848 CorpCorp 5252

CorpCorp 2525 CorpCorp 2828 CorpCorp 4949 CorpCorp 5353 F F I I B B E E R R

TAYLOR Hitachi Storage Array BASTROP Hitachi Storage Array

20 ______5.5 Attachment E – Framework TAYLOR NAMESPACE SERVERS (Domain Controllers ) BASTROP

Server 34 Server 35 Server 36 Server 37 Namespace root: \\company

DFS

\\name\Departments

\\name\Windows

\\name\Users

\\name\business

\\name\Settlements \ \ T

a DFS-R (Admin and Control Room) y l D o r e \\name\admins _ p N a A r t S m

. \\name\controlRoom e e r n c

t o Corp 51 Corp 48 s Corp 51 Corp 48 t

. CorpCorp 2222 CorpCorp 2727 c o m \

Fiber Fiber \ \ B a \ \ \ s \ \ \ \ t \ \ \ \ \ \ \ \ r n n n n \ \ \ \ o n n n a a a \ a n n p a a n m a m m m a a _ m m m a m N e e m m e e e e \ e \ e A \ \ \ e \ u D \ e

Storage Replication \ B S S W D \ u \ s B e . u e e W S s e p e u i r e s t e n r a p s s i t r t c i d n i r l a n s t o n

e Storage Replication o t e l r e t m d e m w s t . m s o s c m e s s o e w e n m e n n t s s n t t \ W t s i n d o w s TAYLOR_NAS.ercot.com BASTROP_NAS.ercot.com

21