When scoping and implementing a digital twin, how do you decide what to include and where to stop? How can you architect a digital twin to support changing needs and future applications while keeping project costs and timelines in check? Answering these questions requires taking a relational view that cuts across traditional disciplinary boundaries. This presentation will start with a simple example and build out to a systems-thinking approach to digital twins.