ISSUED_RFQ.pdf

RFQ IFB RFP

WOMEN-OWNED SMALL BUSINESS

(WOSB) ELIGIBLE UNDER THE WOMEN-OWNED

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30

1. REQUISITION NUMBER PAGE OF

2. CONTRACT NO. 3. AWARD/EFFECTIVE

DATE

4. ORDER NUMBER 5. SOLICITATION NUMBER 6. SOLICITATION ISSUE

DATE

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME b. TELEPHONE NUMBER (No collect calls)

8. OFFER DUE DATE/

LOCAL TIME

9. ISSUED BY

13b. RATING

14. METHOD OF SOLICITATION

CODE

15. DELIVER TO 16. ADMINISTERED BY CODE

18a. PAYMENT WILL BE MADE BY CODEFACILITY

CODE

CODE

TELEPHONE NO.

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN

OFFER

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK

BELOW IS CHECKED

SEE ADDENDUM

19.

ITEM NO.

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA 26. TOTAL AWARD AMOUNT (For Govt. Use Only)

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED

29. AWARD OF CONTRACT: REF.

DATE . YOUR OFFER ON SOLICITATION

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR

30b. NAME AND TITLE OF SIGNER (Type or print) 30c. DATE SIGNED

31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

31b. NAME OF CONTRACTING OFFICER (Type or print) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA - FAR (48 CFR) 53.212

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

OFFER

13a. THIS CONTRACT IS A

RATED ORDER UNDER

DPAS (15 CFR 700)

11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

ARE ARE NOT ATTACHED

ARE ARE NOT ATTACHED

27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1, 52.212-4. FAR 52.212-3 AND 52.212-5 ARE ATTACHED. ADDENDA

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA

17a CONTRACTOR/

OFFEROR.

CODE

8 (A)

SIZE STANDARD:

NAICS:

% FOR:SET ASIDE:UNRESTRICTED OR

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

HUBZONE SMALL

BUSINESS

SMALL BUSINESS

10. THIS ACQUISITION IS

EDWOSB

SMALL BUSINESS PROGRAM

STANDARD FORM 1449 (REV. 2/2012) BACK

19.

ITEM NO.

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED:

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

40. PAID BY

32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f. TELPHONE NUMBER OF AUTHORZED GOVERNMENT REPRESENTATIVE

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

33. SHIP NUMBER 34. VOUCHER NUMBER 35. AMOUNT VERIFIED

CORRECT FOR

PARTIAL FINAL

37. CHECK NUMBER

38. S/R ACCOUNT NO. 39. S/R VOUCHER NUMBER

36. PAYMENT

COMPLETE PARTIAL FINAL

SCHEDULE Continued

ITEM NO. SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

PAGE 3 OF 34 SB1341-15-RQ-0750

The Contractor shall provide a firm fixed price quotation to complete all of the required work.

One firm fixed price contract is expected to be awarded.

BASE LINE ITEM

0001 The Contractor shall provide a data management system meeting all requirements of the statement of work.

1.00 JB

0002 OPTION LINE ITEM

Software maintenance in accordance with the statement of work.

1.00 YR

0003 OPTION LINE ITEM

0004 OPTION LINE ITEM

0005 OPTION LINE ITEM

Table of Contents

PAGE 4 OF 34 SB1341-15-RQ-0750

SECTION

. 1 STATEMENT OF WORK

. 2 EVALUATION CRITERIA AND BASIS FOR AWARD

. 3 52.212-1 INSTRUCTIONS TO OFFERORS--COMMERCIAL ITEMS (APR 2014)

. 4 ADDENDUM TO 52.212-1

. 6 52.204-4 PRINTED OR COPIED DOUBLE-SIDED ON POSTCONSUMER FIBER CONTENT PAPER (MAY 2011)

. 7 52.204-7 SYSTEM FOR AWARD MANAGEMENT (JUL 2013)

. 8 52.204-13 SYSTEM FOR AWARD MANAGEMENT MAINTENANCE (JULY 2013)

. 9 52.204-16 COMMERCIAL AND GOVERNMENT ENTITY CODE REPORTING (JUL 2015)

. 10 52.204-18 COMMERCIAL AND GOVERNMENT ENTITY CODE MANAGEMENT (JUL 2015)

. 11 52.209-7 INFORMATION REGARDING RESPONSIBILITY MATTERS (JULY 2013)

. 12 52.209-9 UPDATES OF PUBLICLY AVAILABLE INFORMATION REGARDING RESPONSIBILITY MATTERS (JULY

2013)

. 13 52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS--COMMERCIAL ITEMS (MAR 2015)

. 14 52.212-4 CONTRACT TERMS AND CONDITIONS--COMMERCIAL ITEMS (MAY 2015)

. 15 52.225-25 PROHIBITION ON CONTRACTING WITH ENTITIES ENGAGING IN CERTAIN ACTIVITIES OR

TRANSACTIONS RELATING TO IRAN--REPRESENTATION AND CERTIFICATIONS (DEC 2012)

. 16 52.232-40 PROVIDING ACCELERATED PAYMENTS TO SMALL BUSINESS SUBCONTRACTORS (DEC 2013)

. 17 52.233-4 APPLICABLE LAW FOR BREACH OF CONTRACT CLAIM (OCT 2004)

. 18 52.247-34 F.O.B. DESTINATION (NOV 1991)

. 19 52.204-17 OWNERSHIP OR CONTROL OF OFFEROR. (NOV 2014)

. 20 52.212-5 CONTRACT TERMS AND CONDITIONS REQUIRED TO IMPLEMENT STATUTES OR EXECUTIVE ORDERS--

COMMERCIAL ITEMS (MAY 2015)

. 21 52.217-5 EVALUATION OF OPTIONS (JUL 1990)

. 22 52.217-7 OPTION FOR INCREASED QUANTITY--SEPARATELY PRICED LINE ITEM (MAR 1989)

. 23 52.217-8 OPTION TO EXTEND SERVICES (NOV 1999)

. 24 52.232-39 UNENFORCEABILITY OF UNAUTHORIZED OBLIGATIONS (JUNE 2013)

. 25 52.237-2 PROTECTION OF GOVERNMENT BUILDINGS, EQUIPMENT, AND VEGETATION (APR 1984)

. 26 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

. 27 1352.201-70 CONTRACTING OFFICER?s AUTHORITY (APR 2010)

. 28 1352.201-72 CONTRACTING OFFICER?s REPRESENTATIVE (C0R) (APR 2010)

. 29 1352.209-73 COMPLIANCE WITH THE LAWS (APR 2010)

. 30 1352.209-74 ORGANIZATIONAL CONFLICT OF INTEREST (APR 2010)

. 31 1352.233-70 AGENCY PROTESTS (APR 2010)

. 32 1352.233-71 GAO AND COURT OF FEDERAL CLAIMS PROTESTS (APR 2010)

. 33 1352.237-75 KEY PERSONNEL (APR 2010)

. 34 1352.246-70 PLACE OF ACCEPTANCE (APR 2010)

. 35 52.227-17 RIGHTS IN DATA--SPECIAL WORKS (DEC 2007)

PAGE 5 OF 34 SB1341-15-RQ-0750

SECTION

. 1 STATEMENT OF WORK

Background

The National Institute of Standards and Technology’s (NIST) Center for Automotive

Lightweighting (NCAL) has a series of highly instrumented mechanical test frames. As such, for a single mechanical test, multiple independent instruments generate data that must be captured. A single ‘test’ may contain data and metadata associated with the fabrication of a test sample, dimensional measurement of the test sample, mechanical test frame control parameters, data acquired by the mechanical test frame, x-ray diffraction

(XRD) linescans and analysis, images and analysis from digital image correlation (DIC), infrared images and analysis, and other characterization methods. In addition to the experimental mechanical tests described, a series of finite element analysis (FEA) or other computational tests are also performed, with related data and metadata and linkages between experimental and computational data.

Definitions

The following definitions apply to stated terms for the purpose of the work required under this statement of work.

Schema - an underlying organizational pattern or structure. This structure defines what information is recorded in the data management system.

(adapted from http://dictionary.reference.com/browse/schema )

Template - an electronic file with a predesigned, customized format and structure, as for a fax, letter, or expense report, ready to be filled in. In the data management system, a template contains the schema terms and space for the data and metadata to be entered.

(adapted from http://dictionary.reference.com/browse/template )

Data - distinct pieces of information, usually formatted in a special way. All software is divided into two general categories: data and programs. Programs are collections of instructions for manipulating data.

(Adapted from www.webopedia.com/TERM/D/data.html)

Metadata - information about the data. By describing the contents and context of data, the usefulness of the original data/files is greatly increased. For example, a web page may include metadata specifying what language it is written in, what tools were used to create it, and where to go for more on the subject, allowing browsers to automatically improve the experience of users.

(adapted from https://en.wikipedia.org/wiki/Metadata )

Workflow - a defined series of tasks to produce a final outcome. Sophisticated workgroup computing applications allow you to define different workflows for different types of jobs. So, for example, in a publishing setting, a document might be automatically routed from writer to editor to proofreader to production. At each stage in the workflow, one individual or group is responsible for a specific task. Once the task is complete, the workflow software ensures that the individuals responsible for the next task are notified and receive the data they need to execute their stage of the process.

(adapted from http://www.webopedia.com/TERM/W/workflow.html )

Test - a procedure, used to identify or characterize a substance or constituent

(adapted from http://www.merriam-webster.com/dictionary/test )

Sample - an item or part representative of a class or whole taken for analysis or testing

(adapted from http://www.thefreedictionary.com/sample )

Field - A space allocated for a particular item of information. In database systems, fields are the smallest units of information you can access.

(adapted from http://www.webopedia.com/TERM/F/field.html )

Script - list of commands that can be executed without user interaction. In the data management system, one example of how a script will be used is to search through a file for data in the file format schema, and transcribe the data into a template with the data management system schema.

(adapted from http://www.webopedia.com/TERM/S/script.html )

PAGE 6 OF 34 SB1341-15-RQ-0750

General Requirements

NCAL requires data management software that will be installed into Government-owned fileservers, to create a “data management system” or “system” that will provide a single location where data and metadata can be housed and a unified environment where the relationships between data (temporal, spatial, dependencies, etc.) can be clearly documented. This data management system must be optimized for experimental mechanical test data and computational mechanical test data.

Figure 1 shows a schematic workflow of our testing processes. The process starts on the left and proceeds to the right in time. Filled rectangles describe stages of our process, dashed rectangles have additional details that are illustrated in figures 2, 3, 4, 5 and

6 (Reference Section IX Supplementary Figures). Trapezoid shapes describe the type of test data and metadata that are required to be included in the data management system, at a minimum. The font choice (as described in the legend) includes details on where these data are located. The term “value” indicates that the data or metadata are a single character/string/numerical. Multiple values are arrays or matrices of single values.

Figure 1 shows the required linkages between data in the data management software. The data management software must have the ability to store this type of data, and store the linkages between the data.

Figure 1: Schematic workflow and types of data and metadata

Specific Requirements

Specifications and User Features

-Figure 1 shows that there are multiple data streams that each have an associated set of data and metadata. The data management system must manage and store: 1) Raw data and metadata from instruments and models, 2) Data and analysis methods used to create derived data from the raw data, and 3) Derived data.

-The raw data comes from a variety of sources, such as fabrication equipment, mechanical test equipment, characterization equipment, finite element models and other computational programs. The management of the data must include a user-defined schema such that the data and metadata populate a searchable database.

-The data management system shall be installed on a government-supplied fileserver. The

Contractor must include system requirements for their software. Preference shall be given to software that can run and perform all required functions on the fileserver defined in the Government Furnished Property section of this document.

Stack of Sheet

Metal

Manufacturer

# of Sheets

Size of Sheets

Coil #

Date Manufactured

Date Received

Sample Fabrication

Sample Layout on sheet

Fabrication Method

Nominal Dimensions

Actual Dimensions (and positions measured at)

Devices Used for measurement

Part Drawings

When fabricated

Who fabricated

Assembly required (weld, glue, etch)

Sample 'name'

Strain Gauge Type

Sample Installation

Sample Orientation

Grip Pressure

Alignment method

Hardware Snapshot

Camera Mounting locations

Lighting source and location

Grip types

Active Acquisition systems

Commentary on test

Testing

Stereo DIC AcqusitionStereo DIC Calibration

Pretest Analysis

Stereo DIC Analysis

ProtoXRD AcqusitionProtoXRD Calibration XRD Analysis

Synchronization between systems

Test Definition

MTS Acqusition & ControlMTS Warmup MTS AnalysisMTS Test Definition

Other analysis

Tested Sample

Constitutive

Measurement

VicGauge Acquistion

Thermal Acquisition

Collate

LEGEND

italics - in software normal - single value bold - multiple values underline - may be repeated

Process Segment (more details on separate page) data or metadata to capture Process Segment

Proprietary

Program

R, Matlab, Octave, Gnuplot, excel

Model Creation

LabView AcquistionLabView Definition

Model Analysis

Stress factor calibration

Filetypes

PAGE 7 OF 34 SB1341-15-RQ-0750

-The system must allow users to manually enter data and metadata, create relational properties and display these values for tests similar to the example test workflow as shown in Figure 1.

-The data and metadata must be shown via a graphical user interface (GUI) with links

(temporal, spatial, dependencies, etc.) between data files containing information about the representative data shown in Figure 1.

-The system must track and display the complete history of data, including modifications.

At a minimum, the following must be tracked and displayed:

Who modified the data;

When was the data modified; and

What was modified in the data.

-The database structure must allow new schema or fields to be added without rebuilding the database.

-The system must allow multiple, separate versions of derived data and analysis scripts or programs. The uploaded data and analysis scripts or procedures must have separate versions if the analysis is repeated, or if the script is changed.

-The system must be hosted internally at NIST.

-Purchase of the software must allow for indefinite use of the software. Perpetual software license(s) are required.

-The system must be able to be backed up via scripts (unattended backup) and administered remotely from inside the NIST firewall.

-The system must be able to be batch export (dump) selected formatted contents (up to and including the entire database and schema) of the data management system into a generic open format (such as XML) that can be read into a different database system.

-For each test, the system must be capable of managing a large number of image files

(typically several thousand 10MB size images or several tens of thousands of 0.25 MB size images), and up to approximately 100 (5 MB max each) ASCII and binary files.

Approximately 100 to 500 tests will be performed each year.

-Storage of data in the system shall be limited by hard drive space, not by database format/structure.

-Access to the software shall be separated by separate user logins to the software. User access must require password authentication.

-Users must be able to connect to the system through dedicated client software from anywhere inside the NIST firewall. Web interface is preferred.

-The system must allow a minimum of ten simultaneous users from a pool of 30 possible users. Preference will be given to concurrent user licenses over named user licenses.

For the purpose of this statement of work, concurrent user licenses means that the licenses can be used by any NIST personnel. Named user licenses means that the licenses are limited to specific individuals.

-Users must be able to use or connect to the system from a variety of different operating systems. At a minimum, users must be able to use or connect to the system through Windows

7, Mac OS 10.9, and Linux Debian.

-Each of the 10 simultaneous users must be able to access from any or all of the operating systems concurrently at any time.

PAGE 8 OF 34 SB1341-15-RQ-0750

-User interface shall support different levels of access based on users’ roles and allow for segregation of data contents by permission. Minimum access levels must be:

*Choose which other users can read the data set and prevent other users from reading the data set.

*Choose which other users can modify the data set and prevent other users from modifying the data set.

*Preventing or allow users to change user access levels.

-Must include a publicly documented Application Program Interface (API) for querying, adding, and deleting records. User manual(s) for the API must be included. One paper and one electronic copy of the user manual(s) must be delivered.

-Must include data plotting tools to generate 2D bar charts and 2D scatter plots at a minimum.

-The types of data, instrumentation and analysis are likely to change over time. As such, the software must allow NIST the in-house ability to add or modify schema and create new import templates/scripts to address these changes.

-The data and metadata in the system must be searchable. The search commands must support multiple nested search terms, wildcard symbols, and incomplete (partial word) search terms. Search queries required for the system shall include, but not be limited to:

*Determining which mechanical tests have been performed on a particular material;

*Tracking calibrations for quality analysis/quality control (QA/QC);

*Listing of all tests performed during a set date range or on a particular type of material;

*Determining what type of speckle pattern on a sample surface for digital image correlation (DIC) resulted in a minimum error;

*Determining which gain setting was used for a particular x-ray diffraction (XRD) analysis searching for which set of post-test analysis data were used as input files for a subsequent FEA test.

-Templates to import the following types of files must be part of the software:

*MTS configuration settings from two testing machines – cruciform & high rate servohydraulic, (exported .txt);

*MTS cruciform data (exported .txt);

*DIC calibration files (exported .txt);

*DIC analysis settings (.z3d);

*ABAQUS input (.inp) and output (.odb) files;

*LS-DYNA input (.k) and output (.d3plot) files;

*ProtoXRD files (.txt files exported from triaxial and multiaxial); and

*Maxiem waterjet part files (.ord, .dxf).

Attachments I and II include example data types for reference only.

Preference shall be given to quoters who provide additional quantities of templates.

Additional quantities of templates must be derived from the list of proprietary software identified under the section below, Capability to be Enhanced.

-The Contractor shall provide a user and operation manual for the system. The manual must be provided in hard copy and electronic format. The manual must address all performance capabilities of the delivered system, including performance capabilities identified as preferences, basic troubleshooting, recommended maintenance, and contact information for software support and maintenance.

-The system must be user friendly in its operation. For the purpose of this statement of work, user friendly means:

(1) The system is efficient and effective in its operation to upload data and create templates with the least number of steps possible;

(2) The system incorporates shortcuts to perform routine functions to the maximum extent practicable; and

(3) The system can be taught to a professional in a one day training session. For

PAGE 9 OF 34 SB1341-15-RQ-0750

the purpose of this statement of work, a professional is defined as an individual who is familiar with the data and templates being captured by the system, has scientific knowledge of the professional environment supported by the system, and maintains a degree in the professional environment supported by the system.

Capability to be Enhanced

Figure 1 shows the range of different data types that must be part of the data management system. While the Contractor is not required to provide enhancements to support all of these data types with the system delivered under this contract, the software must have the capability to be enhanced in accordance with the following requirements.

Enhancements may be purchased via a separate procurement mechanism, subject to the availability of funds.

-The system must import 1) input files and 2) files generated by other proprietary software. These imported files shall be used to populate data and metadata into the system via defined schema. Proprietary software used by NCAL for which such imports may be required are described in Figures 1 through 6 and listed below:

Correlated Solutions: VicSnap, Vic3D, VicGauge, Vic2D

ProtoXRD: XRDWin

MTS: 793, Station Manager, Basic Testware, TestSuite

Instron: 8800 Controller Console

FLIR: ExaminIR Pro

Dassault Systèmes: ABAQUS

LSTC: LS-Dyna

ANSYS: ANSYS

National Instruments: Labview

-The system must support scriptable interactions on computer workstations (such as pushing data to system, pulling data from system, submit analysis script to high performance computing (HPC) cluster) using command line tools (such as bash, Python, R, Matlab, etc.) from, at a minimum PC, Mac and Linux. Other operating systems may also be required.

-The system must manage and store the physical locations of equipment relative to a fixed reference frame.

-The system must notify users who have used a prior version of an analysis when subsequent analysis “replaces” an original analysis.

-Additional plot types or graphing packages must be added to visualize 3D data, data with x and/or y error bars, and color palette mapped 3D and 4D data.

-The system must time stamp comments appended to completed tests.

-The system must have the ability to query data sets from the stored data using scripts, removing the need for users to store local copies of data on a particular computer workstation.

Installation

The Contractor shall install the software and provide all effort required for the system to meet all required specifications and user features. A total of two installations shall be provided.

First Installation

The first installation shall take place two months after the kick-off meeting has been completed. The Contractor shall deliver the system and install the system on the NIST fileserver. The Contractor shall demonstrate all specifications and user features completed as of the date of the installation.

The Government will retain the system on the fileserver, work with the system and provide feedback to the Contractor on the performance capability of the system. The Contractor shall provide telephone support to the Government after the first installation to respond questions. Support must be provided during business hours only.

PAGE 10 OF 34 SB1341-15-RQ-0750

Installation of Final Version

The Contractor shall deliver and install the final version of the software on the NIST fileserver not later than five months after award. All specifications, user features, and quoted preferences must be successfully demonstrated prior to final acceptance of the software. The Contractor must repair/correct any problems or issues with the software at no additional cost to the Government. All repairs/corrections must be completed not later than six months after award.

Training

The Contractor shall provide training on the final version of the system. Training shall be provided for up to ten NIST personnel, on-site at NIST Gaithersburg. Training shall cover all of the following, at a minimum:

-Use of the data management software;

-How to administer the data management software;

-How to write templates;

-Modification of templates. The Contractor shall provide sample templates that can be modified;

-How to add data to the data management software.

Software Support

The Contractor shall provide unlimited support for the software. Software support shall be for a period of one year, at a minimum. Software support shall commence upon final acceptance of the final version of the data management system.

Software support shall include, at a minimum, software updates, releases within a feature set, security patches, telephone, on-line, and email support during regular business hours, and on-site assistance for more complicated requests.

Software updates shall include, at a minimum, bug fixes and/or correction of minor software issues. Software updates do not constitute additional charges to obtain the benefits of the updates.

Kick-Off Meeting and Project Plan

Kick-Off Meeting

The Contractor shall attend a kick-off meeting, on-site at NIST Gaithersburg. The

Contractor shall work with the Contracting Officer’s Representative (COR) and Technical

Point of Contact (TPOC) to schedule a date for the meeting. The meeting shall be scheduled not later than five days from the date of award. The meeting shall be conducted not later than 15 days from the date of award.

The Contract Specialist (CS), COR, TPOC, and other authorized NIST personnel shall be in attendance. The Contractor shall determine the appropriate individuals that should attend the meeting. At a minimum, the Project Manager shall attend.

The kick-off meeting shall be utilized to review all contract requirements, deliverables, and discuss the project plan and subsequent updates. Discussions conducted during the kick-off meeting must not make changes to the terms and conditions of the contract, including requirements of the statement of work.

Milestone Plan

The Contractor shall establish and maintain a milestone plan. The plan shall, at a minimum, include all project milestones and deliverables, clearly indicate the critical path, and clearly indicate the current duration and completion dates for all milestones and deliverables.

The first milestone plan shall be delivered to the Government and discussed at the kick-off meeting.

The Contractor shall provide an up-to-date milestone schedule on a monthly basis to the

COR, TPOC, and CS via e-mail. The milestone schedule shall be provided in MS Project format or equivalent as approved by the COR.

PAGE 11 OF 34 SB1341-15-RQ-0750

Software Maintenance

The Government has included four OPTION LINE ITEMS for software maintenance. Line items

0002, 0003, 0004, and 0005 are option line items. Quoters must provide a firm-fixed price for all option line items. Prices for option line items shall remain valid in accordance with the following:

Line Item 0002, Option Period I, one year from the expiration date of software support;

Line Item 0003, Option Period II, two years from the expiration date of the software support;

Line Item 0004, Option Period III, three years from the expiration date of the software support;

Line Item 0005, Option Period IV, four years from the expiration date of the software support.

The period of performance for all option line items shall be one year from the date of exercise of option. The Government may exercise option line items, at its discretion, at the time of award, or any time prior to the expiration date of the period of performance of the base period or any option period. Options will be exercised by the issuance of a purchase order modification (Standard Form 30).

The Contractor shall provide unlimited maintenance for the software. Software maintenance shall include, at a minimum: software updates, releases within a feature set, security patches, telephone, on-line, and email support, and on-site assistance at NIST for more complicated requests. All maintenance shall be provided during normal business hours.

Software updates shall include, at a minimum, bug fixes and/or correction of minor software issues. Software updates do not constitute additional charges to obtain the benefits of the updates.

Period of Performance

Delivery of the final version of the system, installation, training and demonstration of user features and specifications shall be completed not later than six months from the date of award.

Place of Performance

Installation of the software and training shall be accomplished at NIST, Gaithersburg, Maryland. Normal business hours are Monday through Friday, 8:30 a.m. to 5:00 p.m. with the exception of Federal holidays.

If agreed to by both parties, patches or customization may occur at NIST, Gaithersburg, Maryland.

Government Furnished Property

The Government shall provide all of the following to the Contractor for use in completing work required under this contract. All property shall be utilized on-site at NIST

Gaithersburg.

- NCAL File server (technical details below)

- (2x) AMD Opteron Eight-Core Processor Model 6320 2.8GHz, (total 16 CPU cores)

- 64GB DDR3-1600MHz, Registered ECC memory

- Supermicro H8DGi-F, Dual Opteron Serverboard

- Intel® 82576 controller, Dual-Port Gigabit Ethernet

- Matrox G200eW Graphics

- LSI Logic MegaRAID 9240-4I 4-port, 6Gb/s SAS RAID Controller

- (12x) 3TB 7200 RPM, 6 Gbps, Enterprise SATA Hard Drives (RAID array)

PAGE 12 OF 34 SB1341-15-RQ-0750

- (2x) 500GB 7200 rpm, 2.5" SATA Hard Drives (system files)

- Operating system – Debian 8

Deliverables

The Contractor shall submit all deliverables in accordance with the timelines herein.

References to the submission of deliverables in option periods and/or over the life of the contract includes any and all option periods exercised at the Government’s discretion, however, does not guarantee that option periods will be exercised.

The COR will have five business days to complete review of each deliverable, the COR will accept or reject the deliverables in writing. In the event of the rejection of any deliverable, the Contractor shall be notified in writing by the COR, giving the specific reason(s) for rejection. The Contractor shall have ten business days, to correct the rejected deliverable and return it to the COR.

Description Quantity Due Date

Attend kick-off meeting One (1) 15 days after award

Milestone plan One (1) 15 days after award

Installation of first version of data management system

Telephone support after installation

One (1) 2 months after the kick-off meeting

On-going until final installation

Installation of final version of data management system

1 5 months after award

Training 1 Not later than 6 months after award

Paper and electronic copies of software user manual electronic

1 paper

With installation of final version

Paper and electronic copies of API user manual electronic

1 paper

With installation of final version

Software support As needed

Unlimited

One year after acceptance of the final version of the system

Software maintenance As needed

Unlimited

Upon exercise of option line items

Data Rights

The Government will maintain data rights to all deliverables in accordance with Federal

Acquisition Regulation Clause 52.227-17 Rights in Data—Special Works. This assertion does not apply to deliverables or portions of deliverables that were developed solely at the

Contractor’s expense.

Section 508

Section 508 Standards do not apply to the data management system.

PAGE 13 OF 34 SB1341-15-RQ-0750

Supplementary Figures

Figure 2: ProtoXRD Workflow. Contains details not shown in Figure 1.

Figure 3: Stereo DIC Workflow. Contains details not shown in Figure 1.

PAGE 14 OF 34 SB1341-15-RQ-0750

Figure 4: VicGauge, Thermal and Labview workflows. Contains details not shown in Figure 1.

Figure 5: MTS workflows. Contains details not shown in Figure 1.

PAGE 15 OF 34 SB1341-15-RQ-0750

Figure 6: FEA workflows. Contains details not shown in Figure 1

. 2 EVALUATION CRITERIA AND BASIS FOR AWARD

PAGE 16 OF 34 SB1341-15-RQ-0750

The Government will award a purchase order resulting from this solicitation to the responsible quoter whose quotation, conforming to the solicitation, results in the best value to the Government, price and other factors considered.

The following will be used to evaluate quotations:

Technical Capability

Experience

Past Performance

Price

Technical Capability, Experience, and Past Performance, when combined, shall be more important than price. Technical capability, experience and past performance are equal in merit to each other.

TECHNICAL CAPABILITY

Technical capability will be evaluated to determine that the quoted system will meet all required specifications and user features and that the quotation is feasible and likely to succeed.

In determining best value, stronger consideration shall be given to:

-Software that can run and perform all required functions on the fileserver defined in the Government Furnished Property section of the statement of work;

and/or

-Software that is web interfaced; and/or

-Products that provide additional quantities of templates derived from the list of proprietary software identified in the statement of work; and/or

-Concurrent users.

EXPERIENCE

Experience shall be evaluated to determine the degree of and relevance of experience the

Contractor possesses in developing the same or similar systems.

PAST PERFORMANCE

Past Performance shall be evaluated to determine the overall quality of the products and services provided by the Contractor. Evaluation of Past Performance shall be based on the references provided and/or information provided by NIST and its affiliates.

Quoters with no relevant past performance will receive a neutral rating.

PRICE

Price will be evaluated to determine that the total price is consistent with the technical portion of the quotation and is a fair and reasonable overall price to the

Government.

. 3 52.212-1 INSTRUCTIONS TO OFFERORS--COMMERCIAL ITEMS (APR 2014)

(a) North American Industry Classification System (NAICS) code and small business size standard.

The NAICS code and small business size standard for this acquisition appear in Block 10 of the

PAGE 17 OF 34 SB1341-15-RQ-0750

solicitation cover sheet (SF 1449). However, the small business size standard for a concern which submits an offer in its own name, but which proposes to furnish an item which it did not itself manufacture, is 500 employees.

(b) Submission of offers. Submit signed and dated offers to the office specified in this solicitation at or before the exact time specified in this solicitation. Offers may be submitted on the SF 1449, letterhead stationery, or as otherwise specified in the solicitation. As a minimum, offers must show--

(1) The solicitation number;

(2) The time specified in the solicitation for receipt of offers;

(3) The name, address, and telephone number of the offeror;

(4) A technical description of the items being offered in sufficient detail to evaluate compliance with the requirements in the solicitation. This may include product literature, or other documents, if necessary;

(5) Terms of any express warranty;

(6) Price and any discount terms;

(7) Remit to address, if different than mailing address;

(8) A completed copy of the representations and certifications at FAR 52.212-3 (see FAR 52.212-3(b) for those representations and certifications that the offeror shall complete electronically);

(9) Acknowledgment of Solicitation Amendments;

(10) Past performance information, when included as an evaluation factor, to include recent and relevant contracts for the same or similar items and other references (including contract numbers, points of contact with telephone numbers and other relevant information); and

(11) If the offer is not submitted on the SF 1449, include a statement specifying the extent of agreement with all terms, conditions, and provisions included in the solicitation. Offers that fail to furnish required representations or information, or reject the terms and conditions of the solicitation may be excluded from consideration.

(c) Period for acceptance of offers. The offeror agrees to hold the prices in its offer firm for 30 calendar days from the date specified for receipt of offers, unless another time period is specified in an addendum to the solicitation.

(d) Product samples. When required by the solicitation, product samples shall be submitted at or prior to the time specified for receipt of offers. Unless otherwise specified in this solicitation, these samples shall be submitted at no expense to the Government, and returned at the sender`s request and expense, unless they are destroyed during preaward testing.

(e) Multiple offers. Offerors are encouraged to submit multiple offers presenting alternative terms and conditions or commercial items for satisfying the requirements of this solicitation. Each offer submitted will be evaluated separately.

(f) Late submissions, modifications, revisions, and withdrawals of offers.

(1) Offerors are responsible for submitting offers, and any modifications, revisions, or withdrawals, so as to reach the Government office designated in the solicitation by the time specified in the solicitation. If no time is specified in the solicitation, the time for receipt is 4:30 p.m., local time, for the designated Government office on the date that offers or revisions are due.

(2)

(i) Any offer, modification, revision, or withdrawal of an offer received at the Government office designated in the solicitation after the exact time specified for receipt of offers is late and will not be considered unless it is received before award is made, the Contracting Officer determines that accepting the late offer would not unduly delay the acquisition; and--

(A) If it was transmitted through an electronic commerce method authorized by the solicitation, it was received at the initial point of entry to the Government infrastructure not later than 5:00 p.m. one working day prior to the date specified for receipt of offers; or

(B) There is acceptable evidence to establish that it was received at the Government installation designated for receipt of offers and was under the Government`s control prior to the time set for receipt of offers; or

(C) If this solicitation is a request for proposals, it was the only proposal received.

(ii) However, a late modification of an otherwise successful offer, that makes its terms more favorable to the Government, will be considered at any time it is received and may be accepted.

(3) Acceptable evidence to establish the time of receipt at the Government installation includes the time/date stamp of that installation on the offer wrapper, other documentary evidence of receipt maintained by the installation, or oral testimony or statements of Government personnel.

(4) If an emergency or unanticipated event interrupts normal Government processes so that offers cannot be received at the Government office designated for receipt of offers by the exact time specified in the solicitation, and urgent Government requirements preclude amendment of the solicitation or other notice of an extension of the closing date, the time specified for receipt of offers will be deemed to be extended to the same time of day specified in the solicitation on the first work day on which normal Government processes resume.

PAGE 18 OF 34 SB1341-15-RQ-0750

(5) Offers may be withdrawn by written notice received at any time before the exact time set for receipt of offers. Oral offers in response to oral solicitations may be withdrawn orally. If the solicitation authorizes facsimile offers, offers may be withdrawn via facsimile received at any time before the exact time set for receipt of offers, subject to the conditions specified in the solicitation concerning facsimile offers. An offer may be withdrawn in person by an offeror or its authorized representative if, before the exact time set for receipt of offers, the identity of the person requesting withdrawal is established and the person signs a receipt for the offer.

(g) Contract award (not applicable to Invitation for Bids). The Government intends to evaluate offers and award a contract without discussions with offerors. Therefore, the offeror`s initial offer should contain the offeror`s best terms from a price and technical standpoint. However, the Government reserves the right to conduct discussions if later determined by the Contracting Officer to be necessary. The Government may reject any or all offers if such action is in the public interest; accept other than the lowest offer; and waive informalities and minor irregularities in offers received.

(h) Multiple awards. The Government may accept any item or group of items of an offer, unless the offeror qualifies the offer by specific limitations. Unless otherwise provided in the Schedule, offers may not be submitted for quantities less than those specified. The Government reserves the right to make an award on any item for a quantity less than the quantity offered, at the unit prices offered, unless the offeror specifies otherwise in the offer.

(i) Availability of requirements documents cited in the solicitation.

(1)

(i) The GSA Index of Federal Specifications, Standards and Commercial Item Descriptions, FPMR Part 101-29, and copies of specifications, standards, and commercial item descriptions cited in this solicitation may be obtained for a fee by submitting a request to-- GSA Federal Supply Service Specifications Section Suite 8100 470 East L`Enfant Plaza, SW Washington, DC 20407 Telephone (202) 619-8925 Facsimile (202) 619-8978.

(ii) If the General Services Administration, Department of Agriculture, or Department of Veterans Affairs issued this solicitation, a single copy of specifications, standards, and commercial item descriptions cited in this solicitation may be obtained free of charge by submitting a request to the addressee in paragraph (i)(1)(i) of this provision. Additional copies will be issued for a fee.

(2) Most unclassified Defense specifications and standards may be downloaded from the following ASSIST websites:

(i) ASSIST (https://assist.dla.mil/online/start).

(ii) Quick Search (http://quicksearch.dla.mil/).

(iii) ASSISTdocs.com (http://assistdocs.com).

(3) Documents not available from ASSIST may be ordered from the Department of Defense Single Stock Point (DoDSSP) by--

(i) Using the ASSIST Shopping Wizard (https://assist.dla.mil/wizard/index.cfm);

(ii) Phoning the DoDSSP Customer Service Desk (215) 697-2179, Mon-Fri, 0730 to 1600 EST; or

(iii) Ordering from DoDSSP, Building 4, Section D, 700 Robbins Avenue, Philadelphia, PA 19111-5094, Telephone (215) 697-2667/2179, Facsimile (215) 697-1462.

(4) Nongovernment (voluntary) standards must be obtained from the organization responsible for their preparation, publication, or maintenance.

(j) Data Universal Numbering System (DUNS) Number. (Applies to all offers exceeding $3,000, and offers of $3,000 or less if the solicitation requires the Contractor to be registered in the System for Award Management (SAM) database. The offeror shall enter, in the block with its name and address on the cover page of its offer, the annotation DUNS or DUNS+4 followed by the DUNS or DUNS+4 number that identifies the offeror`s name and address. The DUNS+4 is the DUNS number plus a 4-character suffix that may be assigned at the discretion of the offeror to establish additional SAM records for identifying alternative Electronic Funds Transfer (EFT) accounts (see FAR Subpart 32.11) for the same concern. If the offeror does not have a DUNS number, it should contact Dun and Bradstreet directly to obtain one. An offeror within the United States may contact Dun and Bradstreet by calling 1-866-705-5711 or via the internet at http://fedgov.dnb.com/webform. An offeror located outside the United States must contact the local Dun and Bradstreet office for a DUNS number. The offeror should indicate that it is an offeror for a Government contract when contacting the local Dun and Bradstreet office.

(k) System for Award Management. Unless exempted by an addendum to this solicitation, by submission of an offer, the offeror acknowledges the requirement that a prospective awardee shall be registered in the SAM database prior to award, during performance and through final payment of any contract resulting from this solicitation. If the Offeror does not become registered in the SAM database in the time prescribed by the Contracting Officer, the Contracting Officer will proceed to award to the

PAGE 19 OF 34 SB1341-15-RQ-0750

next otherwise successful registered Offeror. Offerors may obtain information on registration and annual confirmation requirements via the SAM database accessed through https://www.acquisition.gov.

(l) Debriefing. If a post-award debriefing is given to requesting offerors, the Government shall disclose the following information, if applicable:

(1) The agency`s evaluation of the significant weak or deficient factors in the debriefed offeror`s offer.

(2) The overall evaluated cost or price and technical rating of the successful and the debriefed offeror and past performance information on the debriefed offeror.

(3) The overall ranking of all offerors, when any ranking was developed by the agency during source selection.

(4) A summary of the rationale for award;

(5) For acquisitions of commercial items, the make and model of the item to be delivered by the successful offeror.

(6) Reasonable responses to relevant questions posed by the debriefed offeror as to whether source-selection procedures set forth in the solicitation, applicable regulations, and other applicable authorities were followed by the agency.

(End of Provision)

. 4 ADDENDUM TO 52.212-1

PAGE 20 OF 34 SB1341-15-RQ-0750

(a) General Instructions

Quotations are required to conform to solicitation provisions and be prepared in accordance with this section. To aid in evaluation, the quotation must be clearly and concisely written as well as being neat, indexed (cross-indexed as appropriate) and logically assembled. All pages of each part shall be appropriately numbered and identified with the name of the offeror, the date, and the solicitation number.

Quoters shall submit one original of their quotation, marked as such, and two copies of the technical and price quotations. Only one copy of the business portion of the quotation is required to be submitted.

Only one copy of the complete quotation is required to be submitted for email submissions.

Quotations must be received not later than August 13, 2015, at 3:30 PM Eastern Time. E-mail quotations are acceptable. Fax quotations shall not be accepted. E-mail quotations are considered received when the e-mail enters into the electronic inbox of Carol Wood.

Only information received on or before the due date and time shall be considered for award. Any quotation, or part thereof, received after the due date and time, shall be deemed late and not considered for award.

Each volume shall be clearly marked by volume number and title.

(b) Overall Arrangement of the Quotation

(1) BUSINESS QUOTATION

(A)(i) The Standard Form 1449, must be executed fully and used as the cover sheet

(or first page) of Volume I. Include one (1) originally signed copy of the form in the

Original Volume I.

(ii) Acceptance Period - The acceptance period shall not be less than 120 days.

(iii) Concurrence with all terms and conditions of the solicitation.

(iv) The Dun and Bradstreet Number for the quoter’s active registration at the System for Award Management, (www.SAM.Gov) website.

(iv) If the quoter’s representations and certifications do not reflect the

NAICS code governing this solicitation, quoters must submit documentation of their business size under the NAICS code governing this solicitation.

(v) Signature Authority - The person signing the form must have the authority to commit the quoter to all of the provisions and clauses of the solicitation, fully recognizing that the Government has the right, by terms of the solicitation, to make an award without further discussion if it so elects.

(2) TECHNICAL QUOTATION

(A) General

(1) The technical quotation consists of the quoter’s technical and management aspects of the acquisition. It must indicate your company's capabilities and the means to be used to satisfy the requirements of the Statement of Work. It will be evaluated in accordance with the evaluation criteria and must be specific and complete in every detail. The quotation must be practical and be prepared simply and economically, providing straightforward, concise delineation of what it is the quoter will do to satisfy the requirements of the Statement of Work.

(2) In order that the technical quotation may be evaluated strictly on the merit of the material submitted, no price information shall be included.

(3) The quotation shall not merely offer to perform work in accordance with the statement of work, but shall outline the actual work proposed as specifically as practical. The Statement of Work reflects the problems and objective of the program under consideration; therefore, repeating the Scope of Work without sufficient elaboration will not be acceptable.

PAGE 21 OF 34 SB1341-15-RQ-0750

(4) The quotation must be typed, on 8-1/2" by 11" paper, not exceeding 15 pages, single sided, single spaced, exclusive of experience and past performance references.

(B) Specific areas to be addressed:

1. For the purpose of evaluation of Technical Capability, the technical quotation must include:

-Documentation and/or product literature, which clearly demonstrates that the quoter will meet all required specifications and user features, including installation, training and software support. The Contractor shall describe the distinction between an update and an upgrade; AND

-If any required specification or user feature is not covered in the documentation and/or product literature, a discussion of what steps to be taken so that the software will meet that requirement; AND

-A discussion of the telephone support that will be provided and how the Contractor proposes to meet that requirement. The discussion must identify the number of staff that the Contractor has available for support; AND