M67854-18-R-7600_-_Attachment_9_-_PRS.xlsx
XLSX spreadsheet 35 KB Posted
- Attached to
- Amendment 6 Federal contract opportunity
- Solicitation number
- M67854-18-R-7600
- Issued by
- United States Marine Corps
About this file
This document contains a Performance Requirements Summary (PRS) for a federal contract to provide sustainment and engineering support services for the Global Combat Support System-Marine Corps (GCSS-MC).
The PRS outlines over 70 performance-based tasks and requirements across areas including service management, operations, training, product lifecycle support, systems engineering, and program management. Key responsibilities involve maintaining the GCSS-MC production environment; operating a help desk, configuration management, and testing functions; conducting training, data management and interface administration; and applying systems engineering principles. Performance is evaluated on metrics such as issue resolution timeliness and reporting quality. The United States Marine Corps is identified as the contracting agency.
RFP Attachment 9 - Performance Requirements Summary
View the file
Other files for this federal contract opportunity
Show all 50
Amendment 6 has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
GCSS-MC PRS
| Performance Requirements Summary | |||||||
| PWS Par | Performance-based Task | Performance Requirement | Performance Indicator | Acceptable Quality Level | Surveillance Method | Incentive (+ or -) | How will performance be documented AND by whom |
| 3.1 | Service Management | -- Establish SLM framework; manage service delivery and Quality of Service (QoS) --Coordinate and co-chair a quarterly Systems Engineering (SE) Process Integrated Product Team (IPT) and present SE process status, metrics and trends --Update annually the SE Sustaining Engineering Process Plan including each "Process Analysis and Narrative" document | Format, content completeness, content compliance and timeliness of report | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.1.1 | Performance and Metric Analysis | -- Analyze and recommend enhancements to performance requirements and metrics using IT and industry best practice and provided recommendations --Identify, collect and analyze process specific metrics. Create process IPT presentations and materials, presenting metrics and recording minutes and action items for the SE Process IPT | Format, content completeness, content compliance, and timeliness of report | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.1.2 | Service Agreements | -- Review SLAs and provide recommendations to enhance alignment to performance requirements | ||||||
| -- Monitor and report on existing SLAs performance with external providers | Format, content completeness, content compliance, and timeliness of report | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |||
| 3.1.3 | Continual Service Improvement | --Monitor system performance and program processes and identify opportunities for CSI --Identify the approach to be used to collect supporting data, measurement and analysis, and reporting with recommendations to improve the system | Format, content completeness, content compliance, and timeliness of report | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.2 | Service Operations | --Provide technical implementation of the GOC and Enterprise Service Desk processes and functions --Provide technical expertise in system administration, system integration, database administration, application administration, implementation of code, system software support, networking support and Enterprise Service Desk to sustain 24/7/365 operations --Provide integrated incident/problem management to resolve issues and problems, and unplanned outages. | Effective execution of Service operations as detailed in Section 3.2 and 3.2.2.4 of PWS | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.2.1 | GCSS-MC Operations Center (GOC) | --Create an event record for each event --Coordinate planned system outages, including providing notification to the user community before and during outages --Initiate, request, coordinate resources, monitor, and manage all required GCSS-MC/LCM Increment 1 PROD and PSS planned and unplanned outages required for system maintenance | ||||||
| --Investigate the cause(s) and corrective course(s) of action for the workflow communicating a fix or TA.155PROD24 SOP update via CR | --100% of incidents recorded in BMC --Change request implemented for 100% of new types or workflow errors detected | 100% | 100% inspection |
Direct observation
| CPARS | Government Lead/COR review of deliverables and written response | |||
| 3.2.1.1 | Enterprise Application Adminstration | --Resolve application problems not resolved at the Tier 3 level | ||
| --Develop and submit CRs that require Oracle COTS changes to the GCSS-MC GOC Manager --Conduct technical aspects of functional user testing and collaborate with the PMO on code fix designs in accordance with the Government’s Configuration and Change Management processes | --Backlog of unresolved issues less than 10% of all incidents | |||
| --FUT performed | 90% | Quarterly reviews, periodic inspection, BMC reports | CPARS | Government Lead/COR review of deliverables and written response |
| 3.2.1.2 | System Administration | --Provide 24-hour-a day, 7-day-a-week, 365-day-a-year system administration (SA) event and performance monitoring |
--Manage the production hardware warranties, resolve SRs, and perform system backups
| --Perform necessary server maintenance, research hardware, operating system issues, and apply patches and updates | Effective execution of Service operations as detailed in Section 3.2.1.2 of PWS | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response |
| 3.2.1.3 | Database Administration | --Monitor production interfaces to support problem identification |
--Create/prepare and execute approved CRs addressing issues --Perform health checks and monitor system integrity and usability
| --Identify system event thresholds and implement proactive response alerts, respond to alerts, and initiate the incident management process -- Monitor the growth of the database segments and conduct capacity planning and forecasting and present this data to the Government at the Weekly O&S meeting | Format, content completeness, content compliance, and timeliness of report | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |||
| 3.2.1.4 | Systems Integration | --Integrate all hardware, software, applications, data, network, and component subsystems into a singular system --Provide daily workflow administration and troubleshooting to prevent or resolve redline and document script issues --Provide RCA and resolution recommendations for issues requiring additional resources or change management approval | Effective execution of Service operations as detailed in Section 3.2.1.4 of PWS | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.2.1.5 | Interface Administration | --Provide daily, weekly, and periodic Interface and External Tracking Reports with required interface metrics interface status during the past 24 hours, including interface status, downtime over the total records, total success, and success percentage |
--Analyze tracking reports and provide holistic assessments on GCSS-MC/LCM Increment 1 system impacts and provide recommendations for solutions --Provide daily, weekly, and periodic Error Handling Framework (EHF) reports for RICECPW --Analyze reports and provide holistic assessments on GCSS system EHF impacts and provide recommendations for solutions
| --Coordinate with internal and external interface stakeholders to troubleshoot interface issues, determine corrective action, and implement approved solutions | Format, content completeness, content compliance, and timeliness of report | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |||
| 3.2.1.6 | Data Quality | --Maintain data quality to ensure efficient business and transaction processing functions --Collect, compile and evaluate GCSS-MC/LCM Increment 1 enterprise data discrepancies and conduct technical review of data from collection to instantiation (data lifecycle) and present this data to the Government at the Weekly O&S meeting | ||||||
| --Identify and analyze trends and submit recommended CRs for enhancements that improve data quality | 100% notification of potential issues to Government Lead | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |||
| 3.2.1.7 | Information Assurance/Cybersecurity | --Conduct user account auditing | 100% of user account audits conducted | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.2.1.8 | On-Call/Extended Shift | --Be available within a 2-hour window to perform a required task through its resolution during an unexpected outage | 100% of issues responded to within 2 hour window | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling, analysis | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.2.2 | Enterprise Service Desk | --Provide high quality support in a timely and responsive manner and achieve a high level of customer satisfaction --Identify relevant data, perform trend analysis and provide Service Desk Activity Reports that analyze SR data and trends --Collect and report customer satisfaction surveys to ensure Service Desk delivery meets customer expectations --Report the Service Desk’s efforts and status at the Government’s weekly O&S meeting | Conduct Customer Satisfaction Surveys | 90% | Customer complaint, random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.2.2.1 | Tier 1 Service Desk | --Report resolution of issues and trouble tickets/SRs to the user via the established Frequently Asked Questions (FAQ) site within Remedy --Create new KBs or UPKs to document the solutions --Identify trends in inadequate end-user training to enhance GCSS-MC/LCM Increment 1 training curricula in response to end-user needs | 100% of user issues documented in Remedy FAQs | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.2.2.2 | Tier 2 Service Desk | --Update the GCSS-MC/LCM KB when a Tier 2 level SR issue response is not already scripted or documented in the Knowledge Base --Analyze issues to determine if possible trends exist | 100% of Tier 2 SR issue responses in KBs | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.2.2.3 | Tier 3 Service Desk | --Provide a Tier 3 Service Desk comprised of functional and technical SMEs to provide timely and effective responses to operational or technical problems or issues that may arise during system operation and maintenance | 100% of issues responded to within 2 hour window | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.2.3 | Incident Management | --Provide assessment, diagnostic, and escalation procedures to resolve incidents within specified timeframes --Gather information regarding incidents and provide classification as well as provide trend analysis --If incidents cannot be resolved technically or in a timely manner, escalate the issue to Problem Management | Format, content completeness, content compliance, and timeliness of report | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.2.4 | Problem Management | --Report and attempt to facilitate the resolution of data integrity issues and perform analysis of problems related to data contained in the Oracle EBS applications and GCSS-MC/LCM Increment 1 environments --Analyze and resolve functional issues and provide technical and functional support for the GCSS-MC/LCM Increment 1 system to include COTS products, RICECPW components, and related trouble tickets/SRs --Conduct a technical review of system data and provide ad hoc reports or data extracts as it relates to USMC logistics business processes --Maintain and implement SOPs to address GCSS-MC/LCM Increment 1 user needs and provide information to address specific needs/issues | ||||||
| --Identify potential negative trends including those mitigated by training, workarounds, or changes to AIM TA.155 SOPs -- Identify, develop, and submit CRs to Change Management to document known problems that may require further research or long term resolution | Format, content completeness, content compliance, and timeliness of report | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |||
| 3.3 | GCSS-MC Production/PSS Environment Sustainment | --Maintain and sustain the current production system, including hardware, software, and ancillary equipment --Maintain configuration control of the system baseline and ensure all changes to production configuration items are properly documented and reported --Maintain control of production assets and support physical inventories and configuration audits --Apply security patching and risk management framework (RMF) artifact updates to ensure system accreditation and sustainment of its Authority To Operate (ATO) --Provide recommendations for improvement for potential software and proposed hardware used in the Production environment via ECPs utilizing the Engineering Change Proposal | --Production system 99.99% available for users --Configuration control of baseline properly documented at all times --Production asset physical inventory maintained 100% --ATO maintained 100% of time | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling, analysis | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.3.1 | Capacity Management | --Perform capacity planning to accommodate for usage growth through scaling of existing infrastructure (servers, licenses, storage, bandwidth, etc.) and emerging technologies --Provide a weekly GCSS-MC Enterprise NIPRNet Capacity Report that includes information related to service, resource use, and performance --Document current system use and forecast requirements to maintain an annual Capacity Plan | Format, content completeness, content compliance, and timeliness of report | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.3.2 | Oracle Engineered Hardware Suite | --Ensure system backup data is up-to-date and ready for emergency disaster recovery --Prepare CRs to address COTS updates and configurations changes for the f5 and network switches --Maintain and provide accurate system information including system diagrams, network and data flow diagrams, system configurations, system diagrams, and network configurations | System backup data is up to date and available 100% of the time | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.3.3 | Internal Networking and Ancillary Storage | --Ensure the delivery of secure, reliable, and scalable network connections | Network connections meet requirements | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.4 | Solution Development Environment | --Provide an SDE capability to perform changes, testing, integration, product-development, and CM activities | SDE 100% available for use | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.4.1 | SDE Sustainment Support | --Establish Production support instances in the SDE, DEV, and CM environments necessary to develop, test, troubleshoot, and integrate changes --Report the availability of the SDE in the 30/60/90 Release Schedule | ||||||
| --Provide an SDE Instance report to identify configuration of the SDE instances | Support instances 100% available for use | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |||
| 3.4.2 | SDE Operations Support | --Sustain and maintain the software architecture engineering, development, data staging, testing and configuration of the SDE and provide technical drawings, diagrams and other technical data --Evaluate capacity requirements and performance and update the Capacity Plan at least annually or when a significant change is made to the infrastructure --Sustain and maintain the software architecture, engineering, changes, data staging, testing and configuration of the SDE, including applying relevant patches and Critical Patch Updates | SDE 100% available for use | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.5 | Enterprise Training and Training Devices | --Provide an integrated approach to training management, training change management, delivery and training device sustainment | Approach utilizes logical lifecycle sustainment methodology. | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.5.1 | Training Studies | --Conduct training studies to assess and recommend new training methodologies and approaches, and feasibility studies for training development, technical support, and training documentation | --Studies delivered when requested | 100% | 100% inspection |
| CPARS | Government Lead/COR review of deliverables and written response | |||||||
| 3.5.2 | Training Management | --Ensure training materials, training curriculum, training delivery, and training systems accurately reflect the capabilities, functions, and processes of the GCSS-MC/LCM Increment 1 system | ||||||
| --Provide a Training Schedule with Plan of Action and Milestones (POAM) for all training changes and updates --Provide Status Reports of ongoing training activities | Format, content completeness, content compliance, and timeliness of training | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |||
| 3.5.3 | Training Development | --Follow all CM and release management requirements for training material and systems --Include training materials and systems as part of the Technical Data Package (TDP) --Maintain access and control of the training media library --Deliver a quarterly update of curriculum material, eDesktop, and associated documentation for publication to the appropriate environment | --Training follows same Configuration Management and release management process 100% of the time --100% of Training material included in TDP -- Access to training library maintained at all times --Format, content completeness, content compliance, and timeliness | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.5.4 | Training Delivery | --Provide training via instructor-led training, interactive courseware, computer based training and blended training solutions --Maintain attendance rosters and deliver training course completion certificates --Ensure students complete the Student Course Critiques (SCC) and Instructor Review Forms --Analyze training event critiques, identified issues and training effectiveness and provide recommendations and timeline for training improvement within 30 days | --Format, content completeness, content compliance, and timeliness of training | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.5.5 | Training Device Sustainment | --Create and provide a Gold Disk image with Release Notes containing all data for the current patch set/code release and identifying changes to the previous baseline --Load the approved image and configure MTS current and future GEN servers and configure the MTS laptops. --Maintain and update MTS/customized menu scripts, processes and procedures for data and environment backups/restore procedures. | --Maintain 100% of MTS laptops with approved images, scripts and processes/procedures | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.6 | Product Lifecycle Support | -- | -- | -- | -- | -- | -- | |
| 3.6.1 | RAM | --Track and report RAM data at the weekly O&S meeting | Format, content completeness, content compliance, and timeliness of report | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.6.1.1 | Reliability, Availability | --Collect data and compute the weekly reliability percentage --Collect data and compute the weekly Operational Availability (Ao) | Reliability: threshold =99.44%; objective=99.99% Ao: threshold=95.00%; objective=98.00% | 99% | 100% Inspection, analysis, direct observation | Incentive | Government Lead/COR review of deliverables and written response | |
| 3.6.1.2 | Maintainability | --Compute and report the Mean Corrective Maintenance Time (MCMT) and Corrective Maintenance Downtime Occurrences | Threshold:> 4 hours for 90.00% of downtime occurrences | 99% | Quarterly reviews, periodic inspection, formal reporting | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.6.2 | Asset Tracking | --Provide accountability, tracking and reporting of assigned hardware, software, licenses, and warranty information --Report all additions, changes, or deletions to an environment/location GFE/GFI, or if the responsible party changes | Format, content completeness, content compliance, and timeliness of report | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.6.3 | Licenses | --Provide a quarterly license report with information to support licensing agreements --Provide cost effective licensing strategies that reduce total ownership costs for software licenses | Format, content completeness, content compliance, and timeliness of report | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.6.4 | Warranty | --Execute hardware and software warranty support agreements required to sustain and maintain the system --Track and report quarterly the status of all warranties and warranty actions | --Warranties selected for best value and executed properly | |||||
| --Format, content completeness, content compliance, and timeliness of report | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | ||||
| 3.6.5 | Obsolescence Management | --Provide obsolescence management for all system components | Obsolescence Management followed on 100% of the system components | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.7 | Service Transition | --Provide responsive, disciplined support to sustain, change, and enhance the GCSS-MC/LCM Increment 1 system following the Configuration Management Process | Format, content completeness, content compliance, and timeliness of report | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.7.1 | Change Requests (CRs) | --Provide support for problem management to include trouble ticket creation and management, trouble ticket investigation, RCA, detailed estimate analysis, and RICECPW impact assessments | ||||||
| --Provide unit test results to the Government as entrance criteria for test | --100% of problems are evaluated within process guidelines | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |||
| 3.7.2 | Engineering Change Proposals (ECPs) | --Provide responsive, disciplined support to maintain, change and enhance the system | Follow a GCSS-MC compatible ECP process | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.7.3 | System Changes | --Participate in required change management boards (CABs, CCBs, and Release Management) | Participate in CAB's, CCBs and RMBs | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.7.3.1 | Change Analysis | --Analyze the CR and provide the technical approach to implement the change --For trouble tickets and issues identified by the Contractor, the Contractor shall create a CR using the Serena Business Manager CR Workflow for trouble ticket investigation, root cause analysis, detailed estimate analysis, and RICECPW impact assessments | Format, content completeness, content compliance, and timeliness of report | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.7.3.2 | Change Development | --Develop configuration fixes, data scripts, and software for any correction of deficiencies, fixes, or changes to existing RICECPW within the sustainment of the current GCSS-MC/LCM Increment 1 baseline --Provide all custom data, custom code, SQL and all original work product deliverables under this task order in a non-proprietary format --Check in all system changes into the code repository and provide code migration documentation and/or procedures to the Government for Independent Verification and Validation (IV&V) | --Ensure RICEPW functions properly --Format, content completeness, content compliance, and timeliness of report | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.7.3.3 | Change Functional Testing | --Conduct unit testing and functional testing in the development environment --Perform backup and recovery testing and execute regression testing --Create or modify existing test cases and scripts to test changes --Create and maintain regression tests for automated regression testing --Provide unit testing results for Independent Verification and Validation (IV&V) | Create and perform all required testing | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.7.3.4 | Change Documentation | --Create and/or update technical baseline documents | Format, content completeness, content compliance, and timeliness of report | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.7.3.5 | Change Promotion | --Promote approved changes to the PSS and PROD following established GCSS-MC/LCM Increment 1 release processes | Follow promotion process for approved Production releases | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.8 | Systems Engineering Supporting Activities | -- | -- | -- | -- | -- | -- | |
| 3.8.1 | Systems Engineering | --Provide disciplined systems engineering and apply acceptable principles, criteria, and procedures to all GCSS-MC/LCM Increment 1 tasks in compliance with DoD, DON, Marine Corps, and program processes | Provide disciplined systems engineering process | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.8.1.1 | Systainment Engineering Processes | --Integrate processes into the PMO processes and provide recommendations to enhance or streamline together | Provided well integrated sustainment Engineering process | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.8.1.2 | Systems Engineering Management Plan | --Areas to be addressed in the SEMP include: |
1) Organization of the team, including physical location and facilities to be used
2) Management approach and use of the GCSS-MC/LCM Increment 1 environments
3) Description on use of engineering standards, capability models and tools to be employed
4) Technical risk management
5) Requirements management and traceability
6) Configuration management process for identifying and managing configuration items
7) Information Assurance/Cybersecurity processes and tools
8) Test process and methodology
9) Software change methodology
10) Build management process
11) Architecture/System Design process
12) Data Management processes
13) Documentation standards to be used and management approach
14) Production support strategy
15) Change support strategy
| Format, content completeness, content compliance, and timeliness of SEMP | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | ||||
| 3.8.1.3 | Systems Engineering Support | --Provide traceability of CRs through design, development, test, and deployment of system updates --Maintain the existing solution architecture (logical, physical, and network topology) and system diagrams --Provide updates to system diagrams and architectural drawings to reflect changes to the baseline architecture --Provide recommendations, including analysis and technical risk assessment for all system incidents, problems, updates, and changes | Format, content completeness, content compliance, and timeliness of report | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.8.1.4 | Systems Engineering Tool Support | --Implement SE tools to support engineering processes compatible with those used by the GCSS-MC PMO --Provide user account and database administration of the CM, asset management, and test tools --Provide user notifications of outages and work with NSERC personnel to identify performance issues --Maintain access lists and configure users for system access, once access is granted --Provide requirements management data compatible with the schema resident in the GCSS MC/LCM Increment 1 DOORS requirements database --Use a tool that is compatible with Fortify for the automated exchange of code scan findings with the GCSS-MC PMO | --Implement compatible SE tools --Maintain 100% db administration of CM, asset management and test tools --Maintain 100% accurate access lists --Format, content completeness, content compliance, and timeliness of requirements management data --Use a security code scan tool that is 100% compatible with Fortify | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.8.2 | Software Engineering | --Employ the use of sound software engineering principles, methods, practices, and tools to produce and sustain reliable GCSS-MC/LCM Increment 1 applications and associated RICECPW objects in an economical manner --Perform disciplined application development activities consistent with CMMI Level 3 | --Implement sound, economical software engineering and application development principles | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.8.2.1 | Software Development Plan | --Implement application solutions which sustain code and system configurations and associated documentation to support correction of defects and enhancements | Format, content completeness, content compliance, and timeliness of documentation | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.8.3 | Interface and Data Management | -- | -- | -- | -- | CPARS | -- | |
| 3.8.3.1 | Interface Management | --Define, design, and manage the physical and logical interfaces, both internal (communications between system elements) and external (communications between the system and other systems), to ensure the interfaces perform correctly --Work closely and cooperatively with internal and external organizations and agencies to manage agreements between GCSS-MC/LCM Increment 1 and other systems owners --Follow established processes and procedures, as documented in Interface Control Documents (ICDs) --Organize, lead and document meeting meeting minutes and action items for the monthly Systems Integration IPT (SI IPT) | ||||||
| --Support the definition, implementation, and testing of internal and external interfaces, including any associated dependencies, to ensure that systems operate as designed and meet stakeholder requirements throughout the life cycle | Format, content completeness, content compliance, and timeliness of interface documentation | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |||
| 3.8.3.2 | Data Management | --Maintain and update documentation, including the Data Management SOP and TA.155:PROD24 (Data Maintenance) --Analyze Defense Logistics Management Standards (DLMS) changes and define technical impacts to the system and the data exchanges --Provide Data Management Planning to identify impacts to the system environments | Format, content completeness, content compliance, and timeliness of planning report | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.8.4 | Information Security Management/Cybersecurity | --Participate in cybersecurity and vulnerability assessment scan reviews and provide technical guidance --Review IAVAs, Information Assurance Vulnerability Bulletins (IAVBs), Technical Advisories, Communications Tasking Orders, Marine Corps Directives, Operational Directives, CPUs, vulnerability alerts, and vendor notifications to determine applicability to GCSS MC/LCM Increment 1 and to assess impact and provide assessment --Apply security updates and patches to software and operating systems and conduct verification testing and document all findings in a weekly cybersecurity status report -- Track, report status and provide remediation recommendations for the vulnerabilities --Provide an impact assessment of CPUs if there is an impact to RICECPW and document the assessment in CR --Provide encrypted RICECPW code to the GCSS-MC ISSM for code review when updated --Support all activities required for maintaining the ATO or Interim Authority To Test (IATT) and remaining compliant with the Federal Information Security Modernization Act (FISMA) | ||||||
| --Support Cyber Readiness Inspection and IV&V events --Update GCSS-MC/LCM Increment 1 cybersecurity documentation in accordance with DoD policy --Support cybersecurity testing by providing a thorough Cybersecurity Risk Assessment | --100% of solutions must be STIG aligned --Format, content completeness, content compliance, and timeliness of planning report | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |||
| 3.8.5 | Configuration Management | --Follow the PMO’s configuration control and approval processes required to change a CI’s attributes and re-baseline the CIs | ||||||
| --Ensure all CRs properly document affected CIs --Provide a Product Baseline (CM.070) for each patch set --Establish and implement configuration control and approval processes required to change a CI’s attributes, to re-baseline the CIs, and then report the CI completion --Follow established change, documentation and release management processes, and describe the approach to accomplishing the activities --Support a quarterly release cycle | --Format, content completeness, content compliance, and timeliness of reports --Releases occur every quarter | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |||
| 3.8.5.1 | Configuration Management Process | -- | -- | -- | -- | CPARS | -- | |
| 3.8.5.2 | Configuration Control Boards (CCB) | --Support the CR change sponsor at CCBs to discuss the proposed change and technical solution --Prepare CCB briefs | 100% support at CCB for CRs | 95% | 100% inspection, direct observation | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.8.5.3 | Change Management | --Adhere to the PMO’s configuration control processes required to change a CI’s attributes and re-baseline the CIs --Follow the PMO’s CR workflow and ensure approved changes are fully documented throughout the CR life cycle | 100% Compliance to configuration control and CM process | 99% | 100% inspection, direct observation | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.8.5.4 | Change Assessment Board | --Participate in CABs and present evaluation of approved CRs --Identify opportunities to implement block upgrades for related CRs where implementing block upgrades can save time, money, or enhance system performance --Deliver required artifacts to the GCSS-MC Data Repository and Code Management repository | --Format and content completeness of upgrade opportunities --100% of required artifacts delivered to the GCSS-MC Data Repository | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.8.5.5 | Configuration Identification | --Support PMO Physical Configuration Audits (PCA) by locking CIs in the CMDB --Review and provide inputs to PCA plans and draft PCA reports | Lock 100% of CIs in the CMDB during the PCA | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.8.5.6 | Code Managenment | --Describe approach for code management in the CMP --Maintain the integrity of the software development and CM controlled environments, ensure consistent implementation of CAB and CCB decisions --Coordinate migration and delivery of Software Builds to the GOC for promotion --Provide installation and release notes, in conjunction with the code builds, and post the builds to the Government’s designated data repository --Migrate the quarterly build code to the designated Government Code Repository --Freeze the production baseline and create a patch set with the associated documents for the Product Baseline (CM.070) | --Format, content completeness, content compliance, and timeliness of CMP --100% integrity of software development, CM environment and consistency of CAB/CCB decisions | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.8.5.7 | Release Management | --Attend the monthly PMO release planning meeting and provide a proposed release plan --Assign builds to appropriate software releases as identified in the GCSS-MC CMP and develop 30/60/90 day release schedules | ||||||
| --Coordinate with the Government to schedule ad hoc system backups and database clones for promotion to solution development and test instances, and compile the 30/60/90 day release schedule --Provide status updates for ongoing release plans at the release planning meeting --Maintain a PSS and Production Software Baseline Reports (PSBR) and track CRs or software releases by build per release, patch set, and clones provided as GFI --Maintain assignment, prioritization and scheduling spreadsheet --Contractor shall prepare DD Form 1149 and track distribution of clones and clone contents (builds) | Format, content completeness, content compliance, and timeliness of updates and reports | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |||
| 3.8.6 | Validation and Testing | --Perform service validation and testing in conjunction with the development and deployment of system changes and in accordance with the GCSS-MC engineering processes --Provide a test schedule within the Detailed Test Plan identifying test events and activities | --Perform 100% of the required service validation and testing --Format, content completeness, content compliance, and timeliness of test schedule | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.8.6.1 | Test Environment | --Perform test environment setup and coordinate unit testing, integration testing, system testing, regression testing, and performance/load testing --Provide test results for IV&V upon successful completion of unit testing --Maintain CM of the code used for System Integration Testing (SIT) and GAT --Produce a report using GFI provided HP ALM --Implement tools and methods that provide a complete detailed record of test documentation --Include procedures for test data cleansing, conversion, and verification/validation, as necessary. Data shall be transferrable and in a form usable by the Government | -Manage 100% of the test environment system | 99% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.8.6.2 | Test Planning | --Ensure all test documentation and activities are traceable to requirements, issues or incidents, including test plans, test cases, test data staging, test scenarios, and test scripts in accordance with established PDSS processes --Follow a repeatable test strategy for system changes --Plan and execute required test and evaluation processes to include data quality and performance tests as required --Identify and communicate test risks, resource requirements, supporting service needs, and scheduling milestones --Provide proposed test scripts and technical justification for level of testing, to include: function unit test, regression, and failover | ||||||
| --Provide a roll-back plan for each system change | Format, content completeness, content compliance, and timeliness of reports/documentation | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |||
| 3.8.6.3 | Test Execution | --Execute tests in accordance with the Government-approved test plan --Conduct SIT with the Government to demonstrate successful development testing results prior to promotion to PSS for GAT --Monitor GAT and resolve environment, configuration, and code issues --Shall develop and collect TIRs (or respond to Government provided TIRs), perform RCA, and provide analysis and solutions to resolve --Implement the roll-back strategy for all failed system changes | ||||||
| --Validate test scenarios and test scripts which provide verification and validation of the GCSS-MC system functionality and operational performance parameters; document observation points of system anomalies and data collection plans; document technical requirements verification; analyze proposed work arounds and solutions to the root cause; and propose solutions to reduce recurrence of repetitive problems | -Execute 100% of the test requirements effectively | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |||
| 3.10.7 | Project Kickoff brief | -- Deliver a project kickoff brief at least 3 business days before the PAC/PKO | Format, content completeness, content compliance, and timeliness of report | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.10.8 | Performance Evaluation/Technical Status Meeting | --Provide the government technical lead a report at the end of each week that summarizes significant technical activities accomplished and planned technical activities for the following week --Conduct Contract activity and status meetings | Format, content completeness, content compliance, and timeliness of report | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| 3.10.9 | Interim Progress Reviews | -- Support a quarterly Program Management Review Brief | Format, content completeness, content compliance, and timeliness of review | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response | |
| All | ALL CDRL deliverables | --Deliver all CDRLS in accordance with the required schedule | Format, content completeness, content compliance, and timeliness of report | 95% | Quarterly reviews, periodic inspection, customer complaints and random sampling | CPARS | Government Lead/COR review of deliverables and written response |
File details come from the government source that posted it. Updated .