Results 1 to 10 of 10
  1. #1
    Join Date
    Sep 2010
    Location
    PNW
    Posts
    15,286
    Downloads
    0
    Uploads
    0

    ATF eForms Update

    Looks like some potentially good news for this update:



    ATF eForms Update



    The new eForms has been named the “Firearms and Explosives Application Module (FEAM)”. This name was selected to emphasis that FEAM is more than a “fillable form”. It is a business process module which will include at a minimum the functionality listed below:



    · Auto assignment – All applications will be immediately upon submission assigned to an examiner for processing.

    · Auto approval – Some forms, like the ATF Forms 2 and 3, if they meet certain pre-determined criteria will be automatically approved by the FEAM system upon submission.

    · Internal controls and performance measurement reporting – ATF has a full audit trail of every application received with date and time stamps for every step in the process. Digital signatures can be used to lock down portions of the form to ensure the security of the data and the authenticity of the submitter.

    · Improved business processes with automatic Records Management & Retention, as mandated by the Office of Management and Budget.

    · Electronic Signature (for submitter and ATF personnel) - provides enhanced authentication, validation and improves processing and approval.

    · Enhance Industry satisfaction: user-friendly interaction.

    · FEAM provides the Application Program Interface (APIs) needed to update the existing ATF back end databases, to allow for the batch submission of multiple forms using one computer session.

    · Improves efficiency for the Enforcement Programs and Services staff – Forms can be automatically routed, evaluated and tracked so that final determinations can be made in a consistent and expeditious manner.

    We had hoped to be able to present the first iteration of FEAM at the 2016 SHOT Show. ATF performed an assessment of what was contracted to be developed for FEAM and what the contractor planned to deliver. At the end of the assessment, all parties involved felt that the product outlined in the current contract did not fully provide all the functionality that we expected, or that the industry requested. For these reasons we decided that rather than to continue on the current course, we would take the steps listed below to ensure that FEAM is a worthwhile investment for both the industry and ATF:



    1. Curtail the current development effort.

    2. Determine what is needed to sustain the existing eForms system, until the full requirements for FEAM can be determined and developed.

    3. Make the necessary changes to eForms to stabilize the infrastructure with the ever-increasing user population.

    4. Determine if we can re-introduce the Form 3 to the current eForms, through load testing and other system validations.

    5. Perform an assessment of the ATF and industry requirements for FEAM.

    6. Secure required funding for a new FEAM initiative, based on the revised requirements.

    7. Restart the FEAM initiative, to include industry participation during the requirements gathering and testing processes.

    We look at this as only a minor delay. It is our intention to use this delay to acquire the tools and resources necessary to develop a product that will provide more functionality and a stable workflow process and infrastructure. All the work previously done on FEAM is not lost. It will be the foundation for the work that is yet to come. If you have any questions you can contact Lee Alston-Williams at lee.alston-williams@atf.gov.



    © 2016 Microsoft Terms Privacy & cookies Developers English (United States)

  2. #2
    Join Date
    Sep 2009
    Posts
    1,583
    Downloads
    0
    Uploads
    0
    Instant form 20? Yes, please.
    Will - Owner of Arisaka LLC - http://www.arisakadefense.com

  3. #3
    Join Date
    Jan 2012
    Location
    On the bank of the Mighty Muskingum
    Posts
    4,029
    Downloads
    6
    Uploads
    0
    Sounded to me like "Look at all this cool shit we were going to do for you, but we suck big, hairy, donkey balls, so we decided not to."
    There's no "Team" in F**K YOU!

  4. #4
    Join Date
    Nov 2010
    Location
    FL
    Posts
    2,643
    Downloads
    0
    Uploads
    0
    When I got the email today, I had to read it 3 times because it was so poorly written. But once past the .gov speak, it seems like they had a contract in place, the vendor didn't meet the specs of the contract, and now they need to do a re-compete to meet their specs, which resets the whole process. I'm guessing the ATF retained ownership of the programming, as opposed to the initial contracted company retaining the programming and the next contractor having to start from scratch.

    If that's the case, at least it wasn't a complete loss, but given how .gov contract timing works, this won't be complete any time soon.

  5. #5
    Join Date
    Sep 2014
    Location
    Texas
    Posts
    5,854
    Downloads
    2
    Uploads
    0
    Quote Originally Posted by gatordev View Post
    When I got the email today, I had to read it 3 times because it was so poorly written. But once past the .gov speak, it seems like they had a contract in place, the vendor didn't meet the specs of the contract, and now they need to do a re-compete to meet their specs, which resets the whole process. I'm guessing the ATF retained ownership of the programming, as opposed to the initial contracted company retaining the programming and the next contractor having to start from scratch.

    If that's the case, at least it wasn't a complete loss, but given how .gov contract timing works, this won't be complete any time soon.
    I read it two or three times myself. I consider myself marginally literate but damn.

  6. #6
    Join Date
    Sep 2015
    Location
    OKC
    Posts
    458
    Downloads
    5
    Uploads
    1
    From an IT perspective, when they throw out "stabilizing the infrastructure" and "load testing", it sounds like they threw a bunch of crap together at the last minute and found out the code fell on it's face. When you deal with shitty code, the only solution is to throw more hardware at it or rewrite it. It sounds like they did the right thing by halting the project before it went any further.

  7. #7
    Join Date
    Nov 2013
    Location
    Alaska
    Posts
    891
    Downloads
    1
    Uploads
    0
    And then there's this.. The Gun Collective posted this on FB
    ATF releases identifying information of 1400+ NFA item owners
    I haven't seen any other postings about it, but nuts if it is true
    -----------------------------------------------
    Jim
    "You can never have too many guns" - my wife's actual comment
    Alaska Fun

  8. #8
    Join Date
    Jan 2012
    Location
    On the bank of the Mighty Muskingum
    Posts
    4,029
    Downloads
    6
    Uploads
    0
    We should demand reparations. Hell, everybody else does!
    There's no "Team" in F**K YOU!

  9. #9
    Join Date
    Sep 2013
    Location
    WA
    Posts
    4,782
    Downloads
    1
    Uploads
    0
    My head is spinning....

  10. #10
    Join Date
    Sep 2013
    Location
    WA
    Posts
    4,782
    Downloads
    1
    Uploads
    0
    I forgot to add to my last post...was just wish they would fix the verbage here do we can file form 1's ..errr

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •