09.01.2013 Views

draft beb rfp - TACOM Procurement Network - U.S. Army

draft beb rfp - TACOM Procurement Network - U.S. Army

draft beb rfp - TACOM Procurement Network - U.S. Army

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

CONTINUATION SHEET<br />

Name of Offeror or Contractor:<br />

Reference No. of Document Being Continued Page 103 of 170<br />

PIIN/SIIN W56HZV-12-R-0445<br />

MOD/AMD<br />

[ X ] Available at http://contracting.tacom.army.mil/majorsys/<strong>beb</strong>/<strong>beb</strong>.htm<br />

______________________________________________________<br />

titled: BEB Contractor NDA<br />

[ ] Available as an attachment to this solicitation.<br />

Follow the instructions on the Agreement, and email it to the buyer at tuyen.huynh.civ@mail.mil. The buyer will notify the FBO<br />

administrator upon receiving the NDA. The administrator will grant approval to view/download the TDP. An email stating approval has<br />

been granted will be sent to the vendor. It can take up to 24 hours after approval before you are able to view the TDP. If you have<br />

any questions/problems viewing the TDP, contact the buyer.<br />

[End of Clause]<br />

C-5 52.204-4020 ACCESS AND GENERAL PROTECTION/SECURITY POLICY AND PROCEDURES JUN/2012<br />

(<strong>TACOM</strong>)<br />

The contractor and all associated subcontractors employees shall comply with applicable installation, facility, and area commander<br />

installation and facility access and local security policies and procedures (provided by the Government representative). The contractor<br />

shall also provide all information required for background checks to meet installation access requirements to be accomplished by the<br />

installation Provost Marshal Office, Director of Emergency Services, or Security Office. The contractor workforce must comply with all<br />

personal identity verification requirements as directed by DoD, HQDA, and/or local policy. In addition to the changes otherwise<br />

authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or<br />

installation change, the Government may require changes in contractor security matters or processes.<br />

(End of Clause)<br />

C-6 52.204-4022 REQUIREMENT FOR AN OPSEC STANDING OPERATION PROCEDURE/PLAN JUN/2012<br />

(<strong>TACOM</strong>)<br />

The contractor shall develop an OPSEC Standing Operating Procedure (SOP)/Plan within 90 calendar days of contract award, to be reviewed<br />

and approved by the responsible Government OPSEC officer, per AR 530-1, Operations Security. This SOP/Plan will specify the governments<br />

critical information, why it needs to be protected, where it is located, who is responsible for it, and how to protect it. In addition,<br />

the contractor shall identify an individual who will be an OPSEC Coordinator. The contractor will ensure that this individual becomes<br />

OPSEC Level II certified per AR 530-1.<br />

C-7 52.209-4023 OPSEC TRAINING REQUIREMENT JUN/2012<br />

(<strong>TACOM</strong>)<br />

DRAFT<br />

Per AR 530-1, Operations Security, new contractor employees must complete Level I OPSEC training within 30 calendar days of reporting<br />

for duty. All contractor employees must complete annual OPSEC awareness training.<br />

(End of Clause)<br />

C-8 52.209-4024 INFORMATION ASSURANCE (IA)/INFORMATION TECHNOLOGY (IT) TRAINING JUN/2012<br />

(<strong>TACOM</strong>)<br />

All contractor employees and associated subcontractor employees must complete the DoD IA awareness training before issuance of network<br />

access and annually thereafter. All contractor employees working IA/IT functions must comply with DoD and <strong>Army</strong> training requirements in<br />

DoDD 8570.01, DoD 8570.01-M, and AR 25-2 within six months of employment.<br />

(End of Clause)<br />

C-9 52.237-4000 CONTRACTOR MANPOWER REPORTING (CMR) DEC/2012<br />

(<strong>TACOM</strong>)

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!