W81XWH-16-R-0014.pdf

CODE

(Hour)

PAGE(S)

until 01:00 PM local time 16 Aug 2016

X

A X B X C

D

EX

X G F 42 - 48

49 - 54 X H 55 - 60 donna.r.blackstone.civ@mail.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 60

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

W81XWH 8. ADDRESS OFFER TO

See Item 7

9. Sealed offers in original and 3 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)

DONNA BLACKSTONE 301-619-2276

11. TABLE OF CONTENTS

SOLICITATION/ CONTRACT FORM

SUPPLIES OR SERVICES AND PRICES/ COSTS

1 - 2

X I CONTRACT CLAUSES

DESCRIPTION/ SPECS./ WORK STATEMENT X

PACKAGING AND MARKING

4 - 15 J LIST OF ATTACHMENTS

INSPECTION AND ACCEPTANCE

DELIVERIES OR PERFORMANCE

17 - 18

X K

REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

CONTRACT ADMINISTRATION DATA 19 - 22 X

SPECIAL CONTRACT REQUIREMENTS

OFFER (Must be fully completed by offeror) 23 - 29 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

30 - 40

PART II - CONTRACT CLAUSES

USA MED RESEARCH ACQ ACTIVITY

820 CHANDLER ST

FORT DETRICK MD 21702-5014

FAX:

TEL:

FAX:

TEL:

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

SOLICITATION

6. REQUISITION/PURCHASE NO.5. DATE ISSUED

15 Jul 2016

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

[ X ]

3. SOLICITATION NO.

W81XWH-16-R-0014

Section A - Solicitation/Contract Form

SOLICITATION INFORMATION:

1. This requirement is broken into two (2) phases:

Phase I: Firm Fixed Price-Level of Effort Research and Development for the "Software Scripting associated with Commercial Off The Shelf (COTS) Body Sensors" consisting of a two (2) year performance period.

Phase II: Firm Fixed Price for non-personal services to support the software scripted during Phase I consisting of three (3) one (1) year option periods.

2. Award shall be made on a Tradeoff Source Selection Process (TSSP) best value basis using trade-off analysis.

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

RESERVED

FFP-LOE

Offeror shall use Attachment 1 to submit pricing.

Contract Line Identification Number (CLIN) structure (based on Attachment 1) will be established within the final contract award.

FOB: Destination

NET AMT

CEILING PRICE

Section C - Descriptions and Specifications

STATEMENT OF WORK

Software Scripting Associated with Commercial‐Off‐The‐Shelf (COTS) Body Sensors Statement of Work (SOW)

1.0 BACKGROUND: The mission of the U.S. Army Research Institute of Environmental Medicine (USARIEM) is to “optimize Warfighter health and performance through medical research.” The Military Performance Division conducts research to enhance the performance (physical, cognitive, behavioral and psychomotor) of military occupational tasks, or to prevent performance decrements due to physical overload, nutritional deprivation, environmental and operational stresses, and musculoskeletal injuries.

1.1 The Military Performance Division is tasked with conducting biomechanics research into common Soldiering tasks. Current research is mostly laboratory based, and there is a large need to expand data collection capabilities to the field to increase the ecological validity of the research data collected. However, characterization of Soldiering tasks/physical activities through analysis of human movement and loading patterns requires new equipment and software. This requirement is to acquire advanced expertise on characterizing human movement through non‐invasive sensors and scripting of software to both collect and process data to characterize human movement patterns.

2.0 SCOPE OF WORK: Identification of activity types and biomechanics using non‐invasive sensors and scripting software to distinguish between multiple physical activities, provide software updates and training.

3.0 OBJECTIVES: USARIEM is looking to award a contract to one company who can supply body sensor devices that meet the minimum essential characteristics (MECs) listed in section 4.1.1.1 with associated software, provide technical training and support, develop software based on collected data to distinguish between multiple physical activities, and provide software updates

4.0 TASKS. Deliver non‐invasive sensors, and provided software and hardware support for them.

These sensors shall be used in a research study conducted by USARIEM during physical activities. The contractor shall then develop software to identify the different activities performed from the sensor data.

4.1. Task 1 – Purchase Seventeen (17) Body Sensor Devices Contractor shall:

4.1.1 Deliver 17 sensor devices that meet the MECs in paragraph 4.1.1.1 and associated software to distinguish between multiple physical activities within 60 days of contract award to USARIEM.

4.1.1.1 Body Sensor Minimum Essential Characteristics (MECs):

4.1.1.1.1 Size: < 20 cm3 (without attachment mechanism to body (strap, tape, pouch, etc.))

4.1.1.1.2 Mass < 20 g

4.1.1.1.3 Collects and stores (on sensor) 3D acceleration, direction/position and orientation (9 axes total) simultaneously. This collection and storage of data will use sampling rates of up to 500, 100 and 100 Hz, respectively for each data type (acceleration, direction/position and orientation). For example, 500 Hz for vertical acceleration, 500 Hz for anterior/posterior acceleration and 500 Hz for medial/lateral acceleration plus 100 Hz apiece for each of the 3 direction/position axes and 3 orientation axes. Stored data is retrieved from the device via USB cable connection between device and computer.

Data is stored on computer in .csv files.

4.1.1.1.4 Sampling rates must have user selected options that are compatible for time synchronization (i.e., 50, 100 and 1000 Hz are compatible) and not simply set to the maximum value.

4.1.1.1.5 Tri‐axial accelerometer: range ± 16 g and resolution minimum 16‐bit

4.1.1.1.6 Direction/Position sensor: range ± 5 Gauss and resolution minimum 12‐bit

4.1.1.1.7 Orientation sensor: range ± 2000 degrees/second and resolution minimum 16‐bit

4.1.1.1.8 Durable and water‐resistant

4.1.1.1.9 Continuous data collection and storage time of 4 hours without recharging or new power supply/battery when sampling and storing data at the maximum sampling rates listed above.

A device to recharge the power to the sensors or new power supplies will be provided with the sensor.

For either power option, enough power must be provided with the original devices for them to maintain this data collection requirement through the end of the contract.

4.1.1.1.10 Device attachment to human cannot impede ability to perform physical activities including, but not limited to: walking, running, load carriage, sitting, standing, lying prone, sit‐ups, push‐ ups, jumping jacks, etc. Mechanism to attach device to human must be provided.

4.1.1.1.11 Ability to synchronize at least seven devices during data collection or synchronization in post‐processing, i.e., “master time”.

4.1.1.1.12 Data collection software compatible with USARIEM information management (IM) requirements, see below in sections 5.0‐5.2.1.4, Information Management and Technology Compliance.

4.1.1.1.13 Ability to wirelessly (via bluetooth) stream data, to a computer (both stream and computer meeting MRMC IM requirements listed below in sections 5.0‐5.2.1.4, Information Management and Technology Compliance), in real‐time, one axis of data at 100 Hz from either the position or orientation sensors or a minimum of 500 Hz from the accelerometer when data is not being stored on the device.

4.1.1.1.14 Device re‐calibration requires minimal user input and time

4.1.1.1.15 Drift in the time domain between sensors of less than 5 milliseconds per minute (would be 300 ms per hour, or 1200 ms per four hours)

4.1.1.1.16 Auto‐correction for drift, in signal value, during data collection or post‐processing. Either option must not interfere with performance of activities. For instance, device cannot require a zero position of “no activity” every minute. If the auto‐correction occurs during data collection, then the contractor must provide information about how the drift correction is not inducing signal error.

4.1.1.1.17 Data collection and processing software to initialize data collection on devices and obtain data files (tab or comma delimited (.txt or .csv) files) from devices.

4.1.2 Provide training on using the sensors and the data collection software. Contractor shall have at least one company representative visit USARIEM for in person training of up to ten (10) USARIEM personnel on sensors and software for data collection. The contractor shall provide a user manual regarding sensor set‐up, calibration, data collection from both hardware and software perspectives and how to obtain data stored on devices. The in‐person training will include topics in the user manual, time for USARIEM personnel to test out the devices and software as well as anything else the contractor deems necessary for the personnel to use the devices independently. Training will be scheduled at a date convenient for USARIEM and it must occur within 30 days of receipt of the sensors unless a specific request by USARIEM is made to hold training beyond the 30 days.

4.1.3 Provide Technical Support for both Software and Hardware. The contractor shall provide hardware and software technical support to USARIEM personnel for the duration of the contract. The contractor shall assist USARIEM investigators via telephone and email support, in setting up devices for use during data collection and reading data from devices. The contractor shall provide at least one phone number and one email address for USARIEM to contact with support questions. Additionally, the contractor shall provide updated data collection software to USARIEM if the software is updated by the contractor. Any data sent between the contractor and USARIEM as part of a support request will utilize the methods approved by USARIEM.

4.1.3.1 Hardware support. All phone calls and emails will be responded to within 24 hours of receipt, with the exception of phone calls or emails on a Friday, which will be responded to by Monday morning before 1200 (noon). All dates and time are using the Eastern Time Zone (Boston, MA, USA). All hardware problems will be resolved within one week of notification. Any hardware update to remedy the problem will be provided to USARIEM. In the event a device completely ceases to function, a new sensor will be provided and received by USARIEM within thirty (30) calendar days from the date of initial problem report by USARIEM.

4.1.3.2 Software support. All phone calls and emails will be responded to within 24 hours of receipt, with the exception of phone calls or emails on a Friday, which will be responded to by Monday morning before 1200 (noon). All dates and time are using the Eastern Time Zone (Boston, MA, USA). All software problems will be resolved * within one week of notification. Any software update to remedy the issue will be provided to USARIEM. Additionally, after the software scripting task is completed, software support for MATLAB upgrades will be provided. The contractor will supply upgrades within sixty days that the software to characterize activities no longer works with newer MATLAB versions.

4.1.3.3 At no point in time will the contractor have access to US Government systems.

4.1.4 Software Scripting. Knowledge of human movement patterns and activity identification from non‐invasive sensor data is required. Services require proficiency in MATLAB (Mathworks, Natick, MA, USA). The contractor shall develop software to identify when Soldiers are performing each of the physical activities described in section 4.1.4.1. Subjects shall wear seven (7) sensors ‐ 2 arm, 1 waist/torso, 2 leg and 2 feet. USARIEM investigators shall collect the data and provide the data from ten research participants to the contractor. This data shall be referred to as the ‘training data set’ for the software. Each participant’s data may be sent separately to the contractor to expedite when the contractor has a data set to begin work on this task. The contractor will provide software that contains generalizable algorithms and is not limited to only apply to the data set provided by USARIEM. The contractor shall provide their preferred method of test and validation to the COR for approval. After approval has been received, the contractor shall perform the testing and validation within the data set provided and provide the results to USARIEM. The contractor must provide tables and figures that indicate when the software classified each activity as occurring for inspection by USARIEM personnel.

These tables and figures will include information about when USARIEM records indicated the actual activity started compared to when the software algorithms detected the activity started. Additionally, the contractor will provide information and results from their preferred method of validation within the data set provided including false positives and false negatives for each activity.

Milestones for Software Scripting:

Milestone Due Date Objective

1) Software can read file and select time windows to analyze data

Within 30 calendar days of receipt of first participant data

100% of files read in and regions selected as designated

2) All activities are classified regardless of accuracy and the combined output files can be read back into the software

Within 60 calendar days of receipt of first participant data

100% of output files can be read back into the software. 100% of output from software includes a breakdown of all activities regardless of accuracy of classification of activities from sensors

3) All activities are classified to at least 50% accuracy or within 120 seconds of when activities are actually performed, whichever is more stringent

Within 90 calendar days of receipt of all participants’ data

95-100% of activities and files are classified as specified

4) All activities are classified to at least 80% accuracy or within 60 seconds of when activities were actually performed, whichever is less stringent.

Within 180 calendar days of receipt of all participants’ data

95-100% of activities and files are classified as specified

5) All activities are classified to at least 95% accuracy or within 60 seconds of when activities were actually performed, whichever is less stringent.

Within 365 calendar days of receipt of all participants’ data

95-100% of activities and files are classified as specified

6) All activities are classified to at least 90% accuracy or within 60 seconds of when activities were actually performed, whichever is less stringent for novel data set of n=10, which was not previously provided to the contractor

Within 45 calendar days of receipt of novel data set from USARIEM following USARIEM testing of software on

90-100% of activities and files are classified as specified

For milestone 4, Example 1: Activity X was performed for 100 minutes in a 200 minute time period selected (comprised of four 50 minute periods of data). The software must identify Activity X for at least 80 minutes of when it was actually performed and no more than 20 minutes of time when it was not performed.

For milestone 4, Example 2: Activity Y was performed for 3 minutes in a 5 minute file of data. The software must identify Activity Y for at least 2 minutes of when it was actually performed and no more than 1 minute of time when it was not performed.

The contractor will be provided with feedback after the version for each milestone, such as recommended changes to make the software more user friendly that the contractor will make

4.1.4.1 Software Capabilities and Specifications

4.1.4.1.1 The following activities will be characterized: walking, running, sitting, standing, lying prone, change in position from standing to lying prone, lift and carry, sit‐ups, push‐ups and jumping jacks. The objective is to utilize two devices (or one, if possible), and the threshold is using three devices.

4.1.4.1.2 Ability to choose a minimum of twenty different epochs in time (time windows) consisting of different start and stop points for characterizing activities.

4.1.4.1.3 The aforementioned activities will be output as percentage of total time in each activity and actual time in each activity plus a percentage and time of unknown/other activities for each of the specified segments for analysis.

4.1.4.1.4 If a specific epoch of time was chosen for analysis, then the raw data specific to that time period will be output as a tab or comma delimited text file (.txt or .csv) including data from all sensors and the master time for each data point. The software must be able to read this file back into the activity characterization program without any editing. Additionally, the software will output a single file of all of the combined time epochs (with a master time for each data point) for all of the sensors.

4.1.4.1.5 The software for this program will meet USARIEM IM requirements listed in section 5.0‐ Information Management and Technology Compliance.

4.1.4.1.6 The algorithms and sensor locations used in the software to characterize each activity will be disclosed to USARIEM.

4.1.4.1.7 The software will work correctly, as specified by section 4.1.4, to process data and identify activities for data up to the maximum duration of data collection specified in section 4.1.1.1 MECs.

4.1.4.2 Software Testing: USARIEM will test all versions of software provided to ensure that they meet the milestones stated (Figures 1‐3).

Figure 1: Software testing flow chart for milestone 1

Figure 2: Software testing flow chart for milestones 2‐4.

Figure 3: Software testing flow chart for milestones 5‐6.

The algorithms and sensor locations used in the final version of the software must be provided to

USARIEM.

4.3 Task 3 – Purchase Eleven Body Sensor Devices (Optional CLIN) Contractor will provide 11 sensor devices in accordance with the MECs in paragraph 4.1.1.1. Contractor will assist USARIEM investigators, via phone and email support, in setting up devices for use during data collection and performing data processing to read data from devices. The sensors will be provided by the contractor to USARIEM within 60 days electing to purchase them.

4.3.1 Minimum Essential Characteristics (MECs) – 11 Sensors

Sensor Specifications shal1, at a minimum, be the same as 4.1.1.1 Minimum Essential Characteristics (MECs) with the exception that the new 11 sensors will be waterproof instead of water resistant.

5.0 Information Management and Technology Compliance.

5.1 Hardware. All Matlab software must operate on Department of Defense computers in accordance with DoD approved security configuration guidelines and which have no access to the internet and currently run 64 bit Windows 7. The hardware for data collection software must operate on the aforementioned computer specifications or one of several iPad versions: Mini 2, Mini 3, Air or Air 2.

If an iPad is used, then transfer of any files to and from it must be accomplished via USB. Changes to the iPad and software for the sensors that require any files from the internet is a multiple step process. First, the software file from the internet is downloaded on a computer with internet access. Then the file is transferred via CD or DVD from that computer with internet access to a non‐internet connected computer, which also has iTunes. Any other configuration of adding software or files to the iPad will need specific approval from the Information Management (IM) group after an evaluation of current DoD guidance documents. The use of the software will not require administrative privileges to run or write data files. It will run under a regular user account (no power users).

5.2 Software. The software for data collection must be compatible with a Department of Defense (DoD) computer that is locked down (i.e., not connected to the internet) running 64 bit Windows 7 or an iPad with the requirements listed in 5.1. Data processing software to retrieve data from the sensors must be reviewed for IM approval prior to use and installation of the software. The iPad may connect to the locked down Windows 7 machine via USB. The software for data processing of activity identification must be written in MATLAB and include MATLAB m‐file(s). The source code for the software (m‐files), must be included in all versions supplied to USARIEM. The use of the software will not require administrative privileges to run or write data files. It will run under a regular user account (no power users).

5.2.1 Information Assurance (IA). The contract shall implement a comprehensive multi‐approach methodology with respect to DoD IA configuration standards such as the Security Technical Implementation Guides (STIGs), http://iase.disa.mil/stigs/Pages/index.aspx.

5.2.1.1 Software Assurance and Security Engineering Practices

5.2.1.1.1 The contractor shall design, develop and implement secure applications and configurations through applying applicable DoD STIGs, checklists, vendor security guidance, industry best practices, and applicable vendor product security patches. The contractor shall ensure applications are in compliance with DoD instruction 8500.01 Cyber Security (dated 14 March 2014, www.dtic.mil/whs/directives/corres/pdf/850001_2014.pdf) and DoDI 8551.01 Ports, Protocols, and Services Management/ PPSM (dated 28 May 2014, www.dtic.mil/whs/directives/corres/pdf/855101p.pdf). The contractor shall leverage, to the maximum extent possible, automated tools to identify and remediate vulnerabilities or weaknesses in the application design/ coding.

5.2.1.1.2 The Information System Security Engineer shall participate in Government and contractor formal and informal design reviews to identify potential security weaknesses, deficiencies, and/ or vulnerabilities in the design. The Information System Security Engineer shall also ensure appropriate security requirements are included as part of the requirements traceability matrix and are evaluated as part of the security assessment. As part of the contractor’s change control process, the contractor shall ensure participation by the Information System Security Engineer or a qualified cyber security SME to evaluate the impact of each change on security. The contractor shall document the results of this evaluation.

5.2.1.2 Non‐Secure Software

5.2.1.2.1 If the Government determines, after a security audit (e.g. security assessment), that software delivered under this contract is non‐secure, the Government will provide written notice to the contractor of each non‐conformity. Software shall be “non‐secure” under this task order if it contains a software error or a web application security flaw.

5.2.1.2.2 The contractor shall have thirty (30) days after receipt of such notice (Remedy Period) to remedy each non‐conformity by modifying/ replacing and redelivering the software to the Government;

or shall notify the Government within 15 days as to why the remedy cannot be implemented in 30 days, and propose a timeline for correction. If the Government determines, after a security audit following a remedy period, that the redelivered software is non‐secure, and thus non‐conforming, the Government may reject the delivery, provide notice of the non‐conformance, and document the contractor’s performance record. Alternatively, the Government may accept non‐conforming software, receive appropriate consideration (equitable price reduction on a fixed price contract, reimbursement for costs of security audit, reimbursement for costs to correct the non‐compliances, etc.), and document the contractor’s performance record.

5.2.1.3 Malicious Code Warranty. The contractor represents and warrants that upon delivery to the government the software shall be free from all computer viruses, worms, time‐outs, time bombs, back doors, disabling devices and other harmful or malicious code intended to or which may damage, disrupt, inconvenience or permit access to the software user’s or another’s software, hardware, networks, data or information.

5.2.1.4 Source Code Configuration Control (Versioning). The contractor shall utilize a strict version control process for software scripting.

5.3. Data Security. With respect to USARIEM furnishing de‐identified research data (no personally identifiable information, PII) and/or information relating to them, the Parties agree as follows:

5.3.1 Recipient agrees that the Data and/or Information will be used for body sensor and software scripting purposes only. The data and/or information shall not be sold, offered for sale, used for commercial purposes, or be furnished to any other party without advance written approval from the Commander, USARIEM, and any use or furnishing of Data and/or Information shall be subject to the restrictions and obligations imposed by this contract. The parties mutually agree that USARIEM is the repository and gatekeeper of the Data and/or Information and that the Recipient does not obtain any right, title, or financial interest in any of the Data and/or Information to which USARIEM grants access.

5.3.2 No further collaboration regarding the provided data is planned beyond this SOW. Any intellectual property rights to the Data and/or Information in existence prior to this contract, or potential rights, such as issued patents, patent applications or invention disclosures are retained by the Provider. Any invention patentable under U.S. patent law which is conceived or first reduced to practice under the contract shall be owned by the party entitled to ownership under U.S. patent law.

5.3.3 The Parties shall maintain in confidence all Information relating to these Data and/or Information and shall not disclose Information to others without specific written permission from USARIEM, in advance, unless required to by law. The Recipient shall notify USARIEM immediately if the removal of identifiers from the data has not been successful.

5.3.4 When the Data and/or Information are no longer being used for the above purposes, in accordance with this Agreement, all Data and/or Information will be destroyed or unless otherwise directed, in writing, by USARIEM.

6.0 General Requirements

6.1 Place of Performance. All software scripting work shall be performed at the Contractor's facility.

Training associated with the body sensor device shall be conducted on‐site at USARIEM, Natick, MA.

6.2 Antiterrorism/Operations Security (AT/OPSEC):

6.2.1 AT Level I Training: All contractor employees, to include subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete AT Level I awareness training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichecer is applicable. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the contracting officer, if a COR is not assigned, within 5 calendar days after completion of training by all employees and subcontractor personnel. AT Level I awareness training is available at the following website: http://jko.jten.mil

6.2.2 Access and general protection/security policy and procedures: Contractor and all associated subcontractor employees shall provide all information required for background hecks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204‐9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

6.2.2.1 For contractors that do not require CAC, but require access to a DoD facility or installation:

Contractor an all associated subcontractor employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC‐III) and Terrorist Screening Database (TSDBI) (Army Directive 2014‐05/AR 190‐13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations.

6.2.3 For contracts that require OPSEC Training: Per AR 530‐1 Operations Security, the contractor must complete Level I OPSEC Awareness training. New employees must be trained within 30 calendar days of their reporting for duty and annually thereafter.

6.3 Other Direct Costs: Travel associated with contractor personnel required to travel to Natick, MA to provide training in accordance with paragraph 4.1.2 shall be applied against Other Direct Costs.

These costs may include air fare, car rental or taxi (as appropriate), hotel and per diem for meals and incidentals. Per diem shall be at the established GSA per diem rate for Natick, MA. Payment shall be made for allowable and allocable costs incurred after completion of the travel. The payment request must be submitted via electronic invoice through the Wide Area Workflow system and supported by receipts. Only General & Administrative (G&A) costs are allowed for the set‐up and processing of the Travel requirement.

7.0 DELIVERABLES. All deliverables must meet MECs, professional standards and meet the requirements set forth in contractual documentation and shall be delivered to USARIEM.

7.1 Provision of 17 (Seventeen) Body Sensors and associated training within sixty (60) days after contract award.

7.2 Activity Characterization Status Reports for review and revision (as required). The contractor shall submit the reports using the format outlined in CDRL, Exhibit A, DID # DI‐MGMT‐80368A.

7.2.1 First report is due three months from award date.

7.2.2 Subsequent reports are due differently for project phases

7.2.2.1 Monthly until final version of software is accepted by USARIEM. No report is due if USARIEM was testing the software for the entire month.

7.2.2.2 If software must be updated to work with subsequent MATLAB version or other technical issues then a report is due after each month of software scripting if it requires more than one month of effort.

7.3 Software Scripting Plan for review and revision (as required). The contractor shall submit the reports using the format outlined in CDRL, Exhibit B, DID # DI‐IPSC‐81427A.

7.3.1 First report is due four months following award date.

7.3.2 Subsequent reports are only required if either of the following conditions apply

7.3.2.1 The report substantially changes

7.3.2.2 If software must be updated to work with subsequent MATLAB version or other technical issues.

7.4 Software Test Plan for review and revision (as required). The contractor shall submit the reports using the format outlined in CDRL, Exhibit C, DID # DI‐IPSC‐81438A.

7.4.1 First report is due four months following award date.

7.4.2 Subsequent reports are only required if either of the following conditions apply

7.4.2.1 The report substantially changes

7.4.2.2 If software must be updated to work with subsequent MATLAB version or other technical issues.

7.5 Final written technical summary reports for review and revision (as required). The contractor shall submit the final report using the format outlined in CDRL, Exhibit D, DID # DI‐MISC‐80508B.

7.6 Provision of 11 (eleven) Waterproof Body Sensors within 60 days of the exercising of option period 1.

Section E - Inspection and Acceptance

CLAUSES INCORPORATED BY REFERENCE

52.246-2 Inspection Of Supplies--Fixed Price AUG 1996 52.246-4 Inspection Of Services--Fixed Price AUG 1996 52.246-9 Inspection Of Research And Development (Short Form) APR 1984 52.246-16 Responsibility For Supplies APR 1984

Section F - Deliveries or Performance

52.242-15 Stop-Work Order AUG 1989 52.242-17 Government Delay Of Work APR 1984 52.247-34 F.O.B. Destination NOV 1991 252.247-7023 Transportation of Supplies by Sea APR 2014

CLAUSES INCORPORATED BY FULL TEXT

52.211-8 TIME OF DELIVERY (JUN 1997)

(a) The Government requires delivery to be made according to the following schedule:

REQUIRED DELIVERY SCHEDULE

Commercial Off The Shelf (COTS) Body Sensors that meet the Minimum Essential Characteristics aoutlined in Statement of Work (SOW) paragraph 4.1.1.1 shall be delivered

Within Days 60 days

After Date of contract award and exercise of Option Period 1.

Item No. Quantity of Contract

0001 17

1001 11

The Government will evaluate equally, as regards time of delivery, offers that propose delivery of each quantity within the applicable delivery period specified above. Offers that propose delivery that will not clearly fall within the applicable required delivery period specified above, will be considered nonresponsive and rejected. The Government reserves the right to award under either the required delivery schedule or the proposed delivery schedule, when an offeror offers an earlier delivery schedule than required above. If the offeror proposes no other delivery schedule, the required delivery schedule above will apply.

OFFEROR'S PROPOSED DELIVERY SCHEDULE

Within Days

After Date

Item No. Quantity of Contract

(b) Attention is directed to the Contract Award provision of the solicitation that provides that a written award or acceptance of offer mailed, or otherwise furnished to the successful offeror, results in a binding contract. The Government will mail or otherwise furnish to the offeror an award or notice of award not later than the day award is dated. Therefore, the offeror should compute the time available for performance beginning with the actual date of award, rather than the date the written notice of award is received from the Contracting Officer through the ordinary mails. However, the Government will evaluate an offer that proposes delivery based on the Contractor's date of receipt of the contract or notice of award by adding (1) five calendar days for delivery of the award through the ordinary mails, or (2) one working day if the solicitation states that the contract or notice of award will be transmitted electronically. (The term "working day" excludes weekends and U.S. Federal holidays.) If, as so computed, the offered delivery date is later than the required delivery date, the offer will be considered nonresponsive and rejected.

(End of clause)

Section G - Contract Administration Data

CONTRACT ADMINISTRATION DATA

Contractor shall insert the name and contact information for the Contract Administrator who will be responsible for administrative oversight of the contract.

Name: _______________________________________________

Title: _______________________________________________

Company: _____________________________________________

Address: _____________________________________________

E-mail Address: ________________________________________

Telephone: Office: _________________________________

Mobile: ________________________________

Facsimile: ________________________________________

252.232-7003 Electronic Submission of Payment Requests and Receiving

Reports

JUN 2012

252.232-7007 Limitation Of Government's Obligation APR 2014

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.

252.204-0004 LINE ITEM SPECIFIC: BY FISCAL YEAR. (SEP 2009)

The payment office shall make payment using the oldest fiscal year appropriations first, exhausting all funds in the previous fiscal year before disbursing from the next fiscal year. In the event there is more than one ACRN associated with the same fiscal year, the payment amount shall be disbursed from each ACRN within a fiscal year in the same proportion as the amount of funding obligated for each ACRN within the fiscal year.

252.204-7002 PAYMENT FOR SUBLINE ITEMS NOT SEPARATELY PRICED (DEC 1991)

(a) If the schedule in this contract contains any contract subline items or exhibit subline items identified as not separately priced (NSP), it means that the unit price for that subline item is included in the unit price of another, related line or subline item.

(b) The Contractor shall not invoice the Government for any portion of a contract line item or exhibit line item which contains an NSP until --

(1) The Contractor has delivered the total quantity of all related contract subline items or exhibit subline items; and

(2) The Government has accepted them.

(c) This clause does not apply to technical data.

252.204-7006 BILLING INSTRUCTIONS (OCT 2005)

When submitting a request for payment, the Contractor shall--

(a) Identify the contract line item(s) on the payment request that reasonably reflect contract work performance; and

(b) Separately identify a payment amount for each contract line item included in the payment request.

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 (Services Only)

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

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 HQ0490 Issue By DoDAAC W81XWH Admin DoDAAC W81XWH Inspect By DoDAAC N/A Ship To Code N/A Ship From Code N/A Mark For Code N/A Service Approver (DoDAAC) N/A Service Acceptor (DoDAAC) W561UG Accept at Other DoDAAC N/A LPO DoDAAC N/A DCAA Auditor DoDAAC N/A Other DoDAAC(s) N/A

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

COR: TBN

Contract Specialist: Mrs. Donna Blackstone, donna.r.blackstone.civ@mail.mil

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

Not Applicable

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

Section H - Special Contract Requirements

SAFEGUARDING PROPRIETARY INFO

SAFEGUARDING PROPRIETARY INFORMATION (June 2015) (USAMRAA)

a. "Proprietary information" shall mean all information, whether disclosed orally, in writings, by drawings, or otherwise relating to the work to be performed under this contract, whether proprietary to the Government or one of its collaborating partners. Proprietary information includes, but is not limited to, information regarding properties, formulae, structures, manufacturing processes, and test results. Information ceases to be proprietary when it is generally available to the public or is available from sources other than the Department of the Army. All information submitted to the contractor under this contract shall be presumed to be proprietary to the Department of the Army or one of its collaborating partners until the Department of the Army announces to the contrary.

b. The contractor shall safeguard proprietary information both during and after the term of this contract, and shall neither appropriate, nor disclose, nor make unauthorized use of the proprietary information received under this contract. The requirements of this paragraph include, but are not limited to, the following:

(1) Maintain a high degree of physical security over proprietary information at all times;

(2) Discussion of proprietary information only among contractor's employees whose duties and responsibilities require knowledge of that information; and,

(3) Elimination of proprietary information in open publications by the contractor and its personnel.

c. The contractor shall require all personnel who receive proprietary information to execute the statement in paragraph d below when this contract becomes effective or when first employed (if employed after the contract becomes effective). All statements executed pursuant to this paragraph shall be forwarded to the U.S. Army Medical Research Acquisition Activity Contracting Officer when this contract terminates, and/or when the employment ends, or and/or upon request of the Contracting Officer.

d. The following statements shall be executed pursuant to paragraph c above and when completed, placed in the official contract file:

I hereby acknowledge that I (insert contractor’s name here) have been informed that our duties may require that I have access to proprietary information. I /We understand this proprietary information which I/we will receive includes, but is not limited to, properties, formulae, structures, protocols, manufacturing processes, and test results.

I/we agree that I/we will neither appropriate, nor disclose, nor make unauthorized use of proprietary information both during and after my/our employment. I further agree that I/we will neither include nor draw upon proprietary information received under this contract in open publication. This agreement is executed with the intention that collaborating partners of the United States Government who have submitted information to the Government under non-disclosure obligations shall be third party beneficiary hereunder, and shall have the right to enforce the obligations undertaken herein.

Name: ____________________________ Date: ____________________________ Signature:__________________________

e. The contractor shall insert the substance of paragraphs a through d above in each subcontract hereunder.

Compliance with the provisions of this clause shall be the responsibility of the contractor.

INVESTIGATING MISCONDUCT

INVESTIGATING AND REPORTING POSSIBLE SCIENTIFIC MISCONDUCT (June 2015) (USAMRAA)

a. "Misconduct" or "Misconduct in Science" is defined as fabrication, falsification, plagiarism, or other practices that seriously deviate from those that are commonly accepted within the scientific community for proposing, conducting or reporting research. It does not include honest error or honest differences in interpretations or judgments of data.

b. Contractors shall foster a research environment that prevents misconduct in all research and that deals forthrightly with possible misconduct associated with research for which U.S. Army Medical Research and Materiel Command funds have been provided or requested.

c. The contractor agrees to:

(1) Establish and keep current an administrative process to review, investigate, and report allegations of misconduct in science in connection with research conducted by the contractor;

(2) Comply with its own administrative process;

(3) Inform its scientific and administrative staff of the policies and procedures and the importance of compliance with those policies and procedures;

(4) Take immediate and appropriate action as soon as misconduct on the part of employees or persons within the organization's control is suspected or alleged; and

(5) Report to the Administrative Contracting Officer (ACO) a decision to initiate an investigation into possible scientific misconduct.

d. The contractor is responsible for notifying the ACO of appropriate action taken if at any stage of an inquiry or investigation any of the following conditions exist:

(1) An immediate health hazard is involved;

(2) There is an immediate need to protect Federal funds or equipment;

(3) A probability exists that the alleged incident will be reported publicly; or

(4) There is a reasonable indication of possible criminal violation.

252.211-7003 ITEM UNIQUE IDENTIFICATION AND VALUATION (MAR 2016)

(a) Definitions. As used in this clause-

Automatic identification device means a device, such as a reader or interrogator, used to retrieve data encoded on machine-readable media.

Concatenated unique item identifier means--

(1) For items that are serialized within the enterprise identifier, the linking together of the unique identifier data elements in order of the issuing agency code, enterprise identifier, and unique serial number within the enterprise identifier; or

(2) For items that are serialized within the original part, lot, or batch number, the linking together of the unique identifier data elements in order of the issuing agency code; enterprise identifier; original part, lot, or batch number;

and serial number within the original part, lot, or batch number.

Data Matrix means a two-dimensional matrix symbology, which is made up of square or, in some cases, round modules arranged within a perimeter finder pattern and uses the Error Checking and Correction 200 (ECC200) specification found within International Standards Organization (ISO)/International Electrotechnical Commission (IEC) 16022.

Data qualifier means a specified character (or string of characters) that immediately precedes a data field that defines the general category or intended use of the data that follows.

DoD…