PIP STS02380 application for ACI 336.1-01, spec for construction of drilled piers

合集下载

Eaton Intelligent Power Protector (IPP) 软件安全漏洞通知说明

Eaton Intelligent Power Protector (IPP) 软件安全漏洞通知说明

v1.0Eaton Vulnerability Advisory© 2022 Eaton All Rights Reserved Page 1 of 4ETN-VA-2022-1011: Security Vulnerabilities in IPP versionsOverviewEaton has discovered security vulnerabilities in older versions of its Intelligent Power Protector (IPP) software. IPP software provides graceful, automatic shutdown of network devices during a prolonged power disruption, preventing data loss and saving work-in progress. As part of Eaton's power network management system, IPP works alongside Eaton Intelligent Power Manager to deliver comprehensive power management and protection.Vulnerability DetailsIt has been observed that the IPP versions prior to version 1.71 have the following vulnerabilitiesCVE-2022-33861:CVSS v3.1 Base Score – 5.1 CVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:LCWE 345: Insufficient verification of data authenticityIPP software versions prior to v1.71 do not sufficiently verify the authenticity of data, in away that causes it to accept invalid data.CVE-2022-33862:CVSS v3.1 Base Score – 6.7 CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HCWE-693: Protection Mechanism Failure.IPP software prior to v1.71 is vulnerable to default credential vulnerability. This couldlead attackers to identify and access vulnerable systems.Affected Product(s) and Version(s)All IPP versions released prior to 1.71Remediation & MitigationRemediationEaton has remediated the vulnerabilities in IPP software version 1.71. Customers can update their software through the following link .MitigationTo mitigate the risk, Eaton reminds customers to follow the general security best practices outlined below.General Security Best Practices•Restrict exposure to external networks for all control system devices and/or systems and ensure that they are not directly accessible from the open Internet.•Deploy control system networks and remote devices behind barrier devices (e.g. firewalls, data diodes) and isolate them from business networks.•Remote access to control system networks should be made available on a strict need-to-use basis. Remote access should use secure methods, such as Virtual Private Networks (VPNs), updated to the most current version available.•Regularly update/patch software/applications to latest versions available, as applicable.•Enable audit logs on all devices and applications.•Disable/deactivate unused communication channels, TCP/UDP ports and services (e.g., SNMP, FTP, BootP, DHCP, etc.) on networked devices.•Create security zones for devices with common security requirements using barrier devices(e.g. firewalls, data diodes).•Change default passwords following initial startup. Use complex secure passwords or passphrases.•Perform regular security assessments and risk analysis of networked control systems.For more details on cybersecurity best practices and leverage Eaton’s Cybersecurity as a Service, please consult the following –•Eaton offers a suite of cybersecurity assessment and life-cycle management services to help identify vulnerabilities and secure your operational technology network. These services canhelp you complete the recommended remediation and mitigation actions and strengthen your overall network security. More information about these services is available at/cybersecurityservices. If you need immediate support, please call +1-800-498-2678 to connect with a representative.•Cybersecurity Considerations for Electrical Distribution Systems (WP152002EN)•Cybersecurity Best Practices Checklist Reminder (WP910003EN)Additional Support and InformationFor additional information, including a list of vulnerabilities that have been reported on our products and how to address them, please visit our Cybersecurity web site /cybersecurity, or contact us at ***************.Legal Disclaimer:TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, INFORMATION PROVIDED IN THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND. EATON, ITS AFFILIATES, SUBSIDIARIES, AND AUTHORIZED REPRESENTATIVES HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS OF ANY KIND EITHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING, BUT WITHOUT LIMITATION, ANY IMPLIED WARRANTIES AND/OR CONDITIONS OF SECURITY,COMPLETENESS, TIMELINESS, ACCURACY, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. YOU ARE SOLELY RESPONSIBLE FOR REVIEWING THE USER MANUAL FOR YOUR DEVICES AND GAINING KNOWLEDGE ON CYBERSECURITY MEASURES. YOU SHOULD TAKE THE NECESSARY STEPS TO ENSURE THAT YOUR DEVICE OR SOFTWARE IS PROTECTED, INCLUDING CONTACTING AN EATON PROFESSIONAL. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES OR LIMITATIONS, SO THE ABOVE LIMITATIONS MAY NOT APPLY. TO THE EXTENT PERMITTED BY LAW, IN NO EVENT WILL EATON OR ITS AFFILIATES, OFFICERS, DIRECTORS, AND/OR EMPLOYEES, BE LIABLE FOR ANY LOSS OR DAMAGE OF ANY KIND WHATSOEVER, INCLUDING, BUT NOT LIMITED TO, ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, STATUTORY, PUNITIVE, ACTUAL, LIQUIDATED, EXEMPLARY, CONSEQUENTIAL OR OTHER DAMAGES,EVEN IF EATON HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE USE OF THIS NOTIFICATION, INFORMATION CONTAINED HEREIN, OR MATERIALS LINKED TO IT ARE AT YOUR OWN RISK. EATON RESERVES THE RIGHT TO UPDATE OR CHANGE THIS NOTIFICATION AT ANY TIME AND AT ITS SOLE DISCRETION.About Eaton:Eaton is a power management company. We provide energy-efficient solutions that help our customers effectively manage electrical and mechanical power more efficiently, safely, and sustainably. Eaton is dedicated to improving the quality of life and the environment using power management technologies and services. Eaton has approximately 85,000 employees and sells products to customers in more than 175 countries.Revision Control:Office:Eaton, 1000 Eaton BoulevardCleveland, OH 44122, United States。

failed to initialize sentinel

failed to initialize sentinel

failed to initialize sentinelSentinel is an open-source framework designed to provide real-time operational visibility, traffic control, and protection against various failure scenarios in modern distributed systems. It aims to address common challenges faced by microservices-based architectures, such as flow control, traffic shaping, rate limiting, and circuit breaking. However, in some cases, initializing Sentinel might encounter errors or failures. Let's explore the possible reasons and solutions for the "failed to initialize Sentinel" issue. 1. Incorrect Configuration:One common reason for the failure to initialize Sentinel is incorrect configuration. Check if the configuration file contains any errors or misconfigurations. Ensure that the configuration file has the correct format, with all the required parameters properly defined. Verify that the configuration file is being loaded correctly by the application.2. Conflicting Libraries or Dependencies:Sentinel relies on various underlying libraries and dependencies. In case of conflicts or incompatible versions between these libraries, it can result in initialization failures. Make sure that the versions of all the libraries used by Sentinel are compatible and do not conflict with other dependencies of the application.3. Resource Exhaustion:Sometimes, the failure to initialize Sentinel can occur due to resource exhaustion. Check if the system where Sentinel is being initialized has enough resources, such as memory and CPU. If the system is running low on resources, consider allocating moreresources or optimizing the application to reduce its resource requirements.4. Network Connectivity Issues:Sentinel relies on network connectivity for communication between different components. Any network connectivity issues, such as firewall restrictions or network configuration problems, can lead to initialization failures. Ensure that the network is properly configured, allowing the required communication between different components of Sentinel.5. Data Persistence Issues:Sentinel uses data persistence to store its internal state and configuration. If there are any issues with the data persistence layer, such as database connectivity problems or storage corruption, it can result in the failure to initialize Sentinel. Verify that the data persistence layer is functioning correctly and accessible by Sentinel.6. Insufficient Permissions:Lack of sufficient permissions can also cause the failure to initialize Sentinel. Ensure that the user or process initializing Sentinel has the necessary permissions to access and modify the required resources, such as configuration files, network ports, or data persistence layer.7. Known Bugs or Issues:Check if there are any known bugs or issues reported for the version of Sentinel being used. Sometimes, the failure to initialize can be due to a known bug that has been fixed in a newer version.Updating to the latest version of Sentinel can help resolve such issues.8. Debugging and Logging:Enable debugging and logging for Sentinel to get more detailed information about the initialization process. Analyze the logs and debug output to identify any specific errors or exceptions that might be causing the failure. This can provide valuable insights into the root cause of the issue and help in troubleshooting. Remember, the above suggestions are general in nature, and the specific solution to the "failed to initialize Sentinel" issue may vary depending on the context, environment, and specific error messages. It is recommended to consult the official documentation, community forums, or seek assistance from Sentinel's support channels for more specific guidance in troubleshooting and resolving the initialization failures.。

开放API使用常见错误及解决方法总结(六)

开放API使用常见错误及解决方法总结(六)

开放API使用常见错误及解决方法总结引言:在当今数字化的时代,开放API(Application Programming Interface)已成为让不同系统、平台互相连接和数据交互的重要工具。

然而,由于其复杂性和技术要求,许多人在使用开放API时会遇到一些常见的错误。

本文将总结一些开放API使用中的常见错误,并提供相应的解决方法,帮助读者更好地理解和使用开放API。

一、不理解API的基本概念和工作原理API是什么?开放API是一种允许不同软件系统之间相互访问和交换数据的接口。

它定义了软件组件之间的规范和通信机制,使得不同系统、平台之间可以实现数据的共享和交互。

工作原理开放API的工作原理主要包括请求和响应两个过程。

用户通过向API发送请求来获取特定的数据或执行特定的操作,API则根据请求返回相应的数据或结果。

解决方法:要正确使用开放API,首先要对API的基本概念和工作原理有清晰的理解。

可以通过查阅相关文档、教程或参加相关的培训课程来深入了解API的工作原理和使用方法。

二、错误的请求参数或格式缺少必要的参数在向API发送请求时,某些参数可能是必需的,如果缺少了这些参数,API可能会返回错误或无效的数据。

参数格式错误有些API要求参数的格式必须符合特定的规范,如果请求参数的格式错误,API可能无法正确识别和处理请求。

解决方法:在使用API时,务必仔细查阅API文档,了解请求参数的要求和格式。

在发送请求之前,可以使用参数验证工具或参考样例代码来确保请求参数的正确性。

此外,也可以向API提供商咨询,以确保正确使用API。

三、认证和授权问题API密钥缺失或错误许多开放API使用OAuth或API密钥进行认证和授权。

如果用户没有正确配置或提供API密钥,API将拒绝请求。

认证过期或无效有些API要求认证令牌具有一定的有效期,如果过期了或是无效的,API也会拒绝请求。

解决方法:在使用需要认证和授权的API时,务必要正确配置和提供API密钥。

开放API使用常见错误及解决方法总结(一)

开放API使用常见错误及解决方法总结(一)

开放API使用常见错误及解决方法总结引言:在信息技术迅猛发展的时代背景下,开放API(Application Programming Interface)正逐渐成为众多互联网企业的标配。

它为开发者提供了访问某个软件应用或服务的接口,为企业与用户之间打通了沟通的桥梁。

然而,由于使用API具有一定的复杂性,开发者们在实践中常常存在一些常见错误。

本文将探讨开放API使用中常见错误并提供相应解决方法。

一、缺乏认证和授权机制API的认证和授权是保障数据安全的重要手段。

然而,许多开发者在使用API时忽略了这一环节,或者只是简单地使用了基础的认证方式。

这样的做法使得系统的数据容易受到非法访问和篡改。

解决方法:1. 使用OAuth 认证协议来确保API的信息安全。

OAuth 使用令牌(Token)来对请求进行认证和授权,确保只有合法的用户才能访问API。

2. 学习和使用哈希算法,对重要数据进行加密。

采用哈希算法可以将原始数据转化为一定长度的密文,同时保持数据的完整性。

二、频繁的API调用在使用API时,一些开发者可能会频繁地调用同一个接口,这将给服务器带来巨大的压力,并可能导致接口的响应延迟增加。

解决方法:1. 优化API调用逻辑,减少不必要的请求。

可以通过缓存数据、合并请求等方式减少API调用的频率。

2. 合理设置缓存策略,将一些常用的数据存储在本地,避免每次请求都去服务器获取。

三、不合理的错误处理在使用API时,经常会遇到各种错误,如网络故障、服务器异常等。

然而,有些开发者对这些错误处理不当,导致用户体验下降甚至系统崩溃。

解决方法:1. 针对不同类型的错误进行分类处理。

可以使用try-catch语句捕捉异常,根据不同的错误类型进行相应的处理和反馈给用户。

2. 引入错误日志,记录错误的详细信息。

当发生错误时,可以通过查看日志来了解具体的原因,并解决问题。

四、忽视API版本更新开放API随着系统的迭代更新,版本也会不断升级。

Theapplicationhasfailed...(应用程序配置不正确)

Theapplicationhasfailed...(应用程序配置不正确)

Theapplicationhasfailed...(应⽤程序配置不正确)在我们开发⼯程中,可能有些情况下,不能在本机进⾏调试。

这个时候我们⼀般会使⽤VM(vmware)建⽴⼀个虚拟机环境,然后把编译过的程序放在该虚拟机环境下执⾏调试。

可是在某些情况下,不管我们编译的是debug还是release版本,在虚拟机环境中都会报“由于应⽤程序配置不正确,应⽤程序未能启动。

重新安装应⽤程序可能会纠正这个问题。

”(The application has failed to start because its side-by-side configuration is incorrect.Please see the application event log or use the command-line sxstrace.exe for more detail.)这样的错误。

转载请标明出处。

以前我遇到这样的问题,⼀般会认为是⼏个CRT库没有拷贝到虚拟机环境。

可是这个⽅法对我所遇到的场景不奏效,于是我⼜在虚拟机中装上了我程序的开发环境VS2005。

可是在真实机中⽣成的⽂件依然不能在虚拟机中运⾏,仍然报以上的错误。

其实微软在其⽹站上提供了⼀种解决⽅案,也⾮常简单。

原⽂地址我找不到了,我只针对我的VS2005做了⼀个解决⽅案以作事例。

1 建⽴⼀个安装程序⼯程。

2 ⼯程⽂件中加⼊Merge Module3 从系统盘:\Program Files\Common Files\Merge Modules选择加⼊需要的⽂件因为我的IDE环境是xp(32bit)+VS2005,所以我选择了以下⽂件(是我环境中所有的VC80+x86的⽂件,可能不同环境这些⽂件个数不同)policy_8_0_Microsoft_VC80_OpenMP_x86.msmpolicy_8_0_Microsoft_VC80_MFCLOC_x86.msmpolicy_8_0_Microsoft_VC80_MFC_x86.msmpolicy_8_0_Microsoft_VC80_DebugOpenMP_x86.msmpolicy_8_0_Microsoft_VC80_DebugMFC_x86.msmpolicy_8_0_Microsoft_VC80_DebugCRT_x86.msmpolicy_8_0_Microsoft_VC80_CRT_x86.msmpolicy_8_0_Microsoft_VC80_ATL_x86.msmMicrosoft_VC80_OpenMP_x86.msmMicrosoft_VC80_MFCLOC_x86.msmMicrosoft_VC80_MFC_x86.msmMicrosoft_VC80_DebugOpenMP_x86.msmMicrosoft_VC80_DebugMFC_x86.msmMicrosoft_VC80_DebugCRT_x86.msmMicrosoft_VC80_CRT_x86.msmMicrosoft_VC80_ATL_x86.msm4 ⽣成debug和release版⽂件5 在虚拟机中安装上步⽣成的⽂件经过以上步骤,我们编的debug和release版程序便可在虚拟机⾥正常运⾏了。

解决SpringBoot加载application.properties配置文件的坑

解决SpringBoot加载application.properties配置文件的坑

解决SpringBoot加载application.properties配置⽂件的坑SpringBoot加载application.properties配置⽂件的坑事情的起因是这样的⼀次,本⼈在现场升级程序,升级完成后进⾏测试,结果接⼝调⽤都报了这么个错误:⼤概意思是https接⼝需要证书校验,这就奇怪了,项⽬启动加载的是包外的application.properties配置⽂件,配置⽂件⾥没有配置使⽤https啊。

本⼈马上检查了下包内的application.properties配置⽂件,发现包内确实配置了https相关的配置项:明明包外的配置⽂件优先级⾼于包内的,为啥包内的⼀部分配置项起作⽤了呢,我们了解的配置⽂件优先级是这样的:这是为啥呢?后来才了解到除了⾼优先级覆盖低优先级外,还有⼀条重要的规则:如有不同内容,⾼优先级和低优先级形成互补配置。

这下才恍然⼤悟,我包外的配置⽂件⾥把https相关的配置项注释掉了,相当于没有这个配置项,但是包内的配置⽂件有,根据互补原则,包内的这⼏个配置项起作⽤了。

问题原因找到了,如何解决呢?要不我把包内的那⼏个配置项也注释掉,重新打个包?其实不必这么⿇烦,通过-Dspring.config.location命令直接指定包外的配置⽂件就可以了,试了下,果然没有问题了。

问题虽然解决了,但是还有些疑问,为啥指定包外的配置⽂件后就不存在互补情况了呢?通过阅读springboot相关源码,找到了答案:⼤概意思是:如果-Dspring.config.location指定了配置⽂件,则只加载指定的那⼀个配置⽂件,如果没有专门指定配置⽂件则遍历包外、包内相关的配置⽂件,按照⾼优先级覆盖低优先级和互补原则进⾏加载。

弄明⽩这些问题后,实地部署项⽬的时候,保险起见还是通过-Dspring.config.location命令直接指定加载的配置⽂件⽐较好,避免出现⼀些不必要的⿇烦。

Spring Boot加载application.properties探究基于Spring Boot的多Module项⽬中,有许多公共的配置项,为避免在每个接⼊层都配置⼀遍,⼀个设想是在公共依赖的Module的application.properties(application.yml)中进⾏配置。

Theapplicationfa...

Theapplicationfa...

The application failed to initialize the solution(应用程序初始化失败的解决方案)The application failed to initialize (0xc0000135). Click OK to terminate the application"Memory is not a simple solution to the read/written problem:Please, use for reference:First, the possibility of hardware is relatively small, and if it is hardware, it should be caused by memory incompatible with the host, if you can exclude the reasons for the hardware (memory bar is not compatible, replace memory). Loose memory or the accumulation of dust, clean the dust and replug look down):Two, system or other software caused by the following methods: the system itself has problems, timely installation of the official release of the patch, reinstall the system if necessary. Virus problem: antivirus. Antivirus software conflicts with other software: uninstall software that has problems. Is the graphics card or sound card driver properly installed or is it maliciously covered? Reinstall the video card sound driver.1, the use of the system comes with the SFC command, repair the damaged system files to return to normal.To start running, enter CMD, open a command prompt window, input string command sfc/scannow to enter, patiently waiting for thecommand for each file search system to scan once found is not the correct version of the file system or the system file is damaged, it will automatically pop-up interface, insert Windows system installation CD, the extracted file system from normal to replace the normal file system to achieve the purpose of repair system files and finally restart the computer.2, install Domino this procedure leads to a problem, you can start to run to msconfig and start the project to close the Domino startup items, if the system is shut down, not with Kaka aides settings like the software to turn off, if it forcibly or not to prove your system, then reinstall or poisoning recovery completely solve the system backup.Three, some system services are disabled and may cause similar problems. For example, when the QoS RSVP local communication control installation function is disabled, it may prompt that the RPC server is unavailable. Solution: my computerright-click management service and application QoS service RSVP double-click on the project to change the startup type to manual or automatic. If other services are disabled, problems can also be reset by this method.Four, browser memory can not read and write prompts:1, run regedit to enter the registryHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersio n\Explorer\ShellExecuteHooksThis location has a normal key value,{AEB6717E-7E19-11d0-97EE-00C04FD91972}, and a "default" reservation. Other deletions are removed.2, open the CMD window, enter the following command:For,%i, in (%windir%\system32\*.dll), do, regsvr32.exe, /s,%i, returnFor,%i, in (%windir%\system32\*.ocx), do, regsvr32.exe, /s,%i, returnTwo, respectively, after the completion of the operation, restart the machine.Five, if the above method can not be solved, only use the last move:Fully registered DLL: turn on "run", enter "CMD", enter "enter"Then put the following line characters are copied to the black box to enter CMD wait for all DLL files registered off it, in order to prevent the input error can copy this instruction, and then click the right mouse button to paste to enter at the command prompt after patiently waiting, until the screen rolling stop.(here is the code to run.):For,%1, in (%windir%\system32\*.dll), do, regsvr32.exe, /s,%1Restart the machine after completion.Six, if your computer inside the Microsoft NET.Framework component service and you don't use it, then uninstall this service may solve the problem: to start setting the control panel to add remove programs to NET.Framework and delete (if you must use it to restart the computer again after the installation of NET.Framework).Seven. Close this report:1. Right click on "my computer" on the desktop "property", "advanced property", "error report", "wrong report", "check", "disable error reporting" - "but notify me when serious error occurs". This way, for a few small errors, Windows XP won't pop up any errors.2, if not, completely shut down the error reporting service. Start to run in the input to services.msc and open the "services" window to find "Error Reporting Service" to open the "properties" dialog box, Error Reporting Service will be the "startup type" to "disabled" to determine the system restart. (this project closes the registry: start, run, enter, regedit, confirm, find HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows, change the NT\CurrentVersion\AeDebug] in Auto=0 to Auto=1)Important: do not just look at the error code, but to see: above the box shaped part of the blue tip is XXX.EXE that position is what the general positioning procedures, mainly caused by the conflict or error. The simple and effective way to deal with this is to look at the error hint, which software conflicts cause the software to be uninstalled. After you restart themachine, you can shut down the antivirus software first and run the installation again.。

开放API的故障排除与故障恢复指南(六)

开放API的故障排除与故障恢复指南(六)

开放API的故障排除与故障恢复指南随着数字化时代的到来,开放API(Application Programming Interface,应用程序接口)的应用越来越广泛,成为互联网产业中的重要一环。

开放API使得软件系统可以与其他系统进行无缝集成,实现更高效的数据传递和功能扩展。

然而,由于各种原因,API故障是不可避免的。

本文将探讨开放API故障的常见原因、排除方法和恢复指南。

一、故障原因1. 服务器过载:当API请求的数量超过服务器的处理能力时,服务器可能会崩溃或响应时间延长。

这种情况下,可以通过增加服务器容量或优化代码来解决。

2. 网络问题:API请求在传输过程中可能会遇到网络异常,如网络延迟、丢包等。

这时可以通过优化网络或增加冗余节点来提高系统的稳定性。

3. 数据库故障:API通常需要与数据库进行数据交互,数据库故障可能导致API请求失败或数据不一致。

为了避免这种情况,可以采用数据库集群、备份等措施。

4. 代码bug:由于编码或设计错误,API可能会返回错误的数据或无法正常工作。

为了排除这种故障,可以进行代码审查、单元测试和集成测试。

二、排除方法1. 监控和日志:通过在API系统中部署监控工具和日志系统,可以及时发现故障并分析原因。

监控可以检测系统的运行状态,提前发现潜在的故障风险;日志可以记录系统的运行过程,方便故障排查和问题定位。

2. 异常处理:为API设置合适的异常处理机制,当出现错误时能够及时捕获异常并给出相应的错误信息,提高系统的容错性。

同时,合理使用HTTP状态码可以告知请求方错误的类型,方便其进行相应处理。

3. 全面测试:在API上线之前,进行全面的功能测试、性能测试和负载测试。

功能测试可以验证API的各项功能是否正常;性能测试可以评估API的处理能力和响应时间;负载测试可以模拟高负载情况下API的稳定性和可靠性。

4. 限流和熔断:当API面临过多请求时,可以通过设置限流策略,控制请求频率,防止服务器过载。

  1. 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
  2. 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
  3. 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。

COMPLETE REVISIONFebruary 2009Process Industry PracticesStructuralPIP STS02380Application of ACI 336.1-01,Specification for the Construction ofDrilled PiersPURPOSE AND USE OF PROCESS INDUSTRY PRACTICESIn an effort to minimize the cost of process industry facilities, this Practice has been prepared from the technical requirements in the existing standards of major industrial users, contractors, or standards organizations. By harmonizing these technical requirements into a single set of Practices, administrative, application, and engineering costs to both the purchaser and the manufacturer should be reduced. While this Practice is expected to incorporate the majority of requirements of most users, individual applications may involve requirements that will be appended to and take precedence over this Practice. Determinations concerning fitness for purpose and particular matters or application of the Practice to particular project or engineering situations should not be made solely on information contained in these materials. The use of trade names from time to time should not be viewed as an expression of preference but rather recognized as normal usage in the trade. Other brands having the same specifications are equally correct and may be substituted for those named. All Practices or guidelines are intended to be consistent with applicable laws and regulations including OSHA requirements. To the extent these Practices or guidelines should conflict with OSHA or other applicable laws or regulations, such laws or regulations must be followed.Consult an appropriate professional before applying or acting on any material contained in or suggested by the Practice.This Practice is subject to revision at any time.© Process Industry Practices (PIP), Construction Industry Institute, TheUniversity of Texas at Austin, 3925 West Braker Lane (R4500), Austin,Texas 78759. PIP member companies and subscribers may copy this Practicefor their internal use. Changes, overlays, addenda, or modifications of anykind are not permitted within any PIP Practice without the express writtenauthorization of PIP.PRINTING HISTORYAugust 1996 Issued February 2009 Complete RevisionJune 2002 Complete RevisionNot printed with State fundsCOMPLETE REVISIONFebruary 2009Process Industry PracticesStructuralPIP STS02380Application of ACI 336.1-01,Specification for the Construction ofDrilled PiersTable of Contents Introduction (2)Purpose (2)Scope (2)References (2)Process Industry Practices (2)Industry Codes and Standards (2)Definitions (2)Requirements (3)Process Industry Practices Page 1 of 6PIP STS02380 COMPLETE REVISION Application of ACI 336.1-01, Specification for the Construction of Drilled Piers February 2009IntroductionPurposeThis Practice supplements ACI 336.1-01, Specification for the Construction of Drilled Piers. Together, this Practice and ACI 336.1-01 provide requirements for drilled pier construction.ScopeThe requirements of ACI 336.1-01, as modified and supplemented by this Practice, are adopted by this Practice for the construction of drilled piers. Common industry terminology may also refer to drilled piers as caissons or drilled shafts.ReferencesApplicable parts of the following Practice and industry standard shall be considered an integral part of this Practice. The edition in effect on the date of contract award shall be used, except as otherwise noted. Short titles will be used herein where appropriate.Process Industry Practices (PIP)−PIP STS03001 - Plain and Reinforced Concrete SpecificationIndustry Codes and Standards•American Concrete Institute (ACI)−ACI 336.1-01 - Specification for the Construction of Drilled Piers•ASTM International (ASTM)−ASTM A615/A615M Rev A - Standard Specification for Deformed and Plain Carbon-Steel Bars for Concrete Reinforcement−ASTM A706/A706M - Standard Specification for Low-Alloy Steel Deformed and Plain Bars for Concrete ReinforcementsDefinitionsconstructor: The party responsible for supplying the materials, equipment, tools, supervision, and labor for the installation of the drilled piers in accordance with the contract documents. Unless otherwise noted, the term constructor shall apply also to the constructor’s subcontractor(s) and vendor(s). Referred to as “contractor” in ACI 336.1-01.contract documents: Any and all documents, including codes, studies, design drawings, specifications, sketches, practices, and data sheets, that the purchaser or engineer of record has transmitted or otherwise communicated, either by incorporation or reference, and made part of the legal contract agreement or purchase order between the purchaser and the constructorengineer of record: Purchaser’s authorized representative with overall authority and responsibility for the engineering design, quality, and performance of the civil works, structure, foundations, materials, and appurtenances described in the contract documents. The engineer of record shall be licensed as defined by the laws of the locality in which the work is to be constructed, and be qualified to practicePage 2 of 6 Process Industry PracticesCOMPLETE REVISION PIP STS02380 February 2009 Application of ACI 336.1-01, Specification for the Construction of Drilled Piers in the specialty discipline required for the work described in the contract documents. Referred to as “Owner’s Representative” in ACI 336.1-01.geotechnical engineer: The engineer responsible for performing the geotechnical investigation and/or geotechnical consulting during design and installation of drilled piers. Referred to as “Owner’s Representative-Geotechnical Engineer” in ACI 336.1-01.owner: The party who has authority through ownership, lease, or other legal agreement over the site, facility, structure or project wherein drilled piers will be installed.purchaser: The party who awards the contract to the constructor. The purchaser may be the owner or owner’s authorized agent. Referred to as “Owner” in ACI 336.1-01.purchaser’s inspector: The purchaser’s authorized representative with responsibility and authority to act in the interest of, and on behalf of, the purchaser in all quality assurance matters for the quality control of all materials, installations, and workmanship furnished by the constructor and any subcontractors or vendors. The inspector(s) shall be qualified by training and experience and hold certifications or documentation of their qualifications. Referred to as “Owner’s Representative-Geotechnical Engineer” and “Testing agency” in ACI 336.1-01.RequirementsThis Requirements section describes the additions and modifications to the requirements ofACI 336.1-01. The numbering of headings and paragraphs in this section correspond to the numbering of ACI 336.1-01. Only the sections and paragraph, and corresponding numbering, of the revised requirements are included in this section. All provisions of ACI 336.1-01 that are not revised by this Practice shall remain in force for this Practice.SECTION 1 - GENERAL REQUIREMENTS1.1 Scope1.1.1 Addition. Supplement as Follows:These specifications also apply to drilled piers of diameters as small as24 inches (600 mm). Drilled piers may be constructed using cased oruncased holes or slurry stabilized holes. The ability of the soils to maintainan open and essentially dry hole is the determining factor.1.2 DefinitionsAddition. Supplement as Follows:Rock Rock shall be defined as material that cannot be excavated with aconventional earth auger or underreaming tool and requires excavation withspecial rock augers, core barrels, air tools, or blasting.conditions1.6 Project1.6.3 Modification. To Read as Follows:Existing underground utilitiesProcess Industry Practices Page 3 of 6PIP STS02380 COMPLETE REVISION Application of ACI 336.1-01, Specification for the Construction of Drilled Piers February 2009If required by the contract documents, the constructor shall locate all existingunderground structures and utilities which may obstruct his operations.Determine if there are conflicts with the work. Report any conflicts to theowner’s representative. Cease work in this area until the conflicts areresolved and approved by the purchaser.1.6.4 Modification. To Read as Follows:Job conferencesA pre-award conference and/or pre-construction conference should be heldbetween the purchaser and the constructor(s) to review project informationand constructor’s and purchaser’s respective scopes of work. Conferencetopics should include but not be limited to:safety requirements,site entry procedures,job schedules,available subsurface information,underground utility identification and location,surveying for location and elevation of drilled piers,special installation requirements,handling design changes,reinforcing steel placement and alignment,electrical ground cable attachment,concrete, anchor bolt location and installationexcavated materials disposalaction required if suspected contaminated soil is encountered,testing and inspection,required reports.Constructor shall attend all pre-award, pre-construction, and other jobconferences required by the contract documents or established by thepurchaser.1.8 Submittals by the constructor1.8.1.4 Modification. To Read as Follows:Submittals shall include proposed concrete materials and mixture proportionsconforming to the requirements of PIP STS03001. (2.4.1)1.9 Addition. New Paragraph:Regulatory requirementsPage 4 of 6 Process Industry PracticesCOMPLETE REVISION PIP STS02380 February 2009 Application of ACI 336.1-01, Specification for the Construction of Drilled Piers Comply with Federal Standards and Instructions of the U.S. Occupational Safety andHealth Administration (OSHA), including any additional requirements by state orlocal agencies that have jurisdiction where drilled piers are to be installed.SECTION 2 - PRODUCTSsteel2.3 Reinforcing2.3.1Modification. To Read as Follows:Reinforcing steel shall be deformed steel conforming to ASTM A615/A615M,Grade 60. Bars to be welded shall conform to ASTM A706/A706M.2.4 Concrete2.4.1 Modification. To Read as Follows:Concrete and concrete work shall conform to PIP STS03001. Concretematerials and mixture proportion information shall be submitted inaccordance with PIP STS03001.2.4.2 Modification. To Read as Follows:Concrete of the specified slump and strength shall be provided and placed.Concrete for use in the dry method (Section 3.2) shall have a nominalmaximum aggregate size of 1 inch (25 mm). Concrete for use in the slurrydisplacement method (Section 3.7) shall have a maximum nominal aggregatesize of 3/4 inch (20 mm).2.4.8 Addition. New Paragraph:Concrete shall have a 28-day compressive strength not less than 4000 psi(28 MPa).SECTION 3 - EXECUTION3.1 Tolerances3.1.7 Modification. To Read as Follows:Anchorage embedment toleranceInstall anchor bolts embedded in the drilled pier shaft to the tolerances ofPIP STS03001. When reinforcing is required to protrude from the drilledpier, limit the vertical and horizontal deviations of reinforcing steelprotruding from the drilled pier shaft to within 0.5 inches (13 mm) of thespecified location.method3.2 Dry3.2.3.1 Modification. To Read as Follows:For drilled piers bearing on rock, explore bearing stratum with a probe holeto a minimum depth equal to 1.5 times the diameter of the bearing area or amaximum of 10 feet (3 m) below the bottom of each drilled pier.Process Industry Practices Page 5 of 6PIP STS02380 COMPLETE REVISION Application of ACI 336.1-01, Specification for the Construction of Drilled Piers February 20093.2.3.2 Modification. To Read as Follows:For drilled piers with diameters 30 inches (750 mm) or larger, provide a safemethod for personnel access to inspect the bottom of the drilled pier.Alternatives to direct downhole inspection shall be approved by the owner'srepresentative-geotechnical engineer.3.2.3.5 Addition. New Paragraph:If a drilled pier location is within three (3) diameters of the bearing area(center-to-center) of an adjacent new drilled pier, drilling shall commenceonly after concrete in the adjacent foundation has been in place for not lessthan 12 hours.3.3 Steel casing and liner3.3.2.2 Modification. To Read as Follows:Withdrawal of temporary casing is the constructor’s option, provided therequirements of Section 3.6 and any additional requirements of the owner’srepresentative-geotechnical engineer are met.3.5 Modification. To Read as Follows:ConcreteConcrete work shall conform to PIP STS03001.3.5.6 Modification. To Read as Follows:Guide placement of free-fall concrete so as not to hit the reinforcement, holesides, or anchor bolt assemblies. Vibration of concrete free-falling more than20 feet (6 m) is not required.withdrawal3.6 Casing3.6.2 Modification. To Read as Follows:Coordinate casing withdrawal with concrete placement so that the concretepressure head exceeds the anticipated outside soil and water pressure abovethe bottom of the casing at all times during casing withdrawal. Additionally,the rate of casing withdrawal shall be such that the bottom edge of the casingremains at least 10 feet (3 m) below the top of the fresh concrete until thebottom of the casing reaches within 5 feet (1.5 m) of the top of drilled pier. Page 6 of 6 Process Industry Practices。

相关文档
最新文档