About Per Karlberg

Per Karlberg, a technology executive with extensive expertise in the intersection of real estate and technology, boasts an impressive academic background. He holds a Master of Science in Industrial Engineering and Management from The Faculty of Engineering at Lund University, specializing in Mathematical Modeling and Statistics. Additionally, he earned a Master of Science in Business and Economics from Lund University, focusing on Innovation and Strategic Management, and completed coursework at Nanyang Technological University in Singapore. As the CEO of our company and with three years of experience as the Co-Founder of ProptechOS, Per Karlberg has demonstrated exceptional proficiency in the field. He possesses comprehensive knowledge of real estate technology and the challenges confronting the industry, having played a pivotal role in spearheading the development of ProptechOS. This system optimizes real estate portfolios by leveraging data mapping and IoT technology. Per Karlberg's involvement as the co-founder of RealEstateCore, an open-source domain ontology fostering control over buildings and the creation of new services, has significantly shaped his expertise in proptech and real estate technology. He has contributed to mapping existing standards to RealEstateCore, enabling its function as a bridge between prevailing standards and the identification of common denominators. A noteworthy part of his contribution is found in a paper he co-authored, entitled "The realestatecore ontology" published in the proceedings of the 18th International Semantic Web Conference (ISWC 2019). This endeavor has been crucial in preparing buildings for interaction with Smart Cities and actualizing the potential of digital transformation and ESG breakthroughs within the real estate sector. For further information or professional inquiries, Per Karlberg can be contacted via LinkedIn at https://www.linkedin.com/in/perkarlberg/

Release notes – version 4.3.3

In this release We introduce breaking changes for Device. The relations Device servedBy Device Device servesDevice Device Device servesBuildingComponent Building Component Device servesBuilding Building now supports many-to-many and is represented in the API as arrays of IDs instead of single IDs. Space Collection is expanded with areaQuantities information. New Read more

By |2024-02-23T18:11:14+02:002022-11-28|Release Notes|

Release notes – version 4.3.2

In this release Building REC class model was expanded with primary basic building info: Address and Area Quantity. In this release a batch of new Asset subclasses was added.  New functionality RealEstate and Building basic info Now the RealEstate and Building twin objects may keep a list of Address Read more

By |2024-02-23T18:08:09+02:002022-11-07|Release Notes|

Release notes – version 4.3.1

In this release ProptechOS agent management functionality is expanded with application management. Applications like persons can be registered in the ProptechOS system, can be granted with resource permission policies and roles. New functionality Application Application - represents an application agent that can authenticate into ProptechOS and use the API Read more

By |2024-02-23T18:06:26+02:002022-10-13|Release Notes|

Release notes – version 4.3.0

In this release Significant changes are made in ProptechOS security and user management areas. Apart from resource permission policies users can be granted administration roles. ProptechOS is also introducing the Preview API. This API will include endpoints that are not necessarily following RealEstateCore of any version not necessarily supported Read more

By |2024-02-23T16:33:03+02:002022-09-22|Release Notes|

Release notes – version 4.2.7

In this release Streaming API improvement and fixes to the number of defects. New functionality Streaming API improvement Telemetry that is produced by Actuators with READ/WRITE functions is included in the Streaming API. Breaking changes None. Fixes and minor updated (internal links are added only for reference) Fixed defects: Read more

By |2024-02-26T12:17:13+02:002022-08-30|Release Notes|

Release notes – version 4.2.6

In this release This version includes significant delete operations improvements and a couple of PATCH operation improvements. New functionality Hard delete Simple delete means that the twin is archived in the database. Hard delete means complete database removal of the twin without leaving any fallback copy (except snapshot history). Read more

By |2024-02-23T16:08:20+02:002022-07-14|Release Notes|

Release notes – version 4.2.5

In this release Even more collection improvements are introduced, and a new collection subclass: Region. New functionality Region Region - collection sub-class that allows grouping twins of classes RealEstate and Building. New endpoints to manage Regions are introduced: Include twins into region - PUT /json/region/{id}/include Exclude twins from region Read more

By |2024-02-23T16:07:01+02:002022-06-23|Release Notes|

Release notes – version 4.2.4

In this release New Collection sub-classes are introduced: Apartment, TenantUnit, SpaceCollection. User sign up functionality is added. New functionality Apartment Apartment - collection sub-class that allows grouping twins of types Building and BuildingComponent. New endpoints to manage Apartments are introduced: Include twins into apartment - PUT /json/apartment/{id}/include Exclude twins Read more

By |2024-02-23T16:05:27+02:002022-06-16|Release Notes|

Release notes – version 4.2.3

In this release New twin sorting functionality is introduced. New functionality Sorting Since this release it is possible to retrieve sorted paged data. By default all paged data is provided as an unsorted collection. In order to obtain paged and sorted data, a new query parameter ‘sort’ is introduced. Read more

By |2024-02-26T12:19:21+02:002022-05-26|Release Notes|

Release notes – version 4.2.2

In this release New functionality Twin status All twin types are upgraded with new property ‘status’ which describes if the twin is valid or not. Possible status values are: ‘Valid’, ‘Incomplete’, ‘Incorrect’, ‘SuspectedInvalid’. When a twin is onboarded and no status value is provided, ‘Valid’ status will be set Read more

By |2024-02-23T16:02:50+02:002022-04-28|Release Notes|
Go to Top