PWS-_DRAFT_for_Seaport.doc
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,158
On Slideshare
1,158
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
12
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. SPAWAR HQ ARCHITECTURE AND HUMAN SYSTEMS GROUP ARCHITECTURE/SYSTEMS ENGINEERING SUPPORT Performance Work Statement SPAWAR HQ Architecture and Human Systems Group Architecture/Systems Engineering Support Code 5.0.1.2 06 January 2010 1.0 INTRODUCTION The Department of the Navy, Space and Naval Warfare System Command is acquiring architecture/systems engineering support and program management services for the development of the Navy/Department of Navy Enterprise Architecture (N/DoN EA). 2.0 BACKGROUND The N/DoN EA describes the construct and the framework for Naval Warfare in the Information Age transforming the Navy and Marine Corps to make Network Centric Warfare (NCW) a reality. The N/DoN EA integrates Warriors, Sensors, Networks, Command & Control, Platforms, Weapons, and Business Systems into a networked, distributed joint combat force, scalable across the spectrum of conflict from seabed to space and from sea to land. The N/DoN EA will contain the enabling elements for the top-level Joint Capability Areas (JCA) assigned to the Department of the Navy and provides guidance to Program of Record architectures. The architecture will also be coordinated with Service transformation initiatives in the Army, Air Force, and Coast Guard. A fundamental N/DoN EA objective is the development of a Naval networking infrastructure and integrated applications suite with full interoperability among the service components, Joint Task Force elements, and allied/coalition partners. The N/DoN EA will incorporate common engineering, information, protocols, computing, and interface standards across various computing environments and platforms. This blueprint will be based on joint and industry standards, with development and implementation coordinated with transformational initiatives in the Army, Air Force, and Coast Guard as well as Joint Commands and allies. The N/DoN EA is based on a commercial Distributed Services model. This offers the ability to reuse technology across the Naval and Joint enterprise by providing components that can be easily connected in a wide variety of ways to provide new Warfighter and Business mission capabilities with minimal development effort and without requiring detailed knowledge of the internal workings and implementation details of an application. The Distributed Services approach will allow developers to wrap legacy allied/coalition applications for compatibility. Proposed multi-level security implementations will enable efficient and secure sharing of information. The N/DoN EA supports Network Centric Warfare capabilities by: • Aligning and integrating efforts that look across all programs, enabling capabilities, synergies, and efficiencies that would not otherwise be realized under the existing paradigm of individual stove- piped programs and efforts; • Leveraging and integrating existing DoD efforts for the development of a dynamic, multi-path survivable network which will support the integration of existing systems; • Incorporating new technologies and research to provide Human-Centric Design; 1
  • 2. SPAWAR HQ ARCHITECTURE AND HUMAN SYSTEMS GROUP ARCHITECTURE/SYSTEMS ENGINEERING SUPPORT Performance Work Statement • Enhancing Joint, allied, coalition interoperability; • Leveraging Science and Technology (S&T) and operational experimentation to rapidly deliver prototype capability to the Fleet; • Collaborating together with industry to develop and implement a commercially-based, government- sponsored N/ DoN EA open architecture (non-proprietary). The N/DoN EA is described as collaborative, interactive, segmentable, federated and extensible. The N/ DoN EA supports the Spiral Development and Evolutionary Acquisition process bridging the gap between legacy systems of today and the fully netted force of the future Navy. The N/DoN EA does not have a specific end-state configuration; however, it will provide a continuing impetus and support to Naval Transformation, and provide a new way of doing business in the Department of the Navy The SPAWAR Chief Engineer (SPAWAR 5.0) is the Navy’s technical authority for the JCAs of Battlespace Awareness, Command and Control, Net-Centric Operations, Naval Space Operations, and Naval Information Operations. In this role, SPAWAR 5.0 is designated as the Navy’s Chief System and Technical Architect. 3.0 SCOPE The scope of the N/DoN EA includes Navy and Marine Corps forces and their support elements, including warriors, combat systems, sensors, platforms, networks, command and control systems (including decision aids), and business and other support systems. The N/DoN EA will be integrated with the appropriate architectures from other Services and the joint/multi-national community and, ultimately, civilian agencies that support or are supported by the naval warfighting and business enterprise. The N/DoN EA is related to the GIG as follows: Any information flow, information item or process providing common service to more than one user node in support of a naval mission capability will be considered a part of the N/DoN EA. Information flows, information items and processes that are integral and completely self-contained within a particular naval system will not necessarily be a part of the N/DoN EA. However, the goal will be to assimilate all common information flows, duplicative information items and overlapping processes into the N/DoN EA. The N/DoN EA is the basis for acquisition, system engineering, and solution engineering in the Navy. All Navy requirements will be captured by the N/DoN EA as direction to all programs and initiatives. Program of Record architectures will be developed to support the N/DoN EA. The N/DoN EA will provide an overarching framework to the Department of Defense JCAs assigned to the Department of the Navy; Force Support, Battlespace Awareness, Force Application, Logistics, Command and Control, Net- Centric, Protection, Building Partnerships, and Corporate Management and Support. SPAWAR 5.0 is designated by OPNAV as the Navy’s Chief System and Technical Architect. The N/DoN EA provides top-down guidance to programs and initiatives and provides the underlying data to the OPNAV staff and the acquisition community. The Enterprise System and Technical Architect is a vital member of the team ensuring that 2
  • 3. SPAWAR HQ ARCHITECTURE AND HUMAN SYSTEMS GROUP ARCHITECTURE/SYSTEMS ENGINEERING SUPPORT Performance Work Statement POR architectures align to the JCA framework. As such they participate in high-level governance forums and exercise Systems Engineering Technical Authority throughout the SPAWAR claimancy. These Enterprise Architect functionalities provide the framework for integrating the solution architectures into a coherent data set and presentation of the N/DoN EA data used for Navy Resource Planning and Acquisition Planning by the OPNAV Staff and ASN RDA. 3
  • 4. SPAWAR HQ ARCHITECTURE AND HUMAN SYSTEMS GROUP ARCHITECTURE/SYSTEMS ENGINEERING SUPPORT Performance Work Statement 4.0 APPLICABLE DIRECTIVES/DOCUMENTS The Contractor shall adhere to the following documents in accordance with paragraph 5.0, Performance Requirements: Document Type No./Version Title Date Naval (ser) Navy Enterprise Architecture Current Naval (ser) Department of the Navy Enterprise Current Architecture DOD (ser) DoD Architecture Framework Current DOD CJCSI Interoperability and Supportability of Current 6212.01(ser) Information Technology and National Security Systems DOD CJCSI Joint Capabilities Integration and Current 3170.01(ser) Development System DOD Direction 5000.01 Acquisition System Current DODINST 5000.02 Operation of the Defense Acquisition Current System SPAWARINST 5400.3 Systems Engineering Technical Review Current Program DoN CIO Memo (ser) DoN Enterprise Architecture ver 1.0 Current 5.0 PERFORMANCE REQUIREMENTS The Contractor shall perform the following tasks for SPAWAR HQ Architecture and Human Systems Group, Architecture/Systems Engineering development and program support in accomplishing the requirements of this Task Order (TO). The Contractor shall provide timely assistance to meet program emergent requirements as requested by the Program Manager or other properly designated authority. All required written documentation, reports, briefing materials, viewgraphs, studies, meeting minutes, and other materials as described below shall be submitted in the requested format, without spelling, grammatical, or calculation errors and in accordance with the directives listed in Section 4.0 Applicable Directives/Documents where appropriate. The contractor shall provide architecture/system engineering and program support to SPAWAR HQ Architecture and Human Systems Group in the following functional areas: 5.1 Develop appropriate Enterprise Architecture products which provide top-down guidance for PMs (RDT&E). The contractor shall research and develop the N/DoN EA to include the Service Oriented Architecture (SOA) concepts on a spiral basis. Taking this approach, the contractor shall develop the enterprise-level architecture products in terms of Operations, Systems, and Services. These Systems and Services will describe the information services necessary to support Operations, with mapping to existing, planned and target systems that implement the services. These Systems and Services will depict functional views of the architecture and provide the necessary transition between the Operational Architecture and the System Architecture that the PEOs/PMs develop to implement the “to-be” functionalities. 4
  • 5. SPAWAR HQ ARCHITECTURE AND HUMAN SYSTEMS GROUP ARCHITECTURE/SYSTEMS ENGINEERING SUPPORT Performance Work Statement The N/DoN EA Operational, System, and Service views will be derived from the data associated with the set of Authoritative Mission Threads. The typical views developed shall include, but not be limited to, the list of deliverables detailed in Section 6.0. All Architecture products will be developed and refined iteratively within the SYSCOM Architecture Development and Integration Environment (SADIE) as new architectural data is available. The N/DoN EA will provide guidance to the Program Executive Office as to the linkage between program of record (POR) Architectures and JCAs. One manifestation of this linkage is the use of N/DoN EA data to build the PEO C4I Master Plan. Performance Standard: Fully coordinated among stakeholders. Timeliness: Meets required deadlines. Quality: Properly prepared in the appropriate format. Factually correct and meets intended purpose. Acceptable Quality Level (AQL): First iterationdraft: No more than average two mistakes (substantive or typographic) per page. Second and further iterations: No substantive errors, no more than one typo in five pages. Provide resolution on 95% of review comments. Monitoring Method: Contractor shall report monthly on accomplishments. Client feedback and efforts to remedy or mitigate any problems will be monitored. The program office will perform period verification of contractor submissions. 5.2 Develop appropriate target Technical Architecture products which provide top-down guidance for PMs (RDT&E). The contractor shall research technical standards and develop the N/DoN EA Technical Views (TV-1, TV-2) and POR TVs as directed. The TVs are derived from the Operational Views (OVs) and Systems Views (SVs). The Naval Standards Working Group (NSWG) was chartered by ASN RDA CHSENG and uses subject matter experts (SME), working groups, and peer reviews to research the standards needed by N/DoN and by DoD. Many of the N/DoN EA standards supporting warfighting and business environments will be industry based. Several commercial bodies such as the World Wide Web Consortium (W3C), Internet Engineering Task Force (IETF), IEEE, and other commercial standards bodies develop and ratify many of the IT standards. The DISA Defense Information Standards Registry (DISR), ASSIST (source for government specifications and standards), and industry websites will be primary tools for research into IT standards needed by Navy, Air Force, Army, and Marine Corps to ensure interoperability. The contractor will utilize these tools and resources in researching IT standards. The criteria for N/DoN EA standards are: 1. Interoperability – Support implementation of open architecture 2. Maturity – Standards should be technically mature 3. Ease of Implementation – Have technical guidance and market support 4. Public Availability – Should not be proprietary 5. Consistent with Authoritative Sources – Standards consistent with public law, public regulation, and authoritative guidance documents TVs are developed using the DISR. The standards in TVs should be updated to keep pace with changes in the commercial sector and DISR updates. The TV-1 and TV-2 are created for the N/DoN EA and PORs using a mixture of government and commercial standards. Examples of government 5
  • 6. SPAWAR HQ ARCHITECTURE AND HUMAN SYSTEMS GROUP ARCHITECTURE/SYSTEMS ENGINEERING SUPPORT Performance Work Statement standards are North Atlantic Treaty Organization (NATO) Standardization Agreements (STANAGs) for Allied Interoperability. Tasks may include, but are not limited to: 1. Develop EA TVs and register and store in DISR SIPR per DoD Directives. 2. Develop POR TVs as directed and register and store in DISR SIPR per DoD Directives. 3. Research emerging standards and develop technical papers for various IT areas such as SOA and cloud computing. 4. Research standards that should be retired. Performance Standard: Fully coordinated among stakeholders. Timeliness: Meets required deadlines. Quality: Properly prepared in the appropriate format. Factually correct and meets intended purpose. Acceptable Quality Level (AQL): First iterationdraft: No more than average two mistakes (substantive or typographic) per page. Second and further iterations: No substantive errors, no more than one typo in five pages. Provide resolution on 95% of review comments. Monitoring Method: Contractor shall report monthly on accomplishments. Client feedback and efforts to remedy or mitigate any problems will be monitored. The SPAWAR HQ Architecture and Human Systems Group will perform periodic verification of contractor submissions. 5.3 Update and Maintain N/DoN EA to support Navy Resource Management and Acquisition Planning (O&MN). The contractor shall support SPAWAR HQ Architecture and Human Systems Group in the continuing process of updating and maintaining the N/DoN EA Operational Views (OV), System Views (SV), and Technical Views (TV) to support Navy Resource Management and Acquisition Planning. Architecture data and architecture-related products will be configuration managed in SADIE, the single repository for the N/DON EA data. The N/DoN EA data can be used for Navy Resource and Acquisition Planning by OPNAV and ASN RDA; to support modeling and simulation data requirements; and can be reused by program offices for program development and POR architecture development. The N/DoN EA Operational and System Views will be updated to incorporate new information as directed by OPNAV and ASN RDA. The N/DoN EA Technical Views will be updated three times annually in relation to the DISR updates. Updated data sets will be approved as authoritative according to DoN CIO EA Policy. Performance Standard: Fully coordinated among stakeholders. Timeliness: Meets required deadlines. Quality: Properly prepared in the appropriate format. Factually correct and meets intended purpose. Acceptable Quality Level (AQL): First iterationdraft: No more than average two mistakes (substantive or typographic) per page. Second and further iterations: No substantive errors, no more than one typo in five pages. Provide resolution on 95% of review comments. Monitoring Method: Contractor shall report monthly on accomplishments. Client feedback and efforts to remedy or mitigate any problems will be monitored. The SPAWAR HQ Architecture and Human Systems Group will perform periodic verification of contractor submissions. 5.4 Integrator and Configuration Manager for the Navy/DoN Enterprise Architecture (RDT&E). 6
  • 7. SPAWAR HQ ARCHITECTURE AND HUMAN SYSTEMS GROUP ARCHITECTURE/SYSTEMS ENGINEERING SUPPORT Performance Work Statement The contractor shall support SPAWAR HQ Architecture and Human Systems Group as integrator for the N/DoN EA products and to develop and manage the configuration of the integrated architecture repository. In order to ensure architecture data integrity, the contractor shall support SPAWAR HQ Architecture and Human Systems Group by developing and managing the configuration of the N/DoN EA data. The SYSCOM Architecture Development and Integration Environment (SADIE) will be used as the single N/DoN EA repository. Performance Standard: Fully coordinated among stakeholders. Timeliness: Meets required deadlines. Quality: Properly prepared in the appropriate format. Factually correct and meets intended purpose. Acceptable Quality Level (AQL): First iterationdraft: No more than average two mistakes (substantive or typographic) per page. Second and further iterations: No substantive errors, no more than one typo in five pages. Provide resolution on 95% of review comments. Monitoring Method: Contractor shall report monthly on accomplishments. Client feedback and efforts to remedy or mitigate any problems will be monitored. The SPAWAR HQ Architecture and Human Systems Group will perform periodic verification of contractor submissions. 5.5 Conduct Technical Reviews in Support of Systems Engineering Technical Authority (SETA) Operations (O&MN). The contractor shall support SPAWAR HQ Architecture and Human Systems Group in conducting Systems Engineering Technical Authority Operations. The contractor will support Technical Warrant Holders (TWHs) in the areas of Architecture and Standards by providing technical reviews of documents in support of Systems Engineering Technical Review (SETR) events, Joint Capabilities Integration and Development System (JCIDS) document reviews, and program support efforts. The contractor will attend meetings as required on behalf of the TWH and provide technical analysis of meetings and documents to support SETA Operations. Performance Standard: Fully coordinated among stakeholders. Timeliness: Meets required deadlines. Quality: Properly prepared in the appropriate format. Factually correct and meets intended purpose. Acceptable Quality Level (AQL): First iterationdraft: No more than average two mistakes (substantive or typographic) per page. Second and further iterations: No substantive errors, no more than one typo in five pages. Provide resolution on 95% of review comments. Monitoring Method: Contractor shall report monthly on accomplishments. Client feedback and efforts to remedy or mitigate any problems will be monitored. The SPAWAR HQ Architecture and Human Systems Group will perform periodic verification of contractor submissions. 5.6 Requirements Analysis, Architecture Development, and Engineering (RDT&E). The contractor shall support SPAWAR HQ Architecture and Human Systems Group in the research and development of operational, system and technical architecture products along with Human Systems Integration (HSI) analysis that addresses roadmaps from other domains, e.g. Combat Systems OA, C4ISR NESI, Business IT FAM, Sea Warrior ILE, etc. These architecture products shall also include S&T, R&D, and FNC projects that support modeling and simulation or that have the potential to transition into programs of record (PORs) and fill important capability gaps. Performance Standard: Fully coordinated among stakeholders. Timeliness: Meets required deadlines. Quality: Properly prepared in the appropriate format. Factually correct and meets intended purpose. 7
  • 8. SPAWAR HQ ARCHITECTURE AND HUMAN SYSTEMS GROUP ARCHITECTURE/SYSTEMS ENGINEERING SUPPORT Performance Work Statement Acceptable Quality Level (AQL): First iterationdraft: No more than average two mistakes (substantive or typographic) per page. Second and further iterations: No substantive errors, no more than one typo in five pages. Provide resolution on 95% of review comments. Monitoring Method: Contractor shall report monthly on accomplishments. Client feedback and efforts to remedy or mitigate any problems will be monitored. The SPAWAR HQ Architecture and Human Systems Group will perform periodic verification of contractor submissions. 5.7 Joint interoperability (RDT&E). The contractor shall support SPAWAR HQ Architecture and Human Systems Group in the research and development of joint interoperability by using Joint mission threads to build on the Architecture and Standards and Enterprise Architecture. Research interoperability issues between the Army, Air Force, Marine Corps, Coast Guard, Navy, Allies, Coalition, and other government agency architecture developments to leverage work already in progress in other areas and increase interoperability and efficiency. Performance Standard: Fully coordinated among stakeholders. Timeliness: Meets required deadlines. Quality: Properly prepared in the appropriate format. Factually correct and meets intended purpose. Acceptable Quality Level (AQL): First iterationdraft: No more than average two mistakes (substantive or typographic) per page. Second and further iterations: No substantive errors, no more than one typo in five pages. Provide resolution on 95% of review comments. Monitoring Method: Contractor shall report monthly on accomplishments. Client feedback and efforts to remedy or mitigate any problems will be monitored. The SPAWAR HQ Architecture and Human Systems Group will perform periodic verification of contractor submissions. 5.8 SPAWAR CAO IPT Support and Execution (O&MN). The contractor shall provide support to the SPAWAR HQ Architecture and Human Systems Group in the execution of Competency Aligned Organization-Integrated Product Team (CAO-IPT). Assist in the development of a competency process description for implementation across the Architecture, Standards, and Human Systems Integration competencies within the SPAWAR claimancy. These efforts will also include the development of appropriate reports in support of SPAWAR claimancy efforts with regards to the Balanced Scorecard, Capability Maturity Model Integration (CMMI), and other process improvement initiatives. Performance Standard: Fully coordinated among stakeholders. Timeliness: Meets required deadlines. Quality: Properly prepared in the appropriate format. Factually correct and meets intended purpose. Acceptable Quality Level (AQL): First iterationdraft: No more than average two mistakes (substantive or typographic) per page. Second and further iterations: No substantive errors, no more than one typo in five pages. Provide resolution on 95% of review comments. Monitoring Method: Contractor shall report monthly on accomplishments. Client feedback and efforts to remedy or mitigate any problems will be monitored. The SPAWAR HQ Architecture and Human Systems Group will perform periodic verification of contractor submissions. 6.0 DELIVERABLES The Contractor shall provide deliverables in accordance with the PWS and sample list below. Deliverables shall be prepared in contractor format, except the architecture data and architecture- related products, that will be developed in accordance with applicable DoD Directives and 8
  • 9. SPAWAR HQ ARCHITECTURE AND HUMAN SYSTEMS GROUP ARCHITECTURE/SYSTEMS ENGINEERING SUPPORT Performance Work Statement configuration managed in the SYSCOM Architecture Development and Integration Environment (SADIE). All work products generated from the included tasks remain government property. 9
  • 10. SPAWAR HQ ARCHITECTURE AND HUMAN SYSTEMS GROUP ARCHITECTURE/SYSTEMS ENGINEERING SUPPORT Performance Work Statement Views and Products 1. Overview and Summary Information (AV-1), Interim and final. 2. Integrated Dictionary (AV-2), Interim and final. 3. Vision (CV-1), Interim and final. 4. Capability Taxonomy (CV-2), Interim and final. 5. Capability Phasing (CV-3), Interim and final. 6. Capability Dependencies (CV-4), Interim and final. 7. Capability to Organizational Development Mapping (CV-5), Interim and final. 8. Capability to Operational Activity Mapping (CV-6), Interim and final. 9. Capability to Services Mapping (CV-7), Interim and final. 10. Conceptual Data Model (DIV-1), Interim and final. 11. Logical Data Model (DIV-2), Interim and final. 12. Physical Data Model (DIV-3), Interim and final. 13. High-Level Operational Concept Graphic (OV-1), Interim and final. 14. Operational Resource Flow Description (OV-2), Interim and final. 15. Operational Resource Flow Matrix (OV-3), Interim and final. 16. Organizational Relationships Chart (OV-4), Interim and final. 17. Operational Activity Decomposition Tree (OV-5a), Interim and final. 18. Operational Activity Model (OV-5b), Interim and final. 19. Operational Rules Model (OV-6a), Interim and final. 20. State Transition Description (OV-6b), Interim and final. 21. Event-Trace Description (OV-6c), Interim and final. 22. Project Portfolio Relationships (PV-1), Interim and final. 23. Project Timelines (PV-2), Interim and final. 24. Project to Capability Mapping (PV-3), Interim and final. 25. Services Context Description (SvcV-1), Interim and final. 26. Services Resources Flow Description (SvcV-2), Interim and final. 27. Systems-Services Matrix (SvcV-3a), Interim and final. 28. Services-Services Matrix (SvcV-3b), Interim and final. 29. Services Functionality Description (SvcV-4), Interim and final. 30. Operational Activity to Services Traceability Matrix (SvcV-5), Interim and final. 31. Services Resource Flow Matrix (SvcV-6), Interim and final. 32. Services Measures Matrix (SvcV-7), Interim and final. 33. Services Evolution Description (SvcV-8), Interim and final. 34. Services Technology and Skills Forecast (SvcV-9), Interim and final. 35. Services Rules Model (SvcV-10a), Interim and final. 36. Services State Transition Description (SvcV-10b), Interim and final. 37. Services Event-Trace Description (SvcV10c), Interim and final. 38. Technical Standards Profile (TV-1/StdV-1), Interim and final. 39. Technical Standards Forecast (TV-2/StdV-2), Interim and final. 40. Systems Interface Description (SV-1), Interim and final. 41. Systems Resource Flow Description (SV-2), Interim and final. 42. Systems-Systems Matrix (SV-3), Interim and final. 43. Systems Functionality Description (SV-4), Interim and final. 44. Operational Activity to Systems Function Traceability Matrix (SV-5), Interim and final. 45. Systems Resource Flow Matrix (SV-6), Interim and final. 46. Systems Measures Matrix (SV-7), Interim and final. 47. Systems Evolution Description (SV-8), Interim and final. 10
  • 11. SPAWAR HQ ARCHITECTURE AND HUMAN SYSTEMS GROUP ARCHITECTURE/SYSTEMS ENGINEERING SUPPORT Performance Work Statement 48. Systems Technology and Skills Forecast (SV-9), Interim and final. 49. Systems Rules Model (SV-10a), Interim and final. 50. Systems State Transition Description (SV-10b), Interim and final. 51. Systems Event-Trace Description (SV-10c), Interim and final. 52. Technical Review Comments and Responses, Draft and final. 53. Request(s) for Action and Request(s) for Information, Draft and final. 54. Metric Information as requested. 55. Monthly Status Report, No later than the 15th of the following month 56. Other products and reports as required. 7.0 GOVERNMENT FURNISHED PROPERTY (N/A) 8.0 ORGANIZATIONAL CONFLICT OF INTEREST (OCI) ACCESS TO OTHER CONTRACTOR’S PROPRIETARY DATA (N/A) 9.0 ELECTRONIC AND INFORMATION TECHNOLOGY (EIT) SECTION 508 ACCESSIBILITY STANDARDS DETERMINATION OF APPLICABILITY (N/A) 10.0 SECURITY REQUIREMENTS Architecture/Systems Engineering (SE) support of the effort requires access up to Secret information. The work performed by the Contractor will include access to unclassified and up to Secret data, information, and spaces. The Contractor will be required to attend meetings classified up to the Secret level. Note: If foreign travel is required, the contractor must obtain the country specific briefing, required within 90 days of departure, by calling (619) 553-2046, Topside, or (619) 524-3385, Old Town. A staff briefer will assist you in obtaining the country briefing. 11.0 NAVY MARINE CORPS INTRANET (NMCI) The nature of this task does not require Contractors to procure NMCI seats for personnel working at the Contractor site. 12.0 BEST PRACTICES Work performed by the Contractor shall provide support to SPAWAR HQ Architecture and Human Systems Group and SPAWAR command-level “Best Practices” principles incorporated in the SPAWAR Program Manager’s Toolkit Acquisition Support Office Guides (1) Acquisition Program Structure Guide; (2) Contract Management Process Guide; (3) Program Manager’s Handbook; (4) Scheduling Guide; (5) Systems Engineering Guide; (6) Technology Alignment Guide and support the command wide implementation process. 13.0 TECHNICAL POINT OF CONTACT Technical Point of Contact/Task Manager: LCDR Jeffrey S. Messerly, USN- SPAWARSYSCOM (HQ Architecture and Human Systems Group) email: Jeffery.Messerly@navy.mil phone (858) 537-0296 . 14.0 WORKLOAD ESTIMATE The following workload data is provided for informational purposes only to assist you in estimating the price of this Task Order. It, in no way, suggests that this is the effort required by this Task Order. 11
  • 12. SPAWAR HQ ARCHITECTURE AND HUMAN SYSTEMS GROUP ARCHITECTURE/SYSTEMS ENGINEERING SUPPORT Performance Work Statement Estimated annual labor level of effort: 40,000 man-hours (76.25% contractor-site and 13.75% Government-site) 12