W912HZ-14-R-0022-0004.pdf

W912HZ-14-R-0022

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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

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

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

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

FAR (48 CFR) 53.243

This amendment is to post question and answ ers.

Attachment B is revised and replaced in this amendment.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 54

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

16C. DATE SIGNED

BY 03-Feb-2016

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

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

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W912HZ-14-R-0022

X 9B. DATED (SEE ITEM 11)

06-Jan-2016

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

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

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

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

CONTRACT ORDER NO. IN ITEM 10A.

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

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

D. OTHER (Specify type of modification and authority)

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

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

10A. MOD. OF CONTRACT/ORDER NO.

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

6. ISSUED BY

3. EFFECTIVE DATE

02-Feb-2016

CODE

ERDC CONTRACTING OFFICE

3909 HALLS FERRY ROAD

VICKSBURG MS 39180-6199

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been modified:

QUESTION AND ANSWERS

The following questions and answers are provided for informational purposes only:

Question 7: Is Section B required to be completed for the proposal or after award? If so, please provide instructions as to how to complete Section B.

Answer: No monetary amounts are to be entered by the vendor in Section B of Standard Form

33. The Government will complete Section B at time of award.

Question 8: Reference Section L.2.0. The solicitation states that the Government will entertain questions on the RFP up to 7 days prior to the proposal due date. Recommend all questions be posed no later than 14 days prior to proposal due date to afford the Government time to respond to questions and industry time to react and incorporate any necessary changes to their proposals. This will help the Government avoid deadline extension requests.

Answer: Please see revised Section L.2.0.

Question 9: Reference Section L.3.6.1, L.3.6.2, L.3.6.3. Are the Volume I proposal cover, table of contents, and tabs/dividers exempt from page count?

Answer: See revised chart in Section L 3.3.

Question 10: Reference Section L.3.6.3. An Introduction is required at Section L.3.6.3, but it does not appear as part of a page-limited Subfactor. Is the Introduction page-limited?

Should it be placed prior to Subfactor 1 or as part of Subfactor 1?

Answer: See revised chart in Section L 3.3.

Question 11: Reference Section L.3.6.5. Section L.3.6.5 states, “The proposal shall provide a comprehensive description of the offeror’s significant capabilities and relevant corporate experience performing projects similar to the PWS requirements.” Does this requirement include, or allow, subcontractor projects (with PPQs)?

Answer: Yes, subcontractor projects with PPQs are allowed.

Question 12: Reference Section L.3.6.5. States, “Relevant corporate experience is experience within the last five years that is of the same or similar scope and complexity to the work described in the Performance Work Statement, and is of the same or similar magnitude (i.e., performing services that, on an annual basis, are at least half the dollar value proposed by the Offeror to perform the Performance Work Statement’s requirements).” Considering requirements for Volume II are for only fixed-price and cost-plus rates, on what is the “dollar value proposed by the Offeror” based? Sample Task 0001?

Answer: The Government assumes the question is pertaining to Volume III instead of Volume II.

Please see Section F.3 for the maximum ordering limit.

Question 13: Reference Section L.3.7. States, “The offeror shall submit a Past Performance Questionnaire (PPQ) for every project identified as relevant corporate experience. The Past Performance proposal is not limited to only those projects identified as relevant corporate experience (emphasis added).” Considering all relevant experience is captured in Volume I, each of which requires a PPQ in Volume II, what other project types does the Government expect Offerors to provide? Are additional projects allowed to be added in the Past Performance volume? If projects are allowed to be added in the Past Performance Volume, are PPQs also required?

Answer: Volume II may consist of PPQs for projects that were NOT identified in Volume I corporate experience. A PPQ is required for each project submitted in Volume II.

Question 14: Reference Clause 52.215-1 Is the Volume I first page information sheet exempt from page count?

Answer: See revised chart in Section L 3.3.

Question 15: Reference Section M.2.1. States, “Proposals demonstrating a clear understanding of how to deliver services to meet the requirements of the PWS and demonstrate that proposed technical personnel possess the technical qualifications, experience, and capabilities to deliver the expert services called for in the PWS will be evaluated more favorably” (emphasis added). Section L does not require proposed technical personnel. Does the Government expect technical personnel to be proposed in its Technical and Management Approach? Or, does the Government expect technical personnel to be proposed as part of Key Personnel? Please clarify.

Answer: Please see revised Section M.2.1.1.

Question 16: Reference Section L.3.6.6 and Section M.2.1. Does the Government have a specific transition timeline in mind or are offerors free to propose one of their choosing?

Answer: Offerors are free to propose one of their choosing.

Question 17: Reference Section L.3.6.6 and Section M.2.1. Does the current contract contain language that directs the incumbent to provide assistance to a successor contractor?

Answer: No.

Question 18: Reference Section L.3.6.6 and Section M.2.1. Does the Government intend for the incumbent and successor contracts to overlap during transition?

Answer: No.

Question 19: Reference Section L.3.6.6.6 and Section L.3.8. The RFP asks for a Transition / phase in plan to be included as part of the Technical proposal; however there is no requirement to price transition separately. Does the government anticipate transition cost associated with this contract award and if so, will these costs be recoverable as direct cost to this contract?

Answer: No.

Question 20: Reference the PWS 2.3.2 and Section L.3.6.4.3. Please clarify your intent vis-à-vis the Program Manager. PWS language in section 2.3.2 suggests a part time PM with other assignments who, as an additional duty, will administer the contract. However, Section L 3.6.4.3 identifies the PM as a key person. Is your intent that he PM be a key technical contributor, charging direct to the contract except when performing program management duties? This seems to conflict with FAR 31.202 instructions regarding direct and indirect charges as any PM work performed would be solely tied to this contract.

Recommend that you drop the language in 2.3.2 and allow offerors to propose the management approach, and personnel, they choose.

Answer: Please see revised PWS 2.3.2.

Question 21: Reference attachments A and E. Are any of the labor categories on this contract subject to the Service Contract Act?

Answer: No.

Question 22: Reference PWS, Section C.1.3. What percentage of the task orders will be at the vendor’s location? Is the vendor required to have a corporate location at each of the Government locations: (Vicksburg, MS; Alexandria, VA; Champaign, IL and Hanover, N.H.?

Answer: The percentage of task orders that will be performed at the vendor’s location is unknown. The vendor is not required to have a corporate location at each of the Governments locations.

Question 23: Reference PWS, Section C.2.3.3. What services is the Offeror to provide in the sentence: “The contractor shall provide for employees during designated Government non-work days or other periods where Government offices are closed due to weather or security conditions.”?

Answer: Performance/Delivery schedules shall be met in accordance with each task/delivery order issued.

Question 24: Reference PWS, Section C.2.5. Will the Government provide the Labor Categories document mentioned in this paragraph? If not, will the Offeror be allowed to define the requirements?

Answer: Please see Attachment A for the labor categories and descriptions.

Question 25: Reference PWS, Section C.4.2. What is the expected transition time period?

Answer: The vendor must submit a transition plan.

Question 26: Reference PWS, Section C.4.4. There are no directives referenced under paragraph C.3.0 or in paragraph C.4.4. Will the Government publish a list of mandatory documents?

Answer: Please see revised PWS.

Question 27: Reference PWS, Section C.6. Does “Related Documents” refer to the Performance Requirements Summary?

Answer: No. Please see revised PWS.

Question 28: Reference PWS PRS. The entries under Incentive/Remedy are ratings rather than incentives to exceed the AQL or remedies if the AQL is missed. Will the Government change the Incentive/Remedy column title or content?

Answer: Please see revised PWS.

Question 29: Reference PWS PRS, Section 3.1.1. Does the rating for Exceptional mean “100 % on time and 25% earlier than scheduled.”? If so, request the Government modify the rating.

Answer: Please see revised PWS.

Question 30: Reference Attachment B, Sample Task Order. Is the place of performance Government site or Contractor site?

Answer: Please see revised Attachment B.

Question 31: Reference Section M 3.7. How is the Government defining “last five years”:

either from the date of the solicitation release or date of the RFP due date?

Answer: There is not a Section M.3.7. The Government is assuming you are referring to Section L.3.7. The last five years shall be from the solicitation release date.

Question 32: What is the total level of effort, in terms of FTE count, which the incumbent contractor is currently staffing the ERDC?

Answer: Previous awards are performance based, firm fixed price task orders with specified deliverables. Firm fixed price task orders do not specify a specific type or number of personnel/FTE.

Question 33: How many Task Orders does the Government anticipate to be awarded at the IDIQ level over the lifecycle of the contract?

Answer: Unknown.

Question 34: Reference Section L. Which positions does the Government consider Key Personnel?

Answer: The offeror shall identify personnel whom they consider key.

Question 35: Reference Section L.3.3. Does the Table of Contents count in the Volume I - Technical Proposal and Volume II Past Performance Page Limitation?

Answer: See revised chart in Section L 3.3.

Question 36: Reference Section 2.3.3 of the solicitation. “The contractor shall maintain the currency of their employees by providing initial and refresher training as required to meet the PWS requirements.” Will this be considered a reimbursable cost to the Offeror?

Answer: No.

Question 37: Reference Section L.3.6.5. In Section L, it states that “relevant corporate experience is experience within the last five years that is of the same or similar scope and complexity to the work described in the Performance Work Statement…” But in Section M, page 86, it states that the Government will consider the combined Offeror’s and proposed subcontractor’s experience and performance …during the last five years”.

Please clarify.

Answer: Please see section L.3.6.5 for Volume I and Section M.2.2 for Volume II.

Question 38: Reference Section L.3.1. Does the Government want 1 CD containing all proposal files, or 1 CD per proposal volume for a total of 3 CDs?

Answer: One CD.

Question 39: Reference Section L.3.3. Do the page limitations include table of contents, covers, dividers, glossary, compliance matrix, and list of exhibits?

Answer: See revised chart in Section L 3.3.

Question 40: May we hand-deliver our proposal to the address in paragraph 1.1?

Answer: Yes. Refer to FAR clause 52.215-1 INSTRUCTIONS TO OFFERORS-- COMPETITIVE ACQUISITION for information concerning late proposals. Offerors are responsible for submitting proposals, and any modifications, or revisions, so as to reach the Government office (ERDC Contracting Office) designated in the solicitation by the time specified in the solicitation.

Question 41: Is there a minimum and/or maximum number of Past Performance contract references required?

Answer: No.

Question 42: I just came across the above referenced project you are running and am curious if there would be any benefit to the program to obtain parcel property data and associated attributes. This data provides national coverage of the geospatial dataset with financial, structural, and ownership for property parcels. Although this data was not specifically requested in the RFP, I thought it would be prudent to ask if this could be a dataset of interest for the program and if that’s the case to see if you could suggest a way to work with the agency on this project. We are a small commercial business and new to working with the government, but are definitely not a SDVOSB firm.

Answer: This is not applicable to this project.

Question 43: Reference section L, 3.6.7. Can the customer provide more specific requirements of the task/deliverable product in order to more accurately determine labor categories and hours?

Answer: Refer to Attachment B – Sample PWS.

Question 44: No format or specific requirements for the response to the sample task order have been provided. Please provide specific requirements (e.g. management plan, technical approach, staffing plan, etc.). Can the USG provide more details?

Answer: Please see section L paragraph 3.0, specifically section L paragraph 3.6.7.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

PERFORMANCE WORK STATEMENT

Performance Work Statement (PWS) ITL Information Technology Laboratory

Research and Development (R&D) Service Requirements

02/27/2015 Version 8.0

Vision Statement

1 Introduction

1.1 Mission

1.3 Scope

2 General Requirements

2.1 Non-Personal Services

2.2 Business Relations

2.3 Contract Administration and Management

2.3.1 Contract Management

2.3.2 Contract Administration

2.3.3 Personnel Administration

2.4 Subcontract Management

2.5 Contractor Personnel, Disciplines, and Specialties

2.6 Location and Hours of Work

2.7 Travel

3 Performance Requirements

3.1 Scientific Software and Engineering Application Research and Development

3.2 Sensors, Measurement and Instrumentation Research and Development

3.3 Geospatial Analysis Research and Development

3.4 Computer Aided Design/Building Information Modeling Research and Development ... 20

3.5 Data Analysis, Integration and Assessment Research and Development

3.6 Computational Analysis Research and Development

3.7 The Contractor shall comply with all ERDC security and safety requirement(s) outline in Section 4.1 of this PWS

4 Special Requirements

4.1 Security and Safety

4.2 Transition

4.3 Government Furnished Materials

4.4 Quality

4.4.1 Quality Control

4.4.2 Quality Assurance Surveillance Plan (QASP)

5 Deliverables

Vision Statement

1 Introduction

1.1 Mission

1.3 Scope

2 General Requirements

2.1 Non-Personal Services

2.2 Business Relations

2.3 Contract Administration and Management

2.3.1 Contract Management

2.3.2 Contract Administration

2.3.3 Personnel Administration

2.4 Subcontract Management

2.5 Contractor Personnel, Disciplines, and Specialties

2.6 Location and Hours of Work

2.7 Travel

3 Performance Requirements

3.1 Scientific Software and Engineering Application Research and Development

3.2 Sensors, Measurement and Instrumentation Research and Development

3.3 Geospatial Analysis Research and Development

3.4 Computer Aided Design/Building Information Modeling Research and Development ... 17

3.5 Data Analysis, Integration and Assessment Research and Development

3.6 Computational Analysis Research and Development

3.7 The Contractor shall comply with all ERDC security and safety requirement(s) outline in Section 4.1 of this PWS

4 Special Requirements

4.1 Security and Safety

4.2 Transition

4.3 Government Furnished Materials

4.4 Applicable Directives

4.5 Quality

4.5.1 Quality Control

4.5.2 Quality Assurance Surveillance Plan (QASP)

5 Deliverables

6 Related Documents

Performance Work Statement (PWS) ITL Information Technology Laboratory Research and Development (R&D) Service Requirements

Vision Statement

To build state of the art information technology solutions to support our customers.

1 Introduction The U. S. Army Corps of Engineers (USACE) Engineer Research and Development Center (ERDC) has responsibility for investigating, developing and maintaining the nation's water and related environmental resources; constructing and operating projects for navigation, flood control, major drainage, shore and beach restoration and protection, related hydro power development, water supply, water quality control, fish and wildlife conservation and enhancement, and outdoor recreation; responding to emergency relief activities directed by other federal agencies; and administering laws for the protection and preservation of navigable waters, emergency flood control and shore protection.

1.1 Mission

The ERDC Information Technology Laboratory (ITL) provides expertise in the science of information, the practice of information processing and the engineering of information systems to produce enabling technologies for the Corps of Engineers, U.S. Army, Department of Defense (DOD) and their customers.

The ITL conducts research and development in Informatics and Computational Science and Engineering with particular emphasis on providing high-performance computing for scientific and engineering discovery; data acquisition, analysis, and management; geospatial analysis and informatics; software engineering and evaluation; automated information systems; building information modeling.

For more information about the Information Technology Laboratory visit:

http://www.erdc.usace.army.mil/Locations/InformationTechnologyLaboratory.aspx

1.3 Scope

The ERDC ITL requires professional services for its research and development mission-critical activities.

The contractor shall provide all personnel, supervision, and services necessary to provide services for research and development (R&D) and related activities for the ERDC ITL as defined herein and in task order Performance Work Statements (PWS). This will be an indefinite delivery indefinite quantity (IDIQ) contract. The scope is defined as general requirements as outlined below in terms of areas of research and development responsibility or operational mission. Specific requirements of each customer will be detailed in individual task orders issued throughout the term of the contract.

The contractor shall perform R&D services related to the following areas:

Computer-aided Design/Building information Modeling Geospatial Analysis Web Development Application Development Data Standards and Integration Scientific Software and Engineering Application Research and Development Electronic System Research and Development Geospatial Analysis Research and Development Computer Engineering Research and Development Database Development and Administration Technical Documentation Scientific Application Research and Development

Sensors, Measurement and Instrumentation Research and Development Instrumentation research and development Data Collection and Analysis Research and Development Instrument Calibration Research and Development Application and Web Development Data Analysis, Integration and Assessment Electronic System Development Database Creation and Administration Geospatial Analysis Computational Analysis Numerical Analysis Research and Development Computational Application Research and Development Probability Analysis Research Model Simulations The default location for performance of task orders is the vendors location. Primary government sites of performance, if required, will include Vicksburg, MS, Alexandria, VA, Champaign, IL, and Hanover, NH.

2 General Requirements

2.1 Non-Personal Services

The Government shall neither supervise contractor employees nor control the method by which the contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees. It shall be the responsibility of the contractor to manage its employees and to guard against any actions that are of the nature of personal services, or give the perception of personal services. If the contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the contractor's responsibility to notify the Procuring Contracting Officer (PCO) immediately.

2.2 Business Relations

The contractor shall successfully integrate and coordinate all activity needed to execute the requirement.

The contractor shall manage the timeliness, completeness, and quality of problem identification. The contractor shall provide corrective action plans, proposal submittals, timely identification of issues, and effective management of subcontractors. The contractor shall seek to ensure customer satisfaction and professional and ethical behavior of all contractor personnel.

2.3 Contract Administration and Management

The following subsections specify requirements for contract, management, and personnel administration.

2.3.1 Contract Management

The contractor shall establish clear organizational lines of authority and responsibility to ensure effective management of the resources assigned to the requirement. When operating onsite, the contractor shall maintain continuity between ongoing activities at Vicksburg, MS, Alexandria, VA, Champaign, IL, and Hanover, NH and the contractor's corporate offices.

2.3.2 Contract Administration

The contractor shall establish processes and assign appropriate resources to effectively administer the requirement. The contractor shall respond to Government requests for contractual actions in a timely fashion. The contractor shall have a single point of contact between the Government and Contractor personnel assigned to service contracts or task orders. The contractor shall assign work to its personnel.

The contractor shall maintain proper and accurate time keeping records of personnel.

The contractor, at no additional cost to the government, shall provide a Contractor Program Manager who serves as the contract manager along with other duties and who shall be responsible for overall contract performance. The name of this person shall be designated in writing to the contracting officer's representative (COR). The contractor shall be responsible for all expenses associated with task management. The Contractors Program Manager will be available for meetings at the Vicksburg, MS ERDC site given a 48 hour notice. Contract administration functions shall not be billed directly. The contractor may also designate task/project leaders to manage individual tasks.

2.3.3 Personnel Administration

The contractor employees working on this contract shall be able to perform, in their field, at a high level of performance at the commencement of the task. Meaning that contractor employees must have the education, training, certifications and experience to perform the duties required, IAW Army Regulations and Programs. All contractor personnel shall be able to read, write, speak, and understand English, shall possess good written and verbal communications skills, and shall have sufficient knowledge of proper English grammar, spelling, capitalization, and punctuation rules to identify errors and make corrections.

The contractor shall provide sufficient management of personnel as required. The contractor shall provide for employees during designated Government non-work days or other periods where Government offices are closed due to weather or security conditions. The contractor shall maintain the currency of their employees by providing initial and refresher training as required to meet the PWS requirements. The contractor shall make necessary travel arrangements for employees. The contractor shall provide necessary infrastructure for services performed at the contractor's site(s). The contractor shall provide administrative support to employees in a timely fashion (time keeping, leave processing, pay, emergency needs).

2.4 Subcontract Management

The contractor shall be responsible for any subcontract management necessary to integrate work performed on this requirement and shall be responsible and accountable for subcontractor performance on this requirement. The prime contractor will manage work distribution to ensure there are no Organizational Conflict of Interest (OCI) considerations. Contractors may add subcontractors to their team after notification to the Procuring Contracting Officer (PCO) or Contracting Officer Representative (COR).

Cross teaming may or may not be permitted.

2.5 Contractor Personnel, Disciplines, and Specialties

The contractor shall accomplish the assigned work by employing and utilizing qualified personnel with appropriate combinations of education, training, and experience. The contractor shall match personnel skills to the work or task with a minimum of under/over employment of resources. The contractor shall ensure the labor categories as defined in the Labor Categories document utilized in the performance of each Task Order issued hereunder will be the minimum necessary to accomplish the task. The Contractor shall provide the necessary resources and infrastructure to manage, perform, and administer the contract.

Contractor Employee Conduct The contractors employees shall observe and comply with all applicable departmental and agency regulations, policies, and procedures (e.g., fire, safety, sanitation, environmental protection, security, etc.). The contractor shall ensure that all contractor employees represent a professional appearance at all times, and that their conduct does not reflect discredit on the United States Government.

When contractor employees are working on Government facilities or participating at Government meetings, they shall wear identification badges distinguishing themselves as such. The badges at a minimum must have the employee name and word "contractor displayed. Ideally, the company name will appear on the badge. Additionally, not withstanding any other provisions in the PWS, the contractor shall identify themselves as a contractor in meetings, telephone conversations, all written communications and work situations so that their actions cannot be construed as acts of a Government official. The contractor shall take no actions that bind the government to a final decision or results in the exercise of governmental discretion.

Removal of Contractor Employees for Misconduct or Security Reasons The Government may, at its sole discretion, direct the contractor to remove any contractor employee from Government facilities for misconduct or security reasons. Such removal does not relieve the contractor of the responsibility to provide sufficient qualified personnel for adequate and timely service. The Contracting Officer will provide the contractor with an immediate rationale for removal of contractor employee.

Conflict of Interest. Neither the contractor nor its on-site employees shall utilize their knowledge of access to information, sensitive or otherwise, for individual or company gain.

2.6 Location and Hours of Work

The headquarters site of the U.S. Army Corps of Engineers, ERDC is 3909 Halls Ferry Road, Vicksburg, MS 39180-6199. ERDC satellite laboratory sites are located in Alexandria, VA, Champaign, IL, Hanover, NH, and other Government facilities (mainly in the continental United States).

Core Working Hours. Government core working hours are from 0800 1645 local time Monday through Friday except US Federal Holidays. Government workers typically work eight (8) hours per day, 40 hours per week.

Government Facility Closure. In case of government facility closure as directed by the government, contractor employees shall be excused from work at no cost to the government.

2.7 Travel

Travel to other government facilities or other contractor facilities may be required. All travel requirements (including plans, agenda, itinerary, or dates) shall be pre-approved by the government (subject to local policy procedures), and is on a strictly cost reimbursable basis. Costs for travel shall be billed in accordance with the regulatory implementation of Public Law 99-234 and FAR 31.205-46 Travel Costs (subject to local policy & procedures; may reference FAR).

3 Performance Requirements The following section specifies the typical Performance Objectives and Performance Elements for the base contract.

3.1 Scientific Software and Engineering Application Research and Development The following sub-tasks will require knowledge and expertise in the research and development of algorithms for scientific data analysis programming, data mining, data retrieval, fusion, and dissemination, scientific mission proposal development, and support for large- and small-scale software system configuration, sizing, and development methodologies utilizing recognized techniques and scientific data format standards is also required. Functional requirements for the following sub-tasks will be defined within the task order.

Performance Standards

a) Standard (STD): Deliverables are made in accordance with schedule Acceptable Quality Level (AQL): 100% Compliant with schedule Deliverables A013 Status report

3.1.1 The Contractor shall perform application development for software engineering research.

This will require knowledge and expertise in designing and programming high complex scientific software applications. Requires extensive knowledge in programming languages such as, but not limited to, C++, Python, FORTRAN, C-Sharp, or Microsoft Visual Basic. Scientific parallel programming knowledge is required. Functional requirements for the applications will be defined within the task order.

Performance Standards

a) STD: Deliverables are made in accordance with schedule Deliverables A003 technical report A015 Software source code

3.1.1.1 The Contractor shall design and document algorithms for software applications.

Algorithms shall be designed using current state-of-the-art methods. This includes defining the problem the algorithm solves, model used to develop the algorithms, any specifications, process of checking for correctness, analysis and procedures used, process of implementing the algorithm, and program testing.

Algorithms shall be documented sufficiently to explain the algorithms.

Performance Standards

a) STD: Complete

b) STD: Accurate Deliverables A013 Status report A017 Documented algorithm

3.1.1.2 The Contractor shall write and document software code for software applications.

Code shall be developed in languages specified by the government at the time of awarding of task orders.

Common programming languages to be used may include, but not limited to, JAVA, C++, FORTRAN, Python, or Microsoft Visual Basic or C# using Microsoft Visual Studio as the development platform. The code shall contain sufficient comments to allow future understanding of the intended functionality of each segment of the code.

Performance Standards

a) STD: Accurate

b) STD: Executable

c) STD: Meets technical specifications

d) STD: Compliant with applicable standards Deliverables A013 Status report A015 Software source code

3.1.1.3 The Contractor shall test software code for proper functionality of software applications requirements.

Software application testing requirements will be defined in the task order. The contractor shall be capable of testing any software developed against the DoD Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIGs). The STIGs may be used to define technical requirements necessary for the resolution of vulnerabilities to a malicious computer attack of the software application. Additional testing requirements will be defined at the award of the task order.

Performance Standards

a) STD: Executable

b) STD: Identifies and corrects deficiencies

c) STD: Distributable Deliverables A013 Status report A015 Software source code

3.1.1.4 The Contractor shall debug software code for software applications.

The code may be debugged using the debugging tools in Microsoft Visual Studio or other currently acceptable debugging methods.

a) STD: Identifies and corrects deficiencies Deliverables A015 Software source code A016 Debug report

3.1.2 The Contractor shall perform database administration for projects.

Requires knowledge of database administration for Microsoft SQL Server and Oracle databases.

Knowledge of Microsoft Access database development and customization also required.

Performance Standards

a) STD: Deliverables are made in accordance with schedule Deliverables A003 technical report A009 Database

3.1.3 The Contractor shall consolidate and prepare system documentation for projects.

Documentation related to the architecture design of a system and functional capability of the software comprised within the system.

Performance Standards

a) STD: Deliverables are made in accordance with schedule Deliverables A003 technical report

3.1.4 The Contractor shall proof read, format, and edit technical documentation for software engineering research projects.

Writes a variety of technical reports, briefings, and material documenting the design and functional capability of software engineering applications developed.

Performance Standards

a) STD: Accurate AQL: 100% compliant with ERDC technical report preparation guidance Deliverables A003 technical report

3.2 Sensors, Measurement and Instrumentation Research and Development These tasks involve utilizing knowledge and expertise in the research and development of the integration of sensor technologies, electronic and electro-mechanical components and systems. Instrumentation configuration, data collection and measurement methodology expertise in the areas of structural monitoring, and physical phenomenology measurement is also required.

Performance Standards

a) STD: Deliverables are made in accordance with schedule

b) STD: Meets security safeguards

c) STD: No more than 2 validated complaints per month Deliverables A013 Status report

3.2.1 The Contractor shall perform numerical or computational modeling for sensors, measurement, and instrumentation research.

The research may involve developing software code to construct mathematical models using high performance computers to integrate multiple components, (i.e. Sensors, instrumentation, and computer hardware) to solve complex scientific problems. Performing computer simulation and numerical analysis will be required.

AQL: 100% Compliant with schedule Deliverables A003 technical report A011 Numerical Model A015 Software source code

3.2.2 The Contractor shall perform research and development of information web portals for data analysis and integration projects.

The research and development may involve the analysis of data collected using complex sensors and instrumentation.

Performance Standards

a) STD: Complete

AQL: 100%

b) STD: Deliverables are made in accordance with schedule AQL: 100% Compliant with schedule Deliverables A003 technical report A004 web based application A015 Software source code

3.2.3 The Contractor shall perform software engineering research for sensors, measurement, and instrumentation projects.

Code shall be developed in languages specified by the government at the time of award of task orders.

Common programming languages to be used may include, but not limited to, JAVA, C++, FORTRAN, or Microsoft Visual Basic or C# using Microsoft Visual Studio as the development platform. The code shall contain sufficient comments to allow future understanding of the intended functionality of each segment of the code.

Performance Standards

a) STD: Deliverables are made in accordance with schedule AQL: 100% Compliant with schedule Deliverables A003 technical report A010 Software Applications A015 Software source code

3.3 Geospatial Analysis Research and Development

The following sub-tasks outline services required for Geospatial Analysis Research and Development.

3.3.1 The Contractor shall conduct geospatial analysis research for the research and development of enterprise-wide server-based mapping solution projects.

This task may involve using tools such as Google Earth Fusion, Google Earth Enterprise Server, or Google Earth Enterprise Client applications. Knowledge of Keyhole Markup Language is required.

Performance Standards

a) STD: Compliant with applicable standards AQL: Level of accuracy consistent with source data Deliverables A003 technical report A005 Digital Maps A006 Map Metadata A012 Geospatial data

3.3.2 The Contractor shall develop georelational vector data models for research projects.

The georelational vector data models will be developed such that they store spatial and attribute data separately in a split systems.

Performance Standards

a) STD: Compliant with applicable standards AQL: Level of accuracy consistent with source data Deliverables A012 Geospatial data A013 Status report A018 Data model

3.3.3 The Contractor shall perform raster data analysis of mapping data for research projects.

Raster data analysis may involve the manipulation of mapping data using geospatial procedures such as performing masking of data, reclassification of raster data sets, statistical analysis of raster data, or extraction of data from raster data sets.

Performance Standards

a) STD: Media must remain in customers format.

AQL: Level of accuracy consistent with source data Deliverables A005 Digital Maps A009 Database A012 Geospatial data

3.3.4 The Contractor shall perform vector data analysis of mapping data for research projects.

Vector data analysis may involve the manipulation of mapping data using geospatial procedures such as performing buffering, creating mapping overlays, or pattern analysis.

Performance Standards

a) STD: Accurate AQL: Level of accuracy consistent with source data

b) STD: Complete AQL: Final deliverable completed in accordance with task order requirements.

Deliverables A005 Digital Maps A009 Database A012 Geospatial data

3.3.5 The Contractor shall compile, maintain, and update 2D and 3D geospatial data assets for data inventory.

This will require the contractor to maintain a collection of geospatial data, which includes raster, vector, imagery, and geospatial databases.

Performance Standards

a) STD: Timely AQL: 100% Compliant with schedule Deliverables A003 technical report A005 Digital Maps A006 Map Metadata A009 Database

A018 Data model

3.3.6 The Contractor shall collect mapping data for data analysis and integration research projects.

Performance Standards

a) STD: Accurate AQL: Level of accuracy consistent with source data Deliverables A003 technical report A006 Map Metadata

3.4 Computer Aided Design/Building Information Modeling Research and Development These tasks will require knowledge and expertise in the research and development of applications that integrate CAD, BIM, Computer Aided Facility Management (CAFM) and geospatial systems.

Performance Standards

a) STD: Deliverables are made in accordance with schedule AQL: 100% Compliant with schedule Deliverables A013 Status report

3.4.1 The Contractor shall perform research and development for web-based applications for projects.

Code shall be developed in languages specified by the government at the time of awarding of task orders.

Common programming languages to be used may include, but not limited to, JAVA, Microsoft Visual Basic .NET or C# using Microsoft Visual Studio as the development platform. The code shall contain sufficient comments to allow future understanding of the intended functionality of each segment of the code.

Performance Standards

a) STD: Compliant with applicable standards

AQL: 100%

Deliverables A004 web based application A013 Status report A015 Software source code

3.4.2 The Contractor shall perform research and development of CAD/BIM applications for the work units.

Customized applications will be developed to enhance the workflow of performing engineering design using computer aided design and building information modeling software applications. Code shall be developed in languages specified by the government at the time of awarding of task orders. Common programming languages to be used may include C++, Microsoft Visual Basic or C# using Microsoft Visual Studio as the development platform. The code shall contain sufficient comments to allow future understanding of the intended functionality of each segment of the code Performance Standards

a) STD: AEC CAD Standard AQL: Compliant Deliverables A003 technical report A007 CAD/BIM Application A013 Status report

3.4.3 The Contractor shall manage digital library of data and perform data backup for local area networks.

Manage data backup includes scheduling, setup, configuration, install, labeling of media, and written documentation of digital library of data being maintained.

Performance Standards

a) STD: Complete

AQL: 100%

b) STD: Compliant with applicable industry standards

c) STD: Meets Schedules in accordance with service level agreement.

d) STD: Media must remain in customers format.

Deliverables A001 Dashboard Report A013 Status report

3.4.4 The Contractor shall research, develop, and design CAD/BIM systems for deployment on local area network.

This will involve development and administration of enterprise project administration applications which will integrate with computer aided design (CAD) and building information modeling (BIM) automated systems on local area networks. Autodesk and Bentley Systems are the typical CAD and BIM software products that will be used on the local area networks.

Performance Standards

a) STD: Plan can be implemented with minimum impact to system users

b) STD: Recommended solutions and procedures are implementable

c) STD: Utilizes best scientific practices and commercial data

d) STD: Deliverables are made in accordance with schedule AQL: 100% Compliant with schedule Deliverables

3.5 Data Analysis, Integration and Assessment Research and Development The following sub-tasks will require knowledge and expertise in the research and development focused on data display, data analysis, data visualization, data archiving, mass storage, hardware-software integration, knowledge management, search analytics, and mobile computing.

Performance Standards

a) STD: Deliverables are made in accordance with schedule AQL: 100% Compliant with schedule Deliverables A013 Status report

3.5.1 The Contractor shall perform research and development electronic components for complex systems.

The research involved in this task will include the design, programming, and integration of electronic components necessary to perform acquisition, processing or transmission of digital data. Specifications of the electronic components and the design, programming and integration requirements will be detailed in the task order.

Performance Standards

a) STD: Compliant with applicable standards

AQL: 100%

Deliverables A008 Electronic systems

3.5.2 The Contractor shall perform database administration for systems deployed on local area network.

Typical databases requiring administration include, but not limited to, Microsoft SQL Server and Oracle.

Performance Standards

a) STD: Deliverables are made in accordance with schedule Deliverables

A009 Database

3.6 Computational Analysis Research and Development

The following sub-tasks will require technical knowledge in the areas of numerical modeling research and development that will refine, validate, compare, and apply advanced computational methods to develop algorithms to perform simulations for modeling real world phenomena.

Performance Standards

a) STD: Deliverables are made in accordance with schedule AQL: 100% Compliant with schedule Deliverables A013 Status report

3.6.1 The Contractor shall develop computational software applications for work units.

Code shall be developed in languages specified by the government at the time of award of task orders.

Common programming languages to be used may include, but not limited to, C++, FORTRAN, or Microsoft Visual Basic or C# using Microsoft Visual Studio as the development platform. The code shall contain sufficient comments to allow future understanding of the intended functionality of each segment of the code. The specifications for the application design will be defined within the task order.

Performance Standards

a) STD: Applicable Industry Software Standards AQL: Compliant Deliverables A010 Software Applications A013 Status report A015 Software source code

3.6.1.1 The Contractor shall design and document algorithms for software applications.

Algorithms shall be designed using current state-of-the-art methods. This includes defining the problem the algorithm solves, model used to develop the algorithms, any specifications, process of checking for correctness, analysis and procedures used, process of implementing the algorithm, and program testing.

Algorithms shall be documented sufficiently to explain the algorithms.

Performance Standards

a) STD: Complete

b) STD: Accurate Deliverables A013 Status report A017 Documented algorithm

3.6.1.2 The Contractor shall write and document software code for software applications.

Code shall be developed in languages specified by the government at the time of award of task orders.

Common programming languages to be used may include JAVA, C++, FORTRAN, or Microsoft Visual Basic or C# using Microsoft Visual Studio as the development platform. The code shall contain sufficient comments to allow future understanding of the intended functionality of each segment of the code.

Performance Standards

a) STD: Accurate

b) STD: Executable

c) STD: Meets technical specifications

d) STD: Compliant with applicable standards Deliverables A013 Status report A015 Software source code

3.6.1.3 The Contractor shall test software code for proper functionality of software applications.

Software application testing requirements will be defined in the task order. The contractor shall be capable of testing any software developed against the DoD Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIGs). The STIGs may be used to define technical requirements necessary for the resolution of vulnerabilities to a malicious computer attack of the software application. Additional testing requirements will be defined at the awarding of the task order.

Performance Standards

a) STD: Executable

b) STD: Identifies and corrects deficiencies

c) STD: Distributable Deliverables A013 Status report A015 Software source code

3.6.1.4 The Contractor shall debug software code for software applications.

The code may be debugged using the debugging tools in Microsoft Visual Studio or other currently acceptable debugging methods.

Performance Standards

a) STD: Identifies and corrects deficiencies Deliverables A015 Software source code A016 Debug report

3.6.2 The Contractor shall perform research and conduct computational analysis for work units.

The research may involve constructing mathematical models and performing quantitative analysis techniques using high performance computers to solve complex scientific problems. Performing computer simulation and numerical analysis will be required.

Performance Standards

a) STD: Deliverables are made in accordance with schedule AQL: 100% Compliant with schedule Deliverables A003 technical report A011 Numerical Model

3.7 The Contractor shall comply with all ERDC security and safety requirement(s) outline in Section 4.1 of this PWS.

See Section 4.1 of this PWS for Security and Safety requirements of this PWS.

AQL: 100% Compliant with schedule Deliverables A019 AT Level 1 Awareness Training Certificate A020 iWATCH, Corps Watch, or See Something training certificate

4 Special Requirements This section describes the special requirements for this effort. The following sub-sections provide details of various considerations on this effort.

4.1 Security and Safety

4.1.1 All contractor…