Notific Pro V7.2.0 Apk
Janie Mccorey
The Department of Buildings (DOB) will only issue a full demolition permit based on an Asbestos Assessment Report (ACP-5 Form) issued by a DEP-certified asbestos investigator with box 8d checked (which indicates that the entire building is free of asbestos containing material). The Asbestos Project Completion (ACP-21 Form) or Asbestos Project Conditional Completion (ACP-20 Form) will not be accepted as the basis for issuing a full building demolition permit. The only exceptions are a concurrent demolition and Abestos Technical Review Unit (A-TRU) permitted project, immediate emergency demolition, or emergency demolition.
The Statement of Agreement for filing ACP-5 Forms must have original signatures, dates and seal. If you are an employee of a company that has a New York State Department of Labor Asbestos Handling License number, you will be required to submit a letter of authorization from the company together with your forms. The form can either be mailed or hand delivered. Once the form is accepted, we will notify you via email and provide a temporary password with the link where you will electronically file your ACP-5 Form.
An asbestos project is defined as any form of work that will disturb more than 25 linear feet or more than 10 square feet of asbestos-containing material. When the work to be performed constitutes an asbestos project, the building owner or authorized agent must submit an asbestos project notification (ACP-7 Form) in ARTS at least one week in advance of the start of the work along with the associated filing fee (refer to 15 RCNY 1-25). An ACP-7 Form is valid for one year from the original date of filing.
The Asbestos Techinical Review Unit (A-TRU) permit ensures that workplace safety plans and tenant protection plans are prepared by a registered design professional and approved by DEP prior to initiating asbestos abatement activities.
An emergency asbestos project involves the removal, enclosure, encapsulation or cleanup of asbestos-containing material that was not planned but is undertaken when sudden unexpected event(s) result in a situation in which any delay in abatement would pose an immediate danger to public safety and health. When such an emergency asbestos project occurs, an emergency notification must be submitted through the ARTS-E File system. If the applicant does not have a valid ARTS E-File account, immediate telephone notification shall be made to 311 and include:
In accordance with 1-27 (c) Applicant must convert the emergency notification to an Asbestos Project Notification ( ACP-7 Form) through ARTS E-File as soon as possible, but no later than 48 hours after the project begins.
For demolitions ordered by the NYC Department of Buildings (DOB) Immediate Emergency Declaration (IED), Emergency Declaration (ED), Unsafe Building (UB) Violation or Building Owners Condemnation Letter:
A modification of or deviation from the information provided in an ACP-7 Form must be reported immediately in ARTS if the change refers to the asbestos abatement contractor, air monitoring firm, amount of asbestos-containing materials to be disturbed, the dates of the project, or the project location.
An application for any variance must be made directly to DEP through the ARTS E-File System at least two weeks before commencing work. Two types of variance applications exist: (1) a procedural variance which requires DEP approval; and (2) a 1-22b variance which requires DEP and DOB approval.
When the Department approves the application for a procedural variance the applicant must generate an Approval of Variance Letter (V2 form), by entering a start date in the ARTS E-File System, printing out and posting at the workplace a copy of the approved variance (V2 form), the Proposed Method of Work and the Layout Drawing.
When the Department approves the application for the 1-22b variance it will issue the Approval of Variance Letter (V5 form) in the ARTS E-File System. The applicant must submit the V5 form to DOB and post it at the workplace with the Phasing Letter and the Phasing Plan. Please note that a 1-22b variance includes all work areas on the ACP7 form. DOB will require an ACP21 form for DOB final project sign-off.
When any proposed work condition triggers a YES response in the Project Details Questions 27, 28 and/or 29 on the ACP-7 form, an ATRU Permit is required. A Registered Design Professional (RDP), authorized by the building owner or by an authorized agent, must prepare a Work Place Safety Plan (WPSP) for the applicant to submit through the Asbestos Report Tracking System (ARTS E- File ). The WPSP is thoroughly reviewed by the Asbestos Technical Review Unit (ATRU), comprised of two Department of Buildings (DOB) application compliance examiners and two DEP technical reviewers. To expedite the review and approval process, it is strongly recommended to submit the WPSP at least three to four weeks before the project start date.
As per Asbestos Rules and Regulations, Title 15, Chapter 1 of the Rules of the City of New York, simultaneous abatement and full/partial demolition projects require an approved Asbestos Technical Review Unit (A-TRU) permit and 1-22(b) variance prior to the start of demolition/abatement. Abating an entire building prior to the start of demolition may pose an undue hardship to a complex or multi-phased project. This allows applicants the flexibility to phase the project so a Department of Buildings permit can be issued before the completion of abatement activities with the following mandated stipulations:
Welcome to the Merative Social Program Management 7.0.2.0 release. Read this document to find important installation information, and to learn about product improvements and resolved issues in this release.
Ensure that you install the Merative Social Program Management Platform, application modules and program-based offerings in the correct sequence as described in the Overview of the installation steps topic.
If you are upgrading from a previous version, the Merative Social Program Management Upgrade Helper contains documentation and tooling to help you to upgrade your Merative Social Program Management application codebase and database to work with your new version of Merative Social Program Management. The Merative Social Program Management Upgrade Guide describes a recommended process for performing application and database upgrades. The Upgrade Helper contains tools to assist you with implementing the upgrade, including tooling to produce a schedule of required migrations for your upgrade, tooling to provide information about database schema changes and tooling to generate initial SQL scripts for applying changes to your database.
In association with the introduction of support for Websphere 9.0, support for WebSphere 8.0 has been dropped from the product. This now means that the supported WebSphere application server versions for the 7.0.2.0 release are WebSphere 8.5.5 and future fix packs and WebSphere 9.0 and future fix packs.
Support for the JAWS Screen reader Version 17 has been dropped.
The version of JAWS screen reader certified for use with the Social Program Management (SPM) application has been updated to 18. This new version of JAWS has been certified against Internet Explorer 11.
The base level of Java to be used for building and deploying the Merative SPM application has been increased to Java 1.8.
Therefore, the Java 1.6 and 1.7 versions should no longer be used for this purpose.
The Merative Data Server drivers for JDBC and SQLJ shipped as part of Server Development Environment for Java (SDEJ) have been updated from version 3.69 to 4.21.
As part of this change, the file names have changed as outlined below. Any custom references to these files should be updated to reflect these changes.
The Apache Commons FileUpload API released under the Apache License enables file upload capabilities in Java EE web applications. The version of Apache Commons FileUpload used in the Social Program Management (SPM) product has been upgraded from version 1.3.2 to 1.3.3.
The Social Program Management (SPM) Merative SPM application now supports WebSphere Application Server for z/OS version 9.0 and higher fix packs. Note the prerequisite minimum for this support is version 9.0.0.5.
The XML Server had previously been producing invalid PDF documents when there were multi-byte encoded characters in the input XML or XSL. This issue had been occurring due to the XMLServer transformer encoding which was not set by default.
User Interface Impact: No
Steps to Reproduce
Resolution
This issue has been fixed by changing the default encoding to UTF-8.
In some instances where large XML or XSL had been passed to the XMLServer for processing, the server had been throwing a StackOverflowException. To overcome this problem, a new property "java.thread.stack.size" has been introduced in the XMLServer ant script used to launch the XML Server, with a default value of -Xss4m. This value sets the Java thread stack size as 4 Mb to accommodate large XML or XSL files for processing. This size can be overridden by setting a different value for the "java.thread.stack.size" property using the "-Djava.thread.stack.size" build command syntax as shown below when launching the XMLServer:
Support for the Axis 1 web services infrastructure has been dropped from the product. Axis 2 is now the only supported infrastructure for defining and building web services. This has led to some of the following changes:
This dropping of support has also meant that any legacy Axis 1 web services which had been delivered in previous versions of the product have also been removed. These web services are listed below and it should be noted that Axis 2 equivalents were already in place in the product for these (typically with the same name but post-fixed with "WS2" to signify Axis 2 support):
Where a verification was configured on an evidence, and that evidence was brokered from the Person case to the Integrated Case and subsequently to the Product Delivery case. This resulted in the verification record being created twice. The consequence was that two verification items for the same evidence were present in the verification list page and the caseworker was required to verify each even though one was a duplicate.
User Interface Impact: No
Steps to Reproduce