What is recommended in this period is a smart property integrated management platform — MicroCommunity.

HC community property management system is an open source project of back-end separation and distributed architecture initiated by java110 team in April 2017. Currently, the code is open source on github and gitee. The open source projects include HC community management system back-end, HC community management system front-end, and HC community management system back-end. HC Community management system owner mobile version and HC community management system property mobile version.

Function diagram

Flow chart

1.0 Agent Add cell

Agent user opens “Community management” –> Cell Information menu Add cell and refine information such as cell name, cell address, and cell region, submit it to the operations team for review.

2.0 Operator Audit cell

At present, the operator only participates in the review and management of the addition of the community, that is to say, the management of agents. The specific property information should be managed by agents as much as possible. If you do not want to use the role of agents, it is OK.

< p data – track = “15” > < strong > 3.0 property into community < / strong > < / p >

After registering an account through the registration page, the property will jump to the page of perfecting merchant information when logging in with the registered account. If you perfect merchant information in this page and submit it, the property account will jump to the home page. At this time, many functions of the property account cannot be operated before you move into the community. Need to settle in the community to operate, click “community management” –> My community page settled community.

4.0 Agent audit settled

Agents log in the system to review the property settled in the community, and manage in the community –> Audit the merchant, according to the merchant information audit pass or fail.

< p data – track = “19” > < strong > 5.0 property organization Settings < / strong > < / p >

Property organization management is currently divided into head office and branch office. Head office is the property of the group, and branch office is the property of each community. Theoretically, we will establish a branch office for each community, and then bind the community to the branch office, so that the employees under the branch office can manage the community.

6.0 Bind the branch office to the management area

Bind the corresponding community for each branch. If a property team manages multiple communities, bind the corresponding community for him.

7.0 Adding Employees

At present, our employees can only be added to the department, that is, the lower door of the branch. After adding employees, the login account is the name and password is 123456, and please timely change the password after logging in. The community owned by the employee is the community owned by his upper branch.

8.0 Assigning permissions

Rights are divided into rights groups and rights. We suggest that each department or group should be given priority to establish rights groups, and employees should be empowered directly with rights groups.

9.0 Employee login

Add employee The default account is employee name and password is 123456. The password varies according to the platform developer account definition. The current demo environment is 123456. Change the password and assign rights according to 8.0. Employees can only view the menus that have been assigned rights.

10.0 Introduction of property assets in the current community

Employee opens system management –> The template contains the building unit owner information cost setting housing information parking information and other functions require property personnel to fill in the data according to excel requirements, and then import it at the asset import place, so that the information in the community is successfully imported and can be used as normal fees.

Data model graph

System requirements

Development tools

java1.8, idea/eclipse, mysql, redis

Hardware requirements

Test environment Basic requirements: 4 cpus, 16G memory and 80G hard disk

Software requirements

Need to install yourself: mysql5.6, zookeeper, Redis, and kafka

Need to start: service-eureka, service-api, service-order, service-community, service-store, service-user, service-front, service-fee, service-common, and service-job

Source code

HC cell back-end code :
https://gitee.com/wuxw7/MicroCommunity

HC block code :
https://gitee.com/java110/MicroCommunityWeb

HC Smart family (public number and small program) :
https://gitee.com/java110/WechatOwnerService

HC Palm property :
https://gitee.com/java110/PropertyApp

System screenshot

—END—

Open Source protocol: Apache2.0