Document

Standard Application Process Portal

ICR 202212-7100-001CF · OMB 3145-0271 · Object 126350001.

Document Viewer [docx]

Status: Original and derived artifacts are available for this document.

Download: docx | pdf | html

Primary: docxSource: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Loading document viewer…
Document Metadata
File Typeapplication/vnd.openxmlformats-officedocument.wordprocessingml.document
File TitleStandard Application Process Portal
Conversion Statecomplete
Extracted Text
Appendix B – Project Proposal Questions in the SAP Portal
(Note: Questions and question wording are submitted in draft form and are subject to change prior to public release in late 2022.)	

Item #
Application Field
Description (Question-Wording as it Appears on the SAP Application Portal)
Review Criteria
Rationale
35
Project Title
What is the project's title?
None
Gather general project information; for administrative purposes.
36
Project Duration
What is the project's duration, in months? Make sure there is sufficient time for the project to achieve its objectives and that the project’s duration is not greater than the data provider’s maximum duration. Requests for extensions beyond the proposed project duration may not be granted depending on the practices of the data providing agency. (Info button for maximum durations for each agency)
Feasibility
Allows agencies to evaluate whether the project can be executed within the requested timeframe.
37
Funding
Please list any funding sources for the project such as grants, FSRDC funding, university funding, etc.
Feasibility
Allows agencies to verify that the project is resourced and therefore that the project goals are achievable given the specified resource limitations. 
38
Timeline
What is the timeline for completing project tasks?  Please be specific regarding the tasks required to complete your project.  
Feasibility
Allows agencies to evaluate whether the project can be executed within the available timeframe.
39
Research Question
What is/are the proposed research question(s)?
Statistical Purpose
Allows applicants to demonstrate that their project has a statistical purpose. 
40
Demonstrated Need
Explain why the research question(s) can only be addressed using the requested restricted-use microdata.
Demonstrated Need
Allows applicants to express at length why their project's goals can only be met through restricted-use microdata.  
41
Project Scope
Briefly describe the study population or universe and how it relates to the research question 
Feasibility
Provides the agencies insight into the project's goals and objectives, thus allowing a more thorough evaluation of the project's feasibility (i.e., Can the requested data be used to answer the research question?)
42
Project Description
Please provide a project abstract. An abstract about the length of what would be published in a journal article is sufficient. The abstract should describe the purpose of the research, the type of data to be used, and the hypotheses to be tested. 

Statistical Purpose
Allows applicants to demonstrate that their project has a statistical purpose. 
43
Variables Requested
Please list all variables needed from [dataset name]. Please refer to the data dictionary for the dataset to determine the variables available.  (Repeat for each dataset for the agencies that have this requirement.)
Statistical Disclosure Limitation (SDL), Feasibility
Allows agencies to minimize disclosure risk, determine if the use of variables is appropriate, and evaluate project feasibility given the variables requested. 
44
Years Requested and Need and Use of Years 
Please provide the specific years of data requested and a justification for the years of data requested for this project, such as why a certain time series is important to the research.
Demonstrated Need
Allows applicants to justify their need for the time series requested and for agencies to evaluate their needs. 
45
Work Location
Where will the data be accessed?  If you plan on using data in multiple places, please mark all that apply.
Feasibility
Allows agencies to evaluate feasibility in terms of practicality (e.g., is computing space in a data enclave available) and logistics (e.g., can the data assets be physically co-located for analysis).
46
Software requirements
If your project requires statistical software other than that which is currently available in the location in which you will access the data [link to page listing software], please indicate that here.
Feasibility
Allows agencies to consider whether they can provide the requested software (if not, the applicant may be asked to revise and resubmit). 
47
Data Linkages
Discuss any data linkages planned for the research, including the datasets to be linked.  State whether linkages are at the record level, the purpose of the linkage (e.g., geographic/industry context), and basic information on how the linkages are to be performed.
Feasibility, Allowed Use
Applicants must demonstrate allowed use for any external data they plan to link to the requested confidential data asset(s). Agencies must also evaluate whether the requested data linkages can be co-located for analysis.  
48
User-provided Data
Please list all datasets you will provide and use for this project.
Feasibility 
Allows agencies awareness about user-provided datasets. This allows agencies to evaluate whether agency-provided datasets can be co-located with user-provided datasets. 
49
User-provided Data Ownership
Please indicate whether [user-provided dataset] is publicly available or proprietary and the source for the data, including the website address. (Repeated for each dataset - pre-loaded with each dataset listed in item 48).  
Allowed Use
Allows agencies to verify whether user-provided data has been independently collected by the applicant or obtained/acquired by the applicant. This allows agencies to evaluate whether user-provided datasets are consistent with allowed use criteria and if any data agreements with the user allow use of the data for the project. 
50
User-provided Data Anonymized
Will [user-provided dataset] have personal identifiers removed (i.e., anonymized)? (Repeated for each dataset - pre-loaded with each dataset listed in row 48).
Statistical Disclosure Limitation, Maintaining Public Trust
Allows applicants to demonstrate they can apply sound SDL approaches and techniques to minimize the risk of re-identification. Allows agencies to evaluate whether the proposal supports their ability to maintain public confidence. 
51
User-provided Data linkage
Will [user-provided dataset] be linked to other datasets at the record level, such as person, household, or business? (Repeated for each dataset - pre-loaded with each dataset listed in row 48).
Allowed Use, Statistical Disclosure Limitation
Allows agencies to ensure that the project is consistent with allowed use criteria that govern data use. Allows agencies to minimize the risk of re-identification. 
52
User-provided Data PIKs
If you are using Census Bureau data, will any of the user-provided data require Protected Identification Keys (PIK) applied?
Maintaining Public Trust, Feasibility
Allows the Census Bureau to ensure that its ability to maintain public confidence and carry out its mission will not be compromised and that the data can have PIKs applied. 
53
Methodology
Explain the methodology that will be used for the project.  The methodology should be clearly stated, be appropriate for the research question(s), and support the approved uses of the data.  It should discuss factors that support the feasibility of the proposed research and the need for confidential data such as following (as appropriate):
    • How each requested data set will be used
    • Model equations to be estimated
    • Estimation methods
    • How model variables will be constructed 
    • Strategies for addressing data quality issues
    • Expected sample size and subsamples 
    • Unit of analysis including level of geography 
    • Ability to link datasets
    • Availability of the study population in the data
    • Use of sample weights, design variables, and adjustments for use of complex survey design
    • Expected outcomes 
The metadata catalog, agency publications and statistical products, agency webpages describing the restricted access data, and agency contacts are valuable resources for background information for drafting a strong methodology. 
Feasibility, Allowed Use, Demonstrated Need
Allows applicants to provide adequate detail and background information on the proposed methodology, enabling agencies to evaluate the feasibility of the project given its proposed methodology, whether the use of the data is allowed, and if the research could be conducted with public-use rather than restricted-use data.
54



References/Literature Review
Describe how previous research or any other key past works that are of importance to this project support the feasibility of the methodology of the project and demonstrate evidence building or statistical purpose.   

Statistical Purpose, feasibility
Provides context for agencies to determine if data is being used for a statistical purpose. Allows the applicant to justify the feasibility of the project (e.g., by showing whether parts of the proposed methodology have proved feasible). 
55
Project Products
What are the anticipated papers (such as journal articles), conference presentations, technical memoranda, Ph.D. dissertation, government reports, and other expected products for this project?  Please include the names of journals targeted for publication.
Maintaining Public Trust
Provides agencies with additional context to inform their determination regarding whether the project supports their ability to maintain trust and credibility among data users and ensure public confidence is maintained. 
56
Requested Output
What is the anticipated output for this project?  This includes regression/modeling output, summary statistics, and any other output you intend to submit for disclosure review.  Include anticipated methods to meet disclosure requirements (e.g., noise infusion).
Disclosure
Allows applicants to provide information about the proposed reporting of results or output, which will be used for review under SDL criteria. 
57
Census Benefits
List each proposed criterion for this project, explaining how the benefit will be achieved.  Be sure to explain how the proposed work will benefit one or more Census Bureau programs.  Provide evidence from consultation with Census Bureau staff, including FSRDC Administrators, and/or identified needs described in Census Bureau or other publications.  Generalized statements or vague benefits will not be accepted.
Programmatic Benefit
Allows applicants requesting access to Census data to demonstrate compliance with Title 13, which requires all use of restricted-use data to deliver a benefit to the Census Bureau's programs and activities. 
58
Agency Benefits
List the proposed benefits to the agency from whom the data are being requested.  Be sure to explain how the proposed work will benefit the agency providing the data.
Programmatic Benefit
Allows applicants requesting non-Census data to demonstrate how their project will benefit the agency(ies) providing data.