Amendment_1_Attachment_4_-_MCRISS_RCT.docx

Marine Corps Recruiting Information Support System (MCRISS) Indefinite Delivery/ Indefinite Quantity (IDIQ)

Total Force Information Technology Systems (TFITS) February 2016

Table of Contents

List of Figures

List of Tables Table 1: TFITS Management Plans 4

List of Appendices

Marine Corps Recruiting Information Support System Performance Work Statement iii Introduction Purpose and Scope The Total Force Information Technology Systems (TFITS) product office provides acquisition oversight for the portfolio of United States Marine Corps (USMC) systems. Marine Corps Recruiting Information Support System (MCRISS) is a project within the TFITS Manpower Tier.

The purpose of this Performance Work Statement (PWS) is to develop and deploy a MCRISS offline Recruiter Client capability for Marine Corps Recruiters. At a minimum, the contractor shall follow the TFITS management plans through the duration of this effort.

This PWS identifies requirements and performance standards for the elicitation, design, development, and deployment of a MCRISS offline Recruiter Client capability for Marine Corps Recruiters. The vendor’s response shall encompass all required systems engineering processes as reflected in the Marine Corps Systems Command Technical Review Handbook, v1.04, April 2009, the TFITS Systems Engineering Plan, and as described herein.

Background The Marine Corps Recruiting Command (MCRC) is responsible to the Commandant of the Marine Corps for the procurement of qualified individuals in sufficient numbers to meet the established personnel strength levels, officer and enlisted, of the Marine Corps and Marine Corps Reserve. MCRC Headquarters is located at the James Wesley Marsh Center aboard Marine Corps Base (MCB) Quantico, Virginia.

MCRC Recruiting Force has successfully employed a highly effective concept known as systematic recruiting, a synergistic set of recruiting processes that have been in force since the late 1970s. The goal of systematic recruiting is to organize the efforts of recruiters and to ensure that the required contacts, appointments, interviews, and contracts are achieved.

MCRC is comprised of approximately 6,000 members. The following are locations at which MCRC personnel are located:

· MCRC Headquarters on MCB Quantico

· Region Headquarters (Parris Island, SC and San Diego, CA)

· 6 District Headquarters (Garden City, NY; Harrisburg, PA; Parris Island, SC; Ft. Worth, TX; Naval Station Great Lakes, IL; San Diego, CA)

· 1 Recruiter School (San Diego, CA)

· 48 Recruiting Stations (RS)

· 6 Prior Service Recruiting Stations (PSRS)

· 620 Recruiting Substations (RSS)

· 19 Prior Service Recruiting Substations (PSRSS)

· 74 Officer Selection Stations (OSS)

· 67 Military Entrance Processing Stations (MEPS)

· 840 Permanent Contact Stations (PCS)

· 24 Transient Recruiting Facilities (TRF) MCRISS is the enterprise system that supports recruiting efforts at the Headquarters, Regional, District, RS/PSRS, RSS/PSRSS, and OSS locations. It provides a centrally-managed and secure repository of information and services to support the management of applicant processing from prospecting to accession and commission into the Marine Corps and Marine Corps Reserve to meet the established manning levels. MCRISS integrates with other USMC and Department of Defense (DoD) systems.

MCRISS is Mission Assurance Category (MAC) III with a Confidentiality Level as described in Department of Defense Instruction (DoDI) 8500.2 as Sensitive but Unclassified (SBU). MCRISS is identified as Defense Automated Document Management System (DADMS) Number 4665 and The DoD Information Technology Portfolio Repository- Department of the Navy (DITPR-DON) Number is 11339.

An overview of the system including interfaces is provided in Figure 1.

Figure 1: Operational View MCRISS is the authoritative source for the recruiting process and records all prospecting results through accessions. MCRISS is currently a centralized, web-based, enterprise application and database Automated Information System. Updates to this system have been implemented to extend the user base to the RSS, OSS and PSRSS levels.

MCRISS is comprised of eight main modules and two supporting software applications. They are:

· Recruiting Station Module

· Officer Programs Module

· Recruiting Sub-Station Module

· Officer Selection Station Module

· Prior Service Recruiting Module

· Automated Enlistment Package Module

· Automated Commissioning Package Module

· Background Investigation Questionnaire Module

· Web Query Tool (Application)

· SQL Server Reporting Services (Application) MCRISS includes custom developed software, leveraging classic ASP and .Net V3.5 and V4.0 (written in C++) technologies, and configuration tailored Commercial-Off-The-Shelf (COTS) products. The system is comprised of multiple web, application, and database servers which operate in a Microsoft Windows Domain environment. MCRISS is resident on hardware hosted and located on MCB Quantico, VA. The current platform supporting MCRISS consists of the following components:

· VMWare VMWare ESX 5x (Virtual Infrastructure),

· Microsoft Windows Server 2012R2 DataCenter Edition (Operating System),

· Microsoft SQL Server 2012 (Relational Database Management System),

· Windows Active Directory (LDAP),

· F5 BIG IP (Network Loadbalancing, SSL Offloading, Web Application Firewall, Common Access Card (CAC) Authentication/Kerberose Ticketing Services).

· Imperva Database Application Firewall (DAF) appliance The MS SQL environment is comprised of an Online Transactional Processing (OLTP) Database, and an Online Analytical Processing (OLAP) Database, along with other database instances and nodes that run in a clustered environment.

TFITS Management Plan Table 1 identifies the TFITS Management Plans that provide overarching guidance for TFITS managed projects. These documents form the foundation for the baseline for TFITS common best business practices.

Table 1: TFITS Management Plans

Contractor Performance The contract shall be performed in accordance with this PWS and the Government’s Quality Assurance Surveillance Plan (QASP). Additionally the contractor shall perform in accordance with the processes and standards in the Contractor’s PDSS Plan, Software Development Plan (SDP), Project Management Plan, and Quality Assurance Program Plan (QAPP).

During the performance of the MCRISS activities, the SI will be required to work cooperatively with Government personnel and contracted support.

Objectives

· The PDSS and system maintenance and performance upgrades shall be performed, managed, and monitored to the Government’s price, schedule and performance objectives, through an integrated and defined set of project processes tailored from Capability Maturity Model Integration (CMMI) Level III equivalent or higher set of standard processes.

· Perform and implement system modifications and enhancements through Engineering Change Proposals (ECPs).

· The MCRISS system shall be available and operationally suitable on a 24-hour basis, 7 days a week (to the maximum extent practicable).

· Accurate and complete system documentation (configuration baselines, technical documentation, information assurance documentation, user documentation, web-based training (WBT), etc.) updates and any required certifications/accreditations shall precede the deployment of any capabilities.

RESERVED

RESERVED

Software Development All development objectives should be developed and fielded in accordance with the Supplement to Guidebook for Acquisition of Naval Software Intensive Systems: Software Criteria and Guidance for Systems Engineering Technical Reviews and MCSC Technical Review Handbook v1-04 and PM, TFITS Interim Policy Letter 1-11, Implementation of Tailored System Engineering Technical Reviews.

Additionally, all Software Development initiatives impact the system baseline and are therefore governed by the CM process as defined in the SDP and TFITS Management Plans. The SDP lays out the process required to develop, modify, or upgrade Government software and describes the details of each step along with any considerations that need to be addressed.

Software Development Plan (SDP) The SI shall develop an SDP and execute a project-level system engineering process that addresses and coordinates with the processes, products, functions, and objectives described in the TFITS SEP. The SI shall provide an initial SDP and deliver an updated version as required. The SI shall continue to update the SDP to maintain alignment with this SEP. This SDP is considered a living document that will be updated as necessary to support evolving requirements and maturing products and processes. The SDP shall be updated with each system maintenance and performance upgrade. At a minimum, an update to the SDP will be reflected for each system maintenance and performance upgrade (classified as either an second octet/major or third octet/minor change) and new capability requirements (classified as a first octet capability change) shall ensure and provide the following in accordance with the specified level of SETR tailoring based in the ECP classification level.

At a minimum, the SDP shall provide the SI's approach to:

Provide derived requirements.

Design software.

Develop software.

Test software.

Deploy software.

Describe how the SDP can produce supporting artifacts that are based on the recommended methodology in the Supplement to Guidebook for Acquisition of Naval Software Intensive Systems: Software Criteria and Guidance for Systems Engineering Technical Reviews; TFITS Management Plans; and the MCSC Technical Review Handbook, v1.4 dated April 2009.

Describe in the SDP specific Software Development areas where cost savings will be realized through reusability, reliability, and maintainability.

Provide a strategy for integrating CM, Human Systems Integration, Logistics, and Cybersecurity into each stage (4.1.1 - 4.1.5) of the software development process.

Requirements Analysis Phase The key objective of the Requirements Analysis Phase is to transform the Government's needs into a technical view of a required product that could deliver those needs. Efforts involve defining User needs and requirements in the context of planned User use environments and identified system characteristics to determine requirements for system functions.

At a minimum, the SI shall:

Elicit derived requirements.

Perform an iterative process of decomposing requirements into system functional requirements and establishing traceability.

Maintain traceability between the derived and Government-provided requirements.

Align requirements analysis efforts with MCSC acquisition requirements (TFITS Management Plans, and SETR process).

Provide documentation (Requirements Traceability Matrix (RTM)) needed to support the MCSC SETR process for System Requirements Reviews (SRR) and System Functional Reviews (SFR).

Document the functional baseline.

System Design Phase The objective for the System Design Phase is the on-time delivery of Government-approved documentation that provides the detailed design of each configuration item in the approved product baseline. The System Design Phase produces a design that is based on the functional descriptions and products developed during the Requirements Analysis phase. The design is reflected in the products developed and delivered by the SI.

At a minimum the SI shall:

Provide the SI's design process including the use of design and modeling tools, analyses, and tradeoffs.

Align the SI's process with the TFITS Management Plans and the MCSC SETR process for Preliminary and Critical Design Reviews (PDRs/CDRs).

Provide documentation (System/Subsystem Design Document) needed to support the PDRs/CDRs.

Document the Allocated and Product baselines.

Development Phase The prime objective for the Development Phase is the on-time delivery of a Government- validated capability solution.

At a minimum the SI shall:

Develop, integrate, assemble, and test capability.

Provide in-process reviews.

Align the SI's process with the TFITS Management Plans and MCSC SETR process for Test Readiness Review (TRR).

Provide documentation needed to support the MCRISS TRR and PRR.

Support GAT, IV&V, code review, and cyber-penetration testing.

Provide the Government with a copy of the system source code upon request.

Deployment Phase The prime objective for the Deployment Phase is the deployment of the Government-accepted capability into the production environment in accordance with the established performance standards.

At a minimum the SI shall:

Document the SI's deployment process.

Validate that all certifications and accreditations are in place prior to deployment.

Prepare the system User community to receive and use capability.

Coordinate and deliver the deployment package (to include Compiled Release Code) within the PDSS Release Management process.

Optional Objectives All optional Development Objectives shall adhere to the Software Development requirements stated in section “4. Software Development” of this PWS. Optional development objectives shall not degrade sustainment activities that are provided as part of this PWS, likewise sustainment activities shall not degrade the support of awarded optional development objectives.

RESERVED

Recruiter Client Tool (RCT) Providing the recruiter with the ability to perform their job regardless of network connectivity will greatly improve the quality of prospecting activities and provide much needed flexibility to the recruiting force. The Government requires the development and implementation of a client application supporting the following capabilities:

Provide Recruiters with the ability to perform recruiting activities on portable electronic devices without Internet connectivity.

Provide Web-Based Training to recruiters using the Recruiter Client Tool and basic troubleshooting steps one month prior to release date.

Provide a download capability to allow recruiters in a connected state to download relevant prospect lists and applicant data.

Provide a capability to conduct disconnected operations for the primary elements of the Systematic Recruiting Process.

Incorporate existing MCRISS workflow and data validation processes.

Provide a data synchronization capability, allowing a recruiter transitioning from disconnected operations to synchronize with the parent MCRISS application database.

Define and incorporate synchronization business rules, including conflict resolution between client and server databases Provide a deployment package to the Government that complies with Marine Corps policy for deploying software on recruiter workstations, for dissemination to recruiter devices.

Provide service desk support of recruiter client issues.

RESERVED

RESERVED

RESERVED

RESERVED

RESERVED

Project Management The SI shall prepare a Project Management Plan. The Government-approved Project Management Plan serves as the common understanding between the Government and the SI on how the Contract will be managed. The Government fully realizes that the SI shall need to periodically revisit and update the Project Management Plan to ensure that it accurately reflects the dynamics of managing a Contract of this magnitude. At a minimum, the Project Management Plan shall be updated annually and resubmitted to the Government for approval. Other than this annual submission, the SI has the latitude to build upon the document content to ensure all aspects of the SI’s collaborative project management process are addressed. All additional updates will require approval from the Government.

At a minimum, the Project Management Plan shall define and describe the SI’s:

Processes Identify the types of skill sets and skill levels that will be needed and provided and the strategies that will be used to ensure that the right amount of the right skills will be available when needed (Staffing).

Describe the plan for periodically assessing the contract, determining areas for improvement, gaining Government approval, and implementing improvement plans (Process Improvement).

Describe the plan to develop, update, and monitor the project schedule using Microsoft Project version 2010 compatible or a version otherwise approved by the Government and to provide Integrated Master Schedule (IMS) derived schedule and supporting data to the Government.

Risk Management Within the Project Management Plan, the SI shall prepare a Risk Management Plan (RMP). The RMP shall describe the SI’s approach to determining, reporting, rating, and monitoring risks within the project.

The SI shall execute Risk Management in accordance with the TFITS Risk Management Plan.

The SI shall develop and share with the Government risk reports summarizing the risks and identifying the likeliness and consequences of each risk.

Reporting and Monitoring The SI shall describe the metrics, reporting mechanisms, and control procedures it will use to measure, report, and control the contract including requirements, the schedule, resources, and quality assurances.

The SI’s performance monitoring efforts (e.g., performance metric monitoring, risk analysis) shall identify and support the determination of performance variances within sufficient time allowing the SI the ability to implement corrective action before SI and/or system performance falls below acceptable thresholds.

All Priority 1 metrics from the TFITS PMP, previous month’s activities, updated risk register, upcoming activities, all incidents, summary of service issues, problem trends, progress towards the Performance Standard and Acceptable Quality Levels (AQLs), and anticipated travel (with a justification for the travel). The metrics submitted for the MSR shall be in accordance with the TFITS PMP.

The MSR shall include a report of the number of Help Desk tickets resolved during the first contact.

The SI shall participate in MCRISS Integrated Product Team meetings and Working Groups where program status will be reported. The SI shall aid in the development of meeting materials for the meetings listed in the table below. Bi-Monthly is defined as every other month and Bi-Weekly is defined as every other week. At a minimum, the SI shall attend the meetings listed in table 5.

Table 5: MCRISS Meetings

Quality Assurance and Control Within the Project Management Plan, the SI shall prepare a QAPP. The QAPP shall describe the SI’s approach to ensuring quality performance for all aspects of the contract. The QAPP shall include:

The SI’s quality assurance program shall provide a total quality management system approach to the MCRISS effort and shall include program and technical management, quality assurance, quality control, and performance management to achieve the control of product and service quality throughout the task performance.

The Government shall evaluate the SI’s performance under this contract in accordance with the QASP. The QASP focuses on what the Government must do to ensure that the SI has performed in accordance with the performance standards. It defines how the performance standards will be applied and the method and frequency of surveillance.

The SI’s systems engineering, quality assurance and quality control efforts shall comply with Government policy and instructions. These efforts shall be reflected in the SI’s PDSS, System Maintenance and Performance and will ensure both existing and new/enhanced capabilities meet the Government’s objectives for quality as defined in the AQLs.

Common Access Cards (CACs) CACs will only be issued to those contractors supporting this contract that have been authorized by the COR. The COR will only authorize CACs for those contractors that meet current Homeland Security Presidential Directive - 12 (HSPD-12) criteria and have a definitive requirement. CACs are not issued for convenience.

The SI shall notify the Government (in writing) within twenty-four hours of any SI personnel added or removed from the contract that have been granted system access, issued a CAC, and/or MCSC/Government building access.

If an SI employee’s open investigation closes and is not favorably adjudicated, the CAC must be immediately revoked, retrieved, and provided to the COR. Such employees are prohibited from working on the MCRISS SI contract. Facility Security Officers are responsible for notifying the MCSC Security Director if any SI performing on this contract receives an unfavorable adjudication after being issued a CAC. SI CACs are issued with a “ctr@marines.mil” email account that the individual SI is responsible to keep active by logging in on a regular basis (at least twice a month), sending an email and clearing any unneeded emails. SI’s are prohibited from “auto-forwarding” their .mil email account to any other account, including but not limited to a SI or home account.

Complete appropriate forms and processes in order to obtain valid access to systems and facilities. The forms and processes include but are not limited to: System Authorization Access Request (SAAR) (Exhibit 3), access to Operation Directive (OpDir), Marine Corps Certification & Accreditation Support Tool (MCCAST), access badges for Pentagon and MCSC, Contractor Verification System (CVS) and Joint Personnel Adjudication System (JPAS).

PDSS and Software Development Execution At a minimum, the SI for PDSS and Software Development Execution shall:

Perform quality assurance in accordance with the QASP.

Identify and manage risks in accordance with the Risk Management Plan.

Attend, provide agenda and meeting minutes, and participate in any ad hoc working groups, integrated product teams (IPTs), technical reviews, technical interchange meeting, in-process reviews (IPRs), and/or any other system specific meetings to support the requirements of the contract.

Performance Management The SI agrees to attend all Performance Evaluation Reviews (PERs) convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The Contracting Officer (KO), COR, and other Government personnel, as appropriate, may meet periodically with the SI to review the SI's performance. At these meetings the KO will apprise the SI of how the Government views the SI's performance and the SI will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues.

Contract Closeout Provide orderly closeout of the contract including final delivery of any remaining Government products and preparation of a final report to include lessons learned and analysis of task.

Configuration Management The SI shall implement the TFITS CMP for all configuration tasks.

Upon transition to the EDTE development and test environment, utilize the Government provided toolset to maintain configuration control of application source code via a standardized check-in and check-out process.

Integrated Master Schedule The SI shall develop and maintain an overall MCRISS project IMS throughout the contract POP. The MCRISS project IMS shall provide the Government information sufficient to demonstrate how the SI intends to manage the proposed effort.

At a minimum, the SI shall develop an IMS using Microsoft Project version 2010 compatible or a version otherwise approved by the Government. Table 6 identifies key milestones to be included in the IMS.

Table 6: Key Milestones

The Government will determine a date for the MCRISS project IMS to be baselined after the award of the contract. After the baseline is set, the SI will be required to submit a Government-approved Contractor-formatted Schedule Change Request for any task that might exceed it’s set baseline. Government approval is required for any task to be completed after it’s set baseline date.

RESERVED

Performance Standards The SI shall be monitored against the following performance standards and Acceptable Quality Levels listed in table 7.

Table 7: Acceptable Quality Levels

· In-Process Review

· Review and analyze monthly Contractor Invoice billing charges against planned tasks.

Contractor must meet 90%. Govenrment delays will not impact this metric.

Deliverables (Table 9: Deliverables) shall not require more than two review cycles prior to Government acceptance.

· Review of deliverables

· Review of Monthly Status Reports

· In-Process Review Contractor must meet 90%.

· In-Process Review

· Help Desk ticket logs 99.7%. Government incidents, incidents caused by external entities, or planned downtime will not impact this metric.

· Review of Monthly Status Reports

· In-Process Review 99.7%. Government incidents, incidents caused by external entities, or planned downtime will not impact this metric.

· In-Process Review

· Review of Help Desk tickets and associated metrics 95% compliance

· Quarterly Configuration Control Board Meetings.

95% compliance with the Government furnished TFITS Configuration Management (CM) Plan.

· Review Project IMS

· Review Monthly Status Reports

· In-Process Review SI will notify the Government of all license and warranty expirations no later than 1 year prior to the expiration date.

· based on the CITDB

· PIR

100% in accordance with Government Management Plans.

· Report IA activities in Monthly Status Report

· In-Process Review 100% compliance is required. Government actions or prioritizations do not affect this metric.

Applicable Documents and References.

Table 8 provides essential programmatic and technical information for each SI to consider while preparing their response.

Table 8: Other Guidance & Standards

Federal Acquisition Regulation (FAR)

Deliverables and Schedule.

All Deliverables shall be uploaded to the Government’s electronic repository (SharePoint) with a notification to the KO, COR, and the MCRISS Project Manager. The SI shall develop and deliver the following items listed in table 9.

Table 9: Deliverables

3.1.4.19.5 3.1.4.19.5.1

3.1.5.1.4 3.1.5.2.3 3.2.3.1.2 3.2.3.3.2

(Draft provided as part of the RFP response)

(Draft provided as part of the RFP response)

(Draft provided as part of the RFP response)

4.4.6

Government-Furnished Equipment (GFE) and Information.

The Government will furnish hardware (computer, phones, and approved software to perform their duties) and administrative material (paper and pens) for contractor personnel working at Government facilities. Contractor personnel not working in Government facilities may request Government-furnished laptops/tablets. These requests will be approved on a case-by-case basis.

The Government will provide all of the source code, system documentation, system manuals and WBT source code. The Government provides the shared data environment where all MCRISS program information resides. The shared data environment includes repositories to support the MCRISS Team’s configuration control process, baseline documentation, CITDB, action items, risk management, etc.

Period of Performance.

The Period of Performance will be as specified in Section B of the Solicitation.

Place of Performance.

The primary place of performance will be the contractor’s facility located within a reasonable commuting distance from MCB Quantico. On-site personnel will be located at the James Wesley Marsh Center in Quantico, VA. Personnel required to be on-site full-time include database administrators and Help Desk personnel. The Contractor Project Manager may be required to work on-site part-time. The Contractor is expected to attend and participate in meetings and telephone conferences in the Quantico, Virginia area.

Travel and Other Direct Costs.

The Government shall not pay travel costs for SI personnel to commute to work. Travel required for the convenience of the SI to facilitate the SI’s staffing of the contract shall be the responsibility of the SI. Travel for this purpose shall not be reimbursed.

Any travel outside of the NCR requires Government COR approval/authorization. The Government does not anticipate any travel for this effort, with the exception of a possible MCEITS migration (Kansas City, MO). Travel that may be associated with the MCEITS migration should be included in the overall IDIQ proposed price. Travel in support of a MCEITS migration would be approximately two weeks in total duration.

ODCs associated with PDSS and software development will be on a cost only reimbursable basis. No fee shall be allowed for travel or ODC costs. ODCs associated with PDSS and software development will be on a cost only reimbursable basis. No fee shall be allowed for travel or ODC costs.

Appendix A. System Data Exchange Diagram Figure 2 provides a view of the System Interfaces.

Figure 2. System Interface View

A-1 Appendix B. System Data Exchange Matrix

B-1 Appendix C. MCRISS Accreditation Boundary Figure 3 provides a view of the current MCRISS accreditation boundary.

Figure 3. System Architechture Diagram

C-1 Appendix D. Current MCRISS Wbt Modules

· Create Events

· Update Unscheduled Events

· Update Unallocated Events Learn how to navigate the Working File, Create Events and update Unscheduled and Unallocated Events.

· Verify the Weekly/Monthly Activity Report Learn how to approve In, Mid and Out briefs and verify the Weekly/Monthly Activity Report.

· Upload and reconcile a List Learn how to prepare a List and how to Upload and reconcile a List.

· Set High School working days according to the Time Distribution Plan.

Learn how to set working and non-working days for the RSS and Recruiter and how to set high school working days according to the Time Distribution Plan.

· Track Referrals Learn how to schedule Program Action Dates and track referrals.

· Create schedule and update a Media Card

· Create schedule and update a Take One Location

· Create schedule and update an IRT Card Learn how to create, schedule and update Contact, Media, Take One and Itinerant Recruiting Trip Cards.

· Enter a Lead Learn how to search for a Lead and enter a Lead.

· Track Milestones and develop the new HS/CC Plan Learn how to search for the HS/CC Visit Card, schedule and complete Events and track Milestones and develop the new HS/CC Plan

· Set Objective Weeks

· Set RSS Objectives

· Set Recruiter Objectives Learn how to view the data analysis sheet, identify its components, set objective weeks and set Recruiting Substation and Recruiter prospecting objectives.

· Schedule an Event

· Complete an Event Learn how to create a Prospect Applicant Card .

D-2 Appendix E. ECPs for Task Order List of ECPs for this Task Order

ECP No.

MCRISS_294

Develop Recruiter Client Tool

Description: Develop and deploy a MCRISS offline Recruiter Client capability for Marine Corps Recruiters.

Deliverables: See Table 10

Stakeholders/User Groups: MCRISS PMO, MCRC Functional Owners

Description of Higher Level Requirement:

E-2 image1.wmf image2.png image3.jpg image4.jpg