A02.12 PWS for Example Task Order.docx

IDIQ Title: Hydrologic Engineering Software Development for the Hydrologic Engineering Center (CEIWR-HEC), Davis, California, Multiple Award Task Order Contract (IWR-HEC SD MATOC) Task Order Title: HEC-SDS Minor Bug Fixes and Enhancements

1 Introduction The U.S. Army Engineer Institute for Water Resources (IWR) was formed in 1969 to provide the U.S. Army Corps of Engineers (USACE) Civil Works (CW) Program with the capability to analyze and anticipate emerging water resources trends and issues facing our nation. From its beginning, responding to the sweeping changes in water resources development policies and the passage of the National Environmental Policy Act in 1969, IWR has been tackling the water resources challenges coming from an ever-increasing public demand for water projects and the policy and technological challenges of the 21st Century. As such, there remains a compelling need for analytical and professional support to pursue innovative approaches to solving these new problems.

IWR occupies a unique position within the USACE Civil Works program. It is not part of the USACE Headquarters or a District or Division, but rather a Field Operating Activity (FOA) under the supervision of the Director of Civil Works for USACE. IWR’s challenging mission remains integral to shaping the evolution of Federal water resources policy as decision-makers at all levels within USACE look to IWR for insights into a host of complex economic, environmental, and social issues.

IWR seeks services and support in software code development for maintenance of the software called Hydrologic Engineering Center-Storm Drain System (HEC-SDS). Maintenance includes minor bug fixes and enhancements. HEC-SDS software will allow staff and partners to develop water resource modeling applications to support studies spanning multiple USACE business lines.

1.1 Mission

IWR is a FOA under the Commanding General, USACE, and the staff supervision of the USACE Headquarters (HQUSACE) Directorate of Civil Works under the direction of the Deputy Commanding General for Civil and Emergency Operations (DCG-CEO) and the Director of Civil Works (DCW). IWR serves as a national center of expertise, supporting the HQUSACE, the Office of the Assistant Secretary of the Army (Civil Works) and USACE field offices by providing:

a. Analysis of emerging trends and issues in anticipation of changing water resources management conditions to inform the strategic direction of the CW Program and the corporate development of policies, programs and investment decision strategies.

b. Systems-based planning methodologies, tools and training across CW business areas, analysis, economic and socio-economic assessments, and enterprise capacity development.

c. Leadership of the USACE Economics Community of Practice, with a focus on project level, regional and national economic analysis, multi-criteria and risk-informed analysis, economic and socio-economic assessments, and enterprise capacity development.

d. Development of results-oriented CW Program and project information through the management of national data systems, and application for investment decision support to USACECW on an enterprise level.

e. State-of-the-art hydrologic and hydraulic engineering methodologies, models and management systems, and associated planning and environmental methods, models and training.

f. Advanced engineering risk management expertise for dam, levee and infrastructure safety, and the development, application and stewardship of the engineering practice involving contemporary risk-related methods and models.

EXAMPLE TASK ORDER PERFORMANCE WORK STATEMENT

g. Assistance to USACE on anticipating, preventing or minimizing water conflicts and ensuring the interests of the public are addressed in Corps decision-making, and leadership of the USACE Community of Practice for Conflict Resolution and Public Participation.

h. Globally-recognized expertise on water security and Integrated Water Resources Management (IWRM) applied via partnerships with USACE Major Subordinate Commands (MSCs), Department of Defense (DoD) geographic Combatant Commands (COCOMs), the U.S. State Department, United Nations and other U.S. and international institutions and Non-Governmental Organizations (NGOs), to address water and natural resources planning, water policy and governance, water management, trans-boundary water conflict mitigation, and other water-related challenges within the U.S. and around the world.

i. Assistance to HQUSACE, Army, and DoD, working in partnership with USACE MSCs and DoD COCOMs, for strengthening theater security cooperation by facilitating civilian and military collaborations, emphasizing multi-national force capacity development on the life-cycle planning of the humanitarian response and consequence management across all forms of extreme water events and other natural and technological disasters.

j. A critical mass of knowledge on the engineering and scientific aspects of global change and the adaptation to climate change and other risk factors in collaboration with interagency partners.

i. Enterprise-level financial analysis expertise in support of the CW mission and USACE intergovernmental collaboration on public works infrastructure investment decisions.

k. Policy and technical advice to USACE and Army senior leaders on a wide range of water resources, marine transportation, flood/coastal storm risk reduction, conflict resolution, international water, natural resources stewardship and ecosystem management issues.

1.2 Other Background Information

IWR is the USACE center of expertise for integrated water resources management, focusing on planning analysis and hydrologic engineering and on the collection, management and dissemination of Civil Works and navigation information, including the nation’s waterborne commerce data. It also serves as the USACE center of expertise for dam and levee safety, climate change adaptation, collaborative planning and environmental conflict resolution and operates the International Center for Integrated Water Resources Management (ICIWaRM), under the auspices of the United Nations Educational, Scientific and Cultural Organization (UNESCO).

IWR fulfills its mission by providing: (a) analysis of emerging and or long-term water resources and waterborne transportation trends, needs and issues, (b) state-of-the-art planning and hydrologic engineering methods, models and training, (c) policy and program analyses to improve the effectiveness and efficiency of the Civil Works program, (d) strategic planning for the USACE Civil Works program, and (e) national data management of results-oriented program and project information across Civil Works business lines.

IWR is currently responsible for a number of USACE water resources related activities or programs, including evaluation of Civil Works Strategic Plans, Civil Works policies and programs, National Economic Development benefits for water resources development, investment and financial analysis, performance measurements and evaluations, infrastructure analysis, climate change, etc. IWR also routinely provides technical assistance to the USACE Headquarters, Corps Field Operating Activities (Divisions, Districts, and Laboratories), other US Army Commands, other Federal agencies, other levels of government, and international organizations and financial institutions, and other countries, in encompassing a broad range of topic areas related to levee and dam safety, risk assessment, dredging requirements, port/waterway transport, aquatic ecosystem restoration, environmental stewardship, flood and drought risk management, emergency preparedness, watershed planning, regulatory, multi-purpose water resources including hydroelectric power, water supply and reallocation, recreation, and other water and related land resources issues.

Support is rendered through IWR’s operating units at the Humphreys Engineer Center in Alexandria, VA; Hydrologic Engineering Center (HEC) in Davis, CA; Navigation and Civil Works Decision Support Center (NDC) co-located at the Humphreys Engineer Center and the USACE New Orleans District office in New Orleans, LA; Waterborne Commerce Statistics Center also located at the USACE New Orleans District office in New Orleans, LA and the Risk Management Center (RMC) co-located in Denver, CO and Pittsburgh, PA. For more specific information about IWR centers and expertise, please visit the IWR website at: www.iwr.usace.army.mil.

1.3 Scope

HEC-SDS is a Java language software tool designed to simulate storm drain systems within urban areas for both single storm events and period of record analyses. The software includes hydrologic analysis procedures such as event infiltration, unit hydrographs, and hydrologic routing to generate overland runoff volumes and hydrographs. HEC-SDS also includes 2-dimensional hydraulic modeling functionality to route flows overland, as well as pressurized flow capabilities to route runoff through pipe networks defined by the user. Additional features include pumps, weirs, orifice openings, and detention ponds.

The software features a completely integrated work environment including a database, data entry utilities, computation engine, and results reporting tools. A graphical user interface allows the user seamless movement between the different parts of the software. Simulation results are stored in HEC-DSS (Data Storage System) and can be used in conjunction with other software for studies of flow forecasting, future urbanization impact, flood risk management and watershed-scale analyses.

Services to be performed include:

· Evaluating and classifying issues within the existing software code.

· Performing bug fixes in code.

· Providing minor modification or enhancements to the code.

2 General Requirements This section describes the general requirements for this effort. The following sub-sections provide details of various considerations on this effort.

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

This section describes the contract administration and management for this effort. The following sub-sections provide details of various considerations on this effort.

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. The contractor must maintain continuity between the support operations at the location specified in individual Task Orders 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 support contracts or task orders. The contractor shall assign work effort and maintaining proper and accurate time keeping records of personnel assigned to work on the requirement.

2.3.3 Personnel Administration

The contractor shall provide the following management and support as required. The contractor shall provide for employees during designated Government non-workdays or other periods where Government offices are closed due to weather or security conditions. The contractor shall maintain the technical competency of their employees by providing initial and refresher training as required to meet the task order PWS requirements. The contractor shall make necessary travel arrangements for employees. The contractor shall provide necessary infrastructure to support contract tasks.

The contractor shall provide administrative support to employees in a timely fashion (time keeping, leave processing, pay, emergency needs).

If the capability, knowledge, and expertise is no longer available, the contractor is responsible for providing individuals with comparable qualifications.

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 contractor shall also be responsible for insuring timely payment to subcontractors. The prime contractor will manage work distribution to ensure there are no Organizational Conflict of Interest (OCI) considerations.

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 (see Appendix A, attached), labor rates, and man-hours 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.

2.6 Location and Hours of Work

Unless specified at the individual task order level, the work required on this solicitation is expected to be carried out at the contractor’s location. If work is required at Government facilities, normal workdays are Monday through Friday except US Federal Holidays. Federal workers typically work eight (8) hours per day, 40 hours per week. Flextime workers start not earlier than 0600 and not later than 0900. Core hours of work are from 0900 to 1500 daily. All employees are expected to be available during core hours.

2.7 Travel / Temporary Duty (TDY)

Travel to other Government facilities or other contractor facilities may be required and will be specified in the PWS. If authorized at the task order level, travel shall be in accordance with the limitations set forth in FAR 31.205-46, Travel Costs.

2.8 Invoicing Instructions

The contractor is authorized to invoice as frequently as monthly; for work performed. The contractor is required to invoice under this task order issued against the IWR-HEC SD MATOC. The contractor shall append the final invoice with an “F” to indicate final.

All task orders under the IWR-HEC SD MATOC are firm fixed price (Labor and Materials) and the contractor shall give their concurrence to return any unused Travel funding when the final invoice is submitted.

Invoices should be sent to email addresses below. This ensures that a copy of the invoices is sent to the USACE Finance Center (CEFC) and also to the IWR budget officer:

CEFC-Q0Invoices@usace.army.mil DLL-CEIWRCONTRACT@usace.army.mil

2.9 Performance Requirements

The following section specifies the Performance Objectives and Performance Elements for the contract. Within the broad range of activities performed by USACE, these tasks may be required within any of the mission, business or program areas described in Section 1.3, either domestically or internationally. It is anticipated that in many cases, extensive subject matter expertise and cutting-edge technologies and strategies will be required to perform the complex analysis and development of state-of-the-art solutions and deliverables associated with the tasks described below.

3 Software Development Approach This section describes the required software development methods for this effort.

3.1 Agile Software Development

The contractor shall apply Agile software development methods for software maintenance, development, and configuration support. The contractor shall utilize Jira to track and document all software development activities. Code branching best practices should be followed, including minimizing branch life span before merging into the main branch.

An Agile software development approach consists of defined sprints and scrums, and results in incremental deliverables. The steps required for an Agile iteration (sprint) are described below.

1. Sprint Planning. At the beginning of each sprint, the contractor and HEC will meet to discuss the goals, scope, and tasks associated with that sprint. The contractor will document details of tasks required to complete the sprint in Jira.

2. Scrum Meetings. At various frequencies, as appropriate for the sprint, the contractor and HEC will meet to discuss progress of work. HEC will provide direction as needed. Each meeting is expected to last one hour and will be held by phone or webinar.

3. Testing. Tests should be conducted after every sprint to ensure the new code did not introduce bugs into the software. When appropriate, new unit tests and/or integration tests will be created.

4. Sprint Documentation. Include documentation in Jira for work completed that describes assumptions, code development, important notes for the next iteration, as well as design decisions.

5. Sprint Code Review. At the completion of a sprint, the contractor will upload the source code to BitBucket repository and will brief HEC on the completed effort.

Sprints generally last between 2 to 4 weeks. One iteration should not exceed 5 weeks with two contractor staff, with appropriate qualifications as required for the sprint.

3.2 Code Management and Build System

The contractor shall conform to the following code management and build system requirements when completing tasks:

· Code will be stored in BitBucket or Github.

· Unit tests will be developed as appropriate to validate any computational logic (i.e., non-UI code).

· Branches will be tested via an automated system before merging back into the main branch.

· Automated builds will be made via TeamCity and deployed to Nexus, or similar, for each merge into the main branch.

· All work progress and issues will be tracked in Jira.

4 Software Maintenance The contractor shall provide services to support HEC and perform maintenance and minor modifications of HEC-SDS source code. Details of this task are described below.

4.1 Issue Classification

Issue classification requires the contractor to evaluate an issue and determine if the issue is:

a. a bug in existing code,

b. an issue of the government improperly using the existing code or,

c. a functionality gap in what the existing code is capable of doing and what the government would like the code to do.

It is expected that a contractor can classify issues within two hours. The contractor must identify the type of issue and have HEC’s approval in writing prior to conducting any work. An additional 1-hour of time for Admin/Clerical support per issue is appropriate for the overall project management.

4.2 Bug Fixes in software code

Troubleshooting program behavior; testing production sites and then correcting the codebase for the identified errors. Test the bug fix with a variety of data sets to ensure problem is adequately addressed. If applicable, ensure that bug fixes are compatible with the GUI and any changes to the model are displayed correctly. Document how the code was fixed, and how the testing was performed.

a. Minor Bug Fixes are those that normally require a few additional lines of logic/coding to be added to the existing code base. A minor bug fix is one that is expected not to exceed a day’s effort by the contractor to resolve. An additional 2-hours of time for a Senior Analyst and 2-hours of time for Admin/Clerical support is appropriate for the overall project management.

b. Routine Bug Fixes are those that normally require additional logic/coding, but require the addition of additional functions, procedures, or objects to accomplish. The effort for the contractor to resolve a routine bug fix is expected not to exceed two days. An additional 2-hours of time for a Senior Analyst and 2-hours of time for Admin/Clerical support is appropriate for the overall project management.

4.3 Minor Modifications or Enhancements

The government will periodically identify functionality gaps in code. The tasks associated with a minor modification will normally require but are not limited to:

· the creation of new function or procedure calls;

· new classes or packages;

· new tables or other database objects; or

· code objects.

· the creation of a new user function;

· development of work-around methods or script approaches to accomplish special needs;

· tele/web-conferences to coordinate tasks and provide support

Any minor modification or enhancement should be tested with a variety of datasets to ensure it functions appropriately. If applicable, ensure that modifications are compatible with the GUI and any changes to the model are displayed correctly. Document all modifications or enhancements along with test verifications. The effort for the contractor to resolve a minor modification of the codebase is expected not to exceed two days. An additional 2-hours of time for a Senior Analyst and 2-hours of time for Admin/Clerical support is appropriate for the overall project management.

4.4 Deliverables

Deliverables consist of source code for the government-requested minor/routine bug fixes and/or modifications/enhancements, as well as data sets and meeting minutes, as applicable. Testing should be performed to verify that the bug fixes do not introduce additional bugs in other areas of the code.

All delivered source code will be checked into the appropriate government controlled Bitbucket Source Control software depots. The contractor will have 5 days to respond to each individual request. The government technical POC will have 5 workdays to review the working program and request corrections or modifications. Contractor will have 5 workdays to address the government technical POC requests or comments.

Work performed under this purchase order must be initiated in advance and in writing at the request of the Project’s Technical POC, the Project’s Technical Supervisor POC, or their designee. Requests must be provided in the form of Jira Incident Entry. The contractor is required to log their activities and results under each Jira Incident, as well as a log correlating to the requests. The log shall give:

1) Government Requestor,

2) Date of service

3) Notes from log entry item

4) Current status of log entry item

5) For bugs fixed, provide a description on how the issue was addressed or the bug fixed, including the tests performed to verify fix.

6) Hours worked on each log entry item

Each invoice will refer to one or more Jira Incidents/Ticket Numbers. Each Jira ticket will have all the information mentioned in the above log.

Since it is possible for modifications and software support activities to exceed resources, the contractor shall not exceed the following representative list of activities.

3) Eight (8) Minor Modification or Enhancement

4) Four (4) Meetings

PERIOD OF PERFORMANCE IS 365 DAYS FROM AWARD OF THIS TASK ORDER.

5 Special Requirements

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

5.1 Security and Safety

5.1.1 Security

Visitor Group Security Agreement. The contractor shall sign a Contractor Visitor Group Security Agreement to protect classified information involved in performance under this contract or Task Order. The Agreement will outline responsibilities in the following areas: Contractor security supervision; Standard Practice Procedures; access, accountability, storage, and transmission of classified material; marking requirements; security education; personnel security clearances; reports; security checks; security guidance; emergency protection; protection of government resources; DD Forms 254; periodic security reviews; and other responsibilities, as required.

Other Security Requirements.

1. AT Level I Training. All contractor employees, to include subcontractor employees, requiring access to Army installations, facilities, controlled access areas, or require network access, shall complete AT Level I awareness training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. Upon request, the contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the contracting officer (if a COR is not assigned), within 5 calendar days after completion of training by all employees and subcontractor personnel. AT Level I awareness training is available at the following website: https://jkodirect.jten.mil or it can be provided by the RA ATO in presentation form which will be documented via memorandum.

2. Access and General Protection/Security Policy and Procedures. All contractor and all associated sub- contractors’ employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative). The contractor shall also provide all information required for background checks or background investigation and to meet installation/facility access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any installation or facility change, the Government may require changes in contractor security matters or processes.

3. Suspicious Activity Reporting Training (e.g., IWATCH, Corps Watch, or See Something, Say Something). The contractor and all associated sub-contractors shall receive a brief/training (provided by the RA) on the local suspicious activity reporting program. This locally developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the project manager, security representative or law enforcement entity. This training shall be completed within 30 calendar days of contract award and within 30 calendar days of new employees commencing performance with the results reported to the COR NLT 5 calendar days after the completion of the training.

4. Contractor Employees Who Require Access to Government Information Systems. All contractor employees with access to a government info system must be registered in the Army Training Certification Tracking System (ATCTS) at commencement of services, and must successfully complete the DOD Information Assurance Awareness prior to access to the information systems and then annually thereafter in accordance with personnel security standards listed in AR 25-2 (Information Assurance), an appropriate background investigation will be conducted prior to accessing the government information systems.

5. For Contracts that Require OPSEC Training. All new contractor employees will complete Level I OPSEC Training within 30 calendar days of their reporting for duty. Additionally, all contractor employees must complete annual OPSEC awareness training. The contractor shall submit certificates of completion for each affected contractor and subcontractor employee, to the COR or to the contracting officer (if a COR is not assigned), within 5 calendar days after completion of training. OPSEC awareness training is available at: https://www.iad.gov/ioss/ or http://www.cdse.edu/catalog/operations-security.html; or it can be provided by the RA OPSEC Officer in presentation form which will be documented via memorandum.

6. For Information assurance (IA)/information technology (IT) training. All contractor employees and associated sub-contractor employees must complete the DoD IA awareness training before issuance of network access and annually thereafter. All contractor employees working in IA/IT functions must comply with DoD and Army training requirements in DoD 8570.01, DoD 8570.01-M and AR 25-2 within six months of employment.

7. Will be escorted in areas where they may be exposed to classified and/or sensitive materials and/or sensitive or restricted areas. All contract employees, including subcontractor employees who are not in possession of the appropriate security clearance or access privileges, will be escorted in areas where they may be exposed to classified and/or sensitive materials and/or sensitive or restricted areas.

8. Pre-screen candidates using E-Verify Program. The Contractor must pre-screen Candidates using the E- verify Program(http://www.uscis.gov/e-verify) website to meet the established employment eligibility requirements. The Vendor must ensure that the Candidate has two valid forms of Government issued identification prior to enrollment to ensure the correct information is entered into the E-verify system. An initial list of verified/eligible Candidates must be provided to the COR no later than 3 business days after the initial contract award." *When contracts are with individuals, the individuals will be required to complete a Form I-9, Employment Eligibility Verification, with the designated Government representative. This Form will be provided to the Contracting Officer and shall become part of the official contract file.

Local Security Policy:

All contractor employees who require physical access to government-controlled facilities or logical access to government information and or information systems are subject to a fitness determination and appropriate vetting. The Humphreys Engineer Center Support Activity (HECSA) utilizes the same OPM guidelines for fitness determinations that are used to determine suitability for federal employment under 5 CFR part 731.

To assist in the vetting process, the contractor must submit a notice of visit form for each employee who will perform work on the contract, including at the minimum, the name, social security number and date of birth of each employee performing work on the contract that need access. Documents containing personally identifiable information may only be submitted via encrypted email, by first class mail or it may be hand carried to the security office. Notice of visits must be submitted through the government contracting officer representative (COR) or technical representative who will deliver them to the security office. All notice of visits must be received five business days in advance of the contractor reporting for work unless an exception is requested by the COR and approved by the security office.

The COR or technical representative for each contract is the liaison between the security office and the contractor. Contractor employees who are not sponsored by a government employee will not be granted access to any facilities under HECSA control nor will HECSA security approve logical access to information systems if the COR does not provide the notice of visit containing either the DOD ID number (back of the CAC) or the social security number to the security office.

The type of investigation a contracted employee is subject to depends on the type of work being performed and the duration of access required. The minimum requirement for vetting personnel who do not require a common access card is the NCIC III. Contractors who need a common access card must have the minimum of a current favorably adjudicated NACI on file. If no investigation is on file, the CAC will not be issued until a favorable FBI fingerprints check is received by the security office and the NACI has been initiated in PSIP.

If an employee has been the subject of a previous favorably adjudicated investigation, it may be reciprocally accepted if there has not been a two-year break in service and there is no presence of new and potentially unfavorable information that casts doubt about the subject’s suitability. When a background check is reciprocally accepted but is more than 5 years old, the security office may initiate an NCIC III check to ensure no new unfavorable information exists.

Contractor employees whose access to classified information has been suspended or revoked will not be authorized logical access to information systems IAW AR 25-2 paragraph 4-14 b (2) until that investigation is favorably adjudicated. These personnel will also not be allowed unescorted access to government facilities until the investigation has been favorably adjudicated by the Command Security Manager. The contractor must provide employees who can be cleared to perform work and must immediately provide replacement employees for those who cannot be cleared.

5.1.2 Safety

Contractor Compliance: The contractor and its subcontractors shall comply with Public Law 91-596 (Occupational Safety and Health Act (OSHA)) and the Environmental, Safety, and Occupational Health (ESOH) (DODD 4715.1E). These requirements shall be incorporated into the contractor’s safety and health program. The Department of Defense (DoD) participates in the OSHA Voluntary Protection Program (VPP). Contractor personnel performing services on a DoD installation shall participate in the local VPP. Information on the VPP is available at https://www.osha.gov/dcsp/vpp/all_about_vpp.html.

Mishap Notification and Investigation: The contractor and its subcontractors (if applicable) shall promptly report pertinent facts regarding mishaps involving Government property damage or injury to Government personnel and to cooperate in any resulting safety investigation. The contractor shall notify (via telephone) the cognizant contracting officer, the contracting officer’s representative, and/or other applicable members within four (4) hours of all mishaps or incidents. The Government person notified by the contractor will in-turn notify the Safety office. Contractor notifications made after duty hours shall be reported to the appropriate installation Command Post. If requested by the cognizant contracting officer, the contracting officer’s representative, and/or the cognizant program manager, the contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenance and training records until released by the investigating safety office. If the Government investigates the mishap, the contractor and the subcontractors shall cooperate fully and assist the Government personnel until the investigation is completed.

5.2 Government Furnished Materials

It is not anticipated that the contractor will be working at Government facilities. In cases where the Government provides equipment or materials, it will be specified in the individual task order PWS.

5.3 Quality

This section describes the Quality Control components for this effort. The following sub-sections provide details of various considerations on this effort.

5.3.1 Quality Control

The Contractor shall develop a Task/Delivery Order Quality Control Plan (QCP) and maintain an effective quality control program to ensure services are performed in accordance with the IDIQ contract and this PWS. The Contractor shall develop and implement procedures to identify, prevent, and ensure non- recurrence of defective services. The Contractor’s QCP is the means by which he assures himself that his work complies with the requirement of the contract.

The finalized QCP will be accepted by the Government at the time of the award of the Task/Delivery Order. The Contracting Officer may notify the Contractor of required modifications to the plan during the period of performance. The Contractor then shall coordinate suggested modifications and obtain acceptance of the plan by the Contracting Officer. Any modifications to the program during the period of performance shall be provided to the Contracting Officer for review no later than 10 working days prior to effective date of the change. The QCP shall be subject to the Governments review and approval. The Government may find the QCP "unacceptable" whenever the Contractors procedures do not accomplish quality control objective(s). The Contractor shall revise the QCP within 10 working days from receipt of notice that QCP is found "unacceptable."

5.3.2 Quality Assurance Surveillance Plan (QASP)

The Government shall monitor the Contractor’s performance in accordance with the Government’s QASP.

6 Deliverables The Contractor shall provide reports and other print deliverables in publication quality format and provide web publishable versions of such deliverables. All deliverables, including software, shall be provided to the Government with unlimited rights. Format and delivery schedule for deliverables shall be outlined in Contract Data Requirements List and/or in the applicable section of the PWS. The table below identifies a set of deliverables that may be required under this contract. It should be noted that the table is NOT all inclusive of the types of deliverables that may be required.

activities with JIRA and source code submissions.

Performance Requirement Summary (PRS)

Performance Standards: Performance standards will be specified with each PWS solicitation. As a point of reference, the following is a table of potential performance standards and the relevant task statements.

Individual task order PWS’s may also contain specific Standards, AQL’s and Incentives/Remedies.

(Statements)

Contractor shall assure requested work is thoroughly tested before submittal.

a. Timeliness - 100% Completion and submittal of log monthly if work has been requested

b. Quality All work is performed to industry standard 95% of the time Re-perform/correct at no cost to the Government.

a. Timeliness - 100% Completion and submittal of log Re-perform/correct at no cost to the Government.

Contractor shall assure requested work is thoroughly tested before submittal.

monthly if work has been requested

b. Quality All work is performed to industry standard 95% of the time time

APPENDIX A – LABOR CATEGORIES

The following labor categories are the only approved labor categories to be used on task orders:

1. Senior Principal Investigator (SPI)

Responsibility (RESP): This category is intended to be used rarely and only when the highest level of subject matter expertise in water resource related fields is required. When used, they will be the senior topic expert on the assigned task. The SPI may design the approach for solving the problem and may oversee the execution of the study, providing advice and guidance as necessary. It is expected that, when used, the SPI with the most expertise in the required discipline will work on that task, e.g., a task requiring expertise in economics should be headed by a SPI with a background in economics.

Minimum Qualifications (MQ): The SPI shall have a PhD in a discipline that is closely related to the water resources fields, plus 10 years of experience in these fields. In lieu of the PhD, the SPI may substitute a Master's degree in a related field plus 15 years of experience in water resources fields or a Bachelor’s degree in a related field plus 20 years of experience in water resources fields.

2. Principal Investigator (PI)

RESP: The PI will usually be the senior topic expert on the assigned task. The PI will design the approach for solving the problem and will oversee the execution of the study, providing advice and guidance as necessary. It is expected that the PI with the most expertise in the required discipline will work on that task, e.g., a task requiring expertise in economics should be headed by a PI with a background in economics.

MQ: The PI shall have a PhD in a discipline** that is closely related to the water resources fields, plus 3 years of experience in these fields, 2 of which must have been at a level of responsibility equivalent to the senior analysts or PI level. In lieu of the PhD, the PI may substitute a Master’s degree in a related field plus 5 years of experience in water resources fields, 3 years at the PI level. Similarly, a Bachelor’s degree in a related field plus 8 years of experience in water resources fields, 3 years at the PI level meets the minimum qualifications.

3. Senior Analysts (SA)

RESP: The SA will work closely with the PI in developing the approach for solving the problem. The SA will then be the study manager in charge of carrying out the technical aspects of the study. The SA will normally design and perform any analysis of data and draw conclusions.

MQ: The SA shall have a PhD in a discipline that is closely related to these fields, plus 2 years of experience in water resources fields, or a Master’s degree in a related field plus 3 years of experience or a Bachelor’s degree in a related field plus 4 years of experience.

4. Project Manager/Administrator (PM)

RESP: The PA will ensure that the firm has all of the necessary resources available for carrying out an assigned task, including material supplies as well as personnel. The PA will also ensure that work progresses in a timely manner and that schedules are met. When schedules cannot be met, the PA will be responsible for notifying the Contracting Officer or the Contracting Officers Representative and requesting an extension.

MQ: The PM shall have a Master’s degree in Management or a water resources related field plus 3 years of experience, 2 of which must have been at the PA level or a Bachelor’s degree in Management or a water resources related field plus 5 years of experience conducting such studies as will be derived from this contract, 3 of which must have been at the PA level.

5. Programmer/Analysts(P/A)

RESP: The P/A will be responsible for modifying existing computer software or developing new programs to perform various kinds of analysis as directed by the PI and or the SA for the task.

MQ: The P/A shall have a minimum of 5 years’ experience in developing and writing computer software applications, and two years of this experience in water resources related fields.

6. Mid-Level Analyst (MA)

RESP: The MA will work closely with the SA in conducting the analysis of data and drawing conclusions. The MA will also work closely with SA to write-up the results of the study and to prepare any summary of findings and recommendations.

MQ: The MA shall have a Master’s Degree in a field related to water resources plus 2 years of water resources related work or a Bachelor’s degree plus 3 years’ experience at the Research Assistant level.

7. Journeyman Analysts (JA)

RESP: The JA will work closely with the SA and MA in conducting the analysis of data and drawing conclusions. The JA will also work closely with SA/MA to write-up the results of the study and to prepare any summary of findings and recommendations.

MQ: The JA shall have a Master’s degree plus 1 year of experience at water resources related work or a Bachelor’s degree plus 2 years’ experience at the Research Assistant level.

8. Research Assistant (RA)

RESP: The RA will be responsible for gathering data through various sources and sorting out that data into segments that are more useful to the SA and PI. Data collection might consist of collecting original data through interviews, etc. or by use of the U. S. Census and other printed matter or computer files.

MQ: The RA shall have a minimum of a Master’s degree or a Bachelor’s degree with one year experience in water resources related fields.

9. Writer/Editor (W/E)

RESP: Some tasks will require a formal written report, to be completed and presented camera ready for publication. Often this will require the W/E to help write the report to make it more readable to the public. This might mean clarifying technical points so that the layman can understand what is being presented. The degree of simplicity required will be determined by the nature of the task.

MQ: The W/E shall have a Bachelor’s degree and a minimum of 5 years of experience in writing and editing reports and books for publication. One year of experience must be in a water resources related field.

10. Administrative/Clerical (A/C)

(**Water Resources related disciplines include: Civil and Environmental Engineering, Economics, Environmental Planning, Geography, Mathematics, Physical Sciences, Planning, and Sociology.)