12
Summary of Changes for DATA 4.69 David Stevenson April 24, 2008

Summary of Changes for DATA 4.69 David Stevenson April 24, 2008

Embed Size (px)

Citation preview

Page 1: Summary of Changes for DATA 4.69 David Stevenson April 24, 2008

Summary of Changes for DATA 4.69

David StevensonApril 24, 2008

Page 2: Summary of Changes for DATA 4.69 David Stevenson April 24, 2008

2

Summary of Changes for DATA 4.69

DATA v4.69 supports Darlington and 2010 Automotive requests.

Release was made one month after DATA v4.68 was released.

Page 3: Summary of Changes for DATA 4.69 David Stevenson April 24, 2008

3

Background on Darlington/CIL DATA UsageDEP is interested in DATA for the following

reasons: global format consistency, revision control, data accuracy, approval process

Darlington is supporting ChinaCIL is also planning to use DATA and has been

involved in meetings between the UK and the Advisor team.

We have about 3-5 users at DEP – they funnel their changes through one person, currently.

We have about 10 users at CIL – mix of AEs and CPEs.

Page 4: Summary of Changes for DATA 4.69 David Stevenson April 24, 2008

4

Requests from DarlingtonOriginal request from Darlington included:

– Add max oil pressure value.– Add max exhaust pressure at turbo outlet value.– Add max altitude for operation without derate value.– Change clutch engagement torque wording.– Add max coolant flow to accessories value.– Add reference to cooling AEB.– Add heat rejection to aftercooler in the performance section.– Use ps power units instead of hp.– Remove references to Aftertreatment.– Change test condition wording to reference 80/1269/EEC.– Remove all SAE units from the datasheet.

Page 5: Summary of Changes for DATA 4.69 David Stevenson April 24, 2008

5

Requests from Darlington

We broke Darlington’s requests into 2 phases. In phase 1 we made all the requested changes except

the removal of SAE units. In phase 2 we will remove the SAE units from the

datasheet.

Page 6: Summary of Changes for DATA 4.69 David Stevenson April 24, 2008

6

Changes to the Datasheet PrinterWe added a region field to support local customization

The Region field drives units and test condition wording changes. We have region fields on the data input side (DATA) and on the data publication side (Datasheet Printer).

Page 7: Summary of Changes for DATA 4.69 David Stevenson April 24, 2008

7

Requests for 2010 AutomotiveOriginal request from Automotive included:

– Add intake manifold to ambient temp delta.

– Add CAC to ambient temp delta.

– Add DEGR to ambient temp delta.

– Add max press drop across DEGR cooler.

– Add EGR flow pressure and temp values.

– Add max bending moment from front crankshaft values.

– Add max heat rejection from fuel value.

– Add full-on fan intake manifold temp value.

Page 8: Summary of Changes for DATA 4.69 David Stevenson April 24, 2008

8

Bug fixesWe also fixed the following bugs:

– Email notification that nothing changed.

– “Do you want to add comments?” when user already added comments.

“Behind the curtain” changes:– We can push data to Advisor in real time.

– We setup a full development system to test changes.

– Error checking implemented on automotive torque curves.

Page 9: Summary of Changes for DATA 4.69 David Stevenson April 24, 2008

9

Future Changes to DATA Changes for Darlington team:

– Removing SAE units (phase 2)– Other follow-up requests for DEP

Work with CIL on any changes they might need G-drive requests: new emissions datasheets, O&G

datasheet, natural gas datasheet Industrial Gas requests LDD requests Increase the speed of DATA Pushing data to Advisor twice per day

Bug Fixes:– Confidence levels– Array error

Page 10: Summary of Changes for DATA 4.69 David Stevenson April 24, 2008

10

Questions?

Page 11: Summary of Changes for DATA 4.69 David Stevenson April 24, 2008

11

Comments Reminder

Reminds users to enter comments but does not force them to.

Page 12: Summary of Changes for DATA 4.69 David Stevenson April 24, 2008

12

Email Notification of Changes

Asks users if they would like to send an email notifying the Chief Engineer and Application Engineer of changes.

The email describes which fields were changed by whom.