Questions_and_Responses_4.docx

SSA-RFP-13-1010

Amendment 0007 Attachment 2

Questions and Responses #4

If any Government response below conflicts with a previous Government response to a question, the most recent response is controlling.

Question #1 Hardware cabinets, SAN Cabinets, VTL Cabinets

1. Is a 45U x 700mmW(28”) x 1200mmD(48”) cabinet with the Vertical Exhaust Duct desired? If not, please specify desired H x W x D.

2. Square punched rails or tapped rails?

3. Vertical and/or horizontal wire management panels?

4. Filler panels (required in an isolation data center)?

5. Power in this cabinet: Two (2) vertical PDU’s in the cabinet is typical. This cabinet calls for 208 outlets which is also typical. Do these PDU’s need to have and additional functionality? Do they need to be remotely monitored or controlled? Are C13 and C19 outlets desired on the PDU strip?

6. Internal fans are called out. These fans are not required in a Chatsworth VED cabinet environment. Please clarify.

7. SAN Cabinets See above

8. VTL Cabinets See above

Government Response:

SSA has defined its requirements for “Hardware Cabinets” in Section C.3.2.5 and “Cabinet Hot Air Containment” in Section C.3.2.6. The “Cabinet Hot Air Containment” requirement applies to cabinets for installation at the NSC and the NSC test lab located at the NCC. All Cabinets installed in the NSC and the NSC test lab must meet the “Hardware Cabinets” and “Cabinet Hot Air Containment” requirements. Sections C.3.2.5 and C.3.2.6 have been updated to clarify.

1. Vertical exhaust ducts (or chimneys) are not desired, but are technically acceptable if all other specifications are met. See Section C.3.2.6. All cabinets must not exceed 84” (H) x 30” (W) x 48” (D). The ceiling height is 144 inches. So, although not preferred by SSA, a vertical exhaust duct used for hot air containment must not exceed the ceiling.

1. SSA does not have a preference. SSA will only install proposed equipment in those cabinets. Just as a note, SSA currently uses square punched rails in its cabinets.

1. SSA does not have a preference.

1. Yes, all front-to-back air that does not go through the equipment must be blocked.

1. SSA will supply external L6-30 power connections to the equipment as the norm. SSA does not have a preference as to internal connections like the C13 and C19. It will be up to the contractor to manage.

1. The internal fans must be part of the equipment. SSA will not consider cabinet-assist fans technically acceptable. SSA has removed the requirement for fans in the SAN Cabinets and VTL Cabinets. See Sections C.3.3.5.3 and 3.4.5.

1. The Cabinet Hot Air Containment requirement does not apply SAN Cabinets as defined in Section C.3.3.5.3. SSA will not order SAN Cabinets for the NSC. Section C.3.3.5.3 has been amended to clarify.

1. The Cabinet Hot Air Containment requirement does not apply to the VTL Cabinets defined in Section C.3.4.5. SSA will not order VTL Cabinets for the NSC. Section C.3.4.5 has been amended to clarify.

SSA has embedded two technical drawings below to help clarify the Cabinet Hot Air Containment requirement.

Question #2 Government Response to Amendment 0005 Question 49 Regarding the Government’s answer to question # 49, would the Government please elaborate on the statement “The Government will not permit telephone triage before dispatching a technician”? Would the Government agree that it is frequently in their best interest in returning a system to full functionality as quickly as possible to spend a few minutes on the phone answering some basic questions such as what lights are on/off, what error messages are present, etc. so long as the 3 hour on-site requirement is still met? These few minutes of phone triage will enable a dispatch with the best qualified resource with the proper parts and will result in the system being restored to full operation in the most expeditious manner.

Government Response:

No. The Government does not agree that it is in its best interest in returning a system to full functionality as quickly as possible to spend time on the phone answering questions about the equipment. Sections C.3.2.3 and C.3.9.7 specify SSA’s hardware requirements regarding contractor failure notification. SSA lacks staffing to additionally visually inspect the hardware and engage in telephone triage.

Question #3 Government Response to Amendment 0005 Question 43 Regarding the Government’s answer to question # 43, would the Government please explain how an offeror can fill in the pricing table for a VTL solution as well as a non VTL solution without drastically increasing the cost of the proposal by proposing both options as Tab C of the pricing Table adds everything together on Tab A and Tab B?

Government Response:

SSA is unclear as to what the original asker of this question meant by “non VTL solution.” If a “non VTL solution” means an Ethernet-based solution, then Section C.3.4.2.6 requires an Upgrade for a “non VTL solution.” CLINs 105-OS-DD-1, 105-OS-DD-2, 105-OS-DD-3, 105-OS-DD-4, and 105-OS-DD-5 should be used to price a VTL solution. CLINS 105-OS-1-DD-10E-UPG, 105-OS-2-DD-10E-UPG, 105-OS-3-DD-10E-UPG, 105-OS-4-DD-10E-UPG, and 105-OS-5-DD-10E-UPG should be used to provide the price difference between a “VTL solution” and a “non VTL solution.” When the Government orders the “non VTL solution,” the UPG CLIN and the VTL CLIN will be ordered. For example, for the “non VTL solution,” the Government will order CLIN 105-OS-DD-1 and 105-OS-1-DD-10E-UPG.

Question #4 Given that 1) the Government has responded with 186 answers to questions that were not posted to a publicly available web site until after COB on Friday, April 12th , 2)these questions and answers were released almost one month after submission of the questions, 3) it wasn’t until the questions and answers were released that the offeror was made aware of that the performance data could be provided in a non-proprietary format as that option was never offered, 4) the publication of these questions and answers significantly alters offeror’s approach, pricing and configurations and 5) additional questions need to be answered from this round, would the Government please extend the due date an extra week until May 1st?

SSA has extended the due date by two weeks until May 8, 2013.

Question #5 Section C.3.3.3.5 The edits SSA made to section 3.3.3.5 have caused us some confusion as to the true number of IOPS required. Originally in subsection 3.3.3.5.3 SSA was asking for an access density of 0.32 for 9TB (9216GB), which would require 2949 IOPS (2949 IOPS / 9216 GB = 0.32 Access Density). The original requirement also included in subsection 3.3.3.5.2 16,000 NFS or CIFS input outputs per second (IOPS), which we interpreted as file system operations (not the same as a physical IOPS).

The new requirement is still asking for an access density of 0.32 for 9TB in subsection 3.3.3.5.3 but now subsection 3.3.3.5.2 requires 16,000 IOPS (no NFS or CIFS caveat).

Does SSA require 2,949 physical IOPS to achieve an access density of 0.32 or does SSA require 16,000 physical IOPS for the 9TB NAS expansion?

SSA requires 2,949 physical IOPS to achieve an access density of 0.32. Section C.3.3.3 has been amended to match the 16,000 IOPS requirement with the Access Density.

Question #6 Section C.3.5.2.8 SSA has requested an upgrade to configure the appliance (Storage Virtualization Appliance OS-1) with an additional 250 TB of usable storage. Should that be treated as a license upgrade to increase the amount of existing storage that can be virtualized by 250 TB or should that be treated as an upgrade to add 250 TB of new storage to SSA’s environment?

Section C.3.5.2.8 should be read as a requirement to increase the amount of existing storage that can be virtualized by 250 TB. See CLIN 106-OS-SVA-250-UPG-1 under the Equipment Tab of the Pricing Tables. The upgrade should include any required software licenses and any required hardware upgrades. Section C.3.5.2.8 has been amended to clarify.

Question #7 Section C.3.5.3.8 SSA has requested an upgrade to configure the appliance (Storage Virtualization Appliance OS-2) with an additional 250 TB of usable storage. Should that be treated as a license upgrade to increase the amount of existing storage that can be virtualized by 250 TB or should that be treated as an upgrade to add 250 TB of new storage to SSA’s environment?

Section C.3.5.3.8 should be read as a requirement to increase the amount of existing storage that can be virtualized by 250 TB. See CLIN 106-OS-SVA-250-UPG-2 under the Equipment Tab of the Pricing Tables. The upgrade should include any required software licenses and any required hardware upgrades. Section C.3.5.3.8 has been amended to clarify.

Question #8 Section 3.6.2.10 SSA has requested an upgrade to configure the appliance (Continuous Data Protection) with an additional 250 TB of usable storage. Should that be treated as a license upgrade to increase the amount of existing storage that can be replicated by 250 TB or should that be treated as an upgrade to add 250 TB of new storage to SSA’s environment?

Section 3.6.2.10 should be read as a requirement for a license upgrade to increase the amount of existing storage that can be replicated by 250 TB and an upgrade to add 250 TB of new storage to the Continuous Data Protection appliance. Section C.3.6.2.10 has been amended to clarify.

Question #9 Government Response to Amendment 0005 Question 12 SSA stated that “Currently 72 TB of data is being replicated from the NCC to the SSC”. Does that mean on average 72TB of data changes are being sent from NCC to SSC daily or that SSA is only replicating 72TB of its storage footprint?

The 72 TB reference in the Response Question 12 was a mistake. The current amount of storage being replicated between the NCC and the SSC is 107 TB. Over time, the amount of storage being replicated between the NCC and SSC will change. This means it is the total that SSA is currently replicating (107 TB) of SSA’s total open systems storage footprint. SSA is including a revised version of “Questions and Responses 3” with this amendment, “Questions and Responses 3-R.”

Question #10 Government Response to Amendment 0005 Question 12 The answer Question # 12 references the 72 TB of data being replicated presently. Is this in one (1) storage array? Is the storage being replicated asynchronously in near real-time or in a store/forward manner?

Government Response:

The 72 TB reference in the Response Question 12 was a mistake. The current amount of storage being replicated between the NCC and the SSC is 107 TB. This is the total on all storage subsystems (arrays).

SSA is unclear as to exactly what is meant by “near real-time or a “store/forward.” SSA assumes “near real-time” refers to shorter Recovery Point Objectives (RPOs) and “store/forward” means longer RPOs. Some of SSA’s storage is replicated asynchronously in near real-time (i.e. RPO of 90 seconds or less) on the EMC DMX and VMAX storage subsystems (arrays). Other SSA storage is replicated asynchronously in a store/forward manner (RPO of 1 hour) on the EMC Clariion storage subsystems (arrays). Refer to RFP SECTION E, Attachment A – “Open Systems Storage Infrastructure” for more detailed information.

Question #11 Government Response to Amendment 0005 Question 25 The answer to Question #25 references training but remains unclear as to where it can be held. Can training be held in contractors’ facility in the Baltimore/Washington metro area?

Yes, a contractor may hold the training at its facility in the Baltimore/Washington metro area. Training can occur at any of the contractor’s CONUS facilities or be a live interactive online class. Each of these offerings is technically acceptable.

Question #12 Government Response to Amendment 0005 Question 29 The answer to Question # 29 references flash storage and 300 GB, but the revised pricing CLIN references 1 TB. Please clarify the following:

· Can the cache memory in the array be expanded by 300 GB as a reasonable substitute (where/when possible)?

· Is the 1 TB of storage subsystem a useable figure? For example [four (4) 400-GB drives laid out in a 3+1 RAID configuration]?

Government Response:

1) No, expanding the cache memory in the storage subsystem (array) by 300 GB is not acceptable. However, SSA has updated Section C.3.3.6.4.5 to provide QLogic Fabric Cache QLE1000 adapter as an option to meet this requirement.

2) Yes, the 1 TB of storage subsystem is a useable storage figure.

Section C.3.3.6.4.5 has been amended to clarify.

Question #13 Government Response to Amendment 0005 Question 186 The answer to Question 186 refers to multiple vendors in each of the three (3) IT subject areas outlined. We are not aware of multiple vendors in these areas and would ask SSA to list the names of those organizations. We assume that EMC Is one of the vendors in each of the three (3) categories and we simply need SSA to list the others.

The Government will not answer this question.

Question #14 Section C.3.2.6 Could the SSA provide the names of its current Hot Air Containment vendors that are compliant with this section?

The Government will not answer this question.

Question #15 Section C.3.3.1.8 Does this utility check configuration on the server or hypervisor level, or does this configuration check storage and make recommendations on how storage should be configured? Can you clarify the intent with the utility?

The “utility check configuration” must include both the Storage Virtualization Appliance (hypervisor) level and storage subsystem level. The intent of this requirement is to ensure servers are setup properly to use the storage infrastructure (i.e. storage virtualization appliances, storage subsystems, SAN switches, and SAN directors).

Question #16 Section C.3.4.4 The RFP refers a “Source” based de-duplication “appliance.” Is the “appliance” referring to hardware and/or software?

Section C.3.4.4 refers to both hardware and software that can provide “Source” based de-duplication. Section C.3.4.4 has been amended to clarify.

Question #17 Section C.3.5.3.5 Is the SSA’s intention to have a metrocluster-like of active-active architecture and provide CO-OP type of operations? If so, what are the distance requirements?

Yes, it is SSA’s intention to have metro cluster with active-active architecture and provide “Continuation of Operations” or “disaster recovery” operations. Instead of distance requirements, SSA instead only has a time delay requirement that is a maximum network latency of eight (8) milliseconds. SSA will maintain the network latency of 8 milliseconds.

Question #18 Section C.3.6 In terms of CDP appliance, what applications will be required for the CDP appliance to protect?

SSA will use CDP alliances to backup applications with large amounts of data (i.e. over 200 TB in size) such as e-mail archiving.

Question #19 Section C.3.7.2.3 This section calls out for continuous local replication and remote replication for 300TB useable storage. How far will data need to be replicated? Does the replication need to be asynchronous or synchronous?

Section C.3.7 does not have any replication requirements. SSA assumes the intended reference was Section C.3.6.2.3, a requirement for OS CDP Appliances. The data needs to be replicated between the NCC and SSC or the NSC or the SSC. The physical locations of the NCC, SSC, and NSC are specified in Section C.3.12.8. The replication will be asynchronous.

Question #20 Government Response to Amendment 0005 Question 26 Can SSA please clarify what protocol is required and version? For example, NFS v3 or SMBv2

SSA plans to use NFS Version 4 and Server Message Block (SMB) Version 1 to connect Network Attached Storage (NAS) to (z/OS) servers.

Question #21 Government Response to Amendment 0005 Question 43 Will SSA provide guidance on the framework for a non-VTL solution? For example, is SSA open to reviewing archiving type solutions that would take the place of a VTL and current tape silos in use today?

Please see the response to Question 3 above. SSA is uncertain as to what is meant by “archiving type solutions that would take the place of a VTL and current tape silos in use today.” SSA requires both a “VTL solution” and a “non-VTL solution” as understood and explained in Question 3. The De-duplication Appliances (Section 3.4) will be used to support Symantec NetBackup and Oracle RMAN backup software. The only “archiving type solutions” requirement as understood by SSA is defined in Section C.3.4.2.4 and will be used with Symantec NetBackup software.

Question #22 Government Response to Amendment 0005 Question 3 Clarification: Is this FC/IP replication or TCP/IP ONLY for the replication network?

SSA’s Replication Network is TCP/IP ONLY.

Question #23 Is there a framework to quote the large and small data center shutdowns? How many of the OS1 through OS6 configurations will be installed in years 1 through 10 for each size data centers (large and small)?

Government Response:

SSA provided a sample Statement of Work for a shutdown services for both large and small data centers with the response to Question 66 in Amendment 005. SSA considers the NCC, NSC, and SSC large data centers. SSA considers the ROCCs and the WBDOC small data centers. Refer to RFP Section C.3.12.8 for the physical locations. RFP SECTION E -Attachment A and SECTION B Pricing Tables can be used to estimate the amount of equipment that will be installed at each type of data center. SSA plans to replace the equipment listed in Attachment A in the year listed in the “End of Warranty/Maintenance Year” column.

In the small data centers, SSA currently estimates operating one (1) storage subsystem, 4 to 6 SAN Type OS-1 SAN switches, and one (1) data de-duplication appliance. SSA estimates the remaining equipment listed in the pricing table will be split between the NCC, NSC, and SSC. After Contract Year 1, the amount of new equipment installed at the NCC, if any, is estimated to be minimal.

The pricing table contains estimates of the number of OS1 through OS6 configurations that will be installed in years 1 through 5. No hardware or software will be ordered in years 6 through 10, as these years are reserved for services only.

Question #24 Section C.3.3.6 This section appears to have been mis-numbered. In the last revision from the Government, Section 3.3.6.2 was followed by section 3.3.6.3, which began “The Contractor shall provide a quantity of two blades upgrades for SAN Type OS-3 that provide encryption of data on disk…” This language now appears in Section 3.3.6.2.1, but was not highlighted as a change in the latest version of the RFP. The following section (now Section 3.3.6.3) was previously numbered as 3.3.6.4 and its subsections 3.3.6.4.1, 3.3.6.4.2, etc. accordingly. Please clarify if the numbering change was intentional or if it is a simple typographical error.

The numbering change was an error caused by the word processing software used. This has been corrected, and Section C.3.3.6 has been changed back to the original numbering.

Question #25 We respectfully request an extension if all of the new follow-up questions submitted by 12 p.m. EST on April 17th 2013 aren’t answered by 12 p.m. EST on April 19th 2013, especially since we need to begin publishing on Tuesday morning, April 23rd 2013.

Government Response:

SSA has extended the due date by two weeks until May 8, 2013.

Question #26 Government Response to Amendment 0005 Question 29 Question #29 of the Q&As released on April 12th references 3.3.6.4.5; however, there is no 3.3.6.4.5 in the newly amended RFP document (as amended in amendment 9). We have noticed in the newly amended RFP document, there appears to be a requirement numbering issue. When comparing the newly amended RFP to the previous version of the RFP, it appears that 3.3.6.2.1 should have really been 3.3.6.3; that 3.3.6.3 should have really been 3.3.6.4 and that 3.3.6.3.1 through 3.3.6.3.5 should have really been 3.3.6.4.1 through 3.3.6.4.5, respectively. In other words, we do not believe that any of the previous numbering should have changed in these requirement areas – the Government has just modified existing requirements.

Refer to the response to Question 24 above. The numbering issue has been corrected.

Question #27 Section C.3.9.3, Government Response to Amendment 0005 Questions 112 - 114 Understanding that there are multiple ways of designing a solution to avoid “Loss of Data” and the Government has not provided any guidance as to the level of desired data protection which is deeply concerning, as well as the technical evaluation in section F-3 states that it’s a Pass/Fail evaluation, can the Government state how the various technical proposal responses will be evaluated against each other when the approaches are technically different, and revise C.3.9.3 to state that failure must be the offerors hardware or software?

Government Response:

Technical proposals regarding Section C.3.9.3 will not be “evaluated against each other.” Technical proposals will be evaluated against the solicitation to determine whether the proposal demonstrates that the proposed hardware and software meets the requirements as stated regarding the “Loss of Data Warranty.” If the proposal demonstrates that the terms of “Loss of Data Warranty” are met, then SSA will give a “pass” rating to the offeror for that requirement.

Each Offeror should design the level of data protection in a way that the Offeror is satisfied that loss of data shall not occur during the life of this contract. SSA has added a definition of “Loss of Data” to Section C.2.2 to clarify. SSA has also amended Section C.3.9.3 to limit the warranty to apply only to a failure of hardware or software ordered under the resulting contract.

Question #28 Government Response to Amendment 0005 Question 149 In table 1, it appears that the government has deleted both “Port factory upgrade to FCoE” and “Port Field upgrade to FCoE” for OS-3, OS-4, and OS-5 (and indicated N/A for all of these items). Did the government intend to only delete the “Port factory upgrade to FCoE” for OS-3 , OS-4, and OS-5?

No. The Government did intend to delete all the FCoE upgrades for OS-3, OS-4, and OS-5. The Pricing Tables in SECTION B have been updated.

Question #29 Government Response to Amendment 0005 Question 149 In the “equipment Price” tab of the amended pricing worksheet released on April 12th 2013, did the Government intend to delete CLINs “103-0S-3-4-FC-UPG”, “103-0S-4--4-FC-UPG”, and “103-0S-5-4-FC-UPG” (rows 35-37)? Or, did the Government instead intend to delete CLINS “103-OS-3-4-FCOE-UPG-1”, “103-OS-4-4-FCOE-UPG-1”, “103-OS-5-4-FCOE-UPG-1 (rows 40-42)”?

No, the Government did not intend to delete CLINs “103-0S-3-4-FC-UPG,” “103-0S-4--4-FC-UPG,” or “103-0S-5-4-FC-UPG” (rows 35-37). The Equipment Pricing Table in SECTION B has been updated to reinsert CLINs “103-0S-3-4-FC-UPG,” “103-0S-4--4-FC-UPG,” and “103-0S-5-4-FC-UPG” and to remove CLINS “103-OS-3-4-FCOE-UPG-1,” “103-OS-4-4-FCOE-UPG-1,” and “103-OS-5-4-FCOE-UPG-1 (rows 40-42).”

Question #30 Government Response to Amendment 0005 Question 155 In the Government Response to question #155, there is a statement clarifying CLIN 217 that states "Estimated Quantities are per hour. It will be up to each offeror to determine the level of effort required". Would the Government please remove the statement "Estimated Quantities are per hour". We believe this is an error because CLIN 217 is “by year”.

Yes. CLIN 217 is by Year. The answer to Question 155 included in the revised “Questions and Responses 3-R” has been corrected.

Question #31 Government Response to Amendment 0005 Question 172 Section 3.2.11, Table 1 indicates a maximum desired usable capacity of 2PB each for OS1 and OS2. Clarification question #172 indicates that this usable capacity is to be provided by a single storage subsystem and by definition of the clarification of question #172, federated or multiple storage subsystems may not be used to achieve the desired usable capacities for OS1 and OS2. We believe that the requirement of 2PB usable for a single storage device is detrimental to open competition and would seem to favor a single vendor. Would the government be willing to remove the requirement of a single storage system supporting 2PB usable and allow the use of multiple federated systems providing there is no detriment to any of the performance requirements?

The Government’s market research has found multiple storage vendors that can provide one storage subsystem with 2 PB of Useable Storage. However, the Government has amended the maximum Useable Storage capacities in Table 1 for Storage Subsystem Type OS-1 and Storage Subsystem Type OS-2 to 1.5 PB. The Government will not change its requirements to allow federated or multiple storage subsystems to achieve the desired usable capacities or any of the requirements in Section C.3.3.2 for Storage Subsystem Type OS-1, Storage Subsystem Type OS-2, Storage Subsystem Type OS-3, Storage Subsystem Type OS-4 and Storage Subsystem Type OS-5.

Question #32 Government Response to Amendment 0005 Question 172 Section 3.2.11, Table 1 indicates a maximum desired usable capacity of 2PB each for OS1 and OS2. How was this maximum usable capacity determined? Is it acceptable to reach this capacity with Thin Provisioned storage?

Useable Storage is defined in Section C.2.24. Useable Storage does not include capacity saved by using Thin Provisioned software. Section C.2.2 has been updated to clarify the definition of Useable Storage. It is not acceptable to reach this capacity with Thin Provisioned storage.

Question #33 Government Response to Amendment 0005 Question 186 Question #186 outlines the use of the storage virtualization technologies identified Section 3.5 for the purpose of migration from the existing storage systems to the new. How will this impact the required migration services requested? Will this technology be required from day one or will it be implemented as part of the migration strategy in successive years? If the migration requirements are met in separate sections of the proposal will this technology be a requirement?

Storage virtualization appliances can be a tool used by the contractor to complete the required migration services. Storage virtualization appliances are required beginning day one. Storage virtualization appliances will remain a requirement regardless of how the migration requirements are met.

Question #34 Government Response to Amendment 0005 Questions 157 and 183 The Government Responses to Questions #157 and #183 appear to be in conflict. In response to Question #157, the Government states:

“4) Yes, the table requires pricing per-terabyte.

5) No, data migration pricing in any other manner is not acceptable. The pricing is based on the requirements outlined in Section C.3.8.4.”

In response to Question #183, the Government states:

“The requirement has been amended to give offerors the choice to price either per ‘1TB’ or by ‘number of servers’ to be migrated.”

Are we correct in assuming that the Government’s true intent was captured in the response to Question #183?

The response to Amendment 0005 Questions 157 and 183 have been amended to state that pricing is based on the requirements as originally outlined in Section C.3.8.4. The requirements in Section C.3.8.4 are subsystem-based requirements. As a result, the pricing for Migration Services will remain in 1 TB increments. Section C.3.8.4 and the Pricing Tables in SECTION B have been amended to clarify.

Question #35 Government Response to Amendment 0005 Questions 14, 26, 28, 42, 94, 106, 146 & 159 The Government Responses to Questions #14, #26, #28, #42, #94, #106, and #146 all appear to contradict the Government response to Question #159. In the Government responses to Questions #14, #26, #28, #42, #94, #106, and #146, the existence of a current NAS storage environment is stated, as well as a future NAS requirement. However, the Government Response to Question#159 states:

“3) The type of data to be migrated will be fiber channel or block-format.”

As NAS data is neither fiber channel, nor block format (it is instead, file format data) is it the Government’s intention that the existing NAS data not be migrated, during the term of the contract? If not, please provide the quantity and location(s) of the NAS data to be migrated, as well as the year(s) in which its migration is planned

Government Response:

Yes, the Government’s intention is that NAS data will not be migrated during the term of this contract.

The response to Amendment 0005 Questions #42 has been updated to replace block with file. The response to Amendment 0005 Questions #159 has also been updated to remove “or block level.”

Question #36 Government Response to Amendment 0005 Questions 157 & 159 The Government Responses to Questions #157 and #159 are contradictory. The response to Question #159 states:

“The largest migration will occur in Contract Year Two when SSA intends to move from the NCC to the NSC.”

However, the response to Question #157 states 1,000TB migration requirements in Year 2, Year 3, and Year 5. If the largest migration is to occur in Year 2, How much data may the vendor may the vendor actually expect to migrate, during that year?

Government Response:

The response to Amendment 0005 Questions 159 has been updated to “The largest migrations will occur in Contract Years Two and Year Three when SSA intends to move from the NCC to the NSC and in Year Five when the warranty on a large number of subsystems will expire.”

Question #37 Government Response to Amendment 0005 Question 159 Thank you for providing the attached SSA Server List document. While the listing does provide the server make/model, operating system and allocated storage for most of the servers listed, it does not map the servers to either physical location, or their attached (either SAN or NAS) storage. Could that mapping please be provided?

Also, is it correct to assume that these are all individual physical servers, and that the list does not include virtual servers?

The server list (of physical servers) has been updated to include physical location, total number of CPUs and the type of storage platform (SAN or NAS).

Question #38 How many total CPUs by Operating System (AIX, Unix, Linux, Windows)?

See the server list provided in the response to Question 37 above.

Question #39 What is the weight of the 1 storage subsystem cabinet (approx..)?

SSA is unclear as to what Section this question applies. If it applies to Section C.3.8.6 “Moving Services,” then the weight of one storage subsystem cabinet depends on the make and model of storage subsystem proposed. The Contractor will not be required to move currently installed EMC equipment.

Question #40 What is the description of the cabinet (standard size or different)?

SSA is unclear as to reason for this question. SSA assumes the reason for the question is to determine how to price “Moving Services” in Section C.3.8.6. Cabinet sizes will depend on what is proposed by the offeror. See Section C.3.2.5 for the maximum acceptable cabinet sizes.

Question #41 To best cost the move accurately, can we understand what a “system” is comprised of?

Government Response:

SSA has not use the word “System” in RFP Section 3.8.6 Moving Services. Instead, the word “system” was used in one of the previous questions (Amendment 0005 Question 89). SSA believes “System” ” in Amendment 0005 Question 89 refers to a storage subsystem.

In general, a storage subsystem is comprised of disk drives, solid-state drives, storage controllers, power supplies, cache in form of both volatile random-access memory and non-volatile flash memory, and disk enclosures. The exact size of the storage subsystem will depend on what is proposed by the Offeror.

Question #42 203-2 Q1 Please clarify the requirements needed for the “Small Data center shut down”?

Please see the answer to Question 23 above. Section 3.8.5 has been updated to clarify this requirement.

Question #43 203-1 Q2 Please clarify the requirements needed for the “Large Data center shut down”?

Please see the answer to question 23.

Question #44 211 Q3 Will the contract holder need to erase storage from legacy EMC equipment?

No. The Contractor will not need to erase data from currently installed EMC equipment.

Question #45 Section C.3.3.2.8 & Table 1 In Table 1 and in section 3.3.2.8, SSA eliminated configs for OS3, OS4 and OS5. However line items 40-42 are still on the price chart.

The pricing tables in SECTION B have been updated to remove factory upgrades for Fiber Channel over Ethernet (FCoE) ports for Storage Subsystem Type OS-3, Storage Subsystem Type OS-4, and Storage Subsystem Type OS-5.

Question #46 Section C.3.3.2.10 & Table 1 In Table 1 and in section 3.3.2.10, SSA eliminated configs for OS3, OS4 and OS5. However line items 51-53 are still on the price chart.

The pricing tables in SECTION B have been updated to remove field upgrades for Fiber Channel over Ethernet (FCoE) ports for Storage Subsystem Type OS-3, Storage Subsystem Type OS-4 and Storage Subsystem Type OS-5.

Question #47 Section C.3.3.2.7.3, C.3.3.2.7.4 & C.3.3.2.7.5 Line items 35-37 were eliminated on the price chart. However, 3.3.2.7.3, 3.3.2.7.4 and 3.3.2.7.5 remain in the RFP.

Line items 35-37 were mistakenly removed in Amendment 0005. See the response to Question 29 above.

image2.emf

DASD Installed Containment Strategy

18" by 6"

DASD Installed

Cold Aisle

Hot Aisle

Front of Cabinet

Back of Cabinets

24 Inch Max

Hot Exhaust Air

Cold Air

Front of Cabinet

Cold Air

24 Inch Max

Cold Aisle

DASD DASD

Top Exhaust Top Exhaust

Containment Curtain Containment Curtain

Hot Exhaust Air into Ceiling image3.emf

Updated Server List Sheet1

Server Number NAS or SAN Location Storage Subsystem Serial Number Application Server Operating System Server Make Model Number of CPUs Allocated Storage in GB

1 SAN NCC APM00093600058 Net Backup Media Server Windows Dell R900 4 7,649.94

2 SAN NCC APM00093600058 Net Backup Media Server Windows Dell R900 4 7,649.92

3 SAN NCC APM00093600058 Net Backup Media Server Windows Dell R900 4 8,785.29

4 SAN NCC APM00093600058 Net Backup Media Server Windows Dell R900 4 8,785.29

5 SAN NCC APM00093600058 Net Backup Media Server Windows Dell R900 4 7,966.26

6 SAN NCC APM00093600058 Net Backup Media Server Windows Dell R900 4 7,737.01

7 SAN NCC APM00093600058 Net Backup Media Server Windows Dell R900 4 14,020.94

8 SAN NCC APM00093600058 Net Backup Media Server Windows Dell R900 4 12,772.80

9 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 8,998.31

10 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 8,278.32

11 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 7,753.32

12 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 7,753.32

13 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 7,753.32

14 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 7,753.32

15 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 9,650.35

16 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 8,930.36

17 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 8,930.36

18 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 8,930.36

19 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 8,930.36

20 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 8,930.36

21 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 8,789.65

22 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 8,069.66

23 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 8,069.66

24 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 8,069.66

25 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 8,069.66

26 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 8,069.66

27 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 1,979.80

28 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 1,979.80

29 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 5,992.69

30 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 5,272.70

31 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 5,272.70

32 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 5,272.70

33 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 5,272.70

34 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 5,272.70

35 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 9,164.02

36 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 8,444.03

37 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 8,444.03

38 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 8,444.03

39 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 8,444.03

40 SAN NCC APM00093600058 Vmware ESX server OS Dell R710 4 8,444.03

41 SAN SSC APM00093600059 Net Backup Media Server Windows Dell R900 4 10,298.07

42 SAN SSC APM00093600059 Net Backup Media Server Windows Dell R900 4 10,298.05

43 SAN SSC APM00093600059 Net Backup Media Server Windows Dell R900 Unkown 80.00

44 SAN SSC APM00093600059 Net Backup Media Server Windows Dell R900 Unkown 1,912.00

45 SAN SSC APM00093600059 Vmware ESX server OS Dell R710 4 4,205.77

46 SAN SSC APM00093600059 Vmware ESX server OS Dell R710 4 4,205.77

47 SAN SSC APM00093600059 Vmware ESX server OS Dell R710 4 4,205.77

48 SAN SSC APM00093600059 Vmware ESX server OS Dell R710 4 9,223.83

49 SAN SSC APM00093600059 Vmware ESX server OS Dell R710 4 4,205.77

50 SAN SSC APM00093600059 Vmware ESX server OS Dell R710 4 5,122.16

51 SAN SSC APM00093600059 Vmware ESX server OS Dell R710 4 5,122.16

52 SAN SSC APM00093600059 Vmware ESX server OS Dell R710 4 5,122.16

53 SAN SSC APM00093600059 Vmware ESX server OS Dell R710 4 5,122.16

54 SAN SSC APM00093600059 Vmware ESX server OS Dell R710 4 9,223.83

55 SAN SSC APM00093600059 Vmware ESX server OS Dell R710 4 2,544.47

56 SAN SSC APM00093600059 Vmware ESX server OS Dell R710 4 2,544.47

57 SAN SSC APM00093600059 Vmware ESX server OS Dell R710 4 2,544.47

58 SAN SSC APM00093600059 Vmware ESX server OS Dell R710 4 3,156.27

59 SAN SSC APM00093600059 Vmware ESX server OS Dell R710 4 2,544.47

60 SAN SSC APM00093600059 Vmware ESX server OS Dell R710 4 4,134.50

61 SAN SSC APM00093600059 Vmware ESX server OS Dell R710 4 4,134.50

62 SAN SSC APM00093600059 Vmware ESX server OS Dell R710 4 4,134.50

63 SAN SSC APM00093600059 Vmware ESX server OS Dell R710 4 4,134.50

64 SAN SSC APM00093600059 Vmware ESX server OS Dell R710 4 4,134.50

65 SAN NCC APM00101902940 Share Point Windows Dell R900 4 23,040.50

66 SAN NCC APM00101902940 Share Point Windows Dell R900 Unkown 23,040.50

67 SAN NCC APM00101902940 Share Point Windows Dell R900 4 22,920.50

68 SAN NCC APM00101902940 Share Point Windows Dell R900 Unkown 22,920.50

69 SAN NCC APM00101902940 Vmware ESX server OS Dell R710 2 4,094.60

70 SAN NCC APM00101902940 Vmware ESX server OS Dell R710 2 4,094.60

71 SAN NCC APM00101902940 Vmware ESX server OS Dell R710 2 4,094.60

72 SAN NCC APM00101902940 Vmware ESX server OS Dell R710 2 4,094.60

73 SAN NCC APM00101902940 Vmware ESX server OS Dell R710 2 4,094.60

74 SAN NCC APM00101902940 Vmware ESX server OS Dell R710 2 4,094.60

75 SAN NCC APM00101902940 Vmware ESX server OS Dell R710 2 4,094.60

76 SAN NCC APM00101902940 Vmware ESX server OS Dell R710 4 7,875.49

77 SAN NCC APM00101902940 Vmware ESX server OS Dell R710 4 7,875.49

78 SAN NCC APM00101902940 Vmware ESX server OS Dell R710 4 5,827.49

79 SAN NCC APM00101902940 Vmware ESX server OS Dell R710 4 5,827.49

80 SAN NCC APM00101902940 Smarts Solaris Unkown Unkown 3,108.26

81 SAN NCC APM00101902940 Smarts Solaris Unkown Unkown 3,111.24

82 SAN NCC APM00101902940 Unkown Solaris Unkown 2 700.00

83 SAN NCC APM00101902940 Oracle HPUX Unkown Unkown 600.00

84 SAN NCC APM00101902940 Oracle Solaris Unkown Unkown 600.00

85 SAN NCC APM00101902940 Oracle HPUX Unkown Unkown 2,276.07

86 SAN NCC APM00101902940 Unkown Solaris Unkown Unkown 150.00

87 SAN NCC APM00101902940 Unkown Solaris Unkown Unkown 1,550.00

88 SAN NCC APM00101902940 Unkown Solaris Unkown Unkown 1,550.00

89 SAN NCC APM00101902940 Tivoli Windows Unkown 2 1,500.00

90 SAN NCC APM00101902940 Tivoli Windows Unkown 2 500.00

91 SAN NCC APM00101902940 Tivoli Windows Unkown 2 500.00

92 SAN NCC APM00101902940 Tivoli Windows Unkown 2 500.00

93 SAN NCC APM00101902940 Tivoli Windows Unkown 2 500.00

94 SAN NCC APM00101902940 Tivoli Windows Unkown 2 500.00

95 SAN NCC APM00101902940 Tivoli Windows Unkown 2 500.00

96 SAN NCC APM00101902940 Tivoli Windows Unkown 4 500.00

97 SAN NCC APM00101902940 Tivoli Windows Unkown 4 650.00

98 SAN NCC APM00101902940 Oracle HPUX Unkown Unkown 3,968.89

99 SAN NCC APM00101902940 Oracle HPUX Unkown Unkown 3,933.49

100 SAN NCC APM00101902940 Oracle HPUX Unkown Unkown 5,710.25

101 SAN NCC APM00101902940 Unkown Solaris Unkown Unkown 300.00

102 SAN NCC APM00101902940 Unkown Solaris Unkown Unkown 150.00

103 SAN NCC APM00101902940 Oracle HPUX Unkown Unkown 980.34

104 SAN NCC APM00101902940 Unkown Solaris Unkown Unkown 0.00

105 SAN NCC APM00101902940 Unknown Solaris Unkown Unkown 1,800.00

106 SAN NCC APM00101902940 Unknown Solaris Unkown Unkown 1,750.00

107 SAN NCC APM00101902940 Storage Management Windows Dell 2900 2 2,350.52

108 SAN NCC APM00101902940 Oracle Solaris Unkown Unkown 325.00

109 SAN NCC APM00101902940 Oracle Linux Unkown Unkown 7,363.00

110 SAN NCC APM00101902940 Oracle Linux Unkown Unkown 7,362.00

111 SAN NCC APM00101902940 Oracle Linux Unkown Unkown 1,218.00

112 SAN NCC APM00101902940 Oracle Linux Unkown Unkown 1,218.00

113 SAN NCC APM00101902940 Oracle Linux Unkown Unkown 16,384.00

114 SAN NCC APM00101902940 Oracle Linux Unkown Unkown 16,864.82

115 SAN NCC APM00101902940 Oracle Linux Unkown Unkown 16,864.82

116 SAN NCC APM00101902940 Oracle Linux Unkown Unkown 100,703.60

117 SAN NCC APM00101902940 Oracle Linux Unkown Unkown 725.02

118 SAN NCC APM00101902940 Unknown Solaris Unkown Unkown 1,424.00

119 SAN NCC APM00101902940 Unknown Solaris Unkown Unkown 2,110.00

120 SAN NCC APM00101902940 Unknown Solaris Unkown Unkown 2,122.00

121 SAN NCC APM00101902940 Net Backup Media Server Windows Dell R710 2 4,094.60

122 SAN NCC APM00101902940 Net Backup Media Server Windows Dell R710 2 4,094.60

123 SAN NCC APM00102100244 Microsoft Hyper-V Windows Unkown Unkown 1,190.67

124 SAN NCC APM00102100244 Microsoft Hyper-V Windows Unkown Unkown 1,190.67

125 SAN NCC APM00102100244 Microsoft Hyper-V Windows Unkown Unkown 1,190.67

126 SAN NCC APM00102100244 Microsoft Hyper-V Windows Unkown Unkown 1,190.67

127 SAN NCC APM00102100244 Microsoft Hyper-V Windows Unkown Unkown 1,190.67

128 SAN NCC APM00102100244 Microsoft Hyper-V Windows Unkown Unkown 1,190.67

129 SAN NCC APM00102100244 Net Backup Media Server Windows Unkown Unkown 1,024.00

130 SAN NCC APM00102100244 Net Backup Media Server Windows Unkown Unkown 1,024.00

131 SAN NCC APM00102100244 Vmware ESX server OS Dell R710 4 8,998.31

132 SAN NCC APM00102100244 Vmware ESX server OS Dell R710 4 8,278.32

133 SAN NCC APM00102100244 Vmware ESX server OS Dell R710 4 7,753.32

134 SAN NCC APM00102100244 Vmware ESX server OS Dell R710 4 7,753.32

135 SAN NCC APM00102100244 Vmware ESX server OS Dell R710 4 7,753.32

136 SAN NCC APM00102100244 Vmware ESX server OS Dell R710 4 7,753.32

139 SAN NCC APM00102100244 Unkown Windows Unkown Unkown 825.00

140 SAN NCC APM00102100244 WebSphere Solaris Unkown Unkown 1,500.00

141 SAN NCC APM00102100244 Net Backup Media Server Solaris Oracle M5000 Unkown 1,255.62

142 SAN NCC APM00102100244 Storage Management Windows Dell 2900 2 2,350.52

143 SAN NCC APM00102100244 Unkown Solaris Unkown Unkown 4,026.30

144 SAN NCC APM00102100244 Net Backup Master Server Solaris Oracle T2000 Unkown 3,989.22

145 SAN NCC APM00102100244 Net Backup Master Server Solaris Oracle T2000 Unkown 255.62

146 SAN NCC APM00102100244 Storage Management Windows Dell 2900 Unkown 196.58

147 SAN NCC APM00102100244 Net Backup Master Server Solaris Oracle T2000 Unkown 255.62

148 SAN NCC APM00102100244 Oracle Financials Solaris Oracle T5120 Unkown 1,100.00

149 SAN NCC APM00102100244 Oracle Linux Unkown Unkown 7,014.95

150 SAN NCC APM00102100244 Oracle Linux Unkown Unkown 7,014.95

151 SAN NCC APM00102100244 Oracle Linux Unkown Unkown 7,007.94

152 SAN NCC APM00102100244 Oracle Linux Unkown Unkown 7,007.94

153 SAN NCC APM00102100244 Oracle HPUX Unkown Unkown 250.00

154 SAN NCC APM00102100244 Oracle Solaris Unkown Unkown 250.00

155 SAN NCC APM00102100244 Oracle HPUX Unkown Unkown 12,326.59

156 SAN NCC APM00102100244 Oracle HPUX Unkown Unkown 12,326.59

157 SAN NCC APM00102100244 Oracle HPUX Unkown Unkown 250.00

158 SAN NCC APM00102100244 Net Backup Master Server Solaris Oracle T2000 Unkown 6,136.24

159 SAN NCC APM00102100244 Net Backup Master Server Solaris Oracle T2000 Unkown 6,136.24

160 SAN NCC APM00102100244 Net Backup Master Server Solaris Oracle T2000 Unkown 200.00

161 SAN NCC APM00102800007 Unkown Solaris Unkown Unkown 16,508.89

162 SAN NCC APM00102901875 Unkown Solaris Unkown Unkown 1,814.65

163 SAN NCC APM00102901875 Unkown Solaris Unkown Unkown 3,421.99

164 SAN NCC APM00102901875 Unkown Solaris Unkown Unkown 5,007.60

165 SAN NCC APM00102901875 Unkown Solaris Unkown Unkown 1,751.98

166 SAN NCC APM00102901875 Oracle Linux Unkown Unkown 7,343.00

167 SAN NCC APM00102901875 Oracle Linux Unkown Unkown 7,343.00

168 SAN NCC APM00102901875 Oracle Linux Unkown Unkown 250.00

169 SAN NCC APM00102901875 Oracle Solaris Unkown Unkown 8,000.00

170 SAN NCC APM00102901875 Virtual Desktop Infrastructure ESX server OS Dell R710 Unkown 1,365.33

171 SAN NCC APM00102901875 Virtual Desktop Infrastructure ESX server OS Dell R710 Unkown 1,365.33

172 SAN NCC APM00102901875 Virtual Desktop Infrastructure ESX server OS Dell R710 Unkown 1,365.33

173 SAN SSC APM00103200945 Document Management Architecture Solaris Unkown 1 2,000.00

174 SAN SSC APM00103200945 Document Management Architecture Solaris Unkown Unkown 2,600.00

175 SAN SSC APM00103200945 Document Management Architecture Solaris Unkown 1 2,005.00

176 SAN SSC APM00103200945 Document Management Architecture Solaris Unkown 2 1,200.00

177 SAN SSC APM00103200945 Document Management Architecture Solaris Unkown 2 1,200.00

178 SAN SSC APM00103200945 Document Management Architecture Solaris Unkown 2 1,200.00

179 SAN SSC APM00103200945 Share Point Windows Unkown Unkown 27,828.59

180 SAN SSC APM00103200945 Share Point Windows Unkown Unkown 27,828.59

181 SAN SSC APM00103200945 Email Archiving Windows Dell R710 2 18,432.00

182 SAN SSC APM00103200945 Unkown Windows Unkown 4 7,337.00

183 SAN SSC APM00103200945 Vmware ESX server OS Dell R710 Unkown 2,201.16

184 SAN SSC APM00103200945 Vmware ESX server OS Dell R710 Unkown 2,201.16

185 SAN SSC APM00103200945 Vmware ESX server OS Dell R710 Unkown 2,201.16

186 SAN SSC APM00103200945 Vmware ESX server OS Dell R710 Unkown 2,201.16

187 SAN SSC APM00103200945 Vmware ESX server OS Dell R710 Unkown 2,201.16

188 SAN SSC APM00103200945 Vmware ESX server OS Dell R710 Unkown 2,201.16

189 SAN SSC APM00103200945 unkown Solaris Unkown Unkown 2,201.16

190 SAN SSC APM00103200945 Vmware ESX server OS Dell R710 Unkown 2,201.16

191 SAN SSC APM00103200945 Vmware ESX server OS Dell R710 Unkown 2,201.16

192 SAN SSC APM00103200945 Vmware ESX server OS Dell R710 Unkown 2,201.16

193 SAN SSC APM00103200945 unkown Solaris Unkown Unkown 50,088.30

194 SAN SSC APM00103200945 unkown Solaris Unkown Unkown 200.00

195 SAN SSC APM00103200945 unkown Windows Unkown 2 501.00

196 SAN SSC APM00103200945 unkown Solaris Unkown Unkown 700.00

197 SAN SSC APM00103200945 unkown Solaris Unkown Unkown 900.00

198 SAN SSC APM00103200945 unkown Solaris Unkown Unkown 900.00

199 SAN SSC APM00103200945 unkown Solaris Unkown Unkown 900.00

200 SAN SSC APM00103200945 unkown Solaris Unkown Unkown 900.00

201 SAN SSC APM00103200945 Net Backup Media Server Windows Dell R710 2 7,057.00

202 SAN SSC APM00103200945 unkown Windows Unkown Unkown 501.00

203 SAN SSC APM00103200945 VMware ESX server OS Dell R710 2 913.00

204 SAN SSC APM00103200945 VMware ESX server OS Dell R710 2 913.00

205 SAN SSC APM00103200945 VMware ESX server OS Dell R710 2 913.00

206 SAN SSC APM00103200945 VMware ESX server OS Dell R710 2 913.00

207 SAN SSC APM00103200945 VMware ESX server OS Dell R710 2 913.00

208 SAN SSC APM00103200945 VMware ESX server OS Dell R710 2 913.00

209 SAN NCC APM00103500246 Internal Messaging Windows Unkown 4 2,248.00

210 SAN NCC APM00103500246 Internal Messaging Windows Unkown 4 2,248.00

211 SAN NCC APM00103500246 Internal Messaging Windows Unkown 4 2,248.00

212 SAN NCC APM00103500246 Internal Messaging Windows Unkown 4 2,248.00

213 SAN NCC APM00103500246 Internal Messaging Windows Unkown 4 2,248.00

214 SAN NCC APM00103500246 Oracle Solaris Unkown Unkown 102,956.30

215 SAN NCC APM00103500564 Email Archiving Windows Dell R710 2 18,432.00

216 SAN NCC APM00103500564 Internal Messaging Windows Unkown 4 2,248.00

217 SAN NCC APM00103500564 Internal Messaging Windows Unkown 4 2,248.00

218 SAN NCC APM00103500564 Internal Messaging Windows Unkown 4 2,248.00

219 SAN NCC APM00103500564 Internal Messaging Windows Unkown 4 2,248.00

220 SAN NCC APM00103500564 Internal Messaging Windows Unkown 4 2,248.00

221 SAN NCC APM00103500564 Oracle Solaris Unkown Unkown 102,956.30

222 SAN NCC APM00103701465 Net Backup Media Server Windows Dell R710 4 7,649.94

223 SAN NCC APM00103701465 Net Backup Media Server Windows Dell R710 4 7,649.92

224 SAN NCC APM00103701465 Net Backup Media Server Windows Dell R710 4 8,785.29

225 SAN NCC APM00103701465 Net Backup Media Server Windows Dell R710 4 8,785.29

226 SAN NCC APM00103701465 Net Backup Media Server Windows Dell R710 4 7,966.26

227 SAN NCC APM00103701465 Net Backup Media Server Windows Dell R710 4 7,737.01

228 SAN NCC APM00103701465 Net Backup Media Server Windows Dell R710 4 14,020.94

229 SAN NCC APM00103701465 Net Backup Media Server Windows Dell R900 4 12,772.80

230 SAN NCC APM00103701465 VMware ESX server OS Dell R710 4 8,998.31

231 SAN NCC APM00103701465 VMware ESX server OS Dell R710 4 8,278.32

232 SAN NCC APM00103701465 VMware ESX server OS Dell R710 4 7,753.32

233 SAN NCC APM00103701465 VMware ESX server OS Dell R710 4 7,753.32

234 SAN NCC APM00103701465 VMware ESX server OS Dell R710 4 7,753.32

235 SAN NCC APM00103701465 VMware ESX server OS Dell R710 4 7,753.32

236 SAN NCC APM00103701465 VMware ESX server OS…