Exhibit_A_-_MODS_SERVICE_REQUEST_(MSR)_STATUS_CODES_AND_TYPES.pdf
PDF 22 KB Posted
- Attached to
- Medical Operational Data System (MODS)
- Solicitation number
- W81K04-18-R-0005
- Issued by
-
Department of the Army Medical Command
About this file
This document contains a draft request for proposal for the Medical Operational Data System (MODS) contract opportunity. The Department of the Army Medical Command seeks to award a competitive non-personal services contract to provide life cycle management services for the MODS, which is a government-owned, contractor-operated information system currently in the sustainment phase. The attached performance work statement outlines the roles and responsibilities of the contractor, including contract and program administration, inherently governmental functions, oversight, and assistance to government functional proponents. Interested parties are invited to provide feedback on the draft request for proposal and all attachments by January 22, 2018 to assist the government in requirements analysis and acquisition planning.
Exhibit A - MODS SERVICE REQUEST (MSR) STATUS CODES AND TYPES
View the file
Other files
Show all 12
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
MODS SERVICE REQUEST (MSR) STATUS CODES AND TYPES
Status Codes Description Applies To 0 – MSR Need Identified A Functional Proponent, MODS User, or another party has identified to the MODS PMO that there is a need to correct, change, or create a capability, requirement, or function in the system.
Government
1 – MSR in Review Status Contractor has the MSR to propose Technical Solution, identify price quote, and concur with RDD or identify alternate RDD.
Contractor
2 – MSR in Approval Status MODS PMO has received Contractor MSR reply.
Awaiting MODS TM review of Technical Requirements, Functional Approval of quote, CCB Approval if required, or KO MSO preparation.
Government
3 – MSO Issued and Contractor work On Schedule
KO has issued an MSO to the Contractor. Contractor can begin code work, test scripts, and IEEE documentation.
Includes Functional Testing after code completion. If problems occur, includes code corrections and re-test.
Includes Government review prior to formal Functional Acceptance.
Contractor
4 – MSO in work past RDD Same as #3 except RDD is past due. The original RDD remains unchanged unless the Contractor substantiates that the Government or an external third party is at fault for the work performance delay. If the COR validates that the delay is beyond the Contractor’s control, the KO will amend the MSO with a new RDD and MSO status reverts to code 3.
Contractor
5 – MSO Solution Technical Acceptance
Government is in receipt of: Source Code, IEEE Documents, Test Scripts, and Functional Acceptance document. Contractor has completed production deployment of the Solution to MODS Users. MODS PMO has signed the Technical Acceptance document. Includes Contractor invoice preparation.
Government
6 – MSO Invoiced Contractor has submitted into WAWF the final invoice for all work under the MSO. Awaiting Government payment.
Contractor
7 – MSO Paid The Contractor has invoiced all work under the MSO, and the Government has paid all MSO invoices.
Government
8 – MSR Cancelled MODS PM has cancelled an MSR prior to MSO release or has identified to the KO a released MSR that requires cancellation prior to RDD.
Government
9 – MSO Cancelled The KO has amended an issued MSO to cancel the order. Government
MSR Types Description
Labor – software modification 1 (SW1) Modernization/Development. Development of major upgrades increasing the performance envelope of existing systems, or the creation of new application / software capabilities. Technology refreshment that significantly changes the performance envelope of the end item is considered a SW 1. “Performance envelope” means the demonstrated capability of the application and associated software to perform its mission in relation to essential characteristics. SW1 are funded with RDTE appropriations.
Labor software modification 2 (SW 2) Technology Refresh. The intentional, incremental insertion of newer technology to improve reliability, improve maintainability, reduce cost, and/or add minor performance enhancement. Current level of service is being maintained but not significantly enhanced and changes are being made primarily to reduce technical or reduce operational cost. The insertion of such technology into end items as part of maintenance may be funded by Operation and Maintenance (O&M) appropriations.
Labor software modification 3 (SW3) Maintenance. The routine, recurring effort conducted to maintain an application at its intended capability or designed performance level.
Includes maintaining current level of services system / software modifications required to existing baseline applications within the scope of original intent, support of Government policy changes and day-to-day operations. Software releases categorized as iterations on the basic release and not involving significant performance improvements or extensive testing are considered maintenance and are funded by Operation and Maintenance appropriations. Minor improvements in software functionality which are accomplished during routine maintenance are also O&M funded.
Labor other services (SVC) Prepare Training Material, Train, Make Presentation, labor other than software
Travel (TVL) Travel costs allowed under DOD Joint Travel Regulation (JTR)
Other Direct Costs (ODC) Such as printing and conference internet services
File details come from the government source that posted it. Updated .