# US 2004/0083449 A1 · System and method for batch-feeding data

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2004/0083449 A1
- Document ID: US20040083449A1
- Status: Published application
- Kind: A1
- Application number: 10/690,393
- Filed: 2003-10-20
- Published: 2004-04-29
- Earliest claimed: 2002-10-21
- Assignees: The Boeing Comapny
- Inventors: William C. Dodge
- Web page: https://patentgrep.com/patent/US20040083449A1

## CPC

- G06F 16/258: {Data format conversion from or to a database}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system and method for batch-feeding existing data that is formatted for one type of software application to another type of software application. The steps to provide the existing data to another type of software application include assembling the data into one-to-one tables, providing the one-to-one tables to a server, receiving the one-to-one tables at the server, reformatting the data from the one-to-one tables to a reformatted form according to rules of the software application, and entering the data in the reformatted form in a database. The system allows a user to save the existing data in the one-to-one tables on a share drive that is also accessible to a server. The user is then able to initiate the reformatting of the data by emailing the server a request to reformat the data.

## Claims

### Claim 1

A method for providing data to a software application comprising the steps of:
assembling the data into a plurality of tables;
providing the plurality of tables to a memory accessible by a server;
sending a request, from a client to the server, to reformat the data in the plurality of tables;
receiving the plurality of tables at the server in response to the server receiving the request to reformat the plurality of tables;
reformatting, at the server, the data in the plurality of tables to a reformatted form according to rules of the software application; and
entering the data in the reformatted form in a database.

### Claim 2 (depends on 1)

The method of claim 1, wherein the step of assembling the data into the plurality of tables comprises assembling the data at the client into the plurality of tables wherein at least one of the plurality of tables is formatted in a one-to-one relationship.

### Claim 3 (depends on 2)

The method of claim 2, wherein the step of assembling comprises creating each of the plurality of tables in respective spreadsheets, wherein the step of providing the tables to the memory comprises providing the spreadsheets to the memory.

### Claim 4 (depends on 1)

The method of claim 1, wherein the step of sending a request to reformat the data comprises sending the request via an email from the client to the server.

### Claim 5 (depends on 4)

The method of claim 4, further comprising the step of:
authenticating a sender of the request to convert the data;
wherein the step of entering comprises entering the data in response to the step of authenticating producing a confirmation that the sender is authorized to enter the data in the database.

### Claim 6 (depends on 5)

The method of claim 5, wherein the step of authenticating comprises authenticating the sender by comparing an email user name of the sender used in the email with a list of authorized users.

### Claim 7 (depends on 1)

The method of claim 1, further comprising the step of:
validating, prior to the step of entering, the data by comparing the data with validation data in the database.

### Claim 8

A method for providing data to a database comprising the steps of:
receiving, at a server, a request sent via email from a client to assemble the data according to rules of a software application;
receiving, in response to the email being received, the data from a memory accessible by both the server and a client;
assembling the data into data formatted according to the rules of the software application; and
entering the data formatted according to rules of the software application in a database.

### Claim 9 (depends on 8)

The method of claim 8, wherein the step of receiving the data comprises receiving the data as a collection of tables organized in a one-to-one relationship.

### Claim 10 (depends on 9)

The method of claim 9, wherein the step of receiving the data as a collection of tables comprises receiving each of the tables in a collection of respective spreadsheets, wherein the collection of spreadsheets are stored in a folder in the memory.

### Claim 11 (depends on 10)

The method of claim 10, wherein the data is project management data and the collection of tables comprises tables selected from the group consisting of: an activity information table, a resource information table, a relationship information table and a global activity code attribute table.

### Claim 12 (depends on 8)

The method of claim 8, further comprising the step of:
validating, prior to the step of entering the data, the data in the one-to-one tables.

### Claim 13 (depends on 12)

The method of claim 12, further comprising the step of:
compiling an exception report during the step of validating; and
providing the exception report to another folder in the memory.

### Claim 14 (depends on 8)

The method of claim 8, further comprising the step of:
authenticating a sender of the request to assemble the data based upon an email address of the sender;
wherein the step of entering comprises entering the data in response to the step of authenticating producing a confirmation that the sender is authorized to update the database.

### Claim 15 (depends on 8)

The method of claim 8, wherein the step of assembling the into data formatted according to the rules of the software application comprises assembling the data from a one-to-one format into a one-to-many format.

### Claim 16

A computer readable medium embodied with code segments for providing data to a database, the computer readable medium comprising:
a code segment for receiving a request at a server from a client to assemble data into a format that is in accord with rules of a software application;
a code segment for receiving, in response to the request from the client to assemble the data, the data at the server;
a code segment for assembling the data into the format that is in accord with rules of a software application; and
a code segment for entering the data that is in accord with rules of a software application into a database.

### Claim 17 (depends on 16)

The computer readable medium of claim 16, wherein the code segment for receiving comprises a code segment for receiving the data as one-to-one tables from a memory accessible by both the server and a client.

### Claim 18 (depends on 16)

The computer readable medium of claim 16, further comprising:
a code segment for validating the data prior to the data, that is in accord with rules of a software application, being entered into the database.

### Claim 19 (depends on 16)

The computer readable medium of claim 16, wherein the code segment for receiving a request at a server from a client comprises a code segment for receiving the request at the server via an email from the client.

### Claim 20 (depends on 19)

The computer readable medium of claim 19 further comprising:
a code segment for authenticating a sender of the request to assemble the data based upon an email address of the sender;
wherein the code segment for entering the data comprises a code segment for entering the data in response to the sender being authenticated by the code segment for authenticating.
