bayesian computation with r solutions manual

D72C257D608643E72BA2744B29ACC0EA

Bayesian Computation With R Solutions Manual

1 / 8

bayesian computation with r solutions manual

D72C257D608643E72BA2744B29ACC0EA

2 / 8

bayesian computation with r solutions manual

D72C257D608643E72BA2744B29ACC0EA

Please create account

to preview this

document

3 / 8

bayesian computation with r solutions manual

D72C257D608643E72BA2744B29ACC0EA

Please create account

to preview this

document

4 / 8

bayesian computation with r solutions manual

D72C257D608643E72BA2744B29ACC0EA

5 / 8

bayesian computation with r solutions manual

D72C257D608643E72BA2744B29ACC0EA

6 / 8

bayesian computation with r solutions manual

D72C257D608643E72BA2744B29ACC0EA

7 / 8

bayesian computation with r solutions manual

D72C257D608643E72BA2744B29ACC0EA

physics lab manual answer key pearson doosan puma 700 programming manual visual fields via the visual  pathway pearson wisc iv scoring manual cambridge academic english b2 upper intermediate teachers book an  integrated skills course for eap why jazz happened by marc myers dec 10 2012 legalines contracts adaptable to  the sixth edition of the farnsworth casebook laboratory manual light answers honda cb 250 manual eb 480  service repair manual caterpillar 315b service manual fra track safety manual acer h223hq manual 4500 rds  allison transmission parts manual stewart single variable calculus solutions manual rennie and robertons  textbook of neonatology expert consult online and print 5e cleveland clinic cedar ponit tickets 2014 windows  2015 user manual 1987 yamaha fz 600 service manual gl1100 repair manual revolutionary diet plan lose weight fast with healthy diet perfect 10 posture applying pilates and posture training for success in gymnastics and other sports the methods and skills of history a practical guide yanmar marine diesel engine 6ly2 ste 6ly2a stp 6lya stp service repair manual instant download cpt coding study guide manual for craftsman lt1000 lawn tractor use of representations in reasoning and problem solving analysis and improvement new perspectives on learning and  instruction glaucoma expert consult premium edition enhanced online features print and dvd 2 volume set 1e  diffusion through a membrane rover 2 stroke xl manual elastography a practical approach 

8 / 8

GUIDE TO

GRANTS +

POST DOCS FOR

DEVELOPMENT

SOCIOLOGISTS

Compiled by

JEFFREY SWINDLE + KARIN JOHNSON

for the

ASA SECTION ON THE SOCIOLOGY OF DEVELOPMENT

August 2017

PLEASE VISIT OUR WEBPAGE FOR MORE NEWS AND OPPORTUNITIES:

https://sociologyofdevelopment.com 

GRADUATE STUDENT GRANTS + FELLOWSHIPS

AAUW American Fellowship

Due Date: November

Amount: $20,000

AAUW’s American Fellowships program has been in existence since 1888, making it the oldest noninstitutional source of graduate funding for women in the United States. The program provides fellowships for women pursuing full-time study to complete dissertations, conducting postdoctoral research full time, or preparing research for publication for eight consecutive weeks. The purpose of the Dissertation Fellowship is to offset a scholar’s living expenses while she completes her dissertation.

http://www.aauw.org/what-we

do/educational-funding-and-awards/american-fellowships/af-dissertation-application/ 

AAUW International Fellowship

Due Date: November

Amount: $20,000

AAUW’s International Fellowship program has been in existence since 1917. The program provides support for women pursuing full-time graduate or postdoctoral study in the United States who are not U.S. citizens or permanent residents. A limited number of awards are available for study outside of the United States (excluding the applicant’s home country) to women who are members of Graduate Women International (see the list of GWI affiliates). Preference is given to women who show prior commitment to the advancement of women and girls through civic, community, or professional work.

http://www.aauw.org/what-we-do/educational-funding-and-awards/international-fellowships/if-application/

Andrew W. Mellon Mediterranean Regional Research Fellowship

Due Date: January

Amount: $33,500

The Fellowship supports Mediterranean-focused research in the humanities and related social sciences in countries bordering the Mediterranean. Applicants must propose a three-to nine-month humanities or related social science research project. Applicants must propose travel that is crucial to the proposed project, to one or more Mediterranean country(ies), at least one of which hosts a participating American overseas research center (Note: Scholars are required to affiliate with at least one of the overseas research centers).

http://www.caorc.org/#!faq/cglq info@caorc.org

APS Long-term, Predoctoral Fellowship Applications

Due Date: February

Amount: $ 25,000

The American Philosophical Society Library in Philadelphia seeks applicants for three one-year fellowships to assist in the completion of doctoral dissertation research. Fellows can be affiliated with three possible centers,

depending on their interests. The Center for Native American and Indigenous Research (CNAIR) Fellowship: Applicants’ research must pertain to Native American history, anthropology, linguistics, cultural revitalization,

1

and related fields. Friends of the APS Fellowship in Early American History (to 1840): Applicants’ research must pertain to topics in early American history to 1840. History of Science, Technology, and Medicine Fellowship: Applicants’ research must pertain to topics in the history of science, technology, or medicine.

https://amphilsoc.org/library/fellowships/long-term-pre-docs 

ASA Minority Fellowship Program

Due Date: January

Amount: $18,000

The American Sociological Association (ASA) supports up to 12 minority doctoral sociology students for up to 3 years. The fellowship is intended to fund underrepresented racial/ethnic minority PhD candidates in any sub-area or specialty in the sociology discipline. Fellows will be awarded in order to ensure a diverse and highly trained workforce is available to assume leadership roles in research that is relevant to today’s global society. The fellowship is awarded for 12 months and may be extended for up to 3 years.

asanet.org/funding/mfp.cfm minority.affairs@asanet.org

Association for Slavic, East European, and Eurasian Studies (ASEEES) dissertation research grant

Due Date: April

Amount: $5,000

Thanks to the generosity of donors and members, the Association for Slavic, East European, and Eurasian Studies is sponsoring up to ten grants annually, at a maximum of $5,000 each, for the 

purposes of conducting doctoral dissertation research in Eastern Europe and Eurasia in any aspect of Slavic, East European, and Eurasian studies in any discipline. These awards may be held concurrently with other partial funding sources, but are intended to support students whose projects have not yet been fully supported. The grant is for primary dissertation research, not for dissertation write-up.

https://aseees.submittable.com/submit/72315 beb-b2e6-438a-aad3-4eb267acf4fd/aseees-dissertation-research-grant 

CDDRL (Center on Democracy, Development, and the Rule of Law) Pre-doctoral Fellowships at Stanford University

Due Date: January

Amount: Comparable to doctoral student stipends at Stanford

The Center welcomes applications from pre-doctoral students at the write-up stage in any of the four program areas of democracy, development, evaluating the efficacy of democracy promotion, and rule of law. Pre-doctoral fellows receive stipends comparable to that awarded by the Stanford Graduate Fellowships program; the Center also pays non-matriculated student tuition for pre-doctoral fellows as required by Stanford University. Fellows spend the academic year at Stanford University completing their projects, participating in seminars, and interacting with each other and the resident faculty and research staff. The Center facilities on the Stanford campus include offices and cubicles. Fellows have access to other Stanford libraries as well as exercise facilities.

http://cddrl.fsi.stanford.edu/fellowships/cddrl fellowships 

2

Center for Khmer Studies Ph.D. Dissertation Fellowship Competition for Cambodian and U.S. Schola

This program is open to Cambodian and U.S. doctoral Candidates and scholars who have already earned their Ph.D. in the social sciences and humanities. Scholars can pursue research in other countries in mainland Southeast Asia (Thailand, Laos, Vietnam, Burma, Southern China) provided that part of their research is undertaken in Cambodia.

http://www.khmerstudies.org/fellowships/usa-fellowships 

Chateaubriand Fellowship in Science, Technology, Engineering, Mathematics & Health

Due Date: January

Amount: $12,600

The fellowship aims to initiate or reinforce collaborations, partnerships or joint projects between French and American research teams. The fellowship supports PhD students registered in an American university who wish to conduct part of their doctoral research in a French laboratory.

https://www.france-science.org/-The-Chateaubriand-Fellowship-.html 

stem.coordinator@chateaubriand-fellowship.org

Colombia Biodiversity Scholarships

Due Date: October

Amount: 3m COP (max)

The purpose of Colombia Biodiversa Grants is to Stimulate research on issues related to 

knowledge, conservation and use Colombian sustainable biodiversity through the granting of scholarships for finance partially or fully rsearch projects.

http://www.faae.org.co/colombiabiodiversa/ins trucciones-para-aplicar.html 

colombiabiodiversa@faae.org.co

Dan David Prize Scholarships

Due Date: March

Amount: $15,000

The Dan David Foundation offers 10 scholarships for PhD students and postdoctoral scholars to work on a research project topic that changes each year. The Dan David Prize is a joint international enterprise, endowed by the Dan David Foundation and headquartered at Tel Aviv University. Each application cycle, fields are chosen within the 3 Time Dimensions - Past, Present, and Future - that represent realms of human achievement. Each year the

International Board chooses one field within each time dimension. The Dan David Prize promotes interdisciplinary research designed to innovate and explore.

www.dandavidprize.org

ddprize@post.tau.ac.il

Enders Student Fellowship

Due Date: March

Amount: $3,500

This fellowship is designed to encourage advanced scholarship on Canada-U.S. relations

3

by funding fellowships for US scholars Gilbert Chinard Research Fellowships, Harmon

conducting research at a Canadian university. Chadbourn Rorison Fellowship, Edouard

Morot-Sir Fellowship in French Studies

acsus.org/programs/enders-student-fellowship

Due Date: January

a2holman@bridgew.edu

Franklin Research Grants

Due Date: Fall

Amount: $6,000

Since 1933, the American Philosophical Society has awarded small grants to scholars in order to support the cost of research leading to publication in all areas of knowledge. The Franklin program is particularly designed to help meet the costs of travel to libraries and archives for research purposes; the purchase of microfilm, photocopies, or equivalent research materials; the costs associated with fieldwork; or laboratory research expenses.

https://www.amphilsoc.org/grants/franklin

Fulbright-Hays Doctoral Dissertation Research Abroad (DDRA) Fellowship Program (U.S. Department of Education)

Due Date: March, but most universities require early internal submission

Amount: $15,000-$60,000

For graduate students spending 6- 12 months in full-time dissertation research abroad

(excluding those with a focus on Western Europe) in modern foreign languages and area studies. Special consideration is given to students who study a select list of languages.

https://www2.ed.gov/programs/iegpsddrap/appli cant.html 

Amount: $1,500

Awards for maintenance during research in France will be given. Research may be in French studies in the areas of: art, economics, history, history of science, linguistics, literature and social sciences.

http://institut.unc.edu/application/ institutfrancaisdamerique@gmail.com

Global Religion Doctoral Dissertation Fellowships

Due Date: Fall

Amount: $28,000

These doctoral dissertation fellowships are intended to promote among promising, young North American scholars the social scientific study of contemporary religions around the globe, especially religions in the “global south,” beyond the North Atlantic world (i.e., not the U.S., Canada, and Western Europe). They also intend to help better integrate the study of religion into mainstream social sciences.

http://grri.nd.edu/dissertation 

Harry Frank Guggenheim Foundation dissertation fellowship

Due Date: February

Amount: $20,000

Questions that interest the foundation concern violence and aggression in relation to social

change, intergroup conflict, war, terrorism, crime, and family relationships, among other subjects. Dissertations with no relevance to understanding human violence and aggression will not be supported. Priority will also be given to areas and methodologies not receiving adequate attention and support from other funding sources.

http://www.hfg.org/df/guidelines.htm

Horowitz Foundation for Social Policy

Due Date: December

Amount: $7,500

Aim and Mission: (1) to support emerging scholars through small grants; (2) to promote scholarship with a social policy application; (3) to encourage projects that address contemporary issues in the social sciences.

https://www.horowitz-foundation.org/apply

Inter-American Foundation IAF Grassroots Development Fellowship Program

Due Date: October/November

Amount: ~$25,000

The Fellowship Program complements IAF’s support for grassroots development in Latin America and the Caribbean, and preference is for those applicants whose careers or research projects are related to topics of greatest interest to the IAF. The impact on the quality of life of the poor of grassroots development activities in such areas as sustainable agriculture and natural resource management, housing, health care, education, urban development, technology transfer, jobs creation, and marketing and small-enterprise development. Fellowships are available to currently registered students who will have 

advanced to candidacy for the Ph.D. (or other doctoral program) in the social sciences, physical sciences, technical fields and other disciplines (as related to their relationship with grassroots development issues) by their proposed start date (between June 1 and March 31 of the application year).

https://www.iie.org/Programs/IAF-Grassroots-Development-Fellowship-Program 

Joseph L Fisher Doctoral Dissertation Fellowships

Due Date: February

Amount: $18,000

Resources for the Future (RFF) offers 3 yearlong awards to PhD students researching their dissertation on the environment, natural resources, or energy. RFF is a nonprofit and nonpartisan organization that conducts independent research – rooted primarily in economics and other social sciences – on environmental, energy, natural resource and environmental health issues. Awardees will be invited to present their research at RFF, located in Washington DC.

rff.org/AboutRFF/Pages/JosephLFisherDoctora lDissertationFellowships.aspx 

fisher-award@rff.org

KCC Japan Education Exchange Graduate Fellowships Program

Due Date: April

Amount: $30,000

The purpose of the fellowship is to support future American educators who will teach more effectively about Japan. One fellowship of $30,000 will be awarded.

5

https://www.kccjee.org/graduate-fellowship-program 

Mellon/ACLS Dissertation Completion Fellowships

Due Date: October

Amount: $30,000

This fellowship support a year of research and writing to help advanced graduate students in the humanities and related social sciences in the last year of PhD dissertation writing. The program encourages timely completion of the PhD.

Multi-Country Research Fellowship Program

Due Date: January

Amount: $10,500

Council of American Overseas Research Center (CAORC) offers 8 awards to PhD and postdoc to carry out crossregional research outside the US for at least 3 months. The Council of American Overseas Research Centers (CAORC) Multi-Country Fellowship Program supports advanced regional or trans-regional research in the humanities, social sciences, or allied natural sciences for US doctoral candidates and scholars who have already earned their PhD. Scholars will research in at least 2 countries outside of the United States, and at least one will have an American overseas research center.

caorc.org/fellowships/multi  fellowships+multi@caorc.org

NACBS Dissertation Year Fellowship Due Date: April

Amount: $10,000

The North American Conference on British Studies (NACBS) is awarded to support dissertation research in the British Isles on any topic of British (including Scottish, Irish and Imperial) history or British Studies. The fellowship awardee must conduct full-time research in the British Isles for an extended stay of at least three-months duration. Travel grant awardees may conduct shorter research trips. nacbs.org/prizes/nacbs-dissertation-year-fellowship

abigail.swingen@ttu.edu 

National Endowment for the Humanities Summer Stipend

Due Date: September

Summer Stipends support individuals pursuing advanced research that is of value to humanities scholars, general audiences, or both. Eligible projects usually result in articles, monographs, books, digital materials and publications, archaeological site reports, translations, or editions. Projects must not result solely in the collection of data; instead they must also incorporate analysis and interpretation. Summer Stipends support continuous full-time work on a humanities project for a period of two consecutive months. Summer Stipends support projects at any stage of development.

https://www.neh.gov/grants/research/summer -stipends 

National Scholarship Programme of the Slovak Republic (NSP)

Due Date: April/October

Amount: 580-10,000 €

6

The scholarship is intended to cover international scholarship holders' living costs, i.e. the costs related to staying in Slovakia (food, accommodation, etc.), during their study, research/artistic or teaching stay at universities and inresearch organisations in Slovakia. The scholarship holder can ask for assistance concerning accommodation and formalities related to entering and staying in the territory of the Slovak Republic either his/her host institution, or he/she can handle all the necessities him-/herself.

https://www.scholarships.sk/en/news/call-for-applications-academic-year-2017/2018-apply-now 

nsp-foreign@saia.sk

NSF Doctoral Dissertation Research Improvement Grant

Due Date: October

Amount: $12,000

The DDRI funds doctoral dissertation research to defray direct costs associated with conducting research, for example, dataset acquisition, additional statistical or methodological training, meeting with scholars associated with original datasets, and fieldwork away from the student's home campus.

https://www.nsf.gov/funding/pgmsumm.jsp?p imsid=505118 

P.E.O. Scholar Awards

Amount: $15,000

P.E.O. Scholar Awards are one-time, competitive, merit-based awards for women of the United States and Canada who are pursuing a doctoral level degree at an accredited college or university in the United States or Canada. In 

addition to recognizing and encouraging excellence in higher education, these awards provide partial support for study and research for women who will make significant contributions in their varied fields of endeavor. Priority is given to women who are well established in their programs, study or research.

https://www.peointernational.org/about-peo-scholar-awards-psa 

Phillips Fund for North Native American Research Grants

Due Date: March

Amount: $3,500

The American Philosophy Society (APS) provides up to 17 grants for one year, funding research in Native American studies. The Phillips Fund of the American Philosophical Society provides grants for research in Native American linguistics, ethnohistory, and the history of studies of Native Americans, in the continental United States and Canada. Grants are not made for projects in archaeology, ethnography, psycholinguistics, or for the preparation of pedagogical materials.

amphilsoc.org/grants/phillips LMusumeci@amphilsoc.org

Robert S. McNamara Fellowships Program

Due Date: February

Amount: $25,000

Robert S. McNamara Fellowships Program (RSMFP) provides support to developing country nationals who are PhD candidates from developing countries and working in academic and research institutions in a developing

7

country who seek 6-10 months of funding to conduct PhD research in a World Bank member country other than their home country or country of residence. RSMFP was established in 1982 with $2.8 million in funding from the World Bank and the governments of Bangladesh, China, India, Kuwait, Nigeria, Pakistan, Peru, and former Yugoslavia.

http://www.worldbank.org/en/events/2016/09 /15/robert-s-mcnamara-rsm-fellowships-program-seeking-scholarship-applicants-for-phd-research-on-development 

Social Science Research Council Mellon International Dissertation Research Fellowship

Due Date: November

Amount: $21,000

Provides nine to twelve months of support to graduate students in the humanities and humanistic social sciences who are enrolled in PhD programs in the United States and conducting dissertation research on non-US topics. Applicants must request nine to twelve months of on-site, site-specific dissertation research with a minimum of six months of research outside of the United States.

https://www.ssrc.org/fellowships/view/idrf-fellowship/ 

Suomen Kulttuurirahasto / Finnish Cultural Foundation

Due Date: October

Amount: $24,000

Grants are awarded for all fields of cultural activity. The work can be undertaken in Finland or abroad. In the arts, support is given for work and various projects, and also limited support for studies. Science grants are awarded for 

doctoral studies and postgraduate scientific work.

http://www.skr.fi/en/grants/grants-available-application/central-fund-application-period-1-31-october 

apurahainfo@skr.fi

Taiwan Foundation for Democracy dissertation fellowship

Amount: NT$40,000 monthly

The Taiwan Foundation for Democracy seeks to promote an understanding of Taiwan’s democracy and human rights development among the future generation of scholars and practitioners. To this end, Dissertation Fellows may reside in Taiwan for up to one year to carry out in-depth, relevant research. Applicants are encouraged to form relationships with organizations and institutions dealing with democracy and human rights issues based in Taiwan. The TFD hopes that through an active exchange of ideas and expertise, Dissertation Fellows may share their experience with Taiwanese academics, practitioners, NGOs, and think tanks to further encourage democracy and human rights in Taiwan and internationally.

http://www.tfd.org.tw/opencms/english/fellow ships/dissertation/ 

The Charlotte W. Newcombe Doctoral Dissertation Fellowship

Due Date: November

Amount: $25,000

8

The Charlotte W. Newcombe Doctoral Dissertation Fellowships are designed to encourage original and significant study of ethical or religious values in all fields of the humanities and social sciences, and particularly to help Ph.D. candidates in these fields complete their dissertation work in a timely manner. In addition to topics in religious studies or in ethics (philosophical or religious), dissertations appropriate to the Newcombe Fellowship competition might explore the ethical implications of foreign policy, the values influencing political decisions, the moral codes of other cultures, and religious or ethical issues reflected in history or literature.

http://woodrow.org/fellowships/newcombe/

The Woodrow Wilson Dissertation Fellowship in Women’s Studies

Due Date: October

Amount: $25,000

The Woodrow Wilson Dissertation Fellowship in Women’s Studies encourages original and significant research about women that crosses disciplinary, regional, or cultural boundaries. Previous Fellows have explored such topics as transnational religious education for Muslim women, the complex gender dynamics of transidentity management, women’s electoral success across racial and institutional contexts, women’s sports, militarism and the education of American women, and the relationship between family commitments and women’s work mobility.

http://woodrow.org/fellowships/womens-studies/ 

Trajectories of Change Ph.D. ResearchFellowship at ZEIT-Stiftung

Due Date: Winter

The programme offers stipends and fieldwork grants for Ph.D. students in the humanities and social sciences studying political and social change in Eastern Europe, North Africa and the Middle East as well as Central Asia. The first application is for 2 years of living stipend support. If received, then one is eligible to apply for further research funding.

https://www.zeit

stiftung.de/en/projects/researchandscholar  ship/humanitiesandsocialsciences/trajectori esofchange 

U.S. Student Fulbright

Due Date: September/October

Amount: ~$25000

“Academic” research/study grant. It offers 9-12 months of support to recent BS/BA graduates (graduating seniors) and graduate students and young professionals to conduct study and/or research in one country. Awards provide round-trip transportation, language or orientation courses in certain cases, maintenance allowance, and supplemental health and accidental insurance. Applicants must be U.S. citizens.

http://us.fulbrightonline.org/application-components/academic 

XminusY (XminY)

Due Date: June

Amount: $3,000 max

XminusY supports social movements, actiongroups and changemakers who are fighting for a fair, democratic, sustainable and tolerant world. Projects that are supported by XminusY can take place on a broad variety of topics. But more important then the topic, is that the people involved take action themselves to change their own society. Actions supported by XminusY are demonstrations, occupations, direct-action and other creative forms to change the world.

https://www.xminy.nl/english/ info@xminy.nl

POSTDOCTORAL RESEARCH GRANTS

Harry Frank Guggenheim Foundation research grant

Due Date: August

Amount: $40,000

Questions that interest the foundation concern violence and aggression in relation to social change, intergroup conflict, war, terrorism, crime, and family relationships, among other subjects. Dissertations with no relevance to understanding human violence and aggression will not be supported. Priority will also be given to areas and methodologies not receiving adequate attention and support from other funding sources.

http://www.hfg.org/rg/guidelines.htm 

Dan David Prize Scholarships

Due Date: March

Amount: $15,000

The Dan David Foundation offers 10 scholarships for PhD students and postdoctoral scholars to work on a research project topic that changes each year. The Dan David Prize is a joint international enterprise, endowed by the Dan David Foundation and headquartered at Tel Aviv University. Each application cycle, fields are chosen within the 3 Time Dimensions - Past, Present, and Future - that represent realms of human achievement. Each year the

International Board chooses one field within each time dimension. The Dan David Prize promotes interdisciplinary research designed to innovate and explore.

www.dandavidprize.org

ddprize@post.tau.ac.il

ITS Post-Doctoral Summer Travel Grants

Due Date: March

Amount: Airfare to Turkey

The Institute of Turkish Studies (ITS) offers at least 4 weeks of summer research and travel to Turkey for up to 9 postdoctoral scholars. Founded and incorporated in Washington DC in 1982, the ITS is the only non-profit, private educational foundation in the US exclusively dedicated to the support and development of Turkish Studies in American higher education. These grants offers support for research projects in the field of Ottoman and Modern Turkish Studies. The grant must be utilized during the academic year in which it is awarded.

turkishstudies.org/grants/grantscompetition.s html 

itsdirector@turkishstudies.org

American Druze Foundation (ADF) Post-Doctoral Fellowship

Due Date: March

Amount: $50,000

Georgetown University Center for

Contemporary Arab Studies offers one one-year fellowships to post-doctoral scholars

conducting research on Druze communities. The purpose of the ADF Fellowship is to promote specialized social scientific research on the Druze communities centrally and primarily, and on collective political and cultural identities in the Arab world more generally. During the academic year, the Fellow must continue to conduct research on the Druze or other intentional political and cultural communities in the Arab world, in order to transform the 

doctoral dissertation into a book manuscript for publication. The Fellow is encouraged to deliver a public lecture on a relevant topic to be determined with the Director of the CCAS, and must design and teach for CCAS one graduate seminar on the Druze and the broader topics of socio-cultural pluralism, identity politics, and subnational communities in the Arab world. Finally, the Fellow must be in residence at the CCAS for the duration of the academic year.

academicjobsonline.org/ajo/jobs/8676 bnk12@georgetown.edu

Russell Sage Foundation: Investigator-initiated Research Project Awards - Regular Programs: Social Inequality / Future of Work / Race, Ethnicity & Immigration / Behavioral Economics (Project and Presidential Awards)

Due Date: May

Amount: $150,000

The Foundation makes external awards, known as Project Awards and Presidential Awards, for research projects that address questions of interest under the Foundation's programs and special initiatives. The Regular Programs are Behavioral Economics; the Future of Work; Race, Ethnicity, and Immigration; and Social Inequality. The Foundation occasionally pursues time-limited special initiatives on certain topics of emerging interest. The special initiatives are consistent with RSF's interests in strengthening the methods, data, and theoretical core of the social sciences as a means of diagnosing social problems and improving social policies, and are intended to generate new research with an emphasis on any of the foundation's core programs.

http://www.russellsage.org/how-to-apply programs@rsage.org

11

Center for Khmer Studies Ph.D. Dissertation Fellowship Competition for Cambodian and U.S. Scholars

Due Date: November

This program is open to Cambodian and U.S. doctoral candidates and scholars who have already earned their Ph.D. in the social sciences and humanities. Scholars can pursue research in other countries in mainland Southeast Asia (Thailand, Laos, Vietnam, Burma, Southern China) provided that part of their research is undertaken in Cambodia.

http://www.khmerstudies.org/fellowships/usa-fellowships 

POSTDOCTORAL FELLOWSHIPS

Postdoctoral Research Scholar, Institute for Research on Women, Gender, and Sexuality

Columbia University

Due Date: April

Annual Salary: $60,000

We seek an innovative scholar whose work focuses on gender and sexuality, is informed by feminist and queer theory, and is rigorously interdisciplinary in its approach to the world. We are particularly keen to consider transnational research in such fields as critical development studies, law and social justice, environmental studies, migration, indigeneity, human rights, science and technology studies, visual cultures, and performance studies. Scholars in the social sciences, as well as those trained in interdisciplinary fields, whose work focuses on peoples, institutions, discourses, and practices outside North America and Europe are especially encouraged to apply.

http://irwgs.columbia.edu/blog/irwgs-hiring-postdoctoral-research-scholar 

Lieberthal-Rogel Center for Chinese Studies (LRCCS) Postdoctoral Fellowship

University of Michigan

Due Date: February

Annual Salary: $47,276

Research Funds: $10,000

Research topics can cover any historical period of China - including contemporary China - and involve any academic discipline in the humanities and social sciences.

https://ii.umich.edu/lrccs/postdoctoral-fellows.html 

Emerging Democracies Postdoctoral Fellowship at the Weiser Center for Emerging Democracies (WCED)

University of Michigan

Due Date: January

Annual Salary: $50,000

Research Funds: $2,000

The fellowship supports research on the broad historical, political, economic, and societal conditions under which democracies emerge— and autocracies endure.

https://www.ii.umich.edu/wced/postdoctoral-fellows.html 

Center for the Study of Women, Gender, and Sexuality Postdoctoral Fellowship

Rice University

Annual Salary: $50,000

Research funds: $3,000

The Center for the Study of Women, Gender, and Sexuality announces two postdoctoral fellowships in the humanities or social sciences for scholars pursuing research and publication projects that focus on gender and health; gender and urban studies; women in the global economy; sex, race, and nation; or sexuality studies. The Center is particularly interested in applicants who demonstrate a record of innovative teaching and the potential to make a solid contribution to the Center’s program in engaged feminist research.

http://swg.rice.edu/fellowships/

International Institute of Islamic Thought (IIIT)

Post-Doctoral Fellowship

IIIT offices in Herndon, VA

Due Date: February

Salary: $4000 monthly for 6 months

IIIT Post-Doctoral Fellowship is ideal for a recent PhD graduate working on converting their dissertation into a book. Other projects may also be considered. Priority will be given to applicants who are willing to publish the book with IIIT.

http://www.iiit.org/iiit-post-doc-fellowship.html

Voss Postdoctoral Research Associate in Environment & Society

Brown University

Due Date: Fall

Annual Salary: $50,000

Research Funds: $5,000

The Institute at Brown for Environment and Society (IBES) seeks candidates for one or more distinguished postdoctoral positions in interdisciplinary environmental science. IBES was founded in 2014, building on strength across campus in interdisciplinary environmental research. Requirements for the positions include a Ph.D. in a field relevant to the study of environment and society, the intellectual flexibility to reach across fields, ability to take initiative and work independently, and demonstrated interest in interdisciplinary environmental research.

https://www.brown.edu/academics/institute-environment-society/funding

13

opportunities/postdoctoral-research-associate

environment-society

Watson Postdoctoral Fellows Program

Brown University

Due Date: Fall

Annual Salary: $55,000

Research Funds: $2,500

The Watson Institute for International and Public Affairs at Brown University aspires to promote a just and peaceful world through research, teaching, and public engagement. Central to this mission is the Watson Postdoctoral Fellows Program, an effort to galvanize the careers of young social scientists conducting research related to the Institute’s three core thematic areas: development, governance, and security. Participants in this program will join an interdisciplinary community of scholars engaged in theoretically and substantively important research addressing the most pressing global issues of our time.

http://watson.brown.edu/education/postdoc

Einaudi Center Postdoctoral Fellowships Cornell University

The Einaudi Center awards postdoctoral fellowships in the areas of foreign policy, security, and diplomacy. We attract outstanding scholars whose work demonstrates excellence in the social sciences or humanities and addresses questions of lasting importance.

https://einaudi.cornell.edu/postdoctoral-fellowships 

Atkinson Postdoctoral Fellowships in Sustainability

Cornell University

Annual Salary: $60,000

Research Funds: $15,000

The David R. Atkinson Center for a Sustainable Future empowers faculty to think outside of their departments and across disciplines when it comes to tackling the world's greatest challenge—creating a vital and resilient future for the global community. Atkinson

Postdoctoral Fellowships are intended to strengthen and expand the center’s work with external partners, by:

Stimulating original cross-disciplinary research and development of sustainable solutions that address the world’s most pressing sustainability challenges;

Developing and deepening connections with external parties in order to speed the creation and implementation of viable sustainability solutions;

Developing a cohort of postdoctoral fellows on campus working in

sustainability and related fields;

Building a core group of leaders capable of creating effective, workable solutions to the most serious sustainability questions.

http://www.atkinson.cornell.edu/grants/postdoc/

African Studies Postdoctoral Fellowship Program

Harvard University

Our postdoctoral program invites two African scholars whose Africa-related research corresponds to Harvard’s graduate and professional school programs to work in

14

residence at Harvard University in Cambridge and in Johannesburg for a period of two years. During this period, postdocs teach an Africa-related course within the Department of African and African American Studies or another department at Harvard. They are empowered to pursue their own research, utilizing the breadth of faculty resources and support at Harvard.

https://africa.harvard.edu/african-studies-postdoctoral-fellowship-program 

Visiting Fellowship at the Kellogg Institute for International Studies

University of Notre Dame

Due Date: Fall

This widely respected residential program offers you time to pursue scholarly inquiry where it takes you, advance your personal research, and collaborate with other scholars and practitioners from across the US and around the globe. As a visiting fellow, you pursue research related to Kellogg Institute themes of democracy and human development, share your research with the Notre Dame scholarly community, and have the opportunity to publish in Kellogg’s peer-reviewed Working Paper Series.

http://kellogg.nd.edu/vfellowships/fellowships. shtml 

CDDRL (Center on Democracy, Development, and the Rule of Law) Postdoctoral Fellowships

Stanford University

Due Date: January

The Center welcomes applications from postdoctoral scholars working in any of the four program areas of democracy, development, evaluating the efficacy of democracy promotion, 

and rule of law. Post-doctoral fellows receive salaries commensurate with experience and with consideration given to university established minimums for a term period of 9 months. Fellows spend the academic year at Stanford University completing their projects, participating in seminars, and interacting with each other and the resident faculty and research staff. The Center facilities on the Stanford campus include offices and cubicles. Fellows have access to other Stanford libraries as well as exercise facilities.

http://cddrl.fsi.stanford.edu/fellowships/cddrl  fellowships 

Agragrian Studies Program Fellowships

Yale Program in Agrarian Studies

Due Date: January

The Program in Agrarian Studies at Yale fosters the interdisciplinary study of agrarian societies, historically and across the world. We aim to be the crossroads for the best work in the humanities, the social sciences, environmental studies, and related professional fields that breathes new life into the study of farmers, agriculture, and rural society and captures the texture of lived experience as well contributing to theoretical and conceptual advances. The Agrarian Studies Program appoints three fellows annually, chosen for the promise of their research; they are in residence for the year, present a paper, and attend the weekly colloquium. Emerging as well as established scholars are encouraged to apply. We also receive applications from knowledgeable “activists” and “public intellectuals” whose work on rural life transcends the academy. Fellows are expected to be in residence in New Haven to take an active part in the intellectual exchange with other members of the Program.

http://agrarianstudies.macmillan.yale.edu/fello wships 

15

Postdoctoral Fellowships at the Käte Hamburger Kolleg Centre for Global Cooperation Research

University of Duisburg-Essen, Germany Due Date: Fall

The Käte Hamburger Kolleg / Centre for Global Cooperation Research seeks to contribute towards a better understanding of the possibilities and limits of transboundary cooperation. By building a learning community, researchers from different disciplines and world regions develop an innovative framework for contemporary cooperation research that enables the exploration of new options for global public policy. We aim to become a crucial hub for this emerging branch of research. We aim to understand the role of transboundary cooperation as an essential part of public policy addressing global challenges. Käte Hamburger Kolleg / Centre for Global Cooperation Research is an interdisciplinary research institute of the University of Duisburg-Essen. The Centre is the tenth and the last Käte Hamburger Kolleg supported by the Federal Ministry of Education and Research of Germany.

https://www.gcr21.org/en/fellows/how-to-become-a-fellow/fellowships/

University Planning and Analysis

Reference Guide for Using Qualtrics

Using information gathered from the Qualtrics website as well as conversations with Qualtrics support, UPA has created this handout for tips on some common areas users tend to have questions about when getting started with Qualtrics. This reference guide is not intended to be a complete guide to Qualtrics, but should be used a supplement with Qualtrics University training resources. For a complete collection of training resources, visit Qualtrics University at http://www.qualtrics.com/university/researchsuite/

Edit Survey Tips

Question Types

* To add text in your survey, such as at the beginning of a survey or block of questions, choose the question type Text/Graphic, which will create text but no answer choices.

* For Matrix questions that have many statements, consider using the repeat headers feature. This will enable users to continue to see the scale points as they scroll down to answer each statement. In the light blue area to the right, under Options check ‘Repeat Headers’.

* For Text Entry question types, the difference between Single Line, Multi Line, and Essay Text Box is for visual purposes only. There is no character limit, but you can set one if you need to.

Printing and Viewing Survey

* To view your survey as others will see it, click ‘Preview Survey’. Alternatively, click ‘Print Survey’ and print it to a PDF.

* To view your survey with your coding and/or formatting included, go to Edit Survey -> Advanced Options -> Export Survey to Word.

Question Numbering

* To re-number your survey questions in order, go to Edit Survey -> Advanced Options -> Auto-Number Questions.

* To display question numbers in your survey, go to Edit Survey -> Survey Options and check ‘Show Export Tags’.

Page Breaks

* Unless you add a Page Break, pages will automatically break at the end of blocks.

* To add a Page Break, in Edit Survey, click in the question you want the page break to appear after and to the right of the page in the light blue area, click ‘Add Page Break’.

Using Code to Customize Survey

* If you need to customize your survey in a way that you don’t see a point-and-click option, you can use HTML, JavaScript, and CSS code to get your desired results. To learn how to place custom coding into your Qualtrics survey go to http://www.qualtrics.com/university/researchsuite/developer-tools/custom-programming/example-code-snippets/ 

NC State University Planning and Analysis

http://upa.ncsu.edu/srvy/qltrx/support

December 2013

Page 1 of 7

Adding a Progress Bar and Back Button

* To add a Progress Bar go to Edit Survey -> Look and Feel -> General and choose from the drop-down list which type of Progress Bar you want to display.

* To add a Back Button, go to Edit Survey -> Survey Options -> Back Button. The Back button will allow respondents to move backwards within the current block. It allows going back across blocks, unless there is an element between the two blocks in the Survey Flow (like a branch, randomizer, or other similar non-question-block element).

Saving Edits

* Qualtrics automatically saves edits as you work, but you can manually save work by typing CTRL + S.

Distribution Methods

There are two URL options for distributing a survey in Qualtrics: Email Survey and Survey Link.

Email Survey (Qualtrics Mailer)

The distribution method that offers the most features and flexibility is the Qualtrics Mailer. To use Qualtrics Mailer you create and upload a ‘Panel’ in .csv format that includes email addresses for all the recipients as well as any other data you want associated with each person (e.g., name, address, etc.). You then use the Qualtrics Mailer to send emails to your panel. In these emails, each recipient will get a unique link to access the survey. Using the Qualtrics Mailer, you can control access to the survey, track respondents, associate respondents with panel data, customize invitations, track mailing history, and send reminder/thank you emails.

Survey Link (Open-Access)

The alternative option of distribution is to use the Survey Link. When you activate your survey, Qualtrics generates a survey URL. The survey link can be copied and pasted into emails, letters, websites, and so on. Everyone uses the same link to access the survey. Qualtrics uses this same survey link if you use the other distribution options: Social Media, In-Page Popup, Website Feedback, and Survey Director. With Social Media, you can post the Qualtrics link on various sites such as Twitter, Facebook, LinkedIn, etc. In-Page Popup creates a popup on your website. (Note: It is not technically a pop-up but rather a part of the website, and will not get blocked by popup blockers.). Website Feedback is an icon that is placed on the website that directs people to your survey. Survey Director is a tool you can customize to direct people to your survey or your reports. The Survey Link can be used with or without an authenticator depending on the level of features you want.

Using the Survey Link without an Authenticator

The survey link without an authenticator can be an easy and basic way to distribute an open-access survey. This is the preferred method if you do not have a defined population or email addresses. You will not be able to track respondents or control access, but can easily copy the link to handouts or flyers for wider distribution.

Using the Survey Link with an Authenticator

If you do not want to generate unique links (e.g., because you do not have email addresses for your population), but still want to control access to your survey, you can use the Survey Link with an Authenticator. You will need to assign respondents a password that they will use to access your survey. When you add an Authenticator element in your Survey Flow, you will reference a panel that you have created. Every panel requires an Email field so when you don’t have email addresses, you can create a column with dummy emails. Next, you will add a field with ID’s and/or passwords for each respondent.

NC State University Planning and Analysis

http://upa.ncsu.edu/srvy/qltrx/support

December 2013

Page 2 of 7

Then, when a respondent clicks your survey link, they will be asked to login and verify their identity before gaining access to the survey.

To learn about using panels click here:

http://www.qualtrics.com/university/researchsuite/distributing/panels/

To learn about adding an Authenticator click here:

http://www.qualtrics.com/university/researchsuite/advanced-building/survey-flow/authenticator/

Using Survey Flow

Introduction

Survey Flow is an important feature of Qualtrics that everyone creating a survey should learn to use. To get started go to Edit Survey -> Survey Flow. In the Survey Flow screen, you will see your survey separated into blocks. If you have not added any additional blocks to your survey, Survey Flow will only have your default first block. A block is simply a group of questions in your survey. Within Survey Flow, if you click ‘Add a New Element Here’, you will see nine choices: Block, Branch, Embedded Data, Randomizer, Web Service, Authenticator, End of Survey, Table of Contents, and Conjoint. The following paragraphs will briefly describe each of these elements of Survey Flow and how they are commonly used. Remember that the elements described below refer to entire blocks of your survey. There are similar options that can be used for individual questions and these are found outside of Survey Flow in the Edit Survey screen. Also, keep in mind that every survey is unique and people are always finding new ways to use Survey Flow. Therefore this guide doesn’t include every possible method for using the Survey Flow. For tutorials on Survey Flow, go to the following link: http://www.qualtrics.com/university/researchsuite/advanced-building/survey-flow/

Block

The Block element in Survey Flow is used when you want to repeat an existing block somewhere in your Survey Flow. If your respondents are filtered through your survey and you want some of them to answer the same block, add a new block element. Be sure to only repeat a block in mutually exclusive branches so that respondents don’t get the same questions twice. On the other hand, if you do want respondents to get the same block twice in one survey (e.g., so they can review or make changes to previous answers) keep in mind that only the most recent answers will be saved to the results section.

Branch

The Branch element allows you to route respondents to different blocks using conditional logic. The Branch element is similar to Skip/Display logic, only Skip/Display is used for individual questions whereas the Branch element is used for blocks. In the Branch element you choose from a drop down list whether you want to branch based on a ‘Question’, ‘Embedded Data’, ‘Device Type’, ‘Quota’, or ‘GeoIP Location’.

Embedded Data

Embedded Data is any extra information you would like recorded in addition to the question responses. For example, if you have extra fields in your panel (in addition to email and name), the embedded data element can be added so that these fields are appended to your survey results. The value for your Embedded Data field can be pulled from data that you have uploaded into a Panel, information appended to the participant’s survey link, or, it can be a fixed value set in the Survey Flow. Embedded data can be used in several ways within Qualtrics such as for advanced logic, piped text, criteria for creating sample panels, or for filtering data in the ‘Results’ tab.

NC State University Planning and Analysis

http://upa.ncsu.edu/srvy/qltrx/support

December 2013

Page 3 of 7

Randomizer

The Randomizer element allows you to randomly present different blocks or elements within your survey to respondents. You can move the blocks beneath the Randomizer element and choose to either present all of the elements in random order or randomly present a subset of the blocks. If you choose to present a subset, you may want to check the ‘Evenly Present Elements’ box to make sure that each block is seen approximately the same number of times. The Randomizer element is useful for experimental design surveys where you want to randomly assign respondents to experiments or a control group. Keep in mind, that there is also a randomization option outside of Survey Flow in Edit Survey that can be used for individual questions.

Web Service

The Web Service element allows you to pull information from an external websites’ RSS feed and use it as embedded data. RSS (Really Simple Syndication) is a website with frequently changing or updated content. After creating the Web Service element, you can then pipe this embedded data into your survey questions or answer choices. For example, you can copy the RSS feed link for iTunes Top Ten Songs into your Survey Flow. You can then create a question in your survey (e.g., Rank these 10 songs from most favorite to least favorite) and pipe the song names into the answer choices.

Authenticator

The Authenticator element is used to verify respondents’ information by prompting them to ‘log in’ before getting access to the survey. Authenticator is useful for when you don’t have email addresses or want to use the single Survey Link but still want to control access to the survey. You will need to provide respondents with a login id that you create. You can change the options for the Authenticator, such as the number of allowed log in attempts, the error message displayed, and the ability to save and continue. You have the option to authenticate only certain blocks of the survey or the entire survey. If you authenticate the entire survey (require log in to access the survey), be sure to move the Authenticator element to the top of the Survey Flow and move all other blocks underneath and within the Authenticator. For the authenticator to work correctly, all authenticated blocks should be indented to the right underneath Authenticator element. Otherwise, even if a respondent fails authentication, they will still be able to click next to the rest of the survey.

End of Survey

The End of Survey element skips respondents to the end of the survey early. The End of Survey element is often used with other survey flow elements. For example, suppose you want 100 students from each class to complete your survey and you already have responses from 100 sophomores. Once the quote is met, you can skip all sophomore respondents to the end of the survey. In the End of Survey element, click ‘Customize’ for additional options.

Table of Contents

The Table of Contents element allows you to create a list of sections of your survey. The Table of Contents can be placed at the beginning of your survey so that respondents can select which block they want to respond and go directly to that section of the survey.

Conjoint

Conjoint Analysis is a technique used to assess the relative importance individuals place on different features of a given product. A conjoint study usually involves showing respondents a set of features and asking them to indicate how much they like or prefer the different attributes of that feature. Use Survey Flow to add the conjoint element to the correct position in your survey.

NC State University Planning and Analysis

http://upa.ncsu.edu/srvy/qltrx/support

December 2013

Page 4 of 7

Handling Partially Completed Surveys

Often a respondent may respond to part of a survey and exit in the middle of it, with or without the intention of returning at a later time to complete it. Alternatively, sometimes when a respondent receives a request to take a survey, they may open the survey and preview it before coming back at a later time to finish it. There are a couple of things to keep in mind about handling partially completed surveys in Qualtrics.

Things to Know...

* It's a good idea to let the respondents know ahead of time (e.g., in an email or introduction) how long the survey is expected to take to complete. Also, consider adding a Progress Bar to your survey. Keep in mind though that the progress bar can be misleading if you have skips and branching elements in your survey.

* If you distribute your survey with the Qualtrics Mailer, as long as a respondent doesn't click the final arrow at the end of the survey, they can exit the survey and at any time before the expiration date, return to the page where they left off on. Respondents are allowed to return regardless of whether the Save and Continue options is clicked in Options. On the other hand, if you distribute the survey using the Survey Link, you will need to go to Survey Options and check the Save and Continue box to allow users to return to the survey where they left off. This will put a cookie on their browser so that computer will remember where they left off. Keep in mind that when using the Survey Link, if the respondent uses a different browser or device to access the survey, they will have to start from the beginning.

* When a respondent answers some but not all of a survey, Qualtrics stores them temporarily in a ‘partially completed’ holding area. If they return and complete the survey, their response will be recorded as complete. When using the Qualtrics Mailer, if someone answers part of a survey but doesn't return after some set time (by default, one week), their link will expire and their partial responses will be recorded as complete. Also, when you officially close the survey, all partially completed responses are recorded as complete.

Adding a ‘Submit’ button

There is no point-and-click method for adding a ‘Submit’ button to the end of your survey. By default, the final button is just a forward arrow. So unless you add text stating that this is the end of the survey, the respondent will just click the last forward arrow and then see that they have completed the survey. This could create a problem if they wanted to go back and change and answer or were simply previewing the survey before planning to return at a later time to complete it. Depending on your Survey Options settings, they may not be able to return and retake the survey. We suggest you add a final question at the end of the survey to remind respondents that the survey is complete (e.g., ‘Click next to submit your answers’). To change the next arrow to a ‘Submit’ button, visit http://www.qualtrics.com/university/researchsuite/developer-tools/custom-programming/example-code-snippets/. Scroll down the page to Custom ‘Submit’ Button.

For more information on partially completed surveys go to

http://www.qualtrics.com/university/researchsuite/basic-building/basic-survey-options/partial-completion/

NC State University Planning and Analysis

http://upa.ncsu.edu/srvy/qltrx/support

December 2013

Page 5 of 7

Troubleshooting Survey Access Problems

The following are possible messages that recipients may see when trying to access your survey. If a respondent gets one of these messages and has not completed your survey, follow these solutions to troubleshoot the problem.

Message: Thank you for taking the survey. Your response has been recorded.

Solution:

* This message is displayed when the survey link has already been used. To send respondents a new survey link, go to View Results-> Respondents. Under Actions, click the drop box and select ‘Retake Survey’ or ‘Retake Survey as New Response’. A survey link will be generated that can be used to retake the survey.

Message: Page cannot be displayed.

Solution:

* Some email accounts are set up to automatically disable links. When users click on the link, they may see a message such as ‘page cannot be displayed.’ If this is the case, manually copying and pasting the survey URL into the address bar will give them access.

* In rare situations, the user's firewall could be blocking the Qualtrics website. If this is the case, the quickest solution would be to try taking the survey from a different location.

Message: Your survey session has expired and your response if any has been recorded. Solution:

* It’s possible the respondent clicked your survey link when you first sent it out and then returned after a week to finish it, but their session was closed out due to inactivity. Once someone clicks the survey link, by default the survey session expires after one week of inactivity. If this occurs, you can send the respondent a new link by going to View Results-> Respondents. Under Actions, click the drop box and select ‘Retake Survey’ or ‘Retake Survey as New Response’. Also, in Edit Survey -> Survey Options you can change the default expiration for survey links so that respondents have more time to return to complete a survey.

* It’s also possible that the survey link expired even if the respondent never clicked on it. Using the Qualtrics Mailer, by default respondents have 60 days to click the survey link before it expires. In Advanced Options, you can change this but can only go as high as 90 days. If a respondent wants to complete the survey after 90 days, you will need to send them a new link.

* Finally, it's possible that the survey itself expired. Check your Survey Options in the Edit Survey tab. Next to Survey Protection, the default setting is 'This survey does not expire.' If you changed the default setting make sure your survey is still valid.

Message: This survey has expired.

Solution:

* This message means that the survey itself has expired. Check your Survey Options in the Edit Survey tab. Next to Survey Protection, the default setting is 'This survey does not expire.' If you changed the default setting make sure that the end date has not passed.

Message: Thank you for your time, unfortunately this survey has been closed.

Solution:

* Check to make sure there is still a green check next to your survey in the My Surveys tab in Qualtrics. You may have accidentally closed the survey.

NC State University Planning and Analysis

http://upa.ncsu.edu/srvy/qltrx/support

December 2013

Page 6 of 7

For further support in using Qualtrics, visit Qualtrics University at

http://www.qualtrics.com/university/researchsuite/. If you cannot find a solution at Qualtrics University, email Qualtrics at support@qualtrics.com or call 1-800-340-9194.

Last Updated: December 2013

NC State University Planning and Analysis

http://upa.ncsu.edu/srvy/qltrx/support

December 2013

Page 7 of 7

Table of Contents

Introduction 1

Exploring Your Interest in Law 2

Preparing for Law School 4

Determining Where to Apply 5

Understanding Admissions Criteria 8

Applying to Law School 9

Law School Admission Test (LSAT) 9

Law School Data Assembly Service (LSDAS) 10

The Application 11

Personal Statements 12

Letters of Recommendation 12

Filing Your Applications 14

Taking Time Off 15

Considering Admissions Decisions 16

Financing Law School 18

Legal Career Checklist 22

Legal Career Resources 23

© 2008 NAPLA Inc. Permission to use this content is granted to nonprofit educational institutions. All other rights reserved.

Introduction

NAPLA has prepared the Pre-Law Guide for those considering the legal profession, for undergraduates preparing for legal study, and for candidates applying to law school. The Guide is designed to help at each stage by providing accurate and up-to-date information.

Pre-law advisors at nonprofit educational institutions are granted permission by NAPLA to use the Guide and are encouraged to tailor it to their respective schools. The Guide can be printed and distributed to students and alumni, and used on schools' websites. NAPLA requests that the attribution below be included in both print and online versions of the Guide.

The NAPLA Pre-Law Guide is based on Cornell University's Legal Careers Guide, which was used by permission of Cornell Career Services. NAPLA would like to acknowledge the following schools for their contributions to the Guide: Binghamton University, Boston College, Boston University, Bucknell University, Columbia University, Duke University, Northeastern University, Princeton University, and Texas A & M University. The Law School Admission Council provided information on study abroad transcripts, and the Financial Aid section is based on the "Financial Aid Toolkit" developed by the Pre-Law Advisors National Council (PLANC).

NAPLA Pre?Law Guide

Exploring Your Interest in Law

A J.D., Juris Doctor, can lead to a wide range of law-related careers and can open doors to careers in government, business, higher education, communications, and numerous other fields. Law school graduates are administrators, teachers, librarians, and business managers as well as advocates, judges, and politicians.

The law can be a rewarding profession. At its best, legal practice challenges the intellect, demanding the exercise of reason and judgment. The ethics of the profession require attorneys to promote justice, fairness, and morality; thus, legal employment can bring particular satisfaction to those who seek to work, within the law, to seek social injustice.

There are significant differences in career choices lawyers make, from public interest law and government law to private practice in a firm. The range in starting salaries alone can exceed $100,000. And, the need to pay back law school loans can affect the career choices of a new graduate.

Before beginning the application process, consider carefully if a law degree is right for you. It is not necessary to know what kind of law you want to practice or even if you want to practice law to decide to attend law school. There are a number of ways you can explore the field of law:

* Talk with a career counselor and/or a pre-law advisor about your interest in pursuing legal studies. If you are uncertain who the pre-law advisor at your school is, the Law School Admission Council will inform you when you register for the Law School Data Assembly Services (LSDAS).

* Conduct research on legal careers using resources at your pre-law advising office or college career office.

* Investigate online resources, including the American Bar Association, the National  Association of Law Placement, and Internet Legal Research Group.

* Intern with a law firm or law-related organization to gain exposure to the field and to experience the work environment.

* Conduct information interviews to learn about the legal profession. Talk with lawyers

who are family members, family friends, or alumni of your college to learn:

* what lawyers do in a typical work day

* personal attributes needed to be successful in a legal career

* satisfactions and dissatisfactions of the field

* impact of a legal career on personal lives

Realities of a Legal Career

An important step in making a decision is to distinguish between commonly held expectations and the reality of legal practice. Hours can be very long and often include weekends. Legal work can require spending considerable time in tedious, painstaking research. Depending on the type of law practiced and the location, entry into law firms can be difficult and salaries may not meet expectations. The market for new lawyers is competitive for those seeking positions in

NAPLA Pre?Law Guide

cities and firms that are in high demand.

Employment statistics for the class of 2007 law graduates, based on responses from 40,416 (92% of all graduates) reveal the following1:

* The average starting salary was $86,396; the median salary was $65,750.

* About 11% of salaries reported were at or below $40,000.

* Salaries of more than $75,000 accounted for nearly 43% of salaries reported.

* Approximately 56% of the class chose private practice in law firms.

* About 27% took positions in public service, including judicial clerkships, government agencies, and public interest organizations.

* Graduates entering business accounted for about 14%.

* Approximately 23% of graduates were employed in positions for which bar passage is not required.

While a corporate lawyer in a private firm may earn $135,000 the first year, he/she may also work twelve hours a day, six or seven days a week. Most of those interested in public interest law can expect a starting salary around $40,000.

1NALP The Association for Legal Career Professionals Jobs & J.D.’s: Employment and Salaries of New Law Graduates?Class of 2007.

NAPLA Pre?Law Guide

Preparing for Law School

Admissions committees look at a variety of factors and trends in your academic record in an attempt to predict how you will perform in law school. There is no “pre-law major” and unlike medical school, there are no specific educational requirements for entrance into law school.

Develop research, analysis, and writing skills

Law schools are interested in your ability to do rigorous analytical research, to write well, to present, and to persuade. Take courses that will develop these skills. The American Bar  Association offers an overview of the skills and values important to preparing for a legal education and a career in law.

Law-related classes may allow you to get a feel for law as a general subject, but they neither cover the material in the same depth nor embody the intensity and rigor of law school. Therefore, they are not especially accurate indicators of your ability to succeed in the study of law or whether you will enjoy it.

Select a Major

Choose a major that interests you. Admissions offices are not particularly interested in your major, but they are interested in how well you did in the discipline(s) you chose to pursue. A double major is not necessarily a positive factor in the admissions process.

While specific coursework may be helpful in corporate law, environmental law or intellectual property, a JD is a generalist’s degree, and applicants come from widely diverse academic backgrounds.

Compile an impressive record

A solid GPA–particularly within your major–is expected, but a willingness to go beyond requirements demonstrates an intellectual curiosity that would be advantageous in the study of law. Academic excellence reflects discipline and abilities, though the variety and depth of your coursework will also be seriously considered by admissions committees as evidence of your interests and motivation.

In general, lecture courses provide a good foundation for further instruction, while seminars allow you to present, discuss, critique, and defend more specific ideas. Smaller classes give you the opportunity to interact with faculty. Get to know faculty whom you might later ask for recommendations; make yourself stand out as an individual by attending office hours, asking questions in class, and conducting research with faculty.

Pursue Activities

Law schools will be interested in your extracurricular activities, leadership experience, summer jobs, internships, and public service since they seek well-rounded candidates for admission. Select activities that interest you; they do not have to be directly related to law. Over time, get involved in more depth in fewer activities. Take initiative and show leadership.

NAPLA Pre?Law Guide

Determining Where to Apply

With 195 accredited law schools in the United States, how do you decide where to apply and ultimately where to attend? Begin by assembling a list of law schools based on the criteria that are important to you, then revise your choices according to your chances of admission.

Do not let the search for "long shots, good chances, and sure things" govern your selection process. Selecting schools carefully will help reduce the time and expense of applying to an excessive number of schools.

Criteria for Selection

Consider the following factors and determine which are important to you:

National/Regional Schools: Does the school attract applicants from across the country

and abroad, or are most students from the region in which the school is located? Do most

students want to work throughout the country or in the school's region following graduation?

Location: Is the school in an urban area or in a suburban/rural setting? Is it part of

university or independent? Are there other graduate schools nearby? Is the school in a place you would want to be for three years and where you would be willing to work following graduation, depending on employment opportunities?

Faculty/Classes: What are the academic and experiential backgrounds of faculty? How accessible are they? What is the faculty-student ratio, the number of full-time vs. adjunct faculty, and the number of female and minority faculty? How many students are in each course? Are classes taught in the Socratic method or lecture?

Facilities and Resources: Is the school affiliated with a university? Do students have access to courses from a range of academic disciplines to supplement their legal curriculum? Is the library large enough to accommodate holdings and permit students to conduct research and study? How helpful is the library staff? How accessible are electronic databases such as Lexis and Westlaw? In general, do the facilities provide a comfortable learning

environment?

Student Body: What is the size of the entering class? What does the admissions profile tell you about the quality of the student body? Where did students study as undergraduates and what are their geographic backgrounds? Is there diversity in interests and personal/cultural backgrounds? What is the overall atmosphere–are students friendly or overly competitive? Is there much interaction with fellow students outside the classroom?

Special Programs: What courses are available in specialized areas? What joint degree programs of interest to you are available? What are the opportunities for practical experience, including clinics, internships, etc.? Can you “write” on to law reviews in addition to be selected based on class rank? What specialized institutes, journals, or organizations exist in your areas of interest? Does the school demonstrate a commitment to women and minorities through special programs?

NAPLA Pre?Law Guide

Career Services: What advising and resources are available to help you find a job? Is career counseling available? How many employers recruit at the law school and who are they? What percentage of the class has positions at graduation? In what types of positions and geographic areas are they employed? What is the percentage of graduates holding judicial clerkships? What assistance is given to students not interested in working in law firms? What is the bar passage rate for recent graduates? How involved are alumni in career activities?

Student Life: Is housing provided for first-year students? If not, does the school offer assistance in locating off-campus housing? Is the school located in a safe area? What is the cost of living? What types of cultural opportunities are there? Does the school provide recreational facilities? What is the general ambiance?

Costs: What are tuition, housing, and transportation costs? Is financial aid exclusively need-based, or are merit scholarships available? Does the school offer a loan forgiveness program for public interest lawyers? What is the average debt burden for graduates from this school?

There are ways to minimize your cost of attending law school and to keep down the debt you incur. Apply to schools where you will be in the top part of the applicant pool; schools may give you a merit scholarship to attract you. Also, public schools are usually less expensive, and even if you are not a resident of a state in which a school is located, you can sometimes pay in-state tuition after your first year.

Reputation

A number of factors contribute to a school’s reputation, including faculty, facilities, career services, and the reputation of the parent university. Though a number of law-school rankings are available, most factors evaluated are not quantifiable, and therefore you should not perceive the rankings as accurate or definitive.

Selectivity at law schools, however, is one factor that can be quantified; you can gauge a school's relative selectivity by comparing the number of applicants accepted to the overall number of applications. Two resources that will help you determine your competitiveness for schools are the Official Guide to ABA-Approved Law Schools (on the left sidebar) and the Boston College  Online Law School Locator. 

Schools can be divided roughly into three groups:

* Schools with national reputations that tend to appear in various "top ten" lists. They draw students from a national pool and offer geographic mobility to graduates.

* Schools with good regional reputations that are attended primarily by students from the region, who may want to remain in the area following graduation, but who may also seek positions throughout the country.

* Local schools that draw students primarily from the immediate area who want to practice there following graduation.

For a more detailed discussion of law school reputation and the process for evaluating schools, refer to the Official Guide to ABA-Approved Law Schools.

NAPLA Pre?Law Guide

Non-Traditional Alternatives

Evening divisions and part-time programs make it possible for students to work and study law simultaneously, earning a J.D. in four years. A few schools on the quarter system allow students to enter mid-year. Summer entry and/or summer courses can accelerate the degree program from three to two-and-a-half calendar years. And finally, some law schools have created summer trial programs, which allow borderline applicants to prove themselves capable of legal study in time for fall entrance.

Publications and Online Resources

There are a number of resources designed to help you research and evaluate law schools. Two essential resources you will want to use include the following:

* ABA • LSAC Official Guide to ABA-Approved Law Schools 2008 provides information on the 195 American Bar Association-approved law schools, including faculty, library resources, enrollment, bar passage, placement, 25th 75th percentile LSAT scores and GPAs.

* The NAPLA/SAPLA Book of Law School Lists 2007-2008 Edition 

provides information about joint degrees, areas of academic emphasis within the schools, schools that grant one-year deferrals, bar passage rates at a number of schools, schools that award non-need-based scholarships, etc.

After you complete your research and compile a list of schools, meet with a pre-law advisor to discuss schools of interest to you and to get a reality check on your competitiveness for them.

NAPLA Pre?Law Guide

Understanding Admissions Criteria

Objective Criteria

Law schools consider the objective criteria, the GPA and LSAT score, the factors that most accurately predict how applicants will perform in their first year:

Law School Admission Test (LSAT): Applicants take the LSAT, a half-day standardized test, during one of four test administrations offered annually by the Law School Admission Council. Scores, which range from 120 to 180, are used by most law schools as a common measurement of potential for success in law school.

Undergraduate Grade Point Average (GPA): Applicants submit undergraduate transcripts to the Law School Data Assembly Service (LSDAS), which converts grades to a cumulative grade point average using a set of consistent values. The GPA offers admissions committees another numerical basis for comparing applicants.

Applicant Index: Many law schools ask the LSDAS to combine applicants’ LSAT scores and GPAs with weighted constants to produce a single number which can be used to assess and compare potential for doing well.

Subjective Criteria

Subjective criteria are the factors law schools consider in addition to GPAs and LSAT scores:

Personal Statement: Applicants submit a personal statement as part of the application process for almost all law schools. Admissions committees look for a concise, detailed, well-written statement revealing the applicant's individuality. They want to learn from the statement who the applicant is and what makes him/her qualified to study at their law schools.

Letters of Recommendation: Most law schools require applicants to submit letters of recommendation from professors or employers to gain a different perspective on the applicant’s academic strength and personal qualities. Admissions officers find most helpful specific examples of applicants’ motivation and intellectual curiosity, an assessment of communication skills, and a comparison with peers.

Experience: This factor includes undergraduate curricular and extracurricular activities, internships, part-time and full-time work experience. Include a resume in your application materials that demonstrates your skills and abilities relevant to the study of law and how you will contribute to the diversity and strength of the class.

Most law schools have recruitment programs to increase participation in the legal profession by underrepresented groups. State schools may reserve seats for state residents. Review websites of schools to learn about their selection criteria, and you may want to contact schools about your specific concerns.

NAPLA Pre?Law Guide

Applying to Law School

After reaching the decision to pursue a law degree, you will want to file a strong and complete application to increase your chances for admission. The first step in the application process will be to meet with your pre-law advisor, who can help you create a strategy for maximizing your chances for success. (If you are uncertain who the pre-law advisor at your school is, the Law School Admission Council will inform you when you register for the Law School Data Assembly Service [LSDAS]).

Next you should open an online account with the Law School Admission Council (LSAC). LSAC is comprised of the 195 American Bar Association-approved law schools in the U.S. and 15 Canadian law schools, and was founded to coordinate and facilitate the process of applying to law school.

Be aware that applying to law school is not inexpensive. Basic costs include:

* LSDAS registration fee

* LSAT registration fee

* Law School Reports

* Application fees (per school)

You might need to add other costs such as LSAT preparation, travel to visit law schools, etc.

LSAC offers fee waivers for those with a demonstrated inability to pay for essential parts of the application. The waivers cover two LSATs per testing year (June through February); the LSDAS registration, including a total of four LSDAS Law School Reports; and, a copy of The Official LSAT SuperPrepR.

Law School Admission Test (LSAT)

The Law School Admission Test (LSAT) is required for admission to all American Bar Association-approved law schools. The test is administered four times per year by the Law School Admission Council (LSAC). Detailed test information–dates, sites, registration forms, fees, and deadlines–and registration is available online, and information is included in the LSAT/LSDAS Information Book, distributed at many colleges and universities.

Be aware that test sites can fill quickly, especially in or around major cities. It is advisable, then, to register several months in advance of a test date so that you can take the test in a convenient location.

The optimal time to take the exam is June of the year you apply, but taking the test in late September/early October will allow you to see your LSAT score before applying in November.

Scores from the December administration will reach law schools in time to complete application deadlines at all schools. If you take the December test, plan to submit your applications around the time of the test. You may, however, decide to wait to see your score before submitting your applications.

The LSAT is designed to provide law school admissions committees with a common measure of

NAPLA Pre?Law Guide

applicants' aptitude for legal study. The test consists of five multiple choice sections, each thirty-five minutes in length:

1) one reading comprehension section

2) one analytical reasoning section

3) two logical reasoning sections

4) one experimental test question section (not scored)

A 35-minute writing sample at the end of the test is also not scored; copies of the writing sample are sent to schools where you apply.

Your score is computed on a scale of 120 to 180, based on the number of questions you answer correctly; there is no deduction or penalty for incorrect answers, so it is advantageous to guess if you do not have time to answer a question.

Begin your preparation with LSAC materials and then assess your progress. If you feel you would benefit from a more structured program of study, you may want to consider taking a commercial test preparation course.

Commercial courses are expensive and the quality of instruction can be uneven, so it is important to learn who will be teaching the course and what materials will be used.

Talk with others who have taken the LSAT to learn from their experience, especially concerning the effectiveness of courses you may be considering. Such courses can be helpful in motivating you to study and in building your confidence.

If you are registered for a test but feel you are not fully prepared or in a frame of mind to perform well, it may be better not to take the test; law schools will not view your absence on the test date negatively. Plan to be well-prepared and to take the test only once, but if you do not believe your score is representative of your abilities, for example, you were scoring considerably higher on practice tests, you may want to consider retaking the test.

Law schools are required to report the higher/highest of multiple scores of students in their entering class to the American Bar Association. Those scores are then reported to organizations such as the Law School Admission Council for use in their online and print information.

Schools vary, however, in how they consider multiple LSAT scores in making admissions decisions. Though many schools use the higher/highest score in reaching decisions, some of the more competitive schools use the average of multiple scores unless there is a compelling reason to use the higher/highest score.

Most schools welcome an addendum explaining the point difference in scores, including any extenuating circumstances and a history of performance on standardized tests. LSAC will report the results of all LSATs you have taken within five years; however, you may find some schools willing to consider only scores received within a three- or four-year period.

Law School Data Assembly Service (LSDAS)

To centralize and standardize objective application information–GPAs and LSAT scores–ABA-approved law schools require applicants to subscribe to the Law School Data Assembly Service (LSDAS). The service organizes and analyzes applicant information in a way that allows law

NAPLA Pre?Law Guide

schools to compare academic records from undergraduate schools that use different grading systems.

Register for the LSDAS, and then send or take transcript request forms, available through LSDAS, to each college or university from which you have earned academic credit.

Study Abroad

If you enrolled in a study abroad program sponsored by your home institution, and the courses along with grades and credits using your home institution’s grading system are recorded on your official transcript, you do not need to send an additional transcript reflecting the study abroad grades/credits. Those grades will be calculated into both the home institution’s GPA and the overall GPA.

If you enrolled in a study abroad program sponsored by another U.S. or Canadian college or university, in addition to your home institution’s transcript, you must have the college or university sponsoring the study abroad program send a transcript directly to LSDAS. List the U.S. or Canadian institution on your LSDAS registration under “other institutions attended.” If the grades and credits appear on the sponsoring school’s transcript, using the school’s grading scale, then those grades will be calculated into both the sponsoring school’s GPA and the overall GPA, but not into your home institution’s GPA, as this is “transfer” work.

If you directly enrolled in one or more foreign institutions, and the total amount of work is the equivalent of one year or less, do not list the foreign institution when you register for the LSDAS, and do not have a transcript forwarded to LSAC. You may, however, be required to list your attendance at such institutions on your applications to law schools.

The report prepared by LSDAS will include the following:

* a year-by-year grade and credit summary

* photocopies of all your transcripts

* your GPA for each academic year, your degree GPA from your home institution, and your cumulative GPA reflecting work at your home institution and all other institutions you have attended

* a description of your overall grade distribution

* the mean LSAT score and GPA of students at your undergraduate school who have subscribed to the LSDAS and your percentile graduation rank among those students

* up to 12 LSAT scores from the past five years, including cancellations and absences

* an average LSAT score, if you have more than one score on file

* copies of your LSAT writing sample

The LSDAS report may also include an applicant index described in the Admissions Criteria section.

The Application

There are several options for submitting applications to law schools. You can apply to any ABA-approved law school through the LSDAS electronic application, which streamlines the process by allowing you to enter common information only once; you then complete each

NAPLA Pre?Law Guide

school’s individual application and submit your applications electronically.

You can also complete applications located on schools’ websites, or call the schools to request hard-copy applications. Addresses and phone numbers of admissions offices are provided on schools’ websites.

Completing application forms is a fairly straightforward process. Schools will be seeking basic information about you, including your academic background, extracurricular activities, and employment history. You may be asked to list other schools to which you are applying; responding to this question and/or indicating an interest in financial aid will not affect your chances for admission.

Be truthful and forthright as you complete the applications. Enclose a resume with your application, but be sure to respond to all of the questions on the applications.

Personal Statements

Personal statements are requested by most law schools provide the opportunity to go beyond the objective aspects of the application to discuss who you are and what is important to you.

Schools will be seeking information about your background, personal qualities and leadership skills, and motivation to learn what is unique about you and what distinguishes you from other candidates with similar GPAs and LSAT scores.

Your goal, then, will be to write a concise, detailed statement establishing yourself as an individual. An interesting and personal discussion about yourself, one that reveals your personality and character, will help you come alive to the admissions committee.

Personal statements are typically two double-spaced pages, though you may find that some schools will give more latitude in. If schools don’t provide guidelines on length, it’s advisable to submit a statement that’s approximately two pages in length. A few schools will limit the number of words permitted and you should abide by their guidelines.

Proofread carefully, as any typographical or grammatical errors will detract from the favorable impression the statement might otherwise make. Do not use large words in an attempt to impress readers; instead, use simple language correctly, and rely on well-organized, interesting content to make an impression.

Your statement should be serious, honest, and sincere, and the tone should be confident and positive; any negative information you feel compelled or are required to discuss should be addressed in other parts of the application or in an addendum.

Law schools will be looking for evidence that you can write a coherent statement. Follow general guidelines for writing essays: there should be introductory and concluding paragraphs; each paragraph should begin with a topic sentence; and there should be a clear line of development through the statement. Ideas should be supported with concrete examples.

Letters of Recommendation

Most law schools request that one or two letters of recommendation be submitted on behalf of

NAPLA Pre?Law Guide

applicants. If letters are not required, it is a good idea, nonetheless, to submit them.

Admissions committees will be seeking information not provided elsewhere in the applications. Recommendation letters should include concrete examples of intellectual strength, judgment, motivation, and leadership, along with an appraisal of communication skills and a comparison to peers.

Letters written by members of the academic community carry the most weight, since they can address your performance in an academic setting and discuss your potential for success in law school. Law schools value letters that address a student's writing, class participation, research, analytical skills, and other academic abilities.

They are especially interested in a professor's assessment of a student, as compared to other students he or she has taught over the years.

At least one letter should be from a professor in your undergraduate major, if possible. As you consider whom to ask, remember that it is better to have an in-depth letter from a teaching assistant or lecturer with whom you worked closely than to have a cursory letter from a renowned professor who barely knows you.

Letters from people outside academia may carry less weight, since they may be unable to address the topic of greatest interest to admissions committees: your academic potential. However, if you have been in the work force a couple of years or more, letters from supervisors can be helpful.

You can submit additional letters even though a school asks for only one or two. Three letters will be acceptable at most schools, and four should be considered the absolute maximum.

Make an appointment to meet with letter writers well in advance of the application deadline. Ask them, "Do you feel you know my work well enough to write a positive letter on behalf of my application to law school?" Provide information about your background to assist him/her in writing a detailed letter:

* a cover sheet describing your academic relationship, including courses you have taken, research you have conducted, your experience as a TA, etc.

* a copy of your transcript

* a draft of your personal statement (if available)

* a resume

* copies of exams or papers written in his/her class

* recommendation forms from LSDAS or the law schools

* stamped envelopes addressed to the LSAC or to the schools

* a list of dates when recommendations are due

Waive your right of access since you may find writers unwilling to write letters if applicants have access to them, and some admissions committee members may discount disclosed letters.

If you have not been notified that your application is complete by about one month before a deadline, contact the school to see if your recommendations have arrived. Speak with those writers who have not sent letters yet to remind them politely of the approaching deadline. After you have received decisions, send thank-you letters to your recommenders, and let them know where you have been accepted and where you intend to enroll.

NAPLA Pre?Law Guide

The Law School Data Assembly Service offers a recommendation service (LOR). Recommenders send letters directly to the LSDAS, which then forwards up to four letters to law schools to which you are applying. You can specify that targeted letters be sent to specific schools; otherwise, general letters will be sent to every school to which you apply.

Letters will be maintained for five years from the time you register for LSDAS or from the time you take the LSAT, whichever comes last.

Dean’s Certifications

A dean’s certification (or letter/clearance) is required by some law schools to confirm that

applicants have not been involved in academic or disciplinary transgressions as undergraduates.

The certification is generally a formality handled by a designated university official such as an academic advising dean, professor, or registrar, in consultation with those offices responsible for judicial administration on campus. Check with your school’s pre-law advisor to learn who is responsible for preparing dean’s certification forms.

Filing Your Applications

Use this checklist to ensure you are completing all parts of the application:

* Prepare for the LSAT

* Register for the LSAT and LSDAS

* Order LSAT prep materials, videos, and publications

* Change your LSAT location or date, if necessary

* Check test center availability and account information in real time

* Obtain your LSAT score by e-mail and view online your answer sheet, score conversion table, and test book (for disclosed tests)

* Check the status of your file online, including your transcript, letters of

recommendation, and law school requests for your LSDAS report

* Research law schools and application deadlines

* Apply to law school electronically

Remember that your file is not complete until all parts, including the recommendation letters and LSDAS report, have been received by law schools.

Here are some additional strategies for applying to law school:

* Start early.

* Make realistic choices on schools.

* Read carefully information provided by schools online or in hard copy.

* Follow directions.

* Print copies of your applications to use as drafts.

* Use LSAC’s electronic applications or type your applications.

* Provide complete and accurate responses.

* Make copies of your completed applications.

* Submit fees with your applications

* Respect deadlines.

NAPLA Pre?Law Guide

Taking Time Off

Taking some time before entering law school can be advantageous for several reasons:

* You will be able to devote more time and energy during your senior year to your academics rather than to preparation for the LSAT and time-consuming law school applications.

* When you apply to law school, your entire academic record will be available to

law schools, not just six or seven semesters; if you are like most students,

your highest grades will come later in your undergraduate education.

NAPLA Pre?Law Guide

Considering Admissions Decisions

Applicants are informed by e-mail or letter of the schools' decisions; candidates are either accepted, denied, or wait-listed, which means the applicant is considered a desirable candidate and may be admitted later.

Law schools often place applicants on "hold" or "reserve" prior to reaching a decision and frequently notify candidates of this status. Applications of those on hold or reserve are reconsidered at a later date, usually before the files of those who have been wait-listed.

Enhancing Your Application

There are several things you can do to improve your chances of admission if you are on reserve or have been wait-listed:

* Write a letter to the director of admissions to inform him/her of your strong

interest in the school and to provide an update on your activities since you submitted your

application.

* If the school is your first choice, state that you will attend if accepted.

* If you are a senior, inform the school of accomplishments since you applied, for example, that you have completed your honors thesis or you were accepted into Phi Beta Kappa.

* If you are currently working, describe your professional responsibilities and other worthwhile activities in which you are engaged; include an updated resume.

* Send an additional recommendation from a professor or employer; however, the total number of your recommendation letters should not exceed four.

* Visit the law school to demonstrate your strong interest; contact the admissions office to arrange for a tour and to sit in on a class or two. Some admissions officers will agree to meet with applicants, but generally these discussions are not evaluative.

Contact your pre-law advisor for additional strategies and tactics.

Making a Decision

Visit the law schools when deciding among schools that have accepted you. Take tours and attend classes, make an effort to meet faculty and staff, and speak with students to get their perspective on factors important to you, such as accessibility of faculty, competitiveness of students, career services, assistance of library personnel, etc.

Follow up with a thank-you letter to the admissions office stating what impressed you about the

NAPLA Pre?Law Guide

school.

Talking with students/alumni at schools of interest about their experience can be helpful in reaching your decision. Contact the schools to inquire about speaking with current students and whether they have an alumni network you can access.

Cost and financial aid awards also need to be considered when making a decision. If you will be entering law school with debt accumulated as an undergraduate, financial factors can play an even greater role in your decision.

If you are deciding between a school that is highly regarded and one that interests you but is less prestigious, keep in mind that more highly ranked schools will, in general, provide better opportunities after graduation. Large firms focus their recruiting efforts at these schools, and salaries of graduates tend to be higher.

Schools that accept you will probably ask for a deposit to hold a space for you. Deposits may be due before you hear from all schools. Contact schools that accept you to explain your situation and ask if they would be willing to extend the deposit deadline. Also, consult with a pre-law advisor who can help you weigh your options.

On June 15 each year, law schools may be provided information concerning applicants’ commitments to enroll. Applicants should be aware of policies on multiple deposits set by schools to which they applied.

Once you have reached a final decision on which school you will attend, notify schools that accepted you so that they can offer your place to someone else.

Reapplying Later

If you are not accepted at a law school you would like to attend, consider retaking the LSAT if you feel that you can improve your score, or revising your list of schools if you decide to reapply. Working for a few years can make a difference in the admissions process and can also provide exposure to another career field that might engage your interest.

You are encouraged to refer to the Law School Admission Council’s Statement of Good  Admissions and Financial Aid Practices, which will help you understand the practices governing the admissions and financial aid process.

NAPLA Pre?Law Guide

Financing Law School

Law school is an important investment in your future. Consider the financial aid process as seriously as you do the law school application process.

Before you apply to law school, spend money wisely and pay your bills on time to ensure a good credit record. Bad credit will affect your ability to borrow money. If possible, pay off credit cards and other consumer debt before law school.

Think about your post-law school goals. Salaries for lawyers vary widely, depending on the type of practice and region. Law school debt will claim a significant portion of your income as a lawyer.

To keep debt to a minimum, consider state-supported law schools, or schools that offer merit-based aid. If you are considering a career in government or public interest law, investigate loan repayment assistance programs (LRAPs) that help law school graduates repay their education debt.

Sources of Funds

Personal Savings/Family Support

If possible, set aside your own funds to help pay for law school. Talk with family members about whether they can help with law school expenses. Some students choose to live at home during law school to avoid paying rent.

Federal Loans

Many students rely primarily on federal loan programs to finance law school. Total federal aid is available to cover (but not exceed) the law school’s student expense budget, which includes tuition and fees, room and board, books and supplies, transportation, and other expenses. Because you are applying for graduate study, you are considered independent of your parents for these loans.

Some law schools participate in the Ford Direct Loan Program, through which the U.S. Department of Education is the lender. At other law schools, you will choose a lender to obtain the federal Stafford or Grad PLUS loans.

The following federal loans are available to law students:

* (Subsidized) Federal Stafford and Direct (Ford) Loan. Up to $8,500 a year is available to students who meet the need criteria. Interest is paid by the federal government while you are enrolled at least half-time.

* (Unsubsidized) Federal Stafford and Direct (Ford) Loan. In combination with the subsidized loan, a student may borrow up to a combined total of $20,500 in subsidized and unsubsidized loans.

* Graduate PLUS Loans for Law Students. Law students with an absence of bad credit may be eligible for these loans. Many law students are choosing Graduate PLUS

NAPLA Pre?Law Guide

instead of private loans to cover their remaining financial need beyond the $20,500 available through Stafford loans.

* Federal Perkins Loans. These low interest loans are available at some law schools. Each student's award is determined by the school, based on information obtained from the FAFSA (see How to Apply for Financial Aid) .

Private Loans

Credit is an important factor in securing private loans. Interest rates, fees, and terms of

repayment vary significantly.

It is best to work with your law school financial aid office BEFORE making a decision about loans for law school.

Beware of direct marketing from private lenders. It is possible to finance your legal education entirely through Federal Stafford and Direct Loans along with Graduate PLUS Loans, which are regulated by the federal government and typically have lower interest rates.

Grants and Scholarships

Grants and scholarships are offered by law schools based upon criteria set by the school, which can include academic merit, financial need, ethnicity, specific talents, residency or other qualifications. Check with each law school early in the application process for more information.

Law schools may offer merit scholarships to highly qualified applicants with an offer of admission. When law schools consider your financial need, they may require family income information even if you are considered independent for tax purposes, or for federal education loans.

Some states provide limited grants for law school; there are no federal grants for law students. Certain national foundations and organizations offer grants and scholarships for law school through a competitive application process.

Earnings

The American Bar Association sets limits on the number of hours a first-year law student can work per week. After first year, many law students obtain summer employment and part-time employment during the school year. This can help reduce the amount of money borrowed.

Frugality

It is often said, “If you live like a lawyer in law school, you will live like a law student once you

graduate.” Frugality can be your best friend.

How to Apply for Financial Aid

Check your credit. If you will be using Federal Grad PLUS or private loans for law school, order a free copy of your credit report and verify the information. These loans may not be available if your credit history does not meet minimum standards.

Apply early for financial aid. Check each law school’s website to learn financial aid deadlines. Some schools have priority dates for submitting financial aid information; students who apply earlier have a better opportunity to obtain limited grant money.

NAPLA Pre?Law Guide

Complete your FAFSA as soon as possible after January 1. Completion of the FAFSA (Free Application for Federal Student Aid) is required for all federal student loan programs. The FAFSA also is used by some law schools to collect information for their own institutional aid. Because the FAFSA requires tax information from the previous year, it cannot be completed before January 1.

Some schools have separate applications for financial aid, while others use the law school application or the FAFSA. Schools also vary in how they distribute their own funds.

If you have special circumstances, provide this information to the law school financial aid office. This can be critical for law students who have been working full-time in the prior year or who have unusual medical or family expenses.

Do NOT wait to complete the FAFSA until after you are admitted to a law school. You can list up to six law schools where you want reports sent, and update this list with additional schools.

If your federal tax return will not be ready until later in the spring, you can estimate prior year income on the FAFSA. Parental income is not considered in determining eligibility for federal loans to graduate-level students; you will be directed to skip Section III- Parental Information in the FAFSA.

Making the Decision

Once you have provided all required information, law schools can offer you a financial aid package. To determine your financial need, schools take the estimated contribution calculated by the federal government on your FAFSA and subtract it from the school’s student expense budget.

In deciding which law school to attend, it is important to balance your financial considerations with other criteria, such as reputation, location, size, faculty, programs and placement success. Compare the net of your projected costs at each school you are considering, offset by any offers of grants or scholarships from the school, to determine the amount you will need to make up through loans or personal funds.

Applying for Loans

Once you have chosen a law school, expect to receive important additional financial information from the school. Even though you have already completed the FAFSA and law school financial aid forms, you must still apply for the loans.

Your law school financial aid office will help you identify the correct process for securing federal loans, and, private loans if needed. Do your homework to compare fees and repayment terms for all of your loans, using loan calculators available on financial aid websites (see below). Keep good records of all loan transactions.

Borrow only what you need, and not more, to keep your debt low and your monthly repayment amount manageable.

NAPLA Pre?Law Guide

Financial Aid Resources

lsac.org–Financial aid for law school

fafsa.ed.gov–Standardized financial information about Federal loans, and http://studentaid.ed.gov–more information on federal student aid

AnnualCreditReport.com–Free annual credit report

accessgroup.org/Student-Loans/learn-about-loans/wise-borrower-tutorial.htm–Personal finance and other financial aid information

equaljusticeworks.org/finance–Information on public interest law programs and law school loan repayment assistance programs (LRAP)

finaid.org–Student guide to financial aid

fastweb.com–Financial aid search engine

NAPLA Pre?Law Guide

Legal Career Checklist

Freshman and Sophomore Years

* Select a major in a field that both interests you and allows you to excel academically.

* Begin to form relationships with professors, lecturers, and TAs so that they will know your work well enough to serve as recommenders in the future.

* Expand your education by seeking summer jobs or internships in fields of interest.

Junior Year

* Meet with a pre-law advisor to assess your academic, extracurricular, and work experiences and to discuss the application process.

* Begin preparing for the LSAT; if you are ready, register for the June administration.

* Secure a summer job or internship, if possible, in a law-related field.

* Research law schools and compile a list of tentative schools.

Senior Year (or Year Before Entering Law School)

* Decide whether to use the Law School Admission Council’s electronic applications to apply, or call/write to law schools or visit their websites to request catalogs and application materials.

* Register for the Law School Data Assembly Service (LSDAS). Have transcripts from all undergraduate institutions you have attended sent to the LSDAS after verifying their accuracy.

* Make sure your LSDAS report is correct.

* Ask potential recommendation writers if they would be willing to write letters on your behalf. Provide them with the LSDAS recommendation forms or the schools’ forms along with sufficient information to write detailed letters.

* Make arrangements to have dean’s certifications sent to schools that require them.

* Attend law school fairs and programs offered by your college or university on the application process.

* Take the LSAT on September 29 if you did not take the test in June.

* Begin drafting and revising your personal statement.

* Meet with a pre-law advisor, who will help you assess the strength of your application in relation to schools you are considering. Request a critique of your personal statement draft.

* Complete applications by early to mid-November.

* Take the LSAT on December 1 if you did not take it previously or are retaking the test.

* Check with schools to make sure your files are complete.

* Complete the FAFSA and other need analysis forms such as Need Access as well as any institutional financial aid applications as soon after January 1 as possible.

* Have financial aid transcripts sent from Cornell to all schools to which you are applying.

* Meet with a pre-law advisor in the spring to assess your options as schools respond to you.

* Take appropriate action on acceptances, wait-list status, and financial aid packages.

* Before leaving campus, have a final transcript sent to the law school you plan to attend and/or to any schools still considering your application.

NAPLA Pre?Law Guide

Legal Career Resources

The Law School Admission Council provides a comprehensive listing (Resources for Prelaw Candidates, Bibliography) of resources to help prospective law students explore legal careers, consider legal education, apply to law school, and finance their law school education.

Law-Related Organizations

* American Bar Association (ABA) is the national organization of the legal profession. The Council of the Section of Legal Education and Admissions to the Bar of the ABA is identified by the U. S. Department of Education as the "nationally recognized accrediting agency for professional schools of law.

* Council on Legal Education Opportunity (CLEO) assists economically and educationally disadvantaged applicants in preparing for law school. Contact CLEO at abanet.org/cleo.

* Law School Admission Council (LSAC) is a nonprofit corporation comprising 210 law schools in the U.S. and Canada that provides services to the legal education community.

* The Association for Legal Career Professionals (NALP) is dedicated to facilitating legal career counseling and planning, recruitment and retention, and the professional development of law students and lawyers.

* HEATH Resource Center is a national clearinghouse for persons with disabilities.

The following organizations can provide advice and help to minority candidates applying to law school:

* ABA Commission on Racial and Ethnic Diversity in the Profession 

* Asian American Legal Defense and Education Fund (AALDEF)

* Hispanic National Bar Association (HNBA)

* Mexican American Legal Defense and Education Fund (MALDEF)

* NAACP Legal Defense and Education Fund 

* National Asian Pacific American Bar Association (NAPABA)

* National Black Law Student Association (NBLSA)

* Native American Rights Fund (NARF)

* Puerto Rican Legal Defense and Education Fund (PRLDEF)

NAPLA Pre?Law Guide

PRINT ON DEMAND SUBMISSION GUIDELINES

Bookblocks

The bookblock is everything but the cover. Printing limitations are as follows:

4 Minimum of 40 pages

4 Maximum of 550 pages, anything larger and the cover starts to become prohibitively small.

4 Books can be trimmed from about 4.75” squared to a maximum of 8.25”x10.75”

4 The more pages a book has, the wider the spine will be, cutting into the maximum trim size.

In order to submit your bookblock as a print-ready PDF file:

1. Ensure that you are 100% happy with your final written product. If you aren’t, do not

proceed. Any word processing program will most likely work.

2. Format your pages so that they appear how you want them to in your book. These detailed formatting guidelines work with Microsoft Word

a. Using Page Setup change your paper size to whatever you want. We recommend 5.5” x 8.5”. Apply to the whole document.

b. Set all of your margins to 0.8”.

c. Under Paragraph, we recommend tab settings of .25”.

d. Choose your Font and Point Size for the text body. We recommend 11 font. Good choices for font style include: Garamond Palatino Times New Roman Century

e. Choose a Font and Point Size for your headings. Generally you will to increase your heading size from your text and consider using boldface or italics to differentiate your heading from your text body. If you change your font some good options include: Gil Sans Verdana Arial

f. Under Paragraph, we recommend line spacing of 1.15.

g. Look at your pages and determine if the tops and bottoms of your pages look the way you want them to. At all costs, avoid using the Return/Enter key or space bar to get your work to look the way you want it. Use “Page Break”, “Tab”, and “Center” keys. This will save you a lot of frustration, trust us.

h. Save your numbered pages as a Word document. Save the rest of your work, the frontmatter, as a separate document.

i. Using Insert Footer or Insert page Number insert page numbers into your saved text. We recommend that you use a font already present in your body text or headers and make it a couple points smaller than the body text.

3. Save both Word documents as a puff using Adobe Acrobat PDF conversion software.

You should be able to combine the files into one at this point.

394 Railroad St., Ste. 2 St. Johnsbury, Vermont 05819 802 748 3551 fax 802 473 7436

www.railroadstreetpress.com

Cover

The cover is arranged left to right...back+spine+front in a landscape orientation. In the binding process it is wrapped around the bodyblock and then gets trimmed to the size of the bodyblock.

Make sure of the following before creating your cover.

1. The total number of interior pages in your book, including front and back matter, and blank pages.

2. Determine the thickness (PPI) of the paper that the book will be printed on. From this, you will be able to determine the thickness of the book spine: total interior pages ÷ PPI.

3. Make sure the cover is centered vertically and horizontally on an 11” x 17” page.

4. Maximum cover dimensions are “10.75 x 16.75”.

5. No unwanted marks

6. Allow for a 1/2” bleed on all sides so that your images/color will print to the edge after book trimming.

Environmental Statement

We are proud to use the Espresso Book Machine and the EspressNet. These devices will allow for many books to be passed around the world electronically, reducing carbon emissions. In addition, the paper we have chosen to use in the EBM is certified by the forestry service council as being harvested responsibly without emitting additional carbon into the atmosphere. 93 percent of the electricity used to run the EBM comes from carbon-free generation.

394 Railroad St., Ste. 2 St. Johnsbury, Vermont 05819 802 748 3551 fax 802 473 7436

www.railroadstreetpress.com

HP Service Manager

Software Version: 9.41

For the supported Windows® and UNIX® operating systems

Language Pack Installation Guide

Language Pack Installation Guide

Legal Notices

Warranty

The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

Restricted Rights Legend

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Copyright Notice

© 1994 - 2015 Hewlett-Packard Development Company, L.P.

Trademark Notices

Adobe® is a trademark of Adobe Systems Incorporated.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

Oracle and Java are registered trademarks of Oracle and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.

For a complete list of open source and third party acknowledgements, visit the HP Software Support Online web site and search for the product manual called HP Service Manager Open Source and Third Party License Agreements.

Documentation Updates

The title page of this document contains the following identifying information:

?Software Version number, which indicates the software version.

?Document Release Date, which changes each time the document is updated.

?Software Release Date, which indicates the release date of this version of the software.

To check for recent updates or to verify that you are using the most recent edition of a document, go to: https://softwaresupport.hp.com/.

This site requires that you register for an HP Passport and to sign in. To register for an HP Passport ID, click Register on the HP Support site or click Create an Account on the HP Passport login page.

You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details.

Support

Visit the HP Software Support site at: https://softwaresupport.hp.com.

This website provides contact information and details about the products, services, and support that HP Software offers.

HP Software online support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by using the support website to:

?Search for knowledge documents of interest

?Submit and track support cases and enhancement requests

?Download software patches

?Manage support contracts

?Look up HP support contacts

?Review information about available services

?Enter into discussions with other software customers

?Research and register for software training

Most of the support areas require that you register as an HP Passport user and to sign in. Many also require a support contract. To register for an HP Passport ID, click Register on the HP Support site or click Create an Account on the HP Passport login page.

To find more information about access levels, go to: https://softwaresupport.hp.com/web/softwaresupport/access-levels.

HPSW Solutions Catalog accesses the HPSW Integrations and Solutions Catalog portal website. This site enables you to explore HP Product Solutions to meet your business needs, includes a full list of Integrations between HP Products, as well as a listing of ITIL Processes. The URL for this website is https://softwaresupport.hp.com/group/softwaresupport/search-result/-/facetsearch/document/KM01702710.

HP Service Manager (9.41) Page 2 of 3

Language Pack Installation Guide

Contents

Introduction 1

Language pack installation checklist 2

Installing language pack 3

Windows installation requirements 3

Unix installation requirements 4

Prerequisites 4

Required knowledge 4

Service Manager language pack setup 5

Applying the language pack and reconciling the differences   5

Setting up a copy of your production system 6

Applying the language pack 6

Reviewing the results 8

Description of View/Merge results   9

Reconciling differences 10

Merging new objects with your tailored objects 10

Creating and applying the production patch 11

Creating the production patch 12

Testing the production patch 13

Applying the production patch 13

Going live after applying the production patch 14

Viewing Language Pack Information 14

Installing localized help 16

Installation requirements 16

Help language pack setup 17

Send Documentation Feedback 19

HP Service Manager (9.41) Page 3 of 3

Introduction

This document includes the requirements and instructions for installing the HP Service Manager 9.41 language pack components. This document consists of the following sections.

? "Language pack installation checklist" on page 2

? "Installing language pack" on page 3

? "Installing localized help" on page 16

HP Service Manager (9.41) Page 1 of 20

Language pack installation checklist

Use the following steps to install the HP Service Manager 9.41 language packs.

Task

Description

1

If you have not done so already, install the Service Manager components listed in "Prerequisites" on page 4.

See the localized versions of the HP Service Manager 9.40 Interactive Installation Guide on the Language Pack installation CD for installation instructions for these components.

2

Back up your Service Manager applications data.

3

Install the Service Manager server language pack.

Note: Each language has its own separate installation package. To install multiple language packs, you will need the installation packages for all your desired languages.

See "Installing language pack" on page 3.

4

If you want to provide localized online help from a central web server, install the localized help for the language you want to support.

See "Installing localized help" on page 16.

Note: Minor.minor releases of Service Manager (such as SM 9.33) do not provide localized versions of the Service Manager online help.

5

If you want to make customizations to your Windows clients such as changing the splash screen, adding custom images, adding company branding, saving default settings and connections, and configuring connections to a help server or update site, follow these steps:

1. Install the Client Configuration Utility from the English installation CD.

Note that this utility has been updated since SM 9.32. See the localized HP Service Manager 9.40 Interactive Installation Guide on the Service Manager 9.40 Language Pack installation CD for instructions on using the Client Configuration Utility.

2. Open the Client Configuration Utility and customize any additional settings for your multi-language Windows client.

3. Deploy the customized and localized Windows client installer to your development environment.

HP Service Manager (9.41) Page 2 of 20

Installing language pack

The procedure described in this section is specifically for applying language packs for HP Service Manager 9.41.

Note: Unlike previously release language packs, Service Manager 9.41 language packs are designed to use Applications Patch Manager for installation.

The Applications Patch Manager described here is the same as the Applications Patch Manager that you use to apply regular applications patches and Applications Content Packs, except that it has been extended to support language packs.

You must install the server language pack on the same system where you installed the Service Manager server. You can install multiple languages on a Service Manager server. This allows users to select the language they want Service Manager to display the applications forms in.

While the server displays Service Manager applications forms in the selected language, the client’s operating system language determines the language that the client menus display. For example, a Windows client running on an English operating system will display menus in English even though the applications forms might be in Japanese.

You can install the Service Manager server language pack on either a Windows or Unix system.

Note: All steps described in this section must be performed in the Windows client. Applying a language pack using the web client is not supported.

Windows installation requirements

?Compatible Windows operating system (See the Service Manager support matrix)

   o Install the most current Windows updates

   o Install the Service Manager language pack for Windows

?Existing Service Manager server installation

   o Back up your applications data

?50 MB disk space for each language pack you install

HP Service Manager (9.41) Page 3 of 20

Language Pack Installation Guide

Installing language pack

Unix installation requirements

. Compatible Unix platform (Seethe Service Manager compatibility matrix)

   o Install the most current Unix platform updates

   o Install the Service Manager language pack for Unix

. Existing Service Manager server installation

   o Back up your application data

. 50 MB disk space per language installed

Prerequisites

Installing a Service Manager 9.41 language pack with Applications Patch Manager requires the following prerequisites.

. Service Manager 9.41 server and Windows client

. Service Manager 9.41 Applications (in English)

.Before you can install the latest language pack on top of the Service Manager 9.41 applications, your system must have already an earlier 9.4x language pack applied. If not, install the Service Manager 9.40 language pack and then install the latest language pack.

Required knowledge

You should be an experienced System Administrator who is familiar with your Service Manager installation.

You should be familiar with the following:

. How your existing Service Manager system operates

. How the application files function

. How to compare records

HP Service Manager (9.41) Page 4 of 20

Language Pack Installation Guide

Installing language pack

If you do not have the administrative experience necessary to apply the language pack, you may need assistance from your local applications developers and database administrators. You can also contact HP Customer Support.

Service Manager language pack setup

Follow the instructions in this section to use the Applications Patch Manager to install the language packs for HP Service Manager 9.41.

You must install language packs on a system that has already upgraded to the Service Manager 9.41 Applications.

If you are upgrading from a previous 9.4x version, you must first upgrade the English version of your applications data (including conflict resolution, testing, creating a production patch, and applying the production patch), and then upgrade your language packs.

If you are upgrading from a previous 7.x/9.3x version with a language pack already installed, the Upgrade Utility automatically upgrades the previously installed language pack; for a language pack that was not previously installed, you can first install the Service Manager 9.40 language pack and then install the Service Manager 9.41 language pack.

Caution: Installing the Service Manager 9.41 language packs will erase the 9.41 applications patch release results and previous language pack upgrade results.

Topics in this section include:

? "Applying the language pack and reconciling the differences" below

? "Creating and applying the production patch" on page 11

? "Viewing Language Pack Information" on page 14

Applying the language pack and reconciling the differences

Before you can update your tailored Service Manager system, you need to install the language pack on a copy of the production system, and then handle any objects the system could not update automatically.

Topics in this section include:

HP Service Manager (9.41) Page 5 of 20

Language Pack Installation Guide

Installing language pack

. "Setting up a copy of your production system" below

. "Applying the language pack" below

. "Reviewing the results" on page 8

. "Reconciling differences" on page 10

Setting up a copy of your production system

In order to create the best possible production patch, create the patch on a system that replicates your production environment as closely as possible.

When setting up this system, be sure to incorporate the following:

. The same operating system version

. The same database version

. The same Service Manager client and server versions

. A copy of your production data

Applying the language pack

Once you have set up a copy of your production system, you can apply language pack on that duplicate system.

Before you apply language pack to the duplicate system, be sure to update the Service Manager configuration files:

1. Stop the Service Manager server.

2. Apply the required changes to the configuration files.

The following tables list the changes that you need to make to the Service Manager configuration files (sm.ini and sm.cfg) before applying the language pack. Record all changes that you have

HP Service Manager (9.41) Page 6 of 20

Language Pack Installation Guide

Installing language pack

  made so that you can revert them to the original status after the applying the language pack. sm.ini

Parameter

Changes

Description

ir_disable:1

Add this parameter to the end of

This parameter disables all IR keys on

the sm.ini file if it does not

your existing Service Manager system.

exist.

This will make the upgrade process run faster.

sessiontimeout:

Add this parameter to the end of

This parameter defines the number of

60

the sm.ini file if it does not

minutes that the server waits for a client

exist. If this parameter already

heartbeat signal before the server

exists, update it to the

assumes that the client session has

appropriate value (for example, 1200).

timed out and closes the connection.

A value of 1200 sets the timeout to 20

You can increase this timeout

hours (1200 minutes), a period that

value if the installation fails with

should be enough to complete in a typical

a client session termination.

patching scenario.

Note: Ignore the warning message that tells you this value should be 60.

sm.cfg

Parameter

Changes

Description

sm system.start

If this parameter exists in sm.cfg, comment it out by changing it to: #sm system.start

Commenting this parameter out disables the background processes.

3. Restart the Service Manager server.

After you update the Service Manager configuration files, follow these steps to apply a language pack to the duplicate system:

1. Log in to your Service Manager server as a System Administrator.

2. On the Service Manager toolbar, select Window > Preferences.

3. Uncheck the Client side load/unload checkbox and click OK.

4. Go to System Administration > Ongoing Maintenance > Patch Release and select Apply Patch Release.

HP Service Manager (9.41) Page 7 of 20

Language Pack Installation Guide

Installing language pack

5. Enter the fully qualified path and file name to the patchrel.unl unload file of the language pack, and then click Next. All required files must be saved in a location that the server can directly access. The path must be relative to the server, instead of to the client computer, if the client is not installed on the same machine as the server.

The Applications Patch Manager displays the current version of your language pack and the version that will result after you apply the language pack.

Note: It may take a long time to load the file after you click Next, even though there is no indication that the file is being loaded. Do not click Next again until the versions are displayed or the patch application will fail.

6. Confirm that the source and target versions listed match your current production system and the language pack version, and then click Next.

When the Applications Patch Manager finishes applying the language pack, it displays a message indicating that your system was successfully updated.

7. Click Finish.

You will be disconnected from your Service Manger server.

Reviewing the results

After you apply the language packs to your system, you will be able review the list of updated objects. Follow these steps to review the results of the update:

1. Log in to your Service Manager server as a System Administrator.

2. Go to System Administration > Ongoing Maintenance > Patch Release and select View/Merge Results.

Service Manager displays the Applications Patch Results (Release Type: Content) screen.

3. Enter optional search criteria, and then click Search.

Service Manager displays the results of your search. For more information, see "Description of View/Merge results" on the next page

4. Click a record in the list to review it.

HP Service Manager (9.41) Page 8 of 20

Language Pack Installation Guide

Installing language pack

Description of View/Merge results

The search criteria, search results, and a description of the applicable action for each result are described in the following table.

Fields and applicable actions for each result

Field

Definition

Object

Name

Enter the name of the object you want to search for, or leave this field blank to return objects with any name. The object name is typically the unique identifier in the database table specified for the object type.

Object

Type

Enter the type of object you want to search for, or leave this field blank to return all object types. The object types for language pack are: format, scmessage, and help.

Result: Added

Select this option to search for new objects that were added to the system by the patch. These objects did not exist in your system before this update.

For objects with this result, no further action is necessary.

Result:

Error

Select this option to search for objects that encountered an error while being updated by the Applications Patch Manager. For more information about the error, review the sm.log file.

Required Action: Fix the cause of the error in a copy of your production system, and then apply the language pack again.

Result: Forced

Select this option to search for objects that were tailored on your Service Manager system, where the Applications Patch Manager added the new object and backed up your tailored object as a revision. You will only see this result after applying the production patch.

For objects with this result, no further action is necessary.

Result: Merged

Select this option to search for objects that were tailored on your Service Manager system, which you have merged with the version in this patch.

Required Action: Test these objects, and when satisfied change their result to Reconciled.

Result: Previously Reconciled

Select this option to search for objects that were tailored on your Service Manager system, that were marked as reconciled during a previous upgrade or patch release, or where your object was not changed and the Applications Patch Manager added a new object NEW<language pack name><object name>.

Required Action: Choose one of the following for each object with this result.

? Keep the old version — No further action is necessary.

? Keep the new version — Select the object in the merge view and click Copy all from left to right on the tool bar.

HP Service Manager (9.41) Page 9 of 20

Language Pack Installation Guide

Installing language pack

Fields and applicable actions for each result, continued

Field

Definition

?Merge new and old versions — Determine which of the new features should be incorporated into your tailored object, and then make the changes in your tailored object. When finished, delete the new object.

Result: Reconciled

Select this option to search for objects that you have already marked as Reconciled. For objects with this result, no further action is necessary.

Result: Renamed

Select this option to search for objects that were tailored on your Service Manager system, and where your object was not changed and the Applications Patch Manager added anew object NEW<language pack name><object name>. You will only see this result after applying the out-of-box patch.

Required Action: Choose one of the following for each object with this result.

? Keep the old version — No further action is necessary.

? Keep the new version — Select the object in the merge view and click Copy all from left to right on the tool bar.

? Merge new and old versions — Determine which of the new features should be incorporated into your tailored object, and then make the changes in your tailored object. When finished, delete the new object.

Result: Updated

Select this option to search for objects that were automatically updated by the Applications Patch Manager. These are objects that were not tailored on your Service Manager system.

For objects with this result, no further action is necessary.

Result:

Already

Current

Select this option to search for objects that were already the latest version. For objects with this result, no further action is necessary.

Reconciling differences

The next step is to reconcile any differences between your tailored objects and the updated objects introduced by the language pack. You can use the standard Service Manager tools, or the Merge utility.

Merging new objects with your tailored objects

After you have applied a language pack successfully, you are ready to reconcile the differences and merge the new objects with your tailored versions of the objects where necessary.

Follow these steps to use the Merge utility:

HP Service Manager (9.41) Page 10 of 20

Language Pack Installation Guide

Installing language pack

1. Log in to your Service Manager server as a System Administrator.

2. Go to System Administration > Ongoing Maintenance > Patch Release and select View/Merge Results.

3. Enter optional search criteria, and then click Search.

Service Manager displays the results of your search. For more information, see "Description of View/Merge results" on page 9.

4. Open the record you wish to merge, right-click the detail page and then click Merge in the drop-down menu.

Service Manager displays both objects side-by-side in the Merge Applications Patch Records view.

Tip: The XML for the new object is shown on the left side, and the XML for your tailored object is shown on the right side with the differences highlighted.

5. For simple objects and elements, use the arrow buttons at the top of the pane to select individual changes and copy them from the new object over to your tailored object, or copy all changes from the new record to your tailored object. For complex objects, do the merge manually by using the appropriate tool for the object type.

6. Click SAVE.

7. Change the Result to Merged and then click Save.

8. Test the updated functionality of the merged object.

9. When you are satisfied that the object is working correctly, right-click the detail page and then click Mark as Reconciled in the drop-down menu.

10. Repeat this procedure for all changes that need to be merged.

Creating and applying the production patch

Once you have handled all objects requiring reconciliation, you will create a language pack package with your tailoring incorporated and apply it to your actual production system. It is recommended to back up your database after reconciliation to prevent any unexpected loss.

Topics in this section include:

HP Service Manager (9.41) Page 11 of 20

Language Pack Installation Guide

Installing language pack

? "Creating the production patch" below

? "Testing the production patch" on the next page

? "Applying the production patch" on the next page

? "Going live after applying the production patch" on page 14

Creating the production patch

Once you are satisfied with the results of your reconciliation process, you can create a production patch. Follow these steps to create the production patch:

1. Log in to your Service Manager server as a System Administrator.

2. Go to System Administration > Ongoing Maintenance > Patch Release and select Create Patch Release.

The Applications Patch Manager asks you to prepare an area to contain the applications patch files that you will create. This can be referred to as the production patch directory.

a. Using the standard method for your operating system, create the production patch directory.

b. Copy the file patchrel.txt from the directory where you unzipped the out-of-box patch release to the production patch directory.

c. Enter the fully qualified path and file name to patchrel.txt in the production patch directory. This path must point to a location that the server can access.

3. Click Next.

The Applications Patch Manager displays the version you will create the patch for.

4. Click Next to create the patch.

The Applications Patch Manager creates the production patch in the product Applications Patch Manager patch directory.

After you test this patch and confirm that it works as desired, you will be able to apply it to your production system.

HP Service Manager (9.41) Page 12 of 20

Language Pack Installation Guide

Installing language pack

Testing the production patch

After creating the applications patch for your production system, test it extensively. This will be an iterative process that may require several changes to patch objects and the recreation of production patches. Employ user acceptance testing verification and validate your changes.

Applying the production patch

The steps that you used to apply the language pack to the copy of your production system are the same steps you need to apply to the production patch that you created in your actual production system.

Before you apply language pack to your production system, be sure to update the Service Manager configuration files:

1. Stop the Service Manager server.

2. Apply the required changes to the configuration files.

The sm.ini and sm.cfg tables in "Applying the language pack" on page 6 list the changes that you need to make to the Service Manager configuration files (sm.ini and sm.cfg) before applying the language pack. Record all changes that you have made so that you can revert them to the original status after the applying the language pack.

3. Restart the Service Manager server.

After you update the Service Manager configuration files, follow these steps to apply a language pack to your production system:

Note: When applying the patch to the production system, you must be the only user logged in to the system.

1. Have all users log out of the server.

2. Prevent users from logging into your Service Manager Server by running the quiesce command from the operating system’s command prompt.

sm -quiesce:1

3. Log in to your Service Manager server as a System Administrator.

4. Go to System Administration > Ongoing Maintenance > Patch Release and select Apply Patch

HP Service Manager (9.41) Page 13 of 20

Language Pack Installation Guide

Installing language pack

Release.

Service Manager displays a screen that asks you to find a file called patchrel.unl.

5. Enter the fully qualified path and file name to patchrel.unl in the production patch directory, and then click Next. This path must point to a location that the server can access.

The Applications Patch Manager displays the current version of your applications and the version that will result after you apply the patch.

Note: It may take a long time to load the file after you click Next, even though there is no indication that the file is being loaded. Do not click Next again until the versions are displayed or the patch application will fail.

6. Confirm that the source and target versions listed match your current production system and the language pack version, and then click Next to apply the language pack.

When the Applications Patch Manager finishes applying the language pack, it displays a message indicating that your system was successfully updated.

7. Click Finish.

8. Log out from your Service Manger server, and then log in again.

9. Allow users to log in to the server by running the quiesce command from the operating system’s command prompt.

sm -quiesce:0

Going live after applying the production patch

Any tailored objects that were updated by the language pack are backed up as a revision. If issues are encountered after going live, these objects can be quickly swapped back to their original tailored versions. After a period of time, you may want to delete the old revision objects.

Viewing Language Pack Information

Applications Patch Manager allows you to list language packs applied on the system and to view the patching history of each language pack.

Follow these steps to list language packs applied on the system:

HP Service Manager (9.41) Page 14 of 20

Language Pack Installation Guide

Installing language pack

1. Log in to your Service Manager server as a System Administrator.

2. Open the Service Manager Version Information record by doing either of the following:

o In the navigation pane, click System Administration > Base System Configuration > Monitoring > Version Information.

o Open the scversion table the Database Manager and click Search to open the only record.

3. The Content Releases Installed list shows all the content releases and language packs that are installed on the system.

Follow these steps to view language pack details:

1. Log in to your Service Manager server as a System Administrator.

2. Go to System Administration > Ongoing Maintenance > Patch Release and select View Content Information.

3. Click Search to list all language packs.

4. Select a language pack from the list.

Note: Each list item contains all release versions of that language pack.

5. View the information about the language pack in the details pane.

Content Name: indicates the name of the language pack.

Version No.: indicates the current version of the language pack.

Application Version: indicates the application version the first time the language pack was applied.

The list: shows all the previous versions of the language pack.

6. To check the details of a specific release version, click the appropriate item in the list.

HP Service Manager (9.41) Page 15 of 20

Installing localized help

There is no localized online help for Service Manager 9.41. You can get localized Service Manager 9.40 online help from the Service Manager 9.40 Language Pack installation CD.

You can install localized help on one or more web servers. You can host multiple languages from a single web server if you configure the web server so that each language has its own virtual directory and its own unique URL. See your web server help for more information on creating virtual directories.

Caution: You cannot install localized help in the same folder as existing English help. You can either choose a new installation folder or uninstall the English help.

Note: The help is not available in the following languages: Czech, Hungarian, and Polish.

Installation requirements

Have an archive extraction utility

? Have 240 MB disk space

? Have a minimum of 256 MB RAM

o For testing purposes, 128 MB RAM is sufficient.

   o For production purposes, RAM is based on the expected user load.

? Have the multilingual version of Sun’s Java Runtime Environment (JRE)

? If you plan on installing the help on a web server:

o Have a web server installed on the system.

o Have a free communications port to listen for HTTP connection requests. For most web servers, the default communications port is 80.

HP Service Manager (9.41) Page 16 of 20

Language Pack Installation Guide

Installing localized help

Help language pack setup

Use the following steps to install a help language pack.

1. Log onto the system on which you want to install help as a user with local administrator privileges.

2. Insert the HP Service Manager Language Pack installation CD-ROM into the appropriate drive of the server.

3. Access the help archive:

a. To access the help archive from Internet Explorer:

?If you are installing on a system that has auto-run enabled, the DVD browser starts automatically. If auto-run is disabled, start the DVD browser manually by navigating to the DVD directory and opening ClickMe.html.

? Open the Downloads tab.

?Click Download HP Service Manager help to open the help archive, SM_help_ <language>.zip.

Caution: You cannot install localized help in the same folder as existing English help. You can either choose a new installation folder or uninstall the English help.

Note: The help is not available in the following languages: Czech, Hungarian, and Polish.

b. To access the help archive from the command prompt:

Navigate to the \SM_help directory on the installation media. Open SM_help.zip.

4. Extract the online help into your web server's document root. For example, to install the online help on an Apache web server on a Windows system extract the online help into the folder C:\Program Files\Apache Software Foundation\Apache 2.2\htdocs.

The archive creates a folder called SM_help.

Caution: You cannot install localized help in the same directory as an existing English

HP Service Manager (9.41) Page 17 of 20

Language Pack Installation Guide

Installing localized help

installation.

5. Start your web server.

6. Test the help by browsing to the web server's URL:

http://<helpserverhost>:<helpserverport>/<helpdirectory>

where:

o<helpserverhost> is the fully qualified domain name or IP address of the web server hosting the help.

o <helpserverport> is the communications port used to connect to the web server hosting the help. You can omit the port number if you use the default port 80 HTML port.

     o <helpdirectory> is the name of the virtual directory where you have installed the online help. The Service Manager Help Language Pack installation is complete.

HP Service Manager (9.41) Page 18 of 20

Send Documentation Feedback

If you have comments about this document, you can contact the documentation team by email. If an email client is configured on this system, click the link above and an email window opens with the following information in the subject line:

Feedback on Language Pack Installation Guide (Service Manager 9.41)

Just add your feedback to the email and click send.

If no email client is available, copy the information above to a new message in a web mail client, and send your feedback to ovdoc-ITSM@hp.com.

We appreciate your feedback!

HP Service Manager (9.41) Page 19 of 20

0

/ tL Java-OCPATIEtE

Intellectual Property Guidelines

at Queen’s University

(Prepared by the School of Graduate Studies, revised August, 2013)

Intellectual Property Guidelines at Queen’s University

Dear Graduate Students,

These guidelines are intended to support your study and research at Queen’s and to provide you with a general overview of what intellectual property is, what you should know and how to find out more.

In this document, prepared by the School of Graduate Studies in partnership with the Office of Research Services and PARTEQ Innovations, you will find practical guidance about issues associated with intellectual property (IP). I hope that these guidelines will be of use to the broader Queen’s community on matters that arise as part of graduate research involving graduate students and graduate faculty. It is important that you discuss IP with your faculty supervisor to ensure that you understand what, if any, specific considerations might be required. An awareness of IP issues and a plan for protecting IP (e.g. patents, commercialization) is best addressed early in the research process to avoid problems that otherwise could arise.

Note that what follows are guidelines, and do not supersede Senate Policies or provisions in Collective Agreements between the Queen’s University and Employee groups.

I wish you success with your creative and intellectual academic pursuits!

Brenda Brouwer, Ph.D.

Vice-Provost and Dean, School of Graduate Studies

The School of Graduate Studies at Queen’s thanks the University of Toronto for permission to use the basic structure and elements of content from their publication ‘Intellectual Property Guidelines for Graduate Students and Supervisors at the University of Toronto’

2 | P a g e

INTRODUCTION

Universities as institutions of advanced education and research are key sources of knowledge creation promoting innovation, creativity and intellectual capital. A prime commitment of the University is to foster intellectual inquiry, which is enhanced through the existence of policies that deal with issues of ownership and the transfer of results of such inquiry to society. The products of such inquiry are known collectively as intellectual property. Whenever intellectual property is created, questions of ownership may arise in several contexts such as patent application, publication of findings, authorship of creative works, and commercialization. Recognizing that there are diverse circumstances across academic and research units, there is no single set of rules that can be applied to all situations. However, conflict may be avoided if there is appropriate recognition of the contribution of each individual and clear expectations concerning ownership of intellectual property at the outset. Discussion about intellectual property and dissemination should occur early in the research process and it should be open and free from intimidation, harassment and discrimination and ever mindful of situations in which there is a differential power status.

The questions and answers that follow provide information relevant to members of the research community as they pursue creative and scholarly activities.

1. WHAT IS INTELLECTUAL PROPERTY?

Intellectual property is any form of knowledge or expression created with one’s intellect. Specifically, this includes inventions, publications, computer software, works of art, industrial and artistic designs, as well as other creations that can be protected under copyright, patent, or trademark laws. The two main types of intellectual property protection in the University environment are copyright and patents.

Copyright protects original artistic, literary, musical, or dramatic works and written materials and software by preventing anyone from copying, publishing or broadcasting a work without the copyright owner’s permission. Copyright exists as soon as the work is created and is often signaled by marking the work © (author’s name, year). Note that copyright does not protect ideas, but rather the expression of ideas.

1a. Who owns the copyright to my thesis? Can it be published in part or whole by a journal or publishing house?

In the case of a graduate student’s thesis, the student owns copyright to all original work. Third party copyrighted material that is included in a thesis must meet the requirements of the Copyright Act. Students must ensure that they appropriately attribute all third party copyrighted material included in their thesis (e.g. figures and tables) and acquire permission from the publisher. For more information related to copyright and thesis creation, see Copyright and your Thesis (http://library.queensu.ca/copyright/thesis).

If the thesis includes individual chapters or sections that have been published or submitted for publication with co-authors (e.g. manuscript style thesis), a Permission of Co-Authors Form that lists all co-authors with their signatures must be completed in order to include the work in the thesis (http://www.queensu.ca/sgs/forstudents/completion/finalsubmission.html). Chapters or

3 | P a g e

sections that may have already been published prior to final thesis submission are normally allowed to be included in manuscript style theses without obtaining permission. For more information related to copyright and thesis creation, see the getting permission section of the Copyright and your Thesis (http://library.queensu.ca/copyright/thesis#gettingpermission) guide.

In many cases portions of the thesis or the thesis in its entirety may be published after the degree requirements have been met and copyright for the publication is generally transferred to the journal or publishing house at that time.

1b. I have been asked to sign a Library and Archives Canada non-exclusive license agreement. What does this mean?

The license gives the Library and Archives Canada your permission to make your thesis available to interested parties upon request (royalty free, not for profit). You retain copyright ownership of your thesis. Should you assign or license your copyright to someone else, you must inform them of the non-exclusive license agreement with the Library and Archives Canada.

Patents protect new inventions, and are granted, upon application, by the national government in exchange for a complete disclosure of an invention. Patentable subject matter includes devices, processes, new uses of previously known things, and compositions of matter, including chemical compounds and new life forms (e.g. transgenic animals). In most countries, an invention is considered new if it has not been disclosed in an article, presentation, seminar, blog or any other public forum prior to filing a patent application. However, in Canada and the United States there is a one year grace period for filing a patent application if such public disclosure originated with the inventor. A patent prevents anyone from using the invention without the patent owner’s permission.

1c. My work is covered by a patent application. Can I still publish it?

Seeking patent protection for your intellectual property need not prevent you from publishing your research results, providing that there are no existing agreements to restrict dissemination for a period of time. However, publicly disclosing or sharing your findings without initiating patent protection can prevent you from filing for and acquiring a patent later on. If you are planning to present your research findings (including in a seminar, class presentation or thesis defense), and/or submit an abstract, poster or paper, you should seek advice from your supervisor and those knowledgeable about patents and IP (e.g. PARTEQ) beforehand. Once a patent application has been filed, your work described in the application may be presented without loss of rights.

1d. My thesis involves a new invention but the patent application has not yet been submitted or approved. How can I complete the thesis examination and submission without compromising the patent application?

Ideally, patent protection should be initiated before the thesis examination. If this is not possible, there are several things that should be done to ensure confidentiality and non-disclosure of proprietary information. The thesis examination process itself is considered confidential when the student requests a ‘closed’ examination (i.e. only the examination committee and the student are present). If a confidentiality agreement is signed by all present prior to the start of the examination, this is sufficient proof for a patent Examiner that the invention was not publically disclosed. In some instances, a third party (e.g. industrial partner) may request signing of a

4 | P a g e

confidentiality agreement prior to the examination. If the student desires that his/her thesis be kept confidential for some period of time, then upon submission of the final approved thesis in completion of degree requirements, the student must request that the thesis be restricted. This prevents access to the thesis for a five (5) year period, but such embargo may be lifted by the student at any time during the five years (e.g., after the patent application has been filed) upon written request. Note that this restriction does NOT embargo the “metadata” – that is, the thesis title and the abstract. Even if the thesis is restricted, the title and abstract are ordinarily still published on line. In some cases, it may also be necessary or desirable to restrict the metadata. In such cases, a written request including the reason(s) for restricting the metadata must be made to the School of Graduate Studies PRIOR to uploading the completed thesis to QSpace. After a period of five (5) years (or earlier upon written request), the thesis is automatically released and is available electronically.

2. WHAT ARE QUEEN’S UNIVERSITY’S POLICIES REGARDING OWNERSHIP OF INTELLECTUAL PROPERTY?

The University’s policy on intellectual property states that the ownership of all types of intellectual property and for all members of the University should rest with the creators, unless other arrangements have been agreed to in advance for certain categories of employment, for certain types of funding, or by individual contract. Two possible exceptions to this principle of "creator ownership" should be recognized: (1) work for hire and (2) work under a contract between the University and an outside sponsor. In the first instance, intellectual property should be owned by the University if it is created by a faculty member, staff member or student under a contract of employment or service that assigns responsibility specifically for the creation of such intellectual property. In the second instance, intellectual property that is created under a contract between the University and an outside sponsor should be owned by the University. The sponsor may claim ownership only if the sponsor insists on such an arrangement as a condition for funding, and this is acceptable under prevailing University guidelines for contract research. In order to assess your intellectual property rights it is important to understand the nature of your responsibilities and any particular provisions regarding intellectual property rights, publication or confidential information at the outset.

The policy on intellectual property should be viewed in the context of Collective Agreements between Queen’s University and employee groups. To access Collective Agreements between Queen’s University and particular employee groups, please click on the following link: http://www.queensu.ca/humanresources/employees/unions.html 

The Senate report on Intellectual Property can be found at:

http://www.queensu.ca/secretariat/policies/senateandtrustees/intellectualproperty.html

Students should be aware that the university retains a royalty-free irrevocable right to use for educational and research purposes any intellectual property created by a student in relation to his/her research activities.

5 | P a g e

2a. Who can I talk to at Queen’s about protecting my intellectual property?

If you are a student or staff member you should speak with your supervisor first. All members of the Queen’s community (faculty, staff, and students) can consult with the staff of PARTEQ Innovations, a not-for-profit office dedicated to protecting and commercializing research discoveries (www.parteqinnovations.com). For questions about copyright, publishing agreements, Open Access and matters to consider if approached by a publishing company interested in your thesis, the Copyright Advisory Office can offer assistance and provide expertise (http://library.queensu.ca/copyright).

3. I AM EMPLOYED AS A RESEARCH ASSISTANT. WHO OWNS THE INTELLECTUAL PROPERTY THAT I CREATE?

The recommendation of the Senate Ad Hoc Committee on Intellectual Property that ownership of all types of intellectual property should rest with the creators unless other arrangements have been agreed upon in advance applies to all members of the University. Other arrangements may be appropriate for certain categories of employment, certain types of funding, or by individual contract. For example, if the intellectual property is created by a faculty member, staff member or student under a contract of employment or service that assigns responsibility specifically for the creation of such intellectual property then ownership lies with the University. If intellectual property is created under contract between the University and an outside sponsor, the University may require ownership of any intellectual property created in the course of the contract work, in order to fulfill the terms of the contract. In exceptional cases, the sponsor may insist on ownership as a condition of funding.

In the case of many research assistantships held by graduate students or research associate position held by staff, the source of payment is a research grant held by the principal investigator who is usually the employee’s supervisor. As such, the funding is tied to a specific project and its deliverables and the activities of the research assistant are linked to the research objectives as described in the grant. In some cases the contributions of the research assistant may be considered “work for hire” (see section 2). However, in most cases the research assistantship provides support for graduate students as they work on their thesis research (a Graduate research  Assistant Fellowship) and therefore the student makes creative and intellectual contributions that must be recognized and duly acknowledged unless other agreements are in existence (see section 4). Normally acknowledgement is in the form of co-authorship (see sections 5 and 8) or co-applicant on the filing of a patent application. To avoid misunderstandings and potential conflict, the supervisor and research assistant should discuss intellectual property rights at the outset.

4. MY RESEARCH IS SUPPORTED BY EXTERNAL FUNDS. DOES THIS HAVE AN IMPACT ON THE OWNERSHIP OF INTELLECTUAL PROPERTY?

The relationship between funding and ownership of intellectual property is dependent upon who the funding body is, and the terms and conditions of the funding. The federal granting agencies (Social Sciences and Humanities Research Council, Canadian Institutes of Health Research, and Natural Sciences and Engineering Research Council) do not attach intellectual property claims to the research they fund, but require that institutional policies governing intellectual property and

6 | P a g e

its disposition be adhered to in addition to those of other sponsors (e.g. industrial partners, organizations).

Other organizations, notably private companies, do attach intellectual property claims to their support of University research. Some charitable associations or foundations or provincial Centres of Excellence may claim licensing rights or a share of royalties. It is important to be aware of the funding organization’s intellectual property policies with respect to ownership, confidential information and publication as it applies to the research work that you do. In the case of contracts and grants from the private sector, agreements may have a number of provisions with respect to intellectual property, sometimes including a grant of rights in resulting intellectual property. In such instances, project participants will normally be asked to sign an agreement in which they indicate that they have been made aware of the funding terms and agree to abide by them. Faculty involved should consider whether the project is suited for thesis work and if so, the supervisor should disclose all restrictions and conditions at the outset of the graduate work.

4a. I am funded by a scholarship or fellowship from an external agency. What effect does this have on the intellectual property I create?

Scholarships and fellowships are generally adjudicated on the basis of academic merit and research potential and are awarded to the student even though the institution may be required to set up an account to disburse the funds. Since the monies are not to support a research project per sé, but rather to support the student as s/he pursues graduate training, there are no claims on intellectual property. In these situations the student is likely considered as a creator of any intellectual property that results. However, depending on the specific conditions under which the research was undertaken, the student may not necessarily be the sole creator/owner. For example, if others contributed to the concept of the research (e.g. the principal investigator), the analysis and interpretation of the findings, the writing of reports/manuscripts and the like, then they may have a claim on creation/ownership and have intellectual property rights. Consult with your supervisor.

If a fellowship or scholarship is provided by a company, then it is possible that the company may claim rights to resulting intellectual property. The terms and conditions should be clearly laid out and the signature of the award recipient required, indicating acceptance of the award and all its terms and conditions.

5. WHAT RIGHT DOES MY SUPERVISOR HAVE TO ANY INTELLECTUAL PROPERTY I CREATE?

There is no single answer to this as it depends on the individual circumstances, the type of intellectual property, the usual practice within the discipline and whether the research sponsor has rights to own or to license the results of the research (see section 4). In particular, some agreements that require “improvements” to prior or background intellectual property to be assigned or licensed. If the intellectual property is an invention, then patent law determines who is the inventor or co-inventor and, absent other agreements, University policies determine ownership. Students or staff working on a supervisor’s project that could lead to creations or inventions that would be accorded intellectual property rights would have no claim unless they are a co-author or co-inventor. Similarly, a supervisor would have no claim if s/he were not a coauthor or co-inventor. It should be recognized though, that if the work done was part of an

7 | P a g e

ongoing research project or program, the results can be used with appropriate attribution in furthering the supervisor’s research and the research of others working in the same laboratory or group (e.g. in publications, presentations, reports and grant applications).

The rights to intellectual property should be clarified before the submission of papers for publication or disclosure of research findings in any manner which places a creation or invention in the public domain. This is critically important in instances where an application for patent is forthcoming.

With respect to a publication, individuals named as authors must have made a significant intellectual contribution to the work. Individuals hired to perform specific tasks typically do not share authorship, although they may receive acknowledgement for their contribution to the work. The decision about authorship and the order of authors may be based on what is considered the usual practice in a particular field, by the relative contribution made by each co-author, by seniority or by some other method that acknowledges contribution. Increasingly, journals are providing directives with respect to authorship and these must be adhered to.

6. I AM WORKING WITH A PROFESSOR AND OTHER STUDENTS ON A DISCOVERY. HOW DO I KNOW IF I AM AN INVENTOR?

Inventorship is determined by patent law. Generally, an inventor is a person who has contributed an original idea or otherwise made a material contribution to one of the claims granted in a patent. More than one person may be named as an inventor. Inventorship generally gives you rights to a share of the proceeds of your invention should it be commercialized and gives you the right to be informed of the progress of the invention as it makes its way through the patent protection process. However, a person who works under the direction of another and does not contribute any original thought to the claimed invention (for example, working as a technician to confirm an invention) would not be named as an inventor.

6a. What if I am co-author on a paper related to the patent?

Co-authorship is not the same as inventorship. You may be recognized as a co-author in a publication that relates to an invention even though you are not deemed an inventor. However, your contribution to an invention may, in some cases, still be recognized through some sharing of the net proceeds from the invention. Questions about inventorship should be discussed with your supervisor and/or PARTEQ.

7. WHO OWNS THE DATA PRODUCED IN MY RESEARCH PROJECT?

Raw data are not generally considered patentable nor are they creations that can be protected by copyright. Research records and data are to be managed and used in a manner consistent with the highest standards of ethical and scientific practice. According to the Senate Policy on Integrity in Research original data are normally stored in the laboratory or department of the principal investigator. In the case of collaborative research all those directly involved in the conduct of the research (including supervisors and students) will have access to the data. In the case of research involving human subjects, storage of the data and access to it must be in accordance with the procedures outlined by the principal investigator and approved by the University’s Research Ethics Board. Access may be restricted only when a request to do so is made in writing to and

8 | P a g e

approved by the Vice-Principal (Research). The granting agency or research sponsor may have rights to the data as part of the terms of the agreement.

Research records must normally be retained on site for a minimum of 5 years from the date of publication or other form of presentation or communication. The period may be longer if mandated by a legal requirement or an applicable funding or oversight agency. An exception to this would be when, for anonymity purposes, destruction of data has been approved by a Research Ethics Board at Queen`s University.

8. WHEN IS SOMEONE A JOINT INVENTOR? A JOINT AUTHOR?

The fact that a person is not named on the grant or contract under which the research work was performed does not prevent that individual from being named as a co-inventor and/or co-author if their contribution warrants such recognition. A member of the University community who makes an original and substantive contribution to a claimed invention should be named as joint inventor in any patent application. An exception may be if your contribution was limited to the work you were employed to complete and involved standard methodologies/protocols.

The criteria used to determine co-authorship vary across disciplines. It is not uncommon in the humanities and some social sciences that papers are sole authored. Indeed co-authorship is usually limited to cases in which the contributions of the co-authors are indistinguishable. In the physical, applied, natural and life sciences, teamwork and advisory committees are common and members contribute original ideas that help shape the particular project and results. These contributions may be recognized by co-authorship if significant (see also section 5). It is usually the case that co-authors will have made substantial contributions in two or more of the following: concept and design of the experiment; execution of the experiment; analysis and interpretation of the data; and/or the writing of the manuscript. It is normally the supervisor/principal investigator who determines when there is sufficient material to submit a manuscript for publication and may consult with those directly involved in the project to identify target journals.

9. IS IT NECESSARY TO COMMUNICATE INTELLECTUAL PROPERTY?

The University has an obligation to ensure that information and intellectual property is communicated in a timely manner such that it is accessible for scrutiny, wider utilization and societal benefit. It is recognized that knowledge and intellectual property resulting from research and scholarly activities may be disseminated and transferred from the University in many different ways including publications (including published patent applications and patents), presentations, exhibitions, consultation, licensing and commercialization and the movement of personnel to industry, government and other institutions.

Ownership of intellectual property must not be used to suppress the dissemination of or distort results of research or creative work produced by members of the University. In some cases the publication of findings may be deferred for legitimate reasons such as to allow time to apply for patent protection or to comply with the terms of sponsored research. These are exceptions that the University regulates to assure that considerations of intellectual property do not lead to

9 | P a g e

restrictions that are inconsistent with the University’s expectation of making findings/creations accessible to the scholarly community and general public.

10. IF A DISPUTE ARISES WITH RESPECT TO INTELLECTUAL PROPERTY WHERE DO I GO FOR HELP?

Disputes about an individual’s contribution to the research or scholarly activity can arise

whenever people work together. An attempt should be made to resolve the matter by reasonable discussion among those involved that is informed by the relevant University policies and practices (see Integrity in Research, Academic Integrity and the School of Graduate Studies  Academic Integrity Policy. If you have questions or concerns you should consult with your department or faculty office, as well as PARTEQ for legal definitions of inventorship, invention, etc..

10 | P a g e

nInstitute

www.KirwanInstitute.osu.edu

Foretelling the Future

A Critical Perspective on the Use of Predictive

Analytics in Child Welfare

By Kelly Capatosto, Research Associate

KIRWAN INSTITUTE RESEARCH REPORT | FEBRUARY 2017

Introduction

We are living in the era of Big Data. Our current ability to amass huge data sets combined with innovative methods of analysis has led to an unprecedented push toward the use of analytic tools in both the public and private sector. One of the most recent developments in the world of Big Data is the use of predictive analyt-ics as a decision making tool, which has been described as a way to “predict the future using data from the past” (Davenport, 2014, p. 1). These predictions require analyses that sift through enormous sets of data in order to identify patterns. Although there is no standard method for the analysis, these predictions often rely on statistical algorithms and machine learning. Both the public and private sectors already employ predictive analytics to make key decisions in a variety of industries, including advertising, insurance, education, and, of particular interest, child welfare.

The field of child welfare has a long history of using risk analysis to guide institutional decision-making (Russell, 2015). Many in the field look toward predictive analytics as the next big innovation for understanding the risks associated with child maltreatment. Proponents of predictive analytics point to a variety of potential benefits, such as the ability to access hidden patterns, streamline service delivery, and decrease operation budgets. Beyond these benefits, the biggest push for predictive analytics use comes from the potential to prevent youth maltreatment before it occurs by identifying who is most likely to need care (Russell, 2015).

The Problem

While there has been a lot of enthusiasm surrounding predictive analytics and their possible benefit in the area of child welfare, others have begun to voice concerns regarding their use. As discussed in this white paper, there are reasons to be wary

The Ohio State University | Kirwan Institute for the Study of Race and Ethnicity | 33 West 11th Avenue, Columbus, Ohio 43201

Kirwan Institute Research Report | February 2017

of the widespread use of predictive analytics. The risk of perpetuating cognitive and structural biases is among them. While this white paper does not to condemn the use of predictive analytics, it does hope to promote a critical assessment of these tools and the emergence of other Big Data applications.

A Perspective on Predictive Analytics

that is Uniquely Kirwan

At the Kirwan Institute for the Study of Race and Ethnicity, our mission is to ensure that all people and communities have the opportunity to succeed. Through this work, the Institute developed a framework for analyzing inequity that considers both 1) cognitive and 2) structural barriers, defined below. In tandem, the operation of these barriers explains how inequity can persist in various institutions and systems, even in the absence of intentional prejudice or discrimination.

Cognitive Barriers: The role of individual-level

Structural Barriers: The influence of history on

thoughts and actions in maintaining structures of

policies, practices, and values that perpetuate

inequity.

inequity (Davies, Reece, Rogers, & Rudd).

Rather than focusing on explicit, intentional

Although our society has made efforts to address

discrimination, the Kirwan Institute highlights the

importance of implicit bias and other unconscious

racism, sexism, and other forms of discrimination, our nation’s institutions remain rooted in a legacy

psychological processes. Generally, implicit bias is understood as the automatically activated

of legally endorsed discrimination. For example,

redlining—which purposefully devalued homes

evaluations or stereotypes that affect individual’s

in minority neighborhoods by limiting access

understanding, actions, and decisions in an

to financing—was a common practice until the

unconscious manner (Staats, 2013). All humans exhibit implicit bias, and having these biases does

Fair Housing Act of 1968 was passed (Olinger, Capatosto, & McKay, 2016). The enduring harmful

not reflect the intent to cause harm.

impact of these practices is evident in the racial disparities found in the current housing landscape.

Thus, by considering both social forces—structural and cognitive, this white paper aims to do the following:

* Uplift concerns related to the use of predictive analytics in child welfare and other systems

* Examine concerns according to the inputs, outputs and application of predictive analytics

* Propose suggestions for the future of predictive analytics in child welfare

2

Kirwan Institute Research Report | February 2017

Concerns Related to the Use of Predictive Analytics in the Child Welfare System

Models of predictive analytics proceed in three stages. First, data goes into the model. Second, the model, with algorithms and/or statistical analyses, creates an output. Finally, individuals apply the model’s outputs to decision-making at the field level. The following analysis critically examines concerns at each stage of this process—the inputs, outputs, and application of these models—regarding cognitive and structural factors that could be at play.

Inputs

Cognitive: Humans Encode Cognitive Biases into Machines

“Our own values and desires influence our choices, from the data we choose to collect to the questions we ask. Models are opinions embedded in mathematics.”

– Cathy O’Neil, Weapons of Math Destruction, 2016

All humans rely on a variety of automatic mental processes to make sense of the world around us. One example of these processes is the operation of implicit biases. People are typically unaware of the implicit biases they possess, and these biases often do not align with one’s explicit intentions to be egalitarian (Greenwald & Krieger, 2006; Nosek & Hansen, 2008). As such, all people make decisions that unintentionally rely on faulty or biased information. These decisions can have huge ramifications for our ability to safeguard opportunities for individuals of various genders, races, and ability statuses. To illustrate, one study demonstrated that resumes with White sounding names were nearly 50% more likely to get a call back than resumes with Black sounding names, despite controlling for all other factors, including work experience (Bertrand & Mullainathan, 2004).

As research continues to demonstrate how human bias can disrupt attempts to achieve equity, many have looked to the use of technology to ensure that decisions are made more objectively. Predictive analytics, like other data-based decision-making tools, have received considerable support for their potential to combat biases and provide opportunities for marginalized groups (Federal Trade Commission, 2016). However, human beings encode our values, beliefs, and biases into these analytic tools by determining what data is used and for what purpose. The data that institutions choose to use reveal what variables and reporting mechanism are valued most.

The advancement in technology has certainly improved the ability of child welfare systems to harness data to prevent child abuse and neglect. Large-scale data collection and reporting have made it easier than ever to manage cases and communicate among child welfare agencies. Despite this overall progress, the quality and consistency of the data used within the child welfare system remains an area of concern (Russell, 2015). Much of the data that predictive analytics tools use are derived from field-level reports. These may include self-reports on a variety of so

3

Kirwan Institute Research Report | February 2017

cioemotional factors or clinician reports on a child’s background and intake experience (Commission to Eliminate Child Abuse and Neglect Fatalities, 2014). It is impossible to remove all subjectivity from personal reporting tools. Moreover, those who work in child welfare are often working in environments of high ambiguity, time constraints, and stress—all of which increase the likelihood of relying on implicit factors during decision-making (in general, see Mitchell, Banaji, & Nosek, 2003; Van Knippenberg, Dijksterhuis, & Vermeulen, 1999). As such, it is critical to acknowledge that human biases can limit the integrity of the data that informs predictive analytic models.

Structural: Previous Marginalization as a Predictor for Future Risk

“The math-powered applications powering the data economy were based on choices made by fallible human beings. Some of these choices were no doubt made with the best intentions. Nevertheless, many of these models encoded human prejudice, misunderstanding, and bias into the software systems that increasingly managed our lives.”

– Cathy O’Neil, Weapons of Math Destruction, 2016

The adage “garbage in, garbage out” never holds truer than in the field of predictive analytics. When determining the inputs for these analyses, it is almost impossible to avoid incorporating longstanding patterns of inequity that exist in our society. Yet it may be difficult to identify where these patterns originate. For example, some predictive models currently used in the child welfare system assign a numeric indicator of risk associated with youth outcomes. In some cases, this risk informs how likely the child is to be reunited with the family, or how resilient the child is (Russell, 2015; Sledjeski, Dierker, Brigham, & Breslin, 2008; Toche-Manley, Dietzen, Nankin, & Beigel, 2013). Builders of such models would almost certainly avoid overt, illegal discrimination such as reliance on data that linked a family’s race to the probability of child maltreatment or the assignment of a higher risk rating for racial minorities. However, because of past discrimination and historical inequities, subtle biases can emerge when seemingly “race neutral” data acts as a proxy for social categories. For example, data related to neighborhood characteristics are profoundly connected to historic practices of racial exclusion and discrimination. Thus personal information, such as one’s zip code or diet, are deeply connected to racial identity (Sen & Wasow, 2016). Data that is ostensibly used to rate risk to child well-being can serve as a proxy for race or other past oppression, thereby over-representing those who have suffered from past marginalization as more risky. In this way, poor and marginalized communities are often disproportionately penalized by rating systems, even if the data feeding into these models would take considerable—perhaps, unreasonable—time and effort to alter, such as changing one’s credit score or zip code (O’Neil, 2016).

Even more troubling is the omission of information for youth who do not enter the child welfare system as a counterbalance for these predictions of risk. It is impossible to know how many children who are never maltreated and whom would not properly be assessed as “high-risk” for maltreatment under these factors. This type

4

Kirwan Institute Research Report | February 2017

of control group data simply does not (and should not) exist. Thus, it is important to acknowledge that the assumptions often built into data analytic models predict maltreatment with incomplete data.

Outputs

Cognitive: Overconfidence in the Objectivity of Outputs

“Data and data sets are not objective; they are creations of human design. We give numbers their voice, draw inferences from them, and define their meaning through our interpretations. Hidden biases in both the collection and analysis stages present considerable risks, and are as important to the big-data equation as the numbers themselves”

– Kate Crawford, The Hidden Biases in Big Data, 2016

The allure of predictive analytics is their potential for identifying and correcting for human biases that may arise during important child welfare decisions by lessening reliance on individual judgments. However, algorithms alone are no panacea to subjectivity. As discussed earlier, these models can unintentionally encode the same biases reflected in our society. Thus, one of the most serious dangers of predictive analytics is our overconfidence in the objectivity of their outputs.

When tools rely on vast quantities of data and complex analyses, it can be difficult or even impossible to be aware of the cognitive mechanisms influencing a model’s predictions. For example, if field workers are required to enter a particular score related to a child’s recidivism into the foster care system, it is highly unlikely that they will have the opportunity or authority to question the objectivity of that score at a later date, or exercise the discretion to make an exception to the score. For this reason, it can be very difficult to retroactively identify or correct instances where these seemingly objective outputs act as a gatekeeping mecha-nism—steering children and families toward service options that are not a suitable match for their individual needs.

Structural: Predictive Analytics Can Perpetuate Existing Structural Disparities

“The creators of these new models confuse correlation with causation. They punish the poor, and especially racial and ethnic minorities. And they back up their analysis with reams of statistics, which give them the studied air of evenhanded science.”

– Cathy O’Neil, Weapons of Math Destruction, 2016

Beyond relying on data inputs that reflect existing biases, predictive analytics may also exacerbate these structures of inequity through their outputs. For example, the tendency for algorithms to “digitally redline,” sometimes referred to as “we-blining,” garnered significant attention from the federal government in the 2014 Big Data report (Executive Office of the President, 2014, p. 53). In the same way that ubiquitous redlining practices restricted loans and devalued homes in minority neighborhoods, weblining occurs when public and private institutions

5

Kirwan Institute Research Report | February 2017

use opaque scoring algorithms to restrict communication and services to certain groups of people.

In the private sector, this most often occurs in the form of targeted advertising— matching consumers with products that the data reveals are most relevant to them. This matching process can involve various practices such as tracking consumers’ purchase history or grouping consumers with similar attributes in order to offer goods and services that most likely match that population. Although largely viewed as a beneficial use of predictive analytics, targeted marketing has produced instances of racial discrimination. In one example, a test preparation program’s marketing algorithm offered different pricing among geographic regions, which resulted in Asian families being subjected to higher prices (Angwin, Mattu, & Larson, 2015). In another, search engine searches for Black-sounding names were more likely to reveal advertisements offering arrest records than searches with White-sounding names (Sweeney, 2013). Importantly, no one intended for these algorithms to produce discriminatory outputs. Instead, as discussed above, these search processes learned the biases from user patterns, and then played a role in perpetuating these biases through consumer behavior.

A highly controversial example of predictive analytics playing out in the public sector is targeted policing (Executive Office of the President, 2014). While some applaud the use of predictive models for focusing limited resources on high crime areas, the practice has been criticized for justifying an outsized police presence in poor neighborhoods with large minority populations (For a general overview, see joint statement on predictive policing: American Civil Liberties Union, 2016). Some predictive policing efforts have gone so far as to form lists and engage in active surveillance of those deemed most likely to commit a crime (Executive Office of the President, 2014). Individual-level predictions such as these are more likely to target people for who they are (race, proximity to crime, class, education level, etc....) rather than on the basis of observable behavior (O’Neil, 2016).

Predictive analytics tools in child welfare can operate the same way as the predictive policing scenario—by classifying individuals and families based on individual risk profiles for maltreatment. To illustrate, one predictive analytic tool utilized data from youth self-reports to determine the variables most related to youth resiliency. Youth received a resilience score based on 11 indicators in order to assist service workers in developing their treatment goals (Toche-Manley et al., 2013). Even though the identification of these risk factors is empirically valid, research has yet to show the link between these resiliency scores and treatment outcomes. Thus, this type of scoring may have the potential to impose a punitive system of gatekeeping on less-resilient youth who are denied opportunities more resilient youth are routinely offered. This is just one example of predictive analytics efforts, though research-based, that may not generalize into effective field use. Moreover, if tools such as these do get utilized in the field, their application may actually perpetuate existing structural disparities by restricting necessary services to certain families or neighborhoods.

6

Kirwan Institute Research Report | February 2017

How Predictive Analytics Impact Decisions in Child Welfare

The prior sections of this paper addressed what these models encode and produce. This final section will discuss the importance of how these tools can influence decision-making in child welfare systems that reproduce inequity. Predictive analyt-ics are already governing real-world decision-making across many social services fields; many of these decisions literally involve life and death. Although the Kirwan Institute strongly supports the use of data and empirical research to inform organizational behavior, it is essential to remain cautious to the potential drawbacks of how predictive analytics are applied.

First, when relying on predictive analytic models, users can fall into the common trap of confusing correlation with causation. For example, one analysis conducted in New Zealand analyzed all maltreatment cases for five-year-olds and discovered that 83% had been enrolled in the public benefit system before they were two; they concluded that the receipt of public benefits predicted future child maltreatment (Vaithianathan, Maloney, et al., 2013, p. 354). Similarly, other studies have concluded that prior experience with child protective services (CPS) was the best predictor of recurrent maltreatment (DePanfilis & Zuravin, 1999; Fluke, Shuster-man, Hollinshead, & Yuan, 2008; Sledjeski et al., 2008). While this information is empirically valid and instructive for understanding the recurrent nature of child welfare involvement, it does not provide information on the circumstances that determined the families’ need for these services. Moreover, these analyses cannot conclude why youth who a) received public benefits or had CPS contact and b) did not experience maltreatment, fared better than some of their peers. These findings illustrate a classic example of the adage that correlation does not equal causation; public benefits and CPS involvement acted as confounding variables because both were highly correlated to later child maltreatment, but were not the underlying cause. In this case, the lack of a causal relationship between these risk factors and the outcome of maltreatment should seem apparent. However, other variables identified by these models are not held to the same standard of scrutiny; many of these so-called risk factors are then targeted as a potential point of intervention without ever knowing whether they contribute to outcomes in any meaningful way. Equally troublesome is the possibility that these models will comb through vast quantities of data only to reveal what the child welfare system has known for decades—poverty and lack of opportunity are detrimental to families. For example, if a predicative analytics model reveals a risk factor: R, it is necessary to evaluate whether R is truly the source of maltreatment: M (i.e. R ??> M), or if R is just another product of an underlying variable, such as poverty: P (i.e. P ??> R & M).

Child welfare systems have a clear obligation to invest in the most effective methods for mitigating the risk of youth maltreatment. Thus, it is necessary to take a deeper look into the process by which predicative analytic models inform decision-making, especially if they take the place of other decision-making tools (e.g. experimental research literature, staff surveys, etc.) to determine families’

7

Kirwan Institute Research Report | February 2017

access to benefits that exist to promote child well-being. In short, while predictive analytics can help identify important intervention points and patterns of targeted need, it may prove difficult (or even potentially impossible) to reap the full benefits of predictive analytics without first addressing systemic factors such as poverty and discrimination. For these reasons, this paper closes by recommending ways to utilize predictive analytics within the context of a historically informed framework for understanding social inequities.

Suggestions for the Future of Predictive Analytics in Child Welfare

Although this paper casts a wary eye on predictive analytics, these Big Data tools still have much to offer the field of child welfare. They can reveal patterns of social disparities, and help determine the most effective use of limited public and private resources. Nevertheless, it is important to be aware that longstanding and deeply embedded systemic and cognitive inequities can limit the effectiveness of data analytic tools and the conclusions they reach. Thus, when institutions utilize Big Data tools they should be conscious of how the models interact with pre-existing structures of and barriers to opportunity. Thus, the following recommendations are not directed toward reforming predictive analytics in general. Instead, these suggestions focus on ways to help safeguard child welfare agencies and the populations they serve from the misuse of predictive analytic tools.

Develop a Code of Ethics

Among other impacts, predictive analytics use have immense social, legal, and financial ramifications. As such, it may prove beneficial to develop a comprehensive code of ethics to help guide how the field uses predictive analytics and other Big Data applications. Child welfare systems involve a wide range of actors with varying expertise. Thus, to ensure that multiple perspectives weigh in on the ethical considerations of predictive analytics, an interdisciplinary committee or task force should be formed. Examples of potential representatives include human services employees, computer scientists, and social science researchers (For table on potential interdisciplinary connections for Big Data projects, see Staab, Stalla-Bour-dillon, & Carmichael, 2016, pp. 24-25). Moreover, the implementation of child welfare services often involves multiple levels of governance. Thus, to ensure the consistency of ethical standards, the committee should focus on general guidelines at the state and national level, while also representing local interests and concerns whenever possible.

Increase Accountability

“Black box” algorithms are characteristically difficult to understand; the inputs and outputs are observable but the internal processes are ambiguous and complex (Staab et al., 2016, p. 7). Predictive analytics tools that utilize black box algorithms have the potential to restrict transparency and accountability in decision-making.

8

Kirwan Institute Research Report | February 2017

If families are denied services or interventions based on a predictive analytics algorithm, they should be able to understand what factors contributed to that outcome and have a recourse for disputing that decision—especially as these decisions are so vital for determining outcomes for families and children in need. Additionally, if child welfare agencies are unsure of how these algorithms operate, they may find themselves in vicious loop where those working on the ground are unable to provide the appropriate feedback to help these models improve and adapt.

Assess Equity Impact

As part of a comprehensive effort to address disparities in child welfare, predictive analytic models should undergo an evaluation to gauge their equity impact. Simply identifying accurate predictive factors and using these factors to make decisions about service delivery does not guarantee the interventions will be implemented equitably. As such, those who determine the benefits of predictive analyt-ics should be trained to look for existing structures of inequity that may limit the effectiveness of the resulting interventions. For example, racial groups have different experiences when encountering health and social services professionals. Research demonstrates that practitioners’ implicit racial biases may lead to different quality interactions and treatment decisions for Black and White patients (Green et al., 2007; Johnson, Roter, Powe, & Cooper, 2004; Penner et al., 2010). Awareness that practitioner bias can inhibit child welfare interventions should be factored into the operation of application of predictive analytics model.

Broaden the Scope

As the prior sections noted, individual-level risk predictions depends on a variety of factors, many of which are difficult or impossible to control (e.g. race, education, geography, and socioeconomic status). Thus, those who promote the use of predictive analytics in child welfare should consider broadening the scope to include neighborhood and citywide predictions. For example, tools like opportunity mapping can identify geographic regions that would benefit most from additional resources. By targeting neighborhoods for child welfare interventions rather than families alone, it is easier to combat the systemic sources of these risk factors such as poverty and lack of opportunity. Moreover, it is important to acknowledge that neighborhood-level and individual interventions are not in opposition to one another; addressing poverty for a whole community can bolster family-level efforts to promote child welfare. For example, a neighborhood-targeted approach may focus on preventative efforts (such as workforce development programs or a public health campaign to decrease teenage pregnancy), in addition to individual-level supports like therapeutic services for families. n

9

References

American Civil Liberties Union. (2016). Statement of concern about predictive policing by ACLU and 16 civil rights privacy, racial justice, and technology organizations. Retrived from https://www.aclu.org/ other/statement-concern-about-predictive-polic-ing-aclu-and-16-civil-rights-privacy-racial-justice

Angwin, J., Mattu, S., & Larson, J. (2015). The tiger mom tax: Asians are nearly twice as likely to get a higher price from Princeton Review. Retrived from https:// www.propublica.org/article/asians-nearly-twice-as-likely-to-get-higher-price-from-princeton-review

Bertrand, M., & Mullainathan, S. (2004). Are Emily and Greg more employable than Lakisha and Jamal? A field experiment on labor market discrimination. The American Economic Review, 94(4), 991–1013.

Commission to Eliminate Child Abuse and Neglect Fatalities. (2014). The dissenting report of the honorable Judge Patricia M. Martin CECANF commissioner. Retrieved from http://nccpr.org/reports/ JudgeMartinDissent.pdf.

Crawford, K. (2013). The hidden biases in Big Data. Harvard Business Review. Retrieved from https:// hbr.org/2013/04/the-hidden-biases-in-big-data.

Davenport, T. H. (2014). A predictive analytics primer. Harvard Business Review. Retrieved from https:// hbr.org/2014/09/a-predictive-analytics-primer .

Davies, S., Reece, J., Rogers, C., & Rudd, T. (n.d.) Structural racialization: A systems approach to understanding the causes and consequences of racial inequity. The Kirwan Institute. Retrieved from http://kirwaninstitute.osu.edu/docs/NewSR-bro-chure-FINAL.pdf

DePanfilis, D., & Zuravin, S. J. (1999). Predicting child maltreatment recurrences during treatment. Child Abuse & Neglect, 23(8), 729–743.

Executive Office of the President. (2014). Big data: Seizing opportunities, preserving values. The White House. Retrieved from https://www.white-house.gov/sites/default/files/docs/big_data_ privacy_report_5.1.14_final_print.pdf.

Ramirez, E., Brill, J., Ohlhausen, M.K., & McSweeny, T. (2016). Big Data: A tool for inclusion or exclusion. Federal Trade Commission. Retrieved from https://www.ftc.gov/system/files/documents/ reports/big-data-tool-inclusion-or-exclusion-un-derstanding-issues/160106big-data-rpt.pdf.

Fluke, J. D., Shusterman, G. R., Hollinshead, D. M., & Yuan, Y.-Y. T. (2008). Longitudinal analysis of repeated child abuse reporting and victimization: Multistate analysis of associated factors. Child Maltreatment, 13(1), 76–88.

Green, A. R., Carney, D. R., Pallin, D. J., Ngo, L. H., Raymond, K. L., Iezzoni, L. I., & Banaji, M. R. (2007). Implicit bias among physicians and its prediction of thrombolysis decisions for Black and White patients. Journal of General Internal Medicine, 22(9), 1231–1238.

Greenwald, A. G., & Krieger, L. H. (2006). Implicit bias: Scientific foundations. California Law Review, 94(4), 945–967.

Johnson, R. L., Roter, D., Powe, N. R., & Cooper, L. A. (2004). Patient race/ethnicity and quality of patient-physician communication during medical visits. American Journal of Public Health, 94(12), 2084–2090.

Mitchell, J. P., Banaji, M. R., & Nosek, B. A. (2003). Contextual variations in implicit evaluation. Journal of Ex-perimental Psychology: General, 132(3), 455–469.

Nosek, B. A., & Hansen, J. J. (2008). The associations in our heads belong to us: Searching for attitudes and knowledge in implicit evaluation. Cognition and Emotion, 22(4), 553–594.

O’Neil, C. (2016). Weapons of Math Destruction: How Big Data Increases Inequality and Threatens Democracy. New York: Crown Publishers.

Olinger, J., Capatosto, K., & McKay, M. A. (2016). Challenging race as risk: Implicit bias in housing. The Kirwan Insitute. Retrieved from http://kirwanin-stitute.osu.edu/my-product/challenging-race-as-risk-implicit-bias-in-housing/.

Penner, L. A., Dovidio, J. F., West, T. V., Gaertner, S. L., Albrecht, T. L., Dailey, R. K., & Markova, T. (2010). Aversive racism and medical interactions with Black patients: A field study. Journal of Experimental Social Psychology, 46(2), 436–440.

Russell, J. (2015). Predictive analytics and child protection: Constraints and opportunities. Child Abuse and Neglect, 46, 182–189.

Sen, M., & Wasow, O. (2016). Race as a bundle of sticks: Designs that estimate effects of seemingly immutable characteristics. Annual Review of Political Science, 19, 499–522.

Sledjeski, E. M., Dierker, L. C., Brigham, R., & Breslin, E. (2008). The use of risk assessment to predict recurrent maltreatment: A classification and regression tree analysis (CART). Prevention Science, 9(1), 28–37.

Staab, S., Stalla-Bourdillon, S., & Carmichael, L. (2016). Part I: Observing and recommending from a social web with biases. Web Science Institute. Retrieved from https://arxiv.org/ftp/arxiv/ papers/1604/1604.07180.pdf.

Staats, C. (2013). State of the science: Implicit bias review. The Kirwan Institute. Retrieved from http://www. kirwaninstitute.osu.edu/reports/2013/03_2013_ SOTS-Implicit_Bias.pdf.

Sweeney, L. (2013). Discrimination in online ad delivery. Queue, 11(3), 10.

Toche-Manley, L. L., Dietzen, L., Nankin, J., & Beigel, A. (2013). Revolutionizing child welfare with outcomes management. The Journal of Behavioral Health Services & Research, 40(3), 317–329.

Van Knippenberg, Dijksterhuis, A., & Vermeulen, D. (1999). Judgement and memory of a criminal act: The effects of stereotypes and cognitive load. European Journal of Social Psychology, 29(2), 191–201.

This publication was produced by the Kirwan Institute for the Study of Race and Ethnicity at The Ohio State University. As a university-wide, interdisciplinary research institute, the Kirwan Institute works to deepen understanding of the causes of—and solutions to—racial and ethnic disparities worldwide and to bring about a society that is fair and just for all people.

Kirwan Institute research is designed to be actively used to solve problems in society. Its research and staff expertise are shared through an extensive network of colleagues and partners—ranging from other researchers, grassroots social justice advocates, policymakers, and community leaders nationally and globally, who can quickly put ideas into action.

For More Information

The Kirwan Institute for the Study of Race and Ethnicity at The Ohio State University is known and respected nationally and deeply engaged in social issues. We are focused on projects that are integrated with sound research, strategic communication, and advocacy. To learn more, visit www.kirwaninstitute.osu.edu.

1

The PR-2X Owner’s Manual

By Michael Landgraf for Mind Gear, Inc.

Medical Disclaimer

   "Light / Sound Systems" or "Mind Machines" have been on the market for years. Thousands of users have experienced many hours on them with virtually no reported ill effects. But there are some situations and conditions where use of our products is strongly discouraged. These devices create flickering light, which can cause seizures in persons with photosensitive epilepsy. You may be photosensitive and not know it.

Even if you have never had a seizure, there is a small chance that you are photosensitive, and

exposure to flashing lights can cause YOU to have a seizure. If you are not willing to accept this

risk, please do not use Mind Gear L/S systems.

   Mind Gear products are designed for recreational purposes and personal exploration ONLY. No medical claims are made for Mind Gear products, express or implied. They are NOT medical devices and should not be used for the relief of any medical condition. Please consult with your licensed medical practitioner prior to use for any other purpose as the machine is not intended as a replacement for medical or psychological treatment. Our products are not intended to affect the structure or any function of the human body. These products are not approved for any purpose by the FDA.

   If you or anyone else who will use this machine are subject to any form of seizures, epilepsy or visual photosensitivity, are using a pacemaker, suffering cardiac arrhythmia or other heart disorders, currently taking stimulants, tranquilizers or psychotropic medication, specifically including illicit drugs and alcohol, please do not use our or any other Light / Sound system.

   Your experience should feel pleasant and we recommend that you set the volume and light intensity levels with your EYES CLOSED before you or anyone you loan your system to, uses it.

Photosensitive Epilepsy

   Photosensitive Epilepsy is a relatively rare condition, affecting approximately 1 person in 4000. Persons with this condition are susceptible to seizures evoked by flickering lights, such as those produced by a light / sound machine. The information included here on photosensitive epilepsy is mostly from the book "Photosensitive Epilepsy".

   Most persons with photosensitive epilepsy have a first seizure during their teenage years (75% by age 20). About half of initial seizures are induced by watching television. Some persons who are susceptible during their teenage years outgrow the condition, about 25% by age 25. As a result, adults over age 25 who have never had a seizure have about 1 chance in 20,000 of being photosensitive and not know it. So for a person who has not had a seizure, the likelihood of being photosensitive varies from 1 in 4000 for children to 1 in 20,000 for adults over 25.

Remember, Even if you have never had a seizure, there is a small chance that you are photosensitive and a light / sound session could cause a seizure in YOU!.

By Michael Landgraf for Mind Gear, Inc.

Table of Contents

Medical Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

ProgramGuide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

PR-2X Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Introduction: Quick Starting Your PR-2X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Getting the most from your PR-2X system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Controls and Displays

Recharging the Battery

Playing a Program

TurboSonix ‘Plus’ Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Adjusting Stimulation Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Pausing a Program

Stopping a Program

Changing Stimulation Options

System Time-Outs

Stimulation Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Volume

Intensity

Tone

Frequency

Mode

Pitch

Program

Time

Advanced Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Personal Preference Program

Changing Program Run Time

Entering Custom Program

Programming Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 Utilizing Your TENcolor Lightframes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

OperationsSummary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Make Connections

View or Change Function Value

Running a Program

Entering a Personal Preference Program

Warranty. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Addendum. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Autopilot

Erasing all the Stored Programs

By Michael Landgraf for Mind Gear, Inc.

4

Program Time

Description Start

Target Freq.

Notes

P01

10

Quick Alpha relaxer 30

11

Relaxation

P02

15

Slow Ramp Alpha 15

8

Relaxation

P03

10

Magic 11 18

11

Relaxation

P04

20

Schumann's Alpha 19

11, 7.83

Relaxation

P05

30

Schumann Resonance 25

7.83

Relaxation

P06

30

High Stress Alpha 25

7.83, 5

For High Stress

P07

30

Low Stress Alpha 15

10, 7

For Low Stress

P08

10

Quick Fix 11

7

All in high Alpha

P09

15

Alpha Break 11

7

Lower Alpha

P10

30

Meditation Medicine 20

7, 5, 3

Theta meditation

P11

15

Quick Theta 15

7.83, 5

Meditation, dreaming

P12

15

Accelerated Learning 25

6, 10

Absorbing Information

P13

20

9 O'clock High 20

9

Relaxation, Energy

P14

20

Multi-Theta 18

7.83, 4

Different Theta Freq.

P15

30

Deep Theta 25

5, 3

Low Theta Range

P16

30

Relaxation, learning 15

5, 3

Meditation, Learning

P17

30

Intimate Theta/Delta 15

5, 3 2

Close to sleep

P18

30

Insomniacs Dream 11

1

Help in falling asleep

P19

50

Mind Expander 10

7.83, 6, 3, 1

Theta Freq. Near sleep

P20

25

Mental Gymnastics 25

Many

Mental Exercise enjoy

P21

10

Sharpening the mind 25

Many

Mental Exercise, varied

P22

22

Fire of the Mind 30

Many

High energy, good visuals

P23

60

Relaxed Creativity 18

5

Deep Relaxation

P24

20

Basic Brain Tune-up 15

11, 7.83, 5

Mental exercise.

P25

5

Demo 5

5

Demo. stim features

P26

23

The Balancer 35

1-40

Creativity

P27

40

Delta Force 18

4,1

Lucid dreaming

P28

20

Morning Glory 10

10,18

Waking up

P29

30

Magic 14 14

14

A.D.D.* Protocol

P30

30

Mind Massager 7.83

7 thru 15

Mental Tune-up

P31

30

Alpha Theta Train 12

5 thru 12

Creativity/Learning

P32

68

Power Nap 15

3 thru 6

Sleep/Learning

P33

35

Carnival Ride 2

Many

Energized creativity

P34

30

Creative Monster 16

8 thru 32

Energized

P35

30

Alpha Ramp 20

11,10, 9, 7.83

Relaxation

P36

30

Alpha Wave 20

11,10, 9, 7.83

Relaxation

P37

15

Coffee Break 18

8, 11

Relaxation

P38

20

Problem Solver 7.83

4,12, 7.83

Creativity

P39

30

Multi Theta 30

6, 5, 4, 3

Learning

P40

30

Theta Wave 20

5, 3

Meditation

P41

15

Tune-up 7.83

18, 4, 7.83

Mental Tune-up

P42

30

Deep Relaxation 12

7, 4, 3, 8

Relaxation

P43

30

Energized Learning 12

8, 5, 7, 10

Learning

P44

30

Meditation Machine 24

11, 9, 7, 5,3,1

Meditation

P45

30

Dreamy Delight 26

12,10,8,6,4,2,1

Sleep

P46

30

High Energy I 10

40, 36, 32, 30

Creativity

P47

36

High Energy II 16

10, 36,34,32

Creativity

P48

15

Quick Break 12

8,5, 8,10

Rejuvenation

P49

30

Relaxed Creativity 12

8, 5, 3, 1, 3, 5

Problem Solving

P50

20

Quick Learning 7.83

10, 7, 4, 7

Learning

AutoPilot Programs:

APS

30

AutoPilot Super Beta

30 to 40

High energy

APb

30

AutoPilot Beta

15 to 30

High energy

APA

30

AutoPilot Alpha

7 to 14

Alert, aware

APH

30

AutoPilot Theta

4 to 7

Meditative

APd

30

AutoPilot Delta

1 to 4

Sleep

By Michael Landgraf for Mind Gear, Inc.

PR-2X Features

AC Adapter Power Switch External Sound Source

Display Function Lights

Enter Key

Lightframe Port Headphone Port

Your Mind Gear PR-2X System comes complete with:

- PR-2X Unit featuring 50 built-in sessions.

- TENcolor Lightframes

- Stereo Headphones

- AC Adapter

- Stereo Patch Cord

- PR-2X Ultimate Owners Manual on CD

. . . including these Special Features:

- 1-40 Hz. Frequency Range.

- 10% - 90% Expanded Pulse Width Range.

- Soft-On & Soft-Off Ability.

- 5 Minute to 120 Minute Manipulation of Each Program Length.

- Ability to Display the Time Remaining in Every Program.

- Blending Feature to Smoothly Transition Between Different Modes with an ON / OFF Option.

- 5 AutoPilot Programs for Automatic Generation of New and Unique Programs with Storage Capability for Capturing and Saving Your Favorites.

By Michael Landgraf for Mind Gear, Inc.

Introduction

  Thank you for selecting the Personal Relaxer 2X (PR-2X). The PR-2X is the most sophisticated audio / visual mind stimulation devise available today, yet is straightforward, logical, and easy to learn.

  This manual will guide you through operation of your PR-2X system, from running built in programs to generating your own customized programs. Your PR-2X system offers a rich feature repertoire, and can be enjoyed at many different levels. Go just as far as you wish. The basic mind stimulation features are all available at the QUICK START level.

For a Quick Start:

Make connections:

- Headphones to the SOUND jack.

- Stimulation lightframes to the LIGHT jack.

- AC adapter to the PWR jack and to a wall outlet (if you don’t have a battery).

- External CD player to the EXT jack via the stereo cord.

- Turn Power On: Slide the power switch to BATT (or to ON if you are using the AC adapter).

NOTE: You may want to adjust VOLUME and / or INTENSITY. The PROGRAM light will turn on and the current program number (normal PO1) will be displayed. Select and Start Pro

gram:

- Select the program you want with the UP and DOWN keys.

- Suggestion: try P25 first, for demonstration of stimulation options.

- Press and release ENTER to start the program. The display will begin a 10 second countdown, sound and light stimulation will stop.

- Put on the headphones and lightframes, lean back and relax, CLOSE YOUR EYES. When the countdown ends, stimulation begins. When the program is over, stimulation stops, display shows End.

- Remove the lightframes and headphones.

- Press ENTER until the display goes blank (about 2 seconds), then release ENTER. The system will go back to manual control.

Good! You have used all the controls and experienced your first program.

By Michael Landgraf for Mind Gear, Inc.

Getting the most from your PR-2X system:

To receive the most benefit from your PR-2X system, follow these suggestions (also refer to the PR-2X 30 Day Learning / Relaxation Program file for more ideas):

1) Use it in conjunction with any self-improvement tape or a favorite piece of music.

2) Use the system 30-60 minutes every day for the first 30 days.

3) Set aside a specific time and place that you will use the system every day.

4) Wear comfortable clothing, avoid tight or restrictive garments.

5) You can become chilled during deep relaxation, and may want a blanket nearby.

6) Have a goal in mind; state it verbally as a problem to solve, an emotion to drain off, etc.

7) Draw a mental picture of the results you want to attain and keep focused on this goal.

8) Take several deep breaths just before beginning a session.

9) After a session take a minute to listen to the whispers, note any answers that appear.

10) As you try different programs and stimulation options, monitor your energy level, sleep patterns, and stress reactions. Find out what works best for you.

Controls and Displays:

Connect:

- Headphones to the SOUND jack.

- Stimulation lightframes to the LIGHT jack.

- AC adapter to the PWR jack and to a wall outlet (if you don’t want to run on battery).

- External CD player to the EXT jack via the stereo cord.

- The sliding power switch has two positions: ON (left) for running on internal battery or with the AC adapter; and OFF (right).

By Michael Landgraf for Mind Gear, Inc.

There are four keys on top of the unit:

- SELECT selects a function, and lights the corresponding function light.

- UP and DOWN (labeled with arrows) change the value of the selected function.

- ENTER has a variety of control functions (described in the appropriate section) The eight function lights show which function is selected. The three digit display shows the current value of the selected function.

Recharging the Battery:

  If your system has an internal battery, you can recharge it using the AC adapter. Whenever the AC adapter is connected, the battery is recharging. Recharging takes about 8 hours with the system running, and about 5 hours with the system turned off. You can recharge it overnight. To prolong battery life, recharge it before it is completely run down. Running down the battery will not lose internal memory of your personal preference settings or custom programs. Do not leave the AC adapter connected longer than overnight.

Playing a Program:

  When the system is turned on, the PROGRAM function is selected. If you have been using the system, another function may be selected:

- If PROGRAM is not selected, press ENTER or SELECT repeatedly, until it is.

- Use UP and DOWN to select the program you want.

- Lean back in a comfortable chair.

- Press and release ENTER to start the program. The display will begin a 10 second countdown, sound and light stimulation will stop.

- Put on the headphones and lightframes, CLOSE YOUR EYES. When the countdown ends, stimulation begins. Near the end of the program, stimulation will ramp down to off for a gentle termination. When the program is over, stimulation stops, and display shows _End÷.

- Remove the lightframes and headphones.

- Press ENTER until the display goes blank (about 2 seconds), then release ENTER. The system will go back to the manual control, and the manually selected stimulation will start.

By Michael Landgraf for Mind Gear, Inc.

TurboSonix Plus Instructions

To activate the TurboSonix capabilities of your PR2X system follow these simple guidelines:

1. Connect your CD player to your Mind Gear system by plugging one end of the stereo patch cord provided to the headphone jack of your CD player and the other end to the “EXT” jack of your Mind Gear system.

2. Turn on both units.

3. Press the DOWN key until the letters Cd appear in the display.

4. Press the ENTER key. The display will now change to Cd-.

5. You are now in the TurboSonix MODE.

6. Begin playing a specially encoded CD, put on the lightframes and headphones, sit back and enjoy!

7. To turn off the TurboSonix MODE simply press the ENTER key again. The display will once again show just the letters Cd without the hyphen.

   For best results you will need to adjust the volume level of the CD player so that the specially encoded light pulses on the CD will activate the lights of the lightframes.

NOTE: If the volume is turned up too loud, you may find that the lights will not turn off all the way. In this case, you will need to reduce the volume level of the CD player. You can also adjust the INTENSITY level of your Mind Gear system so that both the audio volume and the light intensity are at your preferred level.

When the TurboSonix function is activated, the system will no longer flash lights or produce any sounds by itself.

Adjusting Stimulation Levels:

   The sound volume and light intensity can be adjusted to your personal preference using the SELECT, UP, and DOWN keys at any time before or after starting a program. Be sure to adjust the light intensity with your eyes closed. You can record your preferences in a PERSONAL PREFERENCE PROGRAM so you won’t have to re-enter every time the system is turned on.

By Michael Landgraf for Mind Gear, Inc.

Pausing a Program:

  You can _stop the clock÷, or pause, the execution of a running program by pressing and releasing ENTER. The stimulation will continue in whatever state it was in when you paused it, but it will stop changing; the internal clock that advances the program state will stop and the right hand decimal point in the display will come on. When you are ready to continue the program, press and release ENTER again, and the clock will restart.

Stopping a Program:

  You can stop a program at any time by pressing and holding ENTER until the display goes blank (about 2 seconds). Release ENTER, and the system will go back to manual mode.

Changing Stimulation Options:

  Most built-in programs control only the frequency and phase of stimulation. Any function not controlled by the program can be set or changed manually in the same way as volume and intensity. You may want to experiment with the other stimulation functions to find which works best for you. You can record your selections in a PERSONAL PREFERENCE PROGRAM.

System Time-Outs:

The system automatically takes certain actions based on time:

- During a program, after ten seconds with no actions, FREQUENCY is reselected.

- After approximately eight minutes with no actions, the display is dimmed.

- After approximately two hours with no actions, the system stops operation and displays a single hyphen _÷. If you see this, move the power switch to off (center).

- The last two actions are designed to enhance battery life.

Stimulation Functions:

  There are ten functions in your PR-2X system that can be selected for display and control. One of the eight function’s lights is always on, telling which function is selected. Press SELECT to select a different function. The current value of the selected function is always shown in the display, and the UP and DOWN keys can normally change the value of the selected function. How do eight lights handle ten functions? Three functions are combined on one light (MODE). When MODE is selected, three separate functions (PHASE, DUTY CYCLE, and

By Michael Landgraf for Mind Gear, Inc.

RATE MULTIPLE) are displayed at the same time, one digit each, and three SELECT actions are required to get through MODE. The selected function is displayed brighter than others. As you press the SELECT key, some functions may be skipped. This is because the selections interact, and some selections for one function may make other functions inactive. Inactive functions are skipped as the light selection advances. The following paragraphs point out these interactions.

Volume:

   Ranges from 0-100. The VOLUME function controls the sound level in the headphones, but not the external sound source volume. Use your external sound source volume control to control external volume.

Intensity:

   Ranges from 0-100. The INTENSITY function controls the brightness of the lights in your stimulation lightframes.

Tone:

   The first three TONE selections are pulsed at a rate controlled by the FREQUENCY function.

   Binaural sound creates two continuous tones, separated in frequency by the selected FREQUENCY function value. The mind process sound in such a way that you seem to hear, and sometimes feel, the frequency differences or _beat frequency÷ of the two tones.

White noise is a mixture of many frequencies, with equal sound energy at each frequency.

   Pink noise is also a mixture of many frequencies, with equal sound energy in each octave (an octave is an interval that doubles in frequency, such as 220 Hertz to 440 Hertz.).

   Since there is a broader frequency range in higher tones available, the PR-2X system approximates true white and pink noise frequency generation. When white or pink noise is selected, the PITCH function is inactive.

Frequency:

   Ranges from 1.0-30.0 Hz.. The FREQUENCY function controls the rate of stimulation pulses in the lightframes and in the earphones in all TONE selections except binaural sound. When binaural sound is selected, it controls the difference, or beat frequency of the two tones.

By Michael Landgraf for Mind Gear, Inc.

This function controls the frequency of entrainment of brain waves.

   The frequency 7.83 Hz represents the amount of time required for light to circle the earth, and is referred to as the Schumann resonance. When a RATE MULTIPLE of 2 or 3 is selected, the FREQUENCY function is limited to 15 or 10 Hertz respectively. This is so the higher frequency will be limited to 30 Hertz.

Mode:

   When the MODE light is on, three different functions are displayed. The brightness of the three display digits is the one currently selected. Going from right to left, the functions are:

   Phase: The PHASE function controls the phasing of the stimulation to the four stimulation channels (right eye, left eye, right ear, left ear). If two stimulation channels are _on÷ at once, they are said to be in phase. If one is on while the other is off, they are out of phase or alternating. The various PHASE options provide stimulation phasing represented by the following:

   In FOCUS, all stimulations channels are on together and off together. In Right/Left, the left eye and ear are on together while the right eye and ear are off, then the right side is on while the left side is off, etc. When a RATE MULTIPLE of 2 or 3 is selected, FOCUS is not allowed because it groups all channels together, and has no _other÷ channels for the rate multiple. If FOCUS was selected when the RATE MULTIPLE selection is made, FOCUS is automatically changed to R/L.

   Duty Cycle: Ranges from 1,3,4,5,6,7. The DUTY CYCLE function controls the percentage of the total cycle time that stimulation is on. The default value 5 represents 50% on, 50% off. A DUTY CYCLE display of 4 means 40% on, 60% off; 3 means 30% on, 70% off, etc.

   Rate Multiple: Ranges from 1,2,2.,3,3. The RATE MULTIPLE function allows you to have some stimulation channels running at a multiple of the frequency of other channels. The default value of 1 means that all stimulation channels are the same rate (at the selected frequency). The value 2 means that the _on÷ channels in the PHASE display are running at twice the rate of the _off÷ channels. The rate multiple 2 means that the _off÷ stimulation channels in the PHASE display are running at twice the rate of the _on÷ channels. Similarly, 3 means a rate multiple of 3.

   The RATE MULTIPLE control interacts with the PHASE selection. When a RATE MULTIPLE other than 1 is selected, a PHASE selection of FOCUS is not allowed, and will automatically be changed to R/L (there are no _off÷ channels in FOCUS). Also, the maximum stimulation rate allowed is 30 Hertz, so when a RATE MULTIPLE of 2 is selected, the maximum FREQUENCY selection allowed is 15 Hertz (resulting in 30 Hertz in the _other channels÷), and when a RATE MULTIPLE of 3 is selected, the maximum FREQUENCY allowed is 10 Hertz. The system automatically makes these adjustments.

By Michael Landgraf for Mind Gear, Inc.

Pitch:

  Range of three octaves (36 notes) The pitch of the pulsed tone and binaural sound is controlled by the PITCH function. The PITCH selection is displayed as it’s piano keyboard name, with a period representing a sharp (half step above the named note), and a note number. The actual frequency range is from 92.5 Hertz (the second F sharp below middle C) to 689.47 Hertz (the second F above middle C). When the White or Pink noise tones are selected, PITCH is inactive.

Program:

  Ranges of PPP, E, PO1-P50. There are 50 built-in programs: PO1 thru P50. The E program selection allows you to Enter a program, and is discussed in ENTERING CUSTOM PROGRAMS. The PPP selection allows you to change the default values for all functions to custom selections of your own, and is discussed in PERSONAL PREFERENCE PROGRAM. The PROGRAM function is inactive while a program is running.

Time:

  The TIME function controls two separate parameters: 1. The running of time that a given stimulation state lasts, discussed in ENTERING CUSTOM PR0GRAMS, and 2. The length of time that a given stimulation state lasts, discussed in ENTERING CUSTOM PROGRAMS.

  The TIME function is not accessed in the normal cycling thru functions by the SELECT key. See the sections referenced above for the use of the TIME function.

Advanced Features:

CAUTION: The PERSONAL PREFERENCE PROGRAM and custom programs involve storing information in internal memory. Rapid on-off cycles (less than one second) do not allow the system time to reset properly, and may cause loss of information. Be careful of moving the PWR switch from BATT directly to ON, or vice versa, too quickly.

Personal Preference Program:

  All functions have built-in default values that are in effect until you change them. Some functions, particularly VOLUME and INTENSITY, can be distinctly personal and you may prefer some value other than the built-in value. To save you the inconvenience of setting your pre

By Michael Landgraf for Mind Gear, Inc.

ferred values each time the system is turned on, the PERSONAL PREFERENCE PROGRAM is provided.

   To store your own personal preferences, select the PROGRAM function, and press DOWN until PPP (Personal Preference Program) is displayed. Then press ENTER - the PROGRAM light will blink, indicating that you are now ready to enter information. Don’t worry about mistakes, they are easy to correct. Select each function in turn that you want to control, and select the default value that you want. For example, if you want to select Program 3, Volume 75, and Intensity 90, just manipulate SELECT, UP and DOWN until those functions display the values you want. You can cycle thru all the functions again with SELECT to be sure everything is the way you want it. Then press and hold ENTER until the display goes blank. Release ENTER, and your personal preferences will be recorded, and will come up whenever the system is turned on. After using the system for awhile, you may find that your preferences have changed. No problem! Just record the new values the same way.

Changing Program Run Time:

To run a program faster or slower than its normal time:

- Select the program you want, and press ENTER just as if you were going to run the program normally.

- During the 10 second countdown, press SELECT. The TIME function will be selected, and the normal running time of the program in minutes will be displayed.

- Use UP and DOWN to select shorter (down to 5 minutes) or longer (up to 60 minutes, with a maximum of 4 times the normal program time) running times.

* When the time you want is displayed, press SELECT again to continue the countdown. Entering Custom Programs:

   After experimenting with the built-in programs and the various stimulation options available, you may want to create your own stimulation programs. The PR-2X system provides for storage of 10 such custom programs at one time. You can always overwrite an old program with a new one, but you cannot store more than 10 at once. The custom program that you enter will be labeled in the PROGRAM function display. The program entry process is simple, but does not allow editing like a word processor. To change an incorrect entry, you must start over. For this reason, we suggest that you write down the sequence of stimulation states that you want your program to perform. A “program worksheet” for this purpose is provided. Make copies so you al ways have a blank original. To enter your custom program:

- Select the PROGRAM function. Press DOWN until E is displayed.

- Press and release ENTER. The display will shift to the next unused program number. Use

By Michael Landgraf for Mind Gear, Inc.

UP and DOWN to select the next available number. You cannot skip over unused program numbers. Select the program number that you want to enter, and press and release ENTER. The function light will blink, indicating that you are entering information. You are now ready to enter your custom program. Your custom program is a sequence of timed stimulation states, so repeat the following steps as often as required to enter all the states you have designed:

- Using SELECT, UP, and DOWN, set all functions to the values you want for your stimulation state. Use the stimulation lightframes and headphones to be sure you have things the way you want them. You can use SELECT to cycle through all functions and verify the displays. When everything is right, press and release ENTER. The TIME light will light.

- Use UP and DOWN to select the period of time you want your stimulation state to last. The minimum is 1 second, the maximum will be 20 minutes or less. Minutes are to the left of the decimal point, seconds to the right. When the time you want is displayed, press ENTER. Your stimulation states and its time will be recorded, and the FREQUENCY function will be automatically selected. The system is now ready for your next stimulation states. (repeat the step above).

- When all your stimulation states have been entered, press and hold ENTER until the display goes blank. Release ENTER. Your program is now stored, and can be run in the same way as a built-in program. PROGRAM ENTRY CAPACITY Each custom program can store 200 bytes of information. If you compose a long program with a lot of stimulation state changes, you may run out of memory. The system will automatically terminate program entry and return the system to the manual state if this happens the program as far as you entered it will be intact. To save space so the maximum number of stimulation states can be entered, note the following tips:

- When a stimulation states can be entered, every function that has changed in value is recorded. If you experiment with a function, changing its value, and then restore the original value, the system still treats this as a change and records the value. So be sure to change only the functions you want to change.

- Changes in FREQUENCY, PHASE, DUTY CYCLE, RATE MULTIPLE, and TONE takes one byte to record. Changes in PITCH, VOLUME, and INTENSITY take two bytes each. The time duration of a stimulation states takes one byte. There are approximately ten bytes of _ overhead÷ to get a program started and terminated correctly. The maximum time duration of a program is 60 minutes. When the time of a stimulation state is entered, the system will automatically limit your maximum choice to a value that approximately fills out the 60 minutes. If you reach the 60 minute limit, the program will automatically be terminated, just as it is for using up all the all the available memory.

NOTE: Print the following “PROGRAMMING WORKSHEET” from the CD file by the same name:

By Michael Landgraf for Mind Gear, Inc.

PROGRAM NAME:

PROGRAMMING WORKSHEET

PROGRAM NUMBER:

Time

Frequency

Mode

Pulse Width

Right Eye Rate

Pitch

Volume

Intensity

Tone

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

By Michael Landgraf for Mind Gear, Inc.

17

Utilizing Your TENcolor Lightframes

  TENcolors Lightframes are for personal light and sound users. TENcolors feature independent left eye / right eye color selection and connects directly to your PR-2X light and sound instrument.

  The TENcolors hues will vary somewhat depending upon whether you are using the AC adapter, running a session via the built-in battery and the amount of ‘charge’ left in the battery, but the general colors can be defined by the following chart:

TENcolors SWITCHES “ON”

PURE RED Red

ULTRA RED RED

ROSE QUARTZ RED, Green, Blue

YELLOW Red, Green

CALIFORNIA GOLD RED, Green

“WHITE” Red, Green, Blue

PURE GREEN Green

AQUA Green, Blue

PURE BLUE Blue

INDIGO Blue, RED

VIOLET Blue, Red

  Located on both the left and right sides of the TENcolors lightframes are four color selection switches. The right four switches control the right eye color and the left four control the left eye. When a switch is to the left (next to the numbers one through four) it is in the "OFF" mode. Likewise, when each switch is to the right (the side with ON printed on the top right of the switch) it is in the "ON" mode. To select the color you desire, simply refer to the color key above and set the color switch(es) accordingly. For example, for PURE BLUE switch number one “ON” in both switches while all other switches should be to the left or “OFF”. For INDIGO, switch one and three will be on, two and four will be off.

  Your TENcolors Warranty covers parts and labor for one year. Warranty void if: light-frames have been tampered with; have been subjected to negligent treatment or have been damaged due to spillage from drinks, water, etc.. Shipping costs are not covered or reimbursed under the warranty.

By Michael Landgraf for Mind Gear, Inc.

Operations Summary

Make Connections:

- Headphones to the SOUND jack, Goggles to the LIGHT jack.

- External audio source to the EXT jack with the stereo cord (optional).

- AC adapter to 120 volt wall outlet and PWR jack (optional if you have a battery).

- Power switch to BATT (or ON if using the AC adapter).

View or Change Function Value:

- Press SELECT repeatedly until the desired function is selected.

- Press (hold) UP, DOWN until the desired value is displayed.

Running a Program:

- Select the desired program with SELECT, UP DOWN.

- Get comfortable, put on the headphones and goggles.

- Press ENTER, CLOSE YOUR EYES.

- At End, press and hold ENTER till the display goes blank, release ENTER. PAUSING A PROGRAM

- Press and Release ENTER. To restart E ENTER. STOPPING A PROGRAM

- Press and hold ENTER until the display goes blank, release ENTER. CHANGING PROGRAM RUN TIME

- Select the desired program, press and release ENTER to start countdown. * During countdown, press SELECT. The normal program run time will be displayed.

- Use UP, DOWN, to select the desired run time, press and release SELECT.

Entering a Personal Preference Program:

- Select the PROGRAM function, DOWN to ppp, press and release ENTER.

- Set all functions to the desired values.

- Press and hold ENTER until the display goes blank, release ENTER.

By Michael Landgraf for Mind Gear, Inc.

Entering a Personal Preference Program:

- Select the PROGRAM function, DOWN to E, press and release ENTER.

- Use UP, DOWN to select the program to be entered, press and release ENTER.

- Set stimulation functions, press and release ENTER.

- Select time duration, press and release ENTER, repeat above step.

- When done, press and hold ENTER till the display goes blank, release ENTER.

WARRANTY

  We warrant to the original user that this product shall be free from all defects in material or workmanship for one year from the date of purchase. This warranty does not apply to any product subject to abuse, misuse, negligence or accident, nor does it apply to batteries supplied with the product. Defects caused by tampering, unauthorized alterations, or repairs are not covered by this warranty. We may elect to replace the entire unit at no extra cost to you with the same model or a similar model rather than repair it. If a defect covered by this warranty should occur, promptly return this product with proof of purchase, a check or money order for $ 5.00 to cover shipping and handling, and a brief explanation of the problem to the following address:

Mind Gear, Inc

Attn: Return Department

829 Callendar Blvd.

Painesville, Ohio 44077

  If the product should become defective after the warranty period, Mind Gear will limit the cost of repair to no more than $50 plus S&H if problem is determined to be due to a defect in material or workmanship. Once again, this limit does not apply to any product subject to abuse, misuse, negligence or accident, nor does it apply to batteries supplied with the product. Defects caused by tampering, unauthorized alterations, or repairs are not covered by this $50 repair limit.

  We learned through experience that problems in battery powered products are often due to weak batteries, rather than defects. To save inconvenience, we encourage you to try replacement batteries before you return the product. Please feel free to call our customer service representatives at 1-800-525-6463 or email MindGear@aol.com for answers to any questions. This warranty give you specific legal rights, and you may have other legal rights that vary from state to state.

By Michael Landgraf for Mind Gear, Inc.

Addendum

  Autopilot or AP for short, is a series of 5 programs that have been added to the original 50 programs found in the PR-2X system. Each AP program is assigned a category of brainwave frequencies. They are Super Beta (30-40 hertz), Beta (15-30 Hz ), Alpha (7-14 Hz), Theta (4-7 Hz), and Delta (1-5 Hz). Each time a particular AP program is run, the PR-2X system will generate a NEW & UNIQUE program targeted to the range specific to it!

  For example, each time an Alpha _AUTOPILOT TM÷ program is selected the system will automatically generate a new and unique program that will have target frequencies in the Alpha range. Furthermore, if you like and enjoy the program that the AUTOPILOT TM feature generates, you will have the option to save or _capture÷ the program (up to 10 different ones) when it is finished! This AP TM feature provides virtually an unlimited number of built-in programs and is only available from Mind Gear.

  Starting an _AUTOPILOT TM _ program: Beginning an _AUTOPILOT TM÷ program is exactly the same as running any other program. First you must determine which brainwave frequency range you wish to be stimulated at. Your choices are Super Beta, Beta, Alpha, Theta and Delta. Once you have made your decision, all you have to do is select the appropriate program and press the enter key.

  The _AUTOPILOT+÷ programs are located just below Program P01. Therefore, when you first turn your system on and it displays P01, you will need to press the down key until the appropriate _AUTOPILOT+÷ program is displayed. The options are displayed as follows: for Delta Frequency (1-4 Hz) programs the display will show Apd; for Theta Frequency (4-7 Hz) programs the display will show APH; for Alpha Frequency (7-14 Hz) programs the display will show APA; for Beta Frequency (15-30 Hz) programs the display will show Apb and for Super Beta Frequency (30-40 Hz) programs the display will show APS.

  Once you have the correct _AUTOPILOT+÷ program displayed, all you have to do is press the enter key and the system will begin the 10 second countdown just like any other program. Please note that all _AUTOPILOT+÷ programs are preset to run for 30 minutes. You can change the length of time on these programs just like any other.

  Saving an _AUTOPILOT+÷ program: After running an _AUTOPILOT+÷ program the PR-2X system will automatically assign a new program number and prompt you to decide if you wish to save the program that just finished under that number. If you wish to save the program for playback later, you MUST press the ENTER key FIRST before any other key and the program will be saved under the number that was flashing. If you first press any other key beside the ENTER key, the just completed program will be LOST and NOT SAVED!

NOTE: We suggest that you take the time to write down the program number and the type of program it is so you may refer to it later. Also, all user defined or _AUTOPILOT+÷ generated programs are displayed with the letter U (for user) preceding the program number. If you do not wish to save the _AUTOPILOT+÷ program, then simply hit the select key and the system will not save the program.

By Michael Landgraf for Mind Gear, Inc.

Erasing all the Stored Programs:

To erase all the stored custom programs follow these steps:

- Turn system on and use the down key until the letters ErA appear.

- Press the ENTER key - the system will now begin alternatively flashing all the indicator lights & the word ErA.

- Press the enter key again if you want to erase ALL the programs and the Personal Preferences.

- The System will now go totally blank for about 5 seconds and when done will display P01.

By Michael Landgraf for Mind Gear, Inc.

Project Implementation Plan

(PIP)

User Guide

FM0027-GDL-00034-E-V15

23 November 2007

Financial Mechanism Office, 12/16, Rue Joseph II, 1000 Brussels, Belgium . Tel: +32 (0)2 286 1701 . Fax: +32 (0)2 286 1789 . Email: fmo@efta.int . www.eeagrants.org

Page 2 of 20 FM 002 7-GDL-0003 4-E-V15

1 Introduction

The Project Implementation Plan (PIP) is a representation of the project in a structured format provided by the Financial Mechanism Office (FMO) and completed by the Project Promoter. The PIP is an annex to the Grant Agreement signed between the donors and the beneficiary state, therefore it constitutes a legally binding document.

Regardless the type of project assistance (i.e. individual project, programme or block grant), the same PIP format is to be used. In addition, there will always be one valid PIP per project even if the project is financed by both the EEA and Norwegian Financial Mechanism.

If there are modifications in the project during the implementation phase, and changes are above certain limits defined in the Terms and Conditions of the Grant Agreement, it triggers the submission of an updated PIP by the Project Promoter.

According to the Financial Mechanisms’ legal framework, the Project Implementation Plan (PIP) forms an integral part of the project planning and reporting structure, as the following diagram shows.

Figure 1: project planning and reporting structure

The completed PIP will serve as a baseline for monitoring the performance of a project in terms of its scope, schedule and budget. It means that project interim reports (including individual payment claims) as well as annual progress reports and the project completion report will be reported against the PIP.

Regarding the PIP completion procedure, the FMO will generate a tailor-made PIP template to each project and send it to the Project Promoter through the Focal Point. Certain key project parameters are necessary to the FMO in order to generate a tailor-made PIP. These parameters will be captured from the application form and during the project appraisal process, or if needed, will be requested from the Project Promoter in the same time when a grant is offered. The Project Promoter shall fill in the PIP and return it electronically to the Focal Point, who will forward it to the FMO. A printed hard copy does not need to follow the electronic version since the FMO will print a hard copy and attach it to the Grant Agreement which should be signed.

In case of modifications of the project during the implementation, the Project Promoter is responsible to notify the FMO through the Focal Point about changes, and especially indicating modified project parameters. In such cases the FMO will generate a new PIP template containing actual figures to date, and for future periods the PIP is to be filled in by the Promoter and returned to the FMO in the same way as the original PIP.

This user guide describes in details how to complete the PIP and specifies the information required in particular fields. Filling in correctly the PIP requires thorough project planning. Appendix 1 of the user guide describes an underlying project planning technique recommended by the FMO.

Financial Mechanism Office, 12/16, Rue Joseph II, 1000 Brussels, Belgium . Tel: +32 (0)2 286 1701 . Fax: +32 (0)2 286 1789 . Email: fmo@efta.int . www.eeagrants.org

Page 3 of 20 FM 002 7-GDL-0003 4-E-V15

2 How to complete the PIP

The PIP is a representation of a project plan in a format that is standard across all projects funded by the Financial Mechanisms. It is not a substitute for a detailed project plan prepared in accordance with relevant project stakeholders – such a plan is a prerequisite for completion of the PIP.

General form usage points:

- The PIP is a Microsoft Excel workbook. It is compatible with versions of this software from Excel 97 onwards, although the use of versions more recent that Excel 2000 is strongly recommended;

- The PIP contains no Excel macros;

- Editable cells are light blue in colour, all other cells are locked and not editable by the user;

- Do NOT use cut/paste to move data from one part of the form, as this disrupts the form’s

structure;

- Do NOT drag entire cells by selecting the periphery for the same reason;

- To copy data from another sheet / another place in the same sheet:

o copy the data from the source sheet (ctrl-C)

o select the destination cells, and use ‘Paste Special’ with the ‘Values’ checkbox selected. to paste the data:

Extending data from one cell to another by dragging the bottom right hand corner of the border is acceptable.

Selection of Activities for reporting

The first thing to decide when filling in the PIP is which activities will be used as a baseline. In every case the FMO insists that Project Management is treated as a separate activity.

The FMO does not require the lowest level to be used for reporting – the applicant can select about 10 activities across the project on which to report, as long as the sum of these activities results in the whole project. Small projects may not need as many as 10 activities, larger projects may need more. The FMO suggest keeping the number of activities at maximum 10.

Financial Mechanism Office, 12/16, Rue Joseph II, 1000 Brussels, Belgium . Tel: +32 (0)2 286 1701 . Fax: +32 (0)2 286 1789 . Email: fmo@efta.int . www.eeagrants.org

Page 4 of 20 FM 002 7-GDL-0003 4-E-V15

In Figure 2, the highlighted activities show a correct selection of activities for reporting:

Project Name

   Project Management

   

Major Activity

1

Major Activity

2

Project

Management

sub-activity 1

Project

Management

sub-activity 2

Sub-activity1

Sub-activity 2

Sub-activity 3

Sub-activity 4

Sub-activity 5

A

B

C

D

E

F

Figure 2: good selection of activities for reporting

The highlighted activities add up to the entire project.

Figure 3 shows an incorrect selection of activities for reporting:

A

B

C

D

E

F

Figure 3: bad selection of activities for reporting

The contribution of activities ‘sub-activity 2’ and ‘C’ is not reported on, whilst the contribution of activity ‘E’ is counted twice: in its own right and as part of activity ‘A’

Complete details of activities

For each activity, the following details need to be completed in part IV on worksheet ‘Breakdown’:

- Activity Name;

- Activity Scope Summary – a brief description of the objectives and outcomes of the activity;

- Planned Start Date – from the project schedule;

- Planned Completion Date – from the project schedule;

- Activity-specific expenses, for three month periods, falling into the types of expense listed in the

project budget in part II on worksheet ‘Summary’.

Plan a disbursement schedule

In part V on worksheet ‘Breakdown’:

Financial Mechanism Office, 12/16, Rue Joseph II, 1000 Brussels, Belgium . Tel: +32 (0)2 286 1701 . Fax: +32 (0)2 286 1789 . Email: fmo@efta.int . www.eeagrants.org

Page 5 of 20 FM 002 7-GDL-0003 4-E-V15

- Select the reporting periods;

- Verify that the amount to be disbursed is equal to the grant awarded by the Financial Mechanism Committee (FMC) / Norwegian Ministry of Foreign Affairs (NMFA) – i.e. check that fields [1.12] and [1.13] in part I on worksheet ‘Summary’ have the same value. If they do not, adjust the scheduling of the in-kind co-financing (for more details about scheduling of in-kind contributions please see an example in appendix 2).

Enter the expense categories

In part II on worksheet ‘Summary’:

- Once the activity budgets are in place, categorise the expenditure across all the activities,

according to the selected expense categories, and enter into Part II.

Note that this section is essentially an updated version of the data already provided in the Application form.

Enter details of project revenue

- If the project is revenue-generating, enter details of the annual revenue/ operating expense in the table on worksheet ‘Revenue’.

Check the form

- Verify that no cell on any worksheet is highlighted in red, and that all information provided is correct.

Financial Mechanism Office, 12/16, Rue Joseph II, 1000 Brussels, Belgium . Tel: +32 (0)2 286 1701 . Fax: +32 (0)2 286 1789 . Email: fmo@efta.int . www.eeagrants.org

Page 6 of 20 FM 002 7-GDL-0003 4-E-V15

3 Detailed description of PIP fields

This section describes the data in the PIP. This data comes from three sources: - entered by the Project Promoter

- gathered by the FMO as part of the application and FMO appraisal procedures - calculated to provide information to the Project Promoter

3.0 Project Promoter

This section of the PIP is provided for reference, and requires no input from the Project Promoter. If any of the details in this section are incorrect, then the Project Promoter should inform the Focal Point without delay.

[0.1] Full Legal Name

Populated with the information supplied in Application form associated with this PIP.

Contact information

[0.2] Contact Person

The name of the primary contact for the project. Whilst the vast majority of correspondence between the Promoter and the FMO will be via the Focal Point, any direct communication from the FMO to the Project Promoter will be addressed to this person.

[0.3] Job Title

The job title of the person named in [0.2]

[0.4] Organisation

The name of the organisation to which the person named in [0.2] belongs. In many cases this will be a department within the Promoter’s organisation named in [0.1], but may be a separate entity if the contact person is not part of that organisation.

[0.5] Address

The correspondence address for the person named in [0.2].

[0.6] Telephone

The fixed line telephone number for the person named in [0.2].

[0.7] Mobile

The mobile telephone number for the person named in [0.2].

[0.8] Fax

The fax number for the person named in [0.2].

[0.9] Email

The email address of the person named in [0.2].

3.1 Part I: Project Summary

This section of the PIP is provided for reference, and requires no input from the Project Promoter. It aims to provide an overview of the key project parameters, as well as quick reminders if the PIP has not been completed correctly.

3.1.1 General project data

[1.1] Project Title

The project title as defined in the Application form.

[1.2] Project Number

The project number assigned by the FMO on registration of the Application form. All correspondence relating to this project should reference this number.

Financial Mechanism Office, 12/16, Rue Joseph II, 1000 Brussels, Belgium . Tel: +32 (0)2 286 1701 . Fax: +32 (0)2 286 1789 . Email: fmo@efta.int . www.eeagrants.org

Page 7 of 20 FM 002 7-GDL-0003 4-E-V15

[1.3] 1 Euro =

The exchange rate between the Euro and the local currency of the Beneficiary State that was defined for the Open Call within which the Application form associated with this project was submitted. If the project did not have an open call, this will be the rate agreed between the FMO and the Focal Point.

[1.4] Final Eligibility Date

The date after which expenses associated with the project are deemed to be ineligible - as in the Grant Agreement Article 4 Clause 3.

[1.5] Deadline for final payment claim

The date by which all payment claims associated with the project must be submitted - as defined in the Rules & Procedures Article 3.1.3.

[1.6] Donor Commitment Date

The month in which respective Donors made a positive grant decision and awarded a grant. This date is specified with ‘month’ accuracy. The three month reporting intervals in Part IV Project Activities will start with the first month of the calendar quarter in which the Donors awarded a grant.

[1.7] Planned Completion Date

The month in which the FMO understands that the project will complete. This date is specified with ‘month’ accuracy, and must not be later than the date in [1.4].

3.1.2 Summary of overall project funding

This section has two columns:

- the left hand column repeats information in the Grant Agreement Article 2 referring to the overall project expenditure figures, and the extent to which the project is supported by the Financial Mechanisms

- the right hand column summarises information entered into the PIP

[1.8] Total cost: awarded by FMC / NMFA

The total cost of the project, as defined in the Grant Agreement based on the Application form and data collected during the project’s appraisal by the FMO. (Grant Agreement Article 2 Clause 3)

[1.9] Total cost: totals from this PIP

The total cost of the project, calculated from the expense breakdown in [2.3], [2.4] and [2.7]. [1.10] Total eligible cost: awarded by FMC / NMFA

The total eligible cost of the project, as defined in the Grant Agreement based on the Application form and data collected during the project’s appraisal by the FMO. (Grant Agreement Article 2 Clause 2)

[1.11] Total eligible cost: totals from this PIP

The total eligible cost of the project, calculated from the expense breakdown in [2.3] and [2.4]. [1.12] Total grant: awarded by FMC / NMFA

The total grant awarded under one or both mechanisms, as defined in the Grant Agreement based on the Application form and data collected during the project’s appraisal by the FMO. (Grant Agreement Article 2 Clause 1).

If the cell is highlighted in red then the project as described in the PIP is higher than in the Grant Agreement, please refer to [1.13].

[1.13] Total to be disbursed: totals from this PIP

The total amount to be disbursed calculated from Part V: Disbursement Plan (last column of [5.15]).

If the cell is highlighted in red then the project as described in the PIP is higher than in the Grant Agreement, i.e. the total to be disbursed is higher than total grant awarded by the FMC / NMFA ([5.15]). This difference must be solved, and it is likely that the cash eligible expenses entered into Part IV – Project Activities are too high. If the total to be disbursed is lower than total grant awarded by the FMC / NMFA an explanation must be given in the text box in point [1.15].

Financial Mechanism Office, 12/16, Rue Joseph II, 1000 Brussels, Belgium . Tel: +32 (0)2 286 1701 . Fax: +32 (0)2 286 1789 . Email: fmo@efta.int . www.eeagrants.org

Page 8 of 20 FM 002 7-GDL-0003 4-E-V15

[1.14] Grant Rate

The ratio of grant awarded by the FMC and/or NMFA to the eligible cost of the project, as defined in the Grant Agreement. (Grant Agreement Article 2 Clause 4)

[1.15] Explanation if total to be disbursed is less than total grant awarded

The total to be disbursed could be less than total grant awarded for several reasons, e.g. a complete reporting period till the end of the project has not been entered into the PIP ([5.9]) and/or cash eligible expenses entered into Part IV – Project Activities are lower than grant awarded. The latter needs an explanation and the reporting period need to be complete.

3.1.3 Summary of funding by Financial Mechanism

[1.16] Grant awarded – FMC

The total grant awarded by the EEA Financial Mechanism.

[1.17] Grant awarded – NMFA

The total grant awarded by the Norwegian Financial Mechanism.

[1.18] Partial Grant Rate – FMC

The ratio of the grant awarded by the EEA Financial Mechanism to the Total Eligible Cost of the project [1.19] Partial Grant Rate - NMFA

The ratio of the grant awarded by the Norwegian Financial Mechanism to the Total Eligible Cost of the project

3.2 Part II: Financial Breakdown

This section of the PIP elaborates on the financial data supplied in the application form.

Both the ‘Budget’ and ‘Financial Resources’ tables are structured in the same way:

- columns for expenditure / income per calendar year

- project total for the table row

- this row total as a percentage of another total. The individual row descriptions explain which figures are used to calculate this ratio.

3.2.1 Budget – incurred expenses

[2.1] Cash Eligible Expenses – Budget Headings

Planned eligible expenses across all project activities should be categorised according to the predefined expense categories (drop down menu) and/or up to four user-defined categories. These eligible expenses should be sorted by the calendar year in which they will be incurred, and entered into the appropriate field.

The ‘%’ column contains the ratio of the total for this expense category to the total cash outflow in [2.2].

[2.2] Total Cash Outflow

The total eligible expenditure per calendar year summed over all expense categories.

The figure in the ‘Total’ column is highlighted in red if the total from the eligible expense categories is not the same as the total cash eligible expense from activities in [2.3].

Total Eligible Expense Breakdown (from activities)

[2.3] Cash Eligible Expenses

The cash eligible expenses per calendar year derived from the data entered under the individual activities in Part IV.

Financial Mechanism Office, 12/16, Rue Joseph II, 1000 Brussels, Belgium . Tel: +32 (0)2 286 1701 . Fax: +32 (0)2 286 1789 . Email: fmo@efta.int . www.eeagrants.org

Page 9 of 20 FM 002 7-GDL-0003 4-E-V15

When the PIP is completed correctly, the total figure in this line should be identical to the total figure in [2.2].

The ‘%’ column displays the ratio of total cash eligible expenses to total eligible expense

[2.4] In-kind Eligible Expenses

The in-kind eligible expenses per calendar year, derived from the data entered under the individual activities in Part IV.

The ‘%’ column displays the ratio of total in-kind eligible expenses to total eligible expense.

[2.5] Total Eligible Expenses

The total of the cash [2.3] and in-kind [2.4] eligible expenses.

The ‘%’ column will always read ‘-’ or ‘100.00%’, depending on whether any expense figures have been entered under the activities in Part IV.

Total Project Cost Breakdown (from activities)

[2.6] Total Eligible Expenses The figures in [2.5] carried forward.

The ‘%’ column displays the ratio of eligible expenses to total project cost.

[2.7] Non-eligible Expenses

The non-eligible expenses per calendar year, derived from the data entered under the individual activities in Part IV.

The ‘%’ column displays the ratio of non eligible expenses to total project cost.

[2.8] Total Project Cost

The total of the eligible [2.6] and non-eligible [2.7] expenses.

The ‘%’ column will always read ‘-’ or ‘100.00%’, depending on whether any expense figures have been entered under the activities in Part IV.

3.2.2 Financial Resources – eligible expenses funding

The data in this section is derived from Part IV: Project Activities and Part V: Disbursement Plan. Its purpose is to provide an overview of the project funding, in particular which proportion of the funding comes from which source.

As the reimbursement takes place after expenses have been incurred, there is a time lag between expenditure and reimbursement which may mean that expenses incurred in one calendar year are reimbursed in the next.

Only financial resources that offset eligible expenses are considered – the funding of non-eligible expenses does not feature in the PIP.

Financial Mechanism Financing

[2.9] EEA Financial Mechanism

The grant awarded by the EEA Financial Mechanism per calendar year.

The ‘%’ column displays the ratio of EEA Financial Mechanism funding to total eligible expense funding in [2.20].

[2.10] Norwegian Financial Mechanism

The grant awarded by the Norwegian Financial Mechanism per calendar year.

Financial Mechanism Office, 12/16, Rue Joseph II, 1000 Brussels, Belgium . Tel: +32 (0)2 286 1701 . Fax: +32 (0)2 286 1789 . Email: fmo@efta.int . www.eeagrants.org

Page 10 of 20 FM 002 7-GDL-0003 4-E-V15

The ‘%’ column displays the ratio of Norwegian Financial Mechanism funding to total eligible expense funding in [2.20].

[2.11] Total

The total of [2.9] and [2.10].

The ‘%’ column displays the ratio of total Financial Mechanism funding to total eligible expense funding in [2.20].

Co-financing from central, regional or local government budget

[2.12] Cash co-financing

The cash that must be provided by a government body. This data is calculated from the Disbursement Plan.

The ‘%’ column displays the ratio of government cash co-financing to total eligible expense funding in [2.20].

[2.13] In-kind contribution

The total value of the in-kind contribution per calendar year provided by government bodies, derived from the data entered under the individual activities in [4.7].

The ‘%’ column displays the ratio of the value of government in-kind contribution to total eligible expense funding in [2.20].

[2.14] Total

The total of [2.12] and [2.13].

The ‘%’ column displays the ratio of the total of government cash co-financing and the value of government in-kind contribution to total eligible expense funding in [2.20].

Co-financing from non-government sources

[2.15] Cash co-financing

The cash that must be provided by non-government bodies.

The ‘%’ column displays the ratio of non-government cash co-financing to total eligible expense funding in [2.20].

[2.16] In-kind contribution

The total value of the in-kind contribution per calendar year provided by non-government bodies, derived from the data entered under the individual activities in [4.8].

The ‘%’ column displays the ratio of the value of non-government in-kind contribution to total eligible expense funding in [2.20].

[2.17] Total

The total of [2.15] and [2.16].

The ‘%’ column displays the ratio of the total of non-government cash co-financing and the value of non-government in-kind contribution to total eligible expense funding in [2.20].

Financial Resources Summary

[2.18] Total in-kind contribution The total of [2.13] and [2.16].

Financial Mechanism Office, 12/16, Rue Joseph II, 1000 Brussels, Belgium . Tel: +32 (0)2 286 1701 . Fax: +32 (0)2 286 1789 . Email: fmo@efta.int . www.eeagrants.org

Page 11 of 20 FM 002 7-GDL-0003 4-E-V15

The ‘%’ column displays the ratio of the value of the total in-kind contribution to total eligible expense funding in [2.20].

[2.19] Total cash

The total of [2.11], [2.12] and [2.15].

The ‘%’ column displays the ratio of the value of the total cash financing to total eligible expense funding in [2.20].

[2.20] Total in-kind contribution and cash

The total of [2.18] and [2.19].

The ‘%’ column will always read ‘100.00%’

3.3 Part III: Project Indicators

The project indicators define the scope of the project in terms of its objectives. Please refer to document http://europa.eu.int/comm/europeaid/qsm/documents/pcm_manual_2004_en.pdf for more details on the use of objectives.

The project indicators in the PIP are adapted by the FMO based on those proposed in the Application form, the results of the FMO’s appraisal process and a possible dialog with the Focal Point and/or the applicant. Additionally, indicators may be chosen in such a way that there is commonality across similar projects, enabling the benefit of such projects to be compared.

The Indicator column of the tables [3.2], [3.6], [3.10] should define a measurable parameter.

The Baseline column of the tables [3.3], [3.7], [3.11] represents the actual value of this parameter prior to starting the project.

The Target column of the tables [3.4], [3.8], [3.12] represents the intended value of this parameter when the project is successfully completed.

3.4 Part IV: Project Activities

The budget for project activities is established in three month intervals between the planned start date and planned completion date of the project. The three month reporting intervals will start with the first month of the calendar quarter in which the project execution will begin. Note that the interval for budgeting is independent of the interval for reporting defined in [5.8] and [5.9].

The PIP enables the entry of categorised activity-related expenses, and calculates a total for the activity for each category.

[4.1] Activity Number

The Project Promoter will provide the FMO with a figure for the number of activities against which the Project Promoter wishes to report progress during the FMO appraisal as described in the introduction to this document.

Each activity has a unique number.

[4.2] Activity Title

The title of the activity.

[4.3] Activity Description

A brief description of what is involved in the activity, to include as appropriate

- resources required for the activity

- dependencies on other activities

- risks associated with the activity

- description of any in-kind contribution associated with the activity

- description of any non-eligible expenses associated with the activity

Financial Mechanism Office, 12/16, Rue Joseph II, 1000 Brussels, Belgium . Tel: +32 (0)2 286 1701 . Fax: +32 (0)2 286 1789 . Email: fmo@efta.int . www.eeagrants.org

Page 12 of 20 FM 002 7-GDL-0003 4-E-V15

[4.4] Planned Start Date

The date on which the Promoter plans to start this activity.

[4.5] Planned Completion Date

The date by which the Promoter plans to have completed this activity.

[4.6] Cash eligible expenses

The budgeted cash eligible expenses that are uniquely associated with this activity.

[4.7] In-kind eligible expenses (central, regional, local government budget)

The budgeted value of any eligible in-kind contribution from government sources that is uniquely

associated with this activity.

[4.8] In-kind eligible expenses (non-government sources)

The budgeted value of any eligible in-kind contribution from non-government sources that is uniquely

associated with this activity.

[4.9] Non-eligible expenses

The budgeted cash non-eligible expenses associated with this activity.

[4.10] Total expenses

The total of [4.6], [4.7], [4.8] and [4.9].

3.5 Part V: Disbursement Plan

The PIP calculates the disbursements to be made by the Financial Mechanism(s) and the required co-finance based on:

- The project budget aggregated across the data entered for the individual activities in Part IV; - The reporting periods selected by the Promoter in [5.8] and [5.9].

The PIP calculates disbursements and co-financing amounts using the following criteria:

- At the end of the project, the actual grant rate must be less than or equal to that approved by the FMC / NMFA in [1.12];

- At no point during the project may the actual grant rate (the ratio of the cumulative disbursement to date to the cumulative eligible expense to date) exceed that approved by the FMC / NMFA in [1.12];

- An advance payment must be offset according to the mechanism defined in [5.6];

- Financial Mechanism funding representing the percentage of the planned total eligible expense defined in the Grant Agreement ([5.5]) will be retained from the last payment claim(s) and disbursed on approval of the Project Completion Report.

These criteria mean that for certain project budgets, it will not be possible to achieve the grant rate set out by the FMC / NMFA. Such budgets will typically involve significant in-kind contributions scheduled for late in the project. For a demonstration of this please refer to Appendix 2.

[5.1] Total advance payment

The advance payment approved by the FMC / NMFA defined in Grant Agreement.

[5.2] Brief description of source of cash co-financing from central, regional or local government

budget

Self-explanatory

[5.3] Brief description of source of cash co-financing from non-government sources Self-explanatory

[5.4] Percentage cash co-financing from non-government sources

The disbursement schedule calculates the amount of cash co-financing required to fulfil the criteria described above. The Promoter must specify which proportion of this co-financing will come from non-government sources.

Financial Mechanism Office, 12/16, Rue Joseph II, 1000 Brussels, Belgium . Tel: +32 (0)2 286 1701 . Fax: +32 (0)2 286 1789 . Email: fmo@efta.int . www.eeagrants.org

Page 13 of 20 FM 002 7-GDL-0003 4-E-V15

If the cell is highlighted in red then the source of co-financing in relation to the awarded grant rate is not in compliance with the Guide on Co-Financing Ceilings.

[5.5] Percentage of total eligible expenses to be disbursed on approval of Project Completion

Report (PCR)

The percentage set in the Grant Agreement.

[5.6] Advance offset mechanism

The mechanism defined in the Grant Agreement. This can take one of five values:

1. The whole advance is set off against the first payment claim

2. The advance is set off in equal proportions from the first payment claim until 80% of the grant has been spent

3. The whole advance is set off when 80% of the grant has been spent

4. Manual advance offset scheduling

5. Not Applicable

In the first three of these, the PIP calculates the offset for the advance, and adjusts the planned disbursement accordingly. The fourth enables a custom offset schedule to be entered, and the fifth is used if no advance payment is planned.

[5.7] PIR number

The PIP provides space for the maximum possible number of PIRs that could be submitted on the project, based on the minimum reporting period duration of three months. If the planned project duration is not a multiple of three months, then at least one period will need to be longer than three months.

It is not mandatory to use the maximum number of PIRs – the PIP enables reporting period durations of up to one year to be selected.

[5.8] Reporting period start month

The start month of the period on which a PIR reports. The start month of PIR #1 is always the planned start date of the project. The start month of PIR #<n+1> is always the month following the end month of PIR #<n>.

[5.9] Reporting period end month

The end month of the period on which a PIR reports. This is selected from a drop-down list, with the shortest reporting period being three months, and the longest being one year. If the end of the project falls within one year, then there may be empty spaces at the bottom of the list – the user will need to use the drop-down scroll bars to access the top of the list.

[5.10] Likely disbursement month

The month in which the FMO is likely to disburse funds claimed in this PIR. This is set to three months after the end of the reporting period, and assumes that the Promoter will submit the PIR to the Focal Point at the beginning of the month following the end of the reporting period. The date calculated in this field assumes that the information in the PIR is of a high enough quality to enable timely evaluation of the payment claim – if this is not the case the disbursement date is likely to be delayed.

[5.11] Advance offset

The amount of the advance to be offset in a reporting period. This includes both the offset against the Financial Mechanism(s) grant, and the cash co-financing.

This row is read-only, and the data is calculated by the PIP for all offset mechanisms other than ‘Manual advance offset scheduling’, in which case the user can enter the amounts to be offset in each reporting period.

[5.12] Disbursement

The amount that the Financial Mechanism(s) plan to disburse in a given reporting period.

Financial Mechanism Office, 12/16, Rue Joseph II, 1000 Brussels, Belgium . Tel: +32 (0)2 286 1701 . Fax: +32 (0)2 286 1789 . Email: fmo@efta.int . www.eeagrants.org

Page 14 of 20 FM002 7-GUL-0003 4-E-V15

[5.13] Cash co-financing from central, regional or local government budget

The co-finance that must be made available in a given period from government sources.

[5.14] Cash co-financing from non-government sources

The co-finance that must be made available in a given period from non-government sources. [5.15] Disbursement to date

The planned cumulative funding of the project by the Financial Mechanism(s) from the start of the project to date.

[5.16] Cash co-financing to date

The planned cumulative funding of the project by government and non-government sources of cash co-finance from the start of the project to date.

[5.17] In-kind contribution to date

The planned cumulative value of in-kind contributions from the start of the project to date. [5.18] Total funding to date

The planned total funding of eligible expenses from the start of the project to date (the total of [5.15], [5.16] and [5.17].

3.6 Part VI: Project Revenue

This section is identical to the ‘Revenues associated with the project’ section of the Application form – details of how to complete this can be found in the appropriate version of the ‘Application form User Guide’, available on www.eeagrants.org.

Financial Mechanism Office, 12/16, Rue Joseph II, 1000 Brussels, Belgium . Tel: +32 (0)2 286 1701 . Fax: +32 (0)2 286 1789 . Email: fmo@efta.int . www.eeagrants.org

Page 15 of 20 FM 002 7-GDL-0003 4-E-V15

Appendix 1 Recommended project planning techniques

The following diagram shows a simple project planning methodology. Note that the process is necessarily iterative – the more the project is investigated and analysed, the deeper the understanding of the issues achieved by the project manager.

The project management methodology described in this document is a very highly simplified version of that proposed by the Project Management Institute (PMI). This approach is described in detail in the PMBOK, published by PMI.

This document is intended to be an overview, and is in no way a substitute for project management training or experience.

Figure 4: project planning process

Financial Mechanism Office, 12/16, Rue Joseph II, 1000 Brussels, Belgium . Tel: +32 (0)2 286 1701 . Fax: +32 (0)2 286 1789 . Email: fmo@efta.int . www.eeagrants.org

Page 16 of 20 FM 002 7-GDL-0003 4-E-V15

1. Define Project Objectives

Before project planning can start, the overall objectives of the project need to be defined.

2. Create / Update Work Breakdown Structure (WBS)

The WBS is the most important document generated by the project planning process. It is a hierarchical description of the project’s scope, in terms of the activities required to achieve the high-level project objectives.

Effective use of a WBS can ensure that the project contains the activities required, and only the activities required to achieve these objectives

The WBS:

o Defines the activities to be performed by the project, where activities create measurable outcomes

o Is used as a basis for estimating project cost and duration

o Is used as a reference for measuring project progress

o Obliges project manager to think through the whole project

* What is to be provided

* How individual activities contribute to the whole

o Facilitates communication between project stakeholders

o Facilitates allocation of resources to activities

The WBS can be represented as a tree diagram, or as a list:

Project Name

Figure 5: example WBS tree

Financial Mechanism Office, 12/16, Rue Joseph II, 1000 Brussels, Belgium . Tel: +32 (0)2 286 1701 . Fax: +32 (0)2 286 1789 . Email: fmo@efta.int . www.eeagrants.org

Page 17 of 20 FM 002 7-GDL-0003 4-E-V15

Project Name

1.1 Project Management

1.1.1 Project management sub-activity 1

1.1.2 Project management sub-activity 2

1.2 Major Activity 1

1.2.1 Sub-activity 1

1.2.1.1 A

1.2.1.1.1 E

1.2.1.1.2 F

1.2.1.2 B

1.2.2 Sub-activity 2

1.2.3 Sub-activity 3

1.2.3.1 C

1.2.3.2 D

1.3 Major activity 2

1.3.1 Sub-activity 4

1.3.2 Sub-activity 5

Figure 6: example WBS list

The procedure for creating a WBS is as follows:

1. Define the major activities of the project, treating project management as a separate activity

2. For each activity:

a. Is it hard to estimate the cost or duration of the activity?

b. Is more than one individual or organisational unit responsible for completion of the activity?

c. Is this activity dependent on any other activities in the WBS?

d. Does the activity contain more than one type of work process?

e. Does the activity involve significant risk?

   f. Will it be difficult to measure the progress of the activity? If the answer to any of these is yes, then go to step 3, if no, go to step 4

3. Identify logical sub-activities of the activity. For each sub-activity perform step 2

4. Review the activity definition, and refine as necessary

Note that this procedure may be spread out over time, with more detail being added as the scope of the project becomes better understood. At each stage, the project manager should verify that the project objectives are achieved with the activities in the WBS

3. Identify Resources

For each activity at the lowest level of the WBS, identify the resources, both in terms of physical resources (land, energy, materials, machinery etc) and human resources (labour etc) required to complete the activity.

4. Estimate activity duration

Once the resources required to complete an activity have been identified, an estimate of the activity’s duration using these resources can be made. If this duration is unacceptable, consider changing the resourcing level to modify the duration

Financial Mechanism Office, 12/16, Rue Joseph II, 1000 Brussels, Belgium . Tel: +32 (0)2 286 1701 . Fax: +32 (0)2 286 1789 . Email: fmo@efta.int . www.eeagrants.org

Page 18 of 20 FM 002 7-GDL-0003 4-E-V15

5. Estimate activity cost

Based on the identified resources and the activity duration, an estimate for the activity’s cost can be made. If the cost is unacceptable, consider modifying the resource level and thus the activity duration

6. Define activity sequence

The list of activities defined by the WBS need to be ordered before a project schedule can be developed. Some activities can be performed in parallel; some activities have interdependencies that mean they have to be performed in series.

The most common way of defining an activity sequence is by means of a network diagram.

Figure 7: example network diagram (project tasks represented by nodes)

7. Create project schedule and budget

A project schedule is created by calculating the overall duration of the project based on the sequence of the activities, and thus defining planned start and end dates for each activity. The critical path method is commonly used for this purpose.

Figure 8: example network diagram showing possible critical path between activities

It may be that resource or other constraints mean that activities that could logically be performed in parallel have to be serialised – in this case it will be necessary to modify the activity sequence to reflect such constraints.

With the planned start and finish dates of each activity defined by the schedule, a project budget can be established, detailing the expenditure over the time of the project’s execution.

Financial Mechanism Office, 12/16, Rue Joseph II, 1000 Brussels, Belgium . Tel: +32 (0)2 286 1701 . Fax: +32 (0)2 286 1789 . Email: fmo@efta.int . www.eeagrants.org

Page 19 of 20 FM 002 7-GDL-0003 4-E-V15

8. Risk management

All the preceding activities from the WBS onwards need to be conducted whilst considering the risks to the project. Risks can affect the scope, duration and cost of a project, and risk identification should be an activity that occurs throughout the planning of the project.

Once risks have been identified, their severity should be assessed, typically by evaluating their probability of occurrence and their likely impact, and using a risk rating matrix such as that in Figure 4:

Risk Probability

Low

Medium

High

Risk Impact

Low

Negligible

Low

Medium

Medium

Low

Medium

High

High

Medium

High

Extreme

Figure 9: risk rating matrix

Risks that are judged to have significant severity should to be addressed by:

- Avoiding the risk by ensuring that it can’t occur

- Reducing either the impact or the probability by defining a mitigating strategy

           - Transferring the risk to someone else, for example through insurance or subcontracting Each of these may require a change to the project plan, perhaps through a change to the WBS or the activity sequence.

Less severe risks can also be accepted, typically contingency is built into the project plan to deal with them if they occur.

9. Change Control Planning

The procedures to be followed when managing project changes during the execution phase of the project need to be defined whilst planning. Procedures should be defined for changes to the scope, changes to the schedule, and changes to the cost of the project. These procedures typically describe the authorisation required and the resulting actions when changes of varying magnitudes occur.

Financial Mechanism Office, 12/16, Rue Joseph II, 1000 Brussels, Belgium . Tel: +32 (0)2 286 1701 . Fax: +32 (0)2 286 1789 . Email: fmo@efta.int . www.eeagrants.org

Page 20 of 20 FM 002 7-GDL-0003 4-E-V15

Appendix 2 Example of the effect of the scheduling of in-kind contributions on the actual grant rate

Consider the following project:

- planned duration one year, with PIRs (Project Interim Report) submitted every three months

- planned total eligible expense €1,000,000

- Approved grant rate: 85%

- No advance payment

- 0% retained for PCR (Project Completion Report)

If the eligible expense is entirely in cash, then the grant rate will of course be maintained.

PIR 1

PIR 2

PIR 3

PIR 4

Cash eligible expense

€250,000

€250,000

€250,000

€250,000

In-kind contribution

€0

€0

€0

€0

Disbursement [5.12]

€212,500

€212,500

€212,500

€212,500

Cash co-finance [5.13] +[5.14]

€37,500

€37,500

€37,500

€37,500

Cash expense to date [5.15]+[5.16]

€250,000

€500,000

€750,000

€1,000,000

In-kind contribution to date [5.17]

€0

€0

€0

€0

Total funding to date [5.18]

€250,000

€500,000

€750,000

€1,000,000

Cash expense/ total expense

100%

100%

100%

100%

Running grant rate

85.0%

85.0%

85.0%

85.0%

If the project consists of €950,000 cash eligible expense, budgeted evenly throughout the project and an in-kind contribution, valued at €50,000 reported in the first three-month period, then although the grant rate is below that awarded by the FMC / NMFA in the first reporting period, subsequent periods compensate.

PIR 1

PIR 2

PIR 3

PIR 4

Cash eligible expense

€237,500

€237,500

€237,500

€237,500

In-kind contribution

€50,000

Disbursement [5.12]

€237,500

€208,750

€201,875

€201,875

Cash co-finance [5.13] +[5.14]

€0

€28,750

€35,625

€35,625

Cash expense to date [5.15]+[5.16]

€237,500

€475,000

€712,500

€950,000

In-kind contribution to date [5.17]

€50,000

€50,000

€50,000

€50,000

Total funding to date [5.18]

€287,500

€525,000

€762,500

€1,000,000

Cash expense/ total expense

82.6%

90.5%

93.4%

95%

Running grant rate

82.6%

85.0%

85.0%

85.0%

If the project consists of €950,000 cash eligible expense, budgeted evenly throughout the project and an in-kind contribution, valued at €50,000 reported in the last three-month period, it is not possible to compensate as there are no more reporting periods.

PIR 1

PIR 2

PIR 3

PIR 4

Cash eligible expense

€237,500

€237,500

€237,500

€237,500

In-kind contribution

€0

€0

€0

€50,000

Disbursement [5.12]

€201,875

€201,875

€201,875

€237,500

Cash co-finance [5.13] +[5.14]

€35,625

€35,625

€35,625

€0

Cash expense to date [5.15]+[5.16]

€237,500

€475,000

€712,500

€950,000

In-kind contribution to date [5.17]

€0

€0

€0

€50,000

Total funding to date [5.18]

€237,500

€475,000

€712,500

€1,000,000

Cash expense/ total expense

100%

100%

100%

95%

Running grant rate

85.0%

85.0%

85.0%

84.3%

Financial Mechanism Office, 12/16, Rue Joseph II, 1000 Brussels, Belgium . Tel: +32 (0)2 286 1701 . Fax: +32 (0)2 286 1789 . Email: fmo@efta.int . www.eeagrants.org

Danfoss PLUS+1 GUIDE Software

Release Notes

This file contains important supplementary and late-breaking information that may not appear in the main product documentation. We recommend that you read this file in its entirety.

Product License

If you do not have a PLUS+1 License: Please order your PLUS+1 License through your local Danfoss sales person. You will be sent an email with a Product Key that will allow you to activate a License Key. Please follow the instructions under Help in the License Manager.

For existing PLUS+1 License holders with PLUS+1 version 5.0 or later installed: After installation of

PLUS+1 GUIDE, your License Key is automatically activated in this version.

For Users with versions before 5.0 please see instructions later in this document.

Support for all PLUS+1 License related issues can be obtained by sending an email to: plus+1helpdesk@danfoss.com

System requirements

Service Tool Minimum

GUIDE Minimum

GUIDE/Service Tool Recommended

CPU*

1.5 GHz, 32-bit (x86), 1 core, 2008 or later

3.0 GHz, 64-bit (x64), 4

cores, 2012 or later

OS

Windows 7 SP1 (32/64-bit) or Windows 8 (32/64-bit)** or Windows 8.1 (64-bit)

UAC

Local Administrator Access

RAM

1 GB

3 GB

HD

>1 GB Free, HDD

>2 GB Free, SSD

Resolution

1024 x 768

1920 x 1080

Email

For license registration

PDF

Any recent standards compliant pdf reader

XML

MSXML 4.0 Service Pack 2 (Microsoft XML Core Services)

.Net

N/A

Version 4 (Full) is needed for Structured Text support in GUIDE

* The CPU should be intended for at least laptop use. Processors designed for netbooks, tablets or similar are not recommended.

** Version 7.1 of GUIDE and Service Tool will be the last to officially support Windows 8 32-bit. (The next version will support Windows 7 (32/64-bit), Windows 8 (64-bit), Windows 8.1 (64-bit).)

1

VERSION 7.1.12 (June 2015)

-New Features and Functionality (see the GUIDE User Manual for more detailed information) None

-Important Advisory—Potential User Issues

(No changes from 7.1.11)

-What is Fixed

[P100003322] If the size of an application log definition is set to zero, compilation will fail with error 639.

[P100003352] An error message has been added for the case when a component with an output signal is pasted into a screen definition and the output signal is already in use.

[P100003353] An error message has been added for the case when an output signal is connected to more than one output in a screen definition.

[P100003388] Video images in Vector Based Screen Editor did not compile.

[P100003403] In some cases, corrupt text data source would cause texts of different languages to be mixed.

[P100003446] In some cases, corrupt text data source would cause a compile error. For more detailed information about specific issues, please contact PLUS+1 Helpdesk.

2

Product Information on the Web

For technical support, visit the Danfoss support pages:

powersolutions.danfoss.com/Products/MobileElectronics/PLUS1Guide/PLUS1GuideSupport/index.htm

Telephone support:

North America: 1.888.50PLUS1 (+1-888-507-5871)

Europe: +46 476-569 06

Email support: plus+1helpdeskCa)danfoss.com

PLUS+1 Forum: http://www.plus1forum.danfoss.com/index.php

Please report all suggested enhancements and great ideas to:

PLUS+1 Help desk

Please report all defects to:

PLUS+1 Help desk

Many thanks for all of your support.

The System Development Tools Team.

Legacy Product License

For existing PLUS+1 License holders with PLUS+1 version 3.x/4.x installed: Please use the upgrade key emailed to you in December 2010 or send an email requesting your upgrade key (including your license ID) to:

plus1licenseCa)danfoss.com

Support for all PLUS+1 License related issues can be obtained by sending an email to:

Email support: plus+1helpdeskCa)danfoss.com

Disclaimer

The Danfoss Software License Agreement completely defines the licensed use of this software. Information in this document is provided in connection with Danfoss PLUS+1 GUIDE tool set. No license, express or implied, to any intellectual property rights is granted by this document. Danfoss disclaims all warranties and liabilities for the use of this document and the information contained herein and assumes no responsibility for any errors, which may appear in this document, nor does Danfoss make a commitment to update the information contained herein. Danfoss reserves the right to make changes to this document at any time, without notice.

Copyright

©2004-2014 Danfoss. All rights reserved.

Third party trademarks and brand names are the property of their respective owners.

3

Previous Release Notes

Release notes dating back to 2.0.3 follow:

VERSION 7.1.11 (April 2015)

-New Features and Functionality (see the GUIDE User Manual for more detailed information) None

-Important Advisory—Potential User Issues

(No changes from 7.1.10)

-What is Fixed

[P100003203] For some HWDs, the components Compare in Window and Compare with Hysteresis Middle as well as the following capped components: Add, Sub, Mul and Div could produce incorrect output in some cases where at least one of the connections was signed, at least one global (i.e. connected to a Checkpoint or similar) and the calculation would internally overflow an S32.

[P100003323] The components Compare with Hysteresis High and Compare with Hysteresis Low could in some cases get stuck on true or false output.

[P100003325] The component Compare in Window had an issue in some cases on one compiler when both A1 and A2 entries were of type U32.

[P100003329] The components Compare with Hysteresis High and Compare with Hysteresis Low could in some cases produce incorrect output.

[P100003332] There was a defect in Scale and Scale Capped when 0x10000000000000000 <= (A1-A5)*(A3-A4) <= 0x100000000FFFFFFFF.

[P100003240] In some cases, image lists in large screen definitions did not work.

[P100003237] In some cases, it was not possible to compile text lists in applications where the HWD supports rotated displays.

[P100003318] For some HWDs, a compile changed on a classic screen editor application would result in all images being recompiled if a module was modified in a way that did not affect any screen page. This behavior is now changed so that no images are recompiled when compile changed is invoked and there are no screen editor changes.

[P100003227] The names of module signals in module buses could not start with digits.

[P100003234] Projects compiled for MC0xx-0xx hardware used significantly more ROM memory in 7.1.10 due to different ordering of global variables.

[P100003236] Existing test definitions added in the Test Manager were not saved correctly.

[P100003246] It was possible to add characters to the description field in Test Tool which could lead to an invalid XML file. This has now been fixed so it is not possible to have invalid characters in the description field.

[P100003252] The Module Viewer menu action was disabled when no project was open in GUIDE.

5

[P100003284] On some computers compile could sometimes fail with a write access denied for a .ddt file. This handling has now been made more robust, but note that it will still be unable to succeed if the “Read-only” property is set for the .ddt file.

[P100003279] Custom initialization of Structured Text struct variables was not implemented in the compiler.

[P100003289] Initialization of Structured Text struct variables was displayed incorrectly in the GUI. The last field was not shown in the initialization.

[P100003366] In the debugger, NV parameters were sometimes incorrectly modified when other NV data was modified.

[P100003228] The signal list when connecting on a bus was not in alphabetical order.

[P100003229] For Test Tool the don’t care character (’-’) was not interpreted correctly in the graph.

[P100003283] Pages deleted from project was still present in the test status file. This is now fixed so pages not present in the project are removed from the test status file.

[P100003355] Structured Text coding guidelines are now included in the /Misc folder.

[P100003256] When using Query on a component to change it to another component in the same category and when the output type was an array type, the output type was not retained.

[P100003350] Updated chapter reference in SIL compilation message.

For more detailed information about specific issues, please contact PLUS+1 Helpdesk.

6

VERSION 7.1.10 (December 2014)

-New Features and Functionality (see the GUIDE User Manual for more detailed information)

[F00151] Feature: Debug Tool (Add-On license required: ’FuncSafety’*).

Improvements since the evaluation version in 7.0:

- Repeat-Until now possible to debug through

- The Structured Text editor is now a non-modal window with tabs support

- Conditional Breakpoints, both in graphical code as well as in Structured Text code

- Data breakpoints (Watchpoints) that are triggered when a variable value changes

- New visual indication icons for showing debug status in graphical code

- Visual indication icons for showing Breakpoints and Current Line in Structured Text code

- Net values shown directly on the nets in graphical code

- POU variable values shown directly in the POU interface part as a grid

Limitations:

- The following components have no support; they cannot be part of a debugged application: App Log, the old NV components, Classic Screen editor.

- The following components have stubbed support; they can be part of a debugged application, but are replaced with empty implementations: CCPs, CAN RX/TX, Vector based Screen Editor, Read Applog, Write file

- The following components have limited support; they can be part of a debugged application, but reduced functionality: NV components do not retain their values between debug sessions.

- In order to debug NV signals, their names can only contain letters and numbers.

- The HWD used in the project should be recent, it must at least support the Module Input component and the dynamic diagnostic format.

- Watches cannot currently be set on Structured Text variables.

- When debugging into SCS files that were saved using a previous file format, debug icons and net value texts can sometimes not be displayed correctly. The workaround for this is to save such SCS files using the current GUIDE version.

- Up to 4 data breakpoints can be used concurrently.

[F00262] Feature Extension: Vector Based Screen Editor.

Improvements since the version in 7.0:

- New text(list) property font list makes it possible to switch font in run-mode.

- It is possible to create orthogonally rotated screen definitions (requires support by HWD).

- It is possible to switch between screen definitions inside the vector based screen editor.

- Composite pairs (unicode) are supported.

- Several small improvements and adjustments to align with classic screen editor.

Defect fixes:

- For some fonts, some characters were cut off. This has now been fixed.

- Text list font size was incorrectly presented as zero. This has now been fixed.

7

[F00263] Feature Extension: Test Tool (Add-On license required: ’FuncSafety’*).

Improvements since the version in 7.0:

- Updated user interface, with more functionality built into the tool

- Support for test-driven development with ability to define tests without source code

- Ability to only use subset of page interface for page under test

- Ability to define don’t care on signals for individual test steps

- Array types on the interface is fully supported

- The test report is more complete with the actual test data included

- ’OS.ExecTime’ is always available in the interface to define the execution time

- ’Reset before run’ is implemented to allow reset of all states before running a test

- Unused signals in the page interface of the block under test are culled

Limitations:

- The following components have stubbed support; they can be part of a debugged application,

but are replaced with empty implementations: CCPs, Vector based Screen Editor, Read Ap

plog, Write file

- The HWD used in the project should be recent, it must at least support the Module Input com

ponent and the dynamic diagnostic format.

- Interface signals with leading digit is not supported.

[F00171] Feature: GUIDE Dependency view to show dependencies between components has been added (Patent Pending) (Add-On license required: ’FuncSafety’*).

[F00141] Feature Extension: Clicking on a link to an Error or Warning now displays an icon next to the error position. The icon can be configured in the Options dialog. Navigating between multiple errors in the Error Messages using Ctrl+Up or Down arrow is now also possible. The coordinates in the error and warning messages have been scaled up by a factor of 10000.

[F00271] Feature Extension: File extensions of all generated files are now lower case by default.

[F00278] Feature Extension: For some Errors or Warnings the link to the error position has been complemented with a link that trigger View Logical Net for the net in the error position.

[F00279] Feature Extension: Segmented lines in the CAD area are now automatically cleaned up. As a consequence, the “Optimize Nets” action is now removed from the Tools menu.

[F00280] Feature Extension: The Mouse-Wheel Zoom-Step size is now user-configurable, and has been reduced by default. The zoom keyboard buttons (PageUp/PageDown by default) are also affected by this enhancement.

[F00281] Feature Extension: Pan using a “hand”-type mouse cursor is now enabled as an option activated from the Toolbar. The right mouse button is used for this action.

8

[F00291] Feature Extension: It is now possible to manually force strict standard mode for compiling Structured Text code. This mode was previously only enabled when performing SIL-compilations. The strict mode is activated from the options menu.

[F00294] Feature Extension: It is now possible to disable the bounding box that is displayed in the CAD drawing area around the used components of each page. This is done by changing an option in the General Settings of GUIDE.

[F00289] Feature Extension: It is now possible to save application log contents to USB stick in a faster way using the application log editor interface (requires HWD support). This feature extension is released in evaluation mode.

[Misc] Information: Various speed improvements in design mode have been implemented.

* FuncSafety Add-On License

* Has SAP number 11133293, GUIDE ADDON LICENSE_QUALITY ASSURANCE

* Enables

– Version Control Support

– Test Tool

– Compare SCS (outside the USA)

– Dependency View

– Debugger Tool

– SIL2 Compilation

** SimModel Add-On License

* Has SAP number 11133294, GUIDE ADDON LICENSE_SIMULINK

* Enables

– GUIDE-to-Simulink

-Important Advisory—Potential User Issues

* Components

– The CAN components are always processed on each loop. This is true even when the CAN components are placed in a module and that module is not called by the main loop.

Workaround: Only use CAN components in modules that are always active each loop, such as the main module, or modules called with constant true from the main module.

– Components without output types (e.g. Hardware Input) cannot be directly connected to a class

instance. This will generate a compile error.

Workaround: Use a retype connection in between.

9

– Autotyped constants will not work when connected directly to Objects. This will generate a com

pile error.

Recommendation: Use a Typed constant.

– When connecting the bus output from any one of the following components: “Call Method Of Externally Defined Class”, “Call POU”, “Show Screen”, “Write applog” and “Module Bus Input” to the input bus of the “Module Bus Output” component, only the signals that are actually connected in that module will be available in the module bus. (P100002771).

Workaround: Use a dedicated bus for module connections. Do not connect it to other buses.

– The “Module Bus Input” and “Module Bus Output” components do not support bus-in-bus. Workaround: Use one module bus for each sub bus.

* File Formats

– Due to new features affecting the SCS format, GUIDE version 6.1 and earlier will not open SCS

files saved with GUIDE version 7.0 and later.

Recommendation: Always back up project files before opening them in a new version of the tool.

* OS and other environment considerations

– Running GUIDE on Windows 7 in compatibility mode for Windows XP may cause unhandled exceptions in the program and is not recommended. Running GUIDE in compatibility mode had the benefit of speeding up compiles when using one of the old TI compilers (5.2.5 and older). Extremely long compile times is no longer an issue when using the latest TI compiler: 5.2.15. Recommendation: Use a HWD file that supports the TI 5.2.15 compiler.

– SCS files placed in the Desktop folder might not be available in the import SCS dialog. Workaround: The “My Documents” folder is preferred.

– If you are experiencing problems accessing network locations in Windows 7, then please refer to

this website: http://technet.microsoft.com/en-us/library/ee844140(WS.10).aspx

Workaround: If your IT policies allow it, then modify the UAC setting to its minimum value.

– It is advisable to complete all GUIDE processes before locking or hibernating your computer. Workaround: Close GUIDE before leaving the computer.

– If the Windows PATH environment variable contains paths to folders that contain executables with names that conflict with names of standard Windows commands, such as “echo”, compilation might fail without any clear error message. (For example, a standard MinGW installation might add a folder containing an incompatible binary named echo.exe to the PATH.) (P100003153) Workaround: Temporarily, or permanently, remove such folders from the Windows PATH. (Alternatively, rename or remove the incompatible executable files from those folders.)

– The tool only supports the setting "100%" in "Display / Make text and other items larger or smaller".

* License

– When using GUIDE without a license (Evaluation Mode), saving is not possible. Recommendation: For the best user experience, an existing project to test with is essential. Please contact PLUS+1 Helpdesk to obtain an evaluation project.

10

* Version independent user data

– From version 7.0, version independent user data is saved in different folders than previously. This means that changes made to version independent user data in version 7.0 will not take effect in version 6.1 or earlier, and changes made to version independent user data in version 6.1 or earlier will not affect version 7.0 and later. Only during the very first installation of version 7.0 (or later) will user data be copied from the previous locations. This affects Diagnostic Data (PLG), Hardware (HWD), Library (SDL) and Font (P1F) files, and also “MyBlocks” files.

* Installation

– The user must exit GUIDE to install/uninstall other GUIDE versions. Recommendation: Close all open programs before installing the tool.

– PLUS+1 GUIDE is only intended to work with one single user account.

Workaround: The same user account should be used both for installation and usage of the tool.

* Project handling/ Compilation

– GUIDE cannot handle non-Latin characters in project folder names. Workaround: Use characters ’a’-’z’ in paths.

– Double spacing in file names: Some issues have been found in projects where file names have

double spaces. Single spaces in file names are not known to cause any problems.

Workaround: Only use single spaces in file names.

– In projects using several modules and objects, the Compile changed command can end with a

failure due to the order in which the files are compiled.

Workaround: Use Compile All if this happens.

– When working with projects that contain a high number of files, or files with very long file names, and the sum of the lengths of the file names of these files exceeds thirty thousand characters it is possible that the C linker fails to link the project. (P100002678)

Workaround: remove or shorten the names of the project files until the total length of file names are well under thirty thousand characters.

* Tool

– Assigning single-letter shortcut keys for functionality that is not specific to the graphic code drawing can cause issues. For example assigning the letter ’o’ to the “Open Project” functionality means that the letter ’o’ cannot be used when editing texts.

Workaround: Only assign single-letter shortcut keys to functionality that is specific to the graphic code drawing such as move, stretch and enter page.

* Screen and Application Log

– In the text editor, strings longer than 509 characters in Classic Screen Editor and Application Log may not compile.

11

– Compatibility issues involving display projects using non-Roman fonts created in GUIDE version 3.0 may occur. It is strongly advised that the user make a backup of these files before using GUIDE 7.0 and contact the PLUS+1 GUIDE Help Desk for further information before proceeding.

– In the Vector Based Screen Editor, when working with texts using more than four input values, and the last one uses octal format and is located at the very end of a text, then that value may not be displayed correctly.

Workaround: place a space character after an input value that fulfills the above criteria.

– In the Vector Based Screen Editor, when transparence has been selected by clicking on a specific pixel in an image, and that image is then scaled, it is possible that the transparent color will change. Furthermore, it is also possible when the image is scaled to a smaller size that the selected pixel position will end up outside the image.

Workaround: use images where the transparency data is part of the file format (such as .png) instead.

– In the Vector Based Screen Editor, some Unicode characters will be displayed correctly in the preview, but will then only be displayed as squares on display hardware.

– In the Vector Based Screen Editor, using copy+paste on screen definitions only works within a single project, not from one project to the next.

– In the Vector Based Screen Editor, it is not possible to compile if unused format codes exist in a text definition.

– Ligatures are not supported in the screen editors.

– If a screen definition inside a class has inputs connected directly to the page interface of that class page, this may result in error 63 and error 184. A workaround is to add a retype inside the object page, before the signal is passed to the screen definition.

– If vector based screen editor components having constant-only width and height properties are selected together with a component having both constant and signal width and height properties, then width and height properties may be incorrectly available in the inspector.

– In the classic screen editor, characters of fonts having a large horizontal extension may not be correctly displayed on the display unit.

– Components Show Screen and Write Applog are not allowed inside object pages.

– In the Vector Based Screen Editor, the ScaleSize property does not work as intended for text components.

* Test Tool

– All signals passed through the interface will be of variable type. This means that components that require constant type on an input need to have the constant set from within the tested page.

– Structural test coverage is not measured by the Test Tool. But for the graphical code in PLUS+1 GUIDE statements coverage is implicitly covered within one module.

– There are some rare situations when the Test Tool GUI is not updated to correctly reflect the

current status.

Workaround: Exit the Test Tool and then open it again to refresh the GUI.

12

– It might not be possible to generate test code for projects that are already on the edge of running

out of memory when compiling.

Workaround: Split the project into smaller modules.

* Structured Text Code Editor

– Double-width Unicode characters used in comments in the Structured Text Code Editor can be displayed in a way such that they appeared to be clipped.

Workaround: Place a number of whitespace characters after comments that are displayed as clipped, until they are displayed correctly.

-What is Fixed

[P100003215] Max Value Capped did not work when one input was constant below zero and the other input was unsigned. This defect affected TI compiler 5.2.15 when Optimizer Settings was set to OFF.

[P100002919] Image transparency setting modifications were not detected when compile change was run. This has now been fixed.

[P100002873] When changing between licenses, the SIL compile functionality was not enabled correctly. This has now been fixed.

[P100003107] Component Compare with Hysteresis High behaved incorrectly when inputs A1 and A3 where constant, input A2 was signed and the hysteresis interval started below zero and ended at or above zero. This has now been fixed.

[P100003150] Image lists in the vector based screen editor did not handle rotation point offset correctly - all images were depicted as if the rotation point offset was at (0, 0) and the ActiveIndex constant affected the image list insertion point on the display. This has now been fixed.

[P100002910] A Bidirectional Hardware Output signal could be connected to the same net as a Checkpoint. Since a Bidirectional Hardware Output signal drives the net backwards, this could lead to unpredictable results, including but not limited to the value read from the Checkpoint. This is now fixed by disallowing such connections.

[P100003196] User defined transparency was not handled correctly in flipped images.

[P100003185] A corrupt text data file where texts for some languages were missing resulted in an unhandled error. Now an error message is displayed instead.

[P100003172] When using constant, right angle rotation and rotation point offset on hardware images; touch was not properly detected. This is now fixed in GUIDE 7.1.

[P100003034] Some old projects using the deprecated “3.0.9”C-compiler and certain math components would not compile since GUIDE version 5.0. This is now fixed in GUIDE 7.1.

[P100003037] The compatibility-mode check failed when run on Windows 8.1 (not supported by GUIDE 7.0) due to Windows API changes. This led to a false positive compatibility-mode popup warning. This has now been fixed.

13

[P100003038] Routing signals with names that would be invalid as C identifiers through Module Buses would lead to obscure error messages. The error messages are now improved.

[P100003040] CCP documentation files were not directly available in the Project Manager. This has now been fixed.

[P100003047] The context menu in the hardware tree was not always correct when activated from the keyboard (rather than from mouse-click). This has now been fixed.

[P100002989] Whenever a port name in a bus connected to a legacy screen page contained a dot that was not a bus separator and the signal connected to that port was used inside the screen page, compilation was aborted with an undescriptive error message. This has now been fixed so that error 188 will be raised in these cases.

[P100003022] Font files with default charset resulted in a compile error since the charset was not known. Now the default charset of the system will be used.

[P100003019] There was an error in the classic screen editor that caused data values to be uneditable in the inspector. This has now been fixed.

[P100003032] There was an unused enable signal in application log 2 definitions. It has now been removed.

[P100003028] A defect that resulted in an incorrect compile error has now been fixed.

[P100003065] Boolean "true" values from GUIDE to calls of Structured Text POUs were not necessarily identical to "1", they could also appear as higher values. This has now been fixed.

[P100003067] Importing Structured Text code in PLCopenXML format that was saved by the ’Beremiz’ tool did not work, but has now been fixed.

[P100002975] It was not possible to import test defintions from a XLS file with more than 20 CAN messages. This has now been fixed.

[P100003090] The Absolute Value component could produce incorrect output on TI hardware when the input value was less than -32768, and if the input net was also connected to a checkpoint. This is now fixed.

[P100003095] It was not possible to mix screen definitions and checkpoints inside object pages. This has now been fixed.

[P100002992] In some rare cases, it was not possible to enter area pages. This has now been fixed.

[P100002834] It was not possible to read the full warning message when opening a project with too many missing files. The message window became too large. This is now fixed by showing a resizable and scrollable mesage window instead.

[P100002897] When renaming a project file, but then not saving the project p1x file, the project could end up in an inconsistent state where the project file would no longer be found. This has been resolved by automatically saving the project p1x file when renaming any project file.

14

[P100002898] GUIDE would not work if GUIDE and Service Tool were installed into different paths.

[P100002959] Warnings about project files changed outside GUIDE were sometimes shown when no changes had been made outside GUIDE. This is now fixed.

[P100002949] The attempt to remove a non-existing language dependent font would result in an access violation. This is now fixed.

[P100002950] It was possible to set priority to a negative value even though that is not allowed. This is now fixed.

[P100002854] There was no warning that editing of a linked screen editor page would change the other linked pages as well. A warning message has been added.

[P100003212] Flipped images had a one pixel shift.

[P100002879] When trying to import test definitions from a read-only XLS file there was an error message shown and no test cases were imported. Now the import of XLS file is capable to handle read-only files.

[P100002880] The selected node in the tree-view in Compare SCS was not highlighted in a consistent way. This is now fixed.

[P100002881] When trying to import test definitions from a XLS file columns without header were sometimes misinterpreted as inputs which could result in corrupt data. This is now fixed.

[P100002926] When a test case with no matching interface signals was used and all non-matching signals were deleted an error message was shown. This is now fixed.

[P100002974] For CAN messages in Test Tool the length was not considered when showing data values. Now length is used to determine how many bytes to show in the result.

[P100003104] An incorrect warning message about a required license could sometimes pop up when a new project was opened after the test tool was used in the previous open project. This has now been fixed.

[P100003013] For IDL files with CCP methods with input parameters with default values, an error was triggered if there was no white-space character directly after that default value. This has now been fixed.

[P100003020] The drawing area was all black when routing with space and refreshing the area. This has now been fixed.

[P100003042] The error message for Compile Binary File handle mismatch has been improved.

[P100003045] When non-standard page sizes are used, then incorrect warnings about Components placed outside the page boundaries could be reported. That is now fixed, and additionally non-standard page sizes are now reportCompilation of an application containing an unsupported screen/application log page resulted in an access violation. An error message has been added instead. ed as warnings.

15

[P100003068] Vector based screen definitions were one pixel too large in both dimensions. This has now been fixed.

[P100003055] It was not possible to compile for Test if the project path contained Unicode characters such as for example: ’ciäö’. This also affected Debug. This has now been fixed.

[P100003120] Some svg images were not rendered correctly on the display. This has now been fixed.

[P100003062] Block indentation of Structured Text code using tab and shift+tab keys did not work correctly if the code block was selected from a higher to a lower line number, i.e. it only worked if the selection was made top->down. This is now fixed.

[P100003036] In the vector based screen editor component inspector, signal and constant were not shown for all properties. This has now been fixed.

[P100003098] CCPs with partial IDL includes did not work to compile in GUIDE. This has now been fixed.

[P100003099] A block of “VAR CONSTANT”-variables could not be listed after a block of ordinary “VAR”-variables in the Structured Text editor. They had to be listed first. This is now fixed.

[P100003116] In some cases, the Connect To Bus dialog failed to list all available nets in the bus. This has now been fixed.

[P100003135] Uninstalling HWDs while their documentation files were open in another program could cause those files to not be deleted. This would complicate the reinstallation of those HWD files. This situation will now be detected before the HWD is uninstalled.

[P100003145] The Full installation of the Microsoft .Net v4 Framework is required for Structured Text support to work. However, if the Client installation of the same version was the only installed version, then GUIDE would not detect that the required version was not installed, and no indication would be given to the user. This has now been fixed.

[P100002400] In the classic screen editor, it was possible to use the potentially dangerous %s printf formatting code in some cases. This has now been fixed.

[P100003118] In some cases, importing an already present screen definition would cause the screen and application log repository to become unsavable. This has now been fixed.

[P100003127] Simultaneously editing the font on multiple selected text objects in the vector based screen editor was not possible. This has now been fixed.

[P100003165] If the instance entry (A1) of a "Call Method of Externally Defined Class"-component was not connected, then an unclear error message was displayed. This error message has now been improved.

[P100002838] SYS files expanded to disk were always saved using uppercase letters. Now they are saved using the same case as in the recipe file.

16

[P100002856] Unconnected NV Components were handled differently depending on which type of NV component used. This has now been fixed so that all unconnected NV Components are handled equally; they will now in no case be optimized away.

[P100002859] The error message that is shown when an invalid license is used has been made easier to read.

[P100003140] When the empty string was entered as the name of a language, an incorrect error message was shown. This has now been fixed.

[P100002869] The structured Text editor window was sometimes reopened partially outside a monitor. This has now been fixed.

[P100002876] A number of error messages related to incorrect ROP files have been made easier to read.

[P100002981] Compilation of a project with PLCopenXML files, but without any POU would previously fail. This is now fixed.

[P100002994] Backspace was erasing text on the right side of the cursor when it was at the leftmost position in the edit field. This is now fixed so only text on the left side of the cursor is erased.

[P100003018] The error message that is shown for unlicensed use of licensed function library pages has been clarified in the case where the corresponding function library is not installed.

[P100003027] Compilation of an application containing an unsupported screen/application log page resulted in an access violation. An error message has been added instead.

[P100003017] The font size of a text list in the vector based screen editor was displayed as zero. Now the correct font size is displayed.

[P100003072] Only the first 2 numbers of the required GUIDE version was shown when trying to compiling a project. Now the full required version is shown.

[P100003035] Some files were not cleaned up when a project containing object pages was closed and packed. This has now been fixed.

[P100003143] File extensions for known file types were not shown in the Project View if the correspon-ing setting was active in Windows Explorer. File extension is now always shown.

[P100003193] In the vector based screen editor, text lists were shown with borders in preview mode.

[P100003190] Variables in text lists did not show correct constant value in design mode.

[P100003162] Adding the same test case to a test list more than once was not possible. This has now been fixed.

17

VERSION 7.0.8 (September 2014)

-New Features and Functionality (see the GUIDE User Manual for more detailed information)

-Important Advisory—Potential User Issues

(No changes from 7.0.7)

-What is Fixed

[P100003069] An incorrect checksum calculation made it impossible to download some applications to SC-controllers. This has now been fixed.

[P100003093] Text lists in large screen definitions could in some cases result in a compile error. This has now been fixed.

[P100003094] It was not possible to use several instances of a screen definition. This has now been fixed.

[P100003108] Scaled and rotated image lists got the wrong insertion point. This has now been fixed.

[P100003131] The position of an image list containing a rotated image was not stored correctly. This has now been fixed.

[P100002967] In some cases, importing a screen definition would cause the vector based screen editor to crash. This has now been fixed.

18

VERSION 7.0.7 (March 2014)

-New Features and Functionality (see the GUIDE User Manual for more detailed information)

[F00263] Feature Extension: TestTool, handle test cases on pages within the test manager (Add-On license required: ’FuncSafety’*).

* FuncSafety Add-On License

* Has SAP number 11133293, GUIDE ADDON LICENSE_QUALITY ASSURANCE

* Enables

– Version Control Support

– Test Tool

– Compare SCS (outside the USA)

– Dependency View (for evaluation)

– Debugger Tool (for evaluation)

-Important Advisory—Potential User Issues Version independent user data

* From version 7.0, version independent user data is saved in different folders than previously. This means that changes made to version independent user data in version 7.0 will not take effect in version 6.1 or earlier, and changes made to version independent user data in version 6.1 or earlier will not affect version 7.0. Only during the very first installation of version 7.0 (or later) will user data be copied from the previous locations. This affects Diagnostic Data (PLG), Hardware (HWD), Library (SDL) and Font (P1F) files, and also “MyBlocks” files.

(No other changes from 7.0.6)

-What is Fixed

[P100002843] Running in compatibility mode, for example Windows XP mode on Windows 7, is not supported and can result in an external exception after compilation in some cases. Now a warning message is displayed when starting GUIDE in compatibility mode.

[P100002882] Some valid Toolkey values were not possible to edit in 7.0.6. This has now been fixed.

[P100002889] For certain compilers, and when using large arrays from file, compile time could be quite long and also unpredictable with much variation for small changes of the code. This has now been fixed.

[P100002904] A problem where the GUIDE could sometimes crash when closing the classic screen editor has been addressed.

[P100002914] In some cases when connecting a net from one bus to another, and those buses were recursively sub-buses of each other, the GUIDE could crash. This is now resolved.

19

[P100002935] On some machines and user accounts, the installation failed to place files needed by the CAD GUI in the right folder. That has now been fixed by placing those files in the all users appdata folder instead.

[P100002941] In some cases the Screen Editor crashed when closed. That has now been fixed.

[P100002955] Unsaved changes in the Vector based screen editor, Structured Text editor and Test Tool editor were lost when performing a Save As. This is now fixed.

[P100002957] A project with multiple ROPs of the same type could not be opened correctly. This is now fixed.

[P100002895] An uninformative error message was displayed when a text was missing in the classic screen editor. A proper error message has been added.

[P100002892] In some cases, an unconnected input to the component “Non-volatile Memory Dynamic” was not detected until the compile step, and an unclear error message was shown. This is now fixed and a clear error message is shown.

20

VERSION 7.0.6 (November 2013)

-New Features and Functionality (see the GUIDE User Manual for more detailed information) [F00144] Feature: Test Tool has been added to GUIDE (Add-On license required: ’FuncSafety’*).

[F00145] Feature: GUIDE to Simulink S-Function is now available as a full feature. It is used for converting a subset of a PLUS+1 GUIDE project to a Simulink S-Function (Add-On license required: ’SimModel’**).

[F00164] Feature: Support for using a version control tool when working in GUIDE is now available as a full feature (Add-On license required: ’FuncSafety’*).

[F00092] Feature: Compare SCS is added (outside the USA) as a full feature (Add-On license required: ’FuncSafety’*).

[F00230] Feature Extension: Import and export capabilities have been added to the Vector Based Screen Editor.

[F00213] Feature Extension: Structured Text Editor has been extended to include quick reference to Code Blocks as a full feature.

[F00248] Feature Extension: The external C compiler TI 5.2.15 has been added to support MC hardware (HWD Dependant).

[F00251] Feature Extension: The external C compiler MinGW 4.8.1 has been added to support Test Tool and Debug Tool.

[F00252] Feature Extension: The external C compiler GCC 4.7 for ARM (20130614-q2) has been added to support SC and MC hardware (HWD Dependant).

[F00199] Feature Extension: The Add-On license system has been extended with ’FuncSafety’* and ’SimModel’** GUIDE upgrade features.

[F00257] Feature Extension: A time limited, full, GUIDE license now enables ’FuncSafety’* and ’Sim-Model’** GUIDE upgrade features automatically for evaluation purposes.

[F00151] For Evaluation: Debug Tool has been added to GUIDE (Add-On license required: ’Func-Safety’*).

[F00171] For Evaluation: GUIDE Dependency view to show dependencies between components has been added (Patent Pending) (Add-On license required: ’FuncSafety’*).

[F00225] Information: Windows 8 (32/64-bit) is now supported.

[F00250] Information: The PLUS+1 GUIDE tools are now installed in a ’Danfoss’ program group.

[F00253] Information: The main window caption of the PLUS+1 GUIDE tools now also display the release part of the version number in addition to the major and minor release numbers.

[F00260] Information: The Remote Desktop support software on the Help menu has been updated to a web-based solution.

21

* FuncSafety Add-On License

* Has SAP number 11133293, GUIDE ADDON LICENSE_QUALITY ASSURANCE

* Enables

– Version Control Support

– Test Tool

– Compare SCS (outside the USA)

– Dependency View (for evaluation)

– Debugger Tool (for evaluation)

** SimModel Add-On License

* Has SAP number 11133294, GUIDE ADDON LICENSE_SIMULINK

* Enables

– GUIDE-to-Simulink

-Important Advisory—Potential User Issues

* File Formats

– Due to new features affecting the SCS format, GUIDE version 6.1 and earlier will not open SCS

files saved with GUIDE version 7.0 and later.

Recommendation: Always back up project files before opening them in a new version of the tool.

* OS and other environment considerations

– Running GUIDE on Windows 7 in compatibility mode for Windows XP may cause unhandled exceptions in the program and is not recommended. Running GUIDE in compatibility mode had the benefit of speeding up compiles when using one of the old TI compilers (5.2.5 and older). Extremely long compile times is no longer an issue when using the latest TI compiler: 5.2.15. Recommendation: Use a HWD file that supports the TI 5.2.15 compiler.

– SCS files placed in the Desktop folder might not be available in the import SCS dialog. Workaround: The “My Documents” folder is preferred.

– If you are experiencing problems accessing network locations in Windows 7, then please refer to

this website: http://technet.microsoft.com/en-us/library/ee844140(WS.10).aspx

Workaround: If your IT policies allow it, then modify the UAC setting to its minimum value.

– It is advisable to complete all GUIDE processes before locking or hibernating your computer. Workaround: Close GUIDE before leaving the computer.

* License

– When using GUIDE without a license (Evaluation Mode), saving is not possible. Recommendation: For the best user experience, an existing project to test with is essential. Please contact PLUS+1 Helpdesk to obtain an evaluation project.

22

* Installation

– The user must exit GUIDE to install/uninstall other GUIDE versions. Recommendation: Close all open programs before installing the tool.

– PLUS+1 GUIDE is only intended to work with one single user account.

Workaround: The same user account should be used both for installation and usage of the tool.

* Project handling/ Compilation

– GUIDE cannot handle non-Latin characters in project folder names. Workaround: Use characters ’a’-’z’ in paths.

– Double spacing in file names: Some issues have been found in projects where file names have

double spaces. Single spaces in file names are not known to cause any problems.

Workaround: Only use single spaces in file names.

– In projects using several modules and objects, the Compile changed command can end with a

failure due to the order in which the files are compiled.

Workaround: Use Compile All when this happens.

– When working with projects that contain a high number of files, or files with very long file names, and the sum of the lengths of the file names of these files exceeds thirty thousand characters it is possible that the C linker fails to link the project. (P100002678)

Workaround: remove or shorten the names of the project files until the total length of file names are well under thirty thousand characters.

* Components

– The CAN components are always processed on each loop. This is true even when the CAN components are placed in a module and that module is not called by the main loop.

Workaround: Only use CAN components in modules that are always active each loop, such as the main module, or modules called with constant true from the main module.

– Components without output types (e.g. Hardware Input) cannot be directly connected to a class

instance. This will generate a compile error.

Workaround: Use a retype connection in between.

– Autotyped constants will not work when connected directly to Objects. This will generate a com

pile error.

Recommendation: Use a Typed constant.

– When connecting the bus output from any one of the following components: “Call Method Of Externally Defined Class”, “Call POU”, “Show Screen”, “Write applog” and “Module Bus Input” to the input bus of the “Module Bus Output” component, only the signals that are actually connected in that module will be available in the module bus. (P100002771).

Workaround: Use a dedicated bus for module connections. Do not connect it to other buses.

– The “Module Bus Input” and “Module Bus Output” components do not support bus-in-bus. Workaround: Use one module bus for each sub bus.

* Screen and Application Log

23

– In the text editor, strings longer than 509 characters in Classic Screen Editor and Application Log may not compile.

– Compatibility issues involving display projects using non-Roman fonts created in GUIDE version 3.0 may occur. It is strongly advised that the user make a backup of these files before using GUIDE 7.0 and contact the PLUS+1 GUIDE Help Desk for further information before proceeding.

– In the Vector Based Screen Editor, when working with texts using more than four input values, and the last one uses octal format and is located at the very end of a text, then that value may not be displayed correctly.

Workaround: place a space character after an input value that fulfills the above criteria.

– In the Vector Based Screen Editor, the ImageList Component has a touch behavior which does not take the size of the currently selected image into account. Instead, the whole area reserved for the ImageList will be able to receive touch events, not just the part currently used by the active image even if it is smaller than the ImageList area.

Workaround: if possible, use images of the same size in all ImageLists where touch is used

– In the Vector Based Screen Editor, when transparence has been selected by clicking on a specific pixel in an image, and that image is then scaled, it is possible that the transparent color will change. Furthermore, it is also possible when the image is scaled to a smaller size that the selected pixel position will end up outside the image.

Workaround: use images where the transparency data is part of the file format (such as .png) instead.

– In the Vector Based Screen Editor, fonts that extend beyond their width (e.g. Forte and Edwardian Script ITC in oblique mode) may be cut off when displayed on hardware, although it looks correct in the Screen Editor preview.

– In the Vector Based Screen Editor, some Unicode characters will be displayed correctly in the preview, but will then only be displayed as squares on display hardware.

– In the Vector Based Screen Editor, using copy+paste on screen definitions only works within a single project, not from one project to the next.

– In the Vector Based Screen Editor, it is not possible to compile if unused format codes exist in a text definition.

– Combined unicode characters are not supported.

   – In the Vector Based Screen Editor, automatic scaling of texts does not work. • Test Tool

– The Test Tool currently does not support arrays in the interface. Test code will be generated but the GUI does not support defining input and/or expected output of array type.

– All signals passed through the interface will be of variable type. This means that components that require constant type on an input need to have the constant set from within the tested page.

– Structural test coverage is not measured by the Test Tool. But for the graphical code in PLUS+1 GUIDE statements coverage is implicitly covered within one module.

24

– There are some rare situations when the Test Tool GUI is not updated to correctly reflect the

current status.

Workaround: exit the Test Tool and then open it again to refresh the GUI.

-What is Fixed

[P100002821] Code inside locked pages could under certain circumstances inadvertently be modified through a linked page. This is no longer possible.

[P100002777] Array signals connected as input/output for the CCP and POU components could some

times be prematurely optimized away, potentially leading to data corruption.

This only happened if all of the following specific conditions were met:

a) The CCP or POU component must be the last component using the array signal in the data flow

b) Another component placed after the CCP or POU component (alternatively the CCP/POU

itself) must use another array signal of identical type and length.

-Additionally this other array signal must not be used before, or concurrently with, the

original array signal.

-Furthermore, this other array signal must be used within a limited number of compo

nents after the CCP or POU component (HWD dependent, but typically not more than

a few hundred)

c) There is no checkpoint component connected to the array signal

d) The array signal net is not drawn backwards (from a data flow diagram point of view), and used by another component as input.

e) The array signal is not constant, i.e. it is not the output from a constant component.

This defect is now fixed.

-In previous versions of GUIDE, the simplest and safest containment action is to connect

checkpoints to each array signal used by CCP and POU components.

[P100002860] Application logs created in the vector based screen editor were not stored in a consistent way. This has now been fixed.

[P100002762] Unsupported vector based screen editor components were invisible. Now they are highlighted.

[P100002844] A regression in the handling of Structured Text code could lead to code that worked in GUIDE 6.0 no longer compiled in 6.1. This is now fixed in 7.0.

[P100002828] In some cases, already declared variables could be removed when a new function block variable was added from the code blocks tree in the Structured Text code editor. This is now fixed.

[P100002698] For very large buses, it could take several minutes to connect another bus.This has now been fixed.

[P100002757] Access levels did not work correctly for Advanced Checkpoints.This has now been fixed.

25

[P100002752] Touch is now detected correctly also when the screen definition does not begin in origo.

[P100002738] A regression preventing an array from file to end with a comma has been fixed.

[P100002673] If the P1P backup file was write protected, it could occur that both a P1X and a P1P file with same name exist at same time in project folder. This has now been fixed.

[P100002669] The error message indicating an undriven net was not shown if a Predefine type component was connected to the net.This has now been fixed.

[P100002847] An unconnected module input component made compilations fail with a difficult to understand error message. This is now fixed.

[P100002848] Error reporting for unsupported vector based screen editor features have been enhanced.

[P100002837] Files unpacked from the SYS file had their names changed to upper case. This has been fixed, and files are now unpacked using their original names.

[P100002815] It was not possible to use lower case letters in File Handle for compiled binary file. This is now fixed.

[P100002799] Structured Text compilation of code imported from exp file format generated some warnings. This is now fixed.

[P100002723] On some Windows 7 OS machines, the My Blocks folder was installed in the wrong path. This is now fixed.

[P100002792] In some cases when working with a laptop an access Violation at compile after laptop undock - dock could occur. This has now been fixed.

[P100002781] In Structured Text: Global Variables were sometimes lost after cut and paste. This is now fixed.

[P100002709] In some cases a page name change did not immediately update the GUI. This has now been fixed.

[P100002699] Multiple error messages popped up when duplicate module names were entered.This has now been fixed.

[P100002766] The error message dialog that is displayed when entering an invalid time base was not always displayed when it should, and it did not exactly specify the error. This has now been fixed.

[P100002712] Compile chain error messages didn’t show up in the error messages tab. This has now been fixed.

[P100002839] The component ’Generate Compiler Error on Range’ had an error that made it quite difficult to set the min and max values. This is now fixed.

[P100002719] In some cases when deleting a port in a bus, a segment of the bus itself could be deleted as well. This is now fixed.

26

[P100002713] Large applications using the TI compiler 5.2.5 (or older) could make the C compiler crash. This is solved by using the newer compiler TI 5.2.15, which however requires HWD support. It may also be necessary to decrease the optimization of the TI 5.2.15 compiler to medium or lower in the SYS settings in the project manager. See also [F00248] above.

[P100002542] Applications using the TI compiler 5.2.5 (or older) could take significantly longer time to compile on Windows 7 compared with on Windows XP. This is solved by using the newer compiler TI 5.2.15, which however requires HWD support. See also [F00248] above.

[P100002808] Shortcut keys F5 and F6 did not work “out-of-the-box” after installing GUIDE on a PC without any previous GUIDE installation. This has now been fixed.

[P100002801] It was not possible to create a new POU when no PLCopenXml file had been added to the project previously. This has now been fixed.

[P100002763] Read Access Level could not be set correctly for the old “Non-volatile Memory Dynamic Input” component (the one with only 1 access level setting). This is now fixed.

[P100002157] In some cases the coordinates in error messages were only referncing the affected components, and not specifically the output positions.This has now been fixed.

[P100002747] In some cases, an access violation error could occur in the hardware tree after opening an invalid project. This has now been fixed.

[P100002761] In some cases, a file named _DynamicDiagnostic.h remained in the project folder. This has now been fixed.

[P100002686] In some cases, GUIDE displayed a save changes dialog on exit that was empty. This has now been fixed.

[P100002677] The current day was in some cases difficult to read in a page property calendar edit. This has now been fixed.

[P100002269] It is no longer possible to connect a non-applog port to applog.

[P100002691] TEXTDATA.TDS showed up as a project file when the vector based screen editor as used. This has now been fixed.

[P100002721] It is no longer possible to use the data type COLOR on a Set Value component.

[P100002714] Preview of font LCD5x7e ruined later previews of other fonts.This has now been fixed.

[P100002813] When changing HWD file in a project the button to confirm the hardware comment incorrectly indicated to replace even if keep existing was selected. This has now been fixed.

[P100002819] Internal tool Create SDL failed to lock pages correctly. This has now been fixed.

[P100002840] Non-unicode fonts in projects containing unicode HWDs were generated from fonts installed in Windows; now they are generated from p1f files. An error message is given if an non-existing character in such a font is used.

27

VERSION 6.1.7 (September 2013)

-New Features and Functionality (see the GUIDE User Manual for more detailed information)

None

-Important Advisory—Potential User Issues

* Adding a perpetual Add-On product key is not possible if a time-limited with the same license ID is installed in the License Manager.

Workaround: Select the time-limited Add-On license and press Delete. Click OK to close the License Manager and enter the License Manager again. Add the perpetual Add-On product key.

-What is Fixed

[P100002698] For very large buses, it could take several minutes to connect another bus.This has now been fixed.

[P100002757] Access levels did not work correctly for Advanced Checkpoints.This has now been fixed.

[P100002777] Array signals connected as input/output for the CCP and POU components could some

times be prematurely optimized away, potentially leading to data corruption.

This only happened if all of the following specific conditions were met:

a) The CCP or POU component must be the last component using the array signal in the data flow

b) Another component placed after the CCP or POU component (alternatively the CCP/POU

itself) must use another array signal of identical type and length.

-Additionally this other array signal must not be used before, or concurrently with, the

original array signal.

-Furthermore, this other array signal must be used within a limited number of compo

nents after the CCP or POU component (HWD dependent, but typically not more than

a few hundred)

c) There is no checkpoint component connected to the array signal

d) The array signal net is not drawn backwards (from a data flow diagram point of view), and used by another component as input.

e) The array signal is not constant, i.e. it is not the output from a constant component.

This defect is now fixed.

-In previous versions of GUIDE, the simplest and safest containment action is to con

nect checkpoints to each array signal used by CCP and POU components.

28

VERSION 6.1.6 (April 2013)

-New Features and Functionality (see the GUIDE User Manual for more detailed information)

[F00152] A vector based Screen Editor has been introduced. This feature is HWD dependent.

[F00200] Licensing of function block libraries is now possible.

[F00203] When changing the SYS file in a project, all System Parameters which exists both in the new and in the old SYS file will retain their user selected values, instead of reverting to default values as in previous versions. The user will be notified about this when applicable.

[F00212] Structured Text Compiler improvements, including support for POINTER data type. In non-strict mode there is now more forgiveness from the compiler side for syntactical and semantical user errors.

[F00224] When compiling without a Toolkey in the project, a new notification message has been added that warns about a potential security issue. It is possible to disable this notification message.

-Important Advisory—Potential User Issues

* Due to new features affecting the SCS format, GUIDE version 6.0 and earlier will not open SCS files saved with GUIDE version 6.1 and later.

* GUIDE cannot handle non-Latin characters in project folder names.

* SCS files placed in the Desktop folder might not be available in the import SCS dialog

* See the following website for a workaround if you are experiencing problems accessing network locations in Windows 7: http://technet.microsoft.com/en-us/library/ee844140(WS.10).aspx

* The user must exit GUIDE to install/uninstall other GUIDE versions.

* It is advisable to complete all GUIDE processes before locking or hibernating your computer.

* PLUS+1 GUIDE is only intended to work with one single user account.

* In projects using several modules and objects, the Compile changed command can end with a failure due to the order in which the files are compiled. The workaround is to do another Compile changed.

* In the text editor, strings longer than 509 characters in Classic Screen Editor and Application Log may not compile.

* The CAN components are always processed on each loop. This is true even when the CAN components are placed in a module and that module is not called by the main loop.

* Double spacing in file names: Some issues have been found in projects where file names have double

spaces. Single spaces in file names are not known to cause any problems.

Workaround: Only use single spaces in file names.

* Components without output types (e.g. Hardware Input) cannot be directly connected to a class in

stance. This will generate a compile error.

Workaround: Use a retype connection in between.

29

* Autotyped constants will not work when connected directly to Objects. This will generate a compile

error.

Workaround: Use a Typed constant

* Compatibility issues involving display projects using non-Roman fonts created in GUIDE version 3.0 may occur. It is strongly advised that the user make a backup of these files before using GUIDE 6.1 and contact the PLUS+1 GUIDE Help Desk for further information before proceeding.

* When working with read-only P1P files it is possible to end up in a scenario where the following 3 files exist at the same time: [ProjectName].P1P, [ProjectName].~P1P and [ProjectName].P1X. This happens when a user repeatedly opens and closes to P1P, and the original P1P file is read-only. Workaround: Either make sure that the original P1P is not read-only before opening it initially, or delete the ~P1P manually.

* When working with projects that contain a high number of files, or files with very long file names, and the sum of the lengths of the file names of these files exceeds thirty thousand characters it is possible that the C linker fails to link the project. (P100002678)

Workaround: remove or shorten the names of the project files until the total length of file names are well under thirty thousand characters.

* In the Vector Based Screen Editor, when working with texts using more than four input values, and the last one uses octal format and is located at the very end of a text, then that value may not be displayed correctly.

Workaround: place a space character after an input value that fulfills the above criteria.

* In the Vector Based Screen Editor, the TouchArea Component has a priority property which can be set in the GUI, but that has no effect when used. It will be removed in future versions.

* In the Vector Based Screen Editor, the ImageList Component has a touch behavior which does not take the size of the currently selected image into account. Instead, the whole area reserved for the ImageList will be able to receive touch events, not just the part currently used by the active image even if it is smaller than the ImageList area.

Workaround: if possible, use images of the same size in all ImageLists where touch is used

* In the Vector Based Screen Editor, when transparence has been selected by clicking on a specific pixel in an image, and that image is then scaled, it is possible that the transparent color will change. Furthermore, it is also possible when the image is scaled to a smaller size that the selected pixel position will end up outside the image.

Workaround: use images where the transparency data is part of the file format (such as .png) instead.

* In the Vector Based Screen Editor, when using "curly fonts" such as Forte and Edwardian Script ITC in oblique mode, it is possible that some characters are cut off when displayed on hardware, although it looks correct in the Screen Editor preview.

Workaround: avoid using a combination of “curly fonts” and oblique mode.

* In the Vector Based Screen Editor, some Unicode characters will be displayed correctly in the preview, but will then only be displayed as squares on display hardware.

* Only one instance of the Component “Write Applog” can be used in a project. 30

* In the Vector Based Screen Editor, using copy+paste on screen definitions only works within a single project, not from one project to the next.

* In the Vector Based Screen Editor, it is not possible to compile if unused format codes exist in a text definition.

-What is Fixed

[P100002675] In some cases the Install HWD Window was too small to fully display the name of an HWD. The Install HWD Window is now resizeable. This also applies to the Install SDL Window.

[P100002674] In Structured Text, multiple VAR_IN_OUT sections in the same function header did not work correctly, This has now been fixed.

[P100002593] In some cases it was not possible to adjust line width is Design Screen page using version 6.0. This is now fixed.

[P100002637] LCD5x7 font appeared incorrectly in some cases on DPxxx hardware. This has now been fixed.

[P100002668] Document icon were sometimes not updated correctly in the project manager. This has now been fixed.

[P100002650] Empty ROP types caused compile errors that were difficult to understand. This has now been fixed by not including empty ROP types in compilation.

[P100002647] CAN RX components with protected flag set, and set to receive the same CAN ID, which are placed in different modules did not have a well defined order for capturing CAN messages in the case where multiple CAN mesages with that particular ID are received from one loop to the next. Now the order is defined as the order in which the modules are listed in the project manager.

[P100002525] Some functions of GUIDE were not compatible with conferencing with WebEx. This is now fixed.

[P100002643] In some cases the key combination Ctrl+X in the Project Manager could result in an error. This is now fixed.

[P100002472] Compile Changed did not work correctly for very large modules. This is now fixed.

[P100002613] In some cases it was not possible to disable page view on imported pages. This is now fixed.

[P100002559] A single page set to Object in one module did not compile. This is now fixed.

[P100002558] In some cases it was not possible to get out of the GUIDE drawing area. This is now fixed.

[P100002632] If the SYS file is accidentally deleted, then a bad error message was given on project open. This error message now states the name of the missing file.

31

[P100002628] Multiple instances of the same CCP method using buffered array input with different lengths did not compile. This is now fixed.

[P100002545] When opening a project created by a newer, and not compatible version of GUIDE, the error message was not easily understandable. That error message has now been improved.

[P100002611] An occasional issue where the Compare SCS comparison dialog was not possible to close has now been resolved.

[P100002580] Pressing "delete" while editing a POU name deleted the whole POU. This is now fixed.

[P100002610] In some cases it did not work to add the template. This is now fixed.

[P100002608] There was no warning when GUIDE was not run as admin. Now a warning is added.

[P100002621] In some cases when closing GUIDE with unsaved changes in a read only SCS file those changes might be lost. Now GUIDE does not close if the user expresses an intent to save that file.

[P100002571] The Screen Editor preview did not show transparent gif images correctly. This is now fixed.

[P100002570] Buttons were partly invisible in Screen Library. This is now fixed.

[P100002587] Some of the features used in the CCP tutorial no longer worked correctly in GUIDE 6.0.8. This is now fixed.

[P100002538] In some cases the Component names shown in query dialogs did not match the names for the same Components in the Component tree. This is now fixed.

[P100002575] In some cases when opening a P1P file with GUIDE an existing file on disk with the same name as a project file could be overwritten. This is now fixed.

32

VERSION 6.0.8 (December 2012)

-New Features and Functionality (see the GUIDE User Manual for more detailed information)

[F00164] Support for using a version control tool when working in GUIDE. This includes indicating which files that are source files, temporary files and other files. It also enhances the ability to work on a project with read-only files. Since this feature relies on open projects (no P1P) there is now an option to not get any Pack To P1P prompt on project close. There is now also an option to zip the project to 7z/zip without closing it. Future restriction: This feature is provided for evaluation purposes only. In future releases of PLUS+1 GUIDE this feature will be part of an additional package of features that will require an additional license to be purchased.

[F00174] A new component called “Call POU” is added to call structured text from graphical GUIDE code.

Existing or new structured text code can be added to the project and an integrated structured

text editor allows the user to edit the code from within GUIDE.

Known limitations:

-Editing of data types and global variables is not available.

-Limited support for date, time and string data types.

-Limited support for RETAIN variables. Only local variables of basic integer types in function

block POUs called directly from graphical code are currently supported.

-Some opportunities for optimization remain to be implemented.

-Avoid placing large local variables in functions, these are currently placed on the stack.

-Unicode characters can be used in comments, but double width characters may not always be

displayed correctly.

-Save As can in some cases not work correctly for a single POU where the interface has incor

rect modifications.

-Program POUs cannot be called from graphical code.

-The arithmetic overflow and underflow runtime error flags might not always be set correctly

after a POU call.

Use of this feature requires the Microsoft .NET Framework 4 (Standalone Installer). It is avail

able from Microsoft at: http://www.microsoft.com/en-us/download/details.aspx?id=17718

[F00150] Array support for CCP calls. The GUIDE user can decide if arrays should be buffered or not. This is done by either connecting constant TRUE to an input bus signal named "#Unbuffered", or not. Idl version must be 004A or higher for this feature to be available.

[F00092] It is now possible to compare two SCS files either on the complete SCS level or on page level by setting root node. The result can be shown as a combined view or as two separate views highlighting the differences. The user can then step between differences of different types. A report of the comparison result can be generated. Future restriction: This feature is provided for evaluation purposes only. In future releases of PLUS+1 GUIDE this feature will be part of an additional package of features that will require an additional license to be purchased.

[F00171] Beta: A new functionality “Dependency View” is now available. It is used to determine dependencies between different signals to detect unexpected dependencies or missing dependencies. It is intended to be used during troubleshooting or to understand what impact a change in

33

the code can have and to prove that no unexpected dependencies exists for safety critical signals. Future restriction: This feature is provided for evaluation purposes only. In future releases of PLUS+1 GUIDE this feature will be part of an additional package of features that will require an additional license to be purchased.

[F00145] Beta: A new functionality “GUIDE to Simulink S-Function” is now available. It is used for converting a subset of a PLUS+1 GUIDE project to a Simulink S-Function. Future restriction: This feature is provided for evaluation purposes only. In future releases of PLUS+1 GUIDE this feature will be part of an additional package of features that will require an additional license to be purchased.

-Important Advisory—Potential User Issues

GUIDE cannot handle non-Latin characters in project folder names.

-What is Fixed

[P100002499] Missing signals in bus could sometimes be reported when compiling even though the signals actually did exist. View logical net did not work either for these signals. This has now been fixed.

[P100002493] View Logical Net window could in some cases be too big for the monitor it was displayed on. This has now been fixed.

[P100002505] It was sometimes not possible to reopen compiler messages from toolbar. This has been fixed.

[P100002453] The "Next/Previous Page" functionality could slow down GUIDE after some time of usage. This has been fixed.

[P100002002] It is now possible to change the HWD used in a project even if the API-specification is opened

[P100002117] Using CCPs where a single method has a huge argument list now works

[P100002483] Starting GUIDE while a function block PDF file is open now works.

[P100002369] Illegal numerical values in screen object properties can no longer corrupt a screen page.

[P100002292] Infinite loop across bus: bus members connecting back to top level caused GUIDE to hang up. This has been fixed.

[P100002431] File times are now preserved when unpacking the SYS file during compile.

[P100002415] Typed constants in Application Log will now be output correctly to the log.

[P100002347] Array signals in module busses are now handled correctly.

[P100002379] A corrupt DDT file no longer prevents a GUIDE project from being opened.

[P100002352] Negative S8 values from NV memory on TI platform are now interpreted correctly

34

[P100002395] Spaces now appear correctly on the screen and the display when the font has been reinstalled in the PLUS+1 GUIDE, deleted from the project and added to the project again. [P100002324]

[P100002416] App log texts no longer lose their data values when the format code is changed.

[P100002351] Assigned font no longer disappears when the screen editor is entered.

[P100002334] Signal for Y coordinate is retained when a line is copied.

[P100002333] Long Text in DP600 application now shows up correctly

[P100002337] Undo now works correct in Page Interface Editor

[P100002418] Missing Windows library Nor maliz.dll is now detected when opening a P1P file.

[P100002402] GUIDE compile chain now supports multiple application diagnostic data structures.

[P100002387] Header file for CCPs are now removed on project pack.

[P100002384] Remaining time for expired licenses is now reported correctly.

[P100002079] The code generated from the switch component is now terser.

[P100002380] Confile.exe now reports an error if the input file is missing.

[P100002307] The License Manager window could stop working when starting GUIDE without a license and then later reopening the License Manager, this has now been fixed.

[P100001307] Hardware Input/Output needed to have a connection on the output side in order to compile. This has now been fixed.

[P100002328] The Read Application Log symbol generated a very difficult to find error if an incorrect Application Log name was used. This has now been fixed with an error message that is displayed earlier in the compile process.

[P1dev00001315] Using some of the graphical themes of Windows 7, the text of the Project Management Utility was sometimes not fully visible. This has now been fixed.

[P100002406] When GUIDE was not started in maximized mode, the Compiler Messages window was displayed incorrectly in some cases. This has now been fixed.

[P100002396] The Warning message that is shown when installing fonts was not shown in some cases where it should have been shown. This has now been fixed.

[P100002375] Naming in application log pages has been corrected

[P100002374] Old application log area name changes are now reflected in the area selection dialog

[P100002373] When entering an Application Log page after its assigned area had got a new name there was an access violation. This has not been fixed.

[P100002358] Assign Application Log area popup menu is no longer available when an Application Log area page is already selected.

35

[P100002371] Edit menu items can now be used when editing texts in the screen editor.

[P100002339] Change of the value on a constant symbol was sometimes ignored when using Windows 7. This has now been fixed.

[P100002297] GUIDE was not always possible to activate using Alt+Tab. This has now been fixed

[P100002311] While adding components in GUIDE, the toolbar and menus were not accessible. This has now been fixed.

[P100002295] In some cases an access violation error was thrown by the SCS viewer. This has now been fixed.

[P100002385] Some bus member names that are normally allowed were not allowed if the bus was connected to a screen page. This has now been fixed.

[P100002435] GUIDE Screen Editor could not import Double Byte Character Set fonts as Unicode. This has now been fixed.

[P100002515] Unicode fonts were not processed correctly. This has now been fixed.

[P100002510] Very old screen pages cannot be entered in more recent versions of PLUS+1 GUIDE. In order to be able to enter such screen pages, the following workaround must be performed: 1. Open the project in 4.0.3. 2. Visit all screen pages. 3. Save the project.

36

VERSION 5.1.10 (May 2012)

-What is Fixed

[P100002292] Infinite loop across bus: bus members connecting back to top level caused GUIDE to hang up. This has been fixed.

[P100002337] Undo now works correct in Page Interface Editor

[P100002324] Spaces now appear correctly on the screen and the display when the font has been reinstalled in the PLUS+1 GUIDE, deleted from the project and added to the project again. (P100002395)

[P100002416] App log texts no longer lose their data values when the format code is changed.

[P100002351] Assigned font no longer disappears when the screen editor is entered.

[P100002334] Signal for Y coordinate is retained when a line is copied.

[P100002333] Long Text in DP600 application now shows up correctly

[P100002415] Typed constants in Application Log will now be output correctly to the log.

[P100002347] Array signals in module busses are now handled correctly.

[P100002352] Negative S8 values from NV memory on TI platform are now interpreted correctly

[P100002431] File times are now preserved when unpacking the SYS file during compile.

[P100002379] A corrupt DDT file no longer prevents a GUIDE project from being opened.

37

VERSION 5.1.9 (November 2011)

-Important Advisory—Potential User Issues

If an ActiveX registration error is displayed when starting PLUS+1 GUIDE in Windows 7, select the properties for the PLUS+1 GUIDE shortcut and enable “Run this program as an administrator” in the Compatibility tab.

Display applications containing images with an unsupported color depth will no longer compile in version 5.1, this is done to avoid unexpected behavior in the display. The image will be updated to default color depth when inspected in the image repository, by this only supported color depth will be used and the application will be able to compile.

-What is Fixed

[P100002301] Connecting the Y-coordinate of an image to a signal now works correctly.

[P100002302] The correct default font name is now applied on Text lists in Screen Editor.

[P100002308] Screen Editor texts with multiple lines are now displayed correctly in the layout pane.

[P100002306] Problems upgrading from a 4.x license have been resolved.

[P100002329] Export text in Screen Editor now works correctly.

[P100002332] When new GUIDE applications using Read Only Parameter (ROP) are created in 5.1.8, the method described in the manual will not work. No ROP template file iscreated on first compile. This has now been fixed.

38

VERSION 5.1.8 (September 2011)

-New Features and Functionality (see the GUIDE User Manual for more detailed information)

Compile speed is improved. Depending on the project and the PC that is used, the average compile speed increases 10%–100%. Large display projects with many images now compile much faster.

[F00093] A System ID can be embedded in a GUIDE application. The Service Tool program uses the embedded System ID to automatically open a P1D file with a matching System ID.

[F00101] The Screen Editor now supports Unicode fonts. All display projects now store text in a Unicode format.

A user upgrading a Screen Editor project to GUIDE 5.1 must select a code page for each language that is used in their project. Code pages choices are 1250–1257 (Latin 2, Cyrillic, Latin 1, Greek, Turkish, Hebrew, Arabic, Baltic) and 874 (Thai).

Combined Unicode characters are only supported in cases where precomposed Unicode character forms exist. This can for example affect languages such as Hebrew, Thai and Arabic. An HWD is required to provide Unicode support for new projects that display such languages as Japanese, Chinese, and Korean.

[F00128] The compiler now supports Sauer-Danfoss SC controllers.

[F00129] A user can now rename a P1P file and then open it with the GUIDE program.

The “Save Project As” command now works without a user first having to use the “Save Project” command. Previously, a user had to save changes into their current project before they could save these changes into a new project.

[F00136] An input field in the Screen Editor’s Inspector panel now holds a new value when the cursor moves out of the input field. Previously if the cursor moved out of the input field, the input field returned the old value.

[F00140] The Screen Editor’s Screen Library tab no longer requires a folder for images.

[F00143] The User Messages panel in the Compile Progress dialog box now lists a count of View Disabled pages and Read-only pages. (Show Compiler Statistics in the Options dialog box must be checked to display the page count.)

-Important Advisory—Potential User Issues

Upgrading a GUIDE project to GUIDE 5.1 is a one-way process. Once a project is upgraded to GUIDE 5.1, it cannot be opened by earlier versions of the GUIDE program.

Projects containing objects saved with GUIDE versions4.0 or earlier must be compiled before they can be saved as P1P files.

See the following website for a workaround if you are experiencing problems accessing network locations in

Windows 7:

http://technet.microsoft.com/en-us/library/ee844140(WS.10).aspx

39

The user must exit GUIDE to install/uninstall other GUIDE versions.

It is advisable to complete all GUIDE processes before locking or hibernating your computer.

Compatibility issues involving display projects using non-Roman fonts created in GUIDE version 3.0 may occur. It is strongly advised that the user make a back-up of these files before using GUIDE 5.1 and contact the PLUS+1 GUIDE Help Desk for further information before proceeding.

PLUS+1 GUIDE is only intended to work with one single user account.

In projects using several modules and objects, the Compile changed command can end with a failure due to the order in which the files are compiled. The workaround is to do another Compile changed.

In the text editor, strings longer than 509 characters in Screen Editor and Application Log may not compile.

-What is Fixed

[P100002163] In big applications, GUIDE could sometimes crash or corrupt the source file when pasting large graphical blocks, this has now been fixed. (P100002271)

[P100002202] Renaming bus member variables, sometimes made GUIDE to hang up, this has now been fixed.

[P100002142] In an Array without end parenthesis the compilation was successful but the last value was interpreted wrong, now an error message is given.

[P100002242] In some cases the use of the Repeat-Until components gave an error in the compilation, this has now been fixed.

[P100002196] The page numbering in a project has been fixed, some projects was showing the same page number on two different pages. The page numbering is now according to the execution order.

[P100002139] Issues related to the designs with Application Log has been fixed (P100002141)

[P100002149] Export/Import text in Screen editor can now handle commas

[P100002176] Issues with editing the Page interface of a Screen editor page and then leave the Screen page has been resolved.

[P100002088] In previous version 5.0, A “Compile changed” always resulted in that all C-files were compiled, this has now been fixed.

[P100002110] Application Log write bit now only accepts Boolean as a data type.

[P100002166] It is now possible to connect a constant array to the component “Write Array to File” (entry A2)

40

[P100002093] The default layout now also reflects the Toolbar

[P100001527] Temporary files in the project folder are now removed also from projects with Read Only Parameters.

41

VERSION 5.0.9 (January 2011)

-What is Fixed

* Issues related to reading PC information in the License Manager have been fixed (GetMacAddress failed). [P100002130]

* GUIDE Screen editor now imports 8-bit images with correct palette information [P100002123]

* In the GUIDE Screen editor, the Screen Manager occasionally showed text order incorrectly or hung up; this issue has now been fixed. [P100002131] [P100002132]

42

VERSION 5.0.8 (December 2010)

-New Features and Functionality (see the GUIDE User Manual for more detailed information)

* The License Manager now supports re-hosting and subscription services.

* The License Manager User Manual is available via Tools menu > License Manager > Help.

* Note: PLUS+1 Tools products supported by License Manager version 4.x are not compatible with version 5.x [F00098]

* Support has been enhanced for imported compiled code libraries. The user can now add a code library to a project that has been developed outside GUIDE, e.g., C language. The graphical application can call the objects and thus data can be passed to/from the objects. This feature is HWD dependent. [F00059]

* Added the Application Keying component to give users the ability to lock a specific application to hardware. [F00125]

* It is now possible to use bus member names, port names, page names and namespaces longer than 16 chars. [F00124]

* Several Screen Editor improvements [F00105]:

– A new sorting order in Screen Manager has been introduced. This change shows the stacking order of objects and makes drag and drop objects possible.

– In the Screen Manager tab, when right-clicking a variable-expansion (the variable expanded with the object it is connected to) in the connected Data bus, an Edit option has been added.

– Improved support for multi selection function has been added.

– When selecting multiple objects in the Screen Page Layout pane/Screen Manager, It is now possible to move objects using arrow keys.

– Improved support for starting dialogues with default values has been added. – Automatic choice of HW Ports (when applicable) has been added.

– Automatic increase of screen area that occupies the whole port area has been added (when applicable).

– Dialogues have been changed to use standard Windows buttons

– Improved use of the Tab-key function has been added.

– Auto scroll has been added to Screen Manager and Screen Library.

* The 64 bit version of Windows 7 is now supported. [F00063]

* The icons have been updated and large icon support has been added. [F00123]

* The white color scheme has been updated. [F00116]

* Shortcuts for Compile All, Compile Changed, Error Check All, Error Check Changed, Break Reference Link to Page and Page Interface Editor have been added. [F00103]

43

* Additional compiler support for Displays has been added. [F00054]

* Additional download support for Displays has been added. [F00099]

* Encode 8 has been updated. It is now possible to output arrays longer than 8 positions. Also, the generated C-code is more compact than previously. [F00110]

* Support for graphical terminal applications that were created before the Screen Editor became available have been removed. [F00122].

-Important Advisory—Potential User Issues

* See the following website for a workaround if you are experiencing problems accessing network locations in Windows 7: http://technet.microsoft.com/en-us/library/ee844140(WS.10).aspx

* Due to new features affecting the SCS format, GUIDE versions 4.3 and earlier will not open SCS file types created with GUIDE versions 5.0 and later.

* Due to new features affecting the project format, GUIDE versions 4.1 and earlier will not open P1X/P1P files created with GUIDE versions 4.3 and later. GUIDE version 4.2 will open projects created with 4.3 with a warning message (if enabled)

* Projects containing objects saved with GUIDE versions 4.0 or earlier must be compiled before they can be saved as P1P files.

* The user must exit GUIDE to install/uninstall other GUIDE versions.

* It is advisable to complete all GUIDE processes before locking or hibernating your computer.

* Do not rename GUIDE P1P/P1X files outside of the GUIDE program. Only rename projects using the GUIDE Save Project As... function.

* Compatibility issues involving display projects using non-Roman fonts created in GUIDE version 3.0 may occur. It is strongly advised that the user make a back-up of these files before using GUIDE 4.3 and contact the PLUS+1 GUIDE Help Desk for further information before proceeding.

* PLUS+1 GUIDE is only intended to work with one single user account.

* In projects using several modules and objects, the Compile changed command can end with a failure due to the order in which the files are compiled. The workaround is to do another Compile changed.

* In the text editor, strings longer than 509 characters in Screen Editor and Application Log may not compile.

-What is Fixed

* Several fixes to the User Manual have been implemented. [P100002061], [P100002060], [P100002040], [P100002038], [P100002054], [P100001971], [P100001940], [P100001777], [P100002068]

* Performing many changes when working with large display projects sometimes caused a critical error. This has now been fixed. [P100002011]

44

* Under certain circumstances a compiler error could occur in a large application that uses a Compiled Code Package (CCP). This has been fixed [P100002058].

* The Shift Left and Shift Right components can malfunction when the number of positions to shift is variable and is greater than number of bits in the data type. This error affects MC hardware [P100002051] and has been fixed.

* The Get Array Element component did not typecast to data type S8 (the User Manual described this error). This has been fixed. [P100002071].

* The Arithmetic/Boolean Switch, Connect, Memory and Retype components has been changed to typecast to data type U8 and S8. This affects MC hardware [P100002090].

* Dynamic NV components with data types U8 or S8 now work correctly in projects that uses MC hardware, [P100001799]

* Error handling has been improved when renaming a P1P file and opening it. [P100001644]

* The result of renaming a screen area in an area page is now handled in a more user friendly way. [P100001967]

* Issues with having the API document from the HWD opened for viewing while exchanging the SYS-file have now been resolved. [P100002002]

* An error message is now presented if more than 20 format codes are used in a string for displays or application log. [P100001970]

* When using Query in the Module Viewer, the focus is now kept to the Module Viewer [P100002041]

* Issues involving applications that contains pages with a page name longer than 16 chars have been fixed. [P100001607] [P100001491] [P100001587]

* Array constants can now handle more than 48 characters. [P100001848]

* Improved detection of not supported component versions [P100001862]

* The boundary output on the Switch 16 Capped component only worked when connected to another boundary output. Otherwise a compiler error was generated. This has been fixed [P100001821]

* On the Advanced Checkpoint component there was no check to see if the input was constant or not. This has been fixed. [P100002067].

* Forward/Backward functionality has been fixed to function as standard applications. [P10000195]

* Undo/Redo functionality in Screen Editor-Text/Image Register is now removed. Before it performed erroneous operation. [P100001991]

* Changing language in a display application in the Screen Editor has been sped up significantly. [P100001978]

* Moving multiple Screen Editor objects with the snap to grid option on now only snaps to the object with the lowest order. The other objects keep their relative positions. [P100002014]

45

* Mouse wheel scrolling now works when a dialogue contains a vertical scrollbar. [P100001960]

* Navigations within Screen editor pages using the Page Navigator now works correct when leaving pages. [P100001939]

* Working with images in a copied folder containing images in a screen editor screen library previously created an error. This has now been resolved [P100002032]

* Mouse wheel zoom problems when using a second monitor have been fixed. [P100001791]

* The Error Messages tab displays compiler error messages. When a user clicks a compiler error message caused by an error within a view-disabled page, the closest view-enabled parent page displays along with an appropriate message. [P100000901].

* An un-docked Inspector is now working correctly. [P100001934]

* When canceling an Installation of HWD’s, (i.e. not overwrite) the user information was misleading, this has now been fixed. [P100002031]

* When adding images in screen editor, the default color depth is now controlled from the HWD. [P100002070]

46

VERSION 4.3.7 (April 2010)

-What is Fixed

* The TI compiler, version 5.2.2, has been replaced with version 5.2.5 [F00108]

* Issue with transparency and monochrome bitmaps has been fixed. [CQ100002000]

* Linked pages using a bus with same name on wire and sub-bus now compiles. [CQ100001995]

* Issues with access levels and Checkpoints and Set value/pulse components have been fixed. [CQ100001993]

* Several issues with Compiled Code Packages have been fixed. [CQ100002003] [CQ100002008] [CQ100002007]

* Screen Editor options File Transparency and Visible were not able to uncheck, this is now fixed. [CQ100002012]

* The Screen Editor preview for grayscale images has been fixed. [CQ100002021]

* In the Screen Editor a conversion from an image with palette to an image without palette now works. [CQ100002024]

* Component Limit has been replaced in Component tree to resolve compatibility issues with older versions of this component. [CQ100001918]

47

VERSION 4.3.6 (February 2010)

-New Features and Functionality (see the GUIDE User Manual for more detailed information)

* PLUS+1 GUIDE now runs on Windows 7 (32-bit).

* A new version of the TI compiler, version 5.2.2, is now supported. This compiler will be introduced in HWD files. This feature is HWD dependent. [F00053]

* A new component to read out Application Log data into arrays. This feature is HWD dependent. [F00058]

* A new component to write arrays to USB memory stick. This feature is HWD dependent. [F00057]

* User settings will now be automatically imported from the previously installed version. When editing a GUIDE project, it is now possible to choose to remove files instead of deleting them from the project. In previous versions it was only possible to delete files from the project folder with remove command. the files will now be removed from the project but remain in the project folder. [F00072]

* The project will now always include the API document from the HWD/SYS. [F00071]

* In Screen Editor; The user can now perform Move To Back and Move To Front on objects in the screen. [F00079]

* The install of Hardware and Function Libraries has been improved. Multiple files can be installed with one action. The user can also select which files within a PAC file to install. [F00080]

    * Shortcuts: Leave Page, Zoom In and Zoom Out are now also working in the screen editor. [F00074] -Important Advisory—Potential User Issues

* See the following website for a workaround if you are experiencing problems accessing network locations in Windows 7: http://technet.microsoft.com/en-us/library/ee844140(WS.10).aspx

* Due to new features affecting the project format, GUIDE versions 4.1 and earlier will not open P1X/P1P files created with GUIDE versions 4.3 and later. GUIDE version 4.2 will open projects created with 4.3 with a warning message (if enabled)

* Projects containing objects saved with GUIDE versions 4.0 or earlier must be compiled before they can be saved as P1P files.

* The user must exit GUIDE to install/uninstall other GUIDE versions.

* It is advisable to complete all GUIDE processes before locking or hibernating your computer.

* Do not rename GUIDE P1P/P1X files outside of the GUIDE program. Only rename projects using the GUIDE Save Project As... function.

* Compatibility issues involving display projects using non-Roman fonts created in GUIDE version 3.0 may occur. It is strongly advised that the user make a back-up of these files before using GUIDE 4.3 and contact the PLUS+1 GUIDE Help Desk for further information before proceeding.

* PLUS+1 GUIDE is only intended to work with one single user account.

48

* In projects using several modules and objects, the Compile changed command can end with a failure due to the order in which the files are compiled. The workaround is to do another Compile changed.

* In the text editor, strings longer than 509 characters in Screen Editor and Application Log may not compile.

-What is Fixed

* Miscellaneous updates and clarifications have been added to the user manual. [P100001794] [P100001804] [P100001802] [P100001875] [P100001846]

* In some complex page structures, links to Referenced Pages were erroneously broken. This has been corrected [P100001805]

* Unconnected Connect Nets from Objects now generates correct code. [P100001819]

* Moving folders or moving images/texts in folders in Screen Editor sometimes corrupted the image/text ID and/or settings were lost. This has now been fixed [P100001912] [P100001909] [P100001913]

* Odd numbers of the length of data in a Read Only Parameter file for Displays now work. [P100001822]

* The installation size in Microsoft Windows’ Add/Remove Programs is now correctly reported. [P100001656]

* Improvements has been made when working with large projects that potentially run out of memory [P100001891]

* Using brackets in image names in display projects now works. [P100001783]

* It is now possible to import text containing commas in the Screen Editor (display projects and application log). [P100001792]

* Issues have been fixed with texts containing only characters (%c) [P100001827]

* It is no longer possible to erroneously exit a bit map setup in Screen Editor without setting transparency [P100001906]

* Previously, when the Module viewer was opened, the drawing was zoomed out, the Module viewer now opens the drawing correctly. [P100001814]

* Changing components from group Counters with Query, to specific component Loop Counter with Carry now works correctly. [P100001782]

* It is now possible to double click on an LHX ReadMe file and have it opened by the correct Microsoft Windows associated software. [P100001842]

* Compile changed now works after diagnostic data has changed. [P100001894]

* “ModuleConnectionLog:Enabled” now works in projects using the screen editor. [P100001904]

49

VERSION 4.2.6 (June 2009)

-New Features and Functionality (see the GUIDE User Manual for more detailed information)

* The component Initialize Hardware Output can now be connected to components within a component group; Non Volatile memory dynamic. Previous, it was only possible to connect to constants. For example, this feature enables the same application to have the same node ID as a parameter. Note: it is the user’s responsibility to take care of non initialized non volatile memory cells. Some older Display HWD’s do not support this feature.

* Full color support for displays. This feature enables displays to work with higher color depth. With this feature the colors are taken from the image and there will be no separate palette. This also enables a better preview for both color and monochromatic images, thus it is easier to design. This feature is HWD dependent.

* Supports the possibility for the user to add precompiled code that is executed by the operating system. This feature is HWD dependent.

* Design speed has been improved (enter screen pages)

* It is now possible to directly access the PLUS+1 Support Web Page and launch Remote Desktop from the Help Support menu.

-Important Advisory—Potential User Issues

* Due to new features affecting the project format, GUIDE versions 4.1 and earlier will not open P1X/P1P file types created with GUIDE versions 4.2 and later.

* Projects containing objects saved with GUIDE versions 4.0 or earlier, must be compiled before they can be saved as P1P files.

* The user must exit GUIDE to be able to install/uninstall other GUIDE versions.

* It is advisable to complete all GUIDE processes before locking or hibernating your computer.

* Do not rename GUIDE P1P/P1X files outside of the GUIDE program. Only rename projects using the GUIDE Save Project As... function.

* Compatibility issues involving display projects using non-Roman fonts created in GUIDE version 3.0 may occur. It is strongly advised that the user make a back-up of these files before using GUIDE 4.2 and contact the PLUS+1 GUIDE Help Desk for further information before proceeding.

* PLUS+1 GUIDE is only intended to work with one single user account

* In projects using several modules and using objects, the Compile changed command can end with a failure because of what order the files are compiled. The workaround is to do another Compile changed

-What is Fixed

* In Screen Editor – in an Area page the order was not saved or loaded when doing Undo/Redo, this is now fixed. [P100001736]

50

* In Screen Editor – Undo/Redo now reflects order in Area pages [P100001736]

* In a display project – If the project contained an image with the same name as the project, the compilation failed with an error message that was hard to interpret, this has now been fixed. [P100000974]

* In a display project – In the selector when copy and paste text folders, the text inside the pasted folder were not correct, this has now been fixed. [P100001770]

* The preview feature of the screen editor will now show black text on white images correctly. [P100001652]

* Better error handling in cases of an application using objects but the hardware file (SYS) in the project doesn’t support it. [P100001216]

* Changes in an array constant file will now be detected by a Compile changed command. [P100000628]

* Validation of array values in Multi-character constant component has been fixed [P100001663]

* Validation for maximum length of Application ID:Description/Type/Version naming has been introduced. [P100001733]

* Component Non-volatile Memory Dynamic Input is now correct when it is changed by Query from some other component in the group Non-volatile Memory Dynamic [P100001711] [P100001238]

* It is now possible to access the GUIDE from the taskbar or using Ctrl-Tab when one or more Module viewers were started. [P100001769]

* The component Accessrights App Log Statistics has now the correct name in Component tab, preview and in the graphical source. [P100001157]

* In the screen editor it is now possible for the user to right click and delete text/image list objects. [P100001722]

* It is now not possible to drag in scs files/blocks from the Hardware tab if the project has no hardware. [P100001697]

* Improvements have been made to better support GUIDE when being used on 2 monitors. [P100001704]

* In screen editor in the Screen Library tab in Selector, the preview now shows transparency correctly. [P100001717]

51

VERSION 4.1.7 (April 2009)

-Important Advisory—Potential User Issues

* If the patch does not install correctly and 4.1.6 is still your current version, first reinstall version 4.1.6 and then install the 4.1.7 patch.

-What is Fixed

* Page Name and Namespace properties for a page can now be changed regardless of linked sub-pages. [P100001698]

* Application log port pages can now have names other than the default name. [P100001703]

* The graphical editor has been enhanced to allow the pasting and loading of blocks into large applications. A warning message has been introduced to avoid out of memory situations in large applications. [P100001710]

* Applications containing very complex bus and wire hierarchies would occasionally not compile. This has been fixed [P100001712]

52

VERSION 4.1.6 (January 2009)

-New Features and Functionality (see the GUIDE User Manual for more detailed information)

* The feature Page View Access has been extended.

* It is now possible to perform Force Enable/Read-Only/Disable operations. Because of this feature the SCS format has changed.

* Object Support for Advanced Checkpoint with Namespace and all Non-Volatile Memory Dynamic Components has been added.

* Compilation speed is improved; up to 20% faster.

* Design speed is improved (enter pages, insert blocks, etc)

* Startup speed is improved Module (SCS) file size has been reduced.

* Two new Page View Access settings have been added to options tab

* An unnecessary window has been eliminated when adding new wire/bus-port.

* When exiting the screen editor, the prior state of the Manager tab is now retained.

-Important Advisory—Potential User Issues

* Due to new features affecting the SCS format, GUIDE versions 4.0 and earlier will not open SCS file types created with GUIDE versions 4.1 and later. It is also possible that earlier version may not recognize the 4.1 files as older SCS files.

* The Component Insert Array Elements has been corrected. In previous versions the case where input A4 was larger than the number of elements in input A3, the missing elements were omitted. Now the missing elements are inserted as zeros (up to maximum length of A4).

* Projects containing objects saved with earlier versions need to be compiled before they can be saved as P1P files.

* When attempting to install or uninstall a new version of GUIDE while another version of GUIDE is running, a message may tell the user to exit a version of GUIDE that is not running. The user must exit any version of GUIDE to be able to install/uninstall.

* It is advisable to complete all GUIDE processes before locking or hibernating your computer.

* Do not rename GUIDE P1P/P1X files outside of the GUIDE program. Only rename projects using the GUIDE Save Project As... function.

* Compatibility issues involving display projects using non-Roman fonts made in GUIDE version 3.0 may occur. It is strongly advised that the user make a back-up of these files before using GUIDE 4.1 and contact the PLUS+1 GUIDE Help Desk for further information before proceeding.

-What is Fixed

* The following error messages have been improved;

53

– when an input of an object page is not connected [P100001566]

– when multiple pages contain same area name. [P100001487]

– now case sensitive for signal names [P100001547]

– when access levels on Bios signals [P100001505]

* Occasional errors when using the Next/Previous Arrows in the GUI caused exception errors. This has been corrected [P100001601]

* “Error check all/changed” now functions when objects are in the project. [P100001554]

* An error message is now generated when the “Set Pulse” component output is connected to other component outputs. [P100001613] [P100001615]

* In texts in the text editor, if a user uses a quotation mark [“] it will automatically be converted to a [\”], this method will prevent an error in the compilation. [P100001409]

* Occasionally the Project Manger/Navigator tabs and/or some tool buttons were not visible, this has been fixed. [P100001605] [P100001606]

* Under some circumstances there were problems compiling display projects; no LHX file was generated. This has now been fixed [P100001637]

* A U32 variable can now be retyped to the COLOR data type. [P100000888]

* When the application attempts to use more than the available amount of NV-memory, the compilation is now aborted with an error message. [P100001541]

* When using Save Project As..., the GUI will warn the user that the project must to be saved before the operation can be performed. [P100001496]

* Fonts with numbers at the beginning of the font name will now be corrected [P100001116]

* Problems related to the screen editor when changing to another type of display hardware has been corrected. [P100001537]

* Changes made by user in Icon Menu will now remain changed [P100001546]

* Issues with starting the Icon Menu while the auto save is in operation have now been fixed [P100001552]

* In Page Navigator Window the Forward and Backward arrows now work [P100001321]

* Operating issues involving screen saver functions have been corrected [P100001526]

* Instances involving the screen editor indicating a change even if no change was made has now been corrected [P100000561]

* It is now possible to use Save as... on document Tech info Controllers in Selector. [P100001532]

* The Screen editor inspector default size has been adjusted to accommodate all properties. [P100001533]

* After deleting a screen area in a screen editor layout panel, the screen area will now be updated correctly [P100001542]

54

* In screen editor the “Y” field is now correct for line objects. [P100001600]

* In screen editor, for text lists and image lists, the inspector window now shows values on properties like “AutoIndex” ,“Color”, etc. [P100001603]

* Grid settings are now saved when exiting GUIDE [P100001497] When using multi screen environments, GUIDE is now opened on the 2nd monitor if it was closed there. [P100000229]

* Using the option to make module connections visible for the Service Tool did not work, this has been fixed [P100001632]

* The last used preview font in screen editor is now saved [P100001545]

55

VERSION 4.0.3 (October 2008)

-What is Fixed

* Some defects in GUI – SCS format changed. [P100001575]

* Compile sequence error is not always reported and make job does not terminate correctly. [P100001613]

56

VERSION 4.0.2 (June 2008)

-New Features and Functionality (see the GUIDE User Manual for more detailed information)

* This version supports Application keying

* The user can now lock pages to prevent viewing.

* GUIDE now supports Multiple Application Log Files. Require support from HWD

* GUIDE now supports Multiple Read Only Parameter Files. Require support from HWD

* New Repeat-Until, Loop Counter and Time measurement components

* Support for text variable Qa NS for as NameSpace property container (like Qa PAGENAME).

* In My Blocks tab it is now possible to define a link to a folder.

* It is now possible to select a page (Enter, Stretch, Query etc) by clicking inside its boundary box.

* Forward and backward arrow added in the Toolbar, also on keys Alt+Right/Left and Mouse’s where

supported. The forward and backward function controls the navigation in pages.

* In Options it is possible to enable Auto-generation of interface ports to/from the Page Interface Editor.

* The SYS file and the template can be added by right click functionality.

* It is now possible to use different text font styles in module files (scs)

* . In Options it is possible to enable warning messages to warn the user about conflicting file formats.

* Memory on different file browser dialogues

* When adding signals in Screen Editor the Drop down list is in Alphabetic order.

* Possible to add files to project that already is in project folder.

* Possibility to copy text from Compiler Messages windows by right click in the window.

* Print dialogue options have been enhanced.

* Error Messages have been enhanced.

* GUIDE installs default in a new folder structure containing the version.

* In Options it is possible to disable zoom on mouse wheel.

* In Options it is possible to enable zoom fit to page after leaving the Page Interface Editor.

* In Options it is possible to enable partial compiler statistics.

-Important Advisory—Potential User Issues

* The CAN components are always processed on each loop. This is true even when the CAN components are placed in a module and that module is not called by the main loop.

57

* When installing an older version of GUIDE, the program will not automatically uninstall the current version (4.x and later). The current version of GUIDE must be manually uninstalled. This is done by using Add/Remove Programs in the Windows Control Panel.

* Double spacing in project file names: Some issues have been found in projects where file names have double spaces. Single spaces in file names are not known to cause any problems. Work-around: Only use single spaces in project file names (CQ P100000374).

* Components without output types (e.g. Hardware Input) cannot be directly connected to a class instance. This will generate a compile error. Work-around: Use a retype connection in between.

* Autotyped constants will not work when connected directly to Objects. This will generate a compile error. Work-around: Use a Typed constant

* Old display applications (not using the screen editor) will not work in this version. Please contact the Sauer-Danfoss Help Desk.

* The linked page feature must not be used with older HWDs. For each released HWD, the table below lists the versions that do not work:

– MC24-10: 10101528v150 and older – MC24-20: 10102117v120 and older – MC50-10: 10101674v150 and older – MC50-20: 10102569v110 and older – DP600: 10102102B and older

– DP610: 10102903B and older

-What is Fixed

* Error Check works correct, without forcing a Compile first. [P100001319]

* Switch time bases now works correct. [P100001393]

* After undo in Screen Editor, objects are now displayed in correct. [P100001394]

* Screen capture now works correct [P100001402]

* Default layout now works correct [P100001404]

* It is now possible to drop a Text in a Text List on the Screen Area also if it is zoomed in. [P100001344]

* It is now possible to mark (High light) an Image List also if images are marked. [P100001311]

* Unconnected output of Add Capped symbol causes compile to fail, has been corrected [P100001332]

* Page Navigator now shows linked pages correctly [P100001416]

* Problems with updating graphics when shifting between normal and maximum window are now fixed

[P100001381, P100001258, P100001310]

* Adding a non-linked page does not show icon for linked page; refresh no longer needed[P100001460]

58

* The Manager/Inspector and Selector windows retracts correct [P100001372, P100001377]

* Having an open project but all modules closed, the component selector have no been disabled [P100001397]

* An issue updating the Page Navigator have been corrected [P100001398]

* When drawing area is empty and open a module from Project Manager is now working correct [P100001399]

* After closing and reopening a module, some commands didn’t work correct, this has been fixed [P100001400]

* Change template file name form is always shown when replacing a template [P100000819]

* Compiler messages are always hidden after a successful compile if it was hidden when the compile started [P100001309]

* A situation when exiting screen editor and clicked exit button twice, could sometimes caused an error, this has now been fixed [P100001407]

* Mouse wheel now only zooms when mouse pointer is on drawing area [P100001428]

* Errors in generated Data Template for Read Only Parameters have been corrected [P100001251]

59

VERSION 3.2.5 (April 2008)

-What is Fixed

* Some large display application did not compile a LHX file; this have been resolved (P100001437)

* It is now possible to compile an object inside a module other than the main module (P100001432)

60

VERSION 3.2.4 (January 2008)

-New Features and Functionality (see the GUIDE User Manual for more detailed information)

* Enhanced error messages.

* New Set Pulse component.

* New Array Constant from Binary File component.

* Upgraded Page Interface Editor now has the same look as the main PLUS+1 GUIDE window.

* The SCS Viewer now has a Menu and Toolbar. It is also possible to do a Query as in Editor mode but the properties cannot be edited.

* A Print window replaces the Plotter Output Setup window. Use the mouse scroll wheel to zoom in and zoom out.

* Classic, Windows and Custom short cut key schemes.

* The Transfer between Pages feature is available from menu and custom short cut keys

* . Some components that were restricted to use in Objects now work in Objects (see User Manual for details). Objects inside Objects now work.

-Important Advisory—Potential User Issues

* The CAN components are always processed on each loop. This is true even when the CAN components are placed in a module and that module is not called by the main loop.

* Buses should not be connected to themselves. A bus connected to itself will cause problems when used together with block by reference.

* Double spacing in project file names: Some issues have been found in projects where file names have double spaces. Single spaces in file names are not known to cause any problems. Work-around: Only use single spaces in project file names (CQ P100000374).

* In the Screen Editor, the Preview pane does not correctly display the LCD5x7e 8 system font (CQ P100001083). This is fixed in later Display HWDs. Workaround: Install the lcd5x7e 8 font in the Windows Fonts folder. Typical font location: Program files\Sauer-Danfoss\PLUS1\Misc\LCD7X5.FON To install the font: Start > Settings > Control Panel > Fonts Folder > File menu > Install New Font > browse to and install LCD5x7e 9font.

* Components without output types (e.g. Hardware Input) cannot be directly connected to a class instance. This will generate a compile error. Work-around: Use a retype connection in between.

* Autotyped constants will not work when connected directly to Objects. This will generate a compile error. Work-around: Use a Typed constant

* Old display applications (not using the screen editor) will not work in this version. Please contact the Sauer-Danfoss Help Desk.

61

* The linked page feature must not be used with older HWDs. For each released HWD, the table below lists the versions that do not work:

– MC24-10: 10101528v150 and older – MC24-20: 10102117v120 and older – MC50-10: 10101674v150 and older – MC50-20: 10102569v110 and older – DP600: 10102102B and older

– DP610: 10102903B and older

-What is Fixed

* Bad error messages, all fixed as part of the job to enhanced error messages [ P100000445, P100000485, P100000700, P100000855 and P100000925]

* After a Project Save As operation and rename of scs file, the changes are now not lost [P100001375]

* It is now possible to have underscore, (_ ), in module names [ P100000946 and P100000844]

* In Screen Editor, a defect when selecting multiple objects has been fixed [P100001118]

* A defect regards Missing/Wrong Shortcut Keys in the Edit and View Menus has been corrected[P100001131]

* In Screen Editor: When Holding the shift key while clicking on an object made a copy; this has now been fixed [P100001134]

* In Screen Editor: A problem with Area orders was fixed [P100001160]

* A defect when pressing ’Break’ during build process could possibly cause GUIDE to hang; this has been fixed [P100001198]

* An application/project named "check" will give an error message from the GUI [ P100001210]

* It is now not possible to set the Object flag for an App log page [P100001219]

* In some cases a compile of an empty project gave wrong behavior of GUIDE; this has now been fixed [P100001246]

* Linked pages in a project and right clicked in Page Navigator caused an exception; this has been fixed [P100001263]

* The “Hardware Output” symbol sometimes did not work properly with bidirectional signals. This has now been fixed [ P100001308]

* Page Navigator in GUIDE Forward and Backward Arrows now works [P100001321]

* “Compile changed” and Error Check changed” now works correctly; before it behaved like “Compile All” and “Error Check All” [P100001322]

* Color scheme now works correctly [P100001023]

62

* All plotting of sub pages is now possible because of the new Print Interface [P100000187]

* A module name can now contain an underscore (_) combined with non-volatile memory components [P100000844]

* Hardware Output symbol now works with bidirectional signals properly [P100001308]

63

VERSION 3.1.5 (October 2007)

-New Features and Functionality (see the GUIDE User Manual for more detailed information)

* GUIDE is an IEC61508 SIL2 certified code generation tool.

* GUIDE now has a page-by-reference functionality.

* GUIDE now has cut to clipboard, copy to clipboard, and paste from clipboard functions.

* GUIDE can attach a readme file to an LHX application file. The GUIDE Service Tool software displays this readme file before the LHX file download starts.

* GUIDE has a “lock lhx” feature that restricts the download of an LHX application file by either hardware part number or hardware serial number.

* GUIDE software saves backup files (~***.scs) to the current project folder.

* The installation of GUIDE now follows Microsoft Windows installation guidelines.

– User Data files can now be found in the %UserProfile%\My Documents\Sauer-Danfoss folder. – Application Data files are now in the %AppData%\Sauer-Danfoss folder.

* If previous versions of GUIDE are installed, the installation software will automatically copy all neces

sary user and application data to the 3.1.5 installation.

Notes for directory structure:

– %AppData% is typically: C:\Documents and Settings\<user profile name>\Application Data

– %UserProfile% is typically: C:\Documents and Settings\<user profile name>

– {InstallPath} is typically: C:\Program Files

This pertains to the following GUIDE files:

* Hardware Files

– From: {InstallPath}\Sauer-Danfoss\PLUS1\P1ToolData\Hardware\

– To: %AppData%\Sauer-Danfoss\PLUS1\GUIDE\Hardware\

* Library Files

– From: {InstallPath}\Sauer-Danfoss\PLUS1\P1ToolData\Library\

– To: %AppData%\Sauer-Danfoss\PLUS1\GUIDE\Library\

* Font Files

– From: {InstallPath}\Sauer-Danfoss\PLUS1\P1ToolData\Fonts\

– To: %AppData%\Sauer-Danfoss\PLUS1\GUIDE\Fonts\

* MyBlocks Blocks

64

– From: {InstallPath}\Sauer-Danfoss\PLUS1\P1ToolData\MyBlocks\Blocks\

– To: %UserProfile%\My Documents\Sauer-Danfoss\PLUS1\GUIDE\MyBlocks\Blocks\

* MyBlocks Pages

– From: {InstallPath}\Sauer-Danfoss\PLUS1\P1ToolData\MyBlocks\Pages\

– To: %UserProfile%\My Documents\Sauer-Danfoss\PLUS1\GUIDE\MyBlocks\Pages\

If this auto copy doesn’t work, (e.g. access rights problems), the copy process can be done manually with GUIDE not running.

-Important Advisory—Potential User Issues

* Due to a change in P1P format, GUIDE versions 3.0 and earlier will not open P1P files created with GUIDE versions 3.1 and later.

* Due to a change in SCS format, GUIDE versions 3.0 and earlier will not open SCS files created with GUIDE versions 3.1 and later.

* A module name should not contain an underscore (_). An underscore in a module name combined with non-volatile memory components will cause compiler errors.

* The CAN components are always processed each loop. This is true even when the CAN components are placed in a module and that module is not called by the main loop.

* Buses should not be connected to themselves. A bus connected to itself will cause problems when used together with block by reference.

* A project/application cannot have the name “Check”.

* Double spacing in project file names: Some issues have been found in projects where file names have double spaces. Single spaces in file names are not known to cause any problems. Work-around: Only use single spaces in project file names (CQ P100000374).

* Predefine Type component: A logical net that connects the Predefine Type, Read-only Parameter Input, and Module Bus Output components will cause a compiler error (CQ P100001038). Workaround: Use the Retype component instead of the Predefine Type component.

* In the Screen Editor, the Preview pane does not correctly display the LCD5x7e 8 system font (CQ P100001083). Workaround: Install the lcd5x7e 8 font in the Windows Fonts folder. Typical font location: Program files\Sauer-Danfoss\PLUS1\Misc\LCD7X5.FON To install the font: Start > Settings > Control Panel > Fonts Folder > File menu > Install New Font > browse to and install LCD5x7e 9font.

* Components without output types (e.g. Hardware Input) can’t be directly connected to a class instance. This will generate a compile error. Work-around: Use a retype connection in between.

* Autotyped constants will not work with Objects. This will generate a compile error. Work-around: Use a Typed constant

65

* Old display applications (not using the screen editor) will not work in this version. Please contact the Sauer-Danfoss helpdesk.

* If old NV memory symbols are used and their access levels are set and the HWD is new, it will not be possible to compile the project.

* The linked page feature must not be used with older HWD’s. For each released HWD, the table below lists the versions that do not work:

– MC24-10: 10101528v150 and older – MC24-20: 10102117v120 and older – MC50-10: 10101674v150 and older – MC50-20: 10102569v110 and older – DP600: 10102102B and older

– DP610: 10102903B and older

-What is Fixed

* In the GUIDE User Manual: Errors were corrected in the description of the Loop Counter with Carry component; in the Compare in Window component example; a description was added explaining how the Import command strips out the contents of Define Screen pages; a description of read-only parameters function was added; the Array Constant from File component description now states that no periods are allowed in the file name; and graphical errors were corrected in the Keyboard shortcuts chapter (CQ P100000887, P100000849, P100001077, P100001004, P100001035, P100001061).

* The Loop Counter with Carry component now carries without needing an OUT connection (CQ P100001123).

* The Accessrights History component now requires a BOOL input.

* In earlier GUIDE versions, the Accessrights History component required an INT input. An INT input now causes a compiler error (CQ P100001079).

66

VERSION 3.0.5 (June 2007)

-Important Advisory—Potential User Issues

* Note: Query a value or data type without closing the Query window and switch to another PC program, if the scs autobackup performs a backup it will hide the Query behind the GUIDE. To workaround this: Try to minimize all programs, try to switch with Alt-Tab or close all programs except PLUS+1 GUIDE to place the Query back on top.

-What is Fixed

* Documentation has been fixed for some defects and the descriptions of some features have been enhanced.

* Fixed defect so Checkpoint can be used on data type Array [CQ P100001178, P100001179].

67

VERSION 3.0.4 (April 2007)

-What is Fixed

* Documentation has been fixed for some defects. Sections Install Additional Fonts, Components for Read Only Parameters have been added.

* A defect in the maker has been fixed; it fixes a problem with large display applications containing many images [CQ P100001007].

* Fixed defect where old NV-symbols give an error message when compiling with newer HWD’s [P100001114, P100001135]

* Fixed defect where interaction between GUI and graphical engine caused system lock-up [P100001139, P100001122, P100001106, P100001092]

* Fixed defect that, when closing and compacting a PLUS+1 GUIDE project with unresolved read-only parameter file links, corrupted the project file and the project file could not be reopened. [P100001117]

* Fixed defects where Access violation errors occurred within the Screen Editor [P100001124, P100001136]

* Fixed defect in Screen Editor where errors occurred when the Area orders were changed [P100001160]

68

VERSION 3.0.3 (January 2007)

-New Features and Functionality (see the GUIDE User Manual for more detailed information)

* NOTE: To access many of the new features it is necessary to update the Hardware HWD files. These can be downloaded from the Sauer-Danfoss website.

* NOTE: Please review the relevant section of the manual for further details of the new features added to the PLUS+1 GUIDE program in this release.

* Over 30 new components are included in this version of the PLUS+1 GUIDE program. These include:

– A Family of Switch Components so any number of inputs from 2 to 16 can be selected.

– Rounded and Modulo Divide Arithmetic components with Capped and Uncapped varieties.

– The Modules Connection components have been extended to include Bus connections.

– A Family of Password Components that also control the access level. See User Manual for further details of this powerful new feature.

– A Family of Components to support Read Only Parameter files.

* The Graphical User Interface of the PLUS+1 GUIDE program has been updated with new toolbars, icons and menus.

* Application Logging has been added. This allows the Application to log data to memory that can be subsequently downloaded by the Service Tool (requires hardware that supports this new feature).

* Context sensitive help has been added for all the Components of the Component Selector and Menus. Thus, highlighting a component or a menu item and pressing F1 will open the User Manual at the correct section.

* A “Viewer” has been added. This allows any graphic source file to be viewed by right-clicking it in the Project Manager. It is possible to navigate in the viewer in the normal way and export blocks of data from the viewer. Multiple Viewers may be open at one time, giving multiple views of the same source file if required.

* The Screen Editor now supports the import of fonts. Thus, fonts created or licensed by the user can be imported into the PLUS+1 GUIDE program and used in the screen editor. This includes Arabic, Cyrillic and Asian fonts.

* The Screen Editor allows import of several new image file formats including JPEG, TIF, and GIF.

* The Screen Editor now supports Image and Text Lists. Simple animation can now be supported together with the conversion of a number into a text string from a list of strings.

* Read-Only Parameter files are now supported. This allows read-only constant files to be created and downloaded separately from the application. This feature has many useful implementations, see the User Manual for further details.

* The compile process is now displayed in a single pop-up window.

69

* The memory consumption statistics provided for the Controllers after the compile process in the Compile Message Tab has been extended to Displays.

* The method of storing data for the PLUS+1 GUIDE Service Tool program has been changed so, in most Applications, additional memory is available. When extended diagnostic information is required it can now be accommodated by this new method.

-Important Advisory—Potential User Issues

* Note: The P1P file format has been updated in PLUS+1 GUIDE v2.3. Therefore files created with PLUS+1 GUIDE version 3.0 cannot be opened with earlier versions of the PLUS+1 GUIDE program. It is however possible to export pages and then re import them to earlier versions as the SCS file format has not be changed.

* Note: The LHX download file format has been updated in PLUS+1 GUIDE v3.0. Therefore files created with GUIDE version 3.0 cannot be opened with earlier versions of PLUS+1 GUIDE Service Tool program. Version 3.0 or higher must be used.

* Note: Some new PLUS+1 Compliance, PLUS+ 1 HWD, and PLUS+1 Library files require GUIDE version 3.0.

* Some of the PLUS+1 GUIDE features are determined by the Hardware (HWD) file. It is therefore important to verify that a particular feature is supported by the HWD file. For example: # Application Logging, or Read Only Parameter Files.

* Note: When using Modules the Module name should not include the underscore “_” symbol, otherwise a compile error will be generated when using NV symbols.

* Note: The CAN Symbols are always processed each loop. This is true even when the CAN Symbols are placed in a Module and that Module is not called by the main loop.

* White Space in Filename: Some issues have been found in projects using two or more spaces in a row in the file names. A single white space in the directory name is not known to cause any problems. [CQ P100000374] Work-around: Do not use two or more white spaces in a row in the File Name of a project.

* Component Predefine Type: When the Predefine Type is used on a Read-Only Parameter Input net that is connected to a Module Bus Output the code produced would not compile. [CQ P100001038] Work-around: Instead of Predefine Type use the Retype.

* Incorrect type on GUIDE AccessRights History component [P100001079] In version 3.0.3 this component requires an integer as input; this is a defect and will be corrected in a future version so data type Bool will be used as the required input. In version 3.0.3 use integer value 0 to represent False and value 1 to represent True. In a future version this will generate a compile error and the data type has then to be changed to Bool.

* LCD5x7e 8 system font is not shown correct in preview [P100001083] In Display applications where the font LCD5x7e 8 is delivered as a system font the preview doesn’t work. Workaround: Install font ..\Sauer-Danfoss\PLUS1\Misc\LCD7X5.FON into Windows (Control Panel – Fonts – File Menu – Install New Font)

70

VERSION 2.2.7 (September 2006)

-What is Fixed

* The Component Inspector of the Screen Editor allows properties to be changed without generating errors [CQ P100000932, P100000934, P100000942].

* When leaving Modules with large file sizes on PCs with restricted memory, the data is correctly stored [CQ P100000937].

* In some cases, use of the File/Open Recent projects left the existing project open. This has been corrected [CQ P100000945].

71

VERSION 2.2.6 (June 2006)

-What is Fixed

* In some cases it was not possible to drag a Function Block onto the drawing area after a compile. This defect has been corrected and the Project Manager Tree is left as it was before the compile began [CQ P100000904, P100000884].

* In some cases the names of NV symbols produced an incorrect compile error. This has been corrected [CQ P100000905].

* The Text Editor Preview displays text correctly regardless of the background colour chosen [CQ P100000910].

* The Undo Function has been updated to support Text strings that contain a data value correctly [CQ P100000911].

* PLUS+1 Compliances HWD Files are now installed in the correct locations in the Tree of the Hardware Tab [CQ P100000907].

* The init connect symbol does not terminate the compile process when it is connected to type AR-RAY[259]U8 [CQ P100000912].

* In some cases the memory optimization of Arrays did not work correctly, including the use of the Array Set Component. This has been corrected [CQ P100000919, P100000926].

* It is now possible to connect a checkpoint directly to the output of a CAN Symbol [CQ P100000921].

* The Screen Editor value for clBlack was incorrect ($01010100), this has been updated to black [CQ P100000924].

72

VERSION 2.2.5 (May 2006)

-New Features and Functionality (see the GUIDE User Manual for more detailed information)

* NOTE: Data relating to the GUIDE Service Tool has been moved to a separate GUIDE Service Tool Readme file.

* NOTE: To access some of the new features it is necessary to update the Hardware HWD files. These can be downloaded from the Sauer-Danfoss Website when they are available.

* The Hardware Tab of the Component Selector has been significantly enhanced and now supports multiple levels of folders and hardware. This update is specifically targeted as the support of Sauer-Danfoss PLUS+1 Compliant products.

* The Hardware Tab now includes a search function that allows parts to be found by keyword and part numbers. It is possible to collapse the whole tree with a single click. “Next”/”Previous” navigation keys are also provided.

* A “My Blocks” Tab has been added to the Component Selector. This allows the user to create blocks to be sorted, stored and shared. It is also possible to send complete sections of “My Blocks” to other users using file-zipping tools.

* The Component Inspector pop ups have been extended to the “Hardware” and “My Blocks” Tabs.

* The GUIDE Compiler has been enhanced to significantly reduce the amount of RAM consumed with Arrays.

* The Encode symbol supports conversion of up to 8 bytes of U8 or S8 to an Array, and the Decode symbol supports conversion from Array to U8.

* An online context sensitive windows Help file is now included in addition to the pdf Manual.

* It is now possible to update a Display Application using one type of screen to an Application using a different screen type.

* The operation of the Pop Up Editor has been refined and enhanced, for example it is now possible to enter values before entering the type.

* GUIDE now opens much faster than in previous version.

* This version of GUIDE support Application Hardware and Software Personalities and Application Blocks using the hardware’s property: “Target Part Number” in the Inspector tab.

* A bug report facility has been added to GUIDE to make bug reporting easier and more comprehensive including a facility that allows keystroke and operations to be logged.

-Important Advisory—Potential User Issues

* Note: The P1P file format has been updated in GUIDE v2.2.5. Therefore files created with GUIDE version 2.2 cannot be opened with earlier versions of GUIDE. It is however possible to export pages and then re import them to earlier versions as the scs file format has not be changed.

73

* Note: The LHX download file format has been updated in GUIDE v2.2.5. Therefore files created with GUIDE version 2.2 cannot be opened with earlier versions of GUIDE Service Tool. Version 2.2 or higher must be used.

* Note: Some new PLUS+1 Compliance, HWD and Library files require GUIDE version 2.2.5.

* Some of the GUIDE features are determined by the Hardware (HWD) file. It is therefore important to verify that a particular feature is supported by the HWD file. For example: CAN and NV symbols, write access levels for NV symbols.

* Note: When using Modules the Module name should not include underscore “_”, otherwise a compile error will be generated when using NV symbols.

* Note: The CAN Symbols are always processed each loop. This is true even when the CAN Symbols are placed in a Module that is not called.

* White Space in Filename: Some issues have been found in projects using two or more spaces in a row in the file names. A single white space in the directory name is not known to cause any problems. [CQ P100000374] Work-around: Do not use two or more white spaces in a row in the File Name of a project.

* Adobe Acrobat Reader version 5 does not work with the GUIDE pdf files. Adobe Acrobat Reader should be updated to a later version.

-What is Fixed

* In some conditions Application Files were not saved or memory problems at the beginning of the compile process or generate exception errors were reported when handling file data. These issues have been resolved [CQ P100000065, P100000261, P100000340, P100000413, P100000496, P100000529, P100000681, P100000547, P100000575, P100000727, P100000748]

* In some conditions Access violation errors when opening or closing projects appeared. These issues have been resolved [CQ P100000767].

* A problem when using the constant clBlack in Display applications has been resolved. The constant is redefined so it will show Black in Sauer-Danfoss Displays [CQ P100000754, P100000488, P100000477 ].

* In some cases the names of the wire were displayed in error. This has been corrected [CQ P100000127, P100000573].

* It is possible to add a Module that is already in the project directory [CQ P100000250].

* Cut and Paste in the Screen Editor works correct when used from the menu and toolbar [CQ P100000307].

* Setting images with the transparent property now works [CQ P100000328].

* Changing the names of images in the Screen Editor now behaves as anticipated [CQ P100000422].

* Operation of the toolbar when resizing the screen is improved [CQ P100000434].

* Issues with the Pop Up Query Window displaying a list of data have been resolved [CQ P100000587]

74

* When undo is active other operations are prohibited to ensure incorrect operations do not occur [CQ P100000598].

* Double clicking a P1P file in windows now launches GUIDE and opens the project correctly [CQ P100000600].

* The operation of the pop up panels on the side of the screen has been refined [CQ P100000661].

* Copy and paste of images in the Screen Editor now works correctly [CQ P100000667].

* Operation of toolbar functions has been enhanced [CQ P100000680].

* Drag and drop operation the screen editor has been enhanced to make it easier to drop at the desired location [CQ P100000684, P100000481].

* Hourglass is sometimes displayed when all operations are completed. This has been corrected [CQ P100000688]

* Display of extended characters in the screen editor has been reviewed. All characters with ASCII code below 32 (except 8, 10 and 13) have been removed [CQ P100000713]

* Un install screens have been changed so all data can be displayed [CQ P100000720].

* Turning the grid on and off has an immediate effect [CQ P100000728]

* Operation of keystrokes Ctrl-O and Ctrl-N have been made consistent [CQ P100000512]

* Operation of the Page Navigator now works in the Screen Editor [CQ P100000416]

* Operation of the lists in the Screen Editor have been improved when expanding and collapsing them [CQ P100000525]

* It is possible to enter a “d” or “D” to disable a checkpoint or NV Symbol form diagnostic access [CQ P100000705].

* It is possible to delete a namespace and make it blank after it has been added [CQ P100000733].

* Top View editor is now disabled when in the Screen Editor editing text or images [CQ P100000735].

* The License Manager is disabled when in the Screen Editor [CQ P100000745].

* Error reporting of invalid Page Port names have been improved [CQ P100000431, [CQ P100000432].

* Operation and behavior of the Pop Up menus has been improved and enhanced [CQ P100000466, P100000761].

* Several compiler issues and refinements have been made to make the compile process more robust [CQ P100000601, P100000751, P100000760, P100000762, ].

* An error is generated if a Null constant is used as a connection to a checkpoint [CQ P100000616].

* The GUI text entry editor correctly tests for an array with 0 elements [CQ P100000630].

* The Hardware BIO Symbols has been resized to be consistent with other symbols, other symbols have been reviewed and now align with the standard gird [CQ P100000657, P100000747].

75

* The operation of the Shift Left Symbol (AF_SHL) has been corrected. Previously with a U8 output data type some bits were incorrectly shifted resulting in a result larger than the U8 limit [CQ P100000703].

* Errors reporting associated with connections to an INIT BIOS symbol have been improved, particularly when no connection is present [CQ P100000722].

* If GUIDE is used with a demo license and a project opened, then the P1P file will not be deleted [CQ P100000739].

* Text Color issues between the DP6xx and the preview in GUIDE has been aligned so text does not “disappear” [CQ P100000750]

* Zooming in and out of the screen editor could in some instances move objects. This has been corrected [CQ P100000772].

* The screen editor now validates extended characters. Previous versions did not and this could lead to data corruption [CQ P100000775].

* It was possible to have two Set symbols (IC_SET) with the same name but of a different type. This has been corrected and will generate a compile error [CQ P100000776].

* When GUIDE was processing other commands clicking the icon toolbar sometimes did not result in the action being carried out. This has been reviewed so icons are only available when actions can be executed [CQ P100000780].

* COS and SIN calculations for U32 inputs which should result in a negative result now do so. Also an input of -2147483648 for Controllers which resulted in an error of approximately 1/10,000 been corrected [CQ P100000781]

* The alias names on EEPROM locations have been made more robust [CQ P100000788].

76

VERSION 2.1.3 (November 2005)

-What is Fixed

* The SWITCH16 Symbols works correctly when switching arrays [CQ P100000730].

* Deleting Images from the Screen Editor’s Image Register deletes only the file selected, not the whole folder [CQ P100000693].

* It is possible to connect Capped Symbols to BIOS connections without generating compiler errors [CQ P100000731, P100000679].

77

VERSION 2.1.2 (September 2005)

-New Features and Functionality (see the GUIDE User Manual for more detailed information)

* NOTE: To access many of the new features it is necessary to update the Hardware HWD files. These can be downloaded from the Sauer Danfoss Website.

* Over 30 new symbols are included in this version of GUIDE. These include:

– A Family of CAN symbols implementing virtual mailboxes.

– A Family of Array symbols to allow array data to be manipulated.

– A Family of Non Volatile symbols.

– A Family of “capped” symbols so data does not overflow or underflow in calculations.

– A Family of User Compiler Error symbols.

– A Family of User defined Compiler Error symbols.

• The operation of the Symbols Tab in the Component Inspector has been significantly enhanced:

– The cursor is moved the branches of the tree open automatically and where components have options these are presented.

– Symbols with multiple configurations like “compare” has been radically extended and can now be selected directly before a symbol is placed on the drawing.

* The Hardware tab of the Component Inspector now contains a preview window for the Hardware selected.

* It is now possible to install HWD files for IO Modules and other Plus 1 Compliant Hardware and drag and drop them into an application.

* “Namespace” has been added. This provides an automatic prefix to alias names for example names with Checkpoints. Thus checkpoints can be placed in a page, the page copied and pasted, and by using the “Namespace” in a page’s properties, each checkpoint can be uniquely accessed.

* The range of Security Access Levels has been extended to include “D”, which inhibits access from the Service Tool. Thus is it possible to construct secure passwords within an application.

* The Setup > Options screen has been extended and enhanced to include options not only for the Screen Editor but also the Component Inspect.

* P1P and P1X files are now associated with GUIDE in the Windows registry and will open GUIDE directly from Explorer.

* It is possible to install and uninstall GUIDE and the GUIDE Service tool independently. [CQ P100000553]

* When using newer HWD files, compilations that have been successfully completed will show memory used for the Application in the Compile Messages Tab at the bottom of the screen [CQ P100000632].

* Using the CTRL key it is possible to select multiple objects. Once selected, it is possible to move the objects or edit the common properties collectively.

78

* Images and Text strings are shown in a preview window similar to the symbols tab.

* Scroll bars have been added to the Screen Editor to allow the screen to be panned [CQ P100000419]

* It is possible to export text from the Screen Editor, so it can be translated, and the modified text then imported back into the Screen Editor of an application.

* Image selection has been improved, so it is possible to select an image even from the transparent part of an image.

* When adding an image file the description is automatically complete as the files name, this can then be changed by the User.

* The names used for properties and labels used in panel is much more descriptive of there function. The functionality remains the same in all instances.

* Undo and Redo have been added to the Screen Editor. Multi line text strings can now be easily added by using the <CR> when entering text, (previously it was CTRL <CR>).

* The right click menu of an object has been enhanced to include cut, copy and paste [CQ P100000479]

* Right clicking on an object will cause the properties to be displayed, but will not move the object.

-Important Advisory—Potential User Issues

* Note: The p1p file format has been updated in GUIDE v2.1. Therefore files created with GUIDE version 2.1 cannot be opened with earlier versions of GUIDE.

* Note: The LHX download file format has been updated in GUIDE v2.1. Therefore files created with GUIDE version 2.1 cannot be opened with earlier versions of GUIDE Service Tool. Version 2.1 or higher must be used. Note: Some “newer” LHX Files require GUIDE version 2.1.

* Note: The Enable/Disable of Preview in the Component Inspector has been moved to the Setup ¦ Options dialog box.

* Note: A Retype symbol must be added to all application when using some CAN bios connections because the compiler error detection has been enhanced. [CQ P100000646].

* Note: In some cases version 2.1.2 produces larger application code size than version 2.0.x. This is because some symbol defects have been fixed so the code produced is larger. This specifically affects the Scale Symbol and one application was found to be 3% larger. [CQ P100000645].

* White Space in Filename: Some issues have been found in projects using two or more spaces in a row in the file names. A single white space in the directory name is not known to cause any problems. (CQ P100000374) Work-around: Do not use two or more white spaces in a row in the File Name of a project.

* In some instances a project is not saved correctly. Work-around: No work-around is known. Keeping drawing file small by using Modules, is known to help reduce the occurrence dramatically.

-What is Fixed

79

* The pop up menus of the Component Inspector are disabled when the GUIDE is not the active application.

* The Time data type is correctly validated for all symbols so errors cannot be generated [CQ P100000574].

* It is possible to change an application from one display to another. For example a DP600 application to a DP620 or DP610. This is achieved by removing the link to the Port Name of the display, see manual for further details [CQ P100000551].

* The Compare Symbol behaves as expected when it is changed to different types [CQ P100000557].

* HWD Function Blocks can now be correctly inserted into GUIDE [CQ p100000569].

* Modules can be named by the user as desired. It is not necessary to use the default settings of Module1, Module2 etc. [CQ100000572].

* The Switch Symbols now work correctly with Arrays [CQ P100000591].

* The Receive CAN with ID Mask symbol now behaves correctly when the ID is connected to a variable [CQ P100000619].

* When quotation marks are used in the text of the Screen Editor error messages are reported corrected, ANSI C Syntax should be used to insert quotation mark [CQ P100000620].

* Applications using large arrays will work with the Service Tool [CQ P100000621].

* Arrays now work correctly with the Connect Symbol [CQ P100000624].

* The Get Array Symbol behaves correctly when incorrect indexes are used [CQ P100000625].

* The NV Symbols behaves correctly when the Alias name is changed [CQ P100000626].

* The Memory Used display in the Compile Messages Tab now reports the correct results [CQ P100000632].

* BIOS “CAN Buffers” supported Overrun in the new Library [CQ P100000634]

* When copying a language in the Screen Editor it behaves correctly [CQ P100000635].

* Moving backward and forward in the Screen Editor Define Page is now directionally correct. [CQ P100000639].

* Applications created in 2.0.x will compile in 2.1.2 in all but the most exceptional cases (small amounts of additional memory are required to the defect fixes of some symbols) [CQ P100000641].

* The Switch symbols are now able to switch colour types [CQ P100000642].

* The compiler reports duplicate Alias names correctly [CQ P100000644].

* All transition symbols are available from the pop up query menu once they are placed on the drawing [CQ P100000653].

80

VERSION 2.1.1 (July 2005)

-Important Advisory—Potential User Issues

* White Space in Filename: Some issues have been found in projects using two or more spaces in a row in the file names. A single white space in the directory name is not known to cause any problems. (CQ P100000374) Work-around: Do not use two or more white spaces in a row in the File Name of a project.

* In some instances a project is not saved correctly. Work-around: No work-around is known. Keeping drawing file small by using Modules, is known to help reduce the occurrence dramatically.

* Adobe Acrobat Reader version 5 does not work with the GUIDE pdf files. Adobe Acrobat Reader should be updated to a later version.

-What is Fixed

* The GUIDE Compile function now works consistently for applications [CQ P100000566, P100000576].

* LHX Files are produced correctly and the “INTERNAL: UNKNOWN KEY VALUE” error report from the Service Tool is fixed [P100000581]

* Component “Find Array” corrected regarding data types on input and output

* Component “Loop Counter with Carry” fixed regarding; Outputs always static in corrected version [CQ P100000583]

81

VERSION 2.1.0 (June 2005)

-What is Fixed

* The shift right component operates consistently for all data types when truncating data [CQ P100000533]

* New Symbols can be used in old application where the hardware supports them, for example the Compare symbol. (CQ P100000377).

* The User can determine the number of lines the Menu Toolbar will use [CQ P100000225]

* GUIDE will compile projects in all cases where errors do not exist [CQ P100000483]

* Files that are write protected behave as expected including those in MS-Visual-Source-Safe with meaningful warnings from GUIDE [CQ P100000521]

* File compression of p1p files works in all cases [CQ P100000405]

* Module names can be longer than 16 characters, even when the scale symbol is used [CQ P100000505]

* The compile tests that alias names are unique in all instances [CQ P100000538]

* When updating to different EQ symbols the symbol behaves as expected [CQ P100000377]

* Clicking F1 opens the GUIDE Manual. A new chapter has been added with further details about the use and operation of the Screen Editor.

* It is possible to rename the screen areas without loosing the object on them [CQ P100000478]

* The Image register does not allow an image file with the same name to be added twice to a project [CQ P100000500]

* The insertion point of images is always shown in the same way using EntryX/ValueX, EntryY/ValueY [CQ P100000441].

* Text is displayed correctly in the preview mode, even when placed on a dark background (CQ P100000484).

* The operation of the cursor keys has been corrected so they do not move objects when they should not (CQ P100000457).

* Fast operation when dragging and dropping images or text is now supported (CA P100000470).

* The maximum number of screens in an application is now limited only by memory space The maximum number of images in a project is now limited only by memory space. Deleting text from the Text Editor also removes it from the screen [CQ P100000476].

* When a screen area is renamed the objects associated with the screen area are retained [CQ P100000478].

* An image must have a description before it is possible to save an image [CQ P100000417].

* Images are correctly rotated in the preview screen [CQ P100000442, P100000459, P100000495].

* The Graphic editor keyboard commands are disabled in the Screen Editor [CQ P100000457, P100000425, P100000418].

82

* The Image Register now ensures only a single instance of an image with the same file name is present in the register [CQ P100000500].

* The manual has been extensively updated to provide detailed use of the screen editor [CQ P100000312].

* The positioning and selecting of objects has been made more precise with “intelligent” control of mouse movement [CQ P100000414];

* The insert point of images is always displayed even after the screen is minimized and restored [CQ P100000441];

* The Transparent setting is disabled when it does not perform a function [CQ P100000469].

* When exiting the Screen Editor it behaves as expected and does not start a compile [CQ P100000427].

83

VERSION 2.0.4 (March 2005)

-What is Fixed

* The compile speed on some PCs types was extended this has been corrected. [CQ P100000464].

84

VERSION 2.0.3 (February 2005)

-New Features and Functionality (see the GUIDE User Manual for more detailed information)

* The installation process automatically removes the previous installation of GUIDE, with the user’s confirmation.

* GUIDE Libraries and Hardware Files (HWD) are no longer supplied with GUIDE, they should be downloaded from the website as required. A demonstration library and hardware file is included. These files should be uninstalled when not required. They cannot be used in “real” applications on real hardware.

* The Compile operation has been enhanced to improve the compile speed. It is now 40 times faster than the previously released version of GUIDE.

New symbols have been added to the GUIDE. These include: Module Bus Input, Module Bus Output (allowing Buses to be passed between modules instead of individual wires), Value Initialization, Set Value, Compare (which has 6 options), and may more.

* A preview for the Function Blocks has been added.

* GUIDE now automatically opens with the last project loaded, if it was not compressed to a p1p file.

-Important Advisory—Potential User Issues

* White Space in Filename: Some issues have been found if projects use two or more spaces in a row in the file names. A single white space in the directory name is not known to cause any problems. (CQ P100000374) Work-around: Do not use two or more white spaces in a row in the File Name of a project.

* When working in the screen editor the key of the graphics engine are not disabled. Thus if “L” is pressed then when the screen editor is closed the graphic engine does not show the expected page. (CQ P100000425) Work-around: Do not press keys that are not used in the Screen Editor.

* When working with the DP600 Display the application loop time should not exceed 300mS. If it does, the GUIDE Service Tool will have difficulty communicating with it. Work-around: Keep the loop time below 300mS.

85