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. 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. This includes a brief, yet complete, description of the requirement. It must be stressed out that the requirements are system-wide: they refer to a feature of the system as a whole, without going into individual components. The wording within each requirement shows the requirement level, i.e., whether the requirement is mandatory, recommended, or optional. This follows the widely adopted meanings defined in RFC 2119 [1]. More specifically:
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. R1.1.4 The platform SHOULD implement communication between PALANTIR components with a lightweight message queue The AE relies on the Apache Xxxxx [3] software bus, which is the preferred choice within the PALANTIR project. For compatibility with existing open-source project, the AE uses the Redfish and Keylime APIs between the AE and the SCHI nodes.
Requirement Description. R1.1.4 The platform SHOULD implement communication between PALANTIR components with a lightweight message queue The FBM supports the Apache Xxxxx [3] software bus, which is the preferred choice within the PALANTIR project. For compatibility with existing open-source projects, the FBM relies on a SpringBoot implementation.
Requirement Description. (Include estimated program amount, period of performance, NSNs, and sources)
Requirement Description. Organizational Overview The organizational overview should consist of a succinct statement outlining corporate and business history including a general mission statement, the overall number of employees per position, and other general information about the firm. The Offeror must demonstrate that it possesses adequate staffing resources, financial resources and organization to perform the type, magnitude and quality of work specified herein this RFP, and demonstrate that the Offeror has been in continuous operation for at least the past five (5) years. In addition, the Proposer must provide a statement of previous experience that qualifies the Proposer to provide the Project Services. Proposer may include information not defined as required in this section but deemed necessary to fully understand the Proposer’s Company experience and organizational approach. Consultant’s Organizational Overview Response: Requirement Description: Company Experience
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)
