Released RFP Amd 3.doc

HC1028-10-R-2039

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by reference:

The following have been added by full text:

ADDITIONAL CLAUSES

The following Clauses are hereby incorporated by reference:

52.223-18 Contractor Policy to Ban Text Messaging While Driving.

252.211-7008 Use of Government Assigned Serial Number

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF OBJECTIVES

STATEMENT OF OBJECTIVES

CAPACITY SERVICES COMMUNICATIONS

9 September 2010

1.0 INTRODUCTION

Defense Information Systems Agency (DISA) Computing Services (CS) is a provider of information technology solutions for the Department of Defense (DoD). DISA’s DoD customers require processing, storage and communications services for a variety of applications. DISA CS must have the ability to provide communications capacity in a timely manner whenever and wherever the requirements occur. The purpose of this contract is to provide state-of-the-art communications infrastructure capacity to meet new and emerging customer requirements as well as the ability to replace existing DISA communications capacity that has exceeded its technical or economic life, as determined by the Government.

DISA is required by the DoD to enhance communications effectiveness through improved information interoperability. The Assistant Secretary of Defense for Networks and Information Integration (ASD/NII) has articulated a vision for transforming the information environment in the DoD. This vision calls for a move from the centralized thinking and planning currently reflected in the Task, Process, Exploit, Disseminate (TPED) paradigm, to an edge-centered Task, Post, Process, Use (TPPU) approach to information sharing and availability. The envisioned changes represent a fundamental paradigm shift from providing platform centric applications to platform independent, web-enabled, Net-Centric services that require the support of a ubiquitous network environment, that meet the requirements of the end users, and which are highly available, secure, and reliable. As a result of the shift to Net-Centric services, CS will also need to provide communication capabilities at DISA-owned and other approved processing locations.

2.0 PURPOSE

The purpose of this contract is to obtain reliable, responsive, and cost effective communication infrastructure services in both DISA and at other DISA-approved locations. DISA's goal is to obtain a dynamically scalable communications capability utilizing an on-demand service approach for new equipment that can readily adjust to both increases and decreases in communications requirements and which is priced on a utility ("as used") basis. The present communications equipment will be maintained, technically supported and when necessary identified for technical refresh.

For all communications applications the service provider will acquire, install, uninstall, transport, power up configuration, and provide the necessary hardware (including cabinets/racks/cabling), hardware maintenance, communications operating software and services to support the communication infrastructure associated with this contract. Maintenance on communication items currently in operation will be priced individually by unit. All other maintenance items procured through technical refresh or new purchase will be priced based on the service of the port, concurrent users or bandwidth.

For Infrastructure Communications and for all Information Assurance applications, the Government will maintain day-to-day operational control of the communication environment and retain complete oversight responsibility. Operational control includes the installation of all software updates after the initial delivery. However, all operating system software updates should be included in the maintenance covered under this contract.

3.0 SCOPE.

The scope of this project includes the hardware, the communications operating software, network management tools/software, technical services, and operational control required to deliver DISA flexibility to meet the requirements of security, availability, scalability and modernization of the communication infrastructure.

3.1 Maintenance. Contractor shall provide all predictive, remedial, and preventative maintenance as required by the OEM, on all equipment listed on the most recent equipment list. The present equipment list is only a representative list as of the date it was created and may be changed up until time of award. It is typical for the quantities on the list to change monthly, therefore, at the time of award, the most current list of equipment to be maintained will be provided to the contractor and the pricing will be adjusted accordingly. The Government suggested pricing structure is for the equipment to be priced by make and model number. Other pricing structures will be considered and evaluated but must be accompanied by a detailed explanation. Other suggested pricing structures need to be submitted in addition to the mandatory and in addition to the price per make and model structure. The prices proposed for hardware maintenance shall be the same for each particular make and model number within the Continental United States.

The Government reserves the right, at its sole discretion, to add an equipment item for maintenance service. Examples of such items include, but are not limited to, items with expiring warranties, items on expired contracts, relocated items, and new items purchased or leased without maintenance. The Government will give the contractor written notice of its intent to add these items a minimum of thirty (30) days prior to the maintenance start date, unless the contractor agrees to a lesser period of notice. If there is an existing equipment item on contract, the contractor must agree to offer monthly maintenance at the same price as the existing item with the same configuration, i.e., feature codes, etc. If the piece of equipment is new to the contract, the monthly maintenance charge shall be negotiated. The new equipment will be added to the contract via modification. If the equipment is added prior to or on the 15th of the month, the contractor will be paid for the full month. If added after the 15th of the month, the contractor shall not bill until the following month. The contractor shall inspect equipment hardware and operating system software configurations when requested for the purpose of initiating maintenance for the first time under this contract. The contractor shall provide the CO with documentation of the inspection with its quote.

In the event the Government determines that maintenance of an equipment item is no longer required under this contract, the Government will give the contractor written notice thirty (30) days prior to the discontinuance of maintenance services, unless the contractor agrees to a lesser period of notice. If the equipment is deleted prior to or on the 15th of the month, the contractor will not be paid for the month. If deleted after the 15th of the month, the contractor will be paid for the month. This provision in no way restricts the Governments rights under the termination clauses incorporated elsewhere into this contract.

3.1.1 Maintenance Response and Repair Time. The contractor shall arrive within two hours after being notified by the Government, to commence remedial maintenance. All repairs must be completed within four hours after arriving on site. The total time allotted for repair is 6 hours. These response and repair times do not relieve the contractor of their obligation to maintain 99.95% availability requirement.

3.1.2 Maintenance types.

3.1.2.1 Predictive Maintenance. For the purpose of identifying whether equipment is operating in accordance with established specifications, the Contractor shall monitor equipment/component performance using the diagnostics defined in paragraph 3.1.3. If it is determined that a piece of equipment or component is about to fail or is operating outside OEM specifications, the contractor shall initiate action to effect repair even though no call for remedial maintenance has been initiated by the site help desk or shift supervisor.

Contractors shall call the help desk or shift supervisor to inform them that they are coming in for predictive maintenance. Upon arrival on site, the contractor’s technician shall report to the site help desk or shift supervisor.

3.1.2.2 Remedial Maintenance. Calls will be initiated by the site help desk or shift supervisor to the contractor’s toll free help desk service. Contractor shall respond and make the necessary repairs in accordance with the time lines identified in the contract. When necessary, the contractor shall obtain any required OEM support, in accordance with this specification. The contractor shall complete remedial maintenance within the response and repair times identified in paragraph 3.1.1. Upon arrival on site, contractor’s technician shall report to the site help desk or shift supervisor.

3.1.2.3. Preventative Maintenance. Preventive maintenance shall be scheduled as agreed to by the local point of contact (POC) and the contractor. The contractor shall submit a written preventive maintenance schedule for equipment to the Contracting Officer within 30 days after contract award. The schedule is not going to be part of the evaluation since the most current equipment list will be provided to the contractor after contract award. Submission of the schedule may be in contractor format. The preventive maintenance schedule may be modified at no cost by mutual agreement of both parties. The contractor’s proposed schedule shall not be less than that recommended by the OEM and shall include, as a minimum, the following information:

Nomenclature of hardware item.

Model.

Serial Number.

Remote diagnostics and call home capabilities.

Frequency and duration of preventive maintenance, and type of service to be performed.

The preventive maintenance schedule may be modified by mutual agreement of the parties.

The contractor shall commence preventative maintenance for all covered equipment IAW the approved preventative maintenance schedule within 30 days after contract award. Preventative maintenance shall be scheduled outside the prime system operating hours.

If during the course of preventative maintenance an equipment malfunction is identified, the contractor shall report the malfunction to the site POC. The malfunction shall be corrected as a Remedial Maintenance Service (see paragraph 3.1.2.2) and comply with response and repair times (see paragraph 3.1.1).

3.1.3. Remote Diagnostics and Call-Home Support. The Government requires that remote diagnostics and call home support continue for all equipment that currently has such support. Permanent recorded system errors must be immediately called home to remote service center(s).

The contractor shall provide written confirmation that call home and remote diagnostics support for applicable equipment exists within 7 calendar days after start of performance.

Verbal contact between the local maintenance technician and an off-site support technician is not acceptable for remote diagnostics. The contractor must provide a diagnostic system usable by the remote technician.

The dial-in feature may be used, but only with site authorization. The feature must be capable of disabling and be set up to provide the site the ability to enable the feature upon request from the Contractor. The site will monitor the usage of the dial-in feature while the Contractor is using it and disable that feature immediately after the Contractor has completed their usage.

3.2. Technology Refresh Program. The Technology Refresh Program (Tech Refresh) is a consolidated DISA effort to select, acquire, and install enterprise communication hardware and software on a scheduled basis to prevent obsolescence and increase data processing, storage, and transmission capacity on DISA’s NIPR and SIPR networks, the backbones of DISA’s operations. DISA has experienced Information Technology (IT) growth as a result of the new data sharing initiatives and new customer programs. DISA requires a reliable up-to-date communications network to support DISA’s Information Technology Infrastructure. The Tech Refresh Program is designed to replace aging and out of date communications hardware in order to minimize obsolescence in advance of loss of service or hardware failure. DISA estimates the Tech Refresh Program will replace the oldest communication equipment at a rate of 20% per year. Without a viable Tech Refresh Program, DISA will be at risk due to the fact that the communications equipment cannot be serviced beyond its lifecycle. No new equipment will be ordered, or added to the list, by the incumbent in the option years since they will be treated as a transitioning period. The option years will be exercised for sustainment only.

Government owned property shall not be used for trade-in. The Government Defense Reutilization and Marketing Office (DRMO) disposal procedures shall be followed.

3.2.1. The Tech Refresh Program has three parts: Continuation, Software Refresh and Modernization. These parts are defined as follows:

a. Continuation – replacement of existing communication hardware with the same type or newer equipment.

b. Software refresh – replacement of existing communication programs with new and/or updated software versions.

c. Modernization – conversion of existing systems and migration to the latest communication technology

3.2.2. Industry Standards. Implementation of components of the Information Technology Infrastructure Library (ITIL) will improve overall management of DISA’s communication infrastructure. Companies and Government agencies that have followed the methodologies of these models have improved their service and the reliability of their communication infrastructure and reduced their long-term costs. DISA has always had a technical refresh program of some level; however, the Government is now requesting contractors propose a solution that will implement an all inclusive schedule. The following ITIL principles should be included in the Tech Refresh Program: Change Management, Configuration Management, Asset Management and Release Management.

3.2.2.1. Change Management. An established process for handling change to the communication infrastructure on a continual basis shall be developed. The contractor’s change management process must be provided in writing as part of their tech refresh plan. Over an eight year period (5 year base with three option years) technologies will change, software will be revised, and hardware will be phased out by the manufactures. By having a process in place to handle these inevitable events time and money can be saved. It will also be necessary to incorporate DISA customer requests for new or revised functionality. Changes in focus and/or mission of some or all the DISA business processes will play a role in the type of changes that may need to be incorporated into Tech Refresh Program over an eight year span. The tech refresh program plan/change management process will specifically address end of life and unsupportable issues which may occur during the life of this contract. To minimize risk, the tech refresh program plan for training system administrators on the new emerging technologies needs to be part of the contractor’s proposed Tech Refresh Program.

3.2.2.2. Configuration Management. An established process for managing the infrastructure’s communication configuration shall be developed by the contractor and included in the tech refresh program plan. One method to reduce the cost of Configuration Management which the Government strongly supports, but is open to other ideas, is to reduce the types of hardware. Maintaining the configurations over the eight year period with fewer types of hardware will aid in reducing the overall complexity of the infrastructure. DISA expects this to consequently reduce the number of hardware failures and trouble tickets because less time will be spent on issue resolution.

3.2.2.3. Asset Management. An established process for handling asset recovery and redeployment shall be developed by the contractor and included in the tech refresh program plan. This shall allow the Government to track any equipment deployed on this contract by site and location. The contractor is responsible for establishing an asset management process so that the status of assets can be provided at all times. DISA plans to replace old communications equipment within the first year of the contract and then redeploying it to other DISA sites that have older equipment. Not all of the sites will have new equipment, but this will enable DISA to raise the overall level of service to the communication infrastructure.

3.2.2.4. Release Management. An established process for performing package releases to the infrastructure shall be developed by the contractor and included in the tech refresh program plan. Once the Tech Refresh Program has begun, the need for continual communication infrastructure transformation becomes dependant on the ability to effectively handle changes that need to be made due to problem resolutions, functional requests from the DISA customers, and technology changes forced by manufacturer life cycles. Release Management helps to ensure strong Configuration Management and Change Management exists. In concert with an asset management program, it helps to ensure new assets are introduced into the infrastructure correctly and with the least amount of difficulty. The contractor’s proposal should include a release management plan.

At the end of the Tech Refresh Program the DISA organization should have a well developed and in-place Life Cycle management process that covers all types of change to the communication infrastructure. The tech refresh program plan will end when all equipment covered by this contract has been technically refreshed by communication capacity services.

3.2.2.5 Central Management: This contract requires Central Management capability that includes hardware utilization, reporting, error diagnostics, performance tools, configuration and change management. It also includes fault management, network diagramming, automated code/script updating based on policies and parameters, automated policy enforcement, automated compare/backup/restore device configurations, and integration capabilities. The Government seeks network management and performance tools that work with communications infrastructure, to include a software based solution such as Alterpoint, Openview, Spectrum or a brand name equivalent software solution.

3.2.2.6 Acceptance. The written acceptance of new equipment by the Government will start the billing cycle for this service. The contractor will be required to work with DISA to develop an acceptance testing methodology to smoothly transition the new equipment into the DISA production environment. The official acceptance documentation will be provided by the Government after contract award.

3.3 New Acquisitions. DISA’s goal is to obtain reliable, responsive, and cost effective communication infrastructure services that provide hardware and software equipment including routers, switches, monitoring equipment, monitoring and reporting software and other supporting devices in both DISA and other DISA-approved locations. New acquisitions must conform to all of the requirements of paragraphs 3.2.2.2 thru 3.2.2.6.

The Government reserves the right to incorporate any new communication technology and/or equipment within DISA's current or future inventory into the resultant contract(s) if it is deemed to be in the Government's best interest to do so. The government seeks a solution that provides the capability and flexibility to order any future “state of the art” technology.

3.3.1 Delivery. The contractor shall provide new communication equipment necessary to support contract requirements. The awardee will acquire, install, uninstall, transport, provide the necessary hardware (including cabinets/racks), hardware maintenance, communications operating software and services to support the communication infrastructure associated with the contract.

New communication equipment must have the capability to utilize an on-demand service approach that will readily adjust to changes in communications requirements, both increases and decreases.

DISA CSD will determine the need for additional ports, concurrent users, bandwidth and/or communication equipment. All new equipment must be approved by the Contracting Officer Representative (COR) prior to purchase. The COR will have a period of five calendar days to accept the order for new equipment. Delivery of equipment must occur within 15 days of the acceptance by the Government.

If Contractors cannot meet delivery guidelines above, the Government is willing to negotiate a realistic schedule.

3.3.2 Pricing. New communication equipment shall be priced on a per port, concurrent user, or bandwidth (Mbps) basis as service is ordered. The CLIN structure includes three different categories: (1) Switches (2) Routers, Multiplexors, Hubs and (3) Appliances. The categories are further delineated with Tiers that are based on function as well as speed.

3.4. Infrastructure Communications. Subject to Government approval, the capacity services will be delivered, installed, and maintained at any of the current fourteen (14) DISA CS data centers. The service locations include any future DISA CS centers in the continental US (CONUS), DISA CS centers outside CONUS (OCONUS) such as Hawaii, Germany, and Bahrain, and other DISA or DISA approved locations worldwide in which CS may acquire an operational responsibility.

This initiative will support controlled unclassified and classified, including SCI, level network environments.

The objective is for the Contractor to provide communications services using a “utility contract concept”. This utility concept requires that the Contractor provide all assets needed for the communications service.

3.5 End User and Business Transaction Management Software Services. Removed.

4.0. CURRENT ENVIRONMENT

4.1 DISA CS currently provides communications services at 14 data centers in the CONUS, located at:

Chambersburg, PA, Columbus, OH, Dayton, OH, Denver, CO, Huntsville, AL, Jacksonville, FL

Mechanicsburg, PA, Montgomery, AL, Ogden, UT, Oklahoma City, OK, Pensacola, FL

San Antonio, TX, St Louis, MO, Warner Robins, GA

4.2 OCONUS locations are:

Patch Barracks, Vaihingen, Germany

Pearl Harbor, Hawaii.

Manama, Bahrain

5.0. TECHNICAL OBJECTIVES

5.1 Maintenance. The Contractor shall provide all Preventive Maintenance as required by the OEM, Predictive and Remedial Maintenance, as of the effective date, on all equipment listed on the most recent equipment list. The present equipment list is only a representative list as of the date it was created. A list of equipment to be maintained will be provided at time of award. The pricing structure is for the equipment to be priced by make and model number. The prices for maintenance must be the same for each particular make and model number within the Continental United States. If other pricing structures are preferred, it needs to be submitted with a detailed explanation and in addition to the make and model pricing structure.

5.2 Equipment. The Contractor will provide technical refreshment and new equipment, on an as needed basis.

5.3 Performance/Availability. Communications capacity must meet a 99.95% availability standard.

The contractor must provide 24x7/365 problem escalation/resolution support for hardware, operating system software, and capacity management.

5.4 Capacity. The contractor must provide communications capacity that is scalable to adjust to increases and decreases in required workload.

Provide communications capacity that is priced on a per port, concurrent user or bandwidth basis (as used).

Provide communications capacity for Classified workloads. This must be separate channels and networks, not sharing components as instructed by DISA Security Technical Implementation Guides (STIGs). This requirement does not have any impact on the security clearance provisions of the solicitation.

Provide communications capacity that does not adversely impact existing production workload.

Provide communication capacity that is moveable. If this requires the movement of equipment the first move of each piece of equipment shall be at no cost to Government. Movement is defined as the transfer of equipment within the same DISA site or from one DISA site to another DISA site within CONUS. There will be a “Relocation Services” CLIN to support this requirement.

Capacity can be cancelled at any time at no cost to the Government. The Government will take all reasonable steps not to replace or substitute a SLIN until the end of the SLIN’s defined economic life or until end of contract and/or period of performance in the delivery order.

5.5 Technical assistance.

5.5.1 Technical assistance center (TAC). Standard commercial communications technical support, such as call center support and firmware updates, must be provided at no additional charge to the Government.

5.5.2 Technical assistance support. Technical support must be provided on as needed basis. The support will be divided into three levels depending upon the level of support required. The three levels are designated below and as described in DOD Policy 8570.01-M Information Assurance Workforce Improvement Program.

• Applies knowledge and experience with standard IA concepts, practices, and procedures within the NE.

Expert in all functions of both IAT Level I and IAT Level II positions.

• Applies extensive knowledge of a variety of the IA field’s concepts, practices, and procedures to ensure the secure integration and operation of all enclave systems.

• May lead and direct the work of others.

• Typically reports to an enclave manager.

• Supports, monitors, tests, and troubleshoots hardware and software IA problems pertaining to the enclave environment.

• Must be a U.S. Citizen.

The Contract vendor will be responsible for funding any training and certification testing as well as any certification maintenance requirements. In addition, the contractor will ensure the appropriate Operating Environment or Networking Environment certifications are met and maintained, in accordance with Government guidance.

5.6 Integration/Interfaces. All equipment provided must work with the existing DISA infrastructure and network.

5.7 Installation/Configuration. All installation, uninstalls, and power-up configurations will be completed by the Contractor. The Government will perform final operational cross check on the configurations to ensure it meets their requirements.

5.8 Security. Comply with all applicable security directives, including the DoD Directive 8500.1, "Information Assurance (IA)"; DoD Instruction 8500.2, "Information Assurance (IA) Implementation"; the Assistant Secretary of Defense Memorandum, Subject: Disposition of Unclassified DoD Computer Hard Drives, dated June 4, 2001; DISA Security Technical Implementation Guides (STIGs);

5.9 Transition Strategy. The Contractor shall create a transition strategy. The transition strategy must encompass how the outgoing Contractor plans to provide a smooth and successful transition to the new incoming Contractor. At a minimum, the transition must include the following:

5.9.1 Certificate of Maintainability.

a. The Government will provide any Certificates of Maintainability received from the out-going contractor prior to the start date of the contract calling-out maintenance service. Thereafter, the contractor shall furnish Certificates of Maintainability for all equipment maintained as part of this contract. The certificates shall be furnished to the Contracting Officer in accordance with contractor format as follows:

(1) Forty-Five (45) days prior to the completion or termination of the contract, or

(2) Within fifteen (15) days of notification that items of equipment will be removed from this contract. Under certain circumstances, such as equipment being removed for purposes of disposal, certificates for individual units may be waived. This will be at the discretion of the Government CO or COR.

b. If any portion of this contract is terminated for convenience, the contractor shall provide a Certificate of Maintainability for the terminated portion of the contract unless waived by the Government. The certificate will be furnished to the Contracting Officer within thirty (30) days prior to the termination date of the contract, provided the contractor received at least sixty (60) days notice of termination.

c. Certificate of Maintainability, at a minimum, shall state the following:

(1) That hardware has been maintained in accordance with the OEM standards and specifications.

(2) The most recently issued ECP installed, or, if released within the preceding 30 days, the contractor’s plan for the installation which has been approved by the COR, or his/her designated representative.

(3) Only new, or reconditioned and certified by the contractor “like new” parts have been installed.

(4) Model and serial number of the equipment being certified.

(5) Expiration date, if any, of the certification.

(6) ECP level of the equipment at certification.

5.9.2 Removal of Equipment: The Contractor shall conduct any necessary uninstalls and removal of hardware items on this contract upon request by the Government.

5.9.3 Transition Coordination. Transition coordination is critical to the success of this contract and must be addressed in the proposals. The Government will oversee the transition of equipment and services between the parties.

5.9.4 Transition Plan. The Contractor shall provide a transition plan to include the following at a minimum:

5.9.4.1 Transition Checklist. The Contractor will provide a detailed checklist for all parties to follow during the transition of equipment from one Contractor to next.

5.9.4.2 Transition Timelines. The potential timelines required to transition equipment.

5.9.4.3 Disputes. The contractor agrees that in the event of a dispute between itself and the incoming contractor, it will provide a written statement of the issues and the reasons for its position. If independent resolution cannot be achieved, the Government will request either an OEM technical evaluation and/or a Government technical evaluation. The cost of this evaluation will be billed to whichever Contractor is determined to be at fault. If both parties are determined to be at fault the Government will determine how the cost will be divided.

5.10 Exit Strategy. The Contractor shall create a detailed exit strategy for the end of the contract. The exit strategy shall assist the Government in the transition of services from this contract to any follow-on Contractor. The Contractor must agree to coordinate service transition with any follow-on Contractor to prevent service disruption during the transition. There will be a new follow on contract in place by the end of the base years and the transition period will begin at the end of the base period. The follow-on contractor will provide all new equipment from the end of the base years until the transition is complete. The existing contract will provide coverage on all the equipment under the base years until one of the following occurs: the existing contract ends, the equipment is technically refreshed, or the equipment is no longer required by the Government. The Contractor shall be responsible for the removal of all their Contractor owned equipment related to this contract at the end of the contract. The Contractor shall provide an exit strategy based these criteria. However, an alternative plan may be provided and will be evaluated.

6.0 Ordering/Payment Process.

6.1 Ordering. Delivery Orders for Capacity Services Communications may be placed during the five year base period of performance and Option Years One through Three (provided each applicable option year is exercised). DISA/DITCO is the only activity authorized to place delivery orders against this contract. DISA/DITCO may issue Electronic Task Orders (ETOs), delivery orders, and other correspondence to the contractor via electronic mail. DISA/DITCO will issue delivery orders with funding to be used for the purchase of services. Using an agreed upon call order process between the Government and the Contractor, call orders will be issued via electronic mail to order the actual services. The detailed call order process will operate as follows: first, the Government will issue a preliminary, nonbinding, call order with the Government’s requirement. Second, the vendor will is a solution to the Government requirement within five calendar days. Third the Government will either accept or reject the solution. The acceptance of the solution will result in the issuance of a finalized call order, which will incorporate the vendor’s solution. While the contractor must invoice against the Delivery Order, the invoice must reference all applicable call orders.

6.2 Pricing.

6.2.1 Maintenance. Maintenance, as defined below, will be provided via firm fixed unit cost in accordance with section 3.1.

6.2.2. Technical Refresh & New Acquisitions. Service will be priced on a per port, concurrent user or bandwidth basis in accordance with sections 3.2 and 3.3.

6.2.3 Technical Assistance. Technical assistance will be priced on a firm fixed price hourly basis for each of the three categories of support (Level 1, Level 2, Level 3). The contractor is authorized to invoice only for the actual hours worked and authorized by call order in accordance with section 5.5

6.2.4 Travel. Travel will be priced on a cost basis, in accordance with Federal Travel Regulations. Travel may be required on limited basis. Travel will be permitted with authorization from the Contracting Officer’s Representative (COR) by issuance of a call order authorizing hours for the work to be performed.

6.2.5 Moving. The first move of each piece of equipment will be completed by the contractor at no cost to the Government. The cost of all additional equipment moves will be negotiated. (CLIN 0005, 0012, 0019, 0026, 0033, 1005, 2005, and 3005)

7.0 Meeting Requirements. Program meetings lasting no more than 2 days will be required and held at various CONUS geographical locations. The contractor shall include all costs associated with meeting attendance in the proposed prices of CLIN 0001.

7.1 Contract Kickoff Meeting. Government and contractor representatives will have a contract kickoff meeting to be attended by key participants for each party. The meeting will occur shortly after award of the contract, and the COR will determine the time and place of the meeting. The site will be determined by the Government. The purpose of the meeting is to review the contract requirements.

7.2 Semi-Annual Review Meetings. The parties will have semi-annual contract review meetings at a site to be determined by the DISA program manager. The meeting will be held to review contract status and may be cancelled only by the Government.

7.3 Weekly Teleconference. There will be a weekly status teleconference meeting at a time mutually agreeable to the parties. The contractor will provide a toll free conference line for this meeting. The teleconference may only be cancelled by the Government.

7.4 Monthly Repair Status Teleconference. There will be a monthly repair status teleconference meeting at a time mutually agreed upon. The contractor will provide a toll free conference line.

7.5 Additional Meetings/Teleconferences. Additional meetings and teleconferences may be required based on issues that need to be addressed. The time will be mutually agreed upon. The contractor will provide a toll free conference line.

8.0 Security.

8.1 Information Assurance. DoD and DISA are intensely aware of our adversaries' desire to exploit our networks and systems, and therefore take system and network security very seriously. Our ability to monitor and protect systems is primarily focused on using the network capabilities to do so. Consequently, the majority of our efforts are network-based. With the exception of host based security systems, virtually all other computing assets associated with security and network defense and are considered to be communications assets are therefore expected to be covered under this contract. A few examples are network intrusion/protection systems, firewalls, sniffers, honeygrids, auditing systems, scanning and exploitation systems, and cflowd collectors. Cflowd is a flow analysis tool currently used for analyzing Cisco's NetFlow enabled switching method. The current release includes the collections, storage, and basic analysis modules for cflowd and for arts++ libraries. This analysis package permits data collection and analysis by ISPs and network engineers in support of capacity planning, trends analysis, and characterization of workloads in a network service provider environment. Other areas where cflowd may prove useful are:

tracking for Web hosting, accounting and billing, network planning and analysis, network monitoring, developing user profiles, data warehousing and mining, as well as security-related investigations.

As new security technology and capabilities are developed DISA may require that they be integrated into our environments.

8.2 Department of Defense (DOD) Directive 8500.1, Information Assurance, and DoD Instruction 8500.2, Information Assurance (IA) Implementation, requires that "all IA and IA-enabled IT products incorporated into DOD information systems shall be configured in accordance with DOD-approved security configuration guidelines." These STIGs (or Addendum, as appropriate) serve as the security configuration guidelines required by DODD 8500.1.

Additionally, all equipment that provides an information assurance function, such as SSL termination, must meet specific guidelines such as Federal Information Protection Standards (FIPS) 140-2, or National Institute of Standards and Technology (NIST) Common Criteria EAL-4 evaluation. The service provider will be expected to work with the Government to ensure that all equipment provided meets all required Federal, DoD, and/or DISA standards as appropriate. The service provider will be expected to ensure that all equipment provided meets all applicable Federal, DoD, and/or DISA standards as outlined in the RFP.

8.3 DISA utilizes classified and controlled unclassified information to accomplish mission objectives. Contractor personnel exposed to this level of information must protect the data through the use of the security features inherent to the software loaded, as well as by the strong authentication and physical constraints outlined below. Any deviation from standard practices may compromise data resulting in harm to the Government. When hardware is no longer required, the Government will ensure the media (tapes, hard drives, mass storage devices, etc.) are sanitized in accordance with appropriate regulations and the media will be retained by the Government.

8.4 DISA operating facilities’ security is multifaceted and implemented utilizing the layered approach. The traditional security requirements such as perimeters being patrolled, stationary guards assigned, approved access devices such as locks, card readers, badges, access logs and detection devices are physical controls implemented to deter unauthorized access. Information controls present a different challenge to protect automated sensitive data and associated resources from unauthorized access. Accounts are established after registered personnel meet access and/or clearance levels necessary for their positions. Through awareness training, directives and local policy contracted personnel are expected to comply with local security requirements upholding physical and information system security disciplines. When hardware is no longer required, the Government will ensure the media (tapes, hard drives, mass storage devices, etc.) are sanitized or destroyed in accordance with appropriate regulations. If the media cannot be sanitized and rendered to the unclassified level, the media may be returned to the Contractor in an unusable state. This process is to ensure the protection of controlled unclassified and classified information.

8.5 Contractor Personnel working this contract may have access to and maintenance responsibilities for systems which, if compromised, have a relatively high risk for causing damage to Government facilities, systems and/or data. Prior to the start of contract performance, every contractor employee who will work under this contract must have and must maintain a minimum SECRET Security Clearance resulting from a favorably completed National Agency Check with Local Agency and Credit Check (NCLC). In addition to the requirement for a SECRET clearance for any contractor personnel performing any service under this contract, contractor personnel with systems access must meet a higher security standard as evidenced by a favorably completed Single Scope Background Investigation (SSBI) to obtain a sensitivity level of IT-1. A local determination to grant access to facility, systems and/or data outlined by this contract may be approved by DISA site commander and/or designated representative, on a temporary basis, pending completion of the NCLC and/or SSBI, provided such background check has been initiated.

The Contractor shall ensure that personnel accessing information systems have the proper and current information assurance certifications to perform information assurance functions in accordance with DoD 8570.01-M, Information Assurance Workforce Improvement Program.

8.6 ADPE Maintenance Records/DISA CSD Form 7. Records for all maintenance actions including every predictive, remedial, or preventive maintenance, ECP, install, uninstall, or upgrade action, shall be completed in cooperation with site help desk personnel Records shall be completed using the attached DISA CSD Form 7, or its electronic equivalent. The completed report shall be returned to the help desk, or for remote locations to the shift supervisor, prior to the technician departing the site. If the contractor fails to submit documentation at the time required, it may result in the Government withholding payment. The “Instructions to Complete the ADPE Maintenance Record” lists the information to be entered into the fields by the OST/help desk personnel. Contractor CE personnel should review all fields on the DISA CSD Form 7 for accuracy before they sign the DISA CSD Form 7. Contractor CE personnel will receive a copy of the signed DISA CSD Form 7 before departing the site or upon conclusion of the service call where the machine is repaired and operating within OEM specifications

8.7 Additional Security Requirements. All personnel under this contract who are required to go to DISA Computing Sites to perform hardware maintenance are required to have a SECRET IT-Level I security clearance. They are also required to comply with applicable portions of the above referenced Security Program Directives. The DD254 (RFP Attachment J-3) will be attached with the RFP. Contractors shall have a fully adjudicated facility clearance prior to contract award.

9.0 Period of Performance

Period of performance is five (5) years with three, one year renewal options for a total contract term of eight (8) years.

10.0 Definitions.

10.1 Best Value: the expected outcome of an acquisition that, in the Government's estimation, provides the greatest overall benefit in response to the requirement, based on existing evaluation criteria.

10.2 Communication: the process of using technology to transfer information from point to point.

10.3 Communication Capabilities: include, but are not limited to, remote access availability, the ability to access hardware and software equipment and management services to monitor and manage communication resources at DISA-owned and other approved processing locations.

10.4 Communication Equipment: includes routers, switches, monitoring equipment, monitoring and reporting software and other devices needed to support the overall communication infrastructure.

10.5 Communication Infrastructure: hardware and software equipment including routers, switches, monitoring equipment, monitoring and reporting software and other supporting devices in both DISA and other DISA-approved locations to ensure DISA customers receive uninterrupted, continuous access to information technology equipment and networks.

10.6 DISA Equipment: all equipment necessary to provide hosting and information processing services that enable sharing of information through an assured, accessible, net-centric storage and processing environment.

10.7 Predictive Maintenance: Services rendered for the purpose of precluding an equipment failure. This includes the process of monitoring equipment error activity using automated identification and reporting systems, alert mechanisms and diagnostic routines. When error or event thresholds are exceeded, repairs are affected prior to an actual equipment failure.

10.8 Preventive Maintenance: Regularly scheduled maintenance intended to maintain equipment in fully operating order as recommended by the OEM Contractor. This is accomplished by the use of Contractor-provided system monitoring devices or other monitoring systems to predict impending equipment failure.

10.9 Networks: are a series of points or nodes interconnected by communication paths. The main networks at DISA are NIPRnet, SIPRnet, Defense Information Systems Network (DISN).

10.10 Remedial Maintenance: Unscheduled maintenance to diagnose and repair malfunctioning equipment/equipment failures.

10.11 Port: For the purposes of this contract a port is a physical interface found on network devices such as a switch or router measured at either 1 Gbsp or 10 Gbsp. This interface is used to connect servers, uplinks, and network attached devices.

10.12 Concurrent Users: The number of simultaneous users accessing the devices.

10.13 Bandwidth: For the purposes of this contract, bandwidth is defined as the throughput of appliances measured as the average megabits per second (Mbps) on a rolling 30 day window.

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

ATTACHMENTS

ATTACHMENT

DESCRIPTION

J-1

Section B Maintenance Pricing Table (Excel)

J-2

Quality Assurance Surveillance Plan (QASP)

J-3

DD Form 254- Contract Security Classification Specification

J-4

Non-Disclosure Agreement for Contractor Employees

J-5

Section B Pricing Table (Excel)

J-6

Evaluation Scenario with Quantities

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

INSTRUCTIONS TO OFFERORS

SECTION L

INFORMATION TO OFFERORS AND INSTRUCTIONS FOR PROPOSAL PREPARATION

1.0 Program Structure and Objectives

The purpose of this contract is to obtain reliable, responsive, and cost effective communication infrastructure services in both DISA and at other DISA-approved locations. DISA's goal is to obtain a dynamically scalable communications capability utilizing an on-demand service approach for new equipment that can readily adjust to both increases and decreases in communications requirements and which is priced on a utility ("as used") basis. The present communications equipment will be maintained, technically supported and when necessary identified for technical refresh.

For all applications the service provider will acquire, install, deinstall, transport, power up configuration, and provide the necessary hardware (including cabinets/racks/cabling), hardware maintenance, communications operating software and services to support the communication infrastructure associated with this contract. Maintenance on communication items currently in operation will be priced individually by unit. All other maintenance items procured through technical refresh or new purchase will be priced on a per port basis, which is firm fixed price for each port, concurrent users or bandwidth ordered under this service.

For Infrastructure Communications and for all Information Assurance applications, the government will maintain day-to-day operational control of the communication environment and retain complete oversight responsibility. Operational control includes the installation of all software updates after the initial delivery. However, all operating system software updates should be included in the maintenance covered under this contract.

2.0 General Instructions

(a) This section of the Information to Offerors provides general guidance for preparing proposals as well as specific instructions on the format and content…