W81XWH-16-R-0014-0002.pdf

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

a. The purpose of this amendment is to revise the Statement of Work (SOW) Minimum Essential Characteristics (MECs) and Section L instructions.

b. The SOW MECs are hereby revised to remove specific size and mass requirements and is replaced w ith the condition in w hich the body sensors need to w ork - paragraphs 4.1.1.1.1 and 4.1.1.1.2.

c. Section L changes can be found in paragraphs: L.2.3, L.3, and L.4.2.1.2.1

d. All revisions are delineated by a vertical line in the righthand margin.

e. Proposal submission is hereby extended to Tuesday, August 23, 2016 at 1:00 p.m. Eastern.

f. On-site demonstrations shall be conducted at USARIEM, Natick, MA on August 30 and 31, 2016.

g. All other terms and conditions stated w ithin the solicitation remain the same.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 17

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

16C. DATE SIGNED

BY 12-Aug-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 W81XWH-16-R-0014

X 9B. DATED (SEE ITEM 11)

15-Jul-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 X is extended, 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

12-Aug-2016

CODE

USA MED RESEARCH ACQ ACTIVITY

820 CHANDLER ST

FORT DETRICK MD 21702-5014

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W81XWH-16-R-0014

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 16-Aug-2016 01:00 PM to 23-Aug-2016 01:00 PM.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

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: The device must be small enough to attach to the wrists, waist, ankles and footware without impeding movement during combat training.

4.1.1.1.2 Reserved

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 L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

INSTRUCTIONS TO OFFEROR:

L.1 The Contract Specialist (CS) is the point of contact for this acquisition. Any questions or concerns regarding this acquisition shall be submitted electronically via e-mail to donna.r.blackstone.civ@mail.mil by 12:00 Noon, EDT, Thursday, July 28, 2016. All questions or concerns shall be answered via amendment to the solicitation document (RFP).

L.2 Submission of offers. Offeror's shall submit their proposal in accordance with the instructions outlined below. The Offeror’s proposal shall consist of two (2) volumes. The Volumes are: I - Business Proposal including completed Standard Form (SF) 33 - Solicitation, Offer and Award, Solicitation Amendments, Cost/Price Documentation, Certifications/Representations and Past Performance; and II - Technical Proposal.

L.2.1 Offeror's are responsible for including sufficient details to permit a complete and accurate evaluation of each proposal.

L.2.2 Proprietary information shall be clearly marked.

L.2.3 Offeror's should be prepared to perform a demonstration of the proposed sensors on site at the USARIEM facility, located in Natick, MA on Tuesday, August 30, 2016 or Wednesday, August 31, 2016. Specific day and time will be provided following initial evaluation.

L.3 Proposals are due: Tuesday, August 23, 2016 at 1:00 p.m. EDT and shall be submitted electronically to donna.r.blackstone.civ@mail.mil.

L.4 Content Requirement: All information shall be confined to the appropriate volume. The Offeror shall insure that submissions are clear, specific, complete and limited to essential matters, sufficient to define the proposal in a concise manner, to permit a complete and accurate evaluation of each proposal.

L.4.1 Volume I - Business Proposal: The volume shall contain the following documentation:

L.4.1.1 Company Cover Letter

L.4.1.2 SF 33 - Solicitation, Offer and Award with Blocks 12 - 18 completed by the Offeror.

L.4.1.3 Acknowledgment of Solicitation Amendments (if applicable)

L.4.1.4 Contract Administration Data (Section G - this identifies the Prime Offeror's employee(s) responsible for contract administration.)

L.4.1.5 Representations and Certifications (Section K).

L.4.1.6 Dun & Bradstreet Number (DUNS), CAGE Code, and Tax Identification Number (TIN)

L.4.1.7 Solicitation Attachment 1 (Pricing Schedule) and Attachment 2 (Level of Effort Billing/Milestone Chart).

Offeror's are instructed to complete both Attachments 1 and 2. Documentation must be provided to support all proposed costs.

L.4.1.8 The Offeror shall provide a statement of the methodology and assumptions used as the basis for costs proposed for the required services. Certified Cost or Pricing data is not required. The proposed costs must be sufficiently detailed to evaluate the reasonableness and realism for the proposed level of effort. The Offeror shall submit information other than certified cost or pricing data which will be used to perform a cost analysis. Offeror's shall address, at a minimum, all escalation factors applied and calculations of all Direct, Indirect, Overhead, G&A and Profit/Fee (if proposed) cost factors.

L.4.1.9 SF33, Cost submission, and Certifications/Representations shall not be addressed separately from that submitted in Volume I - Business Proposal. Cost information shall be included in Volume I only and shall not be discussed or exhibited in any other part of the Offeror's proposal.

L.4.1.10 Offeror's proposal must stipulate that it is predicated upon all the terms and conditions of this RFP.

L.4.1.11 Past Performance: This volume shall contain past performance information regarding similar contracts in size, complexity and scope. This volume shall not exceed 15 pages for the prime contractor and five (5) additional pages for each subcontractor (5 pages per sub). Offeror shall submit a listing of no more than three (3) references for Government and/or commercial contracts for the prime Offeror and one (1) reference for each major subcontractor during the past three years which are relevant to the efforts required by this solicitation. Relevant efforts are defined as services/efforts that are the same as or similar to the effort required by the solicitation. Data concerning the Offeror shall be provided first, followed by each proposed major subcontractor, in alphabetical order.

Letters of commitment shall be included for all major subcontractors for their past performance to be considered.

This volume shall be organized in the following sections:

L.4.1.11.1 Section 1 - Contract Descriptions: This section shall include the following information in the following format:

L.4.1.11.1.1 Contractor/Subcontractor place of performance, CAGE Code and DUNS Number. If the work was performed as a subcontractor, also provide the name of the prime contractor and Point of Contact (POC) within the prime contractor organization (name, current address, e-mail address, and telephone/fax numbers).

L.4.1.11.1.2 Government contracting activity, and current address, Contracting Officer's name, e-mail address, and telephone/fax numbers.

L.4.1.11.1.3 Government's technical representative/Contract Officer’s Representative (COR), current e-mail address, telephone/fax numbers.

L.4.1.11.1.4 Contract/Assistance Agreement Number

L.4.1.11.1.5 Contract Type (specific type such as Fixed Price (FP), Cost Reimbursement (CR), Time & Materials (T&M), etc.). In the case of Indefinite Delivery contracts, indicate specific type (Requirements, Definite Quantity, and Indefinite Quantity) and secondary contract type (FP, CR, T&M, etc.).

L.4.1.11.1.6 Awarded price/cost.

L.4.1.11.1.7 Final or projected final price/cost.

L.4.1.11.1.8 Original delivery schedule, including date of start and completion of work.

L.4.1.11.1.9 Final or projected final, delivery schedule, including dates of start and completion of work.

L.4.1.11.2 Section 2 - Performance: Offeror's shall provide a specific narrative explanation of each contract listed in Section 1, Contract Description, describing the objectives achieved and detailing how the effort is relevant to the requirement of this solicitation. For any contracts that did not/do not meet the original schedule or technical performance requirements, provide a brief explanation of the reason(s) for the shortcomings and any corrective action(s) taken to avoid recurrence. The Offeror’s shall list each time the delivery schedule was revised and provide an explanation of why the revision was necessary. All Request for Deviation and Requests for Waiver shall be addressed with respect to causes and corrective actions. The Offeror’s shall also provide copy of any Cure Notices or Show Cause Letters received on each contract listed and a description of any corrective action implemented by the Offeror or proposed subcontractor. The Offeror’s shall indicate if any of the contracts listed were terminated and the type and reasons for the termination.

L.4.1.11.3 Section 3 - Subcontracts (if applicable): The information provided for each proposed major subcontractor must include the entire company name, company address, CAGE Code, DUNS Number and type of work to be performed by citing the applicable Government Statement of Work (SOW) subparagraph number.

L.4.1.12 Each offeror shall forward a copy of the Past Performance Questionnaire (Attachment 3) to the references named in their narratives. The questionnaire shall then be returned directly to the Contract Specialist by the named references prior to the closing date and time of the solicitation. This information will be used to assess relevance and the level of expectation that the offeror can successfully perform the required effort.

L.4.2 Volume II - Technical: The volume shall include three (3) sections, as follows:

Sub-Section Page Limitation Tab A - Executive Summary/Abstract 1 Page Tab B - Technical/Manage Approach Tab B, and C combined total of 20 pages Tab C - Experience

L.4.2.1 FACTOR 1: Technical/Management Approach

L.4.2.1.1 Written Proposal Submission: The Offeror shall submit a technical and management approach that conveys its capabilities, technical expertise, tools, techniques, strategies, and methodologies to be applied to the functional areas outlined within the Statement of Work (SOW). The proposal must indicate a thorough understanding of the SOW and provide a comprehensive approach as to how tasks will be accomplished.

L.4.2.1.2 Demonstration of proposed body sensors shall include the following items:

L.4.2.1.2.1 Three (3) sensors attached to a Government identified person on the waist, ankle and footware;

L.4.2.1.2.2 The sensors shall record synchronously during physical activities, including: walking, running, jumping jacks, push-ups and sit-ups.

L.4.2.1.2.3 The demonstration shall include:

L.4.2.1.2.3.1 Subject set-up through data download to an offeror-owned computer;

L.4.2.1.2.3.2 Visual review of the download using the body sensor software program on an Offeror owned computer;

L.4.2.1.2.3.3 Text file(s) export from the software program on an Offeror owned computer; and

L.4.2.1.2.3.4 Opening the text file(s) in MS Excel and Matlab on an Offeror owned computer

L.4.2.2 FACTOR 2: Experience

L.4.2.2.1 The Offeror shall demonstrate corporate experience identical, similar or related to the requirements of this effort with specific emphasis on laboratory or field-based experience supporting biomechanics research and algorithm development of classifying physical activities from non-invasive sensors, such as accelerometers.

L.4.2.2.2 The Offeror shall demonstrate the ability and competence of proposed key personnel to meet the SOW requirements with provision of complete resumes and/or curriculum vitas (CVs) for all proposed key personnel. A resume or CV is complete if it includes a summary of each individual's qualifications, education, training, work experience, describes how these qualifications fit the individual for his/her proposed responsibilities.

Include current employment verification of individuals employed by the prime contractor, or a Letter of Intent for key personnel not currently employed by the prime contractor.

L.5 Electronic Format Submission:

L.5.1 Proposal submission shall consist of two (2) volumes – Volume I: Business Proposal; and Volume II:

Technical Proposal. Each volume shall consist of a complete proposal in PDF format.

L.5.2 All supporting cost information to aide in the cost evaluation shall be submitted in Microsoft Office Excel Read/Write format and viewable in Microsoft Excel 2010.

**NOTE: Self extracting exe files are NOT acceptable.

**NOTE: Zip file submission is not permitted.

L.6 The following volumes of material shall be submitted:

VOLUME TITLE MAXIMUM PAGES

I - Business Proposal – N/A Section A: SF33 - Solicitation, Offer and Award, Section G; Cost/Price Documentation (Attachments 1 and 2 with supporting documentation); and Certification/ Representations

N/A

Section B: Past Performance 15 (Plus 5 additional pages per major subcontractor)

II - Technical – Executive Summary Abstract; Technical/Management Approach; and Experience

20 Pages Combined

L.6.1 Offeror's are hereby notified that a proposal submitted that exceeds the stated page limitations for each volume shall be evaluated only up to the designated page limit. Any pages in excess of the designated page limit shall be removed from the proposal and not forwarded to the Source Selection Evaluation Board for evaluation. The following items are not included in the page limitations:

L.6.1.1 Cover Pages

L.6.1.2 Table of Contents

L.6.1.3 Sectional Dividers

L.6.1.4 RFP-to-Proposal Cross Reference Matrix

L.7 Period for acceptance of offers. The Offeror agrees to hold the prices in its offer firm for 90 calendar days from the date specified for receipt of offers, unless another time period is specified in an addendum to the solicitation.

L.8 Debriefing. If a debriefing is given to requesting Offeror’s, the Government shall provide the information in accordance with FAR 15.505 or FAR 15.506.

(End of Summary of Changes)