Steps for third party software approval

Owned by Jennifer Mondragon (Unlicensed)
Last updated: Feb 01, 2012 by Larry Talley - NOAA FederalVersion comment
2 min read

How do I get my software approved?

Meet all technical specifications:

  • The elandings project provide technical specifications for software here (and we would link to our interface documented). Including specific XML format, ability to track changes, "makers mark" inside XML code to identify software.
  • Ability to ensure unique numbering of all landing and production reports and fish tickets.
  • The software must have all the fields for data entry and be designed to ensure that an operator can comply with the NMFS record keeping and reporting requirements as described in §679.5 and ADFG reporting requirements as described in 5AAC 39.130 (Gail can you confirm that this is the right link?)
  • The software must produce pdf formats of reports that can be printed and have time and date stamp and clearly identify whether the report has been submitted. If any changes are made to the data in the software, subsequent printed copies must clearly be identified as revised. The software must be designed to prevent the operator from overriding this feature.
  • The software must include sufficient data validation capability to prevent a submitter from accidentally transmitting a data file or printing PDF report that is incomplete or contains clearly erroneous data.
  • The software must ensure that all corrections to catch, species, delivery condition or poundage information be updated within the eLandings system.
  • The software must comply with all eLandings codes.
  • The software must use eLandings Product Recovery Rates for rounding to whole pounds as specified in Table 3 of 50 CFR Part 679.
  • The software must identify and report all overages using the established overage codes (I am not sure we have all overage codes online? Should we create a page? Or show the codes here?)

Ensure proper handling of data:

  • And here we would describe (or give a link) the test certification process. We would develop test scenarios and have them submit a report that meets that scenario. Then we would verify (either automatically or manually) that their submitted report matches the test result.

A vendor or developer wishing to have software approved must submit:

  1. Company, contact person, address, telephone number, and email for the company developing the software.
  2. Software name, type of software, & type of reports it supports (e.g. salmon landing reports, groundfish shoreside production reports, etc).
  3. A fully operational test copy of the software.
  4. Copies of all manuals and documentation for the software.
  5. User support plan (including ways to provide 24x7 support) and user support contact information.
  6. Back-up contingency plan if the software fails for any reason. Describe how users will be able to comply with record keeping and reporting and time-limit requirements. Describe how you ensure the data gets into elandings (e.g., how you process eLandings web service responses and/or submission receipts).