A21_-_Appendix_A_-_PWS_RIBITS.pdf

PDF 137 KB Posted

Attached to
Regulatory In-lieu fee and Bank Information Tracking System (RIBITS)
Solicitation number
W912HQ19R0002
Issued by

About this file

Performance Work Statement

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Performance Work Statement RIBITS Support Services

1. BACKGROUND

RIBITS (Regulatory In-lieu fee and Bank Information Tracking System) is an Oracle-based web application used to track mitigation bank and in-lieu fee (ILF) program operations for Corps Districts and other partners including the U.S. Fish and Wildlife Service (USFWS), National Marine Fisheries Service (NMFS), Federal Highways Administration (FHwA), U.S Department of Agriculture (USDA), and the Environmental Protection Agency (EPA). RIBITS was implemented nationally as a tool to track 3rd party mitigation (mitigation banks & in-lieu fee programs) beginning in 2007. It has been in production mode since 2011.

RIBITS provides users (Corps regulators, state and federal agencies, mitigation bank and ILF program sponsors, and the general public) with comprehensive information on 3rd party mitigation operations including provider contact information, credit ledgers, credit availability (including wetland, stream, and species credits), geographic service areas, bank and ILF program documentation, reports and queries, and information on national, regional, and local compensatory mitigation policy and practices. RIBITS currently resides on an outward-facing Corps server located on the Army Corps of Engineers IT (ACE-IT) De-Militarized Zone (DMZ) but is expected to be migrated to a cloud computing environment (Amazon Web Services) by the end of 2019. RIBITS provides structured data on mitigation banks and ILF programs (name location, service area, status, credit availability, etc.) in response to real time queries from the Corps Regulatory project data management system known as ORM2 (Operations and Maintenance Business Information Link Regulatory Module 2) through a number of web services. This data enables Corps regulators to select specific mitigation banks or ILFs to be used to provide compensatory mitigation for permits and to close actions out in

ORM.

Under Interagency Agreements RIBITS is used by the USFWS and NMFS to track conservation banking activities (offsets for impacts to at-risk species under the Endangered Species Act). That currently includes 188 conservation banks in 15 states.

RIBITS is also being modified to track ILF programs providing compensation for listed and at risk species for the USFWS/.

Under an Interagency Agreement with USDA RIBITS is being modified to track water quality trading activities. Under an Interagency Agreement with NMFS RIBITS will be modified to track Natural Resource Damage Assessment crediting.

Most of the data in RIBITS is accessible to the public. There are several different permissions levels at the district, state, field office (USFWS) or region (NOAA) level:

none (public access), regulator, and administrator. The ability to modify the database or upload data (ledger transactions, shapefiles, documents, etc.) is determined by national and district level administrators who can grant user access permissions based upon role

(e.g. Bank Manager, IRT Member, Bank POC). RIBITS can be accessed through its home page at https://ribits.usace.army.mil.

Much of the content of the individual district, state, field office, or region RIBITS pages is shaped by local administrators (district, field office, or region depending upon agency) through the use of menus and tools that are only visible to local and national administrators as well as the RIBITS contractors and USACE technical and program managers.

Geospatial data is currently available to users through a Google Map © API (plug-in) that does not require a user license. RIBITS uses the plug-in to provide users with data on 6- and 8- digit HUCs, Corps District, USFWS Field Office, and NOAA Region Boundaries, bank and ILF project locations and boundaries, geographic service areas, credit types, bank and ILF program status, and supports user-defined geospatial queries of the system data.

Development of RIBITS has entailed information management (data modeling, database design, legacy data conversion, and quality control), development of web services to share data with other applications, coding, and geospatial processing (spatial data storage, Oracle Spatial Data Objects, Google Map, shapefiles, KML/KMZ files). Because RIBITS is located on a Corps server, close coordination with ACE-IT is required for a number of operations related to system functions like managing automated email system, server restarts and management, and upgrades. Close coordination with the ORM development team is also required in order to maintain data sharing through web services following upgrades or modifications to RIBITS and to

ORM.

RIBITS contains data on more than 4000 operational, pending, sold-out, and terminated bank and ILF project sites and 60 operational In-Lieu Fee programs located across the country. It includes more than 76,000 ledger transactions, 44,000 bank and ILF program-related documents, and more than 7,300 spatial data objects. RIBITS is a tool frequently-used by the public looking for information about mitigation banks and ILFs and by prospective mitigation providers examining opportunities for future compensatory mitigation projects.

2. SCOPE

RIBITS is an automated system for management of compensatory mitigation and conservation bank and in-lieu fee programs and to a lesser extent other environmental credit types (e.g. water quality trading, Natural Resource Damage Assessment credits).

The contractor would be tasked with operations, maintenance, and minor enhancements to RIBITS, as well as more substantive system modifications to facilitate use by USFWS, NMFS, EPA, USDA, FHwA, and the general public (described in Performance Requirements Section 4 below). The required work would include updating and maintaining the application on an outward–facing server in the Corps’ ACE-IT Demilitarized Zone (DMZ), transitioning the application to a cloud environment, establishing and maintaining production, development, and training environments for the system in a cloud environment, managing component software applications (such as Oracle, APEX, Apache, Java, and map controls, troubleshooting operational issues, making minor system enhancements to facilitate operations, assisting system users, and developing, testing, and implementing a number of modifications for specific system users.

More substantive system modifications may include but are not limited to the following:

development of more robust data query and display mechanisms; automated data registration and download for non-USACE users; more robust geospatial analysis and display capabilities; additional web services and xml data exchange capabilities for other system applications both within the Corps Civil Works Business Intelligence systems and outside of the Corps and Department of Defense; alternative map control mechanisms; presentation and display of other data layers (such as soils, ecoregions, HUC 10 boundaries, basic permit information, etc.).

The contractor may also be tasked with developing training materials, hosting training sessions, and developing and modifying user documentation for users at different permission levels.

3. GENERAL REQUIREMENTS

The following sub-sections provide details of various general requirements for this effort.

3.1. Non-Personal Services

The contractor shall provide strictly non-personal services and contractor employees are not subject to direct supervision and control by the Government. The contractor shall advise and support the Government but shall not make final decisions or certifications on behalf of the Government nor perform any inherently governmental functions. The contractor and its employees shall not represent the Government nor appear to represent the Government in performance of these contract services.

Contractor personnel shall clearly identify themselves as contractor employees in all interactions during contract performance.

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.

3.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.

3.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.

3.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.

3.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.

3.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-work days 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).

3.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.

3.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 C, 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.

3.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.

3.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.

3.8 Invoicing Instructions

The contractor shall submit monthly invoices for work completed whether in progress or after completion of a specific task. The contractor shall append the final invoice with an “F” to indicate final.

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

Invoices should be sent to the following email addresses to ensure that a copy goes to the USACE finance office and a copy to the IWR budget officer:

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

4. PERFORMANCE REQUIREMENTS

The following section specifies the Performance Objectives and Performance Elements for the contract. These tasks are all associated with operations, maintenance, management, enhancement, training, or substantive modifications of RIBITS. It is anticipated that in many cases, extensive subject matter expertise and cutting edge technologies and strategies will be required to perform these responsibilities and provide the required products and services described below.

4.1 Studies, Analyses, and Assessments

1.1.1 The Contractor shall conduct necessary studies to examine potential tools, approaches, and solutions to environmental credit tracking data management in RIBITS.

1.1.2 The Contractor shall provide research and analyses of RIBITS and other environmental market data to inform emerging and potential needs and issues.

4.2 RIBITS operations and management support and associated tools

4.2.1 The Contractor shall develop, enhance, and maintain RIBITS as an automated information management and decision support system and tool for the management, analysis, and display of environmental credit (or offset) data and associated information.

4.2.2 The Contractor shall provide management, maintenance, development and implementation of minor enhancements to the RIBITS web application including:

1) Maintaining current data and allow for additional bank and ILF program data entry by Corps, USFWS, NOAA, and other users

2) Allowing Corps Districts, USFWS Field Offices, and NOAA Regional Offices to continue to customize their RIBITS pages to reflect their bank and ILF practices

3) Maintaining public access to RIBITS data including data queries, downloading of ledgers, documents, and geospatial data

4) Maintaining communication with ORM2

5) Maintaining existing security protocols

6) Improving system response and processing and correct operational problems

7) Upgrading system applications

8) Improving data sharing with other systems

9) Developing and implementing features to improve user access

4.2.3 The Contractor shall provide technical assistance for users with permissions in RIBITS and technical support to other users. These support actions include:

1) Providing general user directions/answers to questions

2) Addressing common problems and general troubleshooting

3) Receiving and forwarding reports of operational problems and suggested enhancements to IWR

4) Referring process issues/misunderstandings to IWR or district, field office, or regional administrator

5) Identification of potential modifications or enhancements of the system

4.2.4 The Contractor shall assist with identification, requirements definition, prioritization, implementation, testing, and deployment of RIBITS updates.

4.2.5 The Contractor shall implement maintenance and modifications under direction of IWR/HQ USACE and ACE-IT. Implementation of maintenance and enhancement measures include software upgrades, formatting changes, corrections of operational flaws, and other tasks such as:

1) Upgrades to Oracle, Apache, APEX, Java, and other system component applications

2) Upgrades to RIBITS based on modifications of ORM 2.0 or ECOS (FWS) or any other system which provides information to RIBITS.

3) Upgrades to user browsers that produce incompatibilities with website function

4) Correct operational and program flaws and apply formatting changes

5) Monitor error-tracking reports

6) Monitor usage and response time

7) Improve efficiency of SQL queries to improve website response time

8) Continue to perform intrusion detection and enhance security as new threats emerge

9) Maintain/adjust web services between RIBITS and ORM2

10) Maintain automated email function

11) Continued code optimization to improve system response

12) Develop and implement minor features to improve user interface

(help tools, minor enhancements)

4.3 Develop and implement methodologies and tools

4.3.1 The Contractor shall conduct research and analysis (including data collection as appropriate) in support of developing specific methodologies and tools for analysis, display, use, and exchange of RIBITS data.

4.3.2 The Contractor shall develop, test, and implement analytic methods and tools, applications, software coding, and substantive system upgrades for

RIBITS.

4.4 Environmental market data collection and entry

4.4.1 The Contractor shall work with stakeholders (USACE, FWS, NMFS, USDA, states, mitigation providers, etc.) to collect, compile, and enter into RIBITS environmental market data including geospatial and transactional data and associated documentation.

4.5 Training Services

4.5.1 The Contractor shall develop and deliver user support, training, and system help documentation for RIBITS.

4.5.2 The Contractor shall plan, develop, modify, and present RIBITS training materials including workshops, sessions in courses or conferences, and web-based training.

4.5.3. The Contractor shall develop RIBITS electronic and multi-media products and/or exhibits for professional conferences, exhibitions, training environments, and public outreach and education.

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

a. In compliance with DoDI 8500.01 (2014) section 3.c.2, DoDI 8510.01 (2016) section 3.d, and USACE ER 25-1-112 (2014) section 7.1.3; all information systems (IS) and platform information technology (PIT) systems developed and/or supported under this contract shall comply with all DoD, DISA, Army, and USACE cybersecurity and architectural requirements. This includes IS/PIT compliance with DISA security technical implementation guides (STIG) and being categorized IAW CNSSI 1253 using security controls developed IAW the risk management framework (NIST SP 800-53). STIG compliance includes, but is not limited to most current version of the DISA published Application Security and Development STIG and the internet access point (IAP) demilitarized zone (DMZ)

STIG.

b. The contractor shall provide personnel who are capable of obtaining a CAC on the date of contract award. Replacement employees, if needed, shall have the same capability. The COR is the liaison between the security office and the contractor.

c. The work will be UNCLASSIFIED.

d. A National Agency Check (NAC), INFOSEC certificate, and U-PASS userid are required to support OMBIL Plus. All contractors must have the minimum investigation, a NAC or Questionnaire of public Trust, before accessing a DoD (Department of Defense) computer or working off-site on ORM programs and data.

e. INFOSEC certificate. Annual INFOSEC training for all those contractors accessing a DoD (Department of Defense) computer or working off-site on ORM2 programs and data is required. This training is available on-line at the DISA website, http://iase.disa.mil/eta/index.html, DoD Information Assurance

Awareness, version 2, or by completing Computer Security Training for Users on the Fort Gordon website, https://ia.gordon.army.mil/iss/default.htm

f. All contractor employees, to include subcontractor employees, requiring 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.

g. 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 the following websites: 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.

h. 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 5 business days after the initial contract award.

l. 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.

m. 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 IA/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M and AR 25-2 within six months of employment.

n. The contractor shall be responsible for safeguarding all government equipment, information and property provided for contractor use.

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 http://www.osha.gov/dcsp/vpp/index.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.

The government will provide a copy of the RIBITS data set if required for use in establishment of a development environment for use in future system upgrades and enhancements.

The contractor shall not use Government furnished materials (GFM) for any work outside the scope of this PWS. The contractor is responsible for all GFM during the performance of this PWS and upon termination the contractor shall return all GFM to the Government.

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 Contractors 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 plan 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 Contractors performance under this Task/Delivery Order in accordance with the Government’s QASP.

6. DELIVERABLES

The contractor shall provide deliverables as described in subsequent Task Orders.

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.

Deliverable Type Frequency and Quantity

A01 Studies, analyses, and assessments As specified in task order PWS A02 RIBITS Operations and Management As specified in task order PWS A02 RIBITS system enhancements As specified in task order PWS A03 Development, testing, and implementation of tools, coding, and substantive system upgrades

As specified in task order PWS

A04 Environmental market data compilation and loading

As specified in task order PWS

A05 User support services As specified in task order PWS

A06 User support documentation As specified in task order PWS A07 Software Product(s) As specified in task order PWS A08 Training Material(s) As specified in task order PWS A09 Training Services(s) As specified in task order PWS

7. 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.

Standard Acceptable Quality Level Standard (Statements)

Acceptable Quality Level Incentive/Remedy

Conduct necessary studies, analyses, and assessments (4.1.1, 4.1.2, 4.3.1)

As described in task order

PWS

Re-perform/correct at no cost to the Government.

Develop and maintain system operations (4.2.1, 4.2.2, 4.2.5)

As described in task order

PWS

Re-perform/correct at no cost to the Government.

Develop and implement system enhancements and upgrades (4.2.1, 4.2.2, 4.2.4, 4.3.2, )

100% of the time Re-perform/correct at no cost to the Government.

Compliant with applicable standards (All Statements)

100 % of the time Re-perform/correct at no cost to the Government.

Deliverables completed in accordance with Schedule (All statements)

95% of the time Re-perform/correct at no cost to the Government.

Early identification of problems and/or corrective actions. Report to gov’t within 5 days of discovery.

(4.2.1, 4.2.2, 4.2.3, 4.2.4 )

90% of the time

Re-perform/correct at no cost to the Government.

For user support, responsive to 1st request (4.2.3, 4.5.1)

90% of requests for support resolved within 30 days of receipt. Feedback Tracking system used to verify

Re-perform/correct at no cost to the Government.

Identify trends and areas of improvement (4.1.2, 4.2.3, 4.4.1)

As described in task order

PWS

Re-perform/correct at no cost to the Government.

Environmental market data collection and entry (4.2.4, 4.4.1)

95% of the time Re-perform/correct at no cost to the Government.

Training services (4.2.3, 4.5.1, 4.5.2, 4.5.3)

95% of the time Re-perform/correct at no cost to the Government.

8. DATA RIGHTS

All code and documentation will utilize the DoD approved Defense Intelligence Information Enterprise (DI2E) platform. All existing and developed code and documentation is property of the US Army Corps of Engineers.

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.

File details come from the government source that posted it.