A method of caching a file or a file fragment, wherein a File Management Services, FMS, system provides a channel for file data connection that is separate from its Product Lifecycle Management, PLM, connection by requiring a file ticket to be passed between the PLM system and the FMS system, where the file is in a form of a plurality of file fragments - file respectively file fragment in the following denoted by file only -, to improve file transfer performance, comprising the steps of: A requesting by a user a file from a client interface in a FMS network system, wherein the file - supports product visualization and design and - is segmented into logical areas and only some of the logical areas are required for any given operation. B receiving said request via said channel by a business logic file server and validating whether the user has accesses in case the user has no access, exiting the FMS network system C in case the user has access, generating the file ticket and sending said file ticket to a FMS client cache, wherein the FMS client cache is a shared cache so that it can be accessed by other client programs during the method execution; D checking whether the file is in the FMS client cache; if yes, displaying that file on the client interface, receiving the file ticket by a FMS cache server, validating the file ticket and checking if the file is in the FMS cache server, wherein the FMS cache server is a private cache in that there are not direct clients said FMS cache server; if yes, sending the requested file to the FMS client cache for storage in said FMS client cache, otherwise querying a volume server by validating the file ticket and retrieving the file from the volume server, wherein the volume server is configured for capturing and serving files from reliable PLM data storage sources, and streaming said file through the FMS cache server to the FMS client cache for storage (430, 420) in the FMS cache server and the FMS client cache; E when the file has been streamed to the FMS client cache, returning the file to the client interface for display. A requesting by a user a file from a client interface in a FMS network system, wherein the file - supports product visualization and design and - is segmented into logical areas and only some of the logical areas are required for any given operation. - supports product visualization and design and - is segmented into logical areas and only some of the logical areas are required for any given operation. B receiving said request via said channel by a business logic file server and validating whether the user has accesses in case the user has no access, exiting the FMS network system C in case the user has access, generating the file ticket and sending said file ticket to a FMS client cache, wherein the FMS client cache is a shared cache so that it can be accessed by other client programs during the method execution; D checking whether the file is in the FMS client cache; if yes, displaying that file on the client interface, receiving the file ticket by a FMS cache server, validating the file ticket and checking if the file is in the FMS cache server, wherein the FMS cache server is a private cache in that there are not direct clients said FMS cache server; if yes, sending the requested file to the FMS client cache for storage in said FMS client cache, otherwise querying a volume server by validating the file ticket and retrieving the file from the volume server, wherein the volume server is configured for capturing and serving files from reliable PLM data storage sources, and streaming said file through the FMS cache server to the FMS client cache for storage (430, 420) in the FMS cache server and the FMS client cache; E when the file has been streamed to the FMS client cache, returning the file to the client interface for display.