共查询到20条相似文献,搜索用时 62 毫秒
1.
2.
传统水利工程通常存在管理模式复杂、施工信息繁多、数据收集困难、可视化程度低等问题,研究在复杂管理模式下的信息化的工程管理手段,可有效提高水利工程管理的效率和水平,实现工程精细化管理。以海南省重大水利工程智能建造系统为例,提出 GIS + BIM 的水利工程两层级(集团级和项目级)架构的工程数字化管理系统的管理模式,可通过 PC 端和移动端 App 操作,结合工程建设期内各建设、监理、施工、设计及其他参建单位的工程建设管理需求,实现工程进度、质量、投资、安全等全要素的智能化管控。实际工程应用表明:该模式在复杂管理组织模式下能较快适应现场实际需求,发挥作用,为管理模式复杂的大型水利工程项目群施工期的建设管理提供参考。 相似文献
3.
FujiColorAPS彩色负片的标记采用“Nexla”。现推出ISO100、ISO200、ISO400三种感光度型号,且各有15张、25张及40张三种规格。FujiNexiaFIOO中间的F表示“细颗粒”,这种ISO100的富上彩色APS卷更适合于放大;FujiNexiaA200中间的A代表“多用途”,ISO20的富士APS彩卷号称万能胶卷。富士APS彩卷采用APEN新型纤薄又平整的片基,其颗粒比以往的135胶卷缩小30~50%,所以尽管APS系统的画幅较135的减小了40%,颗粒的缩微化至少是一种补偿。另外,富士在APS胶片上还采用了两项新技术:一是乳剂层减范专利,一是DIR结合剂… 相似文献
4.
5.
北京朗迈控制系统工程有限公司 《数字社区&智能家居》2006,(11):48-52
一、前言
随着建筑智能化技术的迅猛发展,楼宇自控系统已经成为了大型建筑的必备系统。据统计,建筑中楼宇自控系统部分的投资回收期为3年左右,远远高于建筑的其他部分;安装了楼宇自控系统的建筑运行费用和能耗比常规建筑低15%~30%,而售房率和出租率则比常规建筑高出约15%。因此,结合建筑物的实际需求,有目的的安装楼宇自控系统对降低建筑物的使用、管理和维护费用,有着非常重要的经济和现实意义。 相似文献
6.
7.
8.
织物缺陷在线检测是纺织行业面临的重大难题,针对当前织物缺陷检测中存在的误检率高、漏检率高、实时性不强等问题,提出了一种基于深度学习的织物缺陷在线检测算法。首先基于GoogLeNet网络架构,并参考其他分类模型的经典算法,搭建出适用于实际生产环境的织物缺陷分类模型;其次利用质检人员标注的不同种类织物图片组建织物缺陷数据库,并用该数据库对织物缺陷分类模型进行训练;最后对高清相机在织物验布机上采集的图片进行分割,并将分割后的小图以批量的方式传入训练好的分类模型,实现对每张小图的分类,以此来检测缺陷并确定其位置。对该模型在织物缺陷数据库上进行了验证。实验结果表明:织物缺陷分类模型平均每张小图的测试时间为0.37 ms,平均测试时间比GoogLeNet减少了67%,比ResNet-50减少了93%;同时模型在测试集上的正确率达到99.99%。说明其准确率与实时性均满足实际工业需求。 相似文献
9.
Dennis van Booma 《国内外机电一体化技术》2006,9(5):97-98
问题1:传统布线与PROFIBUS布线的价格比如何?
众所周知,PROFIBUS的布线成本比传统布线的成本更节省,事实上,不仅如此,随之相关的其它费用也减少了不少。如:减少了缆线支架,节省能源,简化了档,使界面概观更清晰,减少了测试时间和零件,更易于扩展与改变,由于维修及时大大降低停工周期,这只是基础结构及最初成本的节省;而真正意义上的成本节省开始于维护和运行费用。PROFIBUS是一个非常好的选择,但要经过一些培训才能了解其优越性。 相似文献
10.
传统工艺中对压力容器汽缸中圆堵板的厚度设计采用经验公式,而为了保证产品的安全性能预留余量过大,造成了严重的材料浪费.针对此问题,采用ANSYS软件对常用碳素结构钢Q235-A铸成的不同直径的圆堵板进行不同承压情况下的有限元分析,以工程应用中的许用应力为标准,不断进行有限元计算,直到优化出在满足强度条件下以最小值承受一定压强的堵板厚度值.在将最佳厚度值与经验值进行对比分析的基础上,对经验公式进行修正,并应用到工程实际中,结果表明修正后的厚度在满足安全性的同时节省了30%的材料,因此采用该方法设计圆堵板厚度具有科学性和可行性. 相似文献
11.
This paper tentatively discusses the necessity and the requirements to better educate joint UB1-HIT master students from an engineering and engineer's perspective.The author argues that the students should have a broader engineering culture.After having given the context and basic definitions,the paper presents the author's view on how to better develop the engineering capabilities from a knowledge acquisition and learning point of view.Requirements for engineering education are addressed,based,among others,on the professional experience the first author built up while serving as senior manager in information technology and business transformation,at Capgemini Consulting(Belgium).A series of conclusions are given at the end of the paper. 相似文献
12.
13.
信息服务工程与管理专业的精英式工程教育模式探讨 总被引:1,自引:0,他引:1
Under the guidance of the training tactics for the graduate, "first to guarantee the solid technology, then to expand the knowledge field of management and business", the new discipline named Information Service Engineering and Management introduces eleven courses mentioned below:, , , , , , , , , , , 9 courses of which will be first introduced in SSDUT. In the second term for the juniors, basing on the course of Project Management Method and Practice and Web Development Technology and Practice, with the orientation of project practice, focusing on the main line of students, elite engineering education is to be promoted through team development practice with whole interaction in the certain classrooms to cultivate compound talents with comprehensive knowledge of technology, management and business. 相似文献
14.
以培养应用型人才为目标,突出能力培养主线,分析新工科教育下应用型人才的能力要求,对软件工程课程教学案例的选择、设计思路和实施过程进行探讨,强调学生动手操作,通过对案例进行解剖和验证,掌握知识,提升能力。 相似文献
15.
工程实践是软件工程专业建设十分重要的环节,如何通过与企业深入合作,在实战中培养从事大规模软件工程的软件人才,是建设软件工程专业的院校都需要面临的问题。本文介绍了浙江大学软件工程专业以大规模国际化产学研合作项目为基础,在教育体系、课程体系、工程实践体系和校企合作生态环境建设等方面进行的深入探索和创新。十余年的实践效果表明,探索取得了良好的建设成效。 相似文献
16.
17.
18.
Knowledge engineering stems from E. A. Figenbaum's proposal in 1977, but it will enter a new decade with the new challenges. This paper first summarizes three knowledge engineering experiments we have undertaken to show possibility of separating knowledge development from intelligent software development. We call it the ICAX mode of intelligent application software generation. The key of this mode is to generate knowledge base, which is the source of intelligence of ICAX software, independently and parallel to intelligent software development. That gives birth to a new and more general concept "knowware". Knowware is a commercialized knowledge module with documentation and intellectual property, which is computer operable, but free of any built-in control mechanism, meeting some industrial standards and embeddable in software/hardware. The process of development, application and management of knowware is called knowware engineering. Two different knowware life cycle models are discussed: the furnace model and the crystallization model. Knowledge middleware is a class of software functioning in all aspects of knowware life cycle models. Finally, this paper also presents some examples of building knowware in the domain of information system engineering. 相似文献
19.
This paper analyzes the new demands of software engineering talent training under the background of emerging engineering education, in order to clarify the direction of software engineering teaching reform, and discusses the issue of how to build core competencies of software engineering talent. This paper takes "consolidating professional foundation, training practical ability and improving innovation ability" as the goal of software engineering talent training, puts forward the conception of software engineering teaching reform with "reconstructing the core course platform, improving the practice teaching system, and creating an innovation training environment", and expounds the teaching reform practice activities based on this conception. Finally, the paper summarizes the achievements of teaching reform. 相似文献
20.
Software, Software Engineering and Software Engineering Research: Some Unconventional Thoughts 总被引:1,自引:0,他引:1
下载免费PDF全文
![点击此处可从《计算机科学技术学报》网站下载免费的PDF全文](/ch/ext_images/free.gif)
Software engineering is broadly discussed as falling far short of expectations. Data and examples are used to justify how
software itself is often poor, how the engineering of software leaves much to be desired, and how research in software engineering
has not made enough progress to help overcome these weaknesses. However, these data and examples are presented and interpreted
in ways that are arguably imbalanced. This imbalance, usually taken at face value, may be distracting the field from making
significant progress towards improving the effective engineering of software, a goal the entire community shares. Research
dichotomies, which tend to pit one approach against another, often subtly hint that there is a best way to engineer software
or a best way to perform research on software. This, too, may be distracting the field from important classes of progress. 相似文献