A22_W912HZ-14-R-0022-0005.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 questions and answ ers.

Section M and the PWS have been revised.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 45

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

16C. DATE SIGNED

BY 12-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 X is extended, is not extended.

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

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

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

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

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

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

CONTRACT ORDER NO. IN ITEM 10A.

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

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

D. OTHER (Specify type of modification and authority)

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

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

10A. MOD. OF CONTRACT/ORDER NO.

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

6. ISSUED BY

3. EFFECTIVE DATE

12-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 45: Reference Section L.3.6.5 and Section L.3.7. Section L requires Offerors to identify “relevant corporate experience” by listing and describing contracts/task orders.

Each such project must have a Past Performance Questionnaire (PPQ), which will be included as Attachment C, presumably as part of Volume II, Past Performance. No other requirements for Volume II are identified other than “performance recognition documents.” Does the Government require anything other than PPQs and performance recognition documents as part of Volume II?

Answer: No, only PPQs and personal recognition are required.

Question 46: Reference Section L.3.6.6 and Section M.2.1. Are there any mission-critical activities underway on the current contract that offerors should be aware of when planning and executing contract transition?

Answer: No.

Question 47: Reference Section L.3.6.4.3. The only key position identified in the solicitation is the Program Manager. Are offerors free to propose additional personnel as key personnel?

Answer: See question 34 in Amendment 0004.

Question 48: Reference attachment B 3.1. Please clarify “user”. Is that ERDC ITL workers or all USACE personnel?

Answer: The Government will not clarify “user.”

Question 49: Reference Section L.3.6.5. Since the Offeror is only providing total pricing in the Sample Task Order and not all of the PWS, how do they determine that their projects are at least half the dollar value of all PWS requirements?

Answer: The maximum ordering limit is $95,000,000.00. Please see Section F.3.

Question 50: Section B: Will the government consider providing plug numbers / fixed values for Travel, ODC and Training for estimating purposes and to ensure consistency among bidders?

Answer: The vendor is not required to fill out section B. Please see question 7 in Amendment 0004.

Question 51: Reference PWS, Section C.3.1.1. Will the applications be written for high performance computers? What is the target computer platform for applications?

Answer: The primary targeted computer platforms will be Windows, Linux, and OS based.

Question 52: Reference PWS, Section C.3.1.1.3. Which debug tools does the Government provide for contractor use?

Answer: None.

Question 53: Reference Section M, Subfactor 3. What is the meaning of “work-force-caused change“?

Answer: Please see revised Section M, Subfactor 3.

Question 54: Reference Attachment B, Section 4. Will the Government change the Description of A005 to “Criteria, process and results for functional, security and technical testing.”?

Answer: The vendor can call the deliverable what they wish. They must ensure that it is documented as the deliverable for the required task.

Question 55: Reference Solicitation, Section 3.3.1. Would the Government provide a list of data manipulation software currently in use to support in-house data layer creation and manipulation (i.e. ESRI ArcGIS, MicroStation, AutoCAD, etc.) since Google Earth Enterprise Server/Fusion/Client products are mainly a spatial data display tool?

Answer: Please see revised PWS.

Question 56: Reference Solicitation, Section 3.3.1. What are ITL’s expectations concerning the end of support of Google Earth Enterprise in March 2017 (i.e., ESRI ArcGIS Server solution)?

Answer: Please see revised PWS.

Question 57: Reference Solicitation, Section 3.3.1. If ArcGIS Server is the preferred solution to Google Earth Enterprise end of support, what relational database will be put in place (i.e. – Oracle, SQL Server, etc.)?

Answer: Oracle and SQL Server are the preferred database solutions. However, future database solutions may be prescribed based on the task order.

Question 58: Reference Solicitation, Section 3.3.2. What is the current relational database and vector editing software used in the ITL?

Answer: Oracle and SQL Server are the preferred database solutions. However, future database solutions may be prescribed based on the task order.

Question 59: Reference Solicitation, Section 3.3.3. What is the current raster processing software suite preferred by the ITL?

Answer: The task order will prescribe the deliverable format of the data.

Question 60: Reference Solicitation, Section 3.3.4. What is the current vector processing software suite preferred by the ITL?

Answer: The task order will prescribe the deliverable format of the data.

Question 61: Reference Solicitation, Technical Requirements. What are the primary tool suites which the government uses to date to perform the requirements within the ERDC?

Answer: This question is too vague to provide a response.

Question 62: Reference Section B, CLIN 0005 and 0006. Will the Government be evaluating Travel, ODCs, and Training costs in the IDIQ pricing? If so, will the Government be providing a plugged number?

Answer: Please see question 50.

Question 63: Reference Section L.3.1. Is it acceptable to submit the text and graphic portions of electronic files in PDF format?

Answer: Yes; however, Attachment A and Attachment E shall be submitted in excel.

Question 64: Reference Section 3.1.1 of base PWs and Section 3.6.1 of sample task order PWS. The base PWS and the Sample Task PWS both present apparent redundancies between their section (e.g., as shown under “RFP Text” in this table). Can the Government provide a more detailed description of the product/deliverable to be provided under these PWS sections? The redundancies and lack of specifics in the base and Sample Task PWS’s complicates the Government’s ability to evaluate proposals.

Answer: The base PWS does not order work and only list general deliverables. Specific required deliverables will be identified at the task order level.

Question 65: Is there an interface (automated or manual) requirement to push or pull data from external systems in this Sample PWS?

Answer: The objective of the Sample PWS is to solicit a proposed solution that is innovative. It is the vendor’s choice to propose a solution that either has or does not have an interface and the functionality of the interface regarding the data flow to other systems.

Question 66: Reference section 3.5.2. Is there a requirement to purchase hardware or software in this PWS?

Answer: No.

Question 67: Reference section 3.5.2. Is there a requirement to convert legacy data to a new application/system in this PWS?

Answer: No.

Question 68: Reference sample task order PWS section 3.1. Is there an interface (automated or manual) requirement to push or pull data from external systems in this Sample PWS?

Answer: Please see question 65.

Question 69: Reference sample task order PWS section 3.1.c. Are the architecture requirements software, hardware or both? If hardware, what types of equipment (servers, computers, IT services, etc.)?

Answer: The objective of the Sample PWS is to solicit a proposed solution that is innovative and demonstrates that the functional requirements defined for the project have been addressed. It is the vendor’s choice to propose a solution that addresses hardware and/or software requirements.

Question 70: Reference section 3.6.5. “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” This is difficult to determine a value as this is an IDIQ contract.

Please provide a specific value using the $95M ceiling number would be too large and not allow for sufficient PP.

Answer: $95M is the Government’s anticipated not to exceed capacity. However, it is not guaranteed over the five years.

Question 71: Do resumes count against page count?

Answer: Yes.

Question 72: Please explain 3.2 Performance Standards (c) STD“No more than 2 validated complaints per month”? What is a complaint, formal or informal?

Answer: A complaint is non-compliant performance. The Government does not recognize an “informal” complaint.

Question 73: In many instances the incentive/remedy doesn’t match the AQL (AQL is quality/accuracy based incentive/remedy is time based). Can the USG clarify?

Answer: Please see question 28 and 29 in Amendment 0004.

Question 74: Is there a required minimum set of key personnel or is this left to the bidder?

Answer: Please see question 34 in Amendment 0004.

Question 75: Are key personnel required to be employed by the prime or can they be from a sub?

Answer: We do not have privy of contract with subcontractors.

Question 76: Reference page 9, Para 1.3. Could the government identify the percentage of work to be performed at each location described? (I.e., “Vicksburg, MS, Alexandria, VA, Champaign, IL, and Hanover, NH”)

Answer: Unknown.

Question 77: Reference page 14, Para 3.2. Could the government quantify the type and quantity of sensors and the systems that are supported by the sensors?

Answer: No.

Question 78: Reference page 72, Para 3.6.5. Can you explain the relevant corporate experience described in this section? It states “(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).” Does each past performance have to be at least half the dollar value proposed?

Answer: Relevancy, as it pertains to past performance information, is a measure of the extent of similarity between the service/support effort, complexity, dollar value, contract type, and subcontract/teaming or other comparable attributes of past performance examples and the source solicitation requirements; and a measure of the likelihood that the past performance is an indicator of future performance.

Question 79: Are Resumes (work history, etc.) exempt from the Technical and Management Approach 20-page limit?

Answer: Please see question 71.

Question 80: The USG has asked for a QCP and stated the following in Section L 3.6.4

4. Quality Control Plan: The proposal shall include a Quality Control Plan (QCP) assuring that requirements of the contract are met across functional requirements outlined in the PWS. Discussion: The requirement is overly broad and not definitive. Lack of specificity in the quality expectations can lead to unsuccessful offerors using that as grounds for protest. Question - Can the USG provide a QASP, metrics, audit schedules, and inspection requirements that are expected to be discussed in the QCP for EACH of the PWS sections?

Answer: The requirements for the overall QASP for the master IDIQ are included in the performance requirement summary (PRS).

Question 81: Reference Section L.1.6. States, “The Government reserves the right to award Sample Task Order 0001 as the first task order under the resulting contract if determined to be in the best interest of the Government.” Please confirm that Sample Task Order 0001 is new work and has not previously been delivered.

Answer: The sample task order has never been delivered.

Question 82: Reference: SF 33, block 9: Submission Due date is 22 Feb 2016. Question:

Will the Government be considering the release of a revised submission date due to the Federal holidays on 18 Jan and 15 Feb, and the current submission day a Monday, which may impact shipping lead time?

Answer: The solicitation has been extended to 03 March 2016 4:00PM CST.

Question 83: Reference: Amendment 0001, Section L 3.8, page 12 of 13: The Offeror shall include a plotted graph of all labor rates proposed. The graph shall illustrate the variation in labor rate levels I though VI for all labor categories as well as the variation for each rate across the years. The Offeror shall generate graphs illustrating rates for each rate type (On-site FFP, Off-site FFP, On-site CPFF, and Off-site CPFF). An example of an illustration is provided in Attachment G. The Offeror shall provide a summary of the representation. Question: We have calculated that this requirement will result in 104 graphs that will be included as part of the price/cost volume. Is it the Government’s intention for each responder to provide 104 plotted graphs? Question: Will the Government provide anticipated labor categories by location? Question: Will the Government provide historical hours and/or dollars which were incurred on the current contract effort for offeror pricing purposes?

Answer: Per the solicitation, in Section L, the Offeror shall include a plotted graph of all labor rates proposed. The graph shall illustrate the variation in labor rate levels I though VI for all labor categories as well as the variation for each rate across the years. The Offeror shall generate graphs illustrating rate for each rate type (On-site FFP, Off-site FFP, On-site CPFF, and Off-site CPFF). An example of an illustration is provided in Attachment G. The Offeror shall provide a summary of the representation.

Question 84: Reference: Original Solicitation, Section B, Item No. 0003, page 3 of 91 states, “The Contractor shall perform Research and Development (R&D) services in accordance with Section C, all applicable attachments, and the fully loaded labor rates in Section B.

Specific requirements will be identified through Performance Work Statements (PWS) to be included in each individual task order.” Question: The contractor is requested to price Item No. 0003 in Section B. Will the Government provide hours in order to complete the task?

Answer: Please see question 7 in Amendment 0004.

Question 85: Reference L.3.6.4.3 Key Personnel. The RFP requires KP information that is essentially a CV/Resume. Each will take at least two pages per KP to adequately describe technical skills and experience. Will the USG exclude the KP CV/Resume from the page count?

Answer: Please see question 71.

Question 86: Reference L.3.6.4.4 Quality Control Plan. The RFP requires a QCP, yet does not provide any required components of the QCP. The USG provides a PRS, but it is the same Incentive/Remedy for each of the PWS sections and is very generic. Will the USG provide more specificity for the required QCP?

Answer: Please see question 80.

Question 87: Reference L.3.6.6 Transition. The RFP asks for a schedule for transition and integration. We can find no specified transition period. Request the USG specify the transition period desired e.g., 30 days, 45 days, etc.

Answer: Please see question 16 in Amendment 0004.

Question 88: Reference L 1.1. Instructions stipulate proposal must be mailed. Will USG allow hand delivery and if so where and during what hours?

Answer: Please see question 40 in Amendment 0004.

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 22-Feb-2016 04:00 PM to 03-Mar-2016 04:00 PM.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

PERFORMANCE WORK STATEMENT

Performance Work Statement (PWS) ITL Information Technology Laboratory

Research and Development (R&D) Service Requirements

02/2704/20156 Version 98.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 ... 21

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.

a) STD: Deliverables are made in accordance with schedule 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. Tools commonly used for geospatial data authoring/manipulation included, but not limited to, are ESRI ArcGIS, MicroStation, or AutoCAD. Server tool commonly used for geospatial data publishing include, but not limited to, ArcGIS Server.

a) STD: Compliant with applicable standards AQL: Level of accuracy consistent with source data

A005 Digital Maps A006 Map Metadata A012 Geospatial data A015 Software source code

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

A005 Digital Maps A006 Map Metadata A009 Database A012 Geospatial data 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 A012 Geospatial data

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

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

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

A013 Status report

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 A013 Status report A015 Software source code

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

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.