CSS__final.pdf

CLASSIFICATION CODE: R - Professional, Administrative and Management Support Services

TITLE: - Development of Messaging Standard Semantic Refinement Tool (MSSRT) and Business Process Models (for Business Process Cataloging and Classification System (BPCCS))

SOLICITATION NUMBER: SB1341-16-RQ-0920

RESPONSE DATE: August 22, 2016

CONTACT POINTS: Robert Cowins, Contract Specialist, (301) 975-8335

Abdul-Kudus Yahaya, Contracting Officer, (301) 975-8802

DESCRIPTION:

The National Institute of Standards and Technology (NIST) has a requirement for Administrative and Management Support Services to be utilized by Engineering Laboratory (EL) at NIST, Gaithersburg, MD.

THIS IS A COMBINED SYNOPSIS/SOLICITATION FOR COMMERCIAL

ITEMS PREPARED IN ACCORDANCE WITH THE FORMAT IN FAR SUBPART 12.6-

STREAMLINED PROCEDURES FOR EVALUATION AND SOLICITATION

FOR COMMERCIAL ITEMS-AS SUPPLEMENTED WITH ADDITIONAL INFORMATION

INCLUDED IN THIS NOTICE. THIS ANNOUNCEMENT CONSTITUTES THE ONLY

SOLICITATION; QUOTATIONS ARE BEING REQUESTED, AND A SEPARATE

WRITTEN SOLICITATION DOCUMENT WILL NOT BE ISSUED. THE SOLICITATION IS

BEING ISSUED USING SIMPLIFIED ACQUISITION PROCEDURES UNDER THE

AUTHORITY OF FAR PART 13.

This solicitation is a Request for Quotation (RFQ). The solicitation document and incorporated provisions and clauses are those in effect through Federal Acquisition Circular (FAC) 2005-89.

1352.215-72 INQUIRIES (APR 2010)

Offerors must submit all questions concerning this solicitation in writing to robert.cowins@nist.gov. Questions should be received no later than 3 calendar days after the issuance date of this solicitation. Any responses to questions will be made in writing, without identification of the questioner, and will be included in an amendment to the solicitation.

Even if provided in other form, only the question responses included in the amendment to the solicitation will govern performance of the contract.

(End of Provision) mailto:robert.cowins@nist.gov

The associated North American Industrial Classification System (NAICS) code for this procurement is 541511 with a small business size standard of $27.5 million.

This acquisition is 100% set-aside for small business.

All offerors shall provide a quotation for the following line items:

Line Item 0001:

Quantity: 1 Unit of Issue: Lot Description: Contractor support for NIST Cloud Messaging Standard Semantic Refinement Tool (CMSSRT) and Business Process Models Project (See SOW for detailed requirement) Period of Performance: 12 months.

Statement of Work

Development of Messaging Standard Semantic Refinement Tool (MSSRT) and

Business Process Models (for Business Process Cataloging and Classification System

(BPCCS))

1. BACKGROUND INFORMATION

The National Institute of Standards and Technology (NIST) has a research project entitled Service Oriented Architectures for Smart Manufacturing. The project’s objective is to advance state of manufacturing systems integration, enabling manufacturers to rapidly compose software and hardware services into manufacturing systems to meet changing requirements of the manufacturing enterprise.

Rapid composition of software and hardware services requires an efficient integration approach.

However, efficiency of integration approaches to manufacturing systems is hindered by (1) large and complex messaging specifications, (2) imprecise messaging specification methods, (3) numerous legacy systems and processes with differing data exchange requirements, and (4) the lack of a common, syntax-independent integration specification that supports deployment on multiple platforms.

Removing these hindrances is technically hard due to (1) the complexity of manufacturing systems, (2) the heterogeneity of the systems and platforms within and across enterprises, and (3) the lack of a proven mechanism for cataloging, documenting, sharing, and reusing usage information of messaging specifications, which are needed for the standard development organization (SDO) to produce simpler, more refined, and precise community- or usage-specific messaging specifications. Usage information of a messaging specification is a usage-specific messaging specification and information about goal, business environment (i.e., business context such as industry sector, geo-location, etc.), means (e.g., constraints on standard codes use), and other aspects of use of the usage-specific messaging specification that are essential for effective, repeatable, and traceable use of the specification.

Industry has been building development and usage methods and common meta-models for managing the life-cycle of messaging specifications with only partial success with respect to the aforementioned challenges. Significantly, previous industry-driven efforts to developing a solution for cataloging and documenting usage information have failed due to the complexity of the problem. We believe that life-cycle management of usage information of a messaging specification plays a much more significant role than what has been realized thus far.

The key idea for this project is to develop measurement science, in the form of reference models, methods, software tools, and a knowledge base, which will enable manufacturers to compose software and hardware services into manufacturing systems. Central to our idea is formal, precise treatment and life-cycle management of usage information of messaging specifications that drive the evolution of the core (superset) messaging standard.

The outcomes of the project will (1) allow manufacturers to increase efficiency of manufacturing systems integration, (2) cut standard development costs, and (3) enable systems developers to decrease risk inherent in manufacturing systems integration.. Any company engaged in systems integration will be able to benefit because they will in a position to (1) precisely specify their integration requirements, initially in the form of a formal usage information of a messaging specification; (2) share and reuse usage information from other companies in a (standard) community; and (3) jumpstart their integration projects by using usage-specific messaging standards provided by an SDO, enabled by accessible information on usage information of a messaging specifications provided by users.

As part of this effort, NIST is planning to develop Messaging Standard Semantic Refinement Tool (MSSRT) and Business Process Cataloging and Classification System (BPCCS)

1.1 Messaging Standard Semantic Refinement Tool (MSSRT)

NIST is planning to develop MSSRT – a proof-of-concept (POC) web-based application software environment for the life-cycle management of messaging specifications, including the usage information, where a new method to create, maintain, and use messaging standards will be developed and validated with industry. The POC software tool will validate the multi-tenant methods and meta-models for life-cycle management of messaging specifications developed by NIST (based on the UN/CEFACT Core Component Specification). It will provide core functionalities that can be extended and commercialized by industry.

1.2 Business Process Cataloging and Classification System (BPCCS)

NIST is planning to design Business Process Cataloging and Classification System (BPCCS) to enable life-cycle management of a messaging specification, including usage information of the specification (such as goals, business context, etc.), as planned for the Messaging Standard Semantic Refinement Tool (MSSRT).

A core focus of BPCCS is to provide to open community of stakeholders shared definitions of required concepts and terms for business processes that span across an enterprise and its multitier supplier network. BPCCS consists of two main components: (1) a catalog, for storing business process models (including reference models); and (2) classification scheme, for classifying process models stored in the catalog, which allows encoding the context for an intended usage of the models (e.g., specifying functional actors and their activities that trigger and receive required integration messages). Both components include methods for managing the lifecycle of their content.

2. PURPOSE AND OBJECTIVES OF THE PROCUREMENT

The purpose of the procurement is for the contractor to develop (1) the MSSRT tool and (2) Business Process Models based on manufacturing scenarios from Open Applications Group Integration Specification (OAGIS) to support design of BPCCS system.

2.1 Messaging Standard Semantic Refinement Tool (MSSRT)

Generally, the MSSRT will support both the messaging standard end user and the messaging standard developer roles. At this stage, the focus will be on the functionalities for the end user role that include the following:

• Managing business context and context classification schemes used for creating a business context.

• Managing code lists that include not only creation and deletion but also extension and restriction.

• Managing business information entities (BIEs). A BIE is a usage-specific messaging specification (also known as a profile message specification or a subset) where the usage is defined by the business context. A BIE is derived by subsetting and refining the core messaging specification as well as user extensions. Collectively, the core messaging specification and user extensions are called core components (CC). The current focus of the core standard specification will be the OAGIS standard.

• Managing user extensions. End users may extend the core standard specification to meet their integration requirements.

• Generating a profile XML schema based on the BIE.

These functionalities need to be supported in a multi-tenant, web-based application environment.

2.2 Business Process Cataloging and Classification System (BPCCS)

BPCCS will allow storage and retrieval of Business Process Models based on manufacturing scenarios from OAGIS:

• in a standard, computer processable format (BPMN 2.0 XML)

• as BPMN collaborations, with variants using private and public processes for each OAGIS scenario, created based on OAGIS scenario documentation (sections 0 to 5) o BPMN collaboration with public processes will include start and end events, pools, messages, message flows, sequence flows and only activities that send and receive messages o BPMN collaboration with private processes will include additional elements such as internal activities, lanes, gateways, other event types, event handling, data elements and data associations

• applying BPMN interaction patterns where applicable, such as Acknowledge or Respond interaction pattern or Confirmation pattern shown in Feasibility Document

• on different levels of details o business level, corresponding to the first level of details identified in Feasibility Document o system level, corresponding to the second and third level of details identified in Feasibility Document, adding details such as referencing OAGIS BODs from BPMN model

3. TASKS

The contractor shall provide all labor, project oversight, administration and technical execution of this project. The contractor is responsible for maintaining accurate records of project activities and shall provide the services described below.

3.1 MSSRT Tool

Task Task Title Task Description 1 Multi-tenant MSSRT All sub-tasks below (A – C) culminate in the completion of this task.

1A Multi-tenant usage scenario definition Work with industry and the OAG Semantic Refinement Working Group (OAG SR WG) to determine how BIEs and user extensions may be shared within a community.

This may entail functionality to allow the end user to control what to share.

1B Method and data model enabling the multi-tenant usage scenario developed in 1A.

Develop a data model and a functional design that will support the multi-tenant usage scenario. NIST will provide a data model and a functional design that are architected to support a single tenant (multiple users of a single organization).

1C MSSRT software supporting the functionalities outlined in Section 1 and the multi-tenant usage scenario developed in 1A.

Develop a MSSRT software system. The MSSRT shall be a 3-tier web-application deployable on WebLogic Application Server. The UI tier shall be accessible using an HTML compliant browser. Although the UI should work generally on any HTML compliance browser, Google Chrome will be the target test browser. The application tier shall be developed using the Java programming language. Oracle relational database shall be used in the database tier. A combination with NOSQL database may be used; however, the OAGIS model content shall be kept in the relational database.

NIST will provide a data model and a detailed functional design along with a prototype software system architected to support a single tenant MSSRT. The provided prototype will support managing BIEs, code lists, business context and profile XML schema generation functionalities. It may or may not support the user extension functionality. The primary purpose of providing the prototype system is to help the contractor understand the requirements. It is not necessary for the contractor to start developing the MSSRT from the codes developed for the prototype system. Additionally, NIST will provide the OAGIS 10.1 core standard specification readily imported (from the original XML schema representation) into the Oracle relational database whose schema complies with the NIST-provided data model.

2 Develop the MSSRT user guide

Develop the user guide for the MSSRT.

3.2 BP Models for BPCCS

1 Develop detailed BPMN models of manufacturing scenarios

All sub-tasks below (A – G) culminate in the completion of this task

1A OAGIS Business Process Metamodel

Provide a business process metamodel for the identified OAGIS manufacturing scenarios (see Section 7). This will allow a business process software developer design software that correctly reads OAGIS business process models. The metamodel may be based on a BPMN specification.

1B Analyze and Complete OAGIS manufacturing scenarios

Determine level of detail in OAGIS business scenario documentation for each OAGIS manufacturing scenario and impact that it will have on level of details in appropriate BPMN models. Identify and resolve any potential uncertainties, ambiguities and assumed errors in scenario documentation.

1C Analyze interaction patterns

Identify interaction patterns applicable across identified OAGIS manufacturing scenarios and accordant with provided business process metamodel.

1D Develop BPMN models with public processes

Develop BPMN models with public processes for the identified OAGIS manufacturing scenarios. Provided BPMN models should be based on business process metamodel, defined at business and system level and include interaction patterns where applicable.

1E Develop BPMN models Extend BPMN models with public processes by with private processes including process’ private details from business scenario documentation, if such detail is available in the completed OAGIS scenario. Provided BPMN models should be based on business process metamodel, defined at business and system level and include interaction patterns where applicable.

1F Prepare BPMN models in appropriate format

Export created BPMN models into BPMN 2.0 XML format.

1G Final report summarizing and detailing the process, assumptions, and BPMN model details

A document summarizing and detailing the process, assumptions, and BPMN model details.

The Contractor shall:

1. Acknowledge that all deliverables and data generated under this contract remains the property of the Government. Any improvements to existing open source software may be released under an open source license.

2. Acknowledge that the government retains government use license to all such inventions.

3. Unless otherwise noted, the contractor shall provide all labor and materials for the tasks listed below.

4. CONTRACTOR REQUIREMENTS

A. Minimum Qualifications

The Contractor shall meet the following minimum qualifications:

1. Documented experience working with OAGIS 9.x or 10.x version, including the proven ability to extend, profile, apply, and deploy OAGIS Business Object Document specification.

2. Documented experience in using OAGIS for the purpose of enterprise systems and supply chain management systems integration.

3. Documented experience developing and/or working with the UN/CEFACT Core Component Specification.

4. Documented experience working with Oracle database.

5. Documented experience working with 3-tier software development in HTML, Java Script, and

Java.

6. Documented experience developing web-based application.

7. Documented experience working with Oracle WebLogic.

8. Documented experience working BPMN, including the proven ability to extend, profile, and apply these specifications.

9. Documented experience in developing BPMN models for the purpose of enterprise systems and supply chain management systems modeling and integration.

B. Minimum Qualifications of Key Personnel.

The contractor key personnel shall meet the following minimum qualifications:

1. Five years of experience in OAGIS use, development, and deployment.

2. Three years of experience in applying OAGIS to enterprise systems integration.

3. One year of experience in UN/CEFACT Core Component Specification.

4. Extensive experience working with manufacturing industry on systems integration projects.

5. Five years of experience developing 3-tier, web-based, software development in Java.

6. One year of experience deploying applications in Oracle Web Logic application server.

7. One year of experience developing multi-tenant web application.

8. Three years of experience in BPMN modeling and tool development and deployment.

Personally Identifiable Information: As the work may contain Personally Identifiable Information (PII), the system and its various components must be deemed moderate for confidentiality and security controls must be implemented commensurate with protecting this data type. A Privacy Impact Assessment will be conducted, led by NIST.

5. PERIOD OF PERFORMANCE

The period of performance is 12 months.

6. PLACE OF PERFORMANCE

Work shall be performed at Contractor’s facilities.

7. GOVERNMENT FURNISHED PROPERTY

All material provided by the Government in the performance of this requirement remains the property of the Government and shall be surrendered to the government upon completion or termination of this requirement. Likewise, all data and deliverables generated under this contract remain the property of the Government.

Government furnished property will be provided in an as condition and in a working condition.

This includes:

• A semantic refinement tool high-level requirement document.

• A relational data model and a detailed functional design along with a prototype software system architected to support a single tenant MSSRT. The provide prototype will support managing BIEs, code lists, business context and profile XML schema generation functionalities. It may or may not support the user extension functionality.

• OAGIS 10.1 core standard specification readily imported (from the original XML schema representation) into the Oracle relational database whose schema complies to the provided relational data model.

• A specification for profile XML schema representation.

• A detailed description of the list of OAGIS BOD refinement scenario, including descriptions of the refinement conditions and results.

• A list of target OAGIS manufacturing scenarios.

8. REPORTING REQUIREMENTS AND DELIVERABLES

The Contractor shall provide quarterly technical status reports to ensure work progress is consistent with this requirement and will lead to successful completion of all tasks.

All written technical reports shall include a detailed description of the status of each task as well as tasks planned for the next quarter. In addition, the contractor will make available to NIST all software as it becomes available.

All written technical and progress reports shall be submitted in MS Word.

Standards for Acceptance of Deliverables: The Contracting Officer Representative (COR) will provide comments on each deliverable within 21 calendars days from receipt of a given deliverable. The Contractor shall make any needed changes to the deliverables within 21 calendar days from receipt of electronic or written comments from the COR. The COR will provide written notification when deliverable is accepted.

9. PROGRAM MANAGEMENT REQUIREMENTS

The Contractor shall include program management requirements in his proposal.

10. INSPECTION AND ACCEPTANCE CRITERIA

The COR will evaluate all deliverables and provide written comments and acceptance of all deliverables. The software shall perform with respect to the NIST’s furnished semantic refinement scenarios as well as the multi-tenant usage scenario developed during the course of the contract.

The COR will periodically review the software generated by the Contractor to ensure that it meets the performance requirements set forth in this contract.

The authoritative version of the NIST data must be stored only on NIST authorized systems, and must follow the requirements given in NIST Directive 5701.00.

10.1 MSSRT

The following are acceptance criteria for the MSSRT deliverable tool:

• The tool shall work in a multi-tenant, web-based environment.

• The tool shall demonstrate the required functionalities (see the bulleted list in Section 2.1) including detailed descriptions of these functionalities as provided in the furnished functional design document (see Section 7).

• The tool shall demonstrate the required functionality on a version of the initially provided OAGIS BOD refinement scenario that will provide specific refinement conditions and profile BOD XML schema results. This scenario will be provided no later than the time of software acceptance.

• The tool shall demonstrate BIE and user extensions sharing within a community.

• The tools shall be based on a documented data model and a functional design that will support the multi-tenant usage scenario.

• The tool shall demonstrate o deployment on Oracle WebLogic application server;

o accessibility using Google Chrome browser; and o storage and retrieval of OAGIS model using a relational database.

• IT Security. Any cloud-based or external services shall have FedRAMP authorization, an Authorization to Operate (ATO) letter issued by a Federal Government agency as evidence that they have been assessed and authorized, or have passed an independent security audit (e.g., Statement on Standards for Attestation Engagements (SSAE), PCI Data Security Standard (PCI

DSS)).

o If using a Federal Government agency-issued ATO letter, that letter shall clearly state the impact rating level at which the Contractor has been assessed and authorized. Within five days of contract award, the Contractor shall provide to NIST, as a deliverable, evidence of the audit or instructions on how to obtain evidence of the above, if the Contractor has had any audits described above or other security.

o Post contract award, the Government will perform a review for a local ATO decision, required for go-live, and ongoing security assessments for continuous monitoring thereafter. The Government will determine the risk rating of identified vulnerabilities.

The Contractor shall respond to the Government with an action plan and schedule to mitigate security risks found within 10 business days of notification of security risks. The Government will notify the Contractor of whether or not the action plan and schedule are acceptable. The Contractor shall implement the action plan according to the agreed-upon schedule.

o Anticipated impact rating levels based on NIST use cases (by security objective) are Integrity = Low, Availability = Low, and Confidentiality = Low.

10.2 BP Models for BPCCS

The following are acceptance criteria for the BP models deliverable:

• Given an OAGIS scenario belongs to the set of manufacturing scenarios, when searching for BPMN representation of that scenario within deliverables, then appropriate BPMN models should be present.

• Given a manufacturing OAGIS scenario documentation is completed, when reviewing that documentation, then documentation should be complete with respect to the OAGIS scenario template.

• Given a business process metamodel and BPMN models for OAGIS manufacturing scenarios are defined, when reviewing BPMN models, then those models should contain only elements defined by business process metamodel.

• Given a business process metamodel and BPMN models for OAGIS manufacturing scenarios are defined, when reviewing business process metamodel, then metamodel should contain only elements used in BPMN models.

• Given a BPMN models for an OAGIS manufacturing scenario are defined, when reviewing detailed scenario documentation, then details encoded within textual scenario documentation (such as participants, events occurring in the workflow sequence, exception handling, etc.) should be represented within BPMN models using appropriate constructs.

• Given a BPMN models for an OAGIS manufacturing scenario are defined, when reviewing BPMN models, then every part of BPMN model should be based on some part of detailed scenario documentation.

• Given a BPMN models for an OAGIS manufacturing scenario are defined, when comparing BPMN model with public processes and corresponding BPMN model with private processes, then they should be consistent with each other.

• Given a set of applicable interaction patterns is identified and BPMN models for OAGIS manufacturing scenarios are defined, when reviewing BPMN models, then the interaction patterns should be used consistently across BPMN models.

• Given a BPMN model for an OAGIS manufacturing scenario, when the model is introspected for contextual information surrounding particular activity or message exchange, then the contextual information should be part of the BPMN model.

• Given a BPMN model for an OAGIS manufacturing scenario, when the model is introspected for actual message structures used in exchanges, then OAGIS BODs that are referenced from the BPMN models should be found.

• Given a BPMN model exported to BPMN 2.0 XML format, when file imported into a tool supporting the format, then the XML file should be successfully imported without any errors.

11. Risk Levels

The requirement has been deemed IT Low Risk.

PROVISIONS AND CLAUSES:

The following provisions and clauses apply to this acquisition and are hereby incorporated by reference. All FAR clauses may be viewed at http://farsite.hill.af.mil/.

Provisions

52.212-1 Instructions to Offerors - Commercial Items 52.212-3 Offeror Representations and Certifications-Commercial Items

Representation by Corporations Regarding an Unpaid Delinquent Tax Liability or a Felony Conviction Under Any Federal Law (Class Deviation) (March 2015)

(1) In accordance with Sections 744 and 745 of Division E, Title VII, of the Consolidated and Further Continuing Appropriations Act, 2015 (Pub. L. 113-235), none of the funds made available by the Consolidated and Further Continuing Appropriations Act, 2015 funding may be used to enter into a contract with any corporation that-

(a) Was convicted of a felony criminal violation under any Federal law within the preceding 24 months, where an awarding agency is aware of the conviction, unless the agency has considered suspension or debarment of the corporation and has made a determination that this further action is not necessary to protect the interests of the Government, or

(b) Has any unpaid Federal tax liability that has been assessed, for which all judicial and administrative remedies have been exhausted or have lapsed, and that is not being paid in a timely manner pursuant to an agreement with the authority responsible for collecting the tax liability, where the awarding agency is aware of the unpaid tax liability, unless the agency has considered suspension or debarment of the corporation and made a determination that this further action is not necessary to protect the interests of the Government.

(2) The Offeror represents that, as of the date of this offer -

(a) It is [ ] is not [ ] a corporation that was convicted of a felony criminal violation under a Federal law within the preceding 24 months.

(b) It is [ ] is not [ ] a corporation that has any unpaid Federal tax liability that has been assessed, for which all judicial and administrative remedies have been exhausted or have lapsed, and that is not being paid in a timely manner pursuant to an agreement with the authority responsible for collecting the tax liability.

(End of provision)

Certification by Offerors Regarding Federal Income Tax Filing and Federal Income Tax Violations. (Class Deviation) (March 2015)

(a) In accordance with Section 523 of Division B, Consolidated and Further Continuing Appropriations Act, 2015, (Pub. L. 113-235) none of the funds made available by the Act may be used to enter into a contract in an amount greater than $5,000,000 unless the prospective contractor certifies in writing to the U.S. Consolidated and Further Continuing that, to the best of its knowledge and belief, the contractor has filed all Federal tax returns required during the three years preceding the certification, has not been convicted of a criminal offense under the Internal Revenue Code of 1986, and has not, more than 90 days prior to certification, been notified of any unpaid Federal tax assessment for which the liability remains unsatisfied, unless the assessment is the subject of an installment agreement or offer in compromise that has been approved by the Internal Revenue Service and is not in default, or the assessment is the subject of a non-frivolous administrative or judicial proceeding.

(b) The offeror’s proposal shall include a signed written certification as follows – To the best of my knowledge and belief, ---(name of offeror)--- has filed the Federal tax returns required during the three years preceding this certification, has not been convicted of a criminal offense under the Internal Revenue Code of 1986, and has not, more than 90 days prior to certification, been notified of any unpaid Federal tax assessment for which the liability remains unsatisfied, unless the assessment is the subject of an installment agreement or offer in compromise that has been approved by the Internal Revenue Service and is not in default, or the assessment is the subject of a non-frivolous administrative or judicial proceeding.

Firm _____________________________________________ Signature _________________________________________ Name ____________________________________________ Title _____________________________________________ Date of execution __________________________________

(End of Provision)

52.203-98, Prohibition on Contracting with Entities that Require Certain Internal Confidentiality Agreements—Representation (DEVIATION 2015-02)

(a) In accordance with section 743 of Division E, Title VII, of the Consolidated and

Further Continuing Resolution Appropriations Act, 2015 (Pub. L. 113-235), Government agencies are not permitted to use funds appropriated (or otherwise made available) under that or any other Act for contracts with an entity that requires employees or subcontractors of such entity seeking to report fraud, waste, or abuse to sign internal confidentiality agreements or statements prohibiting or otherwise restricting such employees or subcontractors from lawfully reporting such waste, fraud, or abuse to a designated investigative or law enforcement representative of a Federal department or agency authorized to receive such information.

(b) The prohibition in paragraph (a) of this provision does not contravene requirements applicable to Standard Form 312, Form 4414, or any other form issued by a Federal department or agency governing the nondisclosure of classified information.

(c) Representation. By submission of its offer, the Offeror represents that it does not require employees or subcontractors of such entity seeking to report fraud, waste, or abuse to sign internal confidentiality agreements or statements prohibiting or otherwise restricting such employees or subcontractors from lawfully reporting such waste, fraud, or abuse to a designated investigative or law enforcement representative of a Federal department or agency authorized to receive such information.

(End of provision) Clauses

*52.212-4 Contract Terms and Conditions—Commercial Items 52.212-5 Contract Terms and Conditions Required to Implement Statutes or Executive Orders— Commercial Items (APR 2010)-- including subparagraphs:

52.203-6, Restrictions on Subcontractor Sales to the Government 52.204-10 Reporting Executive Compensation and First Tier Subcontract Awards 52.209-6 Protecting the Government’s Interest when subcontracting with Contractor’s Debarred, Suspended or proposed for Debarment 52.209-10 Prohibition on Contracting with Inverted Domestic Corporations 52.219-6, Notice of Total Small Business Set-Aside 52.219-8, Utilization of Small Business Concerns 52.219-13, Notice of Set-Aside of Orders 52.219-28, Post Award Small Business Program Representation 52.222-3, Convict Labor;

52.222-19, Child Labor – Cooperation with Authorities and Remedies;

52.222-21, Prohibition of Segregated Facilities;

52-222-26, Equal Opportunity;

52.222-35, Equal Opportunity for Special Disabled Veterans, Veterans of the Vietnam Era, and Other Eligible Veterans 52.222-36, Equal Opportunity for Workers with Disabilities;

52.222-37, Employment Reports on Veterans 52.223-18, Encouraging Contractor Policies to Ban Text Messaging While Driving 52.225-13, Restriction on Certain Foreign Purchases;

52.232-30, Installment Payments for Commercial Items 52.232-33 Payment by Electronic Funds Transfer- System for Award Management.

*1352.201-70 Contracting Officer’s Authority *1352.201-72 Contracting Officer’s Representative (COR) *1352.209-73 Compliance With The Laws *1352.209-74 Organizational Conflict of Interest *1352.237-71 Security Processing Requirements - Low Risk Contracts *1352.237-73 Foreign national visitor and guest access to departmental resources

(a) The contractor shall comply with the provisions of Department Administrative Order 207–12, Foreign National Visitor and Guest Access Program; Bureau of Industry and Security Export Administrative Regulations Part 734, and [insert operating unit counsel specific procedures]. The contractor shall provide the Government with notice of foreign nationals requiring access to any Department of Commerce facility or through a Department of Commerce IT system.

(b) The contractor shall identify each foreign national who requires access to any Departmental resources, and shall provide all requested information in writing to the Contracting Officer's Representative.

(c) The contractor shall include the substance of this clause, including this paragraph, in all subcontracts.

(End of clause)

52.203-99, Prohibition on Contracting with Entities that Require Certain Internal Confidentiality Agreements (DEVIATION 2015-02)

(a) The Contractor shall not require employees or subcontractors seeking to report fraud, waste, or abuse to sign or comply with internal confidentiality agreements or statements prohibiting or otherwise restricting such employees or subcontractors from lawfully reporting such waste, fraud, or abuse to a designated investigative or law enforcement representative of a Federal department or agency authorized to receive such information.

(b) The contractor shall notify employees that the prohibitions and restrictions of any internal confidentiality agreements covered by this clause are no longer in effect.

(c) The prohibition in paragraph (a) of this clause does not contravene requirements applicable to Standard Form 312, Form 4414, or any other form issued by a Federal department or agency governing the nondisclosure of classified information.

(d) In accordance with section 743 of Division E, Title VII, of the Consolidated and Further Continuing Resolution Appropriations Act, 2015 (Pub. L. 113-235), use of funds appropriated (or otherwise made available) under that or any other Act may be prohibited, if the Government determines that the Contractor is not in compliance with the provisions of this clause.

(2) The Government may seek any available remedies in the event the Contractor fails to comply with the provisions of this clause.

INSTRUCTIONS:

System for Award Management (SAM)

In accordance with FAR 52.204-7, the awardee must be registered in SAM (www.sam.gov) prior to award. Refusal to register shall forfeit award.

Required Information

The government will not consider any quotation without the information required by this solicitation.

Due Date for Quotations

Offerors shall submit their quotations so that NIST receives them not later than 12:00 p.m.

Eastern Time on Friday, August 19, 2016. FAX and hard-copy quotations shall not be accepted. E-mail quotations shall be accepted at robert.cowins@nist.gov. Offerors’ quotations shall not be deemed received by the Government until the quotation is entered into the e-mail address inbox set forth above. Late quotes will not be accepted.

Addendum to FAR 52.212-1, Quotation Preparation Instructions

1) Price Quotation: The pricing quotation shall be separate from the technical quotation. The vendor must provide a fully burdened hourly labor rate for each proposed labor category, a total number of estimated hours to be worked for each labor category, and a total firm fixed price for each labor category. The firm-fixed-Price for each labor category shall be calculated by multiplying the appropriate labor category fully burdened hourly rate(s) by the proposed number of hours to be worked under that labor category. The offeror shall propose a firm fixed price Payment Schedule for the resultant purchase order. It is anticipated that the proposed Payment Schedule if accepted by the Government will be incorporated into the resultant purchase order awarded.

2) Technical Quotation: The technical quotation shall address the following:

Technical Capability: The technical proposal shall address the vendor’s detailed technical approach for satisfying the SOW requirements. The technical approach shall address how the http://www.sam.gov/ mailto:robert.cowins@nist.gov vendor will (a) perform and manage individual tasks required by the SOW; and (b) ensure that Contractor services and deliverables comply with the requirements of the SOW

Experience: The offeror shall demonstrate the extent of the experience attained providing a similar service. The offeror shall provide a resume for each person proposed as key personnel, to include name, education, experience, and country of citizenship. If a candidate is not a US citizen, then the proper documentation, as required by CAR clause 1352.237-73, must be provided with the proposal.

Past Performance: The offeror shall provide past performance information regarding relevant contracts over the past five (5) years with Federal, state, or local governments, or commercial customers. If the offeror intends to subcontract with another firm(s) for part of this requirement, that firm’s past performance information shall also be provided. If the offeror has no relevant past performance, it may include a statement to that effect in its quotation. The government reserves the right to consider data obtained from sources other than those described by the offeror in its quotation. It is recommended that approximately 3-5 contracts be referenced.

The description of each contract/order described in this section shall not exceed one half page in length. For each contract/order, the offeror shall provide the following information:

1. Contract number;

2. Description and relevance to solicitation requirements including dollar value;

3. Period of Performance – indicate by month and year the state and completion (or “ongoing”) dates for the contract;

4. Reference Contact – If a non-Government contract, identify the name and address of the client with current telephone number and email address of a point of contact of the client responsible for the contract;

5. Contracting Office – If a Government contract (Federal or state), identify the Procuring Contracting Officer (PCO), Administrative Contracting Officer (ACO), and Contracting Officer’s Representative (COR), and their names, current telephone numbers and email addresses.

6. Problems Encountered – include information regarding information regarding any problems encountered on the contracts described above and corrective actions taken to resolve those problems.

Acceptance of Terms and Conditions: This is an open-market solicitation for equipment as defined herein. The Government intends to award a Purchase Order as a result of this solicitation that will include the clauses set forth herein. The quotation should include one of the following statements:

“The terms and conditions in the solicitation are acceptable to be included in the award document without modification, deletion, or addition.”

OR

“The terms and conditions in the solicitation are acceptable to be included in the award document with the exception, deletion, or addition of the following:

Offeror shall list exception(s) and rationale for the exception(s)

Note: This procurement is not being conducted under the GSA Federal Supply Schedule (FSS) program or another Government-Wide Area Contract (GWAC). If an offeror submits a quotation based upon an FSS or GWAC contract, the Government will accept the quoted price.

However, the terms and conditions stated herein will be included in any resultant Purchase Order, not the terms and conditions of the offeror’s FSS or GWAC contract, and the statement required above shall be included in the quotation.

QUOTATION EVALUATION:

Evaluation Factors

Award shall be made to the offeror whose quotation offers the best value to the Government price and other factors considered. The Government will evaluate quotations based on the following evaluation criteria: 1) Technical Capability 2) Experience, 3) Past Performance, and 4) Price. All non-price factors, individually and when combined, are significantly more important than price.

Technical Capability: Evaluation of technical capability will be based on the information provided in the proposal. NIST will evaluate whether the offeror has demonstrated that its proposed services meets or exceeds all minimum requirements. Proposals that do not demonstrate the proposed services meet all requirements will not be considered further for award. If an offeror does not indicate whether its proposed services meet a certain minimum requirement, NIST will determine that it does not. NIST will give preference to offerors who demonstrate that their proposed service exceeds NIST’s requirements.

Experience: NIST will evaluate the extent of the offeror’s experience providing a similar service. NIST will give preference to offerors who demonstrate they have experience delivering the same service they are proposing for the current requirement. The Government will evaluate the offeror’s minimum qualifications as specified under Section 4 A (Contractor Requirements).

The Government will evaluate the minimum qualifications of the proposed Key Personnel as required by Section 4 B (Contractor Requirements).

Past Performance: The Government will evaluate the Offeror's past performance information and, if appropriate, its proposed subcontractors' past performance to determine its relevance to the current requirement and the extent to which it demonstrates that the offeror has successfully completed relevant contracts in the past five years. In assessing the offeror's past performance information, NIST will evaluate, as appropriate, successful performance of contract requirements, quality and timeliness of delivery of goods and services, cost management, communications between contracting parties, proactive management and customer satisfaction..

Evaluation of this factor will be based on information contained in the technical portion of the quotation and information provided by references. The Government will evaluate past performance information by contacting appropriate references, including NIST references, if applicable. The Government may also consider other available information in evaluating the Offeror’s past performance. The Government will assign a neutral rating if the offeror has no relevant past performance information.

NOTE -- If an offeror does not have a history of relevant contract experience, or if past performance information is not available, the offeror will receive a neutral past performance rating; however, an offeror without a history of relevant experience may receive a lowered rating for the Experience Factor.

Price: The Government will evaluate price for reasonableness.

Past Performance, Experience, and Price shall not be evaluated on quotes that are determined technically unacceptable under the Technical Capability Evaluation factor.

1352.233-70 AGENCY PROTESTS (APR 2010)

(a) An agency protest may be filed with either: (1) the contracting officer, or (2) at a level above the contracting officer, with the appropriate agency Protest Decision Authority. See 64 Fed. Reg. 16,651 (April 6, 1999)

(b) Agency protests filed with the Contracting Officer shall be sent to the following address: NIST/ACQUISITION MANAGEMENT DIVISION

ATTN: YAHAYA, ABDUL-KUDUS , CONTRACTING OFFICER

100 Bureau Drive, MS 1640 Gaithersburg, MD 20899

(c) Agency protests filed with the agency Protest Decision Authority shall be sent to the following address: NIST/ACQUISITION MANAGEMENT DIVISION

ATTN: HEAD OF THE CONTRACTING OFFICE (HCO)

100 Bureau Drive, MS 1640

Gaithersburg, MD 20899

(d) A complete copy of all agency protests, including all attachments, shall be served upon the Contract Law Division of the Office of the General Counsel within one day of filing a protest with either the Contracting Officer or the Protest Decision Authority.

(e) Service upon the Contract Law Division shall be made as follows:

U.S. Department of Commerce Office of the General Counsel

Chief, Contract Law Division Room 5893 Herbert C. Hoover Building 14th Street and Constitution Avenue, N.W.

Washington, D.C. 20230.

FAX: (202) 482-5858

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

(a) A protest may be filed with either the Government Accountability Office (GAO) or the Court of Federal Claims unless an agency protest has been filed.

(b) A complete copy of all GAO or Court of Federal Claims protests, including all attachments, shall be served upon (i) the Contracting Officer, and (ii) the Contract Law Division of the Office of the General Counsel, within one day of filing a protest with either GAO or the Court of Federal Claims.

(c) Service upon the Contract Law Division shall be made as follows:

U.S. Department of Commerce Office of the General Counsel Chief, Contract Law Division Room 5893 Herbert C. Hoover Building 14th Street and Constitution Avenue, N.W.

Washington, D.C. 20230.

FAX: (202) 482-5858

All offerors shall provide a quotation for the following line items: