13-t-0134.doc

Section A - Solicitation/Contract Form

CLAUSES INCORPORATED BY FULL TEXT

Fill in Blanks:

TIN (tax ID): ________________

CAGE: ________________

DUNS: __________________

Vendor Point of Contact: ______________________Phone: ____________________

Vendor email: ______________________

Naval Medical Center Portsmouth POC: Main Laboratory

Vendors quoted price shall be inclusive of all cost including, materials, labor, shipping, software license and royalties

Payment Monthly, in Arrears Note: vendor will be required to provide billing electronically via the WAWF Electronic Invoicing method. For additional information, a review of the following web sites may be required: https://wawf.eb.mil http://wawftraining (email) wawf@nmlc.med.navy.mil Vendor to reference N00183-13-T-0134 on all inquires.

Government reserves the right to:

(1) award based on an "All or Nothing Evaluation".

(2) award a “Best Value” requirement. Vendors with superior past performance histories may be given 1st consideration.

For Prompt Payment Act Purposes, this contract is:

Subject to the 7-calender day constructive acceptance period

Section B - Supplies or Services and Prices

Alere Informatics Rals Data System

FFP

Software License & Maintenance for the period Date of Award (target = 1 Mar 13) through 30 Sep 13

See Section C for details of requirements (individual software requirements are listed in sub CLIN's)

FOB: Destination

MILSTRIP: N0018313RQLC339

PURCHASE REQUEST NUMBER: N0018313RQLC339

NET AMT

0001AA

Accucheck Inform / Roche Diagnostics

Roche Glucose Software

Download sites = 25 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0001AB

I-Stat Point of Care Software

Total Devices = 5 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0001AC

ITC Avox 1000E / RALS Connex Software

Total Devices = 1 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0001AD

Medtronic HMSplus / RALS Connex Software

Total Devices = 1 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0001AE

Siemens Diagnostics DCA Vantage

RALS Connex Software

Total Devices = 1 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0001AF

Siemens Diagnostics Clinitek Status

Urinalysis Software

Total Download Sites = 3 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0001AG

RALS E-quiz Software

Max number of Operators = 1,000

See Section C for details of requirements

FOB: Destination

NET AMT

0001AH

On-Site Training

See Section C for details of requirements

FOB: Destination

NET AMT

FFP

Software License & Maintenance for the period 1 Oct 13 through 30 Sep 14

See Section C for details of requirements (individual software requirements are listed in sub CLIN's)

FOB: Destination

NET AMT

0002AA

FFP

Roche Glucose Software

Download sites = 25 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0002AB

FFP

Total Devices = 5 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0002AC

FFP

Total Devices = 1 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0002AD

FFP

Total Devices = 1 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0002AE

FFP

RALS Connex Software

Total Devices = 1 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0002AF

FFP

Urinalysis Software

Total Download Sites = 3 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0002AG

FFP

Max number of Operators = 1,000

See Section C for details of requirements

FOB: Destination

NET AMT

0002AH

FFP

See Section C for details of requirements

FOB: Destination

NET AMT

FFP

Software License & Maintenance for the period 1 Oct 14 through 30 Sep 15

See Section C for details of requirements (individual software requirements are listed in sub CLIN's)

FOB: Destination

NET AMT

0003AA

FFP

Roche Glucose Software

Download sites = 25 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0003AB

FFP

Total Devices = 5 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0003AC

FFP

Total Devices = 1 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0003AD

FFP

Total Devices = 1 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0003AE

FFP

RALS Connex Software

Total Devices = 1 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0003AF

FFP

Urinalysis Software

Total Download Sites = 3 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0003AG

FFP

Max number of Operators = 1,000

See Section C for details of requirements

FOB: Destination

NET AMT

0003AH

FFP

See Section C for details of requirements

FOB: Destination

NET AMT

FFP

Software License & Maintenance for the period 1 Oct 15 through 30 Sep 16

See Section C for details of requirements (individual software requirements are listed in sub CLIN's)

FOB: Destination

NET AMT

0004AA

FFP

Roche Glucose Software

Download sites = 25 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0004AB

FFP

Total Devices = 5 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0004AC

FFP

Total Devices = 1 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0004AD

FFP

Total Devices = 1 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0004AE

FFP

RALS Connex Software

Total Devices = 1 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0004AF

FFP

Urinalysis Software

Total Download Sites = 3 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0004AG

FFP

Max number of Operators = 1,000

See Section C for details of requirements

FOB: Destination

NET AMT

0004AH

FFP

See Section C for details of requirements

FOB: Destination

NET AMT

FFP

Software License & Maintenance for the period 1 Oct 16 through 30 Sep 17

See Section C for details of requirements (individual software requirements are listed in sub CLIN's)

FOB: Destination

NET AMT

0005AA

FFP

Roche Glucose Software

Download sites = 25 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0005AB

FFP

Total Devices = 5 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0005AC

FFP

Total Devices = 1 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0005AD

FFP

Total Devices = 1 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0005AE

FFP

RALS Connex Software

Total Devices = 1 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0005AF

FFP

Urinalysis Software

Total Download Sites = 3 ea

See Section C for details of requirements

FOB: Destination

NET AMT

0005AG

FFP

Max number of Operators = 1,000

See Section C for details of requirements

FOB: Destination

NET AMT

0005AH

FFP

See Section C for details of requirements

FOB: Destination

NET AMT

Section C - Descriptions and Specifications

STATEMENT OF WORK

· Vendor to provide software, software license, maintenance and technical support on the Alere Informatics Rals Data Software systems described in Section B

· Vendors price to be inclusive of all cost including labor, materials, shipping, royalties and software license fees.

· Vendor to provide support during normal work hours of 8:00 am – 5:00 pm (EST) Monday – Friday except Federal Holidays.

· Vendor shall provide all software maintenance releases as soon as possible after release but no later than 14 days after release.

· Copies of software license and software maintenance releases are to be sent to the NMCP MID Office at the below address:

· Naval Medical Center Portsmouth

· 620 John Paul Jones Circle

· Att: Management Information Office / Betty Fisher

· Portsmouth, VA 23708

· Supplied, software / license shall be provided free of all additional royalties or other charges.

· All supplied software must be certified free of malicious codes / damaging properties such as viruses, Trojan horses, worms, spyware etc.

· NMCP recognizes that the use of all supplied software is for the sole use of NMCP. NMCP agrees not to share, sell, copy, lease or assign supplied software without the expressed permission of vendor.

· NMCP shall make all attempts to preserve the proprietary nature of all supplied software. Vendor shall take all reasonable measures to safeguard any and all NMCP file data. (i.e. vendor shall not share any medical records / data collected by supplied software)

· All technical support personnel must be adequately trained and knowledgeable of supplied software.

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

Section F - Deliveries or Performance

DELIVERY INFORMATION

30-SEP-2013

FOB: Destination

30-SEP-2013

LABORATORY/ADMIN

BLDG 2

620 JOHN PAUL JONES CIRCLE

PORTSMOUTH VA 23708

757-953-1709

N00183

30-SEP-2013

N00183

30-SEP-2013

N00183

30-SEP-2013

N00183

30-SEP-2013

N00183

30-SEP-2013

N00183

30-SEP-2013

N00183

30-SEP-2013

N00183

30-SEP-2014

30-SEP-2014

LABORATORY/ADMIN

BLDG 2

620 JOHN PAUL JONES CIRCLE

PORTSMOUTH VA 23708

757-953-1709

N00183

30-SEP-2014

N00183

30-SEP-2014

N00183

30-SEP-2014

N00183

30-SEP-2014

N00183

30-SEP-2014

N00183

30-SEP-2014

N00183

30-SEP-2014

N00183

30-SEP-2015

30-SEP-2015

LABORATORY/ADMIN

BLDG 2

620 JOHN PAUL JONES CIRCLE

PORTSMOUTH VA 23708

757-953-1709

N00183

30-SEP-2015

N00183

30-SEP-2015

N00183

30-SEP-2015

N00183

30-SEP-2015

N00183

30-SEP-2015

N00183

30-SEP-2015

N00183

30-SEP-2015

N00183

30-SEP-2016

30-SEP-2016

LABORATORY/ADMIN

BLDG 2

620 JOHN PAUL JONES CIRCLE

PORTSMOUTH VA 23708

757-953-1709

N00183

30-SEP-2016

N00183

30-SEP-2016

N00183

30-SEP-2016

N00183

30-SEP-2016

N00183

30-SEP-2016

N00183

30-SEP-2016

N00183

30-SEP-2016

N00183

30-SEP-2017

30-SEP-2017

LABORATORY/ADMIN

BLDG 2

620 JOHN PAUL JONES CIRCLE

PORTSMOUTH VA 23708

757-953-1709

N00183

30-SEP-2017

N00183

30-SEP-2017

N00183

30-SEP-2017

N00183

30-SEP-2017

N00183

30-SEP-2017

N00183

30-SEP-2017

N00183

30-SEP-2017

N00183

CLAUSES INCORPORATED BY REFERENCE

Section G - Contract Administration Data

252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (JAN 2013) (DEVIATION)

(a) Definitions. As used in this clause—

“Department of Defense Activity Address Code (DoDAAC)” is a six position code that uniquely identifies a unit, activity, or organization.

“Document type” means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF).

“Local processing office (LPO)” is the office responsible for payment certification when payment certification is done external to the entitlement system.

(b) Electronic invoicing. The WAWF system is the method to electronically process vendor payment requests and receiving reports, as authorized by DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports

(c) WAWF access. To access WAWF, the Contractor shall—

(1) Have a designated electronic business point of contact in the Central Contractor Registration at https://www.acquisition.gov; and

(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this web site

(d) WAWF training. The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the “Web Based Training” link on the WAWF home page at https://wawf.eb.mil/

(e) WAWF methods of document submission. Document submissions may be via web entry, Electronic Data Interchange, File Transfer Protocol, or PayWeb.

(1) To access PayWeb, the vendor may go to the following site: https://onronline.onr.navy.mil/payweb/

(2) For instructions on PayWeb payment request submission, please contact the office identified below:

(Contracting Officer: Insert applicable ONR Regional Office information)

(f) WAWF payment instructions. The Contractor must use the following information when submitting payment requests and receiving reports in WAWF for this contract/order:

(1) Document type. The Contractor shall use the following document type(s).

(Contracting Officer: Insert applicable document type(s). Note: If a “Combo” document type is identified but not supportable by the Contractor’s business systems, an “Invoice” (stand-alone) and “Receiving Report” (stand-alone) document type may be used instead.)

(2) Inspection/acceptance location. The Contractor shall select the following inspection/acceptance location(s) in WAWF, as specified by the contracting officer.

(Contracting Officer: Insert inspection and acceptance locations or “Not applicable.”)

(3) Document routing. The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system.

Routing Data Table

Pay Official DoDAAC

Issue By DoDAAC

Admin DoDAAC

Inspect By DoDAAC

Ship To Code

Ship From Code

Mark For Code

Service Approver (DoDAAC)

Service Acceptor (DoDAAC)

Accept at Other DoDAAC

LPO DoDAAC

DCAA Auditor DoDAAC

Other DoDAAC(s)

(*Contracting Officer: Insert applicable DoDAAC information or “See schedule” if multiple ship to/acceptance locations apply, or “Not applicable.”)

(4) Payment request and supporting documentation. The Contractor shall ensure a payment request includes appropriate contract line item and subline item descriptions of the work performed or supplies delivered, unit price/cost per unit, fee (if applicable), and all relevant back-up documentation, as defined in DFARS Appendix F, (e.g. timesheets) in support of each payment request.

(5) WAWF email notifications. The Contractor shall enter the e-mail address identified below in the “Send Additional Email Notifications” field of WAWF once a document is submitted in the system.

(Contracting Officer: Insert applicable email addresses or “Not applicable.”)

(g) WAWF point of contact.

(1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity’s WAWF point of contact.

(Contracting Officer: Insert applicable information or “Not applicable.”)

(3) For technical WAWF help, contact the WAWF helpdesk at 866-618-5988.

(End of clause)

Section H - Special Contract Requirements

CLAUSES INCORPORATED BY FULL TEXT

N00183-0004 PRIVACY AND SECURITY OF PROTECTED HEALTH INFORMATION

1. Introduction In accordance with DoD 6025.18-R “Department of Defense Health Information Privacy Regulation,” January 24, 2003, the Business Associate meets the definition of Business Associate. Therefore, a Business Associate Agreement is required to comply with both the Health Insurance Portability and Accountability Act (HIPAA) Privacy and Security regulations. This clause serves as that agreement whereby the Business Associate agrees to abide by all applicable HIPAA Privacy and Security requirements regarding health information as defined in this clause, and in DoD 6025.18-R and DoD 8580.02-R, as amended. Additional requirements will be addressed when implemented.

a. Definitions. As used in this clause generally refer to the Code of Federal Regulations (CFR) definition unless a more specific provision exists in DoD 6025.18-R or DoD 8580.02-R.

(1) HITECH Act shall mean the Health Information Technology for Economic and Clinical Health Act included in the American Recovery and Reinvestment Act of 2009.

(2) Individual has the same meaning as the term “individual” in 45 CFR 160.103 and shall include a person who qualifies as a personal representative in accordance with 45 CFR 164.502(g).

(3) Privacy Rule means the Standards for Privacy of Individually Identifiable Health Information at 45 CFR part 160 and part 164, subparts A and E.

(4) Protected Health Information has the same meaning as the term “protected health information” in 45 CFR 160.103, limited to the information created or received by the Business Associate from or on behalf of the Government pursuant to the Contract.

(5) Electronic Protected Health Information has the same meaning as the term “electronic protected health information” in 45 CFR 160.103.

(6) Required by Law has the same meaning as the term “required by law” in 45 CFR 164.103.

(7) Secretary means the Secretary of the Department of Health and Human Services or his/her designee.

(8) Security Incident will have the same meaning as the term “security incident” in 45 CFR 164.304, limited to the information created or received by Business Associate from or on behalf of Covered Entity.

(9) Security Rule means the Health Insurance Reform: Security Standards at 45 CFR part 160, 162 and part 164, subpart C.

(10) Terms used, but not otherwise defined, in this Clause shall have the same meaning as those terms in 45 CFR 160.103, 160.502, 164.103, 164.304, and 164.501.

b. The Business Associate shall not use or further disclose Protected Health Information other than as permitted or required by the Contract or as Required by Law.

c. The Business Associate shall use appropriate safeguards to maintain the privacy of the Protected Health Information and to prevent use or disclosure of the Protected Health Information other than as provided for by this Contract.

d. The HIPAA Security administrative, physical, and technical safeguards in 45 CFR 164.308, 164.310, and 164.312, and the requirements for policies and procedures and documentation in 45 CFR 164.316 shall apply to Business Associate. The additional requirements of Title XIII of the HITECH Act that relate to the security and that are made applicable with respect to covered entities shall also be applicable to Business Associate. The Business Associate agrees to use administrative, physical, and technical safeguards that reasonably and appropriately protect the confidentiality, integrity, and availability of the electronic protected health information that it creates, receives, maintains, or transmits in the execution of this Contract.

e. The Business Associate shall, at their own expense, take action to mitigate, to the extent practicable, any harmful effect that is known to the Business Associate of a use or disclosure of Protected Health Information by the Business Associate in violation of the requirements of this Clause. These mitigation actions will include as a minimum those listed in the TMA Breach Notification Standard Operating Procedure (SOP), which is available at: http://www.tricare.mil/tmaprivacy/breach.cfm

f. The Business Associate shall report to the Government any security incident involving protected health information of which it becomes aware.

g. The Business Associate shall report to the Government any use or disclosure of the Protected Health Information not provided for by this Contract of which the Business Associate becomes aware.

h. The Business Associate shall ensure that any agent, including a sub Business Associate, to whom it provides Protected Health Information received from, or created or received by the Business Associate, on behalf of the Government, agrees to the same restrictions and conditions that apply through this Contract to the Business Associate with respect to such information.

i. The Business Associate shall ensure that any agent, including a subBusiness Associate, to whom it provides electronic Protected Health Information, agrees to implement reasonable and appropriate safeguards to protect it.

j. The Business Associate shall provide access, at the request of the Government, and in the time and manner reasonably designated by the Government to Protected Health Information in a Designated Record Set, to the Government or, as directed by the Government, to an Individual in order to meet the requirements under 45 CFR 164.524.

k. The Business Associate shall make any amendment(s) to Protected Health

Information in a Designated Record Set that the Government directs or agrees to pursuant to 45 CFR 164.526 at the request of the Government, and in the time and manner reasonably designated by the Government.

l. The Business Associate shall make internal practices, books, and records relating to the use and disclosure of Protected Health Information received from, or created or received by the Business Associate, on behalf of the Government, available to the Government, or at the request of the Government to the Secretary, in a time and manner reasonably designated by the Government or the Secretary, for purposes of the Secretary determining the Government’s compliance with the Privacy Rule.

m. The Business Associate shall document such disclosures of Protected Health Information and information related to such disclosures as would be required for the Government to respond to a request by an Individual for an accounting of disclosures of Protected Health Information in accordance with 45 CFR 164.528.

n. The Business Associate shall provide to the Government or an Individual, in time and manner reasonably designated by the Government, information collected in accordance with this Clause of the Contract, to permit the Government to respond to a request by an Individual for an accounting of disclosures of Protected Health Information in accordance with 45 CFR 164.528.

2. General Use and Disclosure Provisions Except as otherwise limited in this Clause, the Business Associate may use or disclose Protected Health Information on behalf of, or to provide services to, the Government for treatment, payment, or healthcare operations purposes, in accordance with the specific use and disclosure provisions below, if such use or disclosure of Protected Health Information would not violate the HIPAA Privacy Rule, the HIPAA Security Rule, DoD 6025.18-R or DoD 8580.02-R if done by the Government. The additional requirements of Title XIII of the HITECH Act that relate to privacy and that are made applicable with respect to covered entities shall also be applicable to Business Associate.

3. Specific Use and Disclosure Provisions

a. Except as otherwise limited in this Clause, the Business Associate may use Protected Health Information for the proper management and administration of the Business Associate or to carry out the legal responsibilities of the Business Associate.

b. Except as otherwise limited in this Clause, the Business Associate may disclose Protected Health Information for the proper management and administration of the Business Associate, provided that disclosures are required by law, or the Business Associate obtains reasonable assurances from the person to whom the information is disclosed that it will remain confidential and used or further disclosed only as required by law or for the purpose for which it was disclosed to the person, and the person notifies the Business Associate of any instances of which it is aware in which the confidentiality of the information has been breached.

c. Except as otherwise limited in this Clause, the Business Associate may use Protected Health Information to provide Data Aggregation services to the Government as permitted by 45 CFR 164.504(e)(2)(i)(B).

d. Business Associate may use Protected Health Information to report violations of law to appropriate Federal and State authorities, consistent with 45 CFR 164.502(j)(1).

4. Obligations of the Government Provisions for the Government to Inform the Business Associate of Privacy Practices and Restrictions

a. The Government shall provide the Business Associate with the notice of privacy practices that the Government produces in accordance with 45 CFR 164.520.

b. The Government shall provide the Business Associate with any changes in, or revocation of, permission by Individual to use or disclose Protected Health

Information, if such changes affect the Business Associate’s permitted or required uses and disclosures.

c. The Government shall notify the Business Associate of any restriction to the use or disclosure of Protected Health Information that the Government has agreed to in accordance with 45 CFR 164.522.

5. Permissible Requests by the Government The Government shall not request the Business Associate to use or disclose

Protected Health Information in any manner that would not be permissible under the HIPAA Privacy Rule, the HIPAA Security Rule, or any applicable Government regulations (including without limitation, DoD 6025.18-R and DoD 8580.02-R) if done by the Government, except for providing Data Aggregation services to the Government and for management and administrative activities of the Business Associate as otherwise permitted by this clause.

6. Termination

a. Termination. A breach by the Business Associate of this clause, may subject the Business Associate to termination under any applicable default or termination provision of this Contract.

b. Effect of Termination.

(1) If this contract has records management requirements, the records subject to the Clause should be handled in accordance with the records management requirements. If this contract does not have records management requirements, the records should be handled in accordance with paragraphs (2) and (3) below

(2) If this contract does not have records management requirements, except as provided in paragraph (3) of this section, upon termination of this Contract, for any reason, the Business Associate shall return or destroy all Protected Health Information received from the Government, or created or received by the Business Associate on behalf of the Government. This provision shall apply to Protected Health Information that agents of the Business Associate may come in contact. The Business Associate shall retain no copies of the Protected Health Information.

(3) If this contract does not have records management provisions and the Business Associate determines that returning or destroying the Protected Health Information is infeasible, the Business Associate shall provide to the Government notification of the conditions that make return or destruction infeasible. Upon mutual agreement of the Government and the Business Associate that return or destruction of Protected Health Information is infeasible, the Business Associate shall extend the protections of this Contract to such Protected Health Information and limit further uses and disclosures of such Protected Health Information to those purposes that make the return or destruction infeasible, for so long as the Business Associate maintains such Protected Health Information.

7. Miscellaneous

a. Regulatory References. A reference in this Clause to a section in DoD 6025.18-R, DoD 8580.02-R, Privacy Rule or Security Rule means the section currently in effect or as amended, and for which compliance is required.

b. Survival. The respective rights and obligations of Business Associate under the “Effect of Termination” provision of this Clause shall survive the termination of this Contract.

c. Interpretation. Any ambiguity in this Clause shall be resolved in favor of a meaning that permits the Government to comply with DoD 6025.18-R, DoD 8580.02-R, the HIPAA Privacy Rule or the HIPAA Security Rule.

The system/assets being developed, procured or acquired shall be IPv6 capable. An IPv6 capable system or product shall be capable of receiving, processing and forwarding IPv6 packets and/or interfacing with other systems and protocols in a manner similar to that of IPv4. Specific current criteria to be deemed IPv6 capable are:

· Conformant with the JTA developed IPv6 standards profile. Systems being developed, procured or acquired shall comply with the Global Information Grid Architecture and Joint Technical Architecture (JTA) standard IPv6 Capable definition. An IPv6 Capable system must meet the IPv6 base requirements defined in the “IPv6 Standard Profiles v1.0” available from the DoD Information Technology Repository (DISR).

· Maintaining interoperability with IPv4. Systems being developed, procured or acquired shall maintain interoperability with IPv4 systems/capabilities. Systems built with dual-stack should also be built to determine which protocol layer to use depending on the destination host it is attempting to communicate with or establish a socket with. If either protocol is possible systems should employ IPv6.

· Existence of migration path and commitment to upgrade as IPv6 evolves.

· Availability of contractor/vendor IPv6 technical support.

DoD IPv6 security guidelines, standards, and solutions shall be utilized and adhered to when available. Currently, DoD IPv6 Information Assurance (IA) guidance is available from the DoD IPv6 Transition Office (DITO).

INFORMATION ONLY: This document has been designated for posting to the Navy Electronic Commerce Online (NECO) at http://www.neco.navy.mil

Section I - Contract Clauses

CLAUSES INCORPORATED BY REFERENCE

52.217-8 OPTION TO EXTEND SERVICES (NOV 1999)

The Government may require continued performance of any services within the limits and at the rates specified in the contract. These rates may be adjusted only as a result of revisions to prevailing labor rates provided by the Secretary of Labor. The option provision may be exercised more than once, but the total extension of performance hereunder shall not exceed 6 months. The Contracting Officer may exercise the option by written notice to the Contractor within 10 days.

(End of clause)

52.217-9 OPTION TO EXTEND THE TERM OF THE CONTRACT (MAR 2000)

(a) The Government may extend the term of this contract by written notice to the Contractor within 10 days; provided that the Government gives the Contractor a preliminary written notice of its intent to extend at least 10 days before the contract expires. The preliminary notice does not commit the Government to an extension.

(b) If the Government exercises this option, the extended contract shall be considered to include this option clause.

(c) The total duration of this contract, including the exercise of any options under this clause, shall not exceed 55 months.

(End of clause)

52.232-18 AVAILABILITY OF FUNDS (APR 1984)

Funds are not presently available for this contract. The Government's obligation under this contract is contingent upon the availability of appropriated funds from which payment for contract purposes can be made. No legal liability on the part of the Government for any payment may arise until funds are made available to the Contracting Officer for this contract and until the Contractor receives notice of such availability, to be confirmed in writing by the Contracting Officer.

(End of clause)

52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es):

https://www.acquisition.gov/far/ http://www.acq.osd.mil/dpap/dars/dfarspgi/current/index.html

(End of clause)

Section K - Representations, Certifications and Other Statements of Offerors

CLAUSES INCORPORATED BY REFERENCE

52.204-3 TAXPAYER IDENTIFICATION (OCT 1998)

(a) Definitions.

Common parent, as used in this provision, means that corporate entity that owns or controls an affiliated group of corporations that files its Federal income tax returns on a consolidated basis, and of which the offeror is a member.

Taxpayer Identification Number (TIN), as used in this provision, means the number required by the Internal Revenue Service (IRS) to be used by the offeror in reporting income tax and other returns. The TIN may be either a Social Security Number or an Employer Identification Number.

(b) All offerors must submit the information required in paragraphs (d) through (f) of this provision to comply with debt collection requirements of 31 U.S.C. 7701(c) and 3325(d), reporting requirements of 26 U.S.C. 6041, 6041A, and 6050M, and implementing regulations issued by the IRS. If the resulting contract is subject to the payment reporting requirements described in Federal Acquisition Regulation (FAR) 4.904, the failure or refusal by the offeror to furnish the information may result in a 31 percent reduction of payments otherwise due under the contract.

(c) The TIN may be used by the Government to collect and report on any delinquent amounts arising out of the offeror's relationship with the Government (31 U.S.C. 7701(c)(3)). If the resulting contract is subject to the payment reporting requirements described in FAR 4.904, the TIN provided hereunder may be matched with IRS records to verify the accuracy of the offeror's TIN.

(d) Taxpayer Identification Number (TIN).

___ TIN:.--------------------------------------------------------

___ TIN has been applied for.

___ TIN is not required because:

___ Offeror is a nonresident alien, foreign corporation, or foreign partnership that does not have income effectively connected with the conduct of a trade or business in the United States and does not have an office or place of business or a fiscal paying agent in the United States;

___ Offeror is an agency or instrumentality of a foreign government;

___ Offeror is an agency or instrumentality of the Federal Government.

(e) Type of organization.

___ Sole proprietorship;

___ Partnership;

___ Corporate entity (not tax-exempt);

___ Corporate entity (tax-exempt);

___ Government entity (Federal, State, or local);

___ Foreign government;

___ International organization per 26 CFR 1.6049-4;

___ Other--------------------------------------------------------

(f) Common parent.

___ Offeror is not owned or controlled by a common parent as defined in paragraph (a) of this provision.

___ Name and TIN of common parent:

Name-------------------------------------------------------------------

TIN--------------------------------------------------------------------

(End of provision)

Section L - Instructions, Conditions and Notices to Bidders

CLAUSES INCORPORATED BY REFERENCE

52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB 1998)

This solicitation incorporates one or more solicitation provisions by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. The offeror is cautioned that the listed provisions may include blocks that must be completed by the offeror and submitted with its quotation or offer. In lieu of submitting the full text of those provisions, the offeror may identify the provision by paragraph identifier and provide the appropriate information with its quotation or offer. Also, the full text of a solicitation provision may be accessed electronically at this/these address(es):

https://www.acquisition.gov/far/ http://www.acq.osd.mil/dpap/dars/dfarspgi/current/index.html (End of provision

Section M - Evaluation Factors for Award

CLAUSES INCORPORATED BY REFERENCE