flaik -> RTP Employee Config Interface

Current Implementations

Powdr	ADP -> flaik -> RTP
Alterra	Workday -> flaik -> RtP

Objectives

• Create a standard, static employee identification, unique per employee per resort within a centralized or decentralized environment.

• Minimize manual re-entry of employee information in multiple systems to reduce effort and data entry issues.

• Enable standard business process capabilities across all RTP Resorts, while retaining core scope.

Scope

In Scope

• Employees only

• Employee/Instructor Onboarding

Out Of Scope

• Dependents/Inheritance profiles

• Off boarding/hotlisting

• Continuous updates of employee information

• Preference from Resorts to allow nickname/contact info updates in RTP without being overwritten

• Automation of Badge ID creation in ADP Vantage

Import Logic/Profile Management

Matching Logic

• Employee ID

• Else: Look for customer matching on Email, First/Last Name and Birthdate

• If no match, new record will be created

Profile Management

• If relationship exists with inheritance of profiles, break the inheritance and write existing to each profile

• IP Type Code: Currently set to utilize Person or Employee Type

  • Investigation to occur to identify if status code types can be utilized to match to different employee types