Pipeline Development

NCP-OUSD · 28 questions

• Communications converts council-chamber OpenUSD to glTF for public 3D web pages. What should the pipeline emphasize?
• Transit publishes station twins to glTF for partner navigation apps. Which pipeline practice best protects quality?
• Parks contractors receive glTF playground packages derived from the master OpenUSD. What fidelity concern should the delivery pipeline address?
• A civic museum converts exhibit OpenUSD to glTF for kiosk viewers. Which conversion practice best keeps visual fidelity?
• A city digital-twin program needs shared OpenUSD packaging rules across departments. What should pipeline documentation emphasize?
• Transit authors package conventions for station platforms. Which asset-structure documentation topic is most useful for teams?
• Parks prepares collaborative plaza packages for multiple vendors. What should asset structure guidelines capture?
• A housing authority wants maintainable OpenUSD unit assemblies across campuses. What should structure guidelines define?
• Airport twin architects choose encodings for policy layers versus heavy airside crates. Which trade-off guidance fits?
• Transit CI reviews station overlays and ships packages to field viewers. How should USDA and USDC be matched to stages?
• County archivists must explain OpenUSD delivery encoding to stakeholders. Which articulation is accurate?
• School facilities must edit classroom renovations in a DCC and return them to the campus OpenUSD twin. What pipeline capability is required?
• Transit artists edit platform furniture in a DCC and must return clean packages to USD. What should the round-trip design prioritize?
• Parks softscape meshes break references after repeated DCC round-trips. What stability practice should the pipeline enforce?
• Airport lookdev round-trips materials between a DCC and OpenUSD. What should documented pipeline rules clarify?
• Housing unit packages use URI-style asset identifiers that must resolve in every city OpenUSD app. What pipeline integration fits?
• Transit stores authoritative asset IDs that must map to on-prem package locations at runtime. How should the pipeline manage those paths?
• Public-works shares curb libraries across lab, staging, and production roots. Which resolver approach supports that?
• A city pipeline must stamp department owner and review state on OpenUSD packages. How should that information be represented?
• Emergency management wants incident overlays to carry trackable case identifiers through the twin pipeline. What should the package store?
• Permitting must keep hearing-case numbers attached to exhibit layers without inventing new geometry schemas. Where should those process identifiers live?
• Before a city digital twin publishes, CI must catch broken references. Which pipeline gate fits Domain 7 path hygiene?
• Transit packaging rejects platform packages that only work on one artist's machine. Which path form should the checker refuse?
• Parks packaging must keep fountain texture references portable across workstations. What should the validator enforce?
• An airport publish gate must fail bad twin packages early. Which failure condition belongs in that quality gate?
• Facilities brings city custom schemas into a modeling DCC for campus twins. What pipeline work is required?
• Transit needs specialized platform model kinds visible inside the modeling DCC after import. What should engineers extend?
• Parks artists expect purpose tokens and materials to survive DCC import for exhibit packages. What should the importer do?