According to the PMBOK® Guide, Organizational Process Assets (OPAs) are the plans, processes, policies, procedures, and knowledge bases specific to and used by the performing organization. These assets influence the project ' s management and are internal to the organization.

OPAs are typically grouped into two categories:

Processes, Policies, and Procedures: These are usually established by the Project Management Office (PMO) or other governing bodies. Examples include standard templates, software tool requirements, and safety or ethics policies.

Organizational Knowledge Bases: These are used for storing and retrieving information. Lessons learned from previous projects, historical information, and completed project files are the most critical assets in this category as they help the project manager avoid " reinventing the wheel. "

Analysis of other options:

B. Information technology software and employee capability: These are categorized as Enterprise Environmental Factors (EEFs). EEFs are conditions, not necessarily under the immediate control of the project team, that influence, constrain, or direct the project.

C. Resource availability and employee capability: These are also EEFs. The existing skills of the workforce and the current availability of resources are environmental constraints the project manager must work within.

D. Marketplace conditions and legal restrictions: These are classic examples of External EEFs. They originate outside the organization (e.g., industry standards, government regulations, or economic climate) and are not considered internal process assets.

Per PMI standards, OPAs are the " internal wealth " of the company, and using policies and lessons learned ensures the project benefits from the organization’s collective experience.