AG-7604-S-17-0017.pdf

SEE ADDENDUMIS CHECKED

CODE 18a. PAYMENT WILL BE MADE BY

CODE

FACILITYCODE

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

OFFEROR

101 B SUN AVE NE

PAN AMERICAN BLDG SUITE 200

WO AQM IT SUPPORT BRANCH

USDA FOREST SERVICE

84JC CODE 16. ADMINISTERED BYCODE

X

X

511210

SIZE STANDARD:

% FOR:SET ASIDE:UNRESTRICTED OR7604

RFPIFB

10. THIS ACQUISITION ISCODE

RFQ

14. METHOD OF SOLICITATION

13b. RATING

NAICS:

SMALL BUSINESS

03/31/2017 1700 ET

03/15/2017

505-563-7379NICOLAS NUNEZ-HIDALGO

(No collect calls)

INFORMATION CALL:

FOR SOLICITATION 8. OFFER DUE DATE/LOCAL TIMEb. TELEPHONE NUMBER a. NAME

4. ORDER NUMBER3. AWARD/ 6. SOLICITATION

AG-7604-S-17-0017

5. SOLICITATION NUMBER

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS 1. REQUISITION NUMBER PAGE OF

1 63 844438OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30

ALBUQUERQUE NM 87109

TELEPHONE NO.

17a. CONTRACTOR/

SALT LAKE CITY UT 84119

2222 WEST 2300 SOUTH

GEOSPATIAL SERVICE AND TECH CENTER

USDA FOREST SERVICE

15. DELIVER TO

ALBUQUERQUE NM 87109

101 B SUN AVE NE

PAN AMERICAN BLDG SUITE 200

WO AQM IT SUPPORT BRANCH

9. ISSUED BY

7.

2. CONTRACT NO.

EFFECTIVE DATE

$38.50

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

ISSUE DATE

DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

11.

SEE SCHEDULE

12. DISCOUNT TERMS

THIS CONTRACT IS A

RATED ORDER UNDER

DPAS (15 CFR 700)

13a.

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

HUBZONE SMALL

BUSINESS

8(A)

USDA FOREST SERVICE

WOMEN-OWNED SMALL BUSINESS

(WOSB) ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

24.

AMOUNT

23.

UNIT PRICE

22.

UNIT

21.

QUANTITY

20.

SCHEDULE OF SUPPLIES/SERVICES

19.

ITEM NO.

Enterprise Image processing contract--RS cloud image processing This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in Federal Acquisition Regulation (FAR) Subpart 12.6, as supplemented with additional information included in this notice.

This solicitation document and incorporated provisions and clauses are those in effect through Federal Acquisition Circular (FAC) 2005-94, effective January 19, 2017. Provisions

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

HEREIN, IS ACCEPTED AS TO ITEMS:

X

XX

DATED

NICOLAS J. NUNEZ-HIDALGO

. YOUR OFFER ON SOLICITATION (BLOCK 5),

INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE SET FORTH

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND DELIVER

ARE

ARE

31c. DATE SIGNED

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

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

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

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

SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

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

26. TOTAL AWARD AMOUNT (For Govt. Use Only)

OFFER

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA - FAR (48 CFR) 53.212

ARE NOT ATTACHED.

ARE NOT ATTACHED.

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

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

30a. SIGNATURE OF OFFEROR/CONTRACTOR

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

25. ACCOUNTING AND APPROPRIATION DATA

29. AWARD OF CONTRACT:

REF.

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE

32c. DATE 32b. SIGNATURE OF AUTHORIZED GOVERNMENT REPRESENTATIVE

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

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

40. PAID BY39. S/R VOUCHER NUMBER38. S/R ACCOUNT NUMBER

37. CHECK NUMBER

FINALPARTIAL

36. PAYMENT

FINALPARTIAL

35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER33. SHIP NUMBER

COMPLETE

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

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

42b. RECEIVED AT (Location)

42a. RECEIVED BY (Print)

41c. DATE41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER

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

STANDARD FORM 1449 (REV. 2/2012) BACK

24.

AMOUNT

23.

UNIT PRICE

22.

UNIT

21.

QUANTITY

20.

SCHEDULE OF SUPPLIES/SERVICES

19.

ITEM NO.

and clauses incorporated by reference have the same force and effect as if they were given full text.

Please read the solicitation in its entirety.

Questions must be submitted in writing to contracting Officer Nicolas Nunez-Hidalgo via email

At nnunezhidalgo@fs.fed.us. By 3:00 PM EST March

22, 2017.

All proposal must be submitted via email to the contracting officer by 5:00pm EST. March 31st, Please provide pricing structure separate from technical proposal.

IMPORTANT NOTICE TO CONTRACTORS: All prospective awardees are required to have an active SAM registration at time of quote submission and are required to maintain active registration during the life of the contract. SAM can be accessed at https://www.sam.gov.

Enterprise Image processing contract--RS cloud image processing

Continued ...

32f. TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT REPRESENTATIVE

63 2 of

ITEM NO. SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

NAME OF OFFEROR OR CONTRACTOR

3 63

CONTINUATION SHEET

REFERENCE NO. OF DOCUMENT BEING CONTINUED PAGE OF

(A) (B) (C) (D) (E) (F)

AG-7604-S-17-0017

NSN 7540-01-152-8067 OPTIONAL FORM 336 (4-86)

Sponsored by GSA

FAR (48 CFR) 53.110

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 CONTRACT ADMINISTRATION DATA

(continuation from Standard Form 1449, block 18A.)

1. Contract Administration: All contract administration matters will be handled by the following individuals:

a. CONTRACTOR: (Offerors are requested to designate a point of contact for prompt contract administration).

Name:

Title:

Name of Company:

Street Address:

City, State, Zip Code:

Email:

Phone:

Fax:

Tax ID:

GSA/FSS Contract Number:

b. GOVERNMENT: Contracting Officer:

Nicolas Nunez-Hidalgo 505-563-7379 Forest Service

Washington Office AQM Management IT Support Branch p: 505-563-7379 f: 505-563-7788 nnunezhidalgo@fs.fed.us

101 B Sun Ave. N.E. Suite 120 Albuquerque, NM 87109 www.fs.fed.us

2. CONTRACTOR REMITTANCE ADDRESS: All payments by the Government to the contractor should be mailed to the following address:

3. INVOICES: Invoices shall be submitted in arrears:

a. Quarterly []

b. Semi-Annually []

c. Other [X]

4. GOVERNMENT INVOICE ADDRESS:

www.ipp.gov mailto:nnunezhidalgo@fs.fed.us http://www.fs.fed.us/

ACKNOWLEDGMENT OF AMENDMENTS: The offeror acknowledges receipt of amendments to the Solicitation numbered and dated as follows:

AMENDMENT NO DATE

Performance Work Statement Technical Requirements – USDA Forest Service Cloud-based Remote Sensing Image Processing

Platform

1.0 Background

The USDA Forest Service (USFS) administers nearly 200 million acres of public land. The agency relies upon passive aerial and satellite-based remote sensing data and systems to gather resource information. Remotely sensed imagery is a critical source of resource information within the agency.

The USFS requests proposals from interested parties for a cloud-based remote sensing image processing platform. This Request for Proposal (RFP), submitted by the USFS Geospatial Technology and Applications Center (GTAC), seeks comprehensive industry responses on their current capabilities to address the functional business requirements.

There are several program staffs in the Forest Service that are interested in using a large scale cloud image processing platform at a production level. These groups include: the Geospatial Technology Application Center, Forest Health Technology and Enterprise Team, Forest Inventory and Analysis research staff, and several regional remote sensing geospatial staff groups.

2.0 Scope and Objectives

The USFS is seeking proposals for a cloud-based remote sensing image processing platform. The USFS has previously beta-tested a platform for operational requirements and is now interested in seeking a short-term (e.g., one base year plus four one-year options) paid-for agreement to use a platform with these capabilities. The agreement will be viewed as a pilot for which the USFS can better get a clear understanding of its business need and vendor capabilities. For this pilot agreement, the USFS is not looking to pay to have the platform built – all vendors must meet requirements with a system they currently have set up. Interested parties will need to address the following requirements as described in this document.

3.0 Functional Business Requirements

Respondents must address the functional requirements for storage, access, processing, and dissemination as described. The vendor should provide information regarding performance limitations of such a system (e.g., methods for upload, data transfer rates, storage capacity, etc.). Items in this section marked with “*” indicate desired features and not requirements.

1. Storage—the platform should have, in its archive, global (where possible) coverage of a broad expanse of earth observation and terrain data at various spatial resolutions. For example:

• High Spatial Resolution Imagery o NAIP: The platform should include all available NAIP image collections (RGB and NIR).

o *Other: The platform should provide other high-resolution image offerings, such as Planet, or similar, as they become freely available.

• Moderate Spatial Resolution Imagery o Landsat: The platform should mirror the archive available from USGS-EROS (Landsat 4 – 8 covering the years 1984 – present). Offerings should include L1T, atmospheric reflectance, and surface reflectance versions of the images.

o Sentinel: The platform should include all available Sentinel 2 imagery.

• Coarse Spatial Resolution Imagery o MODIS: The platform should include daily imagery, 16-day BRDF-adjusted surface reflectance, and a variety of other MODIS-derived products.

o The platform should have the ability to ingest other similar datasets, such as VIIRS.

• Other Data o Climate and Weather: The platform should include a variety of global climate and weather layers, such as:

PRISM

Daymet

GRIDMET

*SSURGO, GFS, NEX-DCP30, and others.

o Topographic: The platform should include elevation models such as the USGS NED (all scales) and SRTM layers.

o Landcover: The platform should include the NLCD suite of products, including the tree canopy cover layer.

o *Crops: The platform should include to any available crop layers, such as the USDA NASS Cropland Data Layer.

o User-created: The platform should include other user-created data layers representing topics of global interest, such as the Global Forest Change layer (High-Resolution Global Maps of 21st-Century Forest Cover Change, Hansen and others, Science, 15 Nov. 2013 :

850-853; http://science.sciencemag.org/content/342/6160/850.full).

o *The platform should provide the ability for users to process data that they upload. For example, if a user procures or creates a raster dataset (e.g., National Insect and Disease Risk Map [NIDRM], they should be able to upload those data and use the server-side processing capabilities of the platform to analyze the data. These data can remain privately accessed by the user and not shared with other platform users to alleviate commercial or government licensing concerns.

2. Access—the processing capabilities should have immediate or online access to the data layers and similar as outlined in the Storage section. Access could be offered through a graphical user interface similar to other GIS software packages, or through a code-based application program interface (API).

3. Custom Processing—the platform should provide custom server-side processing abilities to analyze data at local, continent, and global scales using both internal and user-supplied scripts or tools. The end user should access the processing platform from a web-enabled browser or interface. The only client-side processing required is the API coding or human interaction through a graphical user interface.

4. Dissemination—the platform should allow users to export data in formats generally accepted in the geospatial industry (e.g., tagged image file format [TIFF]) for use in other GIS or image processing software packages such as QGIS, ArcGIS, ERDAS Imagine, or ENVI. In addition, the platform should allow users to export only the data they need within their area of interest.

3.1 Evaluation Criteria

General The Government will accept the offer(s) that represent the best value. Proposals will be objectively evaluated using a performance/cost trade-off method. The Government’s selection will be based on the following factors, listed in descending order of importance: 1) technical evaluation/performance, 2) cost, and 3) past performance.

IAW FAR 52.212-2 –Evaluation—Commercial Items. (Oct 2014) Price is less important than Technical Performance and Past Performance when combined. Options-The Government will evaluate offers for award purposes by adding the total price for all options to the total price for the basic requirement. The Government may determine that an offer is unacceptable if the option prices are significantly unbalanced. Evaluation of options shall not obligate the Government to exercise the option(s).

Offers that include technical capabilities that exceed the minimum technical requirements specified in the Functional Business Requirements will be evaluated based on a performance/cost trade-off. The method of evaluation for each of these factors is described in detail in the Basis for Award section.

Basis for Award Each proposed solution will be evaluated as outlined above. The final award decision will be based on a determination of the overall best value.

Factor 1: Technical Evaluation/Performance There are two phases to the technical evaluation. All offerors submit the written report which will be reviewed in Phase 1. Phase 2 of the technical evaluation requires the offerors to demonstrate the capabilities of their platform by webinar. The top candidates from Phase 1 will be further evaluated in Phase 2. Each of these Phases is described below.

PHASE 1 – WRITTEN REPORT

DELIVERABLE

Phase 1 requires offerors to submit a written report describing capabilities. The written report response to this RFP must be no more than 50 pages in length inclusive of text, graphics, tables, appendices, and figures. The cover page and table of contents are included in the 50 page count. Any material submitted in excess of the 50-page limit and the page limitation exclusions will not be considered. Font size within the response shall be no smaller than 11 point. Font face shall be Arial, Calibri, or Times Roman.

Content should clearly describe the capabilities of the software to meet all core Functional Business Requirements listed in the previous section. The submission must provide sufficient detail and clarity to communicate capabilities of the software in order to insure an effective assessment and evaluation.

EVALUATION CRITERIA

Upon receiving the written proposal, the USFS team of remote sensing specialists will evaluate the platform for the Functional Business Requirement capabilities using the rating system found in table 1.

All criteria will be assessed based on information provided in the written report.

Table 1 Rating system used to evaluate written proposal

Rating Description Exceptional Meets the specified evaluation criteria and exceeds specified minimum criteria in a way beneficial to the Government. A report must have no deficiencies and at least one “exceeds criteria” to receive an exceptional rating.

Acceptable Meets the specified minimum evaluation criteria. A report must have no deficiencies to receive an acceptable rating.

Marginal There is doubt regarding whether an aspect of the report meets a specified minimum evaluation criteria, but any such uncertainty is correctable.

Unacceptable Fails to meet specified minimum evaluation criteria. The report has one or more deficiencies and is not awardable.

Those offerors that rate exceptional or acceptable for all evaluation criteria will be considered for Phase

2. Offerors with more than one marginal or any unacceptable rating will not advance to Phase 2.

Offerors with a single marginal rating may be considered for Phase 2. If all of the offers have more than one marginal, the top 3 will be selected.

PHASE 2 – DEMONSTRATION OF CAPABILITIES

DELIVERABLE

The respondents that are selected for Phase 2 will be required to demonstrate the capabilities of their platform by providing live demonstrations (this will be via webinar or as otherwise determined by mutual agreement between the offeror and originator) of usage of the platform to address the following topics of interest by the USFS:

Table 2 Offeror will demonstrate platform capabilities to address the listed topics

Topic Description Geospatial Inputs

Analytical Methods Involved

Output to be Delivered to Government

Mapping Develop a cloud-free, 30m resolution composite image of the Chugach

Landsat images (multiple observations for multiple WRS2 path/rows)

--Develop cloud and shadow masks for each of the Landsat images --Image compositing using median per pixel

Raster cloud and shadow-free image composite of the entire Chugach

National Forest, Alaska technique in masked areas

National Forest at 30m resolution

Classification / Mapping

Develop a raster GIS map based on a mid-resolution composite image for an area larger than one Landsat WRS2 path/row.

Using a TBD statistical model and training data collected from high resolution imagery create a raster map of a continuous variable (e.g., TCC).

--Landsat images (multiple observations for multiple WRS2 path/rows) --Training data (spatially-enabled table representing tree canopy cover within a discrete areal unit) provided by the Government.

--Image compositing using median per pixel technique --Predictor data extraction from composite image Statistical modeling of continuous variable --Application of model back to median composite image

Raster GIS map of a continuous variable

Monitoring / Change Detection

Replicate the z- Score analysis used in the

MODIS RTFD

project. This involves creating the baseline composite image.

MODIS 8-day composite images for the three years prior to the analysis year

Image algebra median compositing of baseline imagery

Median composite MODIS image from a defined compositing period

The live demonstrations will serve two main purposes: 1) to familiarize the USFS team with the tool layout, capabilities, and, if applicable, general workflow, and; 2) to allow the USFS team to get an in-depth sense and understanding of the ease of use and functionality. Each offeror will be given 3 hours of time to demonstrate. Any necessary training data or documentation of algorithms required to complete these demonstrations will be provided by the Government via the USDA cloud-based data sharing platform, CloudVault.

EVALUATION CRITERIA

The evaluation for Phase 2 deliverables will include the following criteria (see rating system in table below):

1. Layout of the platform tools and user interface (i.e., is the platform intuitive and user friendly?).

2. Functional comprehensiveness (i.e., what are the range of options available to the user when using the platform? Does the platform provide users maximum flexibility to produce desired outputs?) This rating will be evaluated for each core requirement with a summarized overall rating as well).

3. Help and documentation (i.e., are there clear sets of instructions to use the platform? How robust is the help documentation, and can it be accessed from the tools? Are tutorial data and instructions available?).

These criteria will be qualitatively evaluated by a team of experts and rated relative to other offers.

Table 3 Rating criteria used for demonstrations

Rating Description Exceptional Demonstrated software performed at the highest level as compared with other evaluated software.

Acceptable Demonstrated software performed acceptably, but, not at the exceptional level.

Marginal There is doubt regarding whether the demonstrated software meets a specified minimum performance or capability requirements, but any such uncertainty is correctable.

Unacceptable The demonstrated software performed at the lowest level as compared with other evaluated software.

Factor 2: Cost In addition to the Phase 2 Evaluation criteria, cost will be considered in the award decision. Proposals will be analyzed to assess best value to the Government, considering a cost/performance technical trade-off methodology. This may mean that the Government may award to other than the lowest-cost proposal.

Factor 3: Past Performance

DELIVERABLE

Each offeror will need to provide written descriptions of relevant experience as it relates to the technical requirements of the contract.

EVALUATION

The Government will evaluate the relevant merits of each vendor’s past performances. Any lack of relevant or recent (last 5 years) past performance record will result in a rating of neutral. The Government may review some or all of the following in its evaluation of past performance:

Quality of Service Timeliness of Performance Customer Satisfaction (current and former customers)

In evaluating past performance, the Government may also consider information provided by vendors in their proposal submissions, as well as any other information available to the Government. All vendors will be required to submit past performance references which will require 3-5 examples of prior, and recent (within the last 5 years) contracts that they have performed, including a customer/Government point of contact who can be contacted to validate performance.

4.0 Platform Licensing / Pricing Structure

The vendor needs to define a pricing structure that reflects how up to 40 simultaneous USFS users would have access to the platform. The vendor needs to outline all costs incurred by the Government in accessing any of the capabilities of the proposed system. At a minimum, the vendor needs to define or suggest a pricing structure for the following:

1. Upload and Access to Stored or Derived Data

• Cost per GB per month of personal storage space at varying frequencies of access?

2. Access and Processing

• Cost per query? Cost per GB of data/code interaction? Cost of testing vs. production environment? (For example, how would we be billed for testing or developing algorithms vs. actual production toward a final product?)

3. Dissemination

• Cost per map? Cost per click?

5.0 Method of Evaluation

For all RFPs, the Government will accept the offer(s) that represent the best value. Proposals will be objectively evaluated using a performance/cost trade-off method. The Government’s selection will be based on the following factors, listed in descending order of importance: 1) technical capability/performance is more important than 2) cost and 3) past performance when combined.

Offers that include technical capabilities that exceed the minimum technical requirements specified in the Functional Business Requirements will be evaluated based on a performance/cost trade-off. The method of evaluation for each of these factors is described in detail in the Basis for Award section.

6.0 IPv6 requirements

(a) Any system, hardware, software, firmware or networked component (voice, video or data) developed, procured or acquired in support or performance of this contract shall be capable of transmitting, receiving, processing, forwarding and storing digital information across system boundaries utilizing system packets that are formatted in accordance with commercial standards of Internet Protocol (IP) version 6 (IPv6) as set forth in the USGv6 Profile (NIST Special Publication 500-267) and corresponding declarations of conformance defined in the USGv6 Test Program. In addition, this system shall maintain interoperability with IPv4 systems and provide at least the same level of performance and reliability capabilities of IPv4 products:

(b) Specifically, any new IP product or system developed, acquired, or produced must:

1) Interoperate with both IPv6 and IPv4 systems and products, and

2) Have available contractor/vendor IPv6 technical support for development and implementation and fielded product management.

(c) As IPv6 evolves, the Contractor commits to upgrading or providing an appropriate migration path for each item developed, delivered or utilized at no additional cost to the Government.

(d) The Contractor shall provide technical support for both IPv4 and IPv6.

(e) Any system or software must be able to operate on networks supporting IPv4, IPv6 or one that supports both.

(f) Any product whose non-compliance is discovered and made known to the Contractor within one year after acceptance shall be upgraded, modified or replaced to bring it into compliance at no additional cost to the Government.

7.0 Contractual Requirements:

PART 1

Administrative Matters

7.1 The Period of Performance:

Base Year: May 1, 2017 to April 30, 2018 Option 1: May 1, 2018 to April 30, 2019 Option 2: May 1, 2019 to April 30, 2020

7.2 Acceptance of Security Requirements: By accepting this contract/agreement, the Contractor/Cooperator and other external organizations (hereafter called Contractor) providing Information Technology (IT) services to the US Forest Service (FS) agrees to comply with the applicable IT security policy as outlined in this document, the solicitation, and resultant contract. The Contractor and other external organizations will be responsible for IT security for all systems connected to the FS network or operated by the Contractor and other external organizations for the FS, regardless of location. The term 'information technology', as used in this clause, means any equipment or interconnected system or subsystem of equipment, that is used in the automatic acquisition, storage, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data or information. This includes both major applications and general support systems as defined by OMB Circular A-130.

7.3 Protection: The Contractor shall be responsible for properly protecting all information used, gathered, or developed as a result of work under this task. The Contractor shall also protect all unclassified Government data, equipment, etc., by treating information as sensitive business, confidential information, controlling and limiting access to the information, and ensuring the data and equipment are secured within their facility.

7.4 Non-Disclosure: The Contractor or other external organization will not publish or disclose in any manner, without the FS Contracting Officer's written consent, the details of any programs, documentation, data, or safeguards either designed or developed by the Contractor or other external organization under this Contract or otherwise provided by the Government. Contractor may be required to sign non-disclosure agreement. A written agreement between the FS and any contractors and other external organizations will be entered into before FS data and information otherwise exempt from public disclosure may be disclosed to the contractors and other external organizations. The contractor and other external organizations will agree to establish and follow security precautions considered by the FS to be necessary to ensure proper handling of data and information. As may be identified elsewhere in this contract, the Contractor agrees that:

7.5 Documentation Ownership: The draft and final deliverables and all associated working papers and other materials deemed relevant by the COTR that have been generated by the Contractor in the performance of this contract are the property of the U.S. Government and must be submitted to the COTR at the conclusion of the tasks to include concept of operations

(CONOPS).

7.6 Document Reproduction: Documents produced for this project are the property of the U.S.

Government and cannot be reproduced or retained by the Contractor.

7.7 Contractor Cooperation with Federal Agencies: To the extent required to carry out a program of inspection to safeguard against threats and hazards to the security, integrity, and confidentiality of Government data, the Contractor will afford the Government access to the Contractor's or other external organization's facilities, installations, technical capabilities, operations, documentation, records, and databases. The Contractor will cooperate with Federal agencies and their officially credentialed representatives during official inspections or investigations concerning the protection of FS information. Cooperation may include providing relevant documentation showing proof of compliance with federal and agency requirements, and rendering other assistance as deemed necessary.

7.8 Threats or Hazards: If new or unanticipated threats or hazards are discovered by either the Government or the Contractor or other external organization, or if existing safeguards have ceased to function, the discoverer will immediately bring the situation to the attention of the other party.

The Contractor will report real or suspected incidents or violations to the FS Computer Incident Response Team (CIRT), by e-mail, at CIRT@fs.fed.us.

7.9 Subcontractor: The Contractor shall insert these clauses in all subcontracts when the subcontractor is required to have routine physical access to a Federally-controlled facility and/or routine access to a Federally-controlled information system. Failure to comply with said requirements will constitute cause for termination.

The Contractor Agrees To –

(a) Comply with the Privacy Act of 1974 (the Act) and the agency rules and regulations issued under the Act in the design, development, or operation of any system of records on individuals to accomplish an agency function when the contract specifically identifies—

(i) The systems of records; and

(ii) The design, development, or operation work that the contractor is to perform;

(b) Include the Act notification contained in this contract in every solicitation and resulting subcontract and in every subcontract awarded without a solicitation, when the work statement in the proposed subcontract requires the redesign, development, or operation of a system of records on individuals that is subject to the Act; and

(c) Include this clause, including this paragraph (3), in all subcontracts awarded under this contract which requires the design, development, or operation of such a system of records.

In the event of violations of the Act, a civil action may be brought against the agency involved when the violation concerns the design, development, or operation of a system of records on individuals to accomplish an agency function, and criminal penalties may be imposed upon the officers or employees of the agency when the violation concerns the operation of a system of records on individuals to accomplish an agency function. For purposes of the Act, when the mailto:CIRT@fs.fed.us contract is for the operation of a system of records on individuals to accomplish an agency function, the Contractor is considered to be an employee of the agency.

Definitions of the clause:

(a) “Operation of a system of records,” as used in this clause, means performance of any of the activities associated with maintaining the system of records, including the collection, use, and dissemination of records.

(b) “Record,” as used in this clause, means any item, collection, or grouping of information about an individual that is maintained by an agency, including, but not limited to, education, financial transactions, medical history, and criminal or employment history and that contains the person’s name, or the identifying number, symbol, or other identifying particular assigned to the individual, such as a fingerprint or voiceprint or a photograph.

(c) “System of records on individuals,” as used in this clause, means a group of any records under the control of any agency from which information is retrieved by the name of the individual or by some identifying number, symbol, or other identifying particular assigned to the individual.

The contractors and other external organizations will ensure that the following banner is displayed on all FS systems that contain Privacy Act information operated by the contractors and other external organizations prior to allowing anyone access to the system:

“This system contains information protected under the provisions of the privacy act of 1974 (public law 93-579). Any privacy information displayed on the screen or printed must be protected from unauthorized disclosure. Employees who violate privacy safeguards may be subject to disciplinary actions, a fine of up to $5,000, or both.”

7.10 If your contract/agreement is bringing on contractors/cooperators that need building access and/or computer access:

7.11 IT Security Training: The Contractor and other external organizations will ensure that its employees performing under this contract fulfill all Forest Service requirements for mandatory security awareness and role-based advanced security training in accordance with OMB Circular A-130, FISMA, and NIST requirements, and sign all applicable FS statements of responsibilities.

7.12 Background Investigations: All non-government employees with unescorted access to FS facilities, computer systems and/or FS information must have background investigations commensurate with the level of risk and magnitude of loss or harm. The FS will determine the level of background investigation and position classification needed.

7.13 Personal Identity Verification of Contractor Personnel: The Contractor shall be responsible for ensuring compliance by its employees with all applicable federal regulations, to include those of GSA, NIST, USDA, FS and HSPD-12. Contractors and their employees are subject to all Federal laws applicable to Government installations and are under the jurisdiction of the Federal Protective Service (FPS). The Contracting Officer Representatives (CORs; also known as Contracting Officer Technical Representatives), or other designated program/project officers, in conjunction with the FS HCM HSPD-12 staff, will assist the Contractor in processing the required Security Background Investigations/Clearances.

(1) The contractor shall comply with the personal identity verification (PIV) policies and procedures established by Department of Agriculture (USDA) Directives 3800 series.

(2) Should the results of the PIV process require the exclusion of a contractor's employee(s), the contracting officer will notify the contractor in writing.

(3) The contractor must appoint a representative to manage this activity and to maintain a list of employees eligible for a USDA PIV ID Badge required for performance of the work.

(4) The responsibility of maintaining a sufficient workforce remains with the contractor.

Employees may be barred by the Government from performance of the work should they be found ineligible or to have lost eligibility for a USDA PIV ID Badge. Failure to maintain a sufficient workforce of employees eligible for a USDA PIV ID Badge may be grounds for termination of the contract.

(5) The contractor shall insert this clause in all subcontracts when the subcontractor is required to have access to a federally-controlled facility or information system.

(6) The PIV Sponsor for this contract is the contracting officer representative (COR), unless otherwise specified in this contract. The PIV Sponsor will be available to receive contractor identity information from 8:00AM-6:00PM, Monday-Friday at 1400 Independence Avenue SW, Washington, DC 20250. The Government shall notify the contractor if there is a change in the PIV Sponsor, the office address, or the office hours for registration.

(7) At this time, the Government will pay for and process all required security investigations/clearances, except as identified differently within this clause.

(8) The Contractor should be aware of any of its employees possibly having had a background investigation through another government agency. The investigation that was conducted, if verifiable by the FS HSPD-12 staff and, if it was completed within the last 5 years, can be accepted by the Government in lieu of a background check.

(9) The Contractor shall comply with any facility badging requirements for the issuance of building access, badges, etc.:

a. Badging: Ensure that each of the Contractor's employees has been issued either a temporary or permanent badge from the Government. A permanent badge will not be issued until the security questionnaire has been completed and favorably reviewed. Temporary or visitor badges will be provided for persons who are identified as having an infrequent or temporary legitimate business need for access to the site. As noted above, periods that exceed 180 days will require a permanent badge. The badge must be worn at all times while in the facility. It must be displayed above the waist. The individual will retain possession of the badge as long as continued admittance to the site is needed.

b. Ensure the safekeeping, wearing, and visibility of Government furnished badges.

c. Immediately return all badges and permits to the Government when such need ceases to exist.

(10) The Contractor shall comply with any facility security requirements for access to the facility.

(11) The Contractor shall comply with all applicable rules governing parking at USDA locations.

7.14 Acquired Software Applications: If your contract or agreement will acquire and/or implement software applications:

1. Secure Coding Skills: Contractor certifies that at least one member of each programming team working on any code (including C, Java, .Net, ASP.NET, Visual Basic) to be delivered to the Forest Service has earned the Global Information Assurance Certification for Secured Software Programming or equivalent.

2. Source code testing, binary code testing, application scanning, and penetration testing: At least one week prior to delivery of any code due under this contract, Contractor will deliver to the COTR the following reports covering all code that will be delivered:

a. Source code testing results showing all potential security flaws identified by at least one of the commercial source code testing tools approved by the Office of the Chief Information Officer of USDA. On the report, the contractor will highlight all vulnerabilities rated "critical" and "high". The contractor must then correct the vulnerabilities, resend the code and ensure delivered source code health.

b. For web-applications, web application scanning test results showing ail potential security flaws identified by at least one of the commercial web application scanning tools approved by the Office of the Chief Information Officer of USDA. On the report, the contractor will highlight all vulnerabilities rated "critical" and "high".

c. For all applications: application penetration results.

3. Copyright Management and Responsibility: By delivering applications or programming code to the Federal Government, the vendor or Contractor certifies that they have the proper authority to transfer the property and will defend the government against copyright or other lawsuit resulting from the application or programming delivered.

4. Ownership/Copyright: Any software, produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the contractor without written permission from the Contracting Officer. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

5. Data Rights: The Government has unlimited rights to all documents/material produced under this contract. All documents and materials, to include the source codes of any software, produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the contractor without written permission from the Contracting Officer. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

6. IT Hardware/Software: The Contractor and other external organizations will ensure that the appropriate security banners are displayed on all FS systems (both public and private) operated by the contractors and other external organizations prior to allowing anyone access to the system.

http://asp.net/

The Contractors and other external organizations will submit proof to the Contracting Officer that hardware and/or software products acquired as a part of any contract/agreement are appropriate to their risk environment, and will confirm the proof of information assurance showing a cost-effective selection of security measures with appropriate security specifications and requirements.

7.15 Section 508 Compliance for IT Services, Hardware, Software, and Equipment: All electronic and information technology (EIT) procured through this Statement of Work/Bill of Materials and any resulting contract, task orders, delivery order, or purchase order must meet the applicable accessibility standards at 36CFR 1194, unless an agency exception to this requirement exists. 36 CFR 1194 implements Section 508 of the Rehabilitation Act of 1973, as amended, and is viewable at http://www.section508.gov/. The contractor shall indicate for each line item in the schedule whether each product or service is compliant or noncompliant with the accessibility standards at 36 CFR 1194. Further, the proposal must indicate where full details or compliance can be found (e.g., vendor’s website or other exact location). The Technical Exhibit 5 with GPAT Checklist that shall be completed and submitted by the contractor with the POSS Proposal.

7.16 Special Qualifications: None.

7.17 Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The contracting officer, Contracting Officers Representative (COR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the contracting officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

7.18 Contracting Officer Representative (COR) and Contracting Officer Technical Representative (COTR): The COR is:

Dave Vanderzanden phone 801-975-3753 email at dvanderzanden@fs.fed.us

The COTR monitors all technical aspects of the contract and assists the CO and COR in contract administration. The COTR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract: perform inspections necessary in connection with contract performance: maintain written and oral communications with the Contractor concerning technical aspects of the contract: issue written interpretations of technical requirements to the Contracting Officer, including Government drawings, designs, specifications:

monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting contract or order.

mailto:dvanderzanden@fs.fed.us

7.19 Contractor Manager: The contractor shall provide a contractor manager or lead who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the contractor when the manager is absent shall be designated in writing to the contracting officer. The contractor manager or alternate shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract.

Contracting Officer (CO): The (CO) is identified below:

Nicolas Nunez-Hidalgo 101 B Sun Ave N.E. Suite 120 Albuquerque, NM 87109

7.20 Identification of Contractor Employees: All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed. Contractor personnel will not be required to obtain and wear contractor badges in the performance of this service.

PART 2

DEFINITIONS & ACRONYMS

Contracting Officer’s Representative (COR): A representative from the requiring activity assigned by the Contracting Officer to perform surveillance and to act as liaison to the contractor.

Defective Service. A service output that does not meet the standard of performance associated with it in the Technical Requirements.

Quality Assurance Surveillance Plan (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

Quality Control. Those actions taken by a contractor to control the performance of services so that they meet the Technical requirements.

Quality Assurance. Those actions taken by the government to assure services meet the requirements of the Performance Work Statement.

ACRONYMS:

AGAR Agriculture Acquisition Regulation COR Contracting Officer Representative COTR Contracting Officer's Technical Representative

FAR Federal Acquisition Regulation FS Forest Service FFP Firm Fixed Price OCI Organizational Conflict of Interest CONUS Continental United States (includes Alaska and Hawaii) POC Point of Contact PM Program Manager PRS Performance Requirement Summary PWS Performance Work Statement QA Quality Assurance QAP Quality Assurance Program QASP Quality Assurance Surveillance Plan QC Quality Control QCP Quality Control Program TE Technical Exhibit USDA United States Department of Agriculture

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3.1 GENERAL: The government shall provide, the facilities, equipment, materials, and/or services listed below.

3.2 Equipment: None.

3.3 Services: None.

3.3.1 Utilities: None.

3.4 Facilities: None.

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4.1 General: Except for those items specifically stated to be government furnished in Part 3, the contractor shall furnish everything required to perform this requirement.

PART 5

APPLICABLE PUBLICATIONS

5.0 Publications applicable to this Technical Requirement document are listed below:

• Public Law 107-347, Federal Information Security Management Act of 2002, (FISMA)

– http://csrc.nist.gov/drivers/documents/FISMA-final.pdf https://mail.usda.gov/owa/redir.aspx?C=d88GCd6Z_0qrwFStmCcvaTzb9eXnSc8IqrhO9vhJmK5lQdgN_OJnQIqGNIEhrKalCK-Bumd2odg.&URL=http%3a%2f%2fcsrc.nist.gov%2fdrivers%2fdocuments%2fFISMA-final.pdf

• Public Law 99-474, Computer Fraud and Abuse Act of 1986, (18 USC 1030) – http://energy.gov/sites/prod/files/cioprod/documents/ComputerFraud- AbuseAct.pdf

• Public Law 93-574, Privacy Act of 1974, (5 USC 552a) – http://www.foia.cia.gov/txt/pa.pdf

• Public Law No: 107-347, E-Government Act of 2002 (H.R. 2458/S. 803) – http://www.gpo.gov/fdsys/pkg/PLAW-107publ347/pdf/PLAW-107publ347.pdf

• FIPS PUB 199, Security Categorization of Federal Information and Information Systems – http://csrc.nist.gov/publications/fips/fips199/FIPS-PUB-199-final.pdf

• OMB Circular A-123 (revised), Management Accountability and Control – http://www.whitehouse.gov/sites/default/files/omb/assets/omb/circulars/a123/a 123_rev.pdf

• OMB Circular A-130 (revised), Information Resources Management, Appendix III, Security of Federal Automated Information Resources – http://www.whitehouse.gov/sites/default/files/omb/assets/omb/circulars/a130/a 130trans4.pdf

• Public Law 93-502, Freedom of Information Act – http://www.justice.gov/oip/1974attachb.htm

• NIST SP 800-18, Rev. 1 Guide for Developing Security Plans for Information Technology Systems – http://csrc.nist.gov/publications/nistpubs/800-18- Rev1/sp800-18-Rev1-final.pdf

• NIST SP 800-30, Risk Assessment Guide for Information Technology Systems – http://csrc.nist.gov/publications/nistpubs/800-30/sp800-30.pdf

• NIST SP 800-60, Guide for Mapping Types of Information and Information Systems to Security Categories, Rev. 1 – http://csrc.nist.gov/publications/nistpubs/800-60-rev1/SP800-60_Vol1-Rev1.pdf

• NIST SP 800-53, Recommended Security Controls for Federal Information Systems and Organizations, Rev. 3 – http://csrc.nist.gov/publications/nistpubs/800-53- Rev3/sp800-53-rev3-final_updated-errata_05-01-2010.pdf

• Check Clearing for the 21st Century Act of 2003 – http://www.gpo.gov/fdsys/pkg/PLAW-108publ100/pdf/PLAW-108publ100.pdf

• USDA Certification and Accreditation Guide – http://www.ocio.usda.gov/directives/doc/DM3555-000.pdf

• USDA DM 3140-001, Management ADP Security Manual – http://www.ocio.usda.gov/directives/doc/DM3140-001.pdf

• USDA DR 3140-002, USDA Internet Security Policy – http://www.ocio.usda.gov/directives/doc/DR3140-002.pdf

• USDA DR 3300-001, Telecommunications and Internet Services and Use Memorandum Telecommunications and Internet Services and Use Memorandum – http://www.ocio.usda.gov/directives/doc/DR3300-001.pdf

• USDA DR 3440-002, Control and Protection of Sensitive Security Information – http://www.ocio.usda.gov/directives/doc/DR3440-002.pdf

• USDA DR 3500-000, USDA…