[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$apiParty6fBuHLCPZ1LTYs42XHdVbjpSDOYYPYzyxeAGwSN5Tp8":3,"$apiPartyIFk7wFR7OtHIvxyOMq2nZVAYxBPSlov-m_YNAoDtNEU":563,"$apiPartyIFk7wFR7OtHIvxyOMq2nZVAYxBPSlov-m_YNAoDtNEU$H93EERW16b":563},{"product_data":4,"scene_data":21,"task_data":407,"modality_data":441,"domain_data":478},[5,9,12,15,18],{"name":6,"value":7,"add_value":8,"describe":8},"Rivo","1","",{"name":10,"value":11,"add_value":8,"describe":8},"Cubo","2",{"name":13,"value":14,"add_value":8,"describe":8},"Moye","3",{"name":16,"value":17,"add_value":8,"describe":8},"Juro","4",{"name":19,"value":20,"add_value":8,"describe":8},"Ordo","5",[22,73,135,197,232,267,302,337,372],{"name":23,"value":7,"add_value":24,"describe":25,"children":26},"Home & Indoor","sofa","AI enhances everyday home life. Our datasets cover real indoor scenes to support smart devices, robotics, and home intelligence.",[27,29,31,33,35,37,40,43,46,49,52,55,58,61,64,67,70],{"name":28,"value":7},"Living Room",{"name":30,"value":11},"Bedroom",{"name":32,"value":14},"Kitchen",{"name":34,"value":17},"Dining Area",{"name":36,"value":20},"Bathroom",{"name":38,"value":39},"Entrance \u002F Foyer","6",{"name":41,"value":42},"Corridor \u002F Hallway","7",{"name":44,"value":45},"Staircase","8",{"name":47,"value":48},"Home Office","9",{"name":50,"value":51},"Hobby \u002F Game Room","10",{"name":53,"value":54},"Worship Space","11",{"name":56,"value":57},"Garage","12",{"name":59,"value":60},"Utility \u002F Laundry Room","13",{"name":62,"value":63},"Pantry","14",{"name":65,"value":66},"Basement","15",{"name":68,"value":69},"Garden","16",{"name":71,"value":72},"Balcony","17",{"name":74,"value":11,"add_value":75,"describe":76,"children":77},"Office & Educational","workshop","AI is reshaping work and learning. Our datasets capture offices and classrooms to power automation and next-generation productivity tools.",[78,81,84,87,90,93,96,99,102,105,108,111,114,117,120,123,126,129,132],{"name":79,"value":80},"Open Office","18",{"name":82,"value":83},"Private Office","19",{"name":85,"value":86},"Co-working Space","20",{"name":88,"value":89},"Reception \u002F Lobby","21",{"name":91,"value":92},"Conference Room","22",{"name":94,"value":95},"Huddle Room \u002F Booth","23",{"name":97,"value":98},"Lecture Hall \u002F Auditorium","24",{"name":100,"value":101},"Classroom","25",{"name":103,"value":104},"Science Laboratory","26",{"name":106,"value":107},"Library","27",{"name":109,"value":110},"Design Studio","28",{"name":112,"value":113},"Pantry \u002F Breakroom","29",{"name":115,"value":116},"Cafeteria \u002F Canteen","30",{"name":118,"value":119},"Restroom (Commercial)","31",{"name":121,"value":122},"Gymnasium \u002F Sports Hall","32",{"name":124,"value":125},"Server Room","33",{"name":127,"value":128},"Mailroom \u002F Logistics","34",{"name":130,"value":131},"Janitorial Closet","35",{"name":133,"value":134},"Corridor \u002F Elevators","36",{"name":136,"value":14,"add_value":137,"describe":138,"children":139},"Healthcare & Medical","love-and-help","AI is advancing modern healthcare. Our datasets include clinics and hospitals to enable clinical insights and medical automation.",[140,143,146,149,152,155,158,161,164,167,170,173,176,179,182,185,188,191,194],{"name":141,"value":142},"Operating Theatre \u002F OR","37",{"name":144,"value":145},"Consultation Room","38",{"name":147,"value":148},"Treatment Room","39",{"name":150,"value":151},"Dental Clinic","40",{"name":153,"value":154},"Inpatient Ward","41",{"name":156,"value":157},"Nurse Station","42",{"name":159,"value":160},"ICU","43",{"name":162,"value":163},"NICU (Neonatal ICU)","44",{"name":165,"value":166},"Emergency Room (ER)","45",{"name":168,"value":169},"Hospital Corridor","46",{"name":171,"value":172},"Waiting Area","47",{"name":174,"value":175},"CT\u002FMRI","48",{"name":177,"value":178},"Medical Laboratory","49",{"name":180,"value":181},"Phlebotomy Room","50",{"name":183,"value":184},"Rehabilitation Gym","51",{"name":186,"value":187},"Assisted Living Room","52",{"name":189,"value":190},"Pharmacy","53",{"name":192,"value":193},"Sterile Processing Dept","54",{"name":195,"value":196},"Medical Storage","55",{"name":198,"value":17,"add_value":199,"describe":200,"children":201},"Business & Public Service","business","AI is elevating commercial and public services. Our datasets span retail, dining, and service centers to improve intelligent operations.",[202,205,208,211,214,217,220,223,226,229],{"name":203,"value":204},"Shopping Mall Atrium","86",{"name":206,"value":207},"Supermarket Shelf","87",{"name":209,"value":210},"Self-Checkout Counter","88",{"name":212,"value":213},"Restaurant Dining Hall","89",{"name":215,"value":216},"Commercial Kitchen","90",{"name":218,"value":219},"Hotel Lobby","91",{"name":221,"value":222},"Subway Platform","92",{"name":224,"value":225},"Security Checkpoint","93",{"name":227,"value":228},"Underground Parking","94",{"name":230,"value":231},"Bank Teller Zone","95",{"name":233,"value":20,"add_value":234,"describe":235,"children":236},"Industrial & Manufacturing","robot-arm","AI is modernizing industry. Our datasets capture factories and logistics spaces to support robotics and intelligent manufacturing.",[237,240,243,246,249,252,255,258,261,264],{"name":238,"value":239},"Final Assembly Line","96",{"name":241,"value":242},"Quality Control Station","97",{"name":244,"value":245},"Robotic Welding Cell","98",{"name":247,"value":248},"CNC Machining Center","99",{"name":250,"value":251},"Cleanroom","100",{"name":253,"value":254},"Automated Warehouse","101",{"name":256,"value":257},"Loading Dock","102",{"name":259,"value":260},"Sorting Center","103",{"name":262,"value":263},"Chemical Plant","104",{"name":265,"value":266},"Power Substation","105",{"name":268,"value":39,"add_value":269,"describe":270,"children":271},"Transportation & Driving","car","AI is revolutionizing mobility. Our datasets capture road networks, vehicle dynamics and traffic scenarios to support autonomous driving and intelligent transportation systems.",[272,275,278,281,284,287,290,293,296,299],{"name":273,"value":274},"Urban Intersection","56",{"name":276,"value":277},"Highway \u002F Expressway","57",{"name":279,"value":280},"Tunnel","58",{"name":282,"value":283},"Roundabout","59",{"name":285,"value":286},"School \u002F Hospital Zone","60",{"name":288,"value":289},"Toll Station","61",{"name":291,"value":292},"Construction Zone","62",{"name":294,"value":295},"Parking Garage","63",{"name":297,"value":298},"Driver Cabin","64",{"name":300,"value":301},"Adverse Weather","65",{"name":303,"value":42,"add_value":304,"describe":305,"children":306},"Outdoor & Construction","tent-tree","AI is optimizing outdoor operations. Our datasets capture construction sites, open-air work zones and outdoor infrastructure to support smart construction and autonomous outdoor machinery.",[307,310,313,316,319,322,325,328,331,334],{"name":308,"value":309},"Excavation Site","66",{"name":311,"value":312},"Scaffolding Area","67",{"name":314,"value":315},"Material Storage Yard","68",{"name":317,"value":318},"Site Entrance","69",{"name":320,"value":321},"Roadwork Zone","70",{"name":323,"value":324},"Bridge Infrastructure","71",{"name":326,"value":327},"Transmission Line","72",{"name":329,"value":330},"Open-pit Mine","73",{"name":332,"value":333},"Tunneling Site","74",{"name":335,"value":336},"Post-Disaster Rubble","75",{"name":338,"value":45,"add_value":339,"describe":340,"children":341},"Nature, Aerial & Aquatic","global-loop","AI is exploring the natural world. Our datasets capture terrestrial landscapes, aerial vistas and aquatic ecosystems to support environmental monitoring and autonomous exploration systems.",[342,345,348,351,354,357,360,363,366,369],{"name":343,"value":344},"Deep Forest","76",{"name":346,"value":347},"Farmland \u002F Crops","77",{"name":349,"value":350},"River \u002F Lake","78",{"name":352,"value":353},"Open Ocean","79",{"name":355,"value":356},"Underwater Coral Reef","80",{"name":358,"value":359},"Fish Farm","81",{"name":361,"value":362},"Mountain Terrain","82",{"name":364,"value":365},"Urban Low Altitude","83",{"name":367,"value":368},"Fire Scene","84",{"name":370,"value":371},"Desert \u002F Gobi","85",{"name":373,"value":48,"add_value":374,"describe":375,"children":376},"Virtul & Digital","siri","AI is reshaping the virtual realm. Our datasets capture digital twins, virtual environments and simulated spaces to support metaverse development and intelligent digital interaction.",[377,380,383,386,389,392,395,398,401,404],{"name":378,"value":379},"VR Social Space","106",{"name":381,"value":382},"Synthetic Driving Sim","107",{"name":384,"value":385},"Digital Twin City","108",{"name":387,"value":388},"FPS \u002F MOBA Game","109",{"name":390,"value":391},"Robotics Gym","110",{"name":393,"value":394},"AR Navigation","111",{"name":396,"value":397},"Virtual Showroom","112",{"name":399,"value":400},"Code \u002F IDE Interface","113",{"name":402,"value":403},"App GUI Screen","114",{"name":405,"value":406},"Synthetic Face\u002FID","115",[408,411,414,417,420,423,426,429,432,435,438],{"name":409,"value":7,"add_value":410,"describe":8},"Classification","rubric",{"name":412,"value":11,"add_value":413,"describe":8},"Detection","radar",{"name":415,"value":14,"add_value":416,"describe":8},"Segmentation","segmentation",{"name":418,"value":17,"add_value":419,"describe":8},"Tacking","crosshairs",{"name":421,"value":20,"add_value":422,"describe":8},"Estimation","streamline",{"name":424,"value":39,"add_value":425,"describe":8},"QA","qa",{"name":427,"value":42,"add_value":428,"describe":8},"Recognition","finger-scan",{"name":430,"value":45,"add_value":431,"describe":8},"Control","control",{"name":433,"value":48,"add_value":434,"describe":8},"Extraction","extraction",{"name":436,"value":51,"add_value":437,"describe":8},"Retrieval","retrieval",{"name":439,"value":54,"add_value":440,"describe":8},"Forecast","forecast",[442,445,448,451,454,457,460,463,466,469,472,475],{"name":443,"value":7,"add_value":444,"describe":8},"Audio","audio",{"name":446,"value":11,"add_value":447,"describe":8},"Image","image",{"name":449,"value":14,"add_value":450,"describe":8},"Text","text",{"name":452,"value":17,"add_value":453,"describe":8},"Video","video",{"name":455,"value":20,"add_value":456,"describe":8},"Multi","multi",{"name":458,"value":39,"add_value":459,"describe":8},"Document","document",{"name":461,"value":42,"add_value":462,"describe":8},"Time-Series","time-series",{"name":464,"value":45,"add_value":465,"describe":8},"3D cloud","cloud",{"name":467,"value":48,"add_value":468,"describe":8},"Code","code",{"name":470,"value":51,"add_value":471,"describe":8},"Event","event",{"name":473,"value":54,"add_value":474,"describe":8},"Motion","motion",{"name":476,"value":57,"add_value":477,"describe":8},"Interaction","interaction",[479,482,487,491,494,499,504,509,514,519,524,528,532,536,540,544,548,552,556,559],{"id":480,"value":480,"name":233,"intro":481,"add_value":234,"describe":481},2,"智能质检：利用图像识别、多模态模型对产品外观或声音、振动等数据进行分析，自动识别缺陷，提高质量控制效率。\n工业知识问答与文档理解：通过大模型理解和总结技术文档、操作手册，实现快速问答、知识检索和培训支持。\n安全监测与风险预警：实时分析视频、传感器和操作日志，识别潜在危险行为或异常状态，提前预警，保障人员和设备安全。",{"id":483,"value":483,"name":484,"intro":485,"add_value":486,"describe":485},3,"Finance & Insurance","风险评估与预测：分析大量客户数据，评估信用风险、市场风险等，预测违约概率、股价走势等，辅助金融机构决策。\n智能投顾：根据客户风险偏好、资产状况等，提供个性化投资组合建议，实时调整投资策略。\n反欺诈检测：通过分析交易数据、用户行为，识别异常交易和欺诈行为，保障金融安全。","funds",{"id":488,"value":488,"name":489,"intro":490,"add_value":269,"describe":490},1,"Transport & Automotive","智能座舱：打造多模态交互的 AI 座舱，通过语音、手势、面部识别等实现人机交互，如语音控制导航、音乐播放。\n驾驶员状态监测：识别疲劳、分心、抽烟、打电话等行为，通过大模型判断危险等级，触发相应提醒或干预机制。\n智能驾驶：AI 用于环境感知、路径规划与决策控制，使车辆能识别道路、行人、障碍物等，实现自适应巡航、自动泊车、车道保持等功能，提升驾驶安全性与便利性。",{"id":492,"value":492,"name":136,"intro":493,"add_value":137,"describe":493},4,"医学影像诊断：分析 CT、MRI 等影像，辅助医生检测疾病、识别病灶，如 AI 系统可快速发现肺部结节。\n医患对话助手：通过自然语言处理理解患者问题，提供初步健康建议或就诊指导，缓解医生接诊压力。\n智能健康管理：根据用户健康数据，提供个性化健康建议、疾病预警，如智能手环结合 AI 分析用户运动、睡眠、心率等数据。",{"id":495,"value":495,"name":496,"intro":497,"add_value":498,"describe":497},6,"Smart Devices","多模态交互：支持语音、手势、眼神等多种交互方式，如 AI 眼镜可通过语音指令实现翻译、搜索功能。\n智能感知与处理：使设备能感知环境、理解用户需求，如智能音箱根据环境噪音自动调节音量。\n个性化服务：根据用户使用习惯和偏好，提供个性化功能与服务，如智能手表为用户定制运动健身计划。","microscope",{"id":500,"value":500,"name":501,"intro":502,"add_value":503,"describe":502},8,"Law & Government","智能法律问答：面向公众或企业用户，提供合规、劳动法、婚姻继承、知识产权等常见法律问题的智能解答。\n合同审查与风险识别：利用大模型分析合同内容，识别潜在风险条款、漏洞或不合理约定，提升合同审核质量。\n法律知识图谱构建：自动梳理法规、案例、条文之间的引用关系，构建语义化知识图谱，支持智能分析和推理。","hammer",{"id":505,"value":505,"name":506,"intro":507,"add_value":508,"describe":507},7,"Education & Training","个性化学习：根据学生学习进度、能力和知识掌握情况，推送个性化学习内容与练习，如智能辅导系统为学生制定专属学习计划。\n智能教学辅助：AI 助教协助教师进行作业批改、答疑解惑，还可分析教学数据，为教师提供教学反馈，优化教学方法。\n虚拟学习环境：利用 AI 创建虚拟实验、历史场景等，让学生沉浸式学习，如在虚拟化学实验室中进行实验操作。","degree-hat",{"id":510,"value":510,"name":511,"intro":512,"add_value":513,"describe":512},5,"Agriculture & Food","作物病虫害识别与防治：通过图像识别分析农作物叶片、果实等症状，识别病虫害类型，给出防治建议，减少产量损失。\n农产品质量检测：利用图像和传感器数据，识别果蔬等农产品的成熟度、外观缺陷，进行自动分级，提高市场竞争力。\n农情监测与预测：利用卫星遥感、气象和传感器数据，结合大模型预测作物长势、干旱、洪涝等农情变化。","ph-farm",{"id":515,"value":515,"name":516,"intro":517,"add_value":518,"describe":517},9,"Retail & E-commerce","智能客服：通过自然语言对话理解用户需求，提供产品推荐、订单查询、退换货支持等服务，提升客户满意度。\n个性化营销推荐：基于用户浏览、购买、偏好等行为数据，生成个性化推荐内容与优惠策略，提高转化率和客单价。\n商品内容生成：自动撰写商品标题、卖点描述、使用说明等内容，适用于海量SKU的内容生产与多语言发布。","buy",{"id":520,"value":520,"name":521,"intro":522,"add_value":523,"describe":8},10,"Security & Protection",null,"safe-shield-line",{"id":525,"value":525,"name":526,"intro":522,"add_value":527,"describe":8},11,"Environment & Climate","weather",{"id":529,"value":529,"name":530,"intro":522,"add_value":531,"describe":8},12,"Energy & Resource","energy-leaf",{"id":533,"value":533,"name":534,"intro":522,"add_value":535,"describe":8},13,"Express & Logistics","speed-outline",{"id":537,"value":537,"name":538,"intro":522,"add_value":539,"describe":8},15,"Sports","baseball-outline",{"id":541,"value":541,"name":542,"intro":522,"add_value":543,"describe":8},16,"General Data","daily-booth",{"id":545,"value":545,"name":546,"intro":522,"add_value":547,"describe":8},17,"Content & Media","media",{"id":549,"value":549,"name":550,"intro":522,"add_value":551,"describe":8},18,"Construction","construction",{"id":553,"value":553,"name":554,"intro":522,"add_value":555,"describe":8},19,"IT & Telecom","tech",{"id":557,"value":557,"name":558,"intro":522,"add_value":498,"describe":8},20,"Science & Research",{"id":560,"value":560,"name":561,"intro":522,"add_value":562,"describe":8},21,"Language & Culture","lang",{"id":564,"unique_code":565,"title":566,"icon":8,"intro":567,"cate":483,"detail":568,"create_time":569,"update_time":570,"price":571,"view_count":572,"download_count":573,"unit":573,"amount":574,"is_create_order":573,"enterprise_id":488,"seo_keywords":575,"seo_description":576,"data_format":577,"file_size":578,"apply_scene":579,"training_task":580,"version":581,"dataset_type_id":492,"dataset_scene_id":520,"sample_file":582,"banner":8,"unit_name":8,"cate_name":449,"icon_url":8,"banner_url":8,"sample_file_url":8,"data_dict":583,"qa_list":650,"sample_metadatas":667,"text_sample_content":722,"enterprise_name":723,"enterprise_logo":724,"data_distribution":725},1133,"5f94b8bedae36c7d9d1670905a90ed3b","Technical Rope Rescue Incident and Failure Analysis Report Dataset","Combine diverse rescue records with failure analyses to help models produce evidence-based, professional incident reviews.","\u003Cp>This dataset focuses on incidents and system anomalies in technical rope and high-angle rescue, bringing together case details, scene notes, equipment anomalies, personnel statements, and response records alongside event summaries and failure analysis reports. Its contents cover event timelines, failure modes, contributing factors, consequences, response evaluations, and evidentiary uncertainty, supporting models that synthesize multiple sources of evidence into professional long-form reports. It is suitable for domain-specific fine-tuning, report-generation research, and safety review in rope rescue.\u003C\u002Fp>","2026-10-10 20:04:06","2026-10-19 18:25:26","0.00",37,0,5000,"technical rope rescue dataset, rescue incident analysis, failure analysis report, high-angle rescue, rescue case review, safety incident report, long-form generation, domain fine-tuning","Rope rescue incident records, scene evidence, and failure analysis reports for domain fine-tuning, case review, and long-form report generation.","JSON","0.4GB","technical rope rescue operations, rescue incident investigation, emergency response safety assessment","incident report generation, failure analysis, evidence-based reasoning","V1.0","rivo\u002Fsample-packages\u002F7c59e3ae-ded5-4032-8a89-06b10bcadc64\u002F20261010.zip",[584,589,594,599,604,609,614,619,625,630,635,640,645],{"id":573,"name":585,"field":586,"intro":587,"type":588},"File Name","file_name","File name","string",{"id":590,"name":591,"field":592,"intro":593,"type":588},8244,"Case Details","case_record","Original case information, including the incident name, location, time, and rescue mission context.",{"id":595,"name":596,"field":597,"intro":598,"type":588},8245,"Scene Notes","scene_notes","Original records of scene observations, environmental conditions, rope system setup, and operational procedures.",{"id":600,"name":601,"field":602,"intro":603,"type":588},8246,"Event Timeline","event_timeline","A chronological account derived from source materials, identifying key events and their supporting evidence.",{"id":605,"name":606,"field":607,"intro":608,"type":588},8247,"Failure Analysis","failure_analysis","An integrated analysis of failure modes and mechanisms in the rope rescue system or operational procedures, and their relationship to incident progression.",{"id":610,"name":611,"field":612,"intro":613,"type":588},8248,"Response Records","response_records","Original records of actions taken after the incident, including rescue efforts, system adjustments, medical care, and follow-up measures.",{"id":615,"name":616,"field":617,"intro":618,"type":588},8249,"Response Evaluation","response_evaluation","An assessment of response measures, decisions, and coordination after the incident, including effective practices and opportunities for improvement.",{"id":620,"name":621,"field":622,"intro":623,"type":624},8250,"Contributing Factors","contributing_factors","Factors identified and summarized from the case materials that caused or worsened the incident.","array",{"id":626,"name":627,"field":628,"intro":629,"type":588},8251,"Complete Analysis Report","full_analysis_report","A professional long-form report based on source materials and analytical findings, covering the incident overview, timeline, failure and contributing factor analysis, consequences, response evaluation, and recommendations for improvement.",{"id":631,"name":632,"field":633,"intro":634,"type":588},8252,"Personnel Statements","personnel_statements","Original statements from on-scene personnel, rescuers, or other witnesses about the incident, actions taken, and observations.",{"id":636,"name":637,"field":638,"intro":639,"type":588},8253,"Consequences and Impact","consequences_and_impact","A summary of actual or potential effects on personnel, equipment, rescue operations, and mission outcomes.",{"id":641,"name":642,"field":643,"intro":644,"type":588},8254,"Evidence and Uncertainty","evidence_and_uncertainty","An explanation of the source evidence for analytical conclusions, relationships between sources, and any missing, conflicting, or unverified information.",{"id":646,"name":647,"field":648,"intro":649,"type":588},8255,"Equipment and System Anomalies","equipment_system_anomalies","Records of anomalies, damage, or failures involving ropes, connectors, anchors, protective devices, or other rescue systems.",[651,655,659,663],{"id":652,"question":653,"answer":654},5982,"What does the dataset contain?","It includes case details, scene observations, equipment and system anomalies, personnel statements, and response records. These source materials are paired with event timelines, failure analyses, contributing factors, consequence assessments, evidence and uncertainty notes, and complete analysis reports.",{"id":656,"question":657,"answer":658},5983,"How is the data organized, and what should users know about quality?","Records are organized into fields for case materials and analytical reports, making it easier to connect source evidence, event progression, and conclusions. Completeness may vary between cases, so users should review conclusions alongside the evidence and uncertainty fields. Refer to the product listing for dataset size and specific quality criteria.",{"id":660,"question":661,"answer":662},5984,"What are the suitable use cases?","The dataset is suited to domain-specific fine-tuning, long-form report generation, case review, and safety analysis research in technical rope and high-angle rescue. Generated content can support documentation and analysis but should not replace professional field judgment or formal incident investigation procedures.",{"id":664,"question":665,"answer":666},5985,"How can I access the data, and what licensing applies?","Access methods, available formats, and permitted uses are defined by the product listing and purchase or delivery agreement. Before using the data for training, research, or redistribution, review the license terms and requirements for handling personal or sensitive case information.",[668,688,705],{"id":669,"relate_table":670,"relate_id":671,"file_size":573,"file_name":672,"path":8,"duration":573,"cate":483,"file_format":673,"audio_rate":8,"audio_channel":522,"audio_bit_depth":522,"quality":8,"annotation":674,"cate_name":675,"case_record":676,"scene_notes":677,"event_timeline":678,"failure_analysis":679,"response_records":680,"response_evaluation":681,"contributing_factors":682,"full_analysis_report":683,"personnel_statements":684,"consequences_and_impact":685,"evidence_and_uncertainty":686,"equipment_system_anomalies":687},14800,"union_cubo",814020908,"样例_3.json","json","{\"case_record\": \"Event: Portable anchor-frame movement during initial loading for a shaft rescue. Location: Service shaft 4, Larkspur Works. Date: 2025-02-11. A team was preparing to raise an attended litter from the shaft to the surface using a portable anchor frame and a separate backup line connected to a rock anchor. During initial loading, one frame foot shifted on loose gravel. The operation was stopped before the litter was raised. No injury was reported.\", \"scene_notes\": \"At 16:32, the frame was positioned at the shaft edge on a gravel surface. A chalk mark had been placed beside the front foot to observe movement. As the team began a controlled initial loading with the litter still at the lower staging point, the front foot moved approximately 35 mm along the surface and the frame showed a slight tilt. The backup line remained connected to its separate rock anchor and was reported to remain tensioned. The frame did not overturn, and no person or litter fell. The ground around the foot appeared disturbed after the movement.\", \"event_timeline\": \"- 16:32 — The portable frame was positioned at the shaft edge on gravel, with a chalk reference at the front foot; supported by the scene notes.\\n- During initial loading — The front foot moved approximately 35 mm and the frame tilted slightly; supported by the observer's statement and scene notes.\\n- Immediately after the movement was called — The operator stopped loading; the backup line remained connected and tensioned; supported by personnel statements.\\n- After the system was stabilized — The team unloaded the frame and kept the litter at the lower staging point; supported by response records.\\n- Before resuming — The team selected a firmer surface and confirmed stability during renewed controlled loading; supported by response records.\", \"failure_analysis\": \"The observed movement is consistent with the frame foot losing stable support on the gravel surface under initial loading. The displacement relative to the chalk mark and disturbed ground support a movement of the footing; the slight tilt indicates that the frame's position changed. The records do not quantify the applied load or establish whether loose gravel alone, uneven contact, or another surface condition initiated the movement. No structural failure of the frame or attached hardware was observed. The separately anchored backup remained connected and tensioned, and the team stopped before raising the litter. The evidence therefore supports an instability of the initial frame placement, not a failure of the frame structure or backup anchor.\", \"response_records\": \"The team stopped loading and maintained control of both lines. The frame was unloaded, and the litter remained at the lower staging point while the team reassessed the surface and anchor arrangement. The team then used a revised setup located on a firmer surface, with the backup remaining independent. Before proceeding, the edge observer confirmed that the frame was stable during a renewed controlled load. The initial frame position was not returned to service. The movement and ground condition were recorded for equipment and site review.\", \"response_evaluation\": \"The chalk reference made the foot movement visible, and the edge observer's call was followed by an immediate stop. Maintaining both lines, unloading the frame, and relocating to a firmer surface were appropriate responses to the observed instability. The team confirmed the revised arrangement under controlled loading before proceeding. The record could be improved by documenting the revised support conditions and the basis for the stability check, as well as any subsequent technical inspection. It does not establish whether formal surface-assessment criteria were available or used before the initial setup.\", \"contributing_factors\": \"[\\\"The frame was positioned on gravel, and the front foot moved with visible ground disturbance during initial loading.\\\", \\\"The approximately 35 mm displacement and slight tilt show that the initial support arrangement did not remain stable under the load applied.\\\", \\\"The operation involved a shaft-edge setup where frame movement could affect the suspended system; the team had to stop before raising the litter.\\\", \\\"The record contains no load measurements or ground assessment, so the contribution of load magnitude, surface unevenness, or gravel compaction cannot be separated.\\\"]\", \"full_analysis_report\": \"## Event overview\\nOn 11 February 2025, a portable anchor frame moved during initial loading at Service shaft 4, Larkspur Works. The frame stood on gravel at the shaft edge. An observer saw its front foot shift approximately 35 mm from a chalk reference and noted a slight tilt. The team stopped before raising the attended litter. The litter remained at the lower staging point, the backup line remained connected to a separate rock anchor, and no injury was reported.\\n\\n## Sequence and failure analysis\\nThe movement occurred as the team began applying load to the frame. The disturbed gravel around the foot and the change relative to the chalk mark support the conclusion that the footing moved on the surface. The slight tilt indicates that the frame's position was affected. The available evidence does not show a fracture, deformation, or failure of frame hardware. It also does not establish the applied load or whether the initiating condition was loose gravel, uneven foot contact, surface slope, or a combination of factors.\\n\\nThe principal failure mode was loss of stable support at the initial frame placement. The separate backup line remained connected and tensioned, and the litter did not undergo a reported sudden movement. These controls limited exposure while the team stopped and reassessed. The record does not support attributing the event to structural failure of the frame or anchor.\\n\\n## Consequences and response\\nNo fall, injury, or visible equipment damage was reported. The lift was delayed while the team unloaded the frame, selected a firmer surface, and confirmed stability during renewed controlled loading. The response was effective: movement was detected against a reference mark, the operator stopped promptly, and the team did not continue raising the litter on the unstable setup.\\n\\nFurther review should document the surface conditions at the revised position and the method used to confirm stability. A technical inspection of the frame and attached hardware should be recorded if required by the team's equipment process. The initial surface and the observed displacement should be retained in the site review so that future setup decisions account for the demonstrated movement.\\n\\n## Evidence limits\\nThe analysis is grounded in the chalk-mark displacement, disturbed gravel, slight tilt, and sequence recorded by the team. Applied load, ground compaction, and surface geometry were not measured. The exact mechanism causing the foot to move therefore remains uncertain. The record reports no visible structural damage but does not include a detailed inspection report.\", \"personnel_statements\": \"The edge observer stated that the front foot moved relative to the chalk mark and that the frame tilted slightly. The frame operator reported stopping the load as soon as the movement was called out. The backup-line operator stated that the line remained connected to the separate rock anchor and was tensioned during the pause. The person at the lower staging point reported no sudden movement of the litter. No witness reported a fall or injury.\", \"consequences_and_impact\": \"The frame did not overturn, the litter remained at the lower staging point, and no injury was reported. The team halted the planned lift, unloaded and repositioned the frame, and delayed the rescue operation while confirming a stable setup. No visible damage to the frame, hardware, backup line, or anchor was reported. The movement presented a potential for loss of control had loading continued, but the record documents no such loss or resulting harm.\", \"evidence_and_uncertainty\": \"The scene notes and observer statement establish movement of approximately 35 mm relative to a chalk mark, slight frame tilt, and disturbed gravel. The response record establishes that the frame was unloaded and repositioned before the litter was raised. Personnel statements report that the separate backup line remained connected and tensioned and that the litter did not move suddenly. There are no measurements of applied load, frame-foot pressure, surface compaction, or ground slope. The cause is therefore limited to unstable support at the initial placement; the specific surface or loading mechanism cannot be determined from the available record. No detailed post-event frame inspection is included.\", \"equipment_system_anomalies\": \"The front foot of the portable frame shifted approximately 35 mm from the chalk reference during initial loading. A disturbed area in the gravel was observed around the foot. No visible deformation, cracking, or connector damage was reported on the frame or attached hardware. The backup line and its separate rock anchor showed no reported visible damage. The record does not include load measurements, ground compaction data, or a technical inspection report for the frame.\"}","文本","Event: Portable anchor-frame movement during initial loading for a shaft rescue. Location: Service shaft 4, Larkspur Works. Date: 2025-02-11. A team was preparing to raise an attended litter from the shaft to the surface using a portable anchor frame and a separate backup line connected to a rock anchor. During initial loading, one frame foot shifted on loose gravel. The operation was stopped before the litter was raised. No injury was reported.","At 16:32, the frame was positioned at the shaft edge on a gravel surface. A chalk mark had been placed beside the front foot to observe movement. As the team began a controlled initial loading with the litter still at the lower staging point, the front foot moved approximately 35 mm along the surface and the frame showed a slight tilt. The backup line remained connected to its separate rock anchor and was reported to remain tensioned. The frame did not overturn, and no person or litter fell. The ground around the foot appeared disturbed after the movement.","- 16:32 — The portable frame was positioned at the shaft edge on gravel, with a chalk reference at the front foot; supported by the scene notes.\n- During initial loading — The front foot moved approximately 35 mm and the frame tilted slightly; supported by the observer's statement and scene notes.\n- Immediately after the movement was called — The operator stopped loading; the backup line remained connected and tensioned; supported by personnel statements.\n- After the system was stabilized — The team unloaded the frame and kept the litter at the lower staging point; supported by response records.\n- Before resuming — The team selected a firmer surface and confirmed stability during renewed controlled loading; supported by response records.","The observed movement is consistent with the frame foot losing stable support on the gravel surface under initial loading. The displacement relative to the chalk mark and disturbed ground support a movement of the footing; the slight tilt indicates that the frame's position changed. The records do not quantify the applied load or establish whether loose gravel alone, uneven contact, or another surface condition initiated the movement. No structural failure of the frame or attached hardware was observed. The separately anchored backup remained connected and tensioned, and the team stopped before raising the litter. The evidence therefore supports an instability of the initial frame placement, not a failure of the frame structure or backup anchor.","The team stopped loading and maintained control of both lines. The frame was unloaded, and the litter remained at the lower staging point while the team reassessed the surface and anchor arrangement. The team then used a revised setup located on a firmer surface, with the backup remaining independent. Before proceeding, the edge observer confirmed that the frame was stable during a renewed controlled load. The initial frame position was not returned to service. The movement and ground condition were recorded for equipment and site review.","The chalk reference made the foot movement visible, and the edge observer's call was followed by an immediate stop. Maintaining both lines, unloading the frame, and relocating to a firmer surface were appropriate responses to the observed instability. The team confirmed the revised arrangement under controlled loading before proceeding. The record could be improved by documenting the revised support conditions and the basis for the stability check, as well as any subsequent technical inspection. It does not establish whether formal surface-assessment criteria were available or used before the initial setup.","[\"The frame was positioned on gravel, and the front foot moved with visible ground disturbance during initial loading.\", \"The approximately 35 mm displacement and slight tilt show that the initial support arrangement did not remain stable under the load applied.\", \"The operation involved a shaft-edge setup where frame movement could affect the suspended system; the team had to stop before raising the litter.\", \"The record contains no load measurements or ground assessment, so the contribution of load magnitude, surface unevenness, or gravel compaction cannot be separated.\"]","## Event overview\nOn 11 February 2025, a portable anchor frame moved during initial loading at Service shaft 4, Larkspur Works. The frame stood on gravel at the shaft edge. An observer saw its front foot shift approximately 35 mm from a chalk reference and noted a slight tilt. The team stopped before raising the attended litter. The litter remained at the lower staging point, the backup line remained connected to a separate rock anchor, and no injury was reported.\n\n## Sequence and failure analysis\nThe movement occurred as the team began applying load to the frame. The disturbed gravel around the foot and the change relative to the chalk mark support the conclusion that the footing moved on the surface. The slight tilt indicates that the frame's position was affected. The available evidence does not show a fracture, deformation, or failure of frame hardware. It also does not establish the applied load or whether the initiating condition was loose gravel, uneven foot contact, surface slope, or a combination of factors.\n\nThe principal failure mode was loss of stable support at the initial frame placement. The separate backup line remained connected and tensioned, and the litter did not undergo a reported sudden movement. These controls limited exposure while the team stopped and reassessed. The record does not support attributing the event to structural failure of the frame or anchor.\n\n## Consequences and response\nNo fall, injury, or visible equipment damage was reported. The lift was delayed while the team unloaded the frame, selected a firmer surface, and confirmed stability during renewed controlled loading. The response was effective: movement was detected against a reference mark, the operator stopped promptly, and the team did not continue raising the litter on the unstable setup.\n\nFurther review should document the surface conditions at the revised position and the method used to confirm stability. A technical inspection of the frame and attached hardware should be recorded if required by the team's equipment process. The initial surface and the observed displacement should be retained in the site review so that future setup decisions account for the demonstrated movement.\n\n## Evidence limits\nThe analysis is grounded in the chalk-mark displacement, disturbed gravel, slight tilt, and sequence recorded by the team. Applied load, ground compaction, and surface geometry were not measured. The exact mechanism causing the foot to move therefore remains uncertain. The record reports no visible structural damage but does not include a detailed inspection report.","The edge observer stated that the front foot moved relative to the chalk mark and that the frame tilted slightly. The frame operator reported stopping the load as soon as the movement was called out. The backup-line operator stated that the line remained connected to the separate rock anchor and was tensioned during the pause. The person at the lower staging point reported no sudden movement of the litter. No witness reported a fall or injury.","The frame did not overturn, the litter remained at the lower staging point, and no injury was reported. The team halted the planned lift, unloaded and repositioned the frame, and delayed the rescue operation while confirming a stable setup. No visible damage to the frame, hardware, backup line, or anchor was reported. The movement presented a potential for loss of control had loading continued, but the record documents no such loss or resulting harm.","The scene notes and observer statement establish movement of approximately 35 mm relative to a chalk mark, slight frame tilt, and disturbed gravel. The response record establishes that the frame was unloaded and repositioned before the litter was raised. Personnel statements report that the separate backup line remained connected and tensioned and that the litter did not move suddenly. There are no measurements of applied load, frame-foot pressure, surface compaction, or ground slope. The cause is therefore limited to unstable support at the initial placement; the specific surface or loading mechanism cannot be determined from the available record. No detailed post-event frame inspection is included.","The front foot of the portable frame shifted approximately 35 mm from the chalk reference during initial loading. A disturbed area in the gravel was observed around the foot. No visible deformation, cracking, or connector damage was reported on the frame or attached hardware. The backup line and its separate rock anchor showed no reported visible damage. The record does not include load measurements, ground compaction data, or a technical inspection report for the frame.",{"id":689,"relate_table":670,"relate_id":690,"file_size":573,"file_name":691,"path":8,"duration":573,"cate":483,"file_format":673,"audio_rate":8,"audio_channel":522,"audio_bit_depth":522,"quality":8,"annotation":692,"cate_name":675,"case_record":693,"scene_notes":694,"event_timeline":695,"failure_analysis":696,"response_records":697,"response_evaluation":698,"contributing_factors":699,"full_analysis_report":700,"personnel_statements":701,"consequences_and_impact":702,"evidence_and_uncertainty":703,"equipment_system_anomalies":704},14799,1396175079,"样例_2.json","{\"case_record\": \"Event: Brief unintended litter movement following an ambiguous movement command. Location: East Slope, Bracken Creek access route. Date: 2024-09-07. A team was hauling an attended litter up a steep wooded slope toward a trail bench. The litter was managed on a main haul line with a separate belay line. The litter moved a short distance downhill during a stop request. No injury or equipment damage was reported.\", \"scene_notes\": \"At 14:06, the litter was moving uphill on a section of slope with roots and loose surface material. The lead rescuer identified an obstruction ahead and called for the team to hold. The haul operator reported hearing a command to lower by one increment and acted on that interpretation. The litter moved approximately 0.25 m downhill before the lead rescuer repeated the stop request. The belay line, which had some slack immediately before the movement, became tensioned and arrested further travel. The litter remained upright and did not contact the ground. The exact duration of movement was not recorded.\", \"event_timeline\": \"- 14:06 — The litter was being hauled uphill toward an obstruction; supported by the scene notes.\\n- Shortly afterward — The lead rescuer called hold, while the haul operator understood a lower-by-one-increment command and briefly released the haul; supported by the two statements and scene notes, with disagreement about the command heard.\\n- During the brief release — The litter moved approximately 0.25 m downhill and the belay line, previously slack, became tensioned; supported by the scene notes and belay operator statement.\\n- After the repeated stop call — The team stabilized the litter, checked the occupants, and found no injury or visible equipment damage; supported by response records.\\n- Before resuming — The team repeated and acknowledged commands and reassessed the route; supported by the response record.\", \"failure_analysis\": \"The event is best characterized as a brief loss of coordinated movement control rather than a documented hardware failure. A mismatch between the lead rescuer's intended stop command and the haul operator's understanding led to unintended release of the haul. The belay line had slack immediately beforehand, so it did not prevent the initial movement; it became tensioned and arrested further travel. The records do not establish the amount of slack, line loads, or whether radio quality, phrasing, or another factor caused the misunderstanding. The belay functioned as a secondary restraint after movement began, but the event shows that communication and belay readiness were not fully aligned at that moment.\", \"response_records\": \"On the repeated stop call, the haul operator stopped movement and the belay operator maintained the line. The team confirmed that the litter was stable and checked the attendant and patient, with no injury reported. The load was held while the lead rescuer reassessed the route. The team then resumed only after the movement command and stop command were repeated and acknowledged by the relevant operators. A post-event visual check found no visible damage to the ropes, connectors, or anchors. The team recorded the communication discrepancy for review.\", \"response_evaluation\": \"The repeated stop call was followed by prompt cessation of movement. The belay operator maintained the line, and the team checked the patient and attendant before resuming. Repeating and acknowledging commands after the event was a useful immediate correction. Review should focus on using unambiguous standard commands, requiring acknowledgement before movement, and coordinating belay readiness with haul actions. The record supports these as process improvements but does not identify the precise source of the initial misunderstanding.\", \"contributing_factors\": \"[\\\"The lead rescuer and haul operator reported different understandings of the movement command, and the intended hold was not acted on immediately.\\\", \\\"The belay line had some slack immediately before the unintended movement, allowing a short downhill displacement before it became tensioned.\\\", \\\"The litter was approaching an obstruction on a steep slope, increasing the consequence of an unintended movement and the need for coordinated commands.\\\", \\\"The record does not document a closed-loop acknowledgement of the initial hold command before the haul operator acted.\\\"]\", \"full_analysis_report\": \"## Event overview\\nOn 7 September 2024, an attended litter being hauled up East Slope near Bracken Creek moved approximately 0.25 m downhill after the lead rescuer called for the team to hold. The haul operator understood the command as an instruction to lower briefly. A separate belay line, reported to have some slack before the movement, became tensioned and arrested further travel. No injury or visible equipment damage was reported.\\n\\n## Sequence and failure analysis\\nThe event occurred while the team was negotiating an obstruction on a steep, wooded route. The lead rescuer intended to stop movement. The haul operator's statement indicates a different understanding and a brief release of the haul. The litter consequently shifted downhill. The belay line did not prevent the initial displacement because it was not taut at that point, but it limited further travel as it became tensioned.\\n\\nThe records support a communication-and-coordination failure with a delayed secondary restraint, not a mechanical breakage. They do not establish why the command was misunderstood. The possibility of unclear wording or a transmission issue cannot be distinguished from other explanations on the available evidence. Likewise, the amount of belay slack and the forces involved were not measured.\\n\\n## Consequences and response\\nThe litter did not reach the ground, and no injury or equipment damage was reported. The team stopped, maintained the belay, checked the occupants, and reassessed the route. Repeating and acknowledging commands before resuming helped restore shared understanding. The response was timely and proportionate to the recorded event.\\n\\nFor future operations, the team should review consistent command wording, closed-loop acknowledgement before movement, and coordination between haul and belay operators. Belay readiness should be considered as part of movement planning so that a secondary line does not have avoidable slack at a point where an unintended shift could have serious consequences. These recommendations address the documented communication mismatch and slack condition without assuming a specific cause that the record cannot establish.\\n\\n## Evidence limits\\nThe analysis relies on the scene notes and individual statements. The accounts differ on the command heard, and no audio recording is available. Movement distance is approximate, and there are no load or slack measurements. No injury and no visible damage were reported, but the file does not contain a detailed equipment inspection report.\", \"personnel_statements\": \"The lead rescuer stated that the intended command was hold because the litter was approaching an obstruction. The haul operator stated that the command was understood as lower by one increment and that the haul was released briefly. A belay operator reported that the belay had some slack before the movement and tightened as the litter moved. The litter attendant reported a brief downhill shift but no impact or injury. The statements differ on what command was heard; no recording of the radio traffic is available.\", \"consequences_and_impact\": \"The litter moved approximately 0.25 m downhill before the belay arrested further travel. No injury, ground contact, or equipment damage was reported. The team paused the operation, checked the occupants, and reviewed the route and communications before continuing. The incident caused a short operational interruption and revealed a potential for more serious movement if a similar command mismatch occurred with more belay slack or a less favorable litter position; those conditions were not reported in this event.\", \"evidence_and_uncertainty\": \"The timeline is supported by the scene notes and statements from the lead rescuer, haul operator, and belay operator. The lead rescuer's account of calling hold conflicts with the haul operator's account of hearing a lower command. The approximate 0.25 m movement and the belay's transition from slack to tension are recorded, but neither line loads nor slack length were measured. No radio recording is available, so the exact wording, timing, and transmission quality cannot be resolved. The absence of visible damage is based on a visual check, not a documented technical inspection.\", \"equipment_system_anomalies\": \"No broken, deformed, or visibly damaged rope, connector, or anchor was reported. The belay line was reported to have slack before the unintended movement and to become tensioned as the litter moved downhill. The record contains no measured line loads, no measurement of the initial slack, and no inspection findings beyond the absence of visible damage.\"}","Event: Brief unintended litter movement following an ambiguous movement command. Location: East Slope, Bracken Creek access route. Date: 2024-09-07. A team was hauling an attended litter up a steep wooded slope toward a trail bench. The litter was managed on a main haul line with a separate belay line. The litter moved a short distance downhill during a stop request. No injury or equipment damage was reported.","At 14:06, the litter was moving uphill on a section of slope with roots and loose surface material. The lead rescuer identified an obstruction ahead and called for the team to hold. The haul operator reported hearing a command to lower by one increment and acted on that interpretation. The litter moved approximately 0.25 m downhill before the lead rescuer repeated the stop request. The belay line, which had some slack immediately before the movement, became tensioned and arrested further travel. The litter remained upright and did not contact the ground. The exact duration of movement was not recorded.","- 14:06 — The litter was being hauled uphill toward an obstruction; supported by the scene notes.\n- Shortly afterward — The lead rescuer called hold, while the haul operator understood a lower-by-one-increment command and briefly released the haul; supported by the two statements and scene notes, with disagreement about the command heard.\n- During the brief release — The litter moved approximately 0.25 m downhill and the belay line, previously slack, became tensioned; supported by the scene notes and belay operator statement.\n- After the repeated stop call — The team stabilized the litter, checked the occupants, and found no injury or visible equipment damage; supported by response records.\n- Before resuming — The team repeated and acknowledged commands and reassessed the route; supported by the response record.","The event is best characterized as a brief loss of coordinated movement control rather than a documented hardware failure. A mismatch between the lead rescuer's intended stop command and the haul operator's understanding led to unintended release of the haul. The belay line had slack immediately beforehand, so it did not prevent the initial movement; it became tensioned and arrested further travel. The records do not establish the amount of slack, line loads, or whether radio quality, phrasing, or another factor caused the misunderstanding. The belay functioned as a secondary restraint after movement began, but the event shows that communication and belay readiness were not fully aligned at that moment.","On the repeated stop call, the haul operator stopped movement and the belay operator maintained the line. The team confirmed that the litter was stable and checked the attendant and patient, with no injury reported. The load was held while the lead rescuer reassessed the route. The team then resumed only after the movement command and stop command were repeated and acknowledged by the relevant operators. A post-event visual check found no visible damage to the ropes, connectors, or anchors. The team recorded the communication discrepancy for review.","The repeated stop call was followed by prompt cessation of movement. The belay operator maintained the line, and the team checked the patient and attendant before resuming. Repeating and acknowledging commands after the event was a useful immediate correction. Review should focus on using unambiguous standard commands, requiring acknowledgement before movement, and coordinating belay readiness with haul actions. The record supports these as process improvements but does not identify the precise source of the initial misunderstanding.","[\"The lead rescuer and haul operator reported different understandings of the movement command, and the intended hold was not acted on immediately.\", \"The belay line had some slack immediately before the unintended movement, allowing a short downhill displacement before it became tensioned.\", \"The litter was approaching an obstruction on a steep slope, increasing the consequence of an unintended movement and the need for coordinated commands.\", \"The record does not document a closed-loop acknowledgement of the initial hold command before the haul operator acted.\"]","## Event overview\nOn 7 September 2024, an attended litter being hauled up East Slope near Bracken Creek moved approximately 0.25 m downhill after the lead rescuer called for the team to hold. The haul operator understood the command as an instruction to lower briefly. A separate belay line, reported to have some slack before the movement, became tensioned and arrested further travel. No injury or visible equipment damage was reported.\n\n## Sequence and failure analysis\nThe event occurred while the team was negotiating an obstruction on a steep, wooded route. The lead rescuer intended to stop movement. The haul operator's statement indicates a different understanding and a brief release of the haul. The litter consequently shifted downhill. The belay line did not prevent the initial displacement because it was not taut at that point, but it limited further travel as it became tensioned.\n\nThe records support a communication-and-coordination failure with a delayed secondary restraint, not a mechanical breakage. They do not establish why the command was misunderstood. The possibility of unclear wording or a transmission issue cannot be distinguished from other explanations on the available evidence. Likewise, the amount of belay slack and the forces involved were not measured.\n\n## Consequences and response\nThe litter did not reach the ground, and no injury or equipment damage was reported. The team stopped, maintained the belay, checked the occupants, and reassessed the route. Repeating and acknowledging commands before resuming helped restore shared understanding. The response was timely and proportionate to the recorded event.\n\nFor future operations, the team should review consistent command wording, closed-loop acknowledgement before movement, and coordination between haul and belay operators. Belay readiness should be considered as part of movement planning so that a secondary line does not have avoidable slack at a point where an unintended shift could have serious consequences. These recommendations address the documented communication mismatch and slack condition without assuming a specific cause that the record cannot establish.\n\n## Evidence limits\nThe analysis relies on the scene notes and individual statements. The accounts differ on the command heard, and no audio recording is available. Movement distance is approximate, and there are no load or slack measurements. No injury and no visible damage were reported, but the file does not contain a detailed equipment inspection report.","The lead rescuer stated that the intended command was hold because the litter was approaching an obstruction. The haul operator stated that the command was understood as lower by one increment and that the haul was released briefly. A belay operator reported that the belay had some slack before the movement and tightened as the litter moved. The litter attendant reported a brief downhill shift but no impact or injury. The statements differ on what command was heard; no recording of the radio traffic is available.","The litter moved approximately 0.25 m downhill before the belay arrested further travel. No injury, ground contact, or equipment damage was reported. The team paused the operation, checked the occupants, and reviewed the route and communications before continuing. The incident caused a short operational interruption and revealed a potential for more serious movement if a similar command mismatch occurred with more belay slack or a less favorable litter position; those conditions were not reported in this event.","The timeline is supported by the scene notes and statements from the lead rescuer, haul operator, and belay operator. The lead rescuer's account of calling hold conflicts with the haul operator's account of hearing a lower command. The approximate 0.25 m movement and the belay's transition from slack to tension are recorded, but neither line loads nor slack length were measured. No radio recording is available, so the exact wording, timing, and transmission quality cannot be resolved. The absence of visible damage is based on a visual check, not a documented technical inspection.","No broken, deformed, or visibly damaged rope, connector, or anchor was reported. The belay line was reported to have slack before the unintended movement and to become tensioned as the litter moved downhill. The record contains no measured line loads, no measurement of the initial slack, and no inspection findings beyond the absence of visible damage.",{"id":706,"relate_table":670,"relate_id":707,"file_size":573,"file_name":708,"path":8,"duration":573,"cate":483,"file_format":673,"audio_rate":8,"audio_channel":522,"audio_bit_depth":522,"quality":8,"annotation":709,"cate_name":675,"case_record":710,"scene_notes":711,"event_timeline":712,"failure_analysis":713,"response_records":714,"response_evaluation":715,"contributing_factors":716,"full_analysis_report":717,"personnel_statements":718,"consequences_and_impact":719,"evidence_and_uncertainty":720,"equipment_system_anomalies":721},14798,944342520,"样例_1.json","{\"case_record\": \"Event: Edge-protection displacement during a litter lowering operation. Location: Sector C, Alder Ridge. Date: 2024-05-18. The team was lowering a litter with an attendant from a rock ledge to a lower staging area. The operation used a primary lowering line and a separately anchored belay line. No injury was reported.\", \"scene_notes\": \"At 09:12, the litter was staged at the ledge and the edge-protection pad was placed where the primary line crossed the rock lip. The pad was secured before loading. At 09:18, while the litter was moving slowly below the lip, the attendant reported vibration and asked the team to stop. The litter remained suspended without visible contact with the wall. The edge-protection pad was then observed approximately 20 cm away from its initial position. The primary line had contacted the rock at the lip. The belay line remained in place and was reported as available throughout the stop.\", \"event_timeline\": \"- 09:12 — Litter staged and edge protection positioned; supported by the scene notes.\\n- 09:18 — During lowering below the lip, the attendant reported vibration and called for a stop; supported by the scene notes and attendant statement.\\n- Immediately after the stop — The litter remained suspended, and the team observed that the pad had shifted approximately 20 cm; supported by the scene notes.\\n- Following stabilization — Inspection found localized glazing and abrasion on the primary rope; supported by the equipment record.\\n- After the condition was identified — The rope was removed from service and the litter was moved to staging using the backup arrangement; supported by the response record.\", \"failure_analysis\": \"The documented event is consistent with loss of effective edge protection followed by rope contact with the rock lip. The pad displacement and localized rope glazing and abrasion support that interpretation, while the reported vibration provides a contemporaneous indication of increased or changing contact at the edge. The record does not establish exactly when or why the pad moved, nor does it quantify rope damage or prove that the rope reached a defined failure threshold. No primary-line break or uncontrolled descent occurred. The independent belay and the prompt stop limited the consequence of the developing condition. The evidence therefore supports an edge-management anomaly and rope damage, not a conclusion that the rope had already failed structurally.\", \"response_records\": \"The lowering team stopped movement, confirmed that the litter was stable, and maintained the independent belay. The edge team inspected the line path without moving the loaded system. After confirming that the operation could not continue safely with the observed rope condition, the team transferred the litter to a staging position using the available backup arrangement. The primary rope was tagged and quarantined for inspection. The team recorded the pad displacement and rope condition and reviewed the edge setup before resuming other work.\", \"response_evaluation\": \"The attendant's stop call, the lowering operator's prompt compliance, and continued availability of the belay were effective controls. The team avoided continuing to load a rope with visible damage, quarantined it, and recorded the condition. The response could be strengthened by documenting a deliberate post-load check of edge protection and line alignment, specifying who confirms the edge setup during movement, and preserving the rope inspection findings with the incident record. These are improvement opportunities; the available notes do not establish whether such checks were absent from the team's procedure.\", \"contributing_factors\": \"[\\\"The edge-protection pad moved approximately 20 cm during the operation, allowing the primary line to contact the rock lip.\\\", \\\"The rope crossed a rock edge where contact was possible; the post-event abrasion and glazing are consistent with that contact.\\\", \\\"The condition was first recognized through vibration reported by the attendant, indicating that the line path was not confirmed as stable during the lowering interval.\\\", \\\"The record does not describe a subsequent visual confirmation of pad position after the litter passed the lip; whether such a check occurred is unknown.\\\"]\", \"full_analysis_report\": \"## Event overview\\nOn 18 May 2024, a team lowering an attended litter from a rock ledge at Sector C, Alder Ridge, stopped the operation after the attendant reported vibration. The event resulted in localized abrasion and glazing on the primary rope and displacement of the edge-protection pad. No injury, rope break, or uncontrolled descent was reported.\\n\\n## Sequence and failure analysis\\nThe edge pad was positioned before loading. At approximately 09:18, while the litter was below the lip, the attendant requested a stop. The litter remained suspended, and the team found the pad about 20 cm from its original position. After unloading, inspection identified localized glazing and abrasion on the primary rope near the edge. These observations are consistent with the rope contacting the rock lip after the pad moved. They do not establish the exact movement mechanism or show that the rope's core was damaged.\\n\\nThe primary system did not undergo a documented complete failure. Instead, the evidence indicates a developing line-path hazard: displaced protection allowed contact, and the resulting rope condition made continued use inappropriate pending inspection. The independently anchored belay remained available. The stop call and controlled response prevented further loading while the condition was assessed.\\n\\n## Consequences and response\\nNo injury or sudden drop was reported. The team interrupted the lowering operation, moved the litter to staging using the backup arrangement, and removed the primary rope from service. This caused delay and reduced equipment availability, but avoided continued use of a visibly affected rope.\\n\\nThe response was effective in recognizing the warning, stopping promptly, retaining the belay, and quarantining the rope. Future reviews should consider documenting who verifies protection position as the load passes an edge and how that verification is communicated. Any rope inspection should record the extent and location of damage and the disposition decision.\\n\\n## Evidence limits\\nThe conclusion is based on the recorded pad displacement, rope condition, vibration report, and event sequence. The file does not include a detailed rope inspection report, measurements of the damaged section, or evidence identifying why the pad moved. Accordingly, the analysis identifies a supported line-contact mechanism but does not assign a more specific cause or claim structural failure.\", \"personnel_statements\": \"The attendant reported a short vibration through the litter and requested an immediate stop; they did not report a sudden drop. The edge attendant stated that the protection pad had been positioned before loading and that the line appeared centered on it at the start. The lowering operator reported maintaining a slow rate and stopping on the first stop call. No witness reported hearing a line strike or seeing the litter swing into the wall.\", \"consequences_and_impact\": \"No injury or uncontrolled movement was reported. The operation was interrupted, the primary rope was removed from service, and the litter had to be moved to staging using the backup arrangement. The observed rope damage required inspection before any further use and reduced the team's immediately available equipment. The event presented a potential for more serious consequences had the line damage progressed or the belay not remained available, but the record does not show that either occurred.\", \"evidence_and_uncertainty\": \"The scene notes establish the pad's initial placement, its later displacement, the timing of the stop, and the attendant's vibration report. The equipment record establishes localized glazing and abrasion on the primary rope and no reported visible damage to the belay or connectors. The response record establishes quarantine and use of the backup arrangement. Together, these facts support contact between the primary rope and the edge after the pad shifted. The record does not establish the cause or precise timing of the shift, the rope's internal condition, the magnitude of contact force, or whether the pad movement began before or after the reported vibration. No independent inspection report or detailed measurement is included.\", \"equipment_system_anomalies\": \"After the system was unloaded, a section of the primary rope approximately 1.2 m from the edge showed localized glazing and abrasion. The record does not document a cut, exposed core, or measured loss of diameter. The edge-protection pad had shifted from its recorded position. No visible damage was reported on the belay line, connectors, or anchor assemblies. The primary rope was removed from service pending inspection.\"}","Event: Edge-protection displacement during a litter lowering operation. Location: Sector C, Alder Ridge. Date: 2024-05-18. The team was lowering a litter with an attendant from a rock ledge to a lower staging area. The operation used a primary lowering line and a separately anchored belay line. No injury was reported.","At 09:12, the litter was staged at the ledge and the edge-protection pad was placed where the primary line crossed the rock lip. The pad was secured before loading. At 09:18, while the litter was moving slowly below the lip, the attendant reported vibration and asked the team to stop. The litter remained suspended without visible contact with the wall. The edge-protection pad was then observed approximately 20 cm away from its initial position. The primary line had contacted the rock at the lip. The belay line remained in place and was reported as available throughout the stop.","- 09:12 — Litter staged and edge protection positioned; supported by the scene notes.\n- 09:18 — During lowering below the lip, the attendant reported vibration and called for a stop; supported by the scene notes and attendant statement.\n- Immediately after the stop — The litter remained suspended, and the team observed that the pad had shifted approximately 20 cm; supported by the scene notes.\n- Following stabilization — Inspection found localized glazing and abrasion on the primary rope; supported by the equipment record.\n- After the condition was identified — The rope was removed from service and the litter was moved to staging using the backup arrangement; supported by the response record.","The documented event is consistent with loss of effective edge protection followed by rope contact with the rock lip. The pad displacement and localized rope glazing and abrasion support that interpretation, while the reported vibration provides a contemporaneous indication of increased or changing contact at the edge. The record does not establish exactly when or why the pad moved, nor does it quantify rope damage or prove that the rope reached a defined failure threshold. No primary-line break or uncontrolled descent occurred. The independent belay and the prompt stop limited the consequence of the developing condition. The evidence therefore supports an edge-management anomaly and rope damage, not a conclusion that the rope had already failed structurally.","The lowering team stopped movement, confirmed that the litter was stable, and maintained the independent belay. The edge team inspected the line path without moving the loaded system. After confirming that the operation could not continue safely with the observed rope condition, the team transferred the litter to a staging position using the available backup arrangement. The primary rope was tagged and quarantined for inspection. The team recorded the pad displacement and rope condition and reviewed the edge setup before resuming other work.","The attendant's stop call, the lowering operator's prompt compliance, and continued availability of the belay were effective controls. The team avoided continuing to load a rope with visible damage, quarantined it, and recorded the condition. The response could be strengthened by documenting a deliberate post-load check of edge protection and line alignment, specifying who confirms the edge setup during movement, and preserving the rope inspection findings with the incident record. These are improvement opportunities; the available notes do not establish whether such checks were absent from the team's procedure.","[\"The edge-protection pad moved approximately 20 cm during the operation, allowing the primary line to contact the rock lip.\", \"The rope crossed a rock edge where contact was possible; the post-event abrasion and glazing are consistent with that contact.\", \"The condition was first recognized through vibration reported by the attendant, indicating that the line path was not confirmed as stable during the lowering interval.\", \"The record does not describe a subsequent visual confirmation of pad position after the litter passed the lip; whether such a check occurred is unknown.\"]","## Event overview\nOn 18 May 2024, a team lowering an attended litter from a rock ledge at Sector C, Alder Ridge, stopped the operation after the attendant reported vibration. The event resulted in localized abrasion and glazing on the primary rope and displacement of the edge-protection pad. No injury, rope break, or uncontrolled descent was reported.\n\n## Sequence and failure analysis\nThe edge pad was positioned before loading. At approximately 09:18, while the litter was below the lip, the attendant requested a stop. The litter remained suspended, and the team found the pad about 20 cm from its original position. After unloading, inspection identified localized glazing and abrasion on the primary rope near the edge. These observations are consistent with the rope contacting the rock lip after the pad moved. They do not establish the exact movement mechanism or show that the rope's core was damaged.\n\nThe primary system did not undergo a documented complete failure. Instead, the evidence indicates a developing line-path hazard: displaced protection allowed contact, and the resulting rope condition made continued use inappropriate pending inspection. The independently anchored belay remained available. The stop call and controlled response prevented further loading while the condition was assessed.\n\n## Consequences and response\nNo injury or sudden drop was reported. The team interrupted the lowering operation, moved the litter to staging using the backup arrangement, and removed the primary rope from service. This caused delay and reduced equipment availability, but avoided continued use of a visibly affected rope.\n\nThe response was effective in recognizing the warning, stopping promptly, retaining the belay, and quarantining the rope. Future reviews should consider documenting who verifies protection position as the load passes an edge and how that verification is communicated. Any rope inspection should record the extent and location of damage and the disposition decision.\n\n## Evidence limits\nThe conclusion is based on the recorded pad displacement, rope condition, vibration report, and event sequence. The file does not include a detailed rope inspection report, measurements of the damaged section, or evidence identifying why the pad moved. Accordingly, the analysis identifies a supported line-contact mechanism but does not assign a more specific cause or claim structural failure.","The attendant reported a short vibration through the litter and requested an immediate stop; they did not report a sudden drop. The edge attendant stated that the protection pad had been positioned before loading and that the line appeared centered on it at the start. The lowering operator reported maintaining a slow rate and stopping on the first stop call. No witness reported hearing a line strike or seeing the litter swing into the wall.","No injury or uncontrolled movement was reported. The operation was interrupted, the primary rope was removed from service, and the litter had to be moved to staging using the backup arrangement. The observed rope damage required inspection before any further use and reduced the team's immediately available equipment. The event presented a potential for more serious consequences had the line damage progressed or the belay not remained available, but the record does not show that either occurred.","The scene notes establish the pad's initial placement, its later displacement, the timing of the stop, and the attendant's vibration report. The equipment record establishes localized glazing and abrasion on the primary rope and no reported visible damage to the belay or connectors. The response record establishes quarantine and use of the backup arrangement. Together, these facts support contact between the primary rope and the edge after the pad shifted. The record does not establish the cause or precise timing of the shift, the rope's internal condition, the magnitude of contact force, or whether the pad movement began before or after the reported vibration. No independent inspection report or detailed measurement is included.","After the system was unloaded, a section of the primary rope approximately 1.2 m from the edge showed localized glazing and abrasion. The record does not document a cut, exposed core, or measured loss of diameter. The edge-protection pad had shifted from its recorded position. No visible damage was reported on the belay line, connectors, or anchor assemblies. The primary rope was removed from service pending inspection.","{\"case_record\":\"Event: Portable anchor-frame movement during initial loading for a shaft rescue. Location: Service shaft 4, Larkspur Works. Date: 2025-02-11. A team was preparing to raise an attended litter from the shaft to the surface using a portable anchor frame and a separate backup line connected to a rock anchor. During initial loading, one frame foot shifted on loose gravel. The operation was stopped before the litter was raised. No injury was reported.\",\"scene_notes\":\"At 16:32, the frame was positioned at the shaft edge on a gravel surface. A chalk mark had been placed beside the front foot to observe movement. As the team began a controlled initial loading with the litter still at the lower staging point, the front foot moved approximately 35 mm along the surface and the frame showed a slight tilt. The backup line remained connected to its separate rock anchor and was reported to remain tensioned. The frame did not overturn, and no person or litter fell. The ground around the foot appeared disturbed after the movement.\",\"event_timeline\":\"- 16:32 — The portable frame was positioned at the shaft edge on gravel, with a chalk reference at the front foot; supported by the scene notes.\\n- During initial loading — The front foot moved approximately 35 mm and the frame tilted slightly; supported by the observer's statement and scene notes.\\n- Immediately after the movement was called — The operator stopped loading; the backup line remained connected and tensioned; supported by personnel statements.\\n- After the system was stabilized — The team unloaded the frame and kept the litter at the lower staging point; supported by response records.\\n- Before resuming — The team selected a firmer surface and confirmed stability during renewed controlled loading; supported by response records.\",\"failure_analysis\":\"The observed movement is consistent with the frame foot losing stable support on the gravel surface under initial loading. The displacement relative to the chalk mark and disturbed ground support a movement of the footing; the slight tilt indicates that the frame's position changed. The records do not quantify the applied load or establish whether loose gravel alone, uneven contact, or another surface condition initiated the movement. No structural failure of the frame or attached hardware was observed. The separately anchored backup remained connected and tensioned, and the team stopped before raising the litter. The evidence therefore supports an instability of the initial frame placement, not a failure of the frame structure or backup anchor.\",\"response_records\":\"The team stopped loading and maintained control of both lines. The frame was unloaded, and the litter remained at the lower staging point while the team reassessed the surface and anchor arrangement. The team then used a revised setup located on a firmer surface, with the backup remaining independent. Before proceeding, the edge observer confirmed that the frame was stable during a renewed controlled load. The initial frame position was not returned to service. The movement and ground condition were recorded for equipment and site review.\",\"response_evaluation\":\"The chalk reference made the foot movement visible, and the edge observer's call was followed by an immediate stop. Maintaining both lines, unloading the frame, and relocating to a firmer surface were appropriate responses to the observed instability. The team confirmed the revised arrangement under controlled loading before proceeding. The record could be improved by documenting the revised support conditions and the basis for the stability check, as well as any subsequent technical inspection. It does not establish whether formal surface-assessment criteria were available or used before the initial setup.\",\"contributing_factors\":\"[\\\"The frame was positioned on gravel, and the front foot moved with visible ground disturbance during initial loading.\\\", \\\"The approximately 35 mm displacement and slight tilt show that the initial support arrangement did not remain stable under the load applied.\\\", \\\"The operation involved a shaft-edge setup where frame movement could affect the suspended system; the team had to stop before raising the litter.\\\", \\\"The record contains no load measurements or ground assessment, so the contribution of load magnitude, surface unevenness, or gravel compaction cannot be separated.\\\"]\",\"full_analysis_report\":\"## Event overview\\nOn 11 February 2025, a portable anchor frame moved during initial loading at Service shaft 4, Larkspur Works. The frame stood on gravel at the shaft edge. An observer saw its front foot shift approximately 35 mm from a chalk reference and noted a slight tilt. The team stopped before raising the attended litter. The litter remained at the lower staging point, the backup line remained connected to a separate rock anchor, and no injury was reported.\\n\\n## Sequence and failure analysis\\nThe movement occurred as the team began applying load to the frame. The disturbed gravel around the foot and the change relative to the chalk mark support the conclusion that the footing moved on the surface. The slight tilt indicates that the frame's position was affected. The available evidence does not show a fracture, deformation, or failure of frame hardware. It also does not establish the applied load or whether the initiating condition was loose gravel, uneven foot contact, surface slope, or a combination of factors.\\n\\nThe principal failure mode was loss of stable support at the initial frame placement. The separate backup line remained connected and tensioned, and the litter did not undergo a reported sudden movement. These controls limited exposure while the team stopped and reassessed. The record does not support attributing the event to structural failure of the frame or anchor.\\n\\n## Consequences and response\\nNo fall, injury, or visible equipment damage was reported. The lift was delayed while the team unloaded the frame, selected a firmer surface, and confirmed stability during renewed controlled loading. The response was effective: movement was detected against a reference mark, the operator stopped promptly, and the team did not continue raising the litter on the unstable setup.\\n\\nFurther review should document the surface conditions at the revised position and the method used to confirm stability. A technical inspection of the frame and attached hardware should be recorded if required by the team's equipment process. The initial surface and the observed displacement should be retained in the site review so that future setup decisions account for the demonstrated movement.\\n\\n## Evidence limits\\nThe analysis is grounded in the chalk-mark displacement, disturbed gravel, slight tilt, and sequence recorded by the team. Applied load, ground compaction, and surface geometry were not measured. The exact mechanism causing the foot to move therefore remains uncertain. The record reports no visible structural damage but does not include a detailed inspection report.\",\"personnel_statements\":\"The edge observer stated that the front foot moved relative to the chalk mark and that the frame tilted slightly. The frame operator reported stopping the load as soon as the movement was called out. The backup-line operator stated that the line remained connected to the separate rock anchor and was tensioned during the pause. The person at the lower staging point reported no sudden movement of the litter. No witness reported a fall or injury.\",\"consequences_and_impact\":\"The frame did not overturn, the litter remained at the lower staging point, and no injury was reported. The team halted the planned lift, unloaded and repositioned the frame, and delayed the rescue operation while confirming a stable setup. No visible damage to the frame, hardware, backup line, or anchor was reported. The movement presented a potential for loss of control had loading continued, but the record documents no such loss or resulting harm.\",\"evidence_and_uncertainty\":\"The scene notes and observer statement establish movement of approximately 35 mm relative to a chalk mark, slight frame tilt, and disturbed gravel. The response record establishes that the frame was unloaded and repositioned before the litter was raised. Personnel statements report that the separate backup line remained connected and tensioned and that the litter did not move suddenly. There are no measurements of applied load, frame-foot pressure, surface compaction, or ground slope. The cause is therefore limited to unstable support at the initial placement; the specific surface or loading mechanism cannot be determined from the available record. No detailed post-event frame inspection is included.\",\"equipment_system_anomalies\":\"The front foot of the portable frame shifted approximately 35 mm from the chalk reference during initial loading. A disturbed area in the gravel was observed around the foot. No visible deformation, cracking, or connector damage was reported on the frame or attached hardware. The backup line and its separate rock anchor showed no reported visible damage. The record does not include load measurements, ground compaction data, or a technical inspection report for the frame.\"}","MOBIUSI INC","https:\u002F\u002Fstatic.mobiusi.com\u002Fmobiwusi\u002F20250829\u002F7bf4ac62b4533e2b809998a6f1c5491e.png?Expires=1792463130&OSSAccessKeyId=LTAI5tH8MQqhgeiAtrzCHrxM&Signature=v6Tr8jBrdm4s5wU1SnnyGsYg%2Bhw%3D&x-oss-process=image%2Fresize%2Cm_fill%2Cw_35%2Ch_35",[726,732],{"type":727,"title":728,"count_data":729},"bar","Length distribution",[730],{"name":731,"value":483},"1k lower",{"type":733,"title":734,"count_data":735},"pie","Language distribution",[736],{"name":737,"value":483},"English"]