[{"data":1,"prerenderedAt":296},["ShallowReactive",2],{"services-index-ja":3},[4,69,103,169,229],{"id":5,"title":6,"author":7,"body":8,"category":43,"cover":44,"description":47,"draft":48,"extension":49,"gallery":50,"icon":51,"locale":52,"meta":53,"navigation":54,"path":55,"primaryCta":56,"publishedAt":57,"readingTime":58,"related":59,"seo":61,"serviceType":64,"stem":65,"tags":66,"updatedAt":57,"__hash__":68},"services\u002Fservices\u002Fja\u002Fai-product-strategy.md","AI 製品戦略","YHTEK",{"type":9,"value":10,"toc":38},"minimark",[11,15,19],[12,13,14],"p",{},"曖昧な事業構想を、設計・構築・導入できる製品の方向へと整理します。",[16,17,18],"h2",{"id":18},"範囲",[20,21,22,26,29,32,35],"ul",{},[23,24,25],"li",{},"製品の位置づけ",[23,27,28],{},"MVP の範囲",[23,30,31],{},"AI 活用場面の検討",[23,33,34],{},"コンテンツとデータの準備状況",[23,36,37],{},"提供ロードマップ",{"title":39,"searchDepth":40,"depth":40,"links":41},"",2,[42],{"id":18,"depth":40,"text":18},"サービス",{"src":45,"alt":46},"\u002Fimages\u002Fcontent\u002Fservice-ai-strategy.svg","AI 製品戦略の概念図","開発に着手する前に、製品の方向、MVP の範囲、AI の用途、提供計画を定義します。",false,"md",[],"AI","ja",{},true,"\u002Fservices\u002Fja\u002Fai-product-strategy","プロジェクトのご相談","2026-07-10",3,[60],"\u002Fja\u002Fprojects\u002Fai-product-studio-platform",{"title":62,"description":63},"AI 製品戦略サービス","構築前に製品、AI 活用プロセス、MVP の計画を定義します。","戦略","services\u002Fja\u002Fai-product-strategy",[64,51,67],"MVP","tt4X5LDNGKyT0Prr6rlQWmHzXw-1yQXRxqCLhayuFtg",{"id":70,"title":71,"author":7,"body":72,"category":43,"cover":82,"description":85,"draft":48,"extension":49,"gallery":86,"icon":87,"locale":52,"meta":88,"navigation":54,"path":89,"primaryCta":90,"publishedAt":57,"readingTime":58,"related":91,"seo":93,"serviceType":96,"stem":97,"tags":98,"updatedAt":57,"__hash__":102},"services\u002Fservices\u002Fja\u002Fcloud-run-deployment.md","Cloud Run デプロイ",{"type":9,"value":73,"toc":80},[74,77],[12,75,76],{},"クラウドへの導入は後付けではなく、製品の提供プロセスの一部です。",[12,78,79],{},"YHTEK は Docker、CI\u002FCD、環境設定、Cloud Run の公開前確認を支援します。",{"title":39,"searchDepth":40,"depth":40,"links":81},[],{"src":83,"alt":84},"\u002Fimages\u002Fcontent\u002Fservice-cloud-run.svg","Cloud Run デプロイの概念図","Docker、CI\u002FCD、GCP Cloud Run を使い、Nuxt・NestJS・API 連携製品をパッケージ化・運用します。",[],"CL",{},"\u002Fservices\u002Fja\u002Fcloud-run-deployment","デプロイを相談",[92],"\u002Fja\u002Fprojects\u002Fmanufacturing-workflow-system",{"title":94,"description":95},"Cloud Run デプロイサービス","Google Cloud Run 上でウェブ製品をデプロイ・運用します。","エンジニアリング","services\u002Fja\u002Fcloud-run-deployment",[99,100,101],"Cloud Run","Docker","CI\u002FCD","m03wb8hVgIeSiOVbKPcsDKGdpRfgX_LDfDwF_c6H9HE",{"id":104,"title":105,"author":106,"body":107,"category":153,"cover":154,"description":155,"draft":48,"extension":49,"gallery":156,"icon":154,"locale":52,"meta":157,"navigation":54,"path":158,"primaryCta":154,"publishedAt":154,"readingTime":154,"related":159,"seo":160,"serviceType":161,"stem":162,"tags":163,"updatedAt":154,"__hash__":168},"services\u002Fservices\u002Fja\u002Fproduct-development.md","製品企画と統合開発","穎鋐科技",{"type":9,"value":108,"toc":148},[109,112,115,118,135,138,141],[16,110,111],{"id":111},"このサービスが適する段階",[12,113,114],{},"製品のアイデアや明確な産業課題があり、仕様の定義、実現性の確認、技術分野の連携が必要な段階に適しています。",[16,116,117],{"id":117},"支援内容",[20,119,120,123,126,129,132],{},[23,121,122],{},"利用場面、要件、製品仕様の整理。",[23,124,125],{},"各技術分野のインターフェースと責任範囲の計画。",[23,127,128],{},"IoT 機器、アプリ、ウェブ、バックエンドの開発・統合計画。",[23,130,131],{},"試作、試験条件、設計検証。",[23,133,134],{},"コスト、日程、製造方式、量産リスクの評価。",[16,136,137],{"id":137},"進め方",[12,139,140],{},"製品の成熟度に応じて段階的に進めます。設計と試作の前に要件・検収条件を確認し、各段階で確認できる成果を次の判断につなげます。",[12,142,143],{},[144,145,147],"a",{"href":146},"\u002Fja\u002Fcontact","製品のアイデアを相談する",{"title":39,"searchDepth":40,"depth":40,"links":149},[150,151,152],{"id":111,"depth":40,"text":111},{"id":117,"depth":40,"text":117},{"id":137,"depth":40,"text":137},"製品開発",null,"アイデア、利用場面、製品仕様から始め、各技術を統合して検証可能な試作品を構築します。",[],{},"\u002Fservices\u002Fja\u002Fproduct-development",[],{"title":105,"description":155},"統合開発","services\u002Fja\u002Fproduct-development",[164,165,166,167],"ハードウェア","ソフトウェア","ファームウェア","機構","UcGJgMbKj-0eIsHMJIyu57mfuxANnyXznG58OjaW2Wo",{"id":170,"title":171,"author":106,"body":172,"category":214,"cover":154,"description":215,"draft":48,"extension":49,"gallery":216,"icon":154,"locale":52,"meta":217,"navigation":54,"path":218,"primaryCta":154,"publishedAt":154,"readingTime":154,"related":219,"seo":220,"serviceType":221,"stem":222,"tags":223,"updatedAt":154,"__hash__":228},"services\u002Fservices\u002Fja\u002Fproduction-market.md","量産・市場導入計画",{"type":9,"value":173,"toc":210},[174,177,180,182,202,205],[16,175,176],{"id":176},"研究開発から次の段階へ",[12,178,179],{},"試作の後には生産仕様、製造連携、試験工程、納品方法の計画が必要です。機能とコストも市場・利用者のニーズに照らして確認します。",[16,181,117],{"id":117},[20,183,184,187,190,193,196,199],{},[23,185,186],{},"生産仕様、製造方式、調達連携の計画。",[23,188,189],{},"試験条件、品質要件、納品書類の整理。",[23,191,192],{},"生産品質と関連設備を計画し、製品試験と製造要件をつなぎます。",[23,194,195],{},"PCB 試験の要件整理と試験設備開発範囲の計画。",[23,197,198],{},"コスト、保守、将来の改版の検討。",[23,200,201],{},"利用場面、製品の位置づけ、販売導入の計画。",[12,203,204],{},"製造リソース、役割分担、納品範囲、日程は要件整理後に確認します。",[12,206,207],{},[144,208,209],{"href":146},"製品の次の一歩を計画する",{"title":39,"searchDepth":40,"depth":40,"links":211},[212,213],{"id":176,"depth":40,"text":176},{"id":117,"depth":40,"text":117},"製品化","試作品を製造・試験・品質要件につなぎ、コスト、利用者、販売場面から製品導入を計画します。",[],{},"\u002Fservices\u002Fja\u002Fproduction-market",[],{"title":171,"description":215},"生産と市場","services\u002Fja\u002Fproduction-market",[224,225,226,227],"量産","試験","コスト","販売導入","WTuH3RC3NGtcd8IXv6lPEmofNhNHQWf8PWNglu9tH5E",{"id":230,"title":231,"author":106,"body":232,"category":280,"cover":154,"description":281,"draft":48,"extension":49,"gallery":282,"icon":154,"locale":52,"meta":283,"navigation":54,"path":284,"primaryCta":154,"publishedAt":154,"readingTime":154,"related":285,"seo":286,"serviceType":289,"stem":290,"tags":291,"updatedAt":154,"__hash__":295},"services\u002Fservices\u002Fja\u002Fengineering-debug.md","開発が行き詰まっていますか？システム不具合の原因が見つかりませんか？",{"type":9,"value":233,"toc":275},[234,237,242,245,248,251,265,268,271],[12,235,236],{},"問題を一人で抱える必要はありません。",[12,238,239],{},[144,240,241],{"href":146},"技術課題を相談する",[16,243,244],{"id":244},"まず問題を整理する",[12,246,247],{},"異常は複数のサブシステムにまたがることがあります。発生条件、バージョン、測定記録、操作手順を整理し、検証する仮説を見つけます。",[16,249,250],{"id":250},"一緒に検討できる課題",[20,252,253,256,259,262],{},[23,254,255],{},"防水製品の使用環境、密封構造、試験条件の検討。",[23,257,258],{},"負圧製品のセンシング、制御、ファームウェア、機構の統合課題。",[23,260,261],{},"システム通信、タイミング、状態、機器間の相互作用。",[23,263,264],{},"試作と量産の設計差異、試験上の課題。",[16,266,267],{"id":267},"成果物",[12,269,270],{},"委託範囲に応じて再現記録、測定・分析、改善提案、検証結果を提供します。防水等級、性能、認証要件は仕様と正式な試験に基づく確認が必要です。",[12,272,273],{},[144,274,241],{"href":146},{"title":39,"searchDepth":40,"depth":40,"links":276},[277,278,279],{"id":244,"depth":40,"text":244},{"id":250,"depth":40,"text":250},{"id":267,"depth":40,"text":267},"技術課題の解決","異常現象、測定結果、システム間の分析を通じて課題を整理し、検証可能な改善の方向を一緒に見つけます。",[],{},"\u002Fservices\u002Fja\u002Fengineering-debug",[],{"title":287,"description":288},"技術レビューとシステム不具合解析｜YHTEK","各技術領域の相互作用を整理し、異常現象と測定結果から検証可能な改善方向を見つけます。","不具合解析と検証","services\u002Fja\u002Fengineering-debug",[292,293,294],"不具合分析","防水設計","負圧制御","tFGbq2b0ww3CJsCB4vNuOMWUGhpJJQLNnNuML4PjwQA",1791799799924]