Section_L_-_Amend_0001.pdf

HC1028-16-R-0007

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to:

A. Answ er questions received.

B. Provide the follow ing revised documents: Section C - TEC PWS; UC SOW; DJFAS SOW; SODAS PWS; Section L; Section M; Section J Attachment 6 – Task Order 0001 (FFP); Section J Attachment 8 – FFP Pricing Scenario; and add one additional document added to Bidder’s Library (DISA Mandatory Contractor Training).

1. CONTRACT ID CODE PAGE OF PAGES

S 1 3

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 27-Oct-2016

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X HC1028-16-R-0007

X 9B. DATED (SEE ITEM 11)

29-Sep-2016

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

27-Oct-2016

CODE

DISA/DITCO-SCOTT-PL83

2300 EAST DRIVE

SCOTT AFB IL 62225-5406

HC1028 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0001

The pricing detail quantity has increased by 12.00 from 12.00 to 24.00.

CLIN 4001

The pricing detail quantity has decreased by 6.00 from 12.00 to 6.00.

SECTION F - DELIVERIES OR PERFORMANCE

The following Delivery Schedule item for CLIN 0001 has been changed from:

DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC

POP 29-JUL-2017 TO

28-JUL-2019

N/A N/A

FOB: Destination

To:

DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC

POP 29-JUL-2017 TO

28-JUL-2019

The following Delivery Schedule item for CLIN 4001 has been changed from:

POP 29-JUL-2022 TO

28-JAN-2023

To:

POP 29-JUL-2022 TO

28-JAN-2023

SECTION I - CONTRACT CLAUSES

The following have been modified:

52.216-19 ORDER LIMITATIONS. (OCT 1995)

(a) Minimum order. When the Government requires supplies or services covered by this contract in an amount of less than $500, the Government is not obligated to purchase, nor is the Contractor obligated to furnish, those supplies or services under the contract.

(b) Maximum order. The Contractor is not obligated to honor:

(1) Any single task order in excess of $12,000,000.00

(2) Any combination of task orders issued in a 30-day period that are in excess of $50,000,000.00 or

(c) If this is a requirements contract (i.e., includes the Requirements clause at subsection 52.216-21 of the Federal Acquisition Regulation (FAR)), the Government is not required to order a part of any one requirement from the Contractor if that requirement exceeds the maximum-order limitations in paragraph (b) above.

(d) Notwithstanding paragraphs (b) and (c) above, the Contractor shall honor any order exceeding the maximum order limitations in paragraph (b), unless that order (or orders) is returned to the ordering office within 10 days after issuance, with written notice stating the Contractor's intent not to ship the item (or items) called for and the reasons.

Upon receiving this notice, the Government may acquire the supplies or services from another source.

(End of clause)

(End of Summary of Changes)

TEC Services Contract Page 1 of 12 Pages Sample Task Order 2016-10-26

Joint Interoperability Test Command Special Operations DNA Analysis Solutions (SODAS) Test and Evaluation Support

Performance Work Statement

Contract Number:

Task Order Number:

Tracking Number:

Follow-on to Previous Contract and Task Order Number:

1. Contracting Officer’s Representative (COR).

1.1. Primary COR.

Name:

Organization:

Department of Defense Activity Address Code (DODAAC):

Address:

Phone Number:

Fax Number:

E-Mail Address:

1.2. Alternate COR.

Name:

Organization:

DODAAC:

Address:

Phone Number:

Fax Number:

E-Mail Address:

2. Contract or Task Order (TO) Title. Joint Interoperability Test Command (JITC) Special Operations Deoxyri-bonucleic Acid (DNA) Analysis Solutions (SODAS) Test and Evaluation Cost Plus Fixed Fee (CPFF) Support

3. Background.

3.1. The United States Special Operations Command (USSOCOM) requires Test and Evaluation (T&E) support from JITC to plan, conduct, and report the results of a biometric-related capability assessment. USSOCOM is a unified command, tasked with the responsibility of preparing for and conducting special operations. To enable USSOCOM to carry out its mission, the command is empowered with certain Title 10 authorities and responsibilities. Among these is the responsibility and authority to develop and acquire Special Operations Forces (SOF)-unique equipment, material, supplies, and services. These special circumstances allow USSOCOM to develop and field capabilities at a much more rapid pace than conventional forces (e.g., Army, Navy, Air Force, and Marines). SOF Acquisition, Technology and Logistics (AT&L) is the acquisition arm of USSOCOM. Under SOF AT&L, the Program Manager for Tactical Biometrics (PM-TB) manages the acquisition, fielding, sustainment, and evolutionary enhancement of specialized exploitation, biometric, and forensic data collection and processing devices that support SOF mission planning and execution. SOF biometric capabilities are in various stages of the acquisition cycle. Acquisition plans incorporate strategies for Information Technology (IT) insertion as a means to

TEC Services Contract Page 2 of 12 Pages provide continuous and timely enhancement of SOF warfighting capabilities. These devices directly support USSOCOM's priorities to deter, disrupt, and defeat terrorist threats, as well as sustain and modernize the force.

3.2. As part of this overall effort and in support of properly resourcing deployed Exploitation Analysis Centers (EAC), PM-TB is exploring commercial options to provide SOF with the ability to rapidly capture, digitize, and exploit an individual’s DNA. The primary objective of a new PM-TB program called Special Operations DNA Analysis Solutions (SODAS) is to support “Detain or Release” decisions when SOF teams encounter and detain potential “persons of interest” during operations. SODAS will support this objective, while ensuring the DNA data collected and stored is both secure and discoverable by EAC users with appropriate access credentials.

3.3. The PM-TB plans to host two SODAS capability assessment “bake-off” test events to collect both performance data and user feedback regarding candidate solutions. The T&E events are projected to include four vendor-provided SODAS DNA screening capabilities and associated components; the outcome of the T&E events may result in the selection of one device for operational deployment to an EAC. The first T&E event will take place in a controlled laboratory environment. The second T&E event will take place in a field environment with representative operational users. In support of these events, the contractor will provide T&E planning, execution, analysis and reporting services. The contractor will collect and analyze data to characterize how well the SODAS solutions meet specified requirements and will present the results to PM-TB, but will not provide a recommendation for acquiring one system over another. The following candidate systems (ten each Hand-held DNA collection devices and one docking station/database system will be provided) are scheduled to participate in both T&E events:

• DNA Evaluator

• Fast DNA

• Bio Inspector

• DNA Now

3.4. As part of a deployed EAC, SODAS components will operate as depicted in Figure 1. Each SODAS system must provide 10 Hand-held DNA collection devices and a local docking station/database system. The connection between the Hand-held device and the docking station/database shall support secure wireless and wired connectivi-ty, and must meet National Institute of Standards and Technology (NIST) encryption standards. In the SODAS local database, data must meet Armed Forces DNA Identification Laboratory (AFDIL) eXtensible Markup Lan-guage (XML) Data and Secure Hash Algorithm 3-512 (SHA3-512) Hashing standards. In addition, the SODAS system must apply defined XML tags, listed in Figure 3, to the DNA records to ensure the data can be discovered by authorized EAC users via a database query.

3.5. Figure 1 depicts the SODAS data flow; SODAS system components are reflected in blue, while the data flow is purple. The SODAS data flow starts with the Hand-held DNA collection device that connects to the docking sta-tion via a secure Radio Frequency (RF) Link to send DNA data (i.e., profile) that characterizes each DNA sample.

The SODAS system uses wired Internet Protocol (IP) connectivity to connect into the local EAC Network. The EAC Network has a NIPRNet Gateway which allows for connectivity to the Armed Forces DNA Identification La-boratory (AFDIL) and the Public Key Infrastructure (PKI) Server. The SODAS local database system then con-nects to the AFDIL Analysis Request Portal, shown in green, and uploads the DNA Analysis request. Once AFDIL has compared the DNA record(s) to those in its Authoritative Database and has identified the Detain/Release status, the AFDIL Analysis Request Portal will send an update to the SODAS system. The SODAS system will then up-date the Detain/Release information on the SOF Exploitation Node’s Portal that is accessible to EAC users via local workstations. Furthermore, up to five simultaneous authorized users/administrators can access the SODAS data-base; however, only administrators can change/update a record. Data should be searchable via date the DNA sam-ple was collected, the location of the DNA collection, and name of the person who collected the DNA sample. The SODAS system will track changes and annotate the administrator’s credentials in the updated record.

TEC Services Contract Page 3 of 12 Pages

Figure 1. SODAS Data Flow Diagram

3.6. Figure 2 depicts the interactions between the user and the Hand-held DNA collection device. When the user is assigned to the subject of the DNA collection, the user must install his PKI credential certificates for the mission.

The Hand-held device shall synch with the Global Positioning System (GPS) and the docking station via secure Radio Frequency (RF), and then indicate the status (green or red lights) for both GPS and RF; both lights must be green for the DNA collector to start processing the sample. Once a subject’s DNA sample is entered for processing, the user initiates the Hand-held to start processing. The Hand-held shall provide the user with feedback that it is still processing (red light) or has completed processing (green light) the DNA. As part of the DNA processing se-quence, the user shall input the name and physical condition of the subject of the DNA sample. Once the Hand-held has completed processing, it will queue the information for transmission to the SODAS docking station. The SO- DAS Hand-held DNA collection device shall allow a transmission queue of up to 100 DNA analysis request sam-ples. As mission parameters allow, the user shall initiate the RF transmission of DNA analysis requests. The Hand-held shall give the user positive feedback (green light) for the successful receipt of each DNA analysis request rec-ord by the docking station.

TEC Services Contract Page 4 of 12 Pages

Figure 2. SODAS Hand-held DNA Collection Device Process Flow Diagram

3.7. Figure 3 reflects a notional XML structure associated with each DNA sample’s record in the SODAS data-base. The fields represent the minimum implementation; additional fields may be appropriate.

TEC Services Contract Page 5 of 12 Pages

Date Collected <dd/mm/yyyy HH:MM Zulu> Name of Individual <First Name> <Middle Initial> <Last Name> Collection Device ID# <########> Name of Collector <First Name> <Middle Initial> <Last Name> Location of Collection <Lat> <Long> Individuals Condition <Alive/Wounded/Dead> AFDIL DNA Sequence <Data> AFDIL DNA Sequence NIST SHA-3 <Data> AFDIL Request <Y/N>

Y - Date of Request <dd/mm/yyyy HH:MM Zulu> Received AFDIL Response <Y/N>

Y - AFDIL Response <Detain/Release> Y - Date of Response <dd/mm/yyyy HH:MM Zulu>

Possible Alias <Y/N> Y – Alias 1 <Alias Name>

Record last updated <dd/mm/yyyy HH:MM Zulu>

AFDIL

DNA

XML

Req.

Format

Figure 3. SODAS XML Data Structure Requirement

3.8. SODAS Hand-held Requirements. Considering the full range of the following environmental conditions below, users must be able to obtain and process DNA with 95 percent reliability that a physical sample is correctly processed (profile remains in-tact) and is usable for identification and data sharing purposes.

3.8.1 Users shall be able to collect and process DNA samples in a temperature range of 32 degrees Fahrenheit through 125 degrees Fahrenheit.

3.8.2 Users shall be able to collect and process DNA samples in windy conditions up to 30 knots.

3.8.3 Users shall be able to collect and process DNA samples when weather conditions are at or below 90 per-cent humidity.

3.8.4 Users will not collect and process DNA samples outdoors during periods of rain, snow, or other precipita-tion.

4. Objectives:

4.1 The Contractor shall submit a proposal describing their approach for T&E support of the SODAS. The detailed approach will reflect data collection to support the following attributes that PM-TB has indicated as potentially discriminating factors between the candidate systems.

4.1.1. DNA samples are accurately processed by the Hand-held DNA collection device under all specified operational conditions.

TEC Services Contract Page 6 of 12 Pages

4.1.2. Single record DNA processing and secure transmission times meets threshold requirements for security and timeliness.

4.1.3. DNA XML metadata adheres to minimum specified implementations reflected in Figure 3.

4.1.4. DNA data records in the local database are discoverable and accessible only by authorized users.

4.1.5. SODAS must allow up to five simultaneous authenticated users within the EAC Network to query the

SODAS database and/or modify DNA records.

4.1.6. Tactical usability of the SODAS Hand-held DNA collection device.

4.1.7. Hand-held DNA collection device meets size and weight specifications.

5. Scope.

5.1. The Contractor shall support T&E (planning, execution, analysis, and reporting) for the two SODAS assess-ment events sponsored by PM-TB.

5.2. The Contractor’s T&E methodology provided in the response to this PWS shall reflect concepts in the DOT&E memorandum, “Best Practices for Assessing the Statistical Adequacy of Experimental Designs Used in Operational Test and Evaluation,” July 2013.

Figure 4. SODAS Test Configuration

5.3. For both of the test events, PM-TB will provide a test AFDIL site through a test NIPRNet Gateway, as de-picted in Figure 4. Additionally the PM-TB will provide a local SOF Exploitation Node Portal; 10 local work-stations on the EAC network; and a Test Non-Secure Internet Protocol Router Network (NIPRNet) Gateway on the

TEC Services Contract Page 7 of 12 Pages

EAC Network connected to a test PKI Server with 55 test certificates. The PKI certificates will be assigned as fol-lows: 40 for SOF DNA collectors, 10 for Local SOF Exploitation Node users, and 5 for Local SOF Exploitation Node administrators. The test configuration is identical to that employed in the operational environment. The four different SODAS candidate systems will be hosted on separate subnetworks to ensure SODAS systems are isolated from each other. Local workstations will be able to reach each SODAS candidate system to access the associated SODAS database.

5.4. The PM-TB will provide both T&E venues for a total of 15 working days, each with 10-hour test times, with an additional one-hour start up and one-hour close down, for a total of 12-hour daily access to the site. Additional details regarding the test events are as follows:

5.4.1. Laboratory Test Event – This five-day T&E event will take place at the National Forensic Science Tech-nology Center in Largo, Florida. Testers will be able to vary temperature between 10o Fahrenheit and 130o Fahren-heit; humidity levels between 20% and 95%; and wind conditions between 0 and 45 knot winds. PM-TB will pro-vide two trained DNA collectors for each of the four candidate systems and 20 subjects that will provide DNA sam-ples for the test, with two of those individuals being marked as “Detain” in the test AFDIL Database.

5.4.2. Field Test Event – This two-week T&E event will take place at Fort Bragg, North Carolina. The test event will be broken into two parts. The first week’s testing will be conducted during daylight hours, while the second week’s testing will support night operations. There is no testing on the weekends, and there are two make-up days (one per week) in the schedule if needed. The Field Test operations are described as:

5.4.2.1. PM-TB will provide four teams of SOF personnel, each with ten members.

5.4.2.2. PM-TB will design four scenarios that the SOF teams will rotate through during each week of the Field

Test Event.

5.4.2.3. Each scenario will employ 20 subjects who will provide DNA samples for the test, with two of those indi-viduals being marked as “Detain” in the test AFDIL Database.

5.4.2.4. Each scenario will commence with the SOF team receiving a 15-minute refresher training module on the specific SODAS Hand-held device they are assigned.

5.4.2.5. Each SOF team member will have a Collector PKI certificate.

5.4.2.6. Each team will use all ten of the provided Hand-held devices per candidate systems listed in Paragraph 3.3.

5.4.2.7. The SOF teams will execute the same 1.5 hour scenario four times in a test day, using a different Hand-held unit of candidate SODAS systems for each scenario run.

5.4.2.8. The four SOF teams will be running through their scenarios simultaneously and switching to a different

Hand-held DNA collection device after completion of each scenario run.

5.4.2.9. SOF team members will be asked to complete a user survey at the end of each scenario run.

5.4.2.10. User surveys must reflect the concepts in the Director, Operational Test and Evaluation (DOT&E) memo-randum, “Guidance on the Use and Design of Surveys in Operational Test and Evaluation,” June 2014.

5.4.2.11. The four SOF teams will support a different scenario each successive day until each team uses each of the candidate Hand-held devices in each scenario during daylight hours and repeats the sequence during night operations.

6. Performance Requirements.

6.1. Task 1. Test Support. The Contractor shall support planning for, conducting, and reporting the results for the SODAS capability assessment, with two test events (the Laboratory Test Event and the Field Test Event). In providing this support, the Contractor shall conduct the following subtask activities:

6.1.1. Subtask 1 – T&E Planning. In support of both SODAS test events, the Contractor shall develop a test plan using T+- dates to support the conduct of each test event, with T being the day the test starts. Data for this event will be considered Unclassified Protected Health Information (PHI) due to DNA analysis results of individuals. In the test plan, the Contractor shall provide the following information:

a. Test event purpose, scope, and objectives.

TEC Services Contract Page 8 of 12 Pages

b. Test methods, based on Science-Based Test Design (SBTD) approaches, for addressing each test objective, to include required sample sizes and analysis methods.

c. Detailed test procedures specifying data collection sources and methods.

d. Test event schedule of planned test activities by day and hour.

e. Resource requirements to conduct each test event to include test personnel (test director, data collectors, etc.), instrumentation and automation to support data collection, administrative, and travel.

Deliverable: (To be provided with the response to this PWS)

a. Test Plan (includes both the Laboratory and Field Test Events)

6.1.2. Subtask 2. T&E Event Execution. In support of the SODAS test events, the Contractor shall carry out the test execution, data collection and analysis activities called for in the test plan.

Deliverables:

a. Test data collected

b. Test Incident Reports (TIRs)

c. Daily T&E Hot wash - during T&E events 1800 daily or 0400 during Night Operations

6.1.3. Subtask 3. T&E Reporting. In support of the SODAS test events, the Contractor shall develop both a test results briefing and a test report summarizing test findings against each of the test event objectives. The test event results briefing shall provide an overview of test event findings and shall be provided to the Government within seven working days of the completion of each test event. The test event report shall provide detailed analysis, findings, and recommendations and shall be provided to the Government within 30 working days of the completion of the Field Test Event. Analysis and Reporting will be considered unclassified, and reporting shall not include any PHI information.

Deliverables:

a. Data Analysis

b. Test Results Briefings

c. Test Report

6.2. Task 2. SODAS Instrumentation and Automation Support. The Contractor shall describe their proposed approach for providing automation and instrumentation support to the T&E of SODAS and other similar Information Technology (IT)-based systems. The Contractor’s proposed approach for providing T&E automation and instrumentation support must account for both T&E activities performed within JITC testbed and laboratory facilities, as well as T&E activities performed at customer and field locations. The Contractor’s proposed T&E automation and instrumentation capabilities shall address the support of the following T&E functions:

a. Test requirements management

b. Test configuration management

c. Functional testing

TEC Services Contract Page 9 of 12 Pages

d. Performance, capacity, and stress testing

e. Standards verification

f. Security compliance and vulnerability assessment

g. Simulation and modeling of physical systems, interfaces, and information exchanges

h. Test incident or anomaly reporting

i. Test data management and validation

j. Test data analysis and reporting

Deliverable: T&E Automation and Instrumentation Support Whitepaper (To be provided with the response to this PWS). White paper format shall consist of:

Title —

Introduction —

Problem Definition —

Solution

Details —

Benefits/Limitations —

Summary —

7. Performance Standards.

Performance Areas Acceptable Quality Level (AQL) Method of Surveillance Applicable to all delivera-bles associated with this

PWS

• Final deliverables shall not exceed, on average, more than one error per page over the entire page count of the deliverable.

• The Contractor shall correct all errors associated with a final deliverable within five (5) business days of being notified of such errors

• 100% inspection of deliver-ables.

• CORs will perform monthly inspection of contract deliv-erables and document results in the CORT Tool.

Note: A “Final Deliverable” is defined as a product for which all Government comments to prior draft or interim versions of the deliverable have been satisfactorily addressed by the contractor such that the content, form, and for-mat of the product on delivery to the Government is sufficiently accurate, complete, technically sound, and free from spelling, punctuation, syntax, and grammatical errors that it is ready for final government review, staffing, acceptance, and signature.

8. Place of Performance. The primary facility location is at JITC Headquarters, Ft. Huachuca, Arizona, with the T&E events taking place at the National Forensic Science Technology Center in Largo, Florida and at Fort Bragg, North Carolina.

8.1. Weekend/Federal Holiday: Work on weekends or federal holidays may be authorized. Prior coordination with the Government COR is required.

TEC Services Contract Page 10 of 12 Pages

8.2. Overtime, after-hours support, and compensatory time may be required to support contingencies and testing activities. Prior coordination with the Government COR is required before the start of work.

8.3. Flex Time: Since the work involved will require very close coordination with customers in a variety of loca-tions, flex time may be approved if addressed in the proposal; otherwise, other alternatives must be addressed in the proposal. Prior coordination with the Government COR is required.

8.4. Travel: Travel may be required. Prior to traveling, the contractor is required to coordinate with the Govern-ment COR. Travel arrangements must be coordinated via email with the Government COR, such as lodging, rental cars, air travel, etc., prior to final travel arrangements to confirm trip is still necessary. Visit Access Requests should be initiated by the contractor for sites requiring verification of security clearance.

8.5. Alternate Place of Performance – Contingency Only. As determined by the COR, contractor employees may be required to work at an alternate place of performance (e.g., home, the contractor's facility, or another approved activity within the local travel area) in cases of unforeseen conditions or contingencies (e.g., pandemic conditions, exercises, government closure due to inclement weather, etc.). Non-emergency/non-essential contractors should not report to a closed government facility. Contractor shall prepare all deliverables and other contract documentation utilizing contractor resources. To the extent possible, the Contractor shall use best efforts to provide the same level of support as stated in the PWS.

9. Period of Performance. November 1, 2017 – 30 March 2018

9.1. As directed by the Contracting Officer (KO), the contractor shall continue performance in emergency or mis-sion essential conditions. Additionally, the Contractor may be required to account for the whereabouts of their per-sonnel should this information be requested by the COR.

10. Delivery Schedule.

PWS

Task#

Deliverable Title

Format Due Date Distribu-tion/Copies

Frequency and Remarks

6.1.1 SODAS Test

Plan (includes both Lab Event and Field Test)

MS Word

To be provided in response to this PWS

6.1.2 Daily T&E Hot

wash

MS Word For-mat

1800 daily during T&E events or 0400 during Night Opera-tions

Email

6.1.3.b SODAS T&E Emerging Results Briefings

MS Power Point using

DISA/JITC

Template

7 working days after conclusion of each T&E event

Email with hard copy provided to the COR

6.1.3.c SODAS T&E Reports

MS Word 30 calendar days after conclusion of both the Lab and Field Tests

Email with hard copy provided to the COR

1 Report per option year

6.2 T&E

Automation and Instrumentation Support Whitepaper

MS Word

To be provided in response to this PWS

11. Security Requirements. SECRET.

TEC Services Contract Page 11 of 12 Pages

11.1. References:

11.1.1. DOD 5200.2-R, DOD Personnel Security Program.

11.1.2. DISAI 240-110-36, Personnel Security.

11.1.3. DOD 5220.22-M, National Industrial Security Program Operating Manual.

11.1.4. DOD 5220.22-R, Industrial Security Regulation.

11.1.5. DISA Computing Services Directorate (CSD) Security Handbook.

11.1.6. DODM 5200.01, Information Security Program, 24 February 2012

11.2. Facility Security Clearance. Base PWS.

11.3. Security Clearance and Information Technology (IT) Level. Base PWS.

11.4. Investigation Requirements. Base PWS.

11.5. Adjudication for IT Access. Base PWS.

11.6. Interim IT Access. Base PWS.

11.7. Visit Authorization Letters. Base PWS.

11.8. Information Security and Other Miscellaneous Requirements. Base PWS.

11.9. Physical Security Requirements. Base PWS.

12. Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI).

12.1. Base PWS.

12.2. No additional GFE/GFI is projected for this TO.

13. Other Pertinent Information or Special Considerations. The Government requires highly specialized, multi-disciplinary subject matter expertise of USSOCOM’s vast operational and IT architecture; acquisition directives and processes; and tactical biometric capabilities.

13.1. Identification of Possible Follow-on Work. None

13.2. Identification of Potential Conflicts of Interest (COI). Base PWS.

13.3. Identification of Non-Disclosure Requirements. Base PWS.

13.4. Packaging, Packing and Shipping Instructions. Base PWS.

13.5. Inspection and Acceptance Criteria. Base PWS.

13.6. Property Accountability. Base PWS.

13.7. DoD Enterprise Service Management Framework (DESMF) Compliance. Base PWS.

14. Supply Chain Risk Management (SCRM). Base PWS.

14.1. Deliverable: Base PWS.

14.2. Supply Chain Risk Management Update: Base PWS.

15. Section 508 Accessibility Standards. N/A

TEC Services Contract Page 12 of 12 Pages

Appendix PM-TB SODAS System Specifications

Requirement Threshold Value Objective Value

Accuracy: Hand-held DNA collection Device shall be able to col-lect and process DNA samples under all specified conditions listed in Para 3.8.1-3.8.3

95% reliability with 80% confidence

98% reliability with

Transmission Timeliness: Timely transmission of a single DNA Record from Hand-held to docking station using secure transmis-sion link.

60 Seconds with

30 Seconds with

Transmission Security: Secure transmission link between Hand-held and docking station adheres to FIPS 140-2 Level 2 Standards and is registered at:

<http://csrc.nist.gov/groups/STM/cmvp/documents/140- 1/1401val2010.htm>

Pass/Fail Objective = Thresh-old

Analysis Request Timeliness: Docking station/database makes DNA Request to AFDIL once received from Hand-held.

10 Seconds with

Portal Update Timeliness: Docking station/database updates local SOF Exploitation Node’s portal after AFDIL Detain/Release in-formation is received.

10 Seconds with

Standards Compliance: DNA record’s metadata adheres to XML Format.

AFDIL XML DNA

Request Format

SODAS XML Data Structure

Standards Compliance: System complies with NIST’s Secure Hash Algorithm 3-512 (SHA3-512) based on DNA Sequence.

Data Security: Database records shall meet at a minimum NIST Federal Information Processing Standard (FIPS) 140-2 Level 3 Da-ta at Rest protection.

System Access Security: SODAS requires PKI authentication for access.

Attribute Based Access Control: SODAS allows only those indi-viduals with Administrative privileges to change/update a DNA Record within the SODAS database.

Number of Users: SODAS allows up to five simultaneous users within the EAC Network to make database queries or update rec-ords.

Tactical Usability of Hand-held: A survey measuring the opera-tors' perceptions of the system's usability and utility, including their opinions on whether the system aided or hindered mission accom-plishment, and whether it had any effects on workload.

System Usability Score of > 70%

System Usability Score of > 90%

Size/Weight: The Hand-held DNA collection system should weigh no more than 10 pounds and be no larger than 18 X 12 X 8 inches in size.

Delivery Indication: Hand-held Device gives SOF Operator posi-tive feedback that DNA Sample analysis request was delivered to the docking station/database system.

GPS Interface: Hand-held will synchronize with GPS satellites and auto-populate the DNA record with the GPS time stamp and geolo-cation data.

Status Indications: Hand-held will give operator feedback on communication link status to GPS and the docking station.

Figure 1. SODAS Data Flow Diagram

Figure 2. SODAS Hand-held DNA Collection Device Process Flow Diagram

Section L revised – Amend 0001

Section L - Instructions, Conditions and Notices to Bidders

LIST OF SECTION L ATTACHMENTS

Attachment L1 - Question & Answer Template Attachment L2 - Past and Present Performance Information Sheets Attachment L3 - Past Performance Questionnaire Form Attachment L4 – Sample Questionnaire Cover Letter Attachment L5 – Subcontractor/Teaming Partner Consent Letter

L.1.0 Program Title and Objectives

JITC is an element of the Defense Information System Agency within the DoD. JITC requires contractor TEC Services to support its role as the DoD's sole Joint IOP Certifier and only non-Service OTA for IT and NSS. JITC provides TEC support to the DoD Combatant Commanders/Services/Agencies, federal and state agencies, Coalition Partners, and commercial entities to aid in their design, development, acquisition, integration, deployment, operational use, and sustainment of new and enhanced IT/NSS capabilities.

Historically under the current Test and Evaluation Mission Support Services contracts, approximately 600 full time equivalents (FTEs) support over 1,500 TEC activities (of which about 200 are various Acquisition Category (ACAT) level programs) annually. During peak TEC periods, including all program sizes and ACAT levels, the 600 FTEs may simultaneously support up to 250 programs.

The objective of the JITC TEC Services contract is to acquire TEC services that include T&E, T&E Enabling Capability Requirements, and Overarching Contract and TO Requirements.

T&E Requirements include:

• Interoperability T&E

• Standards Compliance and Conformance T&E

• Developmental Test and Evaluation (DT&E)

• Operational Test and Evaluation (OT&E)

• Cybersecurity T&E

• Enterprise Service T&E

• Other T&E and Subject Matter Expert (SME) Support T&E

Enabling Capabilities include:

• TEC Policies and Processes

• Requirements Review and Documentation Management

• DoD Interoperability Status

• Knowledge and Records Management

• JITC Customer Relationship Management

• Advanced Technologies Research and Strategic Planning

• Automation, Instrumentation, Testbed, and Laboratory Support

Overarching Contract and TO Requirements include those pertaining to the overall administration of the TEC Services contract and its individual TOs. The contract awarded will be for non-personal services in accordance with FAR 37.101.

Contractor management is required in order to oversee all contractor support functions. The Government will neither directly nor indirectly supervise contractor personnel.

L.2.0 General Instructions

L.2.0.1 This section of the Information to Offerors provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The Offeror's proposal must include all data and information requested by the RFP and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS), and Contract Data Requirements List (CDRL). Non-conformance with the instructions provided in this Information to Offerors may result in removal of the proposal from further evaluation.

L.2.0.2 The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements but rather shall provide convincing rationale to address how the Offeror intends to meet these requirements.

Offerors shall assume that the Government has no prior knowledge of their facilities and experience and will base its evaluation on the information presented in the Offeror's proposal.

L.2.0.3 Elaborate brochures or documentation, binding, detailed art work, internet hyperlinks, or other embellishments are unnecessary and are not desired.

L.2.0.4 The Offeror shall make a clear statement in Part A of the Executive Summary Volume that the proposal is valid for a minimum of 180 days.

L.2.0.5 In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one digital copy of all unsuccessful proposals.

L.2.0.6 Portions of the successful offeror’s proposal may be incorporated into the contract as an attachment in Section J.

L.2.1 General Information

L.2.1.1 Points of Contact

The KO and the contract specialist (CS) are the sole points of contact for this procurement. Address any questions or concerns you may have to the KO and CS. Written requests for clarification must be sent to the KO at the email address located below.

Contracting Officer Name: Christopher Enriquez Organization/Office Symbol: Phone No.: PSD/PL8315/ (618)-229-9446 E- Mail Address: christopher.m.enriquez.civ@mail.mil

Contract Specialist Name: Kyle Cadwallader Organization/Office Symbol: Phone No: PSD/PL8315/ (618)-229-9460 E- Mail Address: kyle.p.cadwallader.civ@mail.mil

L.2.1.2 Award without Discussions

The Government intends to award without discussions. Therefore, the offeror’s initial proposal should contain the offeror’s best approach/terms for technical, management, past performance, and price; however, despite this intent, the Government reserves the right to conduct discussions if the Source Selection Authority (SSA) determines they are necessary. If the SSA determines that discussions are necessary, a competitive range will be established. In the event issues pertaining to a proposed contract cannot be resolved to the SSA's satisfaction, the Government reserves the right to withdraw and cancel the solicitation. In such event, offerors will be notified in writing.

mailto:christopher.m.enriquez.civ@mail.mil mailto:kyle.p.cadwallader.civ@mail.mil

L.2.1.3 Debriefings

The KO will notify Offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. However, Offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The KO will notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful Offerors may request and receive a debriefing.

Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

L.2.1.4 Discrepancies

If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the KO in writing.

L.2.1.5 Electronic Reference Documents

All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) web site at http://www.fedbizopps.gov. Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation. The TEC Services FedBizOpps (FBO) web page is https://www.fbo.gov/spg/DISA/D4AD/DITCO/HC1028-16-R-0007/listing.html A Bidder’s library is also available on the TEC Services FedBizOpps web page. The Offeror will need to be logged into their FBO account to request access to the Bidder’s Library.

L.2.1.6 Communications

Exchanges of source selection information between Government and Offerors will be controlled by the KO or CS.

Evaluation notices and responses will be transmitted as emails and will be treated as source selection information. The subject line of the email shall be titled: “RFP HC1028-16-R-0007, Contractor Name, Source Selection Information See FAR 2.101 and 3.104.”

Questions/comments are due no later than 12:00 (CT) on October 13, 2016. Questions submitted after the deadline may not be answered. The email address for the KO and CS are contained in para L.2.1.1. Points of Contact, above.

Questions/comments will only be responded to if received in email and only when submitted on Attachment 1 Question and Answer Template in Section L.

No information concerning this solicitation or requests for clarification will be provided in response to Offeror initiated telephone calls. All such requests must be made in writing and submitted as directed above. All questions/comments provided in a timely manner will be answered in writing and provided to all Offerors. However, because of administrative time, written inquiries may not be answered when requests are received by the Government points of contact after the original due date for receipt of questions as specified in this solicitation. The timeframe for submitting inquiries will not be extended as a result of an extension to the due date for the receipt of offers, unless authorized by the KO.

L.2.2 Organization/ Page Limits

The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.2 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits as specified in Table 2.2 below. The contents of each proposal volume are described in applicable paragraphs of Section L as noted in the table below.

http://www.fedbizopps.gov/ https://www.fbo.gov/spg/DISA/D4AD/DITCO/HC1028-16-R-0007/listing.html

Table 2.2 - Proposal Organization

Volume RFP Paragraph Number Volume Title Page Limit

I Executive Summary Part A Proposal Title Page No limit Part B Table of Contents No limit Part C Narrative Summary 10 pages Part D Glossary of Abbreviations and Acronyms No limit II Factor 1- Phase One -Technical/Management Part A Volume Cover Page 1 page Part B Table of Contents No limit Part C Section M.2.2.1

(TEC Services PWS 6.1.1.1.g, 6.1.2.1.a, 6.1.4.1.g, 6.2.7.2.v, 7.2, and 6.1.1.1.f)

Response to Phase One Criteria (Subfactors 1-6) 15 pages and one additional page for IATM (page count does not apply to

ISO 9001

certificate)

Part D Glossary of Abbreviations and Acronyms No limit III Factor 1- Phase Two - Technical/Management Part A Volume Cover Page 1 page Part B Table of Contents No limit Part C Section C/PWS Technical Approach 50 pages Part D Section M.2.2.2.1

6.1.1.1.h, 6.1.4.1.j, and 6.1.5.6.h)

Response to Phase Two Subfactor 1, Science Based Test Design, Automation, and Instrumentation Support

4 pages

Part E Section M.2.2.2.2

(SODAS TO PWS

6.1.1.b, 6.2.a, and 6.2.i)

Response to Phase Two Subfactor 2, Special Operations DNA Analysis Solutions Test and Evaluation Sample Task Order.

30 pages (30 pages consisting of the SODAS Test Plan and T&E Automation and Instrumentation Support Whitepaper)

Part F Section M.2.2.2.3

(UC TO SOW

6.2.1.28)

Response to Phase Two Subfactor 3, Department of Defense (DoD) Enterprise Unified Capabilities (UC) Product TEC Services and Facility Support Task Order 0001.

20 pages

Part G Section M.2.2.2.4

(DJFAS TO SOW

6.2.3.c and 6.6.3.d)

Response to Phase Two Subfactor 4, Defense Joint Finance and Accounting System Test and Evaluation Support Sample Task Order.

20 pages

Part H Section M.2.2.2.5

6.3.2, 6.3.3, and 7.2.1

Response to Phase Two Subfactor 5, Program Management 12 pages

Part I Compliance and Cross Reference Matrix Contractor format, no limit

Part J Sample Resumes No limit Part K Glossary of Abbreviations and Acronyms No limit IV Factor 2– Past Performance Part A Volume Cover Page 1 page

Part C Past and Present Performance Information Sheets 5 pages for each reference

Part D List of POCs for Past Performance Questionnaires 1 page Part E Consent Letters 1 page for each subcontractor, teaming partner, and/or joint venture partner

Part F Organizational Structure Change History, if applicable 4 pages Part G Glossary of Abbreviations and Acronyms No limit V Factor 3 – Cost/Price Part A Volume Cover Page 1 page

Part C Introduction/Summary Descriptions 5 pages. Evidence of approved accounting, estimating and purchasing systems are not included in the page limit.

Part D • Summary Spreadsheet

• Individual spreadsheets for:

o UC Task Order 0001 (FFP) o CPFF Pricing Scenario Template o FFP Pricing Scenario Template

• NOTE: Offerors are not required to submit pricing for The SODAS or DJFAS sample TOs.

No limit (MS Excel 2007 or 2010)

Part E Other Information No limit Part F Final Proposal Revision, if needed TBD Part G Glossary of Abbreviations and Acronyms No limit VI Factor 4 – Small Business Participation Part A Volume Cover Page 1 page Part B Table of Contents No limit Part C Small Business Utilization Commitment Document 30 pages Part D Small Business Subcontracting Plan 30 pages Part E Glossary of Abbreviations and Acronyms No limit VII Contract Documentation Part A Volume Cover Page 1 page Part B Table of Contents No limit Part C Contract Documentation 5 pages Part D Other Company Information (specific to the resultant contract) 3 pages

Part E Organizational and Consultant Conflict of Interest Plan 30 pages Part F SCRM Plan No limit Part G Quality Control Plan 30 pages Part H DD254 No limit Part I Glossary of Abbreviations and Acronyms No limit

L.2.2.1 Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors. Page limitation shall not be circumvented by including inserted text boxes/pop-ups or internet hyperlinks to additional information; such inclusions are not acceptable and will not be considered part of the proposal. The Government reserves the right not to consider for award any proposal that does not adhere to the administrative requirements of this solicitation. Each page shall be counted except for those identified in Table 2.2, Proposal Organization, as having no limit, sample resumes, and blank pages.

L.2.2.2 Page Size and Format

L.2.2.2.1 A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts.

Pages shall be single spaced. Except for the reproduced sections of the solicitation document, the font type/text size shall be Times New Roman, 12 point size. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Pages shall have at least 1 inch margins for the top, bottom, and sides (excluding headers and footers, which shall have Times New Roman, 10 point size). Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to ENs. All Volumes (I-VII) of the quotation are to be submitted as PDF documents. Each part identified in Table 2.2 shall contain one PDF file that includes all contents identified in Table 2.2 for that part. Each Volume of the quotation should be submitted as an Adobe PDF Portfolio whereby the Portfolio contains the Parts required for that Volume as separate PDF documents. For example, Volume I (Executive Summary) would be the first Portfolio submitted. Within that Executive Summary Volume I Portfolio would be Parts A, B and C. Each Part would be its own PDF document within that Portfolio.

L.2.2.2.2 Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc and all shall be single spaced. These displays shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size. Foldout pages shall count as a single page. Foldout pages shall only be used for large tables, charts, graphs, diagrams and schematics - not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 10 point Times New Roman font for all text included in a table.

L.2.2.2.3 IATM’s required by Technical/Management Phase One Subfactor 6 shall not exceed American National Standards Institute Drawing Size “E” (34 x 44 inches) in size. The text shall be no smaller than 10 point Times New Roman font for all text included in the matrix.

L.2.2.3 Cost or Pricing Information

All cost or pricing information shall be addressed ONLY in the Cost/Price Proposal and Contract Documentation Volumes.

L.2.2.4 Cross-Referencing

To the greatest extent possible, each Volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

Cross referencing within a proposal…