Requirement Description. Cloud Development • Cloud configuration design documents Cloud configuration scripts Cloud Security design documents Automated software promotion scripts Software testing scripts Integration testing scripts Performance testing scripts User Interface Option • Scope and delivery requirements documents Core UI2 interfaces Message Bus software Related Services • Software testing reports Quality assurance reports ITHC reports.
Requirement Description. Project Management • The Contractor must ensure that all aspects of project management are carried out in accordance with and reflect Good Industry Practice. • As part if the Services, the Contractor must provide project management services in accordance with Good Industry Practice for the following phases; o Development; • The Contractor must provide such additional project management services as are required to implement each Variation. Risk Management • The Contractor should monitor and formally report to the DCC on Services risks and issues at regular and agreed intervals, through mechanisms agreed with the DCC, or, in the absence of any such agreement, in accordance with Good Industry Practice • The Contractor shall implement, operate and maintain a joint risk and issue management process, which shall include processes to identify, assess, monitor, mitigate, control risks and issues and to communicate such risks and issues to the DCC in accordance with Good Industry practice.
Requirement Description. 2. Identify the KPI(s) that will enable us to measure that we are accomplishing such requirement.
Requirement Description. Getting stakeholders approval Providing business case proposal to different stakeholders Creating database Receiving different database requirement from stakeholders (e.g. HL7, enrollment criterial from clinical trials)
Requirement Description. Creating application different tiers and application coding Creating different IT essential requirements to create these tiers and performing the coding process Launching application Launching the product on different software platforms (iOS, Android, PC, online database, website)
Requirement Description. 4 Create a viewable history to monitor the medication adherence of the population of senior patients with CHF through data visualization tools RISKS Risk Mitigation Senior patients will not adopt technology and app Health Plan will provide volunteers with discounted or cash back on monthly premiums based on health outcome improvement with use of app. Providers will fear workload increase Training and marketing on the public health impact and the visualization tools and benefits of management of patient groups will be provided. Workload will managed by care coordinators and EMR techs and providers will receive benefits of data visualization and ease of treatment management and ADE prevention. Patients will not want to be monitored Patients will be given training and demonstrations that show how this app will allow them to live more independently with minimal assistance from family members.
Requirement Description. (Include estimated program amount, period of performance, NSNs, and sources)
Requirement Description. T5 M Break out of scalability requirements The Contractor shall identify the mechanisms supported by their offering that will enable NYS to support the expected transaction volumes and identify how they can be extended to support the expected expansion of the user base of the RMS. Mechanisms and approaches identified must be consistent with the hardware and software requirements of NYS (as defined in RMS Attachment 3, Requirement T11. Provide a comprehensive description of how the proposed solution satisfies the requirement including technical specifications, capabilities, features, considerations, constraints, and limitations. Reference additional pages, if necessary. Indicate if the solution is offered or not offered → Offered Not Offered Niche Technology response: see our response material immediately following this table. Niche Technology response – Application Scalability Overview NicheRMS is designed to be scalable from very small systems (e.g., a demonstration or small training system on a single laptop) to a very large system capable of supporting the NYSP. The ability to support large transaction volumes is a major feature of our system’s design: our first major installation was for a multi-tenant system supporting more than 40 agencies and 8,000+ sworn officers. Support for requirements
Requirement Description. PP1 The Project Scope Description shall be a narrative which defines all work to be performed by the Contractor to meet the project deliverables and requirements of the RMS as stated within the content of this RFQ. Contractor’s PP1 Response: see our response material immediately following this table. Niche Project Methodology Niche has a standard project methodology for configuring and delivering our COTS police RMS product. It includes all key elements for planning, configuring, testing and implementing NicheRMS. Our approach has been developed and fine-tuned based on our experience with successful implementation of other large police RMS projects over the past 18+ years.
Requirement Description. PP2 The comprehensive Project Schedule shall include a detailed list of the tasks and the resources (e.g., Contractor and NYS), timeframes, all deliverables and dependencies for each task It is desirable that a fully functional records management system is implemented by the Contractor no later than 18 – 24 months following approval of the Contract; regardless, the Project Plan shall reflect the timing of the proposed implementation schedule For the purpose of this RFQ, fully functional means the following: • Containing the functionality as outlined in the contractor’s response to RMS Attachments 1, 2, 3, 4; • The mechanism to access legacy data for the Records Management System has been successfully implemented and the software has been delivered, installed and accepted for the test and production systems; • Acceptance and performance testing have been completed to successful resolution, with all requirements proven, and agreed upon features and interfaces have been implemented; and • The production system has been implemented and all Day 1 agreed-upon RMS functionality have been transitioned to the new RMS. Day 1 functionality will be negotiated and agreed upon with the tentative awardee. All critical milestones, deliverables, tasks, timeframes, dependencies and the schedules’ critical path shall be clearly delineated within the Project Schedule and the defined milestones and delivery dates. Each Contractor shall provide a comprehensive Project Schedule in Microsoft Project format. The Project Schedule shall identify the items mentioned previously for all phases of the project. The plan shall also include an MS Project view which clearly depicts a) critical path and b) major deliverables. Contractor’s PP2 Response: We have provided a comprehensive project schedule on a USB drive in Microsoft Project format, as requested (NYSP - Attachment G Project Plan Niche RMS 2018.08.17.mpp). For full details, see the Microsoft Project plan. Note we have also provided an Excel spreadsheet (NYSP - Attachment G Project Plan Niche RMS 2018.08.17.xlsx) with detailed notes on the tasks in the project plan. For convenience, we have replicated the crucial columns in a table in Appendix A on page 38.
