HTTP Status 500 – Internal Server Error


Type Exception Report

Description The server encountered an unexpected condition that prevented it from fulfilling the request.

Exception

java.lang.NullPointerException

Note The full stack trace of the root cause is available in the server logs.


Apache Tomcat/8.5.43

  1. 当前位置:
  2. 首页
  3. 乡镇党代会年会制
  4. 详情

布尔津县:“党代表为民行”打通服务群众最后一公里

日期:2019-07-12 18:41:52
文章来源:布尔津县委组织部
浏览量:
【字体:

为深入基层调查研究,服务民生听民声,夯实服务群众工作基础,布尔津县充分发挥党代表的政治优势,探索开展了党代表为民行活动。

 

解民忧:巡访群众勇纳谏。实行党代表一室一线工作法。设立78个覆盖全县的党代表工作室,选派456名党代表轮流坐班接待;组织188名党代表,深入基层一线,采取走访座谈、发放问卷的方式,了解基层各族党员群众思想、宗旨、作风、纪律等方面的情况及期待解决的突出问题。先后共接待走访党员群众1300人次,征集意见建议6445条,为民解决287个,158个转交相关部门限时办理,进一步凝聚了党心民心。

 

重落实:挂任基层树表率。44名县党代表主动挂任村(社区)党支部第一书记,带头深入基层了解民情,宣传党的优惠政策,协调解决160余个有关子女入学、农牧灌溉、乡村道路、产业结构调整、增收致富的民生突出问题。采取邀请乡党代表、群众代表列席旁听,第一书记带头剖析自查自纠,限期公示整改等方式,先后召开62场次专题组织生活会、民生工作推进会,树立党代表务实为民的政治表率。

 

交新友:结对帮扶践承诺。广泛推行党代表与群众交朋友机制,组织78党代表与104名困难党员群众结成帮扶对子,公开承诺173件帮扶事项,通过送物资、送资金、送政策、经常性走访、节日重大事件主动走访、双语再结对等措施,先后送去钱物15万元,解决实际问题58件。实行半年一评一销帐制度,每半年公开承诺帮扶事项开展情况,征询帮扶对象满意度,满意度达标的予以销号,未达标的,限期整改,与年底考评相挂钩。

HTTP Status 500 – Internal Server Error

HTTP Status 500 – Internal Server Error


Type Exception Report

Description The server encountered an unexpected condition that prevented it from fulfilling the request.

Exception

java.lang.NullPointerException

Note The full stack trace of the root cause is available in the server logs.


Apache Tomcat/8.5.43

HTTP Status 500 – Internal Server Error

HTTP Status 500 – Internal Server Error


Type Exception Report

Description The server encountered an unexpected condition that prevented it from fulfilling the request.

Exception

java.lang.NullPointerException

Note The full stack trace of the root cause is available in the server logs.


Apache Tomcat/8.5.43

HTTP Status 500 – Internal Server Error

HTTP Status 500 – Internal Server Error


Type Exception Report

Description The server encountered an unexpected condition that prevented it from fulfilling the request.

Exception

java.lang.NullPointerException

Note The full stack trace of the root cause is available in the server logs.


Apache Tomcat/8.5.43