#########  ATTACHMENT A 

######### 

######### 

#########  Beginning Postsecondary Students Longitudinal Study 1996-2001

######### Introduction 

######### I.A. Purpose of Study

The United States Department of Education has a requirement for a large,
complex data collection. This data collection, Beginning Postsecondary
Students Longitudinal Study 1996-2001 (BPS:96/2001), is designed to be
the third in the series of longitudinal data collection efforts
involving first-time entrants to postsecondary education in the 1995-96
academic year. This effort started in 1996 as part of the National
Postsecondary Student Aid Study (NPSAS:96) and continued through 1998.
BPS:96/2001 will collect data elements concerning postsecondary
education activities, work force activities, and other experiences of
postsecondary education program completers. The method of data
collection will be telephone and personal interviews. This study will
culminate in a descriptive report and documented data files.

The BPS:96 sample is made up of all first-time beginning postsecondary
students identified in the 1996 NPSAS sample, a nationally
representative sample of all students in postsecondary education
regardless of level or institution type. Thus, the BPS sample is
nationally representative of all beginning postsecondary students who
first entered postsecondary education (PSE) in 1995-96. BPS tracks the
progress of new college and vocational school entrants through their
undergraduate education and into the work force or graduate education.
BPS provides information to help assess the value of a student's
postsecondary education both to the student and to society. This
component will collect information on the attendance, persistence, and
completion patterns (attainment of awards and degrees), other
educational experiences related to persistence and completion,
application to and direct entry into graduate school, employment both
during and after PSE completion, and participation in civic
responsibilities and family development. Results from this and later
efforts will contribute to the comprehensive national database designed
to address a variety of policy issues at the postsecondary level.

The work will be monitored by the National Center for Education
Statistics (NCES) within the U.S. Department of Education (ED).

**I.A.1. Legislation**

NCES is authorized to conduct this study under Section 404(a) of the
National Education Statistics Act of 1994, Title IV of the Improving
America\'s Schools Act of 1994, P.L. 103‑382, which states:

> \"The duties of the Center are to collect, analyze, and disseminate
> statistics and other information related to education in the United
> States and in other nations, including (1) collecting, acquiring,
> compiling \..., and disseminating full and complete statistics on the
> condition and progress of education. at the pre-school, elementary,
> secondary, and postsecondary levels in the United States, including
> data on \--

*(A) State and local education reform activities;*

*(B) student achievement at all levels of education;*

*(C) secondary school completions, dropouts, and adult literacy;*

*(D) educational access to and opportunity for postsecondary education,
including data on financial aid to postsecondary students;*

*(E) teaching, including data on course-taking, instruction, the
conditions of the education workplace, and the supply of, and demand
for, teachers, which may include data on the proportions of women and
men, cross-tabulated by race or ethnicity, teaching in subjects in which
such individuals have been historically underrepresented;*

*(F) the learning and teaching environment, including data on
libraries;*

\(G\) the incidence, frequency, seriousness, and nature of violence
affecting students, school personnel, and other individuals
participating in school activities, as well as other indices of school
safety;

*(H) the financing and management of education, including data on
revenues and expenditures; and*

*(I) the social and economic status of children;*

*(2) conducting and publishing reports and analyses of the meaning and
significance of such statistics; (3) conducting longitudinal studies as
well as regular and special surveys and data collections, necessary to
report on the condition and progress of education; (4) collecting,
analyzing, cross‑tabulating, and reporting, to the extent feasible, so
as to provide information by gender, race, socioeconomic status,
limited-English proficiency, and other population characteristics when
such disaggregated information would facilitate educational and policy
decisionmaking; . . .\"*

Specifically, BPS:96/2001 activities are included in (1)(B), (D), (E),
(F), and (G), as well as (3).

The Center also assures participating individuals and institutions that
any data collected under the National Postsecondary Student Aid Study
and the related Postsecondary Longitudinal Studies shall conform to
NCES\' standards for protecting the privacy of individuals. Section
408(a)(1)(A) states that:

*\"The Center shall develop and enforce standards designed to protect
the confidentiality of persons in the collection, reporting, and
publication of data under this title.\"*

Further, Section 408(a)(2) states:

*\"No person may -*

*(A) use any individually identifiable information furnished under this
title for any purpose other than a statistical purpose;*

*(B) make any publication whereby the data furnished by any particular
person under this title can be identified; or*

*(C) permit anyone other than the individuals authorized by the
Commissioner to examine the individual reports;\"*

Penalties for misuse have been established in Section 408 (b)(6) for
which:

*\"Any person, who uses any data provided by the Center, in conjunction
with any other information or technique, to identify any individual
student, teacher, administrator, or other individual and who knowingly
discloses, publishes, or uses such data for a purpose other than a
statistical purpose, or who otherwise violates subparagraph (A) or (B)
of subsection (a)(2), shall be found guilty of a . . . felony and
imprisoned . . ., or fined . . ., or both.\"*

**I.A.2. Program Overview**

The BPS is part of the Postsecondary Longitudinal and Sample Surveys
(PLSS) program within the Postsecondary Studies Division (PSD) of the
National Center for Education Statistics (NCES). These postsecondary
cohort studies have been designed to overcome the problems of
elementary/secondary school cohort studies (such as High School and
Beyond \[HS&B\], National Education Longitudinal Study \[NELS:88\])
which lose analytic value as the number of students seeking the next
higher level of education is continuously reduced. To overcome this, the
PLSS surveys select a full base cohort from each new level. These
postsecondary cohort studies currently include three series based on the
National Postsecondary Student Aid Study (NPSAS):

**Beginning Postsecondary Students - BPS:90/92/94**

**Beginning Postsecondary Students - BPS:96/98/2001 -** through
2008**.**

**Baccalaureate and Beyond - B&B:93/94/97** - through 2005.

The BPS:96/2001 sample is made up of those first time beginning
postsecondary students identified in the 1996 NPSAS sample, a nationally
representative sample of all students in postsecondary education
regardless of level or institution type. Thus, the BPS:96/2001 sample is
nationally representative of all beginning postsecondary students who
first entered PSE in 1995-96. Similarly, the BPS:90/94 sample is
nationally representative of all beginning postsecondary students who
first entered PSE in 1989-90. No further follow-ups are planned for
BPS:90/94. BPS:96/2001 will be the second of several planned follow-up
surveys of the 1996 cohort.

Like BPS, Baccalaureate and Beyond (B&B) was based on NPSAS (NPSAS:93)
and will follow those who completed the baccalaureate degree in academic
year 1992-93. B&B follow-up studies occurred in 1994 and 1997, with the
next follow-up planned in 2002, and an additional follow-up, possibly in
2005. A second B&B cohort is planned for NPSAS:2000 which will include
only a one-year follow-up, B&B:2000/2001.

BPS tracks the progress of new college and vocational school entrants
through their undergraduate education and into the work force or
graduate education. BPS provides information to help assess the value of
a postsecondary education both to the student and to society. Results
from this effort and the remaining follow-up components will contribute
to the comprehensive national database designed to address a variety of
policy issues at the postsecondary education level. The series of BPS
studies has been designed to address several PSE issues:

**Persistence**

**Progress/Curriculum**

**Attainment/Outcome Assessment**

**Graduate/Professional School Access**

**Rate of Return**

BPS:96/2001 is the second follow-up survey planned for the 1996 cohort.
Because the time since entry into postsecondary education for the
BPS:96/2001 cohort will be a year longer than that for the similar
BPS:90/94 cohort, BPS:96/2001 will be structured so that information is
available for comparison with the earlier cohort ( over a four-year
period) as well as over the longer five-year period. The longer
five-year period for BPS:96/2001 will allow the identification of a
greater number of bachelor's degree completers, since nearly half take
longer than four years to complete the degree, with many of the
remaining persisters finishing within the fifth year.

BPS:96/2001 will supply information concerning timing of postsecondary
attainment (including degrees, awards, and certificates), academic and
social integration, application to and entry into graduate school, and
relationships between postsecondary enrollment and employment, family
formation, and civic participation.

**I.B. Quality Control**

NCES is firmly committed to determining how well each project meets its
goals, the quality of data collected, and implications for future
projects. Project quality control should be integrated into every phase
of the project. For instance, potential problems should be identified
early so that possible solutions are tested as part of the field test.
Item reliability and validity tests must be built into the data
collection efforts, non-response analyses should be conducted as part of
the final weighting process, and survey methodology and sample design
effects should be presented for use by all data users. Thus, statistical
quality control shall be incorporated into each stage as appropriate.

**I.C. NCES Standards**

All work conducted under this contract must at minimum meet the
standards and guidelines set forth in the publication [Standards and
Policies]{.underline}, March 16, 1987 and as amended by standards
implemented since that time. In addition, all final reports for major
products must at minimum meet the standards and guidelines in the [OERI
Publication Guide]{.underline}. Copies of these publications are
available on request from Dr. Marilyn M. McMillen at (202) 219-1781, or
by mail: National Center for Education Statistics, 555 New Jersey Ave.,
NW, Washington DC 20208-5654.

II. **Scope of Work**

Independently and not as an agent of the United States Government, the
Contractor shall provide all personnel, materials, services, and
facilities necessary for the project and perform the tasks as described
below.

The BPS:96/2001 study shall be an incrementally funded 42 month
contract. This study shall have four major components. The first shall
encompass all initial management and review tasks, including overall
project quality control (Task 1). This component shall encompass the
entire period of the project. The second component shall involve the
conduct and reporting of the field test (Task 2) from data element
development through OMB clearance, data collection and file creation,
and field test reporting. The third component shall involve the conduct
of the full scale survey (Task 3) and shall include stu­dent locating and
interview­ing, data file develop­ment, and methodology reporting. The
fourth component shall be comprised of weighting, creation of derived
variables, the construction of a tabulation system, and a descrip­tive
survey report (Task 4). The following tasks are among those needed to
adequately complete the BPS:96/2001 study. While this list is not
exhaustive, when coupled with the detailed specifications for the
deliverables, it should serve to illuminate the complexity of the
overall study and provide guidance in its conduct.

[Task 1.]{.underline} [Management]{.underline}

The contractor shall manage the collection of BPS:96/2001 data in an
efficient manner that fosters communications with staff, the NCES COTR,
and potential users of the data.

[Subtask 1.1]{.underline} [Post Award Conference]{.underline}

Within the first week after contract award, the contractor\'s project
director and other key project staff as identified in the pro­posal shall
hold a meeting with the NCES Contracting Officer\'s Techni­cal
Representative (COTR) and other appropriate NCES staff to review the
overall contract tasks, to identify potential problems and possi­ble
solutions, and to discuss areas of concern related to the pro­posed
project staffing plan and other management requirements. The primary
purpose of this meeting is to refine the man­agement, staffing, and
scheduling plans. These refine­ments are not to alter the specifications
of the con­tract, but to pro­vide management information for use by both
the contractor and the government in monitor­ing the work to be
performed. This confer­ence is also to help the contractor to make use of
the experience and materials that NCES staff have gained over the years.

[Subtask 1.2]{.underline} [Schedules]{.underline}

Due to the uncertainties of large data collection projects, the
contractor shall develop and maintain a detailed schedule for all
activities of the project. The schedule shall be updated monthly.

**Deliverables: Schedules**

[Subtask 1.3]{.underline} [Technical Review Panel]{.underline}

To obtain peer review of project plans and products and to foster
communications with potential users of the data, the contractor shall
establish a Technical Review Panel (TRP) of 12 non-Federal consultants
plus up to 15 Federal advisors and conduct 6 meetings. The 2-day
meetings shall be held in Washington, DC. The contractor shall prepare
packets, ship packets to TRP members, prepare and provide meeting
materials, and prepare minutes of TRP meetings. The TRP shall work with
the contractor to improve plans, products, and user-friendliness;
however, the TRP does NOT report to or advise NCES.

**Deliverables: List of potential TRP panelists**

**Pre-meeting information packets**

**Meeting agendas**

**Meeting materials**

**Meeting minutes**

[Subtask 1.4]{.underline} [Monthly Reports]{.underline}

The contractor shall report monthly on the progress made in
accomplishing the project tasks, the consumption of funds, problems
encountered, and plans for the next month.

**Deliverables: Monthly reports**

[Subtask 1.5]{.underline} [Integrated Monitoring System]{.underline}

The contractor shall develop and maintain an Integrated Monitoring
System (IMS) to foster communications with staff and the NCES COTR. The
contractor shall design the IMS to routinely produce information about
the project and provide access to this information to the NCES COTR.

**NCES Provided Material: BPS:96/98 Data Files and Documentation**

**Deliverables: Document Archive**

**BSP:96/2001 Data Library**

**BSP:96/2001 Bibliography**

**Relational Instrumentation Interface**

**Production reports**

**Confidentiality reports**

**Quality Control reports**

**Electronic Codebook input files**

[Task 2.]{.underline} [Field Test (FT)]{.underline}

The contractor shall develop all systems for data collection, prepare
materials for IMG/OMB forms clearance, train staff in the methods of
data collection, [test]{.underline} all data collection systems, and
report on the quality of the data collection systems as a field test
prior to the full-scale collection of BSP:96/**2001** data.

[Subtask 2.1]{.underline} [FT Sampling]{.underline}

The contractor shall use the BPS:95/97 field test sample. All
respondents and a subsampling of CATI/CAPI nonrespondents shall be
specified and scheduled for field data collection.

**Deliverables: FT Sampling specifications**

**FT Sample frame**

[Subtask 2.2]{.underline} [FT IMG/OMB Forms Clearance]{.underline}

The contractor shall prepare the IMG/OMB Forms Clearance package for
submission. The package shall request clearance for both the field test
and the full-scale collections.

**Deliverables: FT Data elements and justifications**

**FT IMG/OMB Forms Clearance Package**

**FT SF-83**

**FT Item wording list**

[Subtask 2.3]{.underline} [FT Data Collection]{.underline}

The contractor shall collect the field test data from the FT sample with
a target response rate of 92 percent. In addition, the contractor shall
determine the amount of response time associated with each data element
collected. Finally, the contractor shall re-collect data from a small
(50) number of FT sample respondents to determine the quality of the
data.

**Deliverables: FT Locating/tracing plan**

**FT CAPI executable**

**FT Training materials**

**Data element timing report**

**Debriefing report**

**Re-collection report**

**FT Data files**

[Subtask 2.4]{.underline} [FT Reporting]{.underline}

The contractor shall prepare a report documenting all activities,
methods, and outcomes of the field test.

**Deliverable: FT Methodology report**

[Task 3.]{.underline} [Full-scale (FS) Data Collection]{.underline}

The contractor shall modify all sampling and data collection systems as
needed depending upon the results of the field test. The contractor
shall prepare materials for IMG/OMB forms clearance and shall collect
data from the full-scale BSP:96/**2001** sample members.

[Subtask 3.1 Sampling]{.underline}

The contractor shall use the BPS:96/98 sample. All respondents and a
subsampling of CATI/CAPI nonrespondents shall be specified and scheduled
for field data collection in 2001.

**Deliverables: FS sampling specifications**

**FS sample frame**

[Subtask 3.2]{.underline} [IMG/OMB Forms Clearance]{.underline}

The contractor shall prepare the [IMG]{.underline}/OMB Forms Clearance
package for submission. The package shall request clearance for the
full-scale collection.

**Deliverables: Data elements and justifications**

**IMG/OMB Forms Clearance Package**

**SF 83**

**Final Item wording list**

[Subtask 3.3]{.underline} [Data Collection]{.underline}

The contractor shall collect the full-scale sample data with a target
response rate of 92 percent.

**Deliverables: Locating/tracing plan**

**CAPI executable**

**Training materials**

**Data files**

[Subtask 3.4]{.underline} [Methodology Report]{.underline}

The contractor shall prepare a report documenting all activities,
methods, and outcomes of the full-scale data collection.

**Deliverable: Methodology report**

[Task 4.]{.underline} [Descriptive Reporting]{.underline}

The contractor shall prepare a descriptive survey report based on the
2001 data.

[Subtask 4.1]{.underline} [Analysis Plan]{.underline}

The contractor shall develop specifications for derived variables, table
shells, and report structure.

**Deliverables: Derived variable specifications**

**Table shells**

**Descriptive report outline**

[Subtask 4.2]{.underline} [Data Analysis System]{.underline}

The contractor shall create the derived variables and a Data Analysis
System for the estimation of table values.

**Deliverable: Data Analysis System input files**

[Subtask 4.3]{.underline} [Descriptive Survey Report]{.underline}

The contractor shall prepare the descriptive survey report based on the
2001 data.

**Deliverable: Descriptive survey report**

[Subtask 4.4]{.underline} [Additional Special Tabulations as
required]{.underline}

The contractor shall prepare up to 5 additional sets of special
tabulations and related Data Analysis System files based on the 2001
data, as needed.

**Deliverable: Special tabulations and DAS files**

**III. Deliverable Specifications**

The specifications for all deliverables to be generated by the tasks
described in section II are presented below. Several components of the
Integrated Monitoring System (IMS) are included, but the IMS cannot be
considered as the sum of it's parts\--it is more comprehensive. The IMS
shall link the NCES COTR with project information, of all types.

Unless otherwise specified, deliverables shall not be physically
delivered to the NCES COTR. Instead, the NCES COTR shall be notified of
the deliverable\'s placement within the IMS. An important function of
the IMS from the NCES COTR\'s viewpoint is the IMS capability to
retrieve deliverables.

**III.1 Schedules (Subtask 1.2)**

For all activities within the project, the schedule shall detail the key
staff assigned, the projected start and end dates, and completion dates.
The schedule shall be updated monthly. For any monthly schedule, all
completion dates shall be entered and the future three (3) months
activities shall be detailed. There are only three static dates within
the schedule: \[1\] full scale data collection must begin by March,
2001; \[2\] accepted full-scale derived variable files must be delivered
by December, 2001; and \[3\] accepted descriptive survey report must be
delivered 2 weeks prior to contract termination.

Delivery specifications:

Each month (concurrent with the monthly report) an update of \[1\]
off-the-shelf software scheduling file (not the software itself, but
rather the activity/date file) and \[2\] ASCII text file \"print-out\"
of the schedule shall be included within the IMS.

**III.2 List of potential TRP panelists (Subtask 1.3)**

Fifteen (15) potential panelists shall be listed. Names, addresses,
telephone numbers, affiliations, prior TRP memberships, and annotated
resumes shall be included. To maintain continuity with the BPS:96/98 TRP
(see appendix A), as many of the potential panelists as are available
shall be retained.

Delivery specifications:

Six (6) weeks prior to the first TRP meeting the list of potential TRP
panelists shall be delivered as a Word file. Information about selected
TRP members shall be included within the IMS with off-the-shelf database
software for the generation of personalized letters and mailing labels.

**III.3 Pre-meeting (TRP) information packets (Subtask 1.3)**

These deliverables are materials (such as data element lists, collection
problem reports, etc.) that shall be delivered to TRP members so that
they can be prepared for discussion at the meetings. Six (6) TRP
meetings of 2-day duration shall be held in Washington, DC. Pre-meeting
information packets will be delivered to TRP members one (1) week prior
to TRP meetings.

Delivery specifications:

Two (2) weeks prior to each TRP meeting, pre-meeting information packets
shall be delivered to the COTR as Word files for review and approval.

**III.4 (TRP) Meeting agendas (Subtask 1.3)**

These deliverables provide structure for TRP meetings in terms of times,
topics, and discussion leaders. The expected topics for the six (6) TRP
meetings are as follows:

1\. FT data elements and FT nonrespondent sampling

2\. FT data elements (timing)

3\. Derived variables and descriptive survey report

4\. Data files and electronic codebooks

5\. Data analysis system

6\. Descriptive survey report

Delivery specifications:

Two (2) weeks prior to each TRP meeting, the meeting agenda shall be
delivered as Word files.

**III.5 (TRP) Meeting materials (Subtask 1.3)**

These materials include documents and drafts that are discussed at the
TRP meetings.

Delivery specifications:

Two (2) days prior to each TRP meeting, the meeting materials shall be
delivered as Word files.

**III.6 (TRP) Meeting minutes (Subtask 1.3)**

These minutes document the TRP discussions.

Delivery specifications:

Three (3) weeks after each TRP meeting, the meeting minutes shall be
delivered as Word files.

**III.7 Monthly reports (Subtask 1.5)**

The monthly report shall detail the progress made in accomplishing the
project tasks, problems encountered, and plans for the next month. By
attachment, the financial status of the project shall be described, in
total and by task, including detailed monthly charges by named staff and
comparisons with projected spending.

Delivery specifications:

Monthly (on or before the day corresponding to the contract award date)
progress and financial reports shall be delivered as Word files.

**III.8 (IMS) Document archive (Subtask 1.5)**

All documents (including dated drafts, E-mail communications, meeting
notes, etc.) generated during the life of the project shall be stored in
the document archive. The archive shall identify file name, dates,
author(s), format, and key words corresponding to each document.

Delivery specifications:

Monthly updates (corresponding to the monthly reports) using
off-the-shelf software shall be delivered. A listing of each document\'s
vitals (i.e., file name, dates, author(s), format, and key words) shall
be an ASCII text file.

**III.9 BSP:96/2001 Data library (Subtask 1.5)**

All data files from prior rounds of BPS:96 data collections shall be
stored and documented. These include 1996 and 1998 full-scale
collections and 1995 and 1997 field test collections. When completed,
the 2000 FT and 2001 full-scale data files shall be added to the
library.

Delivery specifications:

Within six (6) weeks of contract award, the ASCII data files and
electronic codebook documentation for the 1995-98 BPS data shall be
available in the Data Library. (NCES will provide these files within
four weeks of contract award.) A monthly listing of the contents of the
Data Library shall be delivered as an ASCII text file.

**III.10 BSP:96/2001 Bibliography (Subtask 1.5)**

All publications using BPS:96 data shall be cataloged. In addition to
NCES publications, titles found in searches of ERIC and Dissertation
Abstracts shall be included.

Delivery specifications:

Within six (6) weeks of contract award, NCES-sponsored BPS:96
publications shall be cataloged using off-the-shelf database software.
Within six (6) months of contract award, titles from ERIC and
Dissertation Abstract searches shall be included. The bibliography shall
be updated at six (6) month intervals.

**III.11 Relational Instrumentation Interface (Subtask 1.5)**

The instrumentation for the collection of BPS:**2001** data shall
consist of a PC-based, scripted, windowed computer assisted telephone
interview (CATI) and computer assisted personal interview (CAPI)
procedures with preload and recursive fills. The CAPI, operating on a
laptop PC, shall be undistinguishable from the CATI system in terms of
screen text, skip patterns, and preloads/fills.

The development of screens for these procedures shall be controlled and
documented by a Relational Instrumentation Interface (RII). The main
function of the RII is to relationally develop CATI/CAPI screens from
the data elements. The essential linkages are as follows:

\[1\] Data elements

\[2\] Variables

\[3\] CATI/CAPI screens

\[4\] Sources (Preload, Prior variable, Screen entry)

\[5\] Range restrictions

\[6\] Sample restrictions

\[7\] Storage parameters

The CATI/CAPI system shall accept translated text from the RII for
\[3\], \[4\], \[5\], \[6\], and \[7\]\--thus, it shall be scripted.
Project staff, not programmer support staff, shall develop the text for
the RII that shall be translated into the CATI/CAPI instructions.

Look-up table software for IPEDS codes, industry and occupation codes,
major field of study codes, and a key word glossary shall be available
within the CATI/CAPI system\--thus, it shall be windowed.

The following list of data elements represent approximately 90 percent
of the data elements that shall be included within the RII:

**Data Elements Policy & Research Issues**

(1)\* First-time beginner status Determine eligibility

Identify as FTB if NPSAS:96

or BPS:96/98 nonrespondent Enrolled at NPSAS institution between

May 1,1995-April 30,1996?

1.  Was this the first time enrolled in any postsecondary after high
    school?

2.  Taking courses for credit, towards a degree, or for a specific
    occupation?

    \*Collect only from new respondents not previously identified as FTB

    **Data Elements Policy & Research Issues**

    (2)\* Additional/ missing background information when Background/

    student began at NPSAS school demographics

    Traditional/nontraditional

    Date of birth students

    Gender

    Race/ethnicity

    Language spoken in the home

    Parental education level

    Parental job characteristics

    Type of high school diploma/GED

    Date of high school graduation/GED

    Citizenship when began at NPSAS school

    Marital status when began

    Number of dependents when began

    \(3\) Enrollment information Persistence/progress

    Retention

    \(a\) Information for each school attended Transfers

    (since last interview): Attainment/outcome

3.  Type of institution

4.  Control of institution

5.  For each institution, classify as:

    Undergraduate

    Graduate or first professional

    Special student---undergraduate

    Special student---graduate

6.  Full time/part time

7.  Dates of attendance for each institution

8.  Major

9.  Completions

    \(b\) Information for each school attended as undergraduate
    Persistence/progress

10. Program Attainment/outcome

11. Type of residence Student work

12. Relation of job to area of study

13. Participation in campus activities

14. Interactions with faculty

    \* Collect only if not previously on file

    **Data Elements Policy & Research Issues**

15. Satisfaction with curriculum

16. Satisfaction with school services

    Academic counseling

    Career counseling

    Job placement

    Campus facilities

    Cultural activities

    Personal safety

    Grade point average

    \(c\) If attended multiple schools as undergraduate (since last
    interview):

17. Reasons for attending this school: (transfer/additional
    courses/summer school/co-enrollment)

    If intention was to transfer:

18. Did the school accept any transfer credits?

19. Change program or degree objective?

20. Complete the program with certificate or degree?

    If not a transfer, purpose of attending:

    (lower cost/unavailable courses/finish sooner)

    \(d\) If enrollment terms were not continuous:

21. Did you decide to take a break from school?

22. Reasons?

    \(e\) Overall grade point average for undergraduate study to
    date/major to date

    \(f\) Work while in school?

23. On/off campus?

24. Work-study, internship, co-op?

25. Number of hours per week?

    **Data Elements Policy & Research Issues**

    \(4\) Characteristics of enrollment\--[graduate]{.underline}
    Persistence/progress

    Attainment/outcome

    \(a\) Current graduate enrollment: Student work

26. Program Graduate access

27. Type of residence Graduate education

28. Relation of job to area of study Rate of return

29. Participation in campus activities

30. Satisfaction with curriculum

31. Satisfaction with school services

    \(b\) Work while in school?

32. On/off campus?

33. Assistantship/fellowship?

34. Work-study, internship, co-op?

35. Number of hours per week?

    \(5\) Application to graduate school Graduate access

    Graduate education

    \(a\) Information regarding application Rate of return

36. When first applied?

37. To how many schools?

38. Information for first and second choice:

> Intended field of study
>
> Applied for financial aid?

(b) Graduate/admissions tests taken, date taken and scores

(c) Intended date for program completion

**Data Elements Policy & Research Issues**

\(6\) Learning experiences and outcomes Persistence/progress

Labor market

\(a\) Vocational program students (entire program): Attainment/outcome

39. Satisfaction with career preparation

40. Satisfaction with training to use tools/equipment

41. Satisfaction with counseling/placement services

```{=html}
<!-- -->
```
(b) Academic program students

```{=html}
<!-- -->
```
42. Academic experience as undergraduate

    Use of the library

    Use of computer labs

    Use a personal computer

    Received lower grades than expected

    Participated in distance learning

    \(7\) If [not]{.underline} enrolled and no BA Persistence/progress

    Labor market

    \(a\) For last institution attended

43. Type of degree program (certificate/AA/BA)

44. Major/vocational program

45. Full time/part time

46. Class level (sophomore/junior)

47. Intend to complete BA?

    \(b\) If enrollment terms were not continuous:

48. Period of break

49. Reasons for a break

    \(8\) Non-traditional students (not beginning right after
    Persistence/progress

    high school, married, or dependents) Attainment/outcome

    Labor market

    \(a\) Account for breaks in education

50. \*Between high school and undergraduate

51. Between undergraduate institutions transfer?

52. Between undergraduate and graduate school

    \(b\) Difficulties/problems attending school?

53. Child care

54. Travel arrangements

55. Living arrangements

56. School/work overlap

    **Data Elements Policy & Research Issues**

    \(9\) Financing of postsecondary
    education\--[undergraduate]{.underline} Persistence/progress

    [graduate]{.underline} Student debt

    Preload from Pell/CPS/NSLDS merges for data since Education costs

    Last BPS merge. Ask only for last year enrolled if Graduate access

    missing:

57. Amount of tuition and fees (before financial aid)

58. Amounts for books and supplies

59. Living expenses

60. Federal grant/loan information

    Ask if:

61. Financial aid received during: Last term enrolled as undergraduate

    Last term enrolled as graduate

    Type of aid if yes:

62. Grants

63. Scholarships

64. Fellowship/assistantship-teaching; assistantship-research

65. Work-study

66. Student loans

67. Assistance from employers or union

68. Other

```{=html}
<!-- -->
```
(b) Other sources of financial support for [undergraduate]{.underline}

-   Earnings

-   Savings

-   Parents' assistance

-   Loans

(b) Total undergraduate loans, all sources

Amount from parents/relatives

\(f\) Total graduate loans, all sources

Amount from parents/relatives

\(10\) Work experience---work for pay since last interview
Persistence/progress

Rate of return

> \(a\) Number of jobs held since 1998 (including part time) Labor
> market

(b) If work/school overlap, what is primary role?

\(d\) Relationship of job to area of study

**Data Elements Policy & Research Issues**

\(e\) First job after end of enrollment:

> If YES:

69. Number of hours per week

70. Hourly/ weekly/ annual wages

71. Job characteristics/duties

72. Date when began this job or position

73. Held this position or a similar job before attending school?

74. If yes, continued working at it while enrolled?

75. If yes, how many hours per week?

76. If no, did the school help place you in a new job?

77. How is job related to studies or career? (able to apply what was
    learned/use tools, equipment, or skills learned/not related)

78. Did the education/training received help qualify you for a new job
    or better position than you had before?

79. Received job placement assistance from school

    \(f\) Current or most recent employment:

80. Job characteristics/duties

81. Number of hours per week

82. Wages

83. Length of time in this job or position

84. Relationship to program of study

85. Continued working at it while enrolled?

86. If yes, how many hours per week?

87. Consider yourself to be employee or student?

\(11\) Family information and other demographics Background /

demographics

\(a\) Current marital status Persistence/progress

> \(b\) Spouse's level of education (update if married)
>
> \(c\) Parents' level of education (update if living with parents)

(b) Household composition

\(e\) Household income

**Data Elements Policy & Research Issues**

> \(f\) Sources of income

-   Own earnings

-   Spouse's income

-   Business income

-   Interest/dividend income

-   AFDC/other non-taxable

-   Other

    \(g\) If respondent owns the following

-   Own home

-   Other residence

-   Car, truck

-   A farm or business

-   Investments

\(12\) Expectations, goals, plans Persistence/progress

Labor market

-   Immediate educational goals Attainment/outcome

-   Long term educational goals

-   Expected career plans

The other 10 percent of the data elements shall be identified during the
first TRP meeting and/or the IMG/OMB clearance process.

Delivery specifications:

Within four (4) weeks of contract award the RII shall be established
within the IMS using off-the-shelf database software. The RII shall be
updated on a flow basis through FT IMG/OMB forms clearance and following
examination of the results of the field test. The RII database software
shall have the capability to produce lists of data elements, skip
pattern instructions, preload designations, fill designations, and range
checks similar to the listing above as ASCII text files. In addition the
RII database software shall have the capability to produce translatable
files compatible with the CATI/CAPI systems.

**III.12 Production reports (Subtask 1.5)**

The status of all cases in the data collection system, by day of
operations, shall be presented in daily production reports. The
following is a minimum of the status categories that shall be displayed:

\[1\] Case not yet worked

\[2\] In location/trace

\[3\] Unlocatable

\[4\] In CATI

\[5\] Completed CATI

\[6\] CATI call back

\[7\] CATI partial complete, no call back

\[8\] CATI refusal

\[9\] In CAPI

\[10\] Completed CAPI

\[11\] CAPI partial complete, no recontact

\[12\] CAPI refusal

\[13\] Ineligible/deceased

Delivery specifications:

One day before the beginning of data collection, the spreadsheet with
days as rows and the status categories as columns shall be loaded into
the IMS. During CATI/CAPI operations, the production report shall be
appended daily.

**III.13 Confidentiality reports (Subtask 1.5)**

Confidentiality reports shall be in two (2) parts. Part 1 shall be a
list of all project staff with access to restricted BPS data. Part 2
shall be a completed (signed and notarized) set of NCES Affidavits of
Nondisclosure for all project staff listed (in part 1).

Delivery specifications:

Within one (1) week of contract award, Part 1 shall be included within
the IMS as a Word file. Each NCES Affidavit of Nondisclosure shall be
completed prior to access to restricted BPS data. The completed NCES
Affidavits of Nondisclosure shall be mailed to the NCES COTR in monthly
batches corresponding to the monthly report. Part I shall be updated on
a flow basis.

**III.14 Quality control reports (Subtask 1.5)**

The quality of CATI operations shall be monitored using the statistical
quality control procedures of W.A. Shewhart and W.E. Deming[^1]. The
operator by time population of CATI activities shall be randomly sampled
and monitored for the following events:

\[1\] No observed errors or deviations

\[2\] Deviation not resulting in error

\[3\] Error with recovery

\[4\] Error without recovery

The quality of CAPI operations, from a monitoring point of view, is more
difficult to assess. The use of supervisory actions, and other methods
shall be evaluated as methods of gauging the quality of CAPI operations
during the field test.

Delivery specifications:

One day before the beginning of CATI operations, the spreadsheet with
days as rows and the event categories as columns shall be loaded into
the IMS. During CATI operations, the quality control report shall be
appended daily.

**III.15 Electronic Codebooks (Subtask 1.5)**

Electronic codebook software enhances the usage of data files. Users are
presented lists of fully-labeled variables with associated frequency
distributions (unweighted) and associated item wording. Users\'
selections of variables are converted into fully-labeled SPSS-PC and
PC-SAS code for extraction of analysis files.

Delivery specifications:

Within four (4) weeks of contract award, the BPS:98 electronic codebook
system shall be available within the IMS.

Development of the electronic codebook for the BPS:95/00 field test data
files and for the BSP:96/**2001** full-scale data files shall be
documented within the project schedule (see subtask 1.2).

**III.16 FT Sampling specifications (Subtask 2.1)**

FT CATI sampling specifications shall present strata and expected rates
for both the field test samples and the plans for the full-scale sample.
This shall include differential sampling rates based on previous
response status and locating difficulty.

Delivery specifications:

Two (2) weeks prior to the first TRP meeting, a draft of the FT sampling
specifications shall be delivered as a Word file. Two (2) weeks after
the first TRP meeting, the final FT sampling specifications shall be
delivered as a Word file.

**III.17 FT Sample frame (Subtask 2.1)**

Based on the accepted FT sampling specifications, the BPS:95 FT sample
frame shall be revised for use in 2000.

Delivery specifications:

Eight (8) weeks after the start of CATI operations on the FT sample, the
FT sample frame shall be delivered as an ASCII text file with
documentation.

**III.18 FT Data elements and justifications (Subtask 2.2)**

For the data elements included within the RII, justifications suitable
for inclusion within the IMG/OMB package shall be developed.

Delivery specifications:

Two (2) weeks prior to the first TRP meeting, a draft of the FT data
elements and justifications shall be delivered as a Word file. One (1)
week after the first TRP meeting, the second draft FT data elements and
justifications shall be delivered as a Word file for NCES
inter-divisional review. One (1) week after NCES inter-divisional
review, the final FT data elements and justifications shall be delivered
as a Word file.

**III.19 FT IMG/OMB Forms Clearance Package (Subtask 2.2)**

The FT IMG/OMB Forms Clearance Package shall include introduction,
project justifications, purpose and use of data, descriptions of
collection methods, descriptions of efforts to identify duplication,
descriptions of the suitability of existing data, methods used to
minimize burden, frequency of data collection, adherence to guidelines
in 5 CFR 1320.6, consultations, confidentiality, sensitive questions,
estimates of costs, estimates of response burden, publication plans and
schedules, statistical methodology, sampling, data elements and
justifications, and sample notifications. This package shall request
clearance for field test and full-scale activities.

Delivery specifications:

One (1) week after NCES inter-divisional review of the FT data elements
and justifications, the FT IMG/OMB Forms Clearance Package shall be
delivered as a Word file. During the 120 day clearance period, two (2)
revisions for IMG and OMB concerns shall be delivered as Word files.

**III.20 FT SF-83 (Subtask 2.2)**

Information needed to complete blocks #13 and #17 on Standard Form 83,
which accompanies the IMG/OMB clearance package, shall be delivered.

Delivery specifications:

One (1) week after NCES inter-divisional review of the FT data elements
and justifications, the FT SF-83 information shall be delivered as a
Word file.

**III.21 FT Item wording list (Subtask 2.2)**

OMB and IMG require documentation of the final CATI/CAPI screens used
for data collection.

Delivery specifications:

One (1) week prior to CATI operations on FT sample \[6\], an ASCII text
file presenting all CATI windows and coding structures shall be
delivered.

**III.22 FT Locating/tracing plan (Subtask 2.3)**

One of the most difficult jobs will be tracing and locating BPS:95 field
test sample members in 2000. All locating/tracing information from
1995-98 was stored on compact disks in relational database format. These
compact disks shall be provided by the Research Triangle Institute,
Research Triangle Park, North Carolina. In addition to planning the
steps for pre-CATI locating activities, strategies for tracing during
CATI, and field efforts, the FT Locating/tracing plan shall include an
evaluation of the 1995-98 information stored on the compact disks.

Delivery specification:

Two (2) months prior to the start of CATI operations on the FT sample,
the FT Locating/tracing plan shall be delivered as a Word file.

**III.23 FT CAPI executable (Subtask 2.3)**

Based on the accepted FT data elements, the FT CATI and (identical) FT
CAPI shall be developed.

Delivery specification:

Two (2) months prior to the start of CATI operations on the FT sample,
the FT CAPI executable shall be delivered.

**III.24 FT Training materials (Subtask 2.2)**

Materials used for the training of trace/location staff, CATI/CAPI
operators, and quality control monitors include mock interview sessions,
glossaries of terms, procedures for refusal conversion, and procedures
for system operations.

Delivery specifications:

One (1) week prior to CATI operations, the FT training materials shall
be delivered as Word files.

**III.25 Data element timing report (Subtask 2.3)**

The data element timing report shall detail the amount of time in
minutes (average and maximum) required for CATI operations with FT
sample for each data element.

Delivery specifications:

Two (2) weeks prior to the second TRP meeting, the data element timing
report shall be delivered as a spreadsheet file.

**III.26 Debriefing report (Subtask 2.3)**

The experiences of CATI/CAPI operators and trace/location staff during
the field test shall be documented in a debriefing report.

Delivery specifications:

Two (2) weeks after termination of CATI/CAPI operations, the debriefing
report shall be delivered as a Word file.

**III.27 Re-collection report (Subtask 2.3)**

Qualitative comparisons of the two interviews conducted with FT sample,
the comments obtained from these respondents, and comments obtained from
the reinterview operators shall be documented in the re-collection
report.

Delivery specifications:

Two (2) weeks after termination of CATI/CAPI operations, the
re-collection report shall be delivered as a Word file.

**III.28 FT Data files (Subtask 2.3)**

The data collected during the field test shall be stored in a series of
files for the analyses needed for the FT methodology report and for
secondary analyses. (The documentation for the FT data files shall be an
electronic codebook, see IMS specification.)

Delivery specifications:

Two (2) months following termination of CATI/CAPI operations, the FT
data files shall be delivered as ASCII text files with fixed variable
positions. The maximum record length shall be less than 1024 characters.

One (1) month following acceptance of the Derived Variable
Specifications (see subtask 4.1), an ASCII text file of derived
variables based on field test data shall be delivered.

**III.29 FT Methodology report (Subtask 2.4)**

All aspects of the field test activities and results shall be documented
in the FT methodology report. Chapters within the FT methodology report
shall include an introduction with a discussion of the history of BPS in
general and the field test sample(s); a description of the collection
systems developed; timing and response rates for data elements; quality
measures (quality control monitoring and re-collection); system
performance in terms of tracing/location rates and times, CATI yields,
and CAPI yields; and significant problem areas.

Delivery specifications:

Two (2) months following delivery of the FT data files, the FT
methodology report shall be delivered as a Word file. During the six
month period of NCES publication review, this report shall be revised to
reflect the concerns of (A) Division statistician review, (B) Associate
Commissioner review, (C) Adjudication panel review, and (D) Chief
statistician review.

**III.30 FS Sampling specifications (Subtask 3.1)**

The sampling specifications for the full-scale collection shall be
adjusted from the FT CATI sampling specifications to reflect the
findings of the field test.

Delivery specifications:

Eight (8) weeks after the start of the full-scale collection, the FS
sampling specifications shall be delivered as a Word file.

**III.31 FS Sample Frame (Subtask 3.1)**

Based on the accepted FS sampling specifications, the BPS:**2001**
sample frame shall be developed.

Delivery specifications:

One (1) week prior to CAPI operations on the full-scale sample, the FS
sample frame shall be delivered as an ASCII text file with
documentation.

**III.32 Data Elements and Justifications (Subtask 3.2)**

For the data elements identified for full-scale collection,
justifications shall be developed. (If IMG/OMB clearance of the field
test extends to the full-scale, this deliverable will describe the
deletions and changes in field test data elements.)

Delivery specifications:

Two (2) weeks prior to submission of the IMG/OMB Forms Clearance Package
for the full-scale collection, the data elements and justifications
shall be delivered as a Word file.

**III.33 IMG/OMB Forms Clearance Package (Subtask 3.2)**

The IMG/OMB Forms Clearance Package shall include introduction, project
justifications, purpose and use of data, descriptions of collection
methods, descriptions of efforts to identify duplication, descriptions
of the suitability of existing data, methods used to minimize burden,
frequency of data collection, adherence to guidelines in 5 CFR 1320.6,
consultations, confidentiality, sensitive questions, estimates of costs,
estimates of response burden, publication plans and schedules,
statistical methodology, sampling, data elements and justifications, and
sample notifications. (If IMG/OMB clearance of the field test extends to
the full-scale, this deliverable will describe the deletions and changes
in the above sections.)

Delivery specifications:

One (1) week after NCES inter-divisional review of the data elements and
justifications, the IMG/OMB Forms Clearance Package shall be delivered
as a Word file. During the 120 day clearance period, two (2) revisions
for IMG and OMB concerns shall be delivered as Word files.

**III.34 SF 83 (Subtask 3.2)**

Information needed to complete blocks #13 and #17 on Standard Form 83,
which accompanies the clearance package, shall be delivered.

Delivery specifications:

One (1) week after NCES inter-divisional review of the data elements and
justifications, the SF 83 information shall be delivered as a Word file.

**III.35 Final Item Wording List (Subtask 3.2)**

OMB and IMG require documentation of the final CATI/CAPI screens used
for data collection.

Delivery specifications:

One (1) week prior to full-scale CATI operations, an ASCII text file
presenting all CATI windows will be delivered.

**III.36 Locating/tracing plan (Subtask 3.3)**

Based on the results of the FT, the locating/tracing plan for the
full-scale data collection shall be developed.

Delivery specification:

Two (2) months prior to the start of CATI operations on the full-scale
sample, the locating/tracing plan shall be delivered as a Word file.

**III.37 CAPI executable (Subtask 3.3)**

Based on the accepted data elements, the CATI and (identical) CAPI shall
be developed.

Delivery specification:

Two (2) months prior to the start of CATI operations on the full-scale
sample, the CAPI executable shall be delivered.

**III.38 Training materials (Subtask 3.3)**

Materials used for the training of trace/location staff, CATI/CAPI
operators, and quality control monitors include mock interview sessions,
glossaries of terms, procedures for refusal conversion, and procedures
for system operations.

Delivery specifications:

One (1) week prior to full-scale CATI operations, the training materials
shall be delivered as Word files.

**III.39 Data files (Subtask 3.3)**

The data collected during the full-scale operations shall be stored in a
series of files for the analyses needed for the methodology report, the
descriptive survey report, and for secondary analyses. (The
documentation for the data files shall be an electronic codebook, see
IMS specification.)

Delivery specifications:

One (1) month following termination of CATI/CAPI operations, the data
files shall be delivered as ASCII text files with fixed variable
positions. The maximum record length shall be less than 1024 characters.
One (1) month following acceptance of the derived variable
specifications (see subtask 4.1), an ASCII text file of derived
variables shall be delivered.

**III.40 Methodology report (Subtask 3.4)**

All aspects of the full-scale collection activities and results shall be
documented in the methodology report. Chapters within the methodology
report shall include an introduction with a discussion of the history of
BPS in general; a synopsis of the field test; a description of the
collection systems developed; response rates for data elements; quality
measures (quality control monitoring); system performance in terms of
tracing/location rates and times, CATI yields, and CAPI yields;
weighting and design effects; and significant problem areas.

Delivery specifications:

One (1) month following delivery of the data files, the methodology
report shall be delivered as a Word file. During the six month period of
NCES publication review, this report shall be revised to reflect the
concerns of (A) Division statistician review, (B) Associate Commissioner
review, (C) Adjudication panel review, and (D) Chief statistician
review. One (1) month following adjudication, the methodology report
shall be delivered as a Word file with an associated HTML file.

**III.41 Derived variable specifications (Subtask 4.1)**

Approximately 250 new variables shall be specified as derivations from
the 1996 through 2001 data. These derived variables shall be composites
of one or more variables that have the potential for inclusion within
the descriptive survey report. The classes of derived variables include
postsecondary activities, labor force activities, family formation, life
goals and values, and demographics. Most of these new derived variables
will be based on the 2001 data, but a few will modify/correct/enhance
existing derived variables from the 1996-98 data.

Delivery specification:

Two (2) weeks prior to the third TRP meeting, a first draft of the
derived variable specifications shall be delivered as a Word file. Three
(3) weeks following the third TRP meeting, the second draft of the
derived variable specifications shall be delivered as an ASCII text file
with PC-SAS or SPSS-PC code detailing each specification. Two (2) months
following termination of CATI/CAPI operations, the final derived
variable specifications shall be delivered as an ASCII text file with
PC-SAS or SPSS-PC code detailing each specification including
adjustments for missing values within the data.

**III.42 Table shells (Subtask 4.1)**

Sixty (60) shells for tables planned for inclusion within the
descriptive survey report shall be developed. Tables shall be specified
with rows, columns, and sample filters for derived variables.

Delivery specification:

Two (2) weeks prior to the third TRP meeting, a first draft of the table
shells shall be delivered as a Word file. Three (3) weeks following the
third TRP meeting, the second draft of the table shells shall be
delivered as a Word file. Two (2) months following termination of
CATI/CAPI operations, the final table shells shall be delivered as a
Word file detailing adjustments for low frequencies within the data.

**III.43 Descriptive report outline (Subtask 4.1)**

An annotated outline of the descriptive survey report shall be
developed. Table topics outlined shall include postsecondary activities,
labor force activities, family formation, and life goals and values.
Further, an essay (15-20 pages) on a policy relevant topic shall be
included.

Delivery specification:

Two (2) weeks prior to the third TRP meeting, a first draft of the
descriptive report outline shall be delivered as a Word file. Three (3)
weeks following the third TRP meeting, the second draft shall be
delivered as a Word file. Two (2) months following termination of
CATI/CAPI operations, the final descriptive report outline shall be
delivered as a Word file.

**III.44 Data Analysis System (Subtask 4.2)**

Based on the 250 new derived variables and the 1998 derived variables, a
data analysis system shall be developed for the estimation of table
values.

Delivery specification:

One (1) month following the acceptance of the derived variables data
file, files for the Data Analysis System (DAS) shall be delivered.

**III.45 Descriptive survey report (Subtask 4.3)**

As specified in the accepted descriptive report outline and using the
accepted DAS to produce tables specified in the accepted table shells,
the descriptive survey report shall be developed. In addition to text
describing group differences, this report shall include approximately 15
graphs and/or charts for the most interesting findings and a 2-page set
of bullets serving as highlights.

Delivery specification:

Six (6) months prior to the termination date of the contract, the
descriptive survey report shall be delivered as a Word file. During the
six month period of NCES publication review, this report shall be
revised to reflect the concerns of (A) Division statistician review, (B)
Associate Commissioner review, (C) Adjudication panel review, and (D)
Chief statistician review. One (1) month following adjudication, the
descriptive survey report shall be delivered as a Word file with an
associated HTML file.

**III.46 Special tabulations and DAS files (Subtask 4.4)**

Up to 5 special analyses tabulations may be required to answer specific
policy-related questions not addressed in the descriptive report. The
creation of these tabulations will require that additional variables be
approved and added to the DAS. Therefore, new DAS files will be required
to prepare these tabulations. These tabulations shall include a 2-page
set of bullets serving as highlights.

Delivery specification:

One (1) month following the acceptance of the new derived variables data
file, files for the Data Analysis System (DAS) shall be delivered which
include these variables.

Two (2) months after delivery of the DAS files, the special tabulations
shall be delivered.

**IV. Inspection and Acceptance Procedures**

The contractor shall consult with the NCES COTR before making any major
decisions or developing the required deliverables. To facili­tate this
communication, the contractor shall make frequent phone calls and visits
to NCES to discuss potential project problems and progress. The
contractor shall set up an electronic system for transferring
information via electronic mail and microcomputers. In addition, the
contractor shall provide the COTR access to files and systems within the
Integrated Monitoring System and remote access for monitoring CATI
operations.

The contractor shall prepare all reports following the guidelines
refer­enced by NCES\'s standards. The NCES review process may take 2-6
months, depending on the type of report. It is paramount that schedules
for publica­tion releases be kept and that NCES standards for all phases
of report production be followed. All materials must be approved before
release. The contractor shall not release any data in raw or derived
form to anyone without NCES\'s review and approval.

**V. Additional Compliance Requirements**

**V.A. Protection of data**

The confidentiality of individually identifiable information contained
in documents, data, and other information supplied by the National
Center for Education Statistics, U.S. Department of Education (NCES/ED)
or acquired in the course of performance under this contract, furnished
under the provisions of section 406 of the General Education Provisions
Act (20 U.S.C. 1221e-1), is a material aspect of the contract, and must
be maintained, as provided in Paragraphs 4(A) through (F) of Section 406
of the General Education Provisions Act and 5 U.S.C. 552a. Therefore,
the contractor shall maintain the confidentiality of all documents,
data, and other information supplied by NCES/ED or acquired in the
course of performance of this contract, except for any documents or
other information specifically designated as nonconfidential by NCES/ED.
The contractor shall take such measures as are necessary to maintain the
required security.

**V.B. Control file maintenance**

The contractor shall store and keep all computer files, including all
locator information and other control files, in a secure place for six
years or until conveyed to NCES and written permission is given by NCES
through the Contracting Officer to otherwise dispose of the files.

**VI. Period of performance**

The length of this contract shall be 42 months from the contract start
date.

**Attachment A. BPS:96/98 TRP**

**BPS:96/98 TRP NON-FEDERAL MEMBER LIST**

Dr. Carol Fuller

National Association of Independent Colleges and Universities

Dr. Elinor Miller Greenberg

University of Colorado

Dr. Jacqueline King

American Council on Education

Charles S. Lenth

Education Commission of the States

Dr. Jim Palmer

Illinois State University

Kent Phillippe

American Association of Community Colleges

Dr. Jacob O. Stampen

University of Wisconsin

Dr. Dawn Terkla

Tufts University

Dr. Vincent Tinto

Syracuse University

[^1]:     ^?^W.E. Deming, \"Some Principles of the Shewhart Methods of
    Quality Control\", [Mechanical Engineering]{.underline}, vol. 66,
    pp. 173-177, March, 1944.