Attachment_5-Quality_Assurance_Surveillance_Plan_(6)_-QASP_final.doc
DOC document 207 KB Posted
- Attached to
- Range Managers Tool Kit
- Solicitation number
- M67854-14-R-7550
- Issued by
-
United States Marine Corps
About this file
Quality Surveillance Plan (QASP)
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Amendment_1-released.doc | DOC document | |
| Solicitation-Conformed_copy.doc | DOC document | |
| Attachment_7-Contractor-Employee-NDA_Template.doc | DOC document | |
| Attachments_3-4-Weapon_Danger_Zone_Tool_Vol._3-4.pdf | ||
| Attachment_8-_DD254.pdf | ||
| Attachment_9-Historical_RMTK_Information.xls | XLS spreadsheet | |
| Solicitation-release.doc | DOC document | |
| Attachments_1-2-Weapon_Danger_Zone_Tool_Vol._1-2.pdf | ||
| Attachment_6_Past_Performance_Questionnaire.docx | DOCX document |
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
M67854-14-R-7550
Attachment 5
RANGE AND TRAINING AREA MANAGEMENT DIVISION
USMC RANGE MANAGERS TOOL KIT SUSTAINMENT AND DEVELOPMENT
QUALITY ASSURANCE SURVEILLANCE PLAN
1. Purpose. This Quality Assurance Surveillance Plan (QASP) serves as the principal basis for assessing overall performance quality associated with this effort. This document will be used by the Government to assess the effectiveness of the Contractor’s management and technical services. This QASP provides the methodology by which the Contractor's performance will be monitored to determine compliance with established performance objectives and to establish performance benchmarks that ensure a quantifiable basis for measuring effectiveness. The plan is designed so that surveillance is limited to that which is necessary to verify the Contractor is performing management and technical services satisfactorily and relates directly in performance of the objectives delineated in the PWS.
2. Authority. Authority for issuance of this QASP will be provided under the resultant task order Inspection and Acceptance section, which provides for inspections and acceptance of the services and documentation called for in service contracts, to be executed by the Contracting Officer’s Representative (COR).
3. Scope.
a. The QASP is put in place to provide Government surveillance oversight of the contractor’s efforts to assure that they are timely, effective and are delivering the results specified in the task order.
b. The contractor’s performance will be evaluated by the Government as described in this QASP. An evaluation will be performed on each deliverable submission as cited under Section 5.0 – Deliverables within the PWS, as well as a single evaluation of the contractor’s overall performance at the completion of the base period and each of the four (4) option periods of the task order. The evaluation will encompass all work performed by the contractor at any time during the specific period of evaluation. Additional interim evaluations may be conducted at the discretion of the Government.
4. Government Resources
a. The following definitions for Government resources are applicable to this plan:
· Contracting Officer - A person duly appointed with the authority to enter into contracts and make related determination and findings on behalf of the Government. The PCO for the resultant task order will be identified in the Contract Administration section. Contracting Officers are designated via a written warrant, which sets forth limitations of authority. The Contracting Officer is the only person with the authority to make changes to the task order.
· Contracting Officers Representative (COR) - An individual appointed in writing by the PCO to act as their authorized representative to assist in administering the task order. The limitations of authority are contained in a written letter of appointment.
5. Responsibilities
a. The following Government resources shall have responsibility for the implementation of this QASP:
· Contracting Officer – The Contracting Officer ensures performance of all necessary actions for effective contracting, ensures compliance with the terms and conditions of the contract and safeguards the interests of the United States in the contractual relationship. It is the Contracting Officer that assures the Contractor receives impartial, fair and equitable treatment under the contract. The Contracting Officer is ultimately responsible for the final determination of the adequacy of the Contractor’s performance. The Contracting Officer provides QASP input to matters relating to Tables 3 and 4.
· Contracting Officer’s Representative (COR) – The COR is responsible for technical administration of the contract and assures proper Government surveillance of the contractor’s technical performance. The COR is not empowered to make any contractual commitments or to authorize any changes on the Government’s behalf. Any changes that the contractor deems may affect contract price, terms, or conditions shall be referred to the Contracting Officer for action.
6. Methods of QA Surveillance
a. QASP - The methods of surveillance listed below shall be used by the COR in the technical administration of this QASP.
b. Contractor Performance Assessment Report System (CPARS) – The market place for information technology, management, and operation / maintenance support services is very competitive. As such, the successful Offeror has a vested interest in the Government generated CPARS under this contract. Additionally, an evaluation using the CPARS format will be performed at the end of each year of performance. This QASP will be used to address the quality of product or service, schedule, cost control, business relations, and management. Since this information may affect future source selections throughout the Department of Defense (DoD) and the continuation of the contract, the annual Government assessment will be used appropriately as an additional performance oversight and communication tool with the QASP.
7. Surveillance.
a. The tables below set forth the performance ratings, standards, incentives, and surveillance methods of the contractor that shall be provided to the COR at the end of each surveillance period.
b. Performance Ratings: The Government will evaluate the contractor’s performance of the Performance Work Statement (PWS) for the task order, and the COR will assign one of the following standard ratings:
Table 1: Overall Performance Ratings (Using CPARS Ratings)
| Overall Performance Rating |
| Standard |
| Exceptional (Blue) |
| Performance exceeds contractual requirements to the Government's benefit. |
| Very Good (Gold) |
| Performance meets contractual requirements and exceeds some to the Government's benefit. |
| Satisfactory (Green) |
| Performance meets all contractual requirements. |
| Marginal (Yellow) |
| Performance does not meet some contractual requirements. The element being assessed reflects a serious problem for which the contractor has not yet implemented satisfactory corrective actions. |
| Unsatisfactory (Red) |
| Performance does not meet contractual requirements and recovery is not likely in a timely manner. Contractor's corrective actions to date are ineffective. |
(a) Performance Evaluation Criteria. The contractor’s performance will be evaluated using the criteria and standards provided for each objective, and identified in Tables 2 and 4.
(b) Organization. Training and Education Command, Range and Training Area Management, Quantico VA.
(c) This performance evaluation does not replace any other requirement for evaluating contractor performance that may be required by this contract such as a CPARS report.
TABLE 2: TASK PERFORMANCE EVALUATION CRITERIA AND STANDARDS
| CRITERION |
| UNSATISFACTORY |
| MARGINAL |
| SATISFACTORY |
| VERY GOOD |
| EXCEPTIONAL |
| Task Performance |
| Work product fails to meet Acceptable Quality Levels (AQLs) defined in Performance Requirements Summary Table, Table 3 |
| Work product occasionally fails to meet AQLs defined in Performance Requirements Summary Table, Table 3 |
| Work product routinely meets AQLs defined in Performance Requirements Summary Table, Table 3 |
| Work product always meets and occasionally exceeds AQLs defined in Performance Requirements Summary Table, Table 3 |
| Work product exceeds AQLs defined in Performance Requirements Summary Table, Table 3 |
| Staffing |
| Contractor provides marginally qualified or unqualified personnel. Lapses in coverage occur regularly. |
| Contractor provides marginally qualified personnel. Lapses in coverage occur more than occasionally |
| Contractor provides qualified personnel. Lapses in coverage may occasionally occur and are managed per contract policy. |
| Contractor provides a mix of qualified and some highly qualified personnel. Lapses in coverage occur infrequently and are managed per contract policy. |
| Contractor provides highly qualified personnel. Contractor reassigns personnel to ensure proper coverage. Actual lapses in coverage occur very rarely, if ever, and are managed per contract policy. Contractor ensures staff training remains current. |
| Timeliness |
| Contractor frequently misses deadlines, schedules, or is slow to respond to Government requests or is non-responsive to Government requests. |
| Contractor occasionally misses deadlines, schedules or is slow to respond to Government requests or is occasionally non-responsive to Government requests. |
| Contractor routinely meets deadlines, schedules, and responds quickly to Government requests. |
| Contractor routinely meets deadlines and schedules and occasionally delivers early and responds immediately to Government requests. |
| Contractor routinely delivers ahead of deadlines, schedules, and responds immediately to Government requests. |
| Customer Satisfaction |
| Fails to meet customer expectations |
| Contractor occasionally fails to meet customer expectations |
| Meets customer expectations. |
| Routinely meets or occasionally exceeds customer expectations. |
| Exceeds customer expectations. |
Table 3: PERFORMANCE REQUIREMENTS SUMMARY TABLE
| Performance-based Task |
| Indicator |
| Standard |
| Acceptable Quality Level (AQL) |
| Surveillance Method |
| 4.3.1.1 RMTK Systems Support |
| Incorporation of MCO new/updated data into the RMTK |
| Contractor incorporates new/updated MCO data as required by the PWS. |
| MCO technical data is incorporated within 360 days and reviewed monthly upon receipt of data from the COR, with all of the data elements required by the PWS as provided by the COR. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval. |
Threshold = 98% approved on initial submission Objective = 100% approved on initial submission
100% Inspection: All deliverables will be reviewed for required content.
| 4.3.1.2 RMTK Systems Support |
| RMTK suite of tools accurately defines the operational capability of the various danger zones |
| Danger zones match technical data associated with the weapon on an operational training range. |
| Approved danger zones are rendered and match the weapons technical data associated with the weapon. |
Threshold = 100% Objective = 100% 100% inspection and approval of all danger zones.
| 4.3.1.3 RMTK Systems Support |
| Hazards associated with danger zones have horizontal and vertical components that are depicted and can be queried |
| Contractor ensures that danger zone hazard areas are rendered and able to be queried in the RMTK tables. |
| All danger zone hazards have horizontal and vertical components depicted and able to be queried in the RMTK, reviewed monthly. |
Threshold = 100%
100% inspection and approval of all danger zone hazards in the tabular data.
4.3.1.4 RMTK Systems Support
| Provide all items created, generated or produced for the RMTK tools |
| Provide yearly, all items created, generated, produced or used to develop the RMTK suite of tools including, but not limited to, all algorithms or “pseudo” code, class diagrams, use cases, and all non-executable (source code) and executable code (object code) |
| Provide on a DVD(s) the data at the end of the contract year |
Threshold = 40 days prior to end of PoP DVD (s) are able to be inserted in a computer and data assessed.
| 4.3.1.5 RMTK Systems Support |
| Incorporate all developed foreign danger zones into RMTK FDZ |
| Ensure that all newly developed FDZ data is incorporated into the RMTK |
| All foreign danger zones are incorporated into the FDZ tool. |
Threshold = 100%
100% inspection and approval of all danger zones
| 4.3.1.6 RMTK Systems Support |
| Implement range design plans into the RMTK |
| Range designs are incorporated into the RMTK |
| All range designs are incorporated into the RMTK. |
Threshold = 100%
Review of the RMTK to ensure that data has been incorporated
| 4.3.1.7 RMTK Systems Support |
| Test plans for both the desktop and web are developed and executed |
| Test plans for the desktop and the web RMTK tools are developed and executed for MCRTAMS, Range Facilities Management Support System (RFMSS), the Service departments within DOD |
| Test plans are provided and utilized for the RMTK tools. |
Threshold = 100%
Test plans are reviewed and approved
| 4.3.1.8 RMTK Systems Support |
| Troubleshoot errors with GIS applications/extensions. |
Errors in GIS applications/extensions.
are investigated All COR provided information is investigated and feedback provided, reviewed monthly.
Threshold = 48 hours Objective = 5 working days RMTK errors are reviewed in the monthly status report
| 4.3.1.9 RMTK Systems Support |
| GIS data is developed for MCRTAMS |
| GIS data developed for use on MCRTAMS |
| GIS data developed for MCRTAMS and deliverables are received within 360 days upon receipt from the COR and the data developed is approved by the COR on initial submission. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval, reviewed monthly. |
Threshold: 360 working days
Objective: 20 working days Monthly status report are reviewed for development status
| 4.3.1.10 RMTK Systems Support |
| Provide RMTK documentation |
| Documentation concerning RMTK data quality, RMTK applications, and GIS data is provided |
| Deliverables are received within 360 days upon receipt from the COR and the data developed is approve d by the COR on initial submission NS reviewed monthly. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval. |
Threshold = 98% approved on initial submission
100% inspection
| 4.3.1.11 RMTK Systems Support |
| Maintain and update RMTK web based certification system on MCRTAMS |
| Data on MCRTAMS for the range certification module is maintained and updated |
| All data pertaining to MCRTAMS based range certification is maintained and updated, reviewed monthly. Deliverables are received within 360 days upon receipt from the COR and the data developed is approve d by the COR on initial submission. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval. |
Threshold = 98% approved on initial submission
100% inspection for inclusion of data
| 4.3.1.12 RMTK Systems Support |
| Web based range certification database is maintained and updated |
| Database is updated and maintained |
| Deliverables are received within 360 days upon receipt from the COR and the data developed is approved and reviewed monthly by the COR on initial submission. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval. |
Threshold = 98% approved on initial submission
100% Inspection: All deliverables will be reviewed monthly for required data.
| 4.3.1.13 RMTK Systems Support |
| Maintain and update PSDZ tool |
| Data is incorporated into the PSDZ tool as provided by the COR |
| PSDZ data incorporated into PSDZ and deliverables are received within 360 days upon receipt from the COR and the data developed is approved by the COR on initial submission, and reviewed monthly. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval. |
Threshold: 360 working days
Objective: 15 working days 100% Inspection: All deliverables will be reviewed monthly for required data.
| 4.3.1.14 RMTK Systems Support |
| Maintain and update LRMT |
| Data and methodologies for the LRMT are incorporated as provided by the COR |
| LRMT data and methodologies are incorporated into LRMT and deliverables are received within 360 days upon receipt from the COR and the data developed is approved by the COR on initial submission and reviewed monthly. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval. |
Threshold: 360 working days
100% Inspection: All deliverables will be reviewed monthly for required content.
| 4.3.1.15 RMTK Systems Support |
| Maintain and update ETR tool |
| Explosives data is incorporated into the ETR tool as provided by the COR |
| Explosives data and methodologies are incorporated into ETR tool and deliverables are received within 360 days upon receipt from the COR and the data developed is approved by the COR on initial submission and reviewed monthly. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval. |
Threshold: 360 working days
100% Inspection: All deliverables will be reviewed monthly for required content.
| 4.3.1.16 RMTK Systems Support |
| Maintain and update Noise tool |
| Noise data is incorporated into the noise tool as provided by the COR |
| Noise data and methodologies are incorporated into noise tool and deliverables are received within 360 days upon receipt from the COR and the data developed is approved by the COR on initial submission and reviewed monthly. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval. |
Threshold: 360 working days
100% Inspection: All deliverables will be reviewed monthly for required content.
| 4.3.1.17 RMTK Systems Support |
| Maintain and update ORAH tool |
| Temporary storage of explosives data is incorporated into the ORAH tool as provided by the COR |
| Temporary storage of explosives data are incorporated into ORAH tool and deliverables are received within 360 days upon receipt from the COR and the data developed is approve d by the COR on initial submission and reviewed monthly. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval. |
Threshold: 360 working days
100% Inspection: All deliverables will be reviewed monthly for required content.
| 4.3.1.18 RMTK Systems Support |
| Maintain and update RCT |
| Range clearance and munitions data is incorporated into the RCT as provided by the COR |
| Range clearance data and munitions information are incorporated into RCT and deliverables are received within 360 days upon receipt from the COR and the data developed is approved by the COR on initial submission and reviewed monthly. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval. |
Threshold: 360 working days
100% Inspection: All deliverables will be reviewed monthly for required content.
| 4.3.1.19 RMTK Systems Support |
| Maintain and update RDT |
| Range design information are incorporated into the RDT as provided by the COR |
| Range design data are incorporated into RDT and deliverables are received within 360 days upon receipt from the COR and the data developed is approved by the COR on initial submission and reviewed monthly. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval. |
Threshold: 360 working days
100% Inspection: All deliverables will be reviewed monthly for required content.
| 4.3.1.20 RMTK Systems Support |
| Maintain and update RDAP |
| Range development and planning information are incorporated into the RDAP as provided by the COR |
| Range development and planning information and deliverables are received within 360 days upon receipt from the COR and the data developed is approved by the COR on initial submission and reviewed monthly. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval. |
Threshold: 360 working days
100% Inspection: All deliverables will be reviewed monthly for required content.
| 4.3.1.21 RMTK Systems Support |
| Maintain and update TEPS |
| RMTK information and data as provided by the COR are incorporated into the Training Event Planning System and displayed in the GIS environment |
| TEPS and deliverables are received within 360 days upon receipt from the COR and the data developed is approved by the COR on initial submission reviewed monthly. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval. |
Threshold: 360 working days
100% Inspection: All deliverables will be reviewed monthly for required content.
| 4.3.1.22 RMTK Systems Support |
| Design and consolidate installation map viewers on MCRTAMS |
| Web map viewers on MCRTAMS are designed and incorporated into the existing MCRTAMS framework as provided by the COR |
| Web map viewers are received within 360 days upon receipt from the COR and the data developed is approved by the COR on initial submission reviewed monthly. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval. |
Threshold: 360 working days
Objective: 45 working days 100% Inspection: All deliverables will be reviewed monthly for required content.
| 4.3.1.23 RMTK Systems Support |
| Maintain and update MCRTAMS of web SDZ, ETRT, and WDZ |
| Web enabled danger zone tools are able to run on MCRTAMS and are compatible with desktop versions |
| Web enabled danger zone tools are received within 360 days upon receipt from the COR and the data developed is approved by the COR on initial submission reviewed monthly. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval. |
Threshold: 360 working days
Objective: 180 days 100% Inspection: All deliverables will be reviewed monthly for required content.
| 4.3.1.24 RMTK Systems Support |
| Implement Government database into FDZ |
| Individual foreign danger zones are incorporated into FDZ as provided by the COR |
| Foreign danger zones are received within 360 days upon receipt from the COR and the data developed is approved by the COR on initial submission reviewed monthly. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval. |
Threshold: 360 working days
Objective: 45 working days 100% Inspection: All deliverables will be reviewed monthly for required content.
| 4.3.1.25 RMTK Systems Support |
| Implement, maintain and update the MCRTAMS based RCT |
| RCT is MCRTAMS based and will function as does the desktop based RCT |
| MCRTAMS based RCT data are received within 360 days upon receipt from the COR and the data developed is approve d by the COR on initial submission reviewed monthly. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval. |
Threshold: 360 working days
100% Inspection: All deliverables will be reviewed monthly for required content.
| 4.3.1.26 RMTK Systems Support |
| Provide a baseline release of all RMTK tools |
| Yearly provide a release of RMTK tools |
| Provide RMTK tools on a yearly schedule for final release. |
Threshold : Within 5 days of tool release timeline
Objective: Within 2 days of tool release timeline 100% Inspection: All deliverables will be reviewed for required content.
| 4.3.1.27 RMTK Systems Support |
| Perform regression testing of the RMTK and provide results to the COR |
| When new builds are tested perform regression testing on the RMTK |
| Provide regression testing results for new builds of RMTK reviewed monthly. |
Threshold : Within 5 days of tool release timeline
Objective: Within 2 days of tool release timeline 100% Inspection: All deliverables will be reviewed for required content.
| 4.3.1.28 RMTK Systems Support |
| Ensure RMTK outputs are in a standard format compatible with RFMSS, PFPS/AMPS, Army mapper |
| Outputs are consistent and able to be utilized by RFMSS, PFPS/AMPS, Army mapper |
| Outputs of RMTK are able to be consumed with no data changes, reviewed monthly. |
Threshold = 98% consumed with secondary submission Objective = 100% consumed on initial submission Planned sampling
| 4.3.2.1 RMTK Recommendations and Strategies. |
| Provide best practice way ahead for the RMTK suite of tools concerning database versioning or type |
| Provide recommendations as to best practices for the RMTK suite of tools centering on database versioning and types. Examine industry standards and upcoming changes and programs for use or change |
| Recommendations for RMTK changes are provided quarterly during the PMR’s and in the monthly status report |
Threshold: Monthly Objective: Monthly 100% Inspection: All deliverables will be reviewed for required content in either quarterly PMR or MSR.
| 4.3.2.2 RMTK Recommendations and Strategies |
| Ensure that the RMTK suite of tools are prepared for upcoming changes in operating systems and ESRI base versioning |
| Provide recommendations for best practices centering on upcoming operating systems changes and ESRI base version changes and how they may impact the RMTK suite of tools. Provide a succession plan and to allow the government to plan version changes of the RMTK suite |
| Recommendations for RMTK changes are provided quarterly during the PMR’s and in the monthly status report. |
Threshold: Monthly
100% Inspection: All deliverables will be reviewed for required content in either quarterly PMR or MSR.
| 4.3.2.3 RMTK Recommendations and Strategies |
| Provide best practice way ahead for the RMTK suite of tools concerning GIS best practices in the GIS community |
| Provide recommendations as to best practices for the RMTK centering on GIS community process improvements. Examine the GIS industry for improvements that can be implement in RMTK |
| Recommendations for RMTK changes are provided quarterly during the PMR’s and in the monthly status report |
Threshold: Monthly
100% Inspection: All deliverables will be reviewed for required content in either quarterly PMR or MSR.
| 4.3.2.4 RMTK Recommendations and Strategies |
| Determine and propose schedule and performance parameters for danger zones |
| Provide a proposed WDZ schedule and performance parameters associated with the development of the danger zone at the PMR |
| Schedule and performance parameter recommendations are provided to the Services |
Threshold: Quarterly
100% Inspection: All deliverables will be reviewed for required content in either quarterly PMR or MSR.
| 4.3.3.1 MCRTAMS RMTK systems support |
| Maintain and update RMTK interface modifications for MCRTAMS |
| Maintain and update RMTK interface incorporated within MCRTAMS |
| MCRTAMS based RMTK modifications are received within 360 days upon receipt from the COR and the data developed is approved by the COR on initial submission. Any rejected deliverables are corrected and reviewed monthly and resubmitted within 5 working days for COR approval. |
Threshold: 360 working days
100% Inspection: All deliverables will be reviewed monthly for required content.
| 4.3.3.2 MCRTAMS RMTK systems support |
| Update the web enabled versions of ETR, SDZ, and WDZ in conjunction with the desktop based versions |
| Updated ETR, SDZ, and WDZ versions are in line with the desktop based versions of the tools |
| RMTK modifications are within 360 days upon receipt from the COR and the data developed is approved by the COR on initial submission. Any rejected deliverables are corrected and reviewed monthly and resubmitted within 5 working days for COR approval. |
Threshold: 360 working days
100% Inspection: All deliverables will be reviewed monthly for required content.
| 4.3.3.3 MCRTAMS RMTK systems support |
| Engineer tools to run in current and planned versions of MCRTAMS |
| Updated and current versions will run on MCRTAMS |
| RMTK modifications are received within 360 days upon receipt from the COR and the data developed is approved by the COR on initial submission and reviewed monthly. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval. |
Threshold: 360 working days
Objective: 180 working days 100% Inspection: All deliverables will be reviewed monthly for required content and functionality.
| 4.3.3.4 MCRTAMS RMTK systems support |
| Engineer tools to run in current and planned version of ESRI software established on MCRTAMS |
| Tools will be engineered to run in the current and planned version of ESRI software on MCRTAMS |
| Tools are received within 360 days upon receipt from the COR and the data developed is approved by the COR on initial submission and reviewed monthly. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval. |
Threshold: 360 working days
100% Inspection: All deliverables will be reviewed monthly for required content and functionality.
| 4.3.3.5 MCRTAMS RMTK systems support |
| Engineer all RMTK tools to run in current and planned version of ESRI software established on Citrix |
| RMTK tools will be engineered to run in the current and planned version of ESRI software on Citrix |
| Tools are received within 360 days upon receipt from the COR and the data developed is approved by the COR on initial submission and reviewed monthly. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval. |
Threshold: 360 working days
100% Inspection: All deliverables will be reviewed monthly for required content and functionality.
| 4.3.4.1 WDZ tool support |
| Provide data cubes for specific aircraft |
| Data cubes are provided for aircraft for inclusion in the WDZ tool |
| WDZ is able to consume data cubes with no errors. |
Threshold = 99% consumed with secondary submission Objective = 100% consumed on initial submission
100% Inspection: All deliverables will be reviewed for required content and functionality.
| 4.3.4.2 WDZ tool support |
| Provide an Integrated Master Schedule (IMS) of WDZ priorities established by the multi-service CMWG quarterly |
| The schedule for WDZ priorities established by the multi-service CMWG quarterly is provided at the PMR |
| Recommendations for the WDZ schedule predicated on government are provided during the PMR’s or in the monthly status report |
Threshold: Quarterly
100% Inspection: All deliverables will be reviewed for required content and functionality.
| 4.3.4.3 WDZ tool support |
| Matrix of WDZ dependencies provided |
| WDZ development dependencies matrix is developed and provided during the PMR |
| WDZ development dependencies matrix is provided during the PMR’s or in the monthly status report |
Threshold: Monthly
100% Inspection: All deliverables will be reviewed for required content and functionality.
| 4.3.4.4 WDZ tool support |
| Provide verification and validation of WDZ’s |
| Provide the verification and validation of WDZ’s developed and implemented during the contract year |
| V and V provided monthly and at the end of the contract year |
Threshold = Annually and within 30 days of PoP 100% Inspection: All deliverables will be reviewed monthly for required content and functionality.
| 4.3.4.5 WDZ tool support |
| Quality control procedure test plans are provided |
| Quality control and procedure test plans are provided |
| Quality control and procedure test plans are provided at the end of the contract year |
Threshold = Annually and within 30 days of PoP 100% Inspection: All deliverables will be reviewed for required content and functionality.
| 4.3.4.6 WDZ tool support |
| Integrate new weapons data, WDZs, modules, or models |
| WDZ tool database, data cubes modules models are updated when new weapons data is provided by the government |
| Updated WDZ tool provided and reviewed monthly. |
Threshold: 270 working days
100% Inspection: All deliverables will be reviewed for required content and functionality.
| 4.3.4.7 WDZ tool support |
| Gather WDZ dispersion data |
| Gather data from DoD departments and approved foreign allies. When data is insufficient to calculate a WDZ develop methodology to derive a new WDZ and provide to COR. |
| Updated WDZ tool deficiencies and methodologies document provided and reviewed monthly. |
Threshold: 90 working days
Objective: 60 working days 100% Inspection: All deliverables will be reviewed for required content and functionality.
| 4.3.4.8 WDZ tool support |
| Track WDZ problems, resolutions and suggestions |
| Track problems, resolutions and suggestions with their recommendations, courses of actions, and time constraints. Present contractor found problems, resolutions and suggestions. |
Provide WDZ issues and reconciliation at each PMR (quarterly) Threshold : Quarterly
Objective: Quarterly 100% Inspection: All deliverables will be reviewed for required content and functionality.
| 4.3.4.9 WDZ tool support |
| Acknowledge government communication |
| Contractor shall acknowledge government communication |
| Send response via phone or email |
Threshold: 5 working days
Objective: 3 working days Planned sampling
| 4.3.4.10 WDZ tool support |
| Update and maintain WDZ tool desktop |
WDZ tool information as provided by the COR is incorporated into an updated desktop WDZ tool.
WDZ data is incorporated into WDZ tool and deliverables are received within 360 days upon receipt from the COR and the data developed is approve d by the COR on initial submission and reviewed monthly. Any rejected deliverables are corrected and resubmitted within 5 working days for COR approval.
Threshold: 360 working days
100% Inspection: All deliverables will be reviewed for required content.
| 4.3.4.11 WDZ tool support |
| Perform regression testing of the WDZ |
| Submit regression test plans to the COR |
| Provide regression testing results for new builds of WDZ. |
Threshold : Quarterly
100% Inspection: All deliverables will be reviewed for required content.
| 4.3.4.12 WDZ tool support |
| WDZ’s are depicted in 3 dimensions for single and composite for multi weapon releases |
| WDZ’s developed generate three-dimensional WDZs for single and composite multi-weapon releases including: (1) terrain profile, (2) weapon trajectories, (3) broached/porpoising ordnance, ricochets, (4) fragmentation, and (5) explosive effects that include the capability of using terrain to mitigate the effects of broaching/porpoising or ricochet |
| All WDZ hazards have horizontal and vertical components depicted and factors that affect the danger zone are included in the danger zones. |
Threshold = 100%
100% inspection and approval of all WDZ hazards and weapons effects
| 4.3.4.13 WDZ tool support |
| New WDZs are developed and integrated into baseline |
| New WDZs are developed and integrated into the baseline as provided by the COR |
| All WDZ data is integrated into WDZ. |
Threshold = 100%
100% inspection and approval of all WDZ hazards and weapons effects
| 4.3.4.14 WDZ tool support |
| Provide data cubes |
| Data cubes that define weapon trajectories and ricochets are derived from Circular Error Probable for Training (CEPt) Polygons, as well as incorporating range scores and Joint Munitions Effectiveness Manual (JMEM) Air-to-Ground Weaponeering System (JAWS) JMEM tables |
| Data cubes are developed and provided for the tool. |
Threshold = 100%
100% inspection and approval of all WDZ data cubes
| 4.3.4.15 WDZ tool support |
| Design documentation and methodologies provided used to develop data cubes |
| Contractor provides updated documentation and methodologies used to develop or modify data cubes |
| Updated documentation is provided or information updated on methodologies used to develop or modify data cubes |
Threshold : Within 5 days of new or updated methodologies Objective: Within 2 days of new or updated methodologies 100% inspection and approval of all data
| 4.3.5.1 General |
| Develop WBS for all tasks |
| Contractor develops a WBS for all tasks |
| WBS is developed and delivered |
Threshold : Within 5 days of new or updated methodologies
Objective: Kickoff and as required wit updates 100% inspection and approval of all data
| 4.3.5.2 General |
| PMR/CMWG |
| Contractor participates and takes notes for PMR/CMWG |
| Conduct PMR/CMWG |
Threshold : Quarterly
100% inspection and approval of all notes
| 4.3.5.3 General |
| Update RMTK help files |
| RMTK help files and glossary are updated |
| Help files are updated |
Threshold : Quarterly
100% inspection and approval of all data
| 4.3.5.4 General |
| Ensures RMTK passing appropriate DISA/STIG |
| Will ensure that the RMTK is developed with passing DISA/STIG accreditation procedures. |
| Passes STIG/DISA requirements and tools can be utilized on Government systems |
Threshold : Quarterly
100% inspection and approval of all data
| 4.3.5.5 General |
| Secure configuration control of code |
| Ensure that RMTK application code has secure configuration control |
| The contractor ensures configuration control of code and is secure |
Threshold = 100% 100% inspection and approval of all data and methods
| 4.3.5.7 General |
| WDZ design documentation |
| WDZ design documentation volumes I-VI are updated with any new or updated information |
| WDZ design documentation volumes 1-6 are updated as required |
Threshold : Quarterly
100% inspection and approval of all data
| 4.3.5.8 General |
| Monthly Status report |
| Monthly status reports |
| Monthly status reports are provided |
Threshold: Provided by the 5th of each month
Objective: Provided by the 7th of each month.
100% inspection and approval monthly report
| 4.3.6 Help Desk |
| Provide Tier 3 tech support to select COR designated personnel only |
| Provide help desk tier 3 high level tech support from 0800-1700 EST |
| Provide tech support and provided tech support information in monthly status reports and quarterly PMR’s |
Threshold: 3 working days response
Objective: 1 working day response 100% inspection and approval of all data
| 4.3.7.1 WDZ training |
| Schedule, plan, and conduct users training |
| Schedule, plan, and conducts users training using COR provided course material |
| Training is conducted and executed as scheduled |
Threshold : Annually, on time as scheduled
Objective: Annually, on time as scheduled Customer satisfaction
| 4.3.8.1 Provide FMS support |
| Foreign Small arms danger zones are provided |
| Small arms danger zones are developed and then included in the FDZ tool |
| Updated danger zones are provided in FDZ tool |
Threshold : 120 days
Objective: 90 days 100% inspection and approval of all data
| 4.3.8.2 Provide FMS support |
| Foreign Tank and fighting vehicle danger zones are provided |
| Tank and fighting vehicle danger zones are developed and then included in the FDZ tool |
| Updated danger zones are provided in FDZ tool |
Threshold : 120 days
100% inspection and approval of all data
| 4.3.8.3 Provide FMS support |
| Foreign Grenade danger zones are provided |
| Grenade danger zones are developed and then included in the FDZ tool |
| Updated danger zones are provided in FDZ tool |
Threshold : 120 days
100% inspection and approval of all data
| 4.3.8.4 Provide FMS support |
| Foreign Anti-tank rocket danger zones are provided |
| Anti-tank rocket danger zones are developed and then included in the FDZ tool |
| Updated danger zones are provided in FDZ tool |
Threshold : 120 days
100% inspection and approval of all data
| 4.3.8.5 Provide FMS support |
| Foreign Anti-tank missile danger zones are provided |
| Anti-tank missile danger zones are developed and then included in the FDZ tool |
| Updated danger zones are provided in FDZ tool |
Threshold : 120 days
100% inspection and approval of all data
| 4.3.8.6 Provide FMS support |
| A desktop WDZ Tool Module for Country Specific Aircraft/ Fighter/Fixed Wing/UAS is provided |
| A desktop WDZ Tool Module for Country Specific Aircraft/ Fighter/Fixed Wing/UAS is developed and then included in that country’s WDZ tool |
| Updated country specific Aircraft/ Fighter/Fixed Wing/UAS is included in the WDZ tool |
Threshold : 120 days
100% inspection and approval of all data
| 4.3.8.7 Provide FMS support |
| A desktop WDZ Tool Module for Country Specific Aircraft/ Fighter/Rotary Wing/ is provided |
| A desktop WDZ Tool Module for Country Specific Aircraft/ Fighter/rotary Wing is developed and then included in that country’s WDZ tool |
| Updated country specific Aircraft/ Fighter/Rotary Wing is included in the WDZ tool |
Threshold : 120 days
100% inspection and approval of all data
| 4.3.8.8 Provide FMS support |
| Provide a Data Cube for a Gravity Delivered, Non-Guided Bomb |
| A Data Cube for a Gravity Delivered, Non-Guided Bomb is developed for the WDZ tool |
| A Country specific Data Cube for a Gravity Delivered, Non-Guided Bomb is included in the WDZ tool |
Threshold : 90 days
Objective: 60 days 100% inspection and approval of all data
| 4.3.8.9 Provide FMS support |
| Provide a Data Cube for a multimode guidance weapon |
| A Data Cube for a multimode guidance weapon is developed for the WDZ tool |
| A Country specific Data Cube for a multimode guidance weapon is included in the WDZ tool |
Threshold : 270 days
Objective: 120 days 100% inspection and approval of all data
| 4.3.10 Provide FMS support |
| Provide a Data Cube for a singlemode guidance weapon |
| A Data Cube for a singlemode guidance weapon is developed for the WDZ tool |
| A Country specific Data Cube for a singlemode guidance weapon is included in the WDZ tool |
Threshold : 270 days
100% inspection and approval of all data
| 4.3.8.11 Provide FMS support |
| Provide a Data Cube for a Unguided Rocket |
| A Data Cube for a unguided Rocket is developed for the WDZ tool |
| A Country specific Data Cube for a Unguided Rocket is included in the WDZ tool |
Threshold : 120 days
100% inspection and approval of all data
| 4.3.8.12 Provide FMS support |
| Provide a Data Cube for a guided Rocket |
| A Data Cube for guided Rocket is developed for the WDZ tool |
| A Country specific Data Cube for a guided Rocket is included in the WDZ tool |
Threshold : 270 days
100% inspection and approval of all data
| 4.3.8.13 Provide FMS support |
| Provide a Data Cube for a Direct Fire Gun |
| A Data Cube for a Direct Fire Gun is developed for the WDZ tool |
| A Country specific Data Cube for a Direct Fire Gun is included in the WDZ tool |
Threshold : 120 days
100% inspection and approval of all data
| 4.3.8.14 Provide FMS support |
| Database updates/maintenance for FMS customers is performed |
| FMS customers database requirements are included in the FDZ tool |
| Updated database is provided in FDZ tool |
Threshold : 120 days
100% inspection and approval of all data
| 4.3.8.15 Provide FMS support |
| Database updates/maintenance for FMS customers is performed |
| FMS customers database requirements are included in the WDZ tool |
| Updated database is provided in WDZ tool |
Threshold : 120 days
100% inspection and approval of all data
| 4.3.8.16 Provide FMS Support |
| Update RMTK foreign tools for FMS customers. |
| Update and maintain the RMTK suite of tools for foreign purchasers. The contractor shall resolve any software errors resulting from operating system upgrades or version changes of the RMTK suite of tools |
| Updated RMTK are provided |
Threshold: 270 working days
100% inspection and approval of all data
| 4.3.8.17 Provide FMS support |
| Training class support |
| Conduct a one (1) week initial training class for users on the basics of the WDZ Tool. |
| Training class is conducted |
Threshold : On time as scheduled
Objective: On time as scheduled Customer Satisfaction with end of course critiques
| 4.3.8.18 Provide FMS support |
| Provide Tier 1-3 tech support to select FMS countries |
| Provide help desk tier 1-3 tech support from 0800-1700 EST for issues resulting from the contractor’s creation, testing, or verification of any RMTK data issues; or issues resulting from use or installation of the RMTK suite of tools |
| Provide tech support and provided tech support information in monthly status reports and quarterly PMR’s |
Threshold: 3 working days response
Objective: 1 working day response Customer satisfaction with customer problem resolution
Table 4: CONTRACT PERFORMANCE ASSESSMENT PERFORMANCE EVALUATION CRITERIA AND STANDARDS
| UNSATISFACTORY |
| MARGINAL |
| SATISFACTORY |
| VERY GOOD |
| EXCEPTIONAL |
| Problem Resolution |
| Problems are unresolved, repetitive, or take excessive Government effort to resolve. |
| Problems are generally resolved but take unusual Government effort to resolve or take an excessive amount of time to resolve |
| Problems are resolved quickly with minimal Government involvement. |
| Problems occur |
infrequently and are generally resolved quickly with minimal Government involvement.
Problems are non-existent or the contractor takes corrective action without Government involvement.
| Responsiveness |
| Contractor is completely unresponsive to Government requests and concerns. |
| Contractor is occasionally unresponsive to Government requests and concerns |
| Contractor is responsive to Government requests and concerns. |
| Contractor is responsive to Government requests and concerns and occasionally is proactive in anticipating Government concerns |
Contractor takes proactive approach in dealing with Government representatives and anticipates Government concerns.
| Communication |
| Contractor often fails to communicate with Government in an effective and timely manner. |
| Contractor occasionally fails to communicate with Government in an effective and timely manner |
| Contractor routinely communicates with Government in an effective and timely manner. |
| Contractor routinely |
communicates with Government in an effective and timely manner and is frequently proactive in managing communications Contractor takes a proactive approach such that communications are almost always clear, effective and timely.
File details come from the government source that posted it. Updated .