KyeongminandClaude Opus 4.8
b836e79ee1
- src: phase_z2 composition/mapper/pipeline/placement_planner/retry, ai_fallback(prompts/schema/validate), mdx_text_atoms 신규 - Front: PipelineTracePanel 신규, FramePanel/SlideCanvas/Home/designAgentApi 등 갱신 + 테스트 4종 추가 - templates/phase_z2: catalog(component_expansion_registry, node_slot_mapping 신규), frames, families, slide_base 갱신 - tests/matching: phase2~26 매칭 실험 스크립트·리포트·온톨로지 전체 (미커밋 진행분) - tests: b4_v4 evidence, task5~28.5 시리즈, regression(imp95 baseline) 등 신규 테스트 대량 추가 - docs/reference: MDX 구조 인벤토리, MDX→Frame 구조 계약 문서 - scripts: mdx 계약/parity/coverage/viewport 체크, gitea comment, run sync 유틸 - .gitignore: tmp*.json, chromedriver, .orchestrator, *.pkl, Front_test* 등 임시/스냅샷 제외 미완성 작업의 보존용 스냅샷 커밋 (2026-07-02) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
349 lines
26 KiB
HTML
349 lines
26 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="ko">
|
|
<head>
|
|
<meta charset="utf-8">
|
|
<title>Anchor Sets Overview — 전체 32 frame 일람</title>
|
|
<style>
|
|
body { font-family: -apple-system, "Segoe UI", Pretendard, sans-serif; max-width: 1100px; margin: 2em auto; padding: 0 1.5em 3em; line-height: 1.55; color: #222; }
|
|
h1 { border-bottom: 2px solid #333; padding-bottom: 0.2em; }
|
|
h3 { margin-top: 2em; color: #111; border-bottom: 1px solid #ddd; padding-bottom: 0.3em; }
|
|
h3:has(em) { background: #fffbdc; padding: 0.4em 0.6em; border-radius: 4px; }
|
|
ul { margin: 0.3em 0 0.8em 0; }
|
|
li { margin: 0.15em 0; }
|
|
code { background: #f4f4f4; padding: 1px 5px; border-radius: 3px; font-size: 0.92em; }
|
|
strong { color: #0a6; }
|
|
em { color: #888; font-style: normal; }
|
|
sup { color: #d33; font-size: 0.7em; margin-left: 1px; }
|
|
.subject, p > strong + em { color: #555; }
|
|
hr { border: 0; border-top: 1px solid #ddd; margin: 1.5em 0; }
|
|
</style>
|
|
</head>
|
|
<body>
|
|
<h1>Anchor Sets Overview — 전체 32 frame 일람</h1>
|
|
<p>리뷰용 한 페이지 뷰. 각 anchor_set 의 id + terms 만 표시.
|
|
상세 수치는 <code>anchor_sets_report.html</code> 참조.</p>
|
|
<p><strong>범례</strong>:
|
|
- <code>S</code> = special token (S/W, H/W, 2D, 3D, DX, BIM, As-is, To-Be, 결과혁신, 과정혁신, 필수조건, 의사소통, 시행착오)
|
|
- <code>M1/M2/M3</code> = 해당 token 의 mdx_df (MDX section 몇 개에 등장)
|
|
- <code>RN</code> = review_needed term
|
|
- 🔸 = set 레벨 review_needed (유지하되 재검토)
|
|
- 🎯 TARGET = MDX 매칭 정답 frame (13, 14, 18, 29)</p>
|
|
<ul>
|
|
<li>frames: <strong>32</strong></li>
|
|
<li>anchor_sets: <strong>92</strong></li>
|
|
</ul>
|
|
<hr />
|
|
<h3>Frame 1 / 1171281172</h3>
|
|
<p><strong>Subject</strong>: 기술기반 중요성 / 디지털전환 직관지 역할 / 품질향상 & 호환성 / 기존 S/W 한계 인식 / S/W 개발목표 설정
|
|
<strong>total_unique_tokens</strong>: 18</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>sw_dx_foundation</strong>: <code>S/W</code> (S,M3), <code>DX</code> (S,M3), <code>융합</code> (M1)</li>
|
|
<li><strong>recognition_and_setup</strong>: <code>인식</code> (M1), <code>설정</code> (RN), <code>역할</code> (M1)</li>
|
|
<li><strong>quality_compatibility</strong>: <code>품질</code> (M3), <code>향상</code> (M3), <code>호환</code> (RN)</li>
|
|
</ul>
|
|
<h3>Frame 2 / 1171281173</h3>
|
|
<p><strong>Subject</strong>: Domain knowledge(토목공학 지식)이 반영될 수 있는 기술기반 / Engineering S/W 개발 / Open Source 혁명 / AI 비약적 발전 / AI
|
|
<strong>total_unique_tokens</strong>: 32</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>ai_open_source</strong>: <code>AI</code> (RN), <code>Open</code> (RN), <code>Source</code> (RN)</li>
|
|
<li><strong>domain_knowledge</strong>: <code>Domain</code> (RN), <code>knowledge</code> (RN), <code>지식</code> (M1)</li>
|
|
<li><strong>sw_hw_basis</strong>: <code>S/W</code> (S,M3), <code>H/W</code> (S,M1), <code>기반</code> (M3), <code>개발</code> (M2)</li>
|
|
</ul>
|
|
<h3>Frame 3 / 1171281174</h3>
|
|
<p><strong>Subject</strong>: 국외 / 오류에 의한 Claim 최소화 / 설계 업무 시 사업 Data 정리 필수 / 자체적인 기술업무 Manual 작성 / 데이터 통합 및 관리
|
|
<strong>total_unique_tokens</strong>: 17</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>data_documentation</strong>: <code>Data</code> (M1), <code>데이터</code> (M3), <code>정리</code></li>
|
|
<li><strong>business_manual_claim</strong>: <code>Manual</code> (RN), <code>Claim</code> (M1), <code>업무</code> (M3)</li>
|
|
</ul>
|
|
<h3>Frame 4 / 1171281175</h3>
|
|
<p><strong>Subject</strong>: 국내 / 건설관리사 / 설계사 / 시공사 / 정부기관&발주처
|
|
<strong>total_unique_tokens</strong>: 45</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>government_regulation</strong>: <code>정부</code> (RN), <code>규정</code> (M1), <code>지침</code> (M1), <code>형식</code> (RN)</li>
|
|
<li><strong>international_finance</strong>: <code>ADB</code> (RN), <code>IBRD</code> (RN), <code>차관</code> (RN), <code>경제</code></li>
|
|
</ul>
|
|
<p><strong>Notes</strong>: <em>삭제된 set: stagnation_obstacles [답습, 저하, 저해].
|
|
이유: 구체화 가능한 후보(규제/제도/장애) 가 Frame 4 에 없음. 부정어만 묶인 anchor 는 약함.</em></p>
|
|
<h3>Frame 5 / 1171281176</h3>
|
|
<p><strong>Subject</strong>: 보상현황·민원 관리 / 종합평면도, 용지도를 사용한 토지 및 물건 현황 시각화 / 보상서류, 사진 및 영상 등 필지별 보상 현황 정보 시각화
|
|
<strong>total_unique_tokens</strong>: 21</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>compensation_status</strong>: <code>보상</code> (RN), <code>현황</code> (RN), <code>민원</code> (M1)</li>
|
|
<li><strong>visualization_media</strong>: <code>시각</code> (M3), <code>영상</code> (RN), <code>사진</code> (RN)</li>
|
|
<li><strong>documentation_analysis</strong>: <code>서류</code> (M1), <code>분석</code> (M1), <code>종합</code> (M1)</li>
|
|
</ul>
|
|
<h3>Frame 6 / 1171281177</h3>
|
|
<p><strong>Subject</strong>: 보상현황·민원 관리 / 시공단계 토지 및 지장물에 대한 보상 현황과 다양한 민원 관리 업무 지원 / 종합 평면도와 용지도를 사용하여 토지 및 물건 현황, 필지별 보상현황 정보 시각화
|
|
<strong>total_unique_tokens</strong>: 43</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>civil_complaint</strong>: <code>민원</code> (M1), <code>보상</code> (RN), <code>현황</code> (RN), <code>토지</code> (RN)</li>
|
|
<li><strong>risk_response</strong>: <code>리스크</code> (M1), <code>대응</code> (M1), <code>선제</code> (RN)</li>
|
|
<li><strong>complaint_types</strong>: <code>유형</code>, <code>요청</code> (RN), <code>승복</code> (RN)</li>
|
|
<li><strong>construction_issues</strong>: <code>데크</code> (RN), <code>배수</code> (RN), <code>불편</code> (RN)</li>
|
|
</ul>
|
|
<h3>Frame 7 / 1171281178</h3>
|
|
<p><strong>Subject</strong>: Display / 범위가 넓고 긴 형태의 인프라 시설 규모에 적합한 대형 사이니지를 적용하여 벡터기반 도면, 3D정보 모델을 높은 정밀도로 표출 / Server & Strorage
|
|
<strong>total_unique_tokens</strong>: 147</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>realtime_monitoring</strong>: <code>실시간</code> (RN), <code>CCTV</code> (RN), <code>사전</code> (M1), <code>위험</code> (RN), <code>데이터</code> (M3)</li>
|
|
<li><strong>bim_dx_digital</strong>: <code>BIM</code> (S,M2), <code>DX</code> (S,M3), <code>3D</code> (S,M3)</li>
|
|
<li><strong>field_management</strong>: <code>현장</code> (M1), <code>관리</code> (M3), <code>공사</code> (M1)</li>
|
|
</ul>
|
|
<p><strong>Notes</strong>: <em>삭제된 set: data_efficiency [데이터, 효율, 기반].
|
|
이유: 너무 일반어 조합. 데이터 는 realtime_monitoring 으로 흡수, 효율/기반 은 anchor 에서 제외.</em></p>
|
|
<h3>Frame 8 / 1171281179</h3>
|
|
<p><strong>Subject</strong>: 효율적인 정보의 관리와 활용 / 무슨 정보 / What / 수량, CBS 내역, 단가, 공사일정, 자원 투입계획 등 계획 정보 / 일일 작업수량, 실제 투입 자원 등 공사 실행 정보
|
|
<strong>total_unique_tokens</strong>: 60</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>construction_planning</strong>: <code>공사</code> (M1), <code>계획</code> (M3), <code>수량</code> (M2)</li>
|
|
<li><strong>information_linkage</strong>: <code>정보</code> (M3), <code>연계</code> (M2), <code>객체</code> (RN)</li>
|
|
<li><strong>resource_planning</strong>: <code>자원</code> (M1), <code>투입</code> (M1)</li>
|
|
<li><strong>sw_3d_modeling</strong>: <code>S/W</code> (S,M3), <code>3D</code> (S,M3)</li>
|
|
</ul>
|
|
<h3>Frame 9 / 1171281180</h3>
|
|
<p><strong>Subject</strong>: 시공 전 모델 기반 시공상세 정보물 이용한 시공계획 작성 지원 / 시공 상세 정보물 / 3차원 형상의 정보 모델과 Data Base (D/B) / 목적물, 가시설 등의 단계별 시공 시뮬레이션
|
|
<strong>total_unique_tokens</strong>: 28</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>simulation_planning</strong>: <code>시뮬레이션</code> (RN), <code>시공</code> (M3), <code>모델</code> (M3), <code>도면</code> (M3)</li>
|
|
<li><strong>pre_construction_info</strong>: <code>정보</code> (M3), <code>추출</code> (M1), <code>안전</code> (M2)</li>
|
|
</ul>
|
|
<p><strong>Notes</strong>: <em>삭제된 set: visualization_aid [가시, 영상물, 차원].
|
|
이유: 가시/차원 너무 일반적, 영상물 단독으로는 anchor 약함. 다른 set 에 자연스러운 흡수처 없음.</em></p>
|
|
<h3>Frame 10 / 1171281181</h3>
|
|
<p><strong>Subject</strong>: 현장 실효성 증대 위한 기본사항 / 시스템 내 디지털 정보물 관리 / 특정 S/W 종속성 해소 / 현장 맞춤형 / Solution
|
|
<strong>total_unique_tokens</strong>: 22</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>field_effectiveness</strong>: <code>현장</code> (M1), <code>실효</code> (RN), <code>증대</code> (M1)</li>
|
|
</ul>
|
|
<p><strong>Notes</strong>: <em>삭제된 set: customization_info [맞춤, 정보, 특정].
|
|
이유: 정보/특정 너무 일반어. 맞춤 단독은 1-term anchor 라 약함.
|
|
Frame 10 에 맞춤을 묶을 구체 term 없음 (field_effectiveness 와 맥락 다름).</em></p>
|
|
<h3>Frame 11 / 1171281182</h3>
|
|
<p><strong>Subject</strong>: 시공단계 BIM 모델과 정보 활용 구분 / 모델기반 / (Model-based) / 최종 목적물의 전체 또는 부분 3D 형상정보 활용 / 객체기반
|
|
<strong>total_unique_tokens</strong>: 28</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>bim_model_usage</strong>: <code>BIM</code> (S,M2), <code>모델</code> (M3), <code>활용</code> (M3), <code>정보</code> (M3)</li>
|
|
<li><strong>location_based</strong>: <code>위치</code> (M2), <code>Position</code> (RN), <code>based</code> (RN)</li>
|
|
<li><strong>construction_object</strong>: <code>공사</code> (M1), <code>객체</code> (RN), <code>Model</code> (M1)</li>
|
|
</ul>
|
|
<h3>Frame 12 / 1171281189</h3>
|
|
<p><strong>Subject</strong>: 건설산업의 목표 (BIM의 목적) / 안전과 / 품질 / 생산성 / 향상
|
|
<strong>total_unique_tokens</strong>: 56</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>quality_safety</strong>: <code>품질</code> (M3), <code>안전</code> (M2), <code>향상</code> (M3)</li>
|
|
<li><strong>communication_trust</strong>: <code>소통</code> (M2), <code>신뢰</code> (M1), <code>강화</code> (M1), <code>의사소통</code> (S,M1)</li>
|
|
<li><strong>cost_productivity</strong>: <code>비용</code> (M3), <code>생산</code> (M2), <code>최소</code> (M3)</li>
|
|
<li><strong>bim_process_innovation</strong>: <code>BIM</code> (S,M2), <code>과정혁신</code> (S,M1), <code>3D</code> (S,M3)</li>
|
|
</ul>
|
|
<h3>Frame 13 / 1171281190 🎯 <strong>TARGET</strong></h3>
|
|
<p><strong>Subject</strong>: 필수조건 / 기술 / 디지털 / 깊은 기반 / (건설산업, 토목) 지식
|
|
<strong>total_unique_tokens</strong>: 57</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>three_pillars</strong>: <code>기술</code> (M3), <code>사람</code> (M1), <code>자연</code> (M1)</li>
|
|
<li><strong>prerequisites</strong>: <code>필수조건</code> (S,M1), <code>역량</code> (M2), <code>여건</code> (M1)</li>
|
|
</ul>
|
|
<p><strong>Notes</strong>: <em>dx_capability [S/W, H/W, 기술, 개발] 은 codex 판단으로 weak 분류, 제외.
|
|
사유: S/W/H/W/기술/개발 은 너무 넓은 도메인어라 Frame 13 의 핵심 선택 신호가 아님.</em></p>
|
|
<h3>Frame 14 / 1171281191 🎯 <strong>TARGET</strong></h3>
|
|
<p><strong>Subject</strong>: 발주자 / 목표 / 시공자 / 설계자 / 민원, 재 작업 등의 예방 및 최소화
|
|
<strong>total_unique_tokens</strong>: 69</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>construction_personas</strong>: <code>발주</code> (M1), <code>시공</code> (M3), <code>설계자</code> (M1)</li>
|
|
<li><strong>collaboration_outcomes</strong>: <code>의사소통</code> (S,M1), <code>소통</code> (M2), <code>원활</code> (M1)</li>
|
|
<li><strong>quality_risk_outcomes</strong>: <code>오류</code> (M3), <code>예방</code> (M1), <code>품질</code> (M3), <code>향상</code> (M3), <code>최소</code> (M3)</li>
|
|
<li><strong>management_outcomes</strong>: <code>관리</code> (M3), <code>효율</code> (M2), <code>실무자</code> (M1)</li>
|
|
</ul>
|
|
<h3>Frame 15 / 1171281192</h3>
|
|
<p><strong>Subject</strong>: 정책목표 / 실행요건 / 국가 신 성장 동력 / 재도약 / 공기ㆍ공사비
|
|
<strong>total_unique_tokens</strong>: 83</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>dx_capability</strong>: <code>DX</code> (S,M3), <code>수행</code> (M3), <code>능력</code> (M2), <code>기술</code> (M3)</li>
|
|
<li><strong>experience_knowledge</strong>: <code>경험</code> (M1), <code>지식</code> (M1), <code>보유</code> (M1)</li>
|
|
<li><strong>user_innovation</strong>: <code>사용자</code> (M1), <code>혁신</code> (M2), <code>창의</code> (M1), <code>실행</code> (M3)</li>
|
|
<li><strong>trial_growth</strong>: <code>시행착오</code> (S,M1), <code>의지</code> (M2), <code>도약</code> (RN)</li>
|
|
</ul>
|
|
<h3>Frame 16 / 1171281193</h3>
|
|
<p><strong>Subject</strong>: 정책 집행 / 수행 개념 / 근본 취지의 이해부족 / 지속적 투자 의지 부재 / Rome wasn't Built in a day!
|
|
<strong>total_unique_tokens</strong>: 151</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>bim_dx_misunderstanding</strong>: <code>BIM</code> (S,M2), <code>DX</code> (S,M3), <code>개념</code> (M2), <code>이해</code> (M3)</li>
|
|
<li><strong>sw_dependency</strong>: <code>S/W</code> (S,M3), <code>모델</code> (M3), <code>의존</code> (M2), <code>과도</code> (RN)</li>
|
|
<li><strong>tech_capability_gap</strong>: <code>기술</code> (M3), <code>부재</code> (RN), <code>부족</code> (RN), <code>기술력</code> (RN)</li>
|
|
</ul>
|
|
<p><strong>Notes</strong>: <em>삭제된 set: institutional_evasion [방침, 집행, 회피].
|
|
이유: Batch 1 Frame 4 stagnation_obstacles 와 동일 패턴 — 부정/비판 맥락 부정어 조합은 anchor 구체성 약함.</em></p>
|
|
<h3>Frame 17 / 1171281194</h3>
|
|
<p><strong>Subject</strong>: 현황 및 문제점 / 개념 부재 / BIM을 Digital 전환의 개념이 아닌, CAD의 확장판으로 해석하여 3D를 그리는 수단 정도로만 인식 / 잘못된 접근방식
|
|
<strong>total_unique_tokens</strong>: 97</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>design_approach_critique</strong>: <code>설계</code> (M3), <code>방식</code> (M3), <code>수행</code> (M3), <code>개념</code> (M2)</li>
|
|
<li><strong>tool_misuse</strong>: <code>S/W</code> (S,M3), <code>2D</code> (S,M3), <code>3D</code> (S,M3), <code>전제</code> (RN), <code>기존</code> (M2)</li>
|
|
<li><strong>perception_gap</strong>: <code>인식</code> (M1), <code>제시</code> (M1), <code>기술자</code> (RN)</li>
|
|
</ul>
|
|
<h3>Frame 18 / 1171281195 🎯 <strong>TARGET</strong></h3>
|
|
<p><strong>Subject</strong>: BIM과 DX의 이해 / BIM vs. DX / Only 3D / 모델 제작용 상용 S/W [Civil 3D, Revit, Navisworks, Autocad] / 기존 2D 설계방식 유지
|
|
<strong>total_unique_tokens</strong>: 106</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>bim_dx</strong>: <code>BIM</code> (S,M2), <code>DX</code> (S,M3)</li>
|
|
<li><strong>dimensional_comparison</strong>: <code>2D</code> (S,M3), <code>3D</code> (S,M3), <code>모델</code> (M3)</li>
|
|
<li><strong>software_tools</strong>: <code>S/W</code> (S,M3), <code>Civil</code> (M1), <code>Revit</code> (M1), <code>Navisworks</code> (M1), <code>Autocad</code> (M1)</li>
|
|
</ul>
|
|
<p><strong>Notes</strong>: <em>weak 세트로 검토되었으나 제외됨: [상용, 소극, 구체]
|
|
— 너무 일반적/추상적 의미라 디자인 선택 신호 약함.</em></p>
|
|
<h3>Frame 19 / 1171281197</h3>
|
|
<p><strong>Subject</strong>: 설계방식의 왜곡은 엔지니어를 기능인으로 전락시킨다. / 건설산업 설계 특성 / 매번 1회성 작업 / 각 단계별 수많은 / 업무 Process가 연계됨
|
|
<strong>total_unique_tokens</strong>: 45</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>engineer_degradation</strong> 🔸<strong>review_needed</strong>: <code>엔지니어</code> (RN), <code>기능인</code> (RN), <code>전락</code> (RN), <code>왜곡</code> (RN)</li>
|
|
<li><strong>design_added_value</strong>: <code>설계</code> (M3), <code>가치</code> (M3), <code>부가</code> (M2), <code>작업</code> (M1)</li>
|
|
<li><strong>decision_authority</strong>: <code>결정</code> (M1), <code>의사</code> (M1), <code>업무</code> (M3)</li>
|
|
</ul>
|
|
<h3>Frame 20 / 1171281198</h3>
|
|
<p><strong>Subject</strong>: 디지털 전환(DX)은 S/W가 필수다. / BIM 전면설계 / 디지털 전환 S/W / 고부가가치 산업전환 / 건설산업 생산성 향상
|
|
<strong>total_unique_tokens</strong>: 42</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>dx_industry_transition</strong>: <code>DX</code> (S,M3), <code>산업</code> (M1), <code>전환</code> (M2), <code>고도</code> (M1), <code>BIM</code> (S,M2)</li>
|
|
<li><strong>added_value</strong>: <code>가치</code> (M3), <code>부가</code> (M2), <code>개선</code> (M2)</li>
|
|
<li><strong>sw_necessity</strong>: <code>S/W</code> (S,M3), <code>필요</code> (M3), <code>업무</code> (M3)</li>
|
|
</ul>
|
|
<p><strong>Notes</strong>: <em>삭제된 set: process_innovation_context [과정혁신, 이해, 건설].
|
|
이유: 이해/건설 너무 일반어, 과정혁신 단독은 1-term anchor 라 약함. dx_industry_transition 에 과정혁신 흡수도 의미 부자연 → 삭제.</em></p>
|
|
<h3>Frame 21 / 1171281201</h3>
|
|
<p><strong>Subject</strong>: Solution Engn. S/W / Model Checker / WatchBIM / Domainer / BCMF
|
|
<strong>total_unique_tokens</strong>: 34</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>solution_platform</strong>: <code>S/W</code> (S,M3), <code>Solution</code> (M2), <code>Platform</code> (RN), <code>Engn.</code> (M1)</li>
|
|
<li><strong>collaboration_field</strong>: <code>협업</code> (M3), <code>현장</code> (M1), <code>반영</code> (M1), <code>의사소통</code> (S,M1)</li>
|
|
</ul>
|
|
<p><strong>Notes</strong>: <em>삭제된 set: user_project [User, Project, 상황].
|
|
이유: User/Project/상황 전부 일반 영문 조합이라 anchor 구체성 약함.</em></p>
|
|
<h3>Frame 22 / 1171281202</h3>
|
|
<p><strong>Subject</strong>: Model에 특화된 Engn. S/W / GIS / · ArcGIS, QGIS · 천지인 / Modeler
|
|
<strong>total_unique_tokens</strong>: 43</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>gis_modeling_tools</strong>: <code>ArcGIS</code> (RN), <code>QGIS</code> (RN), <code>Infraworks</code> (RN), <code>Modeler</code> (RN)</li>
|
|
<li><strong>bim_3d_simulation_sw</strong>: <code>S/W</code> (S,M3), <code>BIM</code> (S,M2), <code>3D</code> (S,M3), <code>Model</code> (M1), <code>Engn.</code> (M1)</li>
|
|
<li><strong>visualization_products</strong>: <code>Simulation</code> (M1), <code>Sketch</code> (RN), <code>Video</code> (RN), <code>Naviswork</code> (RN)</li>
|
|
</ul>
|
|
<h3>Frame 23 / 1171281203</h3>
|
|
<p><strong>Subject</strong>: Application S/W 의 구분 / 구분 / (Commercial) Package Program / (System) Solution S/W / Customer
|
|
<strong>total_unique_tokens</strong>: 100</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>application_software</strong>: <code>S/W</code> (S,M3), <code>Application</code> (RN), <code>Program</code> (RN), <code>Commercial</code> (RN)</li>
|
|
<li><strong>client_requirement</strong>: <code>고객</code> (M1), <code>요구</code> (M2), <code>사용자</code> (M1), <code>변경</code> (M1)</li>
|
|
<li><strong>enterprise_solution</strong>: <code>ERP</code> (RN), <code>CRM</code> (RN), <code>비즈니스</code> (RN), <code>상품</code> (RN), <code>솔루션</code> (M1)</li>
|
|
</ul>
|
|
<h3>Frame 24 / 1171281204</h3>
|
|
<p><strong>Subject</strong>: Engn. S/W의 구성 과 특징 / 구분 / 상용 S/W / 3rd Party (기생 S/W) / 전문ㆍ전용 S/W
|
|
<strong>total_unique_tokens</strong>: 128</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>engineering_software_development</strong>: <code>S/W</code> (S,M3), <code>엔지니어링</code> (RN), <code>개발</code> (M2), <code>목적</code> (M1), <code>제작</code> (M1)</li>
|
|
<li><strong>bim_3d_modeling</strong>: <code>BIM</code> (S,M2), <code>3D</code> (S,M3), <code>Model</code> (M1)</li>
|
|
</ul>
|
|
<p><strong>Notes</strong>: _삭제된 set 1: commercial_sw_vendor [회사, 업체, 전문, 자체].
|
|
이유: 일반 행정어 조합. 구체 상용 S/W 업체명이 frame 에 없어 재구성 불가.</p>
|
|
<p>삭제된 set 2: vehicle_analogy [곡물, 차량, 엔진, 운반, 탱크].
|
|
이유: S/W 를 차량에 비유한 frame 고유 표현이나 MDX 매칭 anchor 로는 노이즈. 비유 표현은 anchor 범위 밖으로 보류._</p>
|
|
<h3>Frame 25 / 1171281205</h3>
|
|
<p><strong>Subject</strong>: 상용 Engn. S/W / 조사/계획/분석 / 해석 / 단가/공정 / Graphic
|
|
<strong>total_unique_tokens</strong>: 43</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>third_party_sw</strong>: <code>S/W</code> (S,M3), <code>Party</code> (RN), <code>rd</code> (RN), <code>상용</code> (M1)</li>
|
|
<li><strong>infrastructure_domains</strong>: <code>도로</code> (RN), <code>철도</code> (RN), <code>상하수도</code> (RN), <code>하천</code> (RN), <code>도시</code> (RN)</li>
|
|
</ul>
|
|
<h3>Frame 26 / 1171281206</h3>
|
|
<p><strong>Subject</strong>: 독과점 생태계 형성 / 기술예속 심화 / S/W 사용료 과다 / 존폐 위기 / 3rd Party의 개발을 유도하여
|
|
<strong>total_unique_tokens</strong>: 36</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>technology_dependency_crisis</strong>: <code>기술</code> (M3), <code>종속</code> (RN), <code>위기</code> (RN), <code>존폐</code> (RN)</li>
|
|
<li><strong>sw_cost_burden</strong>: <code>S/W</code> (S,M3), <code>사용료</code> (RN), <code>과다</code>, <code>감당</code></li>
|
|
<li><strong>monopoly_ecosystem</strong> 🔸<strong>review_needed</strong>: <code>독과점</code> (RN), <code>생태</code>, <code>심화</code></li>
|
|
</ul>
|
|
<h3>Frame 27 / 1171281208</h3>
|
|
<p><strong>Subject</strong>: 정부주도 BIM설계 전면 도입 / 생산성 향상 / 단순 반복되는 업무를 탈피하고 업무 본질에 대한 높은 이해를 바탕으로 창의적 아이디어를 발현 / 디지털 전환
|
|
<strong>total_unique_tokens</strong>: 30</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>dx_industry_value</strong>: <code>DX</code> (S,M3), <code>산업</code> (M1), <code>가치</code> (M3), <code>부가</code> (M2)</li>
|
|
<li><strong>bim_dx_adoption</strong>: <code>BIM</code> (S,M2), <code>DX</code> (S,M3), <code>도입</code> (M2), <code>전면</code> (M1)</li>
|
|
</ul>
|
|
<p><strong>Notes</strong>: <em>삭제된 set: idea_essence [본질, 아이디어, 발현].
|
|
이유: 추상어 조합. MDX 매칭 anchor 로는 구체성 약함.</em></p>
|
|
<h3>Frame 28 / 1171281209</h3>
|
|
<p><strong>Subject</strong>: 현존 상용 S/W의 현실 / 토목 전문성 부족 / 비효율성 / 실무 적용 불가능 / 토목 분야는 각 영역이 고도로 세분화되어 있음에도,
|
|
<strong>total_unique_tokens</strong>: 48</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>commercial_sw_limitations</strong>: <code>S/W</code> (S,M3), <code>소프트웨어</code> (RN), <code>상용</code> (M1), <code>현존</code> (RN), <code>한계</code></li>
|
|
<li><strong>civil_engineering_specialization</strong>: <code>토목</code> (M2), <code>분야</code> (M2), <code>전문</code> (M2), <code>실무</code>, <code>세분</code> (RN)</li>
|
|
</ul>
|
|
<p><strong>Notes</strong>: <em>삭제된 set: development_obstacles [개발, 걸림돌, 전무].
|
|
이유: 개발 일반어, 걸림돌/전무 부정어. 구체 대상 약함 (Batch 1 stagnation_obstacles 와 동일 패턴).
|
|
한계/걸림돌 맥락은 commercial_sw_limitations 의 "한계" 로 일부 반영됨.</em></p>
|
|
<h3>Frame 29 / 1171281210 🎯 <strong>TARGET</strong></h3>
|
|
<p><strong>Subject</strong>: 과정 (Process)의 혁신 / 결과 (Products)의 혁신 / --- / 개념, 도서, 행정 절차 중심 / 2D 도면, 전문가, 규정
|
|
<strong>total_unique_tokens</strong>: 115</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>process_product</strong>: <code>과정혁신</code> (S,M1), <code>Products</code> (RN)</li>
|
|
<li><strong>digital_model_shift</strong>: <code>2D</code> (S,M3), <code>3D</code> (S,M3), <code>모델</code> (M3), <code>지형도</code> (RN)</li>
|
|
<li><strong>software_solution</strong>: <code>S/W</code> (S,M3), <code>H/W</code> (S,M1), <code>BIM</code> (S,M2)</li>
|
|
</ul>
|
|
<h3>Frame 30 / 1171281211</h3>
|
|
<p><strong>Subject</strong>: 산업별 현황 / --- / | 구분 | 제조업 | 건축 | 토목 | / 개요 / · BIM
|
|
<strong>total_unique_tokens</strong>: 96</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>general_purpose_sw_limitation</strong>: <code>S/W</code> (S,M3), <code>범용</code> (RN), <code>제품</code> (RN)</li>
|
|
<li><strong>smart_factory_construction</strong>: <code>Smart</code> (RN), <code>Factory</code> (RN), <code>Construction</code> (RN), <code>시공</code> (M3), <code>건축</code></li>
|
|
<li><strong>cae_modeling_tools</strong>: <code>CAE</code> (RN), <code>모델링</code> (RN), <code>ArchiCAD</code> (RN), <code>CIM</code> (RN)</li>
|
|
</ul>
|
|
<h3>Frame 31 / 1171281212</h3>
|
|
<p><strong>Subject</strong>: 산업별 특성 과 발전방향 / --- / | 구분 | 제조업 | 건축 | 토목 | / 개요 / Product(제품) 및 부품의 생산 및 운영, 유지관리 중심
|
|
<strong>total_unique_tokens</strong>: 126</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>general_vs_specialized_sw</strong>: <code>S/W</code> (S,M3), <code>범용</code> (RN), <code>전용</code> (M1,RN), <code>제품</code> (RN)</li>
|
|
<li><strong>factory_automation</strong>: <code>Smart</code> (RN), <code>부품</code> (RN), <code>반복</code> (M1), <code>구성</code> (RN)</li>
|
|
<li><strong>construction_structure</strong>: <code>건축물</code> (RN), <code>구조체</code> (RN), <code>건물</code> (RN), <code>간섭</code> (RN)</li>
|
|
<li><strong>modeling_infra_3d</strong> 🔸<strong>review_needed</strong>: <code>Modeling</code> (M1), <code>Infra</code> (RN), <code>3D</code> (S,M3), <code>모델</code> (M3)</li>
|
|
</ul>
|
|
<h3>Frame 32 / 1171281213</h3>
|
|
<p><strong>Subject</strong>: 정책 달성 / Engn. Solution / DfMA / ---
|
|
<strong>total_unique_tokens</strong>: 73</p>
|
|
<p><strong>Anchor sets</strong>:</p>
|
|
<ul>
|
|
<li><strong>dfma_concept</strong>: <code>DfMA</code> (RN), <code>Design</code> (RN), <code>Assembly</code> (RN)</li>
|
|
<li><strong>dfma_benefits</strong>: <code>편익</code> (RN), <code>Convenient</code> (RN), <code>Fast</code> (RN), <code>Easy</code> (RN)</li>
|
|
<li><strong>factory_field_production</strong>: <code>공장</code> (RN), <code>현장</code> (M1), <code>생산</code> (M2), <code>Solution</code> (M2)</li>
|
|
<li><strong>dfma_dx_integration</strong>: <code>DfMA</code> (RN), <code>DX</code> (S,M3), <code>S/W</code> (S,M3), <code>H/W</code> (S,M1)</li>
|
|
</ul>
|
|
</body>
|
|
</html> |