[{"data":1,"prerenderedAt":85},["ShallowReactive",2],{"legacy:product\u002Fpms:en":3},{"id":4,"title":5,"description":6,"keywords":7,"author":8,"robots":9,"bodyClass":10,"image":11,"jsonld":12,"html":84},"product\u002Fpms","JEDP-PMS Project Management System - JEDP Digital Platform","JEDP-PMS Project Management System: full-cycle continuity from project intake through planning, execution and acceptance, with L1–L3 \u002F WBS tiered plans plus waterfall and agile modes, cost control, risk prevention and end-to-end delivery.","JEDP, PMS, Project Management, Digital Platform, Lang Bowan","Shenzhen Langbowan Information Technology Co., Ltd.","index, follow","page-products","https:\u002F\u002Fwww.jedp.cn\u002Fres\u002Fimages\u002Fproduct\u002Fpms-slide6.webp",[13,30,58],{"@context":14,"@type":15,"itemListElement":16},"https:\u002F\u002Fschema.org","BreadcrumbList",[17,22,26],{"@type":18,"position":19,"name":20,"item":21},"ListItem",1,"Home","https:\u002F\u002Fwww.jedp.cn\u002F",{"@type":18,"position":23,"name":24,"item":25},2,"Products","https:\u002F\u002Fwww.jedp.cn\u002Fproducts",{"@type":18,"position":27,"name":28,"item":29},3,"JEDP-PMS Project Delivery","https:\u002F\u002Fwww.jedp.cn\u002Fproduct\u002Fpms",{"@context":14,"@type":31,"@id":32,"name":28,"applicationCategory":33,"applicationSubCategory":34,"operatingSystem":35,"inLanguage":36,"description":6,"url":29,"provider":40,"isPartOf":42,"offers":44,"featureList":51},"SoftwareApplication","https:\u002F\u002Fwww.jedp.cn\u002Fproduct\u002Fpms#software","BusinessApplication","Project Management System","Web (browser access; SaaS multi-tenant, private deployment assessed by scenario)",[37,38,39],"zh-CN","zh-TW","en",{"@id":41},"https:\u002F\u002Fwww.jedp.cn\u002F#organization",{"@id":43},"https:\u002F\u002Fwww.jedp.cn\u002F#software",{"@type":45,"url":46,"availability":47,"priceSpecification":48},"Offer","https:\u002F\u002Fwww.jedp.cn\u002Fcontact?from=pms","https:\u002F\u002Fschema.org\u002FInStock",{"@type":49,"priceCurrency":50},"PriceSpecification","CNY",[52,53,54,55,56,57],"WBS & Hierarchical Planning: L1~L3 \u002F WBS decomposition, waterfall and agile work items can be combined. The progress percentage only has a fixed denominator after the baseline is frozen; Gantt charts without a baseline are not included in management standards.","Resources & Workload: Roles and named resources are layered, and load percentages and conflict warnings are visible during the planning stage. Critical role overloads should enter combination priority arbitration, rather than being discovered only after delays.","Four-stage Costing: Estimates, budgets, accounting, and final accounts are assigned to work packages; working hours, procurement, and expenses are recorded in the same account, supporting EAC\u002FETC warnings, avoiding mismatched three books and post-event explosions.","Change Control: Scope changes require approval after impact assessment (schedule\u002Fcost\u002Frisk); the pending assessment pool and CCB practices can be configured. Prevent the 'let's talk later' in emails from silently spreading.","Milestones & Acceptance: List of deliverables, acceptance criteria, and three states of pass\u002Fconditionally pass\u002Ffail; conditionally closed items come with a deadline for remaining issues and can be linked to payment triggers, reducing disputes a week before payment.","Collaboration & Document Completeness: Stakeholder communication, complete documentation, and project portfolio views provide evidence entry points for payment collection, audits, and handovers. Milestones come with an evidence package, not just a date.",{"@context":14,"@type":59,"@id":60,"mainEntity":61},"FAQPage","https:\u002F\u002Fwww.jedp.cn\u002Fproduct\u002Fpms#faq",[62,68,72,76,80],{"@type":63,"name":64,"acceptedAnswer":65},"Question","Which planning modes does JEDP-PMS support?",{"@type":66,"text":67},"Answer","Supports L1–L3 \u002F WBS levels plus waterfall \u002F agile \u002F incremental, with Gantt and board views. Plan changes must go through a change form with versions. Offline date changes that the system never updates will diverge progress and resource load.",{"@type":63,"name":69,"acceptedAnswer":70},"How is the full-cycle cost of a project calculated?",{"@type":66,"text":71},"Covers estimate, budget, actuals, close-out, and material-labor-cost rollup. The project ledger is not the general ledger; posting and invoicing still follow ERP. PMS makes project-side collection and variance visible.",{"@type":63,"name":73,"acceptedAnswer":74},"How to give early warnings for risks and changes?",{"@type":66,"text":75},"Risks go on a register with owner, escalation path, and close criteria. Change, delay, and overdue acceptance need a disposition. This is not a chat reminder. Runtime can complete reviews within that person's own permissions through the API, and does not close risks by itself.",{"@type":63,"name":77,"acceptedAnswer":78},"Can it integrate with CRM \u002F ERP \u002F OA?",{"@type":66,"text":79},"Yes. Opportunity, contract, and project IDs should align, and milestone triggers for shipment \u002F collection boundaries must be written down. Integration failures must be visible to the business—not reconciled only in IT email.",{"@type":63,"name":81,"acceptedAnswer":82},"How to manage multiple projects simultaneously?",{"@type":66,"text":83},"Portfolios, resource load, and document completeness share one view. Overload should be explicit—not every project filled independently. Acceptance and collection tick by milestone; missing documents must not fake close-out.","\u003Csection class=\"product-detail-section page-section\">\n    \u003Cdiv class=\"detail-container\">      \u003Cnav class=\"breadcrumb\" aria-label=\"Breadcrumb\">\n        \u003Ca href=\"\u002F\">Home\u003C\u002Fa>\n        \u003Cspan class=\"breadcrumb-sep\">\u002F\u003C\u002Fspan>\n        \u003Ca href=\"\u002Fproducts\">Products\u003C\u002Fa>\n        \u003Cspan class=\"breadcrumb-sep\">\u002F\u003C\u002Fspan>\n        \u003Cspan>PMS\u003C\u002Fspan>\n      \u003C\u002Fnav>\n      \u003Cdiv class=\"product-detail\">\n        \u003Cdiv class=\"detail-header\">\n          \u003Cdiv class=\"detail-icon\">\u003Ci class=\"fas fa-tasks\">\u003C\u002Fi>\u003C\u002Fdiv>\n          \u003Cdiv>\n            \u003Ch1>JEDP-PMS Project Delivery\u003C\u002Fh1>\n            \u003Cp class=\"detail-subtitle\">Let milestones carry evidence, resources highlight conflicts, and costs enter the same account — scope, schedule, cost, and acceptance can be managed, rather than wish-list-style Gantt charts.\u003C\u002Fp>\n          \u003C\u002Fdiv>\n        \u003C\u002Fdiv>\n\n        \u003Cdiv class=\"detail-content\">\n                    \u003Cdiv class=\"detail-section\">\n            \u003Ch2>Solution Positioning\u003C\u002Fh2>\n            \u003Cp class=\"detail-lead\">Payment is due and the floor still argues whether delivery 'counts as done.' JEDP-PMS covers initiate-to-accept delivery: L1–L3\u002FWBS plans, waterfall and agile practices, resource load, project cost (estimate\u002Fbudget\u002Factual\u002Ffinal) and acceptance milestones—making change control and evidence packs a process, not an email that says 'later.'\u003C\u002Fp>\n            \u003Cp class=\"detail-lead\">A Gantt without a frozen baseline does not enter acceptance. Scope changes, milestones, and resource load belong in the plan; “we'll see” in email is not a change. Works with CRM contracts, EHR time and org permissions, and expense posting.\u003C\u002Fp>\n          \u003C\u002Fdiv>\n\u003Cdiv class=\"detail-section\">\n            \u003Ch2>Where It Fits\u003C\u002Fh2>\n            \u003Cul class=\"pain-list\">\n              \u003Cli>Gantt charts look nice, but without baselines and change control, progress percentages lack a fixed denominator, and scope silently creeps until it explodes at acceptance.\u003C\u002Fli>\n              \u003Cli>Resources are assigned only to people without considering workload, key roles are overloaded with multiple projects and only revealed when delayed, and portfolio priorities cannot be arbitrated.\u003C\u002Fli>\n              \u003Cli>Labor hours, procurement, and expenses are recorded in three separate accounts that do not match, costs explode afterward, EAC\u002FETC are essentially meaningless, and finance and the project each speak their own language.\u003C\u002Fli>\n              \u003Cli>The acceptance milestone only has a date without an evidence package. Disputes over the scope and completion definition start only a week before payment, resulting in passive collection of funds.\u003C\u002Fli>\n            \u003C\u002Ful>\n          \u003C\u002Fdiv>\n          \u003Cdiv class=\"detail-section\">\n            \u003Ch2>Core Process\u003C\u002Fh2>\n            \u003Col class=\"process-flow-steps\">\n              \u003Cli>Initiation & Baseline\u003C\u002Fli>\n              \u003Cli>Plan & Resources\u003C\u002Fli>\n              \u003Cli>Execution & Timesheets\u003C\u002Fli>\n              \u003Cli>Change Control\u003C\u002Fli>\n              \u003Cli>Acceptance & Billing\u003C\u002Fli>\n            \u003C\u002Fol>\n          \u003C\u002Fdiv>\n          \u003Cdiv class=\"detail-section\">\n            \u003Ch2>Core Capabilities\u003C\u002Fh2>\n            \u003Cul class=\"capability-list\">\n              \u003Cli>\u003Cstrong>WBS & Hierarchical Planning\u003C\u002Fstrong>\u003Cspan>L1~L3 \u002F WBS decomposition, waterfall and agile work items can be combined. The progress percentage only has a fixed denominator after the baseline is frozen; Gantt charts without a baseline are not included in management standards.\u003C\u002Fspan>\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>Resources & Workload\u003C\u002Fstrong>\u003Cspan>Roles and named resources are layered, and load percentages and conflict warnings are visible during the planning stage. Critical role overloads should enter combination priority arbitration, rather than being discovered only after delays.\u003C\u002Fspan>\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>Four-stage Costing\u003C\u002Fstrong>\u003Cspan>Estimates, budgets, accounting, and final accounts are assigned to work packages; working hours, procurement, and expenses are recorded in the same account, supporting EAC\u002FETC warnings, avoiding mismatched three books and post-event explosions.\u003C\u002Fspan>\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>Change Control\u003C\u002Fstrong>\u003Cspan>Scope changes require approval after impact assessment (schedule\u002Fcost\u002Frisk); the pending assessment pool and CCB practices can be configured. Prevent the 'let's talk later' in emails from silently spreading.\u003C\u002Fspan>\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>Milestones & Acceptance\u003C\u002Fstrong>\u003Cspan>Deliverables, acceptance criteria, and the three outcomes—pass, conditional, fail—are on the milestone. Conditional close carries a due date for leftovers and can trigger payment. The project is closed only after the documents are archived.\u003C\u002Fspan>\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>Collaboration & Document Completeness\u003C\u002Fstrong>\u003Cspan>Stakeholder communication, complete documentation, and project portfolio views provide evidence entry points for payment collection, audits, and handovers. Milestones come with an evidence package, not just a date.\u003C\u002Fspan>\u003C\u002Fli>\n            \u003C\u002Ful>\n          \u003C\u002Fdiv>\n          \u003Cdiv class=\"detail-section\">\n            \u003Ch2>Scope of functions\u003C\u002Fh2>\n            \u003Cp class=\"detail-lead\">The table lists the modules under the six capabilities, and how a rule advances the next document. Approval, judgment, and write-off stay with a person.\u003C\u002Fp>\n            \u003Cdiv class=\"table-scroll\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Core Capabilities\u003C\u002Fth>\u003Cth>Modules in scope\u003C\u002Fth>\u003Cth>Rule advance\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>WBS & Hierarchical Planning\u003C\u002Ftd>\u003Ctd>L1–L3, waterfall and agile, Gantt and board\u003C\u002Ftd>\u003Ctd>Progress without a frozen baseline is not accepted.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Resources & Workload\u003C\u002Ftd>\u003Ctd>Role load and conflict warnings\u003C\u002Ftd>\u003Ctd>Role overload warns during planning.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Four-stage Costing\u003C\u002Ftd>\u003Ctd>Estimate, budget, actuals, and final account\u003C\u002Ftd>\u003Ctd>After hours and cost are collected, estimate-at-completion variance warns.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Change Control\u003C\u002Ftd>\u003Ctd>Impact assessment, change requests, and baseline comparison\u003C\u002Ftd>\u003Ctd>A change that skipped impact review cannot be executed.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Milestones & Acceptance\u003C\u002Ftd>\u003Ctd>Deliverables, three-state acceptance, archive-to-close, and collection triggers\u003C\u002Ftd>\u003Ctd>A milestone cannot close without the evidence pack. Passing it can trigger collection.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Collaboration & Document Completeness\u003C\u002Ftd>\u003Ctd>Stakeholders, task inbox, and program documents\u003C\u002Ftd>\u003Ctd>A major variance from baseline creates a risk. It does not close by itself.\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n          \u003C\u002Fdiv>\n          \u003Cdiv class=\"detail-section\">Solution Snapshot\u003C\u002Fdiv>\n          \u003Cdiv class=\"detail-section\">\n            \u003Ch2>Platform Boost\u003C\u002Fh2>\n            \u003Cdiv class=\"platform-boost\">\n              \u003Carticle>\u003Ch3>AI Agents\u003C\u002Fh3>\u003Cp>Design-time speeds up project forms and change and acceptance flows. Runtime can query and complete reviews within that person's own permissions through the API; it does not bypass change control and does not close risks automatically.\u003C\u002Fp>\u003C\u002Farticle>\n              \u003Carticle>\u003Ch3>Reports and dashboards\u003C\u002Fh3>\u003Cp>Portfolio dashboards can display combined loads, milestone health, cost deviations, and pending changes to be evaluated; the data comes from WBS \u002F work hours \u002F cost aggregation, rather than creating a separate schedule.\u003C\u002Fp>\u003C\u002Farticle>\n              \u003Carticle>\u003Ch3>Multi-language\u003C\u002Fh3>\u003Cp>The cross-national delivery team and document collaboration can be enabled for the corresponding languages; milestones, risks, and acceptance comments are readable, reducing communication loss and misunderstandings in multi-language projects.\u003C\u002Fp>\u003C\u002Farticle>\n              \u003Carticle>\u003Ch3>Multi-tenant\u003C\u002Fh3>\u003Cp>Delivery center \u002F Regional project isolated operations; the group project portfolio view is aggregated under authorization, project costs and documents are not shared between tenants, meeting multi-legal entity delivery boundaries.\u003C\u002Fp>\u003C\u002Farticle>\n            \u003C\u002Fdiv>\n          \u003C\u002Fdiv>\n                              \u003Cdiv class=\"detail-section\">\n            \u003Ch2>Boundaries & Composition\u003C\u002Fh2>\n            \u003Cp class=\"detail-lead\">PMS has WBS baselines, change entry, resource load, and milestone evidence packages; contracts and invoicing can be connected with CRM\u002Ffinance, and work hours and organization can be reused with EHR. It addresses controlled delivery, rather than replacing professional design tools.\u003C\u002Fp>\n            \u003Cp class=\"detail-lead\">Touchpoints: CRM for opportunity and contract kickoff, EHR for time and assignment, finance for expense posting. Set the write-back direction for contract, time, and cost before building the portfolio board.\u003C\u002Fp>\n          \u003C\u002Fdiv>\n          \u003C!-- product-depth:BEGIN -->\n\u003Cdiv class=\"detail-section\">\n\n            \n            \n            \u003Ch2>Typical breakpoints\u003C\u002Fh2>\n\u003Cdiv class=\"table-scroll\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Breakpoint\u003C\u002Fth>\u003Cth>Common cause\u003C\u002Fth>\u003Cth>Control lever\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>Project progress relies on weekly reports\u003C\u002Ftd>\u003Ctd>WBS is not linked to the work report\u003C\u002Ftd>\u003Ctd>Task—Report—Progress Percentage Same Source\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Accepted but documentation is incomplete\u003C\u002Ftd>\u003Ctd>Deliverables are not set as required\u003C\u002Ftd>\u003Ctd>Deliverable Template + Completeness Check\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Disconnection between budget and procurement\u003C\u002Ftd>\u003Ctd>Purchase request for unlisted items\u003C\u002Ftd>\u003Ctd>Project number runs through ERP PO\u002FMO\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Execute changes without evaluation\u003C\u002Ftd>\u003Ctd>Plan change without approval\u003C\u002Ftd>\u003Ctd>Change Order + Baseline Comparison\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Risk register zombification\u003C\u002Ftd>\u003Ctd>No person in charge and early warning\u003C\u002Ftd>\u003Ctd>Risk Rules + Message Push\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Difficulties in reconciling multiple projects in the contract\u003C\u002Ftd>\u003Ctd>Contract—Project Association Missing\u003C\u002Ftd>\u003Ctd>One Contract Multiple Projects Mapping Table\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Work hours reporting lag\u003C\u002Ftd>\u003Ctd>Mobile work reporting not enabled\u003C\u002Ftd>\u003Ctd>Task Reminder + Work Hours Review Chain\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n            \u003Ch2>Responsibility and Integration\u003C\u002Fh2>\n            \u003Cp class=\"detail-lead\">\u003Cstrong>Primary Responsibility:\u003C\u002Fstrong>PMS has project planning, WBS execution, deliverables, time reporting, issues\u002Frisks, and acceptance\u002Fclosure evidence; sales contracts and receivables are mainly based on CRM\u002FERP, and PMS consumes and writes back project dimensions.\u003C\u002Fp>\n            \u003Cp class=\"detail-lead\">\u003Cstrong>Integration Direction (Typical):\u003C\u002Fstrong>CRM → Opportunities\u002FContracts; ERP ←→ Purchase Requisitions\u002FBOM\u002FPO\u002FMO\u002FShipment\u002FAccounting\u002FReceivables; OA → Approvals (optional); EHR ← Project Work Hours (optional). For manufacturing delivery projects, the responsibility for status updates from BOM issuance to production storage should be clearly defined.\u003C\u002Fp>\n            \u003Ch2>Promote phased implementation and acceptance\u003C\u002Fh2>\n            \u003Cul class=\"accept-list\">\n              \u003Cli>\u003Cstrong>Phase One (Templates and Plans)\u003C\u002Fstrong>: Project templates, L1\u002FL2 WBS, stakeholders and communication mechanisms; plan release and change tracking\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>Phase Two (Execution and Cost)\u003C\u002Fstrong>: Work reporting\u002Fdeliverables\u002Fissues and risks; budget and ERP procurement\u002Flabor cost reconciliation\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>Phase Three (Finishing and Collection)\u003C\u002Fstrong>: Acceptance—Archiving—Payment Closed Loop; Program View and Multi-Project Resource Load Demonstration\u003C\u002Fli>\n              \u003Cli>The baseline plan and change traceability can be demonstrated, and major deviations trigger risk warnings\u003C\u002Fli>\n              \u003Cli>Project cost details can be drilled down to ERP procurement\u002Flabor sources (according to the integration scope)\u003C\u002Fli>\n              \u003Cli>Project communication records and risk\u002Fissue closure rates can be counted, and the upgrade path and responsible person can be demonstrated.\u003C\u002Fli>\n            \u003C\u002Ful>\n            \u003Ch2>When not to apply\u003C\u002Fh2>\n            \u003Cul class=\"pain-list\">\n              \u003Cli>Use PMS to replace MES for shop floor execution — the manufacturing site is still on MES, PMS manages project milestones\u003C\u002Fli>\n              \u003Cli>No WBS discipline, only milestone PPT — tasks should be defined first before discussing intelligent early warning\u003C\u002Fli>\n              \u003Cli>Refusing ERP integration but wanting precise project costing — material and labor costs cannot be reliably aggregated\u003C\u002Fli>\n              \u003Cli>Mixing Agile and Waterfall approaches without rules — a planning model and change strategy should be selected at the start\u003C\u002Fli>\n            \u003C\u002Ful>\n          \u003C\u002Fdiv>\n          \n          \n          \u003C!-- product-depth:END -->\n\n\u003Cdiv class=\"detail-section\">\n            \u003Ch2>Related Practices\u003C\u002Fh2>\n            \u003Cp class=\"detail-lead\">Project-based practices focus mainly on plan scenarios and insight criteria; after having an independent acceptance package, they are then upgraded to named cases.\u003C\u002Fp>\n            \u003Cul class=\"related-cases\">\n              \u003Cli>Project Delivery Plan Scenario: Milestones and Cost Control\u003C\u002Fli>\n              \u003Cli>Progress % you cannot trust—without a frozen WBS baseline and change intake, percentage is mood\u003C\u002Fli>\n              \u003Cli>Resource: Project Delivery Control Self-Assessment\u003C\u002Fli>\n            \u003C\u002Ful>\n          \u003C\u002Fdiv>\n                                                                                                                                            \u003C!-- related-insights:BEGIN -->\n          \u003Cdiv class=\"detail-section\" id=\"related-insights\">\n            \u003Ch2>Related insights\u003C\u002Fh2>\n            \u003Cul class=\"related-cases\">\n              \u003Cli>Acceptance scramble one week before payment? A milestone without an evidence pack is just a dunning calendar\u003C\u002Fli>\n              \u003Cli>Four projects all “fully staffed”? If the load board cannot show conflicts, overtime becomes the default fix\u003C\u002Fli>\n              \u003Cli>Overrun discovered only at close—hours, purchases, and expenses must be visible same-day under one project ID\u003C\u002Fli>\n            \u003C\u002Ful>\n            \u003Cp class=\"related-more\">\u003Ca href=\"\u002Finsights\">Browse all insights\u003C\u002Fa> · \u003Ca href=\"\u002Fresources?from=pms#selftest\">Take an online self-test\u003C\u002Fa> · \u003Ca href=\"\u002Fresources?from=pms#kits\">Download kits\u003C\u002Fa> · \u003Ca href=\"\u002Fresources?from=pms#demo\">Book a demo\u003C\u002Fa>\u003C\u002Fp>\n          \u003C\u002Fdiv>\n          \u003C!-- related-insights:END -->\n          \u003Cdiv class=\"product-detail-cta scroll-reveal\">\n            \u003Ca href=\"\u002Fproducts\" class=\"btn btn-outline\">Back to product solutions\u003C\u002Fa>\n            \u003Ca href=\"\u002Fresources?from=pms#selftest\" class=\"btn btn-outline\">Take a self-test\u003C\u002Fa>\n            \u003Ca href=\"\u002Fresources?from=pms#kits\" class=\"btn btn-ghost\">Download kits\u003C\u002Fa>\n            \u003Ca href=\"\u002Fresources?from=pms#demo\" class=\"btn btn-ghost\">Book a demo\u003C\u002Fa>\n            \u003Ca href=\"\u002Fcontact?from=pms\" class=\"btn\">Get a demo\u003C\u002Fa>\n          \u003C\u002Fdiv>\n\u003C\u002Fdiv>\n      \u003C\u002Fdiv>\n    \u003C\u002Fdiv>\n  \u003C\u002Fsection>\n\n  \u003C!-- GEO:faq-visible:BEGIN · 由 scripts\u002Finject_geo.py 生成，请勿手改 -->\n  \u003Csection class=\"contact-faq page-section\" id=\"faq\">\n    \u003Ch2 class=\"section-title\">FAQ\u003C\u002Fh2>\n    \u003Cp class=\"section-subtitle\">For common questions about the capabilities on this page, take a look here first; if you still have questions, you can contact us.\u003C\u002Fp>\n    \u003Cdiv class=\"faq-list\">\n        \u003Cdetails class=\"faq-item\" open>\n          \u003Csummary>Which planning modes does JEDP-PMS support?\u003C\u002Fsummary>\n          \u003Cp>Supports L1–L3 \u002F WBS levels plus waterfall \u002F agile \u002F incremental, with Gantt and board views. Plan changes must go through a change form with versions. Offline date changes that the system never updates will diverge progress and resource load.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>How is the full-cycle cost of a project calculated?\u003C\u002Fsummary>\n          \u003Cp>Covers estimate, budget, actuals, close-out, and material-labor-cost rollup. The project ledger is not the general ledger; posting and invoicing still follow ERP. PMS makes project-side collection and variance visible.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>How to give early warnings for risks and changes?\u003C\u002Fsummary>\n          \u003Cp>Risks go on a register with owner, escalation path, and close criteria. Change, delay, and overdue acceptance need a disposition. This is not a chat reminder. Runtime can complete reviews within that person's own permissions through the API, and does not close risks by itself.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>Can it integrate with CRM \u002F ERP \u002F OA?\u003C\u002Fsummary>\n          \u003Cp>Yes. Opportunity, contract, and project IDs should align, and milestone triggers for shipment \u002F collection boundaries must be written down. Integration failures must be visible to the business—not reconciled only in IT email.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>How to manage multiple projects simultaneously?\u003C\u002Fsummary>\n          \u003Cp>Portfolios, resource load, and document completeness share one view. Overload should be explicit—not every project filled independently. Acceptance and collection tick by milestone; missing documents must not fake close-out.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n    \u003C\u002Fdiv>\n  \u003C\u002Fsection>\n  \u003C!-- GEO:faq-visible:END -->\n\n  \n  \n\n  \n  \n  \n  \u003C!-- GEO:software-app:BEGIN · 由 scripts\u002Finject_geo.py 生成，请勿手改 -->\n  \n  \u003C!-- GEO:software-app:END -->\n  \u003C!-- GEO:faq:BEGIN · 由 scripts\u002Finject_geo.py 生成，请勿手改 -->\n  \n  \u003C!-- GEO:faq:END -->",1793937990189]