Digital file structure for garment production

Abstract

The present invention provides a method and system for generating a base digital file of a garment that can be used in garment production. For example, the system can receive a library from a data source and generate a base digital file of a garment. The base digital file can include: a garment identifier; a piece object associated with the piece identifier and a reference to garment information in the library; and a seam object representing a seam forming a portion of the garment.

Description

Background Art

[0001] Users may wish to use standards to effectively communicate ideas or instructions in a manner that is easily understood by the recipient. For example, a clothing designer may use specific terminology, drawings, or labels to specify how an article of clothing should be manufactured. However, in many clothing design situations, individual designers may use different wording, formats, or methods to convey instructions, forcing manufacturers to often request clarification of the designer's instructions in order to create a document containing the content and / or format required for the manufacturer to actually produce the garment. Providing clarification for each set of instructions for each article of clothing is very expensive in terms of labor, time, and cost, and leads to increasing complexity and potential scale issues as the size and variety of clothing production lines increase. BRIEF DESCRIPTION OF THE DRAWINGS

[0002] The embodiments of various inventive features will now be described with reference to the following drawings. Throughout the drawings, reference numerals may be reused to indicate the corresponding relationship between referenced elements. The accompanying drawings are provided to illustrate the exemplary embodiments described herein and are not intended to limit the scope of the present disclosure.

[0003] Figure 1 is an illustrative networking environment and system architecture for a digital filing system that may be used in connection with apparel production, according to some embodiments.

[0004] Figure 2 is a data flow diagram depicting an exemplary method for generating a digital filing system for base digital files and customized digital files for use in garment production, according to some embodiments.

[0005] Figure 3 is a flow chart depicting an exemplary method of generating base digital files and customized digital files for garment production, according to some embodiments.

[0006] Figure 4 is a visual representation of components of an exemplary digital file utilized by a digital filing system according to some embodiments.

[0007] Figure 5 is a visual representation depicting an exemplary configuration of garment components in a digital documentation system according to some embodiments.

[0008] Figure 6 is example text for an example garment object utilized in a digital filing system according to some embodiments.

[0009] Figure 7 is exemplary text for an exemplary garment piece object utilized in a digital filing system according to some embodiments.

[0010] Figure 8is example text of an example seam object utilized in a digital filing system according to some embodiments.

[0011] Figure 9 is a visual representation of a garment piece utilized in a digital filing system according to one embodiment.

[0012] Figure 10 is an illustration of an exemplary computing system configured to perform the digital file generation and other methods described herein. DETAILED DESCRIPTION

[0013] Aspects of the present disclosure relate to providing complete manufacturing instructions for any kind of garment via digital files using a digital filing system. Providing digital files for manufacturing a garment can be accomplished in different ways, such as using different algorithms and / or different methods, as will be further described below.

[0014] As will be described herein, a digital filing system can receive a set of information, a document, or a selection of a first size for an item or garment, generate a digital file specific to the item at the first size, and store the digital file. The digital filing system can then receive user input, including personal body measurements or a selection of a standard size for a garment, and generate a customized digital file by applying the personal body measurements or standard size grading criteria to the digital file. As will be discussed further below, the digital filing system can partition the methods and processes among various modules or system components.

[0015] The task of generating instructions for manufacturing a garment according to previously used methods typically involves generating a technical package, where the technical package typically includes a specification sheet for the base size of the garment and a grading sheet for converting the base size to any other standard sizes (e.g., small, medium, and large). Although some automation is accomplished where designers share files (e.g., digital exchange files), there is no semantics associated with the data in the file to help interpret the coordinates in the file. Therefore, if two different manufacturers each use different software (e.g., LibreCAD, AutoCAD) to analyze the received file, the two manufacturers may interpret the same technical package differently. Furthermore, existing uses of technical packages are unreliable when making custom garments because no set of rules exists when making custom garments.

[0016] Furthermore, for manufacturers and designers, ensuring each tech pack is correctly understood can be both arduous and time-consuming, especially when manufacturers need to repeatedly request clarification for each specific article of clothing. Typically, designers provide manufacturers with detailed instructions for producing an article of clothing. However, when conveying instructions in a traditional tech pack, designers may use informal drawings, sketches, or handwriting. Furthermore, while some designers may use computers to help generate tech packs, designers often submit informal instructions scribbled with pen and paper. Consequently, due to a lack of understanding or insufficient detail, the designer's intent may not be effectively conveyed to the manufacturer. Furthermore, in many cases, traditional tech packs do not allow manufacturers to easily measure variations in the article of clothing if it deviates from the dimensions originally envisioned in the tech pack. Consequently, manufacturers or designers often have to manually review and add instructions when manufacturing the article of clothing.

[0017] The digital file methods and systems disclosed herein address these issues, allowing the system to generate digital files that automatically incorporate instructions in a standardized digital format that can be interpreted by both human readers and computers. For example, in some embodiments described herein, the digital file system can receive user input including information associated with a first size of an item, generate a digital file for the item at the first size, store the digital file, receive personal body measurements or standard size selections, and generate a customized digital file by applying the personal body measurements or standard size grading to various parameters within the digital file in a manner that creates a customized result that does not rely on human guesswork.

[0018] There are many technical and practical benefits to utilizing the digital file system and method described in this article. By grouping various instructions into different specification objects within a digital file, the specification objects can handle different parts of a garment's construction and can be spliced together to support different use cases. In addition, by using discrete objects to describe different instructions, additional changes can be easily and efficiently added to the digital file based on the requirements of a specific garment article. In contrast, other methods may require manual generation of a technical package for each possible feature combination in a garment. By improving the ability to generate standardized digital files with instructions, the technology described herein significantly reduces the inefficiency of garment construction for various styles, enabling garments to be produced on a large scale with fewer steps.

[0019] Figure 1is an exemplary networking environment and system architecture for a digital file system according to some embodiments. The exemplary environment includes a user system 110, a manufacturer system 114, a designer system 116, a retail system 119, a network 117, and a digital file system 120. In some embodiments, the user system 110 may be a computer, a handheld mobile computing device, or other computing system. In some embodiments, the user system 110 may include a processor configured to execute instructions to generate a user interface and transmit user input to the digital file system 120.

[0020] In some embodiments, designer system 116 may be a computer, handheld mobile computing device, or other computing system used by a garment designer to submit information about garments to digital file system 120. In some embodiments, designer system 116 may include a data storage device 118 configured to store a plurality of garment information files as data entries.

[0021] In some embodiments, the retail system 119 may be connected to or in communication with a data storage device 121 that stores item information about a plurality of items (such as items listed in an electronic catalog that are available for browsing and / or purchase via the retail system or service). The item data stored in the data storage device 121 may include any information associated with each item. For example, the item data may include, but is not limited to, price, availability, name, item identifier, item feedback (e.g., user reviews, ratings, etc.), item image, item description, item attributes, keywords associated with the item, and the like. In some embodiments, the data storage device 121 may store digital content items (e.g., audiobooks, e-books, music, movies, etc.). In some embodiments, the retail system 119 may also be connected to or in communication with a user data storage device (not shown) that stores user data associated with users of the retail service, such as purchase history, browsing history, item reviews and ratings, personal information, user preferences, location information, physical measurements, activity information, and the like.

[0022] In some embodiments, the manufacturer system 114 can be a computer, handheld mobile computing device, or other computing system used by the manufacturer to receive digital files from the digital file system 120. The manufacturer system 114 can then be used by manufacturing personnel and / or machines to produce garments based on the digital files. In some embodiments, the manufacturer system 114 can include a data storage device 115 configured to store digital files as entries.

[0023] It should be understood that any number of user systems 110, designer systems 116, retail systems 119, and manufacturer systems 114 can be utilized in the digital file system environment. In some embodiments, user systems 110, manufacturer systems 114, designer systems 116, retail systems 119, and digital file system 120 can communicate with each other via a network 117, such as the Internet. As will be discussed in greater detail, in some embodiments, digital file system 120 can communicate with user systems 110, designer systems 116, and manufacturer systems 114 to generate and transmit one or more digital files. In some embodiments, digital file system 120 can include a base digital file module 130, a custom instruction module 140, a custom digital file module 150, and a digital file data storage device 180.

[0024] In some embodiments, the digital file system 120 can utilize a base digital file module 130 to generate a base digital file for a particular garment. As will be discussed below, in some embodiments, the base digital file module 130 can receive information from the designer system 116 regarding the creation of a base size article of clothing. In some embodiments, the base digital file module can receive the information, convert or otherwise process the information, and divide the information into components of a base digital file.

[0025] In some embodiments, customization instruction module 140 can receive user input from user system 110. For example, in some embodiments, a user can interact with a user interface associated with retail system 119 to browse an electronic catalog of items and select an option to purchase clothing in standard sizes. In some embodiments, the user can enter customized body measurements via the user interface, which can be stored in data storage device 121. Retail system 119 can then forward the user's customized body measurements to digital file system 120.

[0026] In some embodiments, the digital file system 120 may utilize a customized digital file module 150 to generate a customized digital file. In some embodiments, the customized digital file module 150 may generate a customized digital file for an article of clothing based, at least in part, on the received customization instructions and a base digital file for a particular article of clothing. For example, the digital file system 120 may receive a request to purchase a first shirt in a standard large size, and the customized digital file module 150 may retrieve the base digital file corresponding to the first shirt from the digital file data storage 180 and, assuming the base digital file is not a large size for the first shirt, apply a grading scale to convert the first shirt to an appropriate large size. The generated customized digital file may be stored in the digital file data storage 180 for access or transmission via the network 117.

[0027] Figure 2is a data flow diagram depicting an exemplary method of a digital file system that may be used in association with garment production according to some embodiments. As part of the digital file method, the designer system 116 may (1) provide information about a first size of a garment. For example, the designer may submit a graphics interchange format (dxf) file or a scalable vector graphics (svg) file that depicts a garment of the first size (e.g., a size medium garment). In some embodiments, the garment designer may provide the information via a user interface associated with the digital file system 120. For example, the user interface may prompt the designer to draw a shape representing a garment piece. The designer may use the user interface to click on a particular piece, change the shape of the piece, select a seam to be used on a particular piece via a drop-down menu, draw connections between pieces, select a type of fabric to be used when manufacturing the piece or garment, edit and view particular pieces, mark a particular location on the garment where embroidery should appear, and the like.

[0028] The digital file system 120 may (2) generate a base digital file for a garment of a first size. In some embodiments, the digital file system 120 may divide the garment into a plurality of component parts. For example, the digital file system 120 may receive information about a particular garment (e.g., a shirt) and may generate a plurality of piece objects to represent the components of the shirt. For example, the digital file system 120 may generate a front shirt piece object and a back shirt piece object to represent the front of the shirt and the back of the shirt, respectively. As mentioned above, in some embodiments, the digital file system 120 may generate the base digital file by receiving and processing information selected or input by a designer via a user interface associated with the digital file system 120. In some embodiments, the base digital file may define a plurality of objects, each representing a physical component used in the production of the garment. In some embodiments, each piece of the garment may be associated with a plurality of attributes. For example, the front piece of the shirt may be associated with a unique piece identifier that identifies the particular piece in the garment and a fabric identifier that indicates the type of fabric to be used to construct the front shirt piece. Advantageously, the unique panel identifier may allow the manufacturer to easily and efficiently determine the proper location of the panel to be sewn or sewed into the article of clothing.

[0029] As discussed below, each of the multiple different components of a base digital file can reference one or more other components of the base digital file. For example, a base digital file for a shirt may include a front shirt panel object and a back shirt panel object, connected by a seam object that represents the sewn connection between the front and back shirt panel objects. In some embodiments, the panel objects may also be associated with panel metadata. For example, the panel objects may be associated with panel annotations, mirror lines along the panel (which indicate areas of symmetry of the panel), fold lines (which indicate where the panel should be folded), and grain lines (which indicate the correct orientation for placing the panel on the fabric). For example, panel metadata for a panel for a shirt sleeve may include the key "panel type" and the value "sleeve" as panel annotation metadata. In some embodiments, the digital file system may represent a garment using a coordinate system, wherein each panel of the garment may include a unique set of coordinates in the coordinate system.

[0030] In some embodiments, a base digital file may also include instructions that specify how the digital file's component objects should be arranged to form a garment. By way of example, a base digital file for a shirt may include sewing instructions that specify how a seam, represented by a Seam object, should sew together a front shirt panel object and a second shirt panel object. Similarly, a base digital file may also include one or more Edge objects that represent edges corresponding to the seam, and therefore to the panels. In some embodiments, an Edge object may be an array of points and an EdgeType attribute. In some embodiments, the EdgeType attribute helps identify the type of edge (e.g., whether the edge is straight or curved). In some embodiments, the EdgeType used for a particular seam or panel may vary depending on the garment panel itself. For example, a panel used to construct the sleeve of a sweater may be associated with an EdgeObject indicating a simple straight edge. On the other hand, a panel forming part of the sweater's collar may alternatively be associated with a CurvedEdgeType.

[0031] In some embodiments, curved edges in garment pieces can be represented using Bezier curves. In some embodiments, the Bezier curve can be a quadratic curve or a cubic curve. In some embodiments, a quadratic Bezier curve can be defined by one vertex and two handle points. In some embodiments, a quadratic Bezier curve can also include one or more control points that allow a main Bezier curve to be separated into multiple smaller curves connected via one or more control points. In some embodiments, a cubic Bezier curve can be defined using two vertices and two handle points. It can also include one or more control points that allow the main cubic Bezier curve to be separated into smaller connected curves.

[0032] Once the digital file system 120 generates a base digital file for a garment of the first size, the digital file system 120 may (3) store the base digital file in the digital file data storage 180. In some embodiments, the base digital file may be stored in an object-oriented format, such as JavaScript Object Notation (JSON) format. Because products may have significantly different structures based on customization options, in some embodiments, the digital file system 120 may store multiple base digital files for the same product. For example, multiple base digital files may be generated for a shirt that may be transformed into a V-neck or a crew neck depending on the cut of the fabric. Although both a V-neck shirt and a crew neck shirt are considered T-shirts, the patterns associated with the V-neck shirt and the crew neck shirt are significantly different, thus justifying having two different base digital files. In some embodiments, the digital file data storage may be an array of base digital files, wherein each entry may also include a product identifier and a name. In some embodiments, the data storage may also track whether a particular base digital file is considered the default option for a particular product. Furthermore, it should be understood that what is often described herein as individual objects (such as panel objects and seam objects) within a single digital file may alternatively be separate files, wherein at least one of the files refers to or references another file. Thus, in such embodiments, some files may be shared between two variations of an item of clothing (such as panels for sleeves of a V-neck shirt and a crew neck shirt), while other files may be different (such as front panels for a V-neck shirt versus front panels for a crew neck shirt).

[0033] Once the digital file system 120 generates the base digital file for the garment and stores the base digital file in the digital file data storage device 180, the user system 110 may (4) select an alternative size or custom measurement for the garment via a user interface associated with the retail system 119, and the digital file system may (5) receive the alternative size or custom measurement selection from the retail system 119. For example, a user on an e-retailer's website may initiate a purchase order for a shirt and select a standard size option (e.g., medium) from a drop-down menu of standard sizes (e.g., small, medium, large) on the website associated with the retail system 119. In some embodiments, the user may submit information about the user's body measurements to a profile stored in the retail system 119. In this case, the digital file system 120 may automatically receive the user's body measurement information from the retail system 119 whenever the user initiates a purchase order for the garment. In some embodiments, the user may provide the body measurement information directly to the digital file system 120 rather than through the retail system 119.

[0034] The digital file system 120 may (6) generate a customized digital file upon receiving the alternative size or custom measurement information or selection. In some embodiments, the customized digital file associated with the item may include the same components of the base digital file, but with altered values. For example, if the base digital file for a pair of pants includes a piece object for a standard small, the customized digital file for a standard medium pair of pants may include the same piece object, but in the size of a standard medium pair of pants. In some embodiments, when a user selects an alternative standard size that is different from the size associated with the base digital file, the digital file system 120 may apply a graded scale to convert the pants from the base size to the alternative size. For example, the graded scale may include one or more formulas that mathematically convert measurements of one size of a garment to the alternative size.

[0035] In some embodiments, the grading scale may be a table of measurements for standard sizes that a manufacturer may reference to create garments of a particular standard size. In some embodiments, the digital file system 120 may replace measurements stored in the base digital file with custom measurements transmitted to the digital file system 120 from the user system 110, designer system 116, or retail system 119. For example, the digital file system 120 may replace a waist measurement associated with a base size of a pair of pants (e.g., 28 inches) with a custom waist measurement of the same pair of pants received from a user (e.g., 30 inches). This may also trigger various stored rules that cause other values in the base digital file (besides the waist measurement itself) to be changed or altered in order to maintain the desired proportions between the various components of the garment. The digital file system 120 may then (7) transmit the custom digital file to the manufacturer system 114. The user of the manufacturer system 114 may then use the custom digital file to create a garment based on the alternative size or custom body measurements. Thus, the manufacturer may successfully create a garment that fits the garment properly without requiring additional input from the designer or user.

[0036] Figure 3is a flowchart depicting an exemplary method for generating a digital file according to some embodiments. In block 310, the digital file system may receive information associated with a first dimension of an item. For example, the digital file system may receive a dxf or svg file depicting an image of a jacket, along with handwritten annotations regarding specific details of the jacket (e.g., the length of the right sleeve, the number of buttons on the jacket, or the placement of a zipper). In some embodiments, the digital file system may receive information from a designer via a user interface associated with the digital file system 120. For example, the user interface may prompt the designer to draw a shape representing a garment panel. The designer may use the user interface to click on a specific panel, change the shape of the panel, select a seam to be used on a specific panel via a drop-down menu, draw connections between panels, select the type of fabric to be used when manufacturing the panel or garment, edit and view specific panels, mark specific locations on the garment where embroidery should appear, and the like.

[0037] In block 315, the digital filing system may generate a base digital file of the item of the first size. Figure 4 An example of a base digital file can be seen in . A base digital file for an item can be generated based at least in part on selections or inputs in a user interface associated with digital file system 120. For example, a user interface can prompt a garment designer to provide responses to certain questions (e.g., what type of fabric should be used for this garment piece?), and digital file system 120 can populate the base digital file with the provided responses or selections.

[0038] At block 325, the digital file system 120 may store the base digital file in the digital file data storage device 180. At block 330, the digital file system 120 may receive personal body measurements or standard size selections from the user's computing device. For example, a user on an e-retailer's website may initiate a purchase order for a shirt and select a standard size option (e.g., medium) from a drop-down menu of standard sizes (e.g., small, medium, large). In some embodiments, the user may submit information regarding the user's body measurements to a profile stored in the designer system 116 for a custom-sized order, rather than selecting a standard size. For example, the user may take a photo of the user's body and submit the photo to the retail system 119. Whenever a user initiates a purchase order for a garment, the digital file system 120 may automatically receive the user's body measurement information, or the user may manually provide the body measurement information to the retail system or the digital file system 120. It should be understood that in other examples, the digital file system 120 may receive information other than personal body measurements or standard size selections. For example, in some embodiments, the digital file system 120 may receive a selection of a specific pattern, embroidery, or fabric for a custom-sized garment.

[0039] In block 335, the digital file system 120 may generate a customized digital file in response to receiving the individual's body measurements or standard size selections. In some embodiments, the customized digital file may include Figure 4 As mentioned above, in some embodiments, a customized digital file associated with an item may include the same components of the base digital file, but with altered values. For example, if the base digital file for a pair of pants includes a piece object in a standard small size, the customized digital file for a standard medium pair of pants may include the same piece object, but in the size of a standard medium pair of pants. In some embodiments, when a user selects an alternative standard size that differs from the size associated with the base digital file, digital file system 120 may apply a graduated scale to convert the pants from the base size to the alternative size. In some embodiments, digital file system 120 may replace the measurements stored in the base digital file with the customized measurements transmitted to digital file system 120 from user system 110 or retail system 119. For example, in some embodiments, a piece may be associated with a unique identifier and an object representing the measurement and unit associated with the piece. For example, a shirt piece may be associated with an object defining the unit "centimeters" and the measurement value "25," indicating that the length and width of a particular shirt piece should be 25 centimeters. In some embodiments, digital documentation system 120 may replace measurements associated with a base size (e.g., 25 cm) with custom measurements received from a user for the same article of clothing (e.g., 30 cm), and alter the measurements of nearby panels, seams, and / or other objects of the garment according to preset rules or formulas.

[0040] Figure 4 is a visual representation of the components in an exemplary digital file. Digital file 400 may be a text file that includes references to garment file 410, sewing file 412, fabric file 414, and sewing supply file 416. In other embodiments, digital file 400 may be a package that itself includes sub-files corresponding to garment file 410, sewing file 412, fabric file 414, and sewing supply file 416. In still other embodiments, Figure 4 The contents shown as different files or sub-files in the figure may alternatively all be included in a single file, such as a single text file, as different definition objects. In some embodiments, the digital file 400 can be used to manufacture a garment or create a digital visualization of the garment (such as a three-dimensional rendering of the garment worn by a virtual person).

[0041] In some embodiments, a garment file 410 defines the components of a garment. For example, a garment file 410 may include a plurality of panel objects for creating a garment. In some embodiments, a garment file 410 may also include a set of instructions that specify how each panel of a garment file 410 should be cut. For example, a front panel object associated with the front of a shirt may need to be cut at a specific length to ensure that the sleeves are a specific size. In some embodiments, a garment file 410 may also include objects that represent details to be considered when constructing a garment. For example, a garment file 410 may include a fabric object that specifies which specific fabric was used to create the garment. For example, a garment file 410 may include a text file that describes that a front panel object for a shirt and a back panel object for the same shirt were both created using a fabric combination of 90% cotton and 10% polyester. In some embodiments, a garment file 410 may include a sewing object that identifies embellishments on an article of clothing. For example, a garment file 410 for a jacket may include a sewing object that defines a number of buttons to be included on the jacket, the placement of the buttons on various panel objects associated with the jacket, or any other embellishments to be included in the garment (e.g., zippers, tassels, pockets).

[0042] In some embodiments, sewing files 412 may specify how different garment panels are sewn or stitched together. For example, a digital file for a pair of jeans may include a seam object that identifies the cross stitch that should be used to sew the inseam of the jeans. On the other hand, a digital file for a jacket may include a seam object that identifies the buttonhole stitch used to sew an embroidery pattern onto the right sleeve of the jacket. In some embodiments, sewing files 412 may include a list of operations that can be performed on the garment panels. For example, sewing files 412 may reference the name of a JSON file associated with a specific operation to be performed in the garment construction. For example, sewing files 412 may reference a "stitch" operation file by name, which defines how to sew two seams using a specific stitch type (e.g., an overlock stitch). It should be understood that sewing files 412 may not be limited to sewing or stitching instructions. For example, sewing files 412 may include construction instructions that define how to attach a patch or print to a garment panel or how to include buttons or buttonholes on one or more garment panels. In some embodiments, each operation may be associated with parameters or other metadata. For example, a lockstitch operation may include a parameter called "length," which may define the overall size of the stitch; an upper thread identifier, which defines which thread should be used for the upper thread of the stitch; and a lower thread identifier, which defines which thread should be used for the lower thread of the stitch. It will be appreciated that other operations may include other types of metadata. For example, a button placement operation may include button spacing metadata, which defines the amount of space to include between each button on a particular garment panel.

[0043] In some embodiments, file 414 may include information specific to the different fabrics used in the construction of the garment. For example, if garment file 410 specifies that cotton should be used to construct a T-shirt, fabric file 414 may include a text file indicating that the T-shirt should specifically comprise a cotton twill fabric. In some embodiments, sewing supplies file 416 may include information specific to the different sewing supplies used in the construction of the garment. For example, if a digital file for a coat specifies that the coat includes five buttons arranged vertically down the center length of the coat, sewing supplies file 416 may include a text file indicating that each button is made of brass. In some embodiments, fabric file 414 may contain metadata related to the fabrics used to construct the garment. For example, in some embodiments, fabric file 414 may include a product identifier identifying a specific article of clothing, a piece identifier identifying a specific piece of clothing, and a fabric array, where each entry in the array indicates a specific fabric used to construct the piece associated with the piece identifier. In some embodiments, fabric file 414 may also include color metadata identifying the color of a specific fabric used in a specific piece of clothing.

[0044] Individuals can access digital file 400 to make changes to the digital file. For example, if a garment designer initially generates digital file 400 to represent a shirt originally made with three different pieces, the garment designer can later edit garment file 410 to change the number of pieces from three to four. In some embodiments, multiple individuals can access digital file 400. For example, the digital file can be stored in a public or private repository accessible to a group of garment designers, allowing garment designers to collaborate on creating unique or complex garment articles. In such an example, each garment designer can have the ability to directly edit any of garment file 410, sewing file 412, fabric file 414, or sewing supply file 416 in digital file 400. In some embodiments, digital file 400 can be opened using a variety of software applications (e.g., LibreCAD or AutoCAD) for easy access. For example, a user interface accessible via a custom design application or a browser can enable a user to visually design and edit components of a garment (such as pieces, annotations, fabric, and other features), which can then cause a computing system to automatically edit the corresponding object data defined in the corresponding digital file.

[0045] In some embodiments, digital file 400 can be generated based on the information pulled from a library or digital repository at least in part. In some embodiments, digital file 400 can include a reference to a file stored in a remote library. For example, if a file stored in a public online repository lists general information about the types of cotton that can be used for clothing manufacturing, fabric file 414 can reference the file by name or fabric identifier to provide information about the specific type of cotton that can be used for the pieces in a particular garment or garment. In some embodiments, the library can also include other information (for example, the curve type for sewing) for garment production. In some embodiments, digital file 400 can include a plurality of references from a plurality of libraries, data sources or files. For example, sewing supplies file 416 can include a reference to an embroidery file list stored in a first library, and sewing file 412 can reference a sewing instruction file stored in a separate library by name to effectively compile the manufacturing information of a particular garment. In some embodiments, digital file 400 can also include a copy of a library or file that was initially stored in a remote library or data source. In some embodiments, digital file 400 may be an expandable JSON file that allows a user to add, delete, or otherwise edit the component files in digital file 400. For example, a garment designer may decide to implement additional embroidery on a pair of pants and, therefore, may add a reference to a specific embroidery file in a remote repository, or add a copy of a remote repository containing the additional embroidery information. In some embodiments, the garment designer may make changes to the copy of the repository or file without affecting the original file or library that may be stored in the remote repository.

[0046] Figure 5 is a visual representation depicting an exemplary configuration of garment components in a digital documentation system according to some embodiments. Figure 5, objects shown as visually connected in the figure can be associated with each other in one or more digital files via an object-based representation that references the objects by identifier, name, or other means. In some embodiments, garment 502 can be an article of clothing (e.g., a hoodie) listed and sold on an electronic catalog. In some embodiments, garment 502 can include multiple piece objects 504, 506, and 508, each of which represents a discrete section or portion of the garment (such as a single portion of fabric cut into a specific shape). For example, if garment 502 is a hoodie, piece object 504 can represent the front portion of the hoodie, piece object 506 can represent the back portion of the hoodie, and piece object 508 can represent the hood of the hoodie. Therefore, piece objects 504, 506, and 508 can be related parts of the entire garment. In some embodiments, piece objects can include multiple seam objects. For example, piece object 504 may include or be associated with seam objects 509 and 510 (e.g., the piece object data of piece object 504 references the seam identifiers of seam objects 509 and 510, or the seam object data of seam objects 509 and 510 reference the piece identifier of piece object 504), piece object 506 may include or be associated with seam object 511, and piece object 508 may include or be associated with seam object 512. In some embodiments, seam objects may be connected together according to a particular set of sewing instructions. For example, sewing instructions that reference seam objects 510 and 511 may provide instructions for sewing the pieces represented by piece objects 504 and 506 together.

[0047] It should be understood that any number of piece objects or seam objects may be included in a particular garment. For example, a relatively simple T-shirt may only have piece objects representing the front and back of the shirt, connected together by a set of stitches. On the other hand, if garment 502 is a complex garment (e.g., a fashionable jacket), many more piece objects and seam objects may be included under garment 502. Although Figure 5 The example of FIG502 shows a piece object and a seam object, but it should be understood that other objects may be included in other embodiments. For example, garment 502 may also include a sewing object branching from piece object 504, which indicates that a piece of embroidery is located on the portion of the garment represented by piece object 504. Similarly, other sewing objects may be included to indicate the presence of other visual embellishments on garment 502, such as buttons or zippers.

[0048] Figure 6614 is a visual representation of an exemplary garment object used in a digital file system according to some embodiments. As mentioned above, a garment can be represented as a file in an object representation format such as a JSON file, wherein the JSON file includes one or more piece objects. In some embodiments, each piece object can correspond to a discrete portion of a garment article. In some embodiments, each piece object can be an entry in an array of piece objects. In some embodiments, the garment object can also include a sewing supplies array 614, wherein each entry in the sewing supplies array 614 corresponds to a decorative or visual personalization (e.g., a button or zipper) of the garment. For example, the sewing supplies array can include JSON files corresponding to thread, collars, embroidery, standardized labels, and custom labels to be included in the garment.

[0049] Figure 7 is a visual representation of an exemplary piece object for use in a digital file system, according to some embodiments. In some embodiments, a piece object can be represented as a file in an object notation format, such as a JSON file, and can refer to other objects within the digital file. For example, a piece object can include a seam array 710, where each entry in the seam array specifies a particular sewing or stitching method to produce a particular seam of a garment. In some embodiments, each piece object can include a garment ID that associates the piece with a particular article of clothing, and one or more seamware objects that specify a plurality of enhancements or details of the garment.

[0050] Figure 8 is a visual representation of an exemplary seam object for use in a digital file system, according to some embodiments. In some embodiments, a seam object may be represented as a file in an object notation format, such as a JSON file, and may include details to be used in the manufacture of a garment. For example, a seam object may include an edges array 830, where each entry in the edges array specifies a particular type of edge used to generate a panel of a garment. In some embodiments, each seam object may include a seam ID 810 that associates the seam with a particular panel in a garment, and one or more seamware objects that specify various enhancements or details of the garment. In some embodiments, a seam object may also include a seam allowance 820 that provides a measurement of the area between the panel edge and the seam or stitching.

[0051] Although the reference JSON file describes Figure 6 、 Figure 7 and Figure 8, but it should be understood that in other embodiments, many alternative formats may be used to transmit object data for a garment. For example, according to some embodiments, the file format of the digital file as described herein may generally be a file format that uses human-readable text to transmit data objects, where the data objects are composed of attribute-value pairs, array data types, and / or other attributes or parameters with associated values. These may be desirable characteristics of the formats used in various aspects of the present disclosure because they enable humans (such as designers and / or manufacturers) to read and understand the object data, while also being easily processed, parsed, and modified by software, hardware, and / or firmware of computer systems (such as systems used by retailers, designers, and / or manufacturers).

[0052] Figure 9 is a visual representation of a garment piece that may be defined by object data in a digital file system according to some embodiments. The digital file may include multiple garment pieces, where each garment piece represents a portion of an entire garment. For example, garment piece 904 may represent a front portion of a shirt, while garment piece 902 may represent a back portion of the same shirt. Additionally, garment pieces 906 and 908 may each represent a sleeve portion of a shirt. It should be understood that more or fewer garment pieces may be included in a garment, depending on the overall complexity of the garment itself. Additionally, garment pieces 902, 904, 906, and 908 may each include multiple seams and seams to assist the manufacturer in correctly constructing the garment. The shapes of the illustrated garment pieces may be defined, for example, in mathematical terms, such as by reference to measurement and curve specifications within the object data for the corresponding garment piece.

[0053] Figure 10 1 is a diagram of an exemplary computing system configured to perform the various methods described herein. Computing system 1000 may be configured to perform all or some features of digital file system 120. Computing system 1000 includes a bus 1002 or other communication mechanism for communicating information, and a hardware processor or processors 1004 coupled to bus 1002 for processing information. Hardware processor 1004 may be, for example, one or more general-purpose microprocessors.

[0054] The computing system 1000 also includes a main memory 1006, such as a random access memory (RAM), cache, or other dynamic storage device, coupled to the bus 1002 for storing information and instructions to be executed by the processor 1004. The main memory 1006 may also be used for storing temporary variables or other intermediate information during execution of instructions to be executed by the processor 1004. When stored in a storage medium accessible to the processor 1004, such instructions render the computing system 1000 as a special-purpose machine customized to perform the operations specified in the instructions.

[0055] Computing system 1000 also includes a read-only memory (ROM) 1008 or other static storage device coupled to bus 1002 for storing static information and instructions for processor 1004. A data storage device 1010, such as a magnetic disk, optical disk, or USB thumb drive (flash drive), is provided and coupled to bus 1002 for storing information and instructions.

[0056] As described below, the computing system 1000 may further implement the techniques described herein using custom hardwired logic, one or more application-specific integrated circuits (ASICs) or field-programmable gate arrays (FPGAs), firmware, and / or program logic that, in combination with the computer system, enables or programs the computing system 1000 to be a special-purpose machine. According to one embodiment, the techniques herein may be performed by the computing system 1000 in response to the processor 1004 executing one or more sequences of one or more computer-readable program instructions contained in the main memory 1006. Such instructions may be read into the main memory 1006 from another storage medium, such as the storage device 1010. Execution of the sequences of instructions contained in the main memory 1006 causes the processor 1004 to perform the process steps described herein. In alternative embodiments, hardwired circuitry may be used in place of or in combination with software instructions.

[0057] As part of a dedicated machine, computing system 1000 may include a base digital file module 1032, a customization instruction module 1034, and a custom digital file module 1036. According to one embodiment, base digital file module 1032 may receive information related to creating an article of apparel of base dimensions. In some embodiments, base digital file module 1034 may receive information and divide it into components and / or objects of the base digital file. In some embodiments, customization instruction module 1034 may receive user input from a user system, including standard size selections or custom body measurements. In some embodiments, custom digital file module 1036 may generate a custom digital file by applying a graded scale to scale the measurements of an item associated with the base digital file to a new standard size. In some embodiments, custom digital file module 1036 may generate a custom digital file customized for the standard size selections or custom body measurements by replacing any measurements stored in the base digital file with custom body measurements. The digital files utilized by modules 1032, 1034, and 1036 may be stored in data storage device 1010. According to one embodiment, the instructions may be transmitted to one or more servers 1030 via communication interface 1018. In one embodiment, the transferred instructions may be stored in ROM 1008 .

[0058] Various forms of computer-readable storage media may be involved in carrying one or more sequences of one or more computer-readable program instructions to processor 1004 for execution. For example, the instructions may initially be carried on a disk or solid-state drive of a remote computer. Bus 1002 may carry the data to main memory 1006, from which processor 1004 retrieves and executes the instructions.

[0059] The computing system 1000 also includes a communication interface 1018 coupled to the bus 1002. The communication interface 1018 provides bidirectional data communication coupled to a network link 1020, which is connected to a local network 1022. For example, the communication interface 1018 can be an integrated services digital network (ISDN) card, a cable modem, a satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface 1018 can be a local area network (LAN) card for providing a data communication connection to a compatible LAN (or to a WAN component in communication with a WAN). A wireless link can also be implemented. In any such implementation, the communication interface 1018 sends and receives electrical, electromagnetic, or optical signals that carry digital data streams representing various types of information.

[0060] Network link 1020 typically provides data communication through one or more networks to other data devices. For example, network link 1020 may provide a connection through local network 1022 to a host computer 1024 or to data devices operated by an Internet Service Provider (ISP). The ISP, in turn, provides data communication services to server 1030 through the Internet.

[0061] Depending on the implementation, certain actions, events, or functions of any process or algorithm described herein may be performed in a different order, may be added, combined, or omitted entirely (e.g., not all described operations or events are required for the practice of the algorithm). Furthermore, in some embodiments, operations or events may be performed concurrently, for example, through multithreading, interrupt handling, or on one or more computer processors or processor cores or other parallel architectures, rather than sequentially.

[0062] The various illustrative logical blocks, modules, routines, and algorithmic steps described in conjunction with the embodiments disclosed herein may be implemented as electronic hardware or as a combination of electronic hardware and executable software. To clearly illustrate this interchangeability, various illustrative components, blocks, modules, and steps have been generally described above in terms of their functionality. Whether such functionality is implemented as hardware or as software running on hardware depends on the specific application and design constraints imposed on the overall system. The described functionality may be implemented in different ways for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of this disclosure.

[0063] In addition, the various illustrative logical blocks and modules described in conjunction with the embodiments disclosed herein may be implemented or executed by a machine designed to perform the functions described herein, such as a c-system, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The digital file system may be or may include a microprocessor, but in an alternative embodiment, the digital file system may be or may include a controller, a microcontroller, or a state machine, or a combination thereof. The digital file system may include circuits configured to process computer-executable instructions. Although primarily described herein with respect to digital technology, the digital file system may also primarily include analog components. For example, some or all of the prediction algorithms described herein may be implemented in analog circuits or mixed analog and digital circuits. The computing environment may include any type of computer system, including but not limited to a microprocessor-based computer system, a mainframe computer, a digital signal processor, a portable computing device, a computing engine within a device controller or apparatus, and the like.

[0064] Elements of the methods, processes, routines, or algorithms described in conjunction with the embodiments disclosed herein may be embodied directly in hardware, in software modules executed by a digital file system, or in a combination of the two. The software modules may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of non-transitory computer-readable storage medium. An exemplary storage medium may be coupled to the digital file system so that the digital file system can read information from and write information to the storage medium. In an alternative embodiment, the storage medium may be integral to the digital file system. The digital file system and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In an alternative embodiment, the digital file system and the storage medium may reside in the user terminal as discrete components.

[0065] Unless otherwise expressly stated or understood in the context of use, conditional language such as "can," "may," "could," "may," "for example," etc., used herein is generally intended to convey that certain embodiments include certain features, elements, and / or steps, while other embodiments do not include certain features, elements, and / or steps. Therefore, such conditional language is generally not intended to imply that the features, elements, and / or steps are necessary for one or more embodiments, or that one or more embodiments must include logic for determining whether to include these features, elements, and / or steps or whether to perform these features, elements, and / or steps in any particular embodiment with or without other input or prompts. The terms "comprise," "include," "have," etc. are synonymous and are used inclusively in an open-ended manner and do not exclude additional elements, features, actions, operations, etc. In addition, the term "or" is used in its inclusive sense (rather than in its exclusive sense) so that when, for example, it is used to connect a list of elements, the term "or" means one, some, or all of the elements in the list.

[0066] Unless expressly stated otherwise, disjunctive language such as the phrase "at least one of X, Y, or Z" should otherwise be understood in context as generally used to indicate that an item, term, etc. can be X, Y, or Z, or any combination thereof (e.g., X, Y, and / or Z). Thus, such disjunctive language is generally not intended to, and should not, imply that certain embodiments require that at least one of X, at least one of Y, or at least one of Z each be present.

[0067] Unless expressly stated otherwise, articles such as "a" or "an" should generally be interpreted to include one or more of the described items. Thus, a phrase such as "a device configured to" is intended to include one or more of the enumerated devices. Such one or more enumerated devices may also be collectively configured to perform the stated statements. For example, "a processor configured to perform statements A, B, and C" may include a first processor configured to perform statement A working in conjunction with a second processor configured to perform statements B and C.

[0068] Although the above detailed description has shown, described and pointed out the novel features applied to various embodiments, it will be understood that various omissions, substitutions and changes may be made to the form and details of the devices or algorithms shown without departing from the spirit of the present disclosure. It will be appreciated that certain embodiments described herein may be embodied in a form that does not provide all of the features and benefits set forth herein, as some features may be used or practiced separately from other features. The scope of certain embodiments disclosed herein is indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalents of the claims will be included within the scope of the claims.

[0069] Examples of embodiments of the present disclosure may be described in terms of:

[0070] Clause 1. A system comprising:

[0071] a memory storing computer-executable instructions; and

[0072] one or more hardware processors in communication with the memory and configured by the executable instructions to at least:

[0073] retrieving a first library from a first data source, wherein the first library includes garment information that can be referenced to manufacture one or more garments;

[0074] retrieving a second library from a second data source, wherein the second library includes garment information that can be referenced to manufacture one or more garments; and

[0075] Generating a base digital file for a garment based at least in part on the first library and the second library, wherein the base digital file defines a plurality of objects, each representing a physical component used in the production of the garment, the base digital file including or referencing each of the following:

[0076] a garment identifier that uniquely identifies the garment from among a plurality of other garments;

[0077] a piece object, wherein the piece object represents a piece that is part of the garment, and wherein the piece object is associated with (a) a piece identifier that uniquely identifies the piece and (b) one or more references to garment information in the first library; and

[0078] a seam object, wherein the seam object represents a seam forming a portion of the garment, and wherein the seam object includes one or more references to garment information in the second library and is associated with a seam identifier that uniquely identifies the seam, wherein the base digital file associates the seam identifier with the panel identifier to indicate that the seam is associated with the panel.

[0079] Clause 2. The system of Clause 1, wherein the one or more references to garment information in the first library associated with the piece object include a fabric identifier identifying a fabric to be used to produce the piece.

[0080] Clause 3. The system of clause 1, wherein the one or more hardware processors are further configured to:

[0081] storing the base digital file in a third data source;

[0082] receiving modifications to the base digital file; and

[0083] The base digital file in the third data source is modified based at least in part on the received modifications.

[0084] Clause 4. The system of Clause 3, wherein the modification to the base digital file comprises at least one of adding, deleting, or editing one or more individual objects included in the base digital file.

[0085] Clause 5. A system comprising:

[0086] a memory storing computer-executable instructions; and

[0087] one or more hardware processors in communication with the memory and configured by the executable instructions to at least:

[0088] obtaining a library from a data source, wherein the library includes garment information that can be referenced to create one or more garments; and

[0089] Generating a base digital file for a garment based at least in part on the library, wherein the base digital file defines a plurality of objects, each representing a physical component used in the production of the garment, the base digital file including or referencing each of:

[0090] a garment identifier that uniquely identifies the garment from among a plurality of other garments;

[0091] a piece object, wherein the piece object represents a piece that is part of the garment, and wherein the piece object is associated with (a) a piece identifier that uniquely identifies the piece and (b) one or more references to garment information in the library; and

[0092] A seam object, wherein the seam object represents a seam forming a portion of the garment, and wherein the seam object includes one or more references to garment information in the library and is associated with a seam identifier that uniquely identifies the seam, wherein the base digital file associates the seam identifier with the piece identifier.

[0093] Clause 6. The system of clause 5, wherein the base digital file further comprises a handicraft object representing embroidery associated with the garment.

[0094] Clause 7. The system of Clause 5, wherein the base digital file is generated based at least in part on references to garment information in one or more additional libraries other than the library.

[0095] Clause 8. The system of Clause 5, wherein the base digital file is generated based at least in part on a selection or input in a user interface.

[0096] Clause 9. The system of Clause 8, wherein the selection or input in the user interface comprises a selection of at least one of a pattern, embroidery, or fabric to be used in the production of the garment.

[0097] Clause 10. The system of clause 8, wherein the base digital file further identifies a default size for the garment.

[0098] Clause 11. The system of Clause 5, wherein the seam object further comprises a reference to one or more construction instructions that define how the seam interacts with the garment.

[0099] Clause 12. A system as described in Clause 11, wherein the construction instructions include at least one of the following: (a) a stitch type defining how to sew two seams together, (b) instructions defining how to attach a patch or print to a garment piece, or (c) instructions defining how to include buttons or buttonholes on a garment piece.

[0100] Clause 13. The system of Clause 5, wherein the piece object further comprises piece metadata, the piece metadata defining a unique set of coordinates of the piece in a coordinate system.

[0101] Clause 14. A computer-implemented method comprising:

[0102] obtaining a library from a data source, wherein the library includes garment information that can be referenced to create one or more garments; and

[0103] Generating a base digital file for a garment based at least in part on the library, wherein the base digital file defines a plurality of objects, each representing a physical component used in the production of the garment, the base digital file including or referencing each of:

[0104] a garment identifier that uniquely identifies the garment from among a plurality of other garments;

[0105] a piece object, wherein the piece object represents a piece that is part of the garment, and wherein the piece object is associated with (a) a piece identifier that uniquely identifies the piece and (b) one or more references to garment information in the library; and

[0106] A seam object, wherein the seam object represents a seam forming a portion of the garment, and wherein the seam object includes one or more references to garment information in the library and is associated with a seam identifier that uniquely identifies the seam, wherein the base digital file associates the seam identifier with the piece identifier.

[0107] Clause 15. The computer-implemented method of Clause 14, wherein the base digital file is formatted to be interpretable by each of a plurality of software applications.

[0108] Clause 16. The computer-implemented method of Clause 14, wherein the base digital file is configured to apply one or more modifications to one or more objects defined therein to generate customized digital files for producing one or more customized instances of the garment.

[0109] Clause 17. The computer-implemented method of Clause 16, wherein the modification comprises at least one of adding, deleting, or editing one or more objects defined in the base digital file.

[0110] Clause 18. The computer-implemented method of Clause 14, wherein the seam object further comprises an edge array, wherein each entry in the edge array specifies a particular type of edge associated with a panel of the garment.

[0111] Clause 19. The computer-implemented method of Clause 14, wherein the seam object further comprises a seam allowance defining a measurement of an area between the panel identified by the panel identifier and the seam represented by the seam identifier.

[0112] Clause 20. The computer-implemented method of clause 14, wherein the piece object further comprises a measurement value and a unit identifier, wherein the unit identifier defines a unit of measurement associated with the piece, and the measurement value defines a size value associated with the piece using the unit of measurement defined by the unit identifier.

[0113] Additional examples of embodiments of the present disclosure may be described in light of the following further clauses:

[0114] Clause 21. A system comprising:

[0115] a memory storing computer-executable instructions; and

[0116] one or more hardware processors in communication with the memory and configured by the executable instructions to at least:

[0117] receiving information associated with a garment, the information including a garment identifier and measurements associated with a first garment size;

[0118] Generate a basic digital file of the garment, the basic digital file comprising:

[0119] Garment identifier;

[0120] a pattern object, the pattern object identifying that the base digital file is associated with the garment of the first garment size;

[0121] an array of piece objects, wherein each piece object in the array of piece objects represents a portion of the garment, and wherein each piece object is associated with a piece identifier, a fabric identifier representing a fabric of the piece object, and one or more seam objects representing one or more seams forming the portion of the garment; and

[0122] an array of sewing supply objects, wherein each sewing supply object in the array of sewing supply objects is associated with a piece object in the array of garment objects and represents an accessory to be applied to the piece object;

[0123] wherein the base digital file of the garment is associated with a grading scale for transforming the garment from the first garment size to a second garment size;

[0124] receiving a request to transform the garment from the first garment size to the second garment size, wherein the request includes a selection of the second garment size or user input of one or more user body measurements;

[0125] generating a customized digital file for the garment at least in part by modifying measurement information within the base digital file for the garment based on at least one of the user body measurements or the grading scale; and

[0126] The customized digital file is transmitted to a remote computing device for use in producing a garment corresponding to the customized digital file.

[0127] Clause 22. The system of Clause 21, wherein each piece identifier associated with the array of piece objects is unique across a plurality of digital files.

[0128] Clause 23. The system of Clause 21, wherein the received information associated with the garment comprises a digital interchange file or a scalable vector graphics file.

[0129] Clause 24. The system of Clause 21, wherein the grading scale comprises a garment measurement chart for a plurality of sizes.

[0130] Clause 25. A system comprising:

[0131] a memory storing computer-executable instructions; and

[0132] one or more hardware processors in communication with the memory and configured by the executable instructions to at least:

[0133] receiving information associated with a garment, the information including a garment identifier and measurements associated with a first garment size;

[0134] A base digital file of the garment is generated, the base digital file including or referencing one of the following:

[0135] Garment identifier;

[0136] a piece object, wherein the piece object represents a portion of the garment, and wherein the piece object is associated with a piece identifier; and

[0137] a seam object, wherein the seam object represents a seam forming a portion of the garment;

[0138] receiving a request to produce an instance of the garment in a second garment size, wherein the request includes a selection of a standard garment size or user input of one or more user body measurements;

[0139] generating a customized digital file of the garment at least in part by modifying measurement information within the base digital file of the garment based on at least one of the user body measurements or a grading scale associated with the standard garment dimensions; and

[0140] The customized digital file is transmitted to a remote computing device for use in producing a garment corresponding to the customized digital file.

[0141] Clause 26. The system of Clause 25, wherein the base digital file and the custom digital file are each JavaScript Object Notation files.

[0142] Clause 27. The system of Clause 25, wherein the garment is associated with a plurality of base digital files.

[0143] Clause 28. A system as described in Clause 25, wherein the base digital file also includes or references a sewing supplies object, wherein the sewing supplies object includes a list of one or more buttons, patches, threads, or zippers to be included on at least one garment piece referenced in the garment piece object.

[0144] Clause 29. The system of Clause 25, wherein the panel object is further associated with a fabric identifier representing a fabric used for the panel object.

[0145] Clause 30. The system of Clause 25, wherein the panel object is further associated with one or more edge objects, wherein each edge object comprises a point array and an edge type.

[0146] Clause 31. The system of Clause 30, wherein the edge type comprises one of a straight line edge or a Bezier curve edge.

[0147] Clause 32. The system of Clause 25, wherein the piece object is associated with piece metadata comprising one or more of a piece annotation, a mirror line, a fold line, or a grain line.

[0148] Clause 33. The system of Clause 25, wherein the piece object is stored in a piece file and the piece object is referenced in the base digital file by the name of the piece file.

[0149] Clause 34. A method comprising:

[0150] A base digital file of a garment in a first size is generated, the base digital file including or referencing each of the following:

[0151] Garment identifier;

[0152] a piece object, wherein the piece object represents a portion of the garment, and wherein the piece object is associated with a piece identifier; and

[0153] a seam object, wherein the seam object represents a seam forming a portion of the garment;

[0154] wherein the base digital file of the garment is associated with a grading scale for transforming the garment from the first size to one or more other sizes;

[0155] receiving a request to produce an instance of the garment in a second size, wherein the request includes a selection of the second size or user input of one or more user body measurements;

[0156] generating a customized digital file for the garment at least in part by modifying measurement information within the base digital file for the garment based on at least one of the user body measurements or the grading scale; and

[0157] The customized digital file is transmitted to a remote computing device for use in producing a garment corresponding to the customized digital file.

[0158] Clause 35. The method of Clause 34, wherein the panel objects and the seam objects are defined in one or more JavaScript Object Notation files.

[0159] Clause 36. The method of Clause 34, wherein the base digital file and the customized digital file are stored in a data storage device.

[0160] Clause 37. The method of Clause 34, further comprising transmitting the base digital file to the remote computing device.

[0161] Clause 38. The method of Clause 34, wherein the garment is represented by a coordinate system and each piece object is associated with a unique set of coordinates in the coordinate system.

[0162] Clause 39. The method of Clause 34, wherein the base digital file includes or references a plurality of panel objects and a plurality of seam objects.

[0163] Clause 40. The method of Clause 34, wherein the remote computing device is a manufacturer computing system.

Claims

1. A system for generating a basic digital file of a garment, comprising: a memory storing computer-executable instructions; and one or more hardware processors in communication with the memory and configured by the executable instructions to at least: obtaining a library from a data source, wherein the library includes garment information that can be referenced to create one or more garments; and Generating a base digital file for a garment based at least in part on the library, wherein the base digital file is in an object representation format, wherein text of the base digital file defines a plurality of objects, each of the plurality of objects representing a physical component used in the production of the garment, the base digital file including or referencing each of the following: a garment identifier that uniquely identifies the garment from a plurality of other garments, wherein the base digital file includes an association between the garment identifier and each of a plurality of piece identifiers for pieces comprising the garment; a first piece object, wherein the first piece object represents a first piece that is part of the garment, and wherein the first piece object is associated with a first piece identifier contained in the base digital file that uniquely identifies the first piece and one or more references to garment information in the library; a second piece object, wherein the second piece object represents a second piece that is part of the garment, and wherein the second piece object is associated with a second piece identifier contained in the base digital file that uniquely identifies the second piece; as well as a seam object, wherein the seam object represents a seam forming a portion of the garment, and wherein the seam object includes one or more references to garment information in the library and is associated with a seam identifier that uniquely identifies the seam, wherein the base digital file associates the seam identifier with both the first and second panel identifiers, and wherein the base digital file further associates the seam identifier with information defining how the seam should connect the first and second panels when the garment is physically manufactured.

2. The system for generating a base digital file of a garment as claimed in claim 1, wherein the base digital file further comprises a sewing item object, the sewing item object representing embroidery associated with the garment.

3. A system for generating a base digital file for a garment as described in claim 1, wherein the base digital file is generated at least in part based on selections or inputs in a user interface, wherein the selections or inputs in the user interface include selection of at least one of a pattern, embroidery, or fabric to be used to produce the garment.

4. The system for generating a base digital file of a garment according to claim 1, wherein the base digital file further identifies a default size of the garment.

5. The system for generating a base digital file of a garment of claim 1 , wherein the information defining how the seam should connect the first and second panels comprises a reference to one or more construction instructions.

6. A system for generating a base digital file for a garment as described in claim 5, wherein the construction instructions include at least one of the following: a stitch type defining how to sew two seams together, instructions defining how to attach a patch or print to a garment panel, or instructions defining how to include buttons or buttonholes on a garment panel.

7. The system for generating a basic digital file of a garment according to claim 1, wherein the first garment part object further comprises first garment part metadata, wherein the first garment part metadata defines a unique coordinate set of the first garment part in a coordinate system.

8. A computer-implemented method for generating a base digital file of a garment, comprising: obtaining a library from a data source, wherein the library includes garment information that can be referenced to create one or more garments; as well as Generating a base digital file for a garment based at least in part on the library, wherein the base digital file is in an object representation format, wherein text of the base digital file defines a plurality of objects, each of the plurality of objects representing a physical component used in the production of the garment, the base digital file including or referencing each of the following: a garment identifier that uniquely identifies the garment from a plurality of other garments, wherein the base digital file includes an association between the garment identifier and each of a plurality of piece identifiers for pieces comprising the garment; a first piece object, wherein the first piece object represents a first piece that is part of the garment, and wherein the first piece object is associated with a first piece identifier contained in the base digital file that uniquely identifies the first piece and one or more references to garment information in the library; a second piece object, wherein the second piece object represents a second piece that is part of the garment, and wherein the second piece object is associated with a second piece identifier contained in the base digital file that uniquely identifies the second piece; as well as a seam object, wherein the seam object represents a seam forming a portion of the garment, and wherein the seam object includes one or more references to garment information in the library and is associated with a seam identifier that uniquely identifies the seam, wherein the base digital file associates the seam identifier with both the first and second panel identifiers, and wherein the base digital file further associates the seam identifier with information defining how the seam should connect the first and second panels when the garment is physically manufactured.

9. A computer-implemented method of generating a base digital file for a garment as recited in claim 8, wherein the base digital file is formatted to be interpretable by each of a plurality of software applications.

10. A computer-implemented method for generating a base digital file of a garment as described in claim 8, wherein the base digital file is configured to apply one or more modifications to one or more objects defined therein to generate a customized digital file for producing one or more customized instances of the garment.

11. The computer-implemented method of generating a base digital file for a garment according to claim 10, wherein the modification comprises at least one of adding, deleting, or editing one or more objects defined in the base digital file.

12. The computer-implemented method for generating a base digital file for a garment of claim 8, wherein the seam object further comprises an edge array, wherein each entry in the edge array specifies a type of edge associated with a panel of the garment.

13. The computer-implemented method for generating a base digital file for a garment of claim 8 , wherein the seam object further comprises a seam allowance defining a measurement of an area between the first panel identified by the first panel identifier and the seam represented by the seam identifier.

14. The computer-implemented method for generating a base digital file for a garment of claim 8, wherein the first garment piece object further comprises a measurement value and a unit identifier, wherein the unit identifier defines a unit of measurement associated with the first garment piece, and the measurement value defines a size value associated with the first garment piece using the unit of measurement defined by the unit identifier.

15. The computer-implemented method for generating a base digital file for a garment according to claim 8, wherein the base digital file is associated with a grading scale for transforming the garment from a first size to one or more other sizes, the computer-implemented method further comprising: receiving a request to produce an instance of the garment in a second size, wherein the request includes a selection of the second size or user input of one or more user body measurements; generating a customized digital file of the garment at least in part by modifying measurement information within the base digital file of the garment based on at least one of the user body measurements or the grading scale; as well as The customized digital file is transmitted to a remote computing device for use in producing a garment corresponding to the customized digital file.

Images