HS0021-15-R-0011_Conformed_RFP_through_Amend_0004.pdf

CODE

(Hour)

PAGE(S)

until 02:00 PM local time 04 Jun 2015

X

A

X B X C

D

EX

G F 36 - 43

44 - 62 X H 63 - 69 shawna.mitchell@dss.mil

RATING PAGE OF PAGES

7. ISSUED BY

(Date)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

Previous Edition is Unusable 33-134 STANDARD FORM 33 (REV. 9-97)

Prescribed by GSA FAR (48 CFR) 53.214(c)

1 69

(If other than Item 7)

15A. NAME 16. NAME AND TITLE OF PERSON AUTHORIZED TO

AND

ADDRESS

SIGN OFFER (Type or print)

OF

OFFEROR

AMENDMENT NO. DATE

15B. TELEPHONE NO (Include area code) 17. SIGNATURE15C. CHECK IF REMITTANCE ADDRESS

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

18. OFFER DATE

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

2. CONTRACT NO.

HS0021 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and 8 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

10. FOR

INFORMATION

CALL:

A. NAME (NO COLLECT

CALLS)SHAWNA MITCHELL

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

2 - 11

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

12 - 16 J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 18 - 21 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror)

22 - 24 X M

L INSTRS., CONDS., AND NOTICES TO OFFERORS

EVALUATION FACTORS FOR AWARD

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments

AMENDMENT NO. DATE

to the SOLICITATION for offerors and related documents numbered and dated):

FACILITY

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period

SOLICITATION, OFFER AND AWARD

X

(X) SEC. DESCRIPTION (X) SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE

26. NAME OF CONTRACTING OFFICER (Type or print)

27. UNITED STATES OF AMERICA 28. AWARD DATE

EMAIL:TEL: (Signature of Contracting Officer)

CODE CODE

B. TELEPHONE (Include area code) C. E-MAIL ADDRESS

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE

PART IV - REPRESENTATIONS AND INSTRUCTIONS

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

25 - 33

PART II - CONTRACT CLAUSES

DEFENSE SECURITY SERVICE

SHAWNA MITCHELL 571.305.6548

RUSSELL-KNOX BUILDING

27130 TELEGRAPH ROAD

QUANTICO VA 22134

FAX:

TEL:

FAX:

TEL:

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SOLICITATION

34 - 35

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

13 Feb 2015

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

HS0021-15-R-0011

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

0001 UNDEFINED Months Labor

CPFF

The contractor shall provide all the labor associated with providing the NISS solution as defined in the individual task orders issued under this contract. Each task order will be issued as a cost plus fixed fee (CPFF) task order.

FOB: Destination

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

UNIT UNIT PRICE MAX AMOUNT

0002 1 Each Software

FFP

To include necessary software, licenses, and maintenance for the NISS solution as defined in the individual task orders issued under this contract. All inclusive price.

MAX

NET AMT

UNIT UNIT PRICE MAX AMOUNT

0003 UNDEFINED Each Travel

COST

The travel associated with is CLIN under each task order shall be in accordance with FAR 31.205-46.

UNIT UNIT PRICE MAX AMOUNT

0004 1 Each Contractor Manpower Report

FFP

The contractor shall comply with the Department of Defense's Contractor Manpower Reporting (CMR) requirements. Data will be required for each task orders and shall not be separately priced.

https://dodcmra.hqda.pentagon.mil/Login.aspx

UNIT UNIT PRICE MAX AMOUNT

1001 UNDEFINED Months OPTION Labor

CPFF

The contractor shall provide all the labor associated with providing the NISS solution as defined in the individual task orders issued under this contract. Each

UNIT UNIT PRICE MAX AMOUNT

1002 1 Each OPTION Software

FFP

To include necessary software, licenses, and maintenance for the NISS solution as defined in the individual task orders issued under this contract. All inclusive

UNIT UNIT PRICE MAX AMOUNT

1003 UNDEFINED Each OPTION Travel

COST

The travel associated with is CLIN under each task order shall be in accordance

UNIT UNIT PRICE MAX AMOUNT

1004 1 Each OPTION Contractor Manpower Report

FFP

The contractor shall comply with the Department of Defense's Contractor Manpower Reporting (CMR) requirements. Data will be required for each task orders and shall not be separately priced.

UNIT UNIT PRICE MAX AMOUNT

2001 UNDEFINED Months OPTION Labor

CPFF

The contractor shall provide all the labor associated with providing the NISS solution as defined in the individual task orders issued under this contract. Each

UNIT UNIT PRICE MAX AMOUNT

2002 1 Each OPTION Software

FFP

To include necessary software, licenses, and maintenance for the NISS solution as defined in the individual task orders issued under this contract. All inclusive

UNIT UNIT PRICE MAX AMOUNT

2003 UNDEFINED Each OPTION Travel

COST

The travel associated with is CLIN under each task order shall be in accordance

UNIT UNIT PRICE MAX AMOUNT

2004 1 Each OPTION Contractor Manpower Report

FFP

The contractor shall comply with the Department of Defense's Contractor Manpower Reporting (CMR) requirements. Data will be required for each task orders and shall not be separately priced.

UNIT UNIT PRICE MAX AMOUNT

3001 UNDEFINED Months OPTION Labor

CPFF

The contractor shall provide all the labor associated with providing the NISS solution as defined in the individual task orders issued under this contract. Each

UNIT UNIT PRICE MAX AMOUNT

3002 1 Each OPTION Software

FFP

To include necessary software, licenses, and maintenance for the NISS solution as defined in the individual task orders issued under this contract. All inclusive

UNIT UNIT PRICE MAX AMOUNT

3003 UNDEFINED Each OPTION Travel

COST

The travel associated with is CLIN under each task order shall be in accordance

UNIT UNIT PRICE MAX AMOUNT

3004 1 Each OPTION Contractor Manpower Report

FFP

The contractor shall comply with the Department of Defense's Contractor Manpower Reporting (CMR) requirements. Data will be required for each task orders and shall not be separately priced.

UNIT UNIT PRICE MAX AMOUNT

4001 UNDEFINED Months OPTION Labor

CPFF

The contractor shall provide all the labor associated with providing the NISS solution as defined in the individual task orders issued under this contract. Each

UNIT UNIT PRICE MAX AMOUNT

4002 1 Each OPTION Software

FFP

To include necessary software, licenses, and maintenance for the NISS solution as defined in the individual task orders issued under this contract. All inclusive

UNIT UNIT PRICE MAX AMOUNT

4003 UNDEFINED Each OPTION Travel

COST

The travel associated with is CLIN under each task order shall be in accordance

UNIT UNIT PRICE MAX AMOUNT

4004 1 Each OPTION Contractor Manpower Report

FFP

The contractor shall comply with the Department of Defense's Contractor Manpower Reporting (CMR) requirements. Data will be required for each task orders and shall not be separately priced.

SCHEDULE B NOTE

This is a single award Indefinite Quantity Indefinite Delivery (IDIQ) type contract. Task orders shall be issued under this arrangement. Total orders under this contract shall not exceed $50,000,000 including all options periods.

(One-year base, four one-year options). The guaranteed minimum is $100,000 for the basic period only. There is no guaranteed minimum for the option periods, if exercised. Orders may only be issued by the Defense Security Service (DSS) Office of Acquisitions (AQ) contracting officers.

Section C - Descriptions and Specifications

SOO CONTENT

This is a single award Indefinite Quantity Indefinite Delivery (IDIQ) type contract. Task orders shall be issued under this arrangement. Total orders under this contract shall not exceed $50,000,000 including all options periods.

(One-year base, four one-year options). The guaranteed minimum is $100,000 for the basic period only. There is no guaranteed minimum for the option periods, if exercised. Orders may only be issued by the Defense Security Service (DSS) Office of Acquisitions (AQ) contracting officers.

NATIONAL INDUSTRIAL SECURITY SYSTEM (NISS) STATEMENT OF OBJECTIVES (SOO)

Introduction As one of four Government Security Agencies (GSA) directed to implement the National Industrial Security Program (NISP) per Executive Order 12829, the Defense Security Service (DSS) provides Industrial Security Services and training to the Department of Defense (DoD) and twenty-seven other federal agencies. Administering the NISP to cleared contractors eligible to receive, handle, and protect classified information for DoD and the 27 agencies makes DSS responsible for an industrial base that includes over 13,000 cleared facilities, 40,000 classified information systems, and over 10,000 industrial security professionals.

Purpose There is an existing “gap” between DSS Agency capacity and national security requirements being predominantly driven by a summation of challenges found within three Agency operational activities:

1) Process Facility Clearances (FCL)

2) Conduct Proactive Monitoring

3) Manage Incident Response

DSS currently conducts its critical missions without an integrated enterprise information technology architecture.

The lack of an enterprise IT solution results in cumbersome, inefficient, and exceedingly manual processes that jeopardize the success of DSS missions.

Five primary factors that span across the three forenamed operational activities challenge DSS’s ability to effectively administer the NISP and account for Industry’s rapidly evolving security environment:

1. Limited ability to identify vulnerabilities and mitigate the expanding threat through consistent interaction and partnership with Industry, given resource constraints.

2. Increasing reliance on proactive NISP stakeholder partnerships, which can be met with hesitation.

3. Scaled directorates to meet growing mission sets, resulting in potential service delivery overlap.

4. Required Department-level clarity on critical issues, such as cyber defense, fogging the Agency’s ability to determine mission effectiveness.

5. Legacy technological infrastructure out-stripped by modern information security demands, and actually hampering the Agency’s ability to provide timely support to NISP stakeholders.

The National Industrial Security System (NISS) is the working name for a new, automated business information capability that DSS is seeking to replace and expand upon the following legacy systems: Industrial Security Facility Database (ISFD) and the Department of Energy (DoE) hosted but DSS owned Electronic Facility Clearance System (e-FCL). The NISS Solution will be an integrated automated solution that will facilitate efficient execution of the Agency's core mission. It will use available technology to drive smoother user workflows, enhance decision-making through stronger and timelier synthesis of information, and improve transparency pertaining to the National Industrial Security Program (NISP). The NISS requirements capture the desired ISFD and e-FCL functionality, which includes workflows to enable contractor performance, provide proactive oversight, and complete reactive incident response. The DSS managed ISFD system and DoE managed e-FCL system contain DSS data which must be migrated to the NISS database for Full Operational Capability (FOC). The successful vendor may be required to incorporate additional functionality.

NISS will allow users to sift through vast volumes of information and more easily form linkages about a facility and its Key Management Personnel (KMP), effectively closing Industry’s safeguarding gaps, while allowing DSS field personnel to proactively partner with Industry on-site through Security Vulnerability Assessments (SVAs).

Presently critical resources are diverted from meaningful customer engagement and identification of high-risk threats to menial data entry without an effective NISS enterprise IT solution.

High Level Objectives for the NISS approach include the following:

a. Expedited performance against classified contracts

i. Streamlined facility clearance (FCL) processing

ii. Enhanced FOCI identification and mitigation

iii. Accelerated and improved C&A of Industry information systems

iv. Expedited production of quality information

b. Enhanced data linkages to provide full risk profile

i. Increased information sharing and transparency

ii. Automated prioritization of Industry engagement (FIL)

iii. Implemented enterprise risk analytics capability

c. Improved ability to make metrics-based decisions

i. Enhanced automated metrics capture and analysis

d. Improved vulnerability management from identification through mitigation

i. Improved vulnerability reporting through automation

ii. Streamlined vulnerability oversight

iii. Expedited vulnerability mitigation

e. Improved threat management from identification through mitigation

i. Improved threat reporting

ii. Expedited threat mitigation

f. Increased technology effectiveness and mobility

i. Create a mobile technology solution to meet mobile workforce needs

ii. Improve ability to utilize data from multiple sources, classifications, and types in a single location

iii. Improve analysis

iv. Improve discovery of unknown unknowns. Expedite data submission validation

NISS Required System Attributes

Attributes required for the NISS include the following features:

a. BPMN - The Defense Security Service (DSS) requires a product which enables the capturing of business operations through Business Process Modeling and Notation (BPMN) workflows with work prioritization.

b. Workflow Management – The contractor shall provide NISS users with the ability to manage workflow processes and ensures that out-of-the-box vender functional capabilities are available.

c. Facility Profile Creation – The contract shall provide an end product that will ensure that each facility has a profile within NISS that includes information such as the facility address, region, KMP list, corporate website, corporate legal structure, research data, facility actions, alerts, change conditions, workflow status, etc. The system shall visually display parent-child and related ownership hierarchies between facilities and companies.

d. Search/Content Management – The contractor shall provide a system that will enable site-wide searching for internal and external users on various information within NISS. While search functionality provided as native capabilities will likely require further customization to meet Agency needs.

e. Reporting – The contractor shall provide a system that will calculate and display standard metrics related to all DSS processes conducted within the system. Additionally, the system should enable advanced ad-hoc reporting and analytics that can record and report historical transaction and usage data, and conduct real-time validation of the data. Reporting should facilitate the implementation of the risk management framework which includes identification of potential threats to detection of realized impacts, for the Industrial Security Supply Chain. The reporting should enable data-driven decision making to identify risks within the supply chain and enable executive level reporting for performance management.

f. Analytics – The contractor shall provide a system capable of transforming structured and unstructured data to help identify and develop meaningful and actionable information to inform business decisions and identify trends or risks. This analytic capability should allow for the easy interpretation of volumes of data, and provide historical, current and predictive views of internal (DSS) and external (Industry) operations. The system should acquire, process, and correlate data that is within the system, as well as within linked sources.

g. Integration and Interoperability – The contractor shall provide a system that will enable access to data from databases internal and external to DSS to complete internal processes and validate information included in this DSS system of record. The technical solution shall conform to DoD Guidelines and DSS infrastructure. The expectation is that the delivered product will have already incorporated external system integration activities prior to DSS Pre-Production staging.

h. Storage – The contractor shall provide a system that will allow users to upload and save documents as well as unstructured data.

i. Dashboard Portal/Single User Interface – The contractor shall provide a system that will present workflow data, notifications and messages, dependent upon roles and permission level assigned to each user. The graphical user interface (GUI) must be innovative in nature.

j. Auditing – The contractor shall provide a system with the capabilities to ensure that transactional logs of various actions are recorded and saved. This includes, but is not limited to, the overall system transactions and facility profile transactions.

k. Attribute Based Access Control (ABAC) – The contractor shall provide a system that establishes rules for users’ access, roles, and permissions within the NISS, in accordance with NIST SP 800- 162.

l. Help – The contractor shall provide a system that provides access to job aides, FAQs, and other help-related documentation.

m. Mobile Capabilities – The contractor shall provide a system that converts core NISS capabilities into a mobile version for access over mobile devices.

n. Automated Notifications/Alerts/Messaging – The contractor shall provide a system that provides the ability for internal and external users to liberally manage notifications, alerts and messages.

o. Automated Cross Domain Solution (CDS) – The contractor shall provide a system that enables automated transfer of data between NIPR and SIPR without spillage. The developer must enable a bridge for NIPR information to be ingested up to SIPR, and primary unclassified NISS SIPR information to be available down to NIPR. A near real-time, bi-directional cross-domain data solution will be required to be in place at NISS initial deployment. The CDS will be included within and throughout the workflow processes.

p. NoSQL (Not Only SQL) data repository with modular systems integration to allow for multiple transactional systems to utilize, modify and validate data

q. Data Migration – The existing legacy application contains data which will continue to be used and must be migrated into the NISS. The developer must prepare existing data so that it ports into the new system without losing functional meaning and with minimal disruption of service for daily operations. Data fields for the existing and receiving systems shall be formally documented mapping schemas for review and approved by stakeholders for accuracy.

r. GUI Interfaces – The Agency requires internal and external GUI interfaces. The interfaces should automate the exchange of Industrial Facility Clearance data, between DSS internal systems and extra-Agency systems. Timely exchange of this information will allow Agency representatives to execute proactive monitoring, risk response, and assessment responsibilities.

s. Milcloud Development - The winning Proof of Concept (PoC) will be uploaded to and developed by the contractor to the DSS Milcloud environment. Milcloud will serve as the development environment for the NISS. The contractor will be expected to conduct remote development activities within the DSS provided Milcloud environment. The Agency anticipates two possible infrastructure related end states for NISS Production; a MilCloud Production instance or deployment to physical virtualized hardware located in Quantico, VA and Monterey, CA.

NISS Delivery Increments

Anticipated NISS Delivery increments include the following:

a. TASK ORDER 0001: Incorporate ISFD and E-FCL into Core NISS Foundation Capabilities – The first increment will provide DSS with core ISFD and e-FCL capabilities and establishes the foundation for accessing facility data, site navigation, and fundamental application functionality within the NISS. The NISS requirements, as stated, capture the desired ISFD and e-FCL functionality, which includes workflows to enable contractor performance, provide proactive oversight, and complete reactive incident response. The DSS managed ISFD system and DoE managed e-FCL system contain DSS data which must be migrated to the NISS database for Initial Operational Capability (IOC). The first increment will centralize all processes required for managing the initial facility security clearance (IFCL) process. The estimated duration for this increment is anticipated to be roughly 18 months since it will include all core capabilities listed as system attributes. [Requirements Development Document (RDD) Tabs 1, 12 (excluding “Mobile”), and 13]

i. ISFD currently interfaces with the Office of the Designated Approval Authority (ODAA) Business Management System (OBMS). The interface displays Industry System Security Plan counts and plans status for internal users.

The interconnectivity between OBMS and ISFD reduces the dependency of non-Information System Security Professionals to access the OBMS system. Further details are provided in the ISFD-OBMS Interface Document. As the system of record for Industrial Security Facilities Data, ISFD provides facility information for display only within OBMS.

ii. JPAS Extracts - The NISS shall provide real time Industrial Security Facility system updates to the Joint Personnel Adjudication System (JPAS) and its replacement system; Defense Information Security System (DISS).

The data transferred includes but is not limited to facility cage code, FCL, facility name and address.

iii. NCAISS – The NISS shall interface with National Industrial Security Program (NISP) Central Access and Information Security System (NCAISS). NCAISS is the Agency’s single point of entry or portal for DSS managed applications. PKI authentication through NCAISS supports both Common Access Card (CAC) and External Certificate Authority (ECA) certificates. The Agency leadership expects NCAISS interface with NISS to be operational by the completion of Full Operational Capability (FOC). The NISS contractor shall only support interface work related to the NISS application as the NCAISS application is administered under another contract.

Increment One (1) is Task Order 0001. The following increments will be future Task Orders.

b. Increment Two: Security Vulnerability and Incident Response Management – The second increment will provide DSS stakeholders with essential tools and information required to manage security violations, assess vulnerabilities and respond to incident reports. This increment also builds upon the functionalities developed in Increment-I by enhancing existing system functionality. Processes include Security Vulnerability Assessment (SVA), Suspicious Contact Report (SCR), and Security Violation (SV) processing; the estimated duration for this increment is roughly 12 months. [RDD Tabs 9, 10, 11]

i. NISS will interface with the Joint Personnel Adjudication System (JPAS) and its ultimate replacement, Defense Information Security System (DISS) for real time data transfer. Industrial Security Facility related data, including but not limited to the Commercial and Government Entity (CAGE) Code, Facility Clearance (FCL), facility name and address, and Key Management Personnel (KMP) details, will be automatically transmitted from NISS to DISS, once updated. NISS KMP personnel clearance details shall update NISS from DISS updates. The DISS is comprised of Case Adjudication Tracking System (CATS) and Joint Verification System (JVS).

ii. NCCS - NISS shall interface with and provide real-time Industrial Security Facility data updates to the NISP Contractor Classified System (NCCS). The NISS will provide Facility related data, including but not limited to the facility CAGE code, FCL, facility name and address. The NISS-NCCS interface shall be directional; with NCCS contained Contractor information sent to NISS through real-time data updates. Data transferred will include but is not limited to contract number, Government Contracting Agency (GCA), prime contractor and subcontractor information

iii. Cross Domain Solution - The NISS shall leverage the DISA Cross Domain Solution (CDS) for the near-real time transfer of data to the DSS SIPR instance to NISS and unclassified data from SIPR instance of NISS to NIPR version. The Agency expects CDS capabilities to be incorporated into in NISS Increment II delivery.

c. Increment Three: Change Condition Monitoring – The third increment will enable DSS to efficiently and effectively perform change condition monitoring making use of all core facility data availability within the NISS.

This increment allows for refinement of system functionality to be established by the task order. Processes to be incorporated into NISS include Key Management Personnel (KMP) Monitoring, NATO Control Point Inspections (CPI), Triage Outreach Program (TOP), NISP Facility Oversight, and Foreign Visit Requests (FVR). [RDD Tabs 4, 5, 6, 7, 8]

d. Increment Four: Mobile Access Enablement – The fourth increment will provide stakeholders with the ability to access NISS functionality in a mobile environment, increasing workforce productivity during facility site visits and security assessment visits. The estimated duration for this increment is roughly nine (9) months. [RDD Tab 12 “Mobile”]

e. Increment Five: Information System Accreditation - The fifth increment shall enable processing of Industry Stakeholder submitted information system certification and accreditation (C&A) plans through the system and associated transfer, review, and processing in support of the field operations mission to enable industry performance and secure digital classified information. The scope of this increment will be determined at a later date. The estimated duration for this increment is roughly 9 months. [RDD Tab 2]

f. Increment Six: Command Cyber Readiness Inspections (CCRI) - The sixth increment will provide the ability to electronically manage the process of scheduling, conducting, and perfuming follow-up activities related to DISA mandated CCRI inspections. The estimated duration for this increment is roughly 9 months. [RDD Tab 3]

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLIN INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY

0001 Destination Government Destination Government 0002 Destination Government Destination Government 0003 Destination Government Destination Government 0004 Destination Government Destination Government 1001 Destination Government Destination Government 1002 Destination Government Destination Government 1003 Destination Government Destination Government 1004 Destination Government Destination Government 2001 Destination Government Destination Government 2002 Destination Government Destination Government 2003 Destination Government Destination Government 2004 Destination Government Destination Government 3001 Destination Government Destination Government 3002 Destination Government Destination Government 3003 Destination Government Destination Government 3004 Destination Government Destination Government 4001 Destination Government Destination Government 4002 Destination Government Destination Government 4003 Destination Government Destination Government 4004 Destination Government Destination Government

Section G - Contract Administration Data

CLAUSES INCORPORATED BY REFERENCE

252.204-0009 Contract-wide: by Fiscal Year SEP 2009

CLAUSES INCORPORATED BY FULL TEXT

252.201-7000 CONTRACTING OFFICER'S REPRESENTATIVE (DEC 1991)

(a) "Definition. Contracting officer's representative" means an individual designated in accordance with subsection 201.602-2 of the Defense Federal Acquisition Regulation Supplement and authorized in writing by the contracting officer to perform specific technical or administrative functions.

(b) If the Contracting Officer designates a contracting officer's representative (COR), the Contractor will receive a copy of the written designation. It will specify the extent of the COR's authority to act on behalf of the contracting officer. The COR is not authorized to make any commitments or changes that will affect price, quality, quantity, delivery, or any other term or condition of the contract.

(End of clause)

252.232-7003 ELECTRONIC SUBMISSION OF PAYMENT REQUESTS AND RECEIVING REPORTS

(JUNE 2012)

(a) Definitions. As used in this clause–

(1) Contract financing payment and invoice payment have the meanings given in section 32.001 of the Federal Acquisition Regulation.

(2) Electronic form means any automated system that transmits information electronically from the initiating system to all affected systems. Facsimile, e-mail, and scanned documents are not acceptable electronic forms for submission of payment requests. However, scanned documents are acceptable when they are part of a submission of a payment request made using Wide Area WorkFlow (WAWF) or another electronic form authorized by the Contracting Officer.

(3) Payment request means any request for contract financing payment or invoice payment submitted by the Contractor under this contract.

(4) Receiving report means the data required by the clause at 252.246-7000, Material Inspection and Receiving Report.

(b) Except as provided in paragraph (c) of this clause, the Contractor shall submit payment requests and receiving reports using WAWF, in one of the following electronic formats that WAWF accepts: Electronic Data Interchange, Secure File Transfer Protocol, or World Wide Web input. Information regarding WAWF is available on the Internet at https://wawf.eb.mil/.

(c) The Contractor may submit a payment request and receiving report using other than WAWF only when–

(1) The Contracting Officer administering the contract for payment has determined, in writing, that electronic submission would be unduly burdensome to the Contractor. In such cases, the Contractor shall include a copy of the Contracting Officer's determination with each request for payment;

(2) DoD makes payment for commercial transportation services provided under a Government rate tender or a contract for transportation services using a DoD-approved electronic third party payment system or other exempted vendor payment/invoicing system (e.g., PowerTrack, Transportation Financial Management System, and Cargo and Billing System);

(3) DoD makes payment for rendered health care services using the TRICARE Encounter Data System (TEDS) as the electronic format; or

(4) When the Governmentwide commercial purchase card is used as the method of payment, only submission of the receiving report in electronic form is required.

(d) The Contractor shall submit any non-electronic payment requests using the method or methods specified in Section G of the contract.

(e) In addition to the requirements of this clause, the Contractor shall meet the requirements of the appropriate payment clauses in this contract when submitting payments requests.

252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (MAY 2013)

(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 System for Award Management 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, or File Transfer Protocol.

(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).

2-in-1

(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.

N/A

(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* Field Name in WAWF Data to be entered in WAWF Pay Official DoDAAC HQ0690 Issue By DoDAAC HS0021 Admin DoDAAC HS0021 Inspect By DoDAAC ____ Ship To Code HS0001 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 email address identified below in the “Send Additional Email Notifications” field of WAWF once a document is submitted in the system.

TBD

(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.

TBD

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

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

Section H - Special Contract Requirements

252.234-7002 EARNED VALUE MANAGEMENT SYSTEM (MAY 2011)

(a) Definitions. As used in this clause--

Acceptable earned value management system means an earned value management system that generally complies with system criteria in paragraph (b) of this clause.

Earned value management system means an earned value management system that complies with the earned value management system guidelines in the Integrated Program Management Report (IPMR) Data Item Description (DID) also known as IPMR DID.

Significant deficiency means a shortcoming in the system that materially affects the ability of officials of the Department of Defense to rely upon information produced by the system that is needed for management purposes.

(b) System criteria. In the performance of this contract, the Contractor shall use--

(1) An Earned Value Management System (EVMS) that complies with the EVMS guidelines in the American National Standards Institute/Electronic Industries Alliance Standard 748, Earned Value Management Systems (ANSI/EIA-748); and EVM DID (DI-MGMT-81861) IPMR.

(2) Management procedures that provide for generation of timely, reliable, and verifiable information for the IPMR DID items 1-7 are required data items of this contract.

(c) If this contract has a value of $50 million or more, the Contractor shall use an EVMS that has been determined to be acceptable by the Cognizant Federal Agency (CFA). If, at the time of award, the Contractor's EVMS has not been determined by the CFA to be in compliance with the EVMS guidelines as stated in paragraph (b)(1) of this clause, the Contractor shall apply its current system to the contract and shall take necessary actions to meet the milestones in the Contractor's EVMS plan.

(d) If this contract has a value of less than $50 million, the Government will not make a formal determination that the Contractor's EVMS complies with the EVMS guidelines in ANSI/EIA-748 with respect to the contract. The use of the Contractor's EVMS for this contract does not imply a Government determination of the Contractor's compliance with the EVMS guidelines in IPMR DID for application to future contracts. The Government will allow the use of a Contractor's EVMS that has been formally reviewed and determined by the CFA to be in compliance with the EVMS guidelines in IPMR DID.

(e) The Contractor shall submit notification of any proposed substantive changes to the EVMS procedures and the impact of those changes to the CFA. If this contract has a value of $50 million or more, unless a waiver is granted by the CFA, any EVMS changes proposed by the Contractor require approval of the CFA prior to implementation. The CFA will advise the Contractor of the acceptability of such changes as soon as practicable (generally within 30 calendar days) after receipt of the Contractor's notice of proposed changes. If the CFA waives the advance approval requirements, the Contractor shall disclose EVMS changes to the CFA at least 14 calendar days prior to the effective date of implementation.

(f) The Government will schedule integrated baseline reviews as early as practicable, and the review process will be conducted not later than 180 calendar days after--

(1) Contract award;

(2) The exercise of significant contract options; and

(3) The incorporation of major modifications.

During such reviews, the Government and the Contractor will jointly assess the Contractor's baseline to be used for performance measurement to ensure complete coverage of the statement of work, logical scheduling of the work activities, adequate resourcing, and identification of inherent risks.

(g) The Contractor shall provide access to all pertinent records and data requested by the Contracting Officer or duly authorized representative as necessary to permit Government surveillance to ensure that the EVMS complies, and continues to comply, with the performance criteria referenced in paragraph (b) of this clause.

(h) When indicated by contract performance, the Contractor shall submit a request for approval to initiate an over-target baseline or over-target schedule to the Contracting Officer. The request shall include a top-level projection of cost and/or schedule growth, a determination of whether or not performance variances will be retained, and a schedule of implementation for the rebaselining. The Government will acknowledge receipt of the request in a timely manner (generally within 30 calendar days).

(i) Significant deficiencies.

(1) The Contracting Officer will provide an initial determination to the contractor, in writing, on any significant deficiencies. The initial determination will describe the deficiency in sufficient detail to allow the Contractor to understand the deficiency.

(2) The Contractor shall respond within 30 days to a written initial determination from the Contracting Officer that identifies significant deficiencies in the Contractor's EVMS. If the Contractor disagrees with the initial determination, the Contractor shall state, in writing, its rationale for disagreeing.

(3) The Contracting Officer will evaluate the Contractor's response and notify the Contractor, in writing, of the Contracting Officer's final determination concerning--

(i) Remaining significant deficiencies;

(ii) The adequacy of any proposed or completed corrective action;

(iii) System noncompliance, when the Contractor's existing EVMS fails to comply with the earned value management system guidelines in the IPMR DID; and

(iv) System disapproval, if initial EVMS validation is not successfully completed within the timeframe approved by the Contracting Officer, or if the Contracting Officer determines that the Contractor's earned value management system contains one or more significant deficiencies in high-risk guidelines in IPMR DID standards. When the Contracting Officer determines that the existing earned value management system contains one or more significant deficiencies in one or more of the remaining seven (7) guidelines in IPMR DID standards, the contracting officer will use discretion to disapprove the system based on input received from functional specialists and the auditor.

(4) If the Contractor receives the Contracting Officer's final determination of significant deficiencies, the Contractor shall, within 45 days of receipt of the final determination, either correct the significant deficiencies or submit an acceptable corrective action plan showing milestones and actions to eliminate the significant deficiencies.

(j) Withholding payments. If the Contracting Officer makes a final determination to disapprove the Contractor's EVMS, and the contract includes the clause at 252.242-7005, Contractor Business Systems, the Contracting Officer will withhold payments in accordance with that clause.

(k) With the exception of paragraphs (i) and (j) of this clause, the Contractor shall require its subcontractors to comply with EVMS requirements as follows:

(1) For subcontracts valued at $50 million or more, the following subcontractors shall comply with the requirements of this clause:

[Contracting Officer to insert names of subcontractors (or subcontracted effort if subcontractors have not been selected) designated for application of the EVMS requirements of this clause.]

TBD

(2) For subcontracts valued at less than $50 million, the following subcontractors shall comply with the requirements of this clause, excluding the requirements of paragraph (c) of this clause:

[Contracting Officer to insert names of subcontractors (or subcontracted effort if subcontractors have not been selected) designated for application of the EVMS requirements of this clause.]

TBD

Section I - Contract Clauses

52.202-1 Definitions NOV 2013 52.203-3 Gratuities APR 1984 52.203-5 Covenant Against Contingent Fees MAY 2014 52.203-7 Anti-Kickback Procedures MAY 2014 52.203-8 Cancellation, Rescission, and Recovery of Funds for Illegal or

Improper Activity

MAY 2014

52.203-10 Price Or Fee Adjustment For Illegal Or Improper Activity MAY 2014 52.203-11 Certification And Disclosure Regarding Payments To

Influence Certain Federal Transactions

SEP 2007

52.203-12 Limitation On Payments To Influence Certain Federal Transactions

OCT 2010

52.203-13 Contractor Code of Business Ethics and Conduct APR 2010 52.203-14 Display of Hotline Poster(s) DEC 2007 52.204-2 Security Requirements AUG 1996 52.204-7 System for Award Management JUL 2013 52.204-12 Data Universal Numbering System Number Maintenance DEC 2012 52.215-2 Audit and Records--Negotiation OCT 2010 52.215-8 Order of Precedence--Uniform Contract Format OCT 1997 52.215-14 Integrity of Unit Prices OCT 2010 52.215-15 Pension Adjustments and Asset Reversions OCT 2010 52.215-16 Facilities Capital Cost of Money JUN 2003 52.215-18 Reversion or Adjustment of Plans for Postretirement Benefits

(PRB) Other than Pensions

JUL 2005

52.215-19 Notification of Ownership Changes OCT 1997 52.215-22 Limitations on Pass-Through Charges--Identification of

Subcontract Effort

OCT 2009

52.215-22 Limitations on Pass-Through Charges--Identification of Subcontract Effort

OCT 2009

52.215-23 Limitations on Pass-Through Charges OCT 2009 52.216-7 Allowable Cost And Payment JUN 2013 52.216-8 Fixed Fee JUN 2011 52.217-4 Evaluation Of Options Exercised At The Time Of Contract

Award

JUN 1988

52.217-5 Evaluation Of Options JUL 1990 52.217-9 Option To Extend The Term Of The Contract MAR 2000 52.219-4 Notice of Price Evaluation Preference for HUBZone Small

Business Concerns

OCT 2014

52.219-8 Utilization of Small Business Concerns OCT 2014 52.222-1 Notice To The Government Of Labor Disputes FEB 1997 52.222-21 Prohibition Of Segregated Facilities FEB 1999 52.222-26 Equal Opportunity MAR 2007 52.222-50 Combating Trafficking in Persons FEB 2009 52.223-18 Encouraging Contractor Policies To Ban Text Messaging

While Driving

AUG 2011

52.225-13 Restrictions on Certain Foreign Purchases JUN 2008 52.225-25 Prohibition on Contracting with Entities Engaging in Certain

Activities or Transactions Relating to Iran-- Representation and Certifications.

DEC 2012

52.227-1 Authorization and Consent DEC 2007

52.227-2 Notice And Assistance Regarding Patent And Copyright Infringement

DEC 2007

52.228-7 Insurance--Liability To Third Persons MAR 1996 52.232-18 Availability Of Funds APR 1984 52.232-22 Limitation Of Funds APR 1984 52.232-39 Unenforceability of Unauthorized Obligations JUN 2013 52.232-40 Providing Accelerated Payments to Small Business

Subcontractors

DEC 2013

52.233-1 Disputes MAY 2014 52.233-2 Service Of Protest SEP 2006 52.233-3 Alt I Protest After Award (Aug 1996) - Alternate I JUN 1985 52.233-4 Applicable Law for Breach of Contract Claim OCT 2004 52.242-1 Notice of Intent to Disallow Costs APR 1984 52.242-4 Certification of Final Indirect Costs JAN 1997 52.243-2 Alt V Changes--Cost-Reimbursement (Aug 1987) - Alternate V APR 1984 52.243-6 Change Order Accounting APR 1984 52.245-1 Government Property APR 2012 52.245-9 Use And Charges APR 2012 52.246-5 Inspection Of Services Cost-Reimbursement APR 1984 52.246-9 Inspection Of Research And Development (Short Form) APR 1984 52.247-17 Charges APR 1984 52.247-27 Contract Not Affected by Oral Agreement APR 1984 52.247-64 Alt II Preference for Privately Owned U.S. - Flag Commercial

Vessels (Apr 2003) - Alternate II

FEB 2006

52.249-6 Termination (Cost Reimbursement) MAY 2004 52.253-1 Computer Generated Forms JAN 1991 252.203-7000 Requirements Relating to Compensation of Former DoD

Officials

SEP 2011

252.203-7002 Requirement to Inform Employees of Whistleblower Rights SEP 2013 252.204-7000 Disclosure Of Information AUG 2013 252.204-7003 Control Of Government Personnel Work Product APR 1992 252.204-7005 Oral Attestation of Security Responsibilities NOV 2001 252.211-7007 Reporting of Government-Furnished Property AUG 2012 252.225-7001 Buy American And Balance Of Payments Program-- Basic

(Nov 2014)

NOV 2014

252.225-7002 Qualifying Country Sources As Subcontractors DEC 2012 252.225-7013 Duty-Free Entry--Basic (Nov 2014) NOV 2014 252.225-7048 Export-Controlled Items JUN 2013 252.227-7013 Rights in Technical Data--Noncommercial Items FEB 2014 252.227-7014 Rights in Noncommercial Computer Software and

Noncommercial Computer Software Documentation

FEB 2014

252.227-7016 Rights in Bid or Proposal Information JAN 2011 252.227-7019 Validation of Asserted Restrictions--Computer Software SEP 2011 252.227-7030 Technical Data--Withholding Of Payment MAR 2000 252.227-7037 Validation of Restrictive Markings on Technical Data JUN 2013 252.227-7038 Patent Rights--Ownership by the Contractor (Large Business) JUN 2012 252.232-7010 Levies on Contract Payments DEC 2006 252.234-7001 Notice of Earned Value Management System APR 2008 252.235-7011 Final Scientific or Technical Report NOV 2004 252.237-7010 Prohibition on Interrogation of Detainees by Contractor

Personnel

JUN 2013

252.239-7017 Notice of Supply Chain Risk NOV 2013 252.242-7005 Contractor Business Systems FEB 2012 252.242-7006 Accounting System Administration FEB 2012 252.244-7000 Subcontracts for Commercial Items JUN 2013

252.245-7001 Tagging, Labeling, and Marking of Government-Furnished Property

APR 2012

252.245-7002 Reporting Loss of Government Property APR 2012 252.245-7003 Contractor Property Management System Administration APR 2012 252.245-7004 Reporting, Reutilization, and Disposal MAY 2013 252.247-7023 Alt II Transportation of Supplies by Sea (APR 2014) Alternate II APR 2014

52.204-5 WOMEN-OWNED BUSINESS (OTHER THAN SMALL BUSINESS) (OCT 2014)

(a) Definition. Women-owned business concern, as used in this provision, means a concern that is at least 51 percent owned by one or more women; or in the case of any publicly owned business, at least 51 percent of its stock is owned by one or more women; and whose management and daily business operations are controlled by one or more women.

(b) Representation. [Complete only if the offeror is a women-owned business concern and has not represented itself as a small business…