RFI - Pension Administration System

RFI - Pension Administration System

Request for Information - PERS

Pension Administrative Systems

OREGON PERS MODERNIZATION PROGRAM
PENSION ADMINISTRATION SYSTEM
REQUEST FOR INFORMATION (RFI)

OregonBuys # S45900-00015032
Issue Date: 10/6/2025
Close Date: 10/31/2025 3:00PM (PST)
Question Submission Date: 10/17/2025 3:00PM (PST)
Question Response Date: 10/21/2025 5:00PM (PST)
Point of Contact: Ryan Ellis, Senior Contract and Procurement Specialist
Contact Information: Ryan.Ellis@pers.oregon.gov
Phone: (503) 598-6165

TABLE OF CONTENTS
1 Introduction ................................ ................................ ................................ ...................... 3
1.1 About PERS ................................ ................................ ................................ .................. 3
1.2 Purpose of this Request for Information (RFI) ................................ ............................. 3
1.3 Glossary ................................ ................................ ................................ .................... 5
2 Organization background and current environment ................................ ................... 5
2.1 Current system overview ................................ ................................ ......................... 5
2.2 Pension plan overview ................................ ................................ ............................. 6
2.3 Integration needs ................................ ................................ ................................ ..... 9
3 Vendor and company information ................................ ................................ ................ 9
3.1 Company overview ................................ ................................ ................................ .. 9
3.2 Project team and approach ................................ ................................ ..................... 9
3.3 Key capabilities ................................ ................................ ................................ ........10
3.4 Implementation and support philosophy Please describe your team's
implementation and support approach: ................................ ................................ ............14
3.5 Innovation and partnership ................................ ................................ .....................14
4 Solution overview and functionality ................................ ................................ ............14
4.1 PAS solution architecture and technology ................................ ............................14
4.2 Reporting and business intelligence ................................ ................................ ......15
5 Data migration and integration ................................ ................................ .....................15
5.1 Data migration strategy ................................ ................................ ..........................15
6 Security, compliance, and business continuity ................................ ...........................15
6.1 Data security ................................ ................................ ................................ ............15
6.2 Disaster recovery and business continuity ................................ ...........................16
7 Commercial information and pricing ................................ ................................ ............16
7.1 Pricing model ................................ ................................ ................................ ...........16
7.2 Contractual terms ................................ ................................ ................................ ....16
8 Vision and roadmap ................................ ................................ ................................ .......17
8.1 Product roadmap ................................ ................................ ................................ ....17
8.2 Future trends ................................ ................................ ................................ ...........17
9 RFI response instructions ................................ ................................ .............................. 17
9.1 Submission format ................................ ................................ ................................ ...17
9.2 Questions and clarifications ................................ ................................ ..................18
10 Attachment A Disclosure Exemption Statement…..…………………….……....…....….. 20

1 Introduction

1.1 About PERS
The Oregon Public Employees Retirement System (PERS) is a public sector retirement
system for administering pension benefits for approximately 195,000 active members,
166,000 retirees and beneficiaries, and 55,000 deferred members across four distinct,
yet intertwined, pension plans. PERS supports more than 900 Oregon employers,
including state, counties, municipalities, cities, school districts, and more. PERS is
overseen by a five-member board. The PERS authorizing statutes are Oregon Revised
Statute (ORS) Chapter 238 and Chapter 238A. PERS assets are managed by the Oregon
Investment Council (OIC).
Since August 2004, PERS has operated as a Defined Benefit-Defined Contribution
hybrid plan with a traditional pension combined with mandatory participation in a
defined contribution plan. The plan components are as follows:
1.1.1 PERS pension plans (defined benefit)
• Plan 1 – PERS 238 Tier One
• Plan 2 – PERS 238 Tier Two
• Plan 3 – Oregon Public Service Retirement Plan (OPSRP) 238a
1.1.2 PERS Individual Account Program (IAP) (defined contribution)
• Plan 4 – Oregon Individual Account Program (IAP) – an account-based benefit
that contains member contributions
Every qualifying Tier One, Tier Two, and OPSRP member has an IAP. Detailed
descriptions of Oregon PERS can be found here:

oregon.gov/pers/Documents/General-Information/PERS-by-the-Numbers.pdf
oregon.gov/pers/Documents/Financials/ACFR/2024-ACFR.pdf

Mission statement
We serve the people of Oregon by administering public employee benefit trusts to pay
the right person the right benefit at the right time.
1.2 Purpose of this Request for Information (RFI)

PERS is looking for information from qualified Pension Administration System (PAS)
vendors. We want to understand how your solutions can replace our current legacy
system, which is a three-tier, monolithic pension administration system, along with
various miscellaneous business support applications. The goal of this RFI is to:
• Gain a comprehensive understanding of the current market landscape for modern
PAS solutions.
• Identify vendors capable of supporting the complex administration of our four
intertwined pension plans.
• Evaluate potential technology architectures, implementation approaches, and
ongoing support models.
• Inform the development of a detailed Request for Proposal (RFP).
• Inform pricing expectations for future budget requests.

Disclaimer
This RFI is for informational purposes only and does not constitute a commitment to
purchase goods or services. No contract or agreement will be awarded as a result of
this RFI. Information provided and Responses to this RFI are not binding by either
party. PERS reserves the right to select any vendor, during a potential future formal
solicitation (such as a Request For Proposal, gather more information, or take no
further action at its sole discretion). Responding to this RFI is voluntary and is not a
prerequisite for participating in any future procurement processes, nor does it
guarantee an invitation to a future procurement. Responses to this RFI will not have
any impact of future solicitation evaluation processes.
All costs associated with Responder’s preparation and submission of this RFI is the
sole responsibility of the Responder and shall not be borne by PERS or The State of
Oregon.
Public Records and Trade Secrets
This RFI shall be kept by PERS and made a part of a file or record that may be open to
public inspection. If an RFI response contains any information that is considered a trade
secret or is otherwise exempt from disclosure under the Oregon Public Records Law,
ORS 192.311 through 192.478, if applicable, the vendor shall complete and submit the
Attachment 1, Disclosure Exemption Affidavit and a fully redacted version of its
response, clearly identified as the redacted version.

If applicable, the Oregon Public Records Law exempts from disclosure only bona fide
trade secrets, and some exemptions from disclosure apply only “unless the public
interest requires disclosure in the particular instance.” Therefore, non-disclosure of
documents or any portion of a document submitted as part of a response to this RFI
may depend upon official or judicial determinations made pursuant to the public records
laws and requirements. If applicable, PERS may give vendor notice of any required
disclosure and cooperate with vendor, at vendor’s expense, in seeking reasonable
protective arrangements. However, PERS shall not be required to act in a manner which
would result in any sanctions or other penalties.

Vendors are cautioned that cost information generally is not considered a trade secret
under Oregon Public Records Law (ORS 192.311 through 192.478) and identifying the
submission, in whole, as exempt from disclosure is not acceptable.
If a vendor requires a Non-Disclosure Agreement (NDA) to provide a response, which
may be considered proprietary, a request including the NDA document must be
submitted by email to Ryan Ellis at ryan.ellis@pers.oregon.gov.by Wednesday Oct. 22,
2025 12:00PM (PST) for legal review.

1.3 Glossary

Term Definition
PERS Oregon State Agency: Oregon Public Employees Retirement System
DAS Oregon State Agency: Department of Administrative Services
EIS A section of DAS: Enterprise Information Services
ORION Oregon Retirement Information Online Network
jClarety Core pension administration application (system of record) within ORION
OMS/ED
X/PHIP
TPA
External self-service portals. The public-facing pages of jClarety:
*Online Member Services (OMS)
*Employer Data Exchange (EDX)
*PERS Health Insurance Plan (PHIP)
* Third-Party Administrator (TPA)
OSA ORION support applications (more than 30 support business applications)
UI/UX User Interface/User Experience
SDLC Software Development Lifecycle is a structured methodology used to design, develop,
test, and maintain high-quality software efficiently.
OPSRP Oregon Public Service Retirement Plan
IAP Individual Account Program


2 Organization background and current environment

The Oregon Public Employees Retirement System depends on jClarety for its pension
administration system (PAS), along with several smaller applications for our Individual
Account Program (IAP) administration and other pension administration gaps within
jClarety. The public-facing pages of jClarety are Online Member Services, Employer Data
Exchange, and PERS Health Insurance Plan third-party administrator portals.
2.1 Current system overview

• System name: ORION
• Architecture: The existing ORION architecture is comprised of several
applications. The main application is jClarety, a highly customized, legacy three-
tier monolithic java application. It operates on RedHat Enterprise Application
Platform, with its backend on Microsoft SQL Server, the operating system on
Microsoft Windows Server, and the frontend served by Microsoft Internet
Information Services. jClarety provides system logs, reports, and SQL used by a
multitude of staff for troubleshooting issues. jClarety is integrated with IBM
FileNet, the business process workflow, documentation, and imaging system. The
collection of other business applications referred to as ORION Support
Applications rounds out what is called ORION. These applications are built in a
variety of platforms including .NET, Access, Excel, C#, Microsoft PowerApps, and
Microsoft SQL Server.

2.2 Pension plan overview

• Plan name: PERS 238 Tier One
o Plan type: Defined benefit
o Number of participants: 14,855 (active and inactive)
o Key features and complexity:

▪ Oldest plan.
▪ Members receive assumed earnings.
▪ Multiple contribution types.
▪ Multiple purchase options to restore service credit and
contributions towards retirement.
▪ Lump sum vacation pay and sick leave pay calculations.
▪ School employee contract month calculations.
▪ Members have 13 benefit options available at retirement (including
six survivorship options) that are updated periodically for cost-of-
living adjustment (COLA) or variable update.
▪ Tax remedy program (based upon whether the retiree lives in
Oregon or outside the state).
▪ Includes judge members that have specialized retirement plans
separate from other Tier One members.
▪ A member can divorce, and their spouse can have an alternate
payee account created based upon court order decree. Court
orders also allow for split benefit calculations at retirement and
reductions from member benefits.
▪ Preretirement beneficiaries are also due benefits with four different
options.
▪ Member contributions started going to their IAP in 2004. Before
then, they were eligible for a variable election program which has a
separate earnings process.
▪ Effective in 2020, a portion of member IAP contributions were
diverted to the Employee Pension Stability Fund which helps to
fund the member’s benefit at retirement.
▪ Member data is open for review all the way up until they receive a
Notice of Entitlement, which means the employment, service credit,
salary and contribution data is able to be changed at any time
during the member life cycle.
▪ PERS has to have functionality to change the member data,
including potentially change a member's tier designation, plan
designation, contribution start date, service credit, balance, benefit
group, job class, and more at any point.
• Plan name: PERS 238 Tier Two
o Plan type: Defined benefit
o Number of participants: 35,881 (active, inactive)
o Key features and complexity:
▪ Started in 1996.
▪ Members receive actual earnings.
▪ Multiple contribution types.
▪ Multiple purchase options to restore service credit and
contributions towards retirement.

▪ Sick leave pay calculations.
▪ Calculating contract months for school district staff.
▪ Members have 13 benefit options available at retirement (including
six survivorship options) that are updated periodically for COLA or
variable update.
▪ A member can divorce, and their spouse can have an alternate
payee account created based upon court order decree. Court
orders also allow for split benefit calculations at retirement and
reductions from member benefits.
▪ Preretirement beneficiaries are also due benefits with four different
options.
▪ Member contributions started going to the IAP in 2004; until then
they were eligible for a variable election program which has a
separate earnings process.
▪ Effective in 2020, a portion of member IAP contributions were
diverted to the Employee Pension Stability Account which helps to
fund the member’s benefit at retirement.
▪ Member data is open for review all the way up until they receive a
Notice of Entitlement, which means the employment, service credit,
salary and contribution data is able to be changed at any time
during the member life cycle.
▪ PERS has to have functionality to change the member data,
including potentially change a member's tier designation, plan
designation, contribution start date, service credit, balance, benefit
group, job class, and more at any point.


• Plan name: OPSRP
o Plan type: Defined benefit
o Number of participants: 198,621 (active, inactive)
o Key features and complexity:
▪ Newest plan began August 29, 2003.
▪ Members do not have earnings.
▪ Member contributions go directly to their IAPs.
▪ Retirees have five benefit options available at retirement (including four
survivorship options) that are updated periodically for COLA.
▪ Members can divorce their spouse and have their benefit split with their
alternate payee at retirement or paid as a reduction at retirement.
▪ Effective 2020, a portion of member IAP contributions were diverted to
the Employee Pension Stability Account which helps to fund members’
benefits at retirement.
▪ Member data is open for review all the way up until they receive a
Notice of Entitlement, which means the employment, service credit,
salary, and contribution data is able to be changed at any time during
the member life cycle.
▪ PERS has to have functionality to change the member data, including
potentially changing a member's tier designation, plan designation,
contribution start date, service credit, balance, benefit group, job class,
and more at any point.
• Program name: Individual Account Program (IAP)
o Plan type: Cash balance (defined contribution)

o Number of participants: 328,994 as of 2023
o Key features and complexity:
▪ Data is reported by employers to PERS, sent to a third-party
administrator for record keeping and check issuance tasks only.
▪ Administration of the program is fragmented and handled by offline
tools and spreadsheets.
▪ Member contributions are split between IAP and Employee Pension
Stability Account.
▪ Retirees have six options, five of which can be paid with varying
frequency (monthly, quarterly, annually).
▪ Accounts continue to receive earnings until fully distributed.
▪ Earnings are credited yearly and are divided into ten target-date
funds assigned by date of birth unless the member elects to choose
a different fund during a yearly election cycle.
▪ Divorce decrees also can impact the IAP, with alternate payee
accounts existing for IAP accounts as well.
▪ Member data is open for review all the way up until they receive a
Notice of Entitlement, which means the employment, service credit,
salary and contribution data is able to be changed at any time
during the member life cycle.
▪ PERS has to have functionality to change the member data,
including potentially change a member's tier designation, plan
designation, contribution start date, service credit, balance, benefit
group, job class and more at any point.

• PERS employers
o More than 900 Employers report demographic and contribution data to
PERS on either a weekly, biweekly, semi-monthly, or monthly basis via two
different types of reports.
o They each have individual contribution rate calculations, their own
earnings rates, and can be part of rate pools with other employers.
o Employers are able to have side accounts, which represent a separate
lump sum, pre-payment of pension costs held in a reserve that can be
amortized as credits to their pension invoice spread out over a 10- to 20-
year period. Employers need to be able to view and pay their invoices,
view their statement, and review and verify pre-2004 legacy data.

• General ledger
o Each financial event in the current PAS is programmed with coding for
general ledger transactions that are imported daily into a separate
accounting system using an interface management system that
compresses and sorts the data into the format required by the state’s
financial accounting program.
o Accounting entries are needed for each financial event, such as
invoicing, cash receipts, applying credits to receivables, benefit
payments, refunds, earnings, and other transaction types.
o Reporting needs include accounts receivable aging, tracking of credits
due to employers, benefit payment details, and the ability to query any
data related to general ledger transactions.
o Compliance with Oregon State Treasury Policy is required:
https://www.oregon.gov/treasury/public-financial-services/banking-
with-treasury/pages/cash-management-policies.aspx

2.3 Integration needs

The new PAS should integrate seamlessly with all key agency systems, including
accounting and financial platforms, document and records management solutions, call
centers, customer relationship management tools, actuarial valuation software, and
external payment processors.
RFI responses should describe supported integrations, whether real-time, batch,
application programming interface (API)-driven or asynchronous.
Vendors should explain how their APIs are documented, how changes and deprecations
are communicated and managed, and what metrics are available for each endpoint,
including any options for customization. In addition, vendors should describe the
integration principles they follow to ensure interoperability, reliability, and scalability.

3 Vendor and company information

PERS is seeking information from vendors regarding their pension administration system
solutions. We are looking for partners who can provide innovative solutions that align
with our commitment to member service excellence.

3.1 Company overview

Please provide a brief overview of your company:

• Company name, address, and website
• Primary contact person for this RFI (name, title, phone, email)
• Company history and size
• Third party business partners or co-partners
• Primary ownership of core software
• Office locations

3.2 Project team and approach

At PERS, we value the expertise, experience, and approach of the specific individuals
who would be working directly with us. Please provide information about:
• The proposed team structure for this project, including key roles, representative
experience and credentials.
• Describe the average number of dedicated people assigned to a large project
throughout the system development life cycle.
• Two to three examples of similar projects and include your high-level project
plans

3.3 Key capabilities

Please indicate your system's capabilities in the following key areas:

• Internal Activities
• Member Portal
• Employer Portal
• Workflow Management
• Document Management
• Member Education & Engagement
• Artificial Intelligence


In addition, please highlight any differentiating features as listed on the following pages.

Internal Activities Highlight Any Differentiating Features
Maintain and view demographic data
Maintain and view employment and
position data


Submit wage and contribution data similar
to employers


Maintain and view salary and contribution
data


Maintain and view service credit data


Maintain and view tier and plan data


Maintain and view member transactions


Maintain and view member earnings


Maintain and view general ledger
transactions


Maintain employer contribution rate
components for all plans


Maintain and view employer credits


Accept and view benefit applications


View and generate benefit estimates


Allow for divorce calculations, divorce
reductions, divorce deductions, and
alternate payee account creations


Allow for pre-retired death calculations


Allow for police and fire unit contribution
calculations


Allow for retirement calculations


Allow for withdrawal calculations


Allow for post-retirement death
calculations


Allow for disability calculations


Allow for manual employer and member
invoicing


Allow for manual checks


Payment for recipients (paper checks and
electronic funds transfer, both domestic
and international)


Allow for benefit adjustments (annual and
ad-hoc)


Maintain web accounts for member,
employer, and PHIP TPA portals


View and maintain member and employer
invoices

Member Portal Highlight Any Differentiating
Features
Account information access


Ability to update specific demographic
information


Access to documents (i.e. member annual
statements, 1099Rs)


Online transactions and form submission
(state type of transactions)


Benefit calculators


Status tracking


Seminar registration and appointment
scheduling


Ability to choose communications
preference (online versus paper)


Secured access (see more information in
the security section of this RFI, 6.1)


Ability to configure to our branding
standards


Ability to support all major devices and
browsers with responsive ADA compliant
UI/UX



Employer Portal Highlight Any Differentiating
Features
Ability to create, submit, and maintain
records and reports for demographic and
wage data


Ability to review submitted reports


Ability to review posted records


Ability to review data for all past, current,
and future employees reported to PERS


Access tasks submitted by PERS for data
verification, sick leave, salary certification,

View employer statements including side
accounts and statement history


View employer statement details by date
range in a filterable, sortable format


Generate member annual statements
extract data


Generate actuarial extract data

salary breakdown, or any other type of
data request needed (work item requests)

Ability to review and export employer
statements (financial statements) by plan
type, statement period, and fund


Secured access (see more information in
the security section of this RFI, 6.1)


Ability to communicate with PERS via the
portal


Ability to support all major devices and
browsers with responsive, ADA compliant
UI/UX



Workflow Management Highlight Any Differentiating
Features
Task assignment and tracking


Status updates visible to members


Process automation


Performance metrics




Document Management Highlight Any Differentiating
Features
Available system that works with new PAS


Integration with existing systems


Electronic forms


Digital signatures and alternative
authentication




Member Education and Engagement Highlight Any Differentiating
Features
Event scheduling capabilities


Appointment management


Virtual meeting support




Artificial Intelligence Highlight Any Differentiating
Features
Current AI capabilities


Member service applications


Administrative efficiency improvements

3.4 Implementation and support philosophy Please describe your team's
implementation and support approach:
• Implementation methodology
o Waterfall, Agile, hybrid?
• Approximate implementation timeline
o What is the estimated average timeline for a full implementation for an
organization like ours?
o What are the drivers for this timeline?
• Resource needs
o What resources do you dedicate to an implementation project and what
resources do you expect to be dedicated from the client?
• System Integrator
o Will a third-party System Integrator be hired to help implement your
product?
o Will the third-party systems integrator also support post go-live?
o How do you partner with client development teams?
• Development and Testing Processes
o Describe your SDLC, Quality Assurance, code quality, DevOps and defect
processes
• User Acceptance Testing
o What is your approach to User Acceptance Testing (UAT)?
o Describe your cut-over process and timeline
• Knowledge transfer approach
o What training programs and materials do you offer?
o Is it on-site, virtual or is self-paced training available?
• Post-implementation support model
o Describe your post-implementation support model.
o What is the release frequency and requirements for clients to
manage/accept releases?
o What are your standard Service Level Agreements for response and
resolution times for different severity levels?
• Client success philosophy

3.5 Innovation and partnership
Please describe:
• How your solution demonstrates innovation in pension administration
• Your approach to forming true partnerships with clients
• Any affiliations with third-party partners
• Current AI capabilities

4 Solution overview and functionality

4.1 PAS solution architecture and technology

• Provide a high-level overview of your PAS solution's architecture (cloud native,
microservices-based, SaaS, configurable off-the-shelf) and underlying technology
stack.

• Explain how your solution scales with growth and adapts to legislative or
business changes while minimizing customization
• Describe your approach to upgrades and releases, confirm compliance with
accessibility standards (ADA/WCAG), and summarize how modular or extensible
your solution is.
• Share your strategy for adopting emerging technologies (e.g., AI/automation)
and how testing and environments are managed to support ongoing
improvements.
4.2 Reporting and business intelligence

• Provide an overview of your standard reporting and ad-hoc/custom reporting
tools, including data extraction and export options
• Describe any integrated dashboards, analytics, or business intelligence
capabilities available within your solution.
•
5 Data migration and integration

5.1 Data migration strategy

• Provide a high-level overview of your approach to migrating data from legacy
systems, including methods, tools, and how you ensure data accuracy, integrity,
and security.
• Describe your system’s integration approach (APIs, connectors, data exchange
methods) and ability to connect with common external systems (e.g., payroll,
financial, actuarial).
• Explain how your platform ingests and exchanges external data (batch, real-time,
ad-hoc) and any support for protocols like FTP, eFax, or similar.
• Summarize how your solution captures data lineage, maintains audit trails, and
supports member correspondence through portals or other delivery models.



6 Security, compliance, and business continuity

6.1 Data security

• Describe your identity and access management capabilities, including supported
identity providers, authentication mechanisms (e.g., SSO, MFA), and identity
verification options.
• Provide an overview of your security architecture, including encryption (in
transit/at rest), access controls, handling of sensitive data (PII/PHI), and controls
around APIs and integrations.

• Explain how your system supports monitoring, audit logging, and reporting on
access/security events, as well as your approach to key management, secret
storage, and evidence of security controls.
• Summarize your security certifications (e.g., SOC 1/2, ISO 27001, HIPAA, GDPR,
FedRAMP, StateRAMP, NIST 800-53) and describe how you maintain compliance
with evolving data privacy regulations.
6.2 Disaster recovery and business continuity

• Outline your disaster recovery plan, including recovery time objective (RTO) and
recovery point objective (RPO).
• Describe your business continuity plan in the event of a major disruption.
• What are your data backup and restoration procedures for the platform?
• What type of high availability does your platform support?

7 Commercial information and pricing

7.1 Pricing model

• Describe your standard pricing model (i.e. subscription-based, per participant,
transaction-based, one-time license plus annual maintenance, or other).
• Provide a high-level estimated cost breakdown for:
o Software licensing and subscription fees. Include how cost is derived (e.g.,
number of members, number of employers, number of users, etc.)
o Implementation services. Include how cost is derived (e.g., lines of code,
complexity, number of integrations, etc.)
o Provide the average cost for implementation services within the first two
years of a project. Specifically separate costs if contracting with another
vendor for system integration services.
o Data migration services.
o Training.
o Ongoing annual support and maintenance.
o Are there any additional or hidden fees we should be aware of?
7.2 Contractual terms

• What are your typical contract terms and conditions for a PAS solution?
• Please provide a sample contract with your terms and conditions.

8 Vision and roadmap

8.1 Product roadmap

• Provide an overview of your product roadmap for the next one to three years.
• What new features, functionalities, or technological advancements are planned?
• How do you incorporate client feedback and industry trends into your roadmap?
• Include your roadmap for Artificial Intelligence for the next one to three years.
8.2 Future trends

• How do you see the pension administration landscape evolving in the next five to
ten years (i.e. artificial intelligence, machine learning, blockchain, enhanced
member engagement)?
• How is your solution positioned to address these future trends?

9 RFI response instructions

9.1 Submission format

• All respondents must register with the PERS portal for goods and services,
OregonBuys. Responses shall be submitted electronically in OregonBuys. PERS
asks that you review the link below to register:
https://oregonbuys.gov/bso/view/login/login.xhtml
• Please organize your response according to the sections and numbering
provided in this RFI.
• Clearly indicate any questions that cannot be fully answered or require additional
clarification.
• Provide detailed answers where requested but avoid excessive marketing
collateral in the core response. You may include an appendix for supplemental
materials, including case studies, white papers, additional architecture diagrams,
and others.
• Include a completed Attachment 1 and a redacted copy of your Response if
deemed applicable. Please refer to Section 1.2 under Public Record and Trade
Secret information.
Response Close Date: 10/31/2025 3:00PM (PST)

9.2 Questions and clarifications

• All questions regarding this RFI must be submitted in writing via OregonBuys by
10/17/2025 3:00PM (PST).
• Responses to all questions will be compiled and posted into OregonBuys by
10/21/2025 5:00PM (PST).


Thank you for your interest in partnering with PERS for our PAS modernization initiative.

ATTACHMENT A — DISCLOSURE EXEMPTION AFFIDAVIT
____________________ (Affiant), being first duly sworn under oath, and representing [insert
Respondent/Vendor Name] (hereafter “Respondent”), hereby deposes and swears or affirms
under penalty of perjury that:
1. I am an employee of the Respondent, I have knowledge of the Request for Information
referenced herein, and I have full authority from the Respondent to submit this affidavit and
accept the responsibilities stated herein.
2. I am aware that the Respondent has submitted a Response, dated on or about [insert date] (the
“Response”), to the State of Oregon (State) in response to Request for Information
Oregonbuys # S45900-00015032, for Pension Administration Systems, and I am familiar
with the contents of the Response.
3. I have read and am familiar with the provisions of Oregon’s Public Records Law, Oregon
Revised Statutes (“ORS”) 192.311 through 192.478, and the Uniform Trade Secrets Act as
adopted by the State of Oregon, which is set forth in ORS 646.461 through ORS 646.475. I
understand that the Response is a public record held by a public body and is subject to
disclosure under the Oregon Public Records Law unless specifically exempt from disclosure
under that law.
4. I have reviewed the information contained in the Response. The Responder believes the
information listed in Exhibit A is exempt from public disclosure (collectively, the “Exempt
Information”), which is incorporated herein by this reference. It is my opinion that the Exempt
Information is exempt from disclosure under Oregon’s Public Records Law under the
specifically designated sections as set forth in Exhibit A or constitutes “Trade Secrets” under
either the Oregon Public Records Law or the Uniform Trade Secrets Act as adopted in Oregon
because that information is either:
A. A formula, plan, pattern, process, tool, mechanism, compound, procedure, production
data, or compilation of information that:
i. is not patented,
ii. is known only to certain individuals within the Responder’s organization and that
is used in a business the Responder conducts,
iii. has actual or potential commercial value, and
iv. gives its user an opportunity to obtain a business advantage over competitors
who do not know or use it.
or
B. Information, including a drawing, cost data, customer list, formula, pattern,
compilation, program, device, method, technique or process that:

i. Derives independent economic value, actual or potential, from not being
generally known to the public or to other persons who can obtain economic value
from its disclosure or use; and
ii. Is the subject of efforts by the Responder that are reasonable under the
circumstances to maintain its secrecy.
5. I understand that disclosure of the information referenced in Exhibit A may depend on official
or judicial determinations made in accordance with the Public Records Law.
________________________________________________
Affiant’s Signature
State of ___________)
) ss:
County of ________)
Signed and sworn to before me on ___________ (date) by ______________________ (Affiant’s name).
________________________________________________
Notary Public for the State of _________________
My Commission Expires: _________

EXHIBIT A TO ATTACHMENT A
Responder identifies the following information as exempt from public disclosure under the
following designated exemption(s):