1018-0109 - Supporting Statement A - rev 2015.rtf

Supporting Statement A for

Paperwork Reduction Act Submission

Application and Performance Reporting for Wildlife and Sport Fish Restoration Grants and Cooperative Agreements

50 CFR 80, 81, 84, 85, and 86

OMB Control Number 1018-0109

Terms of Clearance: None.

Note: OMB approved the use of Wildlife TRACS to collect information and assigned OMB Control Number 1018-0156. We have included in this renewal of 1018-0109, the use of Wildlife TRACS and the additional information we will collect. If OMB approves this renewal, we will discontinue OMB Control Number 1018-0156.

1. Explain the circumstances that make the collection of information necessary.

The Wildlife and Sport Fish Restoration Program (WSFR), U.S. Fish and Wildlife Service (we, Service), administers financial assistance programs in whole or in part. Some Federal financial assistance programs are established through enabling legislation to a Federal program that does not have the administrative resources or expertise to administer them. Some financial assistance programs are directly funded through WSFR; others are funded through non-WSFR Federal programs and WSFR administers various aspects of the financial assistance. When WSFR administers a grant in part of in whole, it follows the same processes for information collection to ensure the recipient complies with Federal laws, regulations, and policies applicable to financial assistance. For the purposes of this information collection, "WSFR-administered" means, at a minimum:

• Completing a pre-award technical review of the proposal. “Technical review” means as the application/grant relates to general grant administrative regulations and policies.

• The opportunity to impose or recommend terms and conditions of an award when necessary.

• Holding a recipient accountable for timely submission of a performance or Federal financial report.

• Responsibility for reviewing a Federal financial report [but not necessarily a performance report].

• Responsibility for giving prior approval for any action, intermediate product, acquisition, or purchase that requires such approval in the Cost Principles, regulations, or program policy.

• Closing out an award.

"WSFR-administered" may or may not include:

• Coordinating or participating in a ranking or selection process.

• Signing the award.

• Reviewing the substance of a performance report.

• Making the award.

Some Federal financial assistance programs are established to serve a long-term or recurring need or goal. Other Federal financial assistance programs are established to serve a short-term, immediate need or goal and are established with the expectation they will not be funded for more time than is considered necessary to serve the purpose. However, for the purposes of this information collection WSFR-administered projects/programs will remain consistent with the criteria listed above and Federal laws, regulations, and policies applicable to financial assistance. Not all WSFR Offices (Regional and Headquarters) administer all programs. We award most financial assistance as grants, but cooperative agreements are possible if the Federal Government will be substantially involved in carrying out the project. The table below lists the current programs that WSFR administers in whole or in part:

Program	CFDA No.	Authority	Implementing Regulations
Sport Fish Restoration	15.605	16 U.S.C. et. seq. except 777e-1 and g-1.	50 CFR 80
Wildlife Restoration	15.611	16 U.S.C. 669 et. seq.	50 CFR 80
Coastal Wetlands Planning, Protection, and Restoration Act	15.614	16 U.S.C. 3951-3956.	50 CFR 84
Cooperative Endangered Species Conservation Fund	15.615	16 U.S.C. 1531 et seq.; 16 U.S.C. 4601.	50 CFR 81
Clean Vessel Act	15.616	16 U.S.C. 777c (a)(3).	50 CFR 85
Sportfishing and Boating Safety Act (Boating Infrastructure Grants)	15.622	16 U.S.C. 777c, g and g-1.	50 CFR 86
Wildlife Conservation and Restoration *	15.625	Pub.L.106-553; 16 U.S.C. 669–669i.	None
Hunter Education and Safety	15.626	16 U.S.C. 669h-1	50 CFR 80
Multistate Conservation Grants	15.628	16 U.S.C. 669c, 669h-2; 16 U.S.C. 777-777c, 777m.	None
Landowner Incentive *	15.633	Pub. L. 110-5; 16 U.S.C. 460l-4–460l-11.	None
State Wildlife Grants	15.634	Pub. L. 112-74 and prior and subsequent Appropriations Acts.	None
Tribal Landowner Incentive *	15.638	Pub. L. 110-5; 16 U.S.C. 460l-4–460l-11.	None
Tribal Wildlife Grants	15.639	Pub. L. 112-74 and prior and subsequent Appropriations Acts.	None
Service Training and Technical Assistance (Generic Training)	15.649	16 U.S.C. 661 and 16 U.S.C. 742f(a)(4).	None
Research Grants (Generic)	15.650	16 U.S.C. 661; 16 U.S.C. 742f(a)(4); 16 U.S.C. 460l-4–460l-11; 16 U.S.C. 1531 – 1543.	None
National Outreach and Communication	15.653	16 U.S.C. 777g(d).	None
Fish and Wildlife Coordination and Assistance Programs (Generic)	15.664	16 U.S.C. 661-666; 16 U.S.C. 742a; 16 U.S.C. 2901-2911; and/or specific Congressional action, generally through the annual Appropriations Acts.	None
Highlands Conservation Program	15.667	Pub. L. 108-421; 16 U.S.C. 3901.	None
*Program has open grants, but no new funding.

Authorities and implementing regulations establish the purposes of the grant programs and the types of projects to be funded. Some list eligibility criteria as well as activities ineligible for funding. The authorities and implementing regulations for the competitive programs establish preferences or ranking factors for the selection of projects to be funded. These legal requirements make it essential for an awarding agency to have certain information so that it funds only eligible projects, and, in the case of competitive programs, to select those projects that will result in the greatest return on the Federal investment.

Some grants are mandatory and receive funds according to a formula set by law or policy. Other grants are discretionary and we award them based on a competitive process. Mandatory grant recipients must give us specific, detailed project information during the application process so that we may ensure that projects are eligible for the mandatory funding, are substantial in character and design, and comply with all applicable Federal laws. Discretionary grant applicants must give us information as dictated by the program requirements and as requested in the Notice of Funding Opportunity (NOFO), including that information that addresses ranking criteria. All grantees must submit financial and performance reports that contain information necessary for us to track costs and accomplishments and according to schedules and rules in 2 CFR part 200. 2 CFR 200, Uniform Administrative Requirements, Cost Principles, and Audit Requirements for Federal Awards, was effective as of December 26, 2014. The part regulates what Federal agencies and financial assistance recipients must provide and supports this information collection.

We have enhanced our information collection through the use of the electronic system Wildlife Tracking and Reporting Actions for the Conservation of Species (Wildlife TRACS), which was approved under OMB Control No. 1018-0156 on February 28, 2014. The use of electronic systems for information collection is supported by 2 CFR 200.9, which states, “agencies should not incur expenses for the printing of performance plans and reports. Rather, agencies should publish plans and reports electronically.” Our information collection is also supported through collaborative efforts. WSFR was the subject of a Program Assessment Rating Tool (PART) Review conducted by the Office of Management and Budget (OMB) in 2005. The results of that review determined that the Program needed a Strategic Plan and performance measures. To meet the requirements of the PART process, the Association of Fish and Wildlife Agencies (AFWA), representing State Fish and Wildlife agencies, and the Director of the Fish and Wildlife Service (Service) agreed that developing a Program Strategic Plan and performance measures should be completed through a joint State agency and Service endeavor. Two documents resulted: The Conservation Heritage Strategic Plan and The Conservation Heritage Measures. These documents serve, in part, to guide information collection strategies and goals.

The Office of Management and Budget Circular A-11, Preparation, Submission, and Execution of the Budget (June 2015) places emphasis on Federal agencies improving Federal program efficiency and effectiveness, assuring public accountability, and focus on results. This information collection reflects improvements the Service is making toward this effort. In past years, grantees sent paper or emailed applications and performance reports to the Service. The process to send applications to the Service has moved to the electronic system at http://www.grants.gov (Grants.gov) for sending applications for competitive programs and some mandatory programs. When processing performance reports, we received the paper reports, reviewed the reports and extracted information, and then entered data into the Federal Assistance Information Management System (FAIMS). FAIMS was decommissioned on October 1, 2012, and is replaced with Wildlife TRACS. Wildlife TRACS allows us to take advantage of newer technology and give grantees direct access to enter project data and report performance accomplishments, improving accuracy and efficiency. We will continue to enter information in Wildlife TRACS for some grantees or programs based on needs, resource limitations, and program size and requirements.

We offer multiple training options for State, tribal, commonwealth, territory, and District of Columbia personnel to use the new system. We will give technical and administrative support, as is needed to operate any electronic data collection system.

While we are replacing FAIMS with Wildlife TRACS, and updating our process to a more efficient and effective electronic method, we have the opportunity to make improvements that will create more consistent and robust reporting that will better help guide the future of conservation.

2. Indicate how, by whom, and for what purpose the information is to be used.

The majority of respondents are States and tribal governments; nonprofit organizations and institutions of higher education make up less than 5 percent of the respondents. We collect the following information from applicants and grantees:

Applications. We use the information provided in applications to: (1) determine eligibility under the authorizing legislation and applicable program regulations; (2) determine allowability of major cost items under the Cost Principles at 2 CFR 200; (3) select those projects that will provide the highest return on the Federal investment; and (4) assist in compliance with laws such as the National Environmental Policy Act, the National Historic Preservation Act, and the Uniform Relocation Assistance and Real Property Acquisition Policies Act of 1970. In addition to the appropriate Standard Forms 424 (Application for Federal Assistance), applications may include:

• Summary and project narratives that describe the proposed project.

• Need for assistance.

• Approach.

• Timelines.

• Budget information including a budget narrative.

• Geospatial entry of project location.

• Project status (active, completed, etc.).

• Project leader contact information.

• Partner information.

• Objectives, including output measures and desired future values.

• Public description.

• Action status (active, completed, etc.).

• Summary trend information, as applicable.

• Estimated costs, by action. (non-auditable).

• Effectiveness measures (initially for State Wildlife Grants).

• Plan information (for projects connected to plans).

• Information related to outcomes.

• Addressing ranking factors, as required by competitive grant programs.

For research and demonstration assistance requests:

• Biographical sketch of the program director with the following information: name, address, telephone number, background, and other qualifying experience for the project.

• Name, training, and background for other key personnel engaged in the project.
  
  

For real property acquisition projects:

• Maps, images and other data that reflect project location and benefits.

• Transactions, such as dates, method of transfer, title holder, and seller.

• Identifiers, such as State and Federal Record ID, parcel number, and property name.

• Values such as appraised value, purchase price and other cost information, and acres or acre feet.

• Encumbrances.

• Partners.

• Copies of any options, purchase agreements, mineral assessment reports, and draft conservation easements.

• Information needed for legal compliance; and copies of documents that demonstrate the grantee complied with 49 CFR 24, 2 CFR 200, program regulations, and other mandatory legal requirements.

Amendments. Most grantees must explain and justify requests for amendments to terms of the grant. We use this information to determine the eligibility and allowability of activities and to comply with the requirements of 2 CFR 200.

Performance Reports. All grantees must submit performance reports in the format requested by the Service. We use this information to ensure that the grantee is accomplishing the work on schedule and to identify any problems that the grantee may be experiencing in accomplishing that work. Grantees submit annual reports; however, reporting periods may be adjusted according to regulations at 2 CFR 200.328. Reports may include:

• A comparison of actual accomplishments with the goals and objectives established for the period, the findings of the investigator, or both.

• Reasons why established goals were not met, if appropriate.

• Other pertinent information including, when appropriate, (i) analysis and explanation of cost overruns or high unit costs and (ii) for land acquisition projects, a copy of the deed or other conveyance document and a copy of the Notice of Federal Participation.

We will use this information in support of grants and cooperative agreements between the Service and a grantee. The information will be collected primarily from States and the territories, commonwealths, tribes, and the District of Columbia when participating in grant programs managed through WSFR, but grantees may also be universities and other nongovernmental entities. The information will primarily be collected electronically, but may be collected through other methods for grantees that do not manage a lot of projects, programs that are small, or entities that do not have the resources to respond electronically.

Most grantees will enter the information directly into the electronic reporting system. This will increase the quality and accuracy of information given to the Service and available to report to the public. The information available to the public will not be controversial, will not represent an official position of the Service, will not ask for or offer the opportunity for the public to comment or respond except through official channels, and will not contain any information about the internal processes of the Service. The information given is primarily project information and reports related to grants offered by the Service which grantees voluntarily apply for.

3. Describe whether, and to what extent, the collection of information involves the use of automated, electronic, mechanical, or other technological collection techniques or other forms of information technology; e.g., permitting electronic submission of responses, and the basis for the decision for adopting this means of collection. Also describe any consideration of using information technology to reduce burden [and specifically how this collection meets GPEA requirements.].

We will use electronic means as the primary collection method for the information we include in this supporting statement. The public may find and apply for grants at Grants.gov. Grantees may submit amendments by email, fax, or mail (unless one method is required by program). Almost all performance reports will be entered electronically in Wildlife TRACS. The electronic systems as they currently exist will not be the official record. This will continue to reside in the Regional and Headquarters offices.

Collecting this information electronically is superior to paper submissions as it improves consistency, credibility, and the ability to collect information for more robust reporting. We have several contracts with third parties for development, hosting, and other information technology needs associated with Wildlife TRACS. The products they provide are not sole-source and can be serviced by others in the future as needs and processes dictate. The information will be stored in the “cloud” for secure, long-lasting storage. All outside contractors are managed through Service staff in WSFR.

Wildlife TRACS is designed to create an electronic work flow and approval system to allow grant managers, their supervisors, and others to work with the Service more efficiently by having documents flow from one to another electronically. This eliminates delays due to manual processing and site-specific availability. States will decide and manage the workflow process for their States according to how they decide they want to control the project review and approval process. Service staff will be part of the workflow for approving projects and actions, and accepting reports.

We continue training State and Service staff on the use of Wildlife TRACS and have staff dedicated to continued training and offerings through various venues to suit learning preferences and availability. We also offer guidance documents, training and usage tools, and other resources that can be accessed at any time at https://tracs.fws.gov/learning. The Service will support the States and other grantees with information entry during the initial transition and as needed in the future. However, we will expect States to assume the majority of the Wildlife TRACS data entry by October 1, 2016. Technical and informational support will continue indefinitely (Ex: a Help Desk). We anticipate that our method of collecting the information will improve with continued use of new technologies and methods, reacting to user suggestions, and experience with new methodologies and concepts. We have developed an agile, electronic system that we can improve upon based on user suggestions, advancements in technology, and improved practices.

We have worked with States during the development of Wildlife TRACS through a Project Advisory Group (PAG), the Association of Fish and Wildlife Agencies (AFWA), contractors, and subgroups to develop and review the electronic system. We are using electronic models and tools to increase usability and intuitive processes to increase the efficient input of data. These include:

• Using drop down menus;

• Incorporating walk through guides that direct users based on the answers given at a prior level (treed approach);

• Incorporating other science-based databases for taxonomy identification of species, habitat identification, and other conservation and information purposes, such as:

  • Bureau of the Census

    • States, Counties, Congressional Districts

  • Bureau of Land Management

    • BLM Lands

    • Public Land Survey System

  • Environmental Systems Research Institute (ESRI)

    • Base Maps (satellite imagery, roads, terrain, elevation)

  • U.S. Department of Agriculture

    • Soil Survey (SSURGO)

  • U.S. Geological Survey

    • National Hydrography Dataset

    • Bailey Ecoregions

  • U.S. Fish & Wildlife Service

    • Cadastral Data, Joint Ventures, Landscape Conservation Cooperatives, Regions, Refuges

    • Threatened and Endangered Species System (TESS)

  • Nature Serve

    • Habitat Types, Ecological Classification System, Endangered Species, Element Occurrence

  • Smithsonian Institute

    • Integrated Taxonomic Information System (ITIS)

  • Microsoft

    • Bing Maps (satellite imagery, roads, etc.)

  • University of Alaska / Alaska Department of Fish and Game

    • GINA Base Maps (satellite imagery, rivers, Wildlife management areas)

• Guided Process Tool (i.e., wizard) to streamline data entry and workflow from start to completion.

• Custom business workflows to streamline interim and long-term business processes (e.g. state and federal approvals).

• Feature Explorer tool to display project structure and complex data relationships.

• Feature Frame to provide one-click access to functions and operations for specific geographic features.

• Automatic spatial filters restrict default map display to specific user groups and permissions.

• Usability tools such as look-ahead pick lists, standardized drop-downs, data inheritance (i.e. default values), and geographic auto-detection features (e.g. habitat types, species occurrence).

• Graphical icons to indicate required fields, public fields, and workflow steps.

• Cross application links between mapping components and dashboard modules.

The methods of collection and reporting will improve accuracy, consistency, and allow the information to be queried to answer many of the questions that the Service and States need to address for grant performance and furthering conservation needs.

Some of the information collected will be available to the public over the internet. Exceptions will be made for information that is related to land ownership, sensitive species or habitats, or other information that would violate Federal, State, or local laws or policies.

4. Describe efforts to identify duplication.

This collection does not duplicate other information collections. Some States may have similar systems to collect their State information. We offer to all States, and are currently working with several States, to ingest the information from their databases into Wildlife TRACS, to further improve efficiencies of data collection and reduce overall burden.

5. If the collection of information impacts small businesses or other small entities, describe the methods used to minimize burden.

We do not believe the amount of information requested will have a significant impact on small entities. We request only the minimum information necessary to meet requirements of the authorizing statutes and Federal regulations, and to allow us to make a funding decision for competitive grants.

6. Describe the consequence to Federal program or policy activities if the collection were not conducted or is conducted less frequently, as well as any technical or legal obstacles to reducing burden.

We are legally obligated by Federal regulations to collect certain information when an applicant requests funding and performance information on Federal grants awarded to our grantees. If we did not collect the information, we would not be able to evaluate applications, competitively award grants and cooperative agreements, or ensure that Government funds are being properly expended. We cannot collect the information less frequently. Application information is collected on occasion in response to a Notice of Funding Opportunity. The majority of performance reports are submitted annually.

7. Explain any special circumstances that would cause an information collection to be conducted in a manner not consistent with OMB guidelines.

* requiring respondents to report information to the agency more often than quarterly;

* requiring respondents to prepare a written response to a collection of information in fewer than 30 days after receipt of it;

* requiring respondents to submit more than an original and two copies of any document;

* requiring respondents to retain records, other than health, medical, government contract, grant-in-aid, or tax records, for more than three years;

* in connection with a statistical survey, that is not designed to produce valid and reliable results that can be generalized to the universe of study;

* requiring the use of a statistical data classification that has not been reviewed and approved by OMB;

* that includes a pledge of confidentiality that is not supported by authority established in statute or regulation, that is not supported by disclosure and data security policies that are consistent with the pledge, or which unnecessarily impedes sharing of data with other agencies for compatible confidential use; or

* requiring respondents to submit proprietary trade secrets, or other confidential information unless the agency can demonstrate that it has instituted procedures to protect the information's confidentiality to the extent permitted by law.

There are no circumstances that require the information be collected in a manner inconsistent with OMB guidelines.

8. If applicable, provide the date and page number of publication in the Federal Register of the agency's notice, required by 5 CFR 1320.8(d), soliciting comments on the information collection prior to submission to OMB. Summarize public comments received in response to that notice (or in response to a PRA statement) and describe actions taken by the agency in response to these comments.

Describe efforts to consult with persons outside the agency to obtain their views on the availability of data, frequency of collection, the clarity of instructions and recordkeeping, disclosure, or reporting format (if any), and on the data elements to be recorded, disclosed, or reported.

On June 1, 2015, we published in the Federal Register (80 FR 31061) a notice of our intent to request that OMB renew approval for this information collection. In that notice, we solicited comments for 60 days, ending on July 31, 2015. We received comments from eight States and one individual.

Whether or not the collection of information is necessary, including whether or not the information will have practical utility.

Comment: Two respondents agreed that the collection of information is necessary and has always been a requirement of WSFR. However, they expressed concerns with the format, saying that using Wildlife TRACS is forcing States to change their established procedures.

Response: We agree that States have always had the responsibility to develop and submit performance reports for projects/grants. Prior to Wildlife TRACS, States submitted written reports to the Service. Service staff then interpreted and entered the information into the electronic system (Federal Aid Information Management System (FAIMS)). The Department of the Interior decommissioned FAIMS on October 1, 2012. We are required by law to collect performance information. Wildlife TRACS gives us the opportunity to allow States to more accurately report information by entering it directly. We agree that both Federal and State procedures for information sharing/data entry are changing following the decommissioning of FAIMS and the introduction of Wildlife TRACS. We are working closely with States to improve information collection and data entry so that the adjustment to using Wildlife TRACS will lead to more efficient and effective reporting. We are open to suggestions for further improvements.

Comment: One commenter stated that rather than thinking of Wildlife TRACS as an “increase in the amount of data” that grantees will be required to submit, using Wildlife TRACS should be thought of as a “change in the format” that the data is submitted. States are already providing the information, just in a different format. This new format will not constitute a significant increase in the time or resources required to either create or report on a project.

Response: We agree and thank the respondent for recognizing that using Wildlife TRACS is changing the format for collecting information to a more efficient and effective electronic system.

Comment: Two respondents stated that the Wildlife TRACS structure does not provide a clear benefit to either States or Regional FWS Offices.

Response: We disagree. The Wildlife TRACS structure is intuitive and helps users to enter information in a logical progression. The fields provided assist users to consider all needed information, allowing the Service to more efficiently review and approve projects. Once States become familiar with the Wildlife TRACS format, it will allow users to better design Wildlife TRACS-ready projects and provide the Service with adequate information to make decisions. As more projects are entered into Wildlife TRACS, States and the Service will be able to run more robust reports that will help identify trends, determine best processes, quantify results, and inform future actions. As additional system improvements are made, more reporting and data analyses tools will be available to provide benefit to the Service and users.

Comment: One respondent stated that Wildlife TRACS is forcing States to alter the format of existing grants and performance reporting to fit the Wildlife TRACS format, rather than a format that States feel works best for their particular projects.

Response: We agree that Wildlife TRACS is a different format for data collection, but disagree that the change in format affects the ability of States to design and implement projects. Wildlife TRACS does not represent a change in program requirements or substantiality in character or design. We will not require users to retroactively enter information into Wildlife TRACS. Wildlife TRACS data entry will only be required going forward. We have imported information on past projects from FAIMS into Wildlife TRACS as legacy data.

Comment: One respondent objected to using the tools in Wildlife TRACS, such as targeted fields and drop down menus, and connecting them back to SMART (Specific, Measurable, Achievable, Relevant, Time-bound) objectives that have significant limitations and questionable utility for reporting.

Response: We disagree. The interface and tools in Wildlife TRACS are designed to logically guide the user and allow less complicated and varied data entry. The selections provided in drop down menus have been vetted through Federal/State teams and it is believed that they cover all possible choices for the information needed. Often, a single metric may be characterized through many variations in language. Standardizing certain entries by limiting selections allows us to generate reports that include all projects that have similar components without having to search for all the variations in language. Using SMART objectives is integral to project management and helps users to focus on the desired outputs. Wildlife TRACS is designed to give users the flexibility to use the SMART objective fields or to create SMART objectives in narrative format.

Comment: One respondent stated that Wildlife TRACS is explained as a way of collecting and reporting useful information for all grant-funded actions. However, the type and purposes of grants is so varied, with such wide-ranging objectives, that Wildlife TRACS information can only be captured and reported effectively at a very high level.

Response: We agree that a large variety of projects will be reported in Wildlife TRACS, but we disagree with the respondent’s statement that suggests reporting won’t be relevant. Reporting is required down to the “Action level” for most projects. This allows us to produce reports that address both high-level and detailed perspectives, depending on need. Wildlife TRACS offers both standardized and customizable approaches for describing objectives in an effort to encapsulate the varied grant types and purposes.

Comment: Two respondents stated that the grants submission and reporting process, which has been successful for many years, provides the Service with the necessary information to approve grants. Wildlife TRACS is not a system that can readily be used to develop, edit, and write a proposal. It is simply a repository of the information, so there is duplication of workload from Wildlife TRACS data entry.

Response: We disagree. Paper submissions often lacked required information and led to additional workload for both Federal and State grant managers. Wildlife TRACS is designed to guide users to address all pertinent project information. We offer training for project leaders that will assist them to use Wildlife TRACS to help build projects. Although Wildlife TRACS is not a grant application system, users can produce reports from Wildlife TRACS that they can then use when submitting grant applications through Grants.gov. Future enhancements to Wildlife TRACS may include the ability to transmit a proposal to Grants.gov for approval. Wildlife TRACS does not create a duplication of effort as we do not require that the information entered into Wildlife TRACS also be submitted on paper.

Comment: Two respondents expressed that the Service should retain the responsibility to enter data into Wildlife TRACS. One stated that the information collected has no practical utility for State programs, which will be charged with managing data input. Their opinion is that Wildlife TRACS is strictly a Service project that is geared for the benefit of the Service. The States are well served for State purposes by the present grant reporting system, which allows States to submit usable products as evidence of grant/project completion. The easing of burdens is only realized by Service staff, not by States. The other respondent stated the transfer of workload will greatly increase administrative costs for States.

Response: We disagree. The information collection will give States the ability to accurately reflect project objectives and accomplishments, as well as providing information that will help States to better assess conservation needs and accomplishments. Wildlife TRACS will allow users to directly enter information, reducing errors from misinterpretation by Service staff tasked with translating and transmitting information from paper to an electronic system. Wildlife TRACS will also help States address increased grant-recipient responsibilities and provide for better reporting of State accomplishments. The reporting mechanisms in Wildlife TRACS will help States to provide evidence of project/agency successes to their elected representatives and the public. Planning and reporting on projects are already being done, so it is a matter of adjusting resources to accommodate Wildlife TRACS. We believe that any increase in administrative costs to States will be temporary and may be addressed through grant funding.

Comment: One respondent supported using an electronic system to collect application and performance reporting information to demonstrate program performance to interested stakeholders and the general public. They also appreciate the efforts of the Service to minimize the burden, including the October 1, 2016, date for State data entry.

Response: We agree and thank the respondent for the support.

Accuracy of our estimate of the burden for this collection of information.

Comment: One respondent stated that many grants are ongoing and have been in effect for more than 50 years. The need to alter the structure of these grants is overly burdensome.

Response: We believe the respondent is referring to ongoing projects and not ongoing grants. Grants have a period of performance that is much less than 50 years. Based on this clarification, we agree that using Wildlife TRACS is a change in the method of reporting information that will require States to initially enter baseline information for ongoing projects. However, once the baseline information is entered, Wildlife TRACS will allow efficiencies for ongoing similar projects. Users will be able to assign new grants to existing projects or to copy projects forward through simple steps that will reduce burden.

Comment: Three respondents commented on their concerns about performance reports. These concerns addressed:

(1) The performance report that was previously one paragraph in length must now be reported through multiple tabs within Wildlife TRACS to produce a lengthy report;

(2) The ability to copy forward a project will not produce the burden reduction the Service suggests;

(3) The reports contain redundant information; and

(4) Performance reports change from year to year, so significant time must still be spent to update pertinent information.

Response: We disagree for the following reasons:

(1) Data entry fields in Wildlife TRACS are designed to guide the user to make choices that will build the project information, increasing accuracy and efficiency. This does not affect the length of reports;

(2) Once the baseline information for an ongoing project is entered, Wildlife TRACS allows the information to be copied forward. This improves efficiency in that the user will not be required to repeat entering all information for continued projects or new, similar projects. Once a project is copied forward, adjustments can be made in selected fields to reflect desired changes from the existing, copied project. We remind users that the Wildlife TRACS function to copy projects forward is an option for users as an efficiency, but doing so is not a requirement. States may choose which method of input is most efficient and effective for their needs;

(3) Reports are created from information in the fields, so if there is redundant information it is because that is what the user entered; and

(4) Users will not be required to pull out reports and make changes; the adjustments will be made through logical changes in applicable fields. In addition, when a project is copied forward, it becomes a new project with new performance reporting. There is no requirement under the current reporting system to revise performance information on a completed project based on other projects, nor will it be a requirement when using Wildlife TRACS.

Comment: One respondent stated that the Uniform Administrative Requirements, Cost Principles, and Audit Requirements for Federal Awards at 2 CFR part 200 were designed to streamline the grant application process, but they feel the requirements for Wildlife TRACS go above and beyond this, placing an undue burden on States and representing steps backwards.

Response: We disagree. The focus of 2 CFR part 200 is to streamline guidance that was previously published as several regulations, into one regulation at 2 CFR part 200. This regulatory update is part of an overall effort to more effectively focus Federal resources on improving performance and outcomes while ensuring the financial integrity of taxpayer dollars in partnership with non-Federal stakeholders. The guidance at 2 CFR part 200 provides a Governmentwide framework for grants management that will be complemented by additional efforts to strengthen program outcomes through innovative and effective use of grant-making models, performance metrics, and evaluation. Wildlife TRACS is the tool that WSFR is using to fulfill this directive.

Comment: Three respondents cited several concerns regarding the role of Wildlife TRACS when States apply for grants and when the Service awards grants. Their concerns include:

(1) States must complete Wildlife TRACS data entry before a grant can be approved. The addition of Wildlife TRACS to the grant approval process is excessive and not necessary for the review and approval of grant applications;

(2) Using Wildlife TRACS for grant approval may put a State agency at risk of reverting apportionments;

(3) The requirement to enter data into Wildlife TRACS prior to a grant award results in a duplication of effort, having to submit the grant proposal twice; and

(4) Wildlife TRACS was proposed as a reporting tool and never was supposed to affect the application process.

Response: We disagree for the following reasons:

(1) Wildlife TRACS is not used to approve grants, but rather to approve projects. Grantees are not required to enter data for projects funded with one of WSFR’s competitive grant programs until after we award a grant. Grantees are required to enter project information and receive approval prior to project start for projects funded under one of WSFR’s mandatory grant programs. However, the Service does not award mandatory grants based on Wildlife TRACS data entry. Mandatory grants are apportioned according to a formula set by law. Entering information for mandatory grant projects allows Service staff the opportunity to review projects to assure they meet program requirements and are substantial in character and design. This process reduces risk and helps States to avoid unallowable, unnecessary, or undesirable expenditures;

(2) It is the responsibility of the State to avoid reverting funds. The time required to approve a grant is not related to Wildlife TRACS, but to the availability of WSFR staff to review the proposal, and the completeness of the State's submittal. When States fully engage in Wildlife TRACS, they can use the workflow tool to help save time and more efficiently commit funds;

(3) As stated above, Wildlife TRACS is not a grant-approval tool, so there is no duplication of effort. However, Wildlife TRACS gives users an option to enter information into Wildlife TRACS that can then produce a report that may be used to supplement/support a grant application; and

(4) Wildlife TRACS is a reporting tool. In order to report on project performance, we must know what the project is and be able to compare achievements against the proposal. Wildlife TRACS allows users to enter project information so that the Service can easily see objectives and compare them to achievements.

Comment: One respondent stated the requirement to use Wildlife TRACS for project approval may be problematic and asks that the Service retain some flexibility to accommodate urgent and/or unusual situations.

Response: The project approval process for mandatory grants requires States to enter information into Wildlife TRACS and route appropriately through the workflow. We must maintain consistent procedures to avoid confusion and assure appropriate project approval. However, having Wildlife TRACS protocols in place does not eliminate the ability of States to coordinate with the Service when special needs or circumstances arise.

Comment: Three respondents suggested that Wildlife TRACS be linked to Grants.gov, reducing a duplication of effort and increased workload for applicants. One suggestion was that the Service use Grants.gov instead of Wildlife TRACS to collect project data.

Response: We agree that Wildlife TRACS is not currently tied to Grants.gov, but remind the respondents that Wildlife TRACS is not a grant application system. Grants.gov provides a central portal for applicants to find and apply for Federal financial assistance. We do understand that often a single grant may fully fund a project and we continue to develop options that users may choose to employ to ease the burden of the application process through Grants.gov. In the future, we plan to implement a protocol where Wildlife TRACS will use web services published by Grants.gov to reduce any potential duplication of effort. WSFR anticipates that Wildlife TRACS will offer this capability by December 2017.

Comment: Two respondents stated that State agencies often submit multiple grant applications and have a rigorous State review process that includes coordination among multiple employees. A heavy workload to enter information into Wildlife TRACS could fall onto one employee because of the complicated process, or will require States to reassign staff or hire Wildlife TRACS-specific personnel.

Response: We disagree, as Wildlife TRACS is not a system that the Service uses to approve grants, but rather assists in efficient project approval. We agree that States will have a transition period while learning Wildlife TRACS, but we disagree that having several project leads is more burdensome using Wildlife TRACS than when using the current, paper-based process. A grant or a project that requires coordination among multiple layers of project leaders and approvers must be managed regardless of whether Wildlife TRACS is used or not. The State processes for reviewing and approving grant applications and project proposals is a State function, determined by the State and not driven by Wildlife TRACS. However, Wildlife TRACS may be customized so that when a State has large grants with multiple actions and several project leads, they can manage workflow among those multiple users. Wildlife TRACS offers a workflow option that can assist States to route information among multiple staff and receive project approvals much faster than would happen if paper copies were circulated. It is ultimately up to States to determine the best approach for managing reporting on all projects, including those that are larger and more complicated. We encourage States to explore ways that Wildlife TRACS can assist them to improve efficiencies during the State preparation, review, and approval phases. The Service is open to suggestions for how Wildlife TRACS might allow further efficiencies for States to use when coordinating projects among multiple employees.

Comment: Three respondents stated concerns that the level of cost accounting in Wildlife TRACS will create a need to alter their internal controls and accounting systems. Wildlife TRACS defines a new focus called the action level and requires associated accounting. Historically, this level of reporting has not been required for WSFR grants and creates an undue burden.

Response: We disagree that Wildlife TRACS is forcing States to change internal controls and accounting systems. States must maintain internal controls within their agencies and they should be designed to respond to a variety of altering situations. Wildlife TRACS workflow tools may be used to complement internal processes. Wildlife TRACS is not an accounting system; however, the regulations at 2 CFR part 200.301 require “recipients to provide cost information to demonstrate cost effective practices” as part of their performance measurement. To reduce burden, it may be desirable for States to work with the Service and determine how Wildlife TRACS can best interface with existing State electronic systems. Although it may be advisable to determine how State systems and using Wildlife TRACS can better work together, Wildlife TRACS does not require States to change any of their existing systems or internal controls. The level of reporting is not a new standard, but is a level that should have been reported all along. By separating projects into discrete actions, States and WSFR can each evaluate project success more efficiently.

Comment: Three respondents objected to including effectiveness measures in Wildlife TRACS beyond the State Wildlife Grant program. One cited that performance reporting (2 CFR 200.328(b)(2)) does not require effectiveness measures. Also stated was that measuring effectiveness on 1-year grants is not always possible. Reporting effectiveness creates an undue burden on States.

Response: We disagree. Performance measurement at 2 CFR 200.301 directs that “the recipient’s performance should be measured in a way that will help the Federal awarding agency and other non-Federal entities to improve program outcomes, share lessons learned, and spread the adoption of promising practices.” The language at 2 CFR 328(b)(2) does not include the term “effectiveness measures,” but does state at paragraph (i), “Where performance trend data and analysis would be informative to the Federal awarding agency program, the Federal awarding agency should include this as a performance reporting requirement.” Our approach is to demonstrate program needs and accomplishments in a meaningful way by moving to strategies that will gather appropriate information that can be used to adequately inform the Service, States, elected officials, interest organizations, and the public.

Comment: One respondent stated that using Wildlife TRACS is taking staff time away from satisfying grants. Given the time constraints on current staff, we are concerned we may have to hire new staff just to address Wildlife TRACS.

Response: We agree that States will have a transition period when moving from processing paper documents to embracing an electronic format. However, Wildlife TRACS is not creating additional project requirements, but rather is a platform to allow users to respond to current requirements. Wildlife TRACS is designed to assist by allowing States to create an electronic workflow that suits their current structure and at the same time, will improve efficiency and document access.

Comment: Two respondents commented on the accuracy of the estimated burden. One respondent stated that they do not have sufficient information on what type of projects, whether new entries, and what iteration of Wildlife TRACS was used. They stated their opinion that Wildlife TRACS becomes increasingly complex and time-consuming. Since full grant documents must still be submitted, there is no doubt that time invested in Wildlife TRACS data entry will be in addition to grant applications and no savings will be realized by States. The other respondent stated that the estimate of burden is too low. Wildlife TRACS has the potential to reduce burden in the future, but the current burden should be increased by 50 percent.

Response: We make no changes in our burden estimates based on these comments. We are estimating the burden that will be realized over the next 3 years. We expect the burden to be slightly higher when States first transition to using Wildlife TRACS. However, once States fully engage in Wildlife TRACS we expect the burden to significantly decrease. We agree that our burden estimates are less comprehensive due to the relatively limited number of States that have fully engaged in Wildlife TRACS. We based burden estimates on information we received from States that responded to our questions, feedback from Service staff, and our planned improvements to Wildlife TRACS. Improvements under development in Wildlife TRACS will make the system more user-friendly and streamlined, while targeting ways to minimize burden. Also, we are developing tools that States may choose to use when applying for grants that will reduce overall workload. The Service welcomes input and suggestions for continual ways to improve Wildlife TRACS efficiency.

Comment: One respondent stated that Wildlife TRACS continues to undergo changes and this makes it impossible to accurately estimate burden.

Response: We agree that change is a natural component of modern web application development and maintenance, particularly in response to the rapid pace of technology and security advancements. We have made changes to the user experience in Wildlife TRACS, based primarily on recommendations from States and other partners for ways to improve Wildlife TRACS and reduce burden. We will continue to work with our partners to identify improvements and efficiencies in data collection. Once States are fully engaged in Wildlife TRACS data entry, we will have a greater response base for estimating burden.

Comment: One respondent stated that Wildlife TRACS does not effectively accommodate Comprehensive Management System (CMS) reporting and that the CMS enhancement will not be completed by October 1, 2016. Requiring CMS States to enter data into the incomplete Wildlife TRACS system by October 1, 2016, will be an undue burden on CMS States. This deadline should be extended for CMS States until Wildlife TRACS is ready to accept CMS data and the Service gives sufficient time for CMS States to adjust internal processes and train staff.

Response: We agree that Wildlife TRACS does not fully accommodate CMS reporting at this time. However, a process has been vetted by a Federal/State team that will allow CMS States to begin to use Wildlife TRACS to capture accomplishment data until the application can be modified to more easily accommodate the CMS structure. The Service will require CMS States to enter reporting information into Wildlife TRACS, consistent with non-CMS States, and will adequately train staff in using the approach identified.

Comment: One respondent supports Wildlife TRACS by stating that States have no good mechanism for reporting project outcomes. An effort led by the Association of Fish and Wildlife Agencies developed effectiveness measures for State Wildlife Grants, which are being incorporated into Wildlife TRACS. Although entering more data will constitute an additional reporting burden, this information will allow us to provide Congress and the public with a much better understanding of our accomplishments. We feel the expanded reporting opportunities will outweigh the additional data entry burden.

Response: We agree that it is important to incorporate reporting information into Wildlife TRACS that will fulfill legal requirements, our responsibility to the public, and our desire to inform the course of conservation for the future. We continue to consider approaches that will give the greatest return for the least burden. We thank this respondent for understanding our combined responsibilities and the importance of measuring the effectiveness of our grant programs.

Ways to enhance the quality, utility, and clarity of the information to be collected.

Comment: One respondent suggested that geospatial information should only be entered as a component of accomplishments and not required as part of the application process.

Response: We make no changes based on this comment. We remind respondents that Wildlife TRACS is not an application system. However, the project statement in a grant application requires location information, so describing the location of a project when applying is not a new requirement. Wildlife TRACS is a geospatial-based system and entering location information is the first step in data entry. We have learned that project location is integral to conservation efforts and expect that reports resulting from Wildlife TRACS and overlapped with other geospatial systems will greatly improve overall conservation. Wildlife TRACS allows for States to initially enter general geospatial information and to improve the information as the project evolves and completes, so perfecting geospatial information comes in the accomplishment phase, as suggested by the respondent.

Comment: Two respondents suggested that geospatial information should only be collected at the project level and not at the action level.

Response: We agree that there may be projects for which it will be sufficient to report geospatial information on a project level, but others will require more detail. There will also be projects for which the location at the project level and the action level are exactly the same. The project scope is a factor when determining the required level of reporting. Wildlife TRACS enables users to choose the precision of their geospatial data as appropriate for the project scope. The Service has also been working with States to define needs of various programs and the level of detail desired to produce the reports that will best support each program.

Comment: One respondent recommended several considerations for upgrading the system, including: improving the mapping tool and GIS detail, adding fields that allow States to enter all parts of the project statement, resolving some problems that have been encountered with converting data entries to pdf reports, addressing need for new/flexible standard indicators, and providing fields for additional information related to real property purchases.

Response: We thank the respondent for these thoughtful comments for improvements to Wildlife TRACS and will take all of these recommendations under consideration.

Comment: One respondent submitted comments asking for increased reporting opportunities that will allow a more complicated and robust inquiry. The respondent gave the following examples of queries not currently supported: identify all projects within a State on behalf of an individual species or group of species; projects within specific ecoregions or Congressional districts; and collective impacts of related projects over time. The comments recognize Wildlife TRACS’ ability to offer opportunities for addressing these reporting needs and even though it may require additional effort at the beginning, the value of the reporting options outweighs the data entry burden.

Response: We agree that robust reporting capabilities are vital to our mission and Wildlife TRACS reporting will allow users to generate this type of report. We expect Wildlife TRACS to be fully functional for robust reporting by December 2016.

Comment: One respondent suggested that the Service should provide a reporting module that State and Federal staff can use to determine if project detail is sufficient to meet reporting needs. When a report module is provided, we will be able to evaluate the situation and better create best management practices for data entry.

Response: We agree that the ability to produce reports from data entered into Wildlife TRACS will help users to identify how to improve data entry. New enhancements to the workflow manager will allow users to more easily view validation and workflow status information. We expect Wildlife TRACS to include these enhancements for workflow management by November 2015. We look forward to working with States to refine best practices for data entry.

Comment: Two respondents suggested that estimated costs by actions should not be collected. Financial reporting should be consistent with Financial and Business Management System (FBMS) and not extend past the subaccount level.

Response: We disagree and recognize that a major benefit of action-level costs is to assist both the Service and States in assessing cost effectiveness of projects. There will be an interface with FBMS that gives users some information to assist with cost analysis, but the cost information in Wildlife TRACS is not auditable. The estimated costs States enter into Wildlife TRACS is for a different purpose than the cost information in FBMS.

Ways to minimize the burden of collection of information on respondents.

Comment: One respondent stated that while it is preferred to minimize the reporting burden, we also want to ensure that the information we provide is sufficient to meet our responsibilities to the Service, elected officials, and the public. When a reporting module has been developed for Wildlife TRACS, we will be in a better position to evaluate reporting burden. At that time, we will work with the Service to find efficiencies that could minimize burden.

Response: We appreciate the commitment to robust reporting and will continue to work with States and other partners to identify efficiencies and to minimize burden.

Comment: Two respondents recommended we develop data communication between Wildlife TRACS and Grants.gov to reduce the burden to States for duplicate work.

Response: We addressed Wildlife TRACS and applications above. When addressing ways to minimize burden, we agree that communication/interfaces with other electronic systems can help to improve efficiencies and reduce burden. Grants.gov is a grant application system and Wildlife TRACS is a project tracking and reporting system, so there will not always be a direct correlation from Wildlife TRACS to Grants.gov. However, for those projects that fall into the category of being funded through one grant, we will work to offer more options that may improve processing and reduce burden. We currently interface with several other electronic systems that serve to improve the user experience and lessen burden, such as FBMS and databases for identifying species, and we will continue to consider other opportunities. We welcome continued suggestions.

Comment: One commenter suggested that Wildlife TRACS should either be upgraded to a full grant-management system, or the Service should retain full responsibility for entering data using State grant applications as the source for obtaining grant data.

Response: We make no change based on this comment. The Department of the Interior made the decision to transition from the various grant and other fiscal management systems being used by programs in the Department to a single fiscal management system, FBMS. Our former system, Federal Aid Information Management System (FAIMS), was decommissioned in October 2012. FAIMS was replaced for financial reporting by the Financial and Business Management System (FBMS), which encompasses all financial and business administrative functions, not only grants programs. FBMS does not address project/grant performance reporting, is not grant-centric, and the system is not accessible to grantees. Wildlife TRACS is focused on filling the gap for performance reporting. There is no change in the responsibility for the grantee to report on project performance. Wildlife TRACS allows States to more accurately report by entering information directly.

Comment: One respondent suggested that we should not implement Wildlife TRACS until it is in its final form, ensuring a stable model, reducing the need for retraining, and reducing the need for State staff to adapt to shifting models and expectations.

Response: We make no changes based on this comment. The adjustments to Wildlife TRACS are to improve the user experience, efficiency of data collection, and response to information requirements. Many of the improvements are a result of recommendations from States that have engaged in Wildlife TRACS. None of the data entered into Wildlife TRACS will be lost as improvements are made. Continued training opportunities are available for users at: https://TRACS.fws.gov/learning.

Comment: One commenter stated that the Service should continue to enter data into Wildlife TRACS, resulting in no impact on States to implement this approach.

Response: We disagree. We refer to responses above for further details. We will continue to assist States during the transition to address the backlog of projects that need to be entered into Wildlife TRACS. We will also work with States after October 1, 2016, to assess needs and offer options.

Comment: One respondent asked us to continue to honor the Federal requirements that grant recipients must only report for those activities that have occurred during the period of performance. Any additional requirements would be especially burdensome and draw resources away from the programs needed to manage the resources.

Response: We agree and will only require reporting on projects during the period of performance. We may ask States to voluntarily assist with information beyond the period of performance, but it is expected that much of the information shared will be from work that States are already accomplishing for their internal needs. We hope to continue to work in partnership with States and other interested organizations to create vital and robust outcome information that will engage and inspire the public; inform our elected officials; and help Federal, State, and local agencies to work together for continued conservation successes.

Comment: The commenter objected to the use of taxpayer dollars for these financial assistance programs.

Response: We note the commenter’s objection to funding these grant programs. The commenter did not address the information collection requirements, and we did not make any changes to our requirements based on this comment.

In addition to the Federal Register notice, we have consulted States; interest organizations; other Federal, State, and local agencies; and other Federal staff when determining the information we need for approving projects and reporting actions. We have formed several teams over the last 3 years, consisting of both Federal and State representatives. These teams advise the Service on the continued development and improvements to Wildlife TRACS to improve functionality, effectiveness, efficiency, and the ability to create robust reports that will inform all levels of government and the public on conservation efforts into the future.

We also contacted the following people soliciting comments on the information collection and our burden estimates:

Ryan Leamy <[email protected]>	Li Lan Carson <[email protected]>
Nahan Soboleff <[email protected]>	Brad Compton <[email protected]>
Randy Curtis [email protected]	Robert Longcor [email protected]

All who responded expressed many of the same concerns received in response to the Federal Register notice, including that using Wildlife TRACS will increase the burden on grantees. In arriving at our burden estimates, we have considered all comments. The estimates in item 12 reflect burden estimates that we expect over the next 3 years. We believe that the burden will decrease as States begin to fully use Wildlife TRACS.

9. Explain any decision to provide any payment or gift to respondents, other than remuneration of contractors or grantees.

We do not provide gifts or payments to respondents.

10. Describe any assurance of confidentiality provided to respondents and the basis for the assurance in statute, regulation, or agency policy.

We do not provide any assurance of confidentiality. We handle any personal information that might be included in accordance with the Privacy Act. We do not ask for social security numbers.

11. Provide additional justification for any questions of a sensitive nature, such as sexual behavior and attitudes, religious beliefs, and other matters that are commonly considered private.

We do not ask questions of a sensitive nature.

12. Provide estimates of the hour burden of the collection of information.

We require applications annually for new grants or as needed for multi-year grants. We require amendments on occasion when key elements of a project change. We require annual and final performance reports in all programs. We may require more frequent reports under the conditions stated at 2 CFR 200.328.

The burden hours below are for the time we anticipate is needed for the information we request. We expect the total burden for collected information to decrease over the next several years as users become more familiar with Wildlife TRACS, and as we make improvements to Wildlife TRACS, as recommended by users.

We estimate a total of 7,500 responses totaling 125,000 annual burden hours for this collection.

The dollar value of the annual burden hours is approximately $6,686,250 ($53.49 times 125,000 hours). We used the Bureau of Labor Statistics USDL 15-1756 entitled “Employer Costs for Employee Compensation – June 2015 (http://www.bls.gov/news.release/pdf/ecec.pdf) released on September 9, 2015 to determine the hourly wage and benefits. Table 3 lists the hourly wage for State management and professional occupations, including wages, salaries, and benefits as $53.49

ACTIVITY	NUMBER OF RESPONDENTS	NUMBER OF RESPONSES	COMPLETION TIME PER RESPONSE	TOTAL ANNUAL BURDEN HOURS
Initial Application (project narrative)	200	2,500	37	92,500
Revision of Award Terms (Amendment)	150	1,500	3	4,500
Performance Reports	200	3,500	8	28,000
TOTALS	550	7,500	------	125,000

13. Provide an estimate of the total annual [nonhour] cost burden to respondents or recordkeepers resulting from the collection of information.

There are no nonhour burden costs associated with this information collection.

14. Provide estimates of annualized costs to the Federal Government.

We estimate the total cost to the Federal Government for processing and reviewing applications, amendments, and reports as a result of this collection of information is $3,841,000 (salary plus other costs)

Salary Costs: $1,088,000 (17,000 hours X $64 (weighted average $/hr).

• For applications, we estimate Federal staff will spend 5,000 hours (2 hours per application) to: (1) develop and post application instructions; (2) review applications; (3) perform data entry; and (4) maintain files.

• For amendments, we estimate a total of 1,500 hours (1 hour per amendment) for staff to: (1) review the amendment; (2) perform data entry; and (3) maintain files.

• For reports, we estimate a total of 10,500 hours (3 hours per report) for staff to: (1) review the reports; (2) perform data entry; and (3) maintain files.

POSITION	GRADE/STEP	HOURLY RATE1	HOURLY RATE INCL BENEFITS2	PERCENTAGE OF TIME SPENT	WEIGHTED AVEREAGE ($/HR)3
Clerical, unskilled	GS-7/step 1	$ 20.63	$ 30.95	10%	$ 4
Skilled, craft and technical	GS-13/step 1	$ 43.52	$ 65.28	85%	$ 55
Management/ professional	GS-15/step 1	$ 60.49	$ 90.74	5%	$ 5
Total Weighted Average ($/HR)					$ 64

While staffs in eight Regional Offices and the Washington Office perform the work, we used the Office of Personnel Management Salary Table 2015-DCB as the basis for an average salary rate.

² Hourly rate multiplied by 1.5 to account for benefits in accordance with BLS News Release USDL 15-1756.

³ Values are rounded.

Other Costs – $2,753,000. FY 2015 costs we reported (eCPIC) for Wildlife TRACS (personnel, hosting, hardware, software, travel, licenses, and other associated costs). We must maintain an electronic reporting system for performance reporting on grants we manage.

15. Explain the reasons for any program changes or adjustments in hour or cost burden.

We estimate a total of 7,500 responses totaling 125,000 annual burden hours for this collection. This is a net increase of 1,000 burden hours from our previous information collection request in 2012. We are reporting this as a program change as a result of using Wildlife TRACS. We have reduced the estimated time to complete an initial application by 3 hours, while we increased the estimated time for an amendment by 1 hour and for performance reports by 2 hours. The increase is expected as users are not yet proficient with using Wildlife TRACS. It is expected that with routine use and increased proficiency, the burden will be further reduced in future years.

16. For collections of information whose results will be published, outline plans for tabulation and publication.

The information we will collect will be visible as reports to the public through the Wildlife TRACS Web site. The type of information will be similar to that previously available to the public on the iFAIMS Web site, but will use newer technology, improved processes, and standardized responses to give more accurate and engaging information. The Wildlife TRACS Web site will allow the public to search geographically, by species or habitat, or using other identifiers that will inform the public on a wide range of conservation efforts.

17. If seeking approval to not display the expiration date for OMB approval of the information collection, explain the reasons that display would be inappropriate.

We will display the OMB control number and expiration date on Notices of Funding Opportunity, the Wildlife TRACS Web site, and other appropriate materials.

18. Explain each exception to the certification statement.

There are no exceptions to the certification statement.

1

2

3