Certified Products Directory FAQ Page
Note:
Errata or addendums will be noted in the footer of each documents.
E.g. [E1A0] would mean that there is one errata published to the
original document.
Frequently
Asked Questions:
Categories
1)
CAR Errors
2)
Incorrect Header Data
3)
Errors in Product Line Options
4)
Errors in Public Search
5)
CPD Functions
6)
Accepting/Publishing Functions
7)
Errors with NFRC Reports
8)
Errors with Uploading Function
9)
Differences from CPD
1.0 to CPD 2.0
10)
Errors with Upload Spreadsheets
11)
Errors with Lab Report Test Tool
<Back
to CPD2.0 Information Page>
CAR
Errors
- Window
Type Skylight, TDD, and DASD, returns an error when running
a CAR.
- CARs
with incorrect expiration dates cannot be issued.
- When
recertifying a product line the simulation report number and
date are incorrect on the CAR.
- This
process now works properly when recertifying a product line.
The user can re-type the simulation report number and date
and reprint the CAR for product lines recertified that contained
the error.
- An
existing product line simulation report number is incorrect
on the CAR.
- The
report number is correct in the database but the CAR is printing
the old report number. Be sure to check for this when printing
a CAR.
- When
a report was published into the product line, all test validation
information was missing and a CAR will not print.
- IA
can re-type the test header detail information into the
product line details and print a CAR for product lines that
created an error. IA should follow steps in chapters 9 and
10 of the NFRC
IA CPD 2.0 User Manual.
- Existing
product lines from CPD 1.0 which are grouped with another product
line are missing test validate information and CAR's are unable
to print.
- IA
can re-type the test header detail information into the
product line details and print a CAR for product lines that
created an error.
<Back
to Top>
Incorrect Header Data
- Fields
that are not editable please contact NFRC staff to resolve on
a case-by-case basis.
- When
report was published into the product line, all test validation
information was missing and a CAR will not print.
- The
header information will have to be investigated / entered
on a case-by-case basis. Product lines without Test Validation
data will not generate a CAR. NFRC to work with Alpha team
to establish a protocol and prioritize solution.
- Existing
product lines from CPD 1.0 which are grouped with another product
line are missing test validate information and CAR's are unable
to be printed.
- Some
CPD 1.0 product lines validation groupings are not associated
in CPD 2.0, please provide NFRC Staff an issue form with
the correct validation grouping scenario which will be resolved
on a case-by-case basis.
- Report
Revision Dates not editable / removable by the IA.
- New
and recertification report types are requiring revision dates
to be entered when these should be initial report dates only.
- NFRC
to work with Alpha team to establish a protocol and prioritize
solution.
- The
expiration date field is incorrectly calculated from the recertification
date field.
- Expiration
Date field now calculates four years from validation test
date. The user can modify the expiration date in accordance
with NFRC
PCP-2008, section 5.6.
- Addendum
report changed certification dates and newest report number
isn't showing.
- Addendum
report types no longer change certification dates. The report
revision date and simulation report number fields can be
edited by the user. For further convenience, the report
number column is now visible in the product line details.
- Frame
Absorptance not filling in for product line header info for
CPD 1.0 and 2.0 uploads.
- The
user can edit the frame absorptance field. NFRC to work
with Alpha team to establish a protocol and prioritize solution.
- Comments
on Product Line can't be changed. I changed some comments and
saved them but the old comments are still there.
- Comments
in Product Line Detail can be replaced but not removed at
this time. Also, the maximum characters in this field is
512 characters but will be increased in future releases.
NFRC to work with Alpha team to establish a protocol and
prioritize solution.
- Test
report number is entered as a date.
- This
error existed in CPD 1.0. Test report number field cannot
be edited by the user, please provide an issue form and
contact NFRC staff to resolve on a case-by-case basis. NFRC
to work with Alpha team to establish a protocol and prioritize
solution.
- Simulation
Report Date is unable to be edited by IA.
- Simulation
report date field cannot be edited by user, please provide
an issue form and contact NFRC staff to resolve on a case-by-case
basis. NFRC to work with Alpha team to establish a protocol
and prioritize solution.
<Back
to Top>
Errors
in Product Line Options
- A
product line detail page is showing duplicate options for dual
Low-Es.
- The
product line detail may display duplicate option for dual
Low-Es; however, the CAR and public search displays options
with dual Low-Es properly. Please provide an issue form
for NFRC staff to resolve on a case-by-case basis. NFRC
to work with Alpha team to establish a protocol and prioritize
solution.
- "LowE
100(6)" shows in the LowE column.
- Please
provide an issue form for NFRC staff to resolve on a case-by-case
basis. NFRC to work
with Alpha team to establish a protocol and prioritize solution.
- After
publishing a report the Manufacturer Product Code column group
leader option's description is copied to all options within
the series grouping unless there are descriptions filled in
for each.
- Interim
suggestion: simulator to provide support to manufacturer
and fill in each line of the Manufacturer Product Code column
to avoid discrepancies. NFRC
to work with Alpha team to establish a protocol and prioritize
solution.
- A
revision inserted options in-between coded out options.
- Individual
product options cannot be inserted between coded out options.
An addendum is used when adding new options to the end of
existing groupings and a simple addendum is used to add
new options at the next available individual product option
in a product line.
- Some
or all of the options within a product line are missing.
- The
missing options will be compared to the CPD 1.0 product
lines which will be investigated / handled on a case-by-case
basis.
- There
are question marks (??) in product line options.
- The
question marks resulted from an incorrect or missing code
that existed in CPD 1.0. The “??” were inserted to make
the user aware during the migration process. Please provide
an issue form for NFRC staff to resolve on a case-by-case
basis.
- There
are duplicate individual options in a product line.
- Please
provide an issue form for NFRC staff to resolve on a one-on-one
basis.
<Back
to Top>
Errors
in Public Search
- A
product line is showing duplicate options for dual Low-Es.
- Public
search properly displays options with dual Low-Es listed
in the product line detail page. Please provide an issue
form for NFRC staff to resolve on a case-by-case basis.
NFRC to work with
Alpha team to establish a protocol and prioritize solution.
- "LowE
100(6)" shows in the LowE column.
- Please
provide an issue form for NFRC staff to resolve on a case-by-case
basis. NFRC to work
with Alpha team to establish a protocol and prioritize solution.
- There
are several duplicated product lines.
- In
some cases there were duplicate product lines in CPD1.0
and which were migrated into the CPD2.0. There were also
cases when a single product type was migrated erroneously
into 2.0 as a duplicate. Please provide an issue form for
NFRC staff to resolve on a case-by-case basis.
<Back to Top>
CPD
Functions
- Can
the back button feature be corrected or removed.
- NFRC
to work with Alpha team to establish a protocol and prioritize
solution.
- Receive
errors when trying to open a report, but can go back and open
it other times. This has happened half the time while trying
to view reports.
- This
issue was a common occurrence at the inception of CPD 2.0
due to resource issues. Many modifications have been implemented
to reduce this occurrence. If the error persists, please
contact NFRC Staff for assistance.
- Two
simulators are viewing Directory Code Listing but each document
states different revision dates.
- There
was a different listing on the Staging and Production servers,
which are current and both servers will be updated each
time a new code is entered in to the CPD2.0.
- CPD
Login denied access and left a message that an error has occurred.
There is then a link to compose an email and contact the support
team.
- Please
provide an issue form for NFRC staff to resolve on a case-by-case
basis.
NEW!
5. Why
do I get a blank test validate page when I use the hyperlink in
a validation email?
- Check
to make sure you have the whole link. If your email
has a broken link, copy the entire link into a browser to
view.
<Back to Top>
Accepting/Publishing
Functions
- Can
the Manufacturer Product Code field be opened to IA's during
the accept process?
- This
field is currently available at the product line detail
page and not at the upload page. NFRC to work with Alpha
team to establish a protocol and prioritize solution.
- When
IA selects "Fail Validation", two emails are generated
instead of one.
- NFRC
to work with Alpha team to establish a protocol and prioritize
solution.
- When
IA selects "Reject Report" when viewing full upload
data, no emails are generated.
- NFRC
to work with Alpha team to establish a protocol and prioritize
solution.
- Received
error when trying to enter get to the screen to enter the validation.
The next time it worked.
- This
issue was due to resource issues. Many modifications have
been implemented to reduce this occurrence. If the error
persists, please contact NFRC Staff for assistance.
- A
product line cannot be deleted by the IA.
- For
requests to delete product lines please provide an issue
form for NFRC staff to resolve on a case-by-case basis.
NFRC to work with
Alpha team to establish a protocol and prioritize solution.
- Opaque
options are unable to get through product line generation.
- IA
received an error message when accepting uploads.
- The
following requirements will eliminate 95% of the acceptance
issues: A simulation lab needs to setup the spreadsheet
in accordance with “NFRC
Simulation Report Format Checking Requirements.pdf”,
then run the spreadsheet through the Lab Report Test Tool
and the IA verifies that the spreadsheets are filled out
properly. If an issue occurs, please provide an issue form
for NFRC staff to resolve on a case-by-case basis.
- Accepting
2.0 report simple and complex revisions or addendums to existing
1.0 product lines create errors when trying to edit the group
leader option.
- This
is because of the differences between 1.0 and 2.0 numbering
system:
a. CPD 1.0 Group Leader starts at KML-N-24-00234
b. CPD 2.0 Group Leader starts at KML-N-24-00234-00001
This issue has been resolved and details are available in
(Information
on May 1, 2009 - Release 2.0.11.)
- TINT
CODE “CL” when published outputs as “LE".
- NFRC
to work with Alpha team to establish a protocol and prioritize
solution.
- Received
an error message after trying to generate a product line for
a recertification. The upload status states Published but the
Product Line Details are not updated.
- The
browser time-out was extended and a new background process
for archiving data was implemented, which increased the
efficiency of publishing the recertification of product
lines. NOTE: For large product lines (500+ spreadsheet rows)
the publishing of the product line will work in the background,
sometimes for 3 -5 hours, even though the web browser has
refreshed. For users that are accepting product lines of
this size, it is recommended to review the published product
line before publishing a product line of similar or greater
in size.
- After
accepting uploads the correct Simulation and Test data is not
showing up in the database.
- Please
submit issue form and upload spreadsheet to NFRC Staff.
- Error
received when trying to validate a product line when gas fill
was entered as decimals.
- Gas
fill must be a whole, non-decimal number. (i.e. 90)
- Product
line was grouped with wrong product line can an IA edit the
necessary fields?
- No,
please submit an issue form containing information about
the grouped product line to be completed by NFRC staff.
<Back to Top>
Errors
with NFRC Reports
-
The IA billing report is not correct,
it is listing all product lines rather than active.
- NFRC
to establish a protocol and priority.
Errors
with Uploading Function
- When
report is uploaded and it cannot be deleted (no delete button).
- There
are different scenarios when this issue occurs:
- The
lab code on the upload spreadsheet and the user that logged
into the system are different; therefore, the user does not
have the authority to delete the spreadsheet.
- The
"delete" button is now available for simulation
and validation after uploading and prior to the IA viewing;
however, after the IA reviews/rejects/accepts the upload,
the delete function is no longer an option.
- When
a report is uploaded for non-validation the selection box does
not hold the selection after submitting to the IA.
- This
issue will be investigated on a one-on-one basis. Please
submit issue form and upload spreadsheet to NFRC Staff.
- A
very large upload will not upload. It looks like a file size
issue.
- Received
an error when testing a report with the Lab Report Test Tool.
- Please
submit issue form and upload spreadsheet to NFRC Staff to
be resolved on a one-on-one basis.
<Back to Top>
Differences
from CPD 1.0 to CPD 2.0
-
CPD
1.0 read "Frame Emissivity" what was the purpose
of changing it to "Frame Absorptance" for CPD 2.0?
- Product
line did not migrate to CPD 2.0.
<Back
to Top>
Errors
with Upload Spreadsheets
- When
data checking a test report upload spreadsheet for an entry
door the following error message is shown: "The item in
this row cannot be both a window and a door." Once the
door codes are deleted then the data check works.
- NFRC
to work with Alpha team to establish a protocol and prioritize
solution.
- Doors
with opaque options are unable to pass Data Check on simulation
report upload spreadsheet.
<Back
to Top>
Errors
with Lab Report Test Tool
NEW!
1. I
am trying to perform the Lab Report Test on my upload for Film
Attachments Products and it gives an
error
and I cannot perform it, any ideas why?
- At this time,
Thermal Test spreadsheets and Film Attachment spreadsheets
are not part of the data checking requirement.
<Back
to Top>
<Back
to CPD2.0 Information Page>
|