Hacker News new | past | comments | ask | show | jobs | submit login

I work with multiple PMS platforms and centralizing even a simple unit price table is hellish given different PMS have different paradigms for concepts such as unit pricing. For example, Yardi (depending on the version of course) has 3 different tables for Market Price of a unit flying around in the backend, each with a slightly different definition.

Another issue (for users not API creators) is the lack of universal KPI definition - there are at least 6 major ways of calculating occupancy, each one needing its own specific dataset (economic occupancy, physical occupancy, economic occupancy revenue generating units, physical occupancy revenue generating units, trending occupancy, trending occupancy revenue generating units)

Concepts such as renewal ratio and collection ratio are particularly difficult due to their time component. Most of the pain comes not from getting the data out of the PMS through an API but rather knowing WHAT data is needed and for what KPI.




Totally agree! This is part of the conversation with each of our customers. We have learned early that this is a part of the pain and we are solving it in two ways:

1. Rapidly developing a deep understanding for naming and meaning within each PMS so we can speak intelligently, and properly guide our customers to focus on the data they care about.

2. Technically, we have data transformations at a couple different layers so we can repoint data coming in to exist in customer-specific locations for their business needs.


zdms, where do you work? would love to connect & chat more. i'm facing this same problem. my email in profile.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: